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 419400 - crash in CD/DVD Creator:
crash in CD/DVD Creator:
Status: RESOLVED DUPLICATE of bug 366207
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-17 16:10 UTC by DraculaXusa
Modified: 2007-03-19 01:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description DraculaXusa 2007-03-17 16:10:11 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 84131840 vsize: 0 resident: 84131840 share: 0 rss: 29024256 rss_rlim: 0
CPU usage: start_time: 1174147858 rtime: 0 utime: 105 stime: 0 cutime:99 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227176272 (LWP 17083)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119454

Thread 1 (Thread -1227176272 (LWP 17083))

  • #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 nautilus_clipboard_monitor_emit_changed
  • #5 nautilus_directory_async_state_changed
  • #6 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-03-19 01:07:09 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 366207 ***