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
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 (Ubuntu)
Assignee: (unassigned) =
*** This bug is a duplicate of bug 315983 ***
https://bugs.launchpad.net/bugs/315983
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
** Attachment added: _usr_bin_nautilus.1000.crash
http://launchpadlibrarian.net/21064297/_usr_bin_nautilus.1000.crash
--
[jaunty] weird crash is specific directory
https://bugs.launchpad.net/bugs/315623
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
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
