After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 472189 - crash in Panel: removing keyboard layout...
crash in Panel: removing keyboard layout...
Status: RESOLVED DUPLICATE of bug 441520
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-31 11:59 UTC by mhuhtala
Modified: 2007-09-02 12:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mhuhtala 2007-08-31 11:59:07 UTC
Version: 2.18.3

What were you doing when the application crashed?
removing keyboard layout selector from the panel


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7PAE #1 SMP Fri Jul 27 18:01:30 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 104091648 vsize: 104091648 resident: 52539392 share: 47067136 rss: 52539392 rss_rlim: 4294967295
CPU usage: start_time: 1187189036 rtime: 963 utime: 853 stime: 110 cutime:0 cstime: 3 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 1073893728 (LWP 2828)]
(no debugging symbols found)
0x40000410 in __kernel_vsyscall ()

Thread 1 (Thread 1073893728 (LWP 2828))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 panel_profile_delete_object
  • #5 ??
    from /usr/lib/libbonoboui-2.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 bonobo_closure_invoke_va_list
    from /usr/lib/libbonobo-2.so.0
  • #8 bonobo_closure_invoke
    from /usr/lib/libbonobo-2.so.0
  • #9 ??
    from /usr/lib/libbonoboui-2.so.0
  • #10 _ORBIT_skel_small_Bonobo_UIComponent_execVerb
    from /usr/lib/libbonobo-2.so.0
  • #11 ??
    from /usr/lib/libORBit-2.so.0
  • #12 ORBit_OAObject_invoke
    from /usr/lib/libORBit-2.so.0
  • #13 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #14 ??
    from /usr/lib/libORBit-2.so.0
  • #15 ??
    from /usr/lib/libORBit-2.so.0
  • #16 ??
    from /usr/lib/libORBit-2.so.0
  • #17 ORBit_handle_request
    from /usr/lib/libORBit-2.so.0
  • #18 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #19 ??
    from /usr/lib/libORBit-2.so.0
  • #20 ??
    from /usr/lib/libORBit-2.so.0
  • #21 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (356105 sec old) ---------------------
Initializing nautilus-open-terminal extension
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
--- Hash table keys for warning below:
--> file:///home/mhuhtala
(nautilus:5178): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 1 element at quit time (keys above)
--- Hash table keys for warning below:
--> file:///home/mhuhtala
(nautilus:5178): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--------------------------------------------------
Comment 1 Vincent Untz 2007-09-02 12:37:30 UTC
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 441520 ***