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 446752 - crash in CD/DVD Creator: Double-clicking on Audio...
crash in CD/DVD Creator: Double-clicking on Audio...
Status: RESOLVED DUPLICATE of bug 320020
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 453321 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-06-12 14:22 UTC by Mike Lea-Wilson
Modified: 2007-07-03 16:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Mike Lea-Wilson 2007-06-12 14:22:48 UTC 
What were you doing when the application crashed?
Double-clicking on Audio Disc.

This must be the same bug I just reported, entitled "Eating my lunch outside in the garden!" Perhaps double clicking on Audio Disc was the last thing I did before going outside? Anyway, the bug seems to be reproducible.


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

Memory status: size: 79441920 vsize: 0 resident: 79441920 share: 0 rss: 26345472 rss_rlim: 0
CPU usage: start_time: 1181657896 rtime: 0 utime: 335 stime: 0 cutime:318 cstime: 0 timeout: 17 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 -1226422608 (LWP 19294)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 140357

Thread 1 (Thread -1226422608 (LWP 19294))

  • #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 nautilus_directory_async_state_changed
  • #6 nautilus_undo_transaction_unregister_object
  • #7 nautilus_directory_async_state_changed
  • #8 fm_directory_view_bump_zoom_level
  • #9 fm_directory_view_bump_zoom_level
  • #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 POA_Nautilus_MetafileMonitor__init
  • #16 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #17 ??
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-06-12 16:38:33 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 and
reopen this bug or report a new one. Thanks in advance!






Comment 2


Mike Lea-Wilson





          2007-06-12 18:11:02 UTC
        



This seems to have a lot more info in it. I hope you find it useful :-)


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

Memory status: size: 81260544 vsize: 0 resident: 81260544 share: 0 rss: 23216128 rss_rlim: 0
CPU usage: start_time: 1181658264 rtime: 0 utime: 705 stime: 0 cutime:664 cstime: 0 timeout: 41 it_real_value: 0 frequency: 0

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 -1227102544 (LWP 19524)]
0xffffe410 in __kernel_vsyscall ()




+
Trace
    140411






Thread 1
          (Thread -1227102544 (LWP 19524))


    

  • 
#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_idle_dispatch

    
                at gmain.c
                  line
                  3926

    

    • 

  • 
#11
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#12
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#13
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#14
IA__gtk_main

    
                at gtkmain.c
                  line
                  1024

    

    • 

  • 
#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 3


palfrey





          2007-06-12 22:37:27 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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






Comment 4


palfrey





          2007-07-03 16:49:10 UTC
        



*** Bug 453321 has been marked as a duplicate of this bug. ***