We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future.
** Changed in: rhythmbox (Ubuntu)
Lawrence thank you for your bug interest, why do you think that's the
same crash?
--
rhythmbox crashed but didn't really
https://bugs.launchpad.net/bugs/89571
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for rhythmbox in ubuntu.
--
d
** Attachment added: "_usr_lib_rhythmbox_rhythmbox-metadata.1000.crash"
http://librarian.launchpad.net/7757270/_usr_lib_rhythmbox_rhythmbox-metadata.1000.crash
--
rhythmbox crashed but didn't really
https://bugs.launchpad.net/bugs/89571
You received this bug notification because you are a me
Any news on the bug?
--
rhythmbox crashed but didn't really
https://bugs.launchpad.net/bugs/89571
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for rhythmbox in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https:
Menno (antigoon) when you reply to a bug-email, it get posted on launchpad.
As to your question, it was not by accident. I tried a tool that would look at
your stack-trace and figure out the debugging symbols, but because the packages
have been updated inbetween it didn't work.
But, Menno, if
could you get a new crash file?
--
rhythmbox crashed but didn't really
https://bugs.launchpad.net/bugs/89571
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for rhythmbox in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu
some input from the noob:
i think its due to the fact that i had my soundcard configured to OSS
instead of ALSAat that moment.. anyway thanks for the help everyone.
On 4/9/07, Ralf Nieuwenhuijsen <[EMAIL PROTECTED]> wrote:
>
> Ok, so I figured out how to retrace using the original core-dump.
> Bu
Ok, so I figured out how to retrace using the original core-dump.
But I've got a lot of warnings in one these styles:
WARNING: [packagename] was loaded at runtime, but is not available
WARNING: [package] is not available
WARNING: [package+version] required, but [version] is available
I guess retr
I've looked at the link.
The problem is, that its not reproduce-able.
Off course, we can install the debug-versions and see if the problem re-occurs.
It appears this bug only happens in very rare situations though.
Just out of curiosity, wouldn't it make sense to have debug versions of the
c
Could you try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report?
** Changed in: rhythmbox (Ubuntu)
Importance: Undecided => Medium
--
rhythmbox crashed but didn't really
https://bugs.launchpad.net/bugs/89571
You received this bug notifica
I was there when he had that crash. It is not easily reproducable. It
claimed it had crash, but it didn't. I suspect this means a program or
task rhythmbox created had crashed.
Looking at ProcStatus, it seems that its related to the indexing of
meta-data. Which would also explain why the rhythmbox
Thank you for the bug report. Also, please answer these questions:
* Is this crash reproducible?
* If so, which are the steps that lead to it?
This will greatly aid us in tracking down your problem.
** Changed in: rhythmbox (Ubuntu)
Assignee: (unassigned) => Cristian Aravena Romero
S
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6608804/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6608805/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6608806/Disassembly.txt
** Attachm
13 matches
Mail list logo
