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 162598 - Logon as non-root user crashes gnome-panel. Logon as root or different non-root does not.
Logon as non-root user crashes gnome-panel. Logon as root or different non-r...
Status: RESOLVED DUPLICATE of bug 160606
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-12-31 01:33 UTC by redkirk
Modified: 2004-12-31 01:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description redkirk 2004-12-31 01:32:36 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-panel
Severity: normal
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Logon as non-root user crashes gnome-panel.  Logon as root or different non-root does not.
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
1. Logging on as root there is no problem.

2. Upon login as non-root user an error dialog appears: "Application
''gnome-panel'' has quit unexpectedly.  You can inform the developers of
what happened to help them fix it. Or you can restart the application
right now."
     2a. Choosing "restart" produces the error: "I've detected a panel
already running and will now exit. OK"
          2a-1. Choosing to click "OK" causes the "I've detected a panel
already running and will now exit. OK" to close this error message and
then have it reappear.
     2b. Choosing "Close" causes the  "Application ''gnome-panel'' has
quit unexpectedly..."  error to close and then reappear.

3. Logging on as a different non-root user does not appear to reproduce
the error.

Steps to reproduce the crash:
1. Logging on as root
2. Logging on as problem user
3. Logging on as a different user

Expected Results:


How often does this happen?
Everytime logging on as problem user.

Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...[Thread debugging using
libthread_db enabled]
[New Thread -151128384 (LWP 3431)]
(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)...(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)...0x009557a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2

Thread 1 (Thread -151128384 (LWP 3431))

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




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-30 20:32 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-panel".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was redkirk@harbornet.com.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Olav Vitters 2004-12-31 01:38:01 UTC
Stack trace matches bug 160606, duping.

Could you attach your ~/.recently-used file of the crashing user to bug 160606?
Does it still crash if you rename this file?

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