[neon] [Bug 488744] New: Some consoles are missing when using session save under X11 session
https://bugs.kde.org/show_bug.cgi?id=488744 Bug ID: 488744 Summary: Some consoles are missing when using session save under X11 session Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY After Plasma 6.1.0 most problems of Session Safe were gone (cf. Bug 488264) - instead of one special: there are now 4 konsole windows missing after 1st reboot - and differently to problems before there are not shifted to virtual desk 1 (I have 8 virtual desks each with 9 konsole windows - I worked several years with that set under KDE 5 without any problem). Those 4 have been randomly selected - not several on one desktop but each one of the 4 on different desk and different places there - also not to find in taskbar - but just not saved with the session or deleted by some strange condition (? just guessing ?) ... STEPS TO REPRODUCE 1. Update to Plasma 6.1.0 under X11 session - 8 virtual desks each with 9 konsole windows (each with special starting directories using login shells - for completeness - should not have any result on the outcome) 2. Session saved after login - and just initiate reboot 3. Aftert reboot all konsoles are there incl. correct directory - but some are missing OBSERVED RESULT In the regular pattern of 9 konsole windows one can directly see that a few are missing. EXPECTED RESULT Each window present on logout should be present after a reboot (So similar to this old screenshot showing some additionol konsole windows: https://www.jmb-edu.de/images/Typical_Virtual_Desktop_KDE_neon_6_0_3_X11_JMB.png) SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: KDE neon 6.1.0 (available in About System) KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Linux: 6.8.12-060812 (Ubuntu PPA - worked with that kernel before) Mesa: Mesa 24.0.8 (kisak-mesa PPA - worked with that release before) Plattform X11 (but also Wayland, which was totally broken with 6.0.0!) ADDITIONAL INFORMATION CPU: 12 × AMD Ryzen 5 3600 6-Core Processor (Zen 2) Memory: 15,5 GiB of RAM Graphic Card: AMD Radeon RX 5700 XT (RDNA 1 / Navi 10) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488264] Konsole and other programs windows are no longer restored for session save on X11 around update to 6.0.5
https://bugs.kde.org/show_bug.cgi?id=488264 JMB9 changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from JMB9 --- I opened the new Bug 488744 as some konsole windows are just missing after reboot (seems to not be placed on virtual desk 1 or in taskbar) - but all the other problems of session saved introduced with the fixes are now gone with the feature update Plasma 6.1.0. I am happy that I can work now - and this bug should be marked as solved. The one thing still not working with session save is handled with the new bug report 488744. Thanks for all the code parts which got the fixes to come to this state. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some consoles are missing when using session save under X11 session
https://bugs.kde.org/show_bug.cgi?id=488744 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout under Wayland
https://bugs.kde.org/show_bug.cgi?id=483615 --- Comment #9 from JMB9 --- Unfortunalely Wayland session is still not capable of performing session save ... while X11 is now fixed with Plasma 6.1.0 in most situations (see resolved Bug 488264). On the other hand starting programs work under Wayland - no graphics' errors spotted (after the strange partly-dead pixel problem was solved) and working was possible. But session save is important for workstation use ... so currently Wayland is not ready to get ones work done. So in case Wayland should be aimed to become the session default this must be fixed first. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session
https://bugs.kde.org/show_bug.cgi?id=488744 JMB9 changed: What|Removed |Added Summary|Some consoles are missing |Some console windows are |when using session save |missing when using session |under X11 session |save under X11 session -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session
https://bugs.kde.org/show_bug.cgi?id=488744 --- Comment #1 from JMB9 --- After updating to 6.1 a boot missed some windows. Next boot was complete concerning all konsole windows. So I will look at it and if after a week no problem appeared, this bug would be due to the complicated changes and no longer a problem with KDE 6.1.0 and will then gave the status resolved. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session and some window features no longer work (using bar in task bar item collecting open konsole windows)
https://bugs.kde.org/show_bug.cgi?id=488744 JMB9 changed: What|Removed |Added Summary|Some console windows are|Some console windows are |missing when using session |missing when using session |save under X11 session |save under X11 session and ||some window features no ||longer work (using bar in ||task bar item collecting ||open konsole windows) --- Comment #2 from JMB9 --- Ok, now I can definitely confirm that the bug is real. My settings of 72 konsole windows (9 on each virtual desks) will show about each 3 boots a not complete setting (about 1-3 konsole windows not respawned) - while I check the setting before shutdown. So the are not saved or respawned correctly ... Additionally on each desk the is an item collecting all konsole windows and here there is a bar to switch it from left to right - but the bar can (worked before 6.0.5 under X11) not be clicked and swiped to a side ... so some other window management features are also broken. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session and some window features no longer work (using bar in task bar item collecting open konsole windows)
https://bugs.kde.org/show_bug.cgi?id=488744 --- Comment #3 from JMB9 --- So the influx of patches for KDE seems to be strong after 6.1 - without any official release ... Thus the experience can vary. The last reboot caused all konsole windows to lose the last directory path ... which should be regarded as a major bug for workstations (maybe a separate bug). But of cause if the Qt changes / framwork is resonsible, bug fixes could cause temporary loss - so hard to say for any tester. Additionally, one konsole window was just missing (not respawned - which is the topic of this bug report - so definetely valid). So the next step for me will be a bug report to get konsole fully functional to be invoced by scripting (the lack of this is a cear regression ... even though also present in KDE 5). Thus a tester can clearly decide if konsole is the one to blame or something built in save session (storing data and respawning everything according to that data). And a workstation usage would still be possible by scripting all konsole windows on all virtual desks - e.g. as workaround for a broken session save feature. But this bug report is valid for current KDE neon with Plasma 6.1 and all new updates released till now, unfortunately. But it is not that clear/frequently as before - but still not fixed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session and some window features no longer work (using bar in task bar item collecting open konsole windows)
https://bugs.kde.org/show_bug.cgi?id=488744 --- Comment #4 from JMB9 --- After last comment Plasma 6.1.1 was available - I updated and change the directorie to see if there were some improvements; but now no konsole window was respawn - no okular was respowned - the ony program which was respawned was Firefox installed in special directory from Mozillar tar.bz2. So now (maybe only as intermidiate state) save session is destroyed as it was around 6.0.5. I wonder why one should test KDE if developer can never have tested 6.0.0, 6.0.5 or 6.1.1 - totally broken and visible directly when really working. These should have never went on KDE neon User Edition! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session (deleted) and some are restored on thew wrong virtual desk
https://bugs.kde.org/show_bug.cgi?id=488744 JMB9 changed: What|Removed |Added Summary|Some console windows are|Some console windows are |missing when using session |missing when using session |save under X11 session and |save under X11 session |some window features no |(deleted) and some are |longer work (using bar in |restored on thew wrong |task bar item collecting|virtual desk |open konsole windows) | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session (deleted) and some are restored on thew wrong virtual desk
https://bugs.kde.org/show_bug.cgi?id=488744 --- Comment #5 from JMB9 --- The problems are changing form 6.1 to further updates to 6.1.1 - but after 3 devasting patches which ruined the entire session since 6.0, with 6.1.1 now after 2 reboots 6.1.1 it seems to get quite stable for session save: but missing konsole windows or displaced ones are seldom but clearly happening. >From my point of view the code must be prone to bugs so should be checked as a whole - these random annoyances are not easy to trigger - but I am sure it just happens with the latest KDE neon patches - no updates pending as checked right now. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session (deleted) and some are restored on a wrong virtual desk (displaced)
https://bugs.kde.org/show_bug.cgi?id=488744 JMB9 changed: What|Removed |Added Summary|Some console windows are|Some console windows are |missing when using session |missing when using session |save under X11 session |save under X11 session |(deleted) and some are |(deleted) and some are |restored on thew wrong |restored on a wrong virtual |virtual desk|desk (displaced) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session (deleted) and some are restored on a wrong virtual desk (displaced)
https://bugs.kde.org/show_bug.cgi?id=488744 --- Comment #6 from JMB9 --- The ongoing development process is a real burdon. When staring this morning (28,06.2024) repawn works except that all konsole windows lost the directory path (all ~). When logging out, only Firefox respawned - a pattern well known, unfortunately - so Save Session was completely ruined for the 4th time since introduction of Plasma 6.0.0! As all desktop savings were lost I tested Wayland - no Save Session at all. So this is stable - in a broken way ... But there were new KDE updates emerging and it looks like Save Session may work again. So this bug report may get updated again when I tested this version for some time without new devastating KDE updates in the meantime ... I hope the development process it not AI based ... but this would explain a lot ... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session (deleted) and some are restored on a wrong virtual desk (displaced)
https://bugs.kde.org/show_bug.cgi?id=488744 --- Comment #7 from JMB9 --- Today the session saved was just firefox - again - so the current 6.1.1 Save Session under X11 it totally broken - and the one under Wayland was never exitisting since 6.0.0 ... so no professional wirkflow possible with KDE neon 6.1.1. Thus the error report for this bug (tested to be still existing) is no longer really testable as everything is - again ... destroyed. And the same pattern as around 6.0.4 - konsole windows lose direcectory, after a reboot no konsole or okular window etc. is respawned. I am still reflecting why Firefox is the only program still respawned ... And why the developers build in the same error patterns again and again and can not keep the status of of working desktop environment ... a pletora of bugs - ok - but one should at least test for bugs which return - this should be in the developers interest ... But I think testers / bug report are no longer taken seriously ... would really like to have PM with a developer to understand why all this happens again - and again - and again - and no one listens ... just sad. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488264] New: Konsole windows and other applications no longer are restored for session save on X11 around update to 6.0.5
https://bugs.kde.org/show_bug.cgi?id=488264 Bug ID: 488264 Summary: Konsole windows and other applications no longer are restored for session save on X11 around update to 6.0.5 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The last few days I remarked vanishing konsole windows from virtual desks 2-8 by chance which were all put to virtual desk 1 ... the shrinking of konsole windows still happened (more slowly and in a random fashion - but it was not just gaps between adjacent windows), then suddenly the konsole (all using login shell) directories were all reset to "~" ... and thereafter no program was respawned after reboot - not even on virtual desk 1. So storing sizes/positions/state of programs and restoring that situation after reboot was completely broken in 3 steps - and the shrinking of konsole windows was more random and happen slowly - but this bug still exists. So with 6.0.5 nothing was fixed but all got a total mess without function. And the 'divide et impera' bug management was not a good idea (diciding shrinking and displacer etc.). Currently, Wayland and X11 are the same - nothing can be "stored on logout and restored on boot" - so session saving is no longer available with KDE neon after bug fixing ... and the next version 6.1 is announced as feature update ... I am shocked that bugs so easily to see were not spotted in tests but rolled out. And the worsening in several steps should imply that the entire code should be looked through to really fix this manyfold broken code. Thus Wayland broken and X11 annoying was a normal bug - now I can not work (my workflow requires a lot of windows [alone more than 72 windows for konsole alone plus lots of windows with okular etc.] on special places for 8 virtual desks which worked perfektly with KDE5) and thus it is major for me and should regarded that way by developers if KDE should be used on workstations ... STEPS TO REPRODUCE 1. updating KDE neon 6.0.5 after 07.06.2024 2. opening several windows and selecting session save on logout 3. rebooting ... :( OBSERVED RESULT The entire session is lost - nothing is restored (no Firefox, Thunderbird, konsole, okular ...). EXPECTED RESULT Session is properly restored with exact sizes/positions/states as it was when logging off SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon (User Edition - fully updated - no pakage problems noted) (available in About this System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Linux: 6.8.12-060812 (Ubuntu PPA - worked with that kernel before) Mesa: Mesa 24.0.8 (kisak-mesa PPA - worked with that release before) Plattform X11 (but also Wayland, which was totally broken with 6.0.0!) ADDITIONAL INFORMATION CPU: 12 × AMD Ryzen 5 3600 6-Core Processor (Zen 2) Memory: 15,5 GiB of RAM Graphic Card: AMD Radeon RX 5700 XT (RDNA 1 / Navi 10) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488264] Konsole windows and other applications no longer are restored for session save on X11 around update to 6.0.5
https://bugs.kde.org/show_bug.cgi?id=488264 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net --- Comment #1 from JMB9 --- Just as additional info: I filed Bug 483615 for the same symptoms as this bug for Wayland on 14th March 2024. But as I checked it is absolutely the same on Wayland (since 6.0.0) and X11 (since 6.0.5). So aftre nearly 3 Months my bug report has status confitmed and no one seems to have looked at the problem - which is now a show stopper and introduced with bug fixes ... Please look at the problem - not limiting it - and test the possible fixes before rolling out on KDE neon (User Edition) ... this would have helped a lot. If some further info are needed, please call for it here (I am on the list for this bug) with a small decription as I am Unix expert and like to help fixing this severe probems. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488264] Konsole and other programs windows are no longer restored for session save on X11 around update to 6.0.5
https://bugs.kde.org/show_bug.cgi?id=488264 JMB9 changed: What|Removed |Added Summary|Konsole windows and other |Konsole and other programs |applications no longer are |windows are no longer |restored for session save |restored for session save |on X11 around update to |on X11 around update to |6.0.5 |6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout under Wayland
https://bugs.kde.org/show_bug.cgi?id=483615 --- Comment #8 from JMB9 --- Just to make clear that the same problem (but clearly concerning different code passages) is now present for X11 session (see Bug 488264). As this can be regarded as different bug as Wayland session save was trashed with 6.0.0 and X11 session saved was trashed around 6.0.5 in different steps which are described in the new Bug report 488264 ... So changing size on X11 is a minor problem of the past - now KDE neon is no longer capable to restore a session at all - which makes it no longer a place to work for me using a lot of konsole and okular windows with fixed positions on 8 virtual desk ... after three months of bugfixes Wayland is still broken (checked it) and by 'fixes' it is broken for X11, too. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485026] New: KDE neon dependency problems libkcolorpicker-qt6-0 and libkimageannotator-qt6-0
https://bugs.kde.org/show_bug.cgi?id=485026 Bug ID: 485026 Summary: KDE neon dependency problems libkcolorpicker-qt6-0 and libkimageannotator-qt6-0 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Beginning of April it started that version to be updated don't have fulfilled dependencies. It concentrates on the two packages libkcolorpicker-qt6-0 and libkimageannotator-qt6-0. [Additionally there is a component in update which is said to not update till something is fullfilles (shim/booting?) - this massage is currently no longer there ...]: STEPS TO REPRODUCE 1. looking for updates 2. try to update systems 3. update failed due to unresolvable dependencies on KDE neon (after correct update to KDE neon 6.0.3) OBSERVED RESULT Output of update process: ~~ (Reading database ... 2531644 files and directories currently installed.) Preparing to unpack .../libkcolorpicker-qt6-0_0.3.1-0xneon+22.04+jammy+release+build2_amd64.deb ... Unpacking libkcolorpicker-qt6-0:amd64 (0.3.1-0xneon+22.04+jammy+release+build2) over (0.3.0-0+22.04+jammy+release+build1) ... dpkg: error processing archive /var/cache/apt/archives/libkcolorpicker-qt6-0_0.3.1-0xneon+22.04+jammy+release+build2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libkColorPicker.so.0', which is also in package libkcolorpicker0:amd64 0.1.6-2 Errors were encountered while processing: /var/cache/apt/archives/libkcolorpicker-qt6-0_0.3.1-0xneon+22.04+jammy+release+build2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: dpkg: dependency problems prevent configuration of libkimageannotator-qt6-0:amd64: libkimageannotator-qt6-0:amd64 depends on libkcolorpicker-qt6-0 (>= 0.3.1); however: Version of libkcolorpicker-qt6-0:amd64 on system is 0.3.0-0+22.04+jammy+release+build1. dpkg: error processing package libkimageannotator-qt6-0:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of gwenview: gwenview depends on libkimageannotator-qt6-0 (>= 0.7.1); however: Package libkimageannotator-qt6-0:amd64 is not configured yet. dpkg: error processing package gwenview (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.35-0ubuntu3.6) ... Errors were encountered while processing: libkimageannotator-qt6-0:amd64 gwenview ~~ EXPECTED RESULT No problem when updating ... this is the 1st time that such a thing happened on KDE neon based on 22.04 LTS (during the long journey from 5.27.2 to 6.0.3), so not business as usual but something which should not have happened. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0.3 (originally installed as User Edition when available and updated) (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version:6.0.0 Qt Version:6.6.3 ADDITIONAL INFORMATION History of OS:KDE neon (originally 5.27.2 installed as User Edition when available and updated several times till 6.0.3 which was reached before that trouble started) Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485026] KDE neon dependency problems libkcolorpicker-qt6-0 and libkimageannotator-qt6-0
https://bugs.kde.org/show_bug.cgi?id=485026 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485026] KDE neon dependency problems libkcolorpicker-qt6-0 and libkimageannotator-qt6-0
https://bugs.kde.org/show_bug.cgi?id=485026 --- Comment #1 from JMB9 --- On my system are thee strange package problems - and it looks more like Windows than Linux. Normaly Reps are concise and dpendencies are automatically met. If some packages can not be installed, they won't be selected for install/update - so these 3 things should never happen: 1) gwenview and libimageannotator-qt6-0: The new libimageannotator-qt6-0 is broken - so I had to delete gwenview to make updates like X11. Would be nice if that could be fixed and one is able to install gwenview again on latest KDE neon (6.0.3 currently). 2) libcolorpicker-qt6-0: It is there to get updated but can not update: E: /var/cache/apt/archives/libkcolorpicker-qt6-0_0.3.1-0xneon+22.04+jammy+release+build2_amd64.deb: trying to overwrite '/usr/lib/x86_64-linux-gnu/libkColorPicker.so.0', which is also in package libkcolorpicker0:amd64 0.1.6-2 3) UEFI dbx 238 -> 371 is there in Updates (in KDE Updater - not shown when using synaptic). But there is a warning message: "Blocked executable in the ESP, ensure grub and shim are up to date: /boot/efi/EFI/Boot/bootx64.efi" So if it is not met, it should not be offered for update - right? Interesting that such messages are totally uncommon under Linux - not seen similar messages in years. And now 3 problems all emerging beginning of April ... I am not ammused. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485026] KDE neon dependency problems libkcolorpicker-qt6-0 and libkimageannotator-qt6-0
https://bugs.kde.org/show_bug.cgi?id=485026 --- Comment #3 from JMB9 --- Ok, as now may commands have effect it seems the dependency problems have been eliminated: Libpicker could be deleted and installes - which was rejected before; and also gwenview with libkImageAnnotator.so.0 could be installed. So package dependencies seem to be corrected. The only annoyance is UEFI dbx 238 -> 371 only visible with Discover (and not really KDE related); when using synaptic (my default) there is currently no problem with packages. So thanks for the correcting of dependenvies in KDE6! This bug report can be closed from my point of view. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485273] New: KDE6 Bug about session restore under X11: konsole windows seem to be shrinked randomly a little after boot
https://bugs.kde.org/show_bug.cgi?id=485273 Bug ID: 485273 Summary: KDE6 Bug about session restore under X11: konsole windows seem to be shrinked randomly a little after boot Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY I am using automatic session save when logging out for many years with Kubuntu and KDE neon systems. It worked perfectly with KDE5 - and no longer with KDE6. First I spotted Bug 483615 under Wayland - where session save/restor is totally broken. But on X11 it _seemed_ to work - but there is a nasty regression which does not keep the size of all windows. Which window and when it is reduced seems random. STEPS TO REPRODUCE 1. Create several konsole windows in desired size and location (e.g. in alignment) 2. configure "Session Restore: On last logout" 3. reboot (several times) OBSERVED RESULT konsole windows are shrinked - e.g. from 80x24 -> 79x?? and even -> 78x?? - and thus no more aligned/touching but separate. EXPECTED RESULT All windows are identical in size and position as they were before logout/reboot/halt. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 6.0.3 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION Kernel: Linux 6.5.0-27 Session: X11 Desktop: 8 virtal desks in a row, in total more than 72 konsole windows open in a session (see screenshot at https://www.jmb-edu.de/images/Typical_Virtual_Desktop_KDE_neon_6_0_3_X11_JMB.png) System was installed as User Edition with Plasma 5.27.2 and updated several times - not in KDE neon 6.0.3. The bug seems to be a regression of KDE 6 - but not absolutely sure on this ... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485273] KDE6 Bug about session restore under X11: konsole windows seem to be shrinked randomly a little after boot
https://bugs.kde.org/show_bug.cgi?id=485273
JMB9 changed:
What|Removed |Added
CC||jmb_...@gmx.net
--- Comment #1 from JMB9 ---
I am working on my KDE system with 6.0.3 since more than two weeks and was
astonished that my 'vi' does not have 80 colums
a line - but 79 - at first I resized all 79-er windows to 80 by increasing
width - but after reboot some changed to 79 again - some
keep 80.
I got a little lazy as this random pattern stayed that way - and correcting all
konsole windows (well over 72 - see my screenshot
of konsole windows below with just title and scroll bar {no menu bar etc.} for
konsole windows and with 8 virtual desks in a row -
which is my working pattern for years) and now found the 1rst ones with on 78
columns - so it is reduced every reboot randomly.
I was thinking of wrong rounding taken place - but this complete random pattern
seems unlikely to be produced by rounding
problems alone ... it seems very strange ...
I depend on all konsole windows having 80 columns - I think I am currently
using 22-25 lines, so this differs just for using the space
as is visible in my screenshot:
https://www.jmb-edu.de/images/Typical_Virtual_Desktop_KDE_neon_6_0_3_X11_JMB.png
Unfortunately this is extremely annoying for me and if there are pieces if
information / data useful to get the reason
for this regression I would be happy to help (I worked as Unix expert in IT
industry) when getting some guiding info
how to gain them.
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout
https://bugs.kde.org/show_bug.cgi?id=483615 --- Comment #7 from JMB9 --- This bug is about a special Wayland issue with KDE6 - unfortunately X11 has also a bug which changes the size of windows sizes (at least for konsole it seem every boot can change it to make them smaller - the pattern seems random at first) ... and I opened Bug 485273 for this different problem ... it could be that while quite different both problems may be related. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485273] KDE6 Bug about session restore under X11: konsole windows seem to be shrinked randomly a little after boot
https://bugs.kde.org/show_bug.cgi?id=485273 --- Comment #2 from JMB9 --- Side question which stops me from really testing the problem: With the 1st problem in Wayland (Bug 483615) I experimented with konsole parameters: konsole --qwindowgeometry 400x400+50+50 --workdir '/home2/jmb/mytex/presentation_jmb/' --hide-menubar --hide-tabbar --notransparency --qwindowtitle 'JMB_Term_1' & But even 'konsole --help-all' seem to not give complete parameters (e.g. how one can create konsole windows on all virtual desktops present; are there absolute coordinate or can the virtual desk be specified ???). https://docs.kde.org/stable5/en/konsole/konsole/konsole.pdf seem just for KDE5 - so maybe one could give a hint where to get information about creating konsole windows with all parameters necessary (which was possible long ago ... I started before Linux 1.0 was released and this was normal way for worstation use in sciences - and KDE has much more features so this should be possible - and otherwise a save session and restore session could not work at all). As this could not be tested I am still not sure if this could be a window manager / compositor / windowsing library problem or really a console problem. But people developing konsole could tell. Im not sure if the 8 virtual screen (6x 4k in a row) could be part of the problem - but as I use this setting for several years with KDE5, it would be a regression of KDE6. Additionally I hope and expect that KDE is prepared for standardized resolutions 8k and 16k ... so 6x 4k should not be a problem. Maybe this problem is related with the bigger problems using Wayland (the above mentioned Bug 483615) - where even positions are completely ignored and can not be restored. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout under Wayland
https://bugs.kde.org/show_bug.cgi?id=483615 JMB9 changed: What|Removed |Added Summary|Konsole windows no longer |Konsole windows no longer |saved/respawned |saved/respawned |automatically via saving|automatically via saving |session on logout |session on logout under ||Wayland -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483612] New: Bottom line and right row are bright like stuck pixels after logging in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483612 Bug ID: 483612 Summary: Bottom line and right row are bright like stuck pixels after logging in KDE 6 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** Bottom and right rim bright / stuck pixels when logging in on KDE neon 6.0.0|2 (i.e. bright line at bottom, bright column at the right - all being stuck pixels - i.e. coulourful) - see screen shot: https://jmb-edu.de/images/screenshot_of_KDE_neon_6_0_2_wayland_with_ill_bottom_and_right_rims_of_stuck_pixels.gif [It is 6734 kB, so larger than allowed attachment - but via Browser no problem ...] It was not existing with other OS - older KDE up to at least 5.27.10 - but emerged with update to KDE 6.0.0 (1st time Wayland - so could be kwin ??? related) on installation of KDE neon [based on Ubuntu 22.04 LTS]. The login screen does not show this pattern but directly after loging in, this pattern is present. *** STEPS TO REPRODUCE 1. Using KDE neon updated to KDE 6 2. Logging in 3. bright rims are visible (at least on my HW, see below) OBSERVED RESULT bright rims to the right and bottom EXPECTED RESULT normal display SOFTWARE/OS VERSIONS KDE neon (User edition) with complete update, i.e. current. ADDITIONAL INFORMATION CPU: AMD Ryzen 5 3600 GPU: AMD Radeon RX 5700 XT Motherboard: ASUS ROG Strix X570-E Gaming Screen: BenQ EW3270U 4k screen => This is common HW and the best supported HW under Linux (gaming versions are chosen for better compatibility - like motherboard). I am a former Unix specialist - so if you need futher details, just ask with some explanation what to do / send to you for clarification. E-Mail: jmb_...@gmx.net Thanks for your good job! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483612] Bottom line and right row are bright like stuck pixels after logging in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483612 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] New: Konsole windows no longer saved/respawned automatically via saving session on logout (at least for Konsole windows)
https://bugs.kde.org/show_bug.cgi?id=483615 Bug ID: 483615 Summary: Konsole windows no longer saved/respawned automatically via saving session on logout (at least for Konsole windows) Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** I open several programs incl. a lot of konsole windows (~72 about 8 virtual desktops; oldschool way of working with a workstation ;). Configuration: "Settings - Session - Desktop session - Session restore: launching ... open: on last logout" which worked perfectly with KDE5. I have not looked for more programs - but Firefox and Thunderbird is restarted after having started them now ... never worked for Konsole since KDE 6.0.0 on my system. I also changed the setting, rebooted, changed it back ... never worked under 6.0.0|2. It did work with other OS - and KDE neon with up to 5.27.10, but was no longer working with update to 6.0.0 and unfortunately no change with next update to 6.0.2. *** STEPS TO REPRODUCE 1. Configuring session save after reboot to restore session 2. Open several konsole windows ... 3. Rebooting - an no konsole window is present at all ... OBSERVED RESULT No konsole window is respawned after booting the system. EXPECTED RESULT All konsole windows present bedore boot are respawned after booting with correct size, directory and position for all virtual desktops (I use 8 in a row). SOFTWARE/OS VERSIONS KDE neon current [Ubuntu 22.04 LTS based] ADDITIONAL INFORMATION ... would not think any other thing could be of relevance ... should be reproducable on any HW ... I am a former Unix specialist - so if you need futher details or have problems to reproduce this problem, just ask with some explanation what to do / send to you for clarification. E-Mail: jmb_...@gmx.net Thanks for your good job! End of Problem description! If the rest would be a reasonable bug report please say so and I will create it ... but may be helpful when looking at the problem - at least I hope so ... # # * Little off-topic - about finding a workaround for that problem # (currently, I can not work as I need a lot of konsole-Windows # which take a lot of time to get 72 of them in right size and position # after each boot): # # I tried creating konsole windows with fixed size and positions, but # while size of window was accepted, the position did not work - it always # emerge in the middle of screen and title can not be set: # konsole --qwindowgeometry 400x400+50+50 --workdir '/home2/jmb/mytex/presentation_jmb/' --hide-menubar --hide-tabbar --notransparency --qwindowtitle 'JMB_Term_1' & # # -> "JMB_Term_1" does not work - maybe a console setting ... will check. # -> --qwindowgeometry was found via command 'konsole --help-all' under #KDE 6.0.2 but first two parameters work (width and height of window) but #next parameters have no meaning ... always respawning in the middle. # -> There seems to be no Konsole Manual for version 6 yet #(KDE5_konsole_handbook.pdf is not helping - I think). # # Im not sure if the 8 virtual screen (6x 8k in a row) should be positions # just by incresing x position - as it worked several years before using KDE # working with XFCE, e.g.: # xfce4-terminal --geometry 80x22+1530+1509 --working-directory=/home/user/mails -T "User@`hostname` `date +%a.,\ %d.%m.%Y\ %H:%M:%S`" & # # Some explanations may be helpful for a lot of KDE users concerning # CLI usage of konsoles for scripting - I guess. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout (at least for Konsole windows)
https://bugs.kde.org/show_bug.cgi?id=483615 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout
https://bugs.kde.org/show_bug.cgi?id=483615 JMB9 changed: What|Removed |Added Summary|Konsole windows no longer |Konsole windows no longer |saved/respawned |saved/respawned |automatically via saving|automatically via saving |session on logout (at least |session on logout |for Konsole windows)| -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483612] Bottom line and right row are bright like stuck pixels after logging in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483612 --- Comment #2 from JMB9 --- I have just updated KDE neon (a lot KDE programs [KDE Gear 24.02.1] - but KDE was on 6.0.2 - with 6.0.3 not yet available). After reboot the problem is still there. --- But you gave the hint on my other bug with session restore that this is Wayland related - and so are my graphic errors after switching to X11 ... the graphic errors are gone - so are Wayland related - which means it does not work with RX 5700 XT / RDNA1 / Navi10 correctly. But on X11 session, everything is ok graphics related. So KDE seems to have trouble with Wayland - concerning graphics mode and session restart. Additionally, the scaling was not changed when switching sessions - but Wayland and X11 are totally different (on X11, konsole windows are much larger) - so both have not the same behaviour under KDE. >From my point of view this is a third Wayland related bug with KDE. I am happy I can start configuring and working under X11 with KDE6 ... so the big problem is Wayland here. Mabe it would have been better to leave the default with X11 session. KDE neon was switched to Wayland with KDE 6.0.0 update - nice to get Wayland bug reports ... not so nice for users, though ... Thanks for the help and hinting to session type ... and I hope the problems with Wayland will be addressed. Should I have to create new bug reports - or can this be pointed to the right category: I think KDE and Wayland are not yet ready for prime time and Wayland and X11 should behave and look the same under KDE ... and one should support X11 (concerning KDE neon) till the bugs have been fixed ... may be heavy lifting if Wayland should be the default for KDE neon based on 24.04.1 LTS ... but maybe this can be fixed faster. I am willing to test if KDE Wayland got better - as I will clone OS partition after I have configered everything right and can test it with the old clone image and working with the new one. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483612] Bottom line and right row are bright like stuck pixels after logging in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483612 --- Comment #3 from JMB9 --- Sorry, I used display scaling - but if I remember correctly, the graphics problem was there before I used scaling. Can check, if this would be of improtance. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout
https://bugs.kde.org/show_bug.cgi?id=483615 --- Comment #4 from JMB9 --- Yes, when selecting X11 session it seems to work for me - applying the same scaling, X11 is larger then Wayland ... this may be addressed, too (at least if KDE is expected to have same appearance under both session type - which I would prefer). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483612] Bottom line and right row are bright like stuck pixels after logging in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483612 --- Comment #5 from JMB9 --- Ok, I checked and with 100% scaling there is no graphics problem visible with Wayland session - as you guessed. I used 155% (ok for konsole windows) and with this under Wayland session the graphics problem is clearly visible. So a combination of scaling and Wayland session triggers this at least on my HW (as given before: AMD Radeon RX 5700 XT / RDNA1 / Navi10). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483615] Konsole windows no longer saved/respawned automatically via saving session on logout
https://bugs.kde.org/show_bug.cgi?id=483615 --- Comment #6 from JMB9 --- New 3rd bug report seems not necessary: Well, the problem with size difference is caused by me selecting 155% on Wayland (after the former factor was not applied but was put to 100% when updating to KDE6 - which is really tiny), while on X11 session the global scale was set to 200% (I don't know why) - so this it was a little too large. But setting it to 155% on X11 seems to be quite similar (eben idetical) with using Wayland and 155%. So the only thing which was not perfect is that both saling factors are not adopted in the other session after changing it. But maybe there exist reasons that this would not be appropriate - so I think this is not worth a bug report - as long as switching between X11 and Wayland with same look and feel is a goal of KDE. Concerning the main problem I found that: 1) X11 session: a) is able to store the konsole windows - and when switching to 2) Wayland those correctly restored konsoles are a) opened with correct windows size (OK) but b) are respawned in the middle of 1st virtual desktop - so window position can not be restored (bug with Wayland). After my findings the position is just not considered in Wayland session. c) konsoles are never saved with session save (bug with Wayland). So both, not saving and not use windows position of konsole windows are severe bugs for people like me working with about 72 konsole windows. So here, Wayland makes trouble while X11 works as it should. On the other hand even with X11 and command line I can not position konsole windows as I wich for (despite being possible in session save): a) I am not able to give a parameter concerning virtual desktop - as it is used by session restore one should give it with parameters; b) larger positions than screen resolution is not interpreted to be sent to further virtual desks (fvwm used virtual coordinates in the 1990-ies - very easy placement for all desktops) but are shifted "last pixel + 1" to "1st pixel" of the current virtual desktop with KDE. For me, this is also a bug - but maybe just a problem of missing help text? Is there any document (web or PDF manual) explaining how to create such konsole windows correctly with KDE6? I tested something like (I did not see more when using 'konsole --help-all' on KDE6): konsole --qwindowgeometry 400x400+50+50 --workdir '/home2/jmb/mytex/' --hide-menubar --hide-tabbar --notransparency --qwindowtitle 'JMB_Term_1' but this is not working for Virtual Desktops and not for Window title - but I am new to this method of creating all windows via a simple script. This could be invoked at session start and no longer saving a session ... which would ba a more robust approach. So not only a workaround but just working more efficient and customizable. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483612] Bottom line and right row are bright like stuck pixels after logging in KDE 6
https://bugs.kde.org/show_bug.cgi?id=483612 --- Comment #7 from JMB9 --- I can clearly say that those bug reports are not related. My bug report is about the Wayland display after log in which is disturbed by a right column and a bottom line with stuck pixels; so it is bright in contrast of the black rim but shows differen colors and is related with wrong usage of graphics card (AFAICS). It looks as if the HW (graphics card) could be harmed - and is really annoying. The other bug report shows System Settings - Wallpaper (i.e. showing wallpaper pictures for sellection) - and the bright column to the left of the picture is calculated by the left column of the respective wallpaper picture (just zoomed in to this bright column) - to produce a 3d like effect (I guess) - which looks nice ... So this seems to have changed ... but does not look bad or broken in any way. But this is just my impression (I worked in Unix business and had been responsible for CAD Workstations - not too familiar with KDE GUI changes - and I have not looked into current wallpaper selection via system settings, though). But a responsible developer should clearly say if something was done this way as stylish means. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487423] New: Whith KDE neon 6.0.4 update on 22.05.2024 (KDE Frameworks 6.2.0?) many KDE icons are missing and new appeared (big mess)
https://bugs.kde.org/show_bug.cgi?id=487423 Bug ID: 487423 Summary: Whith KDE neon 6.0.4 update on 22.05.2024 (KDE Frameworks 6.2.0?) many KDE icons are missing and new appeared (big mess) Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: carlosdema...@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY After the update on Wed., 22.05.2024, most KDE icons e.g. for Application Launcher, Sleep, Restart, Shutdown, Konsole, System etc. are gone - while e.g. Synaptic Package Manager has now a new Icon (low res - ugly - the former was fitting to the rest). Changing icons is always a bad idea when those icons are totally different like with the new one. Was this the KDE Frameworks 6.2.0 upgrade which went totally wrong? KDE Plasma 6.0.5 with hopefully clearing my most enerving problems of KDE 6 is still not rolled out ... STEPS TO REPRODUCE 1. Having former state where all icons were on place 2. making an update 3. rebooting OBSERVED RESULT Most icons are absent - other may be totally different. This is a mess which should have been spotted before rollout. EXPECTED RESULT All icons are there - maybe with higher resolution and better quality - this is no upgrade but a downgrade - as even the new icon I spotted is of much worse quality than the old one. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux KDE neon User version being updated from start version KDE neon 5.27.2 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.10-060810-generic (64-bit) [from Ubuntu PPA] Graphics Platform: X11 (Plasma is a mess with KDE 6.0.4 - see bug reports) ADDITIONAL INFORMATION 12 × AMD Ryzen 5 3600 6-Core Processor 15,5 GiB of RAM AMD Radeon RX 5700 XT ~~ System is completely updated without any package problems. Most things are done via synaptics - as the package manger Discover does not show details about updates, shows packages with not fulfilled dependencies (like the eneving UEFI dbx 238 -> 371 which is just stuck) but is used form time to time to make sure that all things are there. So I have the feeling KDE does not really using the Debian installation but has some strange extensions ... but this is another bug report - just mentioned if this could cause such a mess ... which would still a bug! / is only 72% used ... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487423] Whith KDE neon 6.0.4 update on 22.05.2024 (KDE Frameworks 6.2.0?) many KDE icons are missing and new appeared (big mess)
https://bugs.kde.org/show_bug.cgi?id=487423 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487423] Whith KDE neon 6.0.4 update on 22.05.2024 (KDE Frameworks 6.2.0?) many KDE icons are missing and new appeared (big mess)
https://bugs.kde.org/show_bug.cgi?id=487423 --- Comment #2 from JMB9 --- This bug can be closed as several updates appeared for KDE neon 6.0.4 which solved the problem, thus all icons (AFAIKT) are the same as it was before this bug was introduced. Thanks for solving this so fast ! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487374] Missing icons
https://bugs.kde.org/show_bug.cgi?id=487374 --- Comment #22 from JMB9 --- This bug (as it was marked as being duplicate of my 487423) may be closed as several updates appeared for KDE neon 6.0.4 which solved my problem, thus all icons (AFAIKT) are the same as it was before this bug was introduced. Thanks for solving this so fast ! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session (deleted) and some are restored on a wrong virtual desk (displaced)
https://bugs.kde.org/show_bug.cgi?id=488744 --- Comment #8 from JMB9 --- Till KDE Plasma 6.1.3 the problem is still there ... only 6.1.0 worked for me ... --- About every 5 reboots all konsole windows lose their directories (and use ~ instead), and after the next reboot nothing will come up (except firefox). --- The original problem of missing windows or displaced ones are random and not very frequent ... but is clearly there ... so there must be several problems involved AFAIK ... --- But no real hint to get to the root of that problem ... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 490704] Cannot mix incompatible Qt library (5.15.13) with this library (5.15.14)
https://bugs.kde.org/show_bug.cgi?id=490704 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net --- Comment #10 from JMB9 --- I can confirm the fix, too! (Wanted to make a bug report, found this one, updated my system ... and now the problem is gone.) Thanks for the fast fix ... I hope the various session save problems may also get fixed soon (Bug 488744), which is present since 6.0 to 6.1.3 - but did not show with 6.1.0 ... and being a moving target. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503802] New: I spotted that with latest Plasma 6.3.4 (on current KDE neon) my konsole windows all shrink - so my bug 485273 / session save was resurrected
https://bugs.kde.org/show_bug.cgi?id=503802 Bug ID: 503802 Summary: I spotted that with latest Plasma 6.3.4 (on current KDE neon) my konsole windows all shrink - so my bug 485273 / session save was resurrected Classification: Plasma Product: kwin Version: 6.3.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: jmb_...@gmx.net Target Milestone: --- SUMMARY As KDE 6.0 was a mess I created several bug reports - one of them: https://bugs.kde.org/show_bug.cgi?id=485273 was about shrinking konsole windows which I use to work in workstation mode: 8 virtual desks - all with at least 9 konsole windows (TeXing, programming, editing, Webserver ...). I used Session Save on X11 - as Wayland is currently not usable - and I just think that the problem my be that kwin was splitted so the infant Wayland kwin should use Session Safe via Wayland protocol - which is not even in final stage. As in 6.0 absolutely the same ill behaviour was seen and made me crazy - after many years of perfect behaviour of KDE 5. STEPS TO REPRODUCE 1. Create a normal workstation environment like: 8 virtual desks, on each having 9+ konsole windows all of 80x23 chars size and use session safe 2. Reboot several times - und you see: 3. that no konsole window has 80x23 but less - so your editing and professinal working is trashed totally OBSERVED RESULT Shrinking of all the konsole windows saved by 'session safe' which was one of the innumeral bugs of KDE 6.0 - and now resurrected again - just a little more than 2 months after I closed that Bug Report 485273. This is shocking! The old bug report has 6.5.0 in it - my fault - which may be 6.2.5 of start of 2025 when I no longer saw shrinking - and looked several weeks before closing it to be sure. And now it is back - and shrinking quite fast as before. I think it was said a rounding bug - but windows sizes are integers ... so there is hint of big problems in the programming ... EXPECTED RESULT Session save should restore all programs with correct window sizes, positions etc. - which is a task well working eben with CDE long before KDE existed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon (24.04 LTS/Noble based; daily updated) KDE Plasma Version: 6.3.4 (latest) KDE Frameworks Version: 6.13.0 Qt Version: 6.8.3 ADDITIONAL INFORMATION As this bug was very long lurring in the KDE 6.x.y and was reported by me, I am really tired about the development process which is one step forward, two steps back currently. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503802] I spotted that with latest Plasma 6.3.4 (on current KDE neon) my konsole windows all shrink - so my bug 485273 / session save was resurrected
https://bugs.kde.org/show_bug.cgi?id=503802 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 500729] Okular Menu got totally disrupted by changing settings/configuration via menu
https://bugs.kde.org/show_bug.cgi?id=500729 --- Comment #4 from JMB9 --- I was waiting for Ocular 25.4.0 to make a video to get a reproducible bug about the trashed menu. Unfortunately I was shocked when seeing a new bug in Ocular, that instead of cursor up/down just going to a previous/next entire page only getting some lines up/down, while the former behavour is now in cursor left/right. And to make it worse - also Page Up/Down does the stupid thing which does cursor up/down now. This is an extreme regression - ones again - and I am using faith in LDE developer fixing the mess KDE 6 was (incl. Framework, Gears etc.). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 500729] Okular Menu got totally disrupted by changing settings/configuration via menu
https://bugs.kde.org/show_bug.cgi?id=500729 --- Comment #2 from JMB9 --- I still hope to reproduce it and aimed at making a video with vokoscreenNG to help in reproducing the problem. At 1st I thought the entire configuration would be lost - but when moving "okular" to "OLD_bad_menue_OLD_okular_OLD" in the directory "~/.local/share/kxmlgui5", the menu works as described but all I configured in Settings and okular_part was still there - but just okular_shell was empty - so I changed that - and the menu stays ok. So this seems to be a valid workaround ... but not a point I could start to search for a trigger event so the problem could finally be reproduced. If I remember correctly the breakage of the menu happens quite fast when starting changing okular_part - i.e. putting several things from left to right to make it visible in the toolbar, changing order and deleting a few by putting them from right to left. And that happened reliably in freshly installed KDE neon ... Is it possible to move away all okular configs so I start as if okular was not yet configured in any way (especially losing the config of "okular_part" - as I suspect something here must be the trigger)? With that point I could configure it and if any "no text" label in the menu appears, I should have found a valid trigger ... and can provide the video ... Just out of curiosity: Why is the label "No text" no point to start for finding the problem? I thought it is a label to debug if a label was left empty which should not happen for a menu point ... or what is the use of "No text"? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 485273] KDE6 Bug about session restore under X11: konsole windows seem to be shrinked randomly a little after boot
https://bugs.kde.org/show_bug.cgi?id=485273 JMB9 changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from JMB9 --- The X11-only part is due to Wayland not working at all with session save - so Wayland has much more regressions compared with the X11 session (as the full function is expected from Wayland as is for X11 - I hope so. Additionally, the fallout from KDE 6.0.0 was slowly but steadily repaired - so with Plasma 6.5.0 this problem never occured. As this was seldomly occuring before, I want to be sure that the problem is really gone. So this bug report can be closed - and so I change the bug report to resolved. As I heavily rely on session safe I am sure that the problem is gone ... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 500729] Okular Menu got totally disrupted by changing settings/configuration via menu
https://bugs.kde.org/show_bug.cgi?id=500729 JMB9 changed: What|Removed |Added Summary|Menu got totally disrupted |Okular Menu got totally |by changing |disrupted by changing |settings/configuration via |settings/configuration via |menu|menu -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 500729] Menu got totally disrupted by changing settings/configuration via menu
https://bugs.kde.org/show_bug.cgi?id=500729 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 500729] New: Menu got totally disrupted by changing settings/configuration via menu
https://bugs.kde.org/show_bug.cgi?id=500729 Bug ID: 500729 Summary: Menu got totally disrupted by changing settings/configuration via menu Classification: Applications Product: okular Version: 24.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: jmb_...@gmx.net Target Milestone: --- Created attachment 178871 --> https://bugs.kde.org/attachment.cgi?id=178871&action=edit Screenshot showing broken menu structure with 'no text' and my choice for toolbar - which may caused this *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY When I installed KDE neon Noble (several times due to new PC with booting problems - related to ASUS&Ubuntu 24.04 LTS plus NVMe which at least made the problem more severe) and configured it (while adding things to the toolbar I 1st spotted a 'no text' menu point - so I think that is directly related to the problem), all config changes directly result in a broken menu structure: there were menu points missing (one must rely on shortcuts etc.; like 'print' or 'configure toolbars') and some menue points are just showing "now text". I thought the next update may correct that - but it stays bugged for me. So there is something really strange going on - while I can work (with shortcuts - knowing okular quite well) - but it is an extreme annoyance. Why is this problem not visible for developers and can stay for so long? Would prefer communication in case this is not reproducable ... so that this is solved for all soon. STEPS TO REPRODUCE 1. Install okular 2. configure it (especially toolbars - see screenshot) 3. using okular and seeing that menu is a mess OBSERVED RESULT The menu structure is broken: 1) some labeled are missing but show 'no text' (I think this must be a fallback so this error should be easy to find). 2) menu points are no longer there: print - workaround: Ctrl|Strg-P, configure toolbars - workaround: right mouse click in toolbar etc.) I always had these full toolbar and that never caused any problem ... so there is something weird happening - and not catched even when okular was updated ... My 1st screenshot with that problem was on 14. Dec. 2024 - and I thought, such a big problem will just be solved with next release - but was not! EXPECTED RESULT Correct menu structure as with KDE 5 SOFTWARE/OS VERSIONS GNU/Linux: KDE neon 6.3 (freshly updated) (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 6.3.1 KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 KDE Gears 24.12.2 Qt Version: 6.8.2 # Mesa from Ubuntu Noble HWE2 - Mesa: 24.2.8 # Linux from Ubuntu Mainline-PPA - Linux: 6.12.16 ADDITIONAL INFORMATION I just spotted the problem when installing KDE neon Noble-based on the new PC and configured ocular there - while the clones Jammy partition having already Plasma 6 had no problem - but it was configured on KDE Plasma 5 - so maybe the okular configuration is broken by new KDE 6 in a way it disrupts the menu structure ??? As KDE 6 created a huge pile of problems for my workflow, I am still thinking about some subtile changes causing this. But I am not sure that the problem is KDE related ... may just be intuition - especially as this problem got not solved, maybe most will not see it ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488744] Some console windows are missing when using session save under X11 session (deleted) and some are restored on a wrong virtual desk (displaced)
https://bugs.kde.org/show_bug.cgi?id=488744 JMB9 changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #10 from JMB9 --- As Wayland is not even usable with session save, this problem is X11 only till Wayland is capable of basic KDE functions. As of Plasma 6.3.0 (maybe even 6.2.5? - KDE neon based on Jammy is unfortunately still broken - so 6.2.0 was definitely still buggy) this problem did not occur. As I am depending on session save in a huge way, I can say that the bug is no longer there. As this problem occurred sporadically, I just wanted to be sure. This bug report can be closed - so I set the status to Resolved - Fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503802] Konsole windows created through session restore are slightly smaller than they were originally, changing the terminal dimensions
https://bugs.kde.org/show_bug.cgi?id=503802 --- Comment #4 from JMB9 --- As I am working with the workstation I am not able to use 100% - it is just too tiny. I would try to help - but I don't think that this problem is not easy to reproduce. Especially as this scaling factor was not changed on my workstation during the process of KDE development. So KDE must have introduced the old problem or invented something similar. Now each reboot makes the session save data worse - and even faster than the old bug did (which was described as rounding bug 485273), while such values should be stored with integer values. Each screen has a native resolution which should be used directly; for me scaling should have a direct effect on fonts, not on sizes of windows. I think session save should just do what it implies - getting all values and reproduce them perfectly - degrading values should never be possible at all! Not using entire pixels for windows borders and such must result in troubles. So the method would be just wrong, if I get the problem right. And what I can not get is that this bug was known and fixed - and reintroduced/-invented with (I guess) 6.3.4 - and as I thought it was solved I never guessed this could happen again ... so there from my perspective there is a problem in the development process. As I am not a developer - and never looked at the KDE source code - I just can guess. But one should make sure that problems solved can not be reintroduced later on. This should be spotted by automatic tests - I assume - or at least by changing the code that values for session save must be integers. And if it is a similar bug, the former reason for the old problems would be a good start for this 'new' problem ... and should be the way forward ... if not too many things had been changed. If so, it is a clear hint of a development problem - at least I would call it such when it happens with my own programming - but maybe kwin changes to separate Wayland from X11 my have just provoked that. On the other hand as a developer one will automatically use the highest available resolution - and 4k is cheap since 2014 - so such problems should be seen by lots of developers (Scaling fator of 100% does not make sense at all with 4k with <= 31" diagonal; and it is just strange that it is not set reasonably at the beginning). So I can not get the picture how such clear and extreme bugs are not seen or reproduced. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 503802] Konsole windows created through session restore are slightly smaller than they were originally, changing the terminal dimensions
https://bugs.kde.org/show_bug.cgi?id=503802 --- Comment #2 from JMB9 --- I am not sure - but not set by me on purpose - where can I see if fractional display scale factor is set? I am sure to have only set: Display Monitor - Display Configuration - Global Scale: 150% (for my 31.5" 4k screen) and that I have not changed something about scaling in any way since the original bug was gone - so if fractional display scale factor is used, it must be change by an update of KDE neon components. If you could guide me how I can get this info, I will provide it. One more info - the current bug is more severe than the former one, as it is not a matter of several days - but every day I see new windows with less than 80x23 konsole size even when I had correct all those windows the former day. By the way - I am not sure if it has something to do with kwin or with konsole oder something else. It is probably the same problem as the former bug (Bug 485273) ... only more severe. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 505696] After Inotify got increased its limits 3 times (?), system is slow and not responsive.
https://bugs.kde.org/show_bug.cgi?id=505696 JMB9 changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from JMB9 --- You can see the output (from 18. May, so one month ago - but I think this should be the current situation - as I was busy to make sure my HW is not the culprit): https://www.jmb-edu.de/KDE_bug_with_inotify_survey.txt -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 505696] After Inotify got increased its limits 3 times (?), system is slow and not responsive.
https://bugs.kde.org/show_bug.cgi?id=505696 --- Comment #5 from JMB9 --- My system was fast - and it got slowed about the same time I agreed to extent the limit - even though I did not understand what it does and why. Additionally it asked again and again - and after some time it wants to further extent the limit. So from my perspective it goes crazy! Additionally I don't think that monitoring files is sane ... but mabe one could explain what inotify really does, why and how the changes are done. Currently it is not transparent for me ... Especially as the performance fell more severly than with my old Haswell system with huge mitigations happening in a few months (CPU and chipset graphics) ... so from my point of view if HW is ok which is proved by the other system - the kernel is sevrely limited under KDE6. And as KDE 6 is userspace, this should not be possible ... an extreme memory leak should be well known ... and this would result in some other effects and could be seen. So if Inotify is not the cause for trouble and KDE neon is not known to have problem with some similar AMD systems concerning performance I just have no guess. But I still think it is KDE 6 related - after I have seen Kubuntu with 5.27.12. KDE neon was terrific - a pleanat ride - till it switched to KDE 6 (which was started with 22.04 unfortunately; so no longer a working KDE neon for my new machine). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 505696] After Inotify got increased its limits 3 times (?), system is slow and not responsive.
https://bugs.kde.org/show_bug.cgi?id=505696 --- Comment #7 from JMB9 --- Thanks for your help! I used the command as suggested: sudo su - mv -v /etc/sysctl.d/50-kde-inotify-survey* /root # renamed '/etc/sysctl.d/50-kde-inotify-survey-max_user_instances.conf' -> '/root/50-kde-inotify-survey-max_user_instances.conf' ... and after a reboot I tested the two games which were unpayable with KDE neon after allowing it to rise the limit 3x ... and now I can play them - so what inotify did IS really ugly - even though I must confess that Kubuntu 24.04 LTS is faster and more responsive. But maybe KDE 5 has a smaller footprint than KDE 6 - as KDE 6 is not that optimized yet? >From what I saw KDE 6 is in alpha state - not ready to get tested by users ... KDE neon was so fast and responsive with KDE 5 - much better than Kubuntu 24.04.2 I use now - and I just installed it to proove KDE 6 as cuprit ... and that was right. For this bug report: I don't know why any file should be monitored at all. Root FS and Memory may be monitored and induce warnings ... these are the only two things which should be looked for. Well, another problem emerged as I thought everything was moved away, and so after a reboot and testing I was shocked to get another "Inotify Instance Capacity Low" message. So this message does not come from "/etc/sysctl.d/" but from the running KDE ??? >From my point of view this should be switched off by default as baloo. But while baloo can at least be switched off, intotify is not even found in KDE search (i.e. Quick Setting - System Settings - `Search Field´). So how can I make sure this 'service' (I would rather regard it as malware) never runs on my KDE neon system again? And why has KDE 6 a problem on my oversized machine (see HW data given on "2025-06-17 13:23:58") but still thinks "capacity low" ??? There must be a fundamental problem - and I guessed that KDE developers don't test a system with more than 100 konsole windows each with login shell. That is my working style since 1993 for maximum user efficiency ... and KDE 6 may not be prepared to do that efficiently - while with KDE 5 this is no problem at all. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 505696] New: After Inotify got increased its limits 3 times (?), system is slow and not responsive.
https://bugs.kde.org/show_bug.cgi?id=505696 Bug ID: 505696 Summary: After Inotify got increased its limits 3 times (?), system is slow and not responsive. Classification: KDE Neon Product: neon Version First unspecified Reported In: Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: jmb_...@gmx.net CC: carlosd@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY I am using a workstation which had been extremely performant (see SW and HW below) and is now extremely slow and not responsive due to letting Inotify increase its limits. I installed Kubuntu 26.04.2 just to see it is not my HW but KDE 6. STEPS TO REPRODUCE 1. KDE neon 6.3.5 - updated 2. having 8 virtual desks and more the 100 konsole windows with login shell (see screenshot) 3. increase limits as desired by Inotify OBSERVED RESULT System is no longer responsive ... games are unplayable ... even TeXLive is slow. EXPECTED RESULT System should be working as fast as before and no more "increase limits" calls by Inotify would be seen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 6.3.5 (24.04.2 based/Noble) - up-to-date KDE Plasma Version: 6.3.5 KDE Frameworks Version: 6.14.0 Qt Version: 6.9.0 Gears: 25.4.2 Using X11 session (as Wayland has not even session save) HARDWARE: Silent Workstation, Zen 4: Ryzen 9 7900, RDNA 3: Radeon RX 7800 XT, ASUS ROG STRIX X670E‑E, Kingston KSM48E40BD8KM‑32HM 64 GB DDR5‑ECC RAM, 3x Samsung EVOs 870 SATA III 4 TB, 2x Samsung 980 PRO Interne NVMe SSD 2 TB M.2 2280 PCIe 4.0. ADDITIONAL INFORMATION I am using 8 virtual desks - each with at least 9 - typically more - konsole windows with login shells - a professional workflow. This might be the cause for the trouble (due to KDE 6 not using resources efficiently as KDE 5 did it perfectly) and a screenshot of my desktop is seen here (<4kB attatchment is a joke): https://www.jmb-edu.de/images/KDE_Problem_with_holes_in_konsole_windows_showing_rectangular_parts_of_background_20250506_221202_medium.jpg to give you an impression of the desk and one can see visible problems (two rectangle showing background image an not the background of the konsole window) which may be related to this bug. As experienced Unix expert I thought a component is dying or a mitigation hit me ... would have never thought of a system going crazy for monitoting files. I just installed Kubuntu 24.04.2 and it works like a charm ... the oposite of the dead system KDE 6 created. Before KDE 6 was introduced, KDE neon was king - nearly perfectly configuered, fast, reliable - and with KDE 6 I could not even decide which bugs to report first. But now this is a game changer - if this is not revoked easily, KDE 6 is dead for me! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 505696] After Inotify got increased its limits 3 times (?), system is slow and not responsive.
https://bugs.kde.org/show_bug.cgi?id=505696 JMB9 changed: What|Removed |Added CC||jmb_...@gmx.net --- Comment #1 from JMB9 --- I thought "baloo" is an ill sevice which should be off by default - but at least I can swith that off in KDE settings ... Why is Inotify going crazy that way - and no warning presented. How can I revoke those bad things Inotify did when it increases the limit (3 times, I think - not sure - and still demanding the limit to be further increases!). It must severly disturb the kernel for such an extreme reaction - with 128 GB ECC memory! So like Baloo, Inotify and general file monitoring should never be started in that way and it should be asked if this is welcome with a warning about performance! And it is still crazy giving the same message: ~~ Inotify Instance Capacity Low You have too many applications wanting to monitor file changes! When the capacity is exhausted it will prevent further file monitoring from working correctly. Either close some applications or increase the limit. Currently using 90% of instances and 0% of watches. ~~ And I still wonder why any file should get monitored - this is no trusted system (i.e. hardened) and the only things monitored would bei root filesystem and memory for getting out of free space and causing some info that it is below ??%. But this is not done ... Any explanation what it is intended for and why it ruins a capable workstation that easy would be welcom. Especially how to revoce the ill things Inotify did so I can at least tests KDE 6 - I will work with the Kubuntu partition till KDE 6 is in a suitable situation like Debian Testing - currently KDE neon with KDE 6 is just unstable! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 505696] After Inotify got increased its limits 3 times (?), system is slow and not responsive.
https://bugs.kde.org/show_bug.cgi?id=505696 JMB9 changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #9 from JMB9 --- As it was moved to /root the file '50-kde-inotify-survey-max_user_instances.conf' is only there: ~~ # This file was auto-generated by kde-inotify-survey. Manual changes will be overwritten. fs.inotify.max_user_instances=256 ~~ -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 505696] After Inotify got increased its limits 3 times (?), system is slow and not responsive.
https://bugs.kde.org/show_bug.cgi?id=505696 JMB9 changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #11 from JMB9 --- This is certain - as more than 4 weeks the system was extremely slow. The question is how to stop innotification from doing harm to the system performance again. -- You are receiving this mail because: You are watching all bug changes.
