Issue 618 in connectbot: Crashes after upgrade to Jelly Bean

[conne...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 618 by prog...@gmail.com: Crashes after upgrade to Jelly Bean
http://code.google.com/p/connectbot/issues/detail?id=618

What steps will reproduce the problem?
1. Install ConnectBot Samsung Galaxy S 3
2. Upgrade it to Jelly Bean
3. Run a SSH session and use it a few minutes
4. Switch to another application, and use it several minutes
5. Switch back to ConnectBot

What is the expected output? What do you see instead?
I expect to use the SSH connection, but ConnectBot freezes and then crashes.


What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
1.7.1 (from F-Droid)


What type of system are you trying to connect to?
Debian GNU/Linux Sid with tmux and Weechat


If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?
echo $TERM => screen
uname -a => Linux Hydrogen 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC
2012 x86_64 GNU/Linux


I'm sending you the logcat captured while ConnectBot was "crashing". You
can see the string "#limnoria-bo" (at the tenth line, and in the core
dump), which is part of the text displayed in the terminal.

Regards,
Valentin

Attachments:
logcat.txt 12.0 KB

[conne...@googlecode.com]

Comment #1 on issue 618 by prog...@gmail.com: Crashes after upgrade to
Jelly Bean
http://code.google.com/p/connectbot/issues/detail?id=618

Actually, it happens when I enable the virtual keyboard, ie. when I click
the Keyboard button, or when I switch from another app.
But, it does not appear if I rotate the screen (with or without the
keyboard enabled)

[conne...@googlecode.com]

Comment #2 on issue 618 by prog...@gmail.com: Crashes after upgrade to
Jelly Bean
http://code.google.com/p/connectbot/issues/detail?id=618

Workaround: remove Samsung's OS and replace it with CyanogenMod 10.1. It
works perfectly now.

[conne...@googlecode.com]

Comment #3 on issue 618 by han...@gmail.com: Crashes after upgrade to Jelly
Bean
http://code.google.com/p/connectbot/issues/detail?id=618

For the record: I just got a Samsung Galaxy S3 and I'm experiencing these
crashes as well. The app crashes when I'm using the stock Samsung keyboard.

[conne...@googlecode.com]

Comment #4 on issue 618 by desas...@gmail.com: Crashes after upgrade to
Jelly Bean
http://code.google.com/p/connectbot/issues/detail?id=618

This might be the bug in question:

https://android.googlesource.com/platform/frameworks/base.git/+/832815cb53e951485ff5a0e6c705446d0bfb5883

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[conne...@googlecode.com]

Comment #5 on issue 618 by desas...@gmail.com: Crashes after upgrade to
Jelly Bean
http://code.google.com/p/connectbot/issues/detail?id=618

This workaround seems to work: https://gist.github.com/desaster/6812612