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 386102 - Window Selector: When I login now, my gno...
Window Selector: When I login now, my gno...
Status: RESOLVED DUPLICATE of bug 363437
Product: gtk+
Classification: Platform
Component: Class: GtkRecent
2.10.x
Other All
: High critical
: ---
Assigned To: gtk-bugs
Emmanuele Bassi (:ebassi)
: 386103 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-15 05:13 UTC by hone02
Modified: 2006-12-15 17:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description hone02 2006-12-15 05:13:08 UTC 
Version: 2.16.1

What were you doing when the application crashed?
When I login now, my gnome-panel (or I think it's gnome-panel from the error) keeps crashing.  I don't know why/how to fix.  I know the last dist-upgrade I did updated avahi-daemon and associated libs and kernel-2.6.17-10-generic.  Here's the log that bug buddy gives me:

Memory status: size: 36544512 vsize: 0 resident: 36544512 share: 0 rss: 13611008 rss_rlim: 0
CPU usage: start_time: 1166159190 rtime: 0 utime: 103 stime: 0 cutime:89 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-panel'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224984912 (LWP 6569)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 94318

Thread 1 (Thread -1224984912 (LWP 6569))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/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/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/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 

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0
Comment 1 palfrey 2006-12-15 17:02:14 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 palfrey 2006-12-15 17:02:50 UTC 
*** Bug 386103 has been marked as a duplicate of this bug. ***
Comment 3 Emmanuele Bassi (:ebassi) 2006-12-15 17:16:25 UTC 
looks a lot like bug #358044 - which in turn looks likely a duplicate of bug #363437.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

you should try and update to the latest gtk+.

*** This bug has been marked as a duplicate of 363437 ***