[kwin] [Bug 483183] Using push-to-talk key while using other keys does not work properly on Discord
https://bugs.kde.org/show_bug.cgi?id=483183 --- Comment #3 from teslastormga...@gmail.com --- Updating to version 6.0.2 fixed it, Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483516] Multi subtitle list not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=483516 --- Comment #1 from red_Arti --- Created attachment 167148 --> https://bugs.kde.org/attachment.cgi?id=167148=edit bug-project -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483517] New: Plasmashell crashes when starting with external monitor
https://bugs.kde.org/show_bug.cgi?id=483517 Bug ID: 483517 Summary: Plasmashell crashes when starting with external monitor Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: fengy.map...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 167147 --> https://bugs.kde.org/attachment.cgi?id=167147=edit Crash backtrace SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When starting arch linux with external monitor, the plasmashell will crash. But if I connect the external monitor after the KDE starts, the plasmashell won't crash. STEPS TO REPRODUCE 1. Connect the external monitor 2. Boot the system 3. Login the user OBSERVED RESULT The plasmashell crashed. EXPECTED RESULT The plasmashell runs. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics Platform: x11 Graphics Processor: NVIDIA GeForce RTX 4060 Laptop GPU/PCIe/SSE2 NVIDIA Driver version: 550.54.14 ADDITIONAL INFORMATION I cannot switch the screen layout of the external monitor by display configuration (). I can click the "swith to laptop screen" etc., but nothing happens, it just keep the status. I can only change the screen layout in the settings (Display & Monitor). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 483516] New: Multi subtitle list not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=483516 Bug ID: 483516 Summary: Multi subtitle list not displayed correctly Classification: Applications Product: kdenlive Version: git-master Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jijili...@yandex.com Target Milestone: --- Created attachment 167146 --> https://bugs.kde.org/attachment.cgi?id=167146=edit bug-record_multi-subtitle-miss SUMMARY The multiple subtitle tracks list doesn't display correctly, if you have multiple sequences. STEPS TO REPRODUCE 1. Create project (Project folder option: Parant folder of project file) 2. In Seq1, add a subtitle '1' 3. Create Seq2. In Seq2 add a subtitle '2' 4. Save (click 'yes' for moving temporary files). Close. Reopen the project 5. In Seq2, open Manage Subtitles and create a new subtitle track. Add a subtitle '3' 6. Switch to Seq1. Open Manage Subtitles and create a new subtitle track. Add a subtitle '4' Now: Seq1 has 2 subtitle tracks. Switch to Seq2, also 2 subtitle tracks. 7. Save again. Close. Reopen the project. 8. Switch to Seq1. Check the subtitle list OBSERVED RESULT The subtitle list displays empty. You can only switch to the first subtitle track from the dropdown. Only after you add a new subtitle track now, the previous-added second track shows. EXPECTED RESULT SOFTWARE/OS VERSIONS Latest git master ci build kdenlive-master-7641-linux-gcc-x86_64.AppImage ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483515] New: window outline doesn't match title bar when window is maximized horizontally or vertically
https://bugs.kde.org/show_bug.cgi?id=483515 Bug ID: 483515 Summary: window outline doesn't match title bar when window is maximized horizontally or vertically Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: kwin-bugs-n...@kde.org, uhh...@gmail.com Target Milestone: --- Created attachment 167145 --> https://bugs.kde.org/attachment.cgi?id=167145=edit screenshots showing the bug SUMMARY The Breeze window decoration outline does not fully align with windows that are maximized only horizontally or vertically. Windows that are maximized normally (filling the entire screen) appear correctly. When windows are maximized in only one direction, the following issues occur: 1. The rounded top corners of the title bar become straight. However, the outline is still drawn with a curve slicing over the now straight corner. 2. Horizontally-maximized windows should have no outline on the left or right sides of the window, but an outline is drawn on both the left and right side of the title bar (but only the title bar). 3. Vertically-maximized windows should have no outline on the top or bottom of the window, but an outline is drawn at the top of the titlebar. I have attached screenshots showing unmaximized, vertically-maximized, and horizontally-maximized window corners zoomed to 800%. STEPS TO REPRODUCE 1. Choose the "Breeze Dark" color scheme and a bright wallpaper to be able to better see the window outline. Make sure outline intensity in the Breeze window decoration settings is set to "medium" or higher for best visibility. 2. Maximize a window vertically (by middle-clicking the maximize button) or horizontally (by right-clicking the maximize button). OBSERVED RESULT The outline is erroneously drawn as described in the summary above. EXPECTED RESULT The outline should correctly match the window boundaries. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This bug occurs in both X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483514] New: Panels misplace to main display and break the virtual desktop widget
https://bugs.kde.org/show_bug.cgi?id=483514 Bug ID: 483514 Summary: Panels misplace to main display and break the virtual desktop widget Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: qik0...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Panels that are on secondary displays sometimes jump to the main display after a fresh boot. This also causes the virtual desktops widget to show the main display instead of the secondary display on said panel even when moved to the secondary display (using the "show only current screen" option of the virtual desktops widget) SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX 7900 XTX -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483513] after color scheme edit, kcm_colors is unresponsive to further edits (X11 only)
https://bugs.kde.org/show_bug.cgi?id=483513 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483512] Discover and Microphone symbolic icons are not the correct color with a dark panel.
https://bugs.kde.org/show_bug.cgi?id=483512 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483511] saved copy of a color scheme doesn't appear in the list
https://bugs.kde.org/show_bug.cgi?id=483511 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483510] KDE shows charging in battery icon, even when the laptop is not plugged in.
https://bugs.kde.org/show_bug.cgi?id=483510 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483510] KDE shows charging in battery icon, even when the laptop is not plugged in.
https://bugs.kde.org/show_bug.cgi?id=483510 --- Comment #2 from ljh.art...@gmail.com --- It seems that this problem can be triggered by rebooting while keeping the charger plugged in, and then unplugging it after entering the system. No hibernation is required. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483513] New: after color scheme edit, kcm_colors is unresponsive to further edits (X11 only)
https://bugs.kde.org/show_bug.cgi?id=483513 Bug ID: 483513 Summary: after color scheme edit, kcm_colors is unresponsive to further edits (X11 only) Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY After editing a color scheme, trying to edit a second color scheme does nothing. This bug happens in X11, but does not happen in Wayland. STEPS TO REPRODUCE 1. Go to System Settings → Colors & Themes → Colors. 2. Click the pencil icon to edit any theme. The KColorSchemeEditor window will appear. 3. Close the KColorSchemeEditor window. 4. Click the pencil icon to edit any theme. OBSERVED RESULT Nothing happens. EXPECTED RESULT The KColorSchemeEditor window should appear to allow editing the theme. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This is possibly caused by the same underlying issue as bug #483511. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483510] KDE shows charging in battery icon, even when the laptop is not plugged in.
https://bugs.kde.org/show_bug.cgi?id=483510 --- Comment #1 from ljh.art...@gmail.com --- Guys I found a way to reproduce it, it is related to hibernation in Archlinux. I set up hibernation recovery (Add swap uuid to /etc/default/grub, and add the resume hook in mkinitcpio.conf, copy the memory to the swap partition when hibernating, and recover when the system boots) 1. Close the lid of the laptop when it is not charging (I set hibernating when the lid is closed) 2. Keep the lid closed and plug in the charger 3. Open the cover, turn on the phone, wait for a while, and then pull out the charger. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483512] New: Discover and Microphone symbolic icons are not the correct color with a dark panel.
https://bugs.kde.org/show_bug.cgi?id=483512 Bug ID: 483512 Summary: Discover and Microphone symbolic icons are not the correct color with a dark panel. Classification: Plasma Product: Breeze Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: chase.s.jew...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- Created attachment 167144 --> https://bugs.kde.org/attachment.cgi?id=167144=edit Screenshot of affected system tray SUMMARY *** If you look at the system tray, the microphone indicator and discover update indicator symbolic icons are not light when using a dark theme as they are supposed to be. *** STEPS TO REPRODUCE 1. Have Discover open/a Mic enabled on Breeze Dark. OBSERVED RESULT Icons are dark EXPECTED RESULT Icons are light. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483401] Java applications start with wrong scaling on mixed scale monitors
https://bugs.kde.org/show_bug.cgi?id=483401 el...@seznam.cz changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from el...@seznam.cz --- XWayland - RubyMine - PHPStorm - LanguageTool plugin in LibreOffice Wayland - DBeaver When I set "Scaled by the system", XWayland apps are scaled to 100% on FHD screen and to 200% on 4K, but are blurry. When I set "Apply scaling themselves", I manually configured RubyMine and PHPStorm to use 200% scaling. I did a lot of testing and this behaviour is erratic. Sometimes apps start on 4K, sometimes on FHD (I always keep cursor on 4K). Sometimes they start with correct scaling, sometimes not. And sometimes when I move windows between screens scaling gets "fixed" and sometimes it changes to 50%. Couldn't find any pattern to it… -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483511] New: saved copy of a color scheme doesn't appear in the list
https://bugs.kde.org/show_bug.cgi?id=483511 Bug ID: 483511 Summary: saved copy of a color scheme doesn't appear in the list Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: s_chriscoll...@hotmail.com CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- SUMMARY Saving a copy of a color scheme using the colors KCM in System Settings doesn't add the newly saved scheme to the list until navigating away from and back to the colors page. This bug happens in X11, but does not happen in Wayland. STEPS TO REPRODUCE 1. Go to System Settings → Colors & Themes → Colors. 2. Click the pencil icon to edit a theme, e.g. "Breeze Classic". 3. Click "Save As..." and give it a new name, e.g. "Breeze Classic 2", then click "Close". OBSERVED RESULT The new color scheme does not appear in the list. EXPECTED RESULT The new color scheme should appear in the list. SOFTWARE/OS VERSIONS Linux: KDE neon 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I noticed that it takes much longer to open the window for editing a color scheme under X11 than it does in Wayland, where it appears pretty much instantly. Perhaps this may provide a clue? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 483413] Opening a folder to load a gpx file freezes Digikam if there is a .json file into this folder (any .json file)
https://bugs.kde.org/show_bug.cgi?id=483413 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||8.3.0 --- Comment #16 from caulier.gil...@gmail.com --- digiKam do not touch this file in your home directory. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483510] New: KDE shows charging in battery icon, even when the laptop is not plugged in.
https://bugs.kde.org/show_bug.cgi?id=483510 Bug ID: 483510 Summary: KDE shows charging in battery icon, even when the laptop is not plugged in. Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ljh.art...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Sometimes, the battery icon in the KDE tray menu still displays the charging icon after unplugging the charging cable. Move the mouse up, and the pop-up label shows that the charger is connected, but it is still being discharged. The power supply is insufficient and cannot be charged. Plug in the charger again and it returns to normal, but the charging icon is still displayed when you unplug it again. Whenever this problem occurs, it will only recover after restarting. But I'm not sure how to reproduce this problem, it seems to be a random STEPS TO REPRODUCE 1. Plug charger 2. unplug charger OBSERVED RESULT The battery icon shows charging EXPECTED RESULT show discharged SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Wayland KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION ``` upower -d when bug occurred Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: SCUD model:R14B06W serial: MB10006AE25708AV power supply: yes updated: 2024年03月14日 星期四 12时51分49秒 (20 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging warning-level: none energy: 14.02 Wh energy-empty:0 Wh energy-full: 51.93 Wh energy-full-design: 56 Wh energy-rate: 8.79 W voltage: 14.716 V charge-cycles: N/A time to empty: 1.6 hours percentage: 26% capacity:92.7321% technology: lithium-ion icon-name: 'battery-low-symbolic' History (charge): 1710391909 26.000 discharging History (rate): 1710391909 8.790 discharging 1710391897 8.630 discharging 1710391867 9.640 discharging 1710391837 9.240 discharging Device: /org/freedesktop/UPower/devices/line_power_ADP1 native-path: ADP1 power supply: yes updated: 2024年03月14日 星期四 11时53分28秒 (3521 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o001 native-path: ucsi-source-psy-USBC000:001 power supply: yes updated: 2024年03月14日 星期四 12时37分08秒 (901 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/line_power_ucsi_source_psy_USBC000o002 native-path: ucsi-source-psy-USBC000:002 power supply: yes updated: 2024年03月14日 星期四 12时36分45秒 (924 seconds ago) has history: no has statistics: no line-power warning-level: none online: no icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: 2024年03月14日 星期四 12时51分49秒 (20 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: none energy: 14.02 Wh energy-full: 51.93 Wh energy-rate: 8.79 W charge-cycles: N/A time to empty: 1.6 hours percentage: 26% icon-name: 'battery-low-symbolic' Daemon: daemon-version: 1.90.2 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep ``` -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 482944] The date is wrong! digiKam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.
https://bugs.kde.org/show_bug.cgi?id=482944 mlh.k...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 482944] The date is wrong! digiKam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.
https://bugs.kde.org/show_bug.cgi?id=482944 --- Comment #41 from mlh.k...@gmail.com --- (In reply to mlh.kiwi from comment #40) > (In reply to caulier.gilles from comment #39) > > Thanks for the feedback about your solved problem. > > > > We don't know other situation where a similar error message will appear. > > > > Gilles Caulier > > Only problem is that did not solve the problem exiftool 12.78 is the one I downloaded and this is seeming to be found by the digikam configure (In reply to mlh.kiwi from comment #40) > (In reply to caulier.gilles from comment #39) > > Thanks for the feedback about your solved problem. > > > > We don't know other situation where a similar error message will appear. > > > > Gilles Caulier > > Only problem is that did not solve the problem I re read the meta data from the files to database and yes it does work! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 482944] The date is wrong! digiKam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.
https://bugs.kde.org/show_bug.cgi?id=482944 --- Comment #40 from mlh.k...@gmail.com --- (In reply to caulier.gilles from comment #39) > Thanks for the feedback about your solved problem. > > We don't know other situation where a similar error message will appear. > > Gilles Caulier Only problem is that did not solve the problem -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 482944] The date is wrong! digiKam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.
https://bugs.kde.org/show_bug.cgi?id=482944 mlh.k...@gmail.com changed: What|Removed |Added Version|8.2.0 |8.3.0 Resolution|FIXED |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 482944] The date is wrong! digiKam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.
https://bugs.kde.org/show_bug.cgi?id=482944 caulier.gil...@gmail.com changed: What|Removed |Added Summary|The date is wrong! Digikam |The date is wrong! digiKam |appears to be using |appears to be using |modified date not the |modified date not the |create date despite there |create date despite there |being a "date taken" tag in |being a "date taken" tag in |windows properties. |windows properties. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.
https://bugs.kde.org/show_bug.cgi?id=482944 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.3.0 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #39 from caulier.gil...@gmail.com --- Thanks for the feedback about your solved problem. We don't know other situation where a similar error message will appear. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 482944] The date is wrong! Digikam appears to be using modified date not the create date despite there being a "date taken" tag in windows properties.
https://bugs.kde.org/show_bug.cgi?id=482944 --- Comment #38 from mlh.k...@gmail.com --- (In reply to caulier.gilles from comment #37) > Hi, > > The Windows 8.3.0 pre-release installer will be rebuild this morning with > last changes from Maik. > > Gilles Caulier Very good job. I did get that error right away out of curiosity are there other error messages that can show up? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477223] Setting an icc profile causes reduced system performance.
https://bugs.kde.org/show_bug.cgi?id=477223 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482811] On X11, Panel has moved from one screen to another one after screen lock
https://bugs.kde.org/show_bug.cgi?id=482811 --- Comment #6 from Samuel --- (In reply to Nate Graham from comment #5) > Thanks. Can I ask you to set up a new user account and replicate your panel > setup, and see if it's still happening there? Basically I want to see if it > was caused by an issue upgrading old configs from Plasma 5 to Plasma 6. I did the following tests: Created a 2 users via KDE Settings, a standard and an administrator. Updated and restarted the machine, then logged into the new ones and set the second monitor as primary. In the standard one the bug happened again, and in addition, the second output was not recognized after second screen lock, so suddenly only one monitor was available in that account. In the administrator one all worked without issues, bug did not happen. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 481110] Unsupport hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=481110 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481274] Dolphin crashes while playing video with VLC
https://bugs.kde.org/show_bug.cgi?id=481274 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480866] kate segfault while long pressing ctrl+z
https://bugs.kde.org/show_bug.cgi?id=480866 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479861] Drop event runs when it should not
https://bugs.kde.org/show_bug.cgi?id=479861 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 480939] System monitor doesn't show any graphs
https://bugs.kde.org/show_bug.cgi?id=480939 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480905] Plasmashell does not start when cpu-power governor is set to performance
https://bugs.kde.org/show_bug.cgi?id=480905 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425638] SMS disappears instead of being send
https://bugs.kde.org/show_bug.cgi?id=425638 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #25 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 333547] kfind shall use the Baloo Index
https://bugs.kde.org/show_bug.cgi?id=333547 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 481913] My wacom pen will not align with the canvas. The pen works fine on every other part of the program but as soon as I hover it above the canvas it completely misaligns. I know the p
https://bugs.kde.org/show_bug.cgi?id=481913 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 107302] Per-screen virtual desktops
https://bugs.kde.org/show_bug.cgi?id=107302 sayantan.chaudhuri+...@gmail.com changed: What|Removed |Added CC||sayantan.chaudhuri+kde@gmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482892] Switching activities also switches active virtual desktop
https://bugs.kde.org/show_bug.cgi?id=482892 --- Comment #2 from awenh...@gmail.com --- I did some digging in the source code and it seems like there's a plugin that's responsible for this behavior, however the plugin seems to be shipped and enabled by default (at least on my distro). I found no way of disabling the plugin via configuration, but removing the plugins .so worked. On my system it can be found at `/usr/lib/qt6/plugins/kactivitymanagerd1/org.kde.ActivityManager.VirtualDesktopSwitch.so`. There's a related issue, but this issue was complaining about the *lack of* the exact behavior we are now complaining of existing: https://bugs.kde.org/show_bug.cgi?id=435743 This comment (https://bugs.kde.org/show_bug.cgi?id=435743#c6) indicates the availability of disabling the plugin via the config file of kactivityd (`~/.config/kactivitymanagerdrc`), however I was not able to get it to work by adding `org.kde.ActivityManager.VirtualDesktopSwitchEnabled=false` under `[main]` (just guessing, I didn't find any docs for the configuration options for this file at all). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483393] Systray icons are kind of blurry in Plasma 6 with 1.5 scale factor
https://bugs.kde.org/show_bug.cgi?id=483393 --- Comment #2 from zvova7...@gmail.com --- Nate, well yeah, thanks for the detailed explanations :) I'm understand concept. But I have fillings that in case of the systray it is not just about "a half of the pixel" problem. Because it looks too blurry for that explanation. Every time I look at the systray, I think that my vision has deteriorated so much that I need to start using glasses at the computer :-D Anyway, I will do some experiments with that when I have the time, because it got me interested :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483509] system monitor widget horizontal bars fails to display more than 1 sensor when in panel
https://bugs.kde.org/show_bug.cgi?id=483509 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482668] Crash in Energy Savings KCM when configured power action is newly unsupported
https://bugs.kde.org/show_bug.cgi?id=482668 Jakob Petsovits changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/powerdevil/-/commit/8ecf |ma/powerdevil/-/commit/aedb |6430ee7a3d3670fd9cb1b6af947 |2529b31ec9b62ee5a8b3548be84 |f9ac2f352 |8769f4009 --- Comment #15 from Jakob Petsovits --- Git commit aedb2529b31ec9b62ee5a8b3548be848769f4009 by Jakob Petsovits. Committed on 14/03/2024 at 03:28. Pushed by jpetso into branch 'Plasma/6.0'. kcmodule: Don't crash when a configured button action is unsupported The bounds check in the data() method of PowerButtonActionModel and SleepModeModel was incomplete, so passing an invalid index such as -1 (standard value for "not found") could cause a crash. For power management settings, a user would run into this crash if their configuration from powerdevilrc listed a power button action that's not supported on the current system. For example, a user may have selected "Sleep" as lid action, but subsequently changed their systemd configuration to disable suspend-to-RAM because it caused problems. Or they could have migrated their OS to a new computer which does not support Sleep. Fixing this allows us to assign currentIndex declaratively instead of waiting until Component.onCompleted to (hopefully) find a valid item in the model. (cherry picked from commit 8ecf6430ee7a3d3670fd9cb1b6af947f9ac2f352) M +1-1kcmodule/common/PowerButtonActionModel.cpp M +1-1kcmodule/common/SleepModeModel.cpp M +2-0kcmodule/profiles/ui/GlobalConfig.qml M +8-0kcmodule/profiles/ui/ProfileConfig.qml https://invent.kde.org/plasma/powerdevil/-/commit/aedb2529b31ec9b62ee5a8b3548be848769f4009 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483509] system monitor widget horizontal bars fails to display more than 1 sensor when in panel
https://bugs.kde.org/show_bug.cgi?id=483509 --- Comment #1 from squad...@gmail.com --- Created attachment 167143 --> https://bugs.kde.org/attachment.cgi?id=167143=edit Panel with system monitor widget and two sensors. Nothing is visible. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482668] Crash in Energy Savings KCM when configured power action is newly unsupported
https://bugs.kde.org/show_bug.cgi?id=482668 Jakob Petsovits changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/commit/8ecf ||6430ee7a3d3670fd9cb1b6af947 ||f9ac2f352 Status|ASSIGNED|RESOLVED --- Comment #14 from Jakob Petsovits --- Git commit 8ecf6430ee7a3d3670fd9cb1b6af947f9ac2f352 by Jakob Petsovits. Committed on 14/03/2024 at 03:19. Pushed by jpetso into branch 'master'. kcmodule: Don't crash when a configured button action is unsupported The bounds check in the data() method of PowerButtonActionModel and SleepModeModel was incomplete, so passing an invalid index such as -1 (standard value for "not found") could cause a crash. For power management settings, a user would run into this crash if their configuration from powerdevilrc listed a power button action that's not supported on the current system. For example, a user may have selected "Sleep" as lid action, but subsequently changed their systemd configuration to disable suspend-to-RAM because it caused problems. Or they could have migrated their OS to a new computer which does not support Sleep. Fixing this allows us to assign currentIndex declaratively instead of waiting until Component.onCompleted to (hopefully) find a valid item in the model. M +1-1kcmodule/common/PowerButtonActionModel.cpp M +1-1kcmodule/common/SleepModeModel.cpp M +2-3kcmodule/profiles/ui/GlobalConfig.qml M +8-12 kcmodule/profiles/ui/ProfileConfig.qml https://invent.kde.org/plasma/powerdevil/-/commit/8ecf6430ee7a3d3670fd9cb1b6af947f9ac2f352 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483509] New: system monitor widget horizontal bars fails to display more than 1 sensor when in panel
https://bugs.kde.org/show_bug.cgi?id=483509 Bug ID: 483509 Summary: system monitor widget horizontal bars fails to display more than 1 sensor when in panel Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: squad...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 167142 --> https://bugs.kde.org/attachment.cgi?id=167142=edit Panel with system monitor widget and one sensor SUMMARY No sensors are visible when adding a system monitor widget with horizontal bars to a panel and adding more than one sensor. (Expanded view when clicking works fine.) STEPS TO REPRODUCE 1. Add a system monitor sensor widget to a panel. 2. Set its display mode to horizontal bars. 3. Add more than one sensor. OBSERVED RESULT Sensors disappear from view when there is more than 1. EXPECTED RESULT Horizontal bars stack nicely like in previous versions. SOFTWARE/OS VERSIONS OpenSUSE Tumbleweed 20240311 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Proprietary Nvidia drivers 550.54.14 Wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483404] power-profiles-daemon widget for mode change does not work
https://bugs.kde.org/show_bug.cgi?id=483404 --- Comment #2 from davidb9...@gmail.com --- (In reply to Nate Graham from comment #1) > Does it work to change the setting using the command-line `powerprofilesctl` > program? E.g. `powerprofilesctl set performance` > > Or is that broken too? ❯ powerprofilesctl set performance Traceback (most recent call last): File "/usr/bin/powerprofilesctl", line 7, in from gi.repository import Gio, GLib ModuleNotFoundError: No module named 'gi' -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483508] New: Manage system-wide autostart as well
https://bugs.kde.org/show_bug.cgi?id=483508 Bug ID: 483508 Summary: Manage system-wide autostart as well Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_autostart Assignee: plasma-b...@kde.org Reporter: jus...@kde.org CC: nicolas.fe...@gmx.de Target Milestone: --- I have an item in /usr/share/xdg/autostart/ but I want to disable it from starting, I cannot do this without removing the application. It would be nice to be able to disable items in there from starting. It would require the user to elevate similar to the SDDM KCM. The KCM could then create appname.desktop.disabled in there which would prevent it from starting with Plasma. Changes to the .desktop file itself would just be overwritten on next update so altering that wouldn't work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483503] Window rules: Force app to specific screen don't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=483503 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483377] When screen is turned off for energy saving, can't turn it back on with touch or stylus. Must use a mouse or keyboard.
https://bugs.kde.org/show_bug.cgi?id=483377 --- Comment #2 from andy --- I see. If I set the screen timeout to 1 minute and leave `libinput debug-events` running, then tap the screen a bunch, then press spacebar to turn the screen back on, I see only KEYBOARD_KEY and no TOUCH_* events that I normally see with the screen on. Trying the same with the stylus, I don't see POINTER_* events either when the screen is off. So it would make sense if this is a lower level kernel/firmware thing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483405] Top bar gets rendered at the wrong window after screen being turned off
https://bugs.kde.org/show_bug.cgi?id=483405 iwaters1...@gmail.com changed: What|Removed |Added CC||iwaters1...@gmail.com --- Comment #3 from iwaters1...@gmail.com --- This appears to also be happening in 6.0.2-3 (at least for me) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483075] Global menu items disappear when a pop-up window opens, but don't show up again after it closes
https://bugs.kde.org/show_bug.cgi?id=483075 --- Comment #5 from Kunshan Wang --- (In reply to Nate Graham from comment #4) > Cool, great analysis! Would you like to work on a code change for that and > submit it to KDE? I have no prior experience in KDE development and very little in Qt programming, so I can't contribute code for now. Sorry about that. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 472424] Cannot install wine32 due to broken dependencies
https://bugs.kde.org/show_bug.cgi?id=472424 myrist...@incode-labs.com changed: What|Removed |Added CC||myrist...@incode-labs.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 483507] New: Doesn't update Size, CRC and Date of change on file replacement
https://bugs.kde.org/show_bug.cgi?id=483507 Bug ID: 483507 Summary: Doesn't update Size, CRC and Date of change on file replacement Classification: Applications Product: ark Version: 23.08.1 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: trufano...@gmail.com CC: rthoms...@gmail.com Target Milestone: --- SUMMARY Ark doesn't update Size, CRC and Date of change on replacement of existing file with drag STEPS TO REPRODUCE 1. Archieve some files to zip from dolphin context menu 2. Open zip with ark 3. Chenge file content on disk 4. Drag'n'drop file in ark window 5. Click Replace existing file in dialog window OBSERVED RESULT ark window filelist won't reflect changed details of replaced file EXPECTED RESULT new CRC, size and date of change displayed in filelist details SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-3632QM CPU @ 2.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000 Manufacturer: LENOVO Product Name: Lenovo G780 System Version: Lenovo G780 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 483298] Patch to update holiday_sg_en-gb to the year 2024-2026
https://bugs.kde.org/show_bug.cgi?id=483298 --- Comment #7 from Jin Liu --- (In reply to Will Ng from comment #6) > Hi, have the lines been added? It doesn't seem to be part of any of the > commits and changes in the merge request. Ah sorry, forgot to push to the server. Fixed now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kholidays] [Bug 483298] Patch to update holiday_sg_en-gb to the year 2024-2026
https://bugs.kde.org/show_bug.cgi?id=483298 --- Comment #6 from Will Ng --- (In reply to Jin Liu from comment #5) > Done. Hi, have the lines been added? It doesn't seem to be part of any of the commits and changes in the merge request. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Joe changed: What|Removed |Added CC||jchevar...@gmail.com --- Comment #48 from Joe --- I also just experienced this using a Steam Controller on the latest Plasma 6.0.1 release when trying out the FF7 remake. Screen goes to sleep even with controller input - work around right now is just manually inhibiting sleep/suspend and re-enabling. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483411] KWin Wayland with Nvidia leads to weird shuttering for certain proton game (逆転裁判456 or Apollo Justice: Ace Attorney Trilogy)
https://bugs.kde.org/show_bug.cgi?id=483411 --- Comment #4 from Qu Wenruo --- I'm not sure if it's the same bug of Xwayland. As if I go with gamescope for the game, the shuttering is just gone. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483506] New: /usr/share/icons/default missing and XCURSOR_THEME not set
https://bugs.kde.org/show_bug.cgi?id=483506 Bug ID: 483506 Summary: /usr/share/icons/default missing and XCURSOR_THEME not set Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: gdeve...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- The lack of XCURSOR_THEME not being set means applications who wish to manipulate the cursor like wezterm, can't properly do so because they don't know the theme, and the default theme is missing. The lack of this default theme also results in a missing cursor in the wayland SDDM screen under the kwin_wayland Adding /usr/share/icons/default/index.theme with the content ``` [Icon Theme] Inherits=breeze_cursors ``` Fixes both issues, though XCURSOR_THEME should probably be set somewhere -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483505] System restart required message should be more clear to the user
https://bugs.kde.org/show_bug.cgi?id=483505 Ben Daines changed: What|Removed |Added CC||benjamindai...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483505] New: System restart required message should be more clear to the user
https://bugs.kde.org/show_bug.cgi?id=483505 Bug ID: 483505 Summary: System restart required message should be more clear to the user Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: plasma-b...@kde.org Reporter: benjamindai...@gmail.com CC: baloo-bugs-n...@kde.org Target Milestone: --- SUMMARY When manually adding directories to be either indexed or not indexed, a message is displayed at the top of the screen after clicking apply saying that "the system must be restarted for changes to take effect." The user is here presented with a restart button with a spinning arrows icon that seems to indicate that the entire system will be restarted if the button is clicked. The biggest issue is that (under Plasma 5 Wayland) work will be lost when the session is ended if this button does indeed restart the entire system to make changes to the indexed directories. Supposedly this is fixed with Plasma 6, so that may be a non-issue. However, needing to restart the entire system seems quite intrusive when I can confirm that merely restarting the user service for kde-baloo is plenty to what needs to be done. I purpose that this message should be worded better, either specify that you do in fact mean the computer or the session rather than just "system." The indexing system? The computer system? The what? More to the point of sanity, I would hope that this message can be clarified as "the indexing service needs to be restarted..." and that button can be made to simply restart the baloo service for the current session without requiring the session to be ended or the computer rebooted. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483504] holiday display doesn't update after picking holidays
https://bugs.kde.org/show_bug.cgi?id=483504 t...@adminart.net changed: What|Removed |Added CC||t...@adminart.net -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483504] New: holiday display doesn't update after picking holidays
https://bugs.kde.org/show_bug.cgi?id=483504 Bug ID: 483504 Summary: holiday display doesn't update after picking holidays Classification: Applications Product: korganizer Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: otherviews Assignee: kdepim-b...@kde.org Reporter: t...@adminart.net Target Milestone: --- SUMMARY The holiday display doesn't update after picking holidays. You need to restart korganizer for the holidays to show up in the day view. (Why is there no component for dayview?) STEPS TO REPRODUCE 1. start korgnizer (for the first time) 2. pick holidays for some country (or two countries) in the settings 3. apply the settings and close them by clicking on ok 4. click on a day that is a holiday in the month view OBSERVED RESULT No holidays are showing up in the dayview. (They do show up in the tooltip of the month view when hovering the mouse pointer over the day; but who would notice.) EXPECTED RESULT The holidays should show up in the day view when that day is a holiday once they have been picked without needing to restart korganizer. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.7-200.fc39.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Xeon® CPU E5-2637 v4 @ 3.50GHz Memory: 125.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 Manufacturer: Dell Inc. Product Name: Precision Rack 7910 ADDITIONAL INFORMATION You can also unpick all holidays in the settings and the dayview doesn't get updated, either. The tooltip is being updated in that no holidays are shown. So every time you pick or unpick holidays, you need to restart korganizer for the dayview to correspond with the tooltip. Please consider https://bugs.kde.org/show_bug.cgi?id=483502 : with changing the holidays that were picked, colours in the month view would need to be updated accordingly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483503] New: Window rules: Force app to specific screen don't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=483503 Bug ID: 483503 Summary: Window rules: Force app to specific screen don't work with Wayland Classification: Plasma Product: kwin Version: 6.0.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: i...@gmx.de CC: isma...@gmail.com Target Milestone: --- SUMMARY *** System with two screens (0, 1). Firefox should be started always on the bigger screen (1). Works with X11, but not with Wayland. *** STEPS TO REPRODUCE 1. Window Class (application): Exact Match: firefox firefox (detected by "Detect Window Properties") 2. Screen: Force: 1 3. Apply 4. Double click Firefox icon OBSERVED RESULT Firefox starts on Screen 0. EXPECTED RESULT Firefox starts on Screen 1. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20240311 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION When doing this with X11, an other Window class (application) name is detected by "Detect Window Properties": 1. Window Class (application): Exact Match: Navigator firefox This works correct with X11, but also not with Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483501] Blender icons gone
https://bugs.kde.org/show_bug.cgi?id=483501 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483418] Severe flickering with 2 monitors and one plugged into an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=483418 --- Comment #5 from Hosein --- It's also notable that if I run sddm with wayland and kwin it does not flicker -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482716] Startup sound does not play
https://bugs.kde.org/show_bug.cgi?id=482716 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org --- Comment #4 from Harald Sitter --- Ugh, this is actually terrible. Besides the obvious bug with us not resolving the sounds correctly, the sound device may also be in energy saving and not wake up at all or not in time to produce anything audible -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483418] Severe flickering with 2 monitors and one plugged into an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=483418 --- Comment #4 from Hosein --- (In reply to Nate Graham from comment #2) > Also, is this happening on X11, or Wayland, or both? Just Wayland -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483502] colours are bad for retired people
https://bugs.kde.org/show_bug.cgi?id=483502 t...@adminart.net changed: What|Removed |Added CC||t...@adminart.net -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483502] New: colours are bad for retired people
https://bugs.kde.org/show_bug.cgi?id=483502 Bug ID: 483502 Summary: colours are bad for retired people Classification: Applications Product: korganizer Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: monthview Assignee: kdepim-b...@kde.org Reporter: t...@adminart.net Target Milestone: --- SUMMARY When you're retired and thus have configured no workdays since you don't work, all the days in the month view are shown in red with no good way to change that. STEPS TO REPRODUCE 1. uncheck all days so no days are configured as work days 2. look at the month view 3. try to configure a spefic colour for non-workdays OBSERVED RESULT All the days in every month are shown in red as if they were suddenly dangerous. They also seem to be bold which doesn't exactly improve readability. There doesn't seem to be a way in the settings to change this. EXPECTED RESULT Use a more harmless colour as default and allow to customize colour and font (boldness) for non-workdays. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.7-200.fc39.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Xeon® CPU E5-2637 v4 @ 3.50GHz Memory: 125.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 Manufacturer: Dell Inc. Product Name: Precision Rack 7910 ADDITIONAL INFORMATION Oh! I just found out by chance that the holiday colour is being used for the non-workdays. That means that normal days (i. e. non-workdays) can not be distinguished from holidays. Of course I do want to use a different colour for holidays than the one for non-workdays. Even when one doesn't work on a day that doesn't mean that that day is a holiday. Obviously, that doesn't only go for retired people but for everyone who doesn't work every day. This also as has an effect on weekends. Weekends need their own colour because some people are working on weekends, and not all weekends are holidays, either. And normal days (i. e. non-workdays) should be distinguished from weekends, so that requires yet another colour for weekends (which mostly aren't holidays). Once we have enough colours for the types of days, we'll need to be able to set priorities for the colours of the days. For example, I would prefer holidays always shown in holiday colour even when they are weekends while other users may prefer to keep showing them in weekend colour, etc. ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483418] Severe flickering with 2 monitors and one plugged into an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=483418 --- Comment #3 from Hosein --- (In reply to Nate Graham from comment #1) > Which one flickers? Is it always the one plugged into the NVIDIA GPU? Yes -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483501] New: Blender icons gone
https://bugs.kde.org/show_bug.cgi?id=483501 Bug ID: 483501 Summary: Blender icons gone Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: saileshpoud...@gmail.com Target Milestone: --- SUMMARY After 6.02 update, there are no icons on blender. Blender used to work fine in previous plasma 6. While opening blender it looks like this. [IMAGE] https://imgur.com/UuipPG7 INFO: Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-9300H CPU @ 2.40GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 + NVIDIA -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 483194] Added verification data (CRL/OCSP) break integrity check
https://bugs.kde.org/show_bug.cgi?id=483194 --- Comment #7 from Matej Vašek --- Note that both Foxit Reader and Adobe Reader do not report any errors. Also some government pages seems to accept such a pdf. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 483194] Added verification data (CRL/OCSP) break integrity check
https://bugs.kde.org/show_bug.cgi?id=483194 --- Comment #6 from Matej Vašek --- The thing is that the only modification to the file was embedding OCSP response to it. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483500] New: Window titles should have a unique and consistent pattern that can be matched with a simple regex
https://bugs.kde.org/show_bug.cgi?id=483500 Bug ID: 483500 Summary: Window titles should have a unique and consistent pattern that can be matched with a simple regex Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gravy_starving...@simplelogin.com Target Milestone: --- Since window types don't exist/work in wayland, window rules for the different windows in an application are dependent on matching the window title, so these different window types should each have some unique text or pattern that allows a simple regex to match just that window without the possibility of false positives/negatives. This is aimed at the main window's title, which tends to be so short and simple that the only consistent text to match is the application's own name and maybe a preceding em dash that tends to end up being a substring within other windows' titles in the application, requiring a regex that explicitly excludes every possible other window in that application and has the potential for a false negative if the title contains the name of a file/folder that matches the excluded text. Simply adding a prefix to the window title to allow for a "[prefix][wildcard][application name]" pattern should be enough. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 483194] Added verification data (CRL/OCSP) break integrity check
https://bugs.kde.org/show_bug.cgi?id=483194 --- Comment #5 from Matej Vašek --- Created attachment 167141 --> https://bugs.kde.org/attachment.cgi?id=167141=edit Okular screenshot detail -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 483194] Added verification data (CRL/OCSP) break integrity check
https://bugs.kde.org/show_bug.cgi?id=483194 --- Comment #4 from Matej Vašek --- (In reply to Albert Astals Cid from comment #1) > You will have to attach a document where this happens. I did attach such a pdf document and also include of screenshot of okular behaviour. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 483194] Added verification data (CRL/OCSP) break integrity check
https://bugs.kde.org/show_bug.cgi?id=483194 --- Comment #3 from Matej Vašek --- Created attachment 167140 --> https://bugs.kde.org/attachment.cgi?id=167140=edit Okular screenshot -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483490] No longer possible to set DDC/CI compatible external monitor to 0% brightness using system tray screen brightness slider (limited to 1%)
https://bugs.kde.org/show_bug.cgi?id=483490 Natalie Clarius changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Natalie Clarius --- Yes, this is intentional, to prevent people from accidentally making the contents of their screen invisible. To turn off your screen (and in a way that will save more battery than just turning down brightness), you can use a keyboard shortcut which you can set up in system settings. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 483356] Unable to select text for the second time in OverlaySheet + SelectableLabel
https://bugs.kde.org/show_bug.cgi?id=483356 --- Comment #2 from Fushan Wen --- (In reply to Nate Graham from comment #1) > Hmm, it seems to be working for me. What's your Qt version? I remember it was working in 6.6.0, but is broken in 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 483194] Added verification data (CRL/OCSP) break integrity check
https://bugs.kde.org/show_bug.cgi?id=483194 --- Comment #2 from Matej Vašek --- Created attachment 167139 --> https://bugs.kde.org/attachment.cgi?id=167139=edit Signed pdf with embedded OCSP response -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.92.0/rc1 wayland
https://bugs.kde.org/show_bug.cgi?id=477124 Samantha changed: What|Removed |Added CC||s.r...@outlook.com --- Comment #13 from Samantha --- The CC'd patch has made no difference to this bug. I updated to 6.0.2 today and the bug is still present while playing Helldivers 2 Disabled HDR. 100% scale factor 3440x1440 + 2560X1440 I was able to jog the mouse into working by changing resolution in game and then changing back -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 --- Comment #69 from Arazil --- Mouse input in XIVLauncher / Final Fantasy XIV is back to normal operation on Arch Linux with kwin 6.0.2-3. My installation uses the XWayland based default settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483221] On Wayland, Screen Flickering with KDE Plasma 6 on AMD Radeon 780M
https://bugs.kde.org/show_bug.cgi?id=483221 --- Comment #11 from byd2...@gmail.com --- I tried makepkg --syncdeps --install however error poped up with the message CMake Error at /usr/lib/cmake/KF6CoreAddons/KF6CoreAddonsMacros.cmake:29 (message): Must specify INSTALL_NAMESPACE for kcm_auroraedecoration Call Stack (most recent call first): src/plugins/kdecorations/aurorae/src/config/CMakeLists.txt:1 (kcoreaddons_add_plugin) I tried googling with no solution. Anyway to solve it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458233] In some games, controlling the camera with mouse, camera occasionally snaps into a different position when using Wayland
https://bugs.kde.org/show_bug.cgi?id=458233 --- Comment #68 from Casey --- The latest updates on Arch (6.02-3) seems to have cleared up this warping mouse issue. (At least for what I'm doing with Proton games in Steam.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483497] Mouse panel has no content and no touchpad
https://bugs.kde.org/show_bug.cgi?id=483497 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483495] Some commands are named differently in certain distros
https://bugs.kde.org/show_bug.cgi?id=483495 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 483499] Plasma discover crashes after clicking "Installed", or searching something on the discover home page.
https://bugs.kde.org/show_bug.cgi?id=483499 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 483499] New: Plasma discover crashes after clicking "Installed", or searching something on the discover home page.
https://bugs.kde.org/show_bug.cgi?id=483499 Bug ID: 483499 Summary: Plasma discover crashes after clicking "Installed", or searching something on the discover home page. Classification: Applications Product: Discover Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ashilta.sys...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (6.0.2) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.5.0-25-generic x86_64 Windowing System: X11 Distribution: KDE neon 6.0 DrKonqi: 6.0.2 [KCrashBackend] -- Information about the crash: Plasma discover crashes after clicking "Installed", or searching something on the discover home page. This problem begins after installing the "kde-all" package with the command "apt install --install-recommends kde-all". Also, this problem/bug begins if you install the neon-all package with the command "apt install --install-recommends neon-all". The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f3b2c28625a in KNSCore::ResultsStream::fetch() (this=0x62ea630aa7e0) at ./src/core/resultsstream.cpp:70 #5 0x7f3b2c44cac4 in KNSResultsStream::setRequest(KNSCore::Provider::SearchRequest const&) (this=, request=...) at ./libdiscover/backends/KNSBackend/KNSBackend.cpp:107 #6 0x7f3b2c4507b0 in operator() (__closure=0x62ea6261eea0) at ./libdiscover/backends/KNSBackend/KNSBackend.cpp:479 #7 QtPrivate::FunctorCall, QtPrivate::List<>, void, KNSBackend::search(const AbstractResourcesBackend::Filters&):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:137 #8 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:339 #9 QtPrivate::QCallableObject, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x62ea6261ee90, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h:522 #10 0x7f3b3dfcc9b2 in QObject::event(QEvent*) (this=0x62ea623e51a0, e=0x62ea6261ef40) at ./src/corelib/kernel/qobject.cpp:1437 #11 0x7f3b401f181b in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x62ea623e51a0, e=0x62ea6261ef40) at ./src/widgets/kernel/qapplication.cpp:3296 #12 0x7f3b3e075e08 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x62ea623e51a0, event=event@entry=0x62ea6261ef40) at ./src/corelib/kernel/qcoreapplication.cpp:1121 #13 0x7f3b3e075e4d in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=event@entry=0x62ea6261ef40) at ./src/corelib/kernel/qcoreapplication.cpp:1539 #14 0x7f3b3e076000 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x62ea61920800) at ./src/corelib/kernel/qcoreapplication.cpp:1901 #15 0x7f3b3de584f7 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x62ea61a1f0f0) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:243 #16 0x7f3b3ce79d3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f3b3cecf258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f3b3ce773e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f3b3de55c30 in QEventDispatcherGlib::processEvents(QFlags) (this=0x62ea619dd2d0, flags=...) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:393 #20 0x7f3b3e07fceb in QEventLoop::exec(QFlags) (this=0x7ffd1eb746e0, flags=...) at ./src/corelib/global/qflags.h:34 #21 0x7f3b3e07a36c in QCoreApplication::exec() () at ./src/corelib/global/qflags.h:74 #22 0x7f3b3e4e9a20 in QGuiApplication::exec() () at ./src/gui/kernel/qguiapplication.cpp:1925 #23 0x7f3b401ee469 in QApplication::exec() () at ./src/widgets/kernel/qapplication.cpp:2574 #24 0x62ea60774f3c in main(int, char**) (argc=, argv=) at ./discover/main.cpp:218 [Inferior 1 (process 4293) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482716] Startup sound does not play
https://bugs.kde.org/show_bug.cgi?id=482716 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4067 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482892] Switching activities also switches active virtual desktop
https://bugs.kde.org/show_bug.cgi?id=482892 awenh...@gmail.com changed: What|Removed |Added CC||awenh...@gmail.com --- Comment #1 from awenh...@gmail.com --- This also affects my workflow. I would very much like to see an option to turn on the old behavior. I am using two activities: Work and private. I mentally keep track of which virtual desktop I am at, but when changing activities I have to reorient myself every time since I am very likely not at the same virtual desktop that I switched from. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE 6.0.2 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Using Wayland -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481214] Power/battery widget in tray doesn't show power profile/brightness properly
https://bugs.kde.org/show_bug.cgi?id=481214 Daniel Gibson changed: What|Removed |Added Version|5.27.8 |5.27.10 Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- CC||metalcae...@gmail.com --- Comment #4 from Daniel Gibson --- At this point it will probably surprise no one that the brightness feature of this applet is also still broken in 5.27.10 (and the changelog doesn't look like 5.27.11 changes anything), kinda similar to bugs https://bugs.kde.org/show_bug.cgi?id=471010 and https://bugs.kde.org/show_bug.cgi?id=475255 It's nice that this apparently works in Plasma6, but as the next KUbuntu (24.04, an LTS release even) will unfortunately ship 5.27, that doesn't really help many of your users. My observations: - Changing the screen brightness with the slider works, and (unlike the Power Profile slider) the slider even stays at the selected position - Changing the screen brightness through hotkeys shows the correct brightness percentage on that popup in the middle of the screen, but resets the brightness slider to the initial value after a few seconds (perhaps the value from logging in, definitely not the one last set through that slider! 100% in my case) - Like in the other two bugs linked above, the DBus messages look correct -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483498] New: use highlight colour to tint colors if colorschemes use tint with accent colour and no accent colour is set (or is set to derive from color scheme)
https://bugs.kde.org/show_bug.cgi?id=483498 Bug ID: 483498 Summary: use highlight colour to tint colors if colorschemes use tint with accent colour and no accent colour is set (or is set to derive from color scheme) Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: fritz.marti...@web.de CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Current behaviour of tint with accent colour is that the window gets tinted if an accent colour is derived from the wallpaper or if a custom accent colour is set. But if accent color is set to "Derive from Colour scheme", the color scheme will not tint itself using the "highlight" color of the colorscheme. plasma VERSION: 6.0.1 KDE frameworks: 6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483497] New: Mouse panel has no content and no touchpad
https://bugs.kde.org/show_bug.cgi?id=483497 Bug ID: 483497 Summary: Mouse panel has no content and no touchpad Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: 96wvn...@anonaddy.me CC: natalie_clar...@yahoo.de Target Milestone: --- Created attachment 167138 --> https://bugs.kde.org/attachment.cgi?id=167138=edit screenshot of system settings on the mouse panel, which is blank SUMMARY The mouse panel has no content in it STEPS TO REPRODUCE 1. Open up system settings 2. Go to mouse & touchpad OBSERVED RESULT Nothing EXPECTED RESULT Mouse settings SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION The touchpad panel says that there is no touchpad -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 483168] About this System page: Graphics platform reported as X11 on Wayland
https://bugs.kde.org/show_bug.cgi?id=483168 --- Comment #2 from 96wvn...@anonaddy.me --- (In reply to Nate Graham from comment #1) > Are you forcing that app or any other apps to run under the XCB platform, by > any chance? How would I be able to check this? -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 483496] Oxygen icon theme does not provide all icons required on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483496 Martin Fritz changed: What|Removed |Added Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 483496] New: Oxygen icon theme does not provide all icons required on Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483496 Bug ID: 483496 Summary: Oxygen icon theme does not provide all icons required on Plasma 6 Classification: Plasma Product: Oxygen Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: fritz.marti...@web.de Target Milestone: --- Created attachment 167137 --> https://bugs.kde.org/attachment.cgi?id=167137=edit A few screenshots showcasing the missing icons The oxygen icon theme does not provide icons for online-accounts, night-light, battery indicator, the places menu in kickoff as well as no icon for app-permissions. see attached screenshots -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483377] When screen is turned off for energy saving, can't turn it back on with touch or stylus. Must use a mouse or keyboard.
https://bugs.kde.org/show_bug.cgi?id=483377 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Zamundaaa --- The code in KWin to wake the screen on a double tap is there, but IIRC it doesn't work everywhere because a lower level component (libinput, the kernel or even the firmware) turns off the touchscreen. I'm not sure we can do anything about it. Waking the screen on stylus events isn't there yet though and should definitely be implemented. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483495] New: Some commands are named differently in certain distros
https://bugs.kde.org/show_bug.cgi?id=483495 Bug ID: 483495 Summary: Some commands are named differently in certain distros Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 167136 --> https://bugs.kde.org/attachment.cgi?id=167136=edit Discussion in chat SUMMARY Some of the LSP commands are renamed at the packaging level of some distros. It seems they had contributed the original config for vscode language server of css and html, at least. See screenshot P.S: Kate has no LSP component here in the bug tracker. I think its worth it, doing one. 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.0 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483411] KWin Wayland with Nvidia leads to weird shuttering for certain proton game (逆転裁判456 or Apollo Justice: Ace Attorney Trilogy)
https://bugs.kde.org/show_bug.cgi?id=483411 Zamundaaa changed: What|Removed |Added Status|REPORTED|RESOLVED CC||xaver.h...@gmail.com Resolution|--- |UPSTREAM --- Comment #3 from Zamundaaa --- This is https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483493] Can't change files icon if "Browse" is selected
https://bugs.kde.org/show_bug.cgi?id=483493 mozo changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483221] On Wayland, Screen Flickering with KDE Plasma 6 on AMD Radeon 780M
https://bugs.kde.org/show_bug.cgi?id=483221 --- Comment #10 from Zamundaaa --- Created attachment 167135 --> https://bugs.kde.org/attachment.cgi?id=167135=edit modified kwin package Okay, so here's what you can do. If you extract the archive I attached, and run > makepkg --syncdeps --install in that folder, it'll compile and install a modified KWin package. With that, check again if you see the flickering without any environment variables, and if its still there, check if KWIN_DRM_PREFER_COLOR_DEPTH=24 fixes it this time. Afterwards you can go back to the system provided KWin with > sudo pacman -Syu kwin -- You are receiving this mail because: You are watching all bug changes.
