[plasmashell] [Bug 486768] [git master] - Open app in Icon Only Task manager use more space than closed app.
https://bugs.kde.org/show_bug.cgi?id=486768 Bharadwaj Raju changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||6a0d822c6aea8944fec31bd3881 ||3fba1fe4fb7d5 --- Comment #5 from Bharadwaj Raju --- Git commit 6a0d822c6aea8944fec31bd38813fba1fe4fb7d5 by Bharadwaj Raju. Committed on 13/05/2024 at 08:25. Pushed by bharadwaj-raju into branch 'master'. applets/taskmanager: Fix launcher icon widths when in icons-only mode Commit d1b33d1a9dc872e9a2af042152d6ab5ed2617e4e introduced logic to use height / num_rows as the width for launcher-type (no open windows) icons. This makes sense for Icons-and-Text TM, but leads to incorrect widths in the Icons-only TM. M +1-1applets/taskmanager/package/contents/ui/Task.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/6a0d822c6aea8944fec31bd38813fba1fe4fb7d5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 482519] Copy dialog has disappeared
https://bugs.kde.org/show_bug.cgi?id=482519 Bharadwaj Raju changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |kio-bugs-n...@kde.org CC||kdelibs-b...@kde.org Version|24.02.0 |6.0.0 Product|dolphin |frameworks-kio Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482519] Copy dialog has disappeared
https://bugs.kde.org/show_bug.cgi?id=482519 Bharadwaj Raju changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482468] Plasma 6 Floating Panel unfloat distance is more than the designed 12px
https://bugs.kde.org/show_bug.cgi?id=482468 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #5 from Bharadwaj Raju --- (In reply to João Sousa from comment #3) > Thank you for the clarification. So I guess that design setting changed from > the Plasma 5 panel then? Any reason why? The reason is written as a comment in that code. It avoids an issue (https://bugs.kde.org/show_bug.cgi?id=476743) with KWin's snap-to-panel behavior. > The panel floating mode seems to be designed with a default 8px gap distance > from screen edges (and not 9px as I have mentioned on my report). Any chance > that this 8px value can be used instead for the "property int > defloatDistance"? That would potentially allow the use of an identical value > of 8 px as minimal tiling window padding? I tested multiple values, including 8px. It wasn't enough, I found we needed a 12px distance to avoid the snap-to-panel behavior from activating. Other potential solutions can be investigated. Nate suggested disabling the snapping completely when in floating mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483941] Activating a panel applet without any expanded view (like Minimize All or Show Desktop) breaks Autohide and Dodge Windows
https://bugs.kde.org/show_bug.cgi?id=483941 Bharadwaj Raju changed: What|Removed |Added Assignee|plasma-b...@kde.org |nicc...@venerandi.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483941] New: Activating a panel applet without any expanded view (like Minimize All or Show Desktop) breaks Autohide and Dodge Windows
https://bugs.kde.org/show_bug.cgi?id=483941 Bug ID: 483941 Summary: Activating a panel applet without any expanded view (like Minimize All or Show Desktop) breaks Autohide and Dodge Windows Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bharadwaj.raju...@protonmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY If the panel is in Dodge Windows or Autohide mode, then clicking a widget like Minimize All or Show Desktop breaks the autohiding behavior. That is, the panel does not hide away even if the mouse is not on it, and a window is touching it. Behavior is restored if I open and close the system tray. STEPS TO REPRODUCE 1. Set panel to Dodge Windows or Autohide 2. Click Minimize All or Show Desktop OBSERVED RESULT Autohiding behavior breaks EXPECTED RESULT Autohiding behavior keeps working SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.0 Kernel Version: 6.6.11-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Reason why this happens: PanelView::restoreAutoHide() disables autohide if the panel's status is NeedsAttentionStatus or higher. Recently https://invent.kde.org/plasma/libplasma/-/merge_requests/1036 made a change so that when an applet is activated, the panel gets NeedsAttentionStatus. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 391578] Have kded or plasmashell handle volume-related keyboard shortcuts so they don't stop working when all Audio Volume applet/widget instances are removed
https://bugs.kde.org/show_bug.cgi?id=391578 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-pa/-/commit/e7830 ||539923c871243f07a055c6a8dd6 ||dcc0fafd Status|ASSIGNED|RESOLVED --- Comment #18 from Bharadwaj Raju --- Git commit e7830539923c871243f07a055c6a8dd6dcc0fafd by Bharadwaj Raju. Committed on 16/03/2024 at 07:39. Pushed by bharadwaj-raju into branch 'master'. Create KDED service to handle global shortcuts and OSDs New KDED service which handles global shortcuts and OSDs, called "audioshortcutsservice". Now these functions don't depend on an applet existing. See plasma-desktop#113 M +1-0CMakeLists.txt D +0-64 applet/contents/code/icon.js M +3-5applet/contents/ui/ListItemBase.qml M +16 -301 applet/contents/ui/main.qml M +46 -7src/CMakeLists.txt A +54 -0src/audioicon.cpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +28 -0src/audioicon.h [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] R +0-0src/dbus/osdService.xml [from: src/qml/dbus/osdService.xml - 100% similarity] R +0-0src/globalconfig.kcfg [from: src/qml/globalconfig.kcfg - 100% similarity] R +1-1src/globalconfig.kcfgc [from: src/qml/globalconfig.kcfgc - 086% similarity] R +0-0src/globalconfigskeleton.h [from: src/qml/globalconfigskeleton.h - 100% similarity] M +4-4src/kcm/ui/MuteButton.qml D +0-27 src/kcm/ui/icon.js A +22 -0src/kded/CMakeLists.txt A +367 -0src/kded/audioshortcutsservice.cpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +51 -0src/kded/audioshortcutsservice.h [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +7-0src/kded/audioshortcutsservice.json A +2-0src/kded/audioshortcutsservice.json.license D +0-55 src/qml/globalactioncollection.cpp D +0-48 src/qml/globalactioncollection.h A +59 -0src/qml/globalservice.cpp [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] A +29 -0src/qml/globalservice.h [License: LGPL(3+eV) LGPL(v3.0) LGPL(v2.1)] M +1-0src/qml/listitemmenu.cpp M +1-1src/qml/listitemmenu.h M +6-7src/qml/microphoneindicator.cpp M +3-3src/qml/microphoneindicator.h M +12 -5src/qml/plugin.cpp D +0-36 src/qml/volumeosd.cpp D +0-24 src/qml/volumeosd.h R +0-0src/volumefeedback.cpp [from: src/qml/volumefeedback.cpp - 100% similarity] R +0-0src/volumefeedback.h [from: src/qml/volumefeedback.h - 100% similarity] https://invent.kde.org/plasma/plasma-pa/-/commit/e7830539923c871243f07a055c6a8dd6dcc0fafd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443036] Metabug: let keyboard shortcuts live somewhere persistent, rather than in applets
https://bugs.kde.org/show_bug.cgi?id=443036 Bug 443036 depends on bug 391578, which changed state. Bug 391578 Summary: Have kded or plasmashell handle volume-related keyboard shortcuts so they don't stop working when all Audio Volume applet/widget instances are removed https://bugs.kde.org/show_bug.cgi?id=391578 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 Bharadwaj Raju changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/bluez-qt/-/commit/3c ||60d9e3db6f9d236f1e6a166303f ||51cc6374119 Resolution|--- |FIXED --- Comment #7 from Bharadwaj Raju --- Git commit 3c60d9e3db6f9d236f1e6a166303f51cc6374119 by Bharadwaj Raju. Committed on 15/02/2024 at 10:48. Pushed by bharadwaj-raju into branch 'master'. Fix connecting to org.freedesktop.DBus.ObjectManager InterfacesAdded The metatype also needs to be qRegisterMetaType'd in addition to qDBusRegisterMetaType and Q_DECLARE_METATYPE. I still don't know why it worked in plasmawindowed though… M +1-0src/manager_p.cpp https://invent.kde.org/frameworks/bluez-qt/-/commit/3c60d9e3db6f9d236f1e6a166303f51cc6374119 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633
--- Comment #5 from Bharadwaj Raju ---
Found a "fix", but it's too strange. Connecting to the signal like this works:
void ManagerPrivate::interfacesAdded2(const QDBusObjectPath , const
QMap> );
// ...
QDBusConnection::systemBus().connect(QStringLiteral("org.bluez"),
QStringLiteral("/"),
QStringLiteral("org.freedesktop.DBus.ObjectManager"),
QStringLiteral("InterfacesAdded"),
this,
SLOT(interfacesAdded2(QDBusObjectPath,
QMap>)));
But not if I use a method with QVariantMapMap in the signature, even though
QVariantMapMap is typedef'd to be exactly that. It's already
Q_DECLARE_METATYPE'd as well.
And for some reason the same QVariantMapMap connect call works in
plasmawindowed but not plasmashell or systemsettings. What could possibly be
different?
--
You are receiving this mail because:
You are watching all bug changes.
[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633
--- Comment #4 from Bharadwaj Raju ---
Observing output with kf.bluez debug logs turned on:
For plasmawindowed (where it works), the output goes like:
kf.bluezqt: Rfkill global state changed: BluezQt::Rfkill::Unblocked
kf.bluezqt: Setting usable adapter QSharedPointer(BluezQt::Adapter(0xf5b5b0))
kf.bluezqt: Rfkill global state changed: BluezQt::Rfkill::Unblocked
kf.bluezqt: Setting usable adapter QSharedPointer(QObject(0x0))
kf.bluezqt: Unhandled property change "org.bluez.Adapter1" QMap(("Class",
QVariant(uint, 0))("Discovering", QVariant(bool, false))("PowerState",
QVariant(QString, "on"))("Powered", QVariant(bool, false))) QList()
kf.bluezqt: Setting usable adapter QSharedPointer(BluezQt::Adapter(0x14ba950))
Notice how a non-null adapter was set.
For KCM (where it doesn't), the output is:
kf.bluezqt: Rfkill global state changed: BluezQt::Rfkill::Unblocked
kf.bluezqt: Setting usable adapter QSharedPointer(BluezQt::Adapter(0x25b8b40))
qt.dbus.integration: Could not connect "org.freedesktop.DBus.ObjectManager" to
"InterfacesAdded"
kf.bluezqt: Rfkill global state changed: BluezQt::Rfkill::Unblocked
kf.bluezqt: Setting usable adapter QSharedPointer(QObject(0x0))
kf.bluezqt: Unhandled property change "org.bluez.Adapter1" QMap(("Pairable",
QVariant(bool, true))) QList()
kf.bluezqt: Unhandled property change "org.bluez.Adapter1" QMap(("UUIDs",
QVariant(QStringList, QList("110e--1000-8000-00805f9b34fb",
"111f--1000-8000-00805f9b34fb", "1200--1000-8000-00805f9b34fb",
"1132--1000-8000-00805f9b34fb", "1133--1000-8000-00805f9b34fb",
"110c--1000-8000-00805f9b34fb", "1800--1000-8000-00805f9b34fb",
"112f--1000-8000-00805f9b34fb", "1801--1000-8000-00805f9b34fb",
"1106--1000-8000-00805f9b34fb", "180a--1000-8000-00805f9b34fb",
"1104--1000-8000-00805f9b34fb", "111e--1000-8000-00805f9b34fb",
"1105--1000-8000-00805f9b34fb",
"5005--1000-8000-0002ee01" QList()
[lots more lines]
A non-null adapter was never set again.
I wonder if `qt.dbus.integration: Could not connect
"org.freedesktop.DBus.ObjectManager" to "InterfacesAdded"` is relevant at all?
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 481045] Crash (sometimes) in QQmlMetaType::propertyCache when going to a different KCM in Energy Saving > Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=481045
--- Comment #1 from Bharadwaj Raju ---
Interestingly the base is 0x0 in lookupScopeObjectProperty, is that normal?
Anyway, from some poking in GDB it appears that the file it happens in is
"kcm/kcm_powerdevilprofilesconfig/ComboBoxWithIcon.qml", line 28, which is:
const modelIndex = model.index(currentIndex, 0);
I guess the model is being freed while the page gets unloaded, and sometimes
that results in a call to freed memory?
---
(gdb) frame 11
#11 QV4::QQmlContextWrapper::lookupScopeObjectProperty (l=0x1044610,
engine=0x87e180, base=0x0)
at
/usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4qmlcontext.cpp:637
637 return callWithScopeObject(engine, base, [l, engine, base](const
Value ) {
(gdb) print engine
$3 = (QV4::ExecutionEngine *) 0x87e180
(gdb) print engine->stackTrace(-1)
$4 = {> =
{> = {}, }, d = {d = 0x1a5c620,
ptr = 0x1a5c630, size = 1}}
(gdb) print ((QV4::StackFrame *)(0x1a5c630))->source
$5 = {d = {d = 0x0, ptr = 0x7fffa4032c34
u"qrc:/kcm/kcm_powerdevilprofilesconfig/ComboBoxWithIcon.qml", size = 58},
static _empty = 0 u'\000'}
(gdb) print ((QV4::StackFrame *)(0x1a5c630))->function
$6 = {d = {d = 0x0, ptr = 0x0, size = 0}, static _empty = 0 u'\000'}
(gdb) print ((QV4::StackFrame *)(0x1a5c630))->line
$7 = 28
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 481045] New: Crash (sometimes) in QQmlMetaType::propertyCache when going to a different KCM in Energy Saving > Advanced Power Settings
https://bugs.kde.org/show_bug.cgi?id=481045 Bug ID: 481045 Summary: Crash (sometimes) in QQmlMetaType::propertyCache when going to a different KCM in Energy Saving > Advanced Power Settings Classification: Applications Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: bharadwaj.raju...@protonmail.com CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY System Settings sometimes crashes when going to a different KCM from Energy Saving > Advanced Power Settings > Other Settings > Related Pages. STEPS TO REPRODUCE 1. Open the Energy Saving KCM 2. Go to Advanced Power Settings 3. Click, for example, Notifications: Power Management 4. Repeat if necessary BACKTRACE #0 0x751a41bf in QQmlMetaType::propertyCache (obj=obj@entry=0x26867a0, version=version@entry=...) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/qml/qqmlmetatype.cpp:1328 #1 0x75145582 in QQmlData::createPropertyCache (object=object@entry=0x26867a0) at /usr/include/qt6/QtCore/qversionnumber.h:374 #2 0x75059afc in QQmlData::ensurePropertyCache (object=0x26867a0) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/redhat-linux-build/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/qml/qqmldata_p.h:257 #3 QV4::QObjectWrapper::create (engine=, engine@entry=0x87e180, object=object@entry=0x26867a0) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:796 #4 0x75061dd3 in QV4::QObjectWrapper::wrap_slowPath (engine=0x87e180, object=0x26867a0) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:699 #5 0x74fe48fc in QV4::ExecutionEngine::fromData (this=0x87e180, metaType=..., ptr=0x7fffa5d0, container=0x7fffbcf2a6e0, property=74, flags=3) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4engine.cpp:1827 #6 0x74fe5711 in QV4::ExecutionEngine::fromVariant (this=, variant=, parent=, property=, flags=) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4engine.cpp:1968 #7 0x75063035 in QV4::loadProperty (v4=0x87e180, wrapper=0x7fffbcf2a6e0, object=, property=) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:217 #8 0x75056942 in QV4::QObjectWrapper::lookupPropertyGetterImpl:: > (revertLookup=..., flags=..., object=, engine=0x87e180, lookup=0x1044610) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/redhat-linux-build/include/QtQml/6.6.0/QtQml/private/../../../../../../src/qml/jsruntime/qv4qobjectwrapper_p.h:299 #9 operator() (obj=, __closure=) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4qmlcontext.cpp:641 #10 callWithScopeObject > (c=..., base=0x0, engine=0x87e180) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4qmlcontext.cpp:632 #11 QV4::QQmlContextWrapper::lookupScopeObjectProperty (l=0x1044610, engine=0x87e180, base=0x0) at /usr/src/debug/qt6-qtdeclarative-6.6.0-1.fc39.x86_64/src/qml/jsruntime/qv4qmlcontext.cpp:637 #12 0x7fff895d8701 in ??? () #13 0x in ??? () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477133] OSD for Volume and KB Layout change doesn't always show Wayland
https://bugs.kde.org/show_bug.cgi?id=477133 --- Comment #14 from Bharadwaj Raju --- (In reply to kel...@yahoo.com from comment #10) > (In reply to Vlad Zahorodnii from comment #7) > > Can you run plasmashell with WAYLAND_DEBUG=1, press volume keys and attach > > the log to the bug report? > > I'm going to need some help on exactly how to do this one and save the log. > I ran WAYLAND_DEBUG=1 plasmashell --replace >> log.txt, but the output is > not saving to the file. What should I do? Debug output is printed to stderr, not stdout. To redirect that use: WAYLAND_DEBUG=1 plasmashell --replace 2>> log.txt -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478516] In the task manager, the app icon disappears when there is a running job (or badge in general)
https://bugs.kde.org/show_bug.cgi?id=478516 Bharadwaj Raju changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kdeclarative/-/commi ||t/282928cd17deb976769d9be81 ||734df97a01f81c0 Resolution|--- |FIXED --- Comment #3 from Bharadwaj Raju --- Git commit 282928cd17deb976769d9be81734df97a01f81c0 by Bharadwaj Raju. Committed on 14/12/2023 at 18:14. Pushed by ngraham into branch 'master'. Fix badge effect The path to the QSB file was wrong (needed to specify qrc:), and the fragment shader had a name mismatch with the vertex output (see https://doc.qt.io/qt-6/qml-qtquick-shadereffect.html#having-one-shader-only) M +1-1src/qmlcontrols/graphicaleffects/BadgeEffect.qml M +2-2src/qmlcontrols/graphicaleffects/badge.frag https://invent.kde.org/frameworks/kdeclarative/-/commit/282928cd17deb976769d9be81734df97a01f81c0 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] Bluetooth tray applet sometimes doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 --- Comment #3 from Bharadwaj Raju --- Interestingly it doesn't seem to affect plasmawindowed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478516] In the task manager, the app icon disappears when there is a running job (or badge in general)
https://bugs.kde.org/show_bug.cgi?id=478516 Bharadwaj Raju changed: What|Removed |Added Keywords||qt6 --- Comment #1 from Bharadwaj Raju --- >From plasmashell: Failed to find shader ":/qt/qml/org/kde/graphicaleffects/:/shaders/badge.frag.qsb" ShaderEffect: Failed to deserialize QShader from :/qt/qml/org/kde/graphicaleffects/:/shaders/badge.frag.qsb. Either the filename is incorrect, or it is not a valid .qsb file. In Qt 6 shaders must be preprocessed using the Qt Shader Tools infrastructure. The vertexShader and fragmentShader properties are now URLs that are expected to point to .qsb files generated by the qsb tool. See https://doc.qt.io/qt-6/qtshadertools-index.html for more information. ShaderEffect: shader preparation failed for qrc:/qt/qml/org/kde/graphicaleffects/:/shaders/badge.frag.qsb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478516] New: In the task manager, the app icon disappears when there is a running job (or badge in general)
https://bugs.kde.org/show_bug.cgi?id=478516 Bug ID: 478516 Summary: In the task manager, the app icon disappears when there is a running job (or badge in general) Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: bharadwaj.raju...@protonmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 164165 --> https://bugs.kde.org/attachment.cgi?id=164165=edit screenshot SUMMARY If an app has a badge, its icon doesn't appear. Appears to have something to do with changes to shader infrastructure in Qt 6. Screenshot attached. STEPS TO REPRODUCE 1. Open an app which can have a badge. 2. Make it get a badge somehow. 3. Check the task manager. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.0 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409190] Have kded or plasmashell handle media-related keyboard shortcuts so they don't stop working when all Audio Volume applet/widget instances are removed or when more than one i
https://bugs.kde.org/show_bug.cgi?id=409190 Bharadwaj Raju changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||bharadwaj.raju777@protonmai ||l.com Resolution|--- |FIXED --- Comment #19 from Bharadwaj Raju --- Seems fixed with https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2895 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443036] Metabug: let keyboard shortcuts live somewhere persistent, rather than in applets
https://bugs.kde.org/show_bug.cgi?id=443036 Bug 443036 depends on bug 409190, which changed state. Bug 409190 Summary: Have kded or plasmashell handle media-related keyboard shortcuts so they don't stop working when all Audio Volume applet/widget instances are removed or when more than one is present https://bugs.kde.org/show_bug.cgi?id=409190 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443036] Metabug: let keyboard shortcuts live somewhere persistent, rather than in applets
https://bugs.kde.org/show_bug.cgi?id=443036 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |MOVED CC||bharadwaj.raju777@protonmai ||l.com Status|CONFIRMED |RESOLVED --- Comment #5 from Bharadwaj Raju --- Invent issue: https://invent.kde.org/plasma/plasma-desktop/-/issues/113 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] Bluetooth tray applet sometimes doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 --- Comment #2 from Bharadwaj Raju --- OK, I can reproduce it consistently by waking my laptop from suspend (close lid and reopen). -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] Bluetooth tray applet sometimes doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 --- Comment #1 from Bharadwaj Raju --- Observation: when this happens and Bluetooth is off at that moment, I don't see the enable switch. I just see the enable button. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] Bluetooth tray applet sometimes doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 Bharadwaj Raju changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 477633] New: Bluetooth tray applet sometimes doesn't show any devices even if KCM does
https://bugs.kde.org/show_bug.cgi?id=477633 Bug ID: 477633 Summary: Bluetooth tray applet sometimes doesn't show any devices even if KCM does Classification: Plasma Product: Bluedevil Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: system tray Assignee: plasma-b...@kde.org Reporter: bharadwaj.raju...@protonmail.com CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY Bluetooth tray applet sometimes doesn't show any devices even if KCM does. Restarting plasmashell makes it work fine. There doesn't seem to be anything directly relevant in Plasmashell logs. STEPS TO REPRODUCE I'm not exactly sure what causes this, I'll try some experiments (turning it off and on) and see if anything consistent emerges. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477325] KWin Crash in KWin::OutputInterface::handle() after closing and opening laptop lid
https://bugs.kde.org/show_bug.cgi?id=477325 Bharadwaj Raju changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Bharadwaj Raju --- Yeah, I haven't had a crash since. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477426] System Tray applets sometimes fail to open
https://bugs.kde.org/show_bug.cgi?id=477426 --- Comment #3 from Bharadwaj Raju --- I've noticed it with Bluetooth and Notifications so far. Both of them I was trying to open from the expanded systray. That said, I think only one applet is affected at a time. Like, if Bluetooth is failing to open, I try the other applets and they work fine (and print the same message). Similarly for Notifications. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475257] volume and brightness osd has different backgrounds on desktop and lockscreen
https://bugs.kde.org/show_bug.cgi?id=475257 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #3 from Bharadwaj Raju --- But wait, isn't the SVG image path also controlled by the theme QML? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477426] System Tray applets sometimes fail to open
https://bugs.kde.org/show_bug.cgi?id=477426 --- Comment #1 from Bharadwaj Raju --- Worth noting that right click still works on such applets. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477426] System Tray applets sometimes fail to open
https://bugs.kde.org/show_bug.cgi?id=477426 Bharadwaj Raju changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477426] New: System Tray applets sometimes fail to open
https://bugs.kde.org/show_bug.cgi?id=477426 Bug ID: 477426 Summary: System Tray applets sometimes fail to open Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bharadwaj.raju...@protonmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Sometimes, system tray applets will fail to open. I've observed it with different applets at different times. When this happens, the following is printed by plasmashell: QMetaMethod::invoke: cannot convert formal parameter 0 from QObject * in call to QQuickMouseArea::pressed(QQuickMouseEvent*) kde.systemtray: Failed to invoke onPressed signal on CompactRepresentation_QMLTYPE_749(0x2fec030, parent=0x2fddb70, geometry=0,0 32x47) with QQuickMouseEvent(0x18126c8) However, the same line is printed for applets which do open, so may or may not be relevant? Restarting plasmashell usually solves the issue. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477424] OSDs on lockscreen incorrectly use dark background
https://bugs.kde.org/show_bug.cgi?id=477424 Bharadwaj Raju changed: What|Removed |Added CC||visual-des...@kde.org Component|general |Theme - Breeze Target Milestone|--- |1.0 Product|kscreenlocker |plasmashell Version|git-master |master -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477424] OSDs on lockscreen incorrectly use dark background
https://bugs.kde.org/show_bug.cgi?id=477424 Bharadwaj Raju changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477424] New: OSDs on lockscreen incorrectly use dark background
https://bugs.kde.org/show_bug.cgi?id=477424 Bug ID: 477424 Summary: OSDs on lockscreen incorrectly use dark background Classification: Plasma Product: kscreenlocker Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bharadwaj.raju...@protonmail.com Target Milestone: --- Created attachment 163398 --> https://bugs.kde.org/attachment.cgi?id=163398=edit Screenshot of the OSD SUMMARY OSDs on lockscreen use dark background and dark text, making them unreadable. Desktop theme is Breeze Light. STEPS TO REPRODUCE 1. Set theme to Breeze Light 2. Lock screen 3. Trigger an OSD notification somehow (eg changing the volume) OBSERVED RESULT Dark background and dark text. Screenshot attached. EXPECTED RESULT Theme-appropriate background. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.5.11-300.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 7.1 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476847] plasmashell crashes in PlasmaQuick::ContainmentView::containment() after waking up laptop from standby
https://bugs.kde.org/show_bug.cgi?id=476847 Bharadwaj Raju changed: What|Removed |Added CC||enric...@hotmail.com --- Comment #6 from Bharadwaj Raju --- *** Bug 477204 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477204] plasmashell crash after waking up from standby
https://bugs.kde.org/show_bug.cgi?id=477204 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bharadwaj.raju777@protonmai ||l.com Status|REPORTED|RESOLVED --- Comment #2 from Bharadwaj Raju --- *** This bug has been marked as a duplicate of bug 476847 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 477291] Discover crashed after opening a .flatpakref file
https://bugs.kde.org/show_bug.cgi?id=477291 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #1 from Bharadwaj Raju --- Can you share the .flatpakref file which caused this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477357] Choppy scrolling in Plasma Search KCM
https://bugs.kde.org/show_bug.cgi?id=477357 --- Comment #1 from Bharadwaj Raju --- `reuseItems: true` greatly improves the performance after the first scroll. But I want to profile it and find out why it's taking so long in the first place. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477357] Choppy scrolling in Plasma Search KCM
https://bugs.kde.org/show_bug.cgi?id=477357 Bharadwaj Raju changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477185] META-1, META-2 shortcuts don't work
https://bugs.kde.org/show_bug.cgi?id=477185 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||f86c00156143d1ecc9d97ef1da8 ||3efc40b10dbfd --- Comment #3 from Bharadwaj Raju --- Git commit f86c00156143d1ecc9d97ef1da83efc40b10dbfd by Bharadwaj Raju. Committed on 21/11/2023 at 13:44. Pushed by fusionfuture into branch 'master'. applets/taskmanager: fix model access (task.m -> task.model) Fixes Meta+num shortcuts. Seems to be leftover of some refactor or the other. M +1-1applets/taskmanager/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/f86c00156143d1ecc9d97ef1da83efc40b10dbfd -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476847] plasmashell crashes in PlasmaQuick::ContainmentView::containment() after waking up laptop from standby
https://bugs.kde.org/show_bug.cgi?id=476847 --- Comment #5 from Bharadwaj Raju --- No, I'm on a laptop with no external monitors. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477325] KWin Crash in KWin::OutputInterface::handle() after closing and opening laptop lid
https://bugs.kde.org/show_bug.cgi?id=477325 --- Comment #1 from Bharadwaj Raju --- > In KWin::SurfaceInterface::takePresentationFeedback, neither output nor > d->primaryOutput are nullptrs, yet memory accesses on them are invalid. > Possibly we're deleting them somewhere but not setting them to nullptr? Trying to call d->primaryOutput->isRemoved() also segfaults -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477325] New: KWin Crash in KWin::OutputInterface::handle() after closing and opening laptop lid
https://bugs.kde.org/show_bug.cgi?id=477325
Bug ID: 477325
Summary: KWin Crash in KWin::OutputInterface::handle() after
closing and opening laptop lid
Classification: Plasma
Product: kwin
Version: master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: bharadwaj.raju...@protonmail.com
Target Milestone: ---
BACKTRACE
#0 0x7fd52e41bd7c in QWeakPointer::internalData() const
(this=0xc9) at /usr/include/qt6/QtCore/qsharedpointer_impl.h:704
#1 0x7fd52e6a1cdc in QPointer::data() const (this=0xc9) at
/usr/include/qt6/QtCore/qpointer.h:64
#2 0x7fd52e6a14f4 in QPointer::operator KWin::Output*()
const (this=0xc9) at /usr/include/qt6/QtCore/qpointer.h:72
#3 0x7fd52ea4b3b4 in KWin::OutputInterface::handle() const
(this=0x37249f0) at /home/bharadwaj/kde/src/kwin/src/wayland/output.cpp:265
#4 0x7fd52eac8d12 in
KWin::SurfaceInterface::takePresentationFeedback(KWin::Output*)
(this=0x40b8b10, output=0x263db00)
at /home/bharadwaj/kde/src/kwin/src/wayland/surface.cpp:474
#5 0x7fd52e6da384 in operator()(KWin::SurfaceInterface*) const
(__closure=0x29b4ed0, surface=0x40b8b10)
at /home/bharadwaj/kde/src/kwin/src/scene/workspacescene.cpp:206
#6 0x7fd52e6dcd60 in std::__invoke_impl&,
KWin::SurfaceInterface*>(std::__invoke_other, struct {...} &) (__f=...) at
/usr/include/c++/13/bits/invoke.h:61
#7 0x7fd52e6dc8db in std::__invoke_r&,
KWin::SurfaceInterface*>(struct {...} &) (__fn=...) at
/usr/include/c++/13/bits/invoke.h:111
#8 0x7fd52e6dc5c3 in std::_Function_handler >::_M_invoke(const
std::_Any_data &, KWin::SurfaceInterface *&&) (__functor=...,
__args#0=@0x7ffd763b51f0: 0x40b8b10)
at /usr/include/c++/13/bits/std_function.h:290
#9 0x7fd52ead2f93 in std::function::operator()(KWin::SurfaceInterface*) const
(this=0x7ffd763b5330, __args#0=0x40b8b10)
at /usr/include/c++/13/bits/std_function.h:591
#10 0x7fd52eacd707 in
KWin::SurfaceInterface::traverseTree(std::function) (this=0x40b8b10, callback=...)
at /home/bharadwaj/kde/src/kwin/src/wayland/surface.cpp:1244
#11 0x7fd52e6da613 in KWin::WorkspaceScene::frame(KWin::SceneDelegate*,
KWin::OutputFrame*) (this=0x257f930, delegate=0x42b4110, frame=0x3db89c0)
at /home/bharadwaj/kde/src/kwin/src/scene/workspacescene.cpp:204
#12 0x7fd52e6c0e6b in KWin::SceneDelegate::frame(KWin::OutputFrame*)
(this=0x42b4110, frame=0x3db89c0) at
/home/bharadwaj/kde/src/kwin/src/scene/scene.cpp:49
#13 0x7fd52e3cd064 in KWin::Compositor::framePass(KWin::RenderLayer*,
KWin::OutputFrame*) (this=0x251d0a0, layer=0x263e380, frame=0x3db89c0)
at /home/bharadwaj/kde/src/kwin/src/compositor.cpp:215
#14 0x7fd52e3ccf19 in KWin::Compositor::composite(KWin::RenderLoop*)
(this=0x251d0a0, renderLoop=0x25ea010) at
/home/bharadwaj/kde/src/kwin/src/compositor.cpp:197
#15 0x7fd52e3cc7fe in
KWin::Compositor::handleFrameRequested(KWin::RenderLoop*) (this=0x251d0a0,
renderLoop=0x25ea010)
at /home/bharadwaj/kde/src/kwin/src/compositor.cpp:129
#16 0x7fd52e3d4351 in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(KWin::Compositor::*)(KWin::RenderLoop*)>::call(void
(KWin::Compositor::*)(KWin::RenderLoop*), KWin::Compositor*, void**)
(f=(void (KWin::Compositor::*)(KWin::Compositor * const, KWin::RenderLoop
*)) 0x7fd52e3cc7ce ,
o=0x251d0a0, arg=0x7ffd763b5970) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:145
#17 0x7fd52e3d37b6 in QtPrivate::FunctionPointer::call,
void>(void (KWin::Compositor::*)(KWin::RenderLoop*), KWin::Compositor*, void**)
(f=(void (KWin::Compositor::*)(KWin::Compositor * const, KWin::RenderLoop
*)) 0x7fd52e3cc7ce ,
o=0x251d0a0, arg=0x7ffd763b5970) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:182
--Type for more, q to quit, c to continue without paging--
#18 0x7fd52e3d244f in QtPrivate::QCallableObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(which=1, this_=0x3659bf0, r=0x251d0a0, a=0x7ffd763b5970, ret=0x0) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:520
#19 0x7fd52aa02051 in void doActivate(QObject*, int, void**) () at
/lib64/libQt6Core.so.6
#20 0x7fd52e41efa3 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
(this=0x25ea010, _t1=0x25ea010)
at
/home/bharadwaj/kde/build/kwin/src/kwin_autogen/include/moc_renderloop.cpp:279
#21 0x7fd52e41e56b in KWin::RenderLoopPrivate::dispatch() (this=0x275a1d0)
at /home/bharadwaj/kde/src/kwin/src/core/renderloop.cpp:135
#22 0x7fd52e41df0b in operator()() const (__closure=0x2613a10) at
/home/bharadwaj/kde/src/kwin/src/core/renderloop.cpp:34
#23 0x7fd52e41f284 in QtPrivate::FunctorCall,
QtPrivate::List<>, void,
KWin::RenderLoopPrivate::RenderLoopPrivate(KWin::RenderLoop*)::
>::call(struct {...} &, void **) (f=..., arg=0x7ffd763b5b70) at
[plasmashell] [Bug 476847] plasmashell crashes in PlasmaQuick::ContainmentView::containment() after waking up laptop from standby
https://bugs.kde.org/show_bug.cgi?id=476847 --- Comment #2 from Bharadwaj Raju --- We're trying to access a ContainmentView pointer after/while(?) its destructor is being run: (gdb) frame 21 #21 0x77eff308 in PlasmaQuick::ContainmentView::containment (this=0x141eec0) at /home/bharadwaj/kde/src/plasma-framework/src/plasmaquick/containmentview.cpp:239 239 return d->containment; (gdb) print this $12 = (const PlasmaQuick::ContainmentView * const) 0x141eec0 (gdb) print d warning: RTTI symbol not found for class 'QWindow' $13 = (PlasmaQuick::ContainmentViewPrivate * const) 0x1442360 (gdb) frame 32 #32 0x77eff084 in PlasmaQuick::ContainmentView::~ContainmentView (this=0x141eec0, __in_chrg=) at /home/bharadwaj/kde/src/plasma-framework/src/plasmaquick/containmentview.cpp:205 205 } (gdb) print this $14 = (PlasmaQuick::ContainmentView * const) 0x141eec0 (gdb) print d warning: RTTI symbol not found for class 'QWindow' $15 = (PlasmaQuick::ContainmentViewPrivate * const) 0x1442360 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476847] plasmashell crashes in PlasmaQuick::ContainmentView::containment() after waking up laptop from standby
https://bugs.kde.org/show_bug.cgi?id=476847 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477094] links in kde connect kcm don't use link color from color scheme
https://bugs.kde.org/show_bug.cgi?id=477094 Bharadwaj Raju changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/b174e571625a297febb2c91c6d ||09d1e510bb63c0 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Bharadwaj Raju --- Git commit b174e571625a297febb2c91c6d09d1e510bb63c0 by Bharadwaj Raju. Committed on 19/11/2023 at 13:04. Pushed by albertvaka into branch 'master'. kcm: Don't hardcode link color M +1-1kcm/kcm.ui https://invent.kde.org/network/kdeconnect-kde/-/commit/b174e571625a297febb2c91c6d09d1e510bb63c0 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 233053] Application notifications appear in a wrong place when systray integration is disabled
https://bugs.kde.org/show_bug.cgi?id=233053 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477145] Consider making "Dodge windows" only disappear when touched by the active window, not any window
https://bugs.kde.org/show_bug.cgi?id=477145 --- Comment #3 from Bharadwaj Raju --- In fact we could probably do this without even the small overhead of another model, if we just add a property which filters (on QML side, not a filter on the model) the result of the existing TasksModel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477145] Consider making "Dodge windows" only disappear when touched by the active window, not any window
https://bugs.kde.org/show_bug.cgi?id=477145 --- Comment #2 from Bharadwaj Raju --- It's probably a good idea. I think most people actually have one window or another maximized (or tiled such that it would touch the panel) all the time when actually working. So in practice this renders Dodge Windows to be equivalent to plain Autohide, except on the desktop. Which isn't much of a feature. Having another TaskManager model to filter only based on active window for Dodge Windows is IMO fine. It won't disturb or add complexity to the rest of the QML code handling panel states. We'd just need to change what signal we listen for on the C++ side. Only downside I can think of is that if you switch back-and-forth between a touching window and a non-touching one frequently, the panel popping up might be distracting? But I don't think this is a big issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477133] OSD for Volume and KB Layout change doesn't always show Wayland
https://bugs.kde.org/show_bug.cgi?id=477133 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #1 from Bharadwaj Raju --- Run `journalctl -f` and try to change volume/layout, is there any output which happens there? Does it also happen in X11, or is this Wayland-specific? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 --- Comment #40 from Bharadwaj Raju --- Git commit 7ce3f197be30c445ee9d9a4c298439b1995d5aa5 by Bharadwaj Raju. Committed on 16/11/2023 at 19:53. Pushed by bharadwaj-raju into branch 'master'. Implement UI to enable "Dodge Windows" mode for the panel Depends on https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3508. This adds the configuration UI and tweaks the limit for deciding whether a window is touching to be 12px instead of 6px. After testing various values for it, I found 12px is the smallest that prevents glitches with window snapping.  M +36 -13 desktoppackage/contents/configuration/PanelConfiguration.qml M +20 -4desktoppackage/contents/views/Panel.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/7ce3f197be30c445ee9d9a4c298439b1995d5aa5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Bharadwaj Raju changed: What|Removed |Added Version Fixed In||6.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/105c2c15a5c619e9d963373b3 ||38f25cfcc5e4150 Status|ASSIGNED|RESOLVED --- Comment #39 from Bharadwaj Raju --- Git commit 105c2c15a5c619e9d963373b338f25cfcc5e4150 by Bharadwaj Raju. Committed on 16/11/2023 at 19:53. Pushed by bharadwaj-raju into branch 'master'. Add "Dodge Windows" visibility mode for the panel Adds a new mode called "Dodge Windows" in which the panel is usually visible but hides itself when a window would touch it. FIXED-IN: 6.0 M +23 -6shell/panelview.cpp M +3-0shell/panelview.h M +5-0shell/scripting/panel.cpp M +4-1shell/shellcorona.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/105c2c15a5c619e9d963373b338f25cfcc5e4150 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476567] Moving the mouse within the screen lock grace period breaks the locker in some cases
https://bugs.kde.org/show_bug.cgi?id=476567 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #3 from Bharadwaj Raju --- Interestingly, when this happened just now I noticed that there is no kscreenlocker_greet process running, but the session is still locked (hence loginctl unlock-session being required). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 387797] Scrollviews automatically scroll up or down when you hover over a partially-visible list item
https://bugs.kde.org/show_bug.cgi?id=387797 --- Comment #36 from Bharadwaj Raju --- Git commit 31a547cc420c0778140fad7ed2b0adb2ff46a97f by Bharadwaj Raju. Committed on 13/11/2023 at 20:41. Pushed by bharadwaj-raju into branch 'master'. applets/clipboard: Don't scroll when hovering on partially-visible list item M +6-1applets/clipboard/contents/ui/Menu.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/31a547cc420c0778140fad7ed2b0adb2ff46a97f -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 387797] Scrollviews automatically scroll up or down when you hover over a partially-visible list item
https://bugs.kde.org/show_bug.cgi?id=387797 --- Comment #35 from Bharadwaj Raju --- Git commit b8705faa7b32e94920bb57faa871814b8a7faa56 by Bharadwaj Raju. Committed on 13/11/2023 at 20:24. Pushed by bharadwaj-raju into branch 'master'. ExpandableListItem: Don't change currentIndex if item is partially visible M +9-1 src/declarativeimports/plasmaextracomponents/qml/ExpandableListItem.qml https://invent.kde.org/plasma/plasma-framework/-/commit/b8705faa7b32e94920bb57faa871814b8a7faa56 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476806] Discover crashes in QList on neon unstable
https://bugs.kde.org/show_bug.cgi?id=476806 --- Comment #4 from Bharadwaj Raju --- Did Discover get updated while the symbols were being installed, possibly? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476806] Discover crashes in QList on neon unstable
https://bugs.kde.org/show_bug.cgi?id=476806 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #2 from Bharadwaj Raju --- Can you install debugging symbols and try again? I believe the relevant package on KDE Neon is "plasma-discover-dbgsym". See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476743] Slowly dragging a window near the panel to let it defloat causes the window to jump up and down while dragging (bumpy effect).
https://bugs.kde.org/show_bug.cgi?id=476743 --- Comment #2 from Bharadwaj Raju --- In the Dodge Windows plasma-desktop MR (https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1813), I changed the unfloat/hide threshold to 12px instead of the earlier 6px. This causes the window to unfloat/hide just before snapping behavior would kick in, and it works out smoothly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476711] Following Panel settings redesign, Opaque and Adaptive transparency modes aren't working
https://bugs.kde.org/show_bug.cgi?id=476711 Bharadwaj Raju changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||ac6ac69bf93945c834bda94a95e ||4439b939bb43c Resolution|--- |FIXED --- Comment #2 from Bharadwaj Raju --- Git commit ac6ac69bf93945c834bda94a95e4439b939bb43c by Bharadwaj Raju. Committed on 08/11/2023 at 20:47. Pushed by ngraham into branch 'master'. Fix panel Opaque & Adaptive modes outside X11 KX11Extras::compositingActive returns false outside X11, and thus on Wayland panelOpacity always gets set to zero even though we have compositing. M +1-1desktoppackage/contents/views/Panel.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/ac6ac69bf93945c834bda94a95e4439b939bb43c -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 476433] Plasma gives two notifications when WiFi router goes down, there should be just one
https://bugs.kde.org/show_bug.cgi?id=476433 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-nm/-/commit/19d60 ||985b1e58ece35091b4c21c75bac ||becf3a39 --- Comment #2 from Bharadwaj Raju --- Git commit 19d60985b1e58ece35091b4c21c75bacbecf3a39 by Bharadwaj Raju. Committed on 08/11/2023 at 16:01. Pushed by bharadwaj-raju into branch 'master'. Don't show the SsidNotFound notification As far as I know this notification only comes up simultaneously with the "Connection deactivated" notification, so when the WiFi network goes down we end up showing two notifications for what is really one event, which doesn't look good.  M +1-2kded/notification.cpp https://invent.kde.org/plasma/plasma-nm/-/commit/19d60985b1e58ece35091b4c21c75bacbecf3a39 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476668] Black text on dark background is barely readable
https://bugs.kde.org/show_bug.cgi?id=476668 --- Comment #5 from Bharadwaj Raju --- Thanks. Is this standard Breeze? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476671] Plasmashell crashes when trying to set or look for location in Weather widget
https://bugs.kde.org/show_bug.cgi?id=476671 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #1 from Bharadwaj Raju --- Can't reproduce. According to the stack trace, the code in the weather widget is doing nothing more than a simple KIO::get to a URL. The cause is probably in KIO code. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476533] [kdesrc-build Plasma 6] Pressing Esc no longer turns off the screen when locked
https://bugs.kde.org/show_bug.cgi?id=476533 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #2 from Bharadwaj Raju --- If I just add an unconditional `dpms->switchMode(KScreen::Dpms::Off);` before the connect call, it seems to work. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476668] Black text on dark background is barely readable
https://bugs.kde.org/show_bug.cgi?id=476668 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #1 from Bharadwaj Raju --- Can you add a screenshot? I tested with Breeze, Breeze Dark, and Breeze Twilight, and a very dark background. All the text for me is white. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 476433] Plasma gives two notifications when WiFi router goes down, there should be just one
https://bugs.kde.org/show_bug.cgi?id=476433 Bharadwaj Raju changed: What|Removed |Added Summary|Plasma gives two|Plasma gives two |notifications WiFi when |notifications when WiFi |router goes down, there |router goes down, there |should be just one |should be just one -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 476433] New: Plasma gives two notifications WiFi when router goes down, there should be just one
https://bugs.kde.org/show_bug.cgi?id=476433 Bug ID: 476433 Summary: Plasma gives two notifications WiFi when router goes down, there should be just one Classification: Plasma Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: bharadwaj.raju...@protonmail.com Target Milestone: --- Created attachment 162800 --> https://bugs.kde.org/attachment.cgi?id=162800=edit Screenshot of the notifications SUMMARY When your WiFi router goes down / out of range / whatever, you get two notifications from Plasma about it. STEPS TO REPRODUCE 1. Be connected to WiFi 2. Turn off your router 3. Wait OBSERVED RESULT Two notifications: one about "connection deactivated" and one "the WiFi network could not be found". EXPECTED RESULT Only one notification. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 475575] Underscores display as spaces in the window title bar
https://bugs.kde.org/show_bug.cgi?id=475575 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #7 from Bharadwaj Raju --- What font (and font size) are you using? Are you using any scaling? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471153] Night Color KCM resets "switching times" to "Always Off" on open
https://bugs.kde.org/show_bug.cgi?id=471153 --- Comment #4 from Bharadwaj Raju --- I have a hack solution for this, but I don't feel good about ignoring such a perplexing underlying problem. Do you think it's worth making an MR for the hack? -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 471490] Website mentioned in templete was modified maliciously
https://bugs.kde.org/show_bug.cgi?id=471490 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |FIXED CC||bharadwaj.raju777@protonmai ||l.com Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471153] Night Color KCM resets "switching times" to "Always Off" on open
https://bugs.kde.org/show_bug.cgi?id=471153 --- Comment #3 from Bharadwaj Raju --- For some reason, this problem doesn't appear in kcmshell6. Only in systemsettings. When running under systemsettings, the onActiveChanged connection on kcm.nightColorSettings never gets called, while it does happen under kcmshell6. I have no idea why (yet). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471153] Night Color KCM resets "switching times" to "Always Off" on open
https://bugs.kde.org/show_bug.cgi?id=471153 --- Comment #2 from Bharadwaj Raju --- Looks like the currentIndexChanged() on the combobox gets called too early -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466781] Systemsettings crashes when switching KCMs
https://bugs.kde.org/show_bug.cgi?id=466781 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 470546] xdg-desktop-portal-kde starts too early, causing dbus reads to return incorrect values
https://bugs.kde.org/show_bug.cgi?id=470546 --- Comment #2 from Bharadwaj Raju --- > - Neither of my two tested VMs have this issue, including: > - EndeavourOS KDE Is the VM fully updated to the same release as your laptops? If yes, then there might be something in the configuration of your machines that is causing early startup. If not, then what happens if you do update it, without changing anything else? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 470546] xdg-desktop-portal-kde starts too early, causing dbus reads to return incorrect values
https://bugs.kde.org/show_bug.cgi?id=470546 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470058] Taskbar and mouse cursor sometimes freeze for 1-3 seconds when moving cursor down to the taskbar
https://bugs.kde.org/show_bug.cgi?id=470058 --- Comment #1 from Bharadwaj Raju --- Anywhere on the panel or only when entering the task manager area? If it's the latter then possible duplicate of https://bugs.kde.org/show_bug.cgi?id=450248 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463272] Wrong vertical position of task manager tooltips possibly causing misclicks with media controls
https://bugs.kde.org/show_bug.cgi?id=463272 Bharadwaj Raju changed: What|Removed |Added Version Fixed In||5.27.6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463272] Wrong vertical position of task manager tooltips possibly causing misclicks with media controls
https://bugs.kde.org/show_bug.cgi?id=463272 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/539b6bb6ac3a |ma/kwin/commit/4d4769b8c5b3 |58049b96106de55004806c63982 |ddd5b3bfae6dc7fb4cf7057127a |1 |6 --- Comment #14 from Bharadwaj Raju --- Git commit 4d4769b8c5b3ddd5b3bfae6dc7fb4cf7057127a6 by Bharadwaj Raju. Committed on 23/05/2023 at 13:43. Pushed by bharadwaj-raju into branch 'Plasma/5.27'. XdgPopupWindow: Allow position to be set by Plasma This lets Plasma itself control the position of popup windows such as Plasma tooltips. transientPlacement() now returns the position set by Plasma if available. (cherry picked from commit 539b6bb6ac3a58049b96106de55004806c639821) M +4-1src/xdgshellwindow.cpp https://invent.kde.org/plasma/kwin/commit/4d4769b8c5b3ddd5b3bfae6dc7fb4cf7057127a6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463272] Wrong vertical position of task manager tooltips possibly causing misclicks with media controls
https://bugs.kde.org/show_bug.cgi?id=463272 Bharadwaj Raju changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/539b6bb6ac3a ||58049b96106de55004806c63982 ||1 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #13 from Bharadwaj Raju --- Git commit 539b6bb6ac3a58049b96106de55004806c639821 by Bharadwaj Raju. Committed on 23/05/2023 at 13:41. Pushed by bharadwaj-raju into branch 'master'. XdgPopupWindow: Allow position to be set by Plasma This lets Plasma itself control the position of popup windows such as Plasma tooltips. transientPlacement() now returns the position set by Plasma if available. M +4-1src/xdgshellwindow.cpp https://invent.kde.org/plasma/kwin/commit/539b6bb6ac3a58049b96106de55004806c639821 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463272] Wrong vertical position of task manager tooltips possibly causing misclicks with media controls
https://bugs.kde.org/show_bug.cgi?id=463272 Bharadwaj Raju changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #12 from Bharadwaj Raju --- MR with fix: https://invent.kde.org/plasma/kwin/-/merge_requests/4127 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463272] Wrong vertical position of task manager tooltips possibly causing misclicks with media controls
https://bugs.kde.org/show_bug.cgi?id=463272 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com --- Comment #9 from Bharadwaj Raju --- Correction (to comment 5 on https://bugs.kde.org/show_bug.cgi?id=468352#c5): The tooltip doesn't in fact open at the same y-position as before. It opens exactly 30 pixels upward/downward of it, in the "correct" direction (i.e. it should actually be more than 30 pixels from it but in the same direction). Here are some logs from adding some prints to dialog.cpp in PF: --- opening small tooltip >>> syncToMainItemSize called >>> setVisible: position is: QPoint(0,840) >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 840 >>> updateVisibility: position is: QPoint(0,840) >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 840 >>> updateVisibility: position is: QPoint(0,840) it opened with correct position now going to open tall tooltip >>> syncToMainItemSize called >>> setVisible: position is: QPoint(0,810) >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 810 >>> updateVisibility: position is: QPoint(0,810) >>> repositionIfOffScreen: setting (x, y) = 0 , 776 >>> repositionIfOffScreen: setting (x, y) = 0 , 776 >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 776 >>> updateVisibility: position is: QPoint(0,776) it opened with wrong position - now reopening tall >>> syncToMainItemSize called >>> setVisible: position is: QPoint(0,776) >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 776 >>> updateVisibility: position is: QPoint(0,776) >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 776 >>> updateVisibility: position is: QPoint(0,776) correct position - now opening small >>> syncToMainItemSize called >>> setVisible: position is: QPoint(0,776) >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 806 >>> updateVisibility: position is: QPoint(0,806) >>> repositionIfOffScreen: setting (x, y) = 0 , 840 >>> repositionIfOffScreen: setting (x, y) = 0 , 840 >>> syncToMainItemSize called >>> repositionIfOffScreen: setting (x, y) = 0 , 840 >>> updateVisibility: position is: QPoint(0,840) wrong position -- Turns out (from pixel-measuring screenshots) the wrong position for the tall one is 810, exactly 30 pixels upwards from the correct position of the small tooltip which is 840. Similarly, the wrong position for the small tooltip is 806, exactly 30 pixels downwards from the correct position of the tall tooltip which is 776. I'm not sure what is making this 30 pixel thing happen. Also note how it first says "updateVisibility: position is: " then soon after we get a similar line with the correct position, but even after that has been printed the tooltip only actually shows up at the first, wrong position. It's like the second time its position change isn't having an effect...? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 467369] When creating a link to an application from the desktop context menu, selecting the program path from the browse dialogue doesn't work with spaces
https://bugs.kde.org/show_bug.cgi?id=467369 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram |eworks/kio/commit/374812569 |eworks/kio/commit/bf3c43369 |67b1f0f24e6da8530eacb8bbec7 |b5626740339a62733715ec27104 |58bf|db7e --- Comment #5 from Bharadwaj Raju --- Git commit bf3c43369b5626740339a62733715ec27104db7e by Bharadwaj Raju. Committed on 25/04/2023 at 18:12. Pushed by bharadwaj-raju into branch 'kf5'. KPropertiesDialog: Don't quote the path unnecessarily We don't need to KShell::quoteArg the executable path, since we use KShell::joinArgs later which takes care of proper quoting. cc @davidedmundson (cherry picked from commit 37481256967b1f0f24e6da8530eacb8bbec758bf) M +1-2src/widgets/kpropertiesdialog.cpp https://invent.kde.org/frameworks/kio/commit/bf3c43369b5626740339a62733715ec27104db7e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 467369] When creating a link to an application from the desktop context menu, selecting the program path from the browse dialogue doesn't work with spaces
https://bugs.kde.org/show_bug.cgi?id=467369 Bharadwaj Raju changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kio/commit/374812569 ||67b1f0f24e6da8530eacb8bbec7 ||58bf Resolution|--- |FIXED --- Comment #4 from Bharadwaj Raju --- Git commit 37481256967b1f0f24e6da8530eacb8bbec758bf by Bharadwaj Raju. Committed on 25/04/2023 at 18:11. Pushed by bharadwaj-raju into branch 'master'. KPropertiesDialog: Don't quote the path unnecessarily We don't need to KShell::quoteArg the executable path, since we use KShell::joinArgs later which takes care of proper quoting. cc @davidedmundson M +1-2src/widgets/kpropertiesdialog.cpp https://invent.kde.org/frameworks/kio/commit/37481256967b1f0f24e6da8530eacb8bbec758bf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468352] In a default panel located on the bottom, small window previews with media player controls are often mis-positioned, either overlapping their task item or not touching it
https://bugs.kde.org/show_bug.cgi?id=468352 Bharadwaj Raju changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Bharadwaj Raju --- I have seen this too. I noticed that if you open a tooltip with media controls, let it close, then open a tooltip without that, it opens "floating above", at the same y-position as the first tooltip. If you let that tooltip close and open it again, it opens normally. Now if you let that close and go to a tooltip with media controls, it opens overlapping the task below, again at the same y-position as the first. So clearly the y-position is getting reused across instances when it should not be. Exactly where it is happening I'm not yet sure. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435671] Zoom icons do not use magnifying glass iconography
https://bugs.kde.org/show_bug.cgi?id=435671 Bharadwaj Raju changed: What|Removed |Added CC|bharadwaj.raju777@protonmai | |l.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 Bharadwaj Raju changed: What|Removed |Added CC|bharadwaj.raju777@protonmai | |l.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #7 from Bharadwaj Raju --- Aleksey's problem appears to be unrelated to the triangle mouse filter, and is instead due to some inefficiency in the screencasting. Did this happen before 5.27 as well? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466681] Mouse is lagging/skipping frames when entering Task Manager area
https://bugs.kde.org/show_bug.cgi?id=466681 --- Comment #2 from Bharadwaj Raju --- Probably the filter, yes. Not entirely sure about the cause, but maybe the logic we use for the secondary point is too slow? Will need profiling. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/commit/7f |7f1233a4ad50d70af9cbc39ff95 |1233a4ad50d70af9cbc39ff957a |7a7cb1c47ed9b |7cb1c47ed9b --- Comment #52 from Bharadwaj Raju --- Git commit 7f1233a4ad50d70af9cbc39ff957a7cb1c47ed9b by Bharadwaj Raju. Committed on 08/02/2023 at 17:55. Pushed by bharadwaj-raju into branch 'master'. applets/taskmanager: Triangle mouse filtering, with the component this time Use the triangle mouse filter component from Plasma Workspace. Related: bug 347041 M +3-0applets/taskmanager/package/contents/ui/Task.qml M +81 -36 applets/taskmanager/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/7f1233a4ad50d70af9cbc39ff957a7cb1c47ed9b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347041] Tooltip interaction in multi-row Task Manager suffers from not being able to reach tooltip for lower rows of delegates
https://bugs.kde.org/show_bug.cgi?id=347041 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/6b |ma/plasma-desktop/commit/7f |0dd6514faad6d0803dc0d58ed93 |1233a4ad50d70af9cbc39ff957a |d995b82c237 |7cb1c47ed9b --- Comment #15 from Bharadwaj Raju --- Git commit 7f1233a4ad50d70af9cbc39ff957a7cb1c47ed9b by Bharadwaj Raju. Committed on 08/02/2023 at 17:55. Pushed by bharadwaj-raju into branch 'master'. applets/taskmanager: Triangle mouse filtering, with the component this time Use the triangle mouse filter component from Plasma Workspace. Related: bug 358930 M +3-0applets/taskmanager/package/contents/ui/Task.qml M +81 -36 applets/taskmanager/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/7f1233a4ad50d70af9cbc39ff957a7cb1c47ed9b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347041] Tooltip interaction in multi-row Task Manager suffers from not being able to reach tooltip for lower rows of delegates
https://bugs.kde.org/show_bug.cgi?id=347041 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/commit/6b |7f1233a4ad50d70af9cbc39ff95 |0dd6514faad6d0803dc0d58ed93 |7a7cb1c47ed9b |d995b82c237 --- Comment #14 from Bharadwaj Raju --- Git commit 6b0dd6514faad6d0803dc0d58ed93d995b82c237 by Bharadwaj Raju. Committed on 08/02/2023 at 17:57. Pushed by bharadwaj-raju into branch 'Plasma/5.27'. applets/taskmanager: Triangle mouse filtering, with the component this time Use the triangle mouse filter component from Plasma Workspace. Related: bug 358930 (cherry picked from commit 7f1233a4ad50d70af9cbc39ff957a7cb1c47ed9b) M +3-0applets/taskmanager/package/contents/ui/Task.qml M +81 -36 applets/taskmanager/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/6b0dd6514faad6d0803dc0d58ed93d995b82c237 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/7f |ma/plasma-desktop/commit/6b |1233a4ad50d70af9cbc39ff957a |0dd6514faad6d0803dc0d58ed93 |7cb1c47ed9b |d995b82c237 --- Comment #53 from Bharadwaj Raju --- Git commit 6b0dd6514faad6d0803dc0d58ed93d995b82c237 by Bharadwaj Raju. Committed on 08/02/2023 at 17:57. Pushed by bharadwaj-raju into branch 'Plasma/5.27'. applets/taskmanager: Triangle mouse filtering, with the component this time Use the triangle mouse filter component from Plasma Workspace. Related: bug 347041 (cherry picked from commit 7f1233a4ad50d70af9cbc39ff957a7cb1c47ed9b) M +3-0applets/taskmanager/package/contents/ui/Task.qml M +81 -36 applets/taskmanager/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/6b0dd6514faad6d0803dc0d58ed93d995b82c237 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465595] 5.27: task manager hover is sluggish
https://bugs.kde.org/show_bug.cgi?id=465595 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/06 |ma/plasma-desktop/commit/d1 |a9799ab1321ea193cad77735a80 |c24264b8abe353d38af6ea68d33 |372e3da8d71 |daa857d79d4 --- Comment #10 from Bharadwaj Raju --- Git commit d1c24264b8abe353d38af6ea68d33daa857d79d4 by Bharadwaj Raju. Committed on 12/02/2023 at 17:25. Pushed by bharadwaj-raju into branch 'Plasma/5.27'. applets/taskmanager: Only activate the triangle filter when a tooltip is open (cherry picked from commit 06a9799ab1321ea193cad77735a80372e3da8d71) M +2-0applets/taskmanager/package/contents/ui/Task.qml M +1-1applets/taskmanager/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/d1c24264b8abe353d38af6ea68d33daa857d79d4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465595] 5.27: task manager hover is sluggish
https://bugs.kde.org/show_bug.cgi?id=465595 Bharadwaj Raju changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/commit/06 |d1c24264b8abe353d38af6ea68d |a9799ab1321ea193cad77735a80 |33daa857d79d4 |372e3da8d71 --- Comment #9 from Bharadwaj Raju --- Git commit 06a9799ab1321ea193cad77735a80372e3da8d71 by Bharadwaj Raju. Committed on 12/02/2023 at 17:23. Pushed by bharadwaj-raju into branch 'master'. applets/taskmanager: Only activate the triangle filter when a tooltip is open M +2-0applets/taskmanager/package/contents/ui/Task.qml M +1-1applets/taskmanager/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/commit/06a9799ab1321ea193cad77735a80372e3da8d71 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465595] 5.27: task manager hover is sluggish
https://bugs.kde.org/show_bug.cgi?id=465595 Bharadwaj Raju changed: What|Removed |Added Version Fixed In||5.27.0 Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||d1c24264b8abe353d38af6ea68d ||33daa857d79d4 --- Comment #7 from Bharadwaj Raju --- The fix is going to be in 5.27.0 itself. Thank you for testing it before release! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465595] 5.27: task manager hover is sluggish
https://bugs.kde.org/show_bug.cgi?id=465595 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465595] 5.27: task manager hover is sluggish
https://bugs.kde.org/show_bug.cgi?id=465595 --- Comment #4 from Bharadwaj Raju --- It is, and really I should've done it from the start. I'll make an MR to do that now. I'm not sure if we can get it into 5.27.0, but the fix should be in 5.27.1 for sure. If that is fixed then is that sufficient for you to consider the whole bug fixed? Because if a tooltip is open then the delay feels reasonable to me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465595] 5.27: task manager hover is sluggish
https://bugs.kde.org/show_bug.cgi?id=465595 --- Comment #2 from Bharadwaj Raju --- On second thought it may not be as straightforward, since we use a secondary point to get greater filtering reliability that Kickoff doesn't use. Might have to try and detect the slope of movement? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465595] 5.27: task manager hover is sluggish
https://bugs.kde.org/show_bug.cgi?id=465595 --- Comment #1 from Bharadwaj Raju --- Consequence of the fix to https://bugs.kde.org/show_bug.cgi?id=358930 and https://bugs.kde.org/show_bug.cgi?id=347041. Since the same technique and component is used in Kickoff without impeding fast horizontal switching, I think we can probably fix this without re-breaking those bugs. Will look into it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 347041] Tooltip interaction in multi-row Task Manager suffers from not being able to reach tooltip for lower rows of delegates
https://bugs.kde.org/show_bug.cgi?id=347041 Bharadwaj Raju changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||6b0dd6514faad6d0803dc0d58ed ||93d995b82c237 Status|ASSIGNED|RESOLVED Version Fixed In||5.27.1 --- Comment #12 from Bharadwaj Raju --- Fixed in master and 5.27 branch. I expect the fix will be there in the 5.27.1 release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 Bharadwaj Raju changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||6b0dd6514faad6d0803dc0d58ed ||93d995b82c237 Resolution|--- |FIXED Version Fixed In||5.27.1 --- Comment #50 from Bharadwaj Raju --- Fixed in master and 5.27 branch. I expect the fix will be there in the 5.27.1 release. -- You are receiving this mail because: You are watching all bug changes.
