| Summary: | Digikam crashed upon startup | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Mark Szentes-Wanner <mark> |
| Component: | Preview-Video | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, colin, mark, myriam, sitter |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 6.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Mark Szentes-Wanner
2011-05-28 09:05:56 UTC
Crash occurs in Phonon / Pulse Audio backend Can you work out what the assertion was that caused this? Dr Konqui seems to swallow them up and not actually print them out? If in doubt, just run digikam manually with the --nocrashhandler and let me know what the assertion is. Created attachment 61002 [details]
New crash information added by DrKonqi
digikam (1.9.0) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2
This time the crash occurred again. I cannot say when digikam will crash and when not, so this time I did not start with the --nocrashhandler option. Sorry!
I hope you will see a difference to the other report.
-- Backtrace (Reduced):
#10 0x008537d9 in pa_context_connect () from /usr/lib/libpulse.so.0
#11 0x0050c068 in Phonon::PulseSupport::connectToDaemon (this=0xa863fe0) at ../../phonon/pulsesupport.cpp:904
#12 0x0050cb50 in Phonon::PulseSupport::qt_metacall (this=0xa863fe0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfa797dc) at ./moc_pulsesupport.cpp:78
[...]
#15 0x01ba94d7 in QSingleShotTimer::timeout (this=0xd01e568) at .moc/release-shared/qtimer.moc:82
#16 0x01ba958c in QSingleShotTimer::timerEvent (this=0xd01e568) at kernel/qtimer.cpp:308
Hmm, it's going to be really tricky to nail this down :( When this happens, do you happen to know if PA has restarted itself? (one way to tell is that if PA has been running since login, the device list in Phonon config should look nice. e.g. a list of device names (tho' that list may of course only have one entry in it!). It will be called something like "Internal Audio....". If it just has a single entry called "PulseAudio", then chances are it's been restarted. If PA has been restarted it could indicate that PA has crashed and it's left over remnants that cause this problem. It's just strange as I would have thought this problem should have cropped up a lot more if it was endemic... which is why this is quite strange... :s I'm not really sure what to suggest next. Perhaps try running "PULSE_LOG=99 pactl stat" after the crash to see if things in general are messed up (tho' I suspect things will have recovered by then :s). Like I say it's a tricky one to debug.. :s still an issue? Closing for lack of feedback. Please feel free to reopen if you can reproduce this with Phonon 4.6.0 or later and provide the requested feedback. Not reproducible since digiKam use QtAv framework + ffmpeg to handle video files. |