| Summary: | Bleachbit crashing KWin | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | trennor <trennor.turcotte95> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | ahz001, asraniel, kwin-bugs-null |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Attachement was generated by Crash Reporting Assistant (with some assistance from me; see above) | ||
i'm pretty sure this is a isse with bleachbit that deletes temporary files it is not supposed to delete. There was another similar bugreport where the author of bleachbit said he fixed it by no longer deleting kde* filde in /tmp. So, this is to 99% sure a bleachbit bug and not a kwin bug. and even if it is a kwin issue, the backtrace is missing debug symbols and is pretty useless in this regard (Dr.Konqui should have said so and offered to install debug packages). It crashes in KSharedDataCache::find() from KIconLoader -> this is just bug #254741 and it's SnakeOil's (*) - sorry "BleachBit's" fault by randomly shredding SHM objects, seems fixed in BB - see bug #271889 I feel brave enough to dupe this until a better backtrace can render me wrong. *** This bug has been marked as a duplicate of bug 254741 *** See http://bleachbit.sourceforge.net how to get notified of the BleachBit 0.8.8 beta which includes a fix. Until then, don't shred system temporary files, or in BleachBit add a whitelist for /var/tmp/kdecache-yourusername |
Created attachment 60597 [details] Attachement was generated by Crash Reporting Assistant (with some assistance from me; see above) Version: unspecified (using KDE 4.6.3) OS: Linux If I run Bleachbit, (user version), KWin crashes. Reproducible: Sometimes Actual Results: KWin shuts down, bug report daemon starts up, and can produce a backtrace (attached) but doesn't seem to be able to generate what it considers to be a complete report; complains there's not enough information. Yet, I can save at least part of a report. See attachment. Expected Results: No crash! What should the software have done instead? I've no idea; I'm a user, not a programmer or scripter.