[kwin] [Bug 486263] Overview passes keyboard input to Chromium based apps on Wayland
https://bugs.kde.org/show_bug.cgi?id=486263 TYY331 changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486263] New: Overview passes keyboard input to Chromium based apps on Wayland
https://bugs.kde.org/show_bug.cgi?id=486263 Bug ID: 486263 Summary: Overview passes keyboard input to Chromium based apps on Wayland Classification: Plasma Product: kwin Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- SUMMARY On Wayland, Overview effect passes keyboard input to Chromium based applications like VS Code, Chrome, Brave when they are selected by the effect. This bug is not reproducible on X11 STEPS TO REPRODUCE 1. Open one of the affected applications (Chromium/Electron based) 2. Open the overview effect 3. Type some input that coincides with the application, eg Code (to match VS Code) OBSERVED RESULT The selected window starts to recieve keyboard inputs while they are being typed on the overview search. EXPECTED RESULT Windows never get keyboard input while being selected on the overview effect SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Other Xwayland applications don't seem to be affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471447] Kwin kills applications when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=471447 TYY331 changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471447] Kwin kills applications when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=471447 --- Comment #3 from TYY331 --- (In reply to David Edmundson from comment #1) > That sounds more like kwin crashed and restarted. Please check for crashlogs > of kwin (coredumpctl gbd kwin_wayland) and upload a trace. Nvm, I found the culprit, turns out a 3rd party desktop effect was causing the crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471447] Kwin kills applications when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=471447 --- Comment #2 from TYY331 --- (In reply to David Edmundson from comment #1) I can confirm it's kwin_wayland that crashes > That sounds more like kwin crashed and restarted. Please check for crashlogs > of kwin (coredumpctl gbd kwin_wayland) and upload a trace. Message: Process 14039 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 14039: #0 0x7fb71aa18954 _ZNK7QRegion7isEmptyEv (libQt5Gui.so.5 + 0x418954) #1 0x7fb71aa18ade _ZNK7QRegion12boundingRectEv (libQt5Gui.so.5 + 0x418ade) #2 0x7fb70402718b _ZN4KWin20LightlyShadersEffect14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (kwin4_effect_lightlyshaders.so + 0xb18b) #3 0x7fb71bbfaebe _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x1faebe) #4 0x55b58bceb0e6 n/a (kwin_wayland + 0xa50e6) #5 0x7fb71bbfaebe _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x1faebe) #6 0x55b58bd070e9 n/a (kwin_wayland + 0xc10e9) #7 0x7fb71bbfaebe _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x1faebe) #8 0x7fb71bc81a53 _ZN4KWin14WorkspaceScene24preparePaintSimpleScreenEv (libkwin.so.5 + 0x281a53) #9 0x7fb71bc8460e _ZN4KWin14WorkspaceScene8prePaintEPNS_13SceneDelegateE (libkwin.so.5 + 0x28460e) #10 0x7fb71bbbd844 _ZN4KWin10Compositor12prePaintPassEPNS_11RenderLayerE (libkwin.so.5 + 0x1bd844) #11 0x7fb71bbc1ea0 _ZN4KWin10Compositor9compositeEPNS_10RenderLoopE (libkwin.so.5 + 0x1c1ea0) #12 0x7fb71a2d06a7 n/a (libQt5Core.so.5 + 0x2d06a7) #13 0x7fb71bb716f7 _ZN4KWin10RenderLoop14frameRequestedEPS0_ (libkwin.so.5 + 0x1716f7) #14 0x7fb71bbc85a8 _ZN4KWin17RenderLoopPrivate8dispatchEv (libkwin.so.5 + 0x1c85a8) #15 0x7fb71a2d06a7 n/a (libQt5Core.so.5 + 0x2d06a7) #16 0x7fb71a2d21df _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2d21df) #17 0x7fb71a2c315e _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c315e) #18 0x7fb71997893f _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x17893f) #19 0x7fb71a29b778 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29b778) #20 0x7fb71a2e9e2b _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2e9e2b) #21 0x7fb71a2ea301 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ea301) #22 0x55b58bd7a502 n/a (kwin_wayland + 0x134502) #23 0x7fb71a29a484 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29a484) #24 0x7fb71a29b923 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x29b923) #25 0x55b58bc962fb n/a (kwin_wayland + 0x502fb) #26 0x7fb719239850 n/a (libc.so.6 + 0x23850) #27 0x7fb71923990a __libc_start_main (libc.so.6 + 0x2390a) #28 0x55b58bc97ed5 n/a (kwin_wayland + 0x51ed5) Stack trace of thread 14064: #0 0x7fb719299f0e n/a (libc.so.6 + 0x83f0e) #1 0x7fb71929c7a0 pthread_cond_wait (libc.so.6 + 0x867a0) #2 0x7fb7112c7a4c n/a (radeonsi_dri.so + 0xc7a4c) #3 0x7fb71131495c n/a (radeonsi_dri.so + 0x11495c) #4 0x7fb71929d44b n/a (libc.so.6 + 0x8744b) #5 0x7fb719320e40 n/a (libc.so.6 + 0x10ae40) Stack trace of thread 14065: #0 0x7fb719299f0e n/a (libc.so.6 + 0x83f0e) #1 0x7fb71929c7a0 pthread_cond_wait (libc.so.6 + 0x867a0) #2 0x7fb7112c7a4c n/a (radeonsi_dri.so + 0xc7a4c) #3 0x7fb71131495c n/a (radeonsi_dri.so + 0x11495c) #4 0x7fb71929d44b n/a (libc.so.6 + 0x8744b) #5 0x7fb719320e40 n/a (libc.so.6 + 0x10ae40) Stack trace of thread 14069: #0 0x7fb719299f0e n/a (libc.so.6 + 0x83f0e) #1 0x7fb71929c7a0 pthread_cond_wait (libc.so.6 + 0x867a0) #2 0x7fb7112c7a4c n/a (radeonsi_dri.so + 0xc7a4c) #3 0x7fb71131495c n/a (radeonsi_dri.so + 0x11495c) #4 0x7fb71929d44b n/a (libc.so.6 + 0
[kwin] [Bug 471447] New: Kwin kills applications when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=471447 Bug ID: 471447 Summary: Kwin kills applications when monitor is turned off Classification: Plasma Product: kwin Version: 5.27.6 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- SUMMARY When using Wayland, all applications get killed when the computer screen is disconnected or turned off STEPS TO REPRODUCE 1. Use Wayland 2. Open some apps 3. Unplug the monitor or turn it off OBSERVED RESULT Both wayland and xwayland applications get killed. EXPECTED RESULT Applications should remain opened SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I'm running an AMD 6600 XT GPU -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465528] Windows that get activated by Alt+Tab and Alt+` get lowered when only one window per app exists
https://bugs.kde.org/show_bug.cgi?id=465528 --- Comment #1 from TYY331 --- I've discovered that this bug might be related to the effects, since disabling the option to show the selected window in the task switcher settings fixed the issues -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465528] New: Windows that get activated by Alt+Tab and Alt+` get lowered when only one window per app exists
https://bugs.kde.org/show_bug.cgi?id=465528 Bug ID: 465528 Summary: Windows that get activated by Alt+Tab and Alt+` get lowered when only one window per app exists Classification: Plasma Product: kwin Version: 5.26.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- Using Alt+Tab to change applications (by setting only one window per application) and using Alt+` to switch between windows of the same application (like what Gnome does) bugs when there is only one window of some application. STEPS TO REPRODUCE 1. Go to settings and task switcher behavior, enable one window per application, bind the current application switcher shortcut to Alt+` 2. Open two application, for example Dolphin and Konsole, while for example Dolphin is the active window, hit Alt+Tab (so that konsole gets selected), then without releasing the Alt key, hit the ` key to cycle, since Konsole has only one window opened, only one result is shown, then release the keys to activate the Konsole window OBSERVED RESULT Konsole window gets activated but it's lowered, meaning all other applications are on top, needing to Alt+Tab again to correctly raise the windows. EXPECTED RESULT Konsole window gets activated and raised, note that this bug only happens if the application has one window, if there are multiple windows of the same application the task switcher works as expected SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.5 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465202] New: Assign a keyboard shortcut to system tray item doesn't work
https://bugs.kde.org/show_bug.cgi?id=465202 Bug ID: 465202 Summary: Assign a keyboard shortcut to system tray item doesn't work Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: sebastian.p...@gmail.com CC: mate...@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 *** STEPS TO REPRODUCE 1. Set a default plasma panel with a system tray 2. Open System Tray settings 3. Assign a keyboard shotcut to an applet, for example Meta+u to toggle the media applet OBSERVED RESULT The keyboard shortcut appears to be assigned but nothing really gets changed, reopening the settings shows no keyboard shortcut has been set and pressing said shortcut does nothing. EXPECTED RESULT Keyboard shortcuts are correctly assigned to system tray applets SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 465201] New: Breeze menu headers use incorrect font size
https://bugs.kde.org/show_bug.cgi?id=465201 Bug ID: 465201 Summary: Breeze menu headers use incorrect font size Classification: Plasma Product: Breeze Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: sebastian.p...@gmail.com CC: noaha...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 155903 --> https://bugs.kde.org/attachment.cgi?id=155903=edit Menu headers with incorrect font size SUMMARY When using the default Breeze application style, menus that display headers do so with an incorrect font size. This problem doesn't occur with Kvantum or Lightly application styles. STEPS TO REPRODUCE 1. Use default Breeze application style 2. Open an application, for example Dolphin 3. Right click on a headerbar icon OBSERVED RESULT The headers are displayed with a wrong font size EXPECTED RESULT Header font respects the system font size SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451372] Overview has an input grab glitch
https://bugs.kde.org/show_bug.cgi?id=451372 TYY331 changed: What|Removed |Added CC||sebastian.p...@gmail.com --- Comment #1 from TYY331 --- Are you using Latte Dock? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450716] New: Overview gets stuck when selecting power options on Wayland
https://bugs.kde.org/show_bug.cgi?id=450716 Bug ID: 450716 Summary: Overview gets stuck when selecting power options on Wayland Product: kwin Version: 5.24.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- SUMMARY When using Wayland, using the Overview effect to search and activate a power option (logout, shutdown, restart) the system gets stuck for around 10 seconds and then it works as expected STEPS TO REPRODUCE 1. Activate overview 2. Search for a power option, for example restart 3. hit enter OBSERVED RESULT The system becomes completelty frozen for ~10 seconds, then it continues as normal. EXPECTED RESULT The system doesn't freeze for a time period when using power options from the overview effect SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This freeze doesn't happen on X11, it only happens on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450040] Clipboard manager can't navigate item list with keyboard after focusing the search input
https://bugs.kde.org/show_bug.cgi?id=450040 --- Comment #8 from TYY331 --- (In reply to Nate Graham from comment #7) > Let's make sure we're talking about the same thing here. > > What the up and down arrow keys are supposed to do is move the selection > effect between items in the list view. I gather this is working, then? If > so, what *exactly* are you trying to do that's not working? > > In your example, you would use the up and down arrow keys to select an item > from the filtered list, then you would use the return or enter key to move > it to the top so that it will be pasted the next time you Ctrl+V to paste > text. Yes, they are supposed to do just that, in fact that's how it works in previous versions of Plasma -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450040] Clipboard manager can't navigate item list with keyboard after focusing the search input
https://bugs.kde.org/show_bug.cgi?id=450040 --- Comment #6 from TYY331 --- (In reply to Nate Graham from comment #5) > (In reply to TYY331 from comment #4) > > 1. The searchbox can be focused by typing or clicking, then using the arrow > > keys moves the list view. > Wait, I'm confused now. I thought the bug you were experiencing was that > using the arrow keys did *not* move the list view after you focused the > search box. It moves the list view, that's the issue since it's supposed to select and move the list items, not the list view, that results in not being able to keyboard select anything from the clipboard history. for example suppose you have 2 entries that have the word "def" in them, you activate the clipboard widget, type "def" on the keyboard, then the list filters the 2 items, then if you want to select one of the two elements you should use the up/down arrow key to actually select the item you want, right know the up/down key just move the view but don't interact with the items. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450040] Clipboard manager can't navigate item list with keyboard after focusing the search input
https://bugs.kde.org/show_bug.cgi?id=450040 --- Comment #4 from TYY331 --- (In reply to Nate Graham from comment #3) > OK, some more questions: > 1. Are you focusing the search box by clicking on it? > 2. Are you using any non-default focus stealing settings? > 3. Are you using a mouse or a touchpad, or a more exotic input device such > as a stylus or your finger on a touchscreen? > 4. Are you using the standard Breeze Plasma theme, or another one? If > another one, does it still happen with the Breeze Plasma theme? 1. The searchbox can be focused by typing or clicking, then using the arrow keys moves the list view. 2. I'm using the default focus setting 3. Mouse. 4. Standard. I even tried to use a live USB with KDE Neon to test the bug and it was fully reproducible. Maybe it's because of my hardware, I'm using an Optimus laptop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450040] Clipboard manager can't navigate item list with keyboard after focusing the search input
https://bugs.kde.org/show_bug.cgi?id=450040 TYY331 changed: What|Removed |Added Version|5.24.0 |5.24.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450040] Clipboard manager can't navigate item list with keyboard after focusing the search input
https://bugs.kde.org/show_bug.cgi?id=450040 --- Comment #2 from TYY331 --- (In reply to Nate Graham from comment #1) > Works for me on Wayland. Are you on X11? If so can you try on Wayland? I can reproduce it on both X11 and Wayland, I've tried creating a new user account and the problem still persists. Plasma 5.24.1, KDE Frameworks 5.91, Qt 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450040] New: Clipboard manager can't navigate item list with keyboard after focusing the search input
https://bugs.kde.org/show_bug.cgi?id=450040 Bug ID: 450040 Summary: Clipboard manager can't navigate item list with keyboard after focusing the search input Product: plasmashell Version: 5.24.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Open Clipboard manager widget 2. Focus the search box 3. Use Keyboard up/down arrow to select items from the list OBSERVED RESULT No items are selected and instead the list view is moved with the keyboard EXPECTED RESULT Keyboard up/down arrow keys select and move throughout the clipboard list. 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.
[dolphin] [Bug 440013] Dolhin can't auto update folder view when more than 1 tab is restored
https://bugs.kde.org/show_bug.cgi?id=440013 --- Comment #2 from TYY331 --- (In reply to Patrick Silva from comment #1) > possibly duplicate if bug 387663 I don't really think it's a duplicate since I can fully reproduce the bug and the issues pointed at on that bug report seems really hard to reproduce. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440013] New: Dolhin can't auto update folder view when more than 1 tab is restored
https://bugs.kde.org/show_bug.cgi?id=440013 Bug ID: 440013 Summary: Dolhin can't auto update folder view when more than 1 tab is restored Product: dolphin Version: 21.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: sebastian.p...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If I use the standard Dolphin settings, where it remembers the previous state on opening, and that previous state happens to have more than one tab opened, Dolphin is unable to update the folder contents on real time (for example creating a file with a text editor on that folder) relying on pressing F5 to update it's content (pressing F5 before I make changes fixes the issue, seems like this "unfreezes" the view). This bug doesn't happen if the remember state option is disabled or the restored state only has one tab opened. STEPS TO REPRODUCE 1. Use Dolphin default settings for state restore 2. Open more than one tab 3. Close and reopen Dolphin 4. Use a text editor to create a file on the same folder showed by Dolphin on the active tab OBSERVED RESULT The folder contents are not updated, the user needs to hit F5 on Dolphin to trigger an update to show the new folder contents, this bug is 100% reproducible. EXPECTED RESULT Folder contents should auto update when changes are made to said folder. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE with 5.10 Kernel KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 428910] New: Window focus flicker when moving thought the menu items in titlebar menu button
https://bugs.kde.org/show_bug.cgi?id=428910 Bug ID: 428910 Summary: Window focus flicker when moving thought the menu items in titlebar menu button Product: kded-appmenu Version: 5.20.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: menu popup Assignee: plasma-b...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- SUMMARY When activating and moving thorough the app menu items in the titlebar button the main window flickers in and out of focus, this is especially noticeable on Kvantum themes that have different colors for unfocused windows, also the new Breeze Theme (5.21) is also noticeable. STEPS TO REPRODUCE 1. Open an application that supports app menu, like Dolphin. 2. Open the app menu button on the title bar and move through the items OBSERVED RESULT Main window quickly loose and gains focus when the sub menus are openend and closed. EXPECTED RESULT The window should remain with a consistent focus during app menu traversal SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75 Qt Version: 5.15 ADDITIONAL INFORMATION Using an Intel GPU, haven't tested on other hardware. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417771] No way to configure primary button slider wrap in GTK applications
https://bugs.kde.org/show_bug.cgi?id=417771 TYY331 changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from TYY331 --- (In reply to Mikhail Zolotukhin from comment #1) > Do you have "Clicking in scrollbar track" in Workspace Behavior > General > Behavior? If you have, does the change of value changes the config line in > ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini called > "gtk-primary-button-warps-slider"? Yes it's working now, after changing the setting Breeze and GTK settings are now synced again and working as expected -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417771] New: No way to configure primary button slider wrap in GTK applications
https://bugs.kde.org/show_bug.cgi?id=417771 Bug ID: 417771 Summary: No way to configure primary button slider wrap in GTK applications Product: systemsettings Version: 5.18.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_style Assignee: plasma-b...@kde.org Reporter: sebastian.p...@gmail.com CC: zom...@protonmail.com Target Milestone: --- SUMMARY There is no way to enable the gtk-primary-button-warps-slider configuration option for both GTK2 and GTK3 applications, this leads to inconsistent behavior in QT and GTK applications, in Plasma version 5.17 and prior you can set this setting, now with the recent changes introduced in Plasma 5.18 the option is missing. STEPS TO REPRODUCE 1. Open System Settings 2. Go to Application Style 3. Try to configure how sliders work for both GTK2 and GTK3 application OBSERVED RESULT Missing configuration option EXPECTED RESULT gtk-primary-button-warps-slider should be configurable or at least inherit the current style's option (as with the theme) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399680] Graphical glitch/corruption in certain menus when transparency effect is enabled
https://bugs.kde.org/show_bug.cgi?id=399680 --- Comment #22 from TYY331 --- After some testing I've noticed that using the translucency desktop effect to make context menus translucent instead of breeze's specific effect doesn't produce the bug, the bad thing is it's coded in JS and I don't think it can interop with KDE's blur -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 397215] Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 --- Comment #15 from TYY331 --- I have finally found a workaround, if you enable the FPS counter effect the bug is gone while the effect is active. Btw if you want to trigger the bug in the first place you have to trigger a GPU workload, this is easy to do with a GPU benchmark tool, I use Unigine heaven for testing, once the benchmark is running, open any window and move it around, the bug is triggered every time. Having the FPS counter effect enabled prevent the glitch from appearing. I'm using the modesetting driver, i haven't tested it with the Intel driver yet. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 397215] Visual bug around the maximize/unmaximize button
https://bugs.kde.org/show_bug.cgi?id=397215 --- Comment #13 from TYY331 --- Tried uxa with the Intel driver (using both DRI 2 and 3), problem persists on a HD 4400 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 411977] New: Graphical glitch on Breeze window buttons when GPU is stressed
https://bugs.kde.org/show_bug.cgi?id=411977 Bug ID: 411977 Summary: Graphical glitch on Breeze window buttons when GPU is stressed Product: Breeze Version: 5.16.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: window decoration Assignee: unassigned-b...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- Created attachment 122683 --> https://bugs.kde.org/attachment.cgi?id=122683=edit Graphical glitches SUMMARY Breeze Window buttons present graphical glitches when hovered making certain parts translucent, this glitch happens when the GPU (Intel HD 4400 in my case) is stressed in some way like playing fullHD video or another GPU intensive task STEPS TO REPRODUCE 1. stress the GPU in some way (to cause FPS drops on Kwin) 2. hover the title bar buttons OBSERVED RESULT Graphical glitches are noticed around the window buttons EXPECTED RESULT Breeze buttons should render correctly upon hover SOFTWARE/OS VERSIONS Linux/KDE Plasma: 4.19 (Manjaro), also tested on KDE Neon live USB (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.61 Qt Version: 5.13.1 ADDITIONAL INFORMATION This glitch also happens in QT 5.12 and older version of plasma and frameworks, It might be affecting only Intel GPUs but I can't test because I don't have newer/older intel GPUs and Nvidia/AMD GPUs. WORKAROUNDS TESTED Tried using the Intel driver in SNA/UXA and DRI2/DRI3 settings, tearfree ON/OFF to no avail Tried using the modesetting driver, same results This glitch also happens with window decorations fork like SierraBreeze and SierraBreezeEnhanced Aurorae window decorations are unaffected by this bug -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 410664] File dialog doesn't save preview setting
https://bugs.kde.org/show_bug.cgi?id=410664 TYY331 changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 410664] File dialog doesn't save preview setting
https://bugs.kde.org/show_bug.cgi?id=410664 --- Comment #1 from TYY331 --- i managed to fix it, turns out kdeglobals's file dialog section was corrupted, I recreated the file and checked that it worked, it probably was a legacy option that messed up the parsing, anyhow next are the two version of the section, if someone stumbles upon this bug you have to delete the section and it will be recreated automatically with a correct configuration. produces bug [KFileDialog Settings] Allow Expansion=true Automatically select filename extension=true Breadcrumb Navigation=true Decoration position=2 LocationCombo Completionmode=5 PathCombo Completionmode=5 Preview Width=235 Show Bookmarks=false Show Full Path=false Show Inline Previews=false Show Preview=false Show Speedbar=true Show hidden files=false Sort by=Date Sort directories first=true Sort reversed=true Speedbar Width=156 View Style=Simple listViewIconSize=72 correct configuration [KFileDialog Settings] Allow Expansion=false Automatically select filename extension=true Breadcrumb Navigation=true Decoration position=2 LocationCombo Completionmode=5 PathCombo Completionmode=5 Show Bookmarks=false Show Full Path=false Show Inline Previews=true Show Preview=false Show Speedbar=true Show hidden files=false Sort by=Date Sort directories first=true Sort reversed=true Speedbar Width=152 View Style=Simple -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 410664] New: File dialog doesn't save preview setting
https://bugs.kde.org/show_bug.cgi?id=410664 Bug ID: 410664 Summary: File dialog doesn't save preview setting Product: frameworks-kio Version: 5.60.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: sebastian.p...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY activating previews in the file dialog isn't remembered across instances, even setting previews to true in kdeglobals file gets rewritten when the file dialog is opened again STEPS TO REPRODUCE 1. open a file dialog instance 2. activate previews 3. close the file dialog and open another one OBSERVED RESULT preview settings is always set to false regardless of user configuration EXPECTED RESULT preview settings are remembered across instances SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60 Qt Version: 5.13.0 ADDITIONAL INFORMATION setting icon/detail/compact view works setting bookmarks works setting icon size works setting preview panel works setting sort order works -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388378] Image corruption in Magnifier utility
https://bugs.kde.org/show_bug.cgi?id=388378 --- Comment #6 from TYY331 --- (In reply to Vlad Zagorodniy from comment #5) > @TYY331 > @ah > Can you still reproduce the bug? If so, can you please give more information > how to reproduce it? I can't reproduce the bug anymore, i'm using an Nvidia setup so I guess it's good on other GPUs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388378] Image corruption in Magnifier utility
https://bugs.kde.org/show_bug.cgi?id=388378 TYY331 changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398687] Latte Dock crashes on Plasma 5.14 beta (5.13.90)
https://bugs.kde.org/show_bug.cgi?id=398687 TYY331 changed: What|Removed |Added Resolution|DOWNSTREAM |FIXED -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398687] Latte Dock crashes on Plasma 5.14 beta (5.13.90)
https://bugs.kde.org/show_bug.cgi?id=398687 --- Comment #10 from TYY331 --- After a recent update in the dev stable channel I can confirm Latte Dock is working again, no crashes or problems so far -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398687] Latte Dock crashes on Plasma 5.14 beta (5.13.90)
https://bugs.kde.org/show_bug.cgi?id=398687 --- Comment #4 from TYY331 --- (In reply to Michail Vourlakos from comment #3) > (In reply to TYY331 from comment #2) > > (In reply to Michail Vourlakos from comment #1) > > > are you using the pre-built package of KDE Neon? > > > > Yes (0.8.0+p18.04+git20180905.0023-0), I'll try the master branch if that > > helps > > there is a chance that Latte needs to be rebuilt with new plasma but I will > now for sure in a few hours I've build the master branch of Latte dock, the problem persists, it shows the same error as with the prepackaged version -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398687] Latte Dock crashes on Plasma 5.14 beta (5.13.90)
https://bugs.kde.org/show_bug.cgi?id=398687 --- Comment #2 from TYY331 --- (In reply to Michail Vourlakos from comment #1) > are you using the pre-built package of KDE Neon? Yes (0.8.0+p18.04+git20180905.0023-0), I'll try the master branch if that helps -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398687] New: Latte Dock crashes on Plasma 5.14 beta (5.13.90)
https://bugs.kde.org/show_bug.cgi?id=398687 Bug ID: 398687 Summary: Latte Dock crashes on Plasma 5.14 beta (5.13.90) Product: latte-dock Version: 0.8.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: sebastian.p...@gmail.com Target Milestone: --- Trying to start Latte dock produces the following error message KCrash: Attempting to start /usr/bin/latte-dock directly KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = latte-dock path = /usr/bin pid = 19362 KCrash: Arguments: /usr/bin/latte-dock KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi directly "¡Una instancia esta actualmente en ejecución!, use «--replace» para reiniciar Latte" [1] + 19362 suspended (signal) latte-dock I've tried on a clean user session and the problem persists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395262] New: Transparency/blur is corrupted on context menu of desktop files
https://bugs.kde.org/show_bug.cgi?id=395262 Bug ID: 395262 Summary: Transparency/blur is corrupted on context menu of desktop files Product: plasmashell Version: 5.13.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: sebastian.p...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 113220 --> https://bugs.kde.org/attachment.cgi?id=113220=edit Render corruption Using breeze widget style with transparency/blur enabled produces strange colors in the context menu of desktop files, contextual menu of the desktop (if you have it enabled) renders correctly, panel's widgets that use the effect and contextual menus inside applications like dolphin all render correctly. Steps to reproduce: Set the desktop layout to enable files on desktop Create a file in the desktop right click on it to show the menu. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 394580] Wrong icon size on network manager applet
https://bugs.kde.org/show_bug.cgi?id=394580 --- Comment #10 from TYY331 --- I think what did the trick was change the name of /home/sebastian/.config/plasmashellrc, log out, log in (now the icons should be the correct size) then change back the name of the config file to get back the plasma layout, log out and in again, see if the problem persist. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394871] New: plasmashell fails to start due to error libactivityswitcherextensionplugin.so library
https://bugs.kde.org/show_bug.cgi?id=394871 Bug ID: 394871 Summary: plasmashell fails to start due to error libactivityswitcherextensionplugin.so library Product: plasmashell Version: 5.12.90 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Activity Switcher Assignee: ivan.cu...@kde.org Reporter: sebastian.p...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 In a recent update the desktop fails to start. Plasmashell can't initialize correctly due to an error in libactivityswitcherextensionplugin.so: /usr/bin/plasmashell: symbol lookup error: /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/activityswitcher/libactivityswitcherextensionplugin.so: undefined symbol: _ZN11KActivities15ActivitiesModelC1ERK7QVectorINS_4Info5StateEEP7QObject Workaround: move the file so plasmashell doesn't find it, the desktop is able to start but activities, desktop wallpaper and icons are disabled, but the panels and widgets work. in a TTY type: sudo mv /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/activityswitcher/libactivityswitcherextensionplugin.so /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/activityswitcher/libactivityswitcherextensionplugin.so.bak The error appeared in a recent plasma-desktop update 4:5.12.5+p16.04+git20180530.0845-0 -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 391172] Misplaced menus when appmenu is on bottom
https://bugs.kde.org/show_bug.cgi?id=391172 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 391172] Misplaced menus when appmenu is on bottom
https://bugs.kde.org/show_bug.cgi?id=391172 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||sebastian.p...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from TYY331 <sebastian.p...@gmail.com> --- *** This bug has been marked as a duplicate of bug 391815 *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 391815] menu cutoff
https://bugs.kde.org/show_bug.cgi?id=391815 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added CC||giuseppe.lovare...@gmail.co ||m --- Comment #3 from TYY331 <sebastian.p...@gmail.com> --- *** Bug 391172 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 391815] menu cutoff
https://bugs.kde.org/show_bug.cgi?id=391815 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added CC||sebastian.p...@gmail.com --- Comment #2 from TYY331 <sebastian.p...@gmail.com> --- The menus are displayed correctly if you go to another entry and then back to the original, it's the first time they are displayed that doesn't respect screen space. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 394690] New: Appmenu crash in title bar button mode
https://bugs.kde.org/show_bug.cgi?id=394690 Bug ID: 394690 Summary: Appmenu crash in title bar button mode Product: kded-appmenu Version: 5.12.90 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: menu popup Assignee: plasma-b...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- Under certain workloads the appmenu service crashed in certain applications. Steps to reproduce. Activate the title bar menu button. Open Krita (4.0.3), open an image, inmediately after open and cycle trough the appmenu entries, there is a delay and then the button disappears for every application until plasmashell is restarted. This crash doesn't happen when the global menu applet is used instead of the title bar button. The plasmashell error generated at the time of the crash is: Service "org.kde.StatusNotifierWatcher" status change, old owner: ":1.3" new: "" "org.kde.StatusNotifierWatcher" disappeared -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 394580] Wrong icon size on network manager applet
https://bugs.kde.org/show_bug.cgi?id=394580 --- Comment #5 from TYY331 <sebastian.p...@gmail.com> --- > thanks for response my ask. Another question. This cache files will be > regenerated after delete them? Every cache file by definition is regenerated if not found, Qt isn't the exception. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 394580] Wrong icon size on network manager applet
https://bugs.kde.org/show_bug.cgi?id=394580 --- Comment #3 from TYY331 <sebastian.p...@gmail.com> --- I can't reproduce the issue, all I did was to delete the cache files and folders associated with KDE in the ~.cache folder for example icon-cache.kcache but I really don't know what file did the trick. These kinds of problems are frequent when have big Plasma updates (5.11->5.12->5.13) Maybe it would be sensible to have these cache files removed when a plasma update is installed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394586] New: Missing options in system settings
https://bugs.kde.org/show_bug.cgi?id=394586
Bug ID: 394586
Summary: Missing options in system settings
Product: systemsettings
Version: 5.12.90
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: kcm_lookandfeel
Assignee: plasma-b...@kde.org
Reporter: sebastian.p...@gmail.com
Target Milestone: ---
System settings is unable to display Look and Feel, Desktop theme, Cursor theme
and Welcome screen due to missing files, this is the error output producen when
opeing any on the configuration pages:
kcmshell5 kcm_lookandfeel
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
"file:///usr/share/kpackage/kcms/kcm_lookandfeel/contents/ui/main.qml"
"Error loading QML file.\n23: module \"org.kde.kirigami\" version 2.4 is not
installed\n"
It says kirigami 2.4 isn't installed but both qml-module-org-kde-kirigami and
qml-module-org-kde-kirigami2 are installed and updated (KDE dev stable update
channel)
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 394580] Wrong icon size on network manager applet
https://bugs.kde.org/show_bug.cgi?id=394580 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from TYY331 <sebastian.p...@gmail.com> --- It was a cache corruption. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 394580] New: Wrong icon size on network manager applet
https://bugs.kde.org/show_bug.cgi?id=394580 Bug ID: 394580 Summary: Wrong icon size on network manager applet Product: plasma-nm Version: 5.12.90 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: sebastian.p...@gmail.com Target Milestone: --- Created attachment 112821 --> https://bugs.kde.org/attachment.cgi?id=112821=edit Wrong icon size in network manager applet The network manager applet displays wrong sized icons causing missalignment and difficulties to select a network, see attached screenshot. This behavior is present regardless of the theme used by plasma (Breeze,Arc-Dark, etc) and icon theme used. This bug just appeared in the dev/stable branch of KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389318] menubar section in settings has been disappeared
https://bugs.kde.org/show_bug.cgi?id=389318 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added Version|5.11.95 |5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389318] menubar section in settings has been disappeared
https://bugs.kde.org/show_bug.cgi?id=389318 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added Platform|openSUSE RPMs |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394137] New: Appmenu configuration missing from sytem settings
https://bugs.kde.org/show_bug.cgi?id=394137 Bug ID: 394137 Summary: Appmenu configuration missing from sytem settings Product: systemsettings Version: 5.12.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_style Assignee: unassigned-b...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- Created attachment 112581 --> https://bugs.kde.org/attachment.cgi?id=112581=edit Missing options The appmenu configuration section is missing from system settings Behavior: going to system settings -> application style -> widget style ->fine tuning -> missing options to configure appmenu Expected behavior: the appmenu configuration section is available. Keep in mind that the appmenu still works either being in a panel or a button in the titlebar without any problem, it's just the missing entry in system settings. Running KDE Neon User Stable all packages updated. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 389122] Image and spacing corruption in image heavy directory
https://bugs.kde.org/show_bug.cgi?id=389122 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 389122] Image and spacing corruption in image heavy directory
https://bugs.kde.org/show_bug.cgi?id=389122 --- Comment #2 from TYY331 <sebastian.p...@gmail.com> --- (In reply to Nate Graham from comment #1) > Can you please attach a screenshot or screen recording? I can confirm this bug is fixed, elements in the filepicker are shown correctly even on image heavy directories, I've tried every sorting order, name below or next to the thumbnail, and there isn't any missalignment, I'm running Neon user stable btw. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget
https://bugs.kde.org/show_bug.cgi?id=368838 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added CC||sebastian.p...@gmail.com --- Comment #41 from TYY331 <sebastian.p...@gmail.com> --- The memory leak also occurs while displaying application's icons. Displaying application's icons in the launcher constantly increases plasma's memory usage. Steps to reproduce. 1. Display application's icon (application menu, application launcher and application dashboard trigger the memory leak) Bear in mind since icons are low size files the memory leak per icon is quite low, the problem becomes evident while displaying a lot of icons over time, that's why you have to rapidly navigate the menus due to time constrains, normal use would take a couple of days. The problem is that there is no workaround since application's icons are always present and can't be disabled. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 389880] New: Keyboard shortcut to show/hide the aside preview pane in the KDE filepicker dialog.
https://bugs.kde.org/show_bug.cgi?id=389880 Bug ID: 389880 Summary: Keyboard shortcut to show/hide the aside preview pane in the KDE filepicker dialog. Product: kdialog Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: sebastian.p...@gmail.com Target Milestone: --- Created attachment 110334 --> https://bugs.kde.org/attachment.cgi?id=110334=edit lack of shortcut to hide/show preview pane It would really improve the general workflow if you could have a shortcut to this feature because for example you need to get a good look at a video file before selecting it, on Windows you can do a workaround by opening the file with a video player in the same open file dialog, allowing you to preview the file before selecting it. Having a shortcut to this pane will allow the user to get a quick preview of the file they are going to select and hide the pane afterwards to get more space available. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 389666] New: System settings crash after going back from web shortcuts
https://bugs.kde.org/show_bug.cgi?id=389666 Bug ID: 389666 Summary: System settings crash after going back from web shortcuts Product: systemsettings Version: 5.11.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: sebastian.p...@gmail.com Target Milestone: --- System settings segfaults going back from web shortcuts. Steps to reproduce. Using icon view. Open system settings, go to shortcuts, go to web shortcuts, go back to icon view, similar to bug https://bugs.kde.org/show_bug.cgi?id=216215 Using sidebar view. Open system settings, go to shortcuts, go to web shortcuts, go back or select other option like custom shortcuts. This behavior is always reproduceable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364710] Desktop Grid includes the "close window widget"
https://bugs.kde.org/show_bug.cgi?id=364710 TYY331 <sebastian.p...@gmail.com> changed: What|Removed |Added CC||sebastian.p...@gmail.com --- Comment #7 from TYY331 <sebastian.p...@gmail.com> --- Is this going to be fixed any time soon? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389123] New: Blank page in Look and Feel and desktop theme sections in System Settings
https://bugs.kde.org/show_bug.cgi?id=389123 Bug ID: 389123 Summary: Blank page in Look and Feel and desktop theme sections in System Settings Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: sebastian.p...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- System Settings >> Workspace theme >> Look and feel/Desktop theme show a blank page. That means the user is unable to change all of the related settings because they are unavailable. Workaround. Install the qml-module-org-kde-kcm package, in Neon is sudo apt install qml-module-org-kde-kcm, this solves the problem and the options are both available and work as expected (you can change desktop themes etc). Fix. Mark the qml-module-org-kde-kcm package as a dependency for the systemsettings package and make it installed by default. This is likely caused by a recent change in KDE Frameworks lately since I haven't encountered this bug before. -- You are receiving this mail because: You are watching all bug changes.
[kfile] [Bug 389122] New: Image and spacing corruption in image heavy directory
https://bugs.kde.org/show_bug.cgi?id=389122 Bug ID: 389122 Summary: Image and spacing corruption in image heavy directory Product: kfile Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- When using the KDE file picker viewing a directory that contains mostly images (10+) the images get corrupted and shifted out of alignment, this effect is reproducible always provided the conditions are met. 1. the directory is comprised of mostly images 2. the icon view is set (short view) 3. file preview is enabled 4. sorting by size, date, type Changing any of these conditions produces the correct behavior. System. Neon, Plasma 5.11.5, KDE frameworks 5.42, 4.13.0-26-generic. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388378] Image corruption in Magnifier utility
https://bugs.kde.org/show_bug.cgi?id=388378 --- Comment #2 from TYY331 <sebastian.p...@gmail.com> --- (In reply to Christoph Feck from comment #1) > The systemsettings section that is displayed in the screenshot is special > because it uses OpenGL itself. Is this issue visible always or only with > those OpenGL windows? The issue is always present no matter the content being displayed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 388378] New: Image corruption in Magnifier utility
https://bugs.kde.org/show_bug.cgi?id=388378 Bug ID: 388378 Summary: Image corruption in Magnifier utility Product: kwin Version: 5.11.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: sebastian.p...@gmail.com Target Milestone: --- Created attachment 109600 --> https://bugs.kde.org/attachment.cgi?id=109600=edit Image of the Magnifier utility Observed behavior: Magnifier utility presents corrupted image Expected behavior: Image is presented correctly Additional info. This bug might be related to compositing as selecting XRenderer backend fixes the image corruption and the utility works as expected, using OpenGL2.0 or OpenGL 3.1 backend produces the bug. I'm running an Intel GPU, Kernel 4.10.0-42-generic, KDE Neon user edition. -- You are receiving this mail because: You are watching all bug changes.
