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 300778 - gnome just crashed
gnome just crashed
Status: RESOLVED DUPLICATE of bug 170660
Product: gnome-panel
Classification: Other
Component: workspace switcher
2.10.x
Other other
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-15 18:00 UTC by des972
Modified: 2005-04-16 00:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description des972 2005-04-15 18:00:33 UTC
Distribution: Debian 3.1
Package: gnome-panel
Severity: critical
Version: GNOME2.10.0 2.10.x
Gnome-Distributor: Ubuntu
Synopsis: gnome just crashed
Bugzilla-Product: gnome-panel
Bugzilla-Component: Workspace Switcher Applet
Bugzilla-Version: 2.10.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
normal apps running and then gnome panel crashed.

Steps to reproduce the crash:
1. do not know
2. 
3. 

Expected Results:


How often does this happen?
first time

Additional Information:



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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1221831968 (LWP 11111)]
[New Thread -1224152144 (LWP 11119)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1224152144 (LWP 11119))

  • #0 __kernel_vsyscall
  • #1 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #2 g_main_loop_get_context
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #5 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 g_static_private_free
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-15 14:00 -------


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 des972@gmail.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 Elijah Newren 2005-04-16 00:51:33 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.

Matches the stack trace in bug 171753, which has been marked as a duplicate of
170660

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