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 114435 - Spontaneous panel crash
Spontaneous panel crash
Status: RESOLVED DUPLICATE of bug 114929
Product: gnome-panel
Classification: Other
Component: panel
2.2.x
Other other
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-05 00:56 UTC by x
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description x 2003-06-05 01:01:47 UTC
Package: gnome-panel
Severity: normal
Version: 2.2.0.1
Synopsis: Spontaneous panel crash
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
No idea really... it just crashes all of a sudden.

Steps to reproduce the problem:
1. Run gnome-panel for a while.
2. Wait for crash.

Actual Results:
Crashes

Expected Results:
Doesn't crash

How often does this happen?
Rarely

Additional Information:
I am using the NVidia driver with TwinView. It therefore "looks" like I
have two instances of Gnome panel running. That might be related to the
problem, but most of the time, no crash.



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)...[New Thread 1086421920 (LWP 2064)]
0xffffe002 in ?? ()

Thread 1 (Thread 1086421920 (LWP 2064))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_event_translate
    at gdkevents-x11.c line 814
  • #5 _gdk_events_queue
    at gdkevents-x11.c line 1952

  xunmap = {type = 158, serial = 1086007, send_event = 0, display =
0x80d25b8, 
    event = 14680317, window = 2, from_configure = 2}, xmap = {type =
158, 
    serial = 1086007, send_event = 0, display = 0x80d25b8, event =
14680317, 
    window = 2, override_redirect = 2}, xmaprequest = {type = 158, 
    serial = 1086007, send_event = 0, display = 0x80d25b8, parent =
14680317, 
    window = 2}, xreparent = {type = 158, serial = 1086007, send_event =
0, 
    display = 0x80d25b8, event = 14680317, window = 2, parent = 2, x =
7939, 
    y = 0, override_redirect = 0}, xconfigure = {type = 158, serial =
1086007, 
    send_event = 0, display = 0x80d25b8, event = 14680317, window = 2, x
= 2, 
    y = 7939, width = 0, height = 0, border_width = 0, above = 0, 
    override_redirect = 1}, xgravity = {type = 158, serial = 1086007, 
    send_event = 0, display = 0x80d25b8, event = 14680317, window = 2, x
= 2, 
    y = 7939}, xresizerequest = {type = 158, serial = 1086007,
send_event = 0, 
    display = 0x80d25b8, window = 14680317, width = 2, height = 2}, 
  xconfigurerequest = {type = 158, serial = 1086007, send_event = 0, 
    display = 0x80d25b8, parent = 14680317, window = 2, x = 2, y = 7939,

    width = 0, height = 0, border_width = 0, above = 0, detail = 1, 
    value_mask = 1}, xcirculate = {type = 158, serial = 1086007, 
    send_event = 0, display = 0x80d25b8, event = 14680317, window = 2, 
    place = 2}, xcirculaterequest = {type = 158, serial = 1086007, 
    send_event = 0, display = 0x80d25b8, parent = 14680317, window = 2,

    place = 2}, xproperty = {type = 158, serial = 1086007, send_event =
0, 
    display = 0x80d25b8, window = 14680317, atom = 2, time = 2, state =
7939}, 
  xselectionclear = {type = 158, serial = 1086007, send_event = 0, 
    display = 0x80d25b8, window = 14680317, selection = 2, time = 2}, 
  xselectionrequest = {type = 158, serial = 1086007, send_event = 0, 
    display = 0x80d25b8, owner = 14680317, requestor = 2, selection = 2,

    target = 7939, property = 0, time = 0}, xselection = {type = 158, 
    serial = 1086007, send_event = 0, display = 0x80d25b8, 
    requestor = 14680317, selection = 2, target = 2, property = 7939, 
    time = 0}, xcolormap = {type = 158, serial = 1086007, send_event =
0, 
    display = 0x80d25b8, window = 14680317, colormap = 2, new = 2, 
    state = 7939}, xclient = {type = 158, serial = 1086007, send_event =
0, 
    display = 0x80d25b8, window = 14680317, message_type = 2, format =
2, 
    data = {b = "\003\037", '\0' <repeats 17 times>, s = {7939, 0, 0, 0,
0, 0, 
        0, 0, 0, 0}, l = {7939, 0, 0, 0, 0}}}, xmapping = {type = 158, 
    serial = 1086007, send_event = 0, display = 0x80d25b8, window =
14680317, 
    request = 2, first_keycode = 2, count = 7939}, xerror = {type = 158,

    display = 0x109237, resourceid = 0, serial = 135079352, 
    error_code = 253 '




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-04 21:01 -------

The original reporter (x@xman.org) 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 Elijah Newren 2003-06-12 02:39:59 UTC
Cool!  You have debugging symbols in one of these mysterious crashes.
This may be a duplicate of bug 105745 and may prove helpful.

Since I'm horrible at determining whether these bugs with gdk/gtk+
functions near the top of the stack trace are duplicates, I'll leave
this open.  However, this does look basically identical to 114929
(which is a gnome-terminal crash) and both look like the 105745 crash(es).

Setting version->2.2.x, adding GNOMEVER2.2 & STACKTRACE keywords,
setting priority->high & severity->critical (it's a crasher), and
marking as new.
Comment 2 Mark McLoughlin 2003-06-12 11:05:28 UTC
This does look identical to #114929.

Reporter: what version of gtk+ is this ?
Comment 3 Owen Taylor 2003-06-12 12:58:54 UTC

*** This bug has been marked as a duplicate of 114429 ***
Comment 4 Owen Taylor 2003-06-12 13:01:29 UTC
See bug 114929 for further comments, but the information 
I'd really like to have is an attachment of the output
of 'xdpyinfo -ext all'.
Comment 5 Owen Taylor 2003-06-12 13:01:53 UTC

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