Summary: | konqueror crashes on initial run as fresh kde4 user in kde3 session | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Christoph Feck <cfeck> |
Component: | ksycoca | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | bartoschek, faure, finex, null |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Konsole output from the crash
Backtrace of the crash longer dbus timeout |
Description
Christoph Feck
2009-06-09 00:41:58 UTC
I'm not able to reproduce because I've only KDE 4 on my system. Anyway it looks like you've started konqueror 4 from the shell session. What is the output of konqueror --version ? P.S: Are you able to reproduce every time? Leonardo, thanks for looking into the problem. After some more tests, the problem is not really with Konqueror, but the crash occurs with any application started from a clean KDE. This bug should probably moved to kdecore. My main desktop is KDE3, and I have a separate "kde4" user account for testing. Insider Konsole3, I use "su - kde4" to log in as the kde4 user. Then I use the following commands to get rid of any stuff to simulate a clean KDE4: kill-kde4-binaries.sh rm -rf /home/kde4/.kde /var/tmp/kdecache-kde4 /tmp/kde-kde4 /tmp/ksocket-kde4 /home/kde4/.config /home/kde4/.local (The first command is only required when a previous attempt to run KDE4 programs was made; ask David Faure for the script.) Then running any KDE4 program results in the crash above. The crash happens delayed, probably after DBus decides to timeout. I will attach the Konsole output, as well as the crash that goes with it. Created attachment 36311 [details]
Konsole output from the crash
Created attachment 36312 [details]
Backtrace of the crash
Reproduced. The dbus call in ktoolinvocation (when kded calls kbuildsycoca4) times out (and then konqueror resumes too early, before ksycoca4 is ready). I see some solutions: - longer dbus timeout in ktoolinvocation - using qprocess in kded instead of ktoolinvocation (small performance hit) - launching async and waiting for the dbus signal when it's done (but what if it is never emitted...) (and a nested event loop sounds bad) Created attachment 36330 [details]
longer dbus timeout
David, thanks, but comment #7 did not help. *** Bug 205054 has been marked as a duplicate of this bug. *** *** Bug 238439 has been marked as a duplicate of this bug. *** Fixed by David Faure. http://commits.kde.org/kdelibs/53173d0fbb19d9d812b24291f257a04a7d099edb |