Bug 536244 – crash in Panel: Rebooting FC8 changed /e...

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 536244 - crash in Panel: Rebooting FC8 changed /e...


Summary:	crash in Panel: Rebooting FC8 changed /e...


Status:	RESOLVED DUPLICATE of bug 475065

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-02 14:13 UTC by strokop
Modified:	2008-06-02 14:34 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description strokop 2008-06-02 14:13:23 UTC

Version: 2.20.3

What were you doing when the application crashed?
Rebooting FC8 changed /etc/fstab inserting 'LABEL='


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.3 2008-01-08 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.24.7-92.fc8 #1 SMP Wed May 7 16:26:02 EDT 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 311267328 vsize: 311267328 resident: 14536704 share: 10473472 rss: 14536704 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212415925 rtime: 23 utime: 19 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912508473888 (LWP 3005)]
0x000000397dc0e085 in waitpid () from /lib64/libpthread.so.0

+ Trace 199403

Thread 1 (Thread 46912508473888 (LWP 3005))

#0 waitpid
from /lib64/libpthread.so.0
#1 IA__g_spawn_sync
at gspawn.c line 369
#2 IA__g_spawn_command_line_sync
at gspawn.c line 677
#3 g_cclosure_marshal_VOID__ENUM
at gmarshal.c line 334
#4 <signal handler called>
#5 IA__g_slist_remove_all
at gslist.c line 233
#6 gtk_rc_clear_realized_style
at gtkrc.c line 1652
#7 IA__g_hash_table_foreach
at ghash.c line 680
#8 IA__gtk_rc_reset_styles
at gtkrc.c line 1698
#9 gtk_settings_notify
at gtksettings.c line 1019
#10 IA__g_closure_invoke
at gclosure.c line 490
#11 signal_emit_unlocked_R
at gsignal.c line 2370
#12 IA__g_signal_emit_valist
at gsignal.c line 2199
#13 IA__g_signal_emit
at gsignal.c line 2243
#14 g_object_dispatch_properties_changed
at gobject.c line 563
#15 IA__g_object_notify
at gobjectnotifyqueue.c line 123
#16 _gtk_settings_handle_event
at gtksettings.c line 1737
#17 IA__gtk_main_do_event
at gtkmain.c line 1404
#18 gdk_event_dispatch
at gdkevents-x11.c line 2351
#19 IA__g_main_context_dispatch
at gmain.c line 2061
#20 g_main_context_iterate
at gmain.c line 2694
#21 IA__g_main_loop_run
at gmain.c line 2898
#22 IA__gtk_main
at gtkmain.c line 1163
#23 main
at main.c line 97
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (15 sec old) ---------------------
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2838,unix/unix:/tmp/.ICE-unix/2838
Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.
Checking for Xgl: not present. 
Detected PCI ID for VGA: 05:00.0 0300: 10de:00c0 (rev a2) (prog-if 00 [VGA controller])
06:04.0 0300: 1002:5159 (prog-if 00 [VGA controller])
Checking for texture_from_pixmap: not present. 
Trying again with indirect rendering:
Checking for texture_from_pixmap: not present. 
aborting and using fallback: /usr/bin/metacity 
(gnome-panel:3005): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
could not attach to desktop process
--------------------------------------------------

Comment 1 Philip Withnall 2008-06-02 14:34:03 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 475065 ***