Summary: | Kontact crashes on start | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Pogo_Dick |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | agateau, andresbajotierra, aurelien.gateau, borisss, hugo.pereira.da.costa, jsardid, kdenis, t.kijas |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Pogo_Dick
2010-11-22 10:49:15 UTC
[Comment from a bug triager] - Do you use Desktop Compositing ? This may be related to bug 254066 (the root cause seems to be the same as the backtrace is mostly the same) Thanks Yes, I'm using compositing, but disabling it does not fix the crash. But the backtrace is different. Thread 2 from here is missing and thread 1 is different. Here the backtrace through pastebin: http://pastebin.com/mk2np4hA I am quite confident this is fixed in Natty. Is it possible for you to try the latest alpha? Created attachment 57218 [details]
New crash information added by DrKonqi
kontact (4.4.9) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0
kontact crashes at start.
-- Backtrace (Reduced):
#7 QList (this=0x1) at ../../include/QtCore/../../src/corelib/tools/qlist.h:118
#8 QWidget::actions (this=0x1) at kernel/qwidget.cpp:3181
#9 0x01dd1e8d in DBusMenuExporterDBus::GetChildren (this=0x9c192c0, parentId=69, names=...) at ../3rdparty/dbusmenu-qt/src/dbusmenuexporterdbus_p.cpp:53
#10 0x01dea708 in DBusMenuExporterDBus::qt_metacall (this=0x9c192c0, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf8e328c) at .moc/release-shared/moc_dbusmenuexporterdbus_p.cpp:106
#11 0x006a79dc in QDBusConnectionPrivate::deliverCall (this=0x990e1f8, object=0x9c192c0, msg=..., metaTypes=..., slotIdx=8) at qdbusintegrator.cpp:919
Hi spqr, This bug should be fixed in Natty, is it possible for you to try the latest alpha? Aurélien Question: which widget style do you use ? And does this happen with every widget style ? Bug 267717 has exactly the same backtrace but happens only when using experimental oxygen-transparent widget style. *** Bug 267717 has been marked as a duplicate of this bug. *** In my case kontact crashes when using oxygen-transparent. At least in my case I think it is related to the way kontact (maybe only in kubuntu, not sure) manages transparency because I can use oxygen-transparent if I set the configuration to completely opaque (In reply to comment #5) > Hi spqr, > > This bug should be fixed in Natty, is it possible for you to try the latest > alpha? > > Aurélien So, any Kubuntu Natty tester to confirm whether it is reproducible ? I tried Kontact after my upgrade to Natty and I can confirm that bug https://bugs.kde.org/show_bug.cgi?id=267717 is fixed. I guess these other issues are also fixed although I didn't have them before... *** Bug 268794 has been marked as a duplicate of this bug. *** |