| Summary: | Konsole segfaults | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Malo Deniélou <pmdenielou> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | balcaen.john, gjmcgee, marja11 |
| Version: | Cauldron | Keywords: | NEEDINFO, UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=252602 | ||
| Whiteboard: | MGA2TOO | ||
| Source RPM: | konsole | CVE: | |
| Status comment: | |||
|
Description
Malo Deniélou
2012-01-17 16:32:31 CET
I guess you should report this bug upstream at bugs.kde.org CC:
(none) =>
balcaen.john Just done: https://bugs.kde.org/show_bug.cgi?id=291795 it does not crash here (but i'm currently running Qt 4.8.0 & the crash seems to occurs in Qt ) Could you install qt4-debug,konsole-debug, glib2.0-debug ? At KDE they say that it's the same as: https://bugs.kde.org/show_bug.cgi?id=252602 Jekyll says: "The unfortunate fact is although it is reproducible under certain conditions, it is hard to infer where the thing goes wrong. The backtrace is mostly Qt related." I'll install the debug packages, but so far I haven't been able to reproduce the crash. (In reply to comment #4) > At KDE they say that it's the same as: > https://bugs.kde.org/show_bug.cgi?id=252602 > so IBUS is needed to trigger it, funny. Keywords:
(none) =>
UPSTREAM
Marja Van Waes
2012-04-19 22:02:50 CEST
See Also:
(none) =>
https://bugs.kde.org/show_bug.cgi?id=252602 Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO
Manuel Hiebel
2012-06-12 21:04:15 CEST
Keywords:
NEEDINFO =>
(none) I'm seeing what may be the same or eerily similar bug on Mageia3... (Never saw it on MGA2, and I only see it on one of 5 MGA3 machines, 3 that have no issues are intel based laptops, the one with the persistant issue is AMD based desktop with a 6770 2GB video card. I have a 5th very similar AMD based machine with an NVidia GTX460 card at work with no issues. I even did a clean install on the effected machine with the issue as I assumed it was upgrade related, originally did online update from MGA2, same issue on same hardware. Will load up the debug rpms and see what I can see, only posted the hardware info as it is sometimes overlooked. (QT errors can be from ~anywhere in the rendering pipeline from what I can tell) Usually pops up when calling konsole from the taskbar, box shows KDEInit cannot start `/usr/bin/konsole' In fact, you usually can't start anything (firefox even) via kdeinit when this happens, so it may not be konsole per se, possibly an qt or ibus issue? Logging out/back in always clears the issue for awhile, and sometimes simply closing all konsole sessions and other open programs. CC:
(none) =>
gjmcgee In my case it may be related to bug9877, as I get a huge number of "[fglrx:firegl_apl_loadDatabase] *ERROR* APL: apl initialize fail." errors at the exact same time. Beta fglrx supposed to fix that, working it, curious as to hardware others seeing this "konsole" bug are using. Updating to the beta fglrx listed in bug 9877 has eliminated konsole launching issues for me, machine has been running 24 hours, no issues, I previously could recreate the issue simply by trying to launch multiple konsole sessions, after which ~nothing could be launched from the taskbar or alt+F2 (window would pop up, but kdeinit was locked up and nothing would actually run) Is this issue still present in Mageia 4 & 5? Keywords:
(none) =>
NEEDINFO Have not seen it in ages, I assume it was fixed upstream and corrected in regular updates. Closing as fixed then. Status:
NEW =>
RESOLVED |