[okular] [Bug 489663] New: Mouse cursor doesn't change after context menu hides
https://bugs.kde.org/show_bug.cgi?id=489663 Bug ID: 489663 Summary: Mouse cursor doesn't change after context menu hides Classification: Applications Product: okular Version: 24.05.1 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: publicantro...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Open a document 2. Press secondary mouse button to open context menu 3. Do not move the cursor to the context menu area 4. Click Esc or on the document area OBSERVED RESULT Arrow cursor EXPECTED RESULT Hand cursor SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-41-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics Memory: 14.8 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20UH001JRT System Version: ThinkPad T14s Gen 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482185] Context menu (when right-clicking on the desktop) appears in a separate window after external monitor restart
https://bugs.kde.org/show_bug.cgi?id=482185 antroids changed: What|Removed |Added CC||publicantro...@gmail.com --- Comment #11 from antroids --- I have the same issue on my laptop after several sleep-wakes or external/internal monitor switches. > Operating System: KDE neon 6.0 > KDE Plasma Version: 6.0.4 > KDE Frameworks Version: 6.1.0 > Qt Version: 6.7.0 > Kernel Version: 6.5.0-28-generic (64-bit) > Graphics Platform: Wayland > Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics > Memory: 14.8 GiB of RAM > Graphics Processor: AMD Radeon Graphics > Manufacturer: LENOVO > Product Name: 20UH001JRT > System Version: ThinkPad T14s Gen 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483683] New: TasksModel.activeTask is invalid when xdg-desktop-portal is active
https://bugs.kde.org/show_bug.cgi?id=483683 Bug ID: 483683 Summary: TasksModel.activeTask is invalid when xdg-desktop-portal is active Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: publicantro...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 Created attachment 167263 --> https://bugs.kde.org/attachment.cgi?id=167263&action=edit Google Chrome about://gpu STEPS TO REPRODUCE 1. Install Task Manager widget 2. Open Google Chrome browser 3. Right-click, Save as.. OBSERVED RESULT New task blinks in the Task Manager bus disappears and no tasks marked as active anymore EXPECTED RESULT Google Chrome or any new task should be active in the Task Manager SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 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 × AMD Ryzen 5 PRO 4650U with Radeon Graphics Memory: 14.8 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20UH001JRT System Version: ThinkPad T14s Gen 1 ADDITIONAL INFORMATION Works well in Chromium and Firefox. Chrome arguments: %U --use-gl=angle --use-angle=gl --ignore-gpu-blocklist --disable-gpu-driver-bug-workaround --enable-features=VaapiVideoDecodeLinuxGL --enable-features=VaapiVideoEncoder --enable-features=VaapiVideoDecoder --disable-features=UseChromeOSDirectVideoDecoder The same issue with Telegram Desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483683] TasksModel.activeTask is invalid when xdg-desktop-portal is active
https://bugs.kde.org/show_bug.cgi?id=483683 --- Comment #1 from antroids --- Created attachment 167264 --> https://bugs.kde.org/attachment.cgi?id=167264&action=edit Chromium about://gpu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493724] New: TaskManager::TasksModel: use QDateTime instead of QTime for lastActivated
https://bugs.kde.org/show_bug.cgi?id=493724 Bug ID: 493724 Summary: TaskManager::TasksModel: use QDateTime instead of QTime for lastActivated Classification: Plasma Product: plasmashell Version: 6.1.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: publicantro...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY I've created a widget with window controls. It has a mode to show controls for last activated task instead of active, this option works well with multiple displays. The mode based on TasksModel sorted by SortLastActivated. However, if you have some tasks opened yesterday at some time, they will always be above any tasks opened today before this time. Formaly, everything is correct, sorted by timestamp according to the documentation. But the model is not sorted in expected order. STEPS TO REPRODUCE 1. Install "Application Title Bar" widget to a panel. 2. Switch "Active task source" option to "Last active task". 3. Open first task. 4. Wait until the next day. 5. Open second task. OBSERVED RESULT Controls are showed for the first task. EXPECTED RESULT Controls are showed for the second task. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.8.0-40-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20UH001JRT System Version: ThinkPad T14s Gen 1 ADDITIONAL INFORMATION https://invent.kde.org/plasma/plasma-workspace/-/blob/master/libtaskmanager/waylandtasksmodel.cpp#L415 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 497792] New: Inactive window on top after moving to another virtual desktop
https://bugs.kde.org/show_bug.cgi?id=497792 Bug ID: 497792 Summary: Inactive window on top after moving to another virtual desktop Classification: Plasma Product: kwin Version: 6.2.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: publicantro...@gmail.com Target Milestone: --- Created attachment 176825 --> https://bugs.kde.org/attachment.cgi?id=176825&action=edit Screenshots SUMMARY In overview move it's possible to move not active window from one virtual desktop to another. The window will have active state after moving and activating the desktop, but it will not be shown on top. STEPS TO REPRODUCE 1. Create second virtual desktop. 2. Open two applications on the first virtual desktop. 3. Open one application on the second virtual desktop. 4. Enter to the overview mode on the first virtual desktop. 5. Drag first opened application, which is not active on the first virtual desktop, to the second virtual desktop. 6. Exit overview mode and switch to the second virtual desktop. OBSERVED RESULT The first opened application will be active, but the third will be on top. It will be active in task manager and it will handle input. EXPECTED RESULT Top application should be active. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.2 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.1 Kernel Version: 6.8.0-50-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 4650U with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499128] doing a drag/swipe gesture from a widget to outside of the panel works inconsistently on plasma 6.3 beta and master
https://bugs.kde.org/show_bug.cgi?id=499128
antroids changed:
What|Removed |Added
CC||publicantro...@gmail.com
--- Comment #6 from antroids ---
The issue is related to the ButtonRebinds plugin for KWin.
I've noticed that the device section of QEventPoint object is different when
you start dragging at the edge of the panel and at the rest:
Edge:
"device": {
...
"buttonCount": 0,
"capabilities": 1,
"maximumPoints": 1,
"name": "Button rebinding device touchpad",
"objectName": "",
"pointerType": 2,
"seatName": "",
"systemId": -1,
"type": 4,
"uniqueId": {
"numericId": -1
}
},
The rest:
"device": {
...
"buttonCount": 0,
"capabilities": 1,
"maximumPoints": 10,
"name": "touchpad",
"objectName": "",
"pointerType": 2,
"seatName": "seat0",
"systemId": 8589934592,
"type": 4,
"uniqueId": {
"numericId": -1
}
},
When the "buttonsrebind" is unloaded, dragging wirks fine.
> qdbus6 org.kde.KWin /Plugins UnloadPlugin "buttonsrebind"
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 499128] doing a drag/swipe gesture from a widget to outside of the panel works inconsistently on plasma 6.3 beta and master
https://bugs.kde.org/show_bug.cgi?id=499128 --- Comment #7 from antroids --- Is the ButtonsRebind plugin used somewhere? If the manual config editing is required to configure the plugin, then it should not be loaded by default. -- You are receiving this mail because: You are watching all bug changes.
