[konsole] [Bug 463268] Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text
https://bugs.kde.org/show_bug.cgi?id=463268 Andreas Hartmetz changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/konsole/commit/b238fb ||29cf9fe061df8c79b07f5126346 ||bff9c88 Resolution|--- |FIXED --- Comment #8 from Andreas Hartmetz --- Git commit b238fb29cf9fe061df8c79b07f5126346bff9c88 by Andreas Hartmetz, on behalf of Matan Ziv-Av. Committed on 08/02/2023 at 15:56. Pushed by ahartmetz into branch 'master'. Fix bug in double-click selection A bug introduced in 0752cf3d prevents copying selection to clipboard if a key is pressed a short time after a double click. This is avoided by: - Do not exit selection mode in the time interval between a double click and a (potential) third click. - Save the selection text on a double click, and copy the saved text, rather than the current selection if no third click at the end of the triple click interval. M +31 -15 src/terminalDisplay/TerminalDisplay.cpp M +3-1src/terminalDisplay/TerminalDisplay.h https://invent.kde.org/utilities/konsole/commit/b238fb29cf9fe061df8c79b07f5126346bff9c88 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463268] Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text
https://bugs.kde.org/show_bug.cgi?id=463268 --- Comment #5 from Andreas Hartmetz --- Ah well, there's another thing: double-click to select quickly followed by middle click to paste pastes the selection from before the immediately preceding double-click. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463268] Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text
https://bugs.kde.org/show_bug.cgi?id=463268 --- Comment #4 from Andreas Hartmetz --- (In reply to Bug Janitor Service from comment #3) > A possibly relevant merge request was started @ > https://invent.kde.org/utilities/konsole/-/merge_requests/793 That one seems to fix it, thanks! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463268] Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text
https://bugs.kde.org/show_bug.cgi?id=463268 --- Comment #2 from Andreas Hartmetz --- Another way to reproduce: double-click to copy something from "git log", then quickly close the git log with q. Also doesn't copy. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463268] Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text
https://bugs.kde.org/show_bug.cgi?id=463268 --- Comment #1 from Andreas Hartmetz --- Correction: Shift-left/right arrow, not Ctrl-left/right arrow (the default IIRC) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463268] Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text
https://bugs.kde.org/show_bug.cgi?id=463268 Andreas Hartmetz changed: What|Removed |Added Assignee|konsole-de...@kde.org |ma...@svgalib.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463268] New: Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text
https://bugs.kde.org/show_bug.cgi?id=463268 Bug ID: 463268 Summary: Double-click to copy, then leaving konsole tab quickly (using keyboard?), does not copy text Classification: Applications Product: konsole Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: ahartm...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Double-click-select text in a konsole tab 2.a VERY quickly use a keyboard shortcut to switch to another konsole tab (Ctrl-left/right arrow for me) 2.b Using alt-tab to switch to another window entirely also reproduces the bug (let's say I want to paste a commit hash from konsole into this browser window with Bugzilla...) 3. Middle-click paste text OBSERVED RESULT The pasted text is what was in the middle-click buffer before step 1 EXPECTED RESULT The pasted text is what was selected in step 1 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: kde/5.15 from a few weeks ago ADDITIONAL INFORMATION This bug triggers more often for me than one might think. Seems like I tend to copy and tab away quickly. Because timing matters and it's new, I guess it's a bug in 0752cf3d6261d60bbb20a62194556b2377548368. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443698] Windows do not follow screens when changing screen positions
https://bugs.kde.org/show_bug.cgi?id=443698 Andreas Hartmetz changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Andreas Hartmetz --- This one is fixed here as well, thanks! Other problems have become much less severe after cleaning up my install directory and rebuilding the KDE stack. (Session restore mostly works, except for size / positioning being off in some applications - notably Kate - after restore.) That other stuff is mostly quite unrelated anyway, but I was very tired when I wrote the last comment, and I wanted time to think about it properly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443698] Windows do not follow screens when changing screen positions
https://bugs.kde.org/show_bug.cgi?id=443698 --- Comment #10 from Andreas Hartmetz --- Actually, I have big trouble with session restore since maybe four weeks ago. Sort of randomly, after session restore application windows do not materialize on the screen or in any taskbar (even thought the processes are running), and usually plasmashell needs a restart or two to appear in the correct size or at all It's getting hard to tell apart what exactly is which problem. Application windows that can be hidden and restored from tray *can* be restored from tray every time. Can you keep this open for a bit until I have investigated that or the bug gets too old? FWIW, the problem might be triggered by having the projector connected but disabled at startup. (But the applications do not seem to appear on the projector, "show applications from all windows" in the taskbar settings does nothing, enabling and disabling the projector also does not make any windows appear.) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418293] "filter account is missing" dialog does not show account names
https://bugs.kde.org/show_bug.cgi?id=418293 Andreas Hartmetz changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #3 from Andreas Hartmetz --- This seems related to bug 323455. In that case, the dialog should NOT appear, and it shouldn't be empty. In this case, I guess the dialog SHOULD appear, and again it shouldn't be empty. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443698] Windows do not follow screens when changing screen positions
https://bugs.kde.org/show_bug.cgi?id=443698 --- Comment #8 from Andreas Hartmetz --- (In reply to Andreas Hartmetz from comment #4) s/did stay on the right screen/did stay on the correct screen/ Further information: I am using Kubuntu 21.10 and X11 (Qt and KDE compiled from sources as stated), also most of x.org code I am using (most libraries, notably mesa) is self compiled, but not the Xorg server which is from /usr/lib/xorg/Xorg. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443698] Windows do not follow screens when changing screen positions
https://bugs.kde.org/show_bug.cgi?id=443698 --- Comment #7 from Andreas Hartmetz --- Created attachment 143070 --> https://bugs.kde.org/attachment.cgi?id=143070=edit What it looked like after applying the new configuration -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443698] Windows do not follow screens when changing screen positions
https://bugs.kde.org/show_bug.cgi?id=443698 --- Comment #6 from Andreas Hartmetz --- Created attachment 143069 --> https://bugs.kde.org/attachment.cgi?id=143069=edit The configuration with two screens, before pressing Apply in System Settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443698] Windows do not follow screens when changing screen positions
https://bugs.kde.org/show_bug.cgi?id=443698 --- Comment #5 from Andreas Hartmetz --- Created attachment 143068 --> https://bugs.kde.org/attachment.cgi?id=143068=edit Screenshot with one screen configuration -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443698] Windows do not follow screens when changing screen positions
https://bugs.kde.org/show_bug.cgi?id=443698 Andreas Hartmetz changed: What|Removed |Added Status|RESOLVED|REOPENED CC||ahartm...@gmail.com Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #4 from Andreas Hartmetz --- Ah, it is very nice that someone is taking care of it, thank you. But it doesn't work quite right yet. I have a 1920x1200 primary screen and I sometimes activate a 1920x1080 projector, placed logically above the primary screen because the images is in fact physically above. So far, I worked around the bug reported here by placing the projector logically to the right. I saw the fixes land and tried it again. The existing windows did stay on the right screen, but their height was reduced to almost nothing. I have Qt 5.15 compiled from branch "kde/5.15" and KDE everything master, compiled late on 2021-10-30 / early on 2021-10-31. Attachments: - before-one-screen.png: Screenshot with one screen configuration - two_screen_config_before_apply.png: The configuration with two screens, before pressing Apply in System Settings - after-two-screens.png: What it looked like after applying the new configuration What I wanted is that windows don't change size and stay in the exact same (physical) position on the same (physical) screen. Basically the first screenshot plus an empty second screen. It is possible that some remembered window positions for an earlier two-screen configuration are messing up the result. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437176] I keep getting a "Could not enter folder tags:/." error dialog box (with this release)
https://bugs.kde.org/show_bug.cgi?id=437176 Andreas Hartmetz changed: What|Removed |Added Ever confirmed|0 |1 CC||ahartm...@gmail.com Status|REPORTED|CONFIRMED --- Comment #3 from Andreas Hartmetz --- Confirming. A few weeks ago I briefly had this problem as well but assumed that it was just my problem due to something strange I may have done (or due to running a new git master all the time). At the time I made it go away by deleting either a Baloo data directory, data file, or config file - I forgot which. But I guess a workaround isn't enough if other people have the same problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 --- Comment #7 from Andreas Hartmetz --- Great job, thanks for fixing it so quickly! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 --- Comment #1 from Andreas Hartmetz --- Created attachment 128687 --> https://bugs.kde.org/attachment.cgi?id=128687=edit Three restored and three newly opened tabs By logging out and back into a session, in which Konsole was open with three tabs, I got three restored tabs. Then I opened three new tabs with Ctrl-Shift-T. Observe the difference in tab color. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 Andreas Hartmetz changed: What|Removed |Added CC||gcarnei...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 Andreas Hartmetz changed: What|Removed |Added CC||ahartm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 421906] New: Wrong tab colors after session restore
https://bugs.kde.org/show_bug.cgi?id=421906 Bug ID: 421906 Summary: Wrong tab colors after session restore Product: konsole Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: ahartm...@gmail.com Target Milestone: --- Created attachment 128686 --> https://bugs.kde.org/attachment.cgi?id=128686=edit Tab color settings page for affected session SUMMARY Wrong tab colors after session restore STEPS TO REPRODUCE 1. Open Konsole with any number of tabs (I have six) 2. End Plasma session (for me: shut down the computer) 3. Start new Plasma session (for me: turn on the computer) OBSERVED RESULT The color bar on the restored tabs is black EXPECTED RESULT The color bar on the tabs is light gray (application background color) - which is also the color of newly opened tabs (I use Ctrl-Shift-T). SOFTWARE/OS VERSIONS Linux/KDE Plasma: master as of today (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: compiled from sources, 5.14 branch (may be a few weeks old, almost nothing changed anyway) ADDITIONAL INFORMATION This might be a problem only with old Konsole configuration (Gustavo who did the tab color features might have deleted configuration several times during development, that is how it usually goes). The tab color setting in settings looks strange for me. See screenshot. The text says "user defined" in English. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396891] Regression: Cannot drop tab into existing window
https://bugs.kde.org/show_bug.cgi?id=396891 Andreas Hartmetz changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396726] regressions for tabbar in master
https://bugs.kde.org/show_bug.cgi?id=396726 Andreas Hartmetz changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #3 from Andreas Hartmetz --- Dropping into an existing Konsole window doesn't add the tab but creates another window: bug 396891 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396891] Regression: Cannot drop tab into existing window
https://bugs.kde.org/show_bug.cgi?id=396891 Andreas Hartmetz changed: What|Removed |Added Assignee|konsole-de...@kde.org |tcanabr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 396891] New: Regression: Cannot drop tab into existing window
https://bugs.kde.org/show_bug.cgi?id=396891 Bug ID: 396891 Summary: Regression: Cannot drop tab into existing window Product: konsole Version: master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: ahartm...@gmail.com Target Milestone: --- When tearing off a tab and dropping it into anything that isn't a Konsole window, a new Konsole window is created. So far so good. But when a tab is dropped into (the tabbar of) an existing Konsole window, another new window is created, too. I tested it with windows from the same Konsole process, the way it used to work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392099] Plasmashell crash on login with Qt 5.11 debug build
https://bugs.kde.org/show_bug.cgi?id=392099 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Product|kde |plasmashell Version|unspecified |master Component|general |Notifications Assignee|unassigned-b...@kde.org |k...@privat.broulik.de Target Milestone|--- |1.0 Platform|unspecified |Compiled Sources CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 392099] New: Plasmashell crash on login with Qt 5.11 debug build
https://bugs.kde.org/show_bug.cgi?id=392099 Bug ID: 392099 Summary: Plasmashell crash on login with Qt 5.11 debug build Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ahartm...@gmail.com Target Milestone: --- Application: plasmashell (5.12.80) (Compiled from sources) Qt Version: 5.11.0 Frameworks Version: 5.45.0 Operating System: Linux 4.13.0-37-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: Log in - Unusual behavior I noticed: The wallpaper (background) appeared, then with a slight delay the taskbar appeared, with several entries drawn on top of each other only slightly horizontally displaced. Then the shell froze and crashed. Then it restarted and kept working normally after that. It happened on two out of two logins after switching to Qt 5.11 (debug builds by the way, hence the assertions!) so I'm not sure if it happens every time. I guess this looks quite like an upstream bug really... The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8812a64940 (LWP 1637))] Thread 6 (Thread 0x7f8770025700 (LWP 2746)): #0 0x7f881d5f8951 in __GI___poll (fds=0x7f8768002de0, nfds=1, timeout=3305397) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8819f84169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8819f8427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f881df2beb0 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8768000b10, flags=...) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7f881deccc8b in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f8770024c30, flags=..., flags@entry=...) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventloop.cpp:136 #5 0x7f881decd0d9 in QEventLoop::exec(QFlags) (this=this@entry=0x7f8770024c30, flags=flags@entry=...) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventloop.cpp:214 #6 0x7f881dcff4d2 in QThread::exec() (this=this@entry=0x555818d87d80) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/thread/qthread.cpp:522 #7 0x7f87726a4e89 in KCupsConnection::run() (this=0x555818d87d80) at /home/horst/ksrc5/kde/kdeutils/print-manager/libkcups/KCupsConnection.cpp:304 #8 0x7f881dd0b375 in QThreadPrivate::start(void*) (arg=0x555818d87d80) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/thread/qthread_unix.cpp:367 #9 0x7f881d0d47fc in start_thread (arg=0x7f8770025700) at pthread_create.c:465 #10 0x7f881d604b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f877b1b5700 (LWP 2335)): #0 0x7f881d5f8951 in __GI___poll (fds=0x7f877400aab0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8819f84169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8819f8427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f881df2beb0 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8774000b10, flags=...) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventdispatcher_glib.cpp:425 #4 0x7f881deccc8b in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f877b1b4c10, flags=..., flags@entry=...) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventloop.cpp:136 #5 0x7f881decd0d9 in QEventLoop::exec(QFlags) (this=this@entry=0x7f877b1b4c10, flags=flags@entry=...) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventloop.cpp:214 #6 0x7f881dcff4d2 in QThread::exec() (this=this@entry=0x555816891970) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/thread/qthread.cpp:522 #7 0x7f881fb7e956 in QQuickPixmapReader::run() (this=0x555816891970) at /home/horst/ksrc5/qt/stable/qtdeclarative/src/quick/util/qquickpixmapcache.cpp:934 #8 0x7f881dd0b375 in QThreadPrivate::start(void*) (arg=0x555816891970) at /home/horst/ksrc5/qt/stable/qtbase/src/corelib/thread/qthread_unix.cpp:367 #9 0x7f881d0d47fc in start_thread (arg=0x7f877b1b5700) at pthread_create.c:465 #10 0x7f881d604b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f880e508700 (LWP 1886)): #0 0x7f881d5f8951 in __GI___poll (fds=0x7f88040029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f8819f84169 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8819f8427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f881df2beb0 in QEventDispatcherGlib::processEvents(QFlags)
[kwin] [Bug 389341] Kwin_X11 constantly restarting and not loading.
https://bugs.kde.org/show_bug.cgi?id=389341 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #1 from Andreas Hartmetz <ahartm...@gmail.com> --- Are you using some kind of very recent Mesa version? I had a similar problem and tried to bisect it, then it somehow disappeared. Possibly from deleting the shader cache. Try: rm -rf ~/.cache/mesa* -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378085] Assertion failure in KateViewSpace during session shutdown
https://bugs.kde.org/show_bug.cgi?id=378085 --- Comment #4 from Andreas Hartmetz <ahartm...@gmail.com> --- This actually did fix the crash for me, thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #18 from Andreas Hartmetz <ahartm...@gmail.com> --- Most games do, in fact, inhibit power saving. If you have a game running and open the energy management tray thingie, it will even tell you the name of the game blocking power saving (unfortunately, most don't bother changing the default so they are called something like "an SDL application"). AFAIK the power management inhibition is tied to the DBus name of the application. If the application dies, its DBus name vanishes, and the inhibition is removed as well. All these are not reasons against a workaround for sloppily programmed games, I am just saying that the power management inhibition system works very well when it is used. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380219] plasmashell crashes on startup w/ Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=380219 --- Comment #7 from Andreas Hartmetz <ahartm...@gmail.com> --- Haha, thanks for finding it. That commit does seem dubious in a library that is supposed to stay binary compatible. If a user really cared, they could check nullness of the image themselves. I've reverted that commit for now and my desktop works again. I'll leave it to someone who knows more about the details to mark this as upstream. Maybe the new behavior of Qt is reasonable after all? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380219] plasmashell crashes on startup w/ Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=380219 --- Comment #4 from Andreas Hartmetz <ahartm...@gmail.com> --- I unsuccefully tried to bisect it in qtdeclarative. The bug does not seem to be caused or triggered by any change between qtdeclarative v5.9.0-beta4 and current 5.9, commit df30d90eadcd92eebb4bf79f3eb251bc58d25d09 at the time of writing. H.d.V.: I have everything up to date on the 5.9 branch. Did they screw up the version numbers again? But even then, the only thing that is allowed to blow up is using different patch versions of libraries from the *same* module (I have had that once - there is no rule against it). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380219] plasmashell crashes on startup w/ Qt 5.9
https://bugs.kde.org/show_bug.cgi?id=380219 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com Priority|NOR |HI Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Andreas Hartmetz <ahartm...@gmail.com> --- I can reproduce it as well. Crash on startup, a showstopper. Raising priority even though it's probably an upstream bug. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 323455] "Filter account is missing" after KMail startup
https://bugs.kde.org/show_bug.cgi?id=323455 --- Comment #17 from Andreas Hartmetz <ahartm...@gmail.com> --- It still happens sometimes - for me, maybe on every 20th login. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365339] Several seconds delay switching to certain tabs
https://bugs.kde.org/show_bug.cgi?id=365339 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Andreas Hartmetz <ahartm...@gmail.com> --- This was fixed a few months ago. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378085] Assertion failure in KateViewSpace during session shutdown
https://bugs.kde.org/show_bug.cgi?id=378085 --- Comment #1 from Andreas Hartmetz <ahartm...@gmail.com> --- The crash actually happens every time here, but let's go with "sometimes" because it only happened on the second attempt in my xsm-based test session. The problem with it happening on regular session exit is that there is no time to save the backtrace... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378085] New: Assertion failure in KateViewSpace during session shutdown
https://bugs.kde.org/show_bug.cgi?id=378085 Bug ID: 378085 Summary: Assertion failure in KateViewSpace during session shutdown Product: kate Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: ahartm...@gmail.com Target Milestone: --- Application: kate (17.03.70) (Compiled from sources) Qt Version: 5.8.1 Frameworks Version: 5.33.0 Operating System: Linux 4.10.0-14-lowlatency x86_64 Distribution: Ubuntu Zesty Zapus (development branch) -- Information about the crash: Quitting the session, or alternatively the procedure described under "Testing and Debugging Session Management" here http://doc.qt.io/qt-5/session.html can be used. The crash then also happens when ending the session. For me it only seems to happen when in a Kate session (as opposed to X session) that was pre-existing and reopened. The crash can be reproduced sometimes. -- Backtrace: Application: Kate (kate), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9ae1efcd40 (LWP 8611))] Thread 9 (Thread 0x7f9accc2f700 (LWP 8643)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9ad6b3ba9b in cnd_wait (mtx=0x5596c789e240, cond=0x5596c789e268) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5596c789e6e0) at u_queue.c:158 #3 0x7f9ad6b3b7c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7f9ae7d4a6ca in start_thread (arg=0x7f9accc2f700) at pthread_create.c:333 #5 0x7f9ae8fb50ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 8 (Thread 0x7f9acd430700 (LWP 8642)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9ad6b3ba9b in cnd_wait (mtx=0x5596c789e240, cond=0x5596c789e268) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5596c789e6a0) at u_queue.c:158 #3 0x7f9ad6b3b7c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7f9ae7d4a6ca in start_thread (arg=0x7f9acd430700) at pthread_create.c:333 #5 0x7f9ae8fb50ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 7 (Thread 0x7f9acdc31700 (LWP 8641)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9ad6b3ba9b in cnd_wait (mtx=0x5596c789e240, cond=0x5596c789e268) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5596c789e660) at u_queue.c:158 #3 0x7f9ad6b3b7c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7f9ae7d4a6ca in start_thread (arg=0x7f9acdc31700) at pthread_create.c:333 #5 0x7f9ae8fb50ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 6 (Thread 0x7f9ace432700 (LWP 8640)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9ad6b3ba9b in cnd_wait (mtx=0x5596c789e240, cond=0x5596c789e268) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5596c789db20) at u_queue.c:158 #3 0x7f9ad6b3b7c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7f9ae7d4a6ca in start_thread (arg=0x7f9ace432700) at pthread_create.c:333 #5 0x7f9ae8fb50ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f9acee6d700 (LWP 8639)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9ad6b3ba9b in cnd_wait (mtx=0x5596c78a0360, cond=0x5596c78a0388) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5596c78a0950) at u_queue.c:158 #3 0x7f9ad6b3b7c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7f9ae7d4a6ca in start_thread (arg=0x7f9acee6d700) at pthread_create.c:333 #5 0x7f9ae8fb50ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f9acfdd6700 (LWP 8638)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9ad6b3ba9b in cnd_wait (mtx=0x5596c789d2c8, cond=0x5596c789d2f0) at ../../include/c11/threads_posix.h:159 #2 util_queue_thread_func (input=input@entry=0x5596c789db20) at u_queue.c:158 #3 0x7f9ad6b3b7c7 in impl_thrd_routine (p=) at ../../include/c11/threads_posix.h:87 #4 0x7f9ae7d4a6ca in start_thread (arg=0x7f9acfdd6700) at pthread_create.c:333 #5 0x7f9ae8fb50ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f9adcd22700 (LWP 8622)): #0
[kfile] [Bug 312747] KDE file open dialog truncates showing of file/folder names
https://bugs.kde.org/show_bug.cgi?id=312747 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #4 from Andreas Hartmetz <ahartm...@gmail.com> --- The fix was more about the name column being too narrow even when just opening one folder. By giving the other columns just their required widths and the rest to the name column, the name column automatically gets the maximum possible width, which kind of fixes this bug as a side effect. The interactions are pretty complicated so I've only pushed the change to master where it can get some testing and possibly further fixes. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 312747] KDE file open dialog truncates showing of file/folder names
https://bugs.kde.org/show_bug.cgi?id=312747 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kio/ ||9a997fba312f4d9596cc880685e ||c1e28deb7a665 --- Comment #3 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit 9a997fba312f4d9596cc880685ec1e28deb7a665 by Andreas Hartmetz. Committed on 12/11/2016 at 18:19. Pushed by ahartmetz into branch 'master'. Never stretch the last (=date) column in the file dialog. Stretching the date column makes it appear to need the excessive width when adding up non-name column widths in expandNameColumn(). The name column consequently became too narrow. Now why could the date column expand if the names needed a lot of space? It probably has something to do with expandNameColumn() being called several times while the directory model is loading and the exact order in which things are updated. Needs a more detailed analysis if this change causes a regression or still doesn't completely fix the problem. M +1-2src/filewidgets/kdiroperatordetailview.cpp http://commits.kde.org/kio/9a997fba312f4d9596cc880685ec1e28deb7a665 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 369275] Virtual symlinks to large files are not visible
https://bugs.kde.org/show_bug.cgi?id=369275 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kio/ ||44512b6acbe6bb1c595e330bef7 ||02a0100d7bd4b --- Comment #7 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit 44512b6acbe6bb1c595e330bef702a0100d7bd4b by Andreas Hartmetz, on behalf of Taro Yamada. Committed on 29/10/2016 at 19:13. Pushed by ahartmetz into branch 'master'. Sanitize the symlink name buffer size. Currently, KIO uses lstat to get the buffersize for readlink. But in certain situations, it returns an inappropriate value. For example, "/proc/self" or "/sys/bus/cpu/devices/*" returns its size is 0, and then readlink fails with EINVAL (so the link won't be shown in KDE applications). TMSU seems to return the target's actual filesize instead of the link size, i.e. the length of the target's filename. This patch limits the initial buffer size to sane values and expands the buffer when needed. The behavior is similar to ls, so it should be compatible with all filesystems. REVIEW: 129259 M +16 -6src/ioslaves/file/file.cpp http://commits.kde.org/kio/44512b6acbe6bb1c595e330bef702a0100d7bd4b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.
https://bugs.kde.org/show_bug.cgi?id=346768 --- Comment #79 from Andreas Hartmetz <ahartm...@gmail.com> --- For the record, konsole had a separate session restore bug (bug 367447) which has also been fixed. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 325442] Constant loop reading of /etc/passwd from /proc updates
https://bugs.kde.org/show_bug.cgi?id=325442 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #8 from Andreas Hartmetz <ahartm...@gmail.com> --- The reading of /etc/passwd is just the most visible symptom, it can be fixed with KDirWatch. Ideally there'd be ways to blocking-wait for changes in all (or as many as possible) of the process / tab title information. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365339] Several seconds delay switching to certain tabs
https://bugs.kde.org/show_bug.cgi?id=365339 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Andreas Hartmetz <ahartm...@gmail.com> --- By the way, I'm using Qt 5.7 branch. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365339] Several seconds delay switching to certain tabs
https://bugs.kde.org/show_bug.cgi?id=365339 --- Comment #1 from Andreas Hartmetz <ahartm...@gmail.com> --- Created attachment 9 --> https://bugs.kde.org/attachment.cgi?id=9=edit Backtraces and thread info taken while konsole is hanging -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365339] New: Several seconds delay switching to certain tabs
https://bugs.kde.org/show_bug.cgi?id=365339 Bug ID: 365339 Summary: Several seconds delay switching to certain tabs Product: konsole Version: master Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ahartm...@gmail.com I like to use infinite scrollback. Since recently, it takes several seconds to switch to tabs with many thousands of lines of scrollback, such as from compiling a large project with qmake. From the attached backtrace (and other gdb info dump) it looks like konsole's filtering for highlighting etc. is what is taking so long. I think it's probably scanning more than it has to, which would be really just the current screen. And it probably handled it more cleverly before. Needless to say, the current behavior is quite annoying. Reproducible: Always Steps to Reproduce: 1. Get a few thousand lines of scrollback in a tab (compiling something with qmake works well) 2. Make sure that the scrollback is still growing (konsole is smart enough not to rescan completely constant contents) 3. Switch to another tab 4. Switch back to the tab with lots of lines Actual Results: konsole hangs for some time before the tab with the long scrollback is shown. Expected Results: konsole shows the tab with the long scrollback quasi-instantly, which it used to do before. I think this is major because it kind of kills the infinite scrollback feature and even makes tab switching with "just" 1000 lines a bit slower. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #24 from Andreas Hartmetz <ahartm...@gmail.com> --- I'm with Martin. We should make sure that our processes terminate to avoid wasting resources. Independent of that, systemd is wrong to change behavior because the way it used to work was good. Logout - end the session, leave detached processes alone. Shutdown / reboot - kill everything that still lives and only wait for a very short time. It is not hard to understand why that is the right behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly
https://bugs.kde.org/show_bug.cgi?id=358019 --- Comment #10 from Andreas Hartmetz <ahartm...@gmail.com> --- Note: "some processes" is not precise enough, I take this to be about Kate. There is still a known (to me at least) problem with shutdown because indeed "some processes" don't terminate voluntarily and systemd (unlike other init systems) waits for them for a full two minutes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly
https://bugs.kde.org/show_bug.cgi?id=358019 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Andreas Hartmetz <ahartm...@gmail.com> --- Assuming it's fixed, please reopen if it's not fixed in a recent version. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 --- Comment #8 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit 2946faa9a4e1fa2eb85d67f0bb11bd3f62f331aa by Andreas Hartmetz. Committed on 23/06/2016 at 19:06. Pushed by ahartmetz into branch 'master'. Revert "Remove legacy session management support." This reverts commit 5f0ca1305db4a925dbdbf927f541497be334feff. Firefox and some GTK+ 2 applications still seem to use the old way. For shame. Cherry-picked from 5.6. M +1-0ksmserver/CMakeLists.txt A +419 -0ksmserver/legacy.cpp [License: UNKNOWN] * M +1-0ksmserver/server.cpp M +26 -2ksmserver/server.h M +11 -1ksmserver/shutdown.cpp M +2-0ksmserver/startup.cpp The files marked with a * at the end have a non valid license. Please read: http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. http://commits.kde.org/plasma-workspace/2946faa9a4e1fa2eb85d67f0bb11bd3f62f331aa -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 --- Comment #9 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit 03f0dc51d72ba0ad55fe077a519e1041c937ac6d by Andreas Hartmetz. Committed on 23/06/2016 at 19:07. Pushed by ahartmetz into branch 'master'. Revert "Remove saving and loading (and client matching by) WM_COMMAND." This reverts commit 2eac7634cc524bf5e425cf081a639a6b6407e380. Cherry-picked from 5.6. M +1-1activities.cpp M +17 -4sm.cpp M +1-0sm.h M +13 -0toplevel.cpp M +1-0toplevel.h http://commits.kde.org/kwin/03f0dc51d72ba0ad55fe077a519e1041c937ac6d -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 --- Comment #7 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit bdf555bbcb277566d5901de9902990024f680dfe by Andreas Hartmetz. Committed on 23/06/2016 at 18:59. Pushed by ahartmetz into branch 'Plasma/5.7'. Revert "Remove saving and loading (and client matching by) WM_COMMAND." This reverts commit 2eac7634cc524bf5e425cf081a639a6b6407e380. Cherry-picked from 5.6. M +1-1activities.cpp M +17 -4sm.cpp M +1-0sm.h M +13 -0toplevel.cpp M +1-0toplevel.h http://commits.kde.org/kwin/bdf555bbcb277566d5901de9902990024f680dfe -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 --- Comment #6 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit aee734e126b16db3be510a46ead9134c987fc97b by Andreas Hartmetz. Committed on 23/06/2016 at 19:00. Pushed by ahartmetz into branch 'Plasma/5.7'. Revert "Remove legacy session management support." This reverts commit 5f0ca1305db4a925dbdbf927f541497be334feff. Firefox and some GTK+ 2 applications still seem to use the old way. For shame. Cherry-picked from 5.6. M +1-0ksmserver/CMakeLists.txt A +419 -0ksmserver/legacy.cpp [License: UNKNOWN] * M +1-0ksmserver/server.cpp M +26 -2ksmserver/server.h M +11 -1ksmserver/shutdown.cpp M +2-0ksmserver/startup.cpp The files marked with a * at the end have a non valid license. Please read: http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. http://commits.kde.org/plasma-workspace/aee734e126b16db3be510a46ead9134c987fc97b -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 --- Comment #5 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit 59740e7416bb2b3a9852212fa4b213e5ba76deb7 by Andreas Hartmetz. Committed on 23/06/2016 at 17:40. Pushed by ahartmetz into branch 'Plasma/5.6'. Revert "Remove saving and loading (and client matching by) WM_COMMAND." This reverts commit 2eac7634cc524bf5e425cf081a639a6b6407e380. M +1-1activities.cpp M +17 -4sm.cpp M +1-0sm.h M +13 -0toplevel.cpp M +1-0toplevel.h http://commits.kde.org/kwin/59740e7416bb2b3a9852212fa4b213e5ba76deb7 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/plas ||ma-workspace/e4a76cd947759f ||d723935965ca30c00021601a45 Status|CONFIRMED |RESOLVED --- Comment #4 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit e4a76cd947759fd723935965ca30c00021601a45 by Andreas Hartmetz. Committed on 23/06/2016 at 17:36. Pushed by ahartmetz into branch 'Plasma/5.6'. Revert "Remove legacy session management support." This reverts commit 5f0ca1305db4a925dbdbf927f541497be334feff. Firefox and some GTK+ 2 applications still seem to use the old way. For shame. M +1-0ksmserver/CMakeLists.txt A +419 -0ksmserver/legacy.cpp [License: UNKNOWN] * M +1-0ksmserver/server.cpp M +26 -2ksmserver/server.h M +11 -1ksmserver/shutdown.cpp M +2-0ksmserver/startup.cpp The files marked with a * at the end have a non valid license. Please read: http://techbase.kde.org/Policies/Licensing_Policy and use the headers which are listed at that page. http://commits.kde.org/plasma-workspace/e4a76cd947759fd723935965ca30c00021601a45 -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 329476] no sound device found but it is present
https://bugs.kde.org/show_bug.cgi?id=329476 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Andreas Hartmetz <ahartm...@gmail.com> --- Peter, do you have a custom alsa configuration? This might be a duplicate of bug 182847. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 182847] Phonon-4.3.0 not all alsa pcm listed
https://bugs.kde.org/show_bug.cgi?id=182847 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #14 from Andreas Hartmetz <ahartm...@gmail.com> --- This is probably due to an upstream bug that was fixed by yours truly in VLC 2.2.2. If the default device was created in an .asoundrc / alsa.conf, it could not be selected in VLC. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.
https://bugs.kde.org/show_bug.cgi?id=346768 --- Comment #68 from Andreas Hartmetz <ahartm...@gmail.com> --- Kubuntu 16.04 does not have Qt 5.6, so session management is not expected to work right in it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 355457] Resume from sleep cause kwin crash
https://bugs.kde.org/show_bug.cgi?id=355457 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from Andreas Hartmetz <ahartm...@gmail.com> --- I get a similar backtrace (at least the same failed assertion) after running zdoom (a Doom engine) with unredirection in full screen enabled. After exiting the game, the window decorations (shadows?) flicker and look very glitchy. kwin will usually crash in less than a minute in that state. If I run kwin_x11 --replace, the old instance crashes during exit. I have a backtrace of that: Application: KWin (kwin_x11), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9a1df1f940 (LWP 3573))] Thread 2 (Thread 0x7f9a17fff700 (LWP 3585)): #0 0x7f9a2b908d13 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f9a2a4b4562 in qt_safe_select (nfds=8, fdread=0x7f9a1a78, fdwrite=0x7f9a1d08, fdexcept=0x7f9a1f98, orig_timeout=) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/kernel/qcore_unix.cpp:75 #2 0x7f9a2a4b4b8d in QEventDispatcherUNIX::select (this=, nfds=, readfds=, writefds=, exceptfds=, timeout=) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:320 #3 0x7f9a2a4b6157 in QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7f9a18e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:196 #4 0x7f9a2a4b6945 in QEventDispatcherUNIX::processEvents (this=0x7f9a18c0, flags=...) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventdispatcher_unix.cpp:607 #5 0x7f9a2a461eec in QEventLoop::processEvents (this=this@entry=0x7f9a17ffec60, flags=..., flags@entry=...) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventloop.cpp:128 #6 0x7f9a2a46232b in QEventLoop::exec (this=this@entry=0x7f9a17ffec60, flags=..., flags@entry=...) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/kernel/qeventloop.cpp:204 #7 0x7f9a2a2b76c0 in QThread::exec (this=this@entry=0x7f9a26fb1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/thread/qthread.cpp:504 #8 0x7f9a26f3b05c in QDBusConnectionManager::run (this=0x7f9a26fb1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /opt/src/ksrc5/qt/stable/qtbase/src/dbus/qdbusconnection.cpp:181 #9 0x7f9a2a2bcfe9 in QThreadPrivate::start (arg=0x7f9a26fb1d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/thread/qthread_unix.cpp:340 #10 0x7f9a2b3276fa in start_thread (arg=0x7f9a17fff700) at pthread_create.c:333 #11 0x7f9a2b912b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f9a1df1f940 (LWP 3573)): [KCrash Handler] #6 0x7f9a2b841418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f9a2b84301a in __GI_abort () at abort.c:89 #8 0x7f9a2a2a6395 in qt_message_fatal (message=, context=...) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/global/qlogging.cpp:1645 #9 QMessageLogger::fatal (this=this@entry=0x7ffcbdc5c1f0, msg=msg@entry=0x7f9a2a5093a0 "ASSERT: \"%s\" in file %s, line %d") at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/global/qlogging.cpp:790 #10 0x7f9a2a2a0678 in qt_assert (assertion=assertion@entry=0x7f9a2b76a262 "m_cache.isEmpty()", file=file@entry=0x7f9a2b765d80 "/home/horst/ksrc5/kde/workspace/kwin/scene_opengl.cpp", line=line@entry=2196) at /opt/src/ksrc5/qt/stable/qtbase/src/corelib/global/qglobal.cpp:2999 #11 0x7f9a2b6a6e45 in KWin::DecorationShadowTextureCache::~DecorationShadowTextureCache (this=, __in_chrg=) at /home/horst/ksrc5/kde/workspace/kwin/scene_opengl.cpp:2196 #12 0x7f9a2b845fe8 in __run_exit_handlers (status=0, listp=0x7f9a2bbcf5f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #13 0x7f9a2b846035 in __GI_exit (status=) at exit.c:104 #14 0x7f9a2b82c837 in __libc_start_main (main=0x4008b4 <main(int, char**)>, argc=3, argv=0x7ffcbdc5c358, init=, fini=, rtld_fini=, stack_end=0x7ffcbdc5c348) at ../csu/libc-start.c:325 #15 0x004007d9 in _start () -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349481] konsole session sometimes is not saved into ~/.config/ksmserverrc on logout
https://bugs.kde.org/show_bug.cgi?id=349481
--- Comment #19 from Andreas Hartmetz <ahartm...@gmail.com> ---
I meant ABI change in the sense that if something is compiled against the new
API, it won't run against an older version.
Applications that use KMainWindow (from kxmlgui framework) or KApplication
(from kdelibs4support framework) are fixed automatically. Others all need to be
fixed separately ("disable fallback session management").
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 349481] konsole session sometimes is not saved into ~/.config/ksmserverrc on logout
https://bugs.kde.org/show_bug.cgi?id=349481 --- Comment #16 from Andreas Hartmetz <ahartm...@gmail.com> --- (In reply to Rex Dieter from comment #15) > I'm skeptical of the claim that a full rebuild is required, are you > suggesting that qt-5.6.x introduced some abi change wrt session-management? > If so, what evidence do you have for that claim? 5.6.0 introduced new API that is unfortunately required to fix the bug. That's of course also an ABI change. Evidence: commit e7bf0edfd49de9a4d8285fbe8d878f8fda910e6d in qtbase. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 346768] After login only one tab is present, when several tabs where opened before logout.
https://bugs.kde.org/show_bug.cgi?id=346768 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #66 from Andreas Hartmetz <ahartm...@gmail.com> --- Is the following correct: - Things are mostly fixed now - The ksmserver patch is still needed to make aborted shutdown/logout work correctly? If so, I'm planning to have a look at the ksmserver patch (no promises). The logic in ksmserver does look dubious to me, on the other hand it has worked alright for a long time so one needs to be very careful. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349481] konsole session sometimes is not saved into ~/.config/ksmserverrc on logout
https://bugs.kde.org/show_bug.cgi?id=349481 --- Comment #14 from Andreas Hartmetz <ahartm...@gmail.com> --- (In reply to linuxfluesterer from comment #13) > (In reply to Andreas Hartmetz from comment #12) > > (In reply to linuxfluesterer from comment #11) > > > Hmm, I already use Plasma 5.6.1 as date of 29/03/2016. The above BUG is > > > still given for KDE/Plasma specific applicatitions like Konsole, KWrite, > > > Settings and so on. > > > To relogin to a saved session (last session) was a fine thing in KDE 4.x, > > > because it worked. > > > Is there any try, any work to solve this bug in close future. > > > I would be glad about. > > > Thank you... > > > > Your KDE stack needs to be compiled against Qt 5.6 to fix this. This is hard > > to change without compiling KDE yourself. Even installing Qt 5.6 won't help. > > So then... is there any plan, any schedule to compile KDE by the developers? > If not, could I compile complete KDE packages (Plasma 5.6 Meta packages > maybe) by using Gentoo and the 'emerge' command? > I'm a Sabayon user. Sabayon is a rolling release and offers precompiled > binaries. > Thank you. We don't ship compiled packages, distributions do. They could also backport the necessary changes in Qt and remove the Qt version check in KDE. If you use Gentoo, sure, you can compile your own and get those changes. But I do not know whether they are already in (your) stable versions of Frameworks 5 and Plasma and applications (where necessary). I haven't done much else for KDE recently, so if you see my name in the commit logs of kdelibs4support, kxmlgui and plasma-workspace in those versions, you have recent enough versions. The commit message should be about "fallback session management". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 349481] konsole session sometimes is not saved into ~/.config/ksmserverrc on logout
https://bugs.kde.org/show_bug.cgi?id=349481 --- Comment #12 from Andreas Hartmetz <ahartm...@gmail.com> --- (In reply to linuxfluesterer from comment #11) > Hmm, I already use Plasma 5.6.1 as date of 29/03/2016. The above BUG is > still given for KDE/Plasma specific applicatitions like Konsole, KWrite, > Settings and so on. > To relogin to a saved session (last session) was a fine thing in KDE 4.x, > because it worked. > Is there any try, any work to solve this bug in close future. > I would be glad about. > Thank you... Your KDE stack needs to be compiled against Qt 5.6 to fix this. This is hard to change without compiling KDE yourself. Even installing Qt 5.6 won't help. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 131994] kio bombs remote servers with requests if opening files in parallel
https://bugs.kde.org/show_bug.cgi?id=131994 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Andreas Hartmetz <ahartm...@gmail.com> --- A bit late, but this has been fixed a few years ago. The number of connections per host is limited, and for SFTP the limit is two. -- You are receiving this mail because: You are watching all bug changes.
[kde-windows] [Bug 320319] SFTP kioslave does not behave as expected with the file opening dialog
https://bugs.kde.org/show_bug.cgi?id=320319 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #7 from Andreas Hartmetz <ahartm...@gmail.com> --- About the bug where it tries to open a file instead of the folder of the file, that bug is actually an application bug in Kate and KWrite. Bug 352490 about that has been fixed. If the remaining problems in this bug are just about that, this can be closed. But apparently there are other problems? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 352490] File -> Open error when already have sftp:// file open
https://bugs.kde.org/show_bug.cgi?id=352490 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||ahartm...@gmail.com --- Comment #2 from Andreas Hartmetz <ahartm...@gmail.com> --- The "trying to open file as folder" bug has been fixed in Kate and KWrite master today. It was simply passing the full file URL to the open file dialog. For some reason, that worked with local files. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 345253] Folder I'm currently in not restored when selecting "Open file" with remote protocol
https://bugs.kde.org/show_bug.cgi?id=345253 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #18 from Andreas Hartmetz <ahartm...@gmail.com> --- Regarding the wrong path in open dialog, see bug 352490. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 154839] Allow alternate shortcuts in list of global shortcuts
https://bugs.kde.org/show_bug.cgi?id=154839 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #19 from Andreas Hartmetz <ahartm...@gmail.com> --- Fixed with a48cdc289c054934c5d04c525c5687c9b49f7df6 on April 20th 2015. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #49 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit a08befeac43647e222f48dfd7bed067be81573c4 by Andreas Hartmetz. Committed on 19/02/2016 at 19:08. Pushed by ahartmetz into branch 'master'. KNotes: fix session save / restore. Requires Qt >= 5.6.0 or recent 5.6 branch. M +3-0knotes/src/apps/knotesapp.cpp http://commits.kde.org/kdepim/a08befeac43647e222f48dfd7bed067be81573c4 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #47 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit 58e49487aece3de19aae90bbb9b80cd5aab94d04 by Andreas Hartmetz. Committed on 19/02/2016 at 18:55. Pushed by ahartmetz into branch 'master'. Fix session management for KApplication based applications. - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent premature application exit - Wire up the saveStateRequest() and commitDataRequest() signals to the appropriate methods that had to be turned into slots first. Those methods were never even called, they were not ported properly. - Cancel logout when the user decides to do that. A comment in the code was not sufficient to do that. (?!?!) M +16 -1src/kdeui/kapplication.cpp M +15 -14 src/kdeui/kapplication.h http://commits.kde.org/kdelibs4support/58e49487aece3de19aae90bbb9b80cd5aab94d04 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kxml ||gui/f7cbcc77722256db084d3b0 ||ab6ce76173e959f0e Status|REOPENED|RESOLVED --- Comment #47 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit 58e49487aece3de19aae90bbb9b80cd5aab94d04 by Andreas Hartmetz. Committed on 19/02/2016 at 18:55. Pushed by ahartmetz into branch 'master'. Fix session management for KApplication based applications. - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent premature application exit - Wire up the saveStateRequest() and commitDataRequest() signals to the appropriate methods that had to be turned into slots first. Those methods were never even called, they were not ported properly. - Cancel logout when the user decides to do that. A comment in the code was not sufficient to do that. (?!?!) M +16 -1src/kdeui/kapplication.cpp M +15 -14 src/kdeui/kapplication.h http://commits.kde.org/kdelibs4support/58e49487aece3de19aae90bbb9b80cd5aab94d04 --- Comment #48 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit f7cbcc77722256db084d3b0ab6ce76173e959f0e by Andreas Hartmetz. Committed on 19/02/2016 at 18:49. Pushed by ahartmetz into branch 'master'. Fix session management broken since KF5 / Qt5. Requires Qt 5.6 branch not more than a few days old, or >= 5.6.0 when it is released. Parts of the fix are: - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent application suicide through a mechanism that tries to help applications without any proper session management support, but badly interferes with applications that do implement proper session management, such as KDE applications. - Add back commitData[Request] handling. For some reason it was removed during porting. - Change the returned types of saveState() and commitData() to void. The return values were unused. M +41 -3src/kmainwindow.cpp M +2-1src/kmainwindow_p.h http://commits.kde.org/kxmlgui/f7cbcc77722256db084d3b0ab6ce76173e959f0e -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kxml ||gui/f7cbcc77722256db084d3b0 ||ab6ce76173e959f0e Status|REOPENED|RESOLVED --- Comment #48 from Andreas Hartmetz <ahartm...@gmail.com> --- Git commit f7cbcc77722256db084d3b0ab6ce76173e959f0e by Andreas Hartmetz. Committed on 19/02/2016 at 18:49. Pushed by ahartmetz into branch 'master'. Fix session management broken since KF5 / Qt5. Requires Qt 5.6 branch not more than a few days old, or >= 5.6.0 when it is released. Parts of the fix are: - Call QGuiApplication::setFallbackSessionManagementEnabled(false) to prevent application suicide through a mechanism that tries to help applications without any proper session management support, but badly interferes with applications that do implement proper session management, such as KDE applications. - Add back commitData[Request] handling. For some reason it was removed during porting. - Change the returned types of saveState() and commitData() to void. The return values were unused. M +41 -3src/kmainwindow.cpp M +2-1src/kmainwindow_p.h http://commits.kde.org/kxmlgui/f7cbcc77722256db084d3b0ab6ce76173e959f0e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348031] replugging mouse re-enables touchpad; prevents shutdown/restart/logoff; programs won't open
https://bugs.kde.org/show_bug.cgi?id=348031 Andreas Hartmetz <ahartm...@gmail.com> changed: What|Removed |Added CC||ahartm...@gmail.com --- Comment #2 from Andreas Hartmetz <ahartm...@gmail.com> --- The part about not being able to log out seems session management related - the session management protocol XSMP allows applications to cancel logout. Session management is generally somewhat broken in Qt currently, with one failure mode being undesired cancellation of session exit. In some applications Qt tries to close all windows and if the appllication refuses that (it may do that in response to user input or due to some decision made purely internally), it's interpreted as the application refusing to close and also cancelling session exit. I am working on that. If the problem doesn't disappear by itself by fixing that, some more targeted bug hunting will be necessary. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #45 from Andreas Hartmetz <ahartm...@gmail.com> --- ..and frankly, I don't feel like gold-plating the solution to this mess. It's not going to be pretty either way, nobody cares too much except when their stuff breaks (ours did), and there are many people to convince to effect really big changes. There is bigger fish to fry. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #44 from Andreas Hartmetz <ahartm...@gmail.com> --- I don't think that either dynamic properties or changing behavior that has been pretty much proven to be not broken by being around for over 10 years with no complaints will fly upstream, and I don't think they are a very good idea myself. For Qt5, an application attribute might be a good idea. For Qt6, I don't know. I mean there is the small problem that pseuso-SM for applications that think ignoring SM is fine only works if it asks absolutely nothing from applications. An application attribute might even work there as well: if you do care about SM, you have let's say at least 20 lines to write so you can live with another trivial one. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #41 from Andreas Hartmetz <ahartm...@gmail.com> --- Those patches are just what I currently have, they are just intended to show the important logic changes. I wasn't really planning to even submit them for review because unfortunately I seem to be the expert on session management. It seems pretty clear that applications either largely expect KDE4 behavior through old APIs, which the patches restore, or they don't but still expect not to get killed for no good reason. The solution there is clear as well. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #39 from Andreas Hartmetz <ahartm...@gmail.com> --- These patches mostly fix session saving (and therefore restoring), together with the necessary Qt patch. Applications not using KApplication or KMainWindow will need to call QSessionManager::setAutoCloseWindowsEnabled(false) themselves. There a some processes like that in your average KDE session but the patches are trivial so I'm not posting them. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #38 from Andreas Hartmetz <ahartm...@gmail.com> --- Created attachment 96914 --> https://bugs.kde.org/attachment.cgi?id=96914=edit Fix session saving / KMainWindow changes -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #37 from Andreas Hartmetz <ahartm...@gmail.com> --- Created attachment 96913 --> https://bugs.kde.org/attachment.cgi?id=96913=edit Fix session saving / KApplication changes -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #34 from Andreas Hartmetz <ahartm...@gmail.com> --- Yes indeed, it doesn't work because ignoring close events cancels logout. Damn. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #29 from Andreas Hartmetz <ahartm...@gmail.com> --- We cannot change Qt in a way that breaks existing applications. Qt5 has not exactly just been released, and commercial customers value stability very much. Some of them even pay for Qt licenses, which is good for all Qt users, so really, we should not make things worse for them. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #27 from Andreas Hartmetz <ahartm...@gmail.com> --- You can't just send fake close events to clients that don't expect that. That... technique... is a KDE specialty. KDE applications are written to deal with it. In the general case, though, it is legitimate to start destroying internal data structures in a close event, and it is legitimate not to expect more than one close event before the window is actually closed. Case in point: fixing KMainWindow and KApplication to restore their KDE4 behavior (I have locally tested Qt and KDE patches to that effect) makes Kate crash on logout. Changing behavior but not API is *worse* than adding API that optionally changes behavior - it silently breaks expectations of existing software. We can, however, implement a workaround in KDE (and then fix our stuff when something breaks): At the end of the slot handling commitDataRequest(), install an event filter on the QGuiApplication, which nicely filters ALL events to everything (TODO: check that - otherwise we'd just install an event filter on all toplevel windows). In that filter, check whether QGuiApplication::isSavingSession() is still true: if so, filter out and ignore() all CloseEvents. If not, have the the filter uninstall and delete itself for performance reasons. If you look at QWidgetPrivate::close_helper(), you see that it always sends a close event to ask windows if they agree to be closed, and they can always refuse. Now which repository should that go in? It would be ugly to copy and paste the necessary code around - it should be roughly ten lines. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #18 from Andreas Hartmetz <ahartm...@gmail.com> --- How should that be done, sending close events and expecting applications to save their state in response, but not close windows or the application? It would mean that applications are session management aware but don't use the session management API and implement a very crude version of session management. A stupid thing to do. I think the only choice here is to break session management in applications that actually support it, or break session management in applications that don't (properly) support it, where it may or may not work semi-accidentally. And let's face it, the only Qt applications that really care about session management and do it correctly are X applications, most of which are KDE applications. Something tells me that those are going to be fine. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #16 from Andreas Hartmetz <ahartm...@gmail.com> --- The session manager getting an OK means asking the client and at this point the client can cancel the shutdown, or save its state and wait to get killed. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #14 from Andreas Hartmetz <ahartm...@gmail.com> --- (In reply to Thomas Lübking from comment #13) > Andreas, the Qt patch kills the ability to cancel the logout process (when > the process or user prevents closing a window), I'm not sure it will be > accepted and if, you probably will have caused a feature breakage. See > comment #8. Instead of actually closing, the system likely wants to ask > whether anyone is ok with closing this window (ie. cause close events w/o > actually closing the window) How session management works is that the application connects to the QGuiApplication::saveStateRequest() signal. When that signal arrives, the application either saves its state or calls QSessionManager::cancel() on the instance passed in the signal. Session management never works by just trying to close windows without telling the application that it was triggered by session management. In the absence of any proper mechanism, one *could* do it that way, but it's a bad idea because relevant information and actions are not available to the application that way. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354724] missing some clients or windows when storeSession and performLegacySessionSave
https://bugs.kde.org/show_bug.cgi?id=354724 --- Comment #11 from Andreas Hartmetz <ahartm...@gmail.com> --- Note: sub-session support in the session manager is basically support for activities. Session restore of activities has never worked well enough to be useful for me. -- You are receiving this mail because: You are watching all bug changes.
