Summary: | File dialogs crash applications ( fileModule() returns 0 because KService failed to give a result ) | ||
---|---|---|---|
Product: | [Unmaintained] kfile | Reporter: | gabriel |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, baltasarq, cfeck, christopherheiny, faure, fleabus, gyurco, johnjaylward, m.janssens, nucleo, sebastian |
Priority: | NOR | ||
Version: | 4.10.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
gabriel
2010-10-20 11:34:08 UTC
In kfiledialog.cpp fileModule() returns 0 because KService failed to give a result (kbuildsycoca still running?) Christoph wrote http://kde.pastebin.ca/1974638 but I was wondering if we should just have that -instead- of the KService-based lookup. Sebastian, what do you think about the idea of replacing the trader query with a simple KConfig entry for the moduleName to use? How do you handle configuration right now anyway? Using keditfiletype? I'm not sure what's the best solution. Obviously the trader should be made to work, even if that means waiting longer for kbuildsycoca; but that's unrelated to both the proposed patch and my suggestion; it's something that has to be solved at a much lower level, in fact. *** Bug 263704 has been marked as a duplicate of this bug. *** *** Bug 262943 has been marked as a duplicate of this bug. *** If you can reproduce this crash with KDE 4.9.0 or newer please provide a new backtrace. Bug 320771 is from KDE 4.10.3 and shows the same issue. From the description: "I was also in the process of installing new KDE libraries (upgrade from kde 4.10.2 to 4.10.3) so it could be related to a mismatch of libraries at an inoportune time." Updating KDE could have caused the sycoca to be rebuild. *** Bug 320771 has been marked as a duplicate of this bug. *** *** Bug 327675 has been marked as a duplicate of this bug. *** *** Bug 323450 has been marked as a duplicate of this bug. *** It always happens to me, when I want to run an app compiled for an older version of kdelibs, and running a self-compiled KDE from the master branch (probably because of the system configuration cache mismatches?) This backtrace is created when tried to open a file in KolourPaint for 4.12.5 running in an environment 4.13.60: 0x000000332cbec0bf in KFileDialog::KFileDialog (this=0x7fffffffcb60, startDir=..., filter=..., parent=<optimized out>, customWidget=0x0) at /usr/src/debug/kdelibs-4.12.5/kio/kfile/kfiledialog.cpp:266 266 QWidget* fileQWidget = fileModule()->createFileWidget(startDir, this); *** Bug 347511 has been marked as a duplicate of this bug. *** Thanks for the report. The full redesign around KFileDialog and KFileWidget (+in ksycoca) means this can no longer happen in Plasma 5, closing. |