maverick vnc server gtk application crash due to no keymap

Bug #638686 reported by Shyam
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gtk+2.0 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: libgtk2.0-0

I start the vnc server in a system that is on Maverick beta. I also have icewm or lxde inside the vncserver. I connect to this vncserver from a different machine.

When I try to launch any gtk application (gvim, firefox), it crashes with a error message gdk-error : failed to get keymap.

Now, my vncserver is on display 1. I copy over the keymap from display 0. All gtk applications still crash.

I tried debugging it and found out that the bug (buck !!) stops in libgtk2.0-2.21.7. I tried replacing this is with the package found in lucid, and I do not see any crash.

Revision history for this message
Brian Fuller (slink3r) wrote :

Which VNC Server exactly?

Revision history for this message
Shyam (shyamk) wrote : Re: [Bug 638686] Re: maverick vnc server gtk application crash due to no keymap

Realvnc, tightvnc, tigervnc. All of them.
> Which VNC Server exactly?
>
> --
> maverick vnc server gtk application crash due to no keymap
> https://bugs.launchpad.net/bugs/638686
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gtk+2.0” package in Ubuntu: New
>
> Bug description:
> Binary package hint: libgtk2.0-0
>
> I start the vnc server in a system that is on Maverick beta. I also have
icewm or lxde inside the vncserver. I connect to this vncserver from a
different machine.
>
> When I try to launch any gtk application (gvim, firefox), it crashes with
a error message gdk-error : failed to get keymap.
>
> Now, my vncserver is on display 1. I copy over the keymap from display 0.
All gtk applications still crash.
>
> I tried debugging it and found out that the bug (buck !!) stops in
libgtk2.0-2.21.7. I tried replacing this is with the package found in lucid,
and I do not see any crash.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/638686/+subscribe

Revision history for this message
Brian Fuller (slink3r) wrote :

Sorry, I was trying to reproduce, but in 10.10, I'm having difficulties switching WM's, so hopefully somebody else can try this out on their system.

Revision history for this message
Shyam (shyamk) wrote :

Upgrading gtk+2.0 to gtk2.0-2.21.8 solved the problem for me.

Brian Fuller (slink3r)
Changed in gtk+2.0 (Ubuntu):
status: New → Fix Released
Changed in gtk+2.0 (Ubuntu):
status: Fix Released → In Progress
Revision history for this message
Chris (cabbrick1243-deactivatedaccount) wrote :

How would one go about updating to gtk2.0-2.21.8?
Is it just sudo apt-get install libgtk2.0-dev ?

Changed in gtk+2.0 (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Chris (cabbrick1243-deactivatedaccount) wrote :

I am reopening this because libgtk2.0 2.21.7 is not in synaptic for the server version.

Changed in gtk+2.0 (Ubuntu):
status: Fix Released → Incomplete
Revision history for this message
Chris (cabbrick1243-deactivatedaccount) wrote :

Sorry I meant that 2.21.7 is the latest version (even after sudo apt-get update)

Revision history for this message
Andy Stallwood (andy-stallwood) wrote :

I've managed to install gtk2.0 2.21.8 by downloading it manually

 wget http://ftp.uk.debian.org/debian/pool/main/g/gtk+2.0/libgtk2.0-0_2.21.8-1_i386.deb
 sudo dpkg --install libgtk2.0-0_2.21.8-1_i386.deb

I assume I'll need to reboot, although maybe a log-off and back on will do, so will do that, and report back if it's worked.

Revision history for this message
Andy Stallwood (andy-stallwood) wrote :

That seems to have helped a lot. It's not perfect, but it has helped.

The system is now usable. plymouthd has crashed according to a crash report indicator (but I've no idea what that does, and it doesn't seem to have stopped anything I use from working), and I have two other gtk related packages reporting broken dependencies, but again doesn't seem to be causing me a problem. All the keys on the keyboard work, via VNC, except d which seems to minimise the current window. But it's a heck of a lot better than it was.

Revision history for this message
Kalman Reti (kalman-reti) wrote :

I have the same problem in the Meerkat beta livecd, with both the tight vncserver and the vnc4 server.

I've confirmed that downloading the debian package has the effect Andy described, i.e. it doesn't
crash on every keystroke, but having the 'd' key not work makes many commands unusable, e.g.
'date'.

I run ubuntu on a laptop with a small screen and primarily use it via a much larger vnc server screen
from my desktop (with a large monitor), so this would effectively prevent my updating to a newer version...

Revision history for this message
Andy Stallwood (andy-stallwood) wrote :

I spoke too soon. The newer version has caused problems. Not least of which almost 100% CPU usage, an endless supply of new windows being created in the task bar, and for loads of packages to report broken dependencies meaning I can't upgrade anything else using the usual methods (Synaptic, apt-get, etc). So, I've decided to downgrade back to 2.21.7 and make do with ssh access for the time being.

Here's how I downgrade, if anyone is interested

wget http://de.archive.ubuntu.com/ubuntu/pool/main/g/gtk+2.0/libgtk2.0-0_2.21.7-1ubuntu1_i386.deb
sudo dpkg -i libgtk2.0-0_2.21.7-1ubuntu1_i386.deb

Revision history for this message
Simon Barnes (sw-barnes) wrote :

With reference to the 'd' key minimising windows, I have managed to work around this by going to System->Preferences->Keyboard Shortcuts and defining an alternative mapping for 'Hide all normal windows and set focus to the desktop'. I used Ctrl+M as it happens. The unwanted 'd' shortcut appeared after upgrading to Ubuntu 10.10 Maverick.

Revision history for this message
Andy Stallwood (andy-stallwood) wrote :

Thanks simon. Brilliant tip. At least i can now type sudo :-)
On 14 Oct 2010 16:06, "Simon Barnes" <email address hidden> wrote:
> With reference to the 'd' key minimising windows, I have managed to work
> around this by going to System->Preferences->Keyboard Shortcuts and
> defining an alternative mapping for 'Hide all normal windows and set
> focus to the desktop'. I used Ctrl+M as it happens. The unwanted 'd'
> shortcut appeared after upgrading to Ubuntu 10.10 Maverick.
>
> --
> maverick vnc server gtk application crash due to no keymap
> https://bugs.launchpad.net/bugs/638686
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gtk+2.0” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: libgtk2.0-0
>
> I start the vnc server in a system that is on Maverick beta. I also have
icewm or lxde inside the vncserver. I connect to this vncserver from a
different machine.
>
> When I try to launch any gtk application (gvim, firefox), it crashes with
a error message gdk-error : failed to get keymap.
>
> Now, my vncserver is on display 1. I copy over the keymap from display 0.
All gtk applications still crash.
>
> I tried debugging it and found out that the bug (buck !!) stops in
libgtk2.0-2.21.7. I tried replacing this is with the package found in lucid,
and I do not see any crash.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/638686/+subscribe

Revision history for this message
HardDisk (sambuntu-deactivatedaccount-deactivatedaccount-deactivatedaccount) wrote :

I can confirm the vnc gtk crash. I use x11vnc myself and usually load it in /etc/gdm/Init/Default and crashes randomly.

Revision history for this message
Jeremy Raymond (jeraymond) wrote :

As an example, a constant gtk crash that happens for me is in MonoDevelop when I do File -> Open...
On:
Ubuntu 10.10
tightvncserver 1.3.9
gtk 2.22.0
MonoDevelop 2.4

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gtk+2.0 (Ubuntu) because there has been no activity for 60 days.]

Changed in gtk+2.0 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.