! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
xkb-plugin crashes at startup
Status:
RESOLVED: FIXED
Product:
Xfce4-xkb-plugin
Component:
General

Comments

Description Artur 2009-08-10 11:45:35 CEST
clean installed system, new user and default keymap (us)
I run "xfce4-panel -a"  and click at xkb-plugin but nothing happens on the panel
  
xfce4-panel writes at command line:
-----------------------------------
(xfce4-xkb-plugin:1637): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed

(xfce4-xkb-plugin:1637): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed

(xfce4-xkb-plugin:1637): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table != NULL' failed
The program 'xfce4-xkb-plugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
  (Details: serial 208 error_code 133 request_code 131 minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
libxfce4panel-Message: Keyboard Layouts: screen changed: 0

libxfce4panel-Message: No valid plug window.

(xfce4-panel:1634): Gtk-CRITICAL **: gtk_socket_get_id: assertion `GTK_WIDGET_ANCHORED (socket)' failed

(xfce4-panel:1634): libxfce4panel-CRITICAL **: An item was unexpectedly removed: "Keyboard Layouts".

-------------------------------------
 	
I also tried to install newest version of xkb-plugin but have the same result 

XFce-4.6, HAL is disabled
Comment 1 Artur 2009-08-18 12:40:55 CEST
Hm, I installed xfce-xkb-plugin 0.4.1 and it works good...
Comment 2 Jérôme Guelfucci editbugs 2010-02-25 12:12:10 CET
What version were you using when you had this problem?

Does the current release still have this issue?

Thanks in advance.
Comment 3 Lionel Le Folgoc 2011-04-09 21:00:11 CEST
Reporter wrote it was fixed in 0.4.1, closing.

Bug #5665

Reported by:
Artur
Reported on: 2009-08-10
Last modified on: 2011-04-09

People

Assignee:
Alexander Iliev
CC List:
2 users

Version

Version:
unspecified

Attachments

Additional information