[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 --- Comment #11 from Guido --- (In reply to Arjen Hiemstra from comment #10) > What distribution does this happen on? > > Also, does something change if you add `/sec:nla` to the xfreerdp command > line options? I use Manjaro unstable branch (equivalent to Arch) With that option nothing change. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 --- Comment #8 from Guido --- (In reply to John Kizer from comment #7) > Sorry if this is incorrect, I'm trying to set this to "Confirmed" so it's > not auto-closed, since at least two folks have reported it? Also I see other users report the same problem on Reddit -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 489601] New: Kmail2 sometimes fails to display a message on an IMAP folder
https://bugs.kde.org/show_bug.cgi?id=489601 Bug ID: 489601 Summary: Kmail2 sometimes fails to display a message on an IMAP folder Classification: Applications Product: kmail2 Version: 6.1.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: guido-kdeb...@unknownsite.de Target Milestone: --- SUMMARY Every once in a while, kmail2 will fail to display an email in my IMAP inbox that is visible in other email clients (for example Thunderbird or AquaMail on my smartphone) using that same IMAP account. Right now, I have an important email in my inbox with an important invoice, which kmail is just not showing to me. Even if I press F5 repeatedly, the email will not show up. Restarting both kmail and akonadi (using "akonadi stop" on the command line) does not reveal the missing email, either. If I were to rely exclusively on kmail for reading my emails, I would have no way of even knowing that I have received that mail. That makes this a kind of silent data loss, which is arguably much more severe for the user than any crash could ever be, which is why I selected "grave" as the severity. The IMAP server in question is running Cyrus IMAPd. In the past, I have had success making kmail see the email in question by moving it to a different IMAP folder using a different email client. This time I have not done that, because I don't know how to reproduce the bug intentionally, and it happens only very rarely (but could have major consequences when it does), so keeping the problem around for a while might just be more valuable. STEPS TO REPRODUCE Steps to reproduce this bug are not known to me at this time. It happens randomly. OBSERVED RESULT An email that I know to be in my IMAP inbox is not shown. EXPECTED RESULT All emails that are present in any of my IMAP folders should always be shown in the message list for that folder, with no exceptions, ever. SOFTWARE/OS VERSIONS Windows: – macOS: – Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION The problem is not new by any stretch. It has started turning up every once in a while ever since kmail switched to using akonadi as a back end. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 --- Comment #5 from Guido --- I tried remmina, negotiation error >From the terminal: [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core] - [tpdu_read_connection_confirm]: Error: expected X224_TPDU_CONNECTION_CONFIRM [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core.nego] - [nego_connect]: Protocol Security Negotiation Failure [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core] - [rdp_client_connect]: ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C] [20:33:37:220] [69816:000110fc] [ERROR][com.freerdp.core.connection] - [rdp_client_connect]: Error: protocol security negotiation or connection failure -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] unable to connect using xfreerdp (X224_TPDU_CONNECTION_CONFIRM error)
https://bugs.kde.org/show_bug.cgi?id=488807 --- Comment #4 from Guido --- (In reply to Akseli Lahtinen from comment #2) > Seems xfreerdp as a client does not work. Can you try another client, such > as Remmina installed from Flatpak, just to see if it's client or server > specific thing? Krdp uses freerdp2, krdc also uses freerdp2, and xfreerdp is part of freerdp2. Remind uses freerdp3 So your request sounds a bit strange for me. But I can try in next few days. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 488732] Dual monitor settings are not restored: Screen positions and control bars swapped
https://bugs.kde.org/show_bug.cgi?id=488732 --- Comment #2 from Guido Schmidt --- (In reply to Nate Graham from comment #1) > Does it happen on Wayland too, or just X11? I logged out to check that. And what happend? When the login screens came up they were already swapped. Then I tried Wayland, but that doesn't even run. The screen turns black for a few seconds and brings me back to login. -- You are receiving this mail because: You are watching all bug changes.
[KRdp] [Bug 488807] New: unable to connect
https://bugs.kde.org/show_bug.cgi?id=488807 Bug ID: 488807 Summary: unable to connect Classification: Plasma Product: KRdp Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: guido.iod...@gmail.com CC: ahiems...@heimr.nl Target Milestone: --- I tried the new remote desktop on my machine, but krdc returns a "unknow error". >From the terminal: xfreerdp /u:pino /p:pano /v:192.168.1.115 [19:46:48:881] [6023:6024] [ERROR][com.freerdp.core] - Error: expected X224_TPDU_CONNECTION_CONFIRM [19:46:48:881] [6023:6024] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure [19:46:48:881] [6023:6024] [ERROR][com.freerdp.core] - rdp_client_connect:freerdp_set_last_error_ex ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C] [19:46:48:881] [6023:6024] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure I tried also 192.168.1.115:3389 and 127.0.0.1 and 127.0.0.1:3389 with the same result. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 488804] New: Kactivitymanagerd spikes to 100% CPU when I open a file
https://bugs.kde.org/show_bug.cgi?id=488804 Bug ID: 488804 Summary: Kactivitymanagerd spikes to 100% CPU when I open a file Classification: Plasma Product: kactivitymanagerd Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: guido.iod...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Kactivitymanagerd spikes to 100% CPU when I open a file STEPS TO REPRODUCE 1. run 'top' in a terminal 2. open dolphin then open a file 3. observe the CPU occupation in the terminal OBSERVED RESULT kactivitymanagerd spikes to 45 then 100 then 70% CPU for 2-3 seconds EXPECTED RESULT kactivitymanagerd should consume fewer CPU SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.10.0-rc4-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 ADDITIONAL INFORMATION I tried to disable and reset the "recent file" from kcm but this doesn't help. I have no activities other than the default one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 488732] New: Dual monitor settings are not restored: Screen positions and control bars swapped
https://bugs.kde.org/show_bug.cgi?id=488732 Bug ID: 488732 Summary: Dual monitor settings are not restored: Screen positions and control bars swapped Classification: Applications Product: systemsettings Version: 6.0.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: gu...@sanguepreto.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I have two screens attached. Their relative position and their control bars are swapped after reboot. Happens every time. STEPS TO REPRODUCE 1. Have one monitor (A) connected to the DP port of the mainboard. 2. Add a second monitor (B) to the HDMI port. 3. Find B to be on the left side of A. 4. Open display settings and drag B to the right side of A. 5. Configure A to be the primary screen. 6. Apply and confirm to keep the settings. 7. Also have different control bars configured for each screen. 8. Restart the PC. 9. While A remains the primary screen: OBSERVED RESULT - Screen B is now on the left side of A. - Control bar from A is now on B and vice versa. EXPECTED RESULT - Find B to be on the right side of A. - Control bars are restored to the previous screens. SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed Display server: Xorg KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel: 6.9.1-1-default (64-bit) ADDITIONAL INFORMATION Graphics hardware: AMD Ryzen 9 7900 (plus a now unused NVIDIA GK208B card) Monitor A: Fujitsu Siemens D24W-7 (1920x1200) Monitor B: HP M24fw (1920x1080) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442386] Prefer EGL to GLX for GL support also on X11
https://bugs.kde.org/show_bug.cgi?id=442386 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #6 from Guido --- (In reply to Vlad Zahorodnii from comment #1) > Currently, all our focus is on Wayland. We would prefer to avoid touching > X11 code if possible. > > As for making EGL default, on X11, kwin has no any way to determine when a > buffer swap completes. For some people, it may be an issue because it can > result in stuttering. Is this still true? I have been using kwin with EGL (but with OpenGL not GLES) for some time and have not noticed any problems. In fact, my tests show that kwin occupies less CPU in some cases (Intel TigerLake). For example, if I watch a video and overlay a terminal window (semi-transparent), with GLX kwin takes up about 7% of my CPU, while with EGL it takes up 5%. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 342582] Intel hd 4600 + OpenGL + kwin = can't load
https://bugs.kde.org/show_bug.cgi?id=342582 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #36 from Guido --- why it's only on glx backend, not in egl backend? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 488550] The screnshoot from Spectacle is blurry
https://bugs.kde.org/show_bug.cgi?id=488550 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #1 from Guido --- It is probably because there is gweenview zoom at 99%. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 488541] When using xdg-desktop-portal-kde font in gtk app is blocky and diffucult to read. xdg-desktop-portal-gtk is required to fix this
https://bugs.kde.org/show_bug.cgi?id=488541 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #2 from Guido --- I noticed that this problem only occurs with Wayland, whereas on X11 fonts are rendered correctly even without xdg-desktop-portal-gtk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454732] Application-specific gtk icons do not appear in the global menu
https://bugs.kde.org/show_bug.cgi?id=454732 --- Comment #2 from Guido --- a kind bump for this bug (sorry again) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #11 from Guido --- (In reply to Guido from comment #10) > I tried but seems to work only for KWIN_COMPOSE=O2ES while in the past it > workded also for standard compose Any solution about this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483163] On X11 with compositing turned on, blank screen on lock screen when using Breeze Plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #34 from Guido --- Confirmed for Plasma 6.0.90 KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.10.0-rc2-1 (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 487579] Only-modifier shortcut are too "fast", prevents the use of shortcuts with modifier+something combinations
https://bugs.kde.org/show_bug.cgi?id=487579 --- Comment #1 from Guido --- p.s. I tried sleep .8; qdbus org.kde.krunner /App displaySingleRunner krunner_appmenu but still it seems to keep opening krunner immediately without the possibility of using other combinations. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 487579] New: Only-modifier shortcut are too "fast", prevents the use of shortcuts with modifier+something combinations
https://bugs.kde.org/show_bug.cgi?id=487579 Bug ID: 487579 Summary: Only-modifier shortcut are too "fast", prevents the use of shortcuts with modifier+something combinations Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 6.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: --- In the past I used this: [ModifierOnlyShortcuts] Alt=org.kde.krunner,/App,,displaySingleRunner,krunner_appmenu in kwinrc to have krunner invocation with only the krunner_appmenu plugin With kwin 6.0.90.1 this no longer works, so I created the shortcut for qdbus org.kde.krunner /App displaySingleRunner krunner_appmenu and it works. The problem is that if that shortcut is just 'Alt' then I cannot use Alt+something for other purposes, because krunner_appmenu plugin starts immediately and for example I cannot use alt+f2 to start the full krunner, or other alt+ shortcut. Previously, on the other hand, pressing alt was a small pause that allowed alt+something combinations to be used quietly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487576] kwin seems don't honour shortcuts in kwinrc
https://bugs.kde.org/show_bug.cgi?id=487576 Guido changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Guido --- ok I figerd out how new kglobalaccel works. Still, there is some problem with it but I open a specific bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487576] New: kwin seems don't honour shortcuts in kwinrc
https://bugs.kde.org/show_bug.cgi?id=487576 Bug ID: 487576 Summary: kwin seems don't honour shortcuts in kwinrc Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: --- I intalled kwin 6.0.90.1 (from Arch KDE-Ustable repo). It works very well but It does not seem to honour the shortcut I had set up and which up to version 6.0.5 worked. This is what I have in kwinrc [ModifierOnlyShortcuts] Alt=org.kde.krunner,/App,,displaySingleRunner,krunner_appmenu Pressing Alt, krunner is not shown (alt+f2 works as supposed). I tried modifying it by putting org.kde.krunner1 but it still doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #10 from Guido --- I tried but seems to work only for KWIN_COMPOSE=O2ES while in the past it workded also for standard compose -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #9 from Guido --- (In reply to Zamundaaa from comment #8) > Afaict, the problem here is that the wrong egl display got used for > compositing, so the shared context with Qt doesn't work. With > https://invent.kde.org/plasma/kwin/-/commit/ > 686ea6374bb7e03876006a52822cff9ca23c42cd that's fixed, so this issue should > be gone in 6.1 thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #7 from Guido --- the bug persists with Plasma 6.0.5 Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.10-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441991] screenshot problem on Intel TGL/X11
https://bugs.kde.org/show_bug.cgi?id=441991 Guido changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #4 from Guido --- Intel DDX driver is unmaintaned now. Meanwhile the modesetting DDX driver has improved considerably (In particular, I recommend installing xorg-server from git) and with this driver the problem does not occur. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466204] Total system freeze after login if an external monitor is connected (X11 and Wayland, Intel graphics)
https://bugs.kde.org/show_bug.cgi?id=466204 Guido changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #12 from Guido --- it seems solved in Plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485849] Plasmashell freezes in X11 but works again after right click
https://bugs.kde.org/show_bug.cgi?id=485849 Guido changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Guido --- It seems solved in git version of Kwin. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 454983] motion tracking doesn't work on Arch
https://bugs.kde.org/show_bug.cgi?id=454983 Guido changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Guido --- It's an Arch-specific bug. In other distros it works. For Arch (and derivatives) you can install opencv from KaOS, it works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473651] Dolphin doesn't became sticky
https://bugs.kde.org/show_bug.cgi?id=473651 Guido changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Guido --- Ther bug seems solved in Plasma 6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473411] Morphing Popups effect tooltips effect corrupts QtWidgets apps' tooltips
https://bugs.kde.org/show_bug.cgi?id=473411 --- Comment #11 from Guido --- The bug persists in Plasma 6 Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485849] Plasmashell freezes in X11 but works again after right click
https://bugs.kde.org/show_bug.cgi?id=485849 --- Comment #1 from Guido --- Mmmmh it doesn't seem to be entirely causal. The problem occurs if I launch an app from the menu while if I launch it from the panel it doesn't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #6 from Guido --- (In reply to Conor Dockry from comment #5) > (In reply to Guido from comment #4) > > intel-media-driver > intel-vaapi-driver > > > lspci -k > 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe > Graphics] (rev 04) > Subsystem: Lenovo Device 2309 > Kernel driver in use: i915 > Kernel modules: i915, xe In my case: 00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) DeviceName: Onboard - Video Subsystem: Dell Device 0a02 Kernel driver in use: i915 Kernel modules: i915, xe -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #4 from Guido --- (In reply to Conor Dockry from comment #0) What graphics card do you have? What drivers are you using? In my case (Intel igpu Tigerlake) kwin totally crashes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485849] New: Plasmashell freezes in X11 but works again after right click
https://bugs.kde.org/show_bug.cgi?id=485849 Bug ID: 485849 Summary: Plasmashell freezes in X11 but works again after right click Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: guido.iod...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Apparently causally, the Plasmashell panel seems to freeze (you can't switch between windows or open the menu) but just right-click it and it works again. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467060] Problem with Local Folders of KMail pointing to ~/.local/share/akonadi_maildir_resource_0 but using ~/.local/share/.akonadi_maildir_resource_0.directory
https://bugs.kde.org/show_bug.cgi?id=467060 --- Comment #2 from Guido Pinkernell --- btw, this is with akonadi 24.02.2-1.1 from opensuse's tumbleweed main repository. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467060] Problem with Local Folders of KMail pointing to ~/.local/share/akonadi_maildir_resource_0 but using ~/.local/share/.akonadi_maildir_resource_0.directory
https://bugs.kde.org/show_bug.cgi?id=467060 Guido Pinkernell changed: What|Removed |Added CC||guido.pinkern...@gmx.de --- Comment #1 from Guido Pinkernell --- Same here, now in April 2024. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 --- Comment #3 from Guido --- The bug persist in kwin 6.0.4 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 485606] New: Baloorunner starts even when baloo is not active
https://bugs.kde.org/show_bug.cgi?id=485606 Bug ID: 485606 Summary: Baloorunner starts even when baloo is not active Classification: Plasma Product: krunner Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: filesearch Assignee: baloo-bugs-n...@kde.org Reporter: guido.iod...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de, plasma-b...@kde.org Target Milestone: --- SUMMARY Baloorunner starts even when baloo is not active STEPS TO REPRODUCE 1. Disable file search in KDE Settings 2. Restart session OBSERVED RESULT /usr/lib/baloorunner is executed anyway (via plasma-baloorun.service) EXPECTED RESULT Baloorunner should be not in execution -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483912] Overview, Flip Switch, Show FPS, other OpenGL effects render as black screen when KWIN_OPENGL_INTERFACE=egl
https://bugs.kde.org/show_bug.cgi?id=483912 Guido changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Guido --- I have the same bug so I think it's confirmed. It persist in KWIN 6.0.3 and with last mesa 24.0.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashes kwin
https://bugs.kde.org/show_bug.cgi?id=484472 --- Comment #8 from Guido --- The bug affects also kwin 6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashes kwin
https://bugs.kde.org/show_bug.cgi?id=484472 Guido changed: What|Removed |Added Summary|Overview effect crashs kwin |Overview effect crashes ||kwin --- Comment #7 from Guido --- The bug affects also 6.0.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464715] Non-Icons-Only Task Manager: Option to keep pinned launchers visible after the start of the application
https://bugs.kde.org/show_bug.cgi?id=464715 --- Comment #8 from Guido --- (In reply to Guido from comment #7) Sorry i wrote in Italian... On Plasma 6 it seems to me that the behavior is as desired. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464715] Non-Icons-Only Task Manager: Option to keep pinned launchers visible after the start of the application
https://bugs.kde.org/show_bug.cgi?id=464715 Guido changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Guido --- Su Plasma 6 mi pare che il comportamento sia quello desiderato. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484535] [X11] Kwin animations are much less fluid than in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=484535 Guido changed: What|Removed |Added Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484535] [X11] Kwin animations are much less fluid than in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=484535 Guido changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Guido --- It seems that the problem was a modesetting driver configuration (ShadowFB off). Eliminating it solved the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashs kwin
https://bugs.kde.org/show_bug.cgi?id=484472 --- Comment #6 from Guido --- @David(In reply to David Edmundson from comment #4) Does the bug occur for you as well? Any idea why? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484659] New: Kicker sometimes does not close when it loses focus (and another bug probably related to)
https://bugs.kde.org/show_bug.cgi?id=484659 Bug ID: 484659 Summary: Kicker sometimes does not close when it loses focus (and another bug probably related to) Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: plasma-b...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: 1.0 SUMMARY 1. Kicker sometimes does not close when it loses focus. Strangely, it doesn't happen all the time, but still it happens very often, so it's pretty boring. 2. Also, a "plasmashell" process appears on the task manager when you open a submenu. As a workaround I had to set that plasmashell always skips the task manager in kwin rules. Operating System: Manjaro Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.2-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashs kwin
https://bugs.kde.org/show_bug.cgi?id=484472 --- Comment #5 from Guido --- (In reply to David Edmundson from comment #4) > Ok, but how did you set it? export KWIN_OPENGL_INTERFACE=egl export QT_XCB_GL_INTEGRATION=xcb_egl In my experience, the performance is better (on Plasma 5). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashs kwin
https://bugs.kde.org/show_bug.cgi?id=484472 --- Comment #3 from Guido --- (In reply to David Edmundson from comment #2) > How did you end up not using GLX in Qt? GLX is practically deprecated, EGL is the new standard. On Plasma 5 I had been using EGL for years without any problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] Overview effect crashs kwin
https://bugs.kde.org/show_bug.cgi?id=484472 Guido changed: What|Removed |Added Component|effects-overview|egl -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473410] Dimensioni delle immagini non mostrate se baloo non è attivo
https://bugs.kde.org/show_bug.cgi?id=473410 Guido changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484535] New: [X11] Kwin animations are much less fluid than in Plasma 5
https://bugs.kde.org/show_bug.cgi?id=484535 Bug ID: 484535 Summary: [X11] Kwin animations are much less fluid than in Plasma 5 Classification: Plasma Product: kwin Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: --- SUMMARY Kwin animations are much less fluid than in Plasma 5 STEPS TO REPRODUCE 1. Select X11 session at login 2. use amination like Overview or maximize/minimize (in my case "squeeze") OBSERVED RESULT Evident micro-lags EXPECTED RESULT it should be fluid like in Plasam 5 SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 ADDITIONAL INFORMATION Informazioni per il supporto di KWin: Le seguenti informazioni dovrebbero essere usate quando si richiede supporto su ad es. https://discuss.kde.org. Forniscono i dettagli sull'istanza attualmente in esecuzione, le opzioni usate, quale driver OpenGL e quali effetti sono utilizzati. Pubblicare le informazioni indicate sotto questo testo introduttivo su un servizio paste bin come https://paste.kde.org invece di incollarlo nella conversazione di supporto. == Version === KWin version: 6.0.2 Qt Version: 6.6.2 Qt compile version: 6.6.2 XCB compile version: 1.16.1 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12101099 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 1 decorationButtonsRight: 6, 9, 3, 4, 5 borderSize: 0 gridUnit: 12 font: Droid Sans,11,-1,5,700,0,0,0,0,0,0,0,0,0,0,1,Bold smallSpacing: 3 largeSpacing: 12 Output backend == Name: KWin::X11StandaloneBackend Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: ClickToFocus xwaylandCrashPolicy: 1 xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: 5 activationDesktopPolicy: SwitchToOtherDesktop focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: MouseRaise commandActiveTitlebar2: MouseNothing commandActiveTitlebar3: MouseOperationsMenu commandInactiveTitlebar1: MouseActivateAndRaise commandInactiveTitlebar2: MouseNothing commandInactiveTitlebar3: MouseOperationsMenu commandWindow1: MouseActivateRaiseAndPassClick commandWindow2: MouseActivateAndPassClick commandWindow3: MouseActivateAndPassClick commandWindowWheel: MouseNothing commandAll1: MouseUnrestrictedMove commandAll2: MouseToggleRaiseAndLower commandAll3: MouseUnrestrictedResize keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 2 glSmoothScale: 2 glStrictBinding: true glStrictBindingFollowsDriver: true glPreferBufferSwap: AutoSwapStrategy glPlatformInterface: 1 windowsBlockCompositing: true allowTearing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 100 reActivateThreshold: 700 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Active screen follows mouse: yes Number of Screens: 1 Screen 0: - Name: HDMI-1 Enabled: 1 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 6 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel OpenGL renderer
[kwin] [Bug 484472] Overview effect crashs kwin
https://bugs.kde.org/show_bug.cgi?id=484472 --- Comment #1 from Guido --- update: It seems that the problem is the use of egl. Using glx for both kwin and qt the problem does not occur. KWIN_OPENGL_INTERFACE=xcb QT_XCB_GL_INTEGRATION=glx kwin_x11 --replace works fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484472] New: Overview effect crashs kwin
https://bugs.kde.org/show_bug.cgi?id=484472 Bug ID: 484472 Summary: Overview effect crashs kwin Classification: Plasma Product: kwin Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: --- SUMMARY In the X11 session, activating the overview effect crashes kwin. The same happens with the present windows effect. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482734] Some apps close if plasmashell crash or is closed
https://bugs.kde.org/show_bug.cgi?id=482734 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482734] New: Some apps close if plasmashell crash or is closed
https://bugs.kde.org/show_bug.cgi?id=482734 Bug ID: 482734 Summary: Some apps close if plasmashell crash or is closed Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: guido.iod...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Chromium and Libreoffice (maybe other apps) close if Plasmashell crashes or is intentionally closed. This happens whether I launch them from the Panel or from the Menu. STEPS TO REPRODUCE 1. Lauch Chromium or Libreoffice from Panel or Menu 2. Close Plasmashell with systemctl --user restart plasma-plasmashell.service OBSERVED RESULT Libreoffice Chromium crashes, while Dolphin and Konsole do not. EXPECTED RESULT No application should close. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.7-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 --- Comment #10 from Guido Winkelmann --- I can't see why this bug has been marked as solved and "not a bug". It's clearly still a bug, it's clearly a regression a from 5.27, and it's clearly not caused just by pipewire not actually running, since all reporters so far could confirm that, yes, pipewire is really running the whole time and reachable from various other pipewire frontends. >From my point of view, this is even a rather major bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #37 from Guido --- I realised that in dconf there is a run-on-wayland entry under org.appmenu-gtk-module. Despite this, the menu is not shown in the KDE global menu applet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450711] plasmashell exits with timeout reading from pipe
https://bugs.kde.org/show_bug.cgi?id=450711 --- Comment #9 from Guido Winkelmann --- (In reply to Nate Graham from comment #8) > In any event, we still need a backtrace of the crash to do something with > this. Sorry it took me so long to get back to you. Can I ask you to upgrade > to Plasma 6 (which is due to be released in 5 days) and try it again there, > to see if it's still happening? If so, please use the instructions I > previously provided to get a backtrace, and attach it here. Thanks a lot! I don't have coredumpctl on my system. I googled it and it seems that's a systemd utility, but I'm not using systemd. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481520] Screens stays black after unlocking if monitors were switched off while locked (Wayland)
https://bugs.kde.org/show_bug.cgi?id=481520 --- Comment #2 from Guido Winkelmann --- (In reply to fanzhuyifan from comment #1) > What graphics card are you using? It's and AMD Radeon RX 5700 XT. > Did your laptop suspend to ram in the mean time? This happened on my desktop, not a laptop, and the desktop did not do any suspend operations in that time. Or any other time, because I never configured it to do suspend. My laptop actually did suspend to RAM in that time, but I doubt that is related... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481520] New: Screens stays black after unlocking if monitors were switched off while locked (Wayland)
https://bugs.kde.org/show_bug.cgi?id=481520 Bug ID: 481520 Summary: Screens stays black after unlocking if monitors were switched off while locked (Wayland) Classification: Plasma Product: kwin Version: 5.93.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: guido-kdeb...@unknownsite.de Target Milestone: --- SUMMARY *** When switching off all connected monitors (all DisplayPort) on Plasma (Wayland) while the screen is locked, then switching them back on later and unlocking the screen, all screens will go black apart from the mouse cursor and stay black. Sometimes the desktop is actually visible for a split second before it goes black. The only way I found to get a desktop back at all is to switch to a different VT and kill plasma from the command line. I have chosen the severity categorization "major" for this, as it can seriously hamper the use of the system as a whole if you're not expecting this, including data loss. My current workaround for this problem is to leave my monitors on when I walk away from my computer for a while. Needless to say, I don't like wasting energy like that. Another workaround would be, of course, to save everything and log out before walking away, but there are often reason for not wanting or being unable to do that. *** STEPS TO REPRODUCE 1. Lock the screen 2. Switch off all connected monitors. (Depending on your monitor and type of connection, you may need to physically disconnect them from the graphics port. In my case, just switching them off is enough.) 3. (Optional) Walk away and do something else for a while 4. Switch all monitors on again 5. Unlock the session by entering the current user's password on the lock screen OBSERVED RESULT All connected monitors show a black screen. Sometimes they show the actual session for a split second before that happens. The mouse cursor is still visible and can still be moved. EXPECTED RESULT The screens should show the session as it was before the screen was first locked. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION This is when running on Wayland. I have not tried on X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 --- Comment #2 from Guido Winkelmann --- I'm assuming you mean krfb when you say screen sharing, but in any case, none of these things work for a new user either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] New: Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058
Bug ID: 481058
Summary: Recording windows or screens with OBS or spectacle is
broken in Plasma 6 RC2 on Wayland: Failed to start
pipewire screencast
Classification: Plasma
Product: plasmashell
Version: 5.93.0
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: guido-kdeb...@unknownsite.de
CC: k...@davidedmundson.co.uk
Target Milestone: 1.0
SUMMARY
***
Recording a window or an entire screen with OBS is broken in Plasma 6 RC2.
Spectacle has the same problem for recordings, though screenshots work.
When trying, I get a popup in the message area saying "Das Bildschirmvideo kann
nicht gestartet werden - Failed to connect to PipeWire context". On the console
from which I started OBS, it says "warning: [pipewire] Failed to start
screencast, denied or cancelled by user".
***
STEPS TO REPRODUCE
1. Open OBS
2. Add another source to the sources, either "Window Capture (PipeWire)" or
"Screen Capture (PipeWire)"
3. A window (not belonging to OBS itself) will popup, asking you to select
either a screen or a window to capture. Select any.
OBSERVED RESULT
A popup in the message are saying "Failed to connect to PipeWire context". The
recording area in OBS stays empty.
EXPECTED RESULT
No error messages, and a live view of the selected window or screen appears in
OBS.
SOFTWARE/OS VERSIONS
Windows: n/a
macOS: n/a
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1
ADDITIONAL INFORMATION
This used to work fine with Plasma 5 on Wayland, though I haven't tested it
with Plasma 6 RC1.
I get this console output in .local/share/sddm/wayland-session.log when I try
to start a screen recording with OBS:
===
xdp-kde-wayland-integration: failed to start streaming
ScreencastingStream(0x55f6853bd100) "Failed to connect PipeWire context"
xdp-kde-screencast: Invalid window! QMap((0, QVariant(QString, "Luftrecht und
Sicherheit – LBA – OpenUAV – Mozilla Firefox"))(1, QVariant(QIcon,
QIcon("firefox",availableSizes[normal,Off]=QList(QSize(16, 16), QSize(22, 22),
QSize(32, 32),
QSize(48, 48), QSize(64, 64), QSize(128, 128), QSize(256,
256)),cacheKey=0x1)))(257, QVariant(QString, "firefox"))(258,
QVariant(bool, false))(259, QVariant(bool, true))(260, QVariant(bool,
false))(261, QVariant(bool, true))(262, Q
Variant(bool, true))(263, QVariant(bool, true))(264, QVariant(bool,
false))(265, QVariant(bool, false))(266, QVariant(bool, false))(267,
QVariant(bool, false))(268, QVariant(bool, false))(269, QVariant(bool,
false))(270, QVariant(bool, fal
se))(271, QVariant(bool, false))(272, QVariant(bool, true))(273, QVariant(bool,
true))(274, QVariant(bool, true))(275, QVariant(bool, true))(276,
QVariant(QRect, QRect(2560,0 2560x1440)))(277, QVariant(uint, 5838))(278,
QVariant(bool, fals
e))(279, QVariant(QStringList,
QList("9e528cdd-e14e-418b-8af3-b67fec93034f")))(280, QVariant(QByteArray,
"{2a265327-b83f-4bfc-85a0-673065d86bae}")))
QObject::startTimer: Timers cannot have negative intervals
QQuickItem: Cannot set FocusScope once item has children and is in a window.
Service ":1.232" unregistered
===
I also get an enormous number of this message in that same file when trying to
record a window with OBS or spectacle:
QObject::startTimer: Timers cannot have negative intervals
When trying to record using spectacle, the output in the sddm log looks like
this:
===
dbus-daemon[4571]: [session uid=1000 pid=4571] Activating service
name='org.kde.spectacle' requested by ':1.66' (uid=1000 pid=7593
comm="/usr/bin/krunner --daemon" label="kernel")
dbus-daemon[4571]: [session uid=1000 pid=4571] Successfully activated service
'org.kde.spectacle'
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: Mesa Gallium driver 23.3.1 for AMD Radeon RX
5700 XT (radeonsi, navi10, LLVM 17.0.6, DRM 3.54, 6.6.14) in use for device
"/dev/dri/renderD128"
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib64/va/drivers/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
kpipewire_record_logging: VAAPI: Display initialized
kpipewire_record_logging: VAAPI: API version 1 . 20
kpipewire_record_logging: VAAPI: Mesa Gallium driver 23.3.1 for AMD Radeon RX
5700 XT
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #55 from Guido --- (In reply to Nate Graham from comment #54) > Right, because the bug isn't about QtWidgets tooltips. I am writing here because the bug I had opened was closed because it was considered a duplicate of this one. > The Morphing Popups > effect doesn't apply to them. Are you sure? When I enable the effect the problem with QTWidgets occurs, when it is disabled it does not. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #53 from Guido --- The patch doesn't solve the problem with QTWidget Tooltips -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480182] New: Combining pinned app icons with running windows does not work.
https://bugs.kde.org/show_bug.cgi?id=480182 Bug ID: 480182 Summary: Combining pinned app icons with running windows does not work. Classification: Plasma Product: plasmashell Version: 5.92.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Window List Assignee: plasma-b...@kde.org Reporter: guido-kdeb...@unknownsite.de CC: uhh...@gmail.com Target Milestone: 1.0 SUMMARY *** Combining pinned app icons with running windows does not work. When I have an application pinned in the window list in Plasma 5, and then open an instance/window of that application by clicking on its icon, the window list will replace the pinned app icon with the new entry for the open window, so it does not show both at the same time. In Plasma 6.0 RC1, this functionality is broken. The window list will show both the icon for the closed but pinned app and the entry for the new window. *** STEPS TO REPRODUCE 1. Have an application pinned to the window list, for example dolphin or firefox 2. Open that application by clicking on its icon. OBSERVED RESULT The window list will dhow both the original icon that was shown when the pinned application was closed or had no open windows on that desktop and monitor and the entry for the open window. EXPECTED RESULT The window list should stop showing the pinned app icon once there is at least one window entry for that application that can be shown instead. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Linux 6.6.12 KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477374] New: Plasma on Wayland fails to recognize numlock status on startup
https://bugs.kde.org/show_bug.cgi?id=477374 Bug ID: 477374 Summary: Plasma on Wayland fails to recognize numlock status on startup Classification: Plasma Product: kwin Version: 5.27.8 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: guido-kdeb...@unknownsite.de Target Milestone: --- SUMMARY When starting up KDE Plasma (kde-plasma/kwin-5.27.8-r3) when NumLock is already enabled, it will leave the NumLock indicator on the keyboard on, but treat keyboard input as if NumLock were off. If the NumLock button is pressed in this situation, the internal NumLock status will stay off and the keyboard's NumLock indicator will go dark. STEPS TO REPRODUCE 1. Start up SDDM 2. Make sure NumLock is enabled 3. Log in to a Plasma on Wayland session OBSERVED RESULT 1 - After startup, the keyboard LED indicates the wrong NumLock status. 2 - NumLock is effectively off after Plasma start in all cases I have seen. EXPECTED RESULT 1 - The status of the keyboard's NumLock LED should always correspond 1-1 to how the system will interpret input on the NumPad. 2 - If NumLock is enabled before Plasma starts up, it should still be enabled after startup unless intentionally disabled by the user. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 6.1.62, Plasma 5.27.8 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION While I am reporting this for kwin version 5.27.8, I have seen this behavior in all versions of kwin on Wayland I have tried so far. I have not seen it in kwin on X. See also the corresponding bug report in the Gentoo bug tracker: https://bugs.gentoo.org/917749 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464885] Crash on startup with Movit acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=464885 --- Comment #5 from Guido --- (In reply to farid from comment #4) > Thanks for your report, this is a known issue and is being tracked > elsewhere. Movit improvements are expected after the Qt6 migration. Thank you, happy to hear it! Can you tell me where it is tracked? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 --- Comment #44 from Guido --- (In reply to Guido from comment #43) > still have the same problem on Manjaro Linux > > kdenlive 23.08.1 > mlt 7.18.0 > movit 1.7.1 p.s. for me kdenlive crashes on startup, I post here because the relative bug was marked as a duplicate of this one. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #43 from Guido --- still have the same problem on Manjaro Linux kdenlive 23.08.1 mlt 7.18.0 movit 1.7.1 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474561] some extensions are not present for POCO F5 but are present on other devices
https://bugs.kde.org/show_bug.cgi?id=474561 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474561] New: some extensions are not present for POCO F5 but are present on other devices
https://bugs.kde.org/show_bug.cgi?id=474561 Bug ID: 474561 Summary: some extensions are not present for POCO F5 but are present on other devices Classification: Applications Product: kdeconnect Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: guido.iod...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Uso kdeconnect su vari dispositivi: 1. Xiaomi POCO F5 (android+miui) 2. Xiaomi Pad 5 (android+miui) 3. Samsung S10 Lite (android+OneUI) On POCO F% some extensions are not listed at all in the PC config interface of KDEconnect. They are (italian names): * blocco dispositivo * comandi remoti host * controllo vocale bigscreen * schermo virtuale * volume sistema remoto -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473651] Dolphin doesn't became sticky
https://bugs.kde.org/show_bug.cgi?id=473651 --- Comment #2 from Guido --- Other strange behavior: if Dolphin is maximezed, then unmaximized and snapped on the border, it becomes sticky... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473651] Dolphin doesn't became sticky
https://bugs.kde.org/show_bug.cgi?id=473651 --- Comment #1 from Guido --- PS: if I use the new tiling (with shift) all is ok. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473651] New: Dolphin doesn't became sticky
https://bugs.kde.org/show_bug.cgi?id=473651 Bug ID: 473651 Summary: Dolphin doesn't became sticky Classification: Plasma Product: kwin Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. open 2 dolphin windows or 1 dolphin and one other app 2. drag one window on the left border to tile it 3. drag the other one on the right to tile it 4. try to resize both windows from the center of the screen OBSERVED RESULT Windows aren't sticky EXPECTED RESULT Windows should be sticky This appens with Dolphin, not with other apps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #49 from Guido --- I would like to try to exclude QTWidgets tooltips from the effect. Looking at the documentation here (https://techbase.kde.org/Development/Tutorials/KWin/Effects/JS_API) I understand that there is no property to distinguish. On the other hand looking at the fadindpopups effect I see that there is a window.popupWindow property that is not documented, so I would need to know if there is a property like window.QTWidgetTooltip or window.QMLTooltip that would allow to distinguish between tooltips types. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #48 from Guido --- Created attachment 161096 --> https://bugs.kde.org/attachment.cgi?id=161096=edit QT tootips corruption -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #47 from Guido --- (In reply to Nate Graham from comment #46) > *** Bug 473411 has been marked as a duplicate of this bug. *** Hi Nate, my bug is different. I have no problem with plasma things like panel, etc. only on QTwidgets. I add my video here too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473411] morphin tooltips effect corrupts tooltips
https://bugs.kde.org/show_bug.cgi?id=473411 --- Comment #8 from Guido --- (In reply to Nate Graham from comment #7) > So to be clear: when you disable only the "Morphing Popups" effect, there's > no problem? Yes, no corruption. Of course I lose the morphing effect, which is so beautiful and I would really hate to give it up! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473411] morphin tooltips effect corrupts tooltips
https://bugs.kde.org/show_bug.cgi?id=473411 --- Comment #6 from Guido --- (In reply to Nate Graham from comment #5) > What if you turn off all desktop effects and compositing with Alt+Shift+F12? Of course it works, it also disables the morphing effect. That's what gives me the problem, if I disable only that there is no corruption problem, even with compositing enabled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473411] morphin tooltips effect corrupts tooltips
https://bugs.kde.org/show_bug.cgi?id=473411 --- Comment #4 from Guido --- (In reply to Nate Graham from comment #3) > Thanks. Does the problem still happen if you temporarily switch to the > Fusion style in System Settings > Appearance > Application Style? I did some experiments by turning some desktop effects on and off. I don't know precisely what changed the situation, maybe having changed the values of the blur effect, but now with Dolphin I don't have any more problems. Instead they keep having them with some applications like octopi, libreoffice, but also the systemd module of kcm. Using fusion there continue to be these glitches. They are there even with a different user, so I don't think they depend on the configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473411] morphin tooltips effect corrupts tooltips
https://bugs.kde.org/show_bug.cgi?id=473411 --- Comment #2 from Guido --- (In reply to Nate Graham from comment #1) > Do you see this issue in any other apps? > > Or in any other parts of Dolphin where the tooltip does not overlap with the > location bar? Yes in any QT app, even Libreoffice. In gtk apps morphing doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473411] morphin tooltips effect corrupts tooltips
https://bugs.kde.org/show_bug.cgi?id=473411 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473411] New: morphin tooltips effect corrupts tooltips
https://bugs.kde.org/show_bug.cgi?id=473411 Bug ID: 473411 Summary: morphin tooltips effect corrupts tooltips Classification: Plasma Product: kwin Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: --- Created attachment 160979 --> https://bugs.kde.org/attachment.cgi?id=160979=edit tooltip corruption If the morphing tooltips effect is active, the tooltips are corrupted (see attachment) Operating System: Manjaro Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Inspiron 5502 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473410] New: Dimensioni delle immagini non mostrate se baloo non è attivo
https://bugs.kde.org/show_bug.cgi?id=473410 Bug ID: 473410 Summary: Dimensioni delle immagini non mostrate se baloo non è attivo Classification: Applications Product: dolphin Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: guido.iod...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Dolphin does not display image size in tooltip if baloo is not active. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 473255] After resume, kscreenlocker interface appears corrupted
https://bugs.kde.org/show_bug.cgi?id=473255 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 473255] New: After resume, kscreenlocker interface appears corrupted
https://bugs.kde.org/show_bug.cgi?id=473255 Bug ID: 473255 Summary: After resume, kscreenlocker interface appears corrupted Classification: Plasma Product: kscreenlocker Version: 5.27.7 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: guido.iod...@gmail.com Target Milestone: --- This bug has been present for a long time but I have not found reports so I am reporting it. Some times, after resume, especially if the computer has gone into stand-by automatically, the kcreenlocker interface appears corrupted: the avatar is square instead of round, also the text shadows are missing. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470926] Adopt "explicit apply" paradigm with Apply/Cancel buttons
https://bugs.kde.org/show_bug.cgi?id=470926 --- Comment #3 from Guido Schmidt --- I wouldn't call it plenty. Only 5 out of 70 dialogs in my system settings don't have an Apply button. - Two of them ask if you really want to apply the changes: Global Design and Online accounts. - Game controller asks you before you start a new calibration. I think a confirmation dialog would be appropriate for autostart, too. Good to know that the button issue has been addressed, though. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464885] Crash on startup with Movit acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=464885 Guido changed: What|Removed |Added Summary|Crash on startup with Movit |Crash on startup with Movit |acceleration enabled on |acceleration enabled |Wayland | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 464885] Crash on startup with Movit acceleration enabled on Wayland
https://bugs.kde.org/show_bug.cgi?id=464885 Guido changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #1 from Guido --- I have the same problem with Intel GPU on X11. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470926] New: Autostart has no apply/cancel buttons / changes take effect immediately
https://bugs.kde.org/show_bug.cgi?id=470926 Bug ID: 470926 Summary: Autostart has no apply/cancel buttons / changes take effect immediately Classification: Applications Product: systemsettings Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: plasma-b...@kde.org Reporter: gu...@sanguepreto.de CC: nicolas.fe...@gmx.de Target Milestone: --- SUMMARY I wanted to inspect an autostart entry in my list that didn't have a name. Not sure what that horizontal line at the end meant, I clicked it, only to discover I just had removed the entry. (BTW: Who thinks it's a good idea to hide the button until you hover it?) Well, I didn't press the apply button yet, so nothing to worry, right? Wrong. Entry gone. STEPS TO REPRODUCE 1. Click the minus button of an entry. OBSERVED RESULT 2. See the entry disappear. 3. Find out there are no apply/cancel buttons. EXPECTED RESULT Find apply and cancel button like in the other settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed KDE Plasma Version: 5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405404] Walk Through Windows of Current Application does not work with Keyboard Layout with dead keys
https://bugs.kde.org/show_bug.cgi?id=405404 --- Comment #8 from Guido Sanchez --- Apparently is a merge request for that has the patches for Qt5 https://invent.kde.org/qt/qt/qtbase/-/merge_requests/239 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466528] Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore
https://bugs.kde.org/show_bug.cgi?id=466528 --- Comment #2 from Guido Schmidt --- Thanks, that was it! I actullay saw this setting. But the German translation is so misleading that I didn't even try it: "Automatisch zur Gegenseite navigieren" which more or less translates to "Automatically navigate to the opposite side". I have to admit that I have a hard time finding a good and concise German wording. So can this be changed into a translation bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466204] Black screen at startup if an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=466204 --- Comment #10 from Guido --- (In reply to Nate Graham from comment #9) > Darn. Thanks. > > Does it work if you log in to a Wayland session? Or is that broken too? Yes, also in Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466204] Black screen at startup if an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=466204 --- Comment #8 from Guido --- (In reply to Nate Graham from comment #7) > Thanks, now can you attach the output of `kscreen-doctor -o` after the bug > has happened? > > That way I can compare the output between working and broken system states, I can't. When the bug appears, the system is freezed. I need to hard reset the laptop -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466528] New: Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore
https://bugs.kde.org/show_bug.cgi?id=466528 Bug ID: 466528 Summary: Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore Classification: Applications Product: systemsettings Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: gu...@sanguepreto.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY Some time in fall 2022 (maybe when 5.26 landed) the shortcut that allowed me to cycle between virtual desktops does not bring me from the last to first one anymore. Imagine having three Desktops A, B and C. I used to be able to go from C to A. STEPS TO REPRODUCE 1. Configure a shortcut for "Switch to next desktop", for instance Meta+Tab. 2. Configure 3 desktops A B C. 3. Go to desktop C. 4. Hit Meta+Tab OBSERVED RESULT Nothing happens. EXPECTED RESULT Switch to desktop A. SOFTWARE/OS VERSIONS Linux: Opensuse Tumbleweed KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION "Switch to next desktop" may not be the literal name, I translated it from the German localization: "Zur nächsten Arbeitsfläche umschalten". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466204] Black screen at startup if an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=466204 --- Comment #6 from Guido --- (In reply to Guido from comment #3) > (In reply to Nate Graham from comment #1) > > Does this still happen if you configure the internal display to be on? > > I'm trying. The bug occurs often but not every time, so I need to do more > tests. I tried and the bug arises also when the internal dosplay is setted on. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466204] Black screen at startup if an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=466204 --- Comment #5 from Guido --- I would like to add one more detail: after logging in, the Plasma splash screen appears for 2-3 seconds, only then the screen goes black and the PC completely freezes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466204] Black screen at startup if an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=466204 --- Comment #4 from Guido --- Another thing I notice is that if I start with the 5.15 kernel, after logging in the internal screen turns off and the system starts on the external one without pause, whereas with the 6.2 kernel the external screen goes black for 2 seconds and then turns on again, unless it remains black because of the bug. The bug in this report did not occur with version 5.26, but the black screen for 2 seconds with the 6.x kernel also happened with 5.26 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466204] Black screen at startup if an external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=466204 --- Comment #3 from Guido --- (In reply to Nate Graham from comment #1) > Does this still happen if you configure the internal display to be on? I'm trying. The bug occurs often but not every time, so I need to do more tests. -- You are receiving this mail because: You are watching all bug changes.
