[Powerdevil] [Bug 489510] Screen dims despite video playing
https://bugs.kde.org/show_bug.cgi?id=489510 Szymon Łągiewka changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #2 from Szymon Łągiewka --- You're indubitably right. Tested quickly with VLC from rpm and it doesn't seem to be an issue there. *** This bug has been marked as a duplicate of bug 486506 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486506] Firefox (Flatpak) does not inhibit power management when playing videos
https://bugs.kde.org/show_bug.cgi?id=486506 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #9 from Szymon Łągiewka --- *** Bug 489510 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 489510] New: Screen dims despite video playing
https://bugs.kde.org/show_bug.cgi?id=489510 Bug ID: 489510 Summary: Screen dims despite video playing Classification: Plasma Product: Powerdevil Version: 6.1.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs-...@lagiewka.pl CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- *** 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 STEPS TO REPRODUCE 1. Have "dim automatically" enabled (e.g. after 30s to see it quickly) 2. Start video playback (e.g. in Firefox) 3. Confirm in "Power and Battery" tray widget that sleep and screen locking are blocked due to FF "video-playing" 4. Wait period specified in 1. OBSERVED RESULT Screen dims after 30s EXPECTED RESULT Screen is not dimmed for as long as the video is playing. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.6-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I see no UX reason why screen should get dimmed whilst the video is playing. It just doesn't make any sense to reduce the experience, especially when watching full screen and not performing any mouse/keyboard actions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446431] Automatic do not disturb reason can be confusing
https://bugs.kde.org/show_bug.cgi?id=446431 --- Comment #5 from Szymon Łągiewka --- Created attachment 171208 --> https://bugs.kde.org/attachment.cgi?id=171208&action=edit DND reason as of 30.06.2024 The DND message now shows Firefox Web Browser as the reason. It looks like a FIXED issue to me. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 487658] New naming style is not great when a lot of similar devices are all connected at once
https://bugs.kde.org/show_bug.cgi?id=487658 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 488897] Devices' names are different from System Settings
https://bugs.kde.org/show_bug.cgi?id=488897
--- Comment #4 from Szymon Łągiewka ---
I knew this change was coming to the applet, so I checked the MR behind it. It
seems to use `node.nick` property to display prettier names.
https://invent.kde.org/plasma/plasma-pa/-/merge_requests/239
However, it's seems to be the audio stack PipeWire (or it's PulseAudio/ALSA
compatibility) that provides the weird data. Here's output of `pw-dump` props
for a device that shows us "USB Device #1"
```
"props": {
"alsa.card": 0,
"alsa.card_name": "SteelSeries Arctis 5",
"alsa.class": "generic",
"alsa.components": "USB1038:12aa",
"alsa.device": 1,
"alsa.driver_name": "snd_usb_audio",
"alsa.id": "S5",
"alsa.long_card_name": "SteelSeries SteelSeries Arctis 5 at
usb-:0c:00.3-3, full speed",
"alsa.mixer_name": "USB Mixer",
"alsa.name": "USB Audio #1",
"alsa.resolution_bits": 16,
"alsa.subclass": "generic-mix",
"alsa.subdevice": 0,
"alsa.subdevice_name": "subdevice #0",
"api.alsa.card.longname": "SteelSeries SteelSeries Arctis 5 at
usb-:0c:00.3-3, full speed",
"api.alsa.card.name": "SteelSeries Arctis 5",
"api.alsa.path": "hw:0,1,0",
"api.alsa.pcm.card": 0,
"api.alsa.pcm.stream": "playback",
"audio.adapt.follower": "",
"audio.channels": 2,
"audio.position": "FL,FR",
"card.profile.device": 1,
"client.id": 48,
"clock.quantum-limit": 8192,
"device.api": "alsa",
"device.class": "sound",
"device.id": 72,
"device.profile.description": "Game",
"device.profile.name": "analog-game",
"device.routes": 1,
"factory.id": 18,
"factory.mode": "merge",
"factory.name": "api.alsa.pcm.sink",
"library.name": "audioconvert/libspa-audioconvert",
"media.class": "Audio/Sink",
"node.description": "SteelSeries Arctis 5 Game",
"node.driver": true,
"node.name":
"alsa_output.usb-SteelSeries_SteelSeries_Arctis_5_-00.analog-game",
"node.nick": "USB Audio #1",
"node.pause-on-idle": false,
"object.id": 78,
"object.path": "alsa:pcm:0:hw:0,1,0:playback",
"object.serial": 585,
"priority.driver": 737,
"priority.session": 737
}
```
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-pa] [Bug 488897] Devices' names are different from System Settings
https://bugs.kde.org/show_bug.cgi?id=488897 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #3 from Szymon Łągiewka --- Created attachment 170914 --> https://bugs.kde.org/attachment.cgi?id=170914&action=edit Device names as seen under macOS I'm attaching how macOS sees the same input devices (Arctis headphones with chat+game mode) I'm glad that I finally see devices' more natural names. "USB Audio Codec" is in place of "Analog Output (PCM2902 Audio Codec Analog Stereo)" which never made any sense to me. Now it matches what macOS was always reporting. However, the Arctis case makes it seem unpolished. Looking forward to more updates! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation
https://bugs.kde.org/show_bug.cgi?id=446948 Szymon Łągiewka changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Szymon Łągiewka --- Closing ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation
https://bugs.kde.org/show_bug.cgi?id=446948 --- Comment #4 from Szymon Łągiewka --- I can no longer see the issue! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation
https://bugs.kde.org/show_bug.cgi?id=446948 --- Comment #3 from Szymon Łągiewka --- >From Nate's blog I heard about ``` In the Plasma Wayland session, when you drag a window containing QtQuick-based user interface elements to another screen that’s using a different scale factor, the window instantly adjusts itself to display properly according to that screen’s scale factor, with no blurriness or pixelation. It even works when a window is partially on one screen and partially on another! (David Edmundson, Frameworks 5.101. Link 1 and link 2) ``` This seems like it's similar. I will test if (or when) I get the chance to update to 5.101. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 453352] [Wayland] Undesired save to default folder
https://bugs.kde.org/show_bug.cgi?id=453352 Szymon Łągiewka changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Szymon Łągiewka --- Updated my system to latest Fedora packages: frameworks 5.99, gear 22.08.1, Plasma 5.25.5. Quick test and seems like this is working properly - screenshots are saved only to the clipboard. I'm not using this PC much lately, so I will assume that this won't go rouge again. Closing as resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=455684 --- Comment #7 from Szymon Łągiewka --- Updated my guest Fedora to 5.25.4. Host Arch still on 25.3. Issues seems resolved with .4 - cursor is no longer flipped! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=455684 --- Comment #5 from Szymon Łągiewka --- I can confirm the same issue. QEMU, KVM, virt manager and virgl. Host: Arch Linux Guests: Fedora 36, openSUSE Tumbleweed. This didn't happen with Fedora when it was on 5.24. TW had 5.25 when I first installed it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=455684 --- Comment #4 from Szymon Łągiewka --- Created attachment 150624 --> https://bugs.kde.org/attachment.cgi?id=150624&action=edit openSUSE Tumbleweed, Plasma 5.25.2, virgl and reverted cursor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455684] The cursor was inverted and the selected region was above the cursor position in VMs with 3D acceleration enabled
https://bugs.kde.org/show_bug.cgi?id=455684 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #3 from Szymon Łągiewka --- Created attachment 150623 --> https://bugs.kde.org/attachment.cgi?id=150623&action=edit Fedora 36, Plasma 5.25.3, virgl and reverted cursor -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 453352] New: [Wayland] Undesired save to default folder
https://bugs.kde.org/show_bug.cgi?id=453352 Bug ID: 453352 Summary: [Wayland] Undesired save to default folder Product: Spectacle Version: 22.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: bugs-...@lagiewka.pl CC: k...@david-redondo.de Target Milestone: --- Created attachment 148542 --> https://bugs.kde.org/attachment.cgi?id=148542&action=edit Undesired file on disk is confirmed SUMMARY When using a shortcut to capture rectangular region, a screenshot is saved both to clipboard and as file. The option to save to a default folder is disabled. My settings: "Save file to default folder" off After taking a screenshot: Copy image to clipboard STEPS TO REPRODUCE 1. Set "Save file to default folder" to off 2. Set "After taking a screenshot" to "Copy image to clipboard" (possibly relog/reboot to make sure it applies properly) 3. Press meta+shift+prtscr 4. Select rectangular region OBSERVED RESULT 1. Confirmation notification pops up for clipboard 1a. SS is indeed in clipboard 2. Confirmation notification pops up for file on disk 2a. SS file is indeed in the default folder EXPECTED RESULT 1. Confirmation notification pops up for clipboard 1a. SS is indeed in clipboard SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT ADDITIONAL INFORMATION I've seen https://bugs.kde.org/show_bug.cgi?id=433442, which is a reverse of my issue. I just want the region to be in clipboard so I can forward it easily. Files on disk are just polluting my folder. Great to see 22.04 finally support shortcuts without Spectacle running, but this file thing is just annoying. I've also observed things (I can't reproduce now) like: a) clipboard not receiving the SS on the first try, b) shortcut + region selection causing the opening of the Spectacle window, saving to clipboard with no file present. That's also annoying since I don't need that window and need to close it manually. This might've been related to some weird steps I did why writing this issue. I also updated to 5.24.5, rebooted so there might've been something to that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358277] Chrome apps assuming same icon from chrome browser, in Icon-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=358277 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #12 from Szymon Łągiewka --- My two pennies worth: Just updated Chrome to v99. I use Ozone/Wayland backend. This release sets proper Icons for Chrome apps for me. Tested with Spotify and Tidal. The icon is also properly set for all effects presenting window with its icon visible, i.e. the overview effect. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432264] Wayland context Menus entries disappear/ graphic glitching
https://bugs.kde.org/show_bug.cgi?id=432264 --- Comment #13 from Szymon Łągiewka --- Small update from me. Today I found out that when I open the context menu and then press left alt (as for using hints etc) the context menu gets redrawn (?) to make it all solid as expected. Example: https://youtu.be/qJI0ezn-91Y Hope this helps to point devs into right direction. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429390] Screenshot taken on Wayland via keyboard shortcuts is not copied to clipboard
https://bugs.kde.org/show_bug.cgi?id=429390 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #19 from Szymon Łągiewka --- Didn't know this bug was already reported (and fixed!) until I've read Nate's blog post. Great to see it finally fixed. Was bothering me ever since I've started using Wayland. This feature is just to good to use other ways :) Backport would be awesome to have! 22.04 seems like it's going to be light years away ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446948] Qt apps scaling breaks in multi-monitor setup with 90 degree rotation
https://bugs.kde.org/show_bug.cgi?id=446948 --- Comment #2 from Szymon Łągiewka --- Sure. The outputs from 2> in the snippet: https://invent.kde.org/-/snippets/2010 I've noticed that scaling doesn't break if I move the window directly to another screen via Move to Screen (from title bar). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446894] Dragging maximised window does not un-maximise
https://bugs.kde.org/show_bug.cgi?id=446894 --- Comment #2 from Szymon Łągiewka --- Yes. I will most likely turn it back on. It's just that I've turned it off because I was trying to get this feature out of the way when using a 90 degree rotated screen with 3-window stack (snapping in quarters is weird in this rotation BTW) and decided to report back my impressions. Never mind the resolution, I still think that it's weird UX to have that toggle off resulting in windows staying maximised even though they're being dragged far away from any screen edge. Or at least the title bar is away, other window edges will obviosly still be touching screen edges since the window is the size of the screen (minus panels). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446948] New: Qt apps scaling breaks in multi-monitor setup with 90 degree rotation
https://bugs.kde.org/show_bug.cgi?id=446948 Bug ID: 446948 Summary: Qt apps scaling breaks in multi-monitor setup with 90 degree rotation Product: kwin Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- Created attachment 144521 --> https://bugs.kde.org/attachment.cgi?id=144521&action=edit Screen arrangement SUMMARY When a scaled display is on the right of another display that is rotated 90 degrees anticlockwise, moving Qt-based apps between them will eventually break scaling. See the attachment for the layout. Happens for both clockwise and anticlockwise. I've first thought that it might have something to do with the display's virtual "chin" being in the way (as is in the illustration), but this is not the case when rotated the other way. STEPS TO REPRODUCE 1. Get two displays 2. Rotate the display on the left 90 degrees (anti)clockwise 3. Scale the display on the right to 200% 4. Open a Qt app on left (100% scale) display 5. Move the app to the right screen 6. Move the app to the left screen 7. Move the app to the right screen 1. Get two displays 2. Rotate the display on the left 90 degrees (anti)clockwise 3. Scale the display on the right to 200% 4. Open a Qt app on right (200% scale) display 5. Move the app to the left screen 6. Move the app to the right screen OBSERVED RESULT After each set of steps the Qt app will not keep the scale (will be blurry). EXPECTED RESULT Flipping windows back and forth between screens for hours doesn't break scaling. Amazing. It's worth mentioning that this does not happen if the scaled display is on the left. I have already filed a bug regarding context menu (https://bugs.kde.org/show_bug.cgi?id=446563) which is subject to the same layout rules, but is reproducible _without_ any rotation. If one of the displays is scaled - things on the right display can break. Tested with scaled display above and below - works. Only when on the right - this happens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2+kde (KDE patches in main repos for some packages) ADDITIONAL INFORMATION This doesn't happen for non-Qt apps - Firefox, Electron (Ozone) and other Gtk apps (I've tested Gnome's Files / Nautilus) work just fine. I've no idea whether this is Qt or KWin issue. The fact that this happens only for certain screen arrangements makes me think this might be KWin as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446563] Context menu flickering/redraw for mixed scale setup (Wayland)
https://bugs.kde.org/show_bug.cgi?id=446563 --- Comment #4 from Szymon Łągiewka --- (In reply to Szymon Łągiewka from comment #3) > If I drag any KDE app Forgot to mention - this doesn't happen to Electron apps with Ozone and Firefox running in native Wayland. They rescale normally. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446563] Context menu flickering/redraw for mixed scale setup (Wayland)
https://bugs.kde.org/show_bug.cgi?id=446563 --- Comment #3 from Szymon Łągiewka --- (In reply to justinkb from comment #2) > I should add, if you rearrange the display layout so that the monitor where > everything is fine is on the right, the bug occurs on the other monitor (the > 200% scaled one). Yup, I can observe the same thing. I've rearranged my desk since submitting this bug and... Now I can say that the context menu is broken on the right display that is scaled 200%. If I virtually rearrange them so that the scaled one is back on the left - the issue is gone. This might be connected with something else I just noticed. If I drag any KDE app (i.e. KScreen KCM, Dolphin etc., so might be Qt thing...) to non-scaled display and back to scaled one - scaling doesn't work. If I flip my displays to be on opposite sides - scaling works when dragging across. I will submit a separate bug report later today. But I get a feeling that these are connected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446894] New: Dragging maximised window does not un-maximise
https://bugs.kde.org/show_bug.cgi?id=446894 Bug ID: 446894 Summary: Dragging maximised window does not un-maximise Product: kwin Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- SUMMARY When `Windows dragged to top edge` is off, grabbing the title bar and moving the window around will not un-maximise it (as in - restore state from before it was maximised). STEPS TO REPRODUCE 1. Go to Screen Edges -> Maximise: Windows dragged to top edge - off 2. Maximise a window 3. Drag the window via its title bar (i.e. few inches below) OBSERVED RESULT Window stays maximised (w/o borders, shadows etc). Since the window is in maxmised state still, dragging it to another display will resize it to the size of that display. So will dragging it back to the original display. EXPECTED RESULT Window should un-maximise (as it does when `Windows dragged to top edge` is on). Moving maximised window from one display to another may as well be expected to keep the window maximised. That would be similar to how one can rearrange fullscreen apps in multi-monitor setup in macOS. However, placing the window on the same screen and still having it maximised is counter-intuitive. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm reporting this as wayland-generic. Might as well be the case in X11 - haven't checked. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445554] Trying to move the Panel crashes the whole desktop
https://bugs.kde.org/show_bug.cgi?id=445554 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446563] New: Context menu flickering/redraw for mixed scale setup (Wayland)
https://bugs.kde.org/show_bug.cgi?id=446563 Bug ID: 446563 Summary: Context menu flickering/redraw for mixed scale setup (Wayland) Product: plasmashell Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bugs-...@lagiewka.pl CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I'm having context menu misbehave in my current mixed DPI setup. When a 4K display (28", display 1, HDMI) has any scale applied and QHD display (27", display 2, DisplayPort) has no scale applied, the context menus of Plasma are not showing everything when opened, and show contents on mouse hover. I've played around with different settings and I was almost convinced that this will happen on a non-scaled display only. But after I tried the reverse (no scale on display 1, scale on display 2) I still got this issue on display 2, but not on display 1. STEPS TO REPRODUCE 1. Scale display 1 to 200% 2. Scale display 2 to 100% (no scaling) 3. Try context menu on display 2 - will misbehave 1. Scale display 1 to 100% (no scaling) 2. Scale display 2 to 100% (no scaling) 3. Try context menu on either display - all will work correctly 1. Scale display 1 to 200% 2. Scale display 2 to 200% (or 150, 175% - any scale other than 100%) 3. Try context menu on either display - all will work correctly 1. Scale display 1 to 100% (no scaling) 2. Scale display 2 to 125% (or 150, etc.) 3. Try context menu on display 2 - will misbehave OBSERVED RESULT Context menu of plasmashell (on widgets, on desktop) flickers and redraws on mouse hover. Demonstration: https://youtu.be/--c3om5X3uE Left screen is scaled 175%, same for 200%. Right is not scaled (100%). Dolphin on right display - context menu is OK. Applets and desktop context menu are being redrawn (?) and mostly incomplete on the right screen. EXPECTED RESULT Context menu behaves as on the left screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux with Plasma 5.23.4 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 GPU: AMD RX 550 / open source drivers ADDITIONAL INFORMATION Turing bless Plasma Wayland session. It's come a long way since I was first trying it in 2017. Still some work to do, but right now I'm easily daily driving it for a week or so. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446431] Do not disturb reason is confusing (screen sharing)
https://bugs.kde.org/show_bug.cgi?id=446431 Szymon Łągiewka changed: What|Removed |Added Summary|Do not disturb reason is|Do not disturb reason is |confusing |confusing (screen sharing) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446431] Do not disturb reason is confusing
https://bugs.kde.org/show_bug.cgi?id=446431 --- Comment #1 from Szymon Łągiewka --- Sorry, trying to send attachment with Enter sends the report prematurely. I just noticed that when screen sharing a window or entire screen in Google Meet in Firefox causes DND to show reason as `xdg-desktop-portal-kde`. This will be confusing to any non-technical user. "What is this portal thing?" I'm not familiar with CreateSession details, but is Firefox registering itself as a portal? Or it's not, but the inhibition is using wrong description? On another note: could "Screen sharing in progress" be mentioned first? As a user I would prefer to have this first and then learn any details - which app, which process etc. (that's form thinking about the target user ;) ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446431] New: Do not disturb reason is confusing
https://bugs.kde.org/show_bug.cgi?id=446431 Bug ID: 446431 Summary: Do not disturb reason is confusing Product: plasmashell Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: bugs-...@lagiewka.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 144175 --> https://bugs.kde.org/attachment.cgi?id=144175&action=edit dnd-from-portal SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[ksmserver] [Bug 381045] Logout greeter gets title bar and breaks background view
https://bugs.kde.org/show_bug.cgi?id=381045 --- Comment #12 from Szymon Łągiewka --- (In reply to Nate Graham from comment #11) > Is anyone still seeing this with Plasma 5.17 or the upcoming 5.18? Quick check (I don't use scaling anymore) on Plasma 5.17.5 and Qt 5.14.1 - everything works great with no artifacts as there were in 5.10. Feel free to resolve or wait for others to report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377308] Notifications from disconnected display appear on primary display
https://bugs.kde.org/show_bug.cgi?id=377308 Szymon Łągiewka changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Szymon Łągiewka --- Setting REPORTED the Janitor asked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377308] Notifications from disconnected display appear on primary display
https://bugs.kde.org/show_bug.cgi?id=377308 --- Comment #2 from Szymon Łągiewka --- (In reply to Germano Massullo from comment #1) > Is this bug still happening on newer Plasma versions? Hey Germano, Currently I'm not using KDE extensively and this hardware setup has also changed. Please mark this as resolved if there are no other cases like this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381040] Spectacle does not capture every desktop
https://bugs.kde.org/show_bug.cgi?id=381040 --- Comment #3 from Szymon Łągiewka --- I have not been testing Plasma on Wayland for quite some time now and I don't have a multi display setup to test anymore. You can resolve the issue if you need to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381044] Title bar does not comply to HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=381044 --- Comment #4 from Szymon Łągiewka --- https://paste.kde.org/pbythjfdw/zwzag5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376987] On screen display included in window layout
https://bugs.kde.org/show_bug.cgi?id=376987 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #3 from Szymon Łągiewka --- What about notifications? For me in 5.10.5 notifications are still visible in desktop grid. I can move grab and move them around and so on. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 381045] Logout greeter gets title bar and breaks background view
https://bugs.kde.org/show_bug.cgi?id=381045 --- Comment #3 from Szymon Łągiewka --- Yup, it's better now. Though still opens quarterly as I've previously described. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard
https://bugs.kde.org/show_bug.cgi?id=380902 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378710] OpenGL visual glitches for task switcher, desktop grid and window tiling.
https://bugs.kde.org/show_bug.cgi?id=378710 Szymon Łągiewka changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Szymon Łągiewka --- Changing EGL to GLX in kwinrc seems to fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378710] OpenGL visual glitches for task switcher, desktop grid and window tiling.
https://bugs.kde.org/show_bug.cgi?id=378710 --- Comment #2 from Szymon Łągiewka --- I made a quick video that shows all of the issues in one take. https://youtu.be/tZqx2mgY1Bc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381044] Title bar does not comply to HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=381044 --- Comment #1 from Szymon Łągiewka --- Same is actually happening for wallpaper. Instead of having sharp image of a 4K photo, I can clearly see that it's not HiDPI at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381045] New: Logout greeter gets title bar and breaks background view
https://bugs.kde.org/show_bug.cgi?id=381045 Bug ID: 381045 Summary: Logout greeter gets title bar and breaks background view Product: kwin Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- Plasma 5.10.1 Qt 5.9.0 DrmOutputs Scale=2 A picture should say more than a thousand words: http://imgur.com/a/Sj0a5. As you probably guessed the background window is not what we see with the greeter. It's basically the lower-left quarter of the screen, stretched to the size of the display when logout greeter is present. If it helps, when Yakuake is retrieved (F12) it shows first quarter (lower-left again) of the window and then the rest three quarters, whish is noticeable. Same behaviour can be noticed for the logout greeter as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381044] New: Title bar does not comply to HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=381044 Bug ID: 381044 Summary: Title bar does not comply to HiDPI scaling Product: kwin Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- With scaling enabled (DrmOutputs, Scale=2) with single or multiple displays, the title bar for any window on the scaled display is not natively sharp. Looks like it was rendered for 1600x900 instead of 3200x1600 that I have. The windows themselves are sharp as expected - Dolphin, systemsettigs etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374663] Panel edit tooltips interfer with active window
https://bugs.kde.org/show_bug.cgi?id=374663 --- Comment #2 from Szymon Łągiewka --- Seems to be resolved for me with Plasma/KWin 5.10. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374651] Tray based app cannot run properly
https://bugs.kde.org/show_bug.cgi?id=374651 --- Comment #3 from Szymon Łągiewka --- Update with Plasma 5.10.1. I stopped using the MEGA sync app on startup, but for the sake of this issue I wanted to test what is happening now. Probably due to changes in scaling and forcing DPI for fonts, I can now see the entire error dialog: http://imgur.com/a/R1hTu. And besides that - nothing changed. I need to kill the app process and start it again in order for it to appear in the tray and be accessible for any interaction. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381042] New: Audio Volume widget does not load into System Tray, OSD is missing
https://bugs.kde.org/show_bug.cgi?id=381042 Bug ID: 381042 Summary: Audio Volume widget does not load into System Tray, OSD is missing Product: plasmashell Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: 1.0 I'm not sure whether it should go to generic-wayland or specificly to System Tray Component, so I'm writing to the former. I've just noticed that a System Tray does not load Audio Volume module for me. When the module is gone, the OSD that should indicate volume changes/mute does not appear on the screen. The change itself also does not seem to happen. With Audio Volume KCM I can not see any changes feedback when manipulating volume rockers. The "Audio Volume (automatic load)" in the system tray settings is of course present and checked. I was able to add the Audio Volume widget to the panel. In result, everything works as expected. Volume changes, mute works, OSD is displayed and the KCM shows changes that are happening. Plasma 5.10.1 Qt 5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381040] New: Spectacle does not capture every desktop
https://bugs.kde.org/show_bug.cgi?id=381040 Bug ID: 381040 Summary: Spectacle does not capture every desktop Product: kwin Version: 5.10.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- Long story short: taking screenshots with Spectacle on Wayland does not always catch all displays. I've noticed it when trying to make screenshots for mixed DPI scaling results (through DrmOutputs). On some occasions all of my screens were captured, but usually the middle screen is being omitted. How it looks like: http://imgur.com/a/q1I1F If it matters - the screens are daisy chained. I believe in both screenshots the middle one was the last in the chain. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374978] Font scaling in plasma/wayland is broken; fonts are far too big
https://bugs.kde.org/show_bug.cgi?id=374978 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #13 from Szymon Łągiewka --- Plasma 5.10.1. Qt 5.9.0 Display 3200x1600, Scale=2 Setting force fonts DPI to 96 helps the entire shell, apps to look like they would in the normal scaling environment with X11. But this workaround is not really a solution, is it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced
https://bugs.kde.org/show_bug.cgi?id=377970 --- Comment #7 from Szymon Łągiewka --- Turns out the notification position is also interrupted by i.e. Yakuake. Effect: http://imgur.com/a/QIbME. If Yakuake was on 100% height, the notification would be in the interrupted upper-left corner position. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374659] Windows on HiDPI scaled display are small on the first run
https://bugs.kde.org/show_bug.cgi?id=374659 --- Comment #8 from Szymon Łągiewka --- Before 5.10 I was using kscreen KCM. With 5.10. I started using DrmOutputs in kwinrc as instructed. The issues are not appearing anymore. You can change the status of the bug to whatever it needs to have. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377970] [Wayland] Notifications are often misplaced
https://bugs.kde.org/show_bug.cgi?id=377970 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #6 from Szymon Łągiewka --- I'm curious how the patch will change what we now. For me it's now: 1. First nofitication shows just like in the attachment. 2. All the rest will pop up in the upper-left corner. Tested with notify-send. What's more important - when I'm sending notifications from Konsole/Yakuake, the focus is stolen in favour of the notification. Is it related or deserves another bug report? What's also interesting is that KRunner seems to behave in a similar manner - instead of being in the middle of the top part of the screen - it's in the upper-left corner. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)
https://bugs.kde.org/show_bug.cgi?id=380526 --- Comment #11 from Szymon Łągiewka --- Oh, and restarting plasmashell does not seem to work for me. Neither with kquit/kstart nor killall and executing plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)
https://bugs.kde.org/show_bug.cgi?id=380526 --- Comment #10 from Szymon Łągiewka --- Ok, so we have some weird issues here. What you have pointed I've applied to two applications VLC and Spotify. For Spotify right now (during lock screen): Next/Previous buttons cause skipping not one but two tracks. Pause/Play works normal. For VLC: Next/Previous buttons work, Play/Pause does nothing. I can't tell if it's doubled. This is particulary interesting, because I think Spotify normally behaves like this: Every event is doubled. Double-skips tracks and pauses-unpauses track instead of pausing. I don't know if it is Spotify's issue or Plasma's, but when I'd recently thought that this is no longer happening - here we go. So in essence, looks like Next/Previous on lock screen behave as they should, but play/pause is doubled? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374665] Logging out is nearly never possible
https://bugs.kde.org/show_bug.cgi?id=374665 --- Comment #15 from Szymon Łągiewka --- I can confirm that logout greeter does not crash on me when trying to logout from Wayland session in 5.10. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378710] OpenGL visual glitches for task switcher, desktop grid and window tiling.
https://bugs.kde.org/show_bug.cgi?id=378710 Szymon Łągiewka changed: What|Removed |Added Version|5.9.4 |5.10.0 --- Comment #1 from Szymon Łągiewka --- Any news on that? With my brief sessions on Wayland I can tell that this bug does not occur there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376726] Can't switch to Global Menu by hitting Alt key.
https://bugs.kde.org/show_bug.cgi?id=376726 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #6 from Szymon Łągiewka --- Should this be fixed already in 5.10? Still happens to me with Plasma 5.10 and Qt 5.8. To be more detailed: I have global menu available in my panels that are made with Latte. But I've chceked this with regular App menu by using right mouse click on desktop -> add panel -> Application Menu Bar. The resulting panel does contain the app menu, but does not react to alt actions, i.e. alt+f in Dolphin for File. Before I've added the bar, I quit Latte and restarted plasmashell with kquit/kstart. This may or may not be related to other problems like https://bugs.kde.org/show_bug.cgi?id=375053. For me enabling app menu breaks i.e. Auto-Type in KeePassXC which is bound to Ctrl+V shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380835] New: Customizable background for Desktop Grid
https://bugs.kde.org/show_bug.cgi?id=380835 Bug ID: 380835 Summary: Customizable background for Desktop Grid Product: kwin Version: 5.10.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- Currently the background for the Desktop Grid is all black, and therefore boring and saddening. It would be super nice to allow some customization of the background - set your own image, color or inherit from screen's wallpaper. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361371] Desktop Grid: invisible windows during drag operations
https://bugs.kde.org/show_bug.cgi?id=361371 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #11 from Szymon Łągiewka --- Reproducible for me with Plasma 5.10/Qt 5.8. >From what I can tell (already said) - does not happen on XRender. Everything is great there. But with OpenGL I've noticed that: 1. For maximized windows - drag is visible. 2. For full screen windows drag is not visible. 3. For windows strechted from side to side - drag is visible. The edges need to be opposite to each other. Top+bottom or left+right. Will not work for windows that touch i.e. left+top edges. 4. For windows not touching any edge - drag is not visible. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 380526] Media playback buttons no longer work after locking and unlocking the screen (Regression in 5.10)
https://bugs.kde.org/show_bug.cgi?id=380526 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl --- Comment #5 from Szymon Łągiewka --- Same for me. Media keys are working before the lock, during the lock but not after unlock. Another lock - keys are available again on lock screen, but still not after unlock. Arch Linux, Plasma 5.10, Qt 5.8. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 377208] "Invert scroll direction" controls "Tap-and-drag lock" setting in Touchpad settings (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=377208 --- Comment #3 from Szymon Łągiewka --- Still happening on Plasma 5.10 (Qt 5.8.0 in my system). -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 377208] "Invert scroll direction" controls "Tap-and-drag lock" setting in Touchpad settings (on Wayland)
https://bugs.kde.org/show_bug.cgi?id=377208 Szymon Łągiewka changed: What|Removed |Added CC||bugs-...@lagiewka.pl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378710] New: OpenGL visual glitches for task switcher, desktop grid and window tiling.
https://bugs.kde.org/show_bug.cgi?id=378710 Bug ID: 378710 Summary: OpenGL visual glitches for task switcher, desktop grid and window tiling. Product: kwin Version: 5.9.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- For some time now (before 5.9.4 at least, update did not change anything) there are some glitches that I (and turns out not only me https://www.reddit.com/r/kde/comments/5zij0p/a_visual_glitch_in_the_task_switcher/) have found inf Task Switcher, Desktop Grid effect and when a window is being dragged for tiling into a specific area. This happens when OpenGL 2.0/3.1 was selected. When I tried XRender (as the reddit entry suggests) and everything works as it used to. That's why I'm submitting the bug against KWin. Screenshots: http://imgur.com/a/udzyD For Task Switcher: Task switching looks like on the screenshots 1 and 3. Expected behaviour is to have background and selection on the switcher visible. For Desktop Grid: The buttons (or at least their space) for adjusting the number of virtual desktops is covered with a corner of a desktop. It can be seen on screenshot number 2. 'Browse' text is from full screen Spotify window. Sometimes there is a top panel with a part of the screen visible (so upper-left corner). For window tiling: When a window is dragged to an edge of the screen (no matter which, top/right/left) the area that is going to be covered with resized window should be painted (i.e. take the left half of the screen, upper-left quarter etc.). This does not happen and the only effect is shown on the last screenshot from the gallery. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377438] New: Resize display visualization for scaled display
https://bugs.kde.org/show_bug.cgi?id=377438 Bug ID: 377438 Summary: Resize display visualization for scaled display Product: KScreen Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: kcm Assignee: se...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- When Plasma on Wayland implementation comes in with per-display DPI, one thing that could be a great addition to KCM is resizing the presentation according to scaling factors that were applied per each display. Example: http://imgur.com/a/ZT8iS The laptop screen is QHD+ and has 13.3" diagonal. The external displays are 27" and have QHD resolution. In real life the externals are much bigger and laptop screen takes about a quarter of each external display. In the visualization the laptop screen overwhelms the externals. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377436] New: Non-integer scaling values are not properly propagated to force fonts DPI setting
https://bugs.kde.org/show_bug.cgi?id=377436 Bug ID: 377436 Summary: Non-integer scaling values are not properly propagated to force fonts DPI setting Product: KScreen Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: se...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- For the entire time that I've been using HiDPI display (not so long, since december) I thought that scaling by factors different than 2 was not working for the whole desktop. Yesterday I discovered that scaling by 1.6-1.9 can be easily achieved, but still does not work out of the box. One just needs to set desired scaling factor in Kscreen kcm and proceed to font settings kcm and use Force fonts DPI to Factor x 96 DPI. Why is it a bug? When scaling by 1.5, the force fonts DPI is automatically set to 144 (1.5 x 96). When scaling by 2, the force fonts DPI is automatically set to 192 (2 x 96). When scaling by anything between 1.6 and 1.9 (I suppose 1.1-1.4 as well), the force fonts DPI setting is not set at all, thus scaling is not complete. The common thing between all of them is the fact, that when 96 is multiplied by this factor we get non integer DPI value (i.e. 163.2), which is probably not accepted by whatever is behind font settings. Tested on X11 session. Reproducible: always. Possible solutions: Take the closest integer to the multiplied value (ceiling or floor) or if not every DPI (even integer) can be accepted (I see that arrow up/down in font settings change the value by 24 which is a quarter of 96 DPI) then the closest possible DPI value should be set. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377308] New: Notifications from disconnected display appear on primary display
https://bugs.kde.org/show_bug.cgi?id=377308 Bug ID: 377308 Summary: Notifications from disconnected display appear on primary display Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: bugs-...@lagiewka.pl CC: plasma-b...@kde.org Target Milestone: 1.0 My problem looks very similar to what was described long time ago here: https://bugs.kde.org/show_bug.cgi?id=259549 Scenario: 1. Given setup: Two external displays with panels on top are placed side by side Below them, in the middle, a primary display with another panel. Upper-left and the primary have system tray with notifications enabled. 2. Disconnect external displays (at once - daisy chained, if that matters). Expected result: All panels from external displays are gone and notifications are produced by the system tray from primary display. Actual result: All panels from external displays are gone BUT notifications are produced by all system trays that have notifications enabled. Only known remedy: kquitapp plasmashell && kstart plasmashell The whole thing can be seen in the gallery: http://imgur.com/a/GOKRn Don't mind the wallpaper, it's still 5.9. I just like it very much ;-) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 374660] Krunner first run accepts only one character
https://bugs.kde.org/show_bug.cgi?id=374660 --- Comment #2 from Szymon Łągiewka --- This does not happen when scaling is OFF (in Wayland session, used to be 2x on HiDPI screen). But according to Martin Gräßlin, scaling is not supported as of yet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374654] Input is being stolen between windows
https://bugs.kde.org/show_bug.cgi?id=374654 --- Comment #2 from Szymon Łągiewka --- With XWayland 1.19 I cannot reproduce the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374647] HiDPI display gets unwanted partial scaling
https://bugs.kde.org/show_bug.cgi?id=374647 --- Comment #2 from Szymon Łągiewka --- I can confirm that forcing font DPI makes unscaled Plasma on HiDPI screen look tiny again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374651] Tray based app cannot run properly
https://bugs.kde.org/show_bug.cgi?id=374651 --- Comment #2 from Szymon Łągiewka --- Error message had an X icon, so I presume it's running XWayland. Today I updated XWayland to 1.19 - same issues. Although without scaling on I can see more inside the windows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374659] Windows on HiDPI scaled display are small on the first run
https://bugs.kde.org/show_bug.cgi?id=374659 --- Comment #6 from Szymon Łągiewka --- Ok, understood. Since scaling is a requirement for my setup, I will try Wayland session again once scaling is supported (ideally for multi-monitor setups). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374659] Windows on HiDPI scaled display are small on the first run
https://bugs.kde.org/show_bug.cgi?id=374659 --- Comment #4 from Szymon Łągiewka --- Scaling is done by a factor of 2. The native resolution is 3200x1800. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374668] New: Plugging USB hub results in switching to SDDM
https://bugs.kde.org/show_bug.cgi?id=374668 Bug ID: 374668 Summary: Plugging USB hub results in switching to SDDM Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- SDDM starts my Wayland session on TTY2. After I HOT plugged an USB hub (from an external display) I saw for a second systemd log and then SDDM. Turned out I'm on TTY1. I switched back to TTY2. My wireless connection was now dropped, but the session seemed to be unchanged. Dmesg output from the connection moment: https://paste.kde.org/pyibd7a89/ucnfio After retrying the hot plug, there was no sddm-greeter segfault, but the switch to TTY1 kept happening. Such events do not happen on X11. Though I did not try starting X11 session on TTY2 when SDDM is on TTY1 and I realize this may not be KWin/Wayland related. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374665] New: Logging out is nearly never possible
https://bugs.kde.org/show_bug.cgi?id=374665 Bug ID: 374665 Summary: Logging out is nearly never possible Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- When I try to log out of Wayland session, it usually does not end with success. After I try select logout from shrank leaving dialog (mentioned briefly in https://bugs.kde.org/show_bug.cgi?id=374659), I am not presented with SDDM but with black screen. At this point only the only things I could do is: - force shutdown - hold power button - change tty with ctrl+alt+fx to be greeted with SDDM - no console access Correct log out happens much less often than the issue mentioned above. I still have not found a plausible reason for this to be happening both ways... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374663] New: Panel edit tooltips interfer with active window
https://bugs.kde.org/show_bug.cgi?id=374663 Bug ID: 374663 Summary: Panel edit tooltips interfer with active window Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- When editing a panel and moving mouse around it - tooltips with widget names show. Tooltips closer to the edge make active window to shrink, leaving exact amount of pixels that the tooltips has in width. On mouse out, the window goes back to it's original form. Demo: https://drive.google.com/drive/folders/0B3ahLC5Mtqw3akRCZFg5cXZ2SHM?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374659] Windows on HiDPI scaled display are small on the first run
https://bugs.kde.org/show_bug.cgi?id=374659 --- Comment #2 from Szymon Łągiewka --- Lock screen takes apx. 1/4 of the screen in the upperleft corner. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374662] New: Titlebar cannot be hidden for Wayland windows
https://bugs.kde.org/show_bug.cgi?id=374662 Bug ID: 374662 Summary: Titlebar cannot be hidden for Wayland windows Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- This may not be a bug, more a question regarding changes in Wayland and the Active Window Control plasmoid. https://store.kde.org/p/998910/ This plasmoid is able to hide titlebar of a windows when it's maximized. This is a wonderful integration for me because I can use my top panel to serve as a titlebar when a window is maximized. 1. With Wayland the tiltlebar is not being hidden, whilst X windows behave the same way. I.e. Spotify gets it's titlebar cutoff when maximized, Dolphin doesn't. 2. Pinning a window does not seem to work when pinning with plasmoid's button. Nothing happens when on first Virtual Desktop. Window is taken to first Virtual Desktop when pinning on other VDs. In this case - should the plasmoid's developer adjust for Wayland or can Kwin adopt X11 features that the plasmoid was using? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374660] New: Krunner first run accepts only one character
https://bugs.kde.org/show_bug.cgi?id=374660 Bug ID: 374660 Summary: Krunner first run accepts only one character Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- When using the krunner for the first time in a session, it only accepts one character. Typing more characters leaves us with only the last one being significant. After something is chosen from krunner output (after only one char...) all next runs perform well - user can type as many characters as needed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374659] Windows on HiDPI scaled display are small on the first run
https://bugs.kde.org/show_bug.cgi?id=374659 --- Comment #1 from Szymon Łągiewka --- And one of the most annoying things is also the leaving dialog. I added appropriate photo to the demo folder. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374659] New: Windows on HiDPI scaled display are small on the first run
https://bugs.kde.org/show_bug.cgi?id=374659 Bug ID: 374659 Summary: Windows on HiDPI scaled display are small on the first run Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- This is somehow related to https://bugs.kde.org/show_bug.cgi?id=369196 I get the same result on the first showing of Yakuake. I was also able to reproduce it with MEGAsync when after starting a fresh instance and opening app window from tray. Possibly related: most windows that I start are shrank. This was tested on i.e. Wayland info, Dolphin, System settings and couple other programs. Demo: https://drive.google.com/drive/folders/0B3ahLC5Mtqw3QktNTVZTc1U5dVE?usp=sharing Also, when I was resizing those pictures in Gwenview, I noticed that the window that opened on `Resize` action was ridiculously small as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374658] New: Windows/panel triggered by shortcut are opening on one virtual desktop
https://bugs.kde.org/show_bug.cgi?id=374658 Bug ID: 374658 Summary: Windows/panel triggered by shortcut are opening on one virtual desktop Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- When being on virtual desktops that are not the first one, triggering krunner with alt+f2, alt+space or by starting typing on an empty desktop and triggering Yakuake with f12 always ends up by them being opened on the first VD. If I'm not mistaken the same happens for Application Dashboard but I don't use it anymore. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374656] New: Top panel covering windows
https://bugs.kde.org/show_bug.cgi?id=374656 Bug ID: 374656 Summary: Top panel covering windows Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- My main (and only) panel is placed on top of the screen. When windows are maximized it looks alright. But sometimes windows that should have been placed right underneath the top panel (as they are in X) are being placed where both the screen and the panel start. The result is the window being covered by the panel in it's first couple of dozens pixels. This applies to e.g. krunner, yakuake. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374654] New: Input is being stolen between windows
https://bugs.kde.org/show_bug.cgi?id=374654 Bug ID: 374654 Summary: Input is being stolen between windows Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- Scenario 1: Open a browser with a form (just like this comment form) Open krunner with alt+f2 or alt+space Type some app you'd like to open Submit your choice with Enter Result: The app opens AND the form receives the enter as well and get's submitted Scenario 2: Open any text or textarea in your browser Switch (with alt+tab) to another window that can be quit with Ctrl+Q (Messenger for Desktop in my case) Quit the app The `q` will go to textarea as well Scenario 3: Try using auto-type with KeePass or KeePassX 2 with Ctrl+V The letter `v` will be the first character to be auto-typed into desired field In each case, I used alt+tab to switch from browser (Vivaldi) to perform actions on different windows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374652] Plasma goes black on compositor settings change
https://bugs.kde.org/show_bug.cgi?id=374652 --- Comment #1 from Szymon Łągiewka --- Scenario: Open compositor settings menu Change animation speed (i.e. to slower) Apply The screen goes black Changes to different tty's are possible, though each outputs SDDM dialog Sorry for sending incomplete message. During the writings I opened krunner, typed compositor and pressed enter. The enter went ALSO to this form and a bug report was sent. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374652] Plasma goes black on compositor settings change
https://bugs.kde.org/show_bug.cgi?id=374652 Szymon Łągiewka changed: What|Removed |Added Summary|Compositor crash on |Plasma goes black on ||compositor settings change -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374652] New: Compositor crash on
https://bugs.kde.org/show_bug.cgi?id=374652 Bug ID: 374652 Summary: Compositor crash on Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- Scenario -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374651] New: Tray based app cannot run properly
https://bugs.kde.org/show_bug.cgi?id=374651 Bug ID: 374651 Summary: Tray based app cannot run properly Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- I use MEGA (also known as MEGAsync, mega.nz) cloud synchronization. The app is set to autostart. On Wayland session the app will always notify about it not being able to find a system tray and that it will not function properly. The program keeps running (/usr/bin/megasync process is alive) but the tray icon is missing. Spawning MEGAsync from krunner opens the app's window but it's aligned all the way to the left whereas it should be opened nearby the tray. My tray is located on the right. The panel is on top edge of the screen. When the process is killed manually, the app can be started with the icon in the tray. It's functional - clicking spawns the app's windows (again on the left, though). Nearly all dialogs given by the application cannot be read and there's nothing I can do with them. It may be related to the screen being HiDPI (3200x1800 with 2x scaling). The dialogs are tiny and nearly no text is visible. I cannot take any actions. This includes: - opening the app's windows selecting Syncs->Add sync->Dialog cannot be seen, - opening a file share link (example from my cloud https://mega.nz/#!ZgQgHDZL!OeKVISti6vfcvBh85Z0rOj1jwi1fP0AZ9Jhx548T9Fc) and using Download with MEGAsync -> dialog is nowhere near being operational, - settings menu Under X - none of those issues happen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 374647] New: HiDPI display gets unwanted partial scaling
https://bugs.kde.org/show_bug.cgi?id=374647 Bug ID: 374647 Summary: HiDPI display gets unwanted partial scaling Product: kwin Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: bugs-...@lagiewka.pl Target Milestone: --- My screen is HiDPI - 3200x1800 on a 13.3" laptop. Scaling times 2 under Wayland look generally the same as under X - it pretty much covers everything. The problem is when scaling is set to 1. Effectively this should mean that nothing will be scaled as it does under X. On my Wayland session - I get partial scaling, which seems to be giving me scaling by the factor even greater than 2. What is scaled (unwanted): Plasma elements such as panels (i.e. drop-down from system tray), krunner Fonts in UI - i.e. system settings or dolphin. It also happens for window title panel text but not the panel itself. In result the text does not fit in the title panel. What is not scaled (wanted): Applications in general, i.e. Vivaldi is not informed about scaling and the UI along with websites are not being scaled. Other software I've opened to see effects: KeePassX 2, Slack, Messenger for Desktop, PhpStorm My fonts settings are varying from 8-10. Anit-aliasing - system settings. Force DPI is unchecked. -- You are receiving this mail because: You are watching all bug changes.
