[systemsettings] [Bug 467523] New: Screen Energy Saving duration not remembered
https://bugs.kde.org/show_bug.cgi?id=467523 Bug ID: 467523 Summary: Screen Energy Saving duration not remembered Classification: Applications Product: systemsettings Version: 5.27.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quinten0...@protonmail.com Target Milestone: --- Created attachment 157388 --> https://bugs.kde.org/attachment.cgi?id=157388&action=edit The setting as described in this issue. The Screen Energy Saving setting is disabled but the user defined duration value is visible. This will revert to 10 minutes upon re-opening System Setting. SUMMARY The Screen Energy Saving duration will not be saved when the setting as a whole has been turned off. STEPS TO REPRODUCE 1. Open the System Settings application and navigate to Power Management --> Energy Saving (default tab) 2. Enable Screen Energy Saving (first setting) and change the duration from the default (10m) to another value (e.g. 1m) 3. Apply settings 4. Disable Screen Energy Saving (do not change the duration from your custom value) 5. Apply settings 6. Observe how the (now greyed-out) duration is still set to your custom value (e.g. 1m) 7. Close system settings 8. Re-open the Systems Settings application and navigate back to the Power Management tab (see step 1) 9. Observe how the (still greyed-out) duration has been reset to its default value of 10 minutes OBSERVED RESULT See step 9. The custom duration will not be saved upon re-opening System Settings if the Screen Energy Saving option is disabled. EXPECTED RESULT The custom duration, as inputted and applied by the user, should be kept. Even if the setting as a whole has been toggled off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux kernel 6.2.6-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Using EndeavourOS, an Arch derivative. Applied the `general` component as I was unable to find exactly which component this applies to. Feel free to move to the correct component. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 489515] New: Elisa crashes deep in TagLib on song change
https://bugs.kde.org/show_bug.cgi?id=489515
Bug ID: 489515
Summary: Elisa crashes deep in TagLib on song change
Classification: Applications
Product: Elisa
Version: 24.05.1
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: quinten@quinten.space
Target Milestone: ---
Application: elisa (24.05.1)
Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.9.5-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.1.0 [CoredumpBackend]
-- Information about the crash:
Elisa crashed when I tried to change songs by clicking 'play' on an album.
The crash seems to be in TagLib, and I've seen crashes in taglib before.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Elisa (elisa), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/elisa...
[New LWP 315591]
[New LWP 300335]
[New LWP 300341]
[New LWP 300334]
[New LWP 300333]
[New LWP 300336]
[New LWP 300343]
[New LWP 300347]
[New LWP 300351]
[New LWP 300345]
[New LWP 300344]
[New LWP 315590]
[New LWP 300353]
[New LWP 300352]
[New LWP 315586]
[New LWP 315585]
[New LWP 314833]
[New LWP 315584]
[New LWP 300354]
[New LWP 314831]
[New LWP 315582]
[New LWP 314832]
[New LWP 315583]
[New LWP 315593]
Downloading separate debug info for /usr/lib/libQt6Widgets.so.6...
Downloading separate debug info for /usr/lib/libQt6QuickControls2.so.6...
Downloading separate debug info for /usr/lib/libQt6Quick.so.6...
Downloading separate debug info for /usr/lib/libQt6Qml.so.6...
Downloading separate debug info for /usr/lib/libQt6Gui.so.6...
Downloading separate debug info for /usr/lib/libQt6Core.so.6...
Downloading separate debug info for /usr/lib/libQt6Multimedia.so.6...
Downloading separate debug info for /usr/lib/libQt6Sql.so.6...
Downloading separate debug info for /usr/lib/libQt6DBus.so.6...
Downloading separate debug info for /usr/lib/libQt6QuickTemplates2.so.6...
Downloading separate debug info for /usr/lib/libQt6QmlModels.so.6...
Downloading separate debug info for /usr/lib/libQt6Network.so.6...
Downloading separate debug info for /usr/lib/libQt6OpenGL.so.6...
Downloading separate debug info for /usr/lib/libb2.so.1...
Downloading separate debug info for /usr/lib/libQt6Core5Compat.so.6...
Downloading separate debug info for /usr/lib/libQt6Xml.so.6...
Downloading separate debug info for /usr/lib/libQt6PrintSupport.so.6...
Downloading separate debug info for /usr/lib/libQt6WaylandClient.so.6...
Downloading separate debug info for /usr/lib/libvorbisfile.so.3...
Downloading separate debug info for /usr/lib/libvorbisenc.so.2...
Downloading separate debug info for /usr/lib/libvorbis.so.0...
Downloading separate debug info for
/usr/lib/qt6/plugins/platforms/libqwayland-generic.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/wayland-shell-integration/libxdg-shell.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/wayland-graphics-integration-client/../../../libQt6WaylandEglClientHwIntegration.so.6...
Downloading separate debug info for /usr/lib/libEGL_nvidia.so.0...
Downloading separate debug info for /usr/lib/libnvidia-glsi.so.550.90.07...
Downloading separate debug info for /usr/lib/libdrm.so.2...
Downloading separate debug info for /usr/lib/libnvidia-eglcore.so.550.90.07...
Downloading separate debug info for /usr/lib/libnvidia-gpucomp.so.550.90.07...
Downloading separate debug info for /usr/lib/libnvidia-egl-gbm.so.1...
Downloading separate debug info for /usr/lib/libgbm.so.1...
Downloading separate debug info for /usr/lib/libEGL_mesa.so.0...
Downloading separate debug info for /usr/lib/libglapi.so.0...
Downloading separate debug info for
/usr/lib/qt6/qml/QtCore/libqtqmlcoreplugin.so...
Downloading separate debug info for
/usr/lib/qt6/qml/QtCore/../../../libQt6QmlCore.so.6...
Downloading separate debug info for
/usr/lib/qt6/qml/QtQml/WorkerScript/libworkerscriptplugin.so...
Downloading separate debug info for
/usr/lib/qt6/qml/QtQml/WorkerScript/../../../../libQt6QmlWorkerScript.so.6...
Downloading separate debug info for
/usr/lib/qt6/qml/QtQuick/Controls/libqtquickcontrols2plugin.so...
Downloading separate debug info for
/usr/lib/qt6/qml/QtQuick/Controls/Fusion/libqtquickcontrols2fusionstyleplugin.so...
Downloading separate debug info for
/usr/lib/qt6/qml/QtQuick/Controls/Fusion/../../../../../libQt6QuickControls2Fusion.so.6...
Downloading separate debug info for
/usr/lib/qt6/qml/QtQuick/Controls/Basic/libqtquickcontrols2basicstyleplugin.so...
Downloading separate debug info for
/usr/lib/qt6/q
[systemsettings] [Bug 478266] New: Titlebar Actions do not affect CSD GTK applications
https://bugs.kde.org/show_bug.cgi?id=478266 Bug ID: 478266 Summary: Titlebar Actions do not affect CSD GTK applications Classification: Applications Product: systemsettings Version: 5.27.9 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_kwinoptions Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space CC: plasma-b...@kde.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 *** Gnome applications with CSDs are not affected by changing the settings in Titlebar Actions. This makes sense, however: Gnome allows customizing the behaviour of titlebar actions too, and when you change them in Gnome (via e.g. gnome-tweaks) they also affect GTK CSDs. It would be nice if the KCM was able to configure this, whether automatically synced or not. Automatic syncing is probably undesirable for various reasons, not in the least that Gnome's options are less flexible. But adding these options to the KCM might be nice, so that a user can easily change the GTK CSD behaviour (similarly to how the Application Style KCM can change the GTK style). STEPS TO REPRODUCE 1. Change Titlebar actions to e.g. minimize on middle click. 2. Open a GTK app with CSD 3. Try to use the modified shortcut OBSERVED RESULT Default (GNOME) behaviour EXPECTED RESULT Either customized KDE behaviour, or having an option to customize the GTK behaviour. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482583] New: Vi folding commands
https://bugs.kde.org/show_bug.cgi?id=482583 Bug ID: 482583 Summary: Vi folding commands Classification: Applications Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Vi Input Mode Assignee: kwrite-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY Kate folding does not seem to be supported by corresponding vi commands in the vi input mode (e.g. zc/zo commands) STEPS TO REPRODUCE 1. Open a document with folds 2. See that it can be folded with the arrows in the left sidebar 3. Ensure you are in vi mode (normal) 4. Put cursor inside foldable block 5. Type zc (for example) OBSERVED RESULT Nothing happens EXPECTED RESULT Block folds up SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 24.04.70 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482589] New: Middle click to remove workspace does not work in new Overview desktop grid
https://bugs.kde.org/show_bug.cgi?id=482589 Bug ID: 482589 Summary: Middle click to remove workspace does not work in new Overview desktop grid Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY The Desktop Grid part of the new Overview does not allow managing workspaces (e.g. adding or deleting them). STEPS TO REPRODUCE 1. Open desktop grid (Meta+G or 4 finger swipe down) 2. Middle click a desktop OBSERVED RESULT Nothing happens. There are also no buttons to add/remove desktops. EXPECTED RESULT Desktop should close. Additionally I would maybe expect a button that creates a new desktop, similar to the 'primary' overview screen SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482589] Middle-click to remove virtual desktop on grid view, just like in window view
https://bugs.kde.org/show_bug.cgi?id=482589 --- Comment #3 from Quinten Kock --- Oh yeah, I just noticed I can close windows by middle clicking on them from the desktop grid. That may be a problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483197] New: Konsole's cursor has artifacts when using Qt6 scaling
https://bugs.kde.org/show_bug.cgi?id=483197 Bug ID: 483197 Summary: Konsole's cursor has artifacts when using Qt6 scaling Classification: Applications Product: konsole Version: 24.02.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: quinten@quinten.space Target Milestone: --- Created attachment 166933 --> https://bugs.kde.org/attachment.cgi?id=166933&action=edit Uneven block cursor edges at 150% SUMMARY The block cursor in my Konsole window looks offensively bad at scale factors like 150% and 200%, especially when the window is not focused. STEPS TO REPRODUCE 1. Set the scaling factor to e.g. 150% or 200%. Other factors like 125% also seem to give weird results. 2. Open Konsole. 3. Defocus its window. OBSERVED RESULT The block cursor outline is deformed (at 150%, the edges are uneven). EXPECTED RESULT Nice, even & sharp block cursor outline SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Graphics platform: Wayland Display driver: NVIDIA 535.154.05 (RTX 2070) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483197] Konsole's cursor has artifacts when using Qt6 scaling
https://bugs.kde.org/show_bug.cgi?id=483197 --- Comment #1 from Quinten Kock --- Created attachment 166934 --> https://bugs.kde.org/attachment.cgi?id=166934&action=edit Randomly rounded corners at 200% -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483198] New: Fractional scaling causes 'disruption' in window edge
https://bugs.kde.org/show_bug.cgi?id=483198 Bug ID: 483198 Summary: Fractional scaling causes 'disruption' in window edge Classification: I don't know Product: kde Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY While reporting https://bugs.kde.org/show_bug.cgi?id=483197, I noticed another anomaly: the titlebar (window decoration) edge is different from the actual window edge. I'm guessing this is an issue with KWin or Breeze, but I am unsure. STEPS TO REPRODUCE 1. Set scaling factor to 150% (other factors might also be broken) 2. Look at top right corner of window OBSERVED RESULT Nice continuous edge EXPECTED RESULT Edge suddenly changes in thickness SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Graphics platform: Wayland Graphics driver: NVIDIA proprietary 535.154.05 (RTX 2070) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483287] New: Plasma behaves weirdly and sometimes even crashes when moving applets from desktop to panel
https://bugs.kde.org/show_bug.cgi?id=483287 Bug ID: 483287 Summary: Plasma behaves weirdly and sometimes even crashes when moving applets from desktop to panel Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space Target Milestone: 1.0 Application: plasmashell (6.0.1) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.8-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.1 [CoredumpBackend] -- Information about the crash: STEPS TO REPRODUCE: 0. Have panel on the bottom 1. Put clock widget on desktop 2. Move it to panel 3. Open it 4. Without closing it, open another panel popup (e.g. volume) by clicking it EXPECTED RESULT: Identical to what happens when the widget was on the panel all along OBSERVED RESULT: After step 3, the calendar popup is misplaced. It is at the top of the screen, instead of the bottom. After step 4, Plasma crashes. The backtrace should be automatically attached by DrKonqi. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 QSGGeometryNode::activeMaterial (this=0x0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/scenegraph/coreapi/qsgnode.cpp:987 #6 QSGBatchRenderer::Renderer::prepareRenderMergedBatch (this=0x7bfb9016a4d0, batch=0x7bfb905c6fc0, renderBatch=0x7bfbb9bff8f0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3092 #7 0x7bfc65a6c3d5 in QSGBatchRenderer::Renderer::prepareRenderPass (this=this@entry=0x7bfb9016a4d0, ctx=ctx@entry=0x7bfb9016a818) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3771 #8 0x7bfc65a6d7e6 in QSGBatchRenderer::Renderer::render (this=0x7bfb9016a4d0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3532 #9 QSGBatchRenderer::Renderer::render (this=0x7bfb9016a4d0) at /usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3525 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483287] Plasma behaves weirdly and sometimes even crashes when moving applets from desktop to panel
https://bugs.kde.org/show_bug.cgi?id=483287 --- Comment #1 from Quinten Kock --- Created attachment 166983 --> https://bugs.kde.org/attachment.cgi?id=166983&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483198] Fractional scaling causes 'disruption' in window edge
https://bugs.kde.org/show_bug.cgi?id=483198 --- Comment #2 from Quinten Kock --- Created attachment 166986 --> https://bugs.kde.org/attachment.cgi?id=166986&action=edit Screenshot showing the issue (look closely at the top right window corner) Is this really a dup? The linked issue seems related to the window getting the wrong size. Here the window has the correct size, but within the window there is an artifact visible. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473679] Pinch to zoom with touchpad
https://bugs.kde.org/show_bug.cgi?id=473679 Quinten Kock changed: What|Removed |Added CC||quinten@quinten.space --- Comment #5 from Quinten Kock --- I would also like this feature. IIRC Gwenview already has it, would it be possible to reuse any code from there? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475682] New window overview seems to have minor scaling artifacts
https://bugs.kde.org/show_bug.cgi?id=475682 --- Comment #10 from Quinten Kock --- Created attachment 165794 --> https://bugs.kde.org/attachment.cgi?id=165794&action=edit Behaviour after relevant commit I tried the most recent Neon Unstable (20240211) which should have the relevant commit. It looks a lot better now, the text doesn't look bad anymore and the close button is now also nice and uniform. It does however seem like the icons are slightly blurry? Looking at the system settings icon for example, it seems the blue slider bars aren't as sharp as they should be when compared to the same icon elsewhere. I don't know how WindowHeap handles icon sizes though, so I don't know if this behavior is unexpected, or even fixable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481313] New: Notifications widget: Right click -> do not disturb
https://bugs.kde.org/show_bug.cgi?id=481313 Bug ID: 481313 Summary: Notifications widget: Right click -> do not disturb Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY On the panel's notifications widget, it would be nice if there was a checkmark or similar widget for enabling/disabling do not disturb, similar to what happens on middle click. (Similarly to how there is a mute checkmark when right-clicking the volume widget). STEPS TO REPRODUCE 1. Right click notification widget in system tray OBSERVED RESULT Only options are "Clear" and "Configure" EXPECTED RESULT Also have an option for enabling do not disturb SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481533] New: Some pinned popups move weirdly when floating panel defloats
https://bugs.kde.org/show_bug.cgi?id=481533 Bug ID: 481533 Summary: Some pinned popups move weirdly when floating panel defloats Classification: Plasma Product: plasmashell Version: 5.93.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY When the panel is floating and defloats, an open popup should move smoothly to 'attach' to the panel. Some popups (e.g. Audio Volume) do this, but others don't (e.g. Media Player). STEPS TO REPRODUCE 1. Open and pin Media Player popup 2. Make panel defloat by moving window to it OBSERVED RESULT Popup 'jumps' around EXPECTED RESULT Popup moves smoothly with panel, like happens when you pin the Audio Volume popup instead. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Graphics Platform: Wayland Graphics Driver: Nvidia 545.29.06-r1 (RTX 2070) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453109] Allow scrolling in the overview to switch between virtual desktops
https://bugs.kde.org/show_bug.cgi?id=453109 Quinten Kock changed: What|Removed |Added CC||quinten@quinten.space --- Comment #12 from Quinten Kock --- I think this would be a very useful addition also as of Plasma 6. Currently there is no way to use only the mouse to switch between virtual desktops, nor is there any ergonomic 'left-handed' shortcut like Meta+Tab is for toggling the overview. On my laptop I can nicely switch between desktops by using a 3/4-finger swipe, but it would be nice if there was a similarly easy way on desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485656] New: Media player seek bar stops updating sometimes
https://bugs.kde.org/show_bug.cgi?id=485656 Bug ID: 485656 Summary: Media player seek bar stops updating sometimes Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Media Player Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY The seekbar in the media player applet stops updating sometimes. It doesn't seem related to the player (Elisa) having issues, since the seekbar on my phone (KDE Connect) is fine. STEPS TO REPRODUCE 1. ?? 2. ?? 3. ?? OBSERVED RESULT Seekbar in media player applet is stuck on a specific time (e.g. 2:23) and is only updated when moved within the applet, or changing track. EXPECTED RESULT Seekbar in media player follows the playing media and is affected by seeks from other sources. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION No idea how to reproduce, but IIRC has also occurred previously on my machine(s). -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 486630] New: Elisa crashed on song change
https://bugs.kde.org/show_bug.cgi?id=486630 Bug ID: 486630 Summary: Elisa crashed on song change Classification: Applications Product: Elisa Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: quinten@quinten.space Target Milestone: --- Application: elisa (24.02.2) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.8.8-300.fc40.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora Linux 40 (KDE Plasma)" DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: I clicked a different song to play and Elisa crashed. Unfortunately I'm not too sure what the precise cause/conditions were, but maybe the backtrace is helpful :) The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7fc25ffd0e8f in std::default_delete::operator() (this=, __ptr=0x7fc1b000b020, this=, __ptr=) at /usr/include/c++/14/bits/unique_ptr.h:87 #6 std::__uniq_ptr_impl >::reset (this=0x55fc8b9926b0, __p=0x0, this=, __p=) at /usr/include/c++/14/bits/unique_ptr.h:205 #7 std::unique_ptr >::reset (this=0x55fc8b9926b0, __p=0x0) at /usr/include/c++/14/bits/unique_ptr.h:503 #8 QFFmpeg::AudioRenderer::updateOutput (this=0x55fc8b9925a0, codec=0x7fc1b804be98) at /usr/src/debug/qt6-qtmultimedia-6.7.0-1.fc40.x86_64/src/plugins/multimedia/ffmpeg/playbackengine/qffmpegaudiorenderer.cpp:215 #9 QFFmpeg::AudioRenderer::renderInternal (this=0x55fc8b9925a0, frame=...) at /usr/src/debug/qt6-qtmultimedia-6.7.0-1.fc40.x86_64/src/plugins/multimedia/ffmpeg/playbackengine/qffmpegaudiorenderer.cpp:96 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484827] New: Overview should close when activating an app
https://bugs.kde.org/show_bug.cgi?id=484827 Bug ID: 484827 Summary: Overview should close when activating an app Classification: Plasma Product: kwin Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY When the overview is open, it should close when an application is activated via e.g. Meta+0-9. Currently, KWin goes to the correct virtual desktop, and it focuses/minimizes the application. STEPS TO REPRODUCE 1. Open the overview (Meta+W) 2. Focus an application with Meta+Num OBSERVED RESULT KWin goes to the window's workspace and focuses the window, minimizes the window, or starts the application as if the overview was not open. EXPECTED RESULT I would expect KWin to focus the window or start the application, and close the overview. This way I can immediately use the application I tried to focus/start via Meta+Num. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 482583] Vi folding commands
https://bugs.kde.org/show_bug.cgi?id=482583 Quinten Kock changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Quinten Kock --- PR was merged, so this is fixed in KTextEditor (although it's not very complete, and probably mismatches vim behavior in some ways). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483557] Right clicking on panel when not focused on the desktop after switching monitors causes the context menu to open in a window
https://bugs.kde.org/show_bug.cgi?id=483557 Quinten Kock changed: What|Removed |Added CC||quinten@quinten.space --- Comment #3 from Quinten Kock --- I'm currently experiencing a similar issue, although it could also be related to switching monitors as well. However, my panel is fine. But my desktop is not! When the desktop itself is focused and I right-click on it, everything is fine. But when a window is focused, right-clicking the desktop causes the menu to appear. After restarting the shell, it was indeed fixed. Switching back and forth again causes it to reappear. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483865] New: Magic Lamp has gap with floating panel position
https://bugs.kde.org/show_bug.cgi?id=483865 Bug ID: 483865 Summary: Magic Lamp has gap with floating panel position Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY The Magic Lamp effect is disconnected from the task manager entry when the panel is floating. This looks odd. STEPS TO REPRODUCE 1. Have a floating panel 2. Enable the Magic Lamp effect 3. Minimize a window OBSERVED RESULT The animation does not line up with the icon on the panel, instead 'starting' with some margin above it. (Same gap as what you see when selecting on the desktop with a floating panel, which I'm also not sure is intended/optimal?) EXPECTED RESULT No gap between bottom of magic lamp animation and task manager icon SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Kind of the inverse of bug 466177 from Plasma 5? Reported under General as I'm not sure this is an issue in Plasmashell or KWin. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 483870] New: Kate crashed randomly (seemingly in diagnostics?)
https://bugs.kde.org/show_bug.cgi?id=483870
Bug ID: 483870
Summary: Kate crashed randomly (seemingly in diagnostics?)
Classification: Applications
Product: kate
Version: 24.02.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: quinten@quinten.space
Target Milestone: ---
Application: kate (24.02.0)
Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.9-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.2 [CoredumpBackend]
-- Information about the crash:
Kate crashed unexpectedly. I was writing C++ using the clangd language server.
According to the backtrace, the issue seems to live somewhere in the
diagnostics stuff.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/kate...
[New LWP 20240]
[New LWP 20248]
[New LWP 24837]
[New LWP 24841]
[New LWP 20247]
[New LWP 20242]
[New LWP 24834]
[New LWP 24839]
[New LWP 24838]
[New LWP 24842]
[New LWP 20250]
[New LWP 24835]
[New LWP 20249]
[New LWP 24836]
Downloading separate debug info for /usr/lib/libkateprivate.so.24.02.0...
Downloading separate debug info for /usr/lib/libKF6TextEditor.so.6...
Downloading separate debug info for /usr/lib/libKF6TextWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6UserFeedbackWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6Parts.so.6...
Downloading separate debug info for /usr/lib/libKF6SyntaxHighlighting.so.6...
Downloading separate debug info for /usr/lib/libKF6UserFeedbackCore.so.6...
Downloading separate debug info for /usr/lib/libicui18n.so.74...
Downloading separate debug info for /usr/lib/libicuuc.so.74...
Downloading separate debug info for /usr/lib/libb2.so.1...
Downloading separate debug info for /usr/lib/libeditorconfig.so.0...
Downloading separate debug info for /usr/lib/libQt6TextToSpeech.so.6...
Downloading separate debug info for /usr/lib/libKF6SonnetUi.so.6...
Downloading separate debug info for /usr/lib/libicudata.so.74...
Downloading separate debug info for /usr/lib/libQt6Multimedia.so.6...
Downloading separate debug info for /usr/lib/libpulse.so.0...
Downloading separate debug info for /usr/lib/libpsl.so.5...
Downloading separate debug info for
/usr/lib/pulseaudio/libpulsecommon-17.0.so...
Downloading separate debug info for /usr/lib/libvorbisfile.so.3...
Downloading separate debug info for /usr/lib/libsndfile.so.1...
Downloading separate debug info for /usr/lib/libasyncns.so.0...
Downloading separate debug info for /usr/lib/libvorbis.so.0...
Downloading separate debug info for /usr/lib/libogg.so.0...
Downloading separate debug info for /usr/lib/libvorbisenc.so.2...
Downloading separate debug info for /usr/lib/libFLAC.so.12...
Downloading separate debug info for /usr/lib/libopus.so.0...
Downloading separate debug info for /usr/lib/libmpg123.so.0...
Downloading separate debug info for /usr/lib/libmp3lame.so.0...
Downloading separate debug info for /usr/lib/libEGL_mesa.so.0...
Downloading separate debug info for /usr/lib/libgbm.so.1...
Downloading separate debug info for /usr/lib/libglapi.so.0...
Downloading separate debug info for /usr/lib/dri/iris_dri.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/iconengines/libqsvgicon.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/katefiletreeplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/katesearchplugin.so...
Downloading separate debug info for /usr/lib/libQt6Concurrent.so.6...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/kateprojectplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/externaltoolsplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/katekonsoleplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/lspclientplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/tabswitcherplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/textfilterplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/ktexteditor/kategitblameplugin.so...
Downloading separate debug info for
/usr/lib/qt6/plugins/kf6/parts/konsolepart.so...
Downloading separate debug info for /usr/lib/libkonsoleprivate.so.24.02.0...
Downloading separate debug info for /usr/lib/libKF6NewStuffWidgets.so.6...
Downloading separate debug info for /usr/lib/libKF6NewStuffCore.so.6...
Downloading separate debug info for /usr/lib/libKF6Pty.so.6...
Downloading separate debug info fo
[kcachegrind] [Bug 483973] New: KCacheGrind crashes when opening history menu
https://bugs.kde.org/show_bug.cgi?id=483973 Bug ID: 483973 Summary: KCacheGrind crashes when opening history menu Classification: Developer tools Product: kcachegrind Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: josef.weidendor...@gmx.de Reporter: quinten@quinten.space Target Milestone: --- SUMMARY When opening the history menu in KCacheGrind (to navigate between functions, the Back on the toolbar), it crashes. STEPS TO REPRODUCE 1. Open a file 2. Change the viewed function 3. Click the arrow next to Back in the toolbar OBSERVED RESULT Crash EXPECTED RESULT A nice history of what functions I've looked at SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 483973] KCacheGrind crashes when opening history menu
https://bugs.kde.org/show_bug.cgi?id=483973
--- Comment #1 from Quinten Kock ---
Backtrace from the segfaulted thread. It seems to be clearing a NULL menu:
Thread 1 (Thread 0x71a1d9c0 (LWP 112356) "kcachegrind"):
#0 QMenu::clear (this=this@entry=0x0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qmenu.cpp:2220
acts = {> =
{> = {}, }, d
= {d = 0x5568e700, ptr = 0x77158d06
, size = 140737488340400}}
#1 0x5558985e in TopLevel::backAboutToShow (this=0x5584d100) at
/usr/src/debug/kcachegrind/kcachegrind-24.02.0/kcachegrind/toplevel.cpp:2127
#2 0x76190ca9 in QtPrivate::QSlotObjectBase::call (a=0x7fffc688,
r=0x5584d100, this=0x559e9540, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433
#3 doActivate (sender=0x559aa340, signal_index=7,
argv=0x7fffc688) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039
#4 0x772b6545 in QMenu::aboutToShow (this=0x559aa340) at
/usr/src/debug/qt6-base/build/src/widgets/Widgets_autogen/include/moc_qmenu.cpp:352
#5 QMenuPrivate::popup(QPoint const&, QAction*, std::function) (this=this@entry=0x559edce0, p=..., atAction=atAction@entry=0x0,
positionFunction=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qmenu.cpp:2368
#6 0x772b73e0 in QMenuPrivate::exec(QPoint const&, QAction*,
std::function) (this=0x559edce0, p=..., action=0x0,
positionFunction=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qmenu.cpp:2655
#7 0x7732a5df in QToolButtonPrivate::popupTimerDone
(this=0x55dbd1c0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qtoolbutton.cpp:776
#8 0x7732a9fa in QToolButton::showMenu (this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qtoolbutton.cpp:667
#9 0x7732acc2 in QToolButton::mousePressEvent (this=0x55d6a9e0,
e=0x7fffcef0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qtoolbutton.cpp:569
#10 0x77144fb2 in QWidget::event (this=0x55d6a9e0,
event=0x7fffcef0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidget.cpp:8955
#11 0x770f438b in QApplicationPrivate::notify_helper
(this=this@entry=0x5568f0a0, receiver=receiver@entry=0x55d6a9e0,
e=e@entry=0x7fffcef0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296
#12 0x770f6be8 in QApplication::notify (this=,
receiver=0x55d6a9e0, e=0x7fffcef0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2782
#13 0x76139818 in QCoreApplication::notifyInternal2
(receiver=0x55d6a9e0, event=0x7fffcef0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121
#14 0x7613986d in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1553
#15 0x770f2327 in QApplicationPrivate::sendMouseEvent
(receiver=0x55d6a9e0, event=0x7fffcef0, alienWidget=0x55d6a9e0,
nativeWidget=0x5584d100, buttonDown=, lastMouseReceiver=...,
spontaneous=true, onlyDispatchEnterLeave=false) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2366
#16 0x77157a97 in QWidgetWindow::handleMouseEvent (this=0x55847a00,
event=event@entry=0x7fffd260) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidgetwindow.cpp:653
#17 0x77158db0 in QWidgetWindow::event (this=0x55847a00,
event=0x7fffd260) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidgetwindow.cpp:267
#18 0x770f438b in QApplicationPrivate::notify_helper (this=, receiver=0x55847a00, e=0x7fffd260) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296
#19 0x76139818 in QCoreApplication::notifyInternal2
(receiver=0x55847a00, event=0x7fffd260) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121
#20 0x7613986d in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1553
#21 0x7676f9e5 in QGuiApplicationPrivate::processMouseEvent
(e=0x5630e110) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qguiapplication.cpp:2325
#22 0x767da85c in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qwindowsysteminterface.cpp:1109
#23 0x76bb26c4 in userEventSourceDispatch (source=) at
/usr/src/debug/qt
[kcachegrind] [Bug 483973] KCacheGrind crashes when opening history menu
https://bugs.kde.org/show_bug.cgi?id=483973 Quinten Kock changed: What|Removed |Added Status|NEEDSINFO |REPORTED Platform|Other |Arch Linux Resolution|WAITINGFORINFO |--- --- Comment #3 from Quinten Kock --- The backtrace is from my Arch Linux system, but I can also reproduce from Gentoo. Both the repo version and kdesrc-build seem to suffer from the issue. It's probably a regression from the Qt6 upgrade, because I think it used to work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475682] New window overview seems to have minor scaling artifacts
https://bugs.kde.org/show_bug.cgi?id=475682 --- Comment #4 from Quinten Kock --- Created attachment 165552 --> https://bugs.kde.org/attachment.cgi?id=165552&action=edit Issue shown on Neon unstable Are you sure? I tried Neon unstable 20240201, and the issue still seems to appear. In this picture, it can be seen by the top edge of the close button being 'thinner' than the other edges. That definitely looks like a scaling artifact to me. Maybe it's only really visible/noticeable on a low res screen, like my 1366x768 laptop? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407361] Notifications in the history lack interactive features that are in their pop-ups (click on body to jump to app, clickable buttons, draggable images, etc)
https://bugs.kde.org/show_bug.cgi?id=407361 Quinten K. changed: What|Removed |Added CC||quintenk...@gmail.com --- Comment #22 from Quinten K. --- I think this issue deserves reopening, since what KDE does is different from other projects (such as GNOME). On GNOME, I can click a Telegram Desktop notification that disappeared into the notification drawer on the panel. On KDE, that does not work. On a related note, even for Discover, which keeps a button in the history, clicking the body of the notification does not work, while this does work for the active notification. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 479559] New: Allow modifying font size on-the-fly
https://bugs.kde.org/show_bug.cgi?id=479559 Bug ID: 479559 Summary: Allow modifying font size on-the-fly Classification: Applications Product: yakuake Version: 23.08.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: quinten@quinten.space 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 *** In Konsole, I can adjust the font size on-the-fly using Shrink Font/Enlarge Font (Ctrl+- and Ctrl+=). There is no equivalent for these in Yakuake, but they'd be nice to have. STEPS TO REPRODUCE 1. Open Yakuake 2. Press ctrl+- or ctrl+= OBSERVED RESULT Nothing happens EXPECTED RESULT Font size changes (temporarily) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 479559] Allow modifying font size on-the-fly
https://bugs.kde.org/show_bug.cgi?id=479559 --- Comment #1 from Quinten Kock --- Oh, quick remark; this also affects other programs that embed Konsole, such as Kate or Kile. Maybe this should be implemented in KonsolePart instead so that it works everywhere? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472901] New: Screen flickers when switching virtual desktop with touchpad gesture and animations are off
https://bugs.kde.org/show_bug.cgi?id=472901 Bug ID: 472901 Summary: Screen flickers when switching virtual desktop with touchpad gesture and animations are off Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY The screen flickers black for a frame or so when using the touchpad gesture to switch virtual desktops (three/four finger swipe). More specifically, it happens as soon as you release, and only when animations are disabled. STEPS TO REPRODUCE 1. Disable animations by dragging the "Animation speed" slider in systemsettings all the way to right. 2. Switch virtual desktops with 3/4 finger touchpad swipe. 3. Observe that the screen flickers black when releasing your fingers. OBSERVED RESULT Screen flickers black. EXPECTED RESULT Screen switches instantly to target desktop, without any visual flicker. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 38 kernel 6.4.6 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION GPU: Intel UHD 620, Mesa 23.1.4 Graphics Platform: Wayland Wasn't sure which component to file against, so general. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 475100] New: SSH entries in KRunner
https://bugs.kde.org/show_bug.cgi?id=475100 Bug ID: 475100 Summary: SSH entries in KRunner Classification: Applications Product: konsole Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sshmanager Assignee: konsole-de...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY The SSH manager in Konsole is pretty useful. However, currently it only works if Konsole is already open. It would be nice if I could use KRunner to start an SSH session by its name, like is possible with Konsole profiles. STEPS TO REPRODUCE 1. Open SSH manager 2. Ensure there is at least one config 3. See that it appears when using the shortcut configured in the plugin 4. Try to search for the config in KRunner OBSERVED RESULT No (meaningful) results EXPECTED RESULT The SSH entry that is configured in Konsole SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 475101] New: Task manager right-click actions
https://bugs.kde.org/show_bug.cgi?id=475101 Bug ID: 475101 Summary: Task manager right-click actions Classification: Applications Product: konsole Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY Programs such as Dolphin and Firefox have items such as recent files and actions (like opening a private window) when you right click them in the Plasma task manager. It would be nice to have this for Konsole too, for example bound to profiles or SSH entries so that one can start these quickly. STEPS TO REPRODUCE 1. Right click Konsole in Plasma panel task manager OBSERVED RESULT Only two actions "Open new window" and "Open new tab" EXPECTED RESULT Special actions bound to profiles or SSH entries. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION The "Open a new tab" button also does not work correctly, as it opens a new window instead (on Wayland at least). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475129] New: Panel leaves artifacts when refloating
https://bugs.kde.org/show_bug.cgi?id=475129 Bug ID: 475129 Summary: Panel leaves artifacts when refloating Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 162021 --> https://bugs.kde.org/attachment.cgi?id=162021&action=edit Example - very strong shadow SUMMARY With the floating panel on KDE Neon Unstable 20231001, there are weird artifacts on my machine that appear when it defloats. STEPS TO REPRODUCE 1. Have the floating panel enabled 2. Make it defloat by e.g. maximizing a window 3. Refloat it, e.g. by minimizing all windows. OBSERVED RESULT Weird artifacts like duplicate shadows or other residues left EXPECTED RESULT Panel looks normal SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Kernel Version: 6.2.0-33-generic Mesa Version: 23.0.4-0ubuntu1~22.04.1 GPU: Intel UHD Graphics 620 (KBL GT2) Graphics platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475129] Panel leaves artifacts when refloating
https://bugs.kde.org/show_bug.cgi?id=475129 --- Comment #1 from Quinten Kock --- Created attachment 162022 --> https://bugs.kde.org/attachment.cgi?id=162022&action=edit Other example - 'residue' below the floating panel I also tested this on X11, and there it does seem to work normally (apart from the relatively well-known white flickery artifacts during motion, that iirc aren't really solvable?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475139] New: Notification animation does not match system tray animation
https://bugs.kde.org/show_bug.cgi?id=475139 Bug ID: 475139 Summary: Notification animation does not match system tray animation Classification: Plasma Product: plasmashell Version: master Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 162027 --> https://bugs.kde.org/attachment.cgi?id=162027&action=edit Screencast with slow animations to illustrate the issue SUMMARY When there is a notification popup in Plasma, it normally sits above the system tray. When opening a system tray applet (e.g. the volume control), the notification moves up so that it sits above the popup. This makes sense. However, the notification moves at a different speed than the popup does. This in my opinion looks awkward and gives off the feeling of one of the two lagging behind. STEPS TO REPRODUCE 1. Create a notification (e.g. with notify-send or by downloading a file) 2. Open a system tray widget (such as volume control) OBSERVED RESULT Animations run at different speeds EXPECTED RESULT Animations run at the same speed, such that the distance between the top of the popup and the bottom of the notification is constant. (Assuming that this distance is the same as the distance between the panel and the notification when there is no popup. I think this is the case, but haven't pixel-peeped to verify.) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Should probably be filed under either Notifications or System Tray, but not sure which one. Graphics Platform: Wayland (probably not relevant) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 475143] New: Volume OSD wrongly shows 100% instead of >100% sometimes
https://bugs.kde.org/show_bug.cgi?id=475143 Bug ID: 475143 Summary: Volume OSD wrongly shows 100% instead of >100% sometimes Classification: Plasma Product: plasma-pa Version: 5.27.8 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: isma...@gmail.com, m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY The volume OSD sometimes reports 100% volume instead of the correct volume (which is >100%, with the Raise Maximum Volume option). This seems to happen especially when other OSDs appear (verified with the media volume OSD). This also happens sporadically for me, but the below steps reliably reproduce the issue. STEPS TO REPRODUCE 0. Have media playing. 1. Raise the volume to e.g. 120% by e.g. scrolling over the volume icon. 2. Change the media volume by scrolling over the media player icon. (Might also reproduce with other OSDs like brightness, but did not verify.) 3. Lower the volume to 115% with either the keyboard shortcut or by scrolling. 4. Lower the volume again, to 110%. OBSERVED RESULT After step 3, the OSD wrongly indicates a volume of 100%. After step 4, the OSD correctly indicates 110%. EXPECTED RESULT After step 3 the OSD should report the actual volume of 115% instead. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Could be related to Bug 467123 or perhaps Bug 428425? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 475148] QTWidget applications on QT5 are not getting themed with Breeze on Neon Unstable
https://bugs.kde.org/show_bug.cgi?id=475148 Quinten Kock changed: What|Removed |Added Ever confirmed|0 |1 CC||quinten@quinten.space Status|REPORTED|CONFIRMED --- Comment #2 from Quinten Kock --- A workaround is to run sudo apt install kde-style-breeze5 This should probably be included in some kind of base package. -- You are receiving this mail because: You are watching all bug changes.
[Francis] [Bug 475390] New: Do not disturb blocks Francis notifications
https://bugs.kde.org/show_bug.cgi?id=475390 Bug ID: 475390 Summary: Do not disturb blocks Francis notifications Classification: Applications Product: Francis Version: 1.0.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: c...@carlschwan.eu Reporter: quinten@quinten.space Target Milestone: --- SUMMARY When working, I tend to put my system in Do Not Disturb mode, so that I don't get distracted as easily. It seems that by default this however also blocks the Francis notification, which kind of defeats the point. STEPS TO REPRODUCE 1. Turn on do not disturb 2. Start Francis 3. Wait for the timer to elapse (is there a way to change it so that I can test this more easily?) OBSERVED RESULT Notification gets blocked EXPECTED RESULT Notification goes through SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Francis 1.0.1 from Flatpak ADDITIONAL INFORMATION Looking at the code, it seems Francis sends a low priority notification. Perhaps this should be marked critical instead, so that it overrides DnD? Also, I think the notification goes through the "Plasma Workspace" app, so enabling notifications for that in DnD might be a viable workaround? It might be better for it to be a separate app so that, worst case, letting the user toggle this would be more obvious. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475129] Panel leaves artifacts when refloating
https://bugs.kde.org/show_bug.cgi?id=475129 --- Comment #6 from Quinten Kock --- I haven't had the time yet to try again, but maybe it is specific to Neon unstable? It worked fine when running on Fedora, but the mentioned Neon ISO did seem to be affected. My guess is that it's due to Ubuntu LTS using an at this point quite old Mesa version. Probably best to try it again with the latest Neon ISO, but not sure when I have the time. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477464] New: Sidebar buttons are one pixel from the edge and thus do not adhere to Fitt's law
https://bugs.kde.org/show_bug.cgi?id=477464 Bug ID: 477464 Summary: Sidebar buttons are one pixel from the edge and thus do not adhere to Fitt's law Classification: Applications Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY Sidebar buttons are one pixel removed from the edge, making them harder to hit STEPS TO REPRODUCE 1. Move cursor to edge of screen at position of a sidebar button like "Projects" 2. Click OBSERVED RESULT The entire sidebar is clicked, instead of the specific button that was aimed for EXPECTED RESULT The button touches the edge of the screen and is thus activated SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Kate was built using kdesrc-build but reports as 24.01.75 so not sure if I should report as Git or 24.01.75. Might be related to frameless Breeze? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477469] New: Workspace bounds are not limited correctly for 3-finger swipe.
https://bugs.kde.org/show_bug.cgi?id=477469 Bug ID: 477469 Summary: Workspace bounds are not limited correctly for 3-finger swipe. Classification: Plasma Product: kwin Version: 5.27.9 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY It is possible to swipe out of bounds using 3-finger swipe to switch between workspaces. STEPS TO REPRODUCE 0. Disable "navigation wraps around" for virtual desktops. 1. Create n workspaces 2. Remove the nth one 3. Use 3-finger swipe to go beyond the n-1th one, onto the now-removed n. OBSERVED RESULT Swipes beyond the last workspace into 'the void' EXPECTED RESULT Cannot swipe just like you cannot swipe to the desktop left of desktop 1. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 475143] Volume OSD briefly shows 100% instead of correct over-100% value after when adjusting system volume after adjusting app-specific volume from the Media Player widget
https://bugs.kde.org/show_bug.cgi?id=475143 --- Comment #2 from Quinten Kock --- So I tried to do a little digging, and it's all very confusing. dbus-monitor shows that plasma-pa seems to be sending the correct value of e.g. 105 to org.kde.osdService (member=osdProgress). In the OSD part of plasma-workspace specifically Osd::showProgress, maximumPercent is used to both bound the value and set osdMaxValue which defines how wide the progress bar is. Strangely, the progress bar does have the correct width?! So it seems that osdMaxValue *is* set correctly, but the value is being incorrectly bound somewhere after being sent over dbus. Very confusing. My best guess is that something goes wrong within plasma-workspace/shell/osd.cpp/showProgress, but I have no certainty for this. Maybe something horrible related to QML? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 475143] Volume OSD briefly shows 100% instead of correct over-100% value after when adjusting system volume after adjusting app-specific volume from the Media Player widget
https://bugs.kde.org/show_bug.cgi?id=475143 --- Comment #3 from Quinten Kock --- Okay, after attaching Gammaray it seems like the osdValue property is also being set correctly. Perhaps in plasma-workspace we should update the maxValue first and only THEN the value? Perhaps Qt internally limits the progressbar value too, which is then done with the old incorrect limit of 100 which is 'remembered' from the previous OSD (such as media or brightness). Will try and open an MR if it works! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 475784] Flicker in agenda view (esp. weekview)
https://bugs.kde.org/show_bug.cgi?id=475784 --- Comment #2 from Quinten Kock --- They flicker when scrolling (vertically) within the same week. When switching between weeks using the back/forward button the events are fine (but the days at the top like Monday, 27 November 2023 do seem to flicker; there's no text for one frame or so). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472901] Screen flickers when switching virtual desktop with touchpad gesture and animations are off
https://bugs.kde.org/show_bug.cgi?id=472901 --- Comment #1 from Quinten Kock --- I just noticed, when using the keyboard shortcut to switch between desktops the same issue happens. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 170124] Set as wallpaper on individual activities/desktops option
https://bugs.kde.org/show_bug.cgi?id=170124 Quinten Kock changed: What|Removed |Added CC||quinten@quinten.space --- Comment #27 from Quinten Kock --- I'd like to chime in to say that I would definitely like to have this. The most important consideration is that Dolphin *does* have it, shockingly, and Gwenview is much better for browsing images than Dolphin. When looking at changing my wallpaper, I currently do "browse for the right image in Gwenview -> look at the filename -> hunt for the right filename in Dolphin -> right click, set as wallpaper". Being able to do the last step directly in Gwenview would be a significant improvement. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475681] New: Middle click to close does not work in new Overview
https://bugs.kde.org/show_bug.cgi?id=475681 Bug ID: 475681 Summary: Middle click to close does not work in new Overview Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY In the new Meta+W overview in Plasma 6, I cannot close a window by middle-clicking on it. I think this used to work in Plasma 5, and is very useful to quickly close a window. STEPS TO REPRODUCE 1. Open overview (meta+w) 2. Middle click a window OBSERVED RESULT Nothing happens. EXPECTED RESULT Window closes. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.2 ADDITIONAL INFORMATION Middle clicking to remove a virtual desktop _does_ still work. Additionally, should middleclick do anything in the new desktop grid? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475682] New: New window overview seems to have minor scaling artifacts
https://bugs.kde.org/show_bug.cgi?id=475682 Bug ID: 475682 Summary: New window overview seems to have minor scaling artifacts Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- Created attachment 162344 --> https://bugs.kde.org/attachment.cgi?id=162344&action=edit Screenshot of described issue SUMMARY In the new scaling overview, minor artifacts are visible, likely due to scaling (render window overview at native res -> scale it down to fit)? In the attachment, one can notice the following issues: * The close button is inconsistent (The top border looks 'thinner' than the left or right borders) * The window title text looks kind of odd to me STEPS TO REPRODUCE 0. (maybe) have a low resolution display? 1. Open new overview OBSERVED RESULT Sharp graphics EXPECTED RESULT Blurry graphics. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472901] Screen flickers when switching virtual desktop with touchpad gesture and animations are off
https://bugs.kde.org/show_bug.cgi?id=472901 Quinten Kock changed: What|Removed |Added Version Fixed In||5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 475743] New: Repeat current track 'breaks' next button
https://bugs.kde.org/show_bug.cgi?id=475743 Bug ID: 475743 Summary: Repeat current track 'breaks' next button Classification: Applications Product: Elisa Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: quinten@quinten.space Target Milestone: --- SUMMARY When multiple tracks are queued, and "Repeat current track" is enabled, the "Skip forward" button repeats the current track instead. This makes sense on paper (because of the repeat mode), but in practice it is likely not what the user means as to restart they can already use the "Skip backward" button and repeat mode is generally only expected to affect 'automatic advancing' (and maybe if the backward/forward buttons loop around or are disabled). STEPS TO REPRODUCE 1. Have multiple songs queued 2. Enable "Repeat current track" 3. Click "Skip Forward" OBSERVED RESULT Current song repeats EXPECTED RESULT "Skip forward" overrides repeat mode and starts playing the next song SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Seems this was also implemented in Amarok at some point, BUG: 85087. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475770] New: LSP client view does not allow middle click or a shortcut to close tabs
https://bugs.kde.org/show_bug.cgi?id=475770 Bug ID: 475770 Summary: LSP client view does not allow middle click or a shortcut to close tabs Classification: Applications Product: kate Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY The LSP plugin panel (where you can see things like references) uses tabs (which is good). However, closing these tabs can only be done by clicking the (small) (X) button, or with the Close All Dynamic Reference Tabs action. It would be nice if these tabs could be closed by middle clicking them. Unfortunately implementing this easily seems to depend on https://bugreports.qt.io/browse/QTBUG-82408 (how is it done for the global Kate tabbar? is there a KF widget for it or is it implemented inside Kate/KTextEditor?) Additionally, being able to close the current reference tab with a shortcut might be nice too. STEPS TO REPRODUCE 1. Open one or more reference tabs using the LSP client 2. Middle click one of the tabs OBSERVED RESULT Nothing happens EXPECTED RESULT The middle clicked tab closes. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Also an issue on master -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 475772] New: Message threading broken in Unified Inbox
https://bugs.kde.org/show_bug.cgi?id=475772 Bug ID: 475772 Summary: Message threading broken in Unified Inbox Classification: Applications Product: kmail2 Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: quinten@quinten.space Target Milestone: --- Created attachment 162396 --> https://bugs.kde.org/attachment.cgi?id=162396&action=edit Mails threading correctly with the specific inbox selected SUMMARY Threading seems broken in the Unified Inbox but only there, at least for this specific group of messages. STEPS TO REPRODUCE 1. ??? OBSERVED RESULT Threading being the same in specific and unified inboxes. EXPECTED RESULT Threading differs. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Glad to help debug further; I have a .mbox of the mails on the screenshot, is sharing these risky in any way (e.g. personal data)? Maybe they could help reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 475772] Message threading broken in Unified Inbox
https://bugs.kde.org/show_bug.cgi?id=475772 --- Comment #1 from Quinten Kock --- Created attachment 162397 --> https://bugs.kde.org/attachment.cgi?id=162397&action=edit Mail thread being split in two in the unified inbox -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 475784] New: Flicker in agenda view (esp. weekview)
https://bugs.kde.org/show_bug.cgi?id=475784 Bug ID: 475784 Summary: Flicker in agenda view (esp. weekview) Classification: Applications Product: korganizer Version: 5.24.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-b...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY Scrolling the weekview causes events to flicker, especially if there are many visible. STEPS TO REPRODUCE 1. Have many events in a week 2. Scroll the weekview using the scrollbar or touchpad or some other pixel-by-pixel scrolling mechanism OBSERVED RESULT Events seem to flicker EXPECTED RESULT Events are rendered on-screen every frame SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Using Wayland session and Intel UHD graphics. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475682] New window overview seems to have minor scaling artifacts
https://bugs.kde.org/show_bug.cgi?id=475682 Quinten Kock changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Quinten Kock --- Scaling factor is 100%. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476652] New: Frameless Kate missing separator above e.g. Symbol Outline
https://bugs.kde.org/show_bug.cgi?id=476652 Bug ID: 476652 Summary: Frameless Kate missing separator above e.g. Symbol Outline Classification: Applications Product: kate Version: Git Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- Created attachment 162917 --> https://bugs.kde.org/attachment.cgi?id=162917&action=edit Screenshot of described issue 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 *** The new frameless style in Kate looks great! But it does have at least one annoyance that looks ugly: the Symbol Outline pane doesn't have a border above it STEPS TO REPRODUCE 1. Build Kate from git 2. open symbol outline panel OBSERVED RESULT Consistent border below menubar/toolbar EXPECTED RESULT Border is missing above symbol outline window SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.240.0 Qt Version: 6.5.2 ADDITIONAL INFORMATION See screenshot The terminal panel also seems to have this issue when moved to a sidebar. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474400] New: Volume change popup does not appear when in Overview mode
https://bugs.kde.org/show_bug.cgi?id=474400 Bug ID: 474400 Summary: Volume change popup does not appear when in Overview mode Classification: Plasma Product: kwin Version: 5.27.7 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY When the overview is open, popups such as the one for changing volume do not appear. STEPS TO REPRODUCE 1. Hit Meta+W to open the overview 2. Increase/decrease the volume with the keyboard buttons while the overview is open OBSERVED RESULT Popup appears informing me of the new volume EXPECTED RESULT Popup is not shown, except in the thumbnails for virtual desktops SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Other 'overlays' such as the Kickoff menu also appear in the desktop thumbnails. Filed under General because this also affects other 'overview-like' effects such as desktop grid/present windows. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 474410] New: Allow more compact sidebar
https://bugs.kde.org/show_bug.cgi?id=474410 Bug ID: 474410 Summary: Allow more compact sidebar Classification: Applications Product: kontact Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: quinten@quinten.space Target Milestone: --- Created attachment 161559 --> https://bugs.kde.org/attachment.cgi?id=161559&action=edit The vertical text in the sidebar that is configurable in Kate SUMMARY In Kate, it is possible to configure the sidebar to have vertical text. This is also supported in other, non-KDE, apps such as the Clementine music player. This would be beneficial for users with small screens, as it would reduce the screen real estate occupied by the sidebar. There is an alternative in only using icons, but this is generally less compact, and removes the text entirely making it in my opinion less clear. Additionally the buttons become rather small for Fitt's law. STEPS TO REPRODUCE 1. Right click sidebar 2. See no option for "Show Text & Icons" but vertically OBSERVED RESULT No option for vertical text EXPECTED RESULT An option for vertical text to reduce the size occupied by the sidebar, similar to what is shown in the attachment. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 471429] New: Skip backward/forward buttons not updated when changing playlist
https://bugs.kde.org/show_bug.cgi?id=471429 Bug ID: 471429 Summary: Skip backward/forward buttons not updated when changing playlist Classification: Applications Product: Elisa Version: 23.04.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: quintenk...@gmail.com Target Milestone: --- SUMMARY The buttons for next and previous song are not enabled/disabled correctly. STEPS TO REPRODUCE 1. Create a playlist, and play the last song 2. Drag this song to the top OBSERVED RESULT The "Skip backward" button is enabled and the "Skip forward" button is disabled. EXPECTED RESULT Skip backward should become unactive because it is no longer possible to do so. And skip forward should become active for the opposite reason. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux 6.3.6-arch1-1 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 471456] New: Modifying playlist position of current song breaks pause
https://bugs.kde.org/show_bug.cgi?id=471456 Bug ID: 471456 Summary: Modifying playlist position of current song breaks pause Classification: Applications Product: Elisa Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: quintenk...@gmail.com Target Milestone: --- SUMMARY When the current song is moved in the playlist (either by moving another song over it, or by moving the song itself), the pause button stops playback, instead of pausing it. STEPS TO REPRODUCE 1. Play a song in a playlist 2. Move the playing song, or move another song 'over' the playing song, so that its index in the playlist changes 3. Pause OBSERVED RESULT Playback stops EXPECTED RESULT Playback pauses (Remembers current song and position in song) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 38 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471463] New: Request: "whole word" button in Kate search panel
https://bugs.kde.org/show_bug.cgi?id=471463 Bug ID: 471463 Summary: Request: "whole word" button in Kate search panel Classification: Applications Product: kate Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: search Assignee: kwrite-bugs-n...@kde.org Reporter: quintenk...@gmail.com Target Milestone: --- SUMMARY In the Kate search panel, there are currently options to "Match case" and "Enable regular expressions". Additionally, in the Kate Ctrl-F bar, there's a button for Match case. It would be nice to add a way to easily filter matches by whole word (VSCode for example supports this, and in ripgrep you can use the -w parameter for this). I believe this can also be achieved by using regex word boundaries, but a GUI button is easier to use for most users. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION There was a request for this in Ctrl-F before: bug 290010. However that does not cover Ctrl+Shift+F (Find in Files). That said it'd be nice to have this in Ctrl+F and not just Ctrl+R, imo. (I understand the reasoning for why not, but still consider it a worse UX). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443431] Windows on pager positioned outside of the widget
https://bugs.kde.org/show_bug.cgi?id=443431 Quinten K. changed: What|Removed |Added CC||quintenk...@gmail.com --- Comment #3 from Quinten K. --- On 5.27.5 Wayland, it looks like the pager tries to limit the window outlines to stay within the button. However, when quickly moving a window around it does leave the boundary, only to be 'pulled back in' later. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471804] New: Color scheme "tint all colors colors with accent color" way too prominent on Okular background
https://bugs.kde.org/show_bug.cgi?id=471804 Bug ID: 471804 Summary: Color scheme "tint all colors colors with accent color" way too prominent on Okular background Classification: Applications Product: okular Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: quintenk...@gmail.com Target Milestone: --- Created attachment 160005 --> https://bugs.kde.org/attachment.cgi?id=160005&action=edit Screenshot of the described issue (Okular is in the background on the right) SUMMARY The Okular background, which is normally grey, gets an overly saturated version of my accent color, which looks rather ugly. STEPS TO REPRODUCE 1. Go to System Settings -> Colors, and enable "Tint all colors with accent colors" for the active theme. 2. Open a document in Okular 3. Zoom out so that the margins/background are clearly visible OBSERVED RESULT Background is colored very intensely EXPECTED RESULT Background is colored much more subtly, similar to how other windows are tinted. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 471857] New: "Do not change color from original HTML mail" also makes plain text mail not adhere to color scheme
https://bugs.kde.org/show_bug.cgi?id=471857 Bug ID: 471857 Summary: "Do not change color from original HTML mail" also makes plain text mail not adhere to color scheme Classification: Applications Product: kmail2 Version: 5.23.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: quintenk...@gmail.com Target Milestone: --- SUMMARY The "Do not change color from original HTML mail" option in Settings -> Appearance -> Colors, will make plain-text emails appear in white. This is undesirable e.g. when using a dark theme. STEPS TO REPRODUCE 1. Set the color scheme to e.g. Breeze Dark 2. Enable the option described in the summary 3. Open a plain-text email OBSERVED RESULT The background is white EXPECTED RESULT The viewer adheres to the system color theme because it is displaying plain text without any colors that could act up SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I guess this may actually be a kdepim/messageviewer issue? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 471857] "Do not change color from original HTML mail" also makes plain text mail not adhere to color scheme
https://bugs.kde.org/show_bug.cgi?id=471857 --- Comment #2 from Quinten Kock --- In that case, at least the wording is highly misleading. Because the wording says "HTML mail", it implies that plain-text mail is not affected by the option. Also, I would like the option to have only HTML emails keep their original colors while plaintext email keeps its original color, because HTML email can look very odd with a custom color scheme and bad CSS, while plaintext email has no such issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437089] On Wayland, Windows that were closed when maximized and do not record their own maximized state will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Quinten Kock changed: What|Removed |Added CC||quintenk...@gmail.com --- Comment #30 from Quinten Kock --- Just chiming in to say this is still an issue, but only for some applications. For example, Dolphin behaves correctly and even restores to the right size, but System Monitor is affected, as is Elisa. GTK apps seem to handle this correctly on my Plasma Wayland desktop, at least Nautilus and Lutris do, although the latter doesn't remember the size to restore to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471884] New: Windows that opened maximized behave weirdly when dragged
https://bugs.kde.org/show_bug.cgi?id=471884 Bug ID: 471884 Summary: Windows that opened maximized behave weirdly when dragged Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: quintenk...@gmail.com Target Milestone: --- SUMMARY Some apps (e.g. Dolphin) behave very oddly when they launch maximized and are then restored by dragging the titlebar. STEPS TO REPRODUCE 1. Open Dolphin, maximize it, close it, and reopen it 2. Observe that Dolphin opens maximized 3. Unmaximize Dolphin by dragging the titlebar 4. Resize Dolphin by its top-left corner OBSERVED RESULT In step 3, Dolphin is positioned with the cursor at the top right. In step 4, Dolphin's bottom-right corner suddenly jumps to the position where you started dragging (the top-left corner of the window). EXPECTED RESULT In step 3 I expect Dolphin to keep the cursor in the same relative position, like when dragging to unmaximize a window that was not initially maximized. In step 4 I expect Dolphin to not jump around. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Probably related to bug 437089 Possibly also related to bug 434116? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468497] Configurable highlight behavior for split header bar
https://bugs.kde.org/show_bug.cgi?id=468497 Quinten Kock changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||quintenk...@gmail.com --- Comment #2 from Quinten Kock --- Hi! If you want to contribute a patch to Konsole (or any other KDE project), the best way to do it is to create a Merge Request on https://invent.kde.org/utilties/konsole. I agree that the contrast is a bit low, even with the default Breeze theme where shadowing does have some effect. As for your patch, it seems that on my machine it makes all non-active headers black, which is undesirable IMO. In addition, using the accent color is somewhat bright with my color, and it also prevents the 'outlines' around buttons from appearing (because those are the same color). Looking at other KDE software, it looks like they're using a 'dimmed' version of the accent color when you e.g. hover over a selectable item. The color itself is also used in some places, but generally on smaller regions. The tab bar uses a small line of the accent color to highlight the active one. Figuring out such details is probably best left to the VDG. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463649] New: System setttings crashed upon changing scaling
https://bugs.kde.org/show_bug.cgi?id=463649 Bug ID: 463649 Summary: System setttings crashed upon changing scaling Classification: Applications Product: systemsettings Version: 5.26.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quintenk...@gmail.com Target Milestone: --- Application: systemsettings (5.26.4) Qt Version: 5.15.7 Frameworks Version: 5.101.0 Operating System: Linux 6.0.15-300.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.26.4 [KCrashBackend] -- Information about the crash: I changed my scaling setting from 150% to 100%, hit apply, and then System Settings crashed. (It did however succesfully apply the setting). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f2a268afe7c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7f2a2685faa6 in raise () from /lib64/libc.so.6 #6 0x7f2a268497fc in abort () from /lib64/libc.so.6 #7 0x7f2a1109b349 in _iris_batch_flush.cold () from /usr/lib64/dri/iris_dri.so #8 0x7f2a11d42387 in iris_fence_flush () from /usr/lib64/dri/iris_dri.so #9 0x7f2a11160a64 in st_glFlush () from /usr/lib64/dri/iris_dri.so #10 0x7f2a21eeda1d in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) () from /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #11 0x7f2a2780d23a in QPlatformBackingStore::composeAndFlush(QWindow*, QRegion const&, QPoint const&, QPlatformTextureList*, bool) () from /lib64/libQt5Gui.so.5 #12 0x7f2a27dbc716 in QWidgetRepaintManager::flush(QWidget*, QRegion const&, QPlatformTextureList*) () from /lib64/libQt5Widgets.so.5 #13 0x7f2a27dc0a1a in QWidgetRepaintManager::sync(QWidget*, QRegion const&) () from /lib64/libQt5Widgets.so.5 #14 0x7f2a27e0e22c in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f2a27daed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f2a270a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f2a2756c1a5 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /lib64/libQt5Gui.so.5 #18 0x7f2a2754a02c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #19 0x7f2a2754a3b0 in QWindowSystemInterface::flushWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #20 0x7f2a270d2ec4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f2a27daed12 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7f2a270a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #23 0x7f2a270ab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #24 0x7f2a270f9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #25 0x7f2a25919cbf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #26 0x7f2a2596f598 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #27 0x7f2a25916f40 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #28 0x7f2a270f938a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #29 0x7f2a270a6cca in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #30 0x7f29f41f9902 in KScreen::ConfigOperation::exec() () from /lib64/libKF5Screen.so.7 #31 0x7f29f4250e2f in KCMKScreen::doSave(bool) () from /usr/lib64/qt5/plugins/plasma/kcms/systemsettings/kcm_kscreen.so #32 0x7f2a28391736 in KCModuleQml::save() () from /lib64/libKF5KCMUtils.so.5 #33 0x7f2a28399827 in KCModuleProxy::save() () from /lib64/libKF5KCMUtils.so.5 #34 0x7f2a28966065 in ModuleView::moduleSave(KCModuleProxy*) () from /lib64/libsystemsettingsview.so.3 #35 0x7f2a2896883e in ModuleView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libsystemsettingsview.so.3 #36 0x7f2a270dbdaf in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #37 0x7f2a27ea31d6 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #38 0x7f2a27ea344e in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #39 0x7f2a27ea508c in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #40 0x7f2a27ea52ab in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #41 0x7f2a27df1818 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5
[systemsettings] [Bug 463649] System setttings crashed upon changing scaling
https://bugs.kde.org/show_bug.cgi?id=463649 --- Comment #2 from Quinten K. --- (In reply to Nicolas Fella from comment #1) > Looks same as https://bugs.kde.org/show_bug.cgi?id=450489 Not sure, because this was a systemsettings crash. Plasma itself continued to run as usual. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448801] New: Allow opening terminal in KIO shares
https://bugs.kde.org/show_bug.cgi?id=448801 Bug ID: 448801 Summary: Allow opening terminal in KIO shares Product: dolphin Version: 21.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: quintenk...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- It is not possible to right-click -> actions -> open terminal in e.g. a Samba share mounted with Dolphin. This despite the fact that kio-fuse is running on my system, and a Samba share is existent on my local file system somewhere under /run/user/.../kio-fuse-.../smb/url. Shift+F4 opens a terminal in my home directory as well instead of in the KIO-Fuse directory. STEPS TO REPRODUCE 1. Mount a Samba share in Dolphin (probably same issue with e.g. FTP). 2. Hit Shift+F4 in this network folder. OBSERVED RESULT Terminal's working directory is ~ EXPECTED RESULT Terminal's working directory is the KIO-Fuse folder of the network share (+ subfolder, if applicable) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.16.0 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448801] Allow opening terminal in KIO shares
https://bugs.kde.org/show_bug.cgi?id=448801 Quinten K. changed: What|Removed |Added CC||quintenk...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 448801] Dolphin terminal for KIO shares does not use kiofuse
https://bugs.kde.org/show_bug.cgi?id=448801 --- Comment #2 from Quinten K. --- I made a screenshot of what it looks like on my machine: https://i.imgur.com/eFYMGje.png I removed some private data, like the exact server or the folder contents, but as you can see the context menu does not contain an Actions submenu at all. I did try the Dolphin-integrated terminal with F4 which does go to the correct folder, but that does not negate this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492926] New: Name of newly created desktop does not appear on pager
https://bugs.kde.org/show_bug.cgi?id=492926 Bug ID: 492926 Summary: Name of newly created desktop does not appear on pager Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: h...@kde.org Target Milestone: 1.0 SUMMARY When a new virtual desktop is created, and the pager is set to display desktop names, the pager will not show the name of the newly created desktop. STEPS TO REPRODUCE 1. Set pager to show desktop names 2. Open overview (Meta+W) and create a new virtual desktop OBSERVED RESULT No text on new desktop EXPECTED RESULT Name of new desktop (i.e. "Desktop N") is displayed SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492474] New: Dragging widgets between panels is broken
https://bugs.kde.org/show_bug.cgi?id=492474 Bug ID: 492474 Summary: Dragging widgets between panels is broken Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Edit Mode Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Attempting to drag widgets between Plasma panels can lead to some quite broken situations: - First, everything seems like it needs to go 'via' the desktop containment. It is not possible to drag directly from panel to panel. - Second, with some widgets this leads to them seemingly "disappearing into the void". Notably this happens for the system tray. STEPS TO REPRODUCE 1. Create second panel 2. Try to drag system tray to that panel OBSERVED RESULT System tray becomes invisible but is still counted by 'add widgets' pane EXPECTED RESULT System tray goes to the other panel, or at the very least becomes visible on the desktop. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485656] Media player seek bar stops updating sometimes
https://bugs.kde.org/show_bug.cgi?id=485656 Quinten Kock changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Version|6.0.3 |6.1.4 Status|NEEDSINFO |REOPENED --- Comment #3 from Quinten Kock --- I'm currently experiencing this bug on 6.1.4 :( Still no reliable reproducer though, so determining if it's present is pretty challenging to say the least. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 490064] New: File chooser in directory mode does not default to current directory, making it near-unusable on single-click-to-open systems
https://bugs.kde.org/show_bug.cgi?id=490064 Bug ID: 490064 Summary: File chooser in directory mode does not default to current directory, making it near-unusable on single-click-to-open systems Classification: Plasma Product: xdg-desktop-portal-kde Version: 6.1.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quinten@quinten.space CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When opening a directory through xdg-desktop-portal's File Chooser API, the picker handles this quite badly. On my system, which is single-click-to-open, I have to click the folder I want, then I have two options: - Go up, then the folder I want is selected, then click the OK button - or type '.' into the filename bar and then hit OK. Hitting OK while in a folder does not actually do anything. STEPS TO REPRODUCE 1. Have single-click-to-open 2. Try to open a folder using xdg-desktop-portal (e.g. with ashpd demo, I originally discovered the issue using Zed) 3. Try to open the current directory OBSERVED RESULT Nothing happens EXPECTED RESULT Folder is selected SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Wayland ADDITIONAL INFORMATION I'm not sure what the right behaviour here is, since when something is selected the selected folder would be picked. But probably this is fine, iirc Windows does the same thing where the current folder is just what gets picked when nothing is selected? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443431] Windows on pager positioned outside of the widget
https://bugs.kde.org/show_bug.cgi?id=443431 --- Comment #6 from Quinten Kock --- I can still reproduce on recent master. To reproduce, *quickly* move a window (partially) off-screen. You will see the window go out of bounds before retracting itself back in. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477469] Workspace bounds are not limited correctly for 3-finger swipe.
https://bugs.kde.org/show_bug.cgi?id=477469 Quinten Kock changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Quinten Kock --- Seems this bug has stopped occuring. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 475640] Make F11 be an alternate shortcut for fullscreen to be in harmony with other apps
https://bugs.kde.org/show_bug.cgi?id=475640 Quinten Kock changed: What|Removed |Added CC||quinten@quinten.space --- Comment #1 from Quinten Kock --- This is a feature request, not a bug, but I'd like to second it :) F11 does not seem to be used by anything else in Okular currently, so making it an additional shortcut for fullscreen seems reasonable to me. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 502241] New: When Okular is open in full-screen, a new instance will miss the menubar and toolbar
https://bugs.kde.org/show_bug.cgi?id=502241 Bug ID: 502241 Summary: When Okular is open in full-screen, a new instance will miss the menubar and toolbar Classification: Applications Product: okular Version: 24.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: quinten@quinten.space Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY When an instance of Okular is open in full-screen mode, opening another instance will cause that other instance to not have a menubar or toolbar. STEPS TO REPRODUCE 1. Open a file (e.g. file1.pdf) in Okular 2. View file1.pdf in fullscreen 3. Open a second file (e.g. file2.pdf) in Okular as well OBSERVED RESULT The second instance with file2.pdf is missing the toolbar and menu bar. EXPECTED RESULT The second instance with file2.pdf has all regular window elements. SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
