Bug 491525 – crash in Panel: trying to close Opera

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 491525 - crash in Panel: trying to close Opera


Summary:	crash in Panel: trying to close Opera


Status:	RESOLVED DUPLICATE of bug 487302

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-29 21:04 UTC by jphan
Modified:	2007-10-30 11:37 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description jphan 2007-10-29 21:04:52 UTC

Version: 2.18.3

What were you doing when the application crashed?
trying to close Opera


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 330211328 vsize: 330211328 resident: 14553088 share: 9777152 rss: 14553088 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193691861 rtime: 23 utime: 18 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496364560 (LWP 2869)]
(no debugging symbols found)
0x0000003f6120d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 173760

Thread 1 (Thread 46912496364560 (LWP 2869))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#4 g_hash_table_foreach
from /lib64/libglib-2.0.so.0
#5 gtk_rc_reset_styles
from /usr/lib64/libgtk-x11-2.0.so.0
#6 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#7 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#8 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit
from /lib64/libgobject-2.0.so.0
#11 g_cclosure_marshal_VOID__ENUM
from /lib64/libgobject-2.0.so.0
#12 g_object_notify
from /lib64/libgobject-2.0.so.0
#13 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgtk-x11-2.0.so.0
#14 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__ENUM
from /usr/lib64/libgdk-x11-2.0.so.0
#16 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#17 g_cclosure_marshal_VOID__ENUM
from /lib64/libglib-2.0.so.0
#18 g_main_loop_run
from /lib64/libglib-2.0.so.0
#19 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#20 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
---
---
WARNING! M2_SERVER_COUNT not set, setting to 1
---
SESSION_MANAGER=local/jphan:/tmp/.ICE-unix/2719
(gnome-panel:2869): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x6c3400
(gnome-panel:2869): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x6c3400
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(gnome-panel:2869): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

Comment 1 palfrey 2007-10-30 11:37:00 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 487302 ***