[kwin] [Bug 489744] New: KWin Crashes sometimes after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=489744 Bug ID: 489744 Summary: KWin Crashes sometimes after waking from sleep Classification: Plasma Product: kwin Version: 5.27.11 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: r...@reidswanson.com Target Milestone: --- Application: kwin_x11 (5.27.11) (Compiled from sources) Qt Version: 5.15.14 Frameworks Version: 5.116.0 Operating System: Linux 6.6.32-gentoo-dist x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Sometime, more often than not, KWin crashes after waking up from sleep. I often also have to restart plasmashell to get a fully functional desktop. I suspect, but cannot confirm, that it is related to this elogind bug: https://github.com/elogind/elogind/issues/234. I am currently using Gentoo with OpenRC and an NVIDIA graphics card. However, I have had problems with many Linux distributions (using systemd) with NVIDIA cards when waking from sleep, so the problem may run deeper than just the elogind bug referenced above. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x7fde2d932558 in QScreen::handle() const () from /usr/lib64/libQt5Gui.so.5 #5 0x7fde283bbcb4 in ?? () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #6 0x7fde2d951281 in QOpenGLContext::create() () from /usr/lib64/libQt5Gui.so.5 #7 0x7fde2e5cd390 in ?? () from /usr/lib64/libQt5Quick.so.5 #8 0x7fde2e5cef3f in ?? () from /usr/lib64/libQt5Quick.so.5 #9 0x7fde2e5cffd7 in ?? () from /usr/lib64/libQt5Quick.so.5 #10 0x7fde2d2c1eab in ?? () from /usr/lib64/libQt5Core.so.5 #11 0x7fde2c2ab652 in ?? () from /usr/lib64/libc.so.6 #12 0x7fde2c3278ac in ?? () from /usr/lib64/libc.so.6 Thread 4 (Thread 0x7fddec58e6c0 (LWP 17816) "CPMMListener"): #1 0x7fde25014037 in ?? () from /usr/lib64/libnvidia-glcore.so.550.90.07 #2 0x7fde24ff57c4 in ?? () from /usr/lib64/libnvidia-glcore.so.550.90.07 #3 0x7fde2c2ab652 in ?? () from /usr/lib64/libc.so.6 #4 0x7fde2c3278ac in ?? () from /usr/lib64/libc.so.6 Thread 3 (Thread 0x7fde136de6c0 (LWP 17779) "QQmlThread"): #1 0x7fde2b5e0a8f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fde2b58a8ac in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fde2b58ae3b in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fde2b58b540 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fde2d4d966e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fde2d48450b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fde2d2c0aaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fde2e10d1e9 in ?? () from /usr/lib64/libQt5Qml.so.5 #9 0x7fde2d2c1eab in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x7fde2c2ab652 in ?? () from /usr/lib64/libc.so.6 #11 0x7fde2c3278ac in ?? () from /usr/lib64/libc.so.6 Thread 2 (Thread 0x7fde27eae6c0 (LWP 17709) "QDBusConnection"): #1 0x7fde2b58ae87 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fde2b58b540 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fde2d4d966e in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fde2d48450b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fde2d2c0aaa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fde2c7d721b in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fde2d2c1eab in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fde2c2ab652 in ?? () from /usr/lib64/libc.so.6 #9 0x7fde2c3278ac in ?? () from /usr/lib64/libc.so.6 Thread 1 (Thread 0x7fde283d0840 (LWP 17707) "kwin_x11"): #1 0x7fde2c2aa8a0 in pthread_cond_wait () from /usr/lib64/libc.so.6 #2 0x7fde2d2c7a5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib64/libQt5Core.so.5 #3 0x7fde2e5d1eaa in ?? () from /usr/lib64/libQt5Quick.so.5 #4 0x7fde2e5d2d32 in ?? () from /usr/lib64/libQt5Quick.so.5 #5 0x7fde2d917375 in QWindow::event(QEvent*) () from /usr/lib64/libQt5Gui.so.5 #6 0x7fde2cb03126 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #7 0x7fde2d485bc8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #8 0x7fde2d90cad5 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib64/libQt5Gui.so.5 #9 0x7fde2d8e94ab in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #10 0x7fde27f1696e in ?? ()
[plasmashell] [Bug 450435] Panels missing after unlocking screen when screens have gone to sleep and woken up until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=450435 Reid Swanson changed: What|Removed |Added CC||r...@reidswanson.com --- Comment #44 from Reid Swanson --- I know this is an old report that is marked resolved, but I am having the same problem. About 6 months ago I was having a lot of trouble with NVIDIA and basically any DE. Black screen or completely frozen computer after sleep. I eventually gave up and temporarily went to Windows :-| Of course I couldn't stand it and did a fresh Linux install last week. Most of the serious issues I was having with sleep have apparently been resolved, but the missing panel after sleep has started happening for me. Restarting plasma shell with `plasmashell --replace & disown` will bring the panel back. This is a desktop system with 3 fixed monitors attached by DisplayPort. I have a fixed xorg.conf exported from the NVIDIA settings and I have disabled kscreen2. (Enabling kscreen2 will completely screw up my window positions upon waking from sleep) The base distro is Gentoo using OpenRC. I'm on KDE Plasma Version 5.27.11 KDE Frameworks Version 5.116.0 QT Version 5.15.14 Using X11 I've tried Wayland, but I've encountered worse problems when using it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477887] New: [wayland, plasma 6 beta] cursor jerk/reset in fullscreen game
https://bugs.kde.org/show_bug.cgi?id=477887 Bug ID: 477887 Summary: [wayland, plasma 6 beta] cursor jerk/reset in fullscreen game Classification: Plasma Product: kwin Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: k...@reidwiggins.com Target Milestone: --- SUMMARY I'm trying the new Plasma 6 Beta and I believe I've found a regression. In Final Fantasy XIV (running via XIVLauncher.Core), clicking and dragging with the mouse (which turns the camera), then clicking again, seems to "reset" or "jerk" the camera -- almost as if a mouse movement was "queued up" and sent instantly after the single click? Repro video: https://www.reidwiggins.com/assets/kwin-report-repro-video.webm KWin debug console video (1 reproduction): https://www.reidwiggins.com/assets/kwin-report-log.webm STEPS TO REPRODUCE 1. Run a full screen game that doesn't capture the cursor and uses the mouse to control the camera. (Not sure if this is FFXIV specific or not -- I don't play other games that have this behavior.) 2. Click and drag the mouse, which moves the camera. 3. *Without moving the mouse*, single-click again. Observe camera jerk. OBSERVED RESULT Camera resets wildly to a top down view. (This would be the equivalent of dragging the mouse to the bottom of the screen, ~instantly.) EXPECTED RESULT Camera doesn't move, since a single click doesn't typically move the camera. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.6.3-arch-1-1 KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 Session: Wayland, with NVIDIA 545.29.06 driver Display config: 0,0 1920x1080; 1920,0 3440x1440 (no scaling or rotation) displaying the game Installed via: kde-unstable repo. ADDITIONAL INFORMATION Moving the cursor *at all* after clicking and dragging seems to avoid the bug, which you can see in the repro video. Nonetheless, this bug makes the game effectively unplayable. Additionally: FFXIV in-game System Settings -> Mouse -> "Limit mouse operation to game window" appears to make the bug much harder to reproduce (not impossible), albeit with the cursor now locked to the window. Interestingly, the KWin debug console input log doesn't appear any different with this setting checked. This behavior did not occur in KDE 5.27 (as currently in the main Arch repos). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Reid Wiggins changed: What|Removed |Added CC||k...@reidwiggins.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 462937] New: Kdeveloper doesn't work on OpenSUSE 15.4
https://bugs.kde.org/show_bug.cgi?id=462937 Bug ID: 462937 Summary: Kdeveloper doesn't work on OpenSUSE 15.4 Classification: Applications Product: kdevelop Version: 5.6.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Session support Assignee: kdevelop-bugs-n...@kde.org Reporter: mart...@goldeneraproductions.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. start the program by command line or gui 2. 3. OBSERVED RESULT Nothing happens. So I installed KDevelop on Manjaro, works fine. Tried several different methods and versions. While all other IDEs loaded on OpenSUSE Leap 15.4 work thus far, such as VS Codium, VS Code, Ecliipse C++ version, and SDK version, Code:Blocks, Julpyter Notebook, Eric6, etc, most all of which are installed on Manjaro, KDevelop will not start. No matter how many times installed and what version. EXPECTED RESULT SOFTWARE/OS VERSIONS OpenSUSE Leap 15.4 Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Tried using Plasma DE as well as Cinnamon and also LXQT. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446554] Moving a panel to the left/right sides then back to top/bottom causes margins to stop being applied
https://bugs.kde.org/show_bug.cgi?id=446554 --- Comment #2 from Reid --- (In reply to Nate Graham from comment #1) > Cannot reproduce in current git master; works for me. Did the panel spacer > disappear when you made it horizontal again? I don't see it there. size is reduced to hardly any pixels but it's still there -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446554] New: Moving a panel to the left/right sides then back to top/bottom causes margins to stop being applied
https://bugs.kde.org/show_bug.cgi?id=446554 Bug ID: 446554 Summary: Moving a panel to the left/right sides then back to top/bottom causes margins to stop being applied Product: plasmashell Version: 5.23.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com Target Milestone: 1.0 Created attachment 144264 --> https://bugs.kde.org/attachment.cgi?id=144264=edit bug in action SUMMARY Moving a panel to the left/right sides then back to top/bottom causes margins to stop being applied, moving the panel more, changing themes, or removing and re-adding the margins separators will not fix it, only restarting plasmashell does STEPS TO REPRODUCE 1. move a panel with a margins separator so it goes from a horizontal state to a vertical state 2. move it back to the original position 3. margins are not applied OBSERVED RESULT check attachment EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: Wayland Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445636] The buttons in the colour scheme previews pull their colour from the currently active scheme
https://bugs.kde.org/show_bug.cgi?id=445636 Reid changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445636] The buttons in the colour scheme previews pull their colour from the currently active scheme
https://bugs.kde.org/show_bug.cgi?id=445636 --- Comment #4 from Reid --- (In reply to Nate Graham from comment #3) > Thanks. I can't reproduce the issue when I install that color scheme. Are > you sure you're using Plasma 5.23? What distro are you using? yes I am sure I'm on 5.23, using Arch Linux's builds -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445636] The buttons in the colour scheme previews pull their colour from the currently active scheme
https://bugs.kde.org/show_bug.cgi?id=445636 --- Comment #2 from Reid --- Created attachment 143896 --> https://bugs.kde.org/attachment.cgi?id=143896=edit One such troublesome scheme Added one of the schemes I've observed it with but it seems to happen with any scheme -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445709] Rearranging apps in the task manager is broken
https://bugs.kde.org/show_bug.cgi?id=445709 --- Comment #2 from Reid --- did more testing since I reported this and I wasn't able to reproduce it again My guess: Wayland's design of not letting windows know what keys you're pressing while they're not focused may have caused some buttons getting stuck as "pressed" for the Plasma panel which could've caused this bug, this would also explain why I haven't been able to reproduce it (I just didn't get the button stuck like that again) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 433162] The F-Droid build of KDE Connect doesn't detect nearby devices
https://bugs.kde.org/show_bug.cgi?id=433162 Reid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Reid --- Closing as it got fixed at some point -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445709] Rearranging apps in the task manager is broken
https://bugs.kde.org/show_bug.cgi?id=445709 Reid changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445709] New: Rearranging apps in the task manager is broken
https://bugs.kde.org/show_bug.cgi?id=445709 Bug ID: 445709 Summary: Rearranging apps in the task manager is broken Product: plasmashell Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: this.is.r...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 143701 --> https://bugs.kde.org/attachment.cgi?id=143701=edit vid showing the bug in action SUMMARY The icons in the task manager can't be dragged and rearranged STEPS TO REPRODUCE 1. attempt dnd'ing the icons in the task manager or IOTM 2. 3. OBSERVED RESULT check attached vid EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445636] New: The buttons in the colour scheme previews pull their colour from the currently active scheme
https://bugs.kde.org/show_bug.cgi?id=445636 Bug ID: 445636 Summary: The buttons in the colour scheme previews pull their colour from the currently active scheme Product: systemsettings Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- Created attachment 143656 --> https://bugs.kde.org/attachment.cgi?id=143656=edit Buttons are all using the wrong colour SUMMARY The buttons in the colour scheme previews pull their colour from the currently active scheme STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT check attachment EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 445516] The sliders' nubs in the audio applet have a box around them
https://bugs.kde.org/show_bug.cgi?id=445516 --- Comment #2 from Reid --- (In reply to David Redondo from comment #1) > Is this the plasma breeze theme? yes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445516] New: The sliders' nubs in the audio applet have a box around them
https://bugs.kde.org/show_bug.cgi?id=445516 Bug ID: 445516 Summary: The sliders' nubs in the audio applet have a box around them Product: plasmashell Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 143565 --> https://bugs.kde.org/attachment.cgi?id=143565=edit slider nobs with the boxes SUMMARY The sliders' nubs in the audio applet have a small box around them, visible around the corners STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT see attachment EXPECTED RESULT shouldn't have the boxes SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: Wayland ADDITIONAL INFORMATION *only* affects the audio applet, other -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444035] New: Rearranging favourites in KickOff causes the dragged icon to be misplaced
https://bugs.kde.org/show_bug.cgi?id=444035 Bug ID: 444035 Summary: Rearranging favourites in KickOff causes the dragged icon to be misplaced Product: plasmashell Version: 5.23.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: this.is.r...@tutanota.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142621 --> https://bugs.kde.org/attachment.cgi?id=142621=edit icon being misplaced SUMMARY Rearranging favourites in KickOff causes the dragged icon to be misplaced Looks like the icon will always ends up on the row it was originally on, but always on the first column STEPS TO REPRODUCE 1. rearrange favourite icons in KickOff 2. 3. OBSERVED RESULT check attachment EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #18 from Reid --- the Window Class for the Vivaldi's Picture in Picture rule was set to unimportant instead of Exact Match and that seems to have caused it weird it causes this in Wayland tho -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #16 from Reid --- Created attachment 142437 --> https://bugs.kde.org/attachment.cgi?id=142437=edit kwinrulesrc no active scripts, also happens with fresh kwinrc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #14 from Reid --- Created attachment 142436 --> https://bugs.kde.org/attachment.cgi?id=142436=edit kwinrc here's my kwinrc and since you'll probably mention it: the theme doesn't change anything, both Lightly and Breeze behave the same -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #12 from Reid --- Created attachment 142435 --> https://bugs.kde.org/attachment.cgi?id=142435=edit config files for gwenview, okular, kate, and konsole (+ konsole profile) upon further testing it looks like most KDE apps are affected when launching them with a file as argument like `kate .config/katerc` (any file will do) Konsole is the only one to always do it included the config files for a few apps I've confirmed to be affected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #10 from Reid --- should I provide the config files for the affected apps from my main account? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #9 from Reid --- (In reply to Vlad Zahorodnii from comment #8) > Nope, with two panels, konsole, okular, and gwenview have normal size. Can > you create a new user and check if the initial size issue is present with > the new account? they behave normally in the new account -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443711] panel show/hide animation is broken in Wayland session
https://bugs.kde.org/show_bug.cgi?id=443711 --- Comment #1 from Reid --- seems to not be consistently reproducible... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #7 from Reid --- (In reply to Vlad Zahorodnii from comment #6) > is there anything unorthodox about your setup, e.g. panel being at different > location, etc? do you have window rules set? 2 panels, one full width at the top, one panel configured as a hiding dock at the bottom, some window rules but none for the apps affected by this -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705
--- Comment #5 from Reid ---
(In reply to Vlad Zahorodnii from comment #4)
> [1652733.808] -> xdg_surface@37.set_window_geometry(0, 0, 875, 600)
> [1652733.861] -> xdg_surface@37.ack_configure(810)
> [1652734.567] -> org_kde_kwin_appmenu_manager@25.create(new id
> org_kde_kwin_appmenu@40, wl_surface@23)
> [1652734.636] -> org_kde_kwin_appmenu@40.set_address(":1.404", "/MenuBar/1")
> [1652734.671] -> org_kde_kwin_blur_manager@32.create(new id
> org_kde_kwin_blur@41, wl_surface@23)
> [1652734.709] -> wl_compositor@4.create_region(new id wl_region@42)
> [1652734.736] -> org_kde_kwin_blur@41.set_region(wl_region@42)
> [1652734.756] -> org_kde_kwin_blur@41.commit()
> [1652734.891] -> wl_shm@6.create_pool(new id wl_shm_pool@43, fd 19, 210)
> [1652734.952] -> wl_shm_pool@43.create_buffer(new id wl_buffer@44, 0, 875,
> 600, 3500, 0)
> [1652744.765] -> wl_surface@23.frame(new id wl_callback@45)
> [1652744.840] -> wl_surface@23.attach(wl_buffer@44, 0, 0)
> [1652744.882] -> wl_surface@23.damage(0, 0, 875, 600)
> [1652744.927] -> wl_surface@23.commit()
> [1652744.979] xdg_toplevel@38.configure(1, 1, array)
>
> this one is weird. do you use any scripts?
nope, no scripts
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #3 from Reid --- Created attachment 142430 --> https://bugs.kde.org/attachment.cgi?id=142430=edit log for `WAYLAND_DEBUG=1 gwenview path/to/file` and log for Gwenview another note is it seems like the bug only manifests in Okular and Gwenview when trying to open it with a document right off the getgo, launching them from KickOff or from a terminal without a path to a file won't trigger the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 --- Comment #2 from Reid --- Created attachment 142428 --> https://bugs.kde.org/attachment.cgi?id=142428=edit log for `WAYLAND_DEBUG=1 konsole` log for konsole -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443711] New: panel show/hide animation is broken in Wayland session
https://bugs.kde.org/show_bug.cgi?id=443711 Bug ID: 443711 Summary: panel show/hide animation is broken in Wayland session Product: plasmashell Version: 5.23.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com Target Milestone: 1.0 SUMMARY panel show/hide animation is broken in Wayland session (panel just pops in and out of existence, without an animation) STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443705] New: Various application windows are started with the smallest possible size in Wayland
https://bugs.kde.org/show_bug.cgi?id=443705 Bug ID: 443705 Summary: Various application windows are started with the smallest possible size in Wayland Product: kwin Version: 5.23.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: this.is.r...@tutanota.com Target Milestone: --- SUMMARY Various application windows are started with the smallest possible size in the Wayland session Affected applications I have observed: - Konsole - Gwenview - Okular - qTox chat windows (in multi-window mode, friends list window is unaffected) (some) KDE apps not affected: - Kate - Dolphin - KTorrent - System Settings STEPS TO REPRODUCE 1. log into Plasma Wayland session 2. launch any of the applications listed as affected 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442655] An icon dragged from kickoff cannot be dropped on desktop since Plasma 5.23 beta
https://bugs.kde.org/show_bug.cgi?id=442655 Reid changed: What|Removed |Added CC||this.is.r...@tutanota.com --- Comment #1 from Reid --- Looks like icons don't respond to any sort of dragging anymore, so Favourites become impossible to rearrange and dragging app icons to the desktop or (icons only) task manager becomes impossible as well -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442305] Sliders are sometimes grayed out even when they're not muted
https://bugs.kde.org/show_bug.cgi?id=442305 --- Comment #2 from Reid --- well seems fixed with KF5.86 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442305] Sliders are sometimes grayed out even when they're not muted
https://bugs.kde.org/show_bug.cgi?id=442305 --- Comment #1 from Reid --- nd just as I reported this there's an update: seems to happen at random as well, not only when some sliders are muted and others are not -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442305] Sliders are sometimes grayed out even when they're not muted
https://bugs.kde.org/show_bug.cgi?id=442305 Reid changed: What|Removed |Added Summary|muting a source or output |Sliders are sometimes |sometimes greys out the |grayed out even when |nobs of unmuted sliders |they're not muted -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442305] New: muting a source or output sometimes greys out the nobs of unmuted sliders
https://bugs.kde.org/show_bug.cgi?id=442305 Bug ID: 442305 Summary: muting a source or output sometimes greys out the nobs of unmuted sliders Product: plasma-pa Version: 5.22.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: this.is.r...@tutanota.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 141475 --> https://bugs.kde.org/attachment.cgi?id=141475=edit the nobs are both grayed out and semi-transparent SUMMARY muting a source or output sometimes greys out the nobs of unmuted sources/outputs STEPS TO REPRODUCE 1. have a source and an input in the volume applet (may also work with 2 outputs, couldn't test) 2. mute one and make sure the other is unmuted OBSERVED RESULT see attachment, both nobs are grayed out, can also see a small white line on the unnmuted slider, likely an artifact of the slider being both grayed out and not grayed out EXPECTED RESULT only the muted slider should be grayed out SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 441085] New: Disabling "remember window size" causes Konsole to crash
https://bugs.kde.org/show_bug.cgi?id=441085 Bug ID: 441085 Summary: Disabling "remember window size" causes Konsole to crash Product: konsole Version: 21.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: this.is.r...@tutanota.com Target Milestone: --- SUMMARY Disabling "remember window size" causes Konsole to crash STEPS TO REPRODUCE 1. open Konsole settings 2. Uncheck "Remember window size" and apply 3. launch another konsole window OBSERVED RESULT New window crashes on launch EXPECTED RESULT not supposed to crash ofc SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439309] New: the Media Player plasmoid doesn't clear the player list until all players are closed
https://bugs.kde.org/show_bug.cgi?id=439309 Bug ID: 439309 Summary: the Media Player plasmoid doesn't clear the player list until all players are closed Product: plasmashell Version: 5.22.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: k...@privat.broulik.de Reporter: this.is.r...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY the Media Player plasmoid doesn't clear the player list until all players are closed STEPS TO REPRODUCE 1. open 2 media player and make sure they both get added to the plasmoid 2. close one 3. check the plasmoid OBSERVED RESULT the closed player won't get removed from the list; closing all players will however properly clear the list EXPECTED RESULT players should get removed from the list as they're closed SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439085] New: clipboard applet goes all crazy when the list has a specific length and images are involved
https://bugs.kde.org/show_bug.cgi?id=439085 Bug ID: 439085 Summary: clipboard applet goes all crazy when the list has a specific length and images are involved Product: plasmashell Version: 5.22.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com Target Milestone: 1.0 SUMMARY really can't describe it any better than this: when the clipboard's vertical length is just enough to barely overflow and have a scrollbar and there's an image in the cliboard, the image shrinks to make space for the scrollbars and that causes the length to get just low enough to make the scrollbar not be needed anymore, so it disappears causing the images to get big again which makes the list long enough to overflow again which leads to a never ending cycle STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 ADDITIONAL INFORMATION sorry for the clusterquack of a summary I gave above also proposed solution: make the maximum width for images be what they'd have when shrunk to make space for the scrollbar -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438693] Elisa doesn't properly set the volume if it's set while playback it's stopped
https://bugs.kde.org/show_bug.cgi?id=438693 --- Comment #2 from Reid --- seems to happen specifically when the media is stopped, not paused that seems to consistently reproduce it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439025] New: The system tray doesn't follow the panel opacity
https://bugs.kde.org/show_bug.cgi?id=439025 Bug ID: 439025 Summary: The system tray doesn't follow the panel opacity Product: plasmashell Version: 5.22.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 139591 --> https://bugs.kde.org/attachment.cgi?id=139591=edit bug in action, other plasmoids like KickOff or the Calendar follow the panel, only the tray doesn't SUMMARY The system tray doesn't follow the panel opacity (it's always transparent even when the setting is set to opaque or dynamic with a maximised window present) STEPS TO REPRODUCE 1. set panel opacity to opaque 2. open any panel from the system tray 3. OBSERVED RESULT Tray is still transparent regardless of setting EXPECTED RESULT It's supposed to follow the panel, not sure if this needed to be stated SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432449] Memleak in plasmashell 5.20.5
https://bugs.kde.org/show_bug.cgi?id=432449 Reid changed: What|Removed |Added CC||this.is.r...@tutanota.com --- Comment #15 from Reid --- Confirmed this on 5.20.90, 5.21 and 5.21.1 on Arch as well, doesn't seem to be related to anything 3rd party Might be related to searches to some degree as many successive queries can easily add a full 200MB to `plasmashell`'s usage (on top of its usage after a cold boot), however this might just be coincidental as it doesn't break past 400MB total with searches alone but the leak seems to easily get to almost 1GiB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438565] Mute audio icon appear on all pinned but not running icons when using Pipewire
https://bugs.kde.org/show_bug.cgi?id=438565 --- Comment #3 from Reid --- Update: seems to only happen when there are ALSA clients running -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438693] New: Elisa doesn't properly set the volume if it's set while playback it's stopped
https://bugs.kde.org/show_bug.cgi?id=438693 Bug ID: 438693 Summary: Elisa doesn't properly set the volume if it's set while playback it's stopped Product: Elisa Version: 21.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: this.is.r...@tutanota.com Target Milestone: --- SUMMARY If the volume it's changed while playback it's stopped then it won't be properly applied once playback resumes, it only gets applied if changed while playing STEPS TO REPRODUCE 1. change Elisa's volume while playback is stopped 2. play 3. change volume while playing OBSERVED RESULT song will keep playing at whatever volume was set before playback started, however it will EXPECTED RESULT volume should be properly updated regardless of playback status SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438565] Mute audio icon appear on all pinned but not running icons when using Pipewire
https://bugs.kde.org/show_bug.cgi?id=438565 --- Comment #2 from Reid --- (In reply to Kai Uwe Broulik from comment #1) > Can you post the output of pacmd list-sink-inputs pacmd doesn't exist, probably only a thing on pulseaudio proper and not pipewire-pulse -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438565] New: Mute audio icon appear on all pinned but not running icons when using Pipewire
https://bugs.kde.org/show_bug.cgi?id=438565 Bug ID: 438565 Summary: Mute audio icon appear on all pinned but not running icons when using Pipewire Product: plasmashell Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: this.is.r...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139290 --> https://bugs.kde.org/attachment.cgi?id=139290=edit the bug in action SUMMARY When using Pipewire and there's audio playing all pinned but not running icons get the Mute Audio button STEPS TO REPRODUCE 1. make sure you're using pipewire in place of pulseaudio 2. play media 3. observe the task manager icons OBSERVED RESULT all pinned but not running icons get a "Mute" button EXPECTED RESULT only the apps playing audio should get the mute button SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22 KDE Frameworks Version: 5.82 Qt Version: 5.15.2 ADDITIONAL INFORMATION confirmed this issue on 5.20 and 5.21 as well -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 437766] New: Spectacle consistently segfaults when closed
https://bugs.kde.org/show_bug.cgi?id=437766 Bug ID: 437766 Summary: Spectacle consistently segfaults when closed Product: Spectacle Version: 21.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: this.is.r...@tutanota.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. launch Spectacle 2. close (Alt+F4 or close button on the title bar) OBSERVED RESULT It segfaults EXPECTED RESULT It's not supposed to segfault SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434129] IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window
https://bugs.kde.org/show_bug.cgi?id=434129 --- Comment #10 from Reid --- New update: seems to happen pretty consistently on all but the first virtual desktop, meanwhile Teams seems to not be related with any of it, at least not anymore -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434529] Klipper sometimes doesn't add to clipboard on copy/cut
https://bugs.kde.org/show_bug.cgi?id=434529 --- Comment #4 from Reid --- (In reply to Nate Graham from comment #3) > Is Klipper set to ignore images? That's the default setting, so unless > you've changed it, this would be expected behavior. Can you check in > Klipper's settings window? It's disabled -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434529] Klipper sometimes doesn't add to clipboard on copy/cut
https://bugs.kde.org/show_bug.cgi?id=434529 --- Comment #2 from Reid --- (In reply to Nate Graham from comment #1) > With which apps? Wayland or X11? X11, most commonly observed with Spectacle but it also sometimes happens with other apps when copying images -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 434529] New: Klipper sometimes doesn't add to clipboard on copy/cut
https://bugs.kde.org/show_bug.cgi?id=434529 Bug ID: 434529 Summary: Klipper sometimes doesn't add to clipboard on copy/cut Product: klipper Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com Target Milestone: --- SUMMARY Klipper sometimes doesn't add to clipboard on copy/cut, seems to happen particularly frequently when pictures are involved but they're not a prerequisite for the bug to appear STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434493] New: The color scheme previews sometimes pull some colors from the active scheme
https://bugs.kde.org/show_bug.cgi?id=434493 Bug ID: 434493 Summary: The color scheme previews sometimes pull some colors from the active scheme Product: systemsettings Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com Target Milestone: --- Created attachment 136735 --> https://bugs.kde.org/attachment.cgi?id=136735=edit all previews pull the highlight and view and selection colors from Cinereus Blue (the active scheme) SUMMARY The colorscheme previews sometimes pull the View Background, View Text and Selection Background colors (possibly others as well) from the active scheme instead of the scheme being previewed STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT check attachment EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434129] IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window
https://bugs.kde.org/show_bug.cgi?id=434129 --- Comment #9 from Reid --- (In reply to Nate Graham from comment #8) > Thanks. Are you using a non-default Plasma theme? Any other non-default > settings at all? added a sticky note and memory usage plasmoid, removed the show desktop plasmoid, and using a custom colorscheme, otherwise it's completely stock -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434129] IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window
https://bugs.kde.org/show_bug.cgi?id=434129 --- Comment #7 from Reid --- (In reply to Nate Graham from comment #6) > Cool, thanks for the update. What kind of graphics hardware are you using? Intel UHD -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434129] IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window
https://bugs.kde.org/show_bug.cgi?id=434129 --- Comment #5 from Reid --- (In reply to Nate Graham from comment #4) > OK so compositing being enabled is a factor. That makes me suspect cache > issues even more, since different SVGs are used depending on the compositing > status. Please try clearing the plasma cache and restarting plasmashell the > next time it happens. Thanks! Just managed to reproduce it, turns it out's not related to compositing after all as I disabled the compositor and it's still there Wiping the cache didn't help either -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 434133] The header doesn't disappear when using a per app color scheme without header support
https://bugs.kde.org/show_bug.cgi?id=434133 --- Comment #4 from Reid --- (In reply to Nate Graham from comment #3) > If you open your ~/.config/kdeglobals file, do you see sections in it with > the titles: > > [Colors:Header] > > and > > [Colors:Header][Inactive] Nope, there's nothing there Setting a global color scheme that also doesn't support headers does fix it so I'm positive the issue is Breeze sees a header color in the global scheme and then doesn't bother checking if the app color scheme has a header color and if it doesn't it falls back to using the global color scheme's color for the header instead of hiding the header -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434129] IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window
https://bugs.kde.org/show_bug.cgi?id=434129 --- Comment #3 from Reid --- (In reply to Nate Graham from comment #2) > Whoa, that is weird. Seems like a cache corruption issue. > > Does the issue disappear completely if you clear your plasma cache with `rm > ~/.cache/plasma*`? unfortunately it's not particularly consistent, and might not be related to the cached Plasma theme getting corrupted as last time I managed to trigger the bug it was tied to a single virtual desktops, all others were completely fine Also not sure if it will help much but disabling and reenabling the compositor fixes it for whatever reason (or maybe that was just a coincidence, I don't know as I haven't been able to find a consistent way to reproduce it in order to triage it properly and see what exactly is the trigger So far pretty much the only constant I managed to find is Teams always being around when the bug glitch in -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 434133] The header doesn't disappear when using a per app color scheme without header support
https://bugs.kde.org/show_bug.cgi?id=434133 --- Comment #2 from Reid --- (In reply to Nate Graham from comment #1) > Did you restart your apps after applying these settings? If you do so, does > the line disappear? Restarting does not make the header disappear -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 434133] New: The header doesn't disappear when using a per app color scheme without header support
https://bugs.kde.org/show_bug.cgi?id=434133 Bug ID: 434133 Summary: The header doesn't disappear when using a per app color scheme without header support Product: Breeze Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com CC: noaha...@gmail.com Target Milestone: --- Created attachment 136480 --> https://bugs.kde.org/attachment.cgi?id=136480=edit Header stays when using Breeze Dark globally and BreezeDracula for Kate alone SUMMARY The header doesn't disappear when using a per app color scheme without header support if the global color scheme does support headers STEPS TO REPRODUCE 1. Set a global colorscheme with header support (Breeze Light/Dark) 2. Set a per app color scheme without header support (tested with Kate and Breeze Dracula) 3. OBSERVED RESULT The header stays using the color from the global color scheme (check attachment) EXPECTED RESULT The header should disappear the same way it does with global color schemes without header support SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434129] IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window
https://bugs.kde.org/show_bug.cgi?id=434129 --- Comment #1 from Reid --- Created attachment 136477 --> https://bugs.kde.org/attachment.cgi?id=136477=edit screenshot showing the glitch in action -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434129] New: IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window
https://bugs.kde.org/show_bug.cgi?id=434129 Bug ID: 434129 Summary: IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window Product: plasmashell Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: this.is.r...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY IOTM background glitches out at random, seems to be tied to Teams, possibly other flatpaks too (however I haven't been able to reproduce it with Discord or Telegram so Teams seems the most likely trigger) Also seems to only happen in themes that support the 5.21 margins as I haven't seen this when using old themes that don't support the new margins (No foolproof way to reproduce it unfortunately, just some possible triggers and conditions to let the bug happen) STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT check attachment EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 433162] New: The F-Droid build of KDE Connect doesn't detect nearby devices
https://bugs.kde.org/show_bug.cgi?id=433162 Bug ID: 433162 Summary: The F-Droid build of KDE Connect doesn't detect nearby devices Product: kdeconnect Version: 1.10 Platform: Android OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: this.is.r...@tutanota.com Target Milestone: --- SUMMARY The F-Droid build of KDE Connect doesn't detect nearby devices STEPS TO REPRODUCE 1. install KDE Connect from F-Droid 2. search for other devices OBSERVED RESULT The F-Droid build won't find any devices EXPECTED RESULT SOFTWARE/OS VERSIONS Android: 10 ROM: Havoc-OS 3.9 ADDITIONAL INFORMATION the Play Store build works perfectly fine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433119] New Kickoff doesn't refresh the list of applications to account for removals/additions when 'Applications Updated.'
https://bugs.kde.org/show_bug.cgi?id=433119 Reid changed: What|Removed |Added CC||this.is.r...@tutanota.com --- Comment #5 from Reid --- I have been able to reproduce this, also finding Bug 433151 in the process -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433151] New: Refreshing KickOff's application list twice without changing the category empties the right view
https://bugs.kde.org/show_bug.cgi?id=433151 Bug ID: 433151 Summary: Refreshing KickOff's application list twice without changing the category empties the right view Product: plasmashell Version: 5.21.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: this.is.r...@tutanota.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 135832 --> https://bugs.kde.org/attachment.cgi?id=135832=edit KickOff with an empty right view SUMMARY Refreshing KickOff's application list twice without changing the category empties the right view STEPS TO REPRODUCE 1. open KickOff and keep it open (inside plasmoidviewer or add it to the desktop) 2. update the application list twice without changing the category (in my testing I removed and readded the same icon to ~/.local/share/applications, waiting for Kwin to refresh the application list in between) OBSERVED RESULT KickOff's right view just goes empty, changing categories fixes it however EXPECTED RESULT KickOff should just update the view, adding/removing the icons regardless of how many refreshes there are in the application list SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 432532] New: Elisa displays unneeded scrollbars at the bottom of every non-empty view
https://bugs.kde.org/show_bug.cgi?id=432532 Bug ID: 432532 Summary: Elisa displays unneeded scrollbars at the bottom of every non-empty view Product: elisa Version: 20.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: this.is.r...@tutanota.com Target Milestone: --- Created attachment 135440 --> https://bugs.kde.org/attachment.cgi?id=135440=edit screenshot of unneeded scrollbars SUMMARY Elisa displays unneeded scrollbars at the bottom of every non-empty view (e.g. left sidebar, playlist, main view); empty views (e.g. playlist with no song) are not affected SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432217] New: packagekit backend seems to be broken under X11 on Arch
https://bugs.kde.org/show_bug.cgi?id=432217 Bug ID: 432217 Summary: packagekit backend seems to be broken under X11 on Arch Product: Discover Version: 5.20.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PackageKit Assignee: lei...@leinir.dk Reporter: this.is.r...@tutanota.com CC: aleix...@kde.org Target Milestone: --- SUMMARY the packagekit backend is broken under X11, but works fine in Wayland, might be downstream since Neon isn't affected but still worth mentioning STEPS TO REPRODUCE 1. Log into the X11 Plasma session 2. Launch Discover OBSERVED RESULT Discover will display a toast message about an "unexpected error" for the first packagekit repo: does not happen in Wayland EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux 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.
[plasmashell] [Bug 431925] Meta + number row to select the icon at that position in the task manager doesn't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=431925 --- Comment #2 from Reid --- This bug is pretty weird, works fine here on X and sometimes Wayland too -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431925] New: Meta + number row to select the icon at that position in the task manager doesn't work in Wayland
https://bugs.kde.org/show_bug.cgi?id=431925 Bug ID: 431925 Summary: Meta + number row to select the icon at that position in the task manager doesn't work in Wayland Product: plasmashell Version: 5.20.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: this.is.r...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Meta + number row to select the icon at that position in the task manager doesn't work in Wayland STEPS TO REPRODUCE 1. log into the Wayland session 2. press Meta + number row 3. OBSERVED RESULT The key gets pressed as normal with no shortcut being triggered EXPECTED RESULT The icon on the position of the key on the number row being pressed is supposed to be triggered SOFTWARE/OS VERSIONS Operating System: Arch Linux 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.
[plasmashell] [Bug 431897] Changing some display options causes the plasmoids to stop getting shrunk after a panel separator
https://bugs.kde.org/show_bug.cgi?id=431897 --- Comment #1 from Reid --- ok, update on this, turns out it was the theme I was using -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431897] New: Changing some display options causes the plasmoids to stop getting shrunk after a panel separator
https://bugs.kde.org/show_bug.cgi?id=431897 Bug ID: 431897 Summary: Changing some display options causes the plasmoids to stop getting shrunk after a panel separator Product: plasmashell Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: this.is.r...@tutanota.com Target Milestone: 1.0 SUMMARY Changing the monitor rotation causes the plasmoids to stop getting shrunk after a panel separator, possibly other display settings too STEPS TO REPRODUCE 1. make sure you have a panel separator 2. change the monitor rotation 3. check if the plasmoids after the separator are still shrunk OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux 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.
[Discover] [Bug 431896] New: The package source category header sometimes partially covers the first repo in that category
https://bugs.kde.org/show_bug.cgi?id=431896 Bug ID: 431896 Summary: The package source category header sometimes partially covers the first repo in that category Product: Discover Version: 5.20.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: this.is.r...@tutanota.com CC: aleix...@kde.org Target Milestone: --- Created attachment 135041 --> https://bugs.kde.org/attachment.cgi?id=135041=edit I can't explain it any better than this picture SUMMARY the source category (the header reading Flatpak/distro package/etc) overlaps the first repo in that category sometimes if there are buttons on the header STEPS TO REPRODUCE 1. go in Discover settings page 2. observe the list of sources 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431683] Kate should detach when launched from a terminal
https://bugs.kde.org/show_bug.cgi?id=431683 Reid changed: What|Removed |Added CC||this.is.r...@tutanota.com --- Comment #5 from Reid --- There's nothing really "wrong" with the current behaviour, however I do agree with this changing simply to make things more consistent Currently Kate will detach if there's a running instance but won't if there's no running instance, and that can just throw some users off since the behaviour is just not consistent, or at least not as consistent as it could be, so I can see why some would want the default behaviour changed and move the current behaviour to a flag. -- You are receiving this mail because: You are watching all bug changes.
[kaudiocreator] [Bug 415020] New: audiocd protocol dies reading an enhanced digitally enhanced cd
https://bugs.kde.org/show_bug.cgi?id=415020 Bug ID: 415020 Summary: audiocd protocol dies reading an enhanced digitally enhanced cd Product: kaudiocreator Version: unspecified Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gerdfleisc...@web.de Reporter: fr...@spinn.net Target Milestone: --- SUMMARY audiocd protocol crashed when the cd contains some digital data STEPS TO REPRODUCE 1. any attempt to rip a cd that has some digital data on it as well as the music caused the audiocd protocol to crash. 2. 3. OBSERVED RESULT dies with ripping in the in the jobs window. eventually erroring out. EXPECTED RESULT ripping track SOFTWARE/OS VERSIONS Linux/KDE Plasma: slackware 14.2 kernel 4.4.202 (available in About System) KDE Plasma Version: 4.13.38 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kaudiocreator] [Bug 414836] New: does not work with mp3 encoder
https://bugs.kde.org/show_bug.cgi?id=414836 Bug ID: 414836 Summary: does not work with mp3 encoder Product: kaudiocreator Version: 1.3 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gerdfleisc...@web.de Reporter: fr...@spinn.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. try saving in mpe lame encoder 2. 3. OBSERVED RESULT it creats the directory but no file. It says the encoder is runing forever. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION slackware 14.2 kernel 4.4.202 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414184] Systemsettings5 crash after trying to open Window Appearance menu
https://bugs.kde.org/show_bug.cgi?id=414184 --- Comment #2 from Maxwell Reid --- Created attachment 123952 --> https://bugs.kde.org/attachment.cgi?id=123952=edit New crash information added by DrKonqi systemsettings5 (5.17.3) using Qt 5.13.2 - What I was doing when the application crashed: Trying to open any settings window within the settings manager. Sometimes the settings manager crashes when trying to open one of the settings windows. -- Backtrace (Reduced): #6 0x7efc2a592d8f in QObject::property(char const*) const () at /usr/lib/libQt5Core.so.5 #7 0x7efbe370bed5 in () at /usr/lib/qt/qml/org/kde/kirigami.2/libkirigamiplugin.so #8 0x7efc296809e8 in QQmlObjectCreator::createInstance(int, QObject*, bool) () at /usr/lib/libQt5Qml.so.5 #9 0x7efc2967efd3 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () at /usr/lib/libQt5Qml.so.5 #10 0x7efc2967f71b in QQmlObjectCreator::setupBindings(bool) () at /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414184] Systemsettings5 crash after trying to open Window Appearance menu
https://bugs.kde.org/show_bug.cgi?id=414184 Maxwell Reid changed: What|Removed |Added CC||dicke...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 401042] kate doesn't remember size when resized on second monitor
https://bugs.kde.org/show_bug.cgi?id=401042 Maxwell Reid changed: What|Removed |Added CC||dicke...@outlook.com --- Comment #4 from Maxwell Reid --- I have tested this bug on my dual monitor system. I am seeing the exact same behaviour as shown in the video. Two colleagues of mine who also use KDE can confirm this bug also. This bug occurs with other KDE applications (such as Dolphin and Okular) too, not just Kate. In my case, my primary montior is to the right of my secondary monitor. This means that I have to move a window to my secondary monitor and resize it there before it will remember that size the next time I start it. This interrupts my workflow and makes the desktop unpleasant to work with. I switched the positions of my monitors in KDE's settings (the primary monitor is now to the left of the secondary monitor) and the behaviour is now reversed: window sizes are only remembered when changed on the primary (left) monitor. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182838] Facebook tool does not work any more
https://bugs.kde.org/show_bug.cgi?id=182838 --- Comment #25 from Ben Reid --- Have you had any word from Facebook on the app review yet? I'd still like access to my previously uploaded albums, but that needs the API key to be in public mode again. Thanks, Ben -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 182838] Facebook tool does not work any more
https://bugs.kde.org/show_bug.cgi?id=182838 Ben Reid changed: What|Removed |Added CC||kdeb...@benreid.net --- Comment #21 from Ben Reid --- Maik As far as I can tell, while the API key is in development mode, all albums published by Digikam are no longer visible in Facebook except to specific test users (which would include yourself, I assume, so this may not be obvious to you). For some of us who have uploaded a lot of photos via Digikam this is a more significant issue than the inability to upload new albums directly. The latter problem can be worked around by exporting to file system and doing manual uploads for now until the OAuth2 version is ready. Hopefully the albums will return to visible when the API key is restored to production mode. Is there any way to expedite this please? Many thanks, Ben Reid -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 340267] Plasma crashes when a DisplayPort monitor sleeps
https://bugs.kde.org/show_bug.cgi?id=340267 David Reid <dlr...@gmail.com> changed: What|Removed |Added CC||dlr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366207] no desktop background, no contextmenu on desktop after login or when screens wakeup
https://bugs.kde.org/show_bug.cgi?id=366207 David Reid <dlr...@gmail.com> changed: What|Removed |Added CC||dlr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344706] KMenu won't show sometimes (multi-monitor setup)
https://bugs.kde.org/show_bug.cgi?id=344706 David Reid <dlr...@gmail.com> changed: What|Removed |Added CC||dlr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
