GNOME Bugzilla – Bug 376189
crash in CD/DVD Creator: changing se linux contex...
Last modified: 2006-11-17 14:48:58 UTC
What were you doing when the application crashed? changing se linux context Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- ** (eggcups:3516): WARNING **: IPP request failed with status 1030 Initializing nautilus-image-converter extension Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension Initializing nautilus-flac-converter extension ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name You can not run beagle as root. Beagle is designed to run from your own user account. If you want to create multiuser or system-wide indexes, use the beagle-build-index tool. You can override this setting using the beagle-config or beagle-settings tools. Introspect error: The name edu.duke.linux.yum was not provided by any .service files Unable to connect to yum-updatesd... ** (bug-buddy:3599): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 129282048 vsize: 0 resident: 129282048 share: 0 rss: 28659712 rss_rlim: 0 CPU usage: start_time: 1163739454 rtime: 0 utime: 298 stime: 0 cutime:269 cstime: 0 timeout: 29 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208206592 (LWP 3507)] (no debugging symbols found) 0x00d6b402 in __kernel_vsyscall ()
+ Trace 87121
Thread 1 (Thread -1208206592 (LWP 3507))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 362302 ***