GNOME Bugzilla – Bug 481530
crash in Panel: I was launching synaptic...
Last modified: 2007-10-02 21:32:23 UTC
Version: 2.20.0.1 What were you doing when the application crashed? I was launching synaptics package manager on su session Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 40656896 vsize: 40656896 resident: 25047040 share: 13426688 rss: 25047040 rss_rlim: 4294967295 CPU usage: start_time: 1191052441 rtime: 282 utime: 254 stime: 28 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6f0b6b0 (LWP 3748)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 166361
Thread 1 (Thread 0xb6f0b6b0 (LWP 3748))
----------- .xsession-errors --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) (epiphany-browser:3986): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:3986): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed ** (gnome-cups-icon:3875): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3875): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3875): WARNING **: IPP request failed with status 1280 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 480982 ***