[kwin] [Bug 491453] Occasional graphic corruption in chromium applications
https://bugs.kde.org/show_bug.cgi?id=491453 --- Comment #4 from daf --- I've confirmed that it does happen in xWayland (default) and Native Wayland sessions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491453] Occasional graphic corruption in chromium applications
https://bugs.kde.org/show_bug.cgi?id=491453 --- Comment #3 from daf --- (In reply to David Edmundson from comment #2) > Can you confirm if Chromium is running in wayland mode nor not? > > An easy test is to run "xprop" and hover over chromium. If the cursor > changes to "+" shape, it's in Xwayland. > If it is in wayland, and it's the only application with corruption please > report there. Arc GPUs are new and Chromium's wayland implementation is new. I believe it happens both on native and xWayland sessions, been a while so would have to test a again to confirm. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491453] Occasional graphic corruption in chromium applications
https://bugs.kde.org/show_bug.cgi?id=491453 daf changed: What|Removed |Added Keywords|multiscreen | Summary|Occasional graphic |Occasional graphic |corruption in chromium |corruption in chromium |applications until mouse|applications |over on multi monitor | --- Comment #1 from daf --- I've since then experienced corruption when not using multi monitor, so multimonitor is not related. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491453] Occasional graphic corruption in chromium applications until mouse over on multi monitor
https://bugs.kde.org/show_bug.cgi?id=491453 daf changed: What|Removed |Added Keywords||multiscreen, wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491453] New: Occasional graphic corruption in chromium applications until mouse over on multi monitor
https://bugs.kde.org/show_bug.cgi?id=491453 Bug ID: 491453 Summary: Occasional graphic corruption in chromium applications until mouse over on multi monitor Classification: Plasma Product: kwin Version: 6.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: --- Created attachment 172413 --> https://bugs.kde.org/attachment.cgi?id=172413&action=edit example of the graphical corruption *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When using KDE Plasma with Wayland session and 3 4k screens (125% scale) there's occasional graphical corruption on chromium based applications. The corruption manifests as images on webpages getting an "aurora borealis effect", missing text or flashing colours. Hovering the affected areas will usually make the window refresh and render properly. The corruption is visible to screen recording software. STEPS TO REPRODUCE 1. Use system normally. OBSERVED RESULT Occasional Corruption EXPECTED RESULT No Corruption SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 40 KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Lenovo Thinkpad P1 Gen 7 with Intel Ultra 7 165H Arc iGPU only through Lenovo Thinkpad Workstation Thunderbolt 4 Dock for 3 4k Screens -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491100] Reordering the icon in the Task Manager makes first click on other icons unresponsive
https://bugs.kde.org/show_bug.cgi?id=491100 daf changed: What|Removed |Added CC||daf.pub...@madalien.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 281270] When copying files to a removable disk, speed and progress reflect copying to the local cache not to the disk itself
https://bugs.kde.org/show_bug.cgi?id=281270 --- Comment #41 from daf --- Does glibc 3.39 already have cachestat or is it pending for glibc 3.40? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 281270] When copying files to a removable disk, speed and progress reflect copying to the local cache not to the disk itself
https://bugs.kde.org/show_bug.cgi?id=281270 daf changed: What|Removed |Added CC||daf.pub...@madalien.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 397592] Lock screen before entering to sleep mode
https://bugs.kde.org/show_bug.cgi?id=397592 daf changed: What|Removed |Added CC||daf.pub...@madalien.com --- Comment #3 from daf --- Same issue with a Desktop, tends to happen when sleeping for longer, I'll see the desktop for a second or two before lockscreen is shown. One time I've even been able to bypass the lockscreen (resumed and was able to use the computer without entering my password) which makes me think this is a security concert, however I haven't been able to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 484299] New: Allow moving window by dragging from any point
https://bugs.kde.org/show_bug.cgi?id=484299 Bug ID: 484299 Summary: Allow moving window by dragging from any point Classification: Applications Product: Haruna Version: 1.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY It would be a nice feature to be able to drag the window by clicking and holding any area including the video area but without replacing the current click functionality. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 484298] New: When hiding the toolbar pressing burger button will hang the UI
https://bugs.kde.org/show_bug.cgi?id=484298 Bug ID: 484298 Summary: When hiding the toolbar pressing burger button will hang the UI Classification: Applications Product: Haruna Version: 1.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY When hiding the toolbar a burger button will be placed before play button, pressing it will hang the UI STEPS TO REPRODUCE 1. Hide the toolbar 2. Press the new available burger button OBSERVED RESULT Application UI will stop responding and when trying to close the window KDE will offer to terminate the application EXPECTED RESULT Application not to stop responding SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF ADDITIONAL INFORMATION Using global menu on title bar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471303] Opening Pinned Discord opens new instance if it's been auto started
https://bugs.kde.org/show_bug.cgi?id=471303 --- Comment #8 from daf --- (In reply to Nate Graham from comment #7) > I can't reproduce that at all. Is Discord even capable of opening two > instances? Mine isn't. How are you making that happen? I reproduce it the way i mentioned I open discord and if I close the main window, eventually it will happen. I've had times were I went hours without it happening and others were it will happen right away. At this point I just never close discord window and work around it like that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482587] When snapping a CSD Firefox window, the top border briefly shows the wrong resize cursor
https://bugs.kde.org/show_bug.cgi?id=482587 --- Comment #11 from daf --- While the cursor issue has been confirmed a firefox bug, the cursor offset might be a plasma one, should I change the title of this bug? Related report: https://bugzilla.mozilla.org/show_bug.cgi?id=1884567 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482789] Krita ignores scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=482789 --- Comment #2 from daf --- (In reply to Halla Rempt from comment #1) > Krita does not support wayland at the moment, it uses xwayland when you run > a wayland session. Yes but when running krita in xwayland it ignores scaling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482580] On X11, clicking on bottom edge does not activate panel widgets
https://bugs.kde.org/show_bug.cgi?id=482580 --- Comment #9 from daf --- Added the panel to top and left edge, and work as expected (edge clicks active the widgets). Only bottom and right edge have the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482580] On X11, clicking on bottom edge does not activate panel widgets
https://bugs.kde.org/show_bug.cgi?id=482580 --- Comment #8 from daf --- (In reply to Niccolò Venerandi from comment #7) > Mhh, I can't reproduce on X11 with non-floating auto-hide panel Tried changing my plasma style to default and changing size from 58 to other values (small and big), make it floating and non floating, changing screen edge position and it was broken on all. Anything else I can test? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482587] When snapping a CSD Firefox window, the top border briefly shows the wrong resize cursor
https://bugs.kde.org/show_bug.cgi?id=482587 --- Comment #9 from daf --- https://bugzilla.mozilla.org/show_bug.cgi?id=1884567 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482587] When snapping a CSD Firefox window, the top border briefly shows the wrong resize cursor
https://bugs.kde.org/show_bug.cgi?id=482587 --- Comment #8 from daf --- Related reports: https://bugzilla.mozilla.org/show_bug.cgi?id=1884566 https://bugzilla.mozilla.org/enter_bug.cgi#h=bugForm%7CFirefox -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482586] Cursor size is inconsistent when switching between Wayland and X11
https://bugs.kde.org/show_bug.cgi?id=482586 --- Comment #4 from daf --- (In reply to Nate Graham from comment #3) > It's not really that easy... On X11 the unscaled cursors are an X server bug > that we can't really fix in KWin. The most we could do is replicate that bug > on Wayland, but hauling forward old bugs forever in the name of consistency > isn't really amazing either. Maybe I'm over simplifying the problem but wouldn't it be easier to simply use the Wayland value in the settings and adjust the actual configured cursor size on X11? Example: set size 48 Wayland gets set to size 48 X11 gets set closest size of 48 * scaling factor So Wayland works ass intended and only X11 gets a workaround. Cursor changes don't apply instantly, so when changing session I need to fix the cursor size and then restart to ensure the cursor size is applied to everything which makes swapping sessions more annoying then a dual boot situation with different settings. Panel size used to also have the exact same problem and now in plasma 6 it doesn't, so the cursor sticks out as the only thing that isn't consistent. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471303] Opening Pinned Discord opens new instance if it's been auto started
https://bugs.kde.org/show_bug.cgi?id=471303 --- Comment #6 from daf --- (In reply to Nate Graham from comment #5) > Is that the case in Plasma 6 as well? Currently on plasma 6 and still happens Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF > If so, are the steps to reproduce identical to what was written in the > original problem description? > If not, can you write new ones? Initially i thought it was due to one being started under systemd and another from plasmashell with different paths but since then I've managed to get double instances under plasmashell. Not sure how consistent this is as I already trained myself to never close discord to avoid the bug. Reproducing: 1. Ensure discord is fully closed 2. Launch discord from task manager panel 3. Close main window and confirm tray icon still running 4. Wait around 6 minutes without using discord (but using the browser and other apps) 5. Launch discord again, a second instance should now start -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482580] On X11, clicking on bottom edge does not activate panel widgets
https://bugs.kde.org/show_bug.cgi?id=482580 --- Comment #6 from daf --- (In reply to Nate Graham from comment #5) > How strange. What scale factor are you using? > > Can you reproduce this on X11, Niccolò? I use 200%, but did try scaling back to 100% for a quick test in X11 and made no difference -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482587] When snapping a firefox window the top border shows wrong resize cursor
https://bugs.kde.org/show_bug.cgi?id=482587 --- Comment #6 from daf --- (In reply to Nate Graham from comment #5) > Thanks. Can you reproduce the issue if you turn on the system-provided > titlebars, rather than using built-in CSD headerbars? No, only seems to happen with CSD enabled. While testing it i did notice some odd behaviour, the mouse clicks started to get registered several pixels higher then the cursor so clicks on tabs would get registered on the desktop. Could sometimes reproduce by making a new incognito window and then snapping it. When it triggers the window flashes in a smaller size before expanding to the snapped area, i've made a video of it bellow. https://www.youtube.com/watch?v=j3qv4bqQgSo -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471303] Opening Pinned Discord opens new instance if it's been auto started
https://bugs.kde.org/show_bug.cgi?id=471303 --- Comment #4 from daf --- (In reply to Nate Graham from comment #1) > Are you enabling Discord to autostart in its own settings page, or in System > Settings > Startup and Shutdown > Autostart? issue can still happen without auto start, that said saw people reporting it on ubuntu and I've been able to reproduce it by launching from the command line, so something in discord process "breaks" after a while that makes it's existing instance detection code no longer work so doesn't seem to be a plasma specific bug. https://www.reddit.com/r/discordapp/comments/12ibosm/discord_is_opening_a_new_instance_instead_of_an/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482580] On X11, clicking on bottom edge does not activate panel widgets
https://bugs.kde.org/show_bug.cgi?id=482580 --- Comment #4 from daf --- (In reply to Nate Graham from comment #3) > When you say your panel is "non-floating" does this mean it's never > floating, or it is floating, but it's current;y de-floated due to a window > touching it? > > If the latter, then this may be the same issue as Bug 482827. My panel does not have floating enabled, is in the bottom and set to auto hide. The panel is getting the click as right click opens the generic panel menu but not the task manager menu. So it's more like there's a bottom padding to the panel that's eating the clicks even though hover effect still works -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482791] New: appmenu on title bar does not open in krita window
https://bugs.kde.org/show_bug.cgi?id=482791 Bug ID: 482791 Summary: appmenu on title bar does not open in krita window Classification: Applications Product: krita Version: 5.2.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY When having the appmenu configured on the titlebar it will not open on the krita window Other windows will open the menu normally. STEPS TO REPRODUCE 1. Configure appmenu button on titlebar 2. Open krita 3. Attempt to open appmenu OBSERVED RESULT Nothing seems to happen, if click is spammed on closure of krita the entire desktop will stutter by freeze every few milliseconds not allowing any interaction for a few seconds until it returns to normal. The duration of the stutter seems to be equivalent to how long the button was spammed. EXPECTED RESULT appmenu opening normally SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482789] Krita ignores scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=482789 daf changed: What|Removed |Added Platform|Other |Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 482789] New: Krita ignores scaling in Wayland
https://bugs.kde.org/show_bug.cgi?id=482789 Bug ID: 482789 Summary: Krita ignores scaling in Wayland Classification: Applications Product: krita Version: 5.2.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY Krita ignores scaling in Wayland STEPS TO REPRODUCE 1. Set 200% scaling 2. Open Krita OBSERVED RESULT Krita interface appears to still be rendered at 100% EXPECTED RESULT Krita interface should be rendered at 200% like all other applications SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482582] Wayland GTK applications ignore theme settings
https://bugs.kde.org/show_bug.cgi?id=482582 daf changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from daf --- installing xdg-desktop-portal-gtk seems to have fixed the theme miss-match, apologies for the false report -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482586] Cursor size is inconsistent when switching between Wayland and X11
https://bugs.kde.org/show_bug.cgi?id=482586 --- Comment #2 from daf --- Panel sizing was made the same on Wayland and X11, should cursor size in the settings also be adjusted so it's seamless transition? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482587] When snapping a firefox window the top border shows wrong resize cursor
https://bugs.kde.org/show_bug.cgi?id=482587 --- Comment #4 from daf --- Forgot to mention that on Wayland firefox ignores all Plasma styling thus it never shows the correct cursor https://bugs.kde.org/show_bug.cgi?id=482582 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482587] When snapping a firefox window the top border shows wrong resize cursor
https://bugs.kde.org/show_bug.cgi?id=482587 --- Comment #3 from daf --- While making a video I've realised that what's actually happening is that the inner Firefox window border always shows the incorrect resize cursor, but when not snapped there's a second border around the window that shows the correct cursor. See below video showing behaviour. https://youtu.be/vT_CYkm7C-0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482580] On X11, clicking on bottom edge does not activate panel widgets
https://bugs.kde.org/show_bug.cgi?id=482580 daf changed: What|Removed |Added Version|unspecified |6.0.1 --- Comment #2 from daf --- Indeed, on Wayland it works correctly. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482582] Wayland GTK applications ignore theme settings
https://bugs.kde.org/show_bug.cgi?id=482582 daf changed: What|Removed |Added Version|6.0.0 |6.0.1 --- Comment #3 from daf --- @Nicolas Fella yes on kde-gtk-config no on xdg-desktop-portal-gtk Wouldn't xdg-desktop-portal-gtk only be needed in non plasma desktops? @Nate Graham Confirmed on Mozilla Firefox 123.0.1 and Input Remapper 2.0.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482587] New: When snapping a firefox window the top border shows wrong resize cursor
https://bugs.kde.org/show_bug.cgi?id=482587 Bug ID: 482587 Summary: When snapping a firefox window the top border shows wrong resize cursor Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY When snapping a firefox window the top border shows wrong resize cursor instead of the resize cursor of the user selected theme. unsnapping the top border shows the correct cursor again. STEPS TO REPRODUCE 1. Snap a firefox window to the side 2. Hover top window border OBSERVED RESULT The default GTK resize cursor is shown EXPECTED RESULT The selected theme resize cursor to be shown SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482586] New: Cursor size is inconsistent when switching between Wayland and X11
https://bugs.kde.org/show_bug.cgi?id=482586 Bug ID: 482586 Summary: Cursor size is inconsistent when switching between Wayland and X11 Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_cursortheme Assignee: plasma-b...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY On Wayland cursor size are 2x the size then they are on X11 for any given picked size. STEPS TO REPRODUCE 1. Select a big cursor size in X11 2. Change to a Wayland session OBSERVED RESULT Cursor now looks 2x bigger then it did on X11 EXPECTED RESULT Cursor size should be consistent across Wayland and X11 SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467039] With SDDM using Wayland, syncing settings does not send along the correct scaling as it does with X11
https://bugs.kde.org/show_bug.cgi?id=467039 daf changed: What|Removed |Added CC||daf.pub...@madalien.com --- Comment #2 from daf --- To add to this bug I've notice cursor theme and size is also not respected. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 482582] New: Wayland GTK applications ignore theme settings
https://bugs.kde.org/show_bug.cgi?id=482582 Bug ID: 482582 Summary: Wayland GTK applications ignore theme settings Classification: Plasma Product: kwayland-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY Wayland native GTK applications ignore any GTK theme settings (colors, window theme, cursor). Changing to X11 make gtk applications respect theme again STEPS TO REPRODUCE 1. Start a Wayland session 2. Open a GTK application OBSERVED RESULT GTK application uses default gnome theme and decorations EXPECTED RESULT GTK application respects theme set in plasma settings SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482580] New: Clicking on bottom edge does not activate panel widgets
https://bugs.kde.org/show_bug.cgi?id=482580 Bug ID: 482580 Summary: Clicking on bottom edge does not activate panel widgets Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY When docking the panel to bottom of the screen, clicking on the bottom of the screen does not activate the action of the widget, it does however highlight the widget hover animation. STEPS TO REPRODUCE 1. Have non floating panel in bottom of the screen 2. scroll mouse down until it's no longer visible 3. attempt to click a hovered widget in the panel OBSERVED RESULT Nothing happens EXPECTED RESULT Highlighted widget click action should be triggered SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] No output from KMagnifier on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 --- Comment #6 from daf --- I'm still staying on X11 to use this accessibility tools, but it's not even listed on https://community.kde.org/Plasma/Wayland_Showstoppers . Has this tool been replaced by something else already on Wayland? If not, is accessibility not being considered when migrating to Wayland by default? -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 472437] Doesnt work on Wayland
https://bugs.kde.org/show_bug.cgi?id=472437 daf changed: What|Removed |Added Status|REPORTED|RESOLVED CC||daf.pub...@madalien.com Resolution|--- |DUPLICATE --- Comment #1 from daf --- *** This bug has been marked as a duplicate of bug 438912 *** -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] No output from KMagnifier on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 daf changed: What|Removed |Added CC||amanita+kdeb...@mailbox.org --- Comment #5 from daf --- *** Bug 472437 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] No output from KMagnifier on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 daf changed: What|Removed |Added CC||rafael.linux.u...@gmail.com --- Comment #4 from daf --- *** Bug 472320 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 472320] "KMag" not working in Wayland
https://bugs.kde.org/show_bug.cgi?id=472320 daf changed: What|Removed |Added Resolution|--- |DUPLICATE CC||daf.pub...@madalien.com Status|REPORTED|RESOLVED --- Comment #1 from daf --- *** This bug has been marked as a duplicate of bug 438912 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471303] New: Opening Pinned Discord opens new instance if it's been auto started
https://bugs.kde.org/show_bug.cgi?id=471303 Bug ID: 471303 Summary: Opening Pinned Discord opens new instance if it's been auto started Classification: Plasma Product: plasmashell Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: daf.pub...@madalien.com Target Milestone: 1.0 SUMMARY When configuring discord to autostart it creates a systemd unit, when pinning discord to task manager it also generates a systemd unit when starting. autostart launches under systemd, task manager under plasmashell, if discord was autostarted and main window is closed (running on system tray), opening it again from a pinned task manager icon will generate a new systemd unit and start a new/separate instance of discord instead of re-opening the window of the existing instance. I don't know who's bug this is so reporting it here as a start. STEPS TO REPRODUCE 1. Enable auto start on discord 2. Allow systemd to autostart discord 3. Close the main window 4. Attempt to open discord again from pinned discord on taskbar OBSERVED RESULT A second discord instance is opened instead of the already running instance EXPECTED RESULT It should re-open the window of the existing discord instance SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux Unstable Branch (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.107.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436559] GTK3 CSD buttons are noticeably smaller than regular Breeze Qt style
https://bugs.kde.org/show_bug.cgi?id=436559 daf changed: What|Removed |Added CC||daf.pub...@madalien.com --- Comment #15 from daf --- Created attachment 157003 --> https://bugs.kde.org/attachment.cgi?id=157003&action=edit Issue with 200% scaling, dolphin, input remapper, pamac, pamac about dialog Just adding a screenshot of how it looks when 200% scaling. >From back to front: - dolphin window (qt5) - input remaper config window (gtk3) - pamac main window (gtk3) - pamac about dialog window (gtk3) System: Operating System: Manjaro Linux KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.2-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442790] kdeconnect wont reconnect with pc after sleep until main window on pc is opened
https://bugs.kde.org/show_bug.cgi?id=442790 --- Comment #1 from daf --- Forgot to add the version details: SOFTWARE/OS VERSIONS Windows: Windows 10.0.19043 (21H1) Windows App Version: 0.0.878.0 (windows store version) Android: 10 (lineage 17.1, build: 10 QQ3A, 200805.001) Android App Version: 1.17.0 (not battery optimized) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442790] New: kdeconnect wont reconnect with pc after sleep until main window on pc is opened
https://bugs.kde.org/show_bug.cgi?id=442790 Bug ID: 442790 Summary: kdeconnect wont reconnect with pc after sleep until main window on pc is opened Product: kdeconnect Version: 0.8 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: daf.pub...@madalien.com Target Milestone: --- SUMMARY After resuming the PC from sleep the application will not reconnect unless the interface on PC is opened and the paired phone is clicked. STEPS TO REPRODUCE 1. Put the computer to sleep for a ~1h 2. Resume the computer to sleep 3. Check KDE Connect status OBSERVED RESULT The phone wont show as connected. Opening the kde connect application on the phone by itself wont reconnect, opening the main window on PC and clicking the phone icon will re-establish connection. EXPECTED RESULT KDE Connect automatedly re-establish connection without user interaction. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373072] project is one frame too long
https://bugs.kde.org/show_bug.cgi?id=373072 Assa Daf changed: What|Removed |Added CC||assa...@gmail.com --- Comment #6 from Assa Daf --- Created attachment 107598 --> https://bugs.kde.org/attachment.cgi?id=107598&action=edit Extra black frame at the end of the project Hello Attached simple blckframe.kdenlive project file that has that extra frame at the end after the last clip. Removing the last clip, the extra frame does not disappear but is still there after the new last clip. kdenlive 17.08, opensuse leap 42.3 amd64 -- You are receiving this mail because: You are watching all bug changes.
