rhythmbox crashed but didn't really

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.

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 program itself wouldn't crash. My guess is: thats its a specific file that was causing this.

Another possibility is that the file being indexed was currently locked or still being written to. Perhaps its not so much a situation of fixing the crash, but making it recover gracefully when the meta-data-extractor fails. But thats just my 2 cents worth of speculation.

Could you try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report?

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 complete ubuntu-desktop (like ubuntu-desktop-debug)?
Perhaps even having ubuntu-desktop link to them during development, until the release-candidate? Esspecially for the rare, not reproduceable bugs?

StacktraceTop:?? () from /lib/ld-linux.so.2
?? ()
?? ()
?? ()
?? ()

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 retracing doesn't work when packages have been updated already?

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 address hidden> wrote:
>
> 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 retracing doesn't work when packages have been updated already?
>
> --
> rhythmbox crashed but didn't really
> https://bugs.launchpad.net/bugs/89571
> You received this bug notification because you are a direct subscriber
> of the bug.
>

could you get a new crash file?

ehm.. heb je dit per ongeluk naar me gemaild ofzo?

On 4/9/07, Ralf Nieuwenhuijsen <email address hidden> wrote:
>
>
> StacktraceTop:?? () from /lib/ld-linux.so.2
> ?? ()
> ?? ()
> ?? ()
> ?? ()
>
> ** Attachment added: "Stacktrace.txt (retraced)"
> http://librarian.launchpad.net/7223141/%3Cfdopen%3E
>
> --
> rhythmbox crashed but didn't really
> https://bugs.launchpad.net/bugs/89571
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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 you are able to make this bug happen again, please do so, and submit another report. The packages do not get updated much now, so we'll be able to use that stacktrace.

Any news on the bug?

Lawrence thank you for your bug interest, why do you think that's the same crash?

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.