[plasma-mobile] [Bug 466093] Plasma mobile freezes from time to time
https://bugs.kde.org/show_bug.cgi?id=466093
--- Comment #7 from Marco Mattiolo ---
Hi Devin!
This issue is frustrating, haven't found a way to trigger it reliably so far...
It's not limited to the splash screen and it does not freeze on every splash
screen, but it just happened again and I'm able to add some context. The
session was running without issues, no problem in opening/closing and switching
between apps, then I had telegram-desktop, kwalletmanager and nheko open, I
closed nheko, pressed the square in the bottom bar and plasma froze, screen
lose contrast (gray scale instead of colour) and never came back, I had to
press power button for 3 seconds and log out. Clock was at 21.33, that is
useful to check log:
feb 20 21:33:20 mobian plasmashell[2704]: [2023-02-20 21:33:20.930] [qml]
[warning] QObject::connect(TimelineModel, TimelineFilter): invalid nullptr
parameter (:0, )
feb 20 21:33:20 mobian plasmashell[2704]: [2023-02-20 21:33:20.930] [qml]
[warning] QObject::connect(TimelineModel, TimelineFilter): invalid nullptr
parameter (:0, )
feb 20 21:33:20 mobian plasmashell[2704]: [2023-02-20 21:33:20.930] [qml]
[warning] QObject::connect(QAbstractItemModel, TimelineFilter): invalid nullptr
parameter (:0, )
feb 20 21:33:22 mobian plasmashell[2704]: [2023-02-20 21:33:22.581] [net]
[error] sync error: (parser: [json.exception.parse_error.101] parse error at
line 1, column 1: syntax error while parsing value - unexpected end of input;
expected '[', '{', or a literal: )
feb 20 21:33:23 mobian systemd[816]:
app-nheko-e8abf70b8e144034bd8bfdd4ea49084a.scope: Consumed 21.247s CPU time.
feb 20 21:33:40 mobian dbus-daemon[458]: [system] Activating service
name='org.kde.powerdevil.backlighthelper' requested by ':1.72' (uid=1000
pid=1377 comm="/usr/lib/aarch64-linux-gnu/libexec/org_kde_powerde") (using
servicehelper)
feb 20 21:33:40 mobian dbus-daemon[458]: [system] Successfully activated
service 'org.kde.powerdevil.backlighthelper'
feb 20 21:33:45 mobian systemd-logind[473]: Power key pressed short.
feb 20 21:33:46 mobian dbus-daemon[865]: [session uid=1000 pid=865] Activating
service name='org.kde.LogoutPrompt' requested by ':1.24' (uid=1000 pid=995
comm="/usr/bin/ksmserver")
feb 20 21:33:47 mobian dbus-daemon[865]: [session uid=1000 pid=865]
Successfully activated service 'org.kde.LogoutPrompt'
Another question: in the logs I often find
plasmashell[2080]: QBuffer::seek: Invalid pos: -118765761
a lot of those lines, are those relevant?
About the splashscreen commit, IIRC 5.27.1 should be tagged tomorrow, then I
will directly test the package to be uploaded to Debian in a couple of days,
thank you for pointing it out!
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 466152] Default filters are hiding several developer-relevant configurations
https://bugs.kde.org/show_bug.cgi?id=466152 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/444 -- 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.
[systemsettings] [Bug 466073] Errors when opening Keyboard KCM
https://bugs.kde.org/show_bug.cgi?id=466073 Andrey changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Andrey --- I opened an issue upstream: https://invent.kde.org/frameworks/kconfigwidgets/-/issues/6 Let's track it there as it has nothing to do with the KCMs it seems. Relevant line is here: https://invent.kde.org/frameworks/kconfigwidgets/-/blob/master/src/kconfigdialogmanager.cpp#L266 These should be probably closed, too? https://bugs.kde.org/show_bug.cgi?id=466072 https://bugs.kde.org/show_bug.cgi?id=466073 https://bugs.kde.org/show_bug.cgi?id=466074 -- 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.
[digikam] [Bug 466146] XMP metadata is not written into jxl files
https://bugs.kde.org/show_bug.cgi?id=466146 --- Comment #10 from mahikeulbody --- I read your patch and I see that digikam wrote also iptc args. Exiftool don't support iptc for jxl format so may be it was the cause of the problem. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 463577] Exiv2 alters unrelated DJI Exif metadata when editing tags.
https://bugs.kde.org/show_bug.cgi?id=463577 --- Comment #6 from Maik Qualmann --- The prerequisite for not changing the Makernotes is the activated ExifTool support in digiKam-8.0.0. Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449709] Print Color Mode: not possible to print in black-white
https://bugs.kde.org/show_bug.cgi?id=449709 Guillaume Zin changed: What|Removed |Added CC||guillaume@gmail.com --- Comment #4 from Guillaume Zin --- Created attachment 156547 --> https://bugs.kde.org/attachment.cgi?id=156547=edit Print to PDF as grayscale I confirm this bug for: - Okular 22.08.3 - KDE Frameworks 5.102.0 - Qt 5.15.6 When "Mono" printing is selected via the "Properties" printer configuration dialog, output is in color anyways (Brother printer). The bug is present if you print to a PDF file too and you select grayscale in "Options", cf. OkularPrintPdfGrayscale.png attached file. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 463577] Exiv2 alters unrelated DJI Exif metadata when editing tags.
https://bugs.kde.org/show_bug.cgi?id=463577 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.0.0 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 466144] Possible typo
https://bugs.kde.org/show_bug.cgi?id=466144 Tobias Fella changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kinfocenter/commit/65f13 |ma/kinfocenter/commit/e03be |f4f4357cca5b09798da4373179e |d8561dbfc4ba6994628ae9baf8b |6afcb0c7|be00c491 --- Comment #3 from Tobias Fella --- Git commit e03bed8561dbfc4ba6994628ae9baf8bbe00c491 by Tobias Fella. Committed on 20/02/2023 at 16:56. Pushed by tfella into branch 'Plasma/5.27'. Fix typo in string (cherry picked from commit 65f13f4f4357cca5b09798da4373179e6afcb0c7) M +1-1src/CommandOutputContext.cpp https://invent.kde.org/plasma/kinfocenter/commit/e03bed8561dbfc4ba6994628ae9baf8bbe00c491 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466146] XMP metadata is not written into jxl files
https://bugs.kde.org/show_bug.cgi?id=466146 --- Comment #9 from mahikeulbody --- I don't know if both issues are related but I created an issue about Exiftool : https://exiftool.org/forum/index.php?topic=14515.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 466161] baloo_file_extr crashing randomly, sometimes with garbled Kcrash files
https://bugs.kde.org/show_bug.cgi?id=466161 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465533] Tag's aren't being removed from images.
https://bugs.kde.org/show_bug.cgi?id=465533 Maik Qualmann changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466146] XMP metadata is not written into jxl files
https://bugs.kde.org/show_bug.cgi?id=466146 --- Comment #8 from Maik Qualmann --- Git commit 75f648cac5b14b605d2091871465547c3c219f44 by Maik Qualmann. Committed on 20/02/2023 at 20:29. Pushed by mqualmann into branch 'master'. the behavior of ExifTool is not constant when writting EXV container Check for a JXL file. It may be necessary to check for another format. M +0-1NEWS M +10 -1core/libs/metadataengine/exiftool/exiftoolparser_command.cpp https://invent.kde.org/graphics/digikam/commit/75f648cac5b14b605d2091871465547c3c219f44 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 208215] Valgrind does not support Objective-C garbage collection (Obj-C GC)
https://bugs.kde.org/show_bug.cgi?id=208215 --- Comment #1 from Sean --- In the intervening 14 years, Objective-C garbage collection has been deprecated and then removed from macOS. This ticket should just be closed. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466164] New: kmenueditor crashes after saving and reediting the item.
https://bugs.kde.org/show_bug.cgi?id=466164 Bug ID: 466164 Summary: kmenueditor crashes after saving and reediting the item. Classification: Applications Product: kmenuedit Version: 5.27.0 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bradlee.sarg...@gmail.com Target Milestone: --- Application: kmenuedit (5.27.0) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 5.17.0-1026-oem x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: I entered the following into a submenu of kmenuedit: name: Emacs command: emacsclient -c --socket-name=brademacs ~/org & After saving it and exiting the menu editor, I tried clicking on the item to edit it and it fails. The crash can be reproduced every time. -- Backtrace: Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault [KCrash Handler] #4 0x7f6522e6c324 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x55dd2aa8f387 in ?? () #6 0x7f6522109108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x55dd2aa960ce in ?? () #8 0x7f65221090d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f6523010b32 in QTreeWidget::currentItemChanged(QTreeWidgetItem*, QTreeWidgetItem*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f6522109108 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f652207a6c7 in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f652207e17d in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f6522f9314e in QAbstractItemView::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f6522d5797e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f6522e05d42 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f65220d0dda in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f6522d14782 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f6522d1c3d4 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f65220d107a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f6522d1aeb7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f6522d71210 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f6522d744a5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f6522d14793 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f65220d107a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f6522607a77 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7f65225dba5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #27 0x7f651d470dee in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #28 0x7f6520697d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x7f65206ec6c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f65206953e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f652212aad8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f65220cf99b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f65220d7f34 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x55dd2aa89956 in ?? () #35 0x7f65219ead90 in __libc_start_call_main (main=main@entry=0x55dd2aa88a90, argc=argc@entry=1, argv=argv@entry=0x7ffd78758328) at ../sysdeps/nptl/libc_start_call_main.h:58 #36 0x7f65219eae40 in __libc_start_main_impl (main=0x55dd2aa88a90, argc=1, argv=0x7ffd78758328, init=, fini=, rtld_fini=, stack_end=0x7ffd78758318) at ../csu/libc-start.c:392 #37 0x55dd2aa8a265 in ?? () [Inferior 1 (process 1925280) detached] The reporter indicates this bug may be a duplicate of or related to bug 412587, bug 359588, bug 417097.
[kmail2] [Bug 344099] KMail composer changes HTML format when replying to HTML mail
https://bugs.kde.org/show_bug.cgi?id=344099 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 464972] Kmail cannot properly compose html
https://bugs.kde.org/show_bug.cgi?id=464972 --- Comment #2 from Robert Riemann --- Is this linked to or a duplicate of https://bugs.kde.org/show_bug.cgi?id=344099 ? -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 465882] Implement scroll momentum in Tokodon
https://bugs.kde.org/show_bug.cgi?id=465882 Joshua Goins changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||j...@redstrate.com --- Comment #1 from Joshua Goins --- Yeah momentum scrolling would be nice. Unfortunately on the technical side Qt is a mess in this area from what I know, but it's something I want to look into. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 Roger Noble changed: What|Removed |Added CC||rnbzi...@gmail.com --- Comment #22 from Roger Noble --- Same here with Fedora 37, 5.27.0, 5.103.0, Wayland. Desktop with Radeon RX 6700 XT graphics, None of my three displays will turn off. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 464972] Kmail cannot properly compose html
https://bugs.kde.org/show_bug.cgi?id=464972 Robert Riemann changed: What|Removed |Added CC||rob...@riemann.cc -- 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.
[digikam] [Bug 463785] Slideshow starts with black screen and digikam crashes
https://bugs.kde.org/show_bug.cgi?id=463785 Maik Qualmann changed: What|Removed |Added CC||benedekppe...@gmail.com --- Comment #2 from Maik Qualmann --- *** Bug 466156 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466156] digiKam crash on Windows 10, if you click on "Show Fullscreen" of thumbnail element, and closing this
https://bugs.kde.org/show_bug.cgi?id=466156 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 463785 *** -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 466162] New: Kalendar crashes when hitting the save button on an event that I have already made
https://bugs.kde.org/show_bug.cgi?id=466162 Bug ID: 466162 Summary: Kalendar crashes when hitting the save button on an event that I have already made Classification: Applications Product: kalendar Version: 22.12.2 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: mathma...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-zen1-1-zen x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: I open Kalendar right click the event, click edit, then click save and it crashes The crash can be reproduced every time. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x7fb812faaa3e in QTimeZone::~QTimeZone() () at /usr/lib/libQt5Core.so.5 #5 0x7fb812fa131f in QDateTime::operator=(QDateTime const&) () at /usr/lib/libQt5Core.so.5 #6 0x55c26914b47e in () #7 0x7fb8130bea71 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb813046cd1 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #9 0x7fb81306d3a6 in () at /usr/lib/libQt5Core.so.5 #10 0x7fb8130bec20 in () at /usr/lib/libQt5Core.so.5 #11 0x7fb813046cd1 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #12 0x7fb81306d3a6 in () at /usr/lib/libQt5Core.so.5 #13 0x7fb8130bec20 in () at /usr/lib/libQt5Core.so.5 #14 0x7fb813046cd1 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #15 0x7fb81306d3a6 in () at /usr/lib/libQt5Core.so.5 #16 0x7fb8130bec20 in () at /usr/lib/libQt5Core.so.5 #17 0x7fb813046cd1 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #18 0x7fb81538269b in () at /usr/lib/libKF5ItemModels.so.5 #19 0x7fb8130bea71 in () at /usr/lib/libQt5Core.so.5 #20 0x7fb813046cd1 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () at /usr/lib/libQt5Core.so.5 #21 0x7fb8156c462c in () at /usr/lib/libKF5AkonadiCore.so.5 #22 0x7fb8156a59eb in () at /usr/lib/libKF5AkonadiCore.so.5 #23 0x7fb8130bec20 in () at /usr/lib/libQt5Core.so.5 #24 0x7fb815625d6c in Akonadi::Monitor::itemChanged(Akonadi::Item const&, QSet const&) () at /usr/lib/libKF5AkonadiCore.so.5 #25 0x7fb81563a4a1 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () at /usr/lib/libKF5AkonadiCore.so.5 #26 0x7fb815634b74 in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () at /usr/lib/libKF5AkonadiCore.so.5 #27 0x7fb815633ca5 in Akonadi::MonitorPrivate::flushPipeline() () at /usr/lib/libKF5AkonadiCore.so.5 #28 0x7fb81563465e in Akonadi::MonitorPrivate::dataAvailable() () at /usr/lib/libKF5AkonadiCore.so.5 #29 0x7fb8130bea71 in () at /usr/lib/libQt5Core.so.5 #30 0x7fb8130bec20 in () at /usr/lib/libQt5Core.so.5 #31 0x7fb8149a743a in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib/libKF5CoreAddons.so.5 #32 0x7fb8149ad54c in KJob::finishJob(bool) () at /usr/lib/libKF5CoreAddons.so.5 #33 0x7fb8130b1bb0 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #34 0x7fb813d78b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #35 0x7fb81308df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #36 0x7fb81308ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #37 0x7fb8130d4e88 in () at /usr/lib/libQt5Core.so.5 #38 0x7fb81126e82b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #39 0x7fb8112c5cc9 in () at /usr/lib/libglib-2.0.so.0 #40 0x7fb81126d0e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #41 0x7fb8130d8c6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #42 0x7fb8130866ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #43 0x7fb813091219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #44 0x55c26911fee4 in () #45 0x7fb81283c790 in () at /usr/lib/libc.so.6 #46 0x7fb81283c84a in __libc_start_main () at /usr/lib/libc.so.6 #47 0x55c269120f45 in () [Inferior 1 (process 225874) detached] Reported using DrKonqi -- You are receiving this mail
[frameworks-baloo] [Bug 466161] baloo_file_extr crashing randomly, sometimes with garbled Kcrash files
https://bugs.kde.org/show_bug.cgi?id=466161 thecornish...@protonmail.com changed: What|Removed |Added CC||thecornish...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 466161] baloo_file_extr crashing randomly, sometimes with garbled Kcrash files
https://bugs.kde.org/show_bug.cgi?id=466161 thecornish...@protonmail.com changed: What|Removed |Added Summary|baloo_file_extr crashing|baloo_file_extr crashing |randomly, somethimes with |randomly, sometimes with |garbled Kcrash files|garbled Kcrash files -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466156] digiKam crash on Windows 10, if you click on "Show Fullscreen" of thumbnail element, and closing this
https://bugs.kde.org/show_bug.cgi?id=466156 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Component|Thumbs-Image|Plugin-Generic-SlideShow -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464995] Shortcut displayed inside plugins results in not enabled error
https://bugs.kde.org/show_bug.cgi?id=464995 Kurt Hindenburg changed: What|Removed |Added Latest Commit||b138d1ec7c91cd6ca7a782b9ee7 ||156089ab1def6 Status|ASSIGNED|RESOLVED Version Fixed In||23.04 Resolution|--- |FIXED --- Comment #1 from Kurt Hindenburg --- fixed in b138d1ec7c91cd6ca7a782b9ee7156089ab1def6 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465680] Fails to start due to missing library in openSUSE
https://bugs.kde.org/show_bug.cgi?id=465680 --- Comment #14 from Rafael Linux User --- (In reply to Maik Qualmann from comment #11) > The problem seems to have been found: > > https://bugzilla.suse.com/show_bug.cgi?id=1208248 > > Maik Thank you. I did a rollback to Plasma 5.26 while openSUSE fix issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 466161] New: baloo_file_extr crashing randomly, somethimes with garbled Kcrash files
https://bugs.kde.org/show_bug.cgi?id=466161 Bug ID: 466161 Summary: baloo_file_extr crashing randomly, somethimes with garbled Kcrash files Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.103.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: thecornish...@protonmail.com Target Milestone: --- SUMMARY I'm having a lot of crashes in baloo_file_extr ever since the 5.103 Framework update. The crashes aren't noticeable apart from I'm getting Kcrash files appearing in my Home directory, but not for every crash. The Kcrash files are completely garbled though, the only way to view them is using the inode of the file to open it but even the contents are garbled. Example: [KCrash] exe=0�&ɹU appname=p'%ɹU apppath=��"ɹU signal=11 pid=7464 The journal has lots of recorded crashes. Using coredumpctl gdb 7464 bt full on the above one shows the following: https://pastebin.com/s15JJCmh STEPS TO REPRODUCE 1. Use filesystem normally 2. Check the journal or coredumpctl periodically for baloo_file_extr crashes OBSERVED RESULT Sometimes garbled kCrash files appear in home directory but otherwise no visible issue. EXPECTED RESULT No Kcrash files and no recorded baloo_file_extr crashes SOFTWARE/OS VERSIONS Linux: Arch KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466094] Incorrect cursor rendering with screen scaling enabled
https://bugs.kde.org/show_bug.cgi?id=466094 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/81571203f12c |ma/kwin/commit/e2a082594a85 |3fbd8c7cb8bc6446587a43d3895 |61a7228cfe2d6cf8020fd4c85b6 |b |a --- Comment #5 from Zamundaaa --- Git commit e2a082594a8561a7228cfe2d6cf8020fd4c85b6a by Xaver Hugl. Committed on 20/02/2023 at 19:32. Pushed by zamundaaa into branch 'Plasma/5.27'. cursorsource: fix scaling with Xwayland Before this commit, the device pixel ratio of the cursor was set to ignore the Xwayland scale override, while the size of the cursor surface was scaled. This change removes the scaling of the cursor surface size, to make the cursor be no longer cut off in rendering. (cherry picked from commit 81571203f12c3fbd8c7cb8bc6446587a43d3895b) M +6-1src/cursorsource.cpp https://invent.kde.org/plasma/kwin/commit/e2a082594a8561a7228cfe2d6cf8020fd4c85b6a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 --- Comment #1 from omano --- I don't know what happened but there is no summary :\ Basically, every single Unreal Engine 3 game I start as a Steam/Proton game, starts fullscreen but with the taskbar visible over the game, BUT the game still has focus and you can interact with it. Setting Focus Stealing Prevention to NONE seems to fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] New: Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 Bug ID: 466160 Summary: Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games Classification: Plasma Product: kwin Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: om...@redorchestra2.fr Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Set Focus Stealing Prevention settings to something other than NONE 2. Start an Unreal Engine 3 game from Steam (Windows/Proton game) OBSERVED RESULT The taskbar is visible in the fullscreen game (you can play the game normally, interact with the game with no issue) EXPECTED RESULT The taskbar disappears when the fullscreen game is started SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.12 / KDE 5.26.5 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Here is the old Proton issue about it, where there is a link to the commit that supposedly fix this reoccurring issue (this was already fixed couple years ago) https://github.com/ValveSoftware/Proton/issues/3945 -- You are receiving this mail because: You are watching all bug changes.
[kturtle] [Bug 466159] New: Hard to see the entered text in Kturtle
https://bugs.kde.org/show_bug.cgi?id=466159 Bug ID: 466159 Summary: Hard to see the entered text in Kturtle Classification: Applications Product: kturtle Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: c...@kde.nl Reporter: aron...@gmail.com Target Milestone: --- Created attachment 156545 --> https://bugs.kde.org/attachment.cgi?id=156545=edit screenshot of KTurtle in dark mode Using Breeze dark, you can barely see the text you are currently entering or the previously added ones. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 461746] Unknown error when starting Konqueror
https://bugs.kde.org/show_bug.cgi?id=461746 Stefano Crocco changed: What|Removed |Added CC||stefano.cro...@alice.it --- Comment #2 from Stefano Crocco --- (In reply to Reiner Nix from comment #1) > I can confirm this behavior: when starting konqueror, it show to me "Die > Aktion lässt sich nicht ausführen" , "Ungültiges Adressformat (URL)". > However I have configured Konqueror to start with an empty page. > When entering an file URL, e.g. "/tmp", the tree is displayed but clicking > on an item does not start an action (e.g. open the folder). > > With this error, Konqueror is currently completely unusable for me. > This is a mess because Konquerer provides some productive, unique features > (e.g. tabbed mode, HTML browsing + file management) which I really use for > my daily work in the office and I am currently delaying updates to other > computers to prevent this error. > > > SOFTWARE/OS VERSIONS > Linux: Debian 12 (bookworm, Testing) > KDE Plasma Version: 5.26.90 > KDE Frameworks Version: 5.102.0 > Qt Version: 5.15.8 > Kernel-Version: 6.1.0-3-amd64 Which version of Konqueror are you using? The original report is about an old version, but since you mention Frameworks I guess it's more recent than that. Also, do you start Konqueror by clicking on the quick-launch icon in the Plasma panel? If so, have you tried running Konqueror directly from the application launcher or from KRunner (Alt+F2)? Do you get the same results? There's a bug with the quick launch icon which causes it to run the wrong component of Konqueror, but it should only affect the start page. Entering any other URL in the location bar should work correctly. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466134] Improve task progress information
https://bugs.kde.org/show_bug.cgi?id=466134 --- Comment #6 from Rafael Linux User --- You all have reason. I was looking for a bigger or visible bar, like device capacity or album capacity ones. They are clearly visible. Honestly, until you told me where it appeared, this progress line went unnoticed by me, who already have some visual problems. That's why I suggest changing the format to a bar similar to the ones mentioned above that show the percentage available on the memory card, i.e. with a fixed width and a height equal to the other percentages, showing progressively the percentage achieved. Thank you -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466094] Incorrect cursor rendering with screen scaling enabled
https://bugs.kde.org/show_bug.cgi?id=466094 Zamundaaa changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/81571203f12c ||3fbd8c7cb8bc6446587a43d3895 ||b --- Comment #4 from Zamundaaa --- Git commit 81571203f12c3fbd8c7cb8bc6446587a43d3895b by Xaver Hugl. Committed on 20/02/2023 at 18:50. Pushed by zamundaaa into branch 'master'. cursorsource: fix scaling with Xwayland Before this commit, the device pixel ratio of the cursor was set to ignore the Xwayland scale override, while the size of the cursor surface was scaled. This change removes the scaling of the cursor surface size, to make the cursor be no longer cut off in rendering. M +6-1src/cursorsource.cpp https://invent.kde.org/plasma/kwin/commit/81571203f12c3fbd8c7cb8bc6446587a43d3895b -- 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.
[plasmashell] [Bug 466158] New: Time text cropped at the top
https://bugs.kde.org/show_bug.cgi?id=466158 Bug ID: 466158 Summary: Time text cropped at the top Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: gudvinr+...@gmail.com Target Milestone: 1.0 Created attachment 156544 --> https://bugs.kde.org/attachment.cgi?id=156544=edit panel screenshot SUMMARY Time in digital clock applet is cut off at the top. Panel height is 26, screen scale is 150% Time format: "ddd, MMM d" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-zen1-1-zen (64-bit) Graphics Platform: Wayland Graphics Processor: AMD Radeon RX Vega M GL Graphics -- 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.
[kwin] [Bug 465622] regression: 8000hz mouse polling does not work properly
https://bugs.kde.org/show_bug.cgi?id=465622 --- Comment #3 from Rick Scholten --- (In reply to Vlad Zahorodnii from comment #2) > Does KWIN_DRM_NO_AMS=1 envvar make any different? I looked up setting variables and came across https://userbase.kde.org/Session_Environment_Variables I've made $HOME/.config/plasma-workspace/env/mouse.sh containing #!/bin/bash KWIN_DRM_NO_AMS=1 Rebooted and set mouse firmware to 8000hz. No change in erratic mouse behaviour. I can't stop thinking there's a flaw in my process and I wonder how I can test if that variable has been set. Could you point me in the right direction? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 --- Comment #2 from Zamundaaa --- Bug 452219 is more about NVidia GPUs specifically, but yeah it's most likely the same underlying issue. Please attach the output of drm_info (https://gitlab.freedesktop.org/emersion/drm_info), whether or not KWin falls back to CPU copy should be visible in there. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #20 from Andrew Udvare --- (In reply to Vlad Zahorodnii from comment #18) > Can you check whether the issue is reproducible in 5.27? Still happening in 5.27. I rebooted after fully updating my system to ensure there are no conflicting old still running libs. Only non-maximised windows snapped to the left side of the screen are affected. This happens for others but most notably Chrome and Telegram. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #15 from fdkde --- (In reply to fdkde from comment #14) > (In reply to Harald Sitter from comment #13) > > Interesting data points might be what dolphin reports as free space > > (Alt+Return in a folder) versus what the actual space reported on the server > > is. > > In the folder properties of my personal root directory (which is limited by > a quota of 100 GB) for example Dolphin is reporting that "0 B of 0 B free" > and that are 0 % are being used. A Windows 10 VM is reporting that the > directory has a size of 70,1 GB. When I look at the disk space bar at the > bottom right of the main window Dolphin shows 476,7 GiB as free. However I > don't think that number is accurate. Last week a colleague at work said that > smb clients only see the amount of space which is left on the system > partition of the domain controller which hosts the particular smb share. > > On shares without a per-user-quota the behavior is the same - 0 B of 0 B and > 0 % used. Addition: The data itself is not located on the domain controllers. They only provide the smb shares to the clients. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466156] New: digiKam crash on Windows 10, if you click on "Show Fullscreen" of thumbnail element, and closing this
https://bugs.kde.org/show_bug.cgi?id=466156 Bug ID: 466156 Summary: digiKam crash on Windows 10, if you click on "Show Fullscreen" of thumbnail element, and closing this Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Thumbs-Image Assignee: digikam-bugs-n...@kde.org Reporter: benedekppe...@gmail.com Target Milestone: --- Tested in Windows 10; digiKam 7.10 -- Click on "Show Fullscreen" of thumbnail element Result: Show Fullscreen on Now: -- Press Esc button Result: digiKam crash -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466112] room list broken
https://bugs.kde.org/show_bug.cgi?id=466112 Nerijus Baliūnas changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|CONFIRMED |RESOLVED --- Comment #3 from Nerijus Baliūnas --- Thank you, it worked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466155] Lines around windows popups and sometimes randomly on plasma-wayland.
https://bugs.kde.org/show_bug.cgi?id=466155 --- Comment #1 from Zsolt --- KDE Plasma Version: 5.27.0 it just did not get it on the clipboard, apologies. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464517] Discover crashes on start unless .cache/discover/ deleted
https://bugs.kde.org/show_bug.cgi?id=464517 khaleeq...@gmail.com changed: What|Removed |Added CC||khaleeq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 466146] XMP metadata is not written into jxl files
https://bugs.kde.org/show_bug.cgi?id=466146 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.0.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/9a13abe ||b5fccbde511e5d91e4543373e52 ||e0ff8c --- Comment #7 from Maik Qualmann --- Git commit 9a13abeb5fccbde511e5d91e4543373e52e0ff8c by Maik Qualmann. Committed on 20/02/2023 at 18:38. Pushed by mqualmann into branch 'master'. changed command to sync EXV container with ExifTool FIXED-IN: 8.0.0 M +3-1NEWS M +1-4core/libs/metadataengine/exiftool/exiftoolparser_command.cpp https://invent.kde.org/graphics/digikam/commit/9a13abeb5fccbde511e5d91e4543373e52e0ff8c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466155] New: Lines around windows popups and sometimes randomly on plasma-wayland.
https://bugs.kde.org/show_bug.cgi?id=466155 Bug ID: 466155 Summary: Lines around windows popups and sometimes randomly on plasma-wayland. Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vari4b...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 156542 --> https://bugs.kde.org/attachment.cgi?id=156542=edit short screenrecord with obs, because these lines are not visible on screenshots SUMMARY *** Lines around windows popups and sometimes randomly on plasma-wayland. This seems to be related to either masking/anti aliasing/shadows, as the same lines are visible on auto-hide panels. This also appears inconsistently around popups(window previews, volume change etc.) *** STEPS TO REPRODUCE 1. Use plasma wayland 2. Use scaling (some lines are still visible without scaling, but more frequent with scaling, for instance around autohide panels) OBSERVED RESULT Flickering lights appear. EXPECTED RESULT Normal rendering. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1.12-zen1-1-zen/5.27.0-1 (available in About System) KDE Plasma Version: 5.15.8 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Each of two monitors are mis-identified as the other one on login
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Version|5.26.5 |5.27.0 --- Comment #13 from Raman Gupta --- So I had high hopes for Plasma 5.27 solving this, but it looks like this is *still* an issue in 5.27. Some of my hardware is different from my prior reports, but the problem remains the same. I now have 3 different monitors -- my monitors are all the same model (Dell S2721QS), but Display Configuration shows a different serial # for all of them, so there is no particular reason why Plasma/KScreen shouldn't be able to differentiate them. I choose the screen priorities (middle monitor as highest priority). The display shifts as expected. I then logout, restart sddm, log in again and -- the left monitor has become highest priority again. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 466077] Filelight from Flatpak (Flathub) is useless
https://bugs.kde.org/show_bug.cgi?id=466077 ratijas changed: What|Removed |Added Summary|Filelight from Flatpak |Filelight from Flatpak |(Flathub) it useless |(Flathub) is useless -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466154] 599d44b5 broke asan compiling
https://bugs.kde.org/show_bug.cgi?id=466154 --- Comment #1 from Kurt Hindenburg --- (In reply to Kurt Hindenburg from comment #0) > 599d44b5bfd737d62d8ad846379a8f0babeb4cda broke asan compiling - I don't > want this broken for 22.08 > > https://invent.kde.org/utilities/konsole/-/merge_requests/778 > > /usr/bin/ld: /usr/bin/ld: DWARF error: invalid or unhandled FORM value: 0x23 > ../../lib/libkonsolecolorscheme.a(ColorSchemeEditor.cpp.o): in function > `Konsole::ColorSchemeEditor::ColorSchemeEditor(QWidget*)': > ColorSchemeEditor.cpp:(.text+0x34f5): undefined reference to > `Konsole::WindowSystemInfo::compositingActive()' > /usr/bin/ld: /usr/bin/ld: DWARF error: invalid or unhandled FORM value: 0x23 > ../../lib/libkonsolecolorscheme.a(ColorSchemeViewDelegate.cpp.o): in > function `Konsole::ColorSchemeViewDelegate::paint(QPainter*, > QStyleOptionViewItem const&, QModelIndex const&) const': > ColorSchemeViewDelegate.cpp:(.text+0xbd4): undefined reference to > `Konsole::WindowSystemInfo::compositingActive()' > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > gmake[2]: *** > [src/autotests/CMakeFiles/TerminalCharacterDecoderTest.dir/build.make:134: > bin/TerminalCharacterDecoderTest] Error 1 > gmake[1]: *** [CMakeFiles/Makefile2:2646: > src/autotests/CMakeFiles/TerminalCharacterDecoderTest.dir/all] Error 2 > gmake[1]: *** Waiting for unfinished jobs 23.04 I meant -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 450992] [Dolphin file manager] Search could use some improvements
https://bugs.kde.org/show_bug.cgi?id=450992 --- Comment #3 from K Freed --- Close this. Turns out my baloo database was corrupted. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466154] 599d44b5 broke asan compiling
https://bugs.kde.org/show_bug.cgi?id=466154 Kurt Hindenburg changed: What|Removed |Added CC||nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 466154] New: 599d44b5 broke asan compiling
https://bugs.kde.org/show_bug.cgi?id=466154 Bug ID: 466154 Summary: 599d44b5 broke asan compiling Classification: Applications Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: khindenb...@kde.org Target Milestone: --- 599d44b5bfd737d62d8ad846379a8f0babeb4cda broke asan compiling - I don't want this broken for 22.08 https://invent.kde.org/utilities/konsole/-/merge_requests/778 /usr/bin/ld: /usr/bin/ld: DWARF error: invalid or unhandled FORM value: 0x23 ../../lib/libkonsolecolorscheme.a(ColorSchemeEditor.cpp.o): in function `Konsole::ColorSchemeEditor::ColorSchemeEditor(QWidget*)': ColorSchemeEditor.cpp:(.text+0x34f5): undefined reference to `Konsole::WindowSystemInfo::compositingActive()' /usr/bin/ld: /usr/bin/ld: DWARF error: invalid or unhandled FORM value: 0x23 ../../lib/libkonsolecolorscheme.a(ColorSchemeViewDelegate.cpp.o): in function `Konsole::ColorSchemeViewDelegate::paint(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const': ColorSchemeViewDelegate.cpp:(.text+0xbd4): undefined reference to `Konsole::WindowSystemInfo::compositingActive()' clang: error: linker command failed with exit code 1 (use -v to see invocation) gmake[2]: *** [src/autotests/CMakeFiles/TerminalCharacterDecoderTest.dir/build.make:134: bin/TerminalCharacterDecoderTest] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:2646: src/autotests/CMakeFiles/TerminalCharacterDecoderTest.dir/all] Error 2 gmake[1]: *** Waiting for unfinished jobs -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 465934] Inline editing is broken
https://bugs.kde.org/show_bug.cgi?id=465934 James Graham changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from James Graham --- Fixed by https://invent.kde.org/network/neochat/-/merge_requests/803 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 461746] Unknown error when starting Konqueror
https://bugs.kde.org/show_bug.cgi?id=461746 Reiner Nix changed: What|Removed |Added Version|21.12.3 |21.12.2 CC||reiner@web.de --- Comment #1 from Reiner Nix --- I can confirm this behavior: when starting konqueror, it show to me "Die Aktion lässt sich nicht ausführen" , "Ungültiges Adressformat (URL)". However I have configured Konqueror to start with an empty page. When entering an file URL, e.g. "/tmp", the tree is displayed but clicking on an item does not start an action (e.g. open the folder). With this error, Konqueror is currently completely unusable for me. This is a mess because Konquerer provides some productive, unique features (e.g. tabbed mode, HTML browsing + file management) which I really use for my daily work in the office and I am currently delaying updates to other computers to prevent this error. SOFTWARE/OS VERSIONS Linux: Debian 12 (bookworm, Testing) KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel-Version: 6.1.0-3-amd64 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466153] New: The Edit window freezes if app is uninstalled. Include a check if available.
https://bugs.kde.org/show_bug.cgi?id=466153 Bug ID: 466153 Summary: The Edit window freezes if app is uninstalled. Include a check if available. Classification: Applications Product: kmenuedit Version: 5.27.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: amanita+kdeb...@mailbox.org Target Milestone: --- When uninstalling a Flatpak app while having its application menu properties window open, that window becomes grey and crashes quite okay. A little improvement would be to detect if the app is available, and if not, output a message "this app is not installed on your system" / "The app was uninstalled" instead. This would be like Kwrites cached texts telling you that the original file was deleted. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466043] Editing messages is broken
https://bugs.kde.org/show_bug.cgi?id=466043 James Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||james.h.graham@protonmail.c ||om --- Comment #2 from James Graham --- There is a fix that should land soon *** This bug has been marked as a duplicate of bug 465934 *** -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 465934] Inline editing is broken
https://bugs.kde.org/show_bug.cgi?id=465934 James Graham changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from James Graham --- *** Bug 466043 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 466112] room list broken
https://bugs.kde.org/show_bug.cgi?id=466112 James Graham changed: What|Removed |Added CC||james.h.graham@protonmail.c ||om Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from James Graham --- This is a known issue if you resize the room list it goes away and never returns i.e. it's a one time thing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466094] Incorrect cursor rendering with screen scaling enabled
https://bugs.kde.org/show_bug.cgi?id=466094 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/3642 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 463932] Add upper limit to text size
https://bugs.kde.org/show_bug.cgi?id=463932 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/neochat/-/merge_requests/808 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466152] Default filters are hiding several developer-relevant configurations
https://bugs.kde.org/show_bug.cgi?id=466152 Alex Lowe changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |len...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 466152] New: Default filters are hiding several developer-relevant configurations
https://bugs.kde.org/show_bug.cgi?id=466152 Bug ID: 466152 Summary: Default filters are hiding several developer-relevant configurations Classification: Applications Product: kdevelop Version: 5.10.221202 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: file tree Assignee: kdevelop-bugs-n...@kde.org Reporter: len...@gmail.com Target Milestone: --- This is similar to #466044. Listing some linters whose configuration files are hidden by default that should probably be unhidden: * Pylint (https://pylint.readthedocs.io/en/stable/user_guide/usage/run.html#command-line-options) - .pylintrc * isort (https://pycqa.github.io/isort/docs/configuration/config_files.html) - `.isort.cfg` * pydocstyle (https://www.pydocstyle.org/en/stable/usage.html#configuration-files) - .pydocstyle - .pydocstyle.ini - .pydocstylerc - .pydocstylerc.ini * yamllint (https://yamllint.readthedocs.io/en/stable/configuration.html#configuration) - .yamllint - .yamllint.yaml - .yamllint.yml * readthedocs (https://docs.readthedocs.io/en/stable/config-file/v2.html) - .readthedocs.yaml * codespell (https://github.com/codespell-project/codespell#using-a-config-file) - .codespellrc * mypy (https://mypy.readthedocs.io/en/stable/config_file.html) - .mypy.ini * clippy (https://github.com/rust-lang/rust-clippy#configure-the-behavior-of-some-lints) - .clippy.toml Of these, the following also accept unhidden files or standard project configuration files (e.g. pyproject.toml or setup.cfg for Python): * pylint (prefers pylintrc over hidden version, accepts pyproject.toml and setup.cfg) * isort (accepts pyproject.toml, setup.cfg, tox.ini and .editorconfig) * pydocstyle (accepts setup.cfg, tox.ini and pyproject.yaml) * codespell (accepts setup.cfg or pyproject.toml) * mypy (prefers unhidden mypy.ini, accepts pyproject.toml or setup.cfg) * clippy (prefers clippy.toml) The following require a file that's currently excluded: * yamllint * readthedocs -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431050] SMB error: "There is not enough space on the disk to write smb://..."
https://bugs.kde.org/show_bug.cgi?id=431050 --- Comment #14 from fdkde --- (In reply to Harald Sitter from comment #13) > Interesting data points might be what dolphin reports as free space > (Alt+Return in a folder) versus what the actual space reported on the server > is. In the folder properties of my personal root directory (which is limited by a quota of 100 GB) for example Dolphin is reporting that "0 B of 0 B free" and that are 0 % are being used. A Windows 10 VM is reporting that the directory has a size of 70,1 GB. When I look at the disk space bar at the bottom right of the main window Dolphin shows 476,7 GiB as free. However I don't think that number is accurate. Last week a colleague at work said that smb clients only see the amount of space which is left on the system partition of the domain controller which hosts the particular smb share. On shares without a per-user-quota the behavior is the same - 0 B of 0 B and 0 % used. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 465527] Video playback fails silently when video is over Matrix server's size limit
https://bugs.kde.org/show_bug.cgi?id=465527 Tobias Fella changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/neochat/commit/6d9dca7d ||a83f2a139ed2a38eb93034123e5 ||88923 Resolution|--- |FIXED --- Comment #2 from Tobias Fella --- Git commit 6d9dca7da83f2a139ed2a38eb93034123e588923 by Tobias Fella. Committed on 20/02/2023 at 17:19. Pushed by tfella into branch 'master'. Show a warning when a file is too large to download M +6-0src/controller.cpp https://invent.kde.org/network/neochat/commit/6d9dca7da83f2a139ed2a38eb93034123e588923 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465936] With tiling enabled windows sometimes get "Keep Below Others" and can't be put into zones again
https://bugs.kde.org/show_bug.cgi?id=465936 agilob changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #4 from agilob --- Everything seems to be working better now... I think this can be closed -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466036] kded5 crash after resume from blank
https://bugs.kde.org/show_bug.cgi?id=466036 coherence changed: What|Removed |Added Keywords||regression CC||niuchang...@gmail.com --- Comment #1 from coherence --- I have encountered the same issue after updating to 5.27. The steps to reproduce are also the same. Backtrace: #0 0x7fc0700a08ec in () at /usr/lib/libc.so.6 #1 0x7fc070051ea8 in raise () at /usr/lib/libc.so.6 #2 0x7fc071ce637c in KCrash::defaultCrashHandler(int) () at /usr/lib/libKF5Crash.so.5 #3 0x7fc070051f50 in () at /usr/lib/libc.so.6 #4 0x7fc05e36bcf4 in KScreen::Output::id() const () at /usr/lib/libKF5Screen.so.8 #5 0x7fc05e35e71d in KScreen::Config::setOutputPriority(QSharedPointer const&, unsigned int) () at /usr/lib/libKF5Screen.so.8 #6 0x7fc05e36826f in KScreen::SetConfigOperation::start() () at /usr/lib/libKF5Screen.so.8 #7 0x7fc0708b1bb0 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #8 0x7fc071778b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #9 0x7fc07088df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x7fc07088ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #11 0x7fc0708d4e88 in () at /usr/lib/libQt5Core.so.5 #12 0x7fc06f51682b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #13 0x7fc06f56dcc9 in () at /usr/lib/libglib-2.0.so.0 #14 0x7fc06f5150e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #15 0x7fc0708d8c6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x7fc0708866ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x7fc070891219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #18 0x559c1e9f2040 in () #19 0x7fc07003c790 in () at /usr/lib/libc.so.6 #20 0x7fc07003c84a in __libc_start_main () at /usr/lib/libc.so.6 #21 0x559c1e9f20c5 in () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466150] Window effects flash on my second screen
https://bugs.kde.org/show_bug.cgi?id=466150 Lamdarer changed: What|Removed |Added Component|multi-screen|general -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466150] Window effects flash on my second screen
https://bugs.kde.org/show_bug.cgi?id=466150 --- Comment #1 from Lamdarer --- Actually this is not just a multi monitor issue, it also happens if I have just one monitor enabled(it's just not as noticeable). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466151] New: open documents by default on single page mode, not scrolling continuous mode.
https://bugs.kde.org/show_bug.cgi?id=466151 Bug ID: 466151 Summary: open documents by default on single page mode, not scrolling continuous mode. Classification: Applications Product: okular Version: 22.12.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: petercameronba...@gmail.com Target Milestone: --- SUMMARY Wish to open documents by default on single page mode, not scrolling continuous mode. STEPS TO REPRODUCE 1. add option to change default behavior 2. throw away necessity to shortcut key combo to single page mode every time you open a document 3. enjoy okular more fully OBSERVED RESULT opening a document opens in continuous mode EXPECTED RESULT opening a document opens in single page mode SOFTWARE/OS VERSIONS Edition Windows 11 Pro Version 21H2 Installed on11/27/2021 OS build22000.1574 Experience Windows Feature Experience Pack 1000.22000.1574.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466150] Window effects flash on my second screen
https://bugs.kde.org/show_bug.cgi?id=466150 Lamdarer changed: What|Removed |Added CC||lamda...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466150] New: Window effects flash on my second screen
https://bugs.kde.org/show_bug.cgi?id=466150 Bug ID: 466150 Summary: Window effects flash on my second screen Classification: Plasma Product: kwin Version: 5.27.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: lamda...@mailbox.org Target Milestone: --- Created attachment 156541 --> https://bugs.kde.org/attachment.cgi?id=156541=edit Observed behaviour with Right-Click, on top of FireFox(Left) and on desktop(right) SUMMARY Certain Window effects/Windows flash on my second screen in addition to the screen where they are located. The Right Click Menu (or Forms, e.g. the drop down menu for severity, Platform or OS in this Bug report, file in FireFox), but also whole windows like when closing or opening any window can couse this behavior. Non Plasma submenus seem to be unaffected by this e.g. Steam's Right Click menu doesnt behave like this, but when Steam spawns new Windows e.g. Settings it also flickers on my second screen, so I assume all window effects are effected. But it doesnt happen if I just right click on the desktop itself. This also happens if I turn all desktop effects to instant. This didnt happen on 5.26. STEPS TO REPRODUCE 1. Have 2 screens 2. Do 3. on either of them 3. Spawn a window(e.g. Right Click Menu) on top of another window or Start new Program OBSERVED RESULT The Window Spawn/vanish effect flashes on my seconds screen, even if effects are set to instant(so not sure if it is really an effect).(Maybe the effect is even drawn wrongly on the screen where I spawn the window) The above does happen in most cases, but not if I just right click the desktop itself, but with basically everything else it happens. EXPECTED RESULT It shouldn't flicker on my second screen, the effect should be on only one or disabled completely(if set to instant) SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION See attached video, or ask me if you need any other info -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 465804] Floating annotation tools can get off screen when selecting a region to screenshot
https://bugs.kde.org/show_bug.cgi?id=465804 Noah Davis changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/spectacle/commit/06df8 ||d5086eae42542d8c325c513f6ac ||48e39d12 --- Comment #2 from Noah Davis --- Git commit 06df8d5086eae42542d8c325c513f6ac48e39d12 by Noah Davis, on behalf of Alessio Mattiazzi. Committed on 20/02/2023 at 17:25. Pushed by ndavis into branch 'master'. Fix toolbar getting off screen Prevent the annotations toolbar and annotations options from getting off the top or the bottom of the screen during the rectangular selection M +2-2src/Gui/ImageCaptureOverlay.qml https://invent.kde.org/graphics/spectacle/commit/06df8d5086eae42542d8c325c513f6ac48e39d12 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 459997] Ctrl+PageUp/PageDown shortcuts navigate up or down twice
https://bugs.kde.org/show_bug.cgi?id=459997 Tobias Fella changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/neochat/commit/e0f16054 ||fca51590f05c250cec60a234dad ||3ac9e --- Comment #4 from Tobias Fella --- Git commit e0f16054fca51590f05c250cec60a234dad3ac9e by Tobias Fella, on behalf of Kevin Wolf. Committed on 20/02/2023 at 17:07. Pushed by tfella into branch 'master'. Fix Ctrl+PgUp/PgDn shortcut for room switching Before this change, Ctrl+PgUp/PgDown didn't select the next room, but actually moved two rooms at once because the signal handler was called twice. I'm not entirely sure why this happens (it might be a bug in a lower layer?), but as we don't want to handle the same event elsewhere, accepting the event doesn't feel wrong and it appears to fix the issue. So let's just do that. M +2-0src/qml/Page/RoomPage.qml https://invent.kde.org/network/neochat/commit/e0f16054fca51590f05c250cec60a234dad3ac9e -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465398] Discover repeat crash on launch
https://bugs.kde.org/show_bug.cgi?id=465398 --- Comment #1 from Caroline --- Created attachment 156540 --> https://bugs.kde.org/attachment.cgi?id=156540=edit New crash information added by DrKonqi plasma-discover (5.26.1) using Qt 5.15.6 I have not changed anything on the Steam Deck, I've been using it the majority of the time on game mode. The Discover app has never worked for me, out of the box. -- Backtrace (Reduced): #6 0x7f0205e36a1b in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) () at /usr/lib/libQt5Qml.so.5 #7 0x7f0205e3752a in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) () at /usr/lib/libQt5Qml.so.5 #8 0x7f0205e39011 in QQmlTypeLoader::loadThread(QQmlDataBlob*) () at /usr/lib/libQt5Qml.so.5 [...] #11 0x7f020634fb1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f02052bbb88 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 465398] Discover repeat crash on launch
https://bugs.kde.org/show_bug.cgi?id=465398 Caroline changed: What|Removed |Added CC||carolinensa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464707] system settings crashed in KScreen::Config::outputs() when changing the scale slider and saving/reverting
https://bugs.kde.org/show_bug.cgi?id=464707 --- Comment #3 from NSLW --- Created attachment 156539 --> https://bugs.kde.org/attachment.cgi?id=156539=edit New crash information added by DrKonqi systemsettings (5.27.0) using Qt 5.15.8 Crash happened after failing to enable my external monitor. -- Backtrace (Reduced): #4 0x7f4054a8f8b8 in KScreen::Config::outputs (this=0x0) at /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/config.cpp:263 #5 0x7f4054afb8a2 in KCMKScreen::checkConfig (this=this@entry=0x559f0bd1c8b0) at /usr/src/debug/kscreen-5.27.0-1.fc37.x86_64/kcm/kcm.cpp:352 #6 0x7f4054afbb06 in KCMKScreen::continueNeedsSaveCheck (this=0x559f0bd1c8b0, needs=) at /usr/src/debug/kscreen-5.27.0-1.fc37.x86_64/kcm/kcm.cpp:379 #7 0x7f406d2c8134 in QObject::event (this=0x559f0bd1c8b0, e=0x559f0d726080) at kernel/qobject.cpp:1347 #8 0x7f406dfaed62 in QApplicationPrivate::notify_helper (this=, receiver=0x559f0bd1c8b0, e=0x559f0d726080) at kernel/qapplication.cpp:3640 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464707] system settings crashed in KScreen::Config::outputs() when changing the scale slider and saving/reverting
https://bugs.kde.org/show_bug.cgi?id=464707 NSLW changed: What|Removed |Added CC||lukasz.wojnilow...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465900] Strange kind of lockscreen with no indication how to leave it
https://bugs.kde.org/show_bug.cgi?id=465900 --- Comment #2 from Thomas Grauschopf --- Update: The Battery & Brightness widget is not involved. My bad. I will try to restart plasmashell the next time it happens and report on the result. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466149] New: On Xorg, Plasma's idea of the monitor configuration differs from xrandr's
https://bugs.kde.org/show_bug.cgi?id=466149 Bug ID: 466149 Summary: On Xorg, Plasma's idea of the monitor configuration differs from xrandr's Classification: Plasma Product: KScreen Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: twilightinz...@gmail.com Target Milestone: --- SUMMARY Hi there. I was initially looking into this as a problem in 5.27 where if your primary monitor is the rightmost monitor, things that rely on the primary monitor being index 0 no longer work correctly, such as the Virtual Desktops Only on Primary KWin script (https://github.com/wsdfhjxc/kwin-scripts/tree/master/virtual-desktops-only-on-primary) But I also found that Steam now starts games on the leftmost monitor as well. My rightmost monitor is primary because of how my physical spaces are arranged at home and at work. I found a related complaint on reddit (https://www.reddit.com/r/kde/comments/114sl90/steam_launches_games_on_wrong_monitor_since_527/) and there, someone mentioned that configuring the primary monitor in xrandr was a workaround for them. But then I actually checked xrandr and found that its idea of the display configuration was somehow completely incorrect. My actual display arrangement is two monitors connected via a Dell WD19S dock, laptop closed, rightmost primary. That's what Plasma shows, too. What xrandr shows is that the laptop monitor is on, the leftmost monitor, and the primary monitor. And then only one of the external monitors is shown as connected. STEPS TO REPRODUCE 1. Connect laptop to a dock with two or more external monitors, and close the lid. 2. Configure in Plasma's display configuration, and set the rightmost monitor as primary. 3. Check xrandr configuration in a terminal. OBSERVED RESULT Plasma and xrandr are in disagreement on which monitor is primary, and what the display configuration actually is. EXPECTED RESULT Plasma and xrandr show the same configuration, and applications/scripts that use the primary monitor put things in the right place. SOFTWARE/OS VERSIONS Linux: 5.19.0-32-generic KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION xrandr output: Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP-1 connected primary (normal left inverted right x axis y axis) 1920x1080240.00 + 240.00 1680x1050240.00 1400x1050240.00 1600x900 240.00 1280x1024240.00 1400x900 240.00 1280x960 240.00 1440x810 240.00 1368x768 240.00 1280x800 240.00 1152x864 240.00 1280x720 240.00 1024x768 240.00 1024x768i240.00 960x720 240.00 928x696 240.00 896x672 240.00 1024x576 240.00 960x600 240.00 832x624 240.00 960x540 240.00 800x600 240.00 840x525 240.00 864x486 240.00 700x525 240.00 800x450 240.00 640x512 240.00 700x450 240.00 640x480 240.00 720x405 240.00 720x400 240.00 684x384 240.00 640x400 240.00 576x432 240.00 640x360 240.00 640x350 240.00 512x384 240.00 512x384i 240.00 512x288 240.00 416x312 240.00 480x270 240.00 400x300 240.00 432x243 240.00 320x240 240.00 360x202 240.00 360x200 240.00 320x200 239.99 320x180 240.00 320x175 239.99 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 509mm x 286mm 1920x1080 60.00*+ 1600x900 60.00 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 DP-1-3 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DP-1-0 disconnected (normal left inverted right x axis y axis) kscreen-console output: START: Requesting Config Received config. Took 14 milliseconds Screen: maxSize: QSize(16384, 16384) minSize: QSize(320, 200) currentSize: QSize(3840, 1080) - Id: 65 Name: "eDP-1" Type: "Panel (Laptop)" Connected: true Enabled: false Priority: 0 Rotation: KScreen::Output::None Pos: QPoint(0,0) MMSize: QSize(344, 194) FollowPreferredMode: false Scale: 1 Clones: None Mode:
[plasmashell] [Bug 460771] User selection of active media player is ignored
https://bugs.kde.org/show_bug.cgi?id=460771 --- Comment #7 from Fushan Wen --- Unfortunately it's not easily fixable. There can be more than one media controller widget, so the global media shortcuts can only operate on the default media player, otherwise the logic will be confusing. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 466148] Dolphin, "Open with" dialog doesn't work
https://bugs.kde.org/show_bug.cgi?id=466148 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org, ||sit...@kde.org --- Comment #3 from Nate Graham --- Looks like we need one of the following: 1. plasma-integration should make xdg-desktop-portal and xdg-desktop-portal-kde hard dependencies 2. If xdg-desktop-portal and xdg-desktop-portal-kde aren't installed, fall back to the old dialog. I can see from the CMakeLists.txt file that we don't do #1, so perhaps the intention was to do #2 and it's not working. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 466148] Dolphin, "Open with" dialog doesn't work
https://bugs.kde.org/show_bug.cgi?id=466148 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 466144] Possible typo
https://bugs.kde.org/show_bug.cgi?id=466144 Tobias Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kinfocenter/commit/65f13 ||f4f4357cca5b09798da4373179e ||6afcb0c7 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Tobias Fella --- Git commit 65f13f4f4357cca5b09798da4373179e6afcb0c7 by Tobias Fella. Committed on 20/02/2023 at 16:46. Pushed by davidedmundson into branch 'master'. Fix typo in string M +1-1src/CommandOutputContext.cpp https://invent.kde.org/plasma/kinfocenter/commit/65f13f4f4357cca5b09798da4373179e6afcb0c7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466103] It's too easy to hide the window titlebar and frame
https://bugs.kde.org/show_bug.cgi?id=466103 --- Comment #2 from guimarcalsi...@gmail.com --- (In reply to David Edmundson from comment #1) > People use this on a transient basis - giving a presentation making a screen > cast and so on. > > A window rule would not cover this case and we would get more bug reports. I'm afraid I have to disagree, David. Most applications used for those purposes have their own fullscreen mechanism, and do not require the use of that toggle, otherwise they wouldn't be usable on other DEs or Windows. What is happening here is that there's no way of bringing the titlebar back unless you have a keyboard and know the shortcut. The toggle is completely inaccessible otherwise. Can this bug report be re-opened, at least for discussing alternative solutions? I made the suggestion of only making the option available in Window Rules, but that's only one suggestion and other people might come up with other ways of making that option more easily reversible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392376] Wayland socket buffer gets filled up and application terminates when GUI thread was blocked
https://bugs.kde.org/show_bug.cgi?id=392376 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com --- Comment #8 from Pedro V --- It's rather odd to see this issue to be known for so long while there's apparently still no fix. Somewhat ironically Krusader introduced me to this problem as doing heavy operations there like synchronizing directories and moving the cursor over the window was a guaranteed way to lose progress. Also, I find the "RESOLVED UPSTREAM" status quite amusing. Took it registering here to see that it apparently means that it's resolved as being an upstream problem which is quite unfortunate. Status display could use some improvement. Is it not feasible though to at least throw in a workaround? Upstream doesn't seem to be too interested in fixing yet, even though the buffer seems to be tiny, and expecting the other side to just "simply" keep up on a non-realtime system appears to be bad design, given that regardless of buffer size, the possibility of programs just not getting scheduled in time is always around, so not tolerating a buffer full state practically guarantees a race condition. A significantly larger buffer could already help a lot by not punishing at least a single pass of moving the cursor over busy windows so at least people aware of the issue could have an easier time avoiding the problem. Also, it seems like GNOME stopped waiting for upstream a while ago already: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2122 I believe it's a common enough issue to deserve more attention, at least I've ran into the issue often enough. It was especially bad on a laptop under heavy I/O pressure which lead to this problem quite often. Life is better with a more powerful desktop so far, and apparently Krusader stays responsive during synchronization nowadays, but currently Firefox taps out every few days aside of mystery issues which may or may not be related, and I know that with the issue being a design flaw causing a race condition, it will be never gone without a fix. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working
https://bugs.kde.org/show_bug.cgi?id=462695 Patrick Silva changed: What|Removed |Added CC||rob.d...@telus.net --- Comment #21 from Patrick Silva --- *** Bug 466147 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466147] After update to 5.27 display/monitor stays on idefinately
https://bugs.kde.org/show_bug.cgi?id=466147 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 462695 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465936] With tiling enabled windows sometimes get "Keep Below Others" and can't be put into zones again
https://bugs.kde.org/show_bug.cgi?id=465936 --- Comment #3 from agilob --- This bug doesnt make any sense. I cant find any place where this could be configured. I've never even used "keep below others" before, but now all new windows start in this configuration. I'm going to delete my whole kde/plasma config and see if that helps. That means that any configuration i have will be lost, but if I cant reproduce this later, this bug can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 466144] Possible typo
https://bugs.kde.org/show_bug.cgi?id=466144 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kinfocenter/-/merge_requests/130 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465936] With tiling enabled windows sometimes get "Keep Below Others" and can't be put into zones again
https://bugs.kde.org/show_bug.cgi?id=465936 --- Comment #2 from agilob --- I dont have any other kwin script enabled in "KWin Scripts" section of system settings, not aware of any other place where this could be. -- You are receiving this mail because: You are watching all bug changes.
