abrt 1.0.0 detected a crash. How to reproduce ----- 1. Create a large SVG wallpaper with Inkscape (~4MB) -one that was 3.7MB caused no problems 2. Save it to a folder 3. Open that folder with Nautilus, it will crash when trying to make a thumbnail Comment: I'm guessing it's the size because it didn't have trouble with the smaller ones. If that's not the issue, let me know and I can send you the problem image. Attached file: backtrace cmdline: nautilus component: nautilus executable: /usr/bin/nautilus kernel: 2.6.31.9-174.fc12.x86_64 package: nautilus-2.28.4-1.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 382121 [details] File: backtrace
Crash in librsvg. Attaching the problematic image would be required to make progress here.
Created attachment 382575 [details] problem image This image seems to cause the crash every time.
The backtrace is not useful, and I can't reproduce the crash with the problem image on F12.
The crash is reproducible with Fedora 13 x86_64 and librsvg2-2.26.3-1.fc13.x86_64 in nautilus and geeqie.
Reproducible with Fedora 14 Branched: $ rpm -q librsvg2 librsvg2-2.31.0-2.fc14.x86_64
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This is the same as bug 603183 (Fedora 13), a NULL-ptr crash in g_str_equal: Thread 1 (Thread 5596): #0 __strcmp_ssse3 () at ../sysdeps/x86_64/strcmp.S:106 No locals. #1 0x000000388cc5fcb9 in IA__g_str_equal (v1=<value optimized out>, v2=<value optimized out>) at gstring.c:116 string1 = <value optimized out> string2 = <value optimized out> #2 0x00000038a242100d in rsvg_parse_style_pair (ctx=0x132da80 [RsvgHandle], state=0x7f3bfc026940, name=0x7f3bfc025de0 "stop-color", value=0x0, important=0) at rsvg-styles.c:698 data = <value optimized out>
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 675290 has been marked as a duplicate of this bug. ***
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Close the USB conection between my SMARTPHONE and PC 2. And than the Nautilus crashed 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. "Saffely remove drive" 2. crash 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Single click a USB drive icon 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Booted up 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.just errered on its own 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. . Comment ----- "Safely removed" a phone with a microSD card installed.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I was making ISO images from CD and DVD disks using two local dvd drive devices (one IDE, other USB). Apps open: firefox (nothing too complicated, idle), two bash shells (one idle, other running "iostat -xtmd /dev/dm-2 /dev/scd0 2" on my SSD and the IDE burner), and system monitor. 2. I would insert a CD or DVD disk into the local drive device, close manually, right-click the icon that would appear a few seconds later on the desktop and select copy, which invoked brasero in "copy disk" mode. 3. Two concurrent brasero imaging tasks (simultaneously imaging from IDE device and USB device) had just completed within 20 seconds of eachother and I closed both brasro dialogs, one immediately after the other. 4. I removed the disks from the drives, and inserted a slackware13 DVD in the USB drive. I right clicked on the DVD desktop icon and selected "copy disk." 5. I don't think the brasero dialog even appeared. Then the notice of the nautilus crash appeared. 6. I didn't notice anything else go wrong, and I didn't have a Nautilus window open. 7. I suspect maybe a timing problem, when I closed two instances of the burner, releasing the semaphores for the drives, then asked right away for a new brasero instance. Maybe competition for the semaphores for control of the burner devices resulted in a return code to nautilus it didn't know how to handle? Comment ----- 1. Maybe try creating iso images from an IDE drive and USB drive. 2. Then wait for both to finish. 3. Quickly remove both disks and insert a DVD into the USB drive and use the (subsequent) DVD desktop icon to select the brasero "copy disk" function from the icon's context menu. I also strongly suspect something in my particular hardware setup as the origin of the crash condition. Let me know if you would like me to try to reproduce. I'm assuming the report has all my hardware info. Nevertheless, there is CERTAINLY an opportunity in the nautilus code for robustness improvement. : ) good luck! --Jim. Ottawa, Canada.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. it just crashed
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just pressed the F3 (Extra Panel) 2. And than the Nautilus crashed 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Trying to copy iso to disk 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I opened windows share 2. the switch turned off (power failure) 3. nautilus crashed
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Log in 2. start a VPN connection 3. nautilus crashed
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I'm working with a rather tempermental SSH/SFTP service running on a Windows server (server and service not admin'd by me). The service used is found at this address: http://www.kpym.com/2/kpym/index.htm It seems to be cranky when I have private key and haven't loaded the public key on the server. The admins added my public key, but the service still seems cranky: for example, it doesn't like it when I connect to the root when my SFTP hom is something else. Nautilus reports some sort of error when I do that, but I can get around it by simply adding the full home path after the usser@server This crash happened somewhere with all that: I think my private/public key pair were active, but I hadn't yet added the final path to my "~/.gtk-bookmarks" file and so was getting the Nautilus error message. The crash happened when I had pressed the "eject" button next to the mounted server. (Sorry, that's the best I can do to give you the context and way to reproduce the crash. It's almost certainly due to the Windows service, but I wouldn't expect Nautilus to crash from it.)
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Not a specific pattern 2. System is a Fedora 14 64 bit 3. Just working normally and the crash is reported by the abrt icon Comment ----- The abrt dump icon appeared in my taskbar without any special action or activity, and I cannot correlate it with a specific event or action. BTW the signal happend and the dump looks poiniting to a "non existing directory" problem.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I don't know why 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.touch 1 2.ln -s 1 2 3.rm 1 4.ln -s 2 1 5.nautilus . //start nautlius to display the loop symbolic link and then nautilus crashes.
At bachue.shu : Cannot reproduce. This ticket is about a crash in librsvg2, which means it's an .svg (SVG) file that crashes Nautilus. At acapasso.net : > and the dump looks poiniting to a "non existing directory" problem. Can you attach that backtrace manually, please? ABRT can tell you where to find it on your harddisk.
(In reply to comment #28) > At bachue.shu : > > Cannot reproduce. > > This ticket is about a crash in librsvg2, which means it's an .svg (SVG) file > that crashes Nautilus. > > > At acapasso.net : > > > and the dump looks poiniting to a "non existing directory" problem. > > Can you attach that backtrace manually, please? ABRT can tell you where to find > it on your harddisk. Yes, you are right. May be rabbitvcs and its nautilus plugin cause nautilus crash.
Package: nautilus-2.32.2.1-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Just happened 2. 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Open big(>2Gb) .tar.gz (with fileroller) 2.Select other workspace(with compiz(cube is off))
To all bug reporters, somebody please attached a refreshed backtrace manually. Thank you in advance! ABRT tells the path to where the backtrace file is stored on disk. Please use the "Refresh" button to refresh the backtrace - or even better, run "debuginfo-install -y nautilus" as root before refreshing the backtrace. There is evidence that all these duplicates aren't really duplicates.
comment 31 is a false duplicate, instead it is bug 660311
(In reply to comment #32) > To all bug reporters, > > somebody please attached a refreshed backtrace manually. Thank you in advance! > > ABRT tells the path to where the backtrace file is stored on disk. Please use > the "Refresh" button to refresh the backtrace - or even better, run > "debuginfo-install -y nautilus" as root before refreshing the backtrace. > > There is evidence that all these duplicates aren't really duplicates. I'd love to help, but I don't see any reference to where ABRT stores its backtraces (modified or not). Since I took the time to remove sensitive info from mine, it's unfortunate that it disappeared when ABRT decided (apparently erroneously) that my case was a dup. Also, no "Refresh" button for me when I manually run abrt-gui. Any tips would be appreciated, I'm willing but versed enough to help based on the info I have so far.
Created attachment 479780 [details] updated backtrace
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. select 4 video files 2. right-click and choose Properties 3.
@ Misha Shnurapet : that is bug 650380 (Fedora 14) and bug 595402 (Fedora 13)
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. remove usb drive using safe setings 2. 3.
(In reply to comment #28) > At bachue.shu : > > Cannot reproduce. > > This ticket is about a crash in librsvg2, which means it's an .svg (SVG) file > that crashes Nautilus. > > > At acapasso.net : > > > and the dump looks poiniting to a "non existing directory" problem. > > Can you attach that backtrace manually, please? ABRT can tell you where to find > it on your harddisk. I found the backtrace location, not from the abrt gui, but looking at the abrt configuration and digging into the /var/spool/abrt directory. Unfortunately after following your directions to install the debuginfo, when I refreshed the abrt gui the message about the missing directory disappeared and was replaced by other kind of messages. I hope I didn't misinterpret a message from abrt as a message from the backtrace dump. How can I attach the backtrace file in here? Just cut-n-paste or there is an attach file functionality?
Created attachment 479848 [details] reauested backtrace. see comment #28 Should you need it, I will keep the full coredump for a couple of weeks from now.
@ acapasso : that is bug 655733
(In reply to comment #41) > @ acapasso : that is bug 655733 thanks. I'll subscribe to that one.
Created attachment 479868 [details] backtrace for comment 24 (In reply to comment #39) > I found the backtrace location, not from the abrt gui, but looking at the abrt > configuration and digging into the /var/spool/abrt directory. Many thanks! That helped me find my own. (In reply to comment #32) > To all bug reporters, > > somebody please attached a refreshed backtrace manually. Thank you in advance! Attaching here. I can also send on the coredump file as needed. > ABRT tells the path to where the backtrace file is stored on disk. Please use > the "Refresh" button to refresh the backtrace - or even better, run > "debuginfo-install -y nautilus" as root before refreshing the backtrace. The attached is the original backtrace. I'll refresh if needed, but I'm afraid of losing the original information (see comment 39).
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. select two files (avi & srt) 2. right-click and select Properties 3.
Package: nautilus-2.32.2.1-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I clicked on a Desktop icon 2. 3. Comment ----- I clicked on a Desktop icon
* The original crash (F-12) with the attached example file is no longer reproducible. Not on F-13 either. * The original backtrace is missing details. It has been described as "useless" in an early comment. * The librsvg2 NULL-ptr crash bug 603183 has been fixed in F-13 and newer, so the other example files don't crash Nautilus, Firefox, Tracker, Geeqie and other apps anymore. * To this ticket ABRT has added many false duplicates with no backtraces. It won't be fruitful to keep this ticket open.
(In reply to comment #46) > * To this ticket ABRT has added many false duplicates with no backtraces. It > won't be fruitful to keep this ticket open. Just catching up with my bugzilla mail now, and saw your comment Michael. My report was one of those false duplicates, but I was able to manually attach my backtrace (see comment 43). Is this of any help finding my case? Please let me know if so, so that I can cc myself on the correct bug.
@ John Keller, that's bug 681101 ERROR:nautilus-bookmark.c:501:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))
(In reply to comment #48) > @ John Keller, > > that's bug 681101 > > ERROR:nautilus-bookmark.c:501:nautilus_bookmark_connect_file: assertion failed: > (!nautilus_file_is_gone (bookmark->details->file)) Thanks, Michael! I'll cc myself there...