[systemsettings] [Bug 394698] Selecting locales instead of formats is very frustrating compared to KDE4 version
https://bugs.kde.org/show_bug.cgi?id=394698 --- Comment #18 from AK-47 --- (In reply to Nate Graham from comment #14) > See the upstream discussion in https://bugreports.qt.io/browse/QTBUG-58351. > > We had an idea to allow the user to select values/strings in the Plasma > config UI rather than locales, and then secretly set whatever locale is > mapped to it, but this ran afoul of the fact that the locales include > translated text not just string formatting. The POSIX locale system just > isn't set up to allow this to happen. So unfortunately isn't something we > can feasibly fix in KDE alone. It doesn't even seem like something that can > be done in Qt alone! Because the mapping of locales to both string > formatting and also translated text is baked into the POSIX and libc > implementation of locales, it really needs to be fixed there. > > If it's fixed at a level any higher than that, then the result would simply > be applications not respecting your formatting preferences in a > random-seeming manner. If it was done only in Qt, then all non-Qt apps would > be non-respecting, and if we did it in KDE itself (as we did in Plasma 4 and > earlier), then all non-KDE apps would be non-conforming, even those that use > Qt. It would be a matter of winning the battle but losing the war. > > So someone needs to get the ball rolling at the POSIX and libc levels to > propose a new spec, or backwards-compatible changes to the existing one. Would it be possible to create a set of custom locale files based on a system locale with the custom formats built in and "select" that one? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394698] Selecting locales instead of formats is very frustrating compared to KDE4 version
https://bugs.kde.org/show_bug.cgi?id=394698 AK-47 changed: What|Removed |Added Version|5.23.3 |5.27.80 Platform|openSUSE|Neon --- Comment #17 from AK-47 --- Any reasonable chance that this is getting fixed for Plasma 6.0? The status of this report is now RESOLVED UPSTREAM but when on the latest KDE Neon unstable, this problem is still there. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394698] Selecting locales instead of formats is very frustrating compared to KDE4 version
https://bugs.kde.org/show_bug.cgi?id=394698 AK-47 changed: What|Removed |Added Version|5.20.5 |5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 444249] Place text inside the progress bar instead of outside and next to it
https://bugs.kde.org/show_bug.cgi?id=444249 --- Comment #7 from AK-47 --- (In reply to Nate Graham from comment #6) > I don't know. It's not KDE code, so from a KDE perspective, it doesn't > matter to us. :) Intersting, is this a Qt internal thing? > I don't think there is. > The point remains: A QtWidgets-based app shouldn't assume a particular > visual representation. QStyle styles can do all sorts of crazy things; it's > all explicitly supported. This defeats the whole purpose of a GUI toolkit, yet alone one such as Qt. I agree an app should not assume particular visual details, such as the nature of a border or the default font, but apps should be able to have basic expectations for what something roughly looks like: - A push button is a box with text/icon inside it, instead of a small box with the text right next to it. Users can click on it and it may result in something. - A check box is a tick with some text next to it, rather than a giant banana with text all on the tip. - A scroll bar looks like a bar which you can drag a slider up/down or back/forth, to view a different portion of the area. - A progress bar looks like a box with some text inside it, and filled in with some colour, which together indicates the status of an operation. Or should app developers now recreate these basic controls because their visual representation is undefined? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 444249] Place text inside the progress bar instead of outside and next to it
https://bugs.kde.org/show_bug.cgi?id=444249 --- Comment #5 from AK-47 --- (In reply to AK-47 from comment #4) > Doe Qt have any simple way to check for this? By this, I mean in a platform/desktop independent manner. Otherwise this defeats the purpose of Qt. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 444249] Place text inside the progress bar instead of outside and next to it
https://bugs.kde.org/show_bug.cgi?id=444249 --- Comment #4 from AK-47 --- (In reply to Nate Graham from comment #3) > What the win95 style does isn't relevant to Breeze. Where would be the best category/place to file this bug for the Win95 style then? > If apps are expecting the text to be inside the bar, that's a bug in the > app, because--as you have discovered--the style determined the placement of > the text. Apps need to be designed flexible to accommodate both text > locations. Is there a way for an app to find out where the text is placed? Doe Qt have any simple way to check for this? Because, if not, you can hardly blame the app for this. Breeze is pretty much the only theme I've seen that is designed the way it is. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 444249] Place text inside the progress bar instead of outside and next to it
https://bugs.kde.org/show_bug.cgi?id=444249 --- Comment #2 from AK-47 --- (In reply to Nate Graham from comment #1) > This is intentional; there isn't room in the progress bar for this because > of its intentionally thin design. If we made it thick enough to accommodate > text, it would look too big and out of place with other UI elements. What about on the other styles such as Win95? It's definitely out of place on that style, and looks horrible there. In either case, I think this needs to be reconsidered, it isn't a natural fit in a UI especially for applications that often expect that the text will be inside the bar. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 444249] New: Place text inside the progress bar instead of outside and next to it
https://bugs.kde.org/show_bug.cgi?id=444249 Bug ID: 444249 Summary: Place text inside the progress bar instead of outside and next to it Product: Breeze Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- The Breeze themes all place the progress bar's text next to a thin bar, instead of placing text inside the progress bar, which makes it look hideous and out of proportion on many apps. It affects bars with other text in them, and as the text changes (eg. the current step), the bar's width fluctuates. This occurs even with the Windows 9X style. However, it doesn't appear to be a Qt problem since running an app with -style=fusion will result in normal progress indicators. Most sane UIs contain the progress bar text inside the bar itself, which makes for a compact component. Applications often expect this, and put more than just a percentage on the text. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438729] Icons of some X11 apps not shown in Wayland
https://bugs.kde.org/show_bug.cgi?id=438729 AK-47 changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- Version|5.22.1 |5.22.3 --- Comment #5 from AK-47 --- The last status was NEEDSINFO but the requested info has been provided. This is still a problem as of KDE Plasma 5.22.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438729] Icons of some X11 apps not shown in Wayland
https://bugs.kde.org/show_bug.cgi?id=438729 --- Comment #2 from AK-47 --- Created attachment 139483 --> https://bugs.kde.org/attachment.cgi?id=139483=edit Screenshot as requested (In reply to Nate Graham from comment #1) > 1. What apps are affected? Claws Mail 95% chance, and Virtual Box 20% chance. > 2. What icon is shown instead? Nothing? The generic Wayland icon? Something > else? Nothing. No icon, no tile, nothing. > 3. Can you provide a screenshot? See attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438729] Icons of some X11 apps not shown in Wayland
https://bugs.kde.org/show_bug.cgi?id=438729 AK-47 changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438729] New: Icons of some X11 apps not shown in Wayland
https://bugs.kde.org/show_bug.cgi?id=438729 Bug ID: 438729 Summary: Icons of some X11 apps not shown in Wayland Product: plasmashell Version: 5.22.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: chkb...@safe-mail.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139383 --> https://bugs.kde.org/attachment.cgi?id=139383=edit stderr of "plasmashell --replace" SUMMARY The icons of X11/XWayland apps do not show in the task manager. Since 5.21. STEPS TO REPRODUCE 1. Log in to Wayland session 2. Run an X11-based app like Claws Mail. OBSERVED RESULT The icon is not shown in the task manager. EXPECTED RESULT The icon should be shown in the task manager. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Rawhide (available in About System) KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The icons of Wayland-based apps are shown as expected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438532] [Wayland] Clicking an icon opens the previously-launched application
https://bugs.kde.org/show_bug.cgi?id=438532 AK-47 changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438532] [Wayland] Clicking an icon opens the previously-launched application
https://bugs.kde.org/show_bug.cgi?id=438532 --- Comment #2 from AK-47 --- Created attachment 139283 --> https://bugs.kde.org/attachment.cgi?id=139283=edit stderr of "plasmashell --replace" Nothing non-standard, just the touch pad which KDE thinks is just a mouse (and doesn't see it as a touch pad). It seems the last update to Fedora has made it go away, something to do with KIO perhaps. Anyway here's the stderr (there was nothing in stdout) in case it reveals something else. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438532] [Wayland] Clicking an icon opens the previously-launched application
https://bugs.kde.org/show_bug.cgi?id=438532 AK-47 changed: What|Removed |Added Platform|Other |Fedora RPMs Summary|[Wayland] Clicking an icon |[Wayland] Clicking an icon |opens the last opened |opens the |application |previously-launched ||application -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438532] New: [Wayland] Clicking an icon opens the last opened application
https://bugs.kde.org/show_bug.cgi?id=438532 Bug ID: 438532 Summary: [Wayland] Clicking an icon opens the last opened application Product: plasmashell Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: chkb...@safe-mail.net CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When clicking on an icon in either the Kickoff menu or the launcher, instead of opening the requested application, it will either open nothing or open the program that was previously launched. STEPS TO REPRODUCE 1. Log into the Plasma Wayland session. 2. Click on any icon in the Kickoff menu or the launcher. 3. Click on any other icon in the Kick-off menu or launcher. OBSERVED RESULT If it's the first time an icon was clicked after log-in (ie. Step 2), nothing happens. If it is not the first time an icon was clicked after log-in (ie. Step 3), the previously opened application launches instead of the one the icon is meant to launch. EXPECTED RESULT The icon should launch the application that has been requested, not the one that was launched before (or nothing). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Rawhide (FC35) (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Only happens with the Wayland session. Appears to be normal under X11. Tested with fresh user profile, so 100% default settings after updating from 5.21.90 to 5.22.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437925] Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 AK-47 changed: What|Removed |Added Ever confirmed|0 |1 Resolution|BACKTRACE |--- Status|NEEDSINFO |REOPENED --- Comment #6 from AK-47 --- Stack traces provided as requested. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437925] Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 --- Comment #5 from AK-47 --- And here is when I successfully opened the VM but it crashed when closing: PID: 4446 (kwin_wayland) UID: 1000 () GID: 1000 () Signal: 11 (SEGV) Timestamp: Mon 2021-06-07 ... Command Line: kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Disk Size: 5.3M Message: Process 4446 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 4446: #0 0x7f2dd014bb31 _ZNK4KWin16EffectWindowImpl5shapeEv (libkwin.so.5 + 0x175b31) #1 0x7f2dcff8f1c3 _ZNK4KWin10BlurEffect10blurRegionEPKNS_12EffectWindowE.constprop.0 (libkwin4_effect_builtins.so.1 + 0xd51c3) #2 0x7f2dcfef1e9f _ZN4KWin10BlurEffect14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin4_effect_builtins.so.1 + 0x37e9f) #3 0x7f2dd013cafb _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x166afb) #4 0x7f2dd013cafb _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x166afb) #5 0x7f2dd013cafb _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x166afb) #6 0x7f2dd01b2e3b _ZN4KWin5Scene17paintSimpleScreenEiRK7QRegion (libkwin.so.5 + 0x1dce3b) #7 0x7f2dd01ad936 _ZN4KWin5Scene16finalPaintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x1d7936) #8 0x7f2dd0141a48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #9 0x7f2dd0141a48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #10 0x7f2dd0141a48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #11 0x7f2dd0141a48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #12 0x7f2dd01affe4 _ZN4KWin5Scene11paintScreenEPiRK7QRegionS4_PS2_S5_PNS_10RenderLoopERK10QMatrix4x4 (libkwin.so.5 + 0x1d9fe4) #13 0x7f2db91ccaf8 _ZN4KWin11SceneOpenGL5paintEiRK7QRegionRK5QListIPNS_8ToplevelEEPNS_10RenderLoopE.part.0 (KWinSceneOpenGL.so + 0x20af8) #14 0x7f2dd01106a8 _ZN4KWin10Compositor9compositeEPNS_10RenderLoopE (libkwin.so.5 + 0x13a6a8) #15 0x7f2dce7bec99 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d9c99) #16 0x7f2dd00d5ff6 _ZN4KWin10RenderLoop14frameRequestedEPS0_ (libkwin.so.5 + 0x6) #17 0x7f2dd01a2c97 _ZN4KWin17RenderLoopPrivate8dispatchEv (libkwin.so.5 + 0x1ccc97) #18 0x7f2dce7bec99 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d9c99) #19 0x7f2dce7c1f3e _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2dcf3e) #20 0x7f2dce7b579f _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2d079f) #21 0x7f2dcf5b9423 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1ae423) #22 0x7f2dce78b098 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2a6098) #23 0x7f2dce7db983 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2f6983) #24 0x7f2dce7d9f50 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f4f50) #25 0x55fec48397a1 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (kwin_wayland + 0x8f7a1) #26 0x7f2dce789ab2 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a4ab2) #27 0x7f2dce791fe4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2acfe4) #28 0x55fec47dc1c9 main (kwin_wayland + 0x321c9) #29 0x7f2dcdf0fb75 __libc_start_main (libc.so.6 + 0x27b75) #30 0x55fec47dcace _start (kwin_wayland + 0x32ace) Stack trace of thread 4452: #0 0x7f2dcdfdd7bf __poll (libc.so.6 + 0xf57bf) #1 0x7f2dcbf3247c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa947c) #2 0x7f2dcbedbc03 g_main_context_iteration (libglib
[kwin] [Bug 437925] Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 --- Comment #4 from AK-47 --- Nevermind, I spoke too soon. Here is when I open the VM: PID: 3124 (kwin_wayland) UID: 1000 () GID: 1000 () Signal: 11 (SEGV) Timestamp: Mon 2021-06-07 ... Command Line: kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Disk Size: 6.6M Message: Process 3124 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 3124: #0 0x7f4790490b31 _ZNK4KWin16EffectWindowImpl5shapeEv (libkwin.so.5 + 0x175b31) #1 0x7f47902d41c3 _ZNK4KWin10BlurEffect10blurRegionEPKNS_12EffectWindowE.constprop.0 (libkwin4_effect_builtins.so.1 + 0xd51c3) #2 0x7f4790236e9f _ZN4KWin10BlurEffect14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin4_effect_builtins.so.1 + 0x37e9f) #3 0x7f4790481afb _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x166afb) #4 0x7f47904f7e3b _ZN4KWin5Scene17paintSimpleScreenEiRK7QRegion (libkwin.so.5 + 0x1dce3b) #5 0x7f47904f2936 _ZN4KWin5Scene16finalPaintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x1d7936) #6 0x7f4790486a48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #7 0x7f4790486a48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #8 0x7f47904f4fe4 _ZN4KWin5Scene11paintScreenEPiRK7QRegionS4_PS2_S5_PNS_10RenderLoopERK10QMatrix4x4 (libkwin.so.5 + 0x1d9fe4) #9 0x7f4779511af8 _ZN4KWin11SceneOpenGL5paintEiRK7QRegionRK5QListIPNS_8ToplevelEEPNS_10RenderLoopE.part.0 (KWinSceneOpenGL.so + 0x20af8) #10 0x7f47904556a8 _ZN4KWin10Compositor9compositeEPNS_10RenderLoopE (libkwin.so.5 + 0x13a6a8) #11 0x7f478eb03c99 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d9c99) #12 0x7f479041aff6 _ZN4KWin10RenderLoop14frameRequestedEPS0_ (libkwin.so.5 + 0x6) #13 0x7f47904e7c97 _ZN4KWin17RenderLoopPrivate8dispatchEv (libkwin.so.5 + 0x1ccc97) #14 0x7f478eb03c99 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d9c99) #15 0x7f478eb06f3e _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2dcf3e) #16 0x7f478eafa79f _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2d079f) #17 0x7f478f8fe423 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1ae423) #18 0x7f478ead0098 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2a6098) #19 0x7f478eb20983 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2f6983) #20 0x7f478eb1ef50 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f4f50) #21 0x55fc3350b7a1 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (kwin_wayland + 0x8f7a1) #22 0x7f478eaceab2 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a4ab2) #23 0x7f478ead6fe4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2acfe4) #24 0x55fc334ae1c9 main (kwin_wayland + 0x321c9) #25 0x7f478e254b75 __libc_start_main (libc.so.6 + 0x27b75) #26 0x55fc334aeace _start (kwin_wayland + 0x32ace) Stack trace of thread 3132: #0 0x7f478e3227bf __poll (libc.so.6 + 0xf57bf) #1 0x7f478c27747c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa947c) #2 0x7f478c220c03 g_main_context_iteration (libglib-2.0.so.0 + 0x52c03) #3 0x7f478eb21698 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f7698) #4 0x7f478eaceab2 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a4ab2) #5 0x7f478e91225a _ZN7QThread4execEv (libQt5Core.so.5 + 0xe825a) #6 0x7f478e913456 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xe9456) #7 0x7f478e6dd1c9 start_thread (libpthread.so.0 + 0x91c9) #8 0x7f478e32d463 __clone (libc.so.6 + 0x100463) Stack trace of thread 3128: #0
[kwin] [Bug 437925] Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 --- Comment #3 from AK-47 --- OK so an update. I reinstalled Fedora and the problem with the VM has gone. However, there are other X11 apps that do this, which may be relevant here: PID: 2483 (kwin_wayland) UID: 1000 () GID: 1000 () Signal: 11 (SEGV) Timestamp: Mon 2021-06-07 1 Command Line: kwin_wayland --wayland_fd 4 --xwayland /usr/libexec/startplasma-waylandsession Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 () Disk Size: 6.0M Message: Process 2483 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 2483: #0 0x7f30d3f29b31 _ZNK4KWin16EffectWindowImpl5shapeEv (libkwin.so.5 + 0x175b31) #1 0x7f30d3d6d1c3 _ZNK4KWin10BlurEffect10blurRegionEPKNS_12EffectWindowE.constprop.0 (libkwin4_effect_builtins.so.1 + 0xd51c3) #2 0x7f30d3ccfe9f _ZN4KWin10BlurEffect14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin4_effect_builtins.so.1 + 0x37e9f) #3 0x7f30d3f1aafb _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x166afb) #4 0x7f30d3f1aafb _ZN4KWin18EffectsHandlerImpl14prePaintWindowEPNS_12EffectWindowERNS_18WindowPrePaintDataENSt6chrono8durationIlSt5ratioILl1ELl1000 (libkwin.so.5 + 0x166afb) #5 0x7f30d3f90e3b _ZN4KWin5Scene17paintSimpleScreenEiRK7QRegion (libkwin.so.5 + 0x1dce3b) #6 0x7f30d3f8b936 _ZN4KWin5Scene16finalPaintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x1d7936) #7 0x7f30d3f1fa48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #8 0x7f30d3f1fa48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #9 0x7f30d3f1fa48 _ZN4KWin18EffectsHandlerImpl11paintScreenEiRK7QRegionRNS_15ScreenPaintDataE (libkwin.so.5 + 0x16ba48) #10 0x7f30d3f8dfe4 _ZN4KWin5Scene11paintScreenEPiRK7QRegionS4_PS2_S5_PNS_10RenderLoopERK10QMatrix4x4 (libkwin.so.5 + 0x1d9fe4) #11 0x7f30bcfaaaf8 _ZN4KWin11SceneOpenGL5paintEiRK7QRegionRK5QListIPNS_8ToplevelEEPNS_10RenderLoopE.part.0 (KWinSceneOpenGL.so + 0x20af8) #12 0x7f30d3eee6a8 _ZN4KWin10Compositor9compositeEPNS_10RenderLoopE (libkwin.so.5 + 0x13a6a8) #13 0x7f30d259cc99 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d9c99) #14 0x7f30d3eb3ff6 _ZN4KWin10RenderLoop14frameRequestedEPS0_ (libkwin.so.5 + 0x6) #15 0x7f30d3f80c97 _ZN4KWin17RenderLoopPrivate8dispatchEv (libkwin.so.5 + 0x1ccc97) #16 0x7f30d259cc99 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d9c99) #17 0x7f30d259ff3e _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2dcf3e) #18 0x7f30d259379f _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2d079f) #19 0x7f30d3397423 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1ae423) #20 0x7f30d2569098 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2a6098) #21 0x7f30d25b9983 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2f6983) #22 0x7f30d25b7f50 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f4f50) #23 0x5639e4f167a1 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (kwin_wayland + 0x8f7a1) #24 0x7f30d2567ab2 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a4ab2) #25 0x7f30d256ffe4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2acfe4) #26 0x5639e4eb91c9 main (kwin_wayland + 0x321c9) #27 0x7f30d1cedb75 __libc_start_main (libc.so.6 + 0x27b75) #28 0x5639e4eb9ace _start (kwin_wayland + 0x32ace) Stack trace of thread 2486: #0 0x7f30d1dbb7bf __poll (libc.so.6 + 0xf57bf) #1 0x7f30cfd1047c g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xa947c) #2 0x7f30cfcb9c03 g_main_context_iteration (libglib-2.0.so.0 + 0x52c03) #3 0x7f30d25ba698 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f7698) #4 0x7f30d2567ab2
[kwin] [Bug 437925] Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 --- Comment #1 from AK-47 --- Possibly related, I also find that killing XWayland will also crash the entire session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437925] New: Crash or hang when either opening or closing a VirtualBox VM
https://bugs.kde.org/show_bug.cgi?id=437925 Bug ID: 437925 Summary: Crash or hang when either opening or closing a VirtualBox VM Product: kwin Version: 5.21.90 Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- SUMMARY When opening or closing a VirtualBox VM, the whole session (presumably thanks to KWin) crashes. This does not happen under X11 session. STEPS TO REPRODUCE 1. Open VirtualBox in Wayland session and attempt to start a Virtual Machine. 2. If there is no crash, close the VM. 3. If there is still no crash, repeat the steps. OBSERVED RESULT The entire session either crashes or locks up. This also occurs when attempting to load a saved VM or attempting to save the VM. The Linux OS itself is stable, and this only occurs in the Wayland session. EXPECTED RESULT The VM should either start or stop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Workstation Rawhide, kernel 5.13.0.0-rc3.25.fc35.x86_64 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 On a side note, I wish the System Information dialog would show the KDE Plasma version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433425] New: Panel crashes and does not restart on its own
https://bugs.kde.org/show_bug.cgi?id=433425 Bug ID: 433425 Summary: Panel crashes and does not restart on its own Product: plasmashell Version: 5.21.0 Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: 1.0 SUMMARY Panel crashes frequently, and does not restart STEPS TO REPRODUCE 1. Use KDE under Wayland for some time. 2. Do something like rapid window switching or playing with an XWayland application like VirtualBox 3. After a while, the panel will crash. OBSERVED RESULT The panel does not restart on its own like in previous versions. EXPECTED RESULT The panel should start on its own again, otherwise without a terminal already open or an app that can bring up the terminal (eg. Dolphin or Kate) you are pretty much stuck without a shell. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora (rawhide) (available in About System) KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432299] Firefox flickering and window ghost
https://bugs.kde.org/show_bug.cgi?id=432299 AK-47 changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from AK-47 --- I tried that, and the issue still occurs. Especially so if multiple tabs are opened, and is easily reproducable. In fact it is slightly worse with WebRender enabled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432299] New: Firefox flickering and window ghost
https://bugs.kde.org/show_bug.cgi?id=432299 Bug ID: 432299 Summary: Firefox flickering and window ghost Product: kwin Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- SUMMARY Using Firefox with native Wayland (firefox-wayland, or Firefox with MOZ_ENABLE_WAYLAND=1 set) regularly results in flickering, issues with windows not taking up the required size, and ghosting when Firefox is terminated or exits. STEPS TO REPRODUCE 1. Run "firefox-wayland" OR: MOZ_ENABLE_WAYLAND=1 firefox 2. Try various things such as resizing the window (maximising/minimising) or switching tabs, browsing the web etc. 3. Exit Firefox OBSERVED RESULT STEPS 1-2: Eventually you will see the window flickering and becoming unusable as artifacts appear all over the place. STEP 3: There is a 50/50 chance that ghosted pieces of Firefox window will remain. EXPECTED RESULT Smooth, predictable operation, as expected with any application. Has been a continual problem even with 5.20.5 and earlier. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Rawhide/Plasma 5.20.90 (available in About System) KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 394698] Selecting locales instead of formats is very frustrating compared to KDE4 version
https://bugs.kde.org/show_bug.cgi?id=394698 AK-47 changed: What|Removed |Added CC||chkb...@safe-mail.net Version|5.20.3 |5.20.5 --- Comment #9 from AK-47 --- I agree this UX is a joke. If I want to use 24h or a different/custom format for time, currency, etc. the only choice I have is to select a different country’s locale, and you have to go through the whole world before finding the one with the format you like. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429784] Dragging an icon over another icon causes a crash
https://bugs.kde.org/show_bug.cgi?id=429784 AK-47 changed: What|Removed |Added Version|5.20.3 |5.20.4 Flags||Wayland+, Usability+ --- Comment #1 from AK-47 --- Update: Still present in 5.20.4, Qt 5.15.2. In addition I discovered that this bug appears if you use an application launcher widget, dragging one icon over another (eg. to swap positions?) will do the same thing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427572] Window thumbnail tiles are unresponsive on Wayland
https://bugs.kde.org/show_bug.cgi?id=427572 AK-47 changed: What|Removed |Added Version|5.19.90 |5.20.3 Platform|Other |RedHat RPMs --- Comment #1 from AK-47 --- Update: bug still exists on 5.20.3, but slightly different steps to reproduce: 1. Change to vertical task bar. 2. launch multiple applications as described previously. 3. Bring the focus to another application in another group. 4. Click on the tile menu that has a group, in which none of the applications are currently focus. Same thing happens. However, if one of the apps are already in focus, then clicking on the task manager tile will cycle through the windows in the group. To select an app from a tile with no apps in focus, you need to hover over it and click on the correct tile. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429785] Window thumbnail images are invisible on Wayland
https://bugs.kde.org/show_bug.cgi?id=429785 --- Comment #2 from AK-47 --- Looks like it is, my apologies. Consider this report as extra information in relation to that bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429785] New: Window thumbnail images are invisible on Wayland
https://bugs.kde.org/show_bug.cgi?id=429785 Bug ID: 429785 Summary: Window thumbnail images are invisible on Wayland Product: plasmashell Version: 5.20.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: chkb...@safe-mail.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 133718 --> https://bugs.kde.org/attachment.cgi?id=133718=edit Screenshot of issue SUMMARY Window thumbnails on the task bar are often invisible. The thumbnail pane itself shows, but no thumbnail image. STEPS TO REPRODUCE 1. Hover over a window in the task bar. 2. Wait until the thumbnail pane pops up. OBSERVED RESULT There is no thumbnail image. EXPECTED RESULT The thumbnail image should appear. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Workstation 33 (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION This is easiest to reproduce with X11 apps running under Wayland session. The thumbnail does appear when the application window contents are updated (eg. playing video or image slideshow). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427524] Need an easy method to disconnect a remote folder or drive
https://bugs.kde.org/show_bug.cgi?id=427524 --- Comment #2 from AK-47 --- This is about remote locations accessed via KIO I presume, since I'm not mounting them with anything other than Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429784] New: Dragging an icon over another icon causes a crash
https://bugs.kde.org/show_bug.cgi?id=429784 Bug ID: 429784 Summary: Dragging an icon over another icon causes a crash Product: kwin Version: 5.20.3 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- SUMMARY In many cases, it is possible to cause a crash just by dragging one icon over another. STEPS TO REPRODUCE 1. Repeatedly tap one of the icons on the task bar until it "sticks" to the cursor, or initiate a drag. 2. Hover the icon over another icon on the task bar. 3. You may have to tap a few times again to let go of the icon. OBSERVED RESULT The shell hangs, with suddenly a lot of disk activity, and then eventually the entire desktop including kwin crashes. EXPECTED RESULT The icon shouldn't even stick to the mouse in the first place. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Workstation 33 (available in About System) KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Not sure if this is a "kwin" or "plasmashell" bug. It appears kwin is the one that crashes, since I just get a few characters on the screen once it does, but plasmashell might be causing some havoc here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427445] Cannot select grouped windows on a vertical task bar
https://bugs.kde.org/show_bug.cgi?id=427445 --- Comment #11 from AK-47 --- Done: https://bugs.kde.org/show_bug.cgi?id=427572 Seems more like a shell-related issue than a kwin one though? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427572] New: Window thumbnail tiles are unresponsive
https://bugs.kde.org/show_bug.cgi?id=427572 Bug ID: 427572 Summary: Window thumbnail tiles are unresponsive Product: kwin Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- SUMMARY Window thumbnails do not respond to clicks. Most noticeable with vertical task bar. STEPS TO REPRODUCE 1. Change the task bar to vertical task bar 2. Launch multiple applications, some being the same, so windows get grouped. 3. Click on the group windows or hover over the icon so the tile menu appears. 4. Attempt to click on the tile menu and select the window. OBSERVED RESULT Nothing happens. The clicks do not even generate any visual indication of a response. EXPECTED RESULT Window should be selected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 Workstation (Beta) (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75 Qt Version: 5.15.1 ADDITIONAL INFORMATION Using the Wayland session. Windows can be selected using Alt+Tab. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427445] Cannot select grouped windows on a vertical task bar
https://bugs.kde.org/show_bug.cgi?id=427445 --- Comment #9 from AK-47 --- I'm not sure how this is a separate issue given this is what I was reporting in the first place. It's totally different to what's been considered a duplicate (stuff about browsers and links). When filing the new report, do I just copy the contents of this report and stick it into the new one? Another option (if possible) might be to "unmark" this one? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427445] Cannot select grouped windows on a vertical task bar
https://bugs.kde.org/show_bug.cgi?id=427445 --- Comment #7 from AK-47 --- (In reply to Nate Graham from comment #5) > As a workaround, you can hover over the grouped task and click on one of the > window thumbnails, or else change the "Clicking grouped task" behavior to > anything else. Clicking on the window thumbnails does nothing. The thumbnail menu doesn't disappear though, but it just won't let me click on any of the items. Changing the behavior to "Show tooltip window thumbnails" makes the button respond, but the tooltip menu still doesn't respond at all. No indication it was pressed either. (change in item's border?) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427524] New: Need an easy method to disconnect a remote folder or drive
https://bugs.kde.org/show_bug.cgi?id=427524 Bug ID: 427524 Summary: Need an easy method to disconnect a remote folder or drive Product: dolphin Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: chkb...@safe-mail.net CC: kfm-de...@kde.org Target Milestone: --- One major setback/oversight for Dolphin is the inability to manually disconnect remote folders in the "Network" page. This means that you better hope that nothing is being done on the files before disconnecting from the network or shutting the machine or remote server down. This is a good way to end up corrupting files on the remote end. You can DELETE the shortcut, but that won't solve the issue, there needs to be a menu option to disconnect/unmount the remote location without deleting it, so that it can be accessed easily through the "Network" page again. It is also not possible to easily determine which remote folders are connected and which are not, without going into them (and therefore connecting to them anyway). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427445] Cannot select grouped windows on a vertical task bar
https://bugs.kde.org/show_bug.cgi?id=427445 --- Comment #3 from AK-47 --- Just tried it, it works fine on X11. But I don't see the "+" group indicator, like I do with the horizontal bar (both on X11 and Wayland). -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 421653] "Unknown KDE project" for any attempt to build the system
https://bugs.kde.org/show_bug.cgi?id=421653 AK-47 changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #6 from AK-47 --- So far so good. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427445] Cannot select grouped windows on a vertical task bar
https://bugs.kde.org/show_bug.cgi?id=427445 --- Comment #1 from AK-47 --- Update: hovering over the group icon is possible, but nothing can be selected from the resulting menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427445] New: Cannot select grouped windows on a vertical task bar
https://bugs.kde.org/show_bug.cgi?id=427445 Bug ID: 427445 Summary: Cannot select grouped windows on a vertical task bar Product: plasmashell Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: chkb...@safe-mail.net CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On a vertical task bar, grouped windows cannot be selected. The button does not even appear depressed when clicked on STEPS TO REPRODUCE 1. Change the task bar to a vertical task bar. 2. Create multiple windows so that they become grouped into one icon. 3. Attempt to select the window. OBSERVED RESULT The button to select windows that are grouped together does not respond. EXPECTED RESULT There should be a pop-up menu (like the horizontal bar) that allows selection of an individual window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 Workstation (Beta) with Plasma 5.19.90. (available in About System) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.75 Qt Version: 5.15.1 ADDITIONAL INFORMATION Using the Wayland session. Windows are selectable with Alt+Tab. Occurs with both Task Manager and Icon-only Task Manager. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426913] Window thumbnail not working
https://bugs.kde.org/show_bug.cgi?id=426913 AK-47 changed: What|Removed |Added CC||chkb...@safe-mail.net --- Comment #8 from AK-47 --- I can reproduce the situation Patrick was talking about. Hovering over the icon in the task bar (for the window thumbnail) immediately makes the entire Plasma session crash under a Fedora 33 (beta) install, Plasma 5.19.90 Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 417004] Collapsed window when starting, after exiting in maximized state
https://bugs.kde.org/show_bug.cgi?id=417004 AK-47 changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from AK-47 --- Seems like it was fixed in 5.18.90. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421655] New: Window effects on Firefox (Wayland) only animates the frame, not contents
https://bugs.kde.org/show_bug.cgi?id=421655 Bug ID: 421655 Summary: Window effects on Firefox (Wayland) only animates the frame, not contents Product: kwin Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- SUMMARY When moving, minimising and restoring Firefox running with Wayland enabled, the effects only apply to the frame. The content doesn't have the affect applied to it. STEPS TO REPRODUCE 1. Enable Magic Lamp effect and/or Wobbly Windows 2. Run Firefox with either one of the following: (a) MOZ_ENABLE_WAYLAND=1 firefox (b) firefox-wayland (c) The "Firefox on Wayland" menu item. 3. Move, minimize or restore the window. OBSERVED RESULT The content of the window remains unanimated and does not have the effect applied to it, making it seem "detached" from the frame. The wobble or lamp effect applies to just the frame. EXPECTED RESULT The whole window should have the effect applied to it, not just the frame. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION This is a long-standing issue. It only affects the Wayland version of Firefox, not Firefox under XWayland. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 421653] New: "Unknown KDE project" for any attempt to build the system
https://bugs.kde.org/show_bug.cgi?id=421653 Bug ID: 421653 Summary: "Unknown KDE project" for any attempt to build the system Product: kdesrc-build Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mp...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- SUMMARY Following the build guide here: https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source Attempting to build anything result in an "Unknown KDE Project" failure. STEPS TO REPRODUCE 1. Follow the above guide to setup kdesrc-build. 2. Run kdesrc-build to attempt to build the modules. OBSERVED RESULT "Unknown KDE project: kdesrc-build" (or ktp-common-internals) $ kdesrc-build plasma-workspace plasma-workspace-wayland plasma-framework plasma-nm plasma-pa plasma-thunderbolt plasma-vault plasma-workspace-wallpapers kdeplasma-addons kwin kwin_wayland kscreen sddm-kcm breeze discover print-manager plasma-sdk kaccounts-integration kaccounts-providers kdeconnect-kde plasma-browser-integration xdg-desktop-portal-kde --include-dependencies Updating kde-build-metadata (to branch master) Updating sysadmin-repo-metadata (to branch master) kdesrc-build encountered an exceptional error condition: Runtime Error: Unknown KDE project: ktp-common-internals Can't continue, so stopping now. $ kdesrc-build --pretend kdesrc-build encountered an exceptional error condition: Runtime Error: Unknown KDE project: kdesrc-build Can't continue, so stopping now. $ kdesrc-build Updating kde-build-metadata (to branch master) Updating sysadmin-repo-metadata (to branch master) kdesrc-build encountered an exceptional error condition: Runtime Error: Unknown KDE project: kdesrc-build Can't continue, so stopping now. $ kdesrc-build --include-dependencies Updating kde-build-metadata (to branch master) Updating sysadmin-repo-metadata (to branch master) kdesrc-build encountered an exceptional error condition: Runtime Error: Unknown KDE project: kdesrc-build Can't continue, so stopping now. EXPECTED RESULT The build should complete successfully. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Running Fedora Rawhide. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420802] SECURITY: Notification background "bleeds" into the lock screen
https://bugs.kde.org/show_bug.cgi?id=420802 --- Comment #6 from AK-47 --- (In reply to AK-47 from comment #5) > (In reply to Vlad Zahorodnii from comment #4) > > Argh, the lockscreen window is placed below notifications so it kind of > > makes sense. > Funny you should mention that, I did notice that if there were multiple > notifications on the screen (eg. multiple update failures or some other > things) this often only occurred with just one notification window. To clarify, it would occur with one of the multiple windows, usually the one in the highest position. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420802] SECURITY: Notification background "bleeds" into the lock screen
https://bugs.kde.org/show_bug.cgi?id=420802 --- Comment #5 from AK-47 --- (In reply to Vlad Zahorodnii from comment #4) > Argh, the lockscreen window is placed below notifications so it kind of > makes sense. Funny you should mention that, I did notice that if there were multiple notifications on the screen (eg. multiple update failures or some other things) this often only occurred with just one notification window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420802] SECURITY: Notification background "bleeds" into the lock screen
https://bugs.kde.org/show_bug.cgi?id=420802 --- Comment #2 from AK-47 --- (In reply to David Edmundson from comment #1) > Just to make sure I understand, you see the blur effect on the lockscreen, > but not the contents of the notification itself? That is correct. The blur effect matches the exact position and outline of the notification. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 420802] New: SECURITY: Notification background "bleeds" into the lock screen
https://bugs.kde.org/show_bug.cgi?id=420802 Bug ID: 420802 Summary: SECURITY: Notification background "bleeds" into the lock screen Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- Created attachment 128029 --> https://bugs.kde.org/attachment.cgi?id=128029=edit Bug Screenshot SUMMARY The background of a notification will "bleed" into the lock screen, especially if the notification has blurred or glass effects. PRE-REQUISITES FOR REPRODUCING: 1. Noticed predominantly with a glass theme, especially with blurred effects. 2. Using a theme called "OxygenDymAero7." 3. Noticed on KDE Wayland session. STEPS TO REPRODUCE 1. Lock the screen 2. Trigger a notification, such as an update being available. The order of the steps do not appear to matter. OBSERVED RESULT A section of the lock screen will either be blurred or display an appreciable portion of the background effect used by the window. EXPECTED RESULT The lock screen should NOT give away the positions or contents of ANY window. This is a security issue and may also be the root of other potential information leaks in other circumstances. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Workstation 32 (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION KDE Wayland session. Unknown if this is related to just KWin (Wayland) or if there are other components at play. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 417004] New: Collapsed window when starting, after exiting in maximized state
https://bugs.kde.org/show_bug.cgi?id=417004 Bug ID: 417004 Summary: Collapsed window when starting, after exiting in maximized state Product: konsole Version: 19.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: chkb...@safe-mail.net Target Milestone: --- Created attachment 125584 --> https://bugs.kde.org/attachment.cgi?id=125584=edit Collapsed window SUMMARY When Konsole is exited in the maximized state, the window starts out collapsed the next time it is started. STEPS TO REPRODUCE 1. Open Konsole, and maximize the window. 2. Exit while the window is still maximized 3. Run Konsole again. OBSERVED RESULT The window starts in a collapsed state, like in the screen shot. EXPECTED RESULT The window should start up maximized. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Workstation 31 (x86-64) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION Running under KDE Wayland session. -- You are receiving this mail because: You are watching all bug changes.
