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 124133 - Panel crashed with seg fault.
Panel crashed with seg fault.
Status: RESOLVED DUPLICATE of bug 105745
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-08 16:48 UTC by greg.jandl
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description greg.jandl 2003-10-08 16:49:42 UTC
Package: gnome-panel
Severity: major
Version: 2.2.0.1
Synopsis: Panel crashed with seg fault.
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

Out of the blue, gnome-panel seg faulted. I have no idea how to
reproduce the bug


Expected Results:

Um ... not doing that? ;)

How often does this happen?

This was the first time on a new machine that has only had two days of
normal use on it, so I don't know yet. I hope not often, though!

Additional Information:

I assume that the bug report will grab some sys info, but:

System is a dual Xeon with HT turned on, dual homed (two nicks) and dual
headed (twin outputs on an NVidia Quadro (550 I think)) using Xinerama
rather than Twin-View. Each display has it's own panel. I'm not sure as
I type this which display's panel died ... I'll update when/if I can.
I'm running 4 workspaces per display and using the notificaion area for
rhn updates, the mailbox checker, the system monitor

Interesting. I just stepped away, and when I came back my screensaver
had kicked in. once I unloced the screensaver, it appears that *neither*
panel is redrawing, with the exception that the rhn icon and the system
monitor graphs are still there. No buttons, workspace chooser or window
lists though.



Debugging Information:

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

(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)...[New
Thread 1086426016 (LWP 2123)]

(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)...0xffffe002 in ?? ()

Thread 1 (Thread 1086426016 (LWP 2123))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 ENGINE_load_ibmca
    from /lib/libcrypto.so.4
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-08 12:49 -------

The original reporter (greg.jandl@qlogic.com) 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 mwehner 2003-10-11 02:09:52 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 105745 ***