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 397258 - Crash due to bad .recently-used
Crash due to bad .recently-used
Status: RESOLVED DUPLICATE of bug 363437
Product: gnome-panel
Classification: Other
Component: panel
2.16.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-16 14:12 UTC by søren hauberg
Modified: 2007-01-17 11:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
The .recently-used that causes the crash (8.41 KB, text/plain)
2007-01-16 14:13 UTC, søren hauberg 		Details
It seems that it's the .recently-used.xbel that causes the problem (18.87 KB, text/plain)
2007-01-16 14:18 UTC, søren hauberg 		Details

Description søren hauberg 2007-01-16 14:12:41 UTC 
Steps to reproduce:
I'm not sure! If I start the panel with the attached .recently-used file in my home directory the panel crashed, but it's very possible that it'll only crash on my machine. This causes bug-buddy to be started, but I can't report a bug with it, because bug-buddy doesn't know about gnome-panel (it would seem). If I close bug-buddy, then gnome-panel will restart, which causes it to recrash, and now I have an infinite loop of a crashing gnome-panel. Result: I have a worthless computer (sorry about using such harsh words, but this is the worst program behavior I've ever seen).


Stack trace:


Other information:
Comment 1 søren hauberg 2007-01-16 14:13:25 UTC 
Created attachment 80400 [details]
The .recently-used that causes the crash
Comment 2 søren hauberg 2007-01-16 14:18:04 UTC 
Created attachment 80401 [details]
It seems that it's the .recently-used.xbel that causes the problem
Comment 3 Vincent Untz 2007-01-17 11:23:27 UTC 
Stack trace:

Memory status: size: 168632320 vsize: 168632320 resident: 22446080 share: 15970304 rss: 22446080 rss_rlim: -1
CPU usage: start_time: 1169032913 rtime: 108 utime: 95 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47134919822496 (LWP 19801)]
0x00002ade70d06eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 102931

Thread 1 (Thread 47134919822496 (LWP 19801))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib64/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib64/libglib-2.0.so.0
  • #8 IA__gtk_recent_info_get_short_name
    at gtkrecentmanager.c line 2248
  • #9 IA__gtk_recent_info_get_display_name
    at gtkrecentmanager.c line 1588
  • #10 idle_populate_func
    at gtkrecentchoosermenu.c line 902
  • #11 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #12 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #14 IA__gtk_main
    at gtkmain.c line 1024
  • #15 main
    at main.c line 95
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 4


Vincent Untz





          2007-01-17 11:27:34 UTC
        



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.


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