[neon] [Bug 485494] fcitx5 qt6 library cause desktop failed to start, their maintainer suggests rebuilding the package against new qt
https://bugs.kde.org/show_bug.cgi?id=485494 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Leonard Lausen --- It seems this issue is introduced in fcitx-config-qt 5.1.4-0xneon+22.04+jammy+release+build3 whereas the older 5.1.3-1+22.04+jammy+release+build1 works fine. Is there an archive of the prior packages available? For example, something similar to https://snapshot.debian.org/ for Debian? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452921] Entering wrong password for LUKS encrypted drive n times opens n+1 Dolphin windows once you finally provide the correct password
https://bugs.kde.org/show_bug.cgi?id=452921 Leonard Menzel changed: What|Removed |Added CC||leonard.men...@tutanota.com --- Comment #2 from Leonard Menzel --- Can reproduce it on the Latest Version: Operating System: NixOS 24.05 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478261] New: Flickering on scolling the window propertys
https://bugs.kde.org/show_bug.cgi?id=478261 Bug ID: 478261 Summary: Flickering on scolling the window propertys Classification: Plasma Product: kwin Version: 5.27.10 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: leonard.men...@tutanota.com CC: isma...@gmail.com Target Milestone: --- SUMMARY in the popup "+ Eigenschaft hinzufügen" in systemsettings managing the window rules scrolling with touchpad resultes in flickering up and down STEPS TO REPRODUCE 1. Open Window Rule Settings page 2. open the add propertys popup 3. try to scroll with a touchpad OBSERVED RESULT scroll position jumping up and down EXPECTED RESULT scrolling SYSTEM INFORMATION Operating System: NixOS 23.11 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.7.0-rc4 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION remeber that it happens on older plasma 5.27 versions too -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408182] Scaling with the transform tool deletes the selection
https://bugs.kde.org/show_bug.cgi?id=408182 --- Comment #19 from Unciaa Leonard --- I can no longer reproduce the bug with the given steps as of 5.1.5 (Windows), though admittedly I did not think to try and reproduce it again with the old version first prior to updating to rule out a system issue. -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468557] dark mode not readable
https://bugs.kde.org/show_bug.cgi?id=468557 --- Comment #1 from Leonard Menzel --- Created attachment 158139 --> https://bugs.kde.org/attachment.cgi?id=158139=edit screen shot in dark mode add second attachment -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468557] New: dark mode not readable
https://bugs.kde.org/show_bug.cgi?id=468557 Bug ID: 468557 Summary: dark mode not readable Classification: Applications Product: Arianna Version: 1.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: c...@carlschwan.eu Reporter: leonard.men...@tutanota.com Target Milestone: --- Created attachment 158138 --> https://bugs.kde.org/attachment.cgi?id=158138=edit screen shot in light mode SUMMARY in some books (for example functional programming in java [ ipfs cid: QmQ72DfkfaZ3iuqdapUxf4HZ798HoDHSCdoiqkr2voDhTh ] pictures in the attachmments) the colors in dark mode dont have enough contrast. on some other books it works perfectly. my wild guess is that if the epub defines a font color, the dark mode changes the background, but not the font color. STEPS TO REPRODUCE 1. install arianna flatpak 2. open the same book on light mode and on dark mode 3. try to read OBSERVED RESULT dark gray font on dark gray background with inverted colors in the settings light gray font on wihte background EXPECTED RESULT same contrast as in light mode (white or light gray font) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-38-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Pulse 15 Gen2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468513] Arianna crash when added some books
https://bugs.kde.org/show_bug.cgi?id=468513 Leonard Menzel changed: What|Removed |Added CC||leonard.men...@tutanota.com --- Comment #2 from Leonard Menzel --- the crash happens on my machine to. for example with the book erebos 2 (ipfs cid: bafykbzaceaergvgq4nged4yodtxogwwtrvzl33i2ybqo2cc6panjrf6ojlld4 , found on https://de.annas-archive.org/md5/a2ce5cf0fc8c69037f64d27810310d17) no matter how the filename is. i get the output in terminal. leonard@pacon:~$ flatpak run org.kde.arianna F: Filesystem suffix "rw" is not applicable for --nofilesystem Broken filename passed to function Broken filename passed to function Broken filename passed to function search started kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" <--!!! this is the first line after trying to open the book "Not connected to D-Bus server" kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" kf.solid.backends.udisks2: Failed enumerating UDisks2 objects: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server" -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 Leonard Menzel changed: What|Removed |Added CC||leonard.men...@tutanota.com --- Comment #1 from Leonard Menzel --- i guess its a duplicate of #468468 but not sure current workaround for me is to change the permissions for arianna to have no access for the file system. somehow without filesystem acces arianna can start. -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468468] Start up failing
https://bugs.kde.org/show_bug.cgi?id=468468 Leonard Menzel changed: What|Removed |Added Summary|[ Wayland ]Start up failing |Start up failing -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468468] [ Wayland ]Start up failing
https://bugs.kde.org/show_bug.cgi?id=468468 Leonard Menzel changed: What|Removed |Added Attachment #158070|0 |1 is obsolete|| --- Comment #5 from Leonard Menzel --- Created attachment 158074 --> https://bugs.kde.org/attachment.cgi?id=158074=edit try to start arianna via terminal screenshot v2 installed the new one but it still wont start (semes the wayland permission wasnt the only bug. ) -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468468] [ Wayland ]Start up failing
https://bugs.kde.org/show_bug.cgi?id=468468 --- Comment #3 from Leonard Menzel --- (In reply to Carl Schwan from comment #1) > Thanks for the report, fix for it can be found here: > https://github.com/flathub/org.kde.arianna/pull/1 which I am going to merge > as soon as the pipeline finish. sorry didnt notice you answered already -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468468] [ Wayland ]Start up failing
https://bugs.kde.org/show_bug.cgi?id=468468 --- Comment #2 from Leonard Menzel --- Created attachment 158071 --> https://bugs.kde.org/attachment.cgi?id=158071=edit pine phone flatpak run screenshot Also happens on the pinephone pro with postmarketos edge plasma mobile -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468468] New: [ Wayland ]Start up failing
https://bugs.kde.org/show_bug.cgi?id=468468 Bug ID: 468468 Summary: [ Wayland ]Start up failing Classification: Applications Product: Arianna Version: 1.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: c...@carlschwan.eu Reporter: leonard.men...@tutanota.com Target Milestone: --- Created attachment 158070 --> https://bugs.kde.org/attachment.cgi?id=158070=edit try to start arianna via terminal screenshot SUMMARY *** arianna does not start *** STEPS TO REPRODUCE 1. install the flatpack 2. click on the icon in the launcher or run in terminal 3. OBSERVED RESULT nothing happens (in terminal get error message and terminate) EXPECTED RESULT open arianna SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-38-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 62.2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Pulse 15 Gen2 ADDITIONAL INFORMATION happens on fresh installation. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 464466] background image and pinned applications dont survive reboot
https://bugs.kde.org/show_bug.cgi?id=464466 Leonard Menzel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 464466] background image and pinned applications dont survive reboot
https://bugs.kde.org/show_bug.cgi?id=464466 --- Comment #5 from Leonard Menzel --- just tried again and it seems to work now. i dont realy know the technial part but it was a fresh installation and maybe the first reboot (the one that the favorites did not survive) was for the shutdown part on an older version. only read the version numbers after reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 464466] background image and pinned applications dont survive reboot
https://bugs.kde.org/show_bug.cgi?id=464466 --- Comment #3 from Leonard Menzel --- installed postmarket os now on my pinephone pro and it has the same issue // Plasma 7.27.3 // Kernel 6.2.2 PostmarketOS edge aarch64 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465262] Duplicate counter when install applications
https://bugs.kde.org/show_bug.cgi?id=465262 Leonard Menzel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||leonard.men...@tutanota.com --- Comment #1 from Leonard Menzel --- it seemes every time the discover window is closed a new notification spawns no matter if there is already one. it stacks up. closing discover 3 times gives 3 times the same notification. happens on my device too: Betriebssystem: KDE neon 5.26 KDE-Plasma-Version: 5.26.5 KDE-Frameworks-Version: 5.102.0 Qt-Version: 5.15.8 Kernel-Version: 5.15.0-58-generic (64-bit) Grafik-Plattform: Wayland Prozessoren: 16 × AMD Ryzen 7 5700U with Radeon Graphics Speicher: 62,2 GiB Arbeitsspeicher Grafikprozessor: AMD Radeon Graphics Hersteller: TUXEDO Produktname: TUXEDO Pulse 15 Gen2 -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 464510] [mobile] [ui] cant escape settings
https://bugs.kde.org/show_bug.cgi?id=464510 Leonard Menzel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Leonard Menzel --- there is a back button now :) -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 464461] [mobile] [UI] missplaced thumbnail and buttons in now playing view
https://bugs.kde.org/show_bug.cgi?id=464461 Leonard Menzel changed: What|Removed |Added Attachment #155405|0 |1 is obsolete|| --- Comment #1 from Leonard Menzel --- Created attachment 155887 --> https://bugs.kde.org/attachment.cgi?id=155887=edit screenshot with newer version.(23.01 from 30.01.2023 flatpak) looks fixed for thumbnail and media controll buttons, only the tabs glitch out of the screen now -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464454] [mobile] [ui] Scrolling on description of an app select text instead of scrolling
https://bugs.kde.org/show_bug.cgi?id=464454 Leonard Menzel changed: What|Removed |Added Summary|Scrolling on description of |[mobile] [ui] Scrolling on |an app select text instead |description of an app |of scrolling|select text instead of ||scrolling -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461159] adjusting Region & Language settings - error about missing "check-language-support" executable
https://bugs.kde.org/show_bug.cgi?id=461159 --- Comment #4 from Leonard Menzel --- happens not just in live environement also if installed. no matter which language to which language -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461159] adjusting Region & Language settings - error about missing "check-language-support" executable
https://bugs.kde.org/show_bug.cgi?id=461159 Leonard Menzel changed: What|Removed |Added Summary|22.04 user edition iso |adjusting Region & Language |(20221023-0714) - adjusting |settings - error about |Region & Language settings |missing |- error about missing |"check-language-support" |"check-language-support"|executable |executable | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461159] 22.04 user edition iso (20221023-0714) - adjusting Region & Language settings - error about missing "check-language-support" executable
https://bugs.kde.org/show_bug.cgi?id=461159 Leonard Menzel changed: What|Removed |Added CC||leonard.men...@tutanota.com --- Comment #3 from Leonard Menzel --- Created attachment 155665 --> https://bugs.kde.org/attachment.cgi?id=155665=edit screenshot settings language change error same here. Operating System: KDE neon Testing Edition KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 62,2 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: TUXEDO Product Name: TUXEDO Pulse 15 Gen2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461159] 22.04 user edition iso (20221023-0714) - adjusting Region & Language settings - error about missing "check-language-support" executable
https://bugs.kde.org/show_bug.cgi?id=461159 Leonard Menzel changed: What|Removed |Added CC||kangar...@gmail.com --- Comment #2 from Leonard Menzel --- *** Bug 462589 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462589] KDE neon 5.26 installed, changing Language gives error
https://bugs.kde.org/show_bug.cgi?id=462589 Leonard Menzel changed: What|Removed |Added CC||leonard.men...@tutanota.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Leonard Menzel --- *** This bug has been marked as a duplicate of bug 461159 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464454] Scrolling on description of an app select text instead of scrolling
https://bugs.kde.org/show_bug.cgi?id=464454 --- Comment #2 from Leonard Menzel --- i would prefer select on long press -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 354393] Live session asking for password when booting from live USB
https://bugs.kde.org/show_bug.cgi?id=354393 Leonard Menzel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||leonard.men...@tutanota.com Resolution|--- |UNMAINTAINED --- Comment #3 from Leonard Menzel --- resolve this bug unmaintained because kubuntu 15 is eol for years now -- You are receiving this mail because: You are watching all bug changes.
[unknown] [Bug 357176] volume mount failed after upgrade of the parallel system to Win10
https://bugs.kde.org/show_bug.cgi?id=357176 Leonard Menzel changed: What|Removed |Added CC||leonard.men...@tutanota.com --- Comment #3 from Leonard Menzel --- i would recommend to do a fresh install of both operating systems. and use ext4 for the linux drive (ext4 is not readable from windows so it probably make no unexpected changes.). also i strongly recommend to not use grub + osprobe or simmilar cause it probably confuses windows. just change the bootdevice in bios when boot to the other system -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 464524] New: [moblie] [ui] Queue not visible
https://bugs.kde.org/show_bug.cgi?id=464524 Bug ID: 464524 Summary: [moblie] [ui] Queue not visible Classification: Applications Product: audiotube Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: leonard.men...@tutanota.com Target Milestone: --- Created attachment 155437 --> https://bugs.kde.org/attachment.cgi?id=155437=edit screenshot pinephone pro audiotube at queue tab SUMMARY *** the queue is not visible *** STEPS TO REPRODUCE 1. open audiotube 2. play an album 3. go to queue tab OBSERVED RESULT empty space EXPECTED RESULT the following songs SOFTWARE/OS VERSIONS audiotube: 22.11 Flatpak Linux/KDE Plasma: 5.26.5 mobile manjaro arm on pinephone pro KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION i completely reinstalled the flatpak and even the os is a realy fresh install of manjaro testing. that does not happen on my laptop (kde neon, same flatpak version, also fresh install) -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 464466] background image and pinned applications dont survive reboot
https://bugs.kde.org/show_bug.cgi?id=464466 --- Comment #2 from Leonard Menzel --- updated to 5.26.5 and it still resets every reboot -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 464510] New: [mobile] [ui] cant escape settings
https://bugs.kde.org/show_bug.cgi?id=464510 Bug ID: 464510 Summary: [mobile] [ui] cant escape settings Classification: Applications Product: angelfish Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: leonard.men...@tutanota.com Target Milestone: --- Created attachment 155429 --> https://bugs.kde.org/attachment.cgi?id=155429=edit screenshot on pinephone pro with settings open SUMMARY *** there is no back button or gesture or window to close etc to close the settings without closing the whole app in mobile mode *** STEPS TO REPRODUCE 1. open angelfish in mobile (i did on pinephone) 2. enter settings EXPECTED RESULT a way to exit the settings without closing the application SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.4 manjaro arm on pinephone pro KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 464461] [mobile] [UI] missplaced thumbnail and buttons in now playing view
https://bugs.kde.org/show_bug.cgi?id=464461 Leonard Menzel changed: What|Removed |Added Summary|missplaced thumbnail and|[mobile] [UI] missplaced |buttons in now playing view |thumbnail and buttons in ||now playing view -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 464470] New: misplaced page titel
https://bugs.kde.org/show_bug.cgi?id=464470 Bug ID: 464470 Summary: misplaced page titel Classification: Applications Product: Tokodon Version: 23.01.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: leonard.men...@tutanota.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 155407 --> https://bugs.kde.org/attachment.cgi?id=155407=edit photo of pinephone with tokodon open SUMMARY *** in mobile layout, the titles in the tabs home, local, and global timeline are under the header *** SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 plasma mobile manjaro - arm pinephone pro (available in About System) KDE Frameworks Version: 5.101.0 Qt Version: 1.15.7 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 464469] New: no error message or indication that server down
https://bugs.kde.org/show_bug.cgi?id=464469 Bug ID: 464469 Summary: no error message or indication that server down Classification: Applications Product: Tokodon Version: 23.01.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: leonard.men...@tutanota.com CC: c...@carlschwan.eu Target Milestone: --- when the instance you use is down, there is no indicator or error message that tells you its the servers fault. What actualy happens: every list stays empty, no loading or simmilar Expected behavior: something like [http error message], server not responding -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 464466] New: background image and pinned applications dont survive reboot
https://bugs.kde.org/show_bug.cgi?id=464466 Bug ID: 464466 Summary: background image and pinned applications dont survive reboot Classification: Plasma Product: plasma-mobile Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Shell Assignee: plasma-mobile-bugs-n...@kde.org Reporter: leonard.men...@tutanota.com Target Milestone: --- SUMMARY *** every time i reboot the device, the favorite apps and the backgroundimage are reset to the default wich is kai as image and no apps as favorite. *** STEPS TO REPRODUCE 1. change wallpaper 2. add apps to the favorites 3. reboot device OBSERVED RESULT reset image and no favorites anymore EXPECTED RESULT changes to be persistent SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 manjaro-arm on pinephone pro KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION i dont know if its a plasma bug or if its a manjaro thing. i didnt tested es on other operating systems -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 464462] New: [moblie] no way to exit settings
https://bugs.kde.org/show_bug.cgi?id=464462 Bug ID: 464462 Summary: [moblie] no way to exit settings Classification: Applications Product: NeoChat Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: leonard.men...@tutanota.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY *** once entered the settings, it is not possible to exit them. need to stop the whole app and reopen it on desktop clicking on the settings menu item it opens a new window with the settings. on mobile it seems to overlay the main window. since there is only touch on the phone its not possible to exit it with esc button or something. and its the same window so closing the window and reopen it brings me back to the setting. *** note: if entered the settings while a chat is open, the back button from the chat still works to escape the settings. so its only problematic when entered from the chat and room list STEPS TO REPRODUCE 1. open neochat 2. tap left up hamburger menu and click: (in german its NeoChat einrichten) i guess its called set up neochat or something simmilar 3. try to escape OBSERVED RESULT no back button EXPECTED RESULT anything to cloze the settings a back button, a save and exit button, or the settings opened in another window wich i can close SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 manjaro arm on pinephone pro (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 neochat version 22.11-3 (not the flatpak) ADDITIONAL INFORMATION i tried to film it, but culdnt get screen recording working so i filmed it with another smart phone: sorry for the bad quality, but i hope its a little clearer what i mean now: https://photos.app.goo.gl/NBuiWshaZBcPqx5r5 <-- on google photos because its to large to add as attachment -- You are receiving this mail because: You are watching all bug changes.
[audiotube] [Bug 464461] New: missplaced thumbnail and buttons in now playing view
https://bugs.kde.org/show_bug.cgi?id=464461 Bug ID: 464461 Summary: missplaced thumbnail and buttons in now playing view Classification: Applications Product: audiotube Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@kaidan.im Reporter: leonard.men...@tutanota.com Target Milestone: --- Created attachment 155405 --> https://bugs.kde.org/attachment.cgi?id=155405=edit photo of the pinephone with audiotube open SUMMARY *** The whole ui of the section where you can see the now playing track is shifted to the right. (i guess its because it thinks it cant fit in the available space) *** STEPS TO REPRODUCE 1. open autdiotube 2. select a track 3. click on the track on the bottom to make the playing song fullscreen OBSERVED RESULT looks like the window actually goes byond the screen edge EXPECTED RESULT every clickable element inside of the screen bounds SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 on manjaro arm running on pinephone pro audiotube version: 22.11 KDE Plasma Version: 5.26.4 (plasma mobile) KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION audiotube installed with flatpak dont know if its relevant but: plasma_style: chromeOS, icon_set: ePapirus display settings scale reduced from default 200% to 175% -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464454] New: Scrolling on description of an app select text instead of scrolling
https://bugs.kde.org/show_bug.cgi?id=464454 Bug ID: 464454 Summary: Scrolling on description of an app select text instead of scrolling Classification: Applications Product: Discover Version: 5.26.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: leonard.men...@tutanota.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** In the Mobile layout, scrolling with touch selecct the text underneath instead of scrolling through the page *** STEPS TO REPRODUCE 1. open Discover in mobile layout. 2. go to an app's page wich has a long discription 3. try to scroll with touch starting the finger in the middle of the discription OBSERVED RESULT the description text gets selected. EXPECTED RESULT scroll through the description SOFTWARE/OS VERSIONS macOS: Linux/KDE Plasma: Manjaro Arm on pinephone pro with plasma mobile (available in About System) KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel: 6.1.0-1-MANJARO-ARM ADDITIONAL INFORMATION its only a big deal if the description covers the whole scrollable area because then scrolling with only touch is impossible. and on phone there is only touch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462984] [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor
https://bugs.kde.org/show_bug.cgi?id=462984 --- Comment #2 from Leonard Lausen --- Printenv shows PLASMA_USE_QT_SCALING=1. Maybe that's the default for Wayland? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462984] [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor
https://bugs.kde.org/show_bug.cgi?id=462984 --- Comment #1 from Leonard Lausen --- Created attachment 154551 --> https://bugs.kde.org/attachment.cgi?id=154551=edit Screenshot of buggy scaling -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462984] New: [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor
https://bugs.kde.org/show_bug.cgi?id=462984 Bug ID: 462984 Summary: [Wayland] Disabling Laptop monitor breaks icon and window button scaling on external monitor Classification: Plasma Product: kwin Version: 5.26.4 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- Created attachment 154550 --> https://bugs.kde.org/attachment.cgi?id=154550=edit Screenshot with both displays SUMMARY With a FullHD Laptop display and 2K external display, disabling the laptop display (closing the laptop lid) breaks icon and window button scaling on the remaining display. It doesn't matter if the laptop display or external display is configured as primary. STEPS TO REPRODUCE 1. Obtain laptop with FullHD screen and 2K external monitor. 2. Start a Wayland session with both displays. 3. Close laptop lid OBSERVED RESULT Window icon (upper left corner of the window) as well as the window minimize, maximize and close buttons scale breaks and their size doubles. EXPECTED RESULT Window icon and button scale is not affected by disabling the laptop display SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100 Qt Version: 5.15.6 ADDITIONAL INFORMATION See screenshots attached -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #5 from Leonard Lausen --- Created attachment 154487 --> https://bugs.kde.org/attachment.cgi?id=154487=edit drm_info.txt -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 Leonard Lausen changed: What|Removed |Added CC||vlad.zahorod...@kde.org --- Comment #4 from Leonard Lausen --- The verbose DRM dmesg log shows that all configurations tried by kwin fail the kernel drm_atomic_plane_check, specifically the plane_switching_crtc sanity check [1], meaning that kwin triggers unsupported direct switching of CRTCs. Any ideas why that may happen? msm_dpu ae01000.display-controller: [drm:drm_atomic_check_only] [PLANE:41:plane-0] switching CRTC directly msm_dpu ae01000.display-controller: [drm:drm_atomic_check_only] [PLANE:41:plane-0] atomic core check failed I also noticed that above kwin_wayland_drm output says `"rotation": 1` and `"rotation"=invalid value: 1`. @vladz uploaded a log containing `"rotation": 1` at https://invent.kde.org/-/snippets/1976 Any ideas if that is the root-cause? [1]: https://github.com/torvalds/linux/blob/faf68e3523c21d07c5f7fdabd0daf6301ff8db3f/drivers/gpu/drm/drm_atomic.c#L565-L581 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #3 from Leonard Lausen --- Created attachment 154013 --> https://bugs.kde.org/attachment.cgi?id=154013=edit dmesg with verbose DRM logging -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #2 from Leonard Lausen --- Attaching kernel log with verbose DRM logging, which may help determining why KWin is issuing an invalid command and which. KWin is started at [17471.518135] and killed at [17510.700261]. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462214] New: "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 Bug ID: 462214 Summary: "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU) Classification: Plasma Product: kwin Version: 5.26.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-drm Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- Created attachment 154000 --> https://bugs.kde.org/attachment.cgi?id=154000=edit startplasma-wayland debug log KWin Wayland session is currently broken on ARM devices such as Acer Spin 513 Chromebook with Qualcomm Snapdragon 7c [1] if an external display is used. There are no issues with using the KWin X11 session in this setting with external display, nor any issues with the KWin Wayland session as long as no external display is connected. STEPS TO REPRODUCE 1. Obtain a laptop with Qualcomm Snapdragon chipset 2. From a tty run `export QT_LOGGING_RULES="kwin_*.debug=true"; startplasma-wayland > ~/startplasma-wayland.log 2>&1 ` 3. Wait a minute and `killall startplasma-wayland` from the serial console (as kwin took over the tty and can't be interrupted) OBSERVED RESULT The tty continues to be displayed and kwin fails to start a graphical session and hangs indefinitely. EXPECTED RESULT kwin successfully starts a plasma session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.0.8 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Full startplasma-wayland.log attached. Also attached is startplasma-wayland-newuser.log which contains the debug log upon reproducing with a fresh user (sudo adduser test). Both logs are substantially similar, but have small differences in the debug messages regarding Drm objects. Relevant excerpt: No backend specified, automatically choosing drm kwin_wayland_drm: Skipping KMS incapable drm device node at "/dev/dri/card0" kwin_wayland_drm: drmModeAddFB2WithModifiers is supported on GPU "/dev/dri/card1" kwin_wayland_drm: Using Atomic Mode Setting on gpu "/dev/dri/card1" kwin_wayland_drm: Number of planes on GPU "/dev/dri/card1" : 4 kwin_wayland_drm: Plane 41 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=125829120, "SRC_H"=70778880, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=1920, "CRTC_H"=1080, "FB_ID"=68, "CRTC_ID"=65, "rotation"=invalid value: 1, "IN_FORMATS"=42 kwin_wayland_drm: Plane 47 has properties "type"="Primary", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=125829120, "SRC_H"=70778880, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=1920, "CRTC_H"=1080, "FB_ID"=68, "CRTC_ID"=66, "rotation"=invalid value: 1, "IN_FORMATS"=48 kwin_wayland_drm: Plane 53 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=54 kwin_wayland_drm: Plane 59 has properties "type"="Cursor", "SRC_X"=0, "SRC_Y"=0, "SRC_W"=0, "SRC_H"=0, "CRTC_X"=0, "CRTC_Y"=0, "CRTC_W"=0, "CRTC_H"=0, "FB_ID"=0, "CRTC_ID"=0, "rotation"=invalid value: 1, "IN_FORMATS"=60 kwin_wayland_drm: Crtc 65 has properties "MODE_ID"=69, "ACTIVE"=1, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found kwin_wayland_drm: Crtc 66 has properties "MODE_ID"=71, "ACTIVE"=1, "VRR_ENABLED"=0, "GAMMA_LUT" not found, "GAMMA_LUT_SIZE" not found [...] kwin_core: KGlobalAcceld inited kwin_core: Attempting to load the OpenGL scene kwin_scene_opengl: Egl Initialize succeeded kwin_scene_opengl: EGL version: 1 . 5 kwin_scene_opengl: Created EGL context with attributes: Version requested: true Version:3.1 Robust: true Reset on video memory purge:false Forward compatible: false Core profile: false Compatibility profile: false High priority: true kwin_scene_opengl: Created EGL context with attributes: Version requested: true Version:3.1 Robust: true Reset on video memory purge:false Forward compatible: false Core profile: false Compatibility profile: false High priority: true OpenGL vendor string: freedreno OpenGL renderer string: FD618 OpenGL version string: 3.3 (Core Profile) Mesa 22.2.4 OpenGL shading language version string: 3.30 Driver: Unknown GPU class: Unknown OpenGL version: 3.3 GLSL version: 3.30 Mesa version: 22.2.4 Linux kernel version: 6.0.8 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_scene_opengl: Filter multi-plane format 961959257
[kwin] [Bug 462214] "kwin_wayland_drm: Failed to find a working setup for new outputs!" "Atomic modeset test failed! Invalid argument" with external display (Qualcomm GPU)
https://bugs.kde.org/show_bug.cgi?id=462214 --- Comment #1 from Leonard Lausen --- Created attachment 154001 --> https://bugs.kde.org/attachment.cgi?id=154001=edit startplasma-wayland debug log based on a new test user -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input
https://bugs.kde.org/show_bug.cgi?id=435338 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458882] Menu Bar display only if executed as root (sudo/su)
https://bugs.kde.org/show_bug.cgi?id=458882 --- Comment #11 from Leonard --- I'm happy to see that at least a the culprit was found. In the mean time i gave up on the "app menu" button entirely. I turned off the button and after rebooting the Menu Bar reappears on krita, (Ctrl + Shift + M does not work btw) Sorry for the inconvenience -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458882] Menu Bar display only if executed as root (sudo/su)
https://bugs.kde.org/show_bug.cgi?id=458882 --- Comment #5 from Leonard --- (In reply to Nicolas Fella from comment #4) > Judging from your screenshot you are using a titlebar menu button. That > means that the in-app menubar is disabled. > > If you want the in-app menu bar you need to remove the menu button from the > window decoration I prefer the menu button over the in-app menubar but the problem is that neither of them work as non root user -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458882] Menu Bar display only if executed as root (sudo/su)
https://bugs.kde.org/show_bug.cgi?id=458882 --- Comment #3 from Leonard --- (In reply to Qualimer Judith from comment #2) > Quick question - do you have a global menu applet enabled in your Plasma > desktop? Does this behaviour persist if you remove it, if so? No, I haven't Installed any applet for Plasma that shouldn't be the cause. I've been using Linux for a little less than a month, I'm not really sure what a 'global menu applet' is. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458882] Menu Bar display only if executed as root (sudo/su)
https://bugs.kde.org/show_bug.cgi?id=458882 Leonard changed: What|Removed |Added Attachment #151926|0 |1 is obsolete|| --- Comment #1 from Leonard --- Created attachment 151927 --> https://bugs.kde.org/attachment.cgi?id=151927=edit On top the menubar showing on krita ran as super user, on bottom krita ran as normal user -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458882] New: Menu Bar display only if executed as root (sudo/su)
https://bugs.kde.org/show_bug.cgi?id=458882
Bug ID: 458882
Summary: Menu Bar display only if executed as root (sudo/su)
Product: krita
Version: 5.1.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Usability
Assignee: krita-bugs-n...@kde.org
Reporter: leomonta2...@gmail.com
Target Milestone: ---
Created attachment 151926
--> https://bugs.kde.org/attachment.cgi?id=151926=edit
krita executa as normal user
SUMMARY
***
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE (Even if i don't think that this is not easily reproducible)
1. Open krita from CLI as non root user
2. Open krita from CLI as root user (su or sudo)
OBSERVED RESULT
The menu bar ('File' 'Edit' 'View' etc..) is not visible like normal
nor with the 'application menu' button of KDE Plasma
As super user the menu bar appear (ignoring the 'application menu' button)
EXPECTED RESULT
The Menu bar should appear regardless of being executed as super user or not
And the Menu bar should be visible from the 'application menu' button on Plasma
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch 5.19.7-arch1-1
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
ADDITIONAL INFORMATION
using wayland or X11 does not change behavior
I already tried removing and reinstalling krita via pacman to no avail
deleted both kritarc in the .config folder (kritarc and kritadisplayrc)
Changed the voice 'MenuBar=Disabled' to 'MenuBar=Enabled' in the kritarc
but the file is reset as soon as krita starts
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 439052] kdenlive does not obey global desktop colors
https://bugs.kde.org/show_bug.cgi?id=439052 Leonard Menzel changed: What|Removed |Added CC||leonard.men...@tutanota.com --- Comment #5 from Leonard Menzel --- I use Kdenlive 22.04.3 (the ppa version) in KDE Neon and if i open kdenlive it uses the default breeze dark color scheme in the settings standard is selektet. if i click again on standard it uses my globaly defined colorscheme but if i restart kdenlive it goes back to breeze dark, but shows standard anyway -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408182] Scaling with the transform tool deletes the selection
https://bugs.kde.org/show_bug.cgi?id=408182 Unciaa Leonard changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 457088] New: man page section for debugging Flatpak applications
https://bugs.kde.org/show_bug.cgi?id=457088 Bug ID: 457088 Summary: man page section for debugging Flatpak applications Product: valgrind Version: 3.19.0 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: fedora-topics-562...@protonmail.com Target Milestone: --- I'd like to have a section in Valgrind's man page that details how one should use it when debugging a Flatpak application. The best guide I could find so far for this is at https://discourse.gnome.org/t/how-to-get-full-valgrind-report-in-builder/9883/9 but I'm not sure if this really is the best way, or the official way. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408182] Scaling with the transform tool deletes the selection
https://bugs.kde.org/show_bug.cgi?id=408182 Unciaa Leonard changed: What|Removed |Added CC||unc...@gmail.com --- Comment #15 from Unciaa Leonard --- Created attachment 150568 --> https://bugs.kde.org/attachment.cgi?id=150568=edit Demonstration of bug All I've done is create a new document in Krita 5.0.6, drew a squiggly line, lasso selected a portion and manipulated it, then moved the full layer to demonstrate that, while the original selection may still be visible in the draw buffer, it is in fact gone. This is in Windows 10 on a 2560x1440, 144Hz display, with an nVidia 3070ti and the latest (516.59) drivers, though since the original report was a while ago it's safe to assume neither the specific Krita nor display driver version are required. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455720] Night Light broken on ARM devices (Missing Color Transform Matrix support)
https://bugs.kde.org/show_bug.cgi?id=455720 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455720] New: Night Light broken on ARM devices (Missing Color Transform Matrix support)
https://bugs.kde.org/show_bug.cgi?id=455720
Bug ID: 455720
Summary: Night Light broken on ARM devices (Missing Color
Transform Matrix support)
Product: kwin
Version: unspecified
Platform: unspecified
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-drm
Assignee: kwin-bugs-n...@kde.org
Reporter: leon...@lausen.nl
Target Milestone: ---
Night Light is currently broken on ARM devices such as Acer Spin 513 Chromebook
with Qualcomm Snapdragon 7c [1], as it relies on legacy GAMMA_LUT which is not
supported by the Qualcomm SoCs.
Instead of relying on GAMMA_LUT, these SoCs implement Color Transform Matrix
(CTM), which for example Chrome OS uses to implement their version of night
light. Both GAMMA_LUT and TM are configured through the KMS CRTC Abstraction
[2].
>From IRC #aarch64-laptops:
> robclark | leezu: on CrOS we use display CTM (CRTC property) on internal
> display.. one could also use the GPU for that.. not sure off the top of my
> head what different de's support
> robclark | leezu: yes, that is correct.. GAMMA_LUT is not supported, CTM
> (color transform matrix) is the way to achieve color transform
> robclark | not supported in hw.. CTM is a more general purpose feature
> robclark | GAMMA_LUT is kinda the legacy way, CTM is the new hotness ;-)
It would be great to support Night Light on ARM Laptops by implementing Night
Light via Color Transform Matrix instead of GAMMA_LUT.
drm_info output showing lack of GAMMA_LUT support:
Node: /dev/dri/card1
├───Driver: msm (MSM Snapdragon DRM) version 1.9.0 (20130625)
│ ├───DRM_CLIENT_CAP_STEREO_3D supported
│ ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
│ ├───DRM_CLIENT_CAP_ATOMIC supported
│ ├───DRM_CLIENT_CAP_ASPECT_RATIO supported
│ ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
│ ├───DRM_CAP_DUMB_BUFFER = 1
│ ├───DRM_CAP_VBLANK_HIGH_CRTC = 1
│ ├───DRM_CAP_DUMB_PREFERRED_DEPTH = 0
│ ├───DRM_CAP_DUMB_PREFER_SHADOW = 0
│ ├───DRM_CAP_PRIME = 3
│ ├───DRM_CAP_TIMESTAMP_MONOTONIC = 1
│ ├───DRM_CAP_ASYNC_PAGE_FLIP = 0
│ ├───DRM_CAP_CURSOR_WIDTH = 64
│ ├───DRM_CAP_CURSOR_HEIGHT = 64
│ ├───DRM_CAP_ADDFB2_MODIFIERS = 1
│ ├───DRM_CAP_PAGE_FLIP_TARGET = 0
│ ├───DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
│ ├───DRM_CAP_SYNCOBJ = 1
│ └───DRM_CAP_SYNCOBJ_TIMELINE = 0
├───Device: platform qcom,sc7180-mdss
│ └───Available nodes: primary, render
├───Framebuffer size
│ ├───Width: [0, 5120]
│ └───Height: [0, 4096]
├───Connectors
│ ├───Connector 0
│ │ ├───Object ID: 32
│ │ ├───Type: eDP
│ │ ├───Status: connected
│ │ ├───Physical size: 294x165 mm
│ │ ├───Subpixel: unknown
│ │ ├───Encoders: {0}
│ │ ├───Modes
│ │ │ └───1920x1080@60.00 preferred driver phsync nvsync
│ │ └───Properties
│ │ ├───"EDID" (immutable): blob = 61
│ │ ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│ │ ├───"link-status": enum {Good, Bad} = Good
│ │ ├───"non-desktop" (immutable): range [0, 1] = 0
│ │ ├───"TILE" (immutable): blob = 0
│ │ └───"CRTC_ID" (atomic): object CRTC = 59
│ └───Connector 1
│ ├───Object ID: 34
│ ├───Type: DisplayPort
│ ├───Status: disconnected
│ ├───Encoders: {1}
│ └───Properties
│ ├───"EDID" (immutable): blob = 0
│ ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│ ├───"link-status": enum {Good, Bad} = Good
│ ├───"non-desktop" (immutable): range [0, 1] = 0
│ ├───"TILE" (immutable): blob = 0
│ └───"CRTC_ID" (atomic): object CRTC = 0
├───Encoders
│ ├───Encoder 0
│ │ ├───Object ID: 31
│ │ ├───Type: DSI
│ │ ├───CRTCS: {0, 1}
│ │ └───Clones: {0}
│ └───Encoder 1
│ ├───Object ID: 33
│ ├───Type: TMDS
│ ├───CRTCS: {0, 1}
│ └───Clones: {1}
├───CRTCs
│ ├───CRTC 0
│ │ ├───Object ID: 59
│ │ ├───Legacy info
│ │ │ ├───Mode: 1920x1080@60.00 preferred driver phsync nvsync
│ │ │ └───Gamma size: 0
│ │ └───Properties
│ │ ├───"ACTIVE" (atomic): range [0, 1] = 1
│ │ ├───"MODE_ID" (atomic): blob = 66
│ │ │ └───1920x1080@60.00 preferred driver phsync nvsync
│ │ ├───"OUT_FENCE_PTR" (atomic): range [0, UINT64_MAX] = 0
│ │ ├───"VRR_ENABLED": range [0, 1] = 0
│ │ └───"CTM": blob = 0
│ └───CRTC 1
│ ├───Object ID: 60
│ ├───Legacy info
│ │ └───Gamma size: 0
│ └───Properties
│ ├───"ACTIVE" (atomic): range [0, 1] = 0
│ ├───"MODE_ID" (atomic): blob = 0
│ ├───"OUT_FENCE_PTR" (atomic): range [0, UINT64_MAX] = 0
│ ├───"VRR_ENABLED": range [0, 1] = 0
│ └───"CTM": blob = 0
└───Planes
├───Plane 0
│ ├───Object ID: 35
│ ├───CRTCs: {0, 1, 2, 3, 4, 5, 6, 7}
│ ├───Legacy info
│ │ ├───FB ID: 63
[Discover] [Bug 425380] Discover gets stuck at "Still looking" and never loads the list of app/plasma addons from KDE Store
https://bugs.kde.org/show_bug.cgi?id=425380 Leonard Schiff changed: What|Removed |Added CC||leona...@web.de Resolution|FIXED |REMIND --- Comment #13 from Leonard Schiff --- I have the same bug on Debian 11 Bullseye, fresh install. Made a topic in the Debian-forums and someone else reports the same behavior. https://forums.debian.net/viewtopic.php?f=6=150046 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 115269] Implement the UML 2.0 standard
https://bugs.kde.org/show_bug.cgi?id=115269 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428854] Nightcolor fails to activate after KWin or the whole session is restarted; must manually toggle it off and on again
https://bugs.kde.org/show_bug.cgi?id=428854 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432436] Keyboard layout with variant in 2nd slot prevents switching back to layout in 1st slot
https://bugs.kde.org/show_bug.cgi?id=432436 Leonard Lausen changed: What|Removed |Added Resolution|WORKSFORME |UPSTREAM --- Comment #6 from Leonard Lausen --- I responded upstream that the proposed patch doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crashes and display issues with mixed non-hiDPI / hiDPI multi-screen setup on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 Leonard Lausen changed: What|Removed |Added Summary|Crash in|Crashes and display issues |QMessageLogger::fatal when |with mixed non-hiDPI / |removing screen containing |hiDPI multi-screen setup on |system tray on wayland |wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 --- Comment #8 from Leonard Lausen --- As this bug is about Wine + XWayland, it's not fixed by the Wine Wayland version. Also I don't think it's clear if the XWayland issue reported here is a upstream bug or kwin bug. Compiling Wine Wayland branch can be used as a workaround. I wouldn't bother with the Xwayland issue as the workaround should in due time become part of stable Wine release. But others may feel different and may want to fix the Xwayland issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 --- Comment #6 from Leonard Lausen --- FYI, Alexandros fixed the KDE related bugs in the wine wayland branch and since March 4 2021 it works well (and much better than the XWayland version). The only caveat is that at this point Wine applications will always use en-us keyboard layout, but that will be fixed later. To install: mkdir -p ~/src/ cd ~/src git clone -b wayland https://gitlab.collabora.com/alf/wine/ ./configure --with-wayland make -j$(nproc) To use: WINEARCH="win32" DISPLAY= WAYLAND_DISPLAY=wayland-0 WINEPREFIX=~/.wine_wayland ~/src/wine/wine program.exe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 --- Comment #5 from Leonard Lausen --- Created attachment 136476 --> https://bugs.kde.org/attachment.cgi?id=136476=edit system-tray and layout issue when system tray on 4K screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 --- Comment #4 from Leonard Lausen --- Created attachment 136475 --> https://bugs.kde.org/attachment.cgi?id=136475=edit desktop background issue when system tray on FHD screen resolved after right click Note the filesize of this .png screenshot was double the size of screenshot taken before "right click" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 --- Comment #3 from Leonard Lausen --- Created attachment 136474 --> https://bugs.kde.org/attachment.cgi?id=136474=edit desktop background issue when system tray on FHD screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430835] Crash in QMessageLogger::fatal when removing screen containing system tray on wayland
https://bugs.kde.org/show_bug.cgi?id=430835 Leonard Lausen changed: What|Removed |Added Version|5.20.4 |5.21.2 CC||leon...@lausen.nl --- Comment #2 from Leonard Lausen --- Thank you Nate for taking a look. I think the behavior has improved as of Plasma 5.21. The session/plasmashell does not crash anymore when removing the screen containing the system try. However, the multi-screen behavior is not completely stable yet either. I observed two issues (please let me know if you'd rather have a new bug-report). Further, in the first message I forgot to include that the main screen (laptop screen) of the setup is a 4K screen and scaled, whereas the external screen is a FHD screen and not scaled. Issue 1: plasmashell can trigger qt5-wayland crash when moving the system tray between screens: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7fb5a0838d51 in raise () at /lib64/libc.so.6 #5 0x7fb5a0822536 in abort () at /lib64/libc.so.6 #6 0x7fb5a0c29c97 in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) [clone .cold] () at /usr/lib64/libQt5Core.so.5 #7 0x7fb59f002a50 in QtWaylandClient::QWaylandDisplay::blockingReadEvents() () at /usr/lib64/libQt5WaylandClient.so.5 #8 0x7fb59f002c3d in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) () at /usr/lib64/libQt5WaylandClient.so.5 #9 0x7fb59f00805e in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) () at /usr/lib64/libQt5WaylandClient.so.5 #10 0x7fb59c03e012 in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) () at /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #11 0x7fb5a274377c in QSGRenderThread::syncAndRender(QImage*) () at /usr/lib64/libQt5Quick.so.5 #12 0x7fb5a2743f47 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #13 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #14 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #15 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fb5791b0640 (LWP 67852) "QSGRenderThread"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a2741ad7 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb5a2743f89 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #6 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fb5737fe640 (LWP 65416) "Thread (pooled)"): #1 0x7fb5a0c66dc5 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a0c64762 in QThreadPoolThread::run() () at /usr/lib64/libQt5Core.so.5 #3 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #5 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb4f3fff640 (LWP 3076) "QSGRenderThread"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a2741ad7 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb5a2743f89 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #6 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb4fac9b640 (LWP 3047) "QSGRenderThread"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5a2741ad7 in QSGRenderThread::processEventsAndWaitForMore() () at /usr/lib64/libQt5Quick.so.5 #3 0x7fb5a2743f89 in QSGRenderThread::run() () at /usr/lib64/libQt5Quick.so.5 #4 0x7fb5a0c615bc in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb59fd12f9e in start_thread () at /lib64/libpthread.so.0 #6 0x7fb5a08f964f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb511ffb640 (LWP 2700) "GlobalQueue[08]"): #1 0x7fb5a0c66e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb5702a11e0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fb5702a4d96 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libK
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #11 from Leonard Lausen --- It turns out this is due to a mismatch in fontconfig (too recent) and font file (too old) in Gentoo. See https://bugs.gentoo.org/716856 I opened an upstream bug in Poppler to suggest the idea that poppler may warn the user if the chosen fallback font can't render all characters in the document: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1054 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Leonard Lausen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #10 from Leonard Lausen --- I used qt5/demos/poppler_qt5viewer from poppler to confirm that this is a poppler bug. If I compile qt5/demos/poppler_qt5viewer on Ubuntu 20.04, the checkboxes show up fine. On my Gentoo system they do not. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #9 from Leonard Lausen --- I built Okular 20.04.3 against poppler 0.86 (which matches the versions used in Ubuntu 20.04), but the issue persists on my system. Do you have any suggestions how to further debug? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #8 from Leonard Lausen --- I rebuilt Okular 20.12.2 against poppler 0.86, but the issue persists on my system. Any ideas what component could cause the issue? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #7 from Leonard Lausen --- I was able to reproduce Albert's "Works fine for me" on Ubuntu 20.04 system with poppler 0.86. I'll try poppler 0.86 on the system that currently exhibits the issue and report back. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #6 from Leonard Lausen --- I tried to reproduce Albert's "Works fine for me" on Ubuntu 20.04 system with poppler 0.86. I'll try poppler 0.86 on the system that currently exhibits the issue and report back. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #5 from Leonard Lausen --- Created attachment 136404 --> https://bugs.kde.org/attachment.cgi?id=136404=edit Standard mode -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #4 from Leonard Lausen --- Created attachment 136403 --> https://bugs.kde.org/attachment.cgi?id=136403=edit Show forms mode -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #3 from Leonard Lausen --- Thank you Albert. That's very interesting. Can you share more details on your system configuration (Okular version, poppler version)? I attached two screenshots to show that the boxes do not show up correctly in my environment. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #1 from Leonard Lausen --- I'm using Okular compiled with latest poppler 21.03.0. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 --- Comment #9 from Leonard Lausen --- I opened a related bug at https://bugs.kde.org/show_bug.cgi?id=433979 which however, unlike the current one, is not reproducible with Evince. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] New: American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Bug ID: 433979 Summary: American tax forms checkbox state cannot been seen when form is hidden Product: okular Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY IRS Tax forms such as https://www.irs.gov/pub/irs-pdf/f1040.pdf contain various checkboxes. In "Show Form" mode, these checkboxes are editable, but they do no longer show up in the printout or no-"Show Form" mode. This is unlike Gnome's Evince, which is also poppler based but does show the ticked checkboxes in printout. As this works in Evince, suspect to be a Okular specific rendering problem? STEPS TO REPRODUCE 1. wget https://www.irs.gov/pub/irs-pdf/f1040.pdf 2. okular f1040.pdf 3. Click "Show Forms" 4. Check a box 5. Print the form or click "Show Forms" again OBSERVED RESULT Ticked checkbox is no longer displayed. EXPECTED RESULT Ticked checkbox is visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79 Qt Version: 5.15.2 ADDITIONAL INFORMATION This appears unrelated to the XFA content. The same problem applies to f1040-noxfa.pdf file obtained via "pdftk f1040.pdf output f1040-noxfa.pdf drop_xfa" -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 Leonard Lausen changed: What|Removed |Added Version|1.11.1 |20.12.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 --- Comment #8 from Leonard Lausen --- I have reproduced this issue with Okular 20.12.2 and Poppler 21.03.0. I opened the "PDF file showing the problem" in Okular, clicked "Show forms" ticked a box, hide the forms and saved the file. The box no longer shows up after hiding the forms. I further confirmed that Evince, which is also based on poppler fails to show the checked box. In fact, clicking any other box in Evince will also fail to show. Finally, I confirmed that opening the modified PDF in either Master PDF Editor [1] or Firefox 86 does show the ticked box. Thus I agree with Albert that this is most likely a poppler bug. @Andreas, would you like to report the bug at https://gitlab.freedesktop.org/poppler/poppler/-/issues/ ? [1] https://code-industry.net/masterpdfeditor/ a proprietary PDF software with Linux support -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 --- Comment #5 from Leonard Lausen --- I think it's valid to mention the Wayland build in this issue. In fact you can try compiling it from source. In my experience, it works well for some applications but there were KDE specific bugs for others. However, I also noted KDE specific bugs with Xwayland Wine, so it's possible that the drag bug you report here is also KDE specific. Have you tried if the Xwayland drag works on Gnome Wayland session or Weston? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433168] [Wayland] Drag & drop from Dolphin to WINE application doesn't work
https://bugs.kde.org/show_bug.cgi?id=433168 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl --- Comment #2 from Leonard Lausen --- Are you using the https://gitlab.collabora.com/alf/wine/ wayland wine build? Or are you using stable wine with xwayland? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Keyboard layout's variant for the first layout is not applied
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #12 from Leonard Lausen --- > Oh, the other workaround I forgot to mention: > just add some variants to both layouts. I compiled 5.20.90 again and Neo variant does work fine now even when on position 1. I assume this is because I manually selected "Default" variant for US English while I was still on 5.20 (ie. both layouts now have a variant configured) I'll not touch the setting for as not to risk any problems :) Please let me know once you have a patch that fixes the regression and I'm happy to do further testing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Keyboard layout's variant for the first layout is not applied
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #11 from Leonard Lausen --- Reported as https://bugs.kde.org/show_bug.cgi?id=432436 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432436] New: Keyboard layout with variant in 2nd slot prevents switching back to layout in 1st slot
https://bugs.kde.org/show_bug.cgi?id=432436 Bug ID: 432436 Summary: Keyboard layout with variant in 2nd slot prevents switching back to layout in 1st slot Product: kwin Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl CC: butir...@gmail.com Target Milestone: --- Flags: Wayland+, X11- SUMMARY Both on X11 and Wayland session, configuring German Neo2 Layout as 2nd layout and US English layout as 1st layout will prevent switching back from Neo2 to US layout via keyboard shortcut (Right-Ctrl+Right-shift). There is no such problem if the order is inverse. See https://bugs.kde.org/show_bug.cgi?id=432367#c1 This issue affects both Plasma 5.20.5 and 5.20.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Keyboard layout's variant for the first layout is not applied
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #10 from Leonard Lausen --- > Thanks for testing. Actually I can't explain right now why the order of > layouts matters for the shortcut functionality. > It would be good if you could check on X11 also. I confirmed that also Plasma 5.20 X11 session, if I use Neo as 1st layout and US as 2nd layout, I can switch between them via "Right-Ctrl + Right-Shift" without getting stuck. But once placing Neo as layout 2 and US as layout 1, switching will get stuck once selecting Neo. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts show some oddities with foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 --- Comment #12 from Leonard Lausen --- Have you tried switching the order of layouts? In https://bugs.kde.org/show_bug.cgi?id=432367 I observe related issues that only occur if US layout is on position 1 in the settings screen and my custom layout is on position 2. However, when moving the custom layout to position 1 and US layout to position 2 fixes there are no problems. Note that the Layout Settings have Move Up/Down buttons to change layout order. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #7 from Leonard Lausen --- In Plasma 5.20, if I use Neo as 1st layout and US as 2nd layout, I can switch between them via "Right-Ctrl + Right-Shift" without getting stuck. But once placing Neo as layout 2 and US as layout 1, switching will get stuck once selecting Neo. Further I notice that the problem with "Alt key can no longer activate layer 4 (Ebene 4)" is also present on Plasma 5.20 if Neo is selected as 2nd layout. However, Alt key works correctly as long as Neo is selected as 1st layout. Thus I think the only regression here is "variants of the first layout" support. The others are separate bugs related to difference in handling of 1st and n-th layout. Are these known issues? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375518] global shortcuts show some oddities with foreign keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=375518 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #6 from Leonard Lausen --- > Leonard, this is probably because the shortcuts of these layouts do not match. > I wonder if you had similar problems with the same layouts but in different > order? The problem does not occur when using Default variant for German or placing the German Neo variant on position 1 and US on 2. > So if it worked for you earlier, maybe it was on X11? No, I was using Wayland with Plasma 5.20 and I haven't noticed this problem there. In fact the Right-Shift and Right-Ctrl key used as shortcut by me do not differ between the US and Neo. Thus I don't think it's related to 375518. If you like, I can reinstall kwin 5.20 and double check that the shortcut works fine there. > We could check it right now: > add 3 layouts in different order, and watch how it behaves on the shortcuts: > E.g.: US, US, Neo -> US, Neo, US With 4 layouts: English US, English UK, German Neo, German Default I can switch from US to UK to Neo, but then get stuck. I also notice that switching from US to UK, the overlay notifying me about the new layout shows up immediately. For UK to Neo, the overlay does not show up until I switch the application in focus (eg to my browser where I am writing the bug report now) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 --- Comment #3 from Leonard Lausen --- Specifically, I can activate the neo2 layout via the shortcut fine (Pressing "Right-Ctrl+Right-Shift" switches from US layout to neo2), but pressing the shortcut again does not switch back to US layout. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432367] Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367
--- Comment #2 from Leonard Lausen ---
Thank you Andrey for your work on the Plasma Wayland code and for pointing out
the workaround. The workaround works almost. The only major issue I face now is
that the right Alt key no longer works for activating layer 4 of the layout (cf
https://neo-layout.org/ "Ebene 4" in the picture in the upper right corner).
Pressing the Right Alt key does not perform any action.
For example, Pressing "Right-Alt + D" should result in "Arrow down", but with
your workaround results in "a" (which is the expected result of pressing "D"
but not for "Right-Alt + D").
A second minor issue I find is that switching keyboard layouts via the shortcut
("Right-Ctrl+Right-Shift" in my case) does not work reliably anymore after
moving neo layout to second position.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 432367] New: Neo2 keyboard layout no longer works with Plasma 5.21 beta
https://bugs.kde.org/show_bug.cgi?id=432367 Bug ID: 432367 Summary: Neo2 keyboard layout no longer works with Plasma 5.21 beta Product: kwin Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY After updatin from Plasma 5.20 to 5.21 beta, German Neo2 Layout stops working and the standard German keyboard layout is used instead. STEPS TO REPRODUCE 1. Go to keyboard layout settings 2. Add German (Neo 2) variant 3. Enable the variant and press the key corresponding to a in qwerty. input a is registered instead of expected input u (cf https://neo-layout.org/) OBSERVED RESULT Inputs registered are based on standard German keyboard variant EXPECTED RESULT Inputs registered are based on Neo 2 German keyboard variant SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo with Plasma 5.21 Beta KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm using wayland -- You are receiving this mail because: You are watching all bug changes.
