| Summary: | KWrite crashes attempting Open, from menu or toolbar. | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | aschmidt |
| Component: | kwrite | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | gerald.hameau, kare.sars, maarten.14C |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
aschmidt
2015-12-16 17:45:05 UTC
Are you by chance using Compiz as window manager? There seems to be a problem with Compiz and KDE applications at the moment: https://git.reviewboard.kde.org/r/126397/ I'm using kwin + nouveau + 2 monitors + GeForce 8400 GS Rev. 2 + Fedora 23. I'm aware that some applications (xpra, for example) blacklist nouveau. I unchecked "Enable compositor on startup," then logged in again, and clicking "Open" in the toolbar worked! I had been actually having tearing problems, so my compositor settings were using: Open GL 2.0 GLX Full screen repaints I have this crash, and more. They always involve file dialog. kwrite or kate : - open = crash - save as = crash. With or without content. I can open file through dolphin, and then save them, with both applications (eg: click on a file in dolphin, and open it with kwrite or kate... or use a previous kate session). fedora 22, with recent kde 5.5.0 update. Both kf5 5.16 & 5.17 window manager = kwin compositor = opengl 2.0, or 3.1, glx, on intel chipset (laptop, with nvidia secondary chip. Not active) There was a large swath up updates to kde files in F23 this morning. Lo, opening from the toolbar has worked for me twice with compositing on (having it work with compositing off worked before the update). One of the packages updated was indeed kwrite (qt5-qtbase-gui was not updated -- alas, "dnf history info last" gives me nothing, since I was stupid and allowed packagekit to do the update, and my ability to read the backtrace is limited as far as what to look at as a likely failure candidate). happens to me regularly on up-to-date F23. 'Open recent' causes no crashes. even if this might be older... *** This bug has been marked as a duplicate of bug 356840 *** (In reply to Kåre Särs from comment #6) > even if this might be older... > > *** This bug has been marked as a duplicate of bug 356840 *** I see no 'open' button when following the instructions of bug 35684, so cannot test if this causes the same behaviour. Am using KDE. Problem solved, on fedora 22, with today kf5 5.18 update. (In reply to Gérald Hameau from comment #8) > Problem solved, on fedora 22, with today kf5 5.18 update. problem still persists here with latest kf5 |