Hide Forgot
Description of problem: Whenever I close a luks loopback device, plasma desktop crashes. Version-Release number of selected component (if applicable): cryptsetup-luks-1.3.1-2.fc15.x86_64 kde 4.6.95 How reproducible: open a luks loopbackdevice, then close it and plasma crashes. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: I haven't tried i686 yet, but will.
I just checked: it does not happen on i686, only x86_64. I use the same script on both computers to create and mount, and unmount and delete the loopback devices. On the x86_64, the plasma-desktop crashes (the screen turns black, but the open windows remain, hence konsole is still active, then it restarts itself after a pause and a message about debugging). I just opened it again, and this time it did not happen, even though it had happened 3 times consecutively before I opened this bug report. Strange.
And now it crashed again!
I don't know if this is a luks problem, or a kde one.
Could you please provide backtrace for the crash? Reassigned to kdelibs, probably Solid issue.
(In reply to comment #4) > Could you please provide backtrace for the crash? > Could you tell me how I do that? A problem, the crash doesn't always occur. I just tried opening and closing an encrypted loopback device of the luks type and nothing happened. another time, yesterday, there was a crash, but plasma did not show the usual window for a crashed application. Sometimes it does; sometimes it doesn't.
Created attachment 513862 [details] autogenerated crash report
Okay, this time I did get the window that asks to report. I already reported, but it is presently downloading 400MB of debug programs. It cannot find the debug programs for kde-unstable, I presume, since there was some message about not finding some packages. Tell me which ones I should install.
Created attachment 513866 [details] crash report with the debug packages installed
I upgraded to kde-4.7.0. Unfortunately, this is not solved.
I changed the version to Fedora 16, since I had it happen again, since upgrading.
I was still happening this morning with kde-4.7.1. I just upgraded to 4.7.2, so I don't know yet.
I have been using kde-4.8.0 for a while and I haven't seen this for quite some time.