Summary: | Dockwidgets show ampersand sign | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Patrick Spendrin <ps_ml> |
Component: | kdeui | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christoph, kde-windows, kossebau |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick Spendrin
2010-01-02 23:46:47 UTC
This should be not a problem of just Okteta, but all DockWidget using programs, e.g. Dolphin. Some SC releases ago I fixed this, but obviously some change in kdelibs or Qt seems to have broken this fix. :( Which styles did you try? It could be an Qt QWindowsXPStyle issue, as I cannot reproduce with Oxygen, Plastique, or QWindowsStyle on X11. Perhaps those styles are just too smart and ignore the ampersand sign in the DockWidget title. The problem is rather that these ampersand signs get added at all, probably again by the KAcceleratorManager (or friend). Because neither Okteta nor Dolphin set the DockWidget titles to strings including any ampersand signs. They come from some third party. May perhaps also be the one which creates an endless loop if tabbing DockWidgets, as this work with pure Qt programs. Hm, you have this bug too that when you try to stack dockwidgets it loops infinitely and crashes? btw. it really is in XP (maybe Vista though) style. Since some month, yes, and once I asked on #kde-devel the one person (forgot who, was it you, pepo?) who replied tried and reported the same problem. But it never crashed for me, just froze with 100 % cpu-load (maybe I should wait a little more?). Do you have a backtrace (or even bko#)? I haven't yet taken on this bug, since I am out of experience with attaching gdb to a process (the prize if one's code is always flawless, öhem ;) ) hust, hust ;-) The backtrace is kind of stupid, but I found out that I get a strange recursion (or something like that) in KMainWindowPrivate::setSettingsDirty. I started to debug this a bit further, but now my KDE slowed down like hell, don't really know why. I'll try to debug this further, but I am not sure I can get it if my system fails this way. Please retry with a KF6 version, thanks! |