[Akonadi] [Bug 418727] akonadi_migration_agent "In progress" dialog never goes away
https://bugs.kde.org/show_bug.cgi?id=418727 Henrique Sant'Anna changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418727] akonadi_migration_agent "In progress" dialog never goes away
https://bugs.kde.org/show_bug.cgi?id=418727 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 491220] Ability to pause krfb, showing the client only a blank screen, without disconnecting entirely
https://bugs.kde.org/show_bug.cgi?id=491220 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 489268] krfb sigsegv in libqt in QImage::sizeInBytes()
https://bugs.kde.org/show_bug.cgi?id=489268 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 488981] krfb SEGFAULTs after confirming
https://bugs.kde.org/show_bug.cgi?id=488981 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 451166] Starting krfb from konsole sometimes resulted in a crash of xdg-desktop-portal
https://bugs.kde.org/show_bug.cgi?id=451166 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 489264] krfb still crashes in PipeWireSourceStream::frameReceived::PipeWireFrame() on startup in wayland
https://bugs.kde.org/show_bug.cgi?id=489264 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 492517] krfb crashes in Wayland
https://bugs.kde.org/show_bug.cgi?id=492517 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439664] Dolphin crashes with Insync 3.4.2.40293
https://bugs.kde.org/show_bug.cgi?id=439664 --- Comment #21 from Henrique Sant'Anna --- Dolphin can (or should) handle the plugin error and prevent the entire application from shutting down. The application is closing because its code does not anticipate that plugins can perform actions that result in a fatal error. There are multiple errors that Dolphin itself can cause, but these errors are handled in such a way that they do not result in failure. In short, the application needs to handle not only errors arising from its own native actions, but also generally handle errors that may arise from plugin actions. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 473858] New: Dolphin crashes when right click or context menu key pressed over a file from Insync synced folder
https://bugs.kde.org/show_bug.cgi?id=473858
Bug ID: 473858
Summary: Dolphin crashes when right click or context menu key
pressed over a file from Insync synced folder
Classification: Applications
Product: dolphin
Version: 23.04.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: hsanta...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (23.04.3)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.1.47-1-lts x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Dolphin crashes when right click or press keybord context menu key over a file
inside Insync synced folder
The crash can be reproduced every time.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f0d6acdb614 in QVariant::toString() const () at
/usr/lib/libQt5Core.so.5
#7 0x7f0d1c403275 in
FileItemActionInsyncPlugin::getContextMenuActions(QString const&) () at
/usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#8 0x7f0d1c402fb9 in
FileItemActionInsyncPlugin::actions(KFileItemListProperties const&, QWidget*)
() at /usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#9 0x7f0d6ca8406b in () at /usr/lib/libKF5KIOWidgets.so.5
#10 0x558efa104041 in ()
#11 0x558efa104939 in ()
#12 0x558efa0e98ca in ()
#13 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#14 0x7f0d6cdbe289 in DolphinView::requestContextMenu(QPoint const&,
KFileItem const&, KFileItemList const&, QUrl const&) () at
/usr/lib/libdolphinprivate.so.5
#15 0x7f0d6ce2ea10 in DolphinView::slotItemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#16 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#17 0x7f0d6cdbbb8b in KItemListController::itemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#18 0x7f0d6cdf97b6 in KItemListController::keyPressEvent(QKeyEvent*) () at
/usr/lib/libdolphinprivate.so.5
#19 0x7f0d6cdfd08e in KItemListView::event(QEvent*) () at
/usr/lib/libdolphinprivate.so.5
#20 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#22 0x7f0d6b9aee6d in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#23 0x7f0d6ba5d703 in QFrame::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#24 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#25 0x7f0d6b97d958 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#26 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#27 0x7f0d6b9cec5b in () at /usr/lib/libQt5Widgets.so.5
#28 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#29 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#30 0x7f0d6b145570 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() at /usr/lib/libQt5Gui.so.5
#31 0x7f0d6b12a6c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#32 0x7f0d6815e955 in () at /usr/lib/libQt5WaylandClient.so.5
#33 0x7f0d6890fa31 in g_main_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:3460
#34 g_main_context_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:4200
#35 0x7f0d6896ccc9 in g_main_context_iterate.isra.0
(context=context@entry=0x7f0d6ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#36 0x7f0d6890d0e2 in g_main_context_iteration (context=0x7f0d6ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#37 0x7f0d6aceb51c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#38 0x7f0d6ac9b404 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#39 0x7f0d6ac9c8a3 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#40 0x558efa0deda8 in ()
#41 0x7f0d6a227cd0 in __libc_start_call_main
(main=main@entry=0x558efa0dc520, argc=argc@entry=1,
argv=argv@entry=0x7ffe0a9e3648) at ../sysdeps/nptl/libc_start_call_main.h:58
#42 0x7f0d6a227d8a in __libc_start_main_impl (main=0x558efa0dc520, argc=1,
argv=0x7ffe0a9e3648, init=, fini=,
rtld_fini=, stack_end=0x7ffe0a9e3638) at ../csu/libc-start.c:360
#43 0x558efa0df565 in ()
[Inferior 1 (process 79986) detached]
The reporter in
[dolphin] [Bug 473851] New: Dolphin crashes when right click or context menu key pressed over a file from Insync synced folder
https://bugs.kde.org/show_bug.cgi?id=473851
Bug ID: 473851
Summary: Dolphin crashes when right click or context menu key
pressed over a file from Insync synced folder
Classification: Applications
Product: dolphin
Version: 23.04.3
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: hsanta...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (23.04.3)
Qt Version: 5.15.10
Frameworks Version: 5.109.0
Operating System: Linux 6.1.47-1-lts x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Dolphin crashes when right click or press keybord context menu key over a file
inside Insync synced folder
The crash can be reproduced every time.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f0d6acdb614 in QVariant::toString() const () at
/usr/lib/libQt5Core.so.5
#7 0x7f0d1c403275 in
FileItemActionInsyncPlugin::getContextMenuActions(QString const&) () at
/usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#8 0x7f0d1c402fb9 in
FileItemActionInsyncPlugin::actions(KFileItemListProperties const&, QWidget*)
() at /usr/lib/qt/plugins/fileitemactioninsyncplugin.so
#9 0x7f0d6ca8406b in () at /usr/lib/libKF5KIOWidgets.so.5
#10 0x558efa104041 in ()
#11 0x558efa104939 in ()
#12 0x558efa0e98ca in ()
#13 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#14 0x7f0d6cdbe289 in DolphinView::requestContextMenu(QPoint const&,
KFileItem const&, KFileItemList const&, QUrl const&) () at
/usr/lib/libdolphinprivate.so.5
#15 0x7f0d6ce2ea10 in DolphinView::slotItemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#16 0x7f0d6acd1637 in () at /usr/lib/libQt5Core.so.5
#17 0x7f0d6cdbbb8b in KItemListController::itemContextMenuRequested(int,
QPointF const&) () at /usr/lib/libdolphinprivate.so.5
#18 0x7f0d6cdf97b6 in KItemListController::keyPressEvent(QKeyEvent*) () at
/usr/lib/libdolphinprivate.so.5
#19 0x7f0d6cdfd08e in KItemListView::event(QEvent*) () at
/usr/lib/libdolphinprivate.so.5
#20 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#21 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#22 0x7f0d6b9aee6d in QWidget::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#23 0x7f0d6ba5d703 in QFrame::event(QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#24 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#25 0x7f0d6b97d958 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#26 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#27 0x7f0d6b9cec5b in () at /usr/lib/libQt5Widgets.so.5
#28 0x7f0d6b97893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#29 0x7f0d6ac9c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#30 0x7f0d6b145570 in
QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*)
() at /usr/lib/libQt5Gui.so.5
#31 0x7f0d6b12a6c5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() at /usr/lib/libQt5Gui.so.5
#32 0x7f0d6815e955 in () at /usr/lib/libQt5WaylandClient.so.5
#33 0x7f0d6890fa31 in g_main_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:3460
#34 g_main_context_dispatch (context=0x7f0d6ee0) at
../glib/glib/gmain.c:4200
#35 0x7f0d6896ccc9 in g_main_context_iterate.isra.0
(context=context@entry=0x7f0d6ee0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4276
#36 0x7f0d6890d0e2 in g_main_context_iteration (context=0x7f0d6ee0,
may_block=1) at ../glib/glib/gmain.c:4343
#37 0x7f0d6aceb51c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#38 0x7f0d6ac9b404 in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#39 0x7f0d6ac9c8a3 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#40 0x558efa0deda8 in ()
#41 0x7f0d6a227cd0 in __libc_start_call_main
(main=main@entry=0x558efa0dc520, argc=argc@entry=1,
argv=argv@entry=0x7ffe0a9e3648) at ../sysdeps/nptl/libc_start_call_main.h:58
#42 0x7f0d6a227d8a in __libc_start_main_impl (main=0x558efa0dc520, argc=1,
argv=0x7ffe0a9e3648, init=, fini=,
rtld_fini=, stack_end=0x7ffe0a9e3638) at ../csu/libc-start.c:360
#43 0x558efa0df565 in ()
[Inferior 1 (process 79986) detached]
The reporter in
[kio-extras] [Bug 430210] Font previews do not show up on Wayland
https://bugs.kde.org/show_bug.cgi?id=430210 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%.
https://bugs.kde.org/show_bug.cgi?id=462762 Henrique Sant'Anna changed: What|Removed |Added Depends on||426840 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=426840 [Bug 426840] Panels should automatically enter "Auto-Hide" or "Windows can Cover" mode when full screen content causes them to be covered up -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426840] Panels should automatically enter "Auto-Hide" or "Windows can Cover" mode when full screen content causes them to be covered up
https://bugs.kde.org/show_bug.cgi?id=426840 Henrique Sant'Anna changed: What|Removed |Added Blocks||462762 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=462762 [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%.
https://bugs.kde.org/show_bug.cgi?id=462762 Henrique Sant'Anna changed: What|Removed |Added Depends on||349785 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=349785 [Bug 349785] Intelligent auto-hide mode that hides the panel only when windows are maximized or move over it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Henrique Sant'Anna changed: What|Removed |Added Blocks||462762 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=462762 [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 462762] On Wayland, Yakuake will not cover panels set to "windows can cover" when size is 100%.
https://bugs.kde.org/show_bug.cgi?id=462762 Henrique Sant'Anna changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- I don't think that Yakuake should be in front of any panel if Yakuake is not on full-screen mode (Ctrl + Shift + F11, by default). For me, the expected behavior (when not full-screen) is: The top panel should reaper when Yakuake is shown (currently doesn't happen, leaving a gap), Yakuake window geometry should start right below that panel (already happen). Then, the panel should hide again (if set to auto-hide or "windows can cover) when Yakuake got hidden. This is the behavior when using a Latte dock panel, but is not when using a native plasma panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426840] Panels should automatically enter "Auto-Hide" or "Windows can Cover" mode when full screen content causes them to be covered up
https://bugs.kde.org/show_bug.cgi?id=426840 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 --- Comment #44 from Henrique Sant'Anna --- There is a shortcut key to change focus between panels (just like Alt+Tab for windows), it is Meta+Alt+P. Pressing the shortcut (as many times as panels you need) will make the panel reaper. It is a good workaround to recover a hidden panels without having to minimize all windows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428066] Panel show/hide animation does not work in "Windows Can Cover" mode
https://bugs.kde.org/show_bug.cgi?id=428066 Henrique Sant'Anna changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||hsanta...@gmail.com Ever confirmed|0 |1 --- Comment #2 from Henrique Sant'Anna --- I think that the difference between "auto-hide" and "windows can cover" is the animation that auto-hide shows (and the fact that auto-hide also hides from desktop). This is not a bug, but can be a feature request. Like: To enable the same animation to "windows can cover" panels as in "auto-hide" panels. Personally I would like it configurable, I don't want animations. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 263607] Yakuake as default terminal doesn't open on desired path after SHIFT+F4
https://bugs.kde.org/show_bug.cgi?id=263607 Henrique Sant'Anna changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #10 from Henrique Sant'Anna --- The bug is still reproducible for yakuake 22.08.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 337043] Mouse Mark has no user-definable shortcut, hard-coded one interferes with others
https://bugs.kde.org/show_bug.cgi?id=337043 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444334] Mouse Mark effect draws arrows if ctrl modifier pressed
https://bugs.kde.org/show_bug.cgi?id=444334 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #2 from Henrique Sant'Anna --- It's a feature. Press Ctrl + Shift + Meta, move the mouse pointer, press Ctrl + Shift + Meta again. Only works on Wayland. Probably it would be better to require a mouse down-up do draw the arrow, not only the keyboard short-keys. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454179] Mouse Mark: Make it fully featured like Spectacles' annotation tools
https://bugs.kde.org/show_bug.cgi?id=454179 --- Comment #2 from Henrique Sant'Anna --- (In reply to Henrique Sant'Anna from comment #1) > There is already a rudimentary functionality for drawing arrows, it is a > hidden functionality. (Alt + Shift + Meta, 2x at two different points, only > works somewhat good on Wayland). Actually the secret shortcut key to do arrows is another: Ctrl + Shift + Meta -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454179] Mouse Mark: Make it fully featured like Spectacles' annotation tools
https://bugs.kde.org/show_bug.cgi?id=454179 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- There is already a rudimentary functionality for drawing arrows, it is a hidden functionality. (Alt + Shift + Meta, 2x at two different points, only works somewhat good on Wayland). Anyway, as a teacher I use screen annotation A LOT and a Mouse Mark effect overhaul wold be great. I would also add the following features to this list: * redo to the undo * shapes * hide/show marks * work properly with the zoom effect -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455889] Parse autostarted .desktop files and display any errors in the UI
https://bugs.kde.org/show_bug.cgi?id=455889 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications with malformed .desktop files do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #15 from Henrique Sant'Anna --- The "TerminalOptions=" parameter, which makes ".desktop" files invalid, is added by Plasma. To reproduce: In the startup and shutdown settings click on Properties for any listed application, then enter the Application tab of the properties window, edit the command line and then press the OK button. As a result, the ".desktop" file now has the invalid parameter "TerminalOptions=" which prevents the application from auto-starting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications with malformed .desktop files do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #14 from Henrique Sant'Anna --- I suggest that for every ".desktop" file that cannot be auto-started, a notification be generated for the user, so that the user knows that that specific application could not be started automatically. Furthermore, it is important that in the configuration screen for automatic startup it is clear to the user which of the listed applications will never be started and, if possible, for what reason. Waiting for users to realize for themselves that a certain application did not start when it should and that after that they have to investigate in the logs why the application was not started, does not seem to me to be an desirable behavior. Therefore, I consider that this is a bug, whatever the solution that is developed to fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #8 from Henrique Sant'Anna --- Created attachment 150104 --> https://bugs.kde.org/attachment.cgi?id=150104&action=edit the desktop generates log error and the app will not be autostarted jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Invalid value for boolean: False jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Failed to parse file: Invalid argument jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Failed to parse /home/henrique/.config/autostart/copyq.desktop, ignoring it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 --- Comment #7 from Henrique Sant'Anna --- I'm affected by this bug too. I have 6 apps set to autostart, but only one is currrently starting (Yakuake). X11 plasma session. from `journalctl -b` I can see this: ` jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Invalid value for boolean: False jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/copyq.desktop:181: Failed to parse file: Invalid argument jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Failed to parse /home/henrique/.config/autostart/copyq.desktop, ignoring it jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/insync.desktop:15: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/org.kde.latte-dock.desktop:43: Unknown key name 'InitialPreference' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Configuration file /home/henrique/.config/autostart/org.kde.yakuake.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/org.kde.yakuake.desktop:163: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Configuration file /home/henrique/.config/autostart/telegramdesktop.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/telegramdesktop.desktop:18: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: Configuration file /home/henrique/.config/autostart/goldendict.desktop is marked executable. Please remove executable permission bits. Proceeding anyway. jun 23 15:30:17 anarch systemd-xdg-autostart-generator[1518]: /home/henrique/.config/autostart/goldendict.desktop:16: Unknown key name 'TerminalOptions' in section 'Desktop Entry', ignoring. ` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455252] Applications do not autostart with systemd boot
https://bugs.kde.org/show_bug.cgi?id=455252 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 --- Comment #17 from Henrique Sant'Anna --- I'm using kwin 5.24.4 and can reproduce this problem ALWAYS, every time I unplug HDMI cable without deactivating the external monitor first. But now the screen completely freezes, even the mouse pointer, and after that it will not unfreeze anymore. I'm on Arch and I don't know how to collect useful information about this freeze, since I don't have debug symbols installed, maybe I have to compile it myself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451531] Dual screen, different resolutions, clone mode -> missing panel
https://bugs.kde.org/show_bug.cgi?id=451531 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449957] KWin crash in KWin::PlacementArea() when turning off or unplugging monitor
https://bugs.kde.org/show_bug.cgi?id=449957 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440002] Alternate Zoom effect shortcuts are not saved
https://bugs.kde.org/show_bug.cgi?id=440002 --- Comment #7 from Henrique Sant'Anna --- Try to set those shortcuts as Global Alternative, that is how I do. I don't even know what the shortcut on first column does. For a shortcut to work from anywhere it have to be of the Global type. In case of a desktop effect I think that it should be always as Global shortcuts, at least the way I understand it. With the current UI that is not obvious to the user and can lead to confusion. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371502] Task switcher (task manager) only allows to switch between two windows of application
https://bugs.kde.org/show_bug.cgi?id=371502 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429377] Wayland: zoom effect reverting to proportional mouse-tracking
https://bugs.kde.org/show_bug.cgi?id=429377 --- Comment #8 from Henrique Sant'Anna --- I can reproduce it on wayland. With X11 it works ok. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429377] Wayland: zoom effect reverting to proportional mouse-tracking
https://bugs.kde.org/show_bug.cgi?id=429377 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440002] Alternate Zoom effect shortcuts are not saved
https://bugs.kde.org/show_bug.cgi?id=440002 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #4 from Henrique Sant'Anna --- What do you meant on OBSERVED RESULT when said "It is not saved" ? Are you saying that after setting new shorcuts and pressing OK button to confirm you reopen the setting and the shortcuts are not there anymore? I tested on X11 to set Meta+y as reduce zoom and it works for me. There are some open bugs related to shortcuts not working when there is set multiple keyboard layouts. Does it is your case? Do you have more than one keyboard layout configured? Does it reproduces to any layout? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441898] zoom breaks when reaching above 4x zoom levels
https://bugs.kde.org/show_bug.cgi?id=441898 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402913] Alt shortcuts get eaten when adding a second keyboard layout
https://bugs.kde.org/show_bug.cgi?id=402913 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413075] The first window open in a session has no windeco if non-Breeze
https://bugs.kde.org/show_bug.cgi?id=413075 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 408468] [Wayland] Yakuake on Wayland always appears under top panel
https://bugs.kde.org/show_bug.cgi?id=408468 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #22 from Henrique Sant'Anna --- With a top Latte panel Yakuake appears right next to the top panel. Works good. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 395476] The minimum window size of System Settings is too big for a 1366x768 screen
https://bugs.kde.org/show_bug.cgi?id=395476 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436166] Keyboard navigation and mouse over both move current index
https://bugs.kde.org/show_bug.cgi?id=436166 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 171295] Allow shortcuts for input devices other than the keyboard (mouse, lirc, bluetooth, joystick, etc)
https://bugs.kde.org/show_bug.cgi?id=171295 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 356688] Cannot navigate calendar grid with the keyboard
https://bugs.kde.org/show_bug.cgi?id=356688 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 387663] Dolphin doesn't update view (doesn't show new files)
https://bugs.kde.org/show_bug.cgi?id=387663 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435860] Window decorations broken under non 100% scaling in wayland
https://bugs.kde.org/show_bug.cgi?id=435860 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436595] Badly rendered rounded corners.
https://bugs.kde.org/show_bug.cgi?id=436595 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395725] Blur effect applied to decoration shadows
https://bugs.kde.org/show_bug.cgi?id=395725 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437251] increase disable touchpad while typing time
https://bugs.kde.org/show_bug.cgi?id=437251 --- Comment #5 from Henrique Sant'Anna --- I have enabled the touchpad option to "Disable while typing" and it doesn't work at all on Wayland. As a test I opened Kate and started typing a sequence of keybord keys while doing some touching over touchpad. The result is that every touch over touchpad will trigger mouse clicks, which will change position from text input cursor and sometimes will select already typed text, which will lead to overwriting the selected text if I continue the typing on keyboard. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437251] increase disable touchpad while typing time
https://bugs.kde.org/show_bug.cgi?id=437251 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- 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 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437382] Recent locations and recent files are broken in Dolphin
https://bugs.kde.org/show_bug.cgi?id=437382 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419176] Keyboard shortcut meta+tab only allows one tab per meta, while alt+tab allows repeated presses of tab
https://bugs.kde.org/show_bug.cgi?id=419176 --- Comment #5 from Henrique Sant'Anna --- Tested with Plasma 5.21.5 (Wayland), still an issue. If I change the shortcut it only works for changing one window. If I change the shortcut back to the old value it works multiple times in sequence, for changing between multiple windows. Restarting will fix the behavior for a new set shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 437331] Starting Kget show tray icon instead of main interface
https://bugs.kde.org/show_bug.cgi?id=437331 Henrique Sant'Anna changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Henrique Sant'Anna --- There should be an option to "Start kget minimized to tray", otherwise kget window should be shown when kget is started, no mattering its last state before being closed. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 437330] kget start is slow
https://bugs.kde.org/show_bug.cgi?id=437330 Henrique Sant'Anna changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367666] Add option to change wallpaper for lock screen, login screen, and desktop all at once
https://bugs.kde.org/show_bug.cgi?id=367666 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437089] System Monitor window never opens maximized on Wayland
https://bugs.kde.org/show_bug.cgi?id=437089 --- Comment #3 from Henrique Sant'Anna --- I tested on 5.21.90 and I can confirm that, but not only for System Monitor, the same occurs for other apps tested: Dolphin, System Settings, Discover... If the app is closed while maximized, the next time it will start restored (unmaximized) with the exact same size as it was when maximized, filling the entire screen. >From that state, you can maximize and than restore again with no impact to the window dimensions. I think that the expected behavior is: - If an Window / Application closes while maximized, next time it should start maximized (state). - When a maximized window gets restored, it should be set for its last restored dimensions. - Which possible means that kwin (or the application) should save app's dimensions before it being maximized and than load that saved dimensions when the window is restored. - The saved window dimensions should persist between application sessions, as for its maximized / restored state. - When restoring window dimensions, it probably should be validated against the current screen/desktop size (which kwin already does, it seams). -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 437330] kget start is slow
https://bugs.kde.org/show_bug.cgi?id=437330 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- I could confirm that with my main user and some complete downloads on the list, starting kget that way is abnormally slow to start compared no any other KDE apps. But I couldn't reproduce this with a new user and with empty kget download list. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 437331] Starting Kget show tray icon instead of main interface
https://bugs.kde.org/show_bug.cgi?id=437331 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- It seems kget will remember its last state before quitting. If window was open when kget quits (Ctrl+Q) it will restore the window when started. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437089] System Monitor window never opens maximized on Wayland
https://bugs.kde.org/show_bug.cgi?id=437089 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436821] Streamline the flow of switching users
https://bugs.kde.org/show_bug.cgi?id=436821 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436249] "open klipper at mouse position" shows a menu inside a regular window on Wayland
https://bugs.kde.org/show_bug.cgi?id=436249 --- Comment #4 from Henrique Sant'Anna --- Tested from git master: This bug also affects klipper on default Plasma panel, not only Latte dock. If any window is focused, pressing "open klipper at mouse position" shortcut will open klipper with window decorations AND AT WRONG POSITION (not at mouse position) as reported by Bug 435013. If desktop is focused (e.g. click at desktop first), klipper will open once without window decoration and at the correct mouse position but, interspersed, closing klipper list and pressing shortcut again will than open klipper once at the wrong position and with window decorations. The expected behavior is: - When pressing the shortcut, klipper will always open without window decoration and always at the mouse position, not mattering if the focus is at some window or at desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435013] Popup of Klipper does not open at cursor position on Wayland
https://bugs.kde.org/show_bug.cgi?id=435013 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=436249 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436249] "open klipper at mouse position" shows a menu inside a regular window on Wayland
https://bugs.kde.org/show_bug.cgi?id=436249 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=435013 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437115] kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true
https://bugs.kde.org/show_bug.cgi?id=437115 --- Comment #3 from Henrique Sant'Anna --- Tested and I can confirm that it is fixed on git master. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 --- Comment #8 from Henrique Sant'Anna --- May be a duplicate with Bug 428383 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428383] [Wayland] Yakuake is not minimizing/hiding when clicking on empty area of desktop
https://bugs.kde.org/show_bug.cgi?id=428383 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=380497 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=428383 CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=428383 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428383] [Wayland] Yakuake is not minimizing/hiding when clicking on empty area of desktop
https://bugs.kde.org/show_bug.cgi?id=428383 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=435544 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 --- Comment #2 from Henrique Sant'Anna --- May be a duplicate of Bug 428383. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 428383] [Wayland] Yakuake is not minimizing/hiding when clicking on empty area of desktop
https://bugs.kde.org/show_bug.cgi?id=428383 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435544] Application focus issue
https://bugs.kde.org/show_bug.cgi?id=435544 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- This happens on Wayland or X11? What is your window manager / compositor? Is this kwin? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437115] kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true
https://bugs.kde.org/show_bug.cgi?id=437115 --- Comment #2 from Henrique Sant'Anna --- Here is the bug report on Firefox's side: https://bugzilla.mozilla.org/show_bug.cgi?id=1711266 There we figured out that the crash is probably related to kwin_wayland wp_viewporter (un)support protocol, already requested by Bug 434631. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437115] kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true
https://bugs.kde.org/show_bug.cgi?id=437115 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=434631 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434631] wp_viewporter support
https://bugs.kde.org/show_bug.cgi?id=434631 Henrique Sant'Anna changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=437115 CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437115] New: kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true
https://bugs.kde.org/show_bug.cgi?id=437115 Bug ID: 437115 Summary: kwin_wayland crashes when firefox-nightly starts if gfx.webrender.compositor.force-enabled=true Product: kwin Version: 5.21.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: hsanta...@gmail.com Target Milestone: --- SUMMARY I updated firefox-nightly on Arch Linux to 90.0a1 (2021-05-13) and I'm getting compositor crash on KDE Plasma Wayland (kwin_wayland) every time firefox-nightly is started. Tested with firefox-nightly --safe-mode and that way kwin_wayland compositor will not crash. So I figured out that it was related to Firefox's gfx.webrender.compositor.force-enabled=true about:config setting. Opening firefox-nightly on XWayland (works) and setting gfx.webrender.compositor.force-enabled=false solved the compositor crashing, so I can start the current nightly version as an Wayland client again. STEPS TO REPRODUCE 0. Start KDE Plasma (Wayland) 1. Install and open firefox-nightly 90.0a1 (2021-05-13) 2. go to about:config and set: - gfx.webrender.compositor = true - gfx.webrender.compositor.force-enabled = true 3. Quit Firefox Nighly (Ctrl+Q) 4. Start Firefox Nightly with `MOZ_ENABLE_WAYLAND=1 firefox-nightly` 5. kwin_wayland will crash and all open apps will die. OBSERVED RESULT kwin_wayland compositor will crash when firefox-nightly is started. My previous firefox-nightly version (90.0a1 (2021-05-07)) was working good even with gfx.webrender.compositor.force-enabled=true. EXPECTED RESULT kwin_wayland should not crash when firefox-nightly starts and all open apps should not die together. SOFTWARE/OS VERSIONS Linux: 5.12.3-arch1 (Arch Linux) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2+kde+r192-1 ADDITIONAL INFORMATION Please, I would appreciate any info on how to debug this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 429087] Entire session crashes closing all running apps if kwin_wayland crashes
https://bugs.kde.org/show_bug.cgi?id=429087 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437083] Kwin_wayland crashes and kills all running apps randomly
https://bugs.kde.org/show_bug.cgi?id=437083 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 --- Comment #26 from Henrique Sant'Anna --- Seems related to Bug 436246. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425537] For applications with 2 variants of desktop files remembers the wrong one as pinned
https://bugs.kde.org/show_bug.cgi?id=425537 --- Comment #2 from Henrique Sant'Anna --- As reported at Bug 435923, I had installed Firefox Nightly and Firefox stable, than trying to pin Firefox Nightly from (and to) Icons-only Task Manager will pin Firefox stable instead. Also, pinning from launcher (drag and drop) will produce the correct pinned icon (Firefox Nightly), but once the task is started the task manager will create another icon associated to the started Firefox Nightly but with wrong icon (got from Firefox stable). Trying to workaround this and get more details to this bug report, I removed any Firefox .desktop files from ~/.local/share/applications/, keeping only those in /usr/share/applications/. This didn't help and the problem persisted. So I uninstalled Firefox stable, to remove /usr/share/applications/firefox.desktop and to leave only /usr/share/applications/firefox-nightly.desktop. Than, after starting Firefox Nightly from Icons-Only Task Manager, the started task got a new icon from icon task manager, not related to Firefox Nightly, not even Firefox Stable (which was uninstalled), the new task icon was the orange icon from Wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436249] "open klipper at mouse position" shows a menu inside a regular window on Wayland
https://bugs.kde.org/show_bug.cgi?id=436249 --- Comment #1 from Henrique Sant'Anna --- May be related to Bug #430662 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436249] New: "open klipper at mouse position" shows a menu inside a regular window on Wayland
https://bugs.kde.org/show_bug.cgi?id=436249 Bug ID: 436249 Summary: "open klipper at mouse position" shows a menu inside a regular window on Wayland Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: hsanta...@gmail.com Target Milestone: 1.0 Flags: Wayland+ Created attachment 137949 --> https://bugs.kde.org/attachment.cgi?id=137949&action=edit Klipper menu inside a regular window SUMMARY On Wayland, pressing shortcut to "open klipper at mouse position" will open a menu inside a window (with title-bar and borders) if Klipper was started by/inside notification area on Latte (dock / panel). STEPS TO REPRODUCE 1. Start KDE Plasma Wayland session; 2. Start Latte dock with an layout containing notification area widget inside a latte dock / latte panel; (be sure that isn't any other notification area widget on another plasma panel or another instance of klipper running besides the one started inside latte dock) 3. Press shortcut to "open Klipper at mouse position" OBSERVED RESULT A Window will be opened (with tittle-bar and borders) containing a menu listing clipboard contents. EXPECTED RESULT A menu should be opened (without title-bar or borders) listing clipboard contents on this menu. SOFTWARE/OS VERSIONS Platform: Linux (Arch Linux) QT: 5.15.2+kde+r180-1 Desktop: KDE Plasma 5.21.4 (Wayland) ADDITIONAL INFORMATION If not using Latte dock, but regular plasma panel, pressing shortcut to "open klipper at mouse position" will open a menu at mouse position, without title-bar or borders. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434504] Klipper wayland sync highlight does not work in wayland
https://bugs.kde.org/show_bug.cgi?id=434504 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com --- Comment #1 from Henrique Sant'Anna --- May be related to bug #436246 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436246] New: Mouse selection clipboard (PRIMARY) works on Wayland, but klipper wont capture it
https://bugs.kde.org/show_bug.cgi?id=436246 Bug ID: 436246 Summary: Mouse selection clipboard (PRIMARY) works on Wayland, but klipper wont capture it Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: hsanta...@gmail.com Target Milestone: 1.0 Flags: Wayland+ SUMMARY GTK 3.24.29 received a path that made PRIMARY work between QT/KDE apps on Wayland. So we can mouse select text from (e.g.) Firefox and than paste it by middle clicking to (e.g.) Konsole. But right now this text is not captured by klipper (5.21.4). Klipper will not capture PRIMARY (mouse selection), no matter if from GTK apps or KDE / QT apps. STEPS TO REPRODUCE 1. Start KDE Plasma (Wayland session) and start Klipper 2. Open any app (like a GTK app or a KDE/QT app); 3. Select text with mouse cursor; 4. Open another app; 5. Use middle click to paste the text previously selected, from the first app to the second one; 6. Check Klipper, the selected (and pasted) text was not captured by Klipper. OBSERVED RESULT Klipper will not capture text from mouse selection on Wayland, even when mouse selection clipboard is working good (we can select to copy and middle click to paste). EXPECTED RESULT Klipper should capture from mouse selection on Wayland. SOFTWARE/OS VERSIONS Platform: Linux (Arch Linux) QT: 5.15.2+kde+r180-1 Desktop: KDE Plasma 5.21.4 (Wayland) ADDITIONAL INFORMATION Tested with: QT_QPA_PLATFORM=wayland klipper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 --- Comment #3 from Henrique Sant'Anna --- Created attachment 137707 --> https://bugs.kde.org/attachment.cgi?id=137707&action=edit /usr/share/applications/firefox-nightly.desktop Firefox Nightly .desktop file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 --- Comment #2 from Henrique Sant'Anna --- Created attachment 137706 --> https://bugs.kde.org/attachment.cgi?id=137706&action=edit ~/.local/share/applications/firefox.desktop Firefox (stable) .desktop file -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 --- Comment #1 from Henrique Sant'Anna --- May be related to Bug #425537 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435923] New: Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started
https://bugs.kde.org/show_bug.cgi?id=435923 Bug ID: 435923 Summary: Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started Product: plasmashell Version: 5.21.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: hsanta...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Pinned Firefox Nightly icon at task manager will create a second Firefox (stable) icon when started, instead of the task being associated to already pinned icon. STEPS TO REPRODUCE 1. Pin Firefox Nightly icon to task manager (drag and drop Firefox Nightly icon from menu launcher to task manager); 2. Start Firefox Nightly by clicking over its task manager pinned icon; 3. Firefox Nightly will start and a new separated task icon will show up at task manager; OBSERVED RESULT - Starting Firefox Nightly from pinned icon will generate a new task icon in task manager while Firefox Nightly is running. This new icon is orange and not blue (it is associated to Firefox Stable, and not Firefox Nightly). - Trying to pin Firefox Nightly to task manager (right click over current running instance of Firefox Nightly) will pin Firefox Stable instead of Firefox Nightly. EXPECTED RESULT - Pinned Firefox Nightly icon, when started, should not create a new task icon at task manager. Firefox Nightly task should be associated to the already pinned icon. - Pinning Firefox Nightly from right click over currently running Firefox Nightly task should pin Firefox Nightly icon and not Firefox Stable icon. SOFTWARE/OS VERSIONS Linux: Arch (Linux 5.11.14-arch1-1) KDE Plasma Version: 5.21.4 KDE Frameworks 5.81.0 Qt 5.15.2 (built against 5.15.2) The wayland windowing system ADDITIONAL INFORMATION This behavior seems to have been introduced very recently, somewhat in Plasma 5.21.x, but may be triged by some Firefox update, I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425537] For applications with 2 variants of desktop files remembers the wrong one as pinned
https://bugs.kde.org/show_bug.cgi?id=425537 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355588] Switching between alternative widgets makes them lose settings
https://bugs.kde.org/show_bug.cgi?id=355588 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Henrique Sant'Anna changed: What|Removed |Added CC||hsanta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
