Version: unspecified OS: Linux i see the crash when i search for 'yast' or 'system' in the search field of the upper applist or when i try to add for example yast as an ressource Reproducible: Didn't try Steps to Reproduce: search as described above Actual Results: crash Expected Results: no crash
as i could not change the entries of the list-fields here in the bugtracker using active browser, here two additions: reproducibility: everytime priority: crash
I typed in "Images" on the search field of the application grid and plasma-device crashed. Before crashing, I saw some Nepomuk icons next to the "Images" icon. When the peek area was back, I couldn't get back online; there was an X icon instead of the wifi one. Note: I couldn't reproduce this bug always. Verified on 2011-10-16-16-48-meego-plasma-active-testing-USB-live.iso
Created attachment 64735 [details] crash report
Created attachment 65089 [details] plasma-device crash Just typing "sys" makes it crash. Tested on 2011-10-27-21-59-basyskom-plasma-active-testing-meego-usb-live.iso + latest updates from today.
#19 0xaf92c360 in LightDMDBus (this=0xcb16d98) at ../../../libs/kworkspace/kdisplaymanager.cpp:95 seriously, LightDM? that seems very odd. in any case, it's crashing on _creating_ the Session runner. that looks highly suspicious and like some sort of build issue. in the other crash it's asking for mimeDataForMatch which is VERY odd since that should ONLY be used for things like drag and drop of items. there is no need to call that at all for just general searchs, so perhaps the new model is doing something odd there?
Git commit b2d71803a0c71615df99265200c28e670897d26b by Aaron Seigo. Committed on 01/11/2011 at 11:27. Pushed by aseigo into branch 'master'. don't bother detecting for lightdm if the XDG_SEATH_PATH env var isn't set may be one cause of crashing for some people in the sessions Runner plugin CCBUG:283086 M +1 -1 libs/kworkspace/kdisplaymanager.cpp http://commits.kde.org/kde-workspace/b2d71803a0c71615df99265200c28e670897d26b
Javier, please do not mix different backtraces in the same bug report. Comment #4 is bug 285125.
(In reply to comment #7) > Javier, please do not mix different backtraces in the same bug report. Comment > #4 is bug 285125. The last crash was triggered by doing the same thing as before (typing an app name in the application grid's search field), that's why I included it. But you're right, they are different. Sorry for mixing it up.
Git commit 50b11f7af4acd4f20f9fbf662bc991b4fd95332b by Aaron Seigo. Committed on 01/11/2011 at 11:27. Pushed by aseigo into branch 'KDE/4.7'. don't bother detecting for lightdm if the XDG_SEATH_PATH env var isn't set may be one cause of crashing for some people in the sessions Runner plugin CCBUG:283086 M +1 -1 libs/kworkspace/kdisplaymanager.cpp http://commits.kde.org/kde-workspace/50b11f7af4acd4f20f9fbf662bc991b4fd95332b
Git commit 2f19a1c01ec94adc9f18e7a92fd3441416e0572f by Aaron Seigo. Committed on 01/11/2011 at 15:14. Pushed by aseigo into branch 'master'. ensure no allocations (iterator and ref usage) if what was allocated is cheap and as we have the match, just pass that directly to RunnerManager rather than the ID ... ... since it just uses the ID to find the Match again! CCBUG:283086 M +7 -8 dataengines/runner/runnersource.cpp http://commits.kde.org/plasma-mobile/2f19a1c01ec94adc9f18e7a92fd3441416e0572f
Already fixed on Project:KDE:Devel.