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 92684 - crash panel after manual fsck
crash panel after manual fsck
Status: RESOLVED DUPLICATE of bug 84030
Product: gnome-panel
Classification: Other
Component: workspace switcher
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-09-06 16:08 UTC by foellmi
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description foellmi 2002-09-06 16:06:03 UTC
Package: gnome-panel
Severity: normal
Version: 1.4.0.1
Synopsis: crash panel after manual fsck
Bugzilla-Product: gnome-panel
Bugzilla-Component: Workspace Switcher Applet

Description:
Hello, 

This Bug Buddy appeared after a crahs of my system. In fact, I noticed
that my Ximian Gnome often crash ("freeze") when I use the mouse wheel
of my USB mouse, although it is correctly configured. 

In that cases (more and more often), I need to stop the computer and
reboot again. Then, I make an automatic root filesystem check during the
boot, which often fail. So I run fsck manually (fsck /) as requested. 

Once everything is ok (and some files may have been deleted), I reboot.
This time, however, during the boot, I chose to NOT make again a root
filesystem check during the boot, although it asks me to do so. I chose
not, since I just made a fsck manually!

I started my X server, without any problem. I notice that, contrary to
other times, Gnome didn't ask to "clean" the state of my X session. And
this time, Gnome found that a panel is already running,and ask me to
start another one! I said no, and boum. This Bug Buddy... 

Hope this helps.

Cedric



Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x405a3339 in __wait4 () from /lib/libc.so.6
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 applet_widget_add_full
    from /usr/lib/libpanel_applet.so.0
  • #5 applet_widget_add
    from /usr/lib/libpanel_applet.so.0
  • #6 make_cpuload_applet
  • #7 applet_widget_corba_deactivate
    from /usr/lib/libpanel_applet.so.0
  • #8 _ORBIT_skel_GNOME_GenericFactory_create_object
    from /usr/lib/libgnorba.so.27
  • #9 ORBit_POA_handle_request
    at orbit_poa.c line 513
  • #10 ORBit_handle_incoming_request
    at server.c line 90
  • #11 ORBit_handle_incoming_message
    at server.c line 160
  • #12 giop_main_handle_connection
    at connection.c line 1214
  • #13 goad_register_arguments
    from /usr/lib/libgnorba.so.27
  • #14 g_io_unix_dispatch
    at giounix.c line 137
  • #15 g_main_dispatch
    at gmain.c line 656
  • #16 g_main_iterate
    at gmain.c line 877
  • #17 g_main_run
    at gmain.c line 935
  • #18 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #19 applet_widget_gtk_main
    from /usr/lib/libpanel_applet.so.0
  • #20 main
  • #21 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #3 <signal handler called>
  • #4 applet_widget_add_full
    from /usr/lib/libpanel_applet.so.0
  • #5 applet_widget_add
    from /usr/lib/libpanel_applet.so.0
  • #6 make_cpuload_applet
  • #7 applet_widget_corba_deactivate
    from /usr/lib/libpanel_applet.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-09-06 12:06 -------

The original reporter (foellmi@astro.umontreal.ca) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.

Comment 1 Vincent Untz 2002-09-06 16:16:51 UTC

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