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 162398 - infinite loop crash
infinite loop crash
Status: RESOLVED DUPLICATE of bug 157723
Product: gnome-panel
Classification: Other
Component: panel
2.8.x
Other Linux
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-28 18:42 UTC by Carlos Fenollosa
Modified: 2004-12-28 19:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description Carlos Fenollosa 2004-12-28 18:42:43 UTC
Panel crashes and it is impossible to reload. Always crashes.

I deleted all gconf and gnome config, but no luck. I noticed that if I
create a new user and run a gnome session, it does not crash.
Comment 1 Carlos Fenollosa 2004-12-28 18:43:30 UTC
the backtrace

Debugging Information:

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)...(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 1088105536 (LWP 8949)]
(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)...0xffffe410 in __kernel_vsyscall
()

Thread 1 (Thread 1088105536 (LWP 8949))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 egg_recent_item_get_uri_for_display
  • #5 egg_recent_item_get_short_name
  • #6 egg_recent_view_set_model
  • #7 egg_recent_view_set_model
  • #8 egg_recent_view_set_model
  • #9 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 egg_recent_model_changed
  • #15 egg_recent_view_set_model
  • #16 panel_recent_append_documents_menu
  • #17 panel_action_button_set_dnd_enabled
  • #18 panel_action_button_set_dnd_enabled
  • #19 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #24 panel_menu_bar_get_type
  • #25 panel_applet_on_load_queue
  • #26 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 main
  • #0 __kernel_vsyscall

Comment 2 Elijah Newren 2004-12-28 18:50:56 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but the maintainer(s) are looking for more information
to track down the problem.  Could you answer the question in bug 157723?

*** This bug has been marked as a duplicate of 157723 ***
Comment 3 Carlos Fenollosa 2004-12-28 19:04:34 UTC
okay, I discovered the source of the crash. Deleting ~/.recently-used solves the
problem. Took me about two hours to discover :(

I don't know if it's panel's fault, but an infinite crash isn't nice. How about
a crash handler (or exception, don't know how it is called) for reading
.recently-used ?

greetings