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. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/21330846/gdb-nautilus.txt ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- [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
