*** This bug is a duplicate of bug 94893 ***
https://bugs.launchpad.net/bugs/94893
the backtrace looks like bug #94893
** This bug has been marked a duplicate of bug 94893
[apport] rhythmbox crashed with SIGSEGV in
gnome_vfs_context_get_cancellation()
--
after a while (five minutes)
** Changed in: rhythmbox (Ubuntu)
Status: Needs Info = Unconfirmed
--
after a while (five minutes) listening music, it closes
https://bugs.launchpad.net/bugs/112950
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Well, that was interesting--I'm not sure if I am having the same issue
as the original submitter, but I can at least give details on what I
found. I believe (and I'm ignoring other crash bugs related to
gstreamer or specific songs/files that crash..) in my case this problem
was exacerbated by a
i'm having the same issue after upgrading to 7.04 (i386) yesterday. I
use rhythmbox daily to listen to hours of music, so this is definitely a
huge change with feisty as I can't get through 10 minutes or more of
music. I will try and generate a core file and get a backtrace for the
problem
--
Thank you very much, I'll try to do all the instructions you gave me.
--
after a while (five minutes) listening music, it closes
https://bugs.launchpad.net/bugs/112950
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: rhythmbox (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned)
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7572983/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7572984/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/7572985/ProcStatus.txt
--
after a
Please run the program from a terminal and see if it prints anything
when it exits. Before you run it, execute the command:
ulimit -c unlimited
... so that it will produce a 'core' file if it crashes. If it does,
then you should post that core dump to this bug ticket by using the
