Public bug reported:
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.
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
[jaunty] weird crash is specific directory
https://bugs.launchpad.net/bugs/315623
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
