[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #20 from Brian Kaye --- I agree that there are situations where keeping old session configs might be useful. I suggest there should be some option to decide how many to retain including all of them an give the use the option of which one to activate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 Brian Kaye changed: What|Removed |Added Version|5.24.0 |5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #18 from Brian Kaye --- The problem persists in Fedora 39 with plasma-desktop-5.27.9-1.fc39.x86_64. I have 781 files in .config/session. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Brian Kaye changed: What|Removed |Added Version|23.04.1 |23.04.2 --- Comment #8 from Brian Kaye --- (In reply to Stephan Kulow from comment #7) > Does the version say v23.04.3? No. It says 23.04.2. How do I tell which version of the solver is in it. Or do I have to wait for fedora to pick it up or somehow encourage them to do so? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Brian Kaye changed: What|Removed |Added Platform|Gentoo Packages |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Brian Kaye changed: What|Removed |Added Resolution|FIXED |--- Platform|Other |Gentoo Packages Status|RESOLVED|REOPENED --- Comment #6 from Brian Kaye --- The fedora rpms do not seem to have picked up the change to fix this problem. How do I verify which solver version is being used? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 --- Comment #1 from Brian Kaye --- If you start the golf game after starting kpat, the solver seems to work correctly. If however you start the golf game after running another of the kpat games, the solver does not work. It continually reports that it cannot determine if the game is winnable. You an ask for a re-deal but the response from the solver is always the same. All other games that I tried all seem to work with the solver. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 470166] New: Solver does not work with golf
https://bugs.kde.org/show_bug.cgi?id=470166 Bug ID: 470166 Summary: Solver does not work with golf Classification: Applications Product: kpat Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: solver Assignee: co...@kde.org Reporter: b...@unb.ca CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Solver does not work when running golf. STEPS TO REPRODUCE 1. Run golf game with solver enabled. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #17 from Brian Kaye --- Upon further reflection, I wondered it if someone might want to migrate back to an old session for whatever reason. The system could optionally keep a certain number of old session information and the user could be presented with an option of which one to restore. Perhaps a timer to use the last session configuration like grub2 does on boot and an option to keep old session or not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #16 from Brian Kaye --- I did update to Fedora 38 yesterday. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #15 from Brian Kaye --- I did a restart twice and files were retained for twice for systemsettings, kcalc, dolphin, several console sessions, and kpat. These are the ones that were open at the time so I am not sure what other commands are affected. I can understand that it would be wise to keep one copy in case of a system crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 --- Comment #14 from Brian Kaye --- I have not deleted files in .config/session for some time. It appears that instances for some files have disappeared. The only one that continues to be added if for systemsettings. I will delete all the files in .config/session today and see what happens. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 351402] On session restore, all windows are placed on first virtual desktop
https://bugs.kde.org/show_bug.cgi?id=351402 Brian Kaye changed: What|Removed |Added CC|b...@unb.ca | -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 Brian Kaye changed: What|Removed |Added CC|b...@unb.ca | -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #9 from Brian Kaye --- Tried the attached game several times. No crash or quit after selecting klondik any of those times. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #6 from Brian Kaye --- Mine is version 22.12.3 on fedora 37. The failure for me now is only switching after a successful win on golf to a new game on klondike. It does not seem to eever fail with another game sequence. Sometime it doesn't fail which I suspect will make finding a solution difficult. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 Brian Kaye changed: What|Removed |Added CC||b...@unb.ca -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #8 from Brian Kaye --- Created attachment 157343 --> https://bugs.kde.org/attachment.cgi?id=157343=edit New crash information added by DrKonqi kpat (22.12.3) using Qt 5.15.8 Kpatience Version 22.12.3 fedora 37 . Successfully wond Golf game and waited 2 minutes. When I picked klondike it crashed. -- Backtrace (Reduced): #4 MemoryManager::new_from_block (s=48, this=0x56498917e670) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/memory.cpp:156 #5 Solver<9ul>::pack_position (this=0x56498add54b0) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:217 #6 Solver<9ul>::insert (node=0x7ffe2949f940, d=0, cluster=, this=0x56498add54b0) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:887 #7 Solver<9ul>::new_position (this=this@entry=0x56498add54b0, parent=parent@entry=0x0, m=m@entry=0x7ffe2949f990) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:919 #8 0x5649872cfbbe in Solver<9ul>::doit (this=0x56498add54b0) at /usr/src/debug/kpat-22.12.3-1.fc37.x86_64/src/patsolve/patsolve.cpp:505 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 Brian Kaye changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #4 from Brian Kaye --- kpat killed by SIGSEGV. The program now quits switching between golf and patience. Some time it just quits and sometime it quits with a chance of reporting or restarting -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #7 from Brian Kaye --- (In reply to Stephan Kulow from comment #6) > Yep, as I expected. I remove the old code, so it won't crash on you anymore. > You won't have a solver either, but that's a bug worthy to report to fedora. I would prefer to have the solver there even if it crashes occasionally. What can I do to help? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #5 from Brian Kaye --- ldd /usr/bin/kpat|grep blackhole generates null output -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #4 from Brian Kaye --- (In reply to Brian Kaye from comment #2) > (In reply to Stephan Kulow from comment #1) > > This is the old solver running that was massakred and is no longer tested > > due to most using blackhole solver. I'll remove it > > How does one determine which solver is being used. The problem persists. The > problem only occurs when switching between golf and klonike. I switch > Freecell>Golf>Kondike>Grandfather'sClock>.>Spider. Then reverse.The > problem does not occur in the reverse direction The version I am running is 22.12.2 from a Fedora RPM -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 --- Comment #2 from Brian Kaye --- (In reply to Stephan Kulow from comment #1) > This is the old solver running that was massakred and is no longer tested > due to most using blackhole solver. I'll remove it How does one determine which solver is being used. The problem persists. The problem only occurs when switching between golf and klonike. I switch Freecell>Golf>Kondike>Grandfather'sClock>.>Spider. Then reverse.The problem does not occur in the reverse direction -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 397817] kpat crash when switching games
https://bugs.kde.org/show_bug.cgi?id=397817 --- Comment #25 from Brian Kaye --- On Fedora the latest supplied is kpat-22.04.1-1.fc36.x86_64 and the problem does occur in that version. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 397817] kpat crash when switching games
https://bugs.kde.org/show_bug.cgi?id=397817 Brian Kaye changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 456934] New: Kpat crashes while switching games
https://bugs.kde.org/show_bug.cgi?id=456934 Bug ID: 456934 Summary: Kpat crashes while switching games Product: kpat Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: b...@unb.ca CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (22.04.1) Qt Version: 5.15.3 Frameworks Version: 5.96.0 Operating System: Linux 5.18.11-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.3 [KCrashBackend] -- Information about the crash: Switching games after golf game success causes crash. Does not occur every time. The crash can be reproduced sometimes. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault [KCrash Handler] #4 MemoryManager::new_from_block (s=48, this=0x55cf9cffac30) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/memory.cpp:157 #5 Solver<9ul>::pack_position (this=0x55cf9e67b190) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:217 #6 Solver<9ul>::insert (node=0x7ffdfa218ee0, d=0, cluster=, this=0x55cf9e67b190) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:887 #7 Solver<9ul>::new_position (this=this@entry=0x55cf9e67b190, parent=parent@entry=0x0, m=m@entry=0x7ffdfa218f30) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:919 #8 0x55cf9bea7c2e in Solver<9ul>::doit (this=0x55cf9e67b190) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:505 #9 Solver<9ul>::patsolve (this=0x55cf9e67b190, _max_positions=) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/patsolve/patsolve.cpp:800 #10 0x55cf9be81c33 in DealerScene::isGameLost (this=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1844 #11 DealerScene::isGameLost (this=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1727 #12 0x55cf9be874ba in DealerScene::takeState (this=this@entry=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1331 #13 0x55cf9be89739 in DealerScene::animationDone (this=0x55cf9d1cc200) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/dealer.cpp:1546 #14 0x7f8ca8cdac36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f8ca8cdac36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #16 0x7f8ca8cdac36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #17 0x7f8ca8cddfce in QTimer::timeout(QTimer::QPrivateSignal) () from /lib64/libQt5Core.so.5 #18 0x7f8ca8cd1525 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f8ca99aec82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f8ca8ca7658 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f8ca8cf7681 in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #22 0x7f8ca8cf7fa4 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #23 0x7f8ca6926faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f8ca697c2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #25 0x7f8ca6924940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f8ca8cf82fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f8ca8ca60ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f8ca8cae162 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x55cf9be77596 in main (argc=, argv=) at /usr/src/debug/kpat-22.04.1-1.fc36.x86_64/src/main.cpp:353 [Inferior 1 (process 373529) detached] The reporter indicates this bug may be a duplicate of or related to bug 397817. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 --- Comment #7 from Brian Kaye --- I use the X11 version and it now seems to work properly. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #106 from Brian Kaye --- Hopefully my last comment. Deleted all files in .config/session and started apps one at a time. All old files controlled by ksmserverrc were deleted at each logout/login. So no bug. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #105 from Brian Kaye --- Ran kwriteconfig5 --file startkderc --group General --key systemdBoot true and installed "plasma-workspace-common-5.25.2-1.fc36.x86_64" and associated packages on my Fedora 36 system. Had to try a number of times before it worked though. Seems to work correctly now. But still does not remove the old files in .config/session. Probably a different bug. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 --- Comment #5 from Brian Kaye --- (In reply to kde.org from comment #4) > Now that David fixed https://bugs.kde.org/show_bug.cgi?id=442380, can you > still reproduce the issue with KDE Plasma 5.25.2, or can we close this one > as well? As soon as the distros pick it up and we can veryify. As of this post Fedora has not so it is hard to test. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #104 from Brian Kaye --- I ran the command "kwriteconfig5 --file startkderc --group General --key systemdBoot false" which seemed to correct the problem. The file .config/startkderc was changed(or created) . The file "/etc/xdg/startkderc" still shows "systemdBoot=true". Once the distros pick this change up (fedora has not as of this post) we will have to delete .config/startkderc or run the command "kwriteconfig5 --file startkderc --group General --key systemdBoot true" . This should be done before the fixed package is installed to verify that the new package fixes the problem. Sure wish fedora would hurry up so we can put this issue to bed. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #103 from Brian Kaye --- (In reply to David Edmundson from comment #102) > >Need to get the various distros to pick this up and then turn systemd boot > >back on. > > Who's turned it off? > > >Is the retention of files in .config/session fixed as well or is it a > >separate bug > > Unrelated to this. I have turned it off as a result of a comment on this bug report.. I wonder if the race condition has created the situation where the files are not deleted in .config/session. Once the distros pick up the change we will see if the deletion is still necessary. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] With systemd boot, session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #101 from Brian Kaye --- Need to get the various distros to pick this up and then turn systemd boot back on. Is the retention of files in .config/session fixed as well or is it a separate bug. Still would like to know the what the contents of the .config/session and .config/ksmserverrc files mean. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #86 from Brian Kaye --- (In reply to Nicolas Pomarede from comment #85) > (In reply to Kishore Gopalakrishnan from comment #70) > > Can someone confirm if disabling Plasma's systemd-based startup fixes the > > issue? To disable it, run > > kwriteconfig5 --file startkderc --group General --key systemdBoot false > > in a terminal and reboot. > > At least for me, session restore seems to work perfectly (remembers which > > virtual desktops and activities windows were on) on X11 when this is > > disabled. > Thanks for this, it fixed my restore issue on my laptop PC. After several > reboots, windows are correctly restored on their respective virtual desktop. > But I have mixed results that might match what other reported : I have 2 PC > with exact same packages (Mageia 9 dev version), 1 laptop and 1 "normal" pc. > On the laptop, session restoring is working again after disabling systemd > for kde, but on the other PC session is still not correctly restored (using > the same apps (konsole, kwrite, kate) than on the laptop). > > So, this really looks like some kind of race condition to me ; starting kde > from systemd seems to start components in the wrong order or not waiting > enough to ensure each component had enough time to start fully and handle > session restoring for example. > On my other PC it still doesn't work as if even when kde starts each > component itself (not with systemd) then some parts are not ready to handle > session restoring. > > In the end, we see that code for restoring session is still working in > recent KDE/Plasme, in the sense that session is saved and can be loaded > later on next login, but it seems to me that the process that try to restore > the session happens too soon / at the wrong time when kde/plasma is not > ready yet. I agree. See my comment 29. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #84 from Brian Kaye --- Firefox always seemed to restore to the correct desktop(s). But without testing every application its hard to tell if all other applications exhibit the incorrect behaviour. Firefox may be aware of its desktop configuration when it shuts down. It is certainly aware of which windows it has open. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #78 from Brian Kaye --- On my fedora system there is a file dolphin_dolphin_dolphin in .config/session which seems to be the configuration of dolphin when it is started after being closed. There are other files dolphin_* which has the configuration of each dolphin window after a session restart -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #75 from Brian Kaye --- Is it enabled by default? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #73 from Brian Kaye --- For me I had two dolphin windows opened on desktop 4 and hey were restored in correct locations and with correct correct sizes. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #72 from Brian Kaye --- Seems to bypass the problem. After two logout/login and two reboots everything works properly. I am on Fedora 36 but running a fedora 35 kernel (kernel-core-5.17.8-200.fc35.x86_64). How did you come by this solution? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #66 from Brian Kaye --- The problem persists in Fedora 36 with plasma-workspace-5.24.3-3.fc36.x86_64. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 408433] Amount of files in session folder increases after every restoring of session
https://bugs.kde.org/show_bug.cgi?id=408433 Brian Kaye changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||b...@unb.ca Ever confirmed|0 |1 --- Comment #12 from Brian Kaye --- I have had this issue for some time on Fedora. The file .config/ksmserverrc seems to have entries for commands that indicate that old session files should be deleted. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #60 from Brian Kaye --- I downloaded various versions of Fedora KDE Live ISOs and tried them looking for this bug: Version | Size of ksmserver | Version | Bug F31 | 16568 | 0.4 | No F33 | 175592| 0.4 | Could not logout/in successfully F34 | 163536| 0.4 | Did not restore any applications F35 | 163288| 0.4 | Yes So running the command "ksmserver --version" is useless for getting the actual version. The size of the programs has changed in different versions so someone has been doing something to it either directly or indirectly. The Fedora 34 case is interesting in that there was a failure in the kde crash handler. The trace back had several references to Wayland. This may be why the F34 case showed a failure. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Brian Kaye changed: What|Removed |Added Version|5.23.3 |5.24.2 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #57 from Brian Kaye --- Downloaded Fedora KDE Live 31 the newest version available for old versions. Created and booted a UDB stick. Created 4 virtual desktops, put an application on each desktop, set the system to restore previous. Logout/login 5 times and all desktops had their previous applications on their correct virtual desktop EVERY time. I did not delete the files in .config/session or the file .ksmserverrc. Running the command "ksmserver --version" returned the value 0.4. However here is an anomaly. When I ran "ls - /usr/ksmserver" It showed a size of 16568 bytes as opposed to the size of 163288 bytes on my fedora 35 system. This difference made me go back and check. Surprising unless the ls command is different the two releases (31 vs 35). I guess I need to find an old version of Fedora 33. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #56 from Brian Kaye --- My laptop (Lenovo P50) crashed and I fired up an old IBM P42 Thinkpad. It is running Fedora 29 and the bug appears there as well. Don't remember it doing that but it is probbably six or seven years since I fired that laptop up. I ran the command "ksmserver --version" and it returned the exact same version number (0.4) that is running on my Fedora 35 system. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`
https://bugs.kde.org/show_bug.cgi?id=400079 --- Comment #16 from Brian Kaye --- (In reply to Harald Sitter from comment #2) > I wonder, I wonder... maybe we should just dump the dmidecode output in a > text KCM. It'd be fairly cheap to do and maintain that way. > > The other option would be to feed selective data into the about system kcm. > BUT that is probably fairly costly from a code POV since we need a whole > bunch of heuristics to determine if a given field is indeed useful (e.g. on > any device that isn't from one of the big computer OEMs any number of the > fields may not be filled which usually means they are filled with > placeholder garbage that we need to manually filter out). Smaller ODMs in > particular also fail to fill fields properly at times. > > e.g. my system is custom built so I have > > System Information > Manufacturer: System manufacturer > Product Name: System Product Name > Version: System Version > Serial Number: System Serial Number > Wake-up Type: Power Switch > SKU Number: SKU > Family: To be filled by O.E.M. Harald :In your case where you have a custom build, you probably don't need the smbios information. But it does raise the issue of custom bios where you might like to put your custom info into the bios. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`
https://bugs.kde.org/show_bug.cgi?id=400079 --- Comment #15 from Brian Kaye --- (In reply to Nate Graham from comment #3) > Could we just dump the output of `dmidecode | grep -A9 '^System > Information'` into the current About This System KCM? I suppose we would > need to do some parsing to separate the labels from the data and stick it > into a Formlayout properly, yeah. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #55 from Brian Kaye --- But if I delete the files in .config/session and the file .config/ksmserverrc, t seems to work correctly at most once after one logout/login. There appears to be another less serious bug in this. Even though the file .config/ksmserverrc includes what appears to be delete commands for the files in .config/session for individual applications. These delete commands don't seem to work and after a while there are a lot of old files in .config/session. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #53 from Brian Kaye --- (In reply to Nicolas Pomarede from comment #52) > (In reply to Brian Kaye from comment #48) > > I think we need a kde developer to get involved, but they seem to be quiet > > on this bug. > > same for me, I have the feeling that since it's a known thing that session > restore doesn't work properly with wayland, then no one pay attention to > this bug. > but it has nothing to do with wayland, it's plain X11 that used to work for > years (well, maybe some commits to fix wayland broke the X11 case, can't > really say), if I get some spare time I could try to look at the ksmserver > commits before plasma 5.21 was released. > anyway, for me it's major regression since several months / releases, it's > sad no one among KDE dev is noticing this ... Surely at some point in the development process someone on the development team has a test program to verify the contents of .config/session and .config/ksmserverrc. Such a program would help to determine whether its is a session save or session restore problem. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #51 from Brian Kaye --- Try running the kdebugsettings from a Konsole window. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #49 from Brian Kaye --- You can pick the ksmserver messages in the journal since the last boot with the command "journalctl -b --grep=ksmserver" -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #48 from Brian Kaye --- What I did was run kdebugsettings command. I turned off all the things to trace except ksmserver. Lots more messages appeared in the system journal after a logout/login. Not sure what they all mean. I am not a kde developer by any way. Don't even know much C++. So I will look for messages where something fails. My quick look suggested that ksmserver was starting/stopping more than just the applications I had open on the various virtual desktops (4 in my case). I think we need a kde developer to get involved, but they seem to be quiet on this bug. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #46 from Brian Kaye --- On Fedora the package "kdebugsettings" seems to be able to get ksmserver (or qt?) to send trace messages to the system journal. The seetings seem to persist over logout/login and/or reboot. Need to do some controlled tests -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #45 from Brian Kaye --- Not sure if it has any effect but perhaps if all who are on this bug list should vote for it. At the moment I am the only one who has. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #44 from Brian Kaye --- The other file involved is .config/ksmserverrc. After deleting the files in .config/session and logging out you should see entries in the journal (journalctl -b) where ksmserver fails to delete the files in .config/session because they don't exist any more. For your own edification you might try some controlled tests with a small number of virtual desktops and 1 application in a desktop other than 1. As far as I can tell we have had no response from the developers. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 421870] windows on wrong desktop after session restore on Wayland
https://bugs.kde.org/show_bug.cgi?id=421870 Brian Kaye changed: What|Removed |Added CC||b...@unb.ca --- Comment #3 from Brian Kaye --- More discussion in bug 442380 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #41 from Brian Kaye --- Have you tried this? If the bug appears with this method then the bug is more pervasive than the number who have responded to this bug report. It might be a worthwhile test to use plasma-wayland instead of X11. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #39 from Brian Kaye --- My previous comment does not apply to the file "dolphin_dolphin_dolphin" The file seems to be used to define the configuration of dolphin when a new dolphin window is opened to look like the one that was last closed( settings related). -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #38 from Brian Kaye --- Based on the contents of the .config/ksmserverrc file it looks like the previous versions of files in .config/session should be deleted at login because there is a "rm" command in the ksmserverrc file. "discardCommand2[$e]=rm,$HOME/.config/session/systemsettings_106d61727300016434896860036930008_1643493938_600324 But the audit trace shows that the file deletion fails. So perhaps that is why there seems to be a buildup of old files in .config/session. Maybe it is a separate bug. If we could find someone who has the file buildup problem but not the session restore problem (this bug) it would tell us its a separate problem. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #36 from Brian Kaye --- The issue with the dolphin restarts may have something with the dolphin_dolphin_dolphin file in .config/session. That file seems to be updated when dolphin is closed and started again. It may be a separate but related issue if multiple dolphin windows are restarted at incorrect size(s). I have noted in the past that Firefox is restarted in the correct window. Since I don't use it often ( I use waterfox) , I did not notice if it was the correct size. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #35 from Brian Kaye --- So its not just a Fedora issue. If you create a new user with some virtual desktops does the problem persist? Just add the virtual desktops , start an app in virtual desktop 2 and logoff/logon a couple of times. Like you it just seemed to stop working and I didn't really note when it started. I am increasingly frustrated at the lack of any acknowledgement from the KDE folks. I have contemplated switching away from KDE -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #33 from Brian Kaye --- I did report this problem on the Fedora bug list <https://bugzilla.redhat.com/show_bug.cgi?id=1956916> on 2021-05-04. It might help if the people who have this problem tell us which distribution they are using. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #32 from Brian Kaye --- What linux distribution are you using? How many virtual desktops. I have found that deleting the .config/session files sometime corrects the problem for one or several login/logouts or not at all. Dolphin also adds an entry "dolphin_dolphin_dolphin" in .config/session when a dolphin window is closed. It seems to be used when dolphin is restarted. The question still remains is why more people are not having this problem. According to the bug report this problem is assigned to "David Edmunson" . Sure wish we could get some suggestions from him. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #30 from Brian Kaye --- Forgot to mention the "-p war" parameter on the auditctl command -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #29 from Brian Kaye --- Wondered what programs were accessing .config/session files. 1. added audit rule with auditctl -w /home/**/.config/session -K SESSION 2. restarted the auditd daemon 3. started applications in a couple of desktops 4. emptied /var/log/audit/audit.log 5. cleared files in .config/session 6. logout/login 7. windows did not open in correct desktops 8 . in a konsole window ran ausearch -k SESSION --format text There are a number of applications which are involved, kwin_x11, systemsettings5, konsole (looking at konsole files in.config/session More confused. Woder if its some sort of race condition. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #28 from Brian Kaye --- Files are added to .config/session every time you logout or restart except 'kwin_saved at previous logout_'. which appears to be replaced. There seems to be another file involved .config/ksmserverrc. This file has the same timestamp as the 'kwin_saved at previous logout_' and there are references to the files in .config/session. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #26 from Brian Kaye --- Just ran another set of simple tests with empty ~/.config/session. 1. empty session (nothing open except applets in bottom panel) then logout/login. 2. opened konsole session on desktop 2 ( of 4) 3. after logout/login konsole session ended up in desktop 2 as expected 4. immediate logout/login konsole session ended up in desktop 1 I repeated this test a couple of times with the same result If possible could someone repeat this test. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #24 from Brian Kaye --- Am having a quick look at <https://develop.kde.org/docs/session-managment/> -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #22 from Brian Kaye --- if you do a strings command on /usr/bin/startplasma-x-11 you find a reference to startplasma-x11-5.23.4-1.fc35.x86_64.debug but I can't find it. That might have something relevant -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #18 from Brian Kaye --- Problem persists in Fedora 35. System seems to keep older versions of the application files in .config/session. What surprises me is that more people are not complaining about this problem. That suggests that the problem is related to something in my setup. It occurs even if I create a new user. I really need to know what the configuration files .config/session mean. I suspect one of the developers has a test program to read those files and verify what they should do. If the files are correct then the restore process is at fault. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #16 from Brian Kaye --- Do the logout/login twice and check after each. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #15 from Brian Kaye --- Try deleting the files in .config/session and then logout/login. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 --- Comment #13 from Brian Kaye --- Always seems to fail now even if I delete files in .config/session -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 408708] Excessive cpu and memory usage
https://bugs.kde.org/show_bug.cgi?id=408708 --- Comment #6 from Brian Kaye --- This problem no longer exists as far as I can tell on my Fedora 35 system. Have not noticed it for a couple or releases. Using kpat-21.04.3-1.fc35.x86_64 Did not know you could run this on Windows. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Brian Kaye changed: What|Removed |Added Version|5.22.4 |5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Brian Kaye changed: What|Removed |Added CC||b...@unb.ca --- Comment #11 from Brian Kaye --- Just upgraded from Fedora 34 to Fedora 35. Plasma 5.23.3 for Fedora 35 installed. Had to reboot to pick up new kernel. The first boot seem to restore the applications to the proper virtual desktop. In subsequent logout/login the old behaviour appeared. Deleted all the files in .config/session/ and after a logout/login the correct behaviour appeared but a subsequent logout/login showed the incorrect behaviour. Repeated several times with the same result. I did absolutely nothing between the first and second logout/login sequences. Since I made no other changes, either the session save process messes up the files in .config/session or the restore process is unable to work with the new files. I assume that whoever is working on this has some way to verify the .config/session files. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`
https://bugs.kde.org/show_bug.cgi?id=400079 --- Comment #10 from Brian Kaye --- On my system (Lenovo P50 laptop running Fedora 34) the script below will show whether of not the AC adapter is connected. Not a lot of use if used on a desktop. Would be nice to see if it works on other distros. Another source for battery information can be found in "/sys/class/power_supply/BAT0" if (( $(
[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`
https://bugs.kde.org/show_bug.cgi?id=400079
--- Comment #9 from Brian Kaye ---
On my system (Fedora 34) the directory " /sys/devices/virtual/dmi/id" contains
much of the system information that might be displayed in kinfocenter. Some
items like the serial number need authorization. The little script below
displays the contents. Some info is probably not useful. Other systems my have
the info in different locations. So maybe there is no need to run the dmidecode
command. There is a "power" subdirectory but I am not sure of the contents yet.
DIR="/sys/devices/virtual/dmi/id/*"
for i in ${DIR}; do if ! [ -d $i ]; then echo -ne ${i} "\t"; cat ${i}; fi;
done
--
You are receiving this mail because:
You are watching all bug changes.
[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`
https://bugs.kde.org/show_bug.cgi?id=400079 --- Comment #8 from Brian Kaye --- In addition to the dmidecode stuff it would be nice to have some basic power supply/battery information -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`
https://bugs.kde.org/show_bug.cgi?id=400079 --- Comment #7 from Brian Kaye --- Harald The image for what it looks on your system shows up as a blank darg image. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`
https://bugs.kde.org/show_bug.cgi?id=400079 Brian Kaye changed: What|Removed |Added CC||b...@unb.ca --- Comment #6 from Brian Kaye --- At one time or other I have needed most of the info from dmidecode. Wrote a script to produce the following -- System Information Type s bios-vendor LENOVO bios-versionN1EET91W (1.64 ) bios-release-date 05/12/2021 bios-revision 1.64 firmware-revision 1.18 system-manufacturer LENOVO system-product-name 20ENCTO1WW system-version ThinkPad P50 system-serial-numberPC0DTF1L system-uuid 423e074c-20a8-11b2-a85c-b8c832f25d1c system-family ThinkPad P50 baseboard-manufacturer LENOVO baseboard-product-name 20ENCTO1WW baseboard-version SDK0J40697 WIN baseboard-serial-number L1HF661007G baseboard-asset-tag Not Available chassis-manufacturerLENOVO chassis-typeNotebook chassis-version None chassis-serial-number PC0DTF1L chassis-asset-tag No Asset Information processor-familyCore i7 processor-manufacturer Intel(R) Corporation processor-version Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz processor-frequency 2700 MHz -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 351402] On session restore, all windows are placed on first virtual desktop
https://bugs.kde.org/show_bug.cgi?id=351402 Brian Kaye changed: What|Removed |Added CC||b...@unb.ca --- Comment #3 from Brian Kaye --- See <https://bugzilla.redhat.com/show_bug.cgi?id=1956916> for some further information of this issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390295] The active virtual desktop is no longer remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=390295 --- Comment #14 from Brian Kaye --- Won't be switching to wayland real soon. Here are the tests I ran. 1. Configured in X firefox in desktop 3 and Konsole in desktop 4. Restart with X put Konsole in desktop 1 and firefox in proper desktop. 2. Configured as in 1. and restarted in wayland. Same problem but everything slower to start. 3. Configured in wayland as in 1. Restarted in wayland. Different problem. The Konsole application did not restart. Desktop icons took a long time to show up. 4. Configured in wayland as in 1. Restarted in X. Different problem. The Konsole application did not show up. Took long time (~ 20 seconds) for desktop icons to show up. Login was slow. Have not tried a second login yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390295] The active virtual desktop is no longer remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=390295
--- Comment #12 from Brian Kaye ---
In addition to my previous comment here is the description file in
~/.config/session for the kconsole application (open in Desktop 3 before
restart and Desktop 1 after restart:
[1]
Active=0
Tabs=[{"Orientation":"Horizontal","Widgets":[{"SessionRestoreId":1}]}]
[Number]
NumberOfSessions=1
NumberOfWindows=1
[Session1]
Encoding=UTF-8
LocalTab=%d : %n
Profile[$e]=$HOME/.local/share/konsole/Profile 1.profile
RemoteTab=(%u) %H
SessionGuid={dfe91696-4acf-4b94-a43b-d4ebdebe9794}
TabColor=
WorkingDir[$e]=$HOME/.config/session
[WindowProperties1]
ClassName=Konsole::MainWindow
ObjectName=MainWindow#1
RestorePositionForNextInstance=false
State=/wD9BcwAAAT0BAQICPwBAgIWAG0AYQBpAG4AVABvAG8AbABCAGEAcgEA/wAAHABzAGUAcwBzAGkAbwBuAFQAbwBvAGwAYgBhAHIBAAAC7/8AAA==
StatusBar=Disabled
ToolBarsMovable=Disabled
eDP1 Height 3072x1728=1383
eDP1 Width 3072x1728=1484
eDP1 XPosition 3072x1728=0
eDP1 YPosition 3072x1728=49
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 390295] The active virtual desktop is no longer remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=390295 --- Comment #11 from Brian Kaye --- I simplified my desktops by only having 1 Konsole application open in Desktop 3 (2x2 configuration). Upon restart the Konsole session was opened in Desktop 1. here is the session file for the session: [Session] active=3 activities1= activities2= activities3=726fb687-7df6-4007-a702-d1d5e4496a90 count=3 desktop=3 desktop1=-1 desktop2=-1 desktop3=3 fsrestore1=0,0,0,0 fsrestore2=0,0,0,0 fsrestore3=0,0,0,0 fullscreen1=0 fullscreen2=0 fullscreen3=0 geometry1=0,0,3840,2160 geometry2=0,2088,3840,72 geometry3=0,61,1855,1729 iconified1=false iconified2=false iconified3=false keepBelow1=true keepBelow2=false keepBelow3=false maximize1=0 maximize2=0 maximize3=0 opacity1=1 opacity2=1 opacity3=1 resourceClass1=plasmashell resourceClass2=plasmashell resourceClass3=konsole resourceName1=plasmashell resourceName2=plasmashell resourceName3=konsole restore1=0,0,3840,2160 restore2=0,2088,3840,72 restore3=0,0,1855,1790 sessionId1=106d6172730001625868926002810 sessionId2=106d6172730001625868926002810 sessionId3=106d6172730001625868954002817 shaded1=false shaded2=false shaded3=false shortcut1= shortcut2= shortcut3= skipPager1=false skipPager2=false skipPager3=false skipSwitcher1=false skipSwitcher2=false skipSwitcher3=false skipTaskbar1=false skipTaskbar2=false skipTaskbar3=false stackingOrder1=0 stackingOrder2=1 stackingOrder3=2 staysOnTop1=false staysOnTop2=false staysOnTop3=false sticky1=true sticky2=true sticky3=false userNoBorder1=true userNoBorder2=true userNoBorder3=false windowRole1= windowRole2= windowRole3=MainWindow#1 windowType1=Desktop windowType2=Dock windowType3=Normal wmCommand1= wmCommand2= wmCommand3= -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390295] The active virtual desktop is no longer remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=390295 Brian Kaye changed: What|Removed |Added CC||b...@unb.ca --- Comment #10 from Brian Kaye --- I have this problem on fedora 34 with all the latest patches(.plasma-desktop-5.22.2.1-1.fc34.x86_6). Most applications are restored to the first virtual desktop. I have a 2x2 virtual desktop grid. The only application that seems to be restored to the proper virtual desktop is Firefox which I only run occasionally(Waterfox mostly). I created a new user, created a 2x2 virtual desktop grid and the problem occurred. So its not something peculiar to my user configuration. I did report this through the Fedora Bugzilla. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] New: kapatience crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 Bug ID: 439420 Summary: kapatience crash when switching games Product: kpat Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: b...@unb.ca CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.13-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.2 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed:Finished successful Freecell game and selected new game Golf The crash can be reproduced sometimes. -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault [KCrash Handler] #4 0x7ff82188ceea in KSharedDataCache::find(QString const&, QByteArray*) const () from /lib64/libKF5CoreAddons.so.5 #5 0x7ff821c5400f in KAbstractCardDeck::cardPixmap(unsigned int, bool) () from /lib64/libkcardgame.so #6 0x7ff821c5442e in KCard::paint(QPainter*, QStyleOptionGraphicsItem const*, QWidget*) () from /lib64/libkcardgame.so #7 0x7ff821480263 in QGraphicsScenePrivate::draw(QGraphicsItem*, QPainter*, QTransform const*, QTransform const*, QRegion*, QWidget*, double, QTransform const*, bool, bool) () from /lib64/libQt5Widgets.so.5 #8 0x7ff821481223 in QGraphicsScenePrivate::drawSubtreeRecursive(QGraphicsItem*, QPainter*, QTransform const*, QRegion*, QWidget*, double, QTransform const*) () from /lib64/libQt5Widgets.so.5 #9 0x7ff8214818a2 in QGraphicsScenePrivate::drawItems(QPainter*, QTransform const*, QRegion*, QWidget*) () from /lib64/libQt5Widgets.so.5 #10 0x7ff8214a54ff in QGraphicsView::paintEvent(QPaintEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7ff82119585e in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7ff82123ecd2 in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7ff82124214c in QAbstractScrollAreaFilter::eventFilter(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7ff8205fccfd in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7ff821154e62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7ff8205fcf48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7ff82118d93a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib64/libQt5Widgets.so.5 #18 0x7ff82118e4df in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #19 0x7ff82118f493 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #20 0x7ff82118dc12 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #21 0x7ff82118f493 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #22 0x7ff82118f2bf in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #23 0x7ff82118f2bf in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #24 0x7ff82118dc12 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib64/libQt5Widgets.so.5 #25 0x7ff82116561c in QWidgetRepaintManager::paintAndFlush() () from /lib64/libQt5Widgets.so.5 #26 0x7ff821195f8d in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x7ff821bc782d in KXmlGuiWindow::event(QEvent*) () from /lib64/libKF5XmlGui.so.5 #28 0x7ff821154e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #29 0x7ff8205fcf48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #30 0x7ff8205ffc76 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #31 0x7ff821470483 in QGraphicsScenePrivate::_q_emitUpdated() () from /lib64/libQt5Widgets.so.5 #32 0x7ff820624257 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #33 0x7ff821154e73 in QApplicationPrivate::notify_helper(QObject*,
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #17 from Brian Kaye --- The package libblack-hole-solver1l 1.10.1-2.fc34 is installed on my system but the package black-hole-solver is not. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #16 from Brian Kaye --- The game is simple. Most games cannot be won. All you do is play cards from the draw pile and make sequences up or down regardless of suit. be careful for the boundary cards (kings and aces). -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #13 from Brian Kaye --- If you run strings against /usr/bin/kpat you see black_hole_solver_create black_hole_solver_enable_rank_reachability_prune black_hole_solver_enable_wrap_ranks black_hole_solver_enable_place_queens_on_kings black_hole_solver_config_setup black_hole_solver_read_board black_hole_solver_setup black_hole_solver_set_max_iters_limit black_hole_solver_run black_hole_solver_init_solution_moves black_hole_solver_get_next_move black_hole_solver_free -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #11 from Brian Kaye --- I am running Fedora Core 34. Everything up to date for the most part. I run an old version of Firefox( and an up to date one), and an up to date Waterfox. My machine is a Lenovo P50 laptop with 48G of memory, a 4K screen, a 512G Samsung SSD and a 512K hard drive. Using grub2 I multi-boot Fedora with Windows 10, gparted, Kubuntu, and Lenovo Diagnostics which I use rarely. I upgrade from one version of Fedora to another using dnf system-upgrade. The kde packages are up to date as far as the fedora Red Hat distribution is concerned. Where does that error message come from since I do not have the black-hole-solver installed? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #9 from Brian Kaye --- "flatpak list" gives null output as root or normal user. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #7 from Brian Kaye --- I do see that error message when I run from the application menu. It shows up in the system journal as per the initial post. In the case of running from the application menu the error occurs after the first time I run golf. When run from a terminal it fails after the second. I do not remember ever installing the black-hole-solver either with flatpak or dnf. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #5 from Brian Kaye --- The black-hole-solver is not installed on my system. It is available (black-hole-solver.x86_64 1.10.1-2.fc34). So the solver I am using must be built in. Ran from the command line again. First game worked second game number 1661658864 failed. Got the error message "Error reading the board at line No. 2!". This message occurs with every failure. I did a number of undos during this game. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #3 from Brian Kaye --- Tried starting kpat from a Konsole session and running golf game. Played 5 or 6 games winning some. No failure. Then tried starting from the Application Menu and the first game I tried quit as per the bug description. The command that gets run is "kpat -qwindowtitle %c %u". Tried running without the "-qwindowtitle". No change. Tried running in terminal from the Application Menu. It still failed. Tried adding "--gametype golf" to the Application Menu and it did NOT fail the one time I tried it. Tried without "--gametype golf" and ran golf as the first game from the Application Menu and it did NOT fail. But when I tried a second game of golf it DID fail. More confusing still -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 --- Comment #2 from Brian Kaye --- Can't tell game number after kpat quits. Its not just the game that quits, its all of kpat. How do I tell which version of the solver being used? There is no obvious add-on. I have tried once without the solver and it still happened. Maybe it comes in kf5-kcoreaddons.x86_64 version 5.82.0 Another error message when kpat is started: kf.coreaddons: "2365-1307-background" is too large to be cached. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 438779] New: Kpat golf game quits when near end of game
https://bugs.kde.org/show_bug.cgi?id=438779 Bug ID: 438779 Summary: Kpat golf game quits when near end of game Product: kpat Version: unspecified Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: b...@unb.ca CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY When playing the golf game if one is near the end of the game and you can win, kpat quits. STEPS TO REPRODUCE 1. run kpat 2. play golf 3. OBSERVED RESULT kpat quits near end of game that is winnable with a few cards ( 2 or 3) left. EXPECTED RESULT Win game and be able to deal a new game or switch games. This happens with all other games. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.21.5 (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION kpat version:20.12.2 Ran it under gdb. Here are the messages when it quit. [New LWP 257880] [LWP 257880 exited] [New LWP 257881] [LWP 257881 exited] [New LWP 257882] [LWP 257882 exited] Error reading the board at line No. 2! [LWP 257690 exited] [LWP 257689 exited] [LWP 257688 exited] [LWP 257687 exited] [LWP 257686 exited] [LWP 257849 exited] [LWP 257848 exited] [LWP 257847 exited] [LWP 257846 exited] [LWP 257685 exited] [LWP 257681 exited] --Type for more, q to quit, c to continue without paging-- [Inferior 1 (process 257681) exited with code 0377] >From the system journal: Jun 16 19:26:22 mars plasmashell[184261]: Error reading the board at line No. 2! Jun 16 19:26:22 mars systemd[2742]: app-org.kde.kpat-e3642ec25b7d454c90a03a7287f31aac.scope: Deactivated successfully. Jun 16 19:26:22 mars systemd[2742]: app-org.kde.kpat-e3642ec25b7d454c90a03a7287f31aac.scope: Consumed 7min 40.971s CPU time. Jun 16 19:26:22 mars kwin_x11[2840]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 58644, resource id: 71303174, major code: 15 (QueryTree), minor code: 0 Jun 16 19:26:22 mars kwin_x11[2840]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 58688, resource id: 18877072, major code: 18 (ChangeProperty), minor code: 0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 219403] Create calendar pdf output takes hours
https://bugs.kde.org/show_bug.cgi?id=219403 --- Comment #18 from Brian Kaye --- It works under 7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 219403] Create calendar pdf output takes hours
https://bugs.kde.org/show_bug.cgi?id=219403 --- Comment #15 from Brian Kaye --- The plugin creates a calendar quickly on Fedora 32. i only did it for 3 months and it went quickly. Would like to see some way to duplicate the images used without selecting the same one multiple times. The problem can be marked solved. -- You are receiving this mail because: You are watching all bug changes.
