search

vishwakulkarni / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
0 stars 0 forks source link

Crashes after upgrade to Jelly Bean #618

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
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

Original issue reported on code.google.com by prog...@gmail.com on 9 Nov 2012 at 10:45

Attachments:

GoogleCodeExporter commented 8 years ago 
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)

Original comment by prog...@gmail.com on 11 Nov 2012 at 8:24

GoogleCodeExporter commented 8 years ago 
Workaround: remove Samsung's OS and replace it with CyanogenMod 10.1. It works 
perfectly now.

Original comment by prog...@gmail.com on 13 Jan 2013 at 8:15

GoogleCodeExporter commented 8 years ago 
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.

Original comment by hansfn@gmail.com on 26 Jan 2013 at 11:10

GoogleCodeExporter commented 8 years ago 
This might be the bug in question:

https://android.googlesource.com/platform/frameworks/base.git/+/832815cb53e95148
5ff5a0e6c705446d0bfb5883

Original comment by desas...@gmail.com on 3 Oct 2013 at 3:11

GoogleCodeExporter commented 8 years ago 
This workaround seems to work: https://gist.github.com/desaster/6812612

Original comment by desas...@gmail.com on 4 Oct 2013 at 3:53