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 376449 - crash in Open Folder: Double-clicked an audio ...
crash in Open Folder: Double-clicked an audio ...
Status: RESOLVED DUPLICATE of bug 375019
Product: nautilus
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-17 20:25 UTC by Leonardo Ferreira Fontenelle
Modified: 2006-11-26 23:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Leonardo Ferreira Fontenelle 2006-11-17 20:25:19 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Double-clicked an audio CD.

There is this CD-R, which was recorded as an audio CD. It had no label, so I put it in the CD drive to see what it was. When the icon showed up in the Desktop, I double-clicked it and Nautilus crashed.

This is reproducible from the Computer folder.

I don't know it it matters, but there is no default command for when an audio CD is inserted (well, there is such a command, but the check box is unchecked).

The backtrace is quite short; if a strace would help, then please give me exact instructions on how to get it.


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.1 2006-10-11 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 71671808 vsize: 0 resident: 71671808 share: 0 rss: 16293888 rss_rlim: 0
CPU usage: start_time: 1163794472 rtime: 0 utime: 88 stime: 0 cutime:84 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226144080 (LWP 22986)]
0xb7fd6410 in ?? ()

+ Trace 87309

Thread 1 (Thread -1226144080 (LWP 22986))

  • #0 ??
  • #1 ??
  • #2 ??
  • #0 ?? 






Comment 1


André Klapper





          2006-11-17 22:59:13 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


Leonardo Ferreira Fontenelle





          2006-11-18 01:09:31 UTC
        



Well, I didn't think running gdb would give me more info than bug-buddy, but it did. This is the new backtrace:





+
Trace
    87358






Thread 1
          (Thread -1226795344 (LWP 31550))


    

  • 
#0
lacks_info

    
                at nautilus-directory-async.c
                  line
                  1672

    

    • 

  • 
#1
is_needy

    
                at nautilus-directory-async.c
                  line
                  2241

    

    • 

  • 
#2
file_needs_high_priority_work_done

    
                at nautilus-directory-async.c
                  line
                  3569

    

    • 

  • 
#3
nautilus_directory_async_state_changed

    
                at nautilus-directory-async.c
                  line
                  3332

    

    • 

  • 
#4
call_ready_callbacks_at_idle

    
                at nautilus-directory-async.c
                  line
                  1888

    

    • 

  • 
#5
g_idle_dispatch

    
                at gmain.c
                  line
                  3926

    

    • 

  • 
#6
IA__g_main_context_dispatch

    
                at gmain.c
                  line
                  2045

    

    • 

  • 
#7
g_main_context_iterate

    
                at gmain.c
                  line
                  2677

    

    • 

  • 
#8
IA__g_main_loop_run

    
                at gmain.c
                  line
                  2881

    

    • 

  • 
#9
IA__gtk_main

    
                at gtkmain.c
                  line
                  1001

    

    • 

  • 
#10
main

    
                at nautilus-main.c
                  line
                  389

    

    • 

  • 
#11
__libc_start_main

    
                at libc-start.c
                  line
                  238

    

    • 

  • 
#12
_start

    • 













Comment 3


Leonardo Ferreira Fontenelle





          2006-11-18 01:17:31 UTC
        



Some additional information.

If "Play audio CD discs when inserted" (from gnome-volume-properties) is checked, inserting the CD causes (i.e.) totem to be launched automatically, as well as when the "audio CD" icon in the desktop is double-cliked or when the default gnome-volume-manager action is choosen. When the above option is unchecked, then (of course) no automatic action is taken, but the default acion in gnome-volume-manager, or double-clicking the desktop icon, is to _open the disc_ with nautilus -- then it crashes.

No matter if the above option is checked or not, running "nautilus cdda://" in gnome-terminal made nautilus crash. (I don't know if it was the right URI, but it was the best one I could guess.)






Comment 4


Christian Kirbach





          2006-11-26 13:57:38 UTC
        



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 375019 ***






Comment 5


Leonardo Ferreira Fontenelle





          2006-11-26 21:43:20 UTC
        



I visited the bug report and couldn't find any specific question; do you want me to tell what was I doing when nautilus crashed? I'm watching the bug, anyway (thank you, bugzilla).






Comment 6


Christian Kirbach





          2006-11-26 23:28:54 UTC
        



I've already added your statement, sorry I picked the wrong stock comment.
You are fine. You can unsubscribe from a report if you really want to.