Bug 1014466
Summary: | Kwin crashes intermittently when opening LibreOffice | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Gückel <pgueckel> | ||||
Component: | kde-workspace | Assignee: | Than Ngo <than> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 19 | CC: | dvratil, jgrulich, jreznik, kevin, ltinkl, mbriza, pgueckel, rdieter, rnovacek, than | ||||
Target Milestone: | --- | Keywords: | Upstream | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2014-03-04 04:09:36 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Peter Gückel
2013-10-02 06:49:01 UTC
Can you provide any backtraces (from abrt or drkonqi or whatever)? (In reply to Rex Dieter from comment #1) > Can you provide any backtraces (from abrt or drkonqi or whatever)? OK, next time it happens, I will save it. Do I need to install the debug packages? If so, which ones? debuginfo is indeed required for a good backtrace, drkonqi/abrt should handle that part for you. I was unable to cause a kwin Created attachment 806824 [details]
debuginfo
The program stated that this report provides useful information (***).
Ignore comment 4. By the way, it is kwin that crashes. Anyway, I had a hard time causing for a crash, and then, when I wasn't expecting it, it happened. I used drkonqi (says Crash Reporting Assistant in titlebar). It downloaded 79 debuginfo packages and wanted some others from kde-redhat, that it couldn't find. I installed them manually while the other packages were downloading. Unfortunately, not all of them were in kde-redhat/testing, but I guessed and I must have gotten the correct ones; Just for your information, it wanted: kdelibs-debuginfo kde-workspace-debuginfo kde-workspace-libs-debuginfo (not found) libworkspace-debuginfo (not found) kdepimlibs-debuginfo kdepimlibs-akonadi-debuginfo (not found) kactivities-debuginfo ksysguard-libs-debuginfo (not found) nepomuk-core-libs-debuginfo (not found, but I installed nepomuk-core-debuginfo) So... I allowed drkonqi to run and, once it finished, it asked me to log in to bugzilla. I am guessing that it wanted to generate a new bug report, which seems pointless (I think), so I just saved the output. It appears as an attachment to this bug report. I just wanted to note some of the surrounding conditions: I had firefox opened at the same time (on a different virtual desktop) as I attempted to open libreoffice-calc by clicking on a file name in dolphin. Firefox was displaying only a blank page with the tiles. I am using desktop effects. I am using OpenGL 2.0 compositing, Qt native graphics. Enabled effects are: Zoom Dashboard Fade Highlight Window Kscreen Login Logout Maximize Minimize Animation Screen Edge Screenshot Slide Sliding Popups Translucency wobbly Windows Startup Feedback Dialog Parent Dim Screen for Administrator Mode Desktop Grid Present Windows There is nothing else I can think of. may not be relevant, but I'd recommend using raster over native rendering (it is the upstream/recommmended default) Anyway, my recommendation would be, when/if this crashes again, to allow drkonqi to file an upstream bug at this point OK, I switched it to raster. I never changed it (maybe it got changed automatically when I experimented with OpenGL3 ?), so I am surprised it is the default. I think I'll just do it manually, since it crashes numerous times a day anyway. I will just copy the debug output and link to this report. Non? This is so old that I forgot about it. It clearly was the change to raster that solved it. I think there is no reason not to close this, as it was clearly the non-standard setting I had used that caused the problem. |