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 371200 - crash in CD/DVD Creator: Just logged into gnome a...
crash in CD/DVD Creator: Just logged into gnome a...
Status: RESOLVED DUPLICATE of bug 351713
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-05 20:22 UTC by xrayman
Modified: 2006-11-05 22:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description xrayman 2006-11-05 20:22:55 UTC 
What were you doing when the application crashed?
Just logged into gnome after being logged into kde


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.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.4
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.4
SESSION_MANAGER=local/xray.x-rayman.co.uk:/tmp/.ICE-unix/29012
** (eggcups:29127): WARNING **: IPP request failed with status 1280
Introspect error: The name edu.duke.linux.yum was not provided by any .service files
Unable to connect to yum-updatesd...
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
--------------------------------------------------

Memory status: size: 118427648 vsize: 0 resident: 118427648 share: 0 rss: 16855040 rss_rlim: 0
CPU usage: start_time: 1162758089 rtime: 0 utime: 38 stime: 0 cutime:34 cstime: 0 timeout: 4 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 -1208325376 (LWP 29168)]
(no debugging symbols found)
0x00d87402 in __kernel_vsyscall ()

+ Trace 83341

Thread 1 (Thread -1208325376 (LWP 29168))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/libc.so.6
  • #5 g_strdup
    from /lib/libglib-2.0.so.0
  • #6 nautilus_directory_async_state_changed
  • #7 nautilus_file_get_uri
  • #8 fm_directory_view_bump_zoom_level
  • #9 fm_directory_view_bump_zoom_level
  • #10 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #11 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 fm_directory_view_bump_zoom_level
  • #17 fm_directory_view_bump_zoom_level
  • #18 nautilus_clipboard_monitor_emit_changed
  • #19 nautilus_directory_async_state_changed
  • #20 nautilus_icon_container_request_update_all
  • #21 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #22 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #23 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #24 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #25 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 POA_Nautilus_MetafileMonitor__init
  • #27 __libc_start_main
    from /lib/libc.so.6
  • #28 g_cclosure_marshal_VOID__ENUM
  • #0 __kernel_vsyscall 






Comment 1


Karsten Bräckelmann





          2006-11-05 22:07:40 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 351713 ***