[kdevelop] [Bug 435910] KDevelop crashed on close [ProblemInlineNoteProvider]
https://bugs.kde.org/show_bug.cgi?id=435910 Milian Wolff changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Milian Wolff --- *** This bug has been marked as a duplicate of bug 432248 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 435915] New: KDE Partition Manager crash
https://bugs.kde.org/show_bug.cgi?id=435915 Bug ID: 435915 Summary: KDE Partition Manager crash Product: partitionmanager Version: 4.1.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: chavdar...@hotmail.com Target Milestone: --- Application: partitionmanager (4.1.0) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-50-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: Scaning broken WD Elements Portable P/N: wdbu6y0020bbk-05 - External drive partition table. The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Floating point exception [KCrash Handler] #4 0x7fcf9850b4e5 in PartWidget::paintEvent(QPaintEvent*) () from /lib/x86_64-linux-gnu/libkpmcore.so.9 #5 0x7fcf9784430e in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7fcf97803013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fcf96d4d1ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fcf9783c63a in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fcf9783ce82 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fcf9783e1e3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fcf9783cb9c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fcf9783e1e3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fcf9783e002 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fcf9783cb9c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fcf9783e1e3 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fcf9783e002 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fcf9783e002 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fcf9783e002 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fcf9783cb9c in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fcf97813f7a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7fcf97844a37 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7fcf982c541d in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #23 0x7fcf97803013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7fcf96d4d1ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7fcf97814dd5 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fcf97817850 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7fcf9782cc1f in QWidget::repaint(QRect const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7fcf9782cc7e in QWidget::repaint() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x55b42c82809b in ?? () #30 0x55b42c81ed91 in ?? () #31 0x55b42c81f2a0 in ?? () #32 0x7fcf96d832e6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x55b42c7e5e26 in ?? () #34 0x55b42c8098f2 in ?? () #35 0x55b4
[Discover] [Bug 435830] Discover Notifier crashing when updating through notification
https://bugs.kde.org/show_bug.cgi?id=435830 Aleix Pol changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Aleix Pol --- Can you provide a backtrace maybe? Also please note you're using an unsupported version of Plasma. Please update to a supported version or there's not much we can do about your issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395468] Last selected font style is not reflected in the Font Style: combobox
https://bugs.kde.org/show_bug.cgi?id=395468 Marcelo Sales changed: What|Removed |Added CC||mmtsa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429572] Dolphin does not show image dimensions as additional view properties
https://bugs.kde.org/show_bug.cgi?id=429572 King Kang Kong changed: What|Removed |Added CC||r2b2x3+kde...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435881] Date change in renaming tool
https://bugs.kde.org/show_bug.cgi?id=435881 --- Comment #7 from Thomas Bach --- Ok. I will try it. But if ha have more than 9 pictures with the same datetime, i got two digits at the end. Will it be possible to add an option to the uniqe attribut to add any text like double? Thomas -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435603] Cannot connect to WiFi after restart, if VPN (wireguard) tries to connect simultaneously
https://bugs.kde.org/show_bug.cgi?id=435603 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com --- Comment #3 from Thiago Sueto --- Given the message about secrets, I wonder if it's related to org.freedesktop.secrets? I wouldn't have expected plasma-nm to request secrets as KWallet currently doesn't support it ( https://invent.kde.org/frameworks/kwallet/-/merge_requests/11 ). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 423973] Adding Wireguard .conf file does not save pre-shared key
https://bugs.kde.org/show_bug.cgi?id=423973 --- Comment #2 from Thiago Sueto --- (In reply to soshial from comment #1) > Hey, Thiago. Thank you for submitting your wireguard plasma bug. May I ask > you to have a look at my bug on the screensrecord: > https://bugs.kde.org/show_bug.cgi?id=435603#c2 > > Do you think my bug is related to yours? Hello soshial. I don't think so. I believe I have experienced your bug as well, except the secrets part. After I manually add the pre-shared key, the connection works fine, but I can experience your bug as well, so those two don't seem related. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435881] Date change in renaming tool
https://bugs.kde.org/show_bug.cgi?id=435881 --- Comment #6 from Maik Qualmann --- The filter tab in the right sidebar understands wildcards since digiKam-7.2.0. So, for example, it is possible: *_?.jpg Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #77 from Knut Hildebrandt --- (In reply to GSC from comment #76) > Right click in the left panel and click "Hide Section Remote" seems have > fixed it for me. Otherwise there's a roughly 300kb increase in memory usage > every minute. This seems to slow down the increase in memory usage, but it still happens in some instances. Only remedy: hibernating (suspend to disk) the system. Then memory usage is reduced to below 100 MB, sometimes as little as about 10 MB, per instance. But it increases again after a while. I noticed another interesting thing. Memory usage increases a lot if there is activity in views which contain big files. Last night I watched a movie which was about 700 MB big. After watching it I noticed that the dolphin with the view of the folder containing the respective file used more than 500 MB. Same with another dolphin. I had saved several files of about 300 to 500 MB to one of the folders I had open in it. I did not open these files, but renamed them. The memory usage of respective dolphin rose up to 150-200 MB. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435914] New: If window is closed when maximized, window placement is not saved
https://bugs.kde.org/show_bug.cgi?id=435914 Bug ID: 435914 Summary: If window is closed when maximized, window placement is not saved Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY If the last state of a window on Wayland is maximized, the next time you open it (be it through keyboard shortcuts, KRunner, Kickoff or panel task manager), window placement is not followed, and thus windows open on the left-most screen. STEPS TO REPRODUCE - NOT WORKS 1. Enable Multiscreen behavior: Active screen follows mouse in System Settings > Window Management > Window behavior 2. Open Dolphin 3. Maximize and then close its window 4. Move mouse to any screen that's not the left-most one 5. Open Dolphin via keyboard shortcut, KRunner, Kickoff or panel task manager STEPS TO REPRODUCE - WORKS (Follow steps 1 and 2) 3. Unmaximize/restore window to any size then close its window 4. Move mouse to any screen that's not the left-most one 5. Open Dolphin via keyboard shortcut, KRunner, Kickoff or panel task manager OBSERVED RESULT Window opens on left-most screen regardless of setup EXPECTED RESULT Window opens on the screen the mouse is on SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210415 KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.0-rc7-2.gfb7fb0d-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435531] Slider value changes when hovering over
https://bugs.kde.org/show_bug.cgi?id=435531 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce Version Fixed In||21.04 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435906] Abnormal mouse behavior on effects window
https://bugs.kde.org/show_bug.cgi?id=435906 Julius Künzel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #1 from Julius Künzel --- *** This bug has been marked as a duplicate of bug 435531 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435531] Slider value changes when hovering over
https://bugs.kde.org/show_bug.cgi?id=435531 Julius Künzel changed: What|Removed |Added CC||ca...@libero.it --- Comment #8 from Julius Künzel --- *** Bug 435906 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 435913] New: System apps (eg. KCalc / System Settings) crash after latest SUSE Tumbleweed upgrade 18/04
https://bugs.kde.org/show_bug.cgi?id=435913 Bug ID: 435913 Summary: System apps (eg. KCalc / System Settings) crash after latest SUSE Tumbleweed upgrade 18/04 Product: kcalc Version: 20.12.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: age...@gmail.com Target Milestone: --- Application: kcalc (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.11.11-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Crash everytime i open them (not kernel related. Booted with the previous one as well) The crash can be reproduced every time. -- Backtrace: Application: KCalc (kcalc), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fd962cdec00 (LWP 4194))] [KCrash Handler] #6 QWidget::hide (this=0x0) at kernel/qwidget.cpp:7916 #7 0x7fd965e3535d in QMenuBarPrivate::updateGeometries (this=0x55d3ace24840) at widgets/qmenubar.cpp:256 #8 0x7fd965e39c00 in QMenuBar::changeEvent (this=0x55d3acee93d0, e=0x7ffd5eda5ba0) at widgets/qmenubar.cpp:1446 #9 0x7fd965ce4b16 in QWidget::event (this=0x55d3acee93d0, event=0x7ffd5eda5ba0) at kernel/qwidget.cpp:8961 #10 0x7fd965ca2aff in QApplicationPrivate::notify_helper (this=, receiver=0x55d3acee93d0, e=0x7ffd5eda5ba0) at kernel/qapplication.cpp:3632 #11 0x7fd964fa713a in QCoreApplication::notifyInternal2 (receiver=0x55d3acee93d0, event=0x7ffd5eda5ba0) at kernel/qcoreapplication.cpp:1063 #12 0x7fd965cd5e25 in QWidgetPrivate::updateFont (this=this@entry=0x55d3ace24840, font=...) at kernel/qwidget.cpp:4654 #13 0x7fd965ce4fd2 in QWidget::event (this=0x55d3acee93d0, event=0x7ffd5eda5d40) at kernel/qwidget.cpp:9055 #14 0x7fd965ca2aff in QApplicationPrivate::notify_helper (this=, receiver=0x55d3acee93d0, e=0x7ffd5eda5d40) at kernel/qapplication.cpp:3632 #15 0x7fd964fa713a in QCoreApplication::notifyInternal2 (receiver=0x55d3acee93d0, event=0x7ffd5eda5d40) at kernel/qcoreapplication.cpp:1063 #16 0x7fd965cfdcd6 in sendScreenChangeRecursively (widget=0x55d3acee93d0) at kernel/qwidgetwindow.cpp:752 #17 0x7fd965cfdd0a in sendScreenChangeRecursively (widget=) at kernel/qwidgetwindow.cpp:757 #18 0x7fd965cfddce in QWidgetWindow::handleScreenChange (this=0x55d3acdd67e0) at kernel/qwidgetwindow.cpp:764 #19 QWidgetWindow::qt_static_metacall (_c=QMetaObject::InvokeMetaMethod, _a=, _id=, _o=0x55d3acdd67e0) at .moc/moc_qwidgetwindow_p.cpp:77 #20 QWidgetWindow::qt_static_metacall (_o=0x55d3acdd67e0, _c=, _id=, _a=) at .moc/moc_qwidgetwindow_p.cpp:70 #21 0x7fd964fddc50 in doActivate (sender=0x55d3acdd67e0, signal_index=3, argv=argv@entry=0x7ffd5eda5ec0) at kernel/qobject.cpp:3898 #22 0x7fd964fd6f60 in QMetaObject::activate (sender=sender@entry=0x55d3acdd67e0, m=m@entry=0x7fd965ada600 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd5eda5ec0) at kernel/qobject.cpp:3946 #23 0x7fd9655514cf in QWindow::screenChanged (this=this@entry=0x55d3acdd67e0, _t1=, _t1@entry=0x55d3accf59b0) at .moc/moc_qwindow.cpp:729 #24 0x7fd965551d2d in QWindowPrivate::emitScreenChangedRecursion (this=, newScreen=0x55d3accf59b0) at kernel/qwindow.cpp:484 #25 0x7fd965cd6fc5 in QWidgetPrivate::create (this=this@entry=0x55d3acd37a00) at kernel/qwidget.cpp:1288 #26 0x7fd965cd72e6 in QWidget::create (this=0x55d3acdcd0a0, window=, initializeWindow=, destroyOldWindow=) at kernel/qwidget.cpp:1179 #27 0x7fd965e37822 in QMenuBarPrivate::handleReparent (this=this@entry=0x55d3ace24840) at widgets/qmenubar.cpp:1421 #28 0x7fd965e37c85 in QMenuBarPrivate::init (this=0x55d3ace24840) at widgets/qmenubar.cpp:705 #29 0x7fd965df9e1a in QMainWindow::menuBar (this=this@entry=0x55d3acdcd0a0) at widgets/qmainwindow.cpp:508 #30 0x7fd966630434 in KXmlGuiWindow::createGUI (this=this@entry=0x55d3acdcd0a0, xmlfile=...) at /usr/src/debug/kxmlgui-5.81.0-1.1.x86_64/src/kxmlguiwindow.cpp:225 #31 0x7fd9668cffd3 in KCalculator::KCalculator (parent=0x0, this=, __in_chrg=, __vtt_parm=) at /usr/src/debug/kcalc-20.12.3-1.2.x86_64/kcalc.cpp:89 #32 kdemain (argc=, argv=) at /usr/src/debug/kcalc-20.12.3-1.2.x86_64/kcalc.cpp:2434 #33 0x7fd9666d8b25 in __libc_start_main (main=0x55d3ac02a050 , argc=1, argv=0x7ffd5eda6968, init=, fini=, rtld_fini=, stack_end=0x7ffd5eda6958) at ../csu/libc-start.c:332 #34 0x55d3ac02a08e in _start () at ../sysdeps/x86_64/start.S:120 [Inferior 1 (process 4194) detached] Possible duplicates by query: bug 242368, bug 241056, bug 221431. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435881] Date change in renaming tool
https://bugs.kde.org/show_bug.cgi?id=435881 --- Comment #5 from Thomas Bach --- Meanwhile, i found the uniqe operator. But there is another problem. How can i filter about that operator? If i use them a number with prefix _ is added to the name like Canon 28_01_01 10_00_00_1. Ok, i could filter with text _1. But there are many files also with the _1 in the regular name. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435909] Dragging files onto themselves should be ignored, and not asked for overwrite/rename
https://bugs.kde.org/show_bug.cgi?id=435909 --- Comment #2 from Jens --- Yes, it does. Dolphin shows a popup context menu allowing to copy, link or cancel. Move is not shown as an option since it would not make sense. You can click anywhere to dismiss it. Digikam already assumes you want to move (which totally doesn't make sense here), and shows a modal dialog (!) asking you to rename or overwrite (which would be a null action, overwrite files with themselves). If the behaviour really were the same, I would not complain. :-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386299] Add ExifTool based wrapper to read and write metadata
https://bugs.kde.org/show_bug.cgi?id=386299 --- Comment #14 from caulier.gil...@gmail.com --- Git commit 78bbca7948fc348d9813adf0b220c19d3caf508b by Gilles Caulier. Committed on 19/04/2021 at 11:20. Pushed by cgilles into branch 'master'. Use stackedWidget to show error message from ExifTool at run-time. M +6-6core/libs/properties/itempropertiesmetadatatab.cpp M +66 -0core/libs/widgets/metadata/exiftool/exiftoolwidget.cpp M +21 -1core/libs/widgets/metadata/exiftool/exiftoolwidget.h https://invent.kde.org/graphics/digikam/commit/78bbca7948fc348d9813adf0b220c19d3caf508b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435879] Strange behaviour of right mouse-click on toolbar
https://bugs.kde.org/show_bug.cgi?id=435879 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.3.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435879] Strange behaviour of right mouse-click on toolbar
https://bugs.kde.org/show_bug.cgi?id=435879 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from Maik Qualmann --- I played with this function again under Windows. The behavior is normal for me. The entry has the heading "Text", the tool icon shows the status. The entry is also not started, you probably stay too long on the left mouse button and activate the tool button after the popup has disappeared. I don't think the developers of the KF5 framework would change anything here. You will have to live with it, because the tool button menu is rarely used. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435912] New: Add a filter-function to automatically assign transactions to categories and/or payees based on information in the "memo" field
https://bugs.kde.org/show_bug.cgi?id=435912 Bug ID: 435912 Summary: Add a filter-function to automatically assign transactions to categories and/or payees based on information in the "memo" field Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ri...@gmx-topmail.de Target Milestone: --- SUMMARY Es sollte eine Filter-/Zuweisungsfunktion geben, die Text (exakt, teilweise, mit Platzhaltern *) im Feld "Notiz/Memo" erkennen und entsprechende Zuweisungen vornehmen könnte. Also z.B. WENN im Notizfeld "eBay*" steht, DANN weise die Überweisung der Kategorie "Privatverkäufe" zu. Denn wenn man z.B. bei eBay verkauft, dann ist der Zahler ja immer ein anderer. Mit solch einer Filterfunktion könnte man also eine Überweisung automatisch kategorisieren und müsste es nicht immer manuell machen. Die Zuweisung sollte nicht nur zu Kategorien, sondern auch zu Zahlern/Zahlungsempfängern möglich sein. Denn: Bspw. kann man mehrere Onlineangebote z.B. mit PayPal bezahlen: Online-Paketmarken von DHL, Hermes etc. Als Zahlungsempfänger steht dann immer PayPal auf dem Konto, aber das stimmt ja nicht, denn eigentlich bezahle ich ja zwei verschiedene Versandunternehmen, nur halt über denselben Zahlungsdienstleister (PayPal). In den Notizfeldern steht aber immer verschiedene Mandatsreferenzen. So könnte man dann anhand der unterschiedlichen Mandatsreferenzen die PayPal-Abbuchungen den Zahlungsempfängern "DHL" oder "Hermes" zuweisen, anstatt dass da immer nur PayPal steht und man nicht weiß, welche Abbuchung an welches Versandunternehmen gegangen ist. Einen kleinen Teil dieser Idee beherrscht KMM gegenwärtig ja schon. Man kann nämlich verschiedene Schreibweisen derselben Person im Feld "Name" demselben Zahlungsempfänger zuweisen lassen, also z.B. "Maria Müller" und "M. Müller" und "Mariechen Müller" alle zuweisen lassen an den Zahler "Schwesterherz". Wäre cool, wenn KMM in Zukunft auch das Feld "Notiz/Memo" auswerten und automatisch regelbasierte Zuweisungen zu Kategorien und/oder Zahlern vornehmen könnte. So könnte man also eine Regel erstellen, die nach einem beliebigen Text (es muss nicht auf Mandatsreferenz beschränkt sein) im Feld "Notiz/Memo" Ausschau hält und dann eine Zuweisung der Buchung zu einer Kategorie und/oder einem Zahler vornimmt. Eine solche benutzerdefinierte Automatisierung würde den Benutzern eine Menge manueller (Nach-)Arbeit abnehmen. SOFTWARE/OS VERSIONS Windows: 10 Pro x64 20H2 (but this is OS-independent) KMyMoney version: 5.1 (stable), Aqbanking6, Qt5.11, KF5.65 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433767] Crash while moving panel to second display
https://bugs.kde.org/show_bug.cgi?id=433767 Martin Ueding changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #5 from Martin Ueding --- I have just restarted plasmashell, it came right back up. And then I have dragged the panel to the middle screen; this time without any issues. Hopefully the backtrace will be of some use. I'll come back if it should appear again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435879] Strange behaviour of right mouse-click on toolbar
https://bugs.kde.org/show_bug.cgi?id=435879 Maik Qualmann changed: What|Removed |Added Version|unspecified |7.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435879] Strange behaviour of right mouse-click on toolbar
https://bugs.kde.org/show_bug.cgi?id=435879 Maik Qualmann changed: What|Removed |Added Product|frameworks-kxmlgui |digikam Assignee|kdelibs-b...@kde.org|digikam-bugs-n...@kde.org Component|general |Usability-Menus -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433767] Crash while moving panel to second display
https://bugs.kde.org/show_bug.cgi?id=433767 Martin Ueding changed: What|Removed |Added CC||m...@martin-ueding.de -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435911] New: Sort tags alphabetically in transaction details in ledger view
https://bugs.kde.org/show_bug.cgi?id=435911 Bug ID: 435911 Summary: Sort tags alphabetically in transaction details in ledger view Product: kmymoney Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ri...@gmx-topmail.de Target Milestone: --- SUMMARY When adding tags to a transaction the tags are stored and displayed in the order of their entry, but not in alphabetical order. It would be more logical if tags would automatically be sorted in alphabetical order (just like in the "tags" section). Because tags are not hierarchical it makes the most sense to display them alphabetically in the transaction details in the ledger view section, too. STEPS TO REPRODUCE 1. Go to any ledger and edit a transaction entry by adding some tags. 2. Look at the sorting order of the tags. OBSERVED RESULT Tags are displayed in the order of the entry, not alphabetically. EXPECTED RESULT Tags should be sorted automatically in alphabetical order upon entry. SOFTWARE/OS VERSIONS Windows: 10 Pro x64 20H2 (but this bug is OS-independent) ADDITIONAL INFORMATION KMyMoney version: 5.1 (stable), Aqbanking6, Qt5.11, KF5.65 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435903] Build kdeconnect-kde DMG package with Craft failed on Mac
https://bugs.kde.org/show_bug.cgi?id=435903 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de, ||veyx.s...@gmail.com, ||vonr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information
https://bugs.kde.org/show_bug.cgi?id=435908 --- Comment #2 from Tom Hughes --- Just to be clear, the libraries I'm talking about here have debug information (that is to say that have populated .debug_xxx sections) but they do not have separate debuginfo images. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435731] Extra space between entries in Places panel after reverting icon size to "Small"
https://bugs.kde.org/show_bug.cgi?id=435731 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #10 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/197 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435909] Dragging files onto themselves should be ignored, and not asked for overwrite/rename
https://bugs.kde.org/show_bug.cgi?id=435909 --- Comment #1 from Maik Qualmann --- This is normal file manager behavior. Dolphin shows no other behavior. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435909] Dragging files onto themselves should be ignored, and not asked for overwrite/rename
https://bugs.kde.org/show_bug.cgi?id=435909 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 433549] DBus Interface Definition Appears to be Wrong
https://bugs.kde.org/show_bug.cgi?id=433549 Alexander Lohnau changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Version Fixed In||5.82 Latest Commit||https://invent.kde.org/fram ||eworks/krunner/commit/39e1f ||2e013be8ba09b07ae813a6d429a ||1bb388bb --- Comment #12 from Alexander Lohnau --- Git commit 39e1f2e013be8ba09b07ae813a6d429a1bb388bb by Alexander Lohnau. Committed on 19/04/2021 at 10:33. Pushed by alex into branch 'master'. dbus runner: Fix interface definition qDBusRegisterMetaType registered an int for the type at runtime, but the definitions expect an uint. If one generates code from this XML file the runner's results will not be shown, because the DBus definitions do not match. FIXED-IN: 5.82 M +1-1src/data/org.kde.krunner1.xml M +1-1src/dbusutils_p.h https://invent.kde.org/frameworks/krunner/commit/39e1f2e013be8ba09b07ae813a6d429a1bb388bb -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435464] Invoking task switcher causes active window to show inactive header color on X11
https://bugs.kde.org/show_bug.cgi?id=435464 --- Comment #3 from Michael D --- This affects present windows, and other desktop effects, as well. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information
https://bugs.kde.org/show_bug.cgi?id=435908 Mark Wielaard changed: What|Removed |Added CC||f...@redhat.com, ||m...@klomp.org --- Comment #1 from Mark Wielaard --- The negative caching bug is: https://sourceware.org/bugzilla/show_bug.cgi?id=25628 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 435910] New: KDevelop crashed on close [ProblemInlineNoteProvider]
https://bugs.kde.org/show_bug.cgi?id=435910 Bug ID: 435910 Summary: KDevelop crashed on close [ProblemInlineNoteProvider] Product: kdevelop Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas_norda...@hotmail.com Target Milestone: --- Application: kdevelop (5.6.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.6-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.21.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I closed KDevelop (from the task manager (right-click → "Close")). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f7d227dd2e8 in ProblemInlineNoteProvider::~ProblemInlineNoteProvider (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/probleminlinenoteprovider.cpp:85 #5 0x7f7d227e3ab5 in ProblemInlineNoteProvider::~ProblemInlineNoteProvider (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/probleminlinenoteprovider.cpp:83 #6 qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320 #7 qDeleteAll > (c=..., c=...) at /usr/include/qt5/QtCore/qalgorithms.h:328 #8 ProblemReporterPlugin::~ProblemReporterPlugin (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/problemreporterplugin.cpp:111 #9 0x7f7d227e3bf9 in ProblemReporterPlugin::~ProblemReporterPlugin (this=, this=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/plugins/problemreporter/problemreporterplugin.cpp:112 #10 0x7f7d68258d35 in KDevelop::PluginController::unloadPlugin(KDevelop::IPlugin*, KDevelop::PluginController::PluginDeletion) () from /usr/lib64/libKDevPlatformShell.so.56 #11 0x7f7d68258e12 in KDevelop::PluginController::cleanup() () from /usr/lib64/libKDevPlatformShell.so.56 #12 0x7f7d68266781 in KDevelop::Core::cleanup() () from /usr/lib64/libKDevPlatformShell.so.56 #13 0x7f7d68266b84 in KDevelop::Core::shutdown() () from /usr/lib64/libKDevPlatformShell.so.56 #14 0x7f7d6824685f in KDevelop::MainWindow::~MainWindow() () from /usr/lib64/libKDevPlatformShell.so.56 #15 0x7f7d682468c9 in KDevelop::MainWindow::~MainWindow() () from /usr/lib64/libKDevPlatformShell.so.56 #16 0x7f7d6693b10f in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #17 0x7f7d64abb969 in KXmlGuiWindow::event(QEvent*) () from /usr/lib64/libKF5XmlGui.so.5 #18 0x7f7d6768d4ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f7d6690f32a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #20 0x7f7d66911d61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #21 0x7f7d66967233 in ?? () from /usr/lib64/libQt5Core.so.5 #22 0x7f7d62f8af57 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x7f7d62f8b2d8 in ?? () from /usr/lib64/libglib-2.0.so.0 #24 0x7f7d62f8b38f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x7f7d669668bf in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #26 0x7f7d6690dceb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #27 0x7f7d66915f60 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #28 0x55d28c50a6e6 in main (argc=, argv=) at /usr/src/debug/kdevelop5-5.6.2-1.3.x86_64/app/main.cpp:850 [Inferior 1 (process 13193) detached] Possible duplicates by query: bug 435427, bug 434725, bug 434602, bug 434236, bug 434205. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435800] kdenlive project has vanished completely
https://bugs.kde.org/show_bug.cgi?id=435800 Jonathan Riddell changed: What|Removed |Added CC||j...@jriddell.org --- Comment #5 from Jonathan Riddell --- Thanks, I'll ask the Snap devs to better understand how this works and get back to you -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435909] New: Dragging files onto themselves should be ignored, and not asked for overwrite/rename
https://bugs.kde.org/show_bug.cgi?id=435909 Bug ID: 435909 Summary: Dragging files onto themselves should be ignored, and not asked for overwrite/rename Product: digikam Version: 7.2.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. open any folder 2. select some images 3. start dragging (not ctrl-drag) 4. release onto same folder OBSERVED RESULT dialog pops up asking if we want to rename or ovewrite EXPECTED RESULT no dialog. I wanted to move the images, this should be ignored if the target is the same folder/album because the exact same files are already there. If ctrl-drag is used and released on the same folder/album, it is debatable whether the user should be asked if s?he wants to create duplicates. I think no, in 99% of all cases. There are other options for rare cases where it makes sense to duplicate files (Ctrl-C + Ctrl-V, versioning, etc). Maybe we can add a checkbox "[x] Don't ask again when target and source are identical" to the dialog, and a settings option? Using Digikam appimage with KDE Neon and all available updates applied. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 434407] Size inconsistency in initials-style avatar (default vs change avatar)
https://bugs.kde.org/show_bug.cgi?id=434407 --- Comment #4 from Massimiliano L --- (In reply to Domenico Panella from comment #3) > In my opinion, the default image and the image which we select via window > dialog should be handled at the same way. > I mean both handled as Image or Text otherwise we will always see the > difference between them. I agree with your view. It is otherwise a bit strange to have a default configuration that can never be reset to default. Harmonising the two would be a good idea. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 435908] valgrind tries to fetch from deubginfod for files which already have debug information
https://bugs.kde.org/show_bug.cgi?id=435908 Tom Hughes changed: What|Removed |Added CC||ame...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 435908] New: valgrind tries to fetch from deubginfod for files which already have debug information
https://bugs.kde.org/show_bug.cgi?id=435908 Bug ID: 435908 Summary: valgrind tries to fetch from deubginfod for files which already have debug information Product: valgrind Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: t...@compton.nu Target Milestone: --- The new debuginfod support in valgrind is rather over eager and will try and fetch a debug image for files which already have debug information. Development builds of the code I work on have about 250 shared libraries which are build with full debugging but are not stripped at all so the debug information is in the main image. Because valgrind has always tried to find a debug image before doing any debug lookups, and because that code not includes trying to search debuginfod for an image, programs now takes several minutes to start while valgrind runs 250 debuginfod-find's each of which makes an HTTP call which gets a negative result. There is currently no negative caching in libdebuginfo (though it is planned) so this isn't even a one time thing. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 435907] New: Juk scrambles the cover art between tracks with time
https://bugs.kde.org/show_bug.cgi?id=435907 Bug ID: 435907 Summary: Juk scrambles the cover art between tracks with time Product: juk Version: 20.12.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: greatwh...@posteo.eu CC: mp...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. In the terminal, run `mkdir -p ~/.local/share/juk/coverdb`. Otherwise attempts to download any cover art from last.fm will trigger an error (possibly another bug). 2. Create a last.fm account and enter the details in `Settings > Configure scrobbling ...` (Not sure whether or not this is essential). 3. Go through your music library highlighting all the tracks of a given album, and pressing `Ctrl + Shift + G`. Note, do not try to highlight tracks from several albums at once while doing this, otherwise Juk will give them all the same cover art (possibly another bug). 4. Once you've covered a fair whack of your music collection, maybe just use Juk for a few days, opening & closing it every now and again. Then, the cover art entropy will start to become apparent. OBSERVED RESULT The wrong cover art progressively becomes assigned to tracks. EXPECTED RESULT The correct cover art to be assigned to each track. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS 5.11.15-zen1-2-zen (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.18.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435906] New: Abnormal mouse behavior on effects window
https://bugs.kde.org/show_bug.cgi?id=435906 Bug ID: 435906 Summary: Abnormal mouse behavior on effects window Product: kdenlive Version: 20.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: ca...@libero.it Target Milestone: --- Created attachment 137700 --> https://bugs.kde.org/attachment.cgi?id=137700&action=edit Activation of effect levels with the mouse passage only. SUMMARY When the mouse moves in the effect window, the single pass activates the effect layers. When the mouse moves in the effect window, the single pass activates the effect layers. It is a behavior observed on linux Mint in all its versions and newly installed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 435698] Elisa appears to be blocking the display during playback of music
https://bugs.kde.org/show_bug.cgi?id=435698 Francisco Isgleas changed: What|Removed |Added CC||franci...@isgleas.com --- Comment #1 from Francisco Isgleas --- Created attachment 137699 --> https://bugs.kde.org/attachment.cgi?id=137699&action=edit elisa supresses power management I can confirm this. The power management widget states: "elisa is currently suppressing power management: playing music" This is preventing the session from locking and screen saver to start, but does not seem to interfere with screen going blank. elisa 20.04.2 Plasma 5.18.6 kernel 5.3.18 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435905] New: Allow changing of titlebar color for active/inactive windows when using header colors
https://bugs.kde.org/show_bug.cgi?id=435905 Bug ID: 435905 Summary: Allow changing of titlebar color for active/inactive windows when using header colors Product: Breeze Version: 5.21.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: nortex...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- Header colors give a nice contrast between active/inactive windows by altering the window background color. It would be nice if the titlebar showed the same active/inactive contrast like it does (or can be made to) when not using header colors. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390488] Icons and preview of some files (pdf, png and jpg, for example) look fuzzy in info panel when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=390488 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #11 from Méven Car --- https://invent.kde.org/system/dolphin/-/merge_requests/147 should fix this. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435899] plasma-systemmonitor shows wrong memory usage of shell script app that spawns subprocess
https://bugs.kde.org/show_bug.cgi?id=435899 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- On which page? Can you include a screenshot? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386299] Add ExifTool based wrapper to read and write metadata
https://bugs.kde.org/show_bug.cgi?id=386299 --- Comment #13 from caulier.gil...@gmail.com --- Git commit c86e2844bc4730b91a91458f9bc307863ed617c8 by Gilles Caulier. Committed on 19/04/2021 at 08:37. Pushed by cgilles into branch 'master'. files missing A +48 -0core/libs/widgets/metadata/exiftool/exiftoolbinary.cpp [License: GPL (v2+)] A +48 -0core/libs/widgets/metadata/exiftool/exiftoolbinary.h [License: GPL (v2+)] https://invent.kde.org/graphics/digikam/commit/c86e2844bc4730b91a91458f9bc307863ed617c8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386299] Add ExifTool based wrapper to read and write metadata
https://bugs.kde.org/show_bug.cgi?id=386299 --- Comment #12 from caulier.gil...@gmail.com --- Git commit cc2a9d2a5981537a6df099c765d244dcb8656dac by Gilles Caulier. Committed on 19/04/2021 at 08:36. Pushed by cgilles into branch 'master'. Add new widget to auto-detect ExifTool binary program and version M +2-1core/libs/widgets/CMakeLists.txt R +0-0core/libs/widgets/metadata/exiftool/exiftoolwidget.cpp [from: core/libs/widgets/metadata/exiftoolwidget.cpp - 100% similarity] R +2-1core/libs/widgets/metadata/exiftool/exiftoolwidget.h [from: core/libs/widgets/metadata/exiftoolwidget.h - 096% similarity] https://invent.kde.org/graphics/digikam/commit/cc2a9d2a5981537a6df099c765d244dcb8656dac -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435742] [Plasma Mobile] kwin_wayland crashes in KWin::ApplicationWayland::performStartup()
https://bugs.kde.org/show_bug.cgi?id=435742 --- Comment #8 from Vlad Zahorodnii --- kwin crashes during platform initialization. however, the backtrace misses the most important part - the info where kwin actually crashes in the platform plugin. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435900] plasma-systemmonitor shows wrong memory usage of shell script app that spawns subprocess
https://bugs.kde.org/show_bug.cgi?id=435900 David Redondo changed: What|Removed |Added Resolution|--- |DUPLICATE CC||k...@david-redondo.de Status|REPORTED|RESOLVED --- Comment #1 from David Redondo --- *** This bug has been marked as a duplicate of bug 435899 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 435899] plasma-systemmonitor shows wrong memory usage of shell script app that spawns subprocess
https://bugs.kde.org/show_bug.cgi?id=435899 --- Comment #1 from David Redondo --- *** Bug 435900 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435904] New: stamps are not kept when printing or exporting to PDF
https://bugs.kde.org/show_bug.cgi?id=435904 Bug ID: 435904 Summary: stamps are not kept when printing or exporting to PDF Product: okular Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: jens-bugs.kde@spamfreemail.de Target Milestone: --- SUMMARY see $SUBJECT STEPS TO REPRODUCE 1. open a PDF 2. add a stamp (custom or provided by Okular) 3. open print preview, or export to another PDF OBSERVED RESULT stamps are not visible in the resulting print (preview) EXPECTED RESULT stamps should be visible. I can accept that the *editable* stamps in the PDF file are only visibly in Okular. But if I print a PDF (even into another PDF) the stamps should become a fixed integral rasterized (or rendered) part of the PDF file, and be visible and printable by any other PDF application (but possibly not editable any more). I am using the stamp feature to add my handwritten signature to PDF files just like I used to do in OS X Preview (it works beautifully there), and this works fine - up to the point where I want to "print to PDF" to give the PDF to somebody else. SOFTWARE/OS VERSIONS: KDE Neon 20.04 LTS with all updates applied. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 435901] Package fcitx support for Kate's appimage
https://bugs.kde.org/show_bug.cgi?id=435901 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org, ||vonr...@kde.org --- Comment #1 from Christoph Cullmann --- Hi, good point, I think we miss this as dependency in the craft blueprints. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 435753] No aqbanking plugin available from binary factory
https://bugs.kde.org/show_bug.cgi?id=435753 --- Comment #5 from Ralf Habacker --- (In reply to Ben Cooksley from comment #4) > Note that as KMyMoney is one of the only users of those two packages, the > work in this case should be done by KMyMoney contributors (who also have to > choose which of the two presented roads you wish to go down) The content on the https://www.aquamaniac.de/rdm/projects/aqbanking/wiki/Gwbuild page may shed some light on the available options. -- You are receiving this mail because: You are watching all bug changes.
