[frameworks-kio] [Bug 423031] [Wayland] Modifier keys to move (shift), copy (ctrl) and create a link (ctrl+shift) don't work if pressed after I start to drag the file/folder
https://bugs.kde.org/show_bug.cgi?id=423031 Artur Rudenko changed: What|Removed |Added CC||catcool...@gmail.com --- Comment #15 from Artur Rudenko --- It also appears to be a bug not only in dolphin; for example, in Kate, pressing "ctrl" to move cursor faster will only take effect when pressed before you press arrow keys. X11 works fine. Maybe it's a KWin issue? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 --- Comment #13 from Artur Rudenko --- (In reply to Michele Di Vincenzo from comment #12) > Created attachment 154536 [details] > While a video is playing in a browser (tested both Brave and Firefox), the > artifacts disappear > > While playing a video in a web browser, the artifacts disappear. > Pausing the video makes the artifact visible again. > > Operating System: Arch Linux > KDE Plasma Version: 5.26.4 > KDE Frameworks Version: 5.101.0 > Qt Version: 5.15.7 > Kernel Version: 6.0.12-zen1-1-zen (64-bit) > Graphics Platform: Wayland > Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor > Memory: 31.3 GiB of RAM > Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 > Manufacturer: Gigabyte Technology Co., Ltd. > Product Name: X570 AORUS ELITE > System Version: -CF (In reply to Artur Rudenko from comment #0) > SUMMARY > *** > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > *** > There was a glitches when you open a context menu above a surface with blur > effect, and those were fixed in plasma 5.24 for both wayland and xorg, but > after updating to plasma 5.25 they started to appear again but only in > wayland session > > STEPS TO REPRODUCE > 1. Open konsole > 2. Enable blur in konsole > 3. Open a context menu in konsole > > OBSERVED RESULT > Blur effect glitches > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Arch linux > (available in About System) > KDE Plasma Version: 5.25.0 > KDE Frameworks Version: 5.95.0 > Qt Version: 5.15.4 > > ADDITIONAL INFORMATION > AMD gpu. I can't reproduce that on plasma shell blurred menus, also I can't > reproduce it in konsole while recording through obs/pipewire Yeah also, as I mentioned, they disappear while recording, so playing a video/recording a screen makes something constantly redraw thus the glitches disappear -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456238] Active job progress notifications inappropriately block screen locking
https://bugs.kde.org/show_bug.cgi?id=456238 --- Comment #5 from Artur Rudenko --- I also created minimal pygtk inhibit example and when I run it it says "Is currently blocking sleep and screen locking" however the flag that I set there is GTK_APPLICATION_INHIBIT_SUSPEND So the suspend inhibitor is also perceived as screen locking inhibitor, but gtk documentation says that GTK_APPLICATION_INHIBIT_IDLE should block screen locking and not GTK_APPLICATION_INHIBIT_SUSPEND (https://docs.gtk.org/gtk4/flags.ApplicationInhibitFlags.html) I didn't try inhibiting using qt or dbus though, but chromium most likely uses gtk to do this -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456238] Active job progress notifications inappropriately block screen locking
https://bugs.kde.org/show_bug.cgi?id=456238 --- Comment #4 from Artur Rudenko --- Created attachment 151980 --> https://bugs.kde.org/attachment.cgi?id=151980=edit pygtk4 minimal inhibit example (chromium most likely uses gtk to do this) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456238] Active job progress notifications inappropriately block screen locking
https://bugs.kde.org/show_bug.cgi?id=456238 --- Comment #3 from Artur Rudenko --- (In reply to Kai Uwe Broulik from comment #1) > Check whether Chrome actually posts an inhibition. I think Chrome blocks > suspend during downloads, but that shouldn't block the screen locker. I added an attachment. Yes, it blocks sleep, but why would it also block screen locking? I also installed plasma integration extension in chromium if it matters. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456238] Active job progress notifications inappropriately block screen locking
https://bugs.kde.org/show_bug.cgi?id=456238 --- Comment #2 from Artur Rudenko --- Created attachment 151978 --> https://bugs.kde.org/attachment.cgi?id=151978=edit chrome blocking sleep and screen locking (but not screen dimming) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457335] File search is case sensitive
https://bugs.kde.org/show_bug.cgi?id=457335 --- Comment #7 from Artur Rudenko --- (In reply to tagwerk19 from comment #6) > Does this cover all the questions? You've got baloo working again? Yeah, it started to work properly. I think this bug status should be changed to NOTABUG because the problem most likely is that baloo indexing was slow/buggy and not that it was wrong. If I have new questions about baloo, should I ask them in kde matrix channel or here? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457335] File search is case sensitive
https://bugs.kde.org/show_bug.cgi?id=457335 --- Comment #4 from Artur Rudenko --- (In reply to tagwerk19 from comment #3) > (In reply to Artur Rudenko from comment #2) > > This could be that newly created files remain unindexed > > some time after the creation ... > Yes, could be that baloo "got stuck". It relies on "iNotify" alerts to see > when files are created, deleted or changed - and there are times when baloo > misses something. Why does it miss? It's a baloo bug or inotify problem? > > ... Maybe it would be better if dolphin did > > fallback to the classic search when baloo can't find needed files? > I'm not sure how Dolphin would know that baloo has not indexed particular > files. Maybe when iNotify notifies about a file created (or modified), baloo should mark parent folder as un-indexed? > In general though baloo should be quick at noticing new files and changed > file details. It knows "content indexing" is harder work and queues up "full > text" indexing (something you can watch happening with a "balooctl monitor") But in real situation it is not. For example, try to unpack some archive and then search in unpacked folder. Baloo won't find anything and i think in this case dolphin should just use a general search in this folder (while adding it to index queue), but it doesn't, and it ends up in useless search feature -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457335] File search is case sensitive
https://bugs.kde.org/show_bug.cgi?id=457335 --- Comment #2 from Artur Rudenko --- (In reply to tagwerk19 from comment #1) > For me, if I create SomeFileWithUppercase.txt and somefilewithuppercase.txt, > I see both: > > $ baloosearch -i somefilewithuppercase > 140413fc01 /home/test/somefilewithuppercase.txt > 140388fc01 /home/test/SomeFileWithUppercase.txt > > and I see, with balooshow, that the index contains the two files: > > $ balooshow -x somefilewithuppercase.txt > 140413fc01 64513 1311763 somefilewithuppercase.txt > [/home/test/somefilewithuppercase.txt] > Mtime: 1660941653 2022-08-19T22:40:53 > Ctime: 1660941653 2022-08-19T22:40:53 > Cached properties: > Line Count: 1 > > Internal Info > Terms: Mplain Mtext T5 T8 X20-1 hello penguin > File Name Terms: Fsomefilewithuppercase Ftxt > XAttr Terms: > lineCount: 1 > > $ balooshow -x SomeFileWithUppercase.txt > 140388fc01 64513 1311624 SomeFileWithUppercase.txt > [/home/test/SomeFileWithUppercase.txt] > Mtime: 1660941644 2022-08-19T22:40:44 > Ctime: 1660941644 2022-08-19T22:40:44 > Cached properties: > Line Count: 1 > > Internal Info > Terms: Mplain Mtext T5 T8 X20-1 hello penguin > File Name Terms: Fsomefilewithuppercase Ftxt > XAttr Terms: > lineCount: 1 > > The "File Name Terms" for both are held in lower case - baloo squashes terms > down to lower case. > > I did this test on Neon with ext4 filesystem, one that treats > SomeFileWithUppercase.txt and somefilewithuppercase.txt as distinct. > > The question is what might happen with other filesystems; for vfat if you > try to create SomeFileWithUppercase.txt and then somefilewithuppercase.txt, > you are creating just the one file. > > You are on an arch setup? What filesystem are you using? (I'm assuming your > files are on a local disc) Yes, I'm on updated arch setup and it's ext4 on local disc, but now after I reindexed everything, it works now (I searched using dolphin with file search in settings). This could be that newly created files remain unindexed some time after the creation. Maybe it would be better if dolphin did fallback to the classic search when baloo can't find needed files? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 457335] New: File search is case sensitive
https://bugs.kde.org/show_bug.cgi?id=457335 Bug ID: 457335 Summary: File search is case sensitive Product: frameworks-baloo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: catcool...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When searching files, typing lowercase name in search bar doesn't find the appropriate uppercase files STEPS TO REPRODUCE 1. Create SomeFileWithUppercase.txt 2. Create somefilewithuppercase.txt 3. Try to search "somefilewithuppercase" OBSERVED RESULT It finds only the file with lowercase name EXPECTED RESULT It finds both SomeFileWithUppercase.txt and somefilewithuppercase.txt files Operating System: Arch Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.15-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i7-10700F CPU @ 2.90GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 470 Graphics Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z490 GAMING X AX System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457303] New: Drag and drop between xwayland and wayland apps doesn't work
https://bugs.kde.org/show_bug.cgi?id=457303 Bug ID: 457303 Summary: Drag and drop between xwayland and wayland apps doesn't work Product: kwin Version: 5.25.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: catcool...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open chromium (via xwayland) 2. Open telegram (4.x) 3. Try to drag-n-drop some text from chromium to telegram SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.15-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × Intel® Core™ i7-10700F CPU @ 2.90GHz Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 470 Graphics Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z490 GAMING X AX System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456239] New: [Wayland] In plasma, escape and left arrow closes the whole context menu, not sub-context menus
https://bugs.kde.org/show_bug.cgi?id=456239 Bug ID: 456239 Summary: [Wayland] In plasma, escape and left arrow closes the whole context menu, not sub-context menus Product: plasmashell Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: catcool...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open a context menu on plasma desktop 2. Hover some item with submenu, for example, "Icons" 3. Press left arrow or escape OBSERVED RESULT Current submenu is closed EXPECTED RESULT The whole context menu is closed SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456238] New: Active notifications block auto lock
https://bugs.kde.org/show_bug.cgi?id=456238 Bug ID: 456238 Summary: Active notifications block auto lock Product: Powerdevil Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: catcool...@gmail.com CC: m...@ratijas.tk Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When there's an active notification i.e. it indicates some process progress (like downloading in chrome), automatic lockscreen doesn't trigger, only screensaver does STEPS TO REPRODUCE 1. Set both dim screen and automatic lock timeout to 1 minute 2. Start a large file downloading in chromium with plasma integration addon OBSERVED RESULT After 1 minute, screen dimming triggers, but auto locking doesn't EXPECTED RESULT Both auto lock and screen dimming work after 1 minute SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I think this issue also can be randomly caused by regular notifications if those appear and persist while auto locking timeout ends -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456090] New: Panel popups are shown under kickoff (wayland)
https://bugs.kde.org/show_bug.cgi?id=456090 Bug ID: 456090 Summary: Panel popups are shown under kickoff (wayland) Product: plasmashell Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: catcool...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When hovering an icon in panel while kickoff is open, kickoff overlaps popups so they are not visible STEPS TO REPRODUCE 1. Open kickoff 2. Hover an app icon in panel OBSERVED RESULT Popups are not visible EXPECTED RESULT Popups are visible SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Occurs only in wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456088] New: In kickoff, after moving an item, it freezes till clicked (wayland)
https://bugs.kde.org/show_bug.cgi?id=456088 Bug ID: 456088 Summary: In kickoff, after moving an item, it freezes till clicked (wayland) Product: plasmashell Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: catcool...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When moving an item in kickoff is done, it freezes until right or left clicked. In case of left click, it open recently moved item, in case of right click, it opens context menu and kickoff unfreezes. STEPS TO REPRODUCE 1. Open kickoff 2. Move item SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION This bug is wayland-only -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)
https://bugs.kde.org/show_bug.cgi?id=455360 --- Comment #7 from Artur Rudenko --- (In reply to Artur Rudenko from comment #6) > (In reply to Nate Graham from comment #5) > > I can't remember if inhibitions are universal, or an app gets to choose what > > to inhibit. Hopefully the Powerdevil developers can help some more. > > Looks like I didn't understand the problem correctly. Lutris (which has the > problem I described) uses Gtk.Application.inhibit with > GTK_APPLICATION_INHIBIT_SUSPEND and GTK_APPLICATION_INHIBIT_IDLE flags. > GTK_APPLICATION_INHIBIT_IDLE flag should inhibit both dim screen and lock > screen (if I understood correctly from > https://docs.gtk.org/gtk3/flags.ApplicationInhibitFlags.html) but > powerdevil(?) interprets it as "disable lock screen but not dim screen" so > it's probably powerdevil's regression. But it only work not intended when an > app is not in focus. > > It's a bug anyway because it either should ignore inhibitors for minimized > apps or respect them fully anywhere except lock screen. Blocking auto > locking and not screen dimming is confusing. In addition, because of this bug, lutris now can't block screen dimming for games anymore. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)
https://bugs.kde.org/show_bug.cgi?id=455360 --- Comment #6 from Artur Rudenko --- (In reply to Nate Graham from comment #5) > I can't remember if inhibitions are universal, or an app gets to choose what > to inhibit. Hopefully the Powerdevil developers can help some more. Looks like I didn't understand the problem correctly. Lutris (which has the problem I described) uses Gtk.Application.inhibit with GTK_APPLICATION_INHIBIT_SUSPEND and GTK_APPLICATION_INHIBIT_IDLE flags. GTK_APPLICATION_INHIBIT_IDLE flag should inhibit both dim screen and lock screen (if I understood correctly from https://docs.gtk.org/gtk3/flags.ApplicationInhibitFlags.html) but powerdevil(?) interprets it as "disable lock screen but not dim screen" so it's probably powerdevil's regression. But it only work not intended when an app is not in focus. It's a bug anyway because it either should ignore inhibitors for minimized apps or respect them fully anywhere except lock screen. Blocking auto locking and not screen dimming is confusing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455526] New: Blur glitches started to appear in wayland again
https://bugs.kde.org/show_bug.cgi?id=455526 Bug ID: 455526 Summary: Blur glitches started to appear in wayland again Product: kwin Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: catcool...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** There was a glitches when you open a context menu above a surface with blur effect, and those were fixed in plasma 5.24 for both wayland and xorg, but after updating to plasma 5.25 they started to appear again but only in wayland session STEPS TO REPRODUCE 1. Open konsole 2. Enable blur in konsole 3. Open a context menu in konsole OBSERVED RESULT Blur effect glitches SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch linux (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION AMD gpu. I can't reproduce that on plasma shell blurred menus, also I can't reproduce it in konsole while recording through obs/pipewire -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)
https://bugs.kde.org/show_bug.cgi?id=455360 --- Comment #4 from Artur Rudenko --- (In reply to Nate Graham from comment #3) > So yeah, it's doing what it says: blocking sleep and screen locking. > > Are you saying that something different happened in the past? If so, > specifically what? What changed, and when? So it blocks sleep (system sleep or "suspend") and screen locking but not display sleeping? In the past (before plasma 5.24, it seems) I think it wouldn't trigger monitor sleep at all when there's any inhibitor that blocks somethings even with minimized window or locked screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)
https://bugs.kde.org/show_bug.cgi?id=455360 --- Comment #2 from Artur Rudenko --- (In reply to Nate Graham from comment #1) > Open the Battery & Brightness applet in your System Tray; what does it say > about Chromium? "Chromium is currently blocking sleep and screen locking (playing audio)" (when minimized) This bug also occurs when lutris blocks sleep with "running game" message. Also, maybe it's little off topic, but in xorg firefox after minimizing removes it's inhibitor, but for wayland it doesn't. That's weird because wayland also sends minimize event? So it's probably either firefox wayland implementation bug or xwayland bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448273] Kwin doesn't show "App is not responding" i.e. kwin_killer_helper doesn't work (wayland)
https://bugs.kde.org/show_bug.cgi?id=448273 --- Comment #3 from Artur Rudenko --- Looks in wayland it works for xwayland apps -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455360] New: Screen saver activates but auto lock screen doesn't (security issue?)
https://bugs.kde.org/show_bug.cgi?id=455360 Bug ID: 455360 Summary: Screen saver activates but auto lock screen doesn't (security issue?) Product: plasmashell Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: catcool...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After recent plasma's screensaver behavior changes, plasma now doesn't take into account screensaver inhibitors that come from non focused apps. This is a correct behavior, however, while screen dimming works in that case, automatic screen locking doesn't work. Some apps do dim screen inhibiting randomly (for example, steam) and this can lead to unexpected results, as the user may think that if the screen turns off and nothing interferes with it, then the system should be locked as specified in the settings, but because it doesn't trigger screen locking, unwanted persons can access the OS. STEPS TO REPRODUCE 1. Set both screen dimming and auto locking timeout to 1 minute 2. Open some video in a chromium (so it will inhibit screen dimming) 3. Minimize this window OBSERVED RESULT Screensaver works but after 1 minute OS is still unlocked EXPECTED RESULT Both screensaver and automatic screen locking works SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Wayland/Xorg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449218] New: App icons can be moved from icon-only task manager to tray
https://bugs.kde.org/show_bug.cgi?id=449218 Bug ID: 449218 Summary: App icons can be moved from icon-only task manager to tray Product: plasmashell Version: 5.23.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Show Desktop/Minimize All Assignee: plasma-b...@kde.org Reporter: catcool...@gmail.com Target Milestone: 1.0 Created attachment 145975 --> https://bugs.kde.org/attachment.cgi?id=145975=edit Screen recording (xorg) SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** App icons can be moved to tray and after they moved, some phantom spacer appears STEPS TO REPRODUCE 1. Drag and drop icon to tray 2. Try it again but with another app SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.90 KDE Frameworks Version: 5. 90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION See attachment -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448515] No lock/unlock animation
https://bugs.kde.org/show_bug.cgi?id=448515 --- Comment #4 from Artur Rudenko --- (In reply to Vlad Zahorodnii from comment #1) > hmm, can you clarify what you mean by unlock animation? as far as I know, > kwin has never had an effect to animate unlocking of the screen As you can see from attachment, plasma had a fade effect on locking and unlocking. Though I didn't find it in desktop effects settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448515] No lock/unlock animation
https://bugs.kde.org/show_bug.cgi?id=448515 --- Comment #3 from Artur Rudenko --- Created attachment 145974 --> https://bugs.kde.org/attachment.cgi?id=145974=edit arch plasma 5.23.90 unlock screen recording -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448515] No lock/unlock animation
https://bugs.kde.org/show_bug.cgi?id=448515 --- Comment #2 from Artur Rudenko --- Created attachment 145973 --> https://bugs.kde.org/attachment.cgi?id=145973=edit manjaro plasma 5.23.4 screen recording -- You are receiving this mail because: You are watching all bug changes.
