[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 mydarkstar changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485258 --- Comment #16 from mydarkstar --- Let's wait for the next KDE Frameworks release and see if it's fixed in there. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 485258] Dolphin crashed after dragging a file to the path breadcrumb
https://bugs.kde.org/show_bug.cgi?id=485258 mydarkstar changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=471279 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483645] Drag and drop files to web browser only work for the first file
https://bugs.kde.org/show_bug.cgi?id=483645 mydarkstar changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485630 --- Comment #11 from mydarkstar --- *** Bug 485630 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 mydarkstar changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=485630 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485630] Dolphin freezes or crashes when dragging file to a Firefox window or dragging files sporadically disables until Dolphin is restarted
https://bugs.kde.org/show_bug.cgi?id=485630 mydarkstar changed: What|Removed |Added Summary|Dolphin crashes when|Dolphin freezes or crashes |dragging png file to a FF |when dragging file to a |window |Firefox window or dragging ||files sporadically disables ||until Dolphin is restarted Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED See Also||https://bugs.kde.org/show_b ||ug.cgi?id=471279, ||https://bugs.kde.org/show_b ||ug.cgi?id=483645 --- Comment #8 from mydarkstar --- > Probably, the "3) drag-drop sometimes (sporadically) disables until Dolphin > is restarted" is either > something new, or a duplicate of some other bug. However, it started > happening only recently > and not so frequently (yet), so it deserves a separate, clear, focused > report, so let's forget it here. Agreed! That sounds like a plan. I'm fairly certain you can edit your own bug reports and even close them, by the way. I now tried to set a more descriptive title and linked the other bug reports. Please open a new report or comment on an existing one, if you find out more about the freezing or drag-and-drop issues! You can tell us about any new related bug reports in this report. *** This bug has been marked as a duplicate of bug 483645 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485630] Dolphin crashes when dragging png file to a FF window
https://bugs.kde.org/show_bug.cgi?id=485630
mydarkstar changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|DUPLICATE |---
--- Comment #5 from mydarkstar ---
I apologize! It indeed seems more plausible that the freezing part is related
to bug 483645, from March.
("Drag and drop files to web browser only work for the first file")
Would you prefer to mark it as a duplicate for that bug instead?
As for the crash, Michał and I have commented on bug 471279 that it likely
seems to be identical.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 --- Comment #13 from mydarkstar --- (In reply to Michał from comment #12) Re: Bug 485630 That sounds very plausible. I noticed that the backtrace went pretty much identical as with the one I attached to this issue. When experiencing this bug, I also thought that the issue was related to Kdenlive at first. Until I eventually tried dragging the file to the side instead of upwards. However, as Dilam noted in your bug report, your issue with Dolphin freezing seems to not be related to this. For that, I will comment on your report separately though. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 451774] Selecting remote protocol does not properly auto-fill "//"
https://bugs.kde.org/show_bug.cgi?id=451774 --- Comment #5 from mydarkstar --- (In reply to Bug Janitor Service from comment #4) > A possibly relevant merge request was started @ > https://invent.kde.org/frameworks/kio/-/merge_requests/1233 It seems like the submitted patch is unfortunately not working. @Szymon: Please check the comments on the Merge Request, if possible. Thank you for submitting the patch! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 474893] Plasma crashed in BluezQt::PendingCall::finished() after disconnecting Bluetooth earphones
https://bugs.kde.org/show_bug.cgi?id=474893 --- Comment #4 from mydarkstar --- Bug 482565 seems to crash in the same way. However, that one deals with connecting a Bluetooth audio device. I believe it is fair to assume that this crash may occur on both disconnection and connection. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 474893] Plasma crashed in BluezQt::PendingCall::finished() after disconnecting Bluetooth earphones
https://bugs.kde.org/show_bug.cgi?id=474893 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #3 from mydarkstar --- This may be a duplicate of bug 465031, as both seem to crash in BluezQt::PendingCall::finished. I experienced the same issue in bug 485618. However, I'm not able to reliably reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485700] plasmashell crashes while reordering Favorites in Application Launcher
https://bugs.kde.org/show_bug.cgi?id=485700 --- Comment #1 from mydarkstar --- Created attachment 168627 --> https://bugs.kde.org/attachment.cgi?id=168627=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485700] New: plasmashell crashes while reordering Favorites in Application Launcher
https://bugs.kde.org/show_bug.cgi?id=485700 Bug ID: 485700 Summary: plasmashell crashes while reordering Favorites in Application Launcher Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: mds_f...@protonmail.com Target Milestone: 1.0 Application: plasmashell (6.0.4) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.6.21-273-tkg-linux-lts-tkg-bmq x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: After the update from Plasma 6.0.3 to 6.0.4, my favorite apps in the Application Launcher were out of order. While trying to drag-and-drop them into the correct order, plasmashell crashed right away. After this crash, reordering the items worked fine. The crash does not seem to be reproducible. -- Backtrace (Reduced): #5 std::__atomic_base::load (__m=std::memory_order_acquire, this=0x74006100630079) at /usr/include/c++/13.2.1/atomic:576 #6 std::atomic::load (__m=std::memory_order_acquire, this=0x74006100630079) at /usr/include/c++/13.2.1/atomic:577 #7 QAtomicOps::loadAcquire (_q_value=) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/thread/qatomic_cxx11.h:214 #8 QBasicAtomicPointer::loadAcquire (this=0x74006100630079) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/thread/qbasicatomic.h:177 #9 QObjectPrivate::maybeSignalConnected (this=, signalIndex=9) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.7.0/src/corelib/kernel/qobject.cpp:485 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485558] Dolphin crash
https://bugs.kde.org/show_bug.cgi?id=485558 mydarkstar changed: What|Removed |Added Resolution|--- |DUPLICATE CC||mds_f...@protonmail.com Status|REPORTED|RESOLVED --- Comment #1 from mydarkstar --- *** This bug has been marked as a duplicate of bug 471279 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 mydarkstar changed: What|Removed |Added CC||atesc...@gmail.com --- Comment #10 from mydarkstar --- *** Bug 485558 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 mydarkstar changed: What|Removed |Added CC||laimis.liumpa...@gmail.com --- Comment #9 from mydarkstar --- *** Bug 485672 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485672] Dolphin crashes when dragging any file to address bar
https://bugs.kde.org/show_bug.cgi?id=485672 mydarkstar changed: What|Removed |Added Summary|Dolphinn crashes when |Dolphin crashes when |draging any file to adress |dragging any file to |window |address bar Status|REPORTED|RESOLVED CC||mds_f...@protonmail.com Resolution|--- |DUPLICATE --- Comment #2 from mydarkstar --- *** This bug has been marked as a duplicate of bug 471279 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 mydarkstar changed: What|Removed |Added CC||michal.dybc...@gmail.com --- Comment #8 from mydarkstar --- *** Bug 485630 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485630] Dolphin crashes when dragging png file to a FF window
https://bugs.kde.org/show_bug.cgi?id=485630 mydarkstar changed: What|Removed |Added Resolution|--- |DUPLICATE CC||mds_f...@protonmail.com Status|REPORTED|RESOLVED --- Comment #3 from mydarkstar --- *** This bug has been marked as a duplicate of bug 471279 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471279] Dolphin crash when dragging files or folders across or to the path navigation bar
https://bugs.kde.org/show_bug.cgi?id=471279 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #7 from mydarkstar --- Created attachment 168622 --> https://bugs.kde.org/attachment.cgi?id=168622=edit Backtrace of the crash (Dolphin 24.02.2) I can reproduce this on my system. When dragging any file over the location bar (when it is not in edit mode), Dolphin reliably crashes. I attached a backtrace of the newest Dolphin version, since the previous one is from version 23.04.1. SOFTWARE/OS VERSIONS Operating System: Arch Linux Dolphin Version: 24.02.2 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 485618] plasmashell crash when Bluez hangs
https://bugs.kde.org/show_bug.cgi?id=485618 --- Comment #3 from mydarkstar --- Thread 1 (Thread 0x76d8b35d01c0 (LWP 1695)): [KCrash Handler] #5 0x76d8b95b1629 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlRefPointer const&, QObject*, QV4::String*, QFlags, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #6 0x76d8b95a713a in QV4::QQmlContextWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt6Qml.so.6 #7 0x76d8b95332a3 in QV4::ExecutionContext::setProperty(QV4::String*, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #8 0x76d8b95cbdc5 in QV4::Runtime::StoreNameSloppy::call(QV4::ExecutionEngine*, int, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #9 0x76d8b95ff081 in ??? () at /usr/lib/libQt6Qml.so.6 #10 0x76d8b960da95 in ??? () at /usr/lib/libQt6Qml.so.6 #11 0x76d8b9579af8 in ??? () at /usr/lib/libQt6Qml.so.6 #12 0x76d8b95b1df7 in ??? () at /usr/lib/libQt6Qml.so.6 #13 0x76d8b8591599 in ??? () at /usr/lib/libQt6Core.so.6 #14 0x76d853e60d84 in BluezQt::PendingCall::finished(BluezQt::PendingCall*) () at /usr/lib/libKF6BluezQt.so.6 #15 0x76d853e67488 in ??? () at /usr/lib/libKF6BluezQt.so.6 #16 0x76d8b8591599 in ??? () at /usr/lib/libQt6Core.so.6 #17 0x76d8b93bee90 in ??? () at /usr/lib/libQt6DBus.so.6 #18 0x76d8b857cbb7 in QObject::event(QEvent*) () at /usr/lib/libQt6Core.so.6 #19 0x76d8ba2f437b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt6Widgets.so.6 #20 0x76d8b853a198 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt6Core.so.6 #21 0x76d8b853a51b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt6Core.so.6 #22 0x76d8b8775ba4 in ??? () at /usr/lib/libQt6Core.so.6 #23 0x76d8b7184199 in g_main_dispatch (context=0x76d8ac000f00) at ../glib/glib/gmain.c:3344 #24 0x76d8b71e33bf in g_main_context_dispatch_unlocked (context=0x76d8ac000f00) at ../glib/glib/gmain.c:4152 #25 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x76d8ac000f00, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4217 #26 0x76d8b7183712 in g_main_context_iteration (context=0x76d8ac000f00, may_block=1) at ../glib/glib/gmain.c:4282 #27 0x76d8b8773cd4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt6Core.so.6 #28 0x76d8b85446ee in QEventLoop::exec(QFlags) () at /usr/lib/libQt6Core.so.6 #29 0x76d8b853cc38 in QCoreApplication::exec() () at /usr/lib/libQt6Core.so.6 #30 0x55fa14a58476 in main (argc=, argv=) at /usr/src/debug/plasma-workspace/plasma-workspace-6.0.3/shell/main.cpp:214 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 485618] plasmashell crash when Bluez hangs
https://bugs.kde.org/show_bug.cgi?id=485618 mydarkstar changed: What|Removed |Added Product|plasmashell |frameworks-bluez-qt Assignee|plasma-b...@kde.org |kdelibs-b...@kde.org Version|6.0.3 |6.0.0 Component|generic-crash |general Target Milestone|1.0 |--- --- Comment #2 from mydarkstar --- The following bug report for Plasma 5.27.7 seems relevant, with *disconnecting* a Bluetooth device: https://bugs.kde.org/show_bug.cgi?id=474893 This bug report for Plasma 5.26.5 also *disconnects* a Bluetooth device: https://bugs.kde.org/show_bug.cgi?id=465031 Lastly, this bug report for Plasma 6.0.1 seems similar, but with *connecting* a Bluetooth device: https://bugs.kde.org/show_bug.cgi?id=482565 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485618] plasmashell crash when Bluez hangs
https://bugs.kde.org/show_bug.cgi?id=485618 --- Comment #1 from mydarkstar --- Created attachment 168575 --> https://bugs.kde.org/attachment.cgi?id=168575=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485618] New: plasmashell crash when Bluez hangs
https://bugs.kde.org/show_bug.cgi?id=485618 Bug ID: 485618 Summary: plasmashell crash when Bluez hangs Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: mds_f...@protonmail.com Target Milestone: 1.0 Application: plasmashell (6.0.3) Qt Version: 6.6.3 Frameworks Version: 6.0.0 Operating System: Linux 6.6.21-273-tkg-linux-lts-tkg-bmq x86_64 Windowing System: Wayland Distribution: Arch Linux DrKonqi: 6.0.3 [CoredumpBackend] -- Information about the crash: I more or less accidentally clicked the "Enable Bluetooth" toggle in the Bluetooth applet while listening to music via Bluetooth. The Bluetooth headphones got disconnected, but Plasma still showed them as connected, including a list of other devices, even though it showed the Bluetooth toggle as disabled. Pipewire also continued to play the music via the disconnected device, which was visible in the Audio Volume applet. When trying to restart `bluetooth.service` via systemctl, plasmashell promptly crashed. `bluetooth.service` also would not stop when executing the restart command. I had to kill it. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x76d8b95b1629 in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlRefPointer const&, QObject*, QV4::String*, QFlags, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #6 0x76d8b95a713a in QV4::QQmlContextWrapper::virtualPut(QV4::Managed*, QV4::PropertyKey, QV4::Value const&, QV4::Value*) () at /usr/lib/libQt6Qml.so.6 #7 0x76d8b95332a3 in QV4::ExecutionContext::setProperty(QV4::String*, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #8 0x76d8b95cbdc5 in QV4::Runtime::StoreNameSloppy::call(QV4::ExecutionEngine*, int, QV4::Value const&) () at /usr/lib/libQt6Qml.so.6 #9 0x76d8b95ff081 in ??? () at /usr/lib/libQt6Qml.so.6 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #25 from mydarkstar --- Created attachment 168412 --> https://bugs.kde.org/attachment.cgi?id=168412=edit Demo of the Klipper window opening in the wrong positions I can reproduce the issue on the latest KDE neon Testing (20240402) via the all-defaults Live ISO as well. Please view my attached demo video. STEPS TO REPRODUCE 1. Boot KDE neon Testing Live ISO 2. Copy any text into the clipboard 3. Open a window OR panel widget 4. Press your assigned shortcut for "Show Clipboard Items at Mouse Position" (default: Meta + V) OBSERVED RESULT The Klipper window is NOT spawned at the mouse position. Instead, the top-left of the window is ALWAYS spawned in the center of the screen. Or, for when a panel widget is open, at another weird spot. EXPECTED RESULT The Klipper window should always spawn at the mouse position, like it did previously and on X11. SOFTWARE/OS VERSIONS Linux: KDE neon Testing 20240402 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION - This works fine on X11. I can confirm that ONLY Wayland is affected. - The issue can be reproduced very quickly on an all-defaults KDE neon VM. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added Attachment #168341|breeze2 |Screen Edges UI for description||comparison (Breeze Dark) --- Comment #14 from mydarkstar --- Comment on attachment 168341 --> https://bugs.kde.org/attachment.cgi?id=168341 Screen Edges UI for comparison (Breeze Dark) Nonetheless, the Screen Edges UI serves as a good comparison! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added Attachment #168340|breeze1 |Screen Edges UI (Breeze description||Light) Attachment #168340|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #13 from mydarkstar --- Dennis, the screenshots you sent are for the Screen Edges settings, not for Notifications. You must have mistakenly clicked on the wrong settings page. This issue discusses the fact that the Popup Position UI is broken: System Settings → *Notifications* → Under Popup Location → Choose Custom Position... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- Summary|Notifications KCM "Choose |Notifications KCM "Choose |Custom Position"|Custom Position" UI is |display-visualization is|broken |missing | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #9 from mydarkstar --- Created attachment 168329 --> https://bugs.kde.org/attachment.cgi?id=168329=edit Almost invisible popup position buttons I cannot confirm that this is fixed in the latest release, Plasma 6.0.4 on KDE neon Testing 20240402 (latest). Furthermore, I have just looked at this UI on the latest build using the Breeze color scheme, and the radio buttons are almost invisible! This issue therefore needs to stay open, as the UI is not usable. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449091] kscreenlocker crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=449091 mydarkstar changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added Product|plasmashell |systemsettings Summary|Notifications "Choose |Notifications KCM "Choose |Custom Position" display|Custom Position" |visualization is missing|display-visualization is ||missing Target Milestone|1.0 |--- Component|Notifications |kcm_notify -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460649] 22.04.01 upgrade message fails always
https://bugs.kde.org/show_bug.cgi?id=460649 mydarkstar changed: What|Removed |Added Resolution|--- |REMIND Status|REPORTED|NEEDSINFO CC||mds_f...@protonmail.com --- Comment #5 from mydarkstar --- Since KDE neon is now rebased on Ubuntu 22.04, is this still an open issue? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481670] screen energy saving not working (with HDMI cable)
https://bugs.kde.org/show_bug.cgi?id=481670 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #3 from mydarkstar --- Would this bug be filed more correctly for Powerdevil (5.27) perhaps? That's what handles dimming and turning off displays after a pre-defined idle time. Or is it specific to KDE neon, the distribution? Also, would you please be so kind and check if this is also an issue if you boot the latest KDE neon version? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 453224] Nothing happens when I click on 'Next' button
https://bugs.kde.org/show_bug.cgi?id=453224 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #6 from mydarkstar --- The package `qml-module-org-kde-syntaxhighlighting` seems to be installed on KDE neon now by default. Is this still an open issue? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484849] Wrong mouse pointer during login
https://bugs.kde.org/show_bug.cgi?id=484849 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #1 from mydarkstar --- Hello Rafael, could you please check if going to "System Settings → Colors & Themes → Login Screen (SDDM) → Apply Plasma Settings... → Apply" fixes your issue? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485028] Breeze Dark is broken in Flatpak applications
https://bugs.kde.org/show_bug.cgi?id=485028 mydarkstar changed: What|Removed |Added CC||agrine...@gmail.com, ||mds_f...@protonmail.com, ||uhh...@gmail.com Component|general |gtk theme Version|unspecified |6.0.3 Product|neon|Breeze Ever confirmed|0 |1 Assignee|neon-b...@kde.org |plasma-b...@kde.org Status|REPORTED|CONFIRMED --- Comment #3 from mydarkstar --- I can confirm this issue: a.) After updating to Plasma 6.0, GTK 3 Flatpak apps do not use Breeze-GTK anymore. b.) When setting `GTK_THEME=Breeze` for all Flatpak apps, GTK 4 apps now render with a semi-broken light theme. My recommended workaround would be to only set the `GTK_THEME=Breeze` override for GTK 3 apps, as GTK 4 apps cannot be themed by KDE anyway. This can be done using an application like Flatseal. Something does indeed seem to be wrong here though. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449091] kscreenlocker crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=449091 mydarkstar changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from mydarkstar --- I have just re-filed this bug report for kscreenlocker, which I assume you were referring to. However, I am unfortunately unable to reproduce your issue across different systems. The issue you are describing usually happens after doing a larger Plasma update and locking the screen during it. But it should definitely not occur after a reboot. Could you please check whether this is still an issue for you on a recent version? If so, please provide more details on your setup, such as your GPU and other hardware configuration. If only the mouse pointer is visible after logging into a new session, this does not appear to be an issue with kscreenlocker, but would be something separate to the first issue you described. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449091] kscreenlocker crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=449091 mydarkstar changed: What|Removed |Added CC|neon-b...@kde.org |mds_f...@protonmail.com Component|general |general Product|neon|kscreenlocker Summary|KDE NEON Screensaver|kscreenlocker crashes on |creashed|Wayland Version|unspecified |5.23.5 Assignee|neon-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 451228] Itinerary does not start
https://bugs.kde.org/show_bug.cgi?id=451228 mydarkstar changed: What|Removed |Added Platform|Other |Neon CC||mds_f...@protonmail.com --- Comment #5 from mydarkstar --- Ouch, while attempting to triage this issue, I was not even able to install the program on a fresh KDE neon Testing VM. Not via Discover, not via the terminal. Seems like there are packaging issues with KDE Itinerary in general? The error below mentions kopeninghours as well. The Flatpak seems to work perfectly fine however. ``` $ sudo apt install itinerary Reading package lists... Done Building dependency tree... Done Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) itinerary:amd64 < none -> 23.08.4+p22.04+vstable+git20240219.0025-0 @un puN Ib > Broken itinerary:amd64 Depends on qml-module-org-kde-kopeninghours:amd64 < none @un H > Broken itinerary:amd64 Depends on qml-module-org-kde-kosmindoormap:amd64 < none @un H > Broken itinerary:amd64 Depends on qml6-module-org-kde-i18n-localedata:amd64 < none | 6.0.0+p22.04+vstable+git20240331.1439-0 @un uH > Considering qml6-module-org-kde-i18n-localedata:amd64 1 as a solution to itinerary:amd64 Re-Instated qml6-module-org-kde-i18n-localedata:amd64 Broken itinerary:amd64 Depends on qml6-module-org-kde-kpublictransport:amd64 < none | 24.02.1+p22.04+vstable+git20240323.0105-0 @un uH > Considering qml6-module-org-kde-kpublictransport:amd64 1 as a solution to itinerary:amd64 Re-Instated libkpublictransport1:amd64 Re-Instated qml6-module-org-kde-kpublictransport:amd64 Broken itinerary:amd64 Depends on qml6-module-qtlocation:amd64 < none | 6.6.3-0xneon+22.04+jammy+stable+build26 @un uH > Considering qml6-module-qtlocation:amd64 1 as a solution to itinerary:amd64 Re-Instated qt6-location:amd64 Re-Instated qml6-module-qtlocation:amd64 Broken itinerary:amd64 Depends on qml6-module-qtpositioning:amd64 < none | 6.6.3-0xneon+22.04+jammy+stable+build21 @un uH > Considering qml6-module-qtpositioning:amd64 1 as a solution to itinerary:amd64 Re-Instated qml6-module-qtpositioning:amd64 Broken itinerary:amd64 Depends on kpim6-itinerary:amd64 < none | 24.02.1+p22.04+vstable+git20240402.0932-0 @un uH > (>= 23.08.4+p22.04+vstable+git20240217.0208) Considering kpim6-itinerary:amd64 0 as a solution to itinerary:amd64 Re-Instated osmctools:amd64 Re-Instated kpim6-kmime:amd64 Re-Instated kpim6-pkpass:amd64 Re-Instated libprotobuf23:amd64 Re-Instated libphonenumber8:amd64 Re-Instated kpim6-itinerary:amd64 Broken itinerary:amd64 Depends on libkhealthcertificate1:amd64 < none | 24.02.1+p22.04+vstable+git20240321.0553-0 @un uH > (>= 23.01.0+p22.04+vstable+git20240217.0308) Considering libkhealthcertificate1:amd64 0 as a solution to itinerary:amd64 Re-Instated libkhealthcertificate1:amd64 Broken itinerary:amd64 Depends on libkosmindoormap1:amd64 < none | 24.02.1+p22.04+vstable+git20240401.0149-0 @un uH > (>= 23.08.4+p22.04+vstable+git20240114.0437) Considering libkosmindoormap1:amd64 0 as a solution to itinerary:amd64 Re-Instated libkopeninghours1-qt6:amd64 Re-Instated libkosm1:amd64 Re-Instated libkosmindoormap1:amd64 Broken itinerary:amd64 Depends on libquotient-qt6-0.8:amd64 < none | 0.8.1.2-0xneon+22.04+jammy+stable+build21 @un uH > (>= 0.8.1.2) Considering libquotient-qt6-0.8:amd64 0 as a solution to itinerary:amd64 Re-Instated libolm3:amd64 Re-Instated libqt6keychain1:amd64 Re-Instated libquotient-qt6-0.8:amd64 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: itinerary : Depends: qml-module-org-kde-kopeninghours but it is not installable Depends: qml-module-org-kde-kosmindoormap but it is not installable E: Unable to correct problems, you have held broken packages. ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457515] Window Decorations disappear when selecting Plastik
https://bugs.kde.org/show_bug.cgi?id=457515 mydarkstar changed: What|Removed |Added Summary|window decorations |Window Decorations |disappear |disappear when selecting ||Plastik Version|unspecified |5.25.3 Product|neon|kwin Component|general |decorations CC|neon-b...@kde.org | Assignee|neon-b...@kde.org |kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 457515] window decorations disappear
https://bugs.kde.org/show_bug.cgi?id=457515 mydarkstar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WORKSFORME CC||mds_f...@protonmail.com --- Comment #1 from mydarkstar --- Hi David! I have tried to reproduce this issue on different systems, including the latest KDE neon Testing, but was unable to make the window decorations disappear. Plastik and other window decorations work fine across different systems. Could you please check whether this is still an issue for you? If so, please provide more details on your setup. I will also re-file this bug under kwin -> decorations. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464677] Unable to update KDE neon, shows QML errors
https://bugs.kde.org/show_bug.cgi?id=464677 mydarkstar changed: What|Removed |Added Summary|Не обновляется kde neon,|Unable to update KDE neon, |выдаёт ошибку |shows QML errors CC||mds_f...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477665] Cannot move icon in icons-only task manager if multiple instances of a program are running
https://bugs.kde.org/show_bug.cgi?id=477665
--- Comment #4 from mydarkstar ---
(In reply to Dennis from comment #0)
I can't reproduce this issue on Plasma 6.0.3, even with grouping in the
Icons-only Task Manager disabled ("Do not group").
(In reply to Gurenko Alex from comment #2)
As for the second video uploaded, I believe I have had a similar issue before a
long time ago.
It was however not related to the fact that multiple instances of a program
were running, but that a Flatpak app I had pinned (while it was running) broke
the panel's INI config. Pinning programs that are running with a lot of
parameters may put all those parameters into your panel's configuration, which
I speculate may break the parsing. Because of this, I learned to only pin those
kind of apps from the Application Launcher search.
I would recommend you try to unpin all your apps or remove the Icons-only Task
Manager entirely and re-add it to your panel.
Please report if that helps!
I have also filed this bug report for plasmashell and the Icons-only Task
Manager, instead of the KDE neon distribution and their packages. They have
nothing to do with this. :)
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 479607] plasmashell crash after login with closed lid
https://bugs.kde.org/show_bug.cgi?id=479607 mydarkstar changed: What|Removed |Added Version|unspecified |6.0.3 Product|neon|plasmashell Component|Packages Unstable Edition |generic-crash CC|neon-b...@kde.org |mds_f...@protonmail.com, ||plasma-b...@kde.org Target Milestone|--- |1.0 Assignee|neon-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477674] Notifications "Choose Custom Position" display visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added CC|neon-b...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477665] Cannot move icon in icons-only task manager if multiple instances of a program are running
https://bugs.kde.org/show_bug.cgi?id=477665 mydarkstar changed: What|Removed |Added Summary|Cannot relocate icon on |Cannot move icon in |icon-only taskbar if|icons-only task manager if |multiple instances of an|multiple instances of a |app are running |program are running -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477665] Cannot relocate icon on icon-only taskbar if multiple instances of an app are running
https://bugs.kde.org/show_bug.cgi?id=477665 mydarkstar changed: What|Removed |Added Target Milestone|--- |1.0 Assignee|neon-b...@kde.org |plasma-b...@kde.org CC||mds_f...@protonmail.com, ||qydwhotm...@gmail.com Version|unspecified |6.0.3 Product|neon|plasmashell Component|Packages Unstable Edition |Task Manager and Icons-Only ||Task Manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477674] Notifications "Choose Custom Position" display visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #6 from mydarkstar --- The UI indeed looks very broken. Can confirm. I filed the bug report in "plasmashell -> Notifications" now, instead of "KDE neon", as the issue is unrelated to the distribution. I hope this helps! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477674] Notifications "Choose Custom Position" display visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added Summary|popup position for |Notifications "Choose |notification misses screen |Custom Position" display ||visualization is missing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477674] popup position for notification misses screen
https://bugs.kde.org/show_bug.cgi?id=477674 mydarkstar changed: What|Removed |Added Version|unspecified |6.0.3 Component|Packages Unstable Edition |Notifications Product|neon|plasmashell CC||k...@privat.broulik.de, ||mds_f...@protonmail.com Target Milestone|--- |1.0 Assignee|neon-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 485116] "Retry Authentication" dialog UI appears broken
https://bugs.kde.org/show_bug.cgi?id=485116 --- Comment #1 from mydarkstar --- Created attachment 168208 --> https://bugs.kde.org/attachment.cgi?id=168208=edit Broken dialog - Invalid passphrase -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 485116] New: "Retry Authentication" dialog UI appears broken
https://bugs.kde.org/show_bug.cgi?id=485116 Bug ID: 485116 Summary: "Retry Authentication" dialog UI appears broken Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.1.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: mds_f...@protonmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 168207 --> https://bugs.kde.org/attachment.cgi?id=168207=edit Broken dialog - Invalid password SUMMARY The "Retry Authentication" dialog, that is shown when a passphrase or password gets entered incorrectly, appears broken. See the attached screenshot. STEPS TO REPRODUCE 1. Attempt to access any new remote network resource 2. Enter login details or key passphrase incorrectly OBSERVED RESULT - The second button is broken and appears without text - Both buttons appear to do the same thing EXPECTED RESULT The dialog should continue to appear like it did on Plasma 5.27. SOFTWARE/OS VERSIONS Linux: KDE neon Testing 20240402 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.3 ADDITIONAL INFORMATION The issue can be reproduced very quickly on an all-defaults KDE neon VM. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484880] 1px bottom and right not refreshing on scale +130%
https://bugs.kde.org/show_bug.cgi?id=484880 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #1 from mydarkstar --- Hello Thorsten, is this the bug you are experiencing? https://bugs.kde.org/show_bug.cgi?id=480171 It also shows a white line on the right and bottom edges of the screen. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485060] Breeze decorations draw invisible 1px border / margin on bottom and right edges of windows
https://bugs.kde.org/show_bug.cgi?id=485060 --- Comment #2 from mydarkstar --- Created attachment 168166 --> https://bugs.kde.org/attachment.cgi?id=168166=edit KDE neon with full defaults: Tiling two windows next to each other -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485060] Breeze decorations draw invisible 1px border / margin on bottom and right edges of windows
https://bugs.kde.org/show_bug.cgi?id=485060 --- Comment #1 from mydarkstar --- Created attachment 168165 --> https://bugs.kde.org/attachment.cgi?id=168165=edit KDE neon with full defaults: trying to snap Welcome Center to the bottom right -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 485060] New: Breeze decorations draw invisible 1px border / margin on bottom and right edges of windows
https://bugs.kde.org/show_bug.cgi?id=485060
Bug ID: 485060
Summary: Breeze decorations draw invisible 1px border / margin
on bottom and right edges of windows
Classification: Plasma
Product: Breeze
Version: 6.0.3
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: window decoration
Assignee: plasma-b...@kde.org
Reporter: mds_f...@protonmail.com
CC: kwin-bugs-n...@kde.org, uhh...@gmail.com
Target Milestone: ---
Created attachment 168164
--> https://bugs.kde.org/attachment.cgi?id=168164=edit
Trying to snap a window to the bottom right of a screen
SUMMARY
Any window using the default Breeze window decorations has an invisible 1px
border / margin drawn around it.
This prevents windows from being snapped to the right or bottom sides of the
screen and the background behind them stays visible.
The issue becomes especially noticeable if moving content (i.e. media) is
played behind the window and "shines through" the 1px margin on the bottom and
right sides.
This can also be seen in screenshots taken by Spectacle (if not including
window shadow). Every screenshot will have a 1px padding on the bottom and
right.
ADDITIONAL INFORMATION
- Does not affect fullscreen windows.
- No non-default scaling needed (100% scaling).
- Occurs on BOTH X11 and Wayland platforms.
- Oxygen and Plastik window decorations are NOT affected.
- Many third-party window decorations are NOT affected.
- Top and left edges of windows are NOT affected.
STEPS TO REPRODUCE
1. Use full KDE neon defaults / Use Breeze window decorations on a different OS
2a. Try to snap a window to the right side or the bottom of the screen
OR
2b. Try to snap a windows right or bottom edge to another window
OBSERVED RESULT
- The background behind the window will be visible around the window ("shines"
through).
- The window does not properly snap to other windows or screen edges.
EXPECTED RESULT
The window should properly snap to other windows or screen edges, without any
awkward margins.
SOFTWARE/OS VERSIONS
Linux: KDE neon Testing 20240402
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.3
The issue occurs within the first 15 minutes on KDE neon. I just started the VM
and tried to snap the Welcome Center to the side to reproduce it.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 465489] Selection Mode still gets triggered by Space, even after reassigning the shortcut
https://bugs.kde.org/show_bug.cgi?id=465489 mydarkstar changed: What|Removed |Added Summary|Can no longer unassign |Selection Mode still gets |"space" from activating |triggered by Space, even |selection mode |after reassigning the ||shortcut -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Can no longer unassign "space" from activating selection mode
https://bugs.kde.org/show_bug.cgi?id=465489 --- Comment #6 from mydarkstar --- Created attachment 156585 --> https://bugs.kde.org/attachment.cgi?id=156585=edit Video showing the expected behavior, as on v22.12.1 (45s) I have attached a screen recording of Dolphin version 22.12.1, with the reassigned shortcut fully working as expected. In version 22.12.2, the shortcut can still be reassigned, but pressing Space will still trigger it regardless, as seen in my video in the previous comment. This new video first demonstrates: 1. Selection Mode gets triggered by pressing Space (expected behavior) 2. Selection Mode does not get triggered by pressing A (expected behavior) Then, the shortcut for the Selection Mode gets changed from the default (Space) to "A". The screen recording then demonstrates: 3. Selection Mode does not get triggered by pressing Space anymore (expected behavior) 4. Selection Mode now instead gets triggered by pressing A (expected behavior) I feel like Felix' comment on this having to be newly implemented is a misunderstanding. In the previous version, the shortcut reassignment seems to work perfectly fine, and I have not encountered any bugs with it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Can no longer unassign "space" from activating selection mode
https://bugs.kde.org/show_bug.cgi?id=465489 --- Comment #5 from mydarkstar --- Thank you, Nate. As my bug report has been closed in favor of this one, please do check out the information I documented there on this regression as well! I think the following video I had linked shows the regression very well: https://bugs.kde.org/attachment.cgi?id=156548 > This screen recording first demonstrates: > 1. Selection Mode gets triggered by pressing Space (expected behavior) > 2. Selection Mode does not get triggered by pressing A (expected behavior) > > Then, the shortcut for the Selection Mode gets changed FROM the default TO > "A". > > The screen recording then demonstrates: > 3. Selection mode now gets triggered by pressing A (expected behavior) > 4. Selection mode STILL gets triggered by pressing Space (bug!) I can reproduce that on Dolphin 22.12.1, this still works fully as expected. I hope this information is helpful, as there seems to be a misunderstanding in this report. Reassigning the shortcut was indeed a feature in Dolphin 22.12.0 and 22.12.1, which worked reliably in those versions, but is now buggy in version 22.12.2, unless I'm the one misunderstanding something. Thank you for the hard work on this new feature! Especially now that Linux tablets are getting more popular, I'm sure Selection Mode will be very helpful to many! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 mydarkstar changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from mydarkstar --- I'm marking this bug as resolved for now. Feel free to reopen or create a new report, should this issue ever occur again! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444712] dolphin sometime opens off monitor
https://bugs.kde.org/show_bug.cgi?id=444712 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #5 from mydarkstar --- Hi Rajinder, Plasma 5.27 just landed with a huge multi-monitor overhaul (https://kde.org/et/announcements/plasma/5/5.27.0/). I've noticed that this also affects Dolphin's remembering of its last position and size. Does the update fix this issue for you? A lot of multi-monitor issues were addressed with this overhaul. Hoping for better results now! :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451774] Selecting remote protocol does not properly auto-fill "//"
https://bugs.kde.org/show_bug.cgi?id=451774 mydarkstar changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451774] Selecting remote protocol does not properly auto-fill "//"
https://bugs.kde.org/show_bug.cgi?id=451774 mydarkstar changed: What|Removed |Added Summary|Incorrect protocol |Selecting remote protocol |templates in the address|does not properly auto-fill |bar.|"//" Version|21.12.1 |22.12.2 Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 451774] Incorrect protocol templates in the address bar.
https://bugs.kde.org/show_bug.cgi?id=451774 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #1 from mydarkstar --- Created attachment 156549 --> https://bugs.kde.org/attachment.cgi?id=156549=edit Video demonstrating the issue (35s) I can reproduce this issue on the latest release of KDE neon Testing. If I select a remote protocol on Dolphin's Network page, it only fills in "ftp:" without the "//" at the end. Typing a hostname directly after this results in an error, as the "//" are missing. The user has to type these manually, but they seem to be required every time. Even with the username and port, the URL would look like this: `ftp://username@hostname:port/` I suppose improving this would be a nicety, but I wouldn't consider it a bug per se. In the meantime, I can recommend the "Add Network Folder" button and wizard. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441515] "Open Terminal here" does not work
https://bugs.kde.org/show_bug.cgi?id=441515 mydarkstar changed: What|Removed |Added Summary|Can not open terminal |"Open Terminal here" does ||not work -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441515] Can not open terminal
https://bugs.kde.org/show_bug.cgi?id=441515 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from mydarkstar --- # Translation of the issue into English: STEPS TO REPRODUCE 1. Right-click 2. Click to open the terminal OBSERVED RESULT There is no response EXPECTED RESULT Open the terminal from the current directory as the root directory # Concerning the issue: I cannot reproduce this bug report in any of my systems or a KDE neon VM. Nor have I seen any similar reports about an issue like this. Could you please verify whether this is still an issue for you? If so, please provide us with the Linux distribution you are using and the versions of KDE Plasma, etc. It may be that you don't have Konsole installed. Please make sure that it is installed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466163] Selection Mode "Space" shortcut cannot be removed / changed anymore
https://bugs.kde.org/show_bug.cgi?id=466163 --- Comment #1 from mydarkstar --- Created attachment 156548 --> https://bugs.kde.org/attachment.cgi?id=156548=edit Video demonstrating the issue (35s) This screen recording first demonstrates: 1. Selection Mode gets triggered by pressing Space (expected behavior) 2. Selection Mode does not get triggered by pressing A (expected behavior) Then, the shortcut for the Selection Mode gets changed from the default to "A". The screen recording then demonstrates: 3. Selection mode now gets triggered by pressing A (expected behavior) 4. Selection mode STILL gets triggered by pressing Space (bug!) This bug report concerns the demonstrated point 4. I think in this recording, the issue is visualized quite well! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466163] Selection Mode "Space" shortcut cannot be removed / changed anymore
https://bugs.kde.org/show_bug.cgi?id=466163 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466163] New: Selection Mode "Space" shortcut cannot be removed / changed anymore
https://bugs.kde.org/show_bug.cgi?id=466163 Bug ID: 466163 Summary: Selection Mode "Space" shortcut cannot be removed / changed anymore Classification: Applications Product: dolphin Version: 22.12.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Selection Mode Assignee: kfm-de...@kde.org Reporter: mds_f...@protonmail.com CC: felixer...@kde.org Target Milestone: --- Created attachment 156546 --> https://bugs.kde.org/attachment.cgi?id=156546=edit Screenshot of shortcut concerning Dolphin Selection Mode # SUMMARY When Selection Mode was introduced, it was possible to remove or change the "Space" shortcut that triggers it and restore the previous behavior when Space is pressed. The shortcut is called "Select Files and Folders". The default shortcut for it was "Space". Since version 22.12.2, changing this shortcut does not have the expected effect anymore. Even if the shortcut is changed to another key, it is still being triggered by Space, along with the newly set key. # EXAMPLE USAGE I heavily use Dolphin using the keyboard, and a lot of the time, I open a specific folder with e.g. a single file in it, which I would like to e.g. rename. Previously, I would open the folder by pressing Enter, then select the file using Space, then press F2 to start renaming it. Pressing Space now instead triggers the Selection Mode, but it does never actually select the file. Pressing Space again, while Selection Mode is open, does not select the file either, but closes the Selection Mode again. I have not found an efficient replacement to select a single file in a folder using the keyboard, with Selection Mode turning on when Space is pressed. The only workaround I've found is using arrow keys, which are not very handy to use. My solution to this problem, ever since version 22.12, was to just remove the Space shortcut, that triggers Selection Mode. However, with version 22.12.2, removing the Space shortcut is not possible anymore. # ATTACHMENT See the attached screenshot for the previous defaults. Setting the bottom shortcut "Select Files and Folders" to "None" previously prevented Selection Mode from being triggered, but stopped having any effect with version 22.12.2. If I set the shortcut to another key, like "A", the key will trigger it, but Space will also STILL trigger it. # STEPS TO REPRODUCE 1. Open "Configure Keyboard Shortcuts" in Dolphin 2. Expand the shortcut "Select Files and Folders" 3. Set shortcut to Custom → None (or another key) 4. Save settings and press Space in the file view # OBSERVED RESULT Selection Mode is triggered, even though the shortcut was disabled or changed to another key. # EXPECTED RESULT The file being selected normally, as pre version 22.12. # SOFTWARE/OS VERSIONS Operating System: KDE neon Testing, with newest updates installed as of 2023-02-20. KDE Plasma Version: 5.26 / 5.27.0 (Testing) KDE Frameworks Version: 5.103.0 / 5.104.0 Qt Version: 5.15.8 Graphics Platform: X11 Dolphin Version: 22.12.2 # ADDITIONAL INFORMATION Bug report concerning a similar topic: #466050 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466157] New shortcut for tiling windows conflicts with Mouse Mark
https://bugs.kde.org/show_bug.cgi?id=466157 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466157] New: New shortcut for tiling windows conflicts with Mouse Mark
https://bugs.kde.org/show_bug.cgi?id=466157 Bug ID: 466157 Summary: New shortcut for tiling windows conflicts with Mouse Mark Classification: Plasma Product: kwin Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: mds_f...@protonmail.com Target Milestone: --- Created attachment 156543 --> https://bugs.kde.org/attachment.cgi?id=156543=edit Demonstration of the issue (28s) # SUMMARY KDE Plasma 5.27 introduced a new way of tiling windows in pre-defined zones, by holding down Shift, while dragging the window, optionally by holding down META to drag them from anywhere. The "Mouse Mark" Kwin effect uses the same key combination, META + Shift. If users have this effect enabled, it will start drawing lines on-screen, when windows are bring tiled. Please see the attached screen recording. The key combination to draw using Mouse Mark is currently not configurable, as discussed in #448945. My suggestion would be to change the key combination used for Mouse Mark. Changing it to Ctrl + META seems like a reasonable and easy to adjust to change, that does not seem to be used by anything else yet. # STEPS TO REPRODUCE 1. Go to System Settings → Workspace Behavior → Desktop Effects 2. Enable "Mouse Mark" 3. Start dragging a window by clicking anywhere in the frame while holding down META 4. Attempt to use the new tiling feature by now also holding down Shift # OBSERVED RESULT Mouse Mark will start drawing lines on-screen, while the window is being dragged. # EXPECTED RESULT The shortcuts should not overlap so closely, so Mouse Mark is not accidentally triggered. # SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Testing, with newest updates installed as of 2023-02-20. KDE Plasma Version: 5.27.0 (Testing) KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: X11 # ADDITIONAL INFORMATION Tested and reproduced on the newest KDE neon Testing system. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 407577] Passwords containing certain non-ASCII characters not communicated correctly
https://bugs.kde.org/show_bug.cgi?id=407577 mydarkstar changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from mydarkstar --- Thank you for confirming the issue, Daniel! As other people can reproduce the issue, I'll be setting this bug report to confirmed now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 --- Comment #8 from mydarkstar --- On that note, I can also say that this issue does not affect 5.21.X versions. The issue was introduced with the release of 5.22.0. Between those two versions, the most significant change in Klipper seems to be the implementation of QScreen in `klipperpopup.cpp`. I assume that __could__ be the source of trouble, since this crash seems to happen on setups with two screens. The change occurred in 6befb657dd9fd811160e0369913d769cfff7f02d. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438277] Plasma crashes in PopupProxy::parent() after the opening of the Klipper (Meta+V)
https://bugs.kde.org/show_bug.cgi?id=438277 mydarkstar changed: What|Removed |Added CC||mds_f...@protonmail.com --- Comment #5 from mydarkstar --- I can reproduce this issue too. My left screen is smaller than my right one and aligned further down. I can confirm Sebastian's workaround to work as well. And replacing step one with "Align both screens at the top" does the job also. (In reply to Sebastian E. from comment #3 and comment #4) -- You are receiving this mail because: You are watching all bug changes.
