[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 Eugene San changed: What|Removed |Added CC||eugene...@gmail.com --- Comment #64 from Eugene San --- Created attachment 169403 --> https://bugs.kde.org/attachment.cgi?id=169403=edit klockscreen.sh: "Self-Installing" script to configure screen off delay using notifications hooks The is fixed in Plasma 6 but for Plasma 5 users, I am attaching klockscreen.sh "Self-Installing" script to configure screen off delay using notifications hooks. Place the script anywhere (~/bin or ~/.config) and run run it once with 'install' parameter once. To disable, just delete it and ~/.config/ksmserver.notifyrc Details inside. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485870] Can't resize Application Launcher window under X11, works under Wayland
https://bugs.kde.org/show_bug.cgi?id=485870 Eugene San changed: What|Removed |Added CC||eugene...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485870] Can't resize Application Launcher window under X11, works under Wayland
https://bugs.kde.org/show_bug.cgi?id=485870 Eugene San changed: What|Removed |Added Summary|Can't resize Application|Can't resize Application |Launcher windows under X11, |Launcher window under X11, |works under Wayland |works under Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485870] New: Can't resize Application Launcher windows under X11, works under Wayland
https://bugs.kde.org/show_bug.cgi?id=485870 Bug ID: 485870 Summary: Can't resize Application Launcher windows under X11, works under Wayland Classification: Plasma Product: plasmashell Version: git-stable-Plasma/5.27 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: eugene...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 When opening Application Launcher window, mouse cursor changes to resize style but won't actually resize under X11. The same works as expected under Wayland session. Tested on: Ubuntu 23.10 - KDE 5.27.10, KF 5.112.0, QT 5.15.10 Also on Ubuntu 24.04 with also 5.27.11 Reproduction is simple. Install Kubuntu 23.10 or 24.04, Open Application Launcher by clicking the button in in the panel. Move cursor to the edge of the applet window, try to resize. On X11 the cursor just leaves the window border and does nothing. On Wayland the cursor "grabs" the window edge and resizes it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 --- Comment #42 from Eugene San --- I know Plasma 6 is the main focus nowadays but the bug still affects Plasma 5 which is still shipped on Neon and upcoming Kubuntu 24.04 Plasma 5.27.11 and going to be an issue for a LOT of users and for a LONG time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Eugene San changed: What|Removed |Added CC||eugene...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 481959] Bluetooth status not remembered on login
https://bugs.kde.org/show_bug.cgi?id=481959 --- Comment #2 from Ariel San Román --- (In reply to Nate Graham from comment #1) > Can you open System Settings > Bluetooth > Configure and verify that "On > login:" is set to "Restore previous status?" If it is, does the problem go > away if you set it to "Disable Bluetooth" and reboot? Thank you for your time and for responding. I had tried all possible options, and none were working. That just got resolved now, with the latest update on 01/03. Thanks again for your response. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Ariel San Román changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #22 from Ariel San Román --- (In reply to Rich Johnson from comment #5) Thank you for your time! I was able to solve it following your instructions!!! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481959] New: Issues with the Bluetooth
https://bugs.kde.org/show_bug.cgi?id=481959 Bug ID: 481959 Summary: Issues with the Bluetooth Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ariel.sanro...@hotmail.com Target Milestone: --- STEPS TO REPRODUCE 1. I configure Bluetooth to be disabled on the next login 2. 3. OBSERVED RESULT I log in and Bluetooth starts active EXPECTED RESULT I log in and Bluetooth remains deactivated SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This started happening since the update to Plasma 6.0.0. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481957] New: Issues with the Applications Menu
https://bugs.kde.org/show_bug.cgi?id=481957 Bug ID: 481957 Summary: Issues with the Applications Menu Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ariel.sanro...@hotmail.com Target Milestone: --- STEPS TO REPRODUCE 1. I try to power off, log out, or restart, and it does nothing. 2. 3. OBSERVED RESULT 1. I have to perform that action through the console/terminal. EXPECTED RESULT 1. to execute the actions Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION This started happening since the update to Plasma 6.0.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479201] New: Allow hiding of the titlebar for maximized windows
https://bugs.kde.org/show_bug.cgi?id=479201 Bug ID: 479201 Summary: Allow hiding of the titlebar for maximized windows Classification: Plasma Product: kwin Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: eugene...@gmail.com Target Milestone: --- Default plasma config consumes too much vertical space. It is not suitable for hardly suitable on small 16:9 displays. In previous versions there an option to hide titlebar for maximized windows but it no longer available. It is still possible to add below config option but doesn't work as expected. Instead it hides the titlebar permanently and does not restore the titlebar after un-maximizing. ``` [Windows] BorderlessMaximizedWindows=true ``` Please restore the option to configure titlebar behavior for maximized windows. Also, it would be nice to have window control buttons in the panel or at as first options in the window context menu. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 479200] New: Allow relocation of the tabs bar to other toolbars
https://bugs.kde.org/show_bug.cgi?id=479200 Bug ID: 479200 Summary: Allow relocation of the tabs bar to other toolbars Classification: Applications Product: konsole Version: master Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: eugene...@gmail.com Target Milestone: --- Konsole consumes too much vertical space with default 2 toolbars. It would be nice to be able to hide it and move to the main toolbar as a component. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477763] New: Disappeared night color icon
https://bugs.kde.org/show_bug.cgi?id=477763 Bug ID: 477763 Summary: Disappeared night color icon Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: ariel.sanro...@hotmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 163644 --> https://bugs.kde.org/attachment.cgi?id=163644=edit Screenshot of System Tray Preferences - Inputs (night color not displayed) After the last big update (3 days ago), the night color icon disappeared from the system tray. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] Applying a template in the BQM fails in MP4 files
https://bugs.kde.org/show_bug.cgi?id=467312 --- Comment #7 from san.li@gmail.com --- (In reply to Maik Qualmann from comment #6) > You can also display sub-albums in the main view via the view menu and then > mark the corresponding images and add them to the BQM. This is the intended > workflow. Templates can be applied and in digiKam-8.0.0 also captions and > labels. We already have bug reports requests for more metadata. > > Maik Thank you very much. According to the method you provided, I can select all the pictures that need batch processing before entering BQM. Although this is more cumbersome than freely selecting folders and files after entering BQM, at least there is a solution, which is good start. Looking forward to more surprises in subsequent versions. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] Applying a template in the BQM fails in MP4 files
https://bugs.kde.org/show_bug.cgi?id=467312 san.li@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from san.li@gmail.com --- (In reply to Maik Qualmann from comment #4) > https://docs.digikam.org/en/batch_queue.html > > Maik Thanks, Maik, I'm aware of the documentation, but it doesn't seem to solve my problem: Doing operations on images in multiple folders (a parent folder with multiple subfolders), such as writing metadata or writing Template with copyright information. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] Applying a template in the BQM fails in MP4 files
https://bugs.kde.org/show_bug.cgi?id=467312 san.li@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from san.li@gmail.com --- (In reply to Maik Qualmann from comment #1) > Writing to MP4 files will only be possible in digiKam-8.0.0 with activated > ExifTool support. > > Maik Hi Maik Most of the time I want to batch write metadata or templates to multiple folders, even rename them, and convert them to other formats such as webp. Probably digikam already implements these functions, but I didn't find a way to use them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467312] New: Task batch management
https://bugs.kde.org/show_bug.cgi?id=467312 Bug ID: 467312 Summary: Task batch management Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: BatchQueueManager-Core Assignee: digikam-bugs-n...@kde.org Reporter: san.li@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. selecte mp4 2. Apply Metadata Template 3. selecte templates 4. perform tasks OBSERVED RESULT Unable to process item EXPECTED RESULT Item processed successfully ADDITIONAL INFORMATION Batch operations on parent folders (including subfolders) are currently not available -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461032] With 150% scale, when maximising a window, kwin_x11 fails to redraw the window content
https://bugs.kde.org/show_bug.cgi?id=461032 --- Comment #15 from San --- (In reply to Thomas Kear from comment #14) > that works! many thanks!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461032] With 150% scale, when maximising a window, kwin_x11 fails to redraw the window content
https://bugs.kde.org/show_bug.cgi?id=461032 --- Comment #13 from San --- (In reply to David Warner from comment #12) > @San Does your package manager let you downgrade KWin to 5.26.1? actually I don't know but I doubt it, because the issue came when I dist-upgraded KDE neon to the new version based on ubuntu 22 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461032] With 150% scale, when maximising a window, kwin_x11 fails to redraw the window content
https://bugs.kde.org/show_bug.cgi?id=461032 San changed: What|Removed |Added CC||sanette-li...@laposte.net --- Comment #11 from San --- (In reply to Andreas Sturmlechner from comment #10) > imo this is worth a respin or at least mail to distros list. I agree, for me the workaround to slightly change the scale factor does not work (I normally use 225), hence my only "solution" is to disable compositing, which is not very nice (this even entail some graphics artifacts). I have to give a talk next week with my KDE laptop and I'm not sure how I will handle this :( -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 453962] New: Automatic day/night cycle.
https://bugs.kde.org/show_bug.cgi?id=453962 Bug ID: 453962 Summary: Automatic day/night cycle. Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: smasca...@gmail.com Target Milestone: --- SUMMARY Is it possible to have an automatic day/night cycle? Like post a certain time or even on detecting sunset (based on location or manual) , the system could change the theme/enable a dark version of the same theme, which includes changing the wallpaper and enabling night light. This could expand to other applications to enable their in built dark themes and later on to include fonts, icons, and more. Maybe even a morning/afternoon/night routine? SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.6-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443385] New: Settings window needs horizontal scroll bar
https://bugs.kde.org/show_bug.cgi?id=443385 Bug ID: 443385 Summary: Settings window needs horizontal scroll bar Product: systemsettings Version: 5.22.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: smasca...@gmail.com Target Milestone: --- Created attachment 142202 --> https://bugs.kde.org/attachment.cgi?id=142202=edit Application latched on the left side with the affected UI SUMMARY Settings window doesn't automatically enable the horizontal scroll bar which cuts off the interface and makes some options inaccessible. Only way to access them is by resizing the interface. STEPS TO REPRODUCE 1. Open settings application. (I use a 17.3 inch FHD display for reference.) 2. Latch the window to either side of the screen or reduce the size of the window manually to the smallest allowed horizontal length. OBSERVED RESULT UI elements are cut off and certain options are inaccessible. EXPECTED RESULT Horizontal scroll bar should be available at the bottom of the screen or a responsive UI to make all options available in current window arrangement like in "Workspace Behavior". SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425744] displaylink monitor not recognized
https://bugs.kde.org/show_bug.cgi?id=425744 --- Comment #4 from San --- yes, the displaykink driver seems to give me 4 screens: $ ls /dev/dri/by-path/ pci-:00:02.0-card pci-:00:02.0-render platform-evdi.0-card platform-evdi.1-card platform-evdi.2-card platform-evdi.3-card -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425744] displaylink monitor not recognized
https://bugs.kde.org/show_bug.cgi?id=425744 --- Comment #2 from San --- WOW! it works! Thanks! Now I can set different scalings to monitors with very different resolutions, and move a window from one to the other while the window appears more or less the same on both! (that is, not like twice smaller on one monitor). I've been waiting for this moment for s long ;) Here is the output of $ ls /dev/dri/ by-path card0 card1 card2 card3 card4 renderD128 (while monitor is connected). If I disconnect it, I have the same. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431192] Transparent gap between layer content and stroke layer style
https://bugs.kde.org/show_bug.cgi?id=431192 --- Comment #3 from San Jacobs --- (In reply to Tymond from comment #1) Yes, definitely! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431192] Transparent gap between layer content and stroke layer style
https://bugs.kde.org/show_bug.cgi?id=431192 --- Comment #2 from San Jacobs --- Created attachment 134585 --> https://bugs.kde.org/attachment.cgi?id=134585=edit Krita file with examples of inside and outside -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431192] Transparent gap between layer content and stroke layer style
https://bugs.kde.org/show_bug.cgi?id=431192 San Jacobs changed: What|Removed |Added CC||sanjac...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 431192] New: Transparent gap between layer content and stroke layer style
https://bugs.kde.org/show_bug.cgi?id=431192 Bug ID: 431192 Summary: Transparent gap between layer content and stroke layer style Product: krita Version: 4.4.1 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: sanjac...@protonmail.com Target Milestone: --- Created attachment 134584 --> https://bugs.kde.org/attachment.cgi?id=134584=edit Visual comparison of observed (Krita) and expected result (Photoshop). SUMMARY When using the layer style stroke with position outside, there is a transparent gap between any anti-aliased edges of the layer content and the stroke. The same, but opposite is true about using the position inside. However, instead of a transparent gap, the original layer's color shines through where the outer edge of the stroke and the layer content meet. STEPS TO REPRODUCE 0. Create white background layer 1. Create layer with black content with anti-aliased edges to transparency 2. Enable the stroke layer style 3a. Set stroke position to outside with white color 3b. Set stroke position to inside with black color OBSERVED RESULT Inside position: An edge where the color of the content and the stroke mix. Outside position: An edge where the color of the content and the stroke mix. EXPECTED RESULT The same color at the edge as in the stroke. ADDITIONAL INFORMATION Outside can be solved by rendering the stroke as done with center-position, but double thickness and below the layer in question. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425744] displaylink monitor not recognized
https://bugs.kde.org/show_bug.cgi?id=425744 San changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425744] New: displaylink monitor not recognized
https://bugs.kde.org/show_bug.cgi?id=425744 Bug ID: 425744 Summary: displaylink monitor not recognized Product: kwin Version: 5.19.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: sanette-li...@laposte.net Target Milestone: --- SUMMARY External monitor on a Displaylink device is not recognized by Plasma-Wayland (but it does work with Plasma-Xorg) STEPS TO REPRODUCE 1. install and start the displaylink driver https://www.displaylink.com/downloads/file?id=1576 2. reboot 3. log-in selecting Plasma-Wayland 4. plug-in an external monitor on the Displaylink device OBSERVED RESULT Monitor is not recognized (neither by xrandr nor by Plasma Screen configuration) EXPECTED RESULT external monitor should be recognized, as it is with Plasma-Xorg SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User Edition 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Dell XPS 13 laptop with USB Displaylink extension (including audio, ethernet, and HDMI for external monitors) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423702] bad scaling on external monitor if QT_SCREEN_SCALE_FACTORS is set.
https://bugs.kde.org/show_bug.cgi?id=423702 --- Comment #6 from San --- @Nate, unfortunately I use displaylink driver for my external screen, and it won't work with Wayland. (not detected) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423702] bad scaling on external monitor if QT_SCREEN_SCALE_FACTORS is set.
https://bugs.kde.org/show_bug.cgi?id=423702 --- Comment #5 from San --- my QT_SCREEN_SCALE_FACTORS is eDP-1=2;DP-1=1;HDMI-1=1;DP-2=1;HDMI-2=1; (notice the "2" for the laptop screen eDP-1) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423702] bad scaling on external monitor if QT_SCREEN_SCALE_FACTORS is set.
https://bugs.kde.org/show_bug.cgi?id=423702 --- Comment #2 from San --- @Oliver, I'm not sure but I don't think so, since in my case the problem is due to different scalings on the monitors. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423702] New: bad scaling on external monitor if QT_SCREEN_SCALE_FACTORS is set.
https://bugs.kde.org/show_bug.cgi?id=423702 Bug ID: 423702 Summary: bad scaling on external monitor if QT_SCREEN_SCALE_FACTORS is set. Product: okular Version: 1.10.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: sanette-li...@laposte.net Target Milestone: --- Created attachment 129796 --> https://bugs.kde.org/attachment.cgi?id=129796=edit good/bad antialiasing SUMMARY bad scaling on external monitor, almost impossible to read at normal size, if QT_SCREEN_SCALE_FACTORS is set. STEPS TO REPRODUCE 1. have a Hi-DPI laptop (here 3200x1800) 2. connect an external normal-dpi monitor (1920x1200) to extend the desktop 3. open a PDF document and move the window onto the external screen OBSERVED RESULT the PDF is scaled with very bad antialiasing. EXPECTED RESULT nice antialiasing SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Workaround: export QT_SCREEN_SCALE_FACTORS='' before using okular, then it works -- You are receiving this mail because: You are watching all bug changes.
