[dolphin] [Bug 470849] Completion for path in $HOME works but fails on enter
https://bugs.kde.org/show_bug.cgi?id=470849 --- Comment #2 from gudvinr+...@gmail.com --- I'd rather have it working than not to have it at all tbh. But it's better to not have it at all than having it broken. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476309] Size option with pen pressure is enabled for every brushes all of a sudden.
https://bugs.kde.org/show_bug.cgi?id=476309 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|ASSIGNED Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com CC||dimul...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Dmitry Kazakov --- Hi, acc4commissions! Thank you for your quick report! It seems like it is a regression from my yesterday's fix of bug 476076. I'll try to fix that asap. You can rollback to the yesterday's version, there is no need to resave the brushes. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 305432] It would be nice if ktorrent would support ftp webseeds
https://bugs.kde.org/show_bug.cgi?id=305432 Yaron Shahrabani changed: What|Removed |Added CC||sh.ya...@gmail.com --- Comment #1 from Yaron Shahrabani --- I can't find any http sources these days, wouldn't it be better to support https? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476309] Size option with pen pressure is enabled for every brushes all of a sudden.
https://bugs.kde.org/show_bug.cgi?id=476309 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/-/commit/d843065 ||5625b9643982352c86f69adb0f8 ||649718 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Dmitry Kazakov --- Git commit d8430655625b9643982352c86f69adb0f8649718 by Dmitry Kazakov. Committed on 30/10/2023 at 08:30. Pushed by dkazakov into branch 'krita/5.2'. Fix Size brush option to be checkable again M +1-1plugins/paintops/libpaintop/KisSizeOptionData.cpp https://invent.kde.org/graphics/krita/-/commit/d8430655625b9643982352c86f69adb0f8649718 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476309] Size option with pen pressure is enabled for every brushes all of a sudden.
https://bugs.kde.org/show_bug.cgi?id=476309 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/-/commit/d843065 |hics/krita/-/commit/0891bd3 |5625b9643982352c86f69adb0f8 |8dae789940a2cf9abdedf2d97be |649718 |f4d689 --- Comment #3 from Dmitry Kazakov --- Git commit 0891bd38dae789940a2cf9abdedf2d97bef4d689 by Dmitry Kazakov. Committed on 30/10/2023 at 08:31. Pushed by dkazakov into branch 'master'. Fix Size brush option to be checkable again M +1-1plugins/paintops/libpaintop/KisSizeOptionData.cpp https://invent.kde.org/graphics/krita/-/commit/0891bd38dae789940a2cf9abdedf2d97bef4d689 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 456200] Valgrind should not require neon (simd) on armhf
https://bugs.kde.org/show_bug.cgi?id=456200 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 472346] False positive mismatched frees
https://bugs.kde.org/show_bug.cgi?id=472346 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476309] Size option with pen pressure is enabled for every brushes all of a sudden.
https://bugs.kde.org/show_bug.cgi?id=476309 --- Comment #4 from Dmitry Kazakov --- Hi, @acc4commissions! I have pushed the fix and kicked off the builds for Windows and Linux. Please check when they are ready: https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/2029/ https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/2034/ -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476127] KMail: Accounts display "Unable to start", akonadi gives a lot of crash-reportings
https://bugs.kde.org/show_bug.cgi?id=476127 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Daniel Vrátil --- You installation is misconfigured or incomplete, Akonadi complains that it cannot connect to your window system (X11). Possibly you don't have "DISPLAY" environment set (?). > qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though > it was found. > qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though > it was found. > This application failed to start because no Qt platform plugin could be > initialized. Reinstalling the application may fix this problem. Please report the issue to your distribution. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 476201] Images
https://bugs.kde.org/show_bug.cgi?id=476201 --- Comment #11 from Thomas Vatter --- (In reply to Stefano Crocco from comment #10) > First of all, make sure that Ad Block filters are > disabled This solves the problem (Disabled the Filter-Checkbox). Thank you Stefano -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 476278] Discover fails to install libraries libvte-2.9 and libokularcore10:amd64 on intel Acer laptop with new kernel 6.2.0-35
https://bugs.kde.org/show_bug.cgi?id=476278 Lee Berry changed: What|Removed |Added Attachment #162690|0 |1 is obsolete|| --- Comment #3 from Lee Berry --- Created attachment 162719 --> https://bugs.kde.org/attachment.cgi?id=162719&action=edit Discover 2nd pass work-around fixes missing libraries. Work around: Rerun Discover-update and apt-get update. Missing library files were installed on second pass. Fail-over was undetermined. Possible a TCP connection fault, however off-line updates failed to install and are still in log file. Some very odd grub-update maneuvers happening here. System reverts to old kernel 5.19 and wont run 6.2 unknown cause. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] New: The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 Bug ID: 476316 Summary: The drop-down menu located at the bottom left in digiKam on-line documentation does not work Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: digikam-bugs-n...@kde.org Reporter: jp.bouch...@gmail.com Target Milestone: --- Created attachment 162720 --> https://bugs.kde.org/attachment.cgi?id=162720&action=edit Screen copies in a pdf file Hello everyone, after 10 months of resuming the translations of the digiKam online documentation in another environment, I noticed a strange behavior in the online help which prevented me from understanding that all the translations in French was apparently completed. If you wish to change the language, by default the language presented (despite the choice of language configuration in digiKam) is English. If you want to have the online documentation in French, and if you click on a language option in the drop-down menu located at the bottom left it does not work (?), but surprisingly if you switch back to English a popup appears at the top right of the screen, with the English and French (?) options and if you choose French, after a few seconds the text is correctly translated into French and without looking everywhere, it seems working throughout the documentation, it's just wonderful! Congratulations to the translation teams, but still a little surprising, because you actually have to not use the drop-down menu (?) but the pop-up presented... You will find attached some screenshots to illustrate my Remarks. Despite this inconvenience, congratulations to all, and my greetings to Gilles Caullier, Jean-Pierre Boucher STEPS TO REPRODUCE 1. Manuel utilisateur en ligne 2. Click on French in drop-down menu located at the bottom left 3. OBSERVED RESULT the documentation remains in English EXPECTED RESULT documentation version SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION it works with the proposed pop-up, with a latency time -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475491] When changing the "Transfer from" of a transaction a Deposit is changed into a Payment.
https://bugs.kde.org/show_bug.cgi?id=475491 --- Comment #8 from John Zoetebier --- Have repeated the same test on Windows 10 KMyMoney 5.1.3 Same result: transfer from is changed to transfer to after changing transfer from. For example change Computer Equipment to Home Content. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475491] When changing the "Transfer from" of a transaction a Deposit is changed into a Payment.
https://bugs.kde.org/show_bug.cgi?id=475491 --- Comment #9 from John Zoetebier --- Created attachment 162721 --> https://bugs.kde.org/attachment.cgi?id=162721&action=edit Windows 10 KMyMoney 5.1.3 About dialog -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475491] When changing the "Transfer from" of a transaction a Deposit is changed into a Payment.
https://bugs.kde.org/show_bug.cgi?id=475491 --- Comment #10 from John Zoetebier --- Created attachment 162722 --> https://bugs.kde.org/attachment.cgi?id=162722&action=edit Windows 10 KMyMoney 5.1.3 Transfer From Windows 10 KMyMoney 5.1.3 Transfer From transaction -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475491] When changing the "Transfer from" of a transaction a Deposit is changed into a Payment.
https://bugs.kde.org/show_bug.cgi?id=475491 --- Comment #11 from John Zoetebier --- Created attachment 162723 --> https://bugs.kde.org/attachment.cgi?id=162723&action=edit Windows 10 KMyMoney 5.1.3 Transfer To Windows 10 KMyMoney 5.1.3 Transfer To transaction. After changing the value of Transfer From field from Computer Equipment to Home Contents the transaction type is change to "Transfer To" -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 475491] When changing the "Transfer from" of a transaction a Deposit is changed into a Payment.
https://bugs.kde.org/show_bug.cgi?id=475491 John Zoetebier changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 from John Zoetebier --- Have tested this bug on 3 different computers with KMyMoney 5.1.3. All 3 computers same bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version|8.1.0 |8.2.0 --- Comment #1 from caulier.gil...@gmail.com --- Hi, which web browser did you use ? Here using Windows 10 22H2 : - Firefox 119 => ok - Chrome 118 => ok - Edge 117 => ok Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476300] Brush outline not fully rendered on cursor movement
https://bugs.kde.org/show_bug.cgi?id=476300 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #2 from Dmitry Kazakov --- Okay, the problem happens due to a really complicated reason. The point is that the canvas updates are compressed twice: first by Krita itself (in KisCanvas2), and then by Qt (in QPaintEvent). And the problem happens when the brush outline gets updated while Qt-level compression happens. Which means that the update comes with the old clip rect, but the outline is already updated to the new one. I wonder how we could fix or workaround that... -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 475982] pass signals to debugee
https://bugs.kde.org/show_bug.cgi?id=475982 Milian Wolff changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #3 from Milian Wolff --- ah, so: ``` $ heaptrack sleep 1000 & [1] 8817 heaptrack output will be written to "/tmp/heaptrack.sleep.8817.zst" starting application, this might take some time... NOTE: heaptrack detected DEBUGINFOD_URLS but will disable it to prevent unintended network delays during recording If you really want to use DEBUGINFOD, export HEAPTRACK_ENABLE_DEBUGINFOD=1 $ kill -SIGTERM 8817 ``` -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476317] New: after install 2261 my animation slice up on 5.3
https://bugs.kde.org/show_bug.cgi?id=476317 Bug ID: 476317 Summary: after install 2261 my animation slice up on 5.3 Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: harry...@gmail.com 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION After install version 2261 my animation move up per layer -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476318] New: Quick "share to device" context menu item disappeared
https://bugs.kde.org/show_bug.cgi?id=476318 Bug ID: 476318 Summary: Quick "share to device" context menu item disappeared Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Firefox Assignee: k...@privat.broulik.de Reporter: sephiroth...@hotmail.it Target Milestone: --- SUMMARY The extension used to offer menu items that allowed you to share directly to a device, without having to first click on "share" and then select the device from a popup. This menu item also appeared when you right clicked on tabs. It appears that this feature no longer works, possibly due to changes in Firefox. I have briefly tested this in Vivaldi as well and it's not there either, but as I have never used the integration with that browser I do not know if this is normal. STEPS TO REPRODUCE 1. Right click on a link or a tab OBSERVED RESULT There no longer is a "share to device" menu item. EXPECTED RESULT There is a "share to device" menu item. SOFTWARE/OS VERSIONS Linux: KDE neon KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Using Firefox 119. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476318] Quick "Open on device" context menu item disappeared
https://bugs.kde.org/show_bug.cgi?id=476318 Riccardo Robecchi changed: What|Removed |Added Summary|Quick "share to device" |Quick "Open on device" |context menu item |context menu item |disappeared |disappeared --- Comment #1 from Riccardo Robecchi --- Sorry, I remembered incorrectly. The right wording is "open on device". It is shown in this screenshot from the extension's own page on the Firefox extension store: https://addons.mozilla.org/user-media/previews/full/202/202549.png?modified=1622132803 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476317] after install 2261 my animation slice up on 5.3
https://bugs.kde.org/show_bug.cgi?id=476317 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #1 from Dmitry Kazakov --- That is the same report as on KA: https://krita-artists.org/t/need-testing-animated-transformation-masks-rewritten/76229/13 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 476318] Quick "Open on device" context menu item disappeared
https://bugs.kde.org/show_bug.cgi?id=476318 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 475004 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 475004] Tab Context Menu (Open on device) missing
https://bugs.kde.org/show_bug.cgi?id=475004 Kai Uwe Broulik changed: What|Removed |Added CC||sephiroth...@hotmail.it --- Comment #2 from Kai Uwe Broulik --- *** Bug 476318 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 blackspar...@gmail.com changed: What|Removed |Added CC||blackspar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #2 from Jean-Pierre Boucher --- Windows 10 22H2 Jean-Pierre Boucher Le lun. 30 oct. 2023 à 09:21, a écrit : > https://bugs.kde.org/show_bug.cgi?id=476316 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > Version|8.1.0 |8.2.0 > > --- Comment #1 from caulier.gil...@gmail.com --- > Hi, > > which web browser did you use ? > > Here using Windows 10 22H2 : > > - Firefox 119 => ok > - Chrome 118 => ok > - Edge 117 => ok > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391154] Show LDAP users in the list
https://bugs.kde.org/show_bug.cgi?id=391154 Tomàs Deltell changed: What|Removed |Added CC||tomasdelt...@gmx.es --- Comment #1 from Tomàs Deltell --- Same here Fedora 38 Plasma 5.27.8 KDE frameworks 5.110.0 Qt 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454871] (SDDM) Login screen doesn't save rotation of screen
https://bugs.kde.org/show_bug.cgi?id=454871 spamless.9v...@simplelogin.com changed: What|Removed |Added CC||spamless.9v5xj@simplelogin. ||com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #3 from Maik Qualmann --- I suspect that the cause is the redirection to a mirror server, depending on which country you are in. I can also reproduce it here in Germany, no French, it stays in English. Other languages, Italian or Spanish also work. German also remains in English, but I don't know if there is a German translation yet. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476300] Brush outline not fully rendered on cursor movement
https://bugs.kde.org/show_bug.cgi?id=476300 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/-/commit/6fe21bf ||863bef481076c1bb560132be28c ||7c0990 --- Comment #3 from Dmitry Kazakov --- Git commit 6fe21bf863bef481076c1bb560132be28c7c0990 by Dmitry Kazakov. Committed on 30/10/2023 at 10:20. Pushed by dkazakov into branch 'krita/5.2'. Add update-ahead feature to outline updates Due to a compression for widget updates in Krita and Qt, the brush outline may change while the updates are being passed through the pipeline. We can either pass the outline alongside the update itself (which is a bit complicated) or just do a simple update-ahead. This patch implements the latter approach. It just calculated an approximation of the next outline position and extends the update rect to that. M +41 -1libs/ui/tool/kis_tool_paint.cc https://invent.kde.org/graphics/krita/-/commit/6fe21bf863bef481076c1bb560132be28c7c0990 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476300] Brush outline not fully rendered on cursor movement
https://bugs.kde.org/show_bug.cgi?id=476300 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/-/commit/6fe21bf |hics/krita/-/commit/4bbb383 |863bef481076c1bb560132be28c |c9c3944e208cb78b6347eacea29 |7c0990 |6e32ce --- Comment #4 from Dmitry Kazakov --- Git commit 4bbb383c9c3944e208cb78b6347eacea296e32ce by Dmitry Kazakov. Committed on 30/10/2023 at 10:20. Pushed by dkazakov into branch 'master'. Add update-ahead feature to outline updates Due to a compression for widget updates in Krita and Qt, the brush outline may change while the updates are being passed through the pipeline. We can either pass the outline alongside the update itself (which is a bit complicated) or just do a simple update-ahead. This patch implements the latter approach. It just calculated an approximation of the next outline position and extends the update rect to that. M +41 -1libs/ui/tool/kis_tool_paint.cc https://invent.kde.org/graphics/krita/-/commit/4bbb383c9c3944e208cb78b6347eacea296e32ce -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476300] Brush outline not fully rendered on cursor movement
https://bugs.kde.org/show_bug.cgi?id=476300 --- Comment #5 from Dmitry Kazakov --- Hi, Lynx3d and Tomtomtom! Could you please test an updated version of Krita with my fix? https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/2035/ My fix will not fully fix the tearing. I can still see some tearing when moving the cursor in random directions, but it still makes outline look much better in less quick movements. Is this fix enough for the problem? Or I should investigate further into a more complicated approach? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476319] New: Okular crashes when trying to edit form fields
https://bugs.kde.org/show_bug.cgi?id=476319 Bug ID: 476319 Summary: Okular crashes when trying to edit form fields Classification: Applications Product: okular Version: 23.08.1 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: xeng...@mail.ru Target Milestone: --- Application: okular (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.5.9-dirty x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Open document with forms Click on any field Reproducable crash The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7fdfec36109c in GfxResources::doLookupFont(char const*) const () from /lib/x86_64-linux-gnu/libpoppler.so.126 #5 0x7fdfec3611ad in GfxResources::lookupFont(char const*) () from /lib/x86_64-linux-gnu/libpoppler.so.126 #6 0x7fdfec346f28 in Form::ensureFontsForAllCharacters(GooString const*, std::__cxx11::basic_string, std::allocator > const&, GfxResources*) () from /lib/x86_64-linux-gnu/libpoppler.so.126 #7 0x7fdfec347576 in ?? () from /lib/x86_64-linux-gnu/libpoppler.so.126 #8 0x7fdfefdd7de7 in Poppler::FormFieldText::setText(QString const&) () from /lib/x86_64-linux-gnu/libpoppler-qt5.so.1 #9 0x7fe008f73e88 in ?? () from /lib/x86_64-linux-gnu/libOkular5Core.so.11 #10 0x7fe017903b35 in QUndoStack::push(QUndoCommand*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fdffc7151b2 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #12 0x7fe0168fba32 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fdffc6839ea in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #14 0x7fdffc70c752 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #15 0x7fe0168fba32 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fe0176a8415 in QLineEdit::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fe0176a5a94 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fe0168fb74d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fe0176afbd5 in QWidgetLineControl::textEdited(QString const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fe0176b32cb in QWidgetLineControl::finishChange(int, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fe0176b604d in QWidgetLineControl::processKeyEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fe0176a859f in QLineEdit::keyPressEvent(QKeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7fe0175a5b5f in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fe017562d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7fe01756ac38 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fe0168c30d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fe0175c0d0a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7fe017562d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7fe0168c30d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7fe016d3a8b9 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7fe016d12d5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #32 0x7fe0118fb8ba in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #33 0x7fe014d111b4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7fe014d142d7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7fe014d148f0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7fe01691c8d6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7fe0168c1b7b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7fe0168ca020 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x563ec4bc1398 in ?? () #40 0x7fe0160456ca in __libc_start_call_main (main=main@entry=0x563ec4bc0c20, argc=argc@entry=1, argv=argv@entry=0x7ffc3db29298) at ../sysdeps/nptl/libc_start_call_main.h:58 #41 0x7fe016045785 in __libc_start_main_impl (main=0x563ec4bc0c20, argc=1, argv=0x7ffc3db29298, init=, fini=, rtld_fini=
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #4 from caulier.gil...@gmail.com --- All is well explained in DK doc git repo README : https://invent.kde.org/documentation/digikam-doc/-/blob/master/README.md?ref_type=heads#translations The status of translations is given at this page : https://l10n.kde.org/stats/gui/trunk-kf5/package/digikam-doc/ Even if DE and FR translations are branched in the doc, nobody working on yet. Branched want means ready to use with the Sphinx framework used to render the doc. But if translations are empty (English words still untranslated), the page will rest in English. Why branched rules exists if no translations yet : to render pages with not complete translations, to help translators. In other words : menu work as expected. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476320] New: Build failure with GCC
https://bugs.kde.org/show_bug.cgi?id=476320 Bug ID: 476320 Summary: Build failure with GCC Classification: Developer tools Product: valgrind Version: 3.22 GIT Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: pjfl...@wanadoo.fr Target Milestone: --- Unintentionally I built 3.22 RC2 with GCC rather than clang (FReeBSD 13.2 amd64)_ I got this build error g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../.. -I../../../include -I../../../coregrind -I../../../include -I../../../VEX/pub -I../../../VEX/pub -DVGA_amd64=1 -DVGO_freebsd=1 -DVGP_amd64_freebsd=1 -DVGPV_amd64_freebsd_vanilla=1 -DVGA_SEC_x86=1 -DVGP_SEC_amd64_freebsd=1 -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector -B/usr/local/lib32/gcc12 -Wl,-rpath,/usr/local/lib32/gcc12/ -m32 -mmmx -msse -MT pcmpgt.o -MD -MP -MF $depbase.Tpo -c -o pcmpgt.o pcmpgt.cpp &&\ mv -f $depbase.Tpo $depbase.Po g++ -Winline -Wall -Wshadow -Wno-long-long -g -fno-stack-protector -B/usr/local/lib32/gcc12 -Wl,-rpath,/usr/local/lib32/gcc12/ -m32 -mmmx -msse -o pcmpgt pcmpgt.o /usr/local/bin/ld: /usr/local/lib32/gcc12/libstdc++.so: undefined reference to `__divmoddi4@GCC_7.0.0' collect2: error: ld returned 1 exit status It's probably a missing -lgcc or something like that. Not a blocking iussue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 476319] Okular crashes when trying to edit form fields
https://bugs.kde.org/show_bug.cgi?id=476319 Sune Vuorela changed: What|Removed |Added CC||k...@pusling.com Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Sune Vuorela --- Fixed in poppler 23.05 or 23.06. Please ask your distribution to provide an updated version. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476321] New: Answering an email to which a file is attached
https://bugs.kde.org/show_bug.cgi?id=476321 Bug ID: 476321 Summary: Answering an email to which a file is attached Classification: Applications Product: kmail2 Version: 5.23.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: pitho...@free.fr Target Milestone: --- Kmail must not propose to join a file if nothing in the answer to an original email suggests a file to be joined. If the original email has a file joined (and perhaps words saying a file is joined), Kmail proposes to join a file to the answer !!! Pierre STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Mageia 9 / Plasma 5.27.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #5 from Jean-Pierre Boucher --- good investigation 🔎 in fact the translation hat I have is carried out by the Google Chrome translator, I did not realize that the pop-up was that of Google Chrome. The translation is quite good ! Jean-Pierre Le lun. 30 oct. 2023 à 10:09, Maik Qualmann a écrit : > https://bugs.kde.org/show_bug.cgi?id=476316 > > --- Comment #3 from Maik Qualmann --- > I suspect that the cause is the redirection to a mirror server, depending > on > which country you are in. I can also reproduce it here in Germany, no > French, > it stays in English. Other languages, Italian or Spanish also work. German > also > remains in English, but I don't know if there is a German translation yet. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 476322] New: Krusader can't access SMB shared folders in Windows Active Directory each time I change domain user password
https://bugs.kde.org/show_bug.cgi?id=476322 Bug ID: 476322 Summary: Krusader can't access SMB shared folders in Windows Active Directory each time I change domain user password Classification: Applications Product: krusader Version: 2.8.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: net-connection Assignee: krusader-bugs-n...@kde.org Reporter: rafael.linux.u...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY My Linux machine needs to access folders shared by Windows users on a network where we all belong to a Windows domain. When I need to access a shared folder on a computer owned by another Windows user or Windows domain, I have to enter my domain user (windows_domain_name/my_user_name) and my domain password. So far, everything works fine. Windows domain policies require you to change your domain login password from time to time, and that's when Krusader runs into problems. After changing the domain password and restarting the computer, Krusader asks again and again for the user name and password but doesn't manage to enter the shared folders until more than 5 minutes have elapsed. It is as if the passwords or paths are cached. However, Dolphin accesses the same folders without any problems after reboot, after having requested (like Krusader) the user and password for the domain. I think Krusader performs some kind of caching that remains for some time after reboot. I have both Dolphin and Krusader configured to open the same folders I had open in the last session, but only Krusader crashes when I re-open the session as I said. STEPS TO REPRODUCE 1. Open Krusader and Dolphin and configure both to save and restore sessions always 2. Open some SMB shared folders inside Windows Active Directory domain (user will be asked for "domain\user" and password 3. Close Linux session 4. Change user Windows AD domain password 5. Log in Linux session (not IN Windows AD domain) 6. Open Krusader and Dolphin (previous opened folders should be open, after asking for "domain\user" and password. OBSERVED RESULT Dolphin open without issues SMB folders, but Krusader is unable to reach those same folders. EXPECTED RESULT To open correctly SMB folders after introducing "domain\user" and password SOFTWARE/OS VERSIONS Windows: Windows Active Directory domain with Windows users domain authenticated Linux: Not logged in Windows AD domain user using active and enabled Windows AD domain user to access SMB shared folders. Operating System: openSUSE Tumbleweed 20230613 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.3.7-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436057] Current review sorting algorithm can cause... problems
https://bugs.kde.org/show_bug.cgi?id=436057 Marco Martin changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/discover/-/commit/bd03ad ||a4e222c0039f42d3f94eda74783 ||413aa87 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Marco Martin --- Git commit bd03ada4e222c0039f42d3f94eda74783413aa87 by Marco Martin. Committed on 30/10/2023 at 11:03. Pushed by mart into branch 'master'. Sort Reviews We have a score about comment as "usefulness" use it for sorting, and add 3 options for sorting: "Relevance" (user facing for usefulness) rating (best to worst) and date (recent to old) Adapt the header layout to fit the button sending the optional comment "install to write a review" on a new line when it doesn't fit ![image](/uploads/037faae369e117aa74288a5f5ab65bc0/image.png) ![image](/uploads/929995ccdde59e46ce4732bad1649f6c/image.png) M +3-1discover/qml/ApplicationPage.qml M +0-2discover/qml/ReviewDelegate.qml M +89 -15 discover/qml/ReviewsPage.qml M +7-0libdiscover/ReviewsBackend/Review.cpp M +3-0libdiscover/ReviewsBackend/Review.h M +33 -0libdiscover/ReviewsBackend/ReviewsModel.cpp M +7-0libdiscover/ReviewsBackend/ReviewsModel.h M +45 -5libdiscover/appstream/OdrsReviewsBackend.cpp M +1-0libdiscover/backends/KNSBackend/KNSReviews.cpp https://invent.kde.org/plasma/discover/-/commit/bd03ada4e222c0039f42d3f94eda74783413aa87 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398582] Notarization of Windows Installer as Windows Store package - Use Craft Continuous Deployment System.
https://bugs.kde.org/show_bug.cgi?id=398582 --- Comment #42 from caulier.gil...@gmail.com --- Hi Maik, Good news: KF6 is under compiling and installing under Windows with VCPKG https://i.imgur.com/AwvnRtf.png But compilation is very slow (at least 4x slower than a Linux) PS: LensFun VCPKG portfile is in a PR : https://github.com/microsoft/vcpkg/pull/34783 Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 --- Comment #6 from Jean-Pierre Boucher --- That's great ! The menu works as expected ! This is not a bug ! There is nothing more to say... Only the fact that the translation of digiKam into French is still at a standstill, it's just a window opening on a wall... . Sorry to bother you with the French translation. That's all folk 🙂. You can close the bug. JP. Boucher Le lun. 30 oct. 2023 à 10:35, a écrit : > https://bugs.kde.org/show_bug.cgi?id=476316 > > --- Comment #4 from caulier.gil...@gmail.com --- > All is well explained in DK doc git repo README : > > > https://invent.kde.org/documentation/digikam-doc/-/blob/master/README.md?ref_type=heads#translations > > The status of translations is given at this page : > > https://l10n.kde.org/stats/gui/trunk-kf5/package/digikam-doc/ > > Even if DE and FR translations are branched in the doc, nobody working on > yet. > Branched want means ready to use with the Sphinx framework used to render > the > doc. But if translations are empty (English words still untranslated), the > page > will rest in English. > > Why branched rules exists if no translations yet : to render pages with not > complete translations, to help translators. > > In other words : menu work as expected. > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 476172] Missing selection boxes in Plasma making a lot of UI elements unusable, especially by keyboard since plasma-framework5 5.111.0-1
https://bugs.kde.org/show_bug.cgi?id=476172 Hexagon changed: What|Removed |Added CC||k...@davidedmundson.co.uk, ||m...@ratijas.tk, ||notm...@gmail.com Version|unspecified |5.111.0 Component|general |tooltips Product|kde |frameworks-plasma Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 476287] kio-extras fails to compile due to missing qcoro-qt6 dependency
https://bugs.kde.org/show_bug.cgi?id=476287 --- Comment #2 from benmorde...@protonmail.com --- Thank you, I did not notice that. I had assumed that it was the job of the initial setup script to pull required dependencies. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476317] after install 2261 my animation slice up on 5.3
https://bugs.kde.org/show_bug.cgi?id=476317 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Dmitry Kazakov --- I can confirm the issue using the test file that was sent by the reporter to my private email. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476317] after install 2261 my animation slice up on 5.3
https://bugs.kde.org/show_bug.cgi?id=476317 Dmitry Kazakov changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 476287] kio-extras fails to compile due to missing qcoro-qt6 dependency
https://bugs.kde.org/show_bug.cgi?id=476287 benmorde...@protonmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|CONFIRMED |RESOLVED --- Comment #3 from benmorde...@protonmail.com --- I have edited the wiki to default the section to expanded rather than collapsed -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476316] The drop-down menu located at the bottom left in digiKam on-line documentation does not work
https://bugs.kde.org/show_bug.cgi?id=476316 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.2.0 Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #7 from caulier.gil...@gmail.com --- yep. Of course you welcome to contribute to translate, as i explained in the README (:=))) https://invent.kde.org/documentation/digikam-doc/-/blob/master/README.md?ref_type=heads#translations Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 476323] New: "No connections found" after restarting NetworkManager 1.44
https://bugs.kde.org/show_bug.cgi?id=476323 Bug ID: 476323 Summary: "No connections found" after restarting NetworkManager 1.44 Classification: Plasma Product: plasma-nm Version: 5.27.9 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: m...@0upti.me Target Milestone: --- SUMMARY When running NetworkManager 1.44 and plasma-nm, and restarting NetworkManager (e.g. with `systemctl restart NetworkManager`), the plasma-nm applet enters a weird state where it always shows "No connections found", despite NM operating properly in the background. Restarting Plasma or the applet (if loaded separately) fixes it until the next NM restart. Reported in NixOS: https://github.com/NixOS/nixpkgs/pull/263985 Also reported in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053707 Also similar issues reported in Arch: https://www.reddit.com/r/archlinux/comments/16in04o/plasma_nm_applet_does_not_show_any_networks_and/ STEPS TO REPRODUCE 1. Use NetworkManager 1.44 2. `systemctl restart NetworkManager` OBSERVED RESULT Applet shows "No connections found" EXPECTED RESULT Applet shows connections properly SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS unstable KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.110 Qt Version: 5.11 + KDE patchsets ADDITIONAL INFORMATION This used to work fine with NM 1.42.x, so something must have changed in between 1.42.x and 1.44.0 that causes this behavior. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Teoh Han Hui changed: What|Removed |Added CC||teohhan...@gmail.com --- Comment #35 from Teoh Han Hui --- `qdbus org.kde.kded5 /modules/plasmavault requestImportVault` works for me, with the caveat of having to manually append the trailing `/` for both paths as @medin mentioned. However, the hidden `.directory` (to add the `folder-decrypted` icon) gets persisted which is undesirable in the case of gocryptfs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476192] Text Tool Cursor: Delete key removes two characters instead of one
https://bugs.kde.org/show_bug.cgi?id=476192 wolthera changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/-/commit/2ff67a1 ||4e5758ce47d321d8c38dd425314 ||519e22 Resolution|--- |FIXED --- Comment #1 from wolthera --- Git commit 2ff67a14e5758ce47d321d8c38dd425314519e22 by Wolthera van Hövell tot Westerflier. Committed on 30/10/2023 at 12:55. Pushed by woltherav into branch 'master'. Text: fix next/previous cluster. This changes the nature of the functions a little, but does fix partial deletion on ligatures as well. M +11 -7libs/flake/text/KoSvgTextShape.cpp M +7-4libs/flake/text/KoSvgTextShape.h https://invent.kde.org/graphics/krita/-/commit/2ff67a14e5758ce47d321d8c38dd425314519e22 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476191] Text Tool Cursor: Ctrl+Backspace behaves erradically around whitespace
https://bugs.kde.org/show_bug.cgi?id=476191 wolthera changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/-/commit/bcbe807 ||1510b44399714bc311618014260 ||28eeec Resolution|--- |FIXED --- Comment #1 from wolthera --- Git commit bcbe8071510b44399714bc31161801426028eeec by Wolthera van Hövell tot Westerflier. Committed on 30/10/2023 at 13:10. Pushed by woltherav into branch 'master'. Text: Fix word deletion. M +20 -21 plugins/tools/svgtexttool/SvgTextCursor.cpp https://invent.kde.org/graphics/krita/-/commit/bcbe8071510b44399714bc31161801426028eeec -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476324] New: Dolphin crashed while opening an external network drive such as nextcloud
https://bugs.kde.org/show_bug.cgi?id=476324 Bug ID: 476324 Summary: Dolphin crashed while opening an external network drive such as nextcloud Classification: Applications Product: dolphin Version: 23.08.2 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: reginaldsahilch...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.08.2) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.2.0-35-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: Greetings I opened dolphin and logged in to my next cloud then I mapped that network to my networks tab and onclick of nextcloud name dolphin crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7fa2d7069021 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #5 0x7fa2d52f4334 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa2d7013ecb in KIO::ListJob::redirection(KIO::Job*, QUrl const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #7 0x7fa2d52f4334 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fa2d6ffc2b9 in KIO::SlaveInterface::redirection(QUrl const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #9 0x7fa2d6ffe478 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #10 0x7fa2d6ffc4bd in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #11 0x7fa2d70009f2 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #12 0x7fa2d52f4334 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fa2d52e9dde in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fa2d5f6c763 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fa2d52bc88a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fa2d52bf987 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fa2d5316727 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fa2d3051d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fa2d30a7258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fa2d304f3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fa2d5315d78 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fa2d52bb1ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fa2d52c3754 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x55dd27ae4b97 in ?? () #25 0x7fa2d4829d90 in __libc_start_call_main (main=main@entry=0x55dd27adeca0, argc=argc@entry=1, argv=argv@entry=0x7ffeaaa52358) at ../sysdeps/nptl/libc_start_call_main.h:58 #26 0x7fa2d4829e40 in __libc_start_main_impl (main=0x55dd27adeca0, argc=1, argv=0x7ffeaaa52358, init=, fini=, rtld_fini=, stack_end=0x7ffeaaa52348) at ../csu/libc-start.c:392 #27 0x55dd27ae5435 in ?? () [Inferior 1 (process 7646) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476303] Same issue with Chrome RPM on Flatpak
https://bugs.kde.org/show_bug.cgi?id=476303 Christophe Marin changed: What|Removed |Added Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 --- Comment #36 from Teoh Han Hui --- > with the caveat of having to manually append the trailing `/` for both paths > as @medin mentioned Actually it is not about the trailing `/`. Any manual changes in the textboxes would do. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 472862] plasmashell and kwin_wayland randomly crashed in KDirWatchPrivate::emitEvent() due to kate sessions
https://bugs.kde.org/show_bug.cgi?id=472862 --- Comment #20 from Harald Sitter --- Git commit 436e38ad511b44432be1be31dc4ed27383e4338a by Harald Sitter. Committed on 30/10/2023 at 12:27. Pushed by sitter into branch 'master'. kdirwatch: always unref d, and unset d from inside d previously we could fall into a trap when the current thread for whatever reason has no local data (e.g. the dtor is invoked from the wrong thread). when that happened we would leave our d untouched and never unref, which then causes particularly hard to track down problems because we can crash at a much later point in time when the d tries to send an event to the since-deleted KDirWatch instance. instead let's revisit this a bit... the reason the `dwp_self.hasLocalData()` check was added is because of destruction order between QThreadStorage (the d) and QGlobalStatic (the ::self()) specifically because of this caveat from the QThreadStorage documentation: > QThreadStorage can be used to store data for the main() thread. QThreadStorage deletes all data set for the main() thread when QApplication is destroyed, regardless of whether or not the main() thread has actually finished. versus QGlobalStatic: > If the object is created, it will be destroyed at exit-time, similar to the C atexit function. This effectively means that QThreadStorage (at least on the main() thread) will destroy BEFORE QGlobalStatic. To bypass this problem the dwp_self check was added to conditionally skip unrefing when the QThreadStorage had already cleaned up. The trouble is that this then hides the mentioned scenario where we have a d but no backing data because of poor thread management. Instead improve our management of the pimpl: In ~KDirWatchPrivate we now unset the d pointer of all still monitoring KDirWatch. This allows us to unconditionally check for d in the ~KDirWatch so it always unrefs/removes itself from KDirWatchPrivate. In the shutdown scenario cleanup runs the other way around... KDirWatchPrivate cleans up and unsets itself as d pointer, thereby turning ~KDirWatch effectively no-op so when it runs afterwards it won't access any Private memory anymore. M +10 -1src/lib/io/kdirwatch.cpp M +1-0src/lib/io/kdirwatch.h https://invent.kde.org/frameworks/kcoreaddons/-/commit/436e38ad511b44432be1be31dc4ed27383e4338a -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 471870] The NetworkManager applet disappears or loses all networks appear after stop/start of NetworkManager, which sometimes happens on wake from sleep in certain distros
https://bugs.kde.org/show_bug.cgi?id=471870 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #12 from Nicolas Fella --- What version of NetworkManager are you running? You can check via "NetworkManager -V" -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 472862] plasmashell and kwin_wayland randomly crashed in KDirWatchPrivate::emitEvent() due to kate sessions
https://bugs.kde.org/show_bug.cgi?id=472862 Harald Sitter changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kdeplasma-addons/-/commi ||t/8245dd474d60ea34aa4aa06d3 ||f90b8c9922507cc --- Comment #21 from Harald Sitter --- Git commit 8245dd474d60ea34aa4aa06d3f90b8c9922507cc by Harald Sitter. Committed on 30/10/2023 at 13:27. Pushed by sitter into branch 'master'. katesessions/konsoleprofiles: do not hold profilesmodel on the stack this causes crashes when accessing the kdirwatch since it doesn't get moveToThread along with the runner. i.e. the runner thread calls into a kdirwatch that lives on the gui thread. this is particularly problematic since kdirwatch is really just a facade for thread-local backing technology, so when the wrong thread calls into kdirwatch it may tap into uninitialized memory (for that thread -- it is initialized on the "correct" thread) M +2-0profiles/profilesmodel.cpp M +10 -5runners/katesessions/katesessions.cpp M +2-1runners/katesessions/katesessions.h M +10 -5runners/konsoleprofiles/konsoleprofiles.cpp M +2-1runners/konsoleprofiles/konsoleprofiles.h https://invent.kde.org/plasma/kdeplasma-addons/-/commit/8245dd474d60ea34aa4aa06d3f90b8c9922507cc -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 469709] KDevelop toolbars and options are unreadable on windows 10 when trying to match theme with dark system theme
https://bugs.kde.org/show_bug.cgi?id=469709 Igor Kushnir changed: What|Removed |Added CC||razorbacky@gmail.com --- Comment #2 from Igor Kushnir --- *** Bug 476314 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 476314] Top menu are can't see it. white is too bright.
https://bugs.kde.org/show_bug.cgi?id=476314 Igor Kushnir changed: What|Removed |Added Status|REPORTED|RESOLVED CC||igor...@gmail.com Resolution|--- |DUPLICATE --- Comment #5 from Igor Kushnir --- *** This bug has been marked as a duplicate of bug 469709 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476325] New: Blur glitches appearing again in wayland with Nvidia GPU
https://bugs.kde.org/show_bug.cgi?id=476325 Bug ID: 476325 Summary: Blur glitches appearing again in wayland with Nvidia GPU Classification: Plasma Product: kwin Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: leo0...@hotmail.com Target Milestone: --- Created attachment 162727 --> https://bugs.kde.org/attachment.cgi?id=162727&action=edit Picture of the glitch (whenever i try and use spectacle, the glitch disappears) 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 *** noticing the same glitch as Bug 455526, marked as solved. not finding anyhing remotely recent about this glitch, decided to open a report. these glitches do not appear using Xorg. STEPS TO REPRODUCE 1. Open konsole 2. Enable blur in Konsole 3. Move cursor over konsole window OBSERVED RESULT Blur effect glitches, notably a dark square following cursor movement. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Nvidia 1080 GPU, i can reproduce it on blurred dolphin as well. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476326] New: White Frames/Missing Frames during Recording
https://bugs.kde.org/show_bug.cgi?id=476326 Bug ID: 476326 Summary: White Frames/Missing Frames during Recording Classification: Applications Product: krita Version: 5.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Dockers/Recorder Assignee: krita-bugs-n...@kde.org Reporter: reise...@gmail.com Target Milestone: --- Created attachment 162728 --> https://bugs.kde.org/attachment.cgi?id=162728&action=edit Canvas Settings and Example Recording Video SUMMARY During recording with the new 10 Hz feature we had an issue with a medium sized canvas and a big brush. The raw PNGs, which where exported, are only correct as long as we use a small size brush. As soon as we enlarge the size (we used the Basic-5 Size brush with >500px, but it seems to be independent of the used brush as long as it is big enough), several of the exported PNGs are white. And the complete build up of the colored area was not captured. The colored area just appears from one frame to the next (please also see the attached Show Case video). We didn't observe any LowPerformance warnings. STEPS TO REPRODUCE 1. Open a canvas 2000x2000 pixels and with a resolution of 300 (for additional details see the attached Screenshot) 2. Start the recording of the Docker Recoder Plugin with a Capturing Interval of 0.1 sec 3. Select a big brush with at least 500px 4. Build up a big colored area with your brush. Do this really fast. Probably, it is a performance issue and therefore you must force the system into a little bit of work. OBSERVED RESULT We observed the bug only on the high performance system of my wife. I can imagine, that this has something todo with the LowPerformanceWarnings. On my old system, I get all the time such warnings with the same setup. But not so on my wifes system. The reson is probably, that on my system the capturing is not taken every 100ms, becaus it is just to slow. And this could also explain, why I don't get the same bug. EXPECTED RESULT Every 100 ms the current canvas should be exported as it is, without any white frames or missing frames. SOFTWARE/OS VERSIONS Windows 11: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'm currently working on an additional Real Time Capture Mode for the Docker Plugin, which is almost ready for a merge request (https://invent.kde.org/freiser/krita-freiser/-/tree/freiser/RecorderRealTimeMT?ref_type=heads). Hence, I have a complete Krita development environment setup here. And I have dug a little bit into the Docker Recorder code, already. I'm pretty sure, that this bug is to advanced for my Krita knowledge, I have so far :-) But I'm willing to support you as much as I can, finding this nasty bug. We are heavly depending on this feature to hold our deadline. Hence, we have a big interest in fixing this as soon as possible. Thank you in advance for your support. Florian -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 476323] "No connections found" after restarting NetworkManager 1.44
https://bugs.kde.org/show_bug.cgi?id=476323 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED --- Comment #1 from Nicolas Fella --- Thanks! There are other reports about this being broken, but that it's related to the NetworkManager version is new and very useful information *** This bug has been marked as a duplicate of bug 471870 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 471870] The NetworkManager applet disappears or loses all networks appear after stop/start of NetworkManager, which sometimes happens on wake from sleep in certain distros
https://bugs.kde.org/show_bug.cgi?id=471870 Nicolas Fella changed: What|Removed |Added CC||m...@0upti.me --- Comment #13 from Nicolas Fella --- *** Bug 476323 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 471870] The NetworkManager applet disappears or loses all networks appear after stop/start of NetworkManager, which sometimes happens on wake from sleep in certain distros
https://bugs.kde.org/show_bug.cgi?id=471870 Nicolas Fella changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|FIXED |--- --- Comment #14 from Nicolas Fella --- https://bugs.kde.org/show_bug.cgi?id=476323 suggests that this is related to NetworkManager 1.44, and indeed I cannot reproduce this on Fedora 38 (NetworkManager 1.42) but can on Fedora 39 (NetworkManager 1.44) -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 476323] "No connections found" after restarting NetworkManager 1.44
https://bugs.kde.org/show_bug.cgi?id=476323 --- Comment #2 from K900 --- I am actually not entirely sure this is the same bug - 471870 mentions the applet disappearing entirely, while at least in my case it is still there, just not listing connections. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 476123] KDE Connect randomly starting playback of paused/stopped media on PC side
https://bugs.kde.org/show_bug.cgi?id=476123 --- Comment #1 from k...@sausenthaler.de --- On a different computer with the same phone I just realized a different behaviour. After playback on Youtube, the widget greys out and just displays "Chromium" as media title. Pushing play is not possible. So a replay is not possible there. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 476323] "No connections found" after restarting NetworkManager 1.44
https://bugs.kde.org/show_bug.cgi?id=476323 --- Comment #3 from Nicolas Fella --- There seem to be different symptoms for different people. For me the applet is there with no connections. They may or may not have the same root cause, we'll see after investigating -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #65 from caulier.gil...@gmail.com --- We currently switch from MXE to VCPKG framework to build digiKam for Windows. The port is under progress. I hope finalize this step in next week. In VCPKG project i see this entry about Gphoto2 under Windows, especially this comment : https://github.com/Microsoft/vcpkg/issues/5075#issuecomment-633519224 If M$ can provide a patch to use natively Gphoto2 under Windows, as the camera interface is out-to -date, this will be nice... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476326] White Frames/Missing Frames during Recording
https://bugs.kde.org/show_bug.cgi?id=476326 Florian Reiser changed: What|Removed |Added CC||reise...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 472862] plasmashell and kwin_wayland randomly crashed in KDirWatchPrivate::emitEvent() due to kate sessions
https://bugs.kde.org/show_bug.cgi?id=472862 Harald Sitter changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kdeplasma-addons/-/commi |ma/kdeplasma-addons/-/commi |t/8245dd474d60ea34aa4aa06d3 |t/4a4439a96a44584b781e8a18b |f90b8c9922507cc |8882ab914db5f12 --- Comment #22 from Harald Sitter --- Git commit 4a4439a96a44584b781e8a18b8882ab914db5f12 by Harald Sitter. Committed on 30/10/2023 at 13:30. Pushed by sitter into branch 'Plasma/5.27'. katesessions/konsoleprofiles: do not hold profilesmodel on the stack this causes crashes when accessing the kdirwatch since it doesn't get moveToThread along with the runner. i.e. the runner thread calls into a kdirwatch that lives on the gui thread. this is particularly problematic since kdirwatch is really just a facade for thread-local backing technology, so when the wrong thread calls into kdirwatch it may tap into uninitialized memory (for that thread -- it is initialized on the "correct" thread) (cherry picked from commit 8245dd474d60ea34aa4aa06d3f90b8c9922507cc) M +2-0profiles/profilesmodel.cpp M +10 -5runners/katesessions/katesessions.cpp M +2-1runners/katesessions/katesessions.h M +10 -5runners/konsoleprofiles/konsoleprofiles.cpp M +2-1runners/konsoleprofiles/konsoleprofiles.h https://invent.kde.org/plasma/kdeplasma-addons/-/commit/4a4439a96a44584b781e8a18b8882ab914db5f12 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398166] Import from camera doesn't find path
https://bugs.kde.org/show_bug.cgi?id=398166 --- Comment #66 from Jean-Pierre Boucher --- It' a good news, Frank Zappa said “*A mind is like a parachute. It doesn't work if it is not open*.” Keep progressing digikam for a long time... Jean-Pierre Boucher Le lun. 30 oct. 2023 à 14:22, a écrit : > https://bugs.kde.org/show_bug.cgi?id=398166 > > --- Comment #65 from caulier.gil...@gmail.com --- > We currently switch from MXE to VCPKG framework to build digiKam for > Windows. > > The port is under progress. I hope finalize this step in next week. > > In VCPKG project i see this entry about Gphoto2 under Windows, especially > this > comment : > > https://github.com/Microsoft/vcpkg/issues/5075#issuecomment-633519224 > > If M$ can provide a patch to use natively Gphoto2 under Windows, as the > camera > interface is out-to -date, this will be nice... > > Gilles Caulier > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476327] New: discover crashes if update check page is opened and window is put in background
https://bugs.kde.org/show_bug.cgi?id=476327 Bug ID: 476327 Summary: discover crashes if update check page is opened and window is put in background Classification: Applications Product: Discover Version: 5.27.9 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: testing1237...@yahoo.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.2.0-35-generic x86_64 Windowing System: Wayland Distribution: KDE neon 5.27 DrKonqi: 5.27.9 [CoredumpBackend] -- Information about the crash: i have kde neon installed and i have been facing this bug for very long time. i get the notice that an update is available. i click on the icon and discover gets opened on updates checking page. i am forced to keep the page open because if i keep some other window in foreground, discover crashes. this is repeatable 100% of the time for me. The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x7fdbc2ba62d5 in QQmlPropertyCache::callJSFactoryMethod (args=0x7ffe822445c0, object=0x55963d9d89e0, this=) at ../../include/QtQml/5.15.11/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:403 #7 QV4::QObjectWrapper::create (engine=, object=0x55963d9d89e0) at jsruntime/qv4qobjectwrapper.cpp:690 #8 0x7fdbc2ba814b in QV4::QObjectWrapper::wrap_slowPath (engine=0x55963d94b190, object=0x55963d9d89e0) at jsruntime/qv4qobjectwrapper.cpp:621 #9 0x7fdbc2b28068 in QV4::ExecutionEngine::metaTypeToJS (this=this@entry=0x55963d94b190, type=, data=data@entry=0x55963fc4c6a0) at jsruntime/qv4engine.cpp:1882 #10 0x7fdbc2b279e8 in variantToJS (value=..., v4=0x55963d94b190) at jsruntime/qv4engine.cpp:1448 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 476327] discover crashes if update check page is opened and window is put in background
https://bugs.kde.org/show_bug.cgi?id=476327 --- Comment #1 from johnathan --- Created attachment 162730 --> https://bugs.kde.org/attachment.cgi?id=162730&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475980] Cache data overview does not include preview
https://bugs.kde.org/show_bug.cgi?id=475980 --- Comment #3 from Bernd --- (In reply to Jean-Baptiste Mardelle from comment #2) > Git commit 2f67613f07069970200264bfd168613afe410451 by Jean-Baptiste > Mardelle. > Committed on 28/10/2023 at 15:02. > Pushed by mardelle into branch 'master'. > > Fix timeline preview ignored in temporary data dialog. > FIXED-IN: 23.08.3 > > M +1-1src/doc/kdenlivedoc.cpp > > https://invent.kde.org/multimedia/kdenlive/-/commit/ > 2f67613f07069970200264bfd168613afe410451 Just tested it with the nightly build, and it works! Thank you very much! As a side note: When clicking on the Nightly Builds Linux Experimental a download of artifacts.zip starts immediately. Is this intentional? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 472862] plasmashell and kwin_wayland randomly crashed in KDirWatchPrivate::emitEvent() due to kate sessions
https://bugs.kde.org/show_bug.cgi?id=472862 Nate Graham changed: What|Removed |Added Keywords|qt6 | Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474084] KDE Connect doesn't correct work on MacOS
https://bugs.kde.org/show_bug.cgi?id=474084 Andy Pan changed: What|Removed |Added CC||andy013...@yahoo.com.tw --- Comment #7 from Andy Pan --- Not sure if it is related. I also ran into this problem despite a clean setup with manually started `dbus-launch` and `kdeconnectd` and I can provide some log trace of `kdeconnectd`: ``` Error sending UDP packet: QAbstractSocket::DatagramTooLargeError Identity packet to QHostAddress("255.255.255.255") got rejected because it was too large. Retrying without including the capabilities kdeconnect.core: Could not query capabilities from notifications server new capabilities for "Pixel 3" kdeconnect.plugin.systemvolume: Unknown data source id of device 82 new capabilities for "Pixel 8" kdeconnect.plugin.systemvolume: Unknown data source id of device 82 kdeconnect.plugin.clipboard: Ignoring clipboard without timestamp discarding unsupported packet "kdeconnect.runcommand.request" for "Pixel 8" ``` Although the last line looks suspicious that KDE Connect cannot detect the capabilities correctly, randomly everything works smoothly even if the line appears. -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 464394] [develop.kde.org] Breeze icon browser doesn't work
https://bugs.kde.org/show_bug.cgi?id=464394 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 476125] Valgrind cannot read binaries containing debug symbols in DWARF 64 format
https://bugs.kde.org/show_bug.cgi?id=476125 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #1 from Mark Wielaard --- In theory valgrind should be able to parse DWARF64, see the initial length field reading in readdwarf.c and readdwarf3.c which set an 64bit flag. But it doesn't surprise me that code/path isn't tested and probably fails since by default DWARF32 is used. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] On X11/Wayland, all windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #34 from Maciej Kotliński --- The problem still appears from time to time on my laptop but it is less frequent. Last time I noticed other version of probably the same issue – some windows are scaled to 1px width and ~50px height. It is difficult to find such window. It is possible to resize it. Now all LibreOffice windows are of such size when I start a new document. X11; Debian GNU/Linux 12; KDE Plasma: 5.27.5; KDE Frameworks: 5.103.0; Qt: 5.15.8; Kernel: 6.1.0-13-amd64 (64-bit); NVIDIA GeForce RTX 3060 Laptop -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476288] Unable to navigate to OK/Cancel buttons and select using keyboard in the logout/restart/shutdown screen.
https://bugs.kde.org/show_bug.cgi?id=476288 Nate Graham changed: What|Removed |Added CC||n...@kde.org Keywords||accessibility, usability -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476127] KMail: Accounts display "Unable to start", akonadi gives a lot of crash-reportings
https://bugs.kde.org/show_bug.cgi?id=476127 niklas...@pm.me changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|UPSTREAM|--- --- Comment #2 from niklas...@pm.me --- I don't understand, because I don't use X11. I am using Wayland. Also, my distribution is KDE Neon, that's why I am reporting this here also. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476127] KMail: Accounts display "Unable to start", akonadi gives a lot of crash-reportings
https://bugs.kde.org/show_bug.cgi?id=476127 --- Comment #3 from niklas...@pm.me --- (In reply to Daniel Vrátil from comment #1) > You installation is misconfigured or incomplete, Akonadi complains that it > cannot connect to your window system (X11). I don't understand, because I don't use X11. I am using Wayland. > Possibly you don't have "DISPLAY" environment set (?). How would I set that? > Please report the issue to your distribution. My distribution is KDE Neon, that's why I am reporting this here. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 417993] vbit-test fail on s390x with Iop_Add32: spurious dependency on uninitialised value
https://bugs.kde.org/show_bug.cgi?id=417993 --- Comment #12 from Mark Wielaard --- I think your analysis is correct. We already seem to do this when printing out a complaint about a real mismatch. See memcheck/tests/vbits-test/util.c (print_opnd): /* The value itself might be partially or fully undefined, so take a copy, paint the copy as defined, and print the copied value. This is so as to avoid error messages from Memcheck, which are correct, but confusing. */ And testing your 3 line fix on s390x it does seem to work as expected: $ perl tests/vg_regtest memcheck/tests/vbit-test/vbit-test.vgtest vbit-test: valgrind -q --expensive-definedness-checks=yes ./vbit-test == 1 test, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == I think my only question is whether we should "clear" all of data or just the value fields of the result and opnds[] of the test_data_t? I guess it doesn't matter whether the rest of the test_data_t struct values are cleared too, but it might "hide" other/real bugs? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476328] New: Custom symbol libraries poor quality preview
https://bugs.kde.org/show_bug.cgi?id=476328 Bug ID: 476328 Summary: Custom symbol libraries poor quality preview Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: faniali...@gmail.com Target Milestone: --- Created attachment 162731 --> https://bugs.kde.org/attachment.cgi?id=162731&action=edit Difference previewing the same symbols between Inkscape and Krita Hi there, I use a lot symbol libraries in Inkscape and I tried to import them in Krita, but I found that the preview icon is very poor resolution. My custom libraries are SVG files made with Inkscape. They are fully compatible and recognized instantly by Krita, the only problem is the quality of the preview which is so poor that does not allow to recognize and use symbols. This is not the case for the default symbols in Krita (like Word Balloons for instance). In the file attached you will see the exact same SVG file previewed by Inkscape (left) and Krita (right). I noticed a little improvement by resizing symbols. It seems like for some reason the thumbnail that Krita takes from the SVG symbol file is related to the size of the original path in Inkscape. The bigger the symbol is, the bigger/defined the thumbnail will be. But even making them massive, the preview is very poor for productions use. SOFTWARE/OS VERSIONS Krita 5.2 on Linux Fedora -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 475370] Tokodon doesn't remember Window position or Size
https://bugs.kde.org/show_bug.cgi?id=475370 Joshua Goins changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #6 from Joshua Goins --- Interesting, what screen resolution (and display scaling, if you use that) are you using so I can try reproducing? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475562] krita segfaults on start after displaying the splash screen
https://bugs.kde.org/show_bug.cgi?id=475562 --- Comment #22 from Halla Rempt --- I guess we also need to figure out why KoResourcePaths::getApplicationRoot() doesn't work on this distribution. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Glenn changed: What|Removed |Added CC||glenntann...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476288] Unable to navigate to OK/Cancel buttons and select using keyboard in the logout/restart/shutdown screen.
https://bugs.kde.org/show_bug.cgi?id=476288 Nate Graham changed: What|Removed |Added Version Fixed In||6.0 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/e94199b26e75531c2571554d5 ||41f8fab04e9b1fa --- Comment #2 from Nate Graham --- Git commit e94199b26e75531c2571554d541f8fab04e9b1fa by Nate Graham, on behalf of Efe Çiftci. Committed on 30/10/2023 at 16:12. Pushed by ngraham into branch 'master'. Improve keyboard navigation for logout screen buttons This commit implements the ability to jump between the power/session buttons and the OK/Cancel buttons using the arrow keys, along with triggering the OK/Cancel buttons with the Enter/Return key. FIXED-IN: 6.0 M +17 -0lookandfeel/org.kde.breeze/contents/logout/Logout.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/e94199b26e75531c2571554d541f8fab04e9b1fa -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] On X11/Wayland, all windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #35 from Michael Butash --- (In reply to Maciej Kotliński from comment #34) > The problem still appears from time to time on my laptop but it is less > frequent. Last time I noticed other version of probably the same issue – > some windows are scaled to 1px width and ~50px height. It is difficult to > find such window. It is possible to resize it. Now all LibreOffice windows > are of such size when I start a new document. > > X11; Debian GNU/Linux 12; KDE Plasma: 5.27.5; KDE Frameworks: 5.103.0; Qt: > 5.15.8; Kernel: 6.1.0-13-amd64 (64-bit); NVIDIA GeForce RTX 3060 Laptop Yours is almost exactly my problem too. Nate's prior advice helped me with windows moving around for a while at least by clearing out the mountain of different display geometry "profiles" that accumulate as kde gyrates during display changes, which in my case is exacerbated by my thunderbolt dock weirdness. My windows were moving about and moving to the 1px width same as you mentioned with every geometry hotplug change, also moving off my 50" display to a 15" laptop 4k display, which became infuriating to find and resize _each_ window when it happened. Clearing the geometry profiles in kde as mentioned helped, where I found 40+ profiles had accumulated. My hypothesis is KDE reels every time there is a change, and creates a profile for _every_ iteration it sees. The problem with my TB dock is it'll periodically glitch, reset my displays, and everything starts bouncing around for a minute or so until it settles. It's an oddity only someone with a TB dock would see, plus like you with the nvidia gpu it makes things even more interesting. I think ultimately it is driving KDE insane in doing so, or at least with so many profiles to choose from, it ends up saving geometry to each, better or worse, and it becomes a role of a dice which it lands on. I've been using Wayland now for some time, and it's even worse than xorg in using the TB docks as every hotplug, the displays all land on different port ID's each time, and with 4x displays (3x on the tb dock) doing that, it becomes a problem for KDE to manage. Literally every glitch changes my displays from (dp-4, dp-5.1, dp-1, dp-5) to (dp-4, dp-5, dp-3, dp-1) and then variably from there. With xorg it would do it occasionally too, but far less prone, and far more deterministic. Wayland is far more variable meaning I have 5 different latte-dock profiles for each display tuple that occurs I have to manually switch between every time my displays rearrange themselves by port-id. This probably needs fixed at the thunderbolt/gpu driver levels that the displayport ports so randomly jumble like that. Certainly anyone else using a usb/thunderbolt adapter devices like that would have similar issues with multiple displays. I've tried with multiple TB docs, they both do the same things. Nate also said this should improve with newer handling to not create the static profiles anymore, so hopefully that helps. These corner cases are all hard to describe, and I'm sure harder for folks to emulate with fairly exotic hardware, but hopefully these reports help the devs understand the nature of the problems to consider when writing these features if they don't have a like hardware configuration to experiment with themselves. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 286793] kmail2 cannot spool mail from /var/spool/mail/$USER to inbox
https://bugs.kde.org/show_bug.cgi?id=286793 duha.b...@gmail.com changed: What|Removed |Added CC||duha.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452118] On X11/Wayland, all windows moved to be mostly offscreen after disconnecting external monitor
https://bugs.kde.org/show_bug.cgi?id=452118 --- Comment #36 from Maciej Kotliński --- (In reply to Michael Butash from comment #35) I experienced 1px windows after buying USB 3.1 docking station (one HDMI port connected to external display). Once it starts to resize lets say Libre Office windows it continues also with other setups without docking station. I also noticed that Plasma often freezes when I click on the icon of group of 1px windows on the task bar. This could be connected with our problem. The strange think is that I can not move anything in opened windows during that freeze (few seconds) but the mouse cursor moves normally. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 475792] Qt6 apps started from Kickoff/KRunner still get killed after kwin_wayland restarts
https://bugs.kde.org/show_bug.cgi?id=475792 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- The problem isn't that plasmashell/krunner quit, it's that apps launched from it are not properly detached -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450320] Plasma crashes in QGuiApplicationPrivate::createPlatformIntegration() after quick re-login to Wayland
https://bugs.kde.org/show_bug.cgi?id=450320 --- Comment #9 from Patrick Silva --- Unfortunately crashes in a row, including Plasma crash, are still happening after quick re-login to Wayland session on neon unsatable. I got a black screen with mouse pointer after the following crashes: $ coredumpctl Mon 2023-10-30 12:52:46 -03 6232 1000 1000 SIGSEGV present /usr/lib/x86_64-linux-gnu/libexec/kf6/kioworker2.9M Mon 2023-10-30 12:52:48 -03 6328 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 843.7K Mon 2023-10-30 12:52:50 -03 6364 1000 1000 SIGABRT present /usr/bin/plasmashell 944.4K Mon 2023-10-30 12:52:51 -03 6464 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 842.6K Mon 2023-10-30 12:52:51 -03 6448 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/xdg-desktop-portal-kde 899.7K Mon 2023-10-30 12:52:53 -03 6489 1000 1000 SIGABRT present /usr/bin/plasmashell 944.0K Mon 2023-10-30 12:52:53 -03 6504 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 841.3K Mon 2023-10-30 12:52:55 -03 6533 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdevil 844.2K Mon 2023-10-30 12:53:00 -03 6615 1000 1000 SIGABRT present /usr/bin/gmenudbusmenuproxy 410.3K Mon 2023-10-30 12:53:00 -03 6623 1000 1000 SIGABRT present /usr/bin/xembedsniproxy 403.4K Mon 2023-10-30 12:53:00 -03 6610 1000 1000 SIGABRT present /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd706.0K Mon 2023-10-30 12:53:01 -03 6625 1000 1000 SIGABRT present /usr/bin/kaccess 527.7K -- You are receiving this mail because: You are watching all bug changes.
[libksane] [Bug 476278] Discover fails to install libraries libvte-2.9 and libokularcore10:amd64 on intel Acer laptop with new kernel 6.2.0-35
https://bugs.kde.org/show_bug.cgi?id=476278 Kåre Särs changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Kåre Särs --- I wonder if this bug is filed for the wrong component? libksane is a image and document scanning library -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476293] Login error message from PAM disappears too fast
https://bugs.kde.org/show_bug.cgi?id=476293 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Nate Graham --- Can reproduce when entering a wrong password. The UI disappears inappropriately right after the message appears. Works as expected when swiping the wrong finger on my fingerprint reader. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 476293] Login error message from PAM disappears too fast
https://bugs.kde.org/show_bug.cgi?id=476293 Nate Graham changed: What|Removed |Added Severity|minor |normal Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476293] When entering the wrong password, the UI immediately disappears after showing the "wrong password" message from PAM
https://bugs.kde.org/show_bug.cgi?id=476293 Nate Graham changed: What|Removed |Added Summary|Login error message from|When entering the wrong |PAM disappears too fast |password, the UI ||immediately disappears ||after showing the "wrong ||password" message from PAM Product|kscreenlocker |plasmashell CC||visual-des...@kde.org Component|general |Theme - Breeze Version|git-master |master Target Milestone|--- |1.0 -- You are receiving this mail because: You are watching all bug changes.