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 402531 - crash in CD/DVD Creator: Tentative d'exploration ...
crash in CD/DVD Creator: Tentative d'exploration ...
Status: RESOLVED DUPLICATE of bug 320020
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 424518 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-01-30 18:32 UTC by bmarty79
Modified: 2008-04-18 19:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description bmarty79 2007-01-30 18:32:36 UTC
What were you doing when the application crashed?
Tentative d'exploration d'un cd à contenu mixte


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

Memory status: size: 113864704 vsize: 0 resident: 113864704 share: 0 rss: 30101504 rss_rlim: 0
CPU usage: start_time: 1170180173 rtime: 0 utime: 521 stime: 0 cutime:484 cstime: 0 timeout: 37 it_real_value: 0 frequency: 56

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 -1227094352 (LWP 6178)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227094352 (LWP 6178))

  • #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_directory_async_state_changed
  • #5 ??
  • #6 _IO_stdin_used
  • #7 ??
  • #8 g_object_add_weak_pointer
    from /usr/lib/libgobject-2.0.so.0
  • #9 nautilus_directory_async_state_changed
  • #10 ??
  • #11 _IO_stdin_used
  • #12 nautilus_directory_async_state_changed
  • #13 ??
  • #14 ??
  • #0 __kernel_vsyscall

Comment 1 Susana 2007-01-31 15:05:35 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 bmarty79 2007-01-31 20:51:19 UTC
Sorry but I'm a french newbie and can't help much.
When that happend, I was trying to explore with nautilus a CD containing audio tracks AND other kinds of files.
After inserting the CD I was asked if I wanted to open the CD with "sound juicer" or explore it with Nautilus. I chose the second one but nothing happened. After clicking on media/cdrom0 in nautilus, that crash happened.
Hope that help !!
Thanks for all this terrific work !!!

Take care.

Bruno
Comment 3 André Klapper 2007-02-04 16:48:41 UTC
Salut bmarty, oui, tu peux aider si tu veux et si tu as un peu de temps. :-)

Please install the following debug packages provided by Ubuntu: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, and libgnomeui-0-dbg, and try to reproduce the crash.

Thanks in advance for helping. :-)
Comment 4 André Klapper 2007-03-31 14:36:46 UTC
*** Bug 424518 has been marked as a duplicate of this bug. ***
Comment 5 dougorleans 2007-03-31 16:34:27 UTC
Here's the stack trace with the nautilus-dbg package installed.  Let me know if you need me to install more debugging packages.

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

Memory status: size: 131629056 vsize: 0 resident: 131629056 share: 0 rss: 37867520 rss_rlim: 0
CPU usage: start_time: 1175269782 rtime: 0 utime: 6229 stime: 0 cutime:4254 cstime: 0 timeout: 1975 it_real_value: 0 frequency: 7055

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

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

Thread 1 (Thread -1226537296 (LWP 26708))

  • #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_directory_async_state_changed
    at nautilus-directory-async.c line 1917
  • #5 nautilus_directory_monitor_add_internal
    at nautilus-directory-async.c line 669
  • #6 vfs_file_monitor_add
    at nautilus-vfs-directory.c line 105
  • #7 nautilus_directory_file_monitor_add
    at nautilus-directory.c line 1619
  • #8 update_monitoring
    at fm-tree-model.c line 1071
  • #9 update_monitoring_idle_callback
    at fm-tree-model.c line 1437
  • #10 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
    at nautilus-main.c line 372
  • #16 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #17 _start
  • #0 __kernel_vsyscall

Comment 6 André Klapper 2007-04-12 14:24:20 UTC
definitely a duplicate of bug 320020 - do you have all the latest ubuntu updates installed?
Comment 7 bmarty79 2007-04-14 14:07:23 UTC
Hi !
I rencently upgraded to Ubuntu 7.04 herd 5.
Do you need me to try something else with this new configuration ?

Bruno
Comment 8 André Klapper 2008-04-18 19:59:36 UTC

*** This bug has been marked as a duplicate of 320020 ***