[kfontview] [Bug 476546] New: I cannot install TrueType or OpenType font style variations on Linux
https://bugs.kde.org/show_bug.cgi?id=476546 Bug ID: 476546 Summary: I cannot install TrueType or OpenType font style variations on Linux Classification: Applications Product: kfontview Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- I have installed a TrueType font on Linux, in this case the Light variation. But when I try to install the other font style variations, such as Bold, Normal, Italic, etc., it gives me the following error (same error verified with OpenType fonts): https://drive.google.com/file/d/1p-3IRMi8Co2snQxNZgqnu5qCmbcW0qxy/view?usp=drivesdk And it won't let me install any of the other variations (of course, this doesn't happen on Windows). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476523] New: Krita correctly displays the colors of an Adobe Photoshop psd file in the thumbnail of recently opened images, but does not display them correctly when the file is opened
https://bugs.kde.org/show_bug.cgi?id=476523 Bug ID: 476523 Summary: Krita correctly displays the colors of an Adobe Photoshop psd file in the thumbnail of recently opened images, but does not display them correctly when the file is opened Classification: Applications Product: krita Version: 5.2.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- In the Krita thumbnail preview of a recently opened image from an Adobe Photoshop psd file, the colors are displayed correctly (see the following screenshot of the preview, note the red colors of the letters "PODC"): https://drive.google.com/file/d/12KoX3vqM_pBQ95vYM4TQ5QL66UUP4Cbg/view?usp=drivesdk But when the image is opened, the colors are incorrect (see the following screenshot of the opened psd file). Note how the red color of the letters "PODC" is displayed in red in the thumbnail, which is correct since it is the original color in Adobe Photoshop, while when opening the file in Krita the red color is changed to blue: https://drive.google.com/file/d/1aVtxF2-u_LsSUfHDoiL0jGbVFXfq4l0_/view?usp=drivesdk I understand that if the colors are showing correctly in the thumbnail of the recently opened image, it means that Krita can correctly interpret the Photoshop psd file, then I understand that it is a bug that it does not do the same when the file is opened. I can send you the original psd file by email so you can see the problem. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #52 from Chema --- > That is strange. It's the bug I originally reported here because I'm having > issues when scaling is less than 100%, not more. I set it to less because my > current laptop top resolution is 1366x768, so things wind up too large. The truth is that, indeed, the example that you mentioned and that opened this bug, was with a percentage less than 100%. Therefore, effectively, to be concise, this bug was not solved in the last update, therefore it should be reopened indicating that it has failed and the one that I opened a few days ago at Nate's indication should be closed since it would be duplicated with this one. But whatever Nage says, whatever he thinks is best for this bug to be solved once and for all, because we've been dealing with it for I don't know how many months... What I think has happened is that the developers have made a bit of a mess with the bug because many other people wrote in it that they had problems when the scaling was greater than 100%. I think that as seen in the comments of the bug, it affected both percentages lower and higher than 100%. So effectively with version 23.08.0 it has been solved for percentages greater than 100%, but it remains for the lower ones... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #50 from Chema --- OK, if anyone is interested, the new bug that has been created for when using Spectacle with fractional scaling less than 100% is 473888. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 473888] New: Spectacle does not capture the screen correctly when using fractional scaling with a value less than 100%
https://bugs.kde.org/show_bug.cgi?id=473888 Bug ID: 473888 Summary: Spectacle does not capture the screen correctly when using fractional scaling with a value less than 100% Classification: Applications Product: Spectacle Version: 23.08.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: rondo...@gmail.com CC: k...@david-redondo.de Target Milestone: --- This bug is a derivation of bug 462860 as there is a case that keeps failing. When fractional scaling is used and this is set to a value less than 100%, using Spectacle to capture the screen produces a strange effect, part of it is resized and some is not, and of course the capture Spectacle does is not correct, nor is the editing of notes in this case. You can see this error in the following two videos: https://drive.google.com/file/d/1oNMH3jLnxXK7ePg8glF6iXBGb4vmYca-/view?usp=sharing https://drive.google.com/file/d/1FJ2aGCJcmKC8p7RMaKtD0md6IxRHQl6d/view?usp=drivesdk My system: Operating System: Manjaro Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.12-lqx1-2-lqx (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 62,2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Micro Computer (HK) Tech Limited Product Name: UM580 Spectacle version: 23.08.0 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #48 from Chema --- (In reply to Altamush Nayyer Khan from comment #47) > The bug appears to be gone for me. > > I have my leftmost monitor at 110%, middle at 150%, and the rightmost at > 125%. > > I haven't marked this solved as some people are still having this bug. Altamush, please, can you try with a scaling less than 100%, for example 95% or 90% and let me know if it works for you? Please note if capturing the screen gives you a strange scaling effect (it happens as if part of the screen is automatically rescaled with another percentage). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #46 from Chema --- (In reply to Ilya Bizyaev from comment #45) > FWIW I have this bug with both monitors set to 125% scaling. I just tested with 125% and for me, with the new version 23.08.0, it works fine. As I say, the problem happens to me when the scaling percentage is less than 100%. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #44 from Chema --- I've been doing more testing on this bug, and I see that it occurs when the scaling percentage is less than 100%. If it's higher than 100%, it seems that Spectacle captures well, but if it's lower than 100% it produces the effect that you can see in the following video that I re-recorded with the latest version of Spectacle (23.08.0) , where you can see again the bug that I mention: https://drive.google.com/file/d/1FJ2aGCJcmKC8p7RMaKtD0md6IxRHQl6d/view?usp=drivesdk -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #43 from Chema --- I just installed the new version of Spectacle, 23.0.8, and although in the release notes it says that this bug is resolved, the same thing is still happening (I just tried with 95% scaling and the exact same error is still happening ). The bug is certainly not fixed. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 --- Comment #39 from Chema --- I'm just writing to say that this bug continues to happen with Spectacle version 23.04.3. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Chema changed: What|Removed |Added CC||rondo...@gmail.com --- Comment #37 from Chema --- I have the same problem. I have the latest version of KDE and Spectacle: Operating System: Manjaro Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.8-4-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 29.3 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: BESSTAR TECH LIMITED Product Name: UM350 Spectacle: 23.04.2 I have recorded a video to my Google Drive so that the problem can be seen. You can see it at the following link, it will be available until this bug is resolved: https://drive.google.com/file/d/1oNMH3jLnxXK7ePg8glF6iXBGb4vmYca-/view?usp=sharing The display is using a resolution of 2560x1440 with a 90% of scaling. Observe how when Spectacle is going to capture a region of the screen, it is automatically rescaled producing a strange effect, and also what is captured is not what is seen on the rescaled screen, it is captured over 90%, not over the one that shown rescaled. Observe how the image captured in Spectacle does not correspond to the one that appears selected in the rescaled region on the screen. On the other hand, when you add annotations to the image, they are also added incorrectly, when you copy the image with the annotations and paste it somewhere else, it looks like the frame I added doesn't appear in the same position as it does in Spectacle . -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467554] When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes
https://bugs.kde.org/show_bug.cgi?id=467554 Chema changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #5 from Chema --- I installed a few days ago the new version KDE 5.27.5, but this problem is still not solved, the same thing happens. Please, I insist on the idea of making a donation so that a developer can buy this device on Amazon and that he can study why it works correctly on Windows and not on KDE, I think it is the fastest and easiest way to an experienced developer can find the cause of the malfunction in KDE. I have already given up hope that this can be fixed in the current version 5.27, but at least so that it can be fixed in the new KDE 6. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467554] When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes
https://bugs.kde.org/show_bug.cgi?id=467554 --- Comment #2 from Chema --- The HDMI EDID emulator is used for 2 functions: 1- If you use a remote control application like AnyDesk or similar, the remote computer must be receiving an HDMI signal for it to work correctly. If the computer stops receiving this signal, for example because you unplug the HDMI cable, the remote control of the computer stops working. If you have both computers plugged into a KVM switch, and from the first computer you want to remote control the second computer using one of these remote control programs, you can't do it without using a hardware emulator like this because when you activate the first computer on the KVM switch computer from which you control the second computer remotely, this remote connection does not work because the second computer stops receiving the HDMI signal (since you are receiving the HDMI signal on the first computer). What the HDMI EDID emulator does is that even if the HDMI cable is unplugged, it emulates the signal as if it continued to reach the computer, so it is believed that it is connected to a monitor and then the remote control works, although the computer does not really is connected to a monitor (or is not receiving the signal from the HDMI cable). But unlike a normal EDID emulator, this one is bi-directional, which allows the HDMI cable to be connected to it and you can quickly switch on the KVM switch to the remote computer and start receiving the HDMI signal from the monitor, just in case there is some problem that cannot be fixed from the remote control. 2- By emulating HDMI resolutions, switching between devices on the KVM switch is almost instantaneous, it only takes 1 or 2 seconds. Without this kind of emulator, switching the display between computers on the KVM switch takes a long time, about 15-20 seconds, because it has to re-receive the HDMI signal, readjust the resolution, etc. while with the HDMI EDID emulator it never loses the signal or the resolution that the equipment had, it is believed that it is always connected to a monitor, so switching between the equipment screens is almost instantaneous. In Windows this hardware works perfectly, allowing me to select any resolution that the system detects. In Linux I am having the problem that of all the resolutions that Wayland detects and offers, only Full HD, 2K and 4K resolutions work, intermediate resolutions do not work with this adapter plugged in, but this does not happen only in KDE, it happens to me also in GNOME, so I think it's more of a bug with the Linux kernel graphic driver that for some reason is not able to work correctly with this hardware. With versions prior to KDE 5.27.3, this hardware worked fine in the resolutions that I have mentioned, with the only problem that when suspending the computer in 4K resolution and turning it on, it did not receive the HDMI signal and you had to change the console by pressing Ctrl + F2, when doing so, it received the HDMI signal again and it was possible to switch to the session with KDE by pressing Ctrl + F1 and everything worked fine (but this problem did not occur in GNOME). But since KDE version 5.27.3 the 4K resolution has stopped working, when I activate it the screen stays black and does not return to the previous resolution even after 1 minute passes, forcing me to change to another console and restart the computer. Please, I don't want to sound selfish with what I'm going to say now, but this connector is only $20 on Amazon, is there any chance that I would donate the money to some KDE developer to buy this hardware so he can carry out the relevant tests? I've been having problems with this connector for more than a year and we haven't found a solution, from here the tests I can do are very limited due to my knowledge of Linux and I think that because of this, it would take a long time to find a solution. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #40 from Chema --- No errors on my end either, in this case a KDE 5.27.3 with Wayland, so the error seems to be fixed. Thanks for your great support. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467554] New: When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes
https://bugs.kde.org/show_bug.cgi?id=467554 Bug ID: 467554 Summary: When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes Classification: Plasma Product: KScreen Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- Created attachment 157408 --> https://bugs.kde.org/attachment.cgi?id=157408=edit Wayland display modes SUMMARY *** When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes *** STEPS TO REPRODUCE 1. Connect a bi-directional HDMI EDID emulator to the computer's HDMI output and connect the monitor's HDMI cable to it (https://www.amazon.com/-/Passthrough-Generrtion-Eliminado-Adaptador-Thunderbolt/dp/B07YMTMMH5?th=1=en_US) 2. Activate 4K resolution (3840x2160) in KDE with Wayland OBSERVED RESULT 1. The screen goes completely black and does not return to the previous resolution after a few seconds even though the new resolution has not been accepted. 2. I open a new console by pressing Ctrl + F2 and from there it tries to return to the KDE session by pressing Ctrl + F1 in an attempt to refresh the HDMI signal, when doing this the computer freezes and the keyboard stops responding . The only solution is to restart the machine by pressing the power button. EXPECTED RESULT It should correctly enable 4K resolution, in version prior to KDE 5.27.3 this worked fine. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.3.0-1-MANJARO (64-bit) --> Tested also with kernel 6.2.7. Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 29,3 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: BESSTAR TECH LIMITED Product Name: UM350 ADDITIONAL INFORMATION In 2K resolution everything works fine, but: - Although Wayland adequately detects all the resolutions offered by the HDMI EDID emulator (see attached screenshot. All resolutions have been tested from Windows and work correctly in this operating system), resolutions greater than 2K (2560x1440) cannot be activated properly, the screen goes black and after a few seconds it returns to the original resolution, which was 2K. - The only resolution greater than 2K that worked was 4K in previous versions of KDE, but now when switching to 4K the problem I mentioned above occurs and the computer ends up freezing. I've been looking at the logs, but I don't see anything, no error indication. Apparently Linux keeps running even though the screen goes black, until at 01:25:45 I am forced to press the power button because the keyboard is no longer responding: mar 19 01:01:01 ComputerM-K CROND[8701]: (root) CMD (run-parts /etc/cron.hourly) mar 19 01:01:01 ComputerM-K anacron[8708]: Anacron started on 2023-03-19 mar 19 01:01:01 ComputerM-K CROND[8700]: (root) CMDEND (run-parts /etc/cron.hourly) mar 19 01:01:01 ComputerM-K anacron[8708]: Normal exit (0 jobs run) mar 19 01:01:11 ComputerM-K NetworkManager[380]: [1679184071.3916] device (wlp2s0): set-hw-addr: set MAC address to 46:3B:11:6A:A9:3A (scanning) mar 19 01:02:36 ComputerM-K plasmashell[676]: QString::arg: 2 argument(s) missing in firefox mar 19 01:02:36 ComputerM-K systemd[527]: Started Firefox - Web Browser. mar 19 01:02:36 ComputerM-K plasmashell[676]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [undefined] to QString mar 19 01:02:37 ComputerM-K plasmashell[8838]: ATTENTION: default value of option mesa_glthread overridden by environment. mar 19 01:02:37 ComputerM-K plasmashell[8838]: ATTENTION: default value of option mesa_glthread overridden by environment. mar 19 01:02:37 ComputerM-K plasmashell[8838]: ATTENTION: default value of option mesa_glthread overridden by environment. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Successfully made thread 8978 of process 8838 owned by '1000' RT at priority 10. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 11 threads of 4 processes of 1 users.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #28 from Chema --- Sorry, not true, the new kernel doesn't fix the Powerdevil problem. Please look at the bug: https://bugs.kde.org/show_bug.cgi?id=466620 Where you can find an explanation of what happened when I did the test and why it worked for me. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost
https://bugs.kde.org/show_bug.cgi?id=466620 --- Comment #17 from Chema --- Sorry, not true, the new kernel doesn't fix the Powerdevil problem... I explain what has happened. I have a bi-directional EDID emulator connected to the HDMI output. This small connector is used to fool the computer into thinking that it is still receiving the HDMI signal from the monitor even if the HDMI cable is disconnected or other computer is active on a KVM switch. It is mainly used with KVM switches since it allows you to switch between computers instantly since it does not have to recover or readapt the video signal on the monitor when you change computers since the EDID emulator has it saved. It also has another function and that is to be able to use the computer with the monitor disconnected for remote control sessions with applications such as VNC, AnyDesk, etc. That's why the test worked for me, because I didn't realize when I did it that I had this little connector connected and then even if I changed the computer on the KVM switch, the Powerdevil continued to detect the HDMI signal and that's why it didn't fail. You can buy one of these plugs, it will solve the problem of the Powerdevil and they are not expensive at all. What is clear with this test is that the failure is in the interruption of the HDMI signal, at the moment it is cut, the Powerdevil crashes. If the EDID emulator is connected and the computer is still receiving a 'ghost' HDMI signal (provided by the EDID emulator), the Powerdevil does not fail and you can switch between computers without problem. What is certain is that with this version of the kernel one of the errors that it had has been fixed. With the version prior to 6.2.2, if the KDE + Wayland computer was suspended while having the bi-directional EDID emulator, switched to the Windows computer, and then went back to the Linux computer and woke it up, the KDE + Wayland session was completely locked and it was impossible to recover it (in X11 it worked fine). After installing kernel 6.2.2 now this problem in Wayland seems to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 Chema changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- Ever confirmed|1 |0 --- Comment #27 from Chema --- As I just wrote in this related bug: https://bugs.kde.org/show_bug.cgi?id=466620 After installing the new kernel 6.2.2 my problems with the Powerdevil on Wayland have disappeared. Please, try yourselves to see if with luck this also solves you. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost
https://bugs.kde.org/show_bug.cgi?id=466620
Chema changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #16 from Chema ---
I have good news! I just installed the new kernel 6.2.2, and with this version
the Powedevil problem is solved, at least for me in Wayland, which was where it
crashed! I hope it works for others too.
Going through the kernel changelog, I can only find these reviews that I see
that may have had something to do with it:
commit 83d403e773a851c9447e4d1847a6f1df91604d43
Author: Stylon Wang
Date: Tue Jan 10 14:38:33 2023 +0800
drm/amd/display: Properly reuse completion structure
commit 0cf8307adbc6beb5ff3b8a76afedc6e4e0b536a9 upstream.
[Why]
Connecting displays to TBT3 docks often produces invalid
replies for DPIA AUX requests. It turns out the completion
structure was not re-initialized before reusing it, resulting
in immature wake up to completion.
[How]
Properly call reinit_completion() on reused completion structure.
Cc: sta...@vger.kernel.org
Reviewed-by: Solomon Chiu
Acked-by: Alan Liu
Signed-off-by: Stylon Wang
Tested-by: Daniel Wheeler
Signed-off-by: Alex Deucher
Cc: "Limonciello, Mario"
Signed-off-by: Greg Kroah-Hartman
commit 9c591e6a027053460b61d63c239df4391fbce98f
Author: Nicholas Kazlauskas
Date: Mon Jan 23 14:59:28 2023 -0500
drm/amd/display: Move DCN314 DOMAIN power control to DMCUB
commit e383b12709e32d6494c948422070c2464b637e44 upstream.
[Why]
DOMAIN power gating control is now required to be done via firmware
due to interlock with other power features. This is to avoid
intermittent issues in the LB memories.
[How]
If the firmware supports the command then use the new firmware as
the sequence can avoid potential display corruption issues.
The command will be ignored on firmware that does not support DOMAIN
power control and the pipes will remain always on - frequent PG cycling
can cause the issue to occur on the old sequence, so we should avoid it.
Reviewed-by: Hansen Dsouza
Acked-by: Qingqing Zhuo
Signed-off-by: Nicholas Kazlauskas
Tested-by: Daniel Wheeler
Signed-off-by: Alex Deucher
Cc: "Limonciello, Mario"
Signed-off-by: Greg Kroah-Hartman
commit 8417e002b7165bdde96ef6af48708ad8de6fe194
Author: Thomas Weißschuh
Date: Mon Feb 20 06:46:12 2023 +
vc_screen: don't clobber return value in vcs_read
commit ae3419fbac845b4d3f3a9fae4cc80c68d82cdf6e upstream.
Commit 226fae124b2d ("vc_screen: move load of struct vc_data pointer in
vcs_read() to avoid UAF") moved the call to vcs_vc() into the loop.
While doing this it also moved the unconditional assignment of
ret = -ENXIO;
This unconditional assignment was valid outside the loop but within it
it clobbers the actual value of ret.
To avoid this only assign "ret = -ENXIO" when actually needed.
[ Also, the 'goto unlock_out" needs to be just a "break", so that it
does the right thing when it exits on later iterations when partial
success has happened - Linus ]
Reported-by: Storm Dragon
Link: https://lore.kernel.org/lkml/y%2fks6vdql2pis...@hotmail.com/
Fixes: 226fae124b2d ("vc_screen: move load of struct vc_data pointer in
vcs_read() to avoid UAF")
Signed-off-by: Thomas Weißschuh
Link:
https://lore.kernel.org/lkml/64981d94-d00c-4b31-9063-43ad0a384...@t-8ch.de/
Signed-off-by: Linus Torvalds
Signed-off-by: Greg Kroah-Hartman
I don't know if any of these fixes could really solve the problem, but it's the
only thing I see that makes any sense related to the Powerdevil problem.
Now I only have to solve the KDE problems with the HDMI, if one day I get
it
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 466623] Unable to display screen if computer starts without HDMI cable connected (or without HDMI signal)
https://bugs.kde.org/show_bug.cgi?id=466623 --- Comment #5 from Chema --- Until a few months ago, when I would suspend the computer with a bi-directional EDID emulator plugged into the HDMI output and wake it up, the screen would go black, but I could switch to another session by pressing Ctrl + F2, which would activate the HDMI, and then I could return to the previous open session by pressing Ctrl + F1 and everything worked fine. The thing is, since kernel 6.2 was released, the situation has gotten worse. When you do this, the session you had open is completely locked with a black screen and it is completely impossible to return to it. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost
https://bugs.kde.org/show_bug.cgi?id=466620 --- Comment #8 from Chema --- Not sure but sounds very similar to my case, Powerdevil works for me too on X11, problem occurs on Wayland when HDMI signal is lost. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466623] Unable to display screen if computer starts without HDMI cable connected (or without HDMI signal)
https://bugs.kde.org/show_bug.cgi?id=466623 --- Comment #3 from Chema --- Sorry, I forgot that Mate and Cinnamon are also based on GTK... So, I don't know the reason for the problem, all I know is that with GNOME (with Wayland), Xfce and Budgie it doesn't give any problem. As I said before, I think it's all about the detection of the HDMI. I've had to switch back to KDE with X11 to mitigate some of these issues. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] powerdevil continues to crash in KScreen::AbstractDpmsHelper::isSupported() when HDMI signal is lost
https://bugs.kde.org/show_bug.cgi?id=466620 Chema changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Chema --- coredumpctl backtrace: PID: 1984 (org_kde_powerde) UID: 1000 (rondo) GID: 1000 (rondo) Signal: 11 (SEGV) Timestamp: Tue 2023-02-28 23:05:34 CET (1 day 4h ago) Command Line: /usr/lib/org_kde_powerdevil Executable: /usr/lib/org_kde_powerdevil Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-powerdevil.service Unit: user@1000.service User Unit: plasma-powerdevil.service Slice: user-1000.slice Owner UID: 1000 (rondo) Boot ID: 1f36683284624ef78d6a3a1b6af2fda9 Machine ID: f894d2e603cd424bb9bcb2d128098414 Hostname: ComputerL Storage: /var/lib/systemd/coredump/core.org_kde_powerde.1000.1f36683284624ef78d6a3a1b6af2fda9.1984.167762193400.zst (present) Size on Disk: 1.2M Message: Process 1984 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 1984: #0 0x7fdffcd3a479 wl_proxy_marshal_array_flags (libwayland-client.so.0 + 0xa479) #1 0x7fdffcd3aafa wl_proxy_marshal_flags (libwayland-client.so.0 + 0xaafa) #2 0x7fdff429af5b n/a (libKF5ScreenDpms.so.8 + 0x6f5b) #3 0x7fdff429b960 n/a (libKF5ScreenDpms.so.8 + 0x7960) #4 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #5 0x7fdff641daef _ZN15QtWaylandClient15QWaylandDisplay19addRegistryListenerEPFvPvP11wl_registryjRK7QStringjES1_ (libQt5WaylandClient.so.5 + 0x74aef) #6 0x7fdff643b760 _ZN23QWaylandClientExtension19addRegistryListenerEv (libQt5WaylandClient.so.5 + 0x92760) #7 0x7fdffc09d51e _ZNK11QMetaMethod6invokeEP7QObjectN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS5_S5_S5_S5_S5_S5_S5_S5_S5_ (libQt5Core.so.5 + 0x29d51e) #8 0x7fdffc09df10 _ZN11QMetaObject12invokeMethodEP7QObjectPKcN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS7_S7_S7_S7_S7_S7_S7_S7_S7_ (libQt5Core.so.5 + 0x29df10) #9 0x7fdff429ad8c n/a (libKF5ScreenDpms.so.8 + 0x6d8c) #10 0x7fdff429c928 _ZNK7KScreen4Dpms11isSupportedEv (libKF5ScreenDpms.so.8 + 0x8928) #11 0x7fdffcce4d70 _ZN10PowerDevil10ActionPool4initEPNS_4CoreE (libpowerdevilcore.so.2 + 0x12d70) #12 0x7fdffcceca9d _ZN10PowerDevil4Core14onBackendReadyEv (libpowerdevilcore.so.2 + 0x1aa9d) #13 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #14 0x7fdff556735b _ZN23PowerDevilUPowerBackend18initWithBrightnessEb (powerdevilupowerbackend.so + 0x1135b) #15 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #16 0x7fdff555e414 _ZN23PowerDevilUPowerBackend24brightnessSupportQueriedEb (powerdevilupowerbackend.so + 0x8414) #17 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #18 0x7fdffcb6d43a _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x5a43a) #19 0x7fdffcb7354c _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x6054c) #20 0x7fdffc0bea71 n/a (libQt5Core.so.5 + 0x2bea71) #21 0x7fdff557f785 n/a (kauth_helper_plugin.so + 0xa785) #22 0x7fdff557fe91 n/a (kauth_helper_plugin.so + 0xae91) #23 0x7fdffcaf445f n/a (libQt5DBus.so.5 + 0x6145f) #24 0x7fdffc0b1bb0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1bb0) #25 0x7fdffc08df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48) #26 0x7fdffc08ea53 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x28ea53) #27 0x7fdffc0d4e88 n/a (libQt5Core.so.5 + 0x2d4e88) #28 0x7fdffad1682b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b) #29 0x7fdffad6dcc9 n/a (libglib-2.0.so.0 + 0xaccc9) #30 0x7fdffad150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #31 0x7fdffc0d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #32 0x7fdffc0866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #33 0x7fdffc091219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #34 0x563ded70c55b n/a (org_kde_powerdevil + 0x655b) #35 0x7fdffb83c790 n/a (libc.so.6 + 0x23790) #36
[KScreen] [Bug 466623] Unable to display screen if computer starts without HDMI cable connected (or without HDMI signal)
https://bugs.kde.org/show_bug.cgi?id=466623 Chema changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Chema --- As far as I can remember, since I started using KDE a couple of years ago, I don't really remember what version it was back then, I think it was 5.25 but I'm not sure, this problem has always happened, so I don't think be a regression error (at least, since I've been using it, obviously I can't know the previous versions). All I can say is that if I try other desktops, like GNOME or Xfce, this problem doesn't happen with them, it only happens with KDE. I don't know if it only happens to me, but from the beginning I think that KDE has a serious problem with the detection of HDMI on my computer: - If I boot the computer and it does not receive an HDMI signal while the system boots and the KDE login screen loads, there is no way for that session to recover the HDMI signal, the screen stays completely black. - If with the computer turned on I change the KVM switch to another computer, even if KDE only loses the HDMI signal for a couple of seconds, when returning to KDE the Powerdevil has crashed. - If I have a bi-directional EDID emulator connected to the HDMI output and I switch to another computer on the KVM switch and then come back to KDE, the session hangs with a black screen and there is no way to recover that session. I don't think it's a KDE-only problem, I think more of a QT problem, since Xfce and Gnome (based in GTK) don't have any of these problems, while Mate and Cinnamon do some (but not all) of them. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working).
https://bugs.kde.org/show_bug.cgi?id=466620 --- Comment #2 from Chema --- Created attachment 156840 --> https://bugs.kde.org/attachment.cgi?id=156840=edit Powerdevil error log 2 I have done more tests and I have a news about this: it is not necessary to wait 15 minutes, as soon as KDE loses the HDMI signal, either by disconnecting the HDMI cable or by activating another computer on the KVM swtich, the error occurs from Powerdevil and power management stops working. I attach another log with this case, the crash starts at line 900: 28/2/23 23:07 systemd-coredumpProcess 3736 (org_kde_powerde) of user 1000 dumped core. Stack trace of thread 3736: #0 0x7f6d3cea08ec n/a (libc.so.6 + 0x878ec) #1 0x7f6d3ce51ea8 raise (libc.so.6 + 0x38ea8) #2 0x7f6d3e3e637c _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x737c) #3 0x7f6d3ce51f50 n/a (libc.so.6 + 0x38f50) #4 0x7f6d3e405479 wl_proxy_marshal_array_flags (libwayland-client.so.0 + 0xa479) #5 0x7f6d3e405afa wl_proxy_marshal_flags (libwayland-client.so.0 + 0xaafa) #6 0x7f6d34161f5b n/a (libKF5ScreenDpms.so.8 + 0x6f5b) #7 0x7f6d34162960 n/a (libKF5ScreenDpms.so.8 + 0x7960) #8 0x7f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #9 0x7f6d37524aef _ZN15QtWaylandClient15QWaylandDisplay19addRegistryListenerEPFvPvP11wl_registryjRK7QStringjES1_ (libQt5WaylandClient.so.5 + 0x74aef) #10 0x7f6d37542760 _ZN23QWaylandClientExtension19addRegistryListenerEv (libQt5WaylandClient.so.5 + 0x92760) #11 0x7f6d3d69d51e _ZNK11QMetaMethod6invokeEP7QObjectN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS5_S5_S5_S5_S5_S5_S5_S5_S5_ (libQt5Core.so.5 + 0x29d51e) #12 0x7f6d3d69df10 _ZN11QMetaObject12invokeMethodEP7QObjectPKcN2Qt14ConnectionTypeE22QGenericReturnArgument16QGenericArgumentS7_S7_S7_S7_S7_S7_S7_S7_S7_ (libQt5Core.so.5 + 0x29df10) #13 0x7f6d34161d8c n/a (libKF5ScreenDpms.so.8 + 0x6d8c) #14 0x7f6d34163928 _ZNK7KScreen4Dpms11isSupportedEv (libKF5ScreenDpms.so.8 + 0x8928) #15 0x7f6d3e3afd70 _ZN10PowerDevil10ActionPool4initEPNS_4CoreE (libpowerdevilcore.so.2 + 0x12d70) #16 0x7f6d3e3b7a9d _ZN10PowerDevil4Core14onBackendReadyEv (libpowerdevilcore.so.2 + 0x1aa9d) #17 0x7f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #18 0x7f6d36c2f35b _ZN23PowerDevilUPowerBackend18initWithBrightnessEb (powerdevilupowerbackend.so + 0x1135b) #19 0x7f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #20 0x7f6d36c26414 _ZN23PowerDevilUPowerBackend24brightnessSupportQueriedEb (powerdevilupowerbackend.so + 0x8414) #21 0x7f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #22 0x7f6d3e23843a _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x5a43a) #23 0x7f6d3e23e54c _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x6054c) #24 0x7f6d3d6bea71 n/a (libQt5Core.so.5 + 0x2bea71) #25 0x7f6d3805a785 n/a (kauth_helper_plugin.so + 0xa785) #26 0x7f6d3805ae91 n/a (kauth_helper_plugin.so + 0xae91) #27 0x7f6d3e1bf45f n/a (libQt5DBus.so.5 + 0x6145f) #28 0x7f6d3d6b1bb0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2b1bb0) #29 0x7f6d3d68df48 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28df48) #30 0x7f6d3d68ea53 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x28ea53) #31 0x7f6d3d6d4e88 n/a (libQt5Core.so.5 + 0x2d4e88) #32 0x7f6d3c11682b g_main_context_dispatch (libglib-2.0.so.0 + 0x5582b) #33 0x7f6d3c16dcc9 n/a (libglib-2.0.so.0 + 0xaccc9) #34 0x7f6d3c1150e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2) #35 0x7f6d3d6d8c6c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d8c6c) #36 0x7f6d3d6866ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2866ec) #37 0x7f6d3d691219 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x291219) #38 0x55eb4210055b n/a (org_kde_powerdevil + 0x655b) #39 0x7f6d3ce3c790 n/a (libc.so.6 + 0x23790) #40 0x7f6d3ce3c84a __libc_start_main (libc.so.6 + 0x2384a) #41 0x55eb42101095 n/a (org_kde_powerdevil + 0x7095) Stack trace of thread 3738: #0 0x7f6d3ce9b9a0 n/a (libc.so.6 + 0x829a0) #1 0x7f6d3cea1ea2 pthread_mutex_lock (libc.so.6 + 0x88ea2) #2 0x7f6d3e403635 wl_display_read_events (libwayland-client.so.0 + 0x8635) #3 0x7f6d37522d3d n/a (libQt5WaylandClient.so.5 + 0x72d3d) #4 0x7f6d3d4e432a n/a (libQt5Core.so.5 + 0xe432a) #5 0x7f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5) #6 0x7f6d3cf20d90 n/a (libc.so.6 + 0x107d90) Stack trace of thread 3739: #0 0x7f6d3ce9b9a0 n/a (libc.so.6 + 0x829a0) #1 0x7f6d3cea1ea2 pthread_mutex_lock (libc.so.6 + 0x88ea2) #2 0x7f6d3e403635 wl_display_read_events (libwayland-client.so.0 + 0x8635) #3 0x7f6d37522d3d n/a (libQt5WaylandClient.so.5 + 0x72d3d) #4 0x7f6d3d4e432a n/a (libQt5Core.so.5 + 0xe432a) #5 0x7f6d3ce9ebb5 n/a (libc.so.6 + 0x85bb5)
[Powerdevil] [Bug 466620] The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working).
https://bugs.kde.org/show_bug.cgi?id=466620 --- Comment #1 from Chema --- Tested that this error does not occur with GNOME. I have made the same combinations that I have indicated above and in all cases in GNOME the power management has worked perfectly, with or without an HDMI cable connected or without an HDMI signal through the KVM switch. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466623] New: Unable to display screen if computer starts without HDMI cable connected (or without HDMI signal)
https://bugs.kde.org/show_bug.cgi?id=466623 Bug ID: 466623 Summary: Unable to display screen if computer starts without HDMI cable connected (or without HDMI signal) Classification: Plasma Product: KScreen Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- Created attachment 156839 --> https://bugs.kde.org/attachment.cgi?id=156839=edit Log when black screen SUMMARY *** If the computer is booted without HDMI signal (disconnecting the HDMI cable or having another computer active on a KVM switch), then when connecting the computer's HDMI cable or turning on the computer on the KVM switch, the screen looks completely black and it is not possible to recover the signal. Pressing Ctrl + F2 activates the HDMI signal and you can access another console and from there start X11 with KDE, but it is completely impossible to recover the screen in the first session (Ctrl + F1). *** STEPS TO REPRODUCE Test 1: with KVM switch (IMPORTANT: without it having EDID emulation) 1. With computer 1 active on the KVM switch, turn on computer 2 that has Linux. 2. Wait a few minutes for the system to load completely and the KDE login screen to appear. 3. Switch control on the KVM switch to the Linux computer. 4. The screen is completely black and there is no way to recover the HDMI signal in that session. Test 2: no KVM switch 1. Disconnect the HDMI cable from the computer. 2. Boot the computer with Linux. 3. Wait a few minutes for the system to load completely and the KDE login screen to appear. 4. Connect the HDMI cable to the computer. 5. The screen is completely black and there is no way to recover the HDMI signal in that session. Attached log in case you can see something. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-x64v3-xanmod1 (64-bit) Graphics Platform: X11 --> It indicates the session that I managed to start from another console, but I don't know the KDE login screen if it is on X11 or Wayland, which is what was displayed when the screen fails, showing black after connecting the HDMI cable. Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 29,3 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: BESSTAR TECH LIMITED Product Name: UM350 Tested that this error does not occur with GNOME. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466620] New: The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working).
https://bugs.kde.org/show_bug.cgi?id=466620 Bug ID: 466620 Summary: The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working). Classification: Plasma Product: Powerdevil Version: 5.27.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rondo...@gmail.com CC: m...@ratijas.tk Target Milestone: --- Created attachment 156838 --> https://bugs.kde.org/attachment.cgi?id=156838=edit Powerdevil error log SUMMARY *** The bug I reported a few days ago with Powerdevil continues to occur (power management options stop working). *** STEPS TO REPRODUCE After installing KDE 5.27.2 I see that the error with Powerdevil continues to occur. I have done some more testing and have been able to pinpoint a bit more when the problem occurs. The bug is independent of the installed kernel version, contrary to what I reported at first. I see that the failure occurs when the computer loses the HDMI signal for a period of about 15 minutes. I don't mean just the monitor turning off, I mean completely losing the signal to the monitor by unplugging the cable (or switching the active computer on a KVM switch, which would be the same result). I have done 2 tests. Test 1: 1. Having two computers connected to a KVM switch (IMPORTANT: without it having EDID emulation). 2. Boot computer 1 with Linux. Logging in KDE. 3. Now through the KVM switch, pass control to computer 2, in such a way that computer 1 loses the HDMI signal. 4. Wait around 15 minutes. 5. Return control now to computer 1. 6. Go to the power management option in Settings. Now the following error will be displayed: "Power Management configuration module could not be loaded. The Power Management Service appears not to be running". Test 2: (without KVM switch) 1. Boot the computer with Linux. Logging in KDE. 2. Disconnect the HDMI cable from the computer. 3. Wait around 15 minutes. 4. Reconnect the HDMI cable to the computer. 6. Go to the power management option in Settings. Now the following error will be displayed: "Power Management configuration module could not be loaded. The Power Management Service appears not to be running". Looking at the logs in KSystemLog (which I attached), I see that it is leaving this error related to Power Management: 2/28/23 20:12 systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" 2/28/23 20:12 systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" 2/28/23 20:12 systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-x64v3-xanmod1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 29,3 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: BESSTAR TECH LIMITED Product Name: UM350 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #21 from Chema --- Sorry, I think I didn't take a good look at the logs before. I don't understand now what is happening, I don't think any KDE component has been updated today. Right now it's also failing me with Kernel 6.1.13 when it didn't fail before, I don't understand it... I have reviewed the logs and I see that it is effectively leaving the same log as in Kernel 6.2. What I don't understand is why this started to fail when a couple of days ago it worked perfectly... Anyway, I'm waiting for KDE 5.27.2 to see if the bug is fixed with the change you've made. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #19 from Chema --- Reviewing the KSystemLog log with Kernel 6.1.14, I see that the error it is giving now is not the same as the one with Kernel 6.2, now it is leaving the following error when trying to access the power management configuration: 26/2/23 0:37systemsettings Failed to query platform profile choices "The name org.kde.Solid.PowerManagement was not provided by any .service files" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 --- Comment #18 from Chema --- I know this bug is marked as fixed, but I wanted to point it out, because it has come to my attention, that with the new Linux Kernel 6.1.14 that has just been released, Powerdevil has also started to crash as it was in version 6.2 (also tested with version 6.2.1 and it continues to fail), I am commenting on it because I found it interesting to note that with previous versions of 6.1 (tested up to 6.1.13) this problem did not occur, in case this could give some other important information. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466371] New: The taskbar randomly disappears and then automatically restarts several times throughout the day when you mouse over the taskbar icons
https://bugs.kde.org/show_bug.cgi?id=466371 Bug ID: 466371 Summary: The taskbar randomly disappears and then automatically restarts several times throughout the day when you mouse over the taskbar icons Classification: Plasma Product: plasmashell Version: 5.27.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: rondo...@gmail.com Target Milestone: 1.0 Created attachment 156686 --> https://bugs.kde.org/attachment.cgi?id=156686=edit Log of the error obtained in KSystemLog SUMMARY *** The taskbar randomly disappears and then automatically restarts several times throughout the day when you mouse over the taskbar icons *** STEPS TO REPRODUCE I can't say a safe way to reproduce the problem since as I say, it happens randomly sometimes, but the problem happens when you hover the mouse pointer over some icon on the taskbar OBSERVED RESULT The taskbar disappears and then reloads automatically EXPECTED RESULT The taskbar should not disappear when you hover the mouse pointer over one of its icons SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.13-x64v3-xanmod1 (64-bit) --> Tested also with standard 6.1.13 and 6.2 Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 29,3 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: BESSTAR TECH LIMITED Product Name: UM350 ADDITIONAL INFORMATION This error began to occur after updating to one of the versions published in the last two years, before this error did not occur. I have tried from KDE 5.27.1 with a session in Wayland and with Linux Kernel 6.1.13 and 6.2, and in both cases the same thing happens. I haven't tested much with X11, but in this environment the time I've tested it seems to work fine, so the problem seems to only occur on Wayland. I attach the log file obtained with KSystemLog. The error I believe occurs at line 964: 24/2/23 20:09 kwin_wayland_wrappererror in client communication (pid 819) 24/2/23 20:09 plasmashell wl_display@1: error 1: invalid method 1, object zkde_screencast_stream_unstable_v1@137 24/2/23 20:09 plasmashell The Wayland connection experienced a fatal error: Invalid argument 24/2/23 20:09 plasmashell The Wayland connection experienced a fatal error: Invalid argument 24/2/23 20:09 systemd plasma-plasmashell.service: Main process exited, code=exited, status=1/FAILURE 24/2/23 20:09 systemd plasma-plasmashell.service: Failed with result 'exit-code'. 24/2/23 20:09 systemd plasma-plasmashell.service: Consumed 23.097s CPU time. 24/2/23 20:09 systemd plasma-plasmashell.service: Scheduled restart job, restart counter is at 1. 24/2/23 20:09 systemd Stopped KDE Plasma Workspace. 24/2/23 20:09 systemd plasma-plasmashell.service: Consumed 23.097s CPU time. 24/2/23 20:09 systemd Starting KDE Plasma Workspace... 24/2/23 20:09 plasmashell Checking screens: available: (QScreen(0x56260f5d5ca0, name="HDMI-A-1")) redundant: QHash() fake: QSet() all: (QScreen(0x56260f5d5ca0, name="HDMI-A-1")) 24/2/23 20:09 systemd Started KDE Plasma Workspace. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466191] A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working
https://bugs.kde.org/show_bug.cgi?id=466191 --- Comment #4 from Chema --- I've been doing some tests this afternoon and I can confirm that it doesn't happen with X11, that is, in KDE 5.27.1 + Linux Kernel 6.2 + X11, Powerdevil works fine. Therefore, the problem is in the conjunction KDE 5.27.1 + Linux Kernel 6.2 + Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466191] A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working
https://bugs.kde.org/show_bug.cgi?id=466191 Chema changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466191] A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working
https://bugs.kde.org/show_bug.cgi?id=466191 --- Comment #3 from Chema --- Created attachment 156626 --> https://bugs.kde.org/attachment.cgi?id=156626=edit Powerdevil crash log in KSystemLog I have been with the computer on for a while until I have seen that the problem has occurred, I am attaching here the log that the KSystemLog application shows, in it you can see some problems with Powerdevil, especially a crash that begins at line 651 and that it is repeated later, it seems that because it cannot restart this service correctly. I want to point out that logging starts at 00:28, which is when KDE logs in, and Powerdevil crashes at 00:40 for no apparent reason, that is, 12 minutes after KDE login. Also comment that a couple of hours ago I downloaded Powerdevil 2.57.1-2 in Manjaro, but the error keeps happening with this version. And also comment, although it will be seen in the logs, that I am using Wayland (I forgot to comment it before). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466191] A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working
https://bugs.kde.org/show_bug.cgi?id=466191 --- Comment #1 from Chema --- I add a little more information. When the power management settings stopped working in KDE, I tried running the following lines from a Konsole, in case the upowerd daemon stopped or terminated unexpectedly: systemctl enable --now upower.service and systemctl start upower But neither has worked, the only way to get the power management settings working again is by logging out of KDE and logging back into a new session, until after a few minutes it stops working again. I also want to point out that, although the power management settings in KDE stop working, and therefore the scheduler sleep mode does not work, putting the computer to sleep by pressing the "Sleep" option in KDE does work perfectly, as well as then wake up the computer. My computer has 32 GB of RAM and an AMD Ryzen 5 3550H chip, it is a mini PC, a Minisforum DeskMini UM350 that is usually sold with Manjaro Linux installed. As I said before, with Linux Kernel 6.1.12 it works perfectly, it looks like a conjunction of KDE + the new Linux Kernel 6.2. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466191] New: A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working
https://bugs.kde.org/show_bug.cgi?id=466191 Bug ID: 466191 Summary: A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working Classification: Plasma Product: Powerdevil Version: 5.27.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rondo...@gmail.com CC: m...@ratijas.tk Target Milestone: --- Created attachment 156566 --> https://bugs.kde.org/attachment.cgi?id=156566=edit Screenshot of Power Management configuration error SUMMARY A few minutes after the computer is active in a KDE 5.27 session with Linux Kernel 6.2 on Manjaro, the power management settings stop working. STEPS TO REPRODUCE 1- Get into KDE 5.27 with Linux Kernel 6.2 in Manjaro. 2- Go to System Settings --> Power Management, it show all options correctly. 3- Now wait a few minutes with the computer on (5 or 10 minutes). 4- Go to System Settings --> Power Management, it shows the following error attached in the screenshot: "Power Management configuration module could not be loaded. The Power Management Service appears not to be running." OBSERVED RESULT As I just indicated above, it shows an error message indicating that the Power Management Service is not running, and indeed the computer's automatic sleep mode no longer works. And now if I run the following line in a Konsole: ps -e | grep upower I get the following result: 550? 00:00:00 upowerd Which I don't know if it actually indicates if the daemon is running or not. If I then log out of the KDE session and log back in, the power management settings work again until, after a few minutes, they stop working again. EXPECTED RESULT Of course, the power management settings should work fine, just like they do with Linux Kernel 6.1.12, and not stop working after a few minutes after the computer is turned on. I want to point out that it doesn't seem like just a KDE problem, since KDE 5.27 with Linux Kernel 6.1.12 works perfectly, but it seems like a conjunction of KDE with the new Linux Kernel 6.2. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE with Linux Kernel 6.2 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453557] Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected
https://bugs.kde.org/show_bug.cgi?id=453557 --- Comment #8 from Chema --- In that case, I'll wait for version 5.27 to see if that change solves this problem and the other problem with the HDMI bidirectional emulator. If it still doesn't work, I'll resend the logs. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453557] Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected
https://bugs.kde.org/show_bug.cgi?id=453557 --- Comment #6 from Chema --- Hi, I have performed the test again executing the command that you have indicated in the terminal, but the result is the same, when the computer goes into sleep mode, when it is woken up the screen stays black until you press Ctrl + F1 to change session in Linux, then the HDMI signal is recovered. I am not using two monitors, nor am I using a laptop, I only have one monitor plugged into a KVM switch to which I have another 2 mini pc plugged, one with Windows and the other with Linux, and I have the HDMI emulator plugged into them so that the screen switching between machines is instantaneous. However, I have also carried out the test connecting only the monitor cable directly to the computer, which has the HDMI emulator connected (I mean, without using the KVM switch) and the result is the same as indicated above. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #15 from Chema --- Hi, I'm sorry it's taking so long to respond, but on the one hand I've been very busy these weeks and on the other hand to be able to test the bug I had to reinstall the KVM switch that was causing the problem (in the end, after searching and searching on Amazon and trying several models, I found one where the problem did not occur). Well, I ran the test again, and the result is still the same: when I switch to Windows PC, the switch is quite fast. But when I switch from it to the Linux computer which has the latest version of KDE (at the moment I have KDE Plasma 5.26.4 and Linux kernel 6.1rc8), the monitor stops receiving the signal and goes dark for about 1 minute, until it gets it back magically. Also, when the screen recovers, the applications that were open have remained frozen, they do not respond, you have to minimize them and then they refresh and you can continue using them. I don't know if it could be related, but a while ago I also opened a bug for something similar (Bug 453557), if you use a bidirectional HDMI emulator (https://www.amazon.com/EVanlak-Passthrough-Generrtion-Eliminated-Thunderbolt /dp/B07YMTMMH5) with a KVM switch to make switching between screens instant, works fine in KDE except when you put the computer to sleep, when you wake it up the screen doesn't react, it goes black, you have to press Ctrl + F1 to switch sessions in Linux, then the screen reacts and you can go back to KDE by pressing Ctrl + F2. The curious thing about these two problems is that, as I already mentioned at the time, this does not happen with the GNOME desktop using Wayland. Regards. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459038] When the active KDE session loses the HDMI signal, it is no longer possible to re-enter it, having to reboot the machine or opening another console session with Ctrl + (F1, F2,
https://bugs.kde.org/show_bug.cgi?id=459038 Chema changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Chema --- After detecting that at the initial session in KDE some flickering pixels appeared on the screen, I proceeded to tighten the HDMI connectors and this seems to have solved the problem. Sorry for the inconvenience, false alarm. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459038] When the active KDE session loses the HDMI signal, it is no longer possible to re-enter it, having to reboot the machine or opening another console session with Ctrl + (F1, F2,
https://bugs.kde.org/show_bug.cgi?id=459038 --- Comment #1 from Chema --- Sorry, I forgot to mention that this happens indifferently in both Wayland and X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459038] New: When the active KDE session loses the HDMI signal, it is no longer possible to re-enter it, having to reboot the machine or opening another console session with Ctrl + (F1,
https://bugs.kde.org/show_bug.cgi?id=459038 Bug ID: 459038 Summary: When the active KDE session loses the HDMI signal, it is no longer possible to re-enter it, having to reboot the machine or opening another console session with Ctrl + (F1, F2, F3...) Product: KScreen Version: 5.25.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- SUMMARY *** After installing the latest KDE updates (I work with the unstable branch of Manjaro), when the active KDE session loses the HDMI signal, either because the session is switched by pressing Ctrl + (F1, F2, F3...), the monitor enters standby mode or because the signal is changed with a KVM switch, it is completely impossible to be able to recover the KDE session again, when it receives the HDMI signal again when changing back to the session by pressing Ctrl + (F1, F2, F3...), when leaving the monitor from standby or changing the signal to the computer with Linux on the KVM switch, the screen stays completely black and does not show the unlock screen, forcing you to open another console session with Ctrl + (F1, F2, F3...) to open another KDE session or directly being forced to restart the machine. Please, this error is serious, I can't work this way, every time the monitor goes into standby mode because I get up to have a coffee or do something, when I come back I am forced to restart the machine, losing all my work that I have open. *** STEPS TO REPRODUCE 1. Switch to another console by pressing Ctrl + (F1, F2, F3...), waiting for the monitor to standby mode or switch to another machine via a KVM switch, anything that causes the current KDE session to lose HDMI signal 2. Trying to go back to the previous KDE session by pressing Ctrl + (F1, F2, F3...), moving the mouse to bring the monitor out of standby mode, or switching to the previous Linux machine via a KVM switch, anything that wakes up the HDMI signal in the previous KDE session. OBSERVED RESULT Then you will see that the KDE session does not react and the screen remains completely black, not being able to enter it again and being forced to restart the machine or open another console by pressing Ctrl + (F1, F2, F3...). EXPECTED RESULT Prior to installing the latest KDE updates, it would display the unlock screen without issue and allow you to re-login to KDE. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma working with unstable branch (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Tested with kernels 5.19.8-1 and 6.0.0rc5-1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #12 from Chema --- Hi Zamundaaa, I just uploaded the drm debug log with the other option that you have indicated in a 7z compressed file since the file occupies 5.5 MB and I cannot upload it directly here as it has a 4 MB limit. Regards. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #11 from Chema --- Created attachment 149469 --> https://bugs.kde.org/attachment.cgi?id=149469=edit drm debug 2 This is the drm debug with option "echo 0xFF | sudo tee /sys/module/drm/parameters/debug" -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #9 from Chema --- Hi Zamundaaa, I just uploaded the drm-debug.log, I hope I executed correctly the instructions you told me. Regards. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #8 from Chema --- Created attachment 149269 --> https://bugs.kde.org/attachment.cgi?id=149269=edit drm-debug log -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #6 from Chema --- Hi Zamundaaa, I just uploaded the log executing the instruction you told me. As you can see in it, it starts at 19:10:44 and ends at 19:12:39, which means that it took almost 2 minutes to perform all the operations that generated the log. Regards. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #5 from Chema --- Created attachment 149268 --> https://bugs.kde.org/attachment.cgi?id=149268=edit Wayland log for KVM switch -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #3 from Chema --- Hi, I enclose the log obtained from an X11 session so that you can compare the times with that of the session in Wayland, as you can see in an X11 session it is much faster. For this test: - I switched to another computer at 08:45. - I returned to the Linux computer at 08:47. -- may 27 08:47:36 ComputerM dbus-daemon[963]: [session uid=1000 pid=963] Activating via systemd: service name='org.f> may 27 08:47:36 ComputerM systemd[941]: Starting Xdg Desktop Portal For KDE... may 27 08:47:36 ComputerM dbus-daemon[963]: [session uid=1000 pid=963] Successfully activated service 'org.freedes> may 27 08:47:36 ComputerM systemd[941]: Started Xdg Desktop Portal For KDE. may 27 08:47:36 ComputerM xdg-desktop-portal-kde[5581]: xdp-kde: Desktop portal registered successfully may 27 08:47:36 ComputerM xdg-desktop-portal-kde[5581]: qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequ> may 27 08:47:36 ComputerM xdg-desktop-portal-kde[5581]: xdp-kde-background: GetAppState called: no parameters may 27 08:47:37 ComputerM kernel: usb 1-3: new high-speed USB device number 16 using xhci_hcd may 27 08:47:37 ComputerM kernel: usb 1-3: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 may 27 08:47:37 ComputerM kernel: usb 1-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 may 27 08:47:37 ComputerM kernel: usb 1-3: Product: USB 2.0 Hub may 27 08:47:37 ComputerM kernel: hub 1-3:1.0: USB hub found may 27 08:47:37 ComputerM kernel: hub 1-3:1.0: 4 ports detected may 27 08:47:37 ComputerM kernel: usb 1-3.1: new full-speed USB device number 17 using xhci_hcd may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: RRNotify_OutputChange may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Timestamp: 4004143 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Output: 82 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: CRTC: 0 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Mode: 0 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Rotation: "Rotate_0" may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Connection: "Connected" may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Subpixel Order: 0 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xrandr: XRandROutput 82 update m_connected: 1 m_crtc QObject(0x0) CRTC: 0 MODE: 0 Connection: 0 Primary: false may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xrandr: Output 82 : connected = true , enabled => may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: RRScreenChangeNotify may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Timestamp: 4004143 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Config_timestamp: 4111952 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Window: 58720261 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Root: 1735 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Rotation: "Rotate_0" may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Size ID: 65535 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Size: 3840 2160 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: SizeMM: 956 537 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: RRNotify_OutputChange may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Timestamp: 4004143 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Output: 82 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: CRTC: 0 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Mode: 0 may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Rotation: "Rotate_0" may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xcb.helper: Connection: "Connected" may 27 08:47:37 ComputerM kscreen_backend_launcher[5272]: kscreen.xc
[KScreen] [Bug 454387] HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 --- Comment #2 from Chema --- Hi, I have tried to execute the line that you have indicated after adding the line in the etc/environment and after reproducing the error again: journalctl --boot 0 --user-unit plasma-kwin_wayland | grep kwin_wayland_drm But it does not return any result from the terminal. However, I have found something that may be interesting. I did the following test: - I switched on the KVM switch to another computer at 07:48. - I returned to the Manjaro Linux KDE Wayland computer at 07:50. After executing this line: journalctl --since today And looking at the lines that start at 07:50, which is when I changed the switch to the Linux machine, I see the following (I attach the log): -- may 27 07:50:24 ComputerM kernel: usb 1-3: new high-speed USB device number 13 using xhci_hcd may 27 07:50:24 ComputerM kernel: usb 1-3: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 may 27 07:50:24 ComputerM kernel: usb 1-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 may 27 07:50:24 ComputerM kernel: usb 1-3: Product: USB 2.0 Hub may 27 07:50:25 ComputerM kernel: hub 1-3:1.0: USB hub found may 27 07:50:25 ComputerM kernel: hub 1-3:1.0: 4 ports detected may 27 07:50:25 ComputerM kernel: usb 1-3.1: new full-speed USB device number 14 using xhci_hcd may 27 07:50:25 ComputerM kernel: usb 1-3.1: New USB device found, idVendor=145f, idProduct=02be, bcdDevice= 1.00 may 27 07:50:25 ComputerM kernel: usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 may 27 07:50:25 ComputerM kernel: usb 1-3.1: Product: Trust OpticalMouse may 27 07:50:25 ComputerM kernel: usb 1-3.1: Manufacturer: PixArt may 27 07:50:25 ComputerM kernel: input: PixArt Trust OpticalMouse as /devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.1/1-3.1:1.0/0003:145F:02BE.0011/input/input32 may 27 07:50:25 ComputerM kernel: hid-generic 0003:145F:02BE.0011: input,hidraw0: USB HID v1.11 Mouse [PixArt Trust OpticalMouse] on usb-:04:00.3-3.1/input0 may 27 07:50:25 ComputerM kernel: input: PixArt Trust OpticalMouse Keyboard as /devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.1/1-3.1:1.1/0003:145F:02BE.0012/input/input34 may 27 07:50:25 ComputerM kernel: hid-generic 0003:145F:02BE.0012: input,hiddev96,hidraw1: USB HID v1.11 Keyboard [PixArt Trust OpticalMouse] on usb-:04:00.3-3.1/input1 may 27 07:50:25 ComputerM kernel: usb 1-3.4: new low-speed USB device number 15 using xhci_hcd may 27 07:50:26 ComputerM kernel: usb 1-3.4: New USB device found, idVendor=145f, idProduct=02c9, bcdDevice= 1.01 may 27 07:50:26 ComputerM kernel: usb 1-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 may 27 07:50:26 ComputerM kernel: usb 1-3.4: Product: Trust Keyboard may 27 07:50:26 ComputerM kernel: usb 1-3.4: Manufacturer: SIGMACHIP may 27 07:50:26 ComputerM kernel: input: SIGMACHIP Trust Keyboard as /devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.4/1-3.4:1.0/0003:145F:02C9.0013/input/input35 may 27 07:50:26 ComputerM kernel: hid-generic 0003:145F:02C9.0013: input,hidraw2: USB HID v1.10 Keyboard [SIGMACHIP Trust Keyboard] on usb-:04:00.3-3.4/input0 may 27 07:50:26 ComputerM kernel: input: SIGMACHIP Trust Keyboard Consumer Control as /devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.4/1-3.4:1.1/0003:145F:02C9.0014/input/input36 may 27 07:50:26 ComputerM kernel: input: SIGMACHIP Trust Keyboard System Control as /devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.4/1-3.4:1.1/0003:145F:02C9.0014/input/input37 may 27 07:50:26 ComputerM kernel: hid-generic 0003:145F:02C9.0014: input,hidraw4: USB HID v1.10 Device [SIGMACHIP Trust Keyboard] on usb-:04:00.3-3.4/input1 may 27 07:50:26 ComputerM mtp-probe[2695]: checking bus 1, device 14: "/sys/devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.1" may 27 07:50:26 ComputerM mtp-probe[2696]: checking bus 1, device 15: "/sys/devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.4" may 27 07:50:26 ComputerM mtp-probe[2695]: bus: 1, device: 14 was not an MTP device may 27 07:50:26 ComputerM mtp-probe[2696]: bus: 1, device: 15 was not an MTP device may 27 07:50:26 ComputerM systemd-logind[579]: Watching system buttons on /dev/input/event13 (SIGMACHIP Trust Keyboard System Control) may 27 07:50:26 ComputerM systemd-logind[579]: Watching system buttons on /dev/input/event9 (PixArt Trust OpticalMouse Keyboard) may 27 07:50:26 ComputerM systemd-logind[579]: Watching system buttons on /dev/input/event11 (SIGMACHIP Trust Keyboard Consumer Control) may 27 07:50:26 ComputerM systemd-logind[579]: Watching system buttons on /dev/input/event10 (SIGMACHIP Trust Keyboard) may 27 07:50:26 ComputerM mtp-probe[2715]: checking bus 1, device 15: "/sys/devices/pci:00/:00:08.1/:04:00.3/usb1/1-3/1-3.4" may 27 07:50:26 ComputerM mtp-probe[2715]: bus: 1, device: 15 was not an MTP device may 2
[KScreen] [Bug 454387] New: HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine)
https://bugs.kde.org/show_bug.cgi?id=454387 Bug ID: 454387 Summary: HDMI signal loss when connecting to a KDE Linux PC in a Wayland session from a 4-port HDMI KVM switch (in a KDE X11 session it works fine) Product: KScreen Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- SUMMARY I have connected a Manjaro Linux KDE PC to an HDMI KVM switch of 4 ports (for 4 PC). If I'm in KDE with an X11 session, switching from another machine to the Linux machine is almost instantaneous, it only takes 2-3 seconds. But if I'm on KDE with a Wayland session, when I switch to the Linux computer the HDMI signal is lost, the screen goes black and it takes 15-20 seconds to get the signal back. STEPS TO REPRODUCE 1. Connect at least two PCs to an HDMI KVM switch (of 4 ports), one of which is a Linux KDE. 2. The Linux KDE must have a Wayland session started. 3. Switch to the other computer with the HDMI KVM switch. 4. Change and return back to the Linux KDE computer with the HDMI KVM switch. OBSERVED RESULT HDMI signal is lost when switching to Linux KDE Wayland session machine. The screen goes black and the HDMI signal is not recovered until after 15 or 20 seconds. EXPECTED RESULT When switching with the HDMI KVM switch to the Linux KDE Wayland machine, the HDMI signal should not be lost and the switch should be almost instantaneous, like when in a Linux KDE X11 session. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux KDE (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Tested with Kernels 5.17.9 and 5.18.0 and with two different HDMI KVM switches of different brands (all of 4 ports), and in all cases the same thing happens. And as I say, if the PC Linux KDE computer is in an X11 session, it works perfectly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453557] Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected
https://bugs.kde.org/show_bug.cgi?id=453557 --- Comment #3 from Chema --- I have discovered an interesting thing, I comment it in case it can give some clue of the cause of the problem. When in a session with KDE at 4K screen resolution with the bidirectional HDMI Edid emulator connected, the computer is put into sleep mode and then wakes up, as I have mentioned, the monitor does not receive an HDMI signal and the screen remains black, no matter how much you move the mouse does not react, it does not receive a HDMI signal. However, I have discovered a curious thing. If with the screen being black without receiving an HDMI signal, you wait 5 minutes for the lock screen to pop up, then when you move the mouse, it works! The monitor starts to receive HDMI signal, it is activated and you can see the KDE lock screen perfectly! I just tested this with the KDE version of Fedora 36 that was released yesterday. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453557] Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected
https://bugs.kde.org/show_bug.cgi?id=453557 --- Comment #2 from Chema --- Sorry, I also forgot to comment that this happens indistinctly in both X11 and Wayland, it doesn't matter which one you started, the same thing happens in both. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453557] Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected
https://bugs.kde.org/show_bug.cgi?id=453557 --- Comment #1 from Chema --- Sorry, the link to the HDMI Edid emulator was pasted wrong. The correct link is: https://www.evanlak.com/products/hdmi-edid-emulator-4k-120hz Or in Amazon: https://www.amazon.com/EVanlak-Generrtion-Passthrough-Eliminated-Thunderbolt/dp/B07YMTMMH5?th=1 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453557] New: Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected
https://bugs.kde.org/show_bug.cgi?id=453557 Bug ID: 453557 Summary: Black screen when waking up the computer in 4K resolution with KDE and an HDMI Edid emulator connected Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- SUMMARY When the computer cable is connected to an HDMI Edid emulator and the screen resolution is in 4K, when the computer sleeps from KDE and then wakes up, the monitor does not receive HDMI video signal and only black screen is displayed. When you switch sessions by pressing the Ctrl+Alt+F1 keys, the computer starts sending the HDMI signal to the monitor and then you can see the screen perfectly. This problem does not occur on the Windows operating system nor does it occur with the GNOME desktop environment (tested with Fedora and Manjaro). In GNOME this works perfectly when the screen is in 4K resolution. It also does not happen if the KDE resolution at the time of suspending the computer is set to less than 4K resolution, but if it is 4K or higher, the problem I just mentioned occurs. It does not depend on the Linux kernel either, I have tried with versions 5.16, 5.17 and 5.18 and the same thing happens in all of them from KDE. STEPS TO REPRODUCE 1. Have an HDMI Edid emulator connected to the computer (or a KVM switch) in the HDMI input, and have the HDMI cable from the computer connected to the HDMI Edid emulator --> (HDMI Edid emulator: https://www.evanlak.com/products /hdmi-edid-emulator-4k-120hz). 2. Have the screen resolution in 4K mode (3840x2160). 3. Put the computer in sleep mode and wait a few seconds. 4. Wake up the computer. OBSERVED RESULT When I wake up the computer, the screen is completely black, the monitor does not receive an HDMI video signal. It doesn't react until you press (for example) Ctrl+Alt+F1 to switch sessions. By doing so, the monitor begins to receive the video signal and is already displayed correctly. In KDE it works correctly with the HDMI Edid emulator connected if the screen resolution is less than 4K, but from 4K resolution the problem that I mentioned occurs that the screen stays black when waking up the computer. I have tried several distros with GNOME (Fedora and Manjaro) and with this desktop environment it works perfectly having the HDMI Edid emulator connected, the computer can be suspended in 4K resolution and when it wakes up it shows the screen correctly again. However, I have tried several distros with KDE (Manjaro and KDE Neon) and in both the same thing happens, when suspending the computer in 4K resolution with the HDMI Edid emulator connected, when waking it up the screen is black until it is changed from session. I have also tried several Linux kernels (5.16, 5.17 and 5.18) and the same thing happens in all of them. It doesn't seem like a problem with the kernel, but with KDE, since as I say in the GNOME distros it works perfectly. In the Windows operating system it also works perfectly, if I suspend the computer with the screen at 4K resolution, when I wake it up it is displayed correctly. EXPECTED RESULT As it happens in the GNOME desktop environment, when you wake up the computer it should correctly display the KDE screen and not get a black screen on the monitor without receiving an HDMI signal. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.24.5 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION My computer is an AMD Ryzen 5 3550H with Radeon Vega Mobile GFX, the GPU is an integrated AMD Radeon Vega 8 Graphics. Linux is using the video-linux driver (Picasso [ATI Technologies Inc]). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 360745] Cannot pair with android phone nor samsung galaxy tab.
https://bugs.kde.org/show_bug.cgi?id=360745 Chema Ramírez <dhou...@gmail.com> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Chema Ramírez <dhou...@gmail.com> --- I managed to sort this out. There was some kind of misconfiguration in my firewall. Deleted and added again kdeconnect to firewall rules worked. Now I should look for what made my firewall act like this. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 360745] Cannot pair with android phone nor samsung galaxy tab.
https://bugs.kde.org/show_bug.cgi?id=360745 --- Comment #2 from Chema Ramírez <dhou...@gmail.com> --- My packages manager says it's 0.9g-2.10-x86_64 while kdeconnect android app is 0.9g. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 360745] New: Cannot pair with android phone nor samsung galaxy tab.
https://bugs.kde.org/show_bug.cgi?id=360745 Bug ID: 360745 Summary: Cannot pair with android phone nor samsung galaxy tab. Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: dhou...@gmail.com Created attachment 97975 --> https://bugs.kde.org/attachment.cgi?id=97975=edit WIndow showing kdeconnect error. I cannot connect to any device since I'm getting an error message about having an old kdeconnect old app version. My android app is up-to-date since Google Play Store shows there's no newer versions and I'm using KDE 5.6 on openSUSE 42.1 Leap. The devices are detected since they appear in settings dialog but, oddly, it disappears and disappears over and over when a click on "Refresh" button. Screenshot is attached. -- You are receiving this mail because: You are watching all bug changes.
