[plasmashell] [Bug 479755] [Wayland] Invisible icons/texts in the logout screen if an icc color profile is used
https://bugs.kde.org/show_bug.cgi?id=479755 Nate Graham changed: What|Removed |Added CC||ballog...@gmail.com --- Comment #8 from Nate Graham --- *** Bug 482793 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #49 from Giacomo Lozito --- (In reply to Jakob Petsovits from comment #44) > Not sure how best to deal with bug reports because ideally we'd have two > separate ones, but if the symptoms are indeed very similar then it'll be > difficult to tell them apart. Hopefully a large number of users will see > their setup fixed and the remaining ones can target the screen locker / > Plasma theme issue in a targeted way. I have created a separate bug report (https://bugs.kde.org/show_bug.cgi?id=483163) for the breeze style + kscreenlocker issue. Not an urgent one to fix imho as I can simply switch to Breeze Light for now to mitigate issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482828] Task Manager icons disappear/move to the left when mouse is moved over them
https://bugs.kde.org/show_bug.cgi?id=482828 Nate Graham changed: What|Removed |Added Product|kwin|plasmashell CC||n...@kde.org, ||qydwhotm...@gmail.com Summary|Task bar/panel icons|Task Manager icons |disappear when mouse is |disappear/move to the left |moved over them |when mouse is moved over ||them Component|general |Task Manager and Icons-Only ||Task Manager Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM Target Milestone|--- |1.0 Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org --- Comment #3 from Nate Graham --- This is unfortunately an NVIDIA GPU driver glitch, IIRC introduced with the 550 series. Please report this issue to the NVIDIA folks, either by sending an email to linux-b...@nvidia.com or making a post at https://forums.developer.nvidia.com/c/gpu-graphics/linux. It would be helpful to the NVIDIA developers if you could run nvidia-bug-report.sh and attach the resulting file in your report. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482666] KRunner not horizontally centered on X11
https://bugs.kde.org/show_bug.cgi?id=482666 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #10 from Nate Graham --- Did I understand you in the other bug report that you managed to fix this by removing some obsolete packages? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482862] plasma desktop freezes on wayland
https://bugs.kde.org/show_bug.cgi?id=482862 Nate Graham changed: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Resolution|--- |WAITINGFORINFO Product|plasmashell |kwin CC||n...@kde.org Status|REPORTED|NEEDSINFO Component|general |wayland-generic Target Milestone|1.0 |--- --- Comment #1 from Nate Graham --- I can't reproduce this with a dual-monitor setup (I don't have a 3rd monitor) in 5.27, or 6.0. Could you try Plasma 6.0 and see if it still happens? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483163] New: blank screen on lock screen activation when using breeze plasma style
https://bugs.kde.org/show_bug.cgi?id=483163 Bug ID: 483163 Summary: blank screen on lock screen activation when using breeze plasma style Classification: Plasma Product: kscreenlocker Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: giacomo.loz...@protonmail.com Target Milestone: --- SUMMARY When activating lock screen (via shortcut, menu option or timer), the screen becomes blank. The screen is not turned off and maintains the backlight on, but nothing is drawn on screen. Cursor can be seen when moved, and password can be blindly typed to return into desktop, which becomes immediately visible again. Also, when the lock screen is blank like this, switching to another virtual terminal and returning to the lock screen vt will cause it to be displayed correctly. This behavior only occurs when Breeze is selected as plasma style, and it happens most of the time. Switching to Breeze Light, Breeze Dark or Oxygen will result in the lock screen being displayed correctly 100% of the time. Switching back to Breeze will cause the wrong behavior again. Please note that this bug is separate from https://bugs.kde.org/show_bug.cgi?id=481308 which is powerdevil-related and causes the screen to turn off. Energy settings make no difference for this issue, the screen is still on but blank. The difference to behaviour seems to be made by changing the plasma style. STEPS TO REPRODUCE 1. Use Breeze as plasma style 2. Activate lock screen using keyboard shortcut, launcher option or wait for it to be activated by inactivity 3. 19 times out of 20, the lock screen will be blank, even if the screen is turned on OBSERVED RESULT Blank screen, with the screen turned on. Moving cursor around makes it visible. EXPECTED RESULT Lock screen window correctly drawn. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 10 Graphics ADDITIONAL INFORMATION Speculation: one notable difference between Breeze and the other plasma styles (Breeze Light, Dark, etc.) is that Breeze is the only style that is designed to follow the user-chosen color scheme. So it is possible that color scheme implementation in plasma is playing a role into the issue. I have tried changing the color scheme (i.e., using the one from wallpaper or the default one) but changing the scheme itself makes no difference. The issue only seems to occur with the screen locker and I have not seen it anywhere else in plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 482855] Network applet shows wrong upload speeds
https://bugs.kde.org/show_bug.cgi?id=482855 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 479230 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479230] Network graph always shows 2 GiB/s download speed
https://bugs.kde.org/show_bug.cgi?id=479230 Nate Graham changed: What|Removed |Added CC||ty3...@chaox.ro --- Comment #8 from Nate Graham --- *** Bug 482855 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482854] Crash (and failed monitor connectrion) when connecting a second display using a KVM switch
https://bugs.kde.org/show_bug.cgi?id=482854 --- Comment #3 from Nate Graham --- Looks like it would be a Qt bug to me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482854] Crash (and failed monitor connectrion) when connecting a second display using a KVM switch
https://bugs.kde.org/show_bug.cgi?id=482854
Nate Graham changed:
What|Removed |Added
Keywords|qt6 |multiscreen
CC||n...@kde.org
--- Comment #2 from Nate Graham ---
Thread 1 (Thread 0x7babdfee19c0 (LWP 1867)):
[KCrash Handler]
#5 std::__atomic_base::fetch_add (__m=std::memory_order_acq_rel, __i=1,
this=0x7babe6333930 , this=, __i=, __m=) at
/usr/include/c++/13.2.1/bits/atomic_base.h:633
#6 QAtomicOps::ref (_q_value=std::atomic = { -98693133 },
_q_value=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qatomic_cxx11.h:258
#7 QBasicAtomicInteger::ref (this=0x7babe6333930
, this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qbasicatomic.h:49
#8 QtSharedPointer::ExternalRefCountData::getAndRef
(obj=obj@entry=0x64ab2cbea120) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer.cpp:1409
#9 0x7babe5692170 in QWeakPointer::QWeakPointer
(ptr=0x64ab2cbea120, this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer_impl.h:685
#10 QWeakPointer::assign (this=0x64ab323e5870,
ptr=0x64ab2cbea120) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer_impl.h:680
#11 0x7babe56e3957 in QPointer::operator= (p=0x64ab2cbea120,
this=0x64ab323e5870, this=, p=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qpointer.h:68
#12 QWindowPrivate::connectToScreen (screen=, this=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qwindow.cpp:481
#13 QWindowPrivate::setTopLevelScreen (this=0x64ab323e5720,
newScreen=0x64ab2cbea120, recreate=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/gui/kernel/qwindow.cpp:506
#14 0x7babe6dc7bae in QWidgetPrivate::setScreen (this=0x64ab322cd0e0,
screen=0x64ab2cbea120) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qwidget.cpp:2413
#15 0x7babe6f540f0 in QMenuPrivate::popup(QPoint const&, QAction*,
std::function) (this=0x64ab322cd0e0, p=...,
atAction=atAction@entry=0x0, positionFunction=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qmenu.cpp:2333
#16 0x7babe6f542f2 in QMenu::popup (this=, p=...,
atAction=atAction@entry=0x0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/widgets/qmenu.cpp:2306
#17 0x7babe7914bdb in ContainmentItem::mousePressEvent
(this=0x64ab2d4e9550, event=0x7ffc99fe0600) at
/usr/include/c++/13.2.1/bits/unique_ptr.h:199
#18 0x7babe67d933b in QQuickItem::event (this=0x64ab2d4e9550,
ev=0x7ffc99fe0600) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickitem.cpp:8892
#19 0x7babe6d9138b in QApplicationPrivate::notify_helper (this=, receiver=0x64ab2d4e9550, e=0x7ffc99fe0600) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296
#20 0x7babe507b818 in QCoreApplication::notifyInternal2
(receiver=0x64ab2d4e9550, event=0x7ffc99fe0600) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121
#21 0x7babe507b85d in QCoreApplication::sendEvent (receiver=, event=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1539
#22 0x7babe6943ef4 in
QQuickDeliveryAgentPrivate::deliverMatchingPointsToItem
(this=this@entry=0x64ab2cd77520, item=item@entry=0x64ab2d4e9550,
isGrabber=isGrabber@entry=false,
pointerEvent=pointerEvent@entry=0x7ffc99fe0600,
handlersOnly=handlersOnly@entry=false) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/util/qquickdeliveryagent.cpp:2179
#23 0x7babe6945445 in
QQuickDeliveryAgentPrivate::deliverPressOrReleaseEvent
(this=this@entry=0x64ab2cd77520, event=event@entry=0x7ffc99fe0600,
handlersOnly=handlersOnly@entry=false) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/util/qquickdeliveryagent.cpp:2128
#24 0x7babe6945f69 in QQuickDeliveryAgentPrivate::deliverPointerEvent
(this=0x64ab2cd77520, event=0x7ffc99fe0600) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/util/qquickdeliveryagent.cpp:1853
#25 0x7babe693aa08 in QQuickDeliveryAgent::event (this=,
ev=0x7ffc99fe0600) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/util/qquickdeliveryagent.cpp:705
#26 0x7babe687e5d5 in QQuickWindow::event (this=,
event=) at
/usr/src/debug/qt6-declarative/qtdeclarative-everywhere-src-6.6.2/src/quick/items/qquickwindow.cpp:1508
#27 0x7babe6d9138b in QApplicationPrivate::notify_helper (this=, receiver=0x64ab2d461e20, e=0x7ffc99fe0600) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296
#28 0x7babe507b818 in
[systemsettings] [Bug 482851] Different size for category and subcategory titles fonts
https://bugs.kde.org/show_bug.cgi?id=482851 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #2 from Nate Graham --- I'm afraid all the sizes here are intentional. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 392253] Startup URL setting and Home button in KDE 5 Web Browser Plasma widget
https://bugs.kde.org/show_bug.cgi?id=392253 Shubham Arora changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Shubham Arora --- (In reply to Nate Graham from comment #6) > Is there anything else need to do here, or are those patches enough? They > look to be enough to me. Yeah, all items should be implemented. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 --- Comment #5 from András Manţia --- Meantime I deinstalled some kf5 kcmutils related packages (but kept the library) and works now. Even more, bug https://bugs.kde.org/show_bug.cgi?id=482666 too. Thanks for the hint! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 András Manţia changed: What|Removed |Added Resolution|DOWNSTREAM |FIXED --- Comment #4 from András Manţia --- Yes, I have both KF5 and KF6 kcmutils, the KF5 version is needed for some apps -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459973] Touch mode on convertible laptop gets activated even when there is an USB keyboard & mouse attached
https://bugs.kde.org/show_bug.cgi?id=459973 wincak changed: What|Removed |Added CC||win...@seznam.cz --- Comment #2 from wincak --- I have the same problem on Dell 7210 2-in-1 tablet. Disconnecting the tablet's main keyboard switches the device to Touch mode even if an external keyboard and mouse are connected. Also there does not seem to be an easy way to turn the Touch mode on and off manually except for directly in the system settings. I'm using a keyboard and a mouse that share a wireless USB adapter. Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: Latitude 7210 2-in-1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479230] Network graph always shows 2 GiB/s download speed
https://bugs.kde.org/show_bug.cgi?id=479230 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Nate Graham --- I can reproduce this at will in Plasma 6. So, not fixed by that commit for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483075] Global menu disappears when a pop-up window shows up
https://bugs.kde.org/show_bug.cgi?id=483075 Sdar changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||s...@vivaldi.net --- Comment #1 from Sdar --- Can confirm, in my case when using gimp and it opens any popup window I lost the global menu too. ie: open and image in gimp go to "File -> export as" the global menu is gone and it doesn't come back after closing the export window. If you alt tab out and back to gimp the global menu comes back. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479230] Network graph always shows 2 GiB/s download speed
https://bugs.kde.org/show_bug.cgi?id=479230 --- Comment #6 from madc...@atlas.cz --- (In reply to Shubham Arora from comment #5) > I am not able to reproduce this in plasma 6. Likely fixed by > https://invent.kde.org/plasma/plasma-nm/-/commit/ > 7ef8d079d1ce97b1d342f4ebf8691e014710e060. It uses real for rxSpeed now in > qml instead of int. Can you verify. I'm afraid I don't quite follow. The commit you reference is from 5 months ago and, as far as I can determine, it was part of Plasma 6 Beta 1 against which I reported the bug. The commit also does the exact opposite to what you say, it replaces reals with ints which is the actual cause of the problem. If I wait for the problem to occur, hot-edit ConnectionItem.qml to use reals for the prev[RT]xBytes and restart Plasma, the problem goes away. If I change the types back to ints, the problem reappears. This happens on Plasma 6.0.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483162] New: Window is in wrong stacking order
https://bugs.kde.org/show_bug.cgi?id=483162 Bug ID: 483162 Summary: Window is in wrong stacking order Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: glados9...@protonmail.com Target Milestone: --- SUMMARY All my Windows are randomly going over the other when unfocused, and the focused one sometimes goes to the very behind or in the middle somewhere. STEPS TO REPRODUCE 1. Start and play Apex Legends with Proton Hotfix 2. Start and use Cura Ultimaker 5.6.0 from Flatpak 3. Wait for some time. 4. See windows go below other windows when focused. OBSERVED RESULT Having the newest window behind the second newest (in other words, having the current clicked window behind the window that is 1 click older). Some Windows stay below all windows for some weird reason, like Spotify did. Meaning that the stacking order is not reversed, but random? Even the shutdown screen where I can log out, sleep etc. is going behind all Windows. EXPECTED RESULT Have the focused window, the top window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, Plasma 6.0.1 Wayland (available in About System) KDE Plasma Version: 6.0.1 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 482632] Mouse look stuck in some xwayland applications (specifically games under proton)
https://bugs.kde.org/show_bug.cgi?id=482632 --- Comment #17 from tylerkstray...@gmail.com --- (In reply to rejedai from comment #15) > (In reply to tylerkstrayhan from comment #14) > > I tired updating qt in the kde-unstable repo on arch and it ended up just > > breaking plasma for me. Is there another package it needs to get running? > > You need to rebuild all KDE applications. During beta and rс, KDE packages > were automatically built on qt 6.7. Hm, did that as well, but it immediately crashes on login. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483161] "Shake Cursor" effect should have some configuration options
https://bugs.kde.org/show_bug.cgi?id=483161 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483143] Wayland multi-monitor output order changing on session start
https://bugs.kde.org/show_bug.cgi?id=483143 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||xaver.h...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Zamundaaa --- Please attach your ~/.config/kwinoutputconfig.json when the screens are in the right order, and when the screens are in the wrong order -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483160] [wayland] Enlarged Cursor from "Shake Cursor" Effect Does Not Scale Well
https://bugs.kde.org/show_bug.cgi?id=483160 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483158] kwin_wayland spams logs with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=483158 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483157] [wayland] Spectacle Rectangle Select Resolution Preview Box will not appear at the bottom of the selection if there is a display arranged above/below
https://bugs.kde.org/show_bug.cgi?id=483157 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483159] [wayland] On a scaled display, icons jump very slightly to the side when being focused/unfocused with the mouse if the mouse moves over them during the focusing/unfocusing
https://bugs.kde.org/show_bug.cgi?id=483159 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483155] [wayland] Spectacle Rectangle Select has Inaccurate Sizing on Multi-Screen Multi-Scale Configurations
https://bugs.kde.org/show_bug.cgi?id=483155 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483154] Plamsa shell crash opening Steam menu
https://bugs.kde.org/show_bug.cgi?id=483154 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 483156] Dr Konqi UI issues
https://bugs.kde.org/show_bug.cgi?id=483156 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483153] Dolphin crashed when I restarted plasmashell
https://bugs.kde.org/show_bug.cgi?id=483153 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477738] [NVIDIA] kwin on Wayland black screen with cursor after most resume-from-RAM
https://bugs.kde.org/show_bug.cgi?id=477738 Dashon changed: What|Removed |Added CC||dashonww...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477223] Setting an icc profile causes reduced system performance.
https://bugs.kde.org/show_bug.cgi?id=477223 Dashon changed: What|Removed |Added CC||dashonww...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483029] Firefox On Plasma 6 Wayland Dragging and Rearranging A Bookmark Auto Opens A Bookmark Above It
https://bugs.kde.org/show_bug.cgi?id=483029 Shubham Arora changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||shubhamar...@protonmail.com --- Comment #1 from Shubham Arora --- Able to reproduce the issue and basedon the comments in mozilla tickets seems plasma 6 wayland specific. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452188] While playing Apex Legends player's aim (mouse) spins and looks straight downwards.
https://bugs.kde.org/show_bug.cgi?id=452188 Dashon changed: What|Removed |Added CC||dashonww...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483161] New: "Shake Cursor" effect should have some configuration options
https://bugs.kde.org/show_bug.cgi?id=483161 Bug ID: 483161 Summary: "Shake Cursor" effect should have some configuration options Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: eamonn...@protonmail.com Target Milestone: --- SUMMARY The "Shake Cursor" effect could benefit from a couple of configuration options, especially if it is to be enabled by default. The ones I have in mind are: - A configurable end delay. Right now the effect stays for a fairly long time. On macOS, if I'm remembering correctly, the effect ends pretty much as soon as you stop shaking the mouse. On Plasma, it stays for about 3-4 seconds. This may be desired by some, and not others, so exposing a configurable delay makes sense. - A configurable "start" delay / configuring the amount of shaking required. I haven't checked in a long time, but I think macOS allows you to configure how "much" you have to shake the cursor. Sure, this could be directly tied to mouse sensitivity, but people may want to configure this. I personally think the amount of shaking required is fine, but others may disagree. - A configurable cursor size. I find the cursor size fine and I think it's large enough that most people will see it (especially now that Plasma 6 sizes cursors properly regardless of scale factor, woohoo!) but some people might want a smaller, or even a larger cursor size. This could be a simple slider to set the value. - Perhaps a shortcut to enlarge the cursor? This is one I just thought of while writing this report, so it is not as well thought out, but something I wanted to mention as a just-in-case. There is the "Track Mouse" effect that may render this unnecessary, even if they achieve this in different ways. STEPS TO REPRODUCE N/A OBSERVED RESULT "Shake Cursor" effect has no configuration options. EXPECTED RESULT "Shake Cursor" effect should have some configuration options, such as the ones outlined above (although it need not be a prescriptive nor exhaustive list). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.8 Linux Zen KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from Nate Graham --- Thanks. The code here (https://invent.kde.org/frameworks/kcmutils/-/blob/master/src/qml/kcmlauncher.cpp?ref_type=heads#L14) clearly indicates that it'll open kcmshell6, so I think the most likely possibility is that you've still got the KF5 version of the kcmutils framework on your machine. Another one is that there's a downstream patch breaking this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=480835 --- Comment #3 from Dāvis --- Hmm this might be duplicated of https://bugs.kde.org/show_bug.cgi?id=480835 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 480835] plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when monitor is turned off
https://bugs.kde.org/show_bug.cgi?id=480835 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482768 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483113] Default cursor theme "Breeze" is not synchronized to SDDM
https://bugs.kde.org/show_bug.cgi?id=483113 Shubham Arora changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||shubhamar...@protonmail.com --- Comment #2 from Shubham Arora --- Can confirm with sddm 0.21.0-4 and Plasma 6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=464258 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464258] plasmashell crashed with the error The Wayland connection experienced a fatal error: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=464258 Dāvis changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=482768 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482768] Plasmashell crashes in KScreen::WaylandConfig::setupRegistry() when I turn my monitor off and back on
https://bugs.kde.org/show_bug.cgi?id=482768 Dāvis changed: What|Removed |Added CC||davis...@gmail.com --- Comment #2 from Dāvis --- I also got this same crash but I didn't turn off my monitor. Maybe it went into power saving mode? in log I see > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.graphsplasmoid", fileName: > "/usr/share/plasma/plasmoids/org.kde.graphsplasmoid/metadata.json") does not > match requested format "Plasma/Applet" > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.plasma.kclock_1x2", fileName: > "/usr/share/plasma/plasmoids/org.kde.plasma.kclock_1x2/metadata.json") does > not match requested format "Plasma/Applet" > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.plasma.kweather_1x4", fileName: > "/usr/share/plasma/plasmoids/org.kde.plasma.kweather_1x4/metadata.json") does > not match requested format "Plasma/Applet" > plasmashell[200110]: KPackageStructure of > KPluginMetaData(pluginId:"org.kde.merkuro.contact", fileName: > "/usr/share/plasma/plasmoids/org.kde.merkuro.contact/metadata.json") does not > match requested format "Plasma/Applet" > plasmashell[200110]: kf.coreaddons: The plugin > "/usr/lib/qt6/plugins/plasma/applets/plasma_applet_kweather_1x4.so" > explicitly states an Id in the embedded metadata, which is different from the > one derived from the filename The Id field from the KPlugin object in the > metadata should be removed > plasmashell[200110]: kscreen.kwayland: Connection to Wayland server timed out. > plasmashell[200110]: qt.core.qobject.connect: QObject::connect(QObject, > ConfigMonitor::Private): invalid nullptr parameter > plasmashell[200110]: KCrash: Application 'plasmashell' crashing... > crashRecursionCounter = 2 > systemd-coredump[200163]: [] Process 200110 (plasmashell) of user 1000 > dumped core. Note this looks very similar to https://bugs.kde.org/show_bug.cgi?id=464258 but message is different. Backtrace: Thread 18 (Thread 0x7ea495e006c0 (LWP 200136)): #0 0x7ea4b9aa5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5c8066e6a048) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5c8066e6a048, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7ea4b9aa5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5c8066e6a048, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7ea4b9aa8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5c8066e69ff0, cond=0x5c8066e6a020) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5c8066e6a020, mutex=0x5c8066e69ff0) at pthread_cond_wait.c:618 #5 0x7ea4b048685c in cnd_wait () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.2/src/util/u_queue.c:290 #7 0x7ea4b049e82c in impl_thrd_routine () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:67 #8 0x7ea4b9aa955a in start_thread (arg=) at pthread_create.c:447 #9 0x7ea4b9b26a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 17 (Thread 0x7ea497c006c0 (LWP 200133)): #0 0x7ea4b9aa5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5c8066e7e108) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5c8066e7e108, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87 #2 0x7ea4b9aa5f3f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5c8066e7e108, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x7ea4b9aa8750 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5c8066e7e0b0, cond=0x5c8066e7e0e0) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x5c8066e7e0e0, mutex=0x5c8066e7e0b0) at pthread_cond_wait.c:618 #5 0x7ea4b048685c in cnd_wait () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:135 #6 util_queue_thread_func () at ../mesa-24.0.2/src/util/u_queue.c:290 #7 0x7ea4b049e82c in impl_thrd_routine () at ../mesa-24.0.2/src/c11/impl/threads_posix.c:67 #8 0x7ea4b9aa955a in start_thread (arg=) at pthread_create.c:447 #9 0x7ea4b9b26a3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 16 (Thread 0x7ea4a7e006c0 (LWP 200121)): #0 0x7ea4b9aa5ebe in __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393,
[systemsettings] [Bug 483131] Cursor theme not applied to Flatpak Qt5 apps
https://bugs.kde.org/show_bug.cgi?id=483131 Shubham Arora changed: What|Removed |Added Summary|Cursor theme not applied to |Cursor theme not applied to |Flatpak Qt apps |Flatpak Qt5 apps -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482077] powerdevil can pass -1 to KIdleTime::addIdleTimeout()
https://bugs.kde.org/show_bug.cgi?id=482077 duha.b...@gmail.com changed: What|Removed |Added CC||dandrag...@gmail.com --- Comment #60 from duha.b...@gmail.com --- *** Bug 483158 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483158] kwin_wayland spams logs with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=483158 duha.b...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||duha.b...@gmail.com --- Comment #1 from duha.b...@gmail.com --- *** This bug has been marked as a duplicate of bug 482077 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483131] Cursor theme not applied to Flatpak Qt apps
https://bugs.kde.org/show_bug.cgi?id=483131 Shubham Arora changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||shubhamar...@protonmail.com Ever confirmed|0 |1 --- Comment #1 from Shubham Arora --- Can confirm. Able to reproduce this with qBittorrent. Looks like it affect qt5 flatpak applications only. Tested with https://flathub.org/apps/io.github.Arisotura.CoinKiller (QT6 flatpak) Icon works on it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423390] Bottom Plasma panel and desktop are not fully adjacent to screen border (1 pixel on the right and bottom) when PLASMA_USE_QT_SCALING=1 is set on X11
https://bugs.kde.org/show_bug.cgi?id=423390 --- Comment #18 from Nate Graham --- This bug report is about X11; please open a new one to track the issue on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483160] New: [wayland] Enlarged Cursor from "Shake Cursor" Effect Does Not Scale Well
https://bugs.kde.org/show_bug.cgi?id=483160 Bug ID: 483160 Summary: [wayland] Enlarged Cursor from "Shake Cursor" Effect Does Not Scale Well Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: eamonn...@protonmail.com Target Milestone: --- SUMMARY When the "Shake Cursor" effect is enabled, the enlarged cursor does not look sharp. This is true across display resolutions and scales. Due to the nature of this bug, I cannot easily get a good screenshot of it. Sorry. STEPS TO REPRODUCE 1. Enable the "Shake Cursor" effect 2. Shake Cursor :-) 3. Cursor does enlarge, but it is blurry/blocky. OBSERVED RESULT Enlarged cursor does not look good when scaled. EXPECTED RESULT Enlarged cursor looks crisp, as if the cursor was set to this size, mirroring the macOS effect this feature was inspired by. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.8 Linux Zen KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 482967] Show keyboard with default and super useful Plasma shortcuts
https://bugs.kde.org/show_bug.cgi?id=482967 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- IMO some app that can visualize all current shortcuts (programmatically) would be a great feature. It doesn't even need to be shipped by kde, as we expose dbus API to get all shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482182] Breeze is mixes up light & dark
https://bugs.kde.org/show_bug.cgi?id=482182 --- Comment #8 from Gustavo A. Díaz --- I've forgot to add, when I want to reinstall the package it says that can't be downloaded: sudo apt install plasma-integration --reinstall Reading package lists... Done Building dependency tree... Done Reading state information... Done Reinstallation of plasma-integration is not possible, it cannot be downloaded. Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 483156] Dr Konqi UI issues
https://bugs.kde.org/show_bug.cgi?id=483156 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483128] vertical floating panel bleeds into adjacent monitor when window maximized.
https://bugs.kde.org/show_bug.cgi?id=483128 Aleksey Zagorodnikov changed: What|Removed |Added CC||xglo...@gmail.com --- Comment #3 from Aleksey Zagorodnikov --- Created attachment 166905 --> https://bugs.kde.org/attachment.cgi?id=166905=edit Horizontal panel bleeds on second monitor Hi, I assume there is the same problem with my panels' arrangement. Maximized or not - it doesn't matter. Floating or fixed too. If I have a vertical panel on the left, then the horizontal panel on top or bottom will shift to another monitor. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 474471] [Feature request] In Rectangular Region mode, right-clicking on the screen area when there's no active selection should Cancel the Rectangle Region mode as if Esc were pressed
https://bugs.kde.org/show_bug.cgi?id=474471 Nate Graham changed: What|Removed |Added Status|ASSIGNED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483159] New: [wayland] On a scaled display, icons jump very slightly to the side when being focused/unfocused with the mouse if the mouse moves over them during the focusing/unfocusing
https://bugs.kde.org/show_bug.cgi?id=483159 Bug ID: 483159 Summary: [wayland] On a scaled display, icons jump very slightly to the side when being focused/unfocused with the mouse if the mouse moves over them during the focusing/unfocusing Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: eamonn...@protonmail.com Target Milestone: --- Created attachment 166904 --> https://bugs.kde.org/attachment.cgi?id=166904=edit Video of Jumpy Icon using Kate SUMMARY When focusing/unfocusing windows with Breeze decorations using the mouse, the icon will jump to the left very slightly if the mouse moves over them during the focusing/unfocusing, and then jump back to its regular position. I have attached a video of the issue. The video looks really strange and does not reflect how my desktop actually looks - It is not even nearly as blocky, and the purple line is actually the Spectacle region recording select preview, which jumps incorrectly once recording starts - These are issues unrelated to this bug, but I wanted to clarify why it looks the way it does. This issue is not present when using Alt+Tab, or when clicking inside of the window. This issue is also exclusive to scaled displays, it does not happen on my unscaled displays. STEPS TO REPRODUCE 1. Open a window on a scaled display 2. Focus/unfocus the window with the mouse, ensuring the mouse goes over the icon during the focusing. 3. Observe the icon jumping slightly to the side during this. OBSERVED RESULT Window icons jump slightly to the side when being focused/unfocused with the mouse, if the mouse moves over them to focus/unfocus. EXPECTED RESULT Window icons do not move when being focused, which is the behaviour on non-scaled displays. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.8 Linux Zen KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482182] Breeze is mixes up light & dark
https://bugs.kde.org/show_bug.cgi?id=482182 --- Comment #7 from Gustavo A. Díaz --- Hi, in my Notebook I can't fix this bug. I have: dpkg --list | grep plasma-integration ii plasma-integration 5.19.5-0xneon+20.04+focal+build11amd64Qt Platform Theme integration plugins for KDE Plasma ii plasma-integration5 6.0.0-0xneon+22.04+jammy+release+build40 amd64Qt Platform Theme integration plugins for KDE Plasma And will not upgrade. How to solve this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483105] shortcuts does not accept extended keys on a microsoft natural ergonomic keyboard 4000
https://bugs.kde.org/show_bug.cgi?id=483105 lpcor...@gmail.com changed: What|Removed |Added CC||lpcor...@gmail.com --- Comment #2 from lpcor...@gmail.com --- I confirm this same issue with version 6x. I can assign kcalc to another key combination, such as META+k, but the calculator key on the Microsoft 4000 ergo keyboard can no longer be assigned to this or any other app. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 478033] EWS accounts unusable - constantly lose authentication
https://bugs.kde.org/show_bug.cgi?id=478033 Nicky726 changed: What|Removed |Added CC||nicky...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 481937] After plasma6 update, VirtualBox VM is unusable with 3D acceleration turned off
https://bugs.kde.org/show_bug.cgi?id=481937 Liang Qi changed: What|Removed |Added CC||cavendish...@gmail.com --- Comment #11 from Liang Qi --- See also https://bugs.kde.org/show_bug.cgi?id=482965 for KDE 6 vm in VMware Fusion on MacBook Pro M3 Max. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483158] kwin_wayland spams logs with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=483158 Dandraghas changed: What|Removed |Added CC||dandrag...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483158] New: kwin_wayland spams logs with "QObject::startTimer: Timers cannot have negative intervals"
https://bugs.kde.org/show_bug.cgi?id=483158 Bug ID: 483158 Summary: kwin_wayland spams logs with "QObject::startTimer: Timers cannot have negative intervals" Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dandrag...@gmail.com Target Milestone: --- SUMMARY kwin_wayland spams logs with: Mar 10 20:53:31 archlinux kwin_wayland[1634]: QObject::startTimer: Timers cannot have negative intervals STEPS TO REPRODUCE 1. Start "plasma (wayland)" session 2. Execute "journalctl -f" SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 483114] Crash when opening details sidebar
https://bugs.kde.org/show_bug.cgi?id=483114 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 482169 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 482169] System Monitor in Plasma 6 crashes on clicking "Show Details Sidebar"
https://bugs.kde.org/show_bug.cgi?id=482169 Patrick Silva changed: What|Removed |Added CC||mokaz...@disroot.org --- Comment #10 from Patrick Silva --- *** Bug 483114 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483052] Plasma 6 - stuttering, redrawing previous frames? I have examples of video stuttering and typing stuttering.
https://bugs.kde.org/show_bug.cgi?id=483052 Zamundaaa changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #4 from Zamundaaa --- Okay, then this is https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480517] Icons only task manager and applet overlapping
https://bugs.kde.org/show_bug.cgi?id=480517 --- Comment #7 from Doug --- I'm still not reproducing with those steps. Operating System: KDE neon Testing Edition KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: AMD Radeon Pro WX 3200 Series -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483157] New: [wayland] Spectacle Rectangle Select Resolution Preview Box will not appear at the bottom of the selection if there is a display arranged above/below
https://bugs.kde.org/show_bug.cgi?id=483157 Bug ID: 483157 Summary: [wayland] Spectacle Rectangle Select Resolution Preview Box will not appear at the bottom of the selection if there is a display arranged above/below Classification: Applications Product: Spectacle Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: eamonn...@protonmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY If you have a display configuration where one display is above/below, Spectacle will not move the Resolution Preview box below the selection, even if the selection box is not visible on the upper display. If you have the upper/lower display arranged with an offset, such as more to the left/right and not directly aligned, then the preview will appear partially on the upper display even if it is not all visible on the upper display. If you have a setup where the upper/lower display is entirely offset, such as only touching at the corners, there is nowhere for the resolution preview box to be visible, but Spectacle will still draw it, although there is nowhere to see it. You can tell it is drawing it because if the resolution preview box moves from top to bottom, it will fade in/fade out, but no such animation plays. STEPS TO REPRODUCE 1. Activate Spectacle Rectangle Select on a display configuration as described above. 2. Draw a selection box at the top of the top display, or at a part on the bottom display where there is an offset such that content above this display will not draw on the upper display. 3. The Resolution Preview box is not visible. OBSERVED RESULT Spectacle Resolution Preview will not draw below the region select on multi-screen configurations with at least one vertical display. EXPECTED RESULT Spectacle Resolution Preview should always draw above/below itself if it is at the top/bottom of a display with no display above it to render on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.8 Linux Zen KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 483156] Dr Konqi UI issues
https://bugs.kde.org/show_bug.cgi?id=483156 --- Comment #1 from jaxad0...@gmail.com --- Just remembered, I had to go through the debug symbol download twice. First time, it looked like it fully finished, but the stack traces were still filled with question marks. I went back a screen and then to the back trace page again, redownloaded the symbols, and then the stack trace was filled out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property
https://bugs.kde.org/show_bug.cgi?id=479712 Matthias changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #17 from Matthias --- Sorry, we failed. That issue here is indeed solved and we encountered an independent problem in Qbittorrent. Closing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379474] KWin wakes up the monitor right after going to sleep
https://bugs.kde.org/show_bug.cgi?id=379474 k...@dinolek.me changed: What|Removed |Added CC||k...@dinolek.me --- Comment #20 from k...@dinolek.me --- Created attachment 166903 --> https://bugs.kde.org/attachment.cgi?id=166903=edit journalctl -t kwin_wayland -t org_kde_powerdevil -t ksmserver after kscreen-doctor -d off Still happens with plasma 6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482989] Scaling down always produces blurry display
https://bugs.kde.org/show_bug.cgi?id=482989 --- Comment #3 from medin --- (In reply to David Edmundson from comment #2) > Scaling at <100 will be supported better from Qt 6.7 onwards. Otherwise it > is rescaled by the compositor, which is what you're seeing here. When will it be released for Plasma6? And will it also solve scaling down for non Qt apps? While waiting, is there any command line or setting to add to any config file to resize all Qt toolbar icons to small (16), because for some apps like Spectacle, open/save dialogs... there are no settings to resize their toolbar icons. It was working last week with latest 5.27.10 even with toolbar resizing feature removed, so I suppose Plasma was reading the toolbar icons size from somewhere. I'm happy with just decreasing font to 9pt and decreasing toolbar icons to 16, instead of scaling down my whole desktop under 100% and suffering from unnecessary bugs, because most my apps as Qt based and 4 or 5 GTK apps. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478750] krunner is not evoked by typing on desktop on Wayland session without first clicking on the desktop
https://bugs.kde.org/show_bug.cgi?id=478750 --- Comment #3 from Doug --- (In reply to Dashon from comment #2) > I'm having the same issue on endeavourOS. It seems like the desktop does not > have focus. It works sometimes, but not all the time. I'll keep trying to > find a reproducible case. It seems to consistently not work on my first > virtual desktop even when it works on others. If I trigger it and then hit > escape enough times. Eventually it stops showing up. If I trigger krunner > via shortcut such as alt + space or restart plasmashell. It starts working > again. Except for on my first virtual desktop as mentioned before. Good catch- yes, the problem is only on virtual desktop 1. All other desktops are working as they should -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483142] [wayland] Pressing Enter on Application Dashboard Takes Newline Instead of Opening First Application in List
https://bugs.kde.org/show_bug.cgi?id=483142 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 482123 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 482123] Application Dashboard add new lines in search field
https://bugs.kde.org/show_bug.cgi?id=482123 Patrick Silva changed: What|Removed |Added CC||eamonn...@protonmail.com --- Comment #9 from Patrick Silva --- *** Bug 483142 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 483156] New: Dr Konqi UI issues
https://bugs.kde.org/show_bug.cgi?id=483156 Bug ID: 483156 Summary: Dr Konqi UI issues Classification: Applications Product: drkonqi Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jaxad0...@gmail.com Target Milestone: --- Created attachment 166902 --> https://bugs.kde.org/attachment.cgi?id=166902=edit Partial screenshot SUMMARY Dr Konqi could use some UI refinement. When downloading debug symbols, the view doesn't autoscroll to the latest line, making it look like Dr Konqi isn't doing anything. The preview screen has the log cutoff and weird spacing (see attachment). The final screen has a nonclickable bug URL, despite it being blue and underlined. Also, the generated and submitted stacktrace includes all of the debug symbol download lines. Would probably be good to remove those. STEPS TO REPRODUCE 1. Use Dr Konqi OBSERVED RESULT UI issues EXPECTED RESULT A better experience SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.2.2-4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483132] system settings high CPU usage opening firewall tab
https://bugs.kde.org/show_bug.cgi?id=483132 --- Comment #5 from Lucas Biaggi --- Could you test with firewalld? On Sun, 10 Mar 2024, 17:24 Paul Worrall, wrote: > https://bugs.kde.org/show_bug.cgi?id=483132 > > Paul Worrall changed: > >What|Removed |Added > > > Status|REPORTED|CONFIRMED > Ever confirmed|0 |1 > CC||p.r.worr...@gmail.com > > --- Comment #2 from Paul Worrall --- > I can reproduce this. I have the UFW firewall installed and the issue is > present whether it's enabled or disabled: while the KCM is selected my CPU > usage is about 50% on my two-core processor and when I switch to a > different > KCM the CPU drops to less than 10%. > > Setting to confirmed > > Operating System: Arch Linux > KDE Plasma Version: 6.0.1 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.2 > Kernel Version: 6.7.9-arch1-1 (64-bit) > Graphics Platform: Wayland > Processors: 2 × AMD A6-6400K APU with Radeon(tm) HD Graphics > Graphics Processor: AMD CEDAR > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483132] system settings high CPU usage opening firewall tab
https://bugs.kde.org/show_bug.cgi?id=483132 --- Comment #4 from Lucas Biaggi --- Could you inform which backend are you using? On Sun, 10 Mar 2024, 16:38 Erfan, wrote: > https://bugs.kde.org/show_bug.cgi?id=483132 > > Bug ID: 483132 >Summary: system settings high CPU usage opening firewall tab > Classification: Applications >Product: systemsettings >Version: 6.0.1 > Platform: Arch Linux > OS: Linux > Status: REPORTED > Severity: critical > Priority: NOR > Component: kcm_firewall > Assignee: plasma-b...@kde.org > Reporter: erfan.q...@gmail.com > CC: lucas.bia...@kde.org, tcanabr...@kde.org > Target Milestone: --- > > SUMMARY > *** > *** > when i open firewall setting in kde settings cpu usage going high and my > laptop > fan speed also last time systemsetting even can't show status of firewall > but > now its fixed with new update i get from arch but i have still cpu problem > > SOFTWARE/OS VERSIONS > Linux/KDE Plasma: Arch linux 6.0.1 > (available in About System) > KDE Plasma Version: 6.0.1 > KDE Frameworks Version: 6.0.0 > Qt Version: 6.6.2 > > ADDITIONAL INFORMATION > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483155] New: [wayland] Spectacle Rectangle Select has Inaccurate Sizing on Multi-Screen Multi-Scale Configurations
https://bugs.kde.org/show_bug.cgi?id=483155 Bug ID: 483155 Summary: [wayland] Spectacle Rectangle Select has Inaccurate Sizing on Multi-Screen Multi-Scale Configurations Classification: Applications Product: Spectacle Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: eamonn...@protonmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When Spectacle's Rectangle Select is activated, selecting a region will show the sizing in a box above or below the region select. However, this sizing is very inaccurate. Selecting a window on a 1080p screen will show it as being larger than the actual resolution of the screen. Selecting close to the whole 1080p screen will actually display a value approaching 3840x2160 (give or take 10-15 pixels), which is the resolution of my scaled display. On the scaled display, single, small windows can exceed measurements of 5,000 pixels in width and 3,000 pixels in height, which is of course not correct. Even if the displayed resolution is incorrect, screenshots saved on the scaled display are actually correct (i.e. instead of displaying 5,000 pixels, it will only be 2,000 pixels when saved). However this is NOT the case for screenshots on the non-scaled displays; the incorrect value Spectacle shows is the actual resolution the files are saved as - This issue is probably the same as Bug 478426. STEPS TO REPRODUCE 1. Activate region select with Spectacle 2. Select a region 3. Size is not accurate OBSERVED RESULT The resolution preview for Spectacle Rectangle Select is inaccurate. EXPECTED RESULT The resolution preview for Spectacle Rectangle Select should be accurate, reflecting the actual window sizes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.8 Linux Zen KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Possibly related to Bug 478426. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483152] [wayland] Windows with Breeze Window Decorations have 1px Extra Border on the Top and Left with Fractional Scaling
https://bugs.kde.org/show_bug.cgi?id=483152 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483154] Plamsa shell crash opening Steam menu
https://bugs.kde.org/show_bug.cgi?id=483154 --- Comment #1 from jaxad0...@gmail.com --- Created attachment 166899 --> https://bugs.kde.org/attachment.cgi?id=166899=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483154] New: Plamsa shell crash opening Steam menu
https://bugs.kde.org/show_bug.cgi?id=483154 Bug ID: 483154 Summary: Plamsa shell crash opening Steam menu Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: jaxad0...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.0.0) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.6-arch1-1 x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 6.0.0 [CoredumpBackend] -- Information about the crash: Plasma shell crashed trying to open the Steam app menu in the system tray. 6.0.0 from Arch testing repo. The crash can be reproduced sometimes. -- Backtrace (Reduced): #5 0x77c33b669b8e in std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/13.2.1/bits/atomic_base.h:837 #6 std::atomic::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/13.2.1/atomic:577 #7 QAtomicOps::loadRelaxed (_q_value=, _q_value=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qatomic_cxx11.h:201 #8 QBasicAtomicPointer::loadRelaxed (this=, this=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qbasicatomic.h:172 #9 QtSharedPointer::ExternalRefCountData::getAndRef (obj=obj@entry=0x58b8799b9220) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qsharedpointer.cpp:1407 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[XWaylandVideoBridge] [Bug 479178] xwaylandvideobridge doesn't work, shares white/black screen
https://bugs.kde.org/show_bug.cgi?id=479178 --- Comment #3 from Dashon --- I believe this issue is also related to this other issue https://bugs.kde.org/show_bug.cgi?id=476846. It's just not outright crashing yet. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483153] New: Dolphin crashed when I restarted plasmashell
https://bugs.kde.org/show_bug.cgi?id=483153
Bug ID: 483153
Summary: Dolphin crashed when I restarted plasmashell
Classification: Applications
Product: dolphin
Version: unspecified
Platform: openSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: j...@holodeck1.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (24.04.70)
Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.7-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 6.0.80 [CoredumpBackend]
-- Information about the crash:
I noticed that the panel with task manager got stuck in always visible state (I
have it set to auto-hide) and covering lower parts of windows (status bars). At
the same time I had Dolphin window open, but not focused. So I decided to
restart plasmashell. When it restarted Dolphin crashed.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
This GDB supports auto-downloading debuginfo from the following URLs:
[XWaylandVideoBridge] [Bug 479178] xwaylandvideobridge doesn't work, shares white/black screen
https://bugs.kde.org/show_bug.cgi?id=479178 Dashon changed: What|Removed |Added CC||dashonww...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479712] Plasma 6's SNI implementation doesn't respect the IconThemePath property
https://bugs.kde.org/show_bug.cgi?id=479712 Nicolas changed: What|Removed |Added CC||nico...@hoeft.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483150] Window preview covers context menu
https://bugs.kde.org/show_bug.cgi?id=483150 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483146] [wayland] Opening Display Configuration Does Not Select Current Display
https://bugs.kde.org/show_bug.cgi?id=483146 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483148] "Move to [activity name]" doesn't move window and instead shows window on all activities
https://bugs.kde.org/show_bug.cgi?id=483148 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483149] Konsole's content doesn't update/is stuck/frozen
https://bugs.kde.org/show_bug.cgi?id=483149 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 483151] Skanpage scans only 75dpi
https://bugs.kde.org/show_bug.cgi?id=483151 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483147] [wayland] Overview Effect Calculator Sometimes Shows "aborted" on some/all displays, usually on first calculation of the session
https://bugs.kde.org/show_bug.cgi?id=483147 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483144] [wayland] Opening some windows on a scaled display shows them distorted while they are loading
https://bugs.kde.org/show_bug.cgi?id=483144 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483142] [wayland] Pressing Enter on Application Dashboard Takes Newline Instead of Opening First Application in List
https://bugs.kde.org/show_bug.cgi?id=483142 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483143] Wayland multi-monitor output order changing on session start
https://bugs.kde.org/show_bug.cgi?id=483143 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483141] KMail doesn't exit/froze/hung
https://bugs.kde.org/show_bug.cgi?id=483141 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483152] New: [wayland] Windows with Breeze Window Decorations have 1px Extra Border on the Top and Left with Fractional Scaling
https://bugs.kde.org/show_bug.cgi?id=483152 Bug ID: 483152 Summary: [wayland] Windows with Breeze Window Decorations have 1px Extra Border on the Top and Left with Fractional Scaling Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: eamonn...@protonmail.com Target Milestone: --- Created attachment 166898 --> https://bugs.kde.org/attachment.cgi?id=166898=edit Screenshot showing the extra border SUMMARY Windows which have the new KDE window borders (i.e. any system application, but not something like Firefox that draws its own CSD) will display a 1px wider window border on the left and top, only on scaled displays - Or at least, on my 150% scaled display. On non-scaled displays, the window displays fine. The extra border is most noticeable on the left, but it is also along the top, and it extends a little to the top-right corner as well, but it abruptly cuts off. I realise this probably sounds *incredibly* petty, but the 1px extra on the left is surprisingly noticeable. I have attached a screenshot, where you can zoom into the left and see the extra pixel. I have attached a screenshot of Konsole, plese zoom in quite far (i.e. 1600% in Gwenview) to see it better. You can see the border is all the way along the leftm and all the way along the top, but only a little on the top-right, and not at all along the bottom where it is still 1px. It is my opinion that having a 1px border all the way around the window looks better even on scaled displays, but having a consistent 2px border is probably also ok as long as it extends all the way around the window (I assume one of these is the intended functionality). STEPS TO REPRODUCE 1. Open a window on a scaled display, or at least, a 150% scaled display. 2. Window decorations have one extra pixel on the left and top only on the scaled display. On the non-scaled display, it is 1px consistently. OBSERVED RESULT Window border have 1px extra on the left side, on the top side, and a little on the top-right, but only on my 150% scaled display. EXPECTED RESULT Window border sizing is consistent, either 1px or 2px (or some other size), all the way around on scaled displays. The border is consistently 1px all the way around on non-scaled displays. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.8 Linux Zen KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION - I am using the Breeze Dark theme. - Issue is not present when window decorations are hidden, because the border is hidden too. - GTK applications that draw their own window decorations are unaffected. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 482831] Krunner settings do not show up
https://bugs.kde.org/show_bug.cgi?id=482831 András Manţia changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from András Manţia --- Mar 10 20:30:22 stein.andtib krunner[5664]: kf.kio.gui: Could not find an executable named: "kcmshell5" Mar 10 20:30:22 stein.andtib krunner[5664]: QObject::connect(KProcessRunner, KJob): invalid nullptr parameter Mar 10 20:30:22 stein.andtib krunner[5664]: QObject::connect(KProcessRunner, KJob): invalid nullptr parameter Why does it try to start kcmshell5? andris@stein: ~ > krunner -v krunner 6.0.0 andris@stein: ~ > ps uax | grep krunner andris5664 0.0 0.4 6824540 288388 ? Ssl Feb29 3:42 /usr/bin/krunner andris 25957 0.0 0.0 8216 816 pts/16 S+ 20:31 0:00 grep --color=auto krunner andris@stein: ~ > which krunner /usr/bin/krunner andris@stein: ~ > ls /usr/bin/kcmshell* /usr/bin/kcmshell6 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480489] Kate crashes when using search tab
https://bugs.kde.org/show_bug.cgi?id=480489 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 480489] Kate crashes when using search tab
https://bugs.kde.org/show_bug.cgi?id=480489 --- Comment #4 from Christoph Cullmann --- https://invent.kde.org/utilities/kate/-/merge_requests/1418 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466499] Opacity of desktop wallpaper can be changed with hotkey -> desktop fades to black
https://bugs.kde.org/show_bug.cgi?id=466499 --- Comment #1 from bastimeyer...@gmail.com --- Still a problem on 6.0.1. Tested on Wayland... -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 483151] New: Skanpage scans only 75dpi
https://bugs.kde.org/show_bug.cgi?id=483151 Bug ID: 483151 Summary: Skanpage scans only 75dpi Classification: Applications Product: Skanpage Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: g_...@hotmail.com Target Milestone: --- SUMMARY When I launch a scan in skanpage, no matter the dpi I choose, it will default to 75 dpi STEPS TO REPRODUCE 1. Open skanpage 2. select a resolution higher than 75 dpi 3. perform the scan OBSERVED RESULT The saved file has 75 dpi resolution EXPECTED RESULT The saved file has the resolution chosen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0 Qt Version: 6.6 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
