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 405725 - When I'm working with firefox, sometime. . . just crash!
When I'm working with firefox, sometime. . . just crash!
Status: RESOLVED DUPLICATE of bug 364115
Product: gnome-panel
Classification: Other
Component: panel
2.16.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-08 13:37 UTC by NetCutter
Modified: 2007-02-09 00:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description NetCutter 2007-02-08 13:37:08 UTC 
Steps to reproduce:
1. 
2. 
3. 


Stack trace:
Memory status: size: 84029440 vsize: 0 resident: 84029440 share: 0 rss: 28295168 rss_rlim: 0
CPU usage: start_time: 1170835707 rtime: 0 utime: 1372 stime: 0 cutime:1099 cstime: 0 timeout: 273 it_real_value: 0 frequency: 0

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)
(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 -1225394512 (LWP 4842)]
(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)
0xffffe410 in __kernel_vsyscall ()

+ Trace 109011

Thread 1 (Thread -1225394512 (LWP 4842))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 na_fixed_tip_new
    from /usr/lib/gnome-panel/libnotification-area-applet.so
  • #5 na_fixed_tip_new
    from /usr/lib/gnome-panel/libnotification-area-applet.so
  • #6 _na_marshal_VOID__OBJECT_STRING_LONG_LONG
    from /usr/lib/gnome-panel/libnotification-area-applet.so
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 na_tray_manager_check_running
    from /usr/lib/gnome-panel/libnotification-area-applet.so
  • #12 gdk_events_pending
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #14 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 main
  • #0 __kernel_vsyscall 


Other information:
Comment 1 Mariano Suárez-Alvarez 2007-02-09 00:02: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 364115 ***