Nautilus crashes when opening folder containing .sql file

Bug #9914 reported by Matthew Metzger
10
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

Nautilus crashes when opening folder containing .sql file. It happens every
time. It also happens when I am using Evolution 2.0.2 and I try to attach a file
by going to a folder which contains an .sql file. Both Evolution 2.0.2 and
Nautilus 2.8.1 crash and ask to be restarted when opening a folder containing an
.sql file.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you provide a backtrace of the crash ? When nautilus crash you should get
a bug-buddy window
to report the problem. In the details you have a backtrace of the crash.

I think this crash is a librsvg2 problem fixed with 2.8.0 in hoary ...

Revision history for this message
Matthew Metzger (ubuntu-thinkdeeper) wrote :
Download full text (7.5 KiB)

Here's the Backtrace:

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)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using libthread_db
enabled]
[New Thread 1089458496 (LWP 22453)]
[New Thread 1101278128 (LWP 22462)]
[Thread debugging using libthread_db enabled]
[New Thread 1089458496 (LWP 22453)]
[New Thread 1101278128 (LWP 22462)]
[Thread debugging using libthread_db enabled]
[New Thread 1089458496 (LWP 22453)]
[New Thread 1101278128 (LWP 22462)]
(no debugging symbols found)...[New Thread 1101011888 (LWP 22461)]
(no debugging symbols found)...[New Thread 1100745648 (LWP 22460)]
(no debugging symbols found)...[New Thread 1099955120 (LWP 22455)]
(no debugging symbols found)...[New Thread 1099676592 (LWP 22454)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging s...

Read more...

Revision history for this message
Matthew Metzger (ubuntu-thinkdeeper) wrote :

I'm using a custom icon set created by another Ubuntu user that I downloaded
from the Ubuntu wiki. Could that have anything to do with the crash?

Revision history for this message
Matt Zimmerman (mdz) wrote :

(In reply to comment #3)
> I'm using a custom icon set created by another Ubuntu user that I downloaded
> from the Ubuntu wiki. Could that have anything to do with the crash?

Yes. Please show us exactly which icon set you are using.

Revision history for this message
Matthew Metzger (ubuntu-thinkdeeper) wrote :

It was the custom icon set that caused the problem. I changed the icon set back
to the default for Ubuntu and nautilus did not crash when opening folders
containing .sql files. Sorry about that. The icon set was called Suede and I
downloaded it from somewhere on the Ubuntu wiki (can't remember from exactly
where). Maybe the bug should be about Nautilus crashing when something isn't
quite right with the icon set.

Revision history for this message
Sebastien Bacher (seb128) wrote :

There is a good chance that librsvg2 2.8.0 fixes it, any chance to test it ?

Revision history for this message
Matthew Metzger (ubuntu-thinkdeeper) wrote :

I have librsvg2-2 version 2.7.2-2 from Ubuntu. How can I get 2.8 using synaptic
or apt-get (what repository do I need to add?)

Revision history for this message
Sebastien Bacher (seb128) wrote :

(In reply to comment #7)
> I have librsvg2-2 version 2.7.2-2 from Ubuntu. How can I get 2.8 using synaptic
> or apt-get (what repository do I need to add?)

librsvg2-2 2.8.0 is in hoary, you can add the hoary source, install this package
and switch back
to the warty source, it should not require extra depends.
BTW just upgrade it if you want to test it, you can also keep your warty system,
and we will figure
later if the bug is really fixed, that's not a problem.

Revision history for this message
Sebastien Bacher (seb128) wrote :

no news, probably fixed in hoary, I'm closing the bug. Feel free to reopen if
the problem
still happens with the new version.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.