[jaunty] weird crash is specific directory

Bug #315623 reported by Bogdan Butnaru
4
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Up-to-date Jaunty here.

Weird situation. I wanted to look at the sources of Amarok for some reason, so I did this:

$ apt-get source amarok
$ cd amarok-1.4.10/amarok/src
$ nautilus .
Initializing nautilus-share extension

(nautilus:24767): GLib-GObject-WARNING **: Two different plugins tried to register 'NautilusBurn'.

(nautilus:24767): GLib-GObject-CRITICAL **: g_type_add_interface_dynamic: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(nautilus:24767): GLib-GObject-CRITICAL **: g_type_add_interface_dynamic: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
seahorse nautilus module initialized
Segmentation fault (core dumped)

******************
The weird thing is that it only happens in amarok-1.4.10/amarok/src and amarok-1.4.10/debian. I can open amarok-1.4.10/debian/icons, for example. It crashes whenever I try to enter in those directories, whether via the command line or via navigating in the Nautilus windows.

The messages before the segmentation fault appear everywhere, I've filed bug #315618 about them. (I only noticed them now, I'm not sure if they're recent.)

I got a couple of "an application crashed" pop-ups at first and I carelessly dismissed them. Now they don't seem to appear, although the crash is always reproducible. I found the attached file in /var/crash, according to its timestamp it should belong to one of these crashes. No idea where to find the core dump.

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :
Revision history for this message
Connor Imes (ckimes) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

Hi Connor, thanks for helping. I can't do that exactly because of bug #314212. However I made a backtrace as indicated at https://wiki.ubuntu.com/Backtrace

The backtrace above happens with the source for amarok-1.4.10. I got that originally with "apt-get source amarok", but since the Jaunty repositories passed to amarok2 you might need to get it from somewhere else. Apt gave me amarok_1.4.10-0ubuntu3.dsc, amarok_1.4.10-0ubuntu3.diff.gz and amarok_1.4.10.orig.tar.gz. I only untarred the orig.tar.gz file* and I didn't apply the Ubuntu diff.**

(*: apt does the unpacking itself, but I had deleted the unpacked directory for space.)
(**: my original report was with the diff applied. This backtrace is without it, though.)

Then I entered amarok-1.4.10 and ran gdb as demanded in the Backtrace wiki page. I ran nautilus with "run amarok/src", which is the directory that makes it crash.

Anyway, I can obtain crashes inside the amarok2 source, too (the ./src folder).

Let me know if I can help more.

Changed in nautilus:
status: Incomplete → Confirmed
Revision history for this message
A. Walton (awalton) wrote :

Can you attach the desktop entry file that is causing the crash to the bug? (according the attached trace, it should be file:///home/bogdanb/code/nautilus-bug/amarok-1.4.10/amarok/src/amarok_addaspodcast.desktop on your drive).

Changed in nautilus:
assignee: nobody → desktop-bugs
status: Confirmed → Incomplete
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

Here it is.

Revision history for this message
A. Walton (awalton) wrote :

Thanks. The fix for this crash has already been fixed upstream; for posterity's sake, it's because the desktop entry file is invalid, as the file does not contain a "Type=" field, as required by the specification: http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html

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.