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 358044 - My panel crashes every times
My panel crashes every times
Status: RESOLVED DUPLICATE of bug 363437
Product: gnome-panel
Classification: Other
Component: general
2.16.x
Other Linux
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
: 366658 369062 374445 377302 382227 393448 393563 393847 400170 406424 411162 420373 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-27 22:24 UTC by logan.leichmann
Modified: 2007-03-21 01:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description logan.leichmann 2006-09-27 22:24:53 UTC
Steps to reproduce:
1. Launch Gnome (from GDM for example) and I see the Gnome foot for the menu and it crashes
2. 
3. 


Stack trace:
Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Memory status: size: 37937152 vsize: 0 resident: 37937152 share: 0 rss: 17207296 rss_rlim: 0
CPU usage: start_time: 1159268358 rtime: 0 utime: 38 stime: 0 cutime:33 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225967952 (LWP 627)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225967952 (LWP 627))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_recent_info_get_short_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_recent_info_get_display_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_recent_chooser_menu_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main
  • #0 __kernel_vsyscall


Other information:
Comment 1 logan.leichmann 2006-09-28 08:38:07 UTC
I have upgarded libgnomeui-2.16 to libgnomeui-2.16-r1 (under Gentoo Linux) and now, it's work well.
Comment 2 André Klapper 2006-10-29 15:16:04 UTC
*** Bug 366658 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2006-11-02 12:54:34 UTC
*** Bug 369062 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2006-11-13 10:53:53 UTC
*** Bug 374445 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2006-11-20 09:48:38 UTC
*** Bug 377302 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2006-12-05 23:11:22 UTC
*** Bug 382227 has been marked as a duplicate of this bug. ***
Comment 7 Jens Granseuer 2007-01-06 17:15:25 UTC
*** Bug 393448 has been marked as a duplicate of this bug. ***
Comment 8 Jens Granseuer 2007-01-06 17:16:21 UTC
*** Bug 393563 has been marked as a duplicate of this bug. ***
Comment 9 Jens Granseuer 2007-01-06 23:49:32 UTC
*** Bug 393563 has been marked as a duplicate of this bug. ***
Comment 10 Jens Granseuer 2007-01-06 23:53:27 UTC
According to bug 393563 this is not yet fixed with libgnomeui 2.16.1. Reopening. The gentoo change log only lists one change for 2.16.0 -> 2.16.0r1 and that is in upstream, too, so the real cause may be unrelated.

Trace from bug 393563:

Thread 1 (Thread -1225435472 (LWP 5420))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
    at gmessages.c line 552
  • #10 IA__gtk_recent_info_get_short_name
    at gtkrecentmanager.c line 2208
  • #11 IA__gtk_recent_info_get_display_name
    at gtkrecentmanager.c line 1588
  • #12 idle_populate_func
    at gtkrecentchoosermenu.c line 902
  • #13 g_idle_dispatch
    at gmain.c line 3926

Comment 11 mts 2007-01-07 13:41:24 UTC
*** Bug 393847 has been marked as a duplicate of this bug. ***
Comment 12 mts 2007-01-09 15:35:40 UTC
This helped for me:

solution:
delete the
recently-used.xbel
file found in your home directory

I found it from:
http://ubuntuforums.org/showthread.php?t=316356
Comment 13 Kjartan Maraas 2007-02-09 14:54:53 UTC
*** Bug 400170 has been marked as a duplicate of this bug. ***
Comment 14 Christian Kirbach 2007-02-10 22:45:42 UTC
good trace, dups, confirming, blaming Vincent ;)

Comment 15 Christian Kirbach 2007-02-10 22:46:11 UTC
*** Bug 406424 has been marked as a duplicate of this bug. ***
Comment 16 Christian Kirbach 2007-02-10 22:46:40 UTC
intresting comment from last dup

"I had an obviously very corrupted ISO on my computer and I meant to "Move to
Trash" but instead I missed and hit "Extract Here" which caused gnome-panel to
crash violently and whenever I login to Ubuntu with a gnome session, the panel
crashes, comes up with a bug report window and then will continuously restart
and crash, over and over again until I restart X.

Out if desperation, I recompiled gnome-panel from source but had no effect
other than some better debugging information. So the first trace/debug info
block that I have provided is from the original panel provided with Ubuntu, and
the second one is from after I recompiled it."
Comment 17 jimah45abmw 2007-02-11 00:59:50 UTC
Well, Bug 400170 could offer us an obviously very corrupted ISO.
Comment 18 admin.maddog39 2007-02-11 04:01:16 UTC
Okay, I was the author of that duplicate entry and I will attach the ISO for anyone who wants it. But be careful with it cuz it screwed everything up...
Comment 19 Vincent Untz 2007-02-12 20:03:22 UTC
This was a GTK+ bug.

*** This bug has been marked as a duplicate of 363437 ***
Comment 20 Christian Kirbach 2007-02-23 21:02:21 UTC
*** Bug 411162 has been marked as a duplicate of this bug. ***
Comment 21 Pedro Villavicencio 2007-03-21 01:06:20 UTC
*** Bug 420373 has been marked as a duplicate of this bug. ***