[kontact] [Bug 426906] Attempting to change Google Calendar colour crashes Kontact
https://bugs.kde.org/show_bug.cgi?id=426906 Kevin changed: What|Removed |Added CC||hubble...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436177] Category Auto-Creation does not work as intended
https://bugs.kde.org/show_bug.cgi?id=436177 --- Comment #2 from Marcel Hoffmann --- Created attachment 137910 --> https://bugs.kde.org/attachment.cgi?id=137910=edit Actual parent is shown on the bottom of this screenshot -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436177] Category Auto-Creation does not work as intended
https://bugs.kde.org/show_bug.cgi?id=436177 --- Comment #1 from Marcel Hoffmann --- Created attachment 137909 --> https://bugs.kde.org/attachment.cgi?id=137909=edit Selecting the correct parent -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436177] New: Category Auto-Creation does not work as intended
https://bugs.kde.org/show_bug.cgi?id=436177 Bug ID: 436177 Summary: Category Auto-Creation does not work as intended Product: kmymoney Version: 5.1.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: kdebugrep...@pastsecurity.com Target Milestone: --- Created attachment 137908 --> https://bugs.kde.org/attachment.cgi?id=137908=edit Dialog after creating a new category from the ledger view SUMMARY Entering a new ledger entry allows to auto-create a new category if it does not exist. The dialog explains that the parent category will be Expense/Income, but can be changed in the next dialog. Selecting the correct parent category in the next dialog does not work as intended. Instead of adding the new category under the selected parent, it duplicates the whole category structure under the new parent entry. STEPS TO REPRODUCE 1. Enter new ledger entry 2. Enter non-existing category, e.g. "Food:Groceries:Fruit" 3. Click "Yes" in next dialog 4. Change parent category, e.g. from "Expense" to "Expense:Food:Groceries" 5. Click "OK" OBSERVED RESULT New category structure is "Food:Groceries:Food:Groceries:Fruit" EXPECTED RESULT New category structure should be "Food:Groceries:Fruit" SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (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.
[kdenlive] [Bug 436176] New: "Click to add composition" keeps popping up when hovering over the button to enable/disable video
https://bugs.kde.org/show_bug.cgi?id=436176 Bug ID: 436176 Summary: "Click to add composition" keeps popping up when hovering over the button to enable/disable video Product: kdenlive Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jer...@ecere.com Target Milestone: --- SUMMARY "Click to add composition" keeps popping up when I hover over the button to enable/disable video STEPS TO REPRODUCE 1. Hover over the button to enable/disable the video. This was happening while having tweaked the composition settings of the clip (dragging the time position dots). OBSERVED RESULT "Click to add composition" pops up preventing to click the button and otherwise messing up with the focus EXPECTED RESULT This tooltip should not be popping up. SOFTWARE/OS VERSIONS 20.12.2 appimage on Artix Linux -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 411681] Yakuake always shown on second monitor on wayland
https://bugs.kde.org/show_bug.cgi?id=411681 Ashark changed: What|Removed |Added CC||ash...@linuxcomp.ru -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436170] LSP plugin auto-completion should follow "remove tail on complete" setting
https://bugs.kde.org/show_bug.cgi?id=436170 --- Comment #4 from Ahmad Samir --- Mid-air comments collision :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436170] LSP plugin auto-completion should follow "remove tail on complete" setting
https://bugs.kde.org/show_bug.cgi?id=436170
--- Comment #3 from Ahmad Samir ---
An example:
if (fileName.endsWith("foo")) {
}
Now if I put the cursor right before "fileName" and type "QStringV", and
auto-complete it to QStringView the text becomes:
if (QStringView.endsWith("foo")) {
whereas with "remove tail on complete" (in settings -> Editing ->
Auto-Completion) disabled I expect (and that's how it works without the LSP
completion, i.e. if I disable the LSP plugin):
if (QStringViewfileName.endsWith("foo")) {
(then I just type the opening '(' and go on ...etc.)
Does that make sense?
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 436170] LSP plugin auto-completion should follow "remove tail on complete" setting
https://bugs.kde.org/show_bug.cgi?id=436170 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #2 from Kåre Särs --- When you are in the middle of a word and autocomplete a word from the document and have "Remove tail on complete" disabled, it will autocomplete the rest of the completion word, but not remove the end of the "original" word. autocomplete the word "startComplete" with the cursor at "|" on the following line start|End would give: startComplete|End in stead of: startComplete| (without "End") Further if the "Remove" is enabled, the first undo will only undo the removal of the "End", so the completion is done as two separate edit actions... I have been missing this, but not enough to scratch my itch... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436175] New: Error ("can't do this while dragging the timeline") ungrouping clips after a while
https://bugs.kde.org/show_bug.cgi?id=436175
Bug ID: 436175
Summary: Error ("can't do this while dragging the timeline")
ungrouping clips after a while
Product: kdenlive
Version: 20.12.2
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: jer...@ecere.com
Target Milestone: ---
SUMMARY
Getting an error ungrouping clips after a while saying "can't do this while
dragging the timeline" (but the timeline is not being dragged).
Saving the project and
STEPS TO REPRODUCE
1. Does not seem easy to reproduce. Having a bunch of clips grouped (e.g. a
video with audio+video that was split into ~20 smaller clips), then trying to
ungroup each clip one by one eventually results in this error.
OBSERVED RESULT
Getting the "can't do this while dragging the timeline" error and no longer
able to ungroup clips until restarting (or reloading?) the project.
EXPECTED RESULT
Not getting this bug.
SOFTWARE/OS VERSIONS
appimage on Artix Linux
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 436174] New: Usability issues with zooming & scrolling the time line
https://bugs.kde.org/show_bug.cgi?id=436174 Bug ID: 436174 Summary: Usability issues with zooming & scrolling the time line Product: kdenlive Version: 20.12.2 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: jer...@ecere.com Target Milestone: --- SUMMARY The interface to scroll and zoom the timeline is very difficult to use and wastes users a lot of time ending up scrolled at an unintended point. Aspect #1 STEPS TO REPRODUCE Use ctrl-mouse wheel with the intent to zoom in & out on the current time positon OBSERVED RESULT Always zooming where I don't intend to zoom. I'm not even sure whether it zooms in on the cursor or in the middle of the screen because it appears so random. EXPECTED RESULT When the time bar is on the screen, more likely than not the user intends to zoom on the time bar. Especially if it's centered on the screen and/or the cursor is close to the time bar. Aspect #2 STEPS TO REPRODUCE Click the timeline horizontal scroll bar to try to scroll OBSERVED RESULT The timeline is scrolled even before the mouse is moved. EXPECTED RESULT No scrolling until the suer moves the mouse. Taking into account the user's click position on the scroll thumb so that any scrolling is relative to where the user clicked and where the scroll thumb was originally. Aspect #3 STEPS TO REPRODUCE Go to hotkeys, find a hotkey for scrolling or zooming the time line via the keyboard OBSERVED RESULT Could not find any hotkeys for scrolling or zooming the timeline EXPECTED RESULT There should be easy keyboard hotkeys for scrolling and zooming the timeline (towards the timebar if in view / center of the screen otherwise). SOFTWARE/OS VERSIONS appimage 20.12.2 on Artix Linux ADDITIONAL INFORMATION There are serious usability issues with zooming in/out & scrolling the timeline... Clicking the scroll thumb should not move it if you just click it but don't move the mouse yet... and exactly what ctrl-wheel mouse centers on is super on clear. My opinion is that it should always keep the time bar right in the middle of screen as you ctrl-wheel up/down super not* clear. sometimes it feels like it centers on the mouse position, but sometimes it simply does not do that. even if it did always center on the mouse, 2 notches and wherever you're trying to zoom on (which really is ALWAYS the timebar) is no longer in the middle of the screen so you get lost. (also keyboard hotkeys for scrolling the timeline would be extremely helpful) as well for zooming in/out on the timebar centered in the middle of the screen. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436173] Okular does not render Latin characters in annotation tools
https://bugs.kde.org/show_bug.cgi?id=436173 --- Comment #3 from Yuri Chornoivan --- (In reply to Rind from comment #2) > Hi Yuri, thanks for the quick reply. > > I am using okular with mupdf backend > (https://github.com/sandsmark/okular-backend-mupdf), and this other bug > seems to be poppler related. Is it still duplicated? There is nothing in Okular's code that prevents using non-Latin characters, imho. So I guess it's the backend's problem. But I might be wrong... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436173] Okular does not render Latin characters in annotation tools
https://bugs.kde.org/show_bug.cgi?id=436173 --- Comment #2 from Rind --- Hi Yuri, thanks for the quick reply. I am using okular with mupdf backend (https://github.com/sandsmark/okular-backend-mupdf), and this other bug seems to be poppler related. Is it still duplicated? -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 436155] extra-cmake-modules commits 7f47f20ba / 834efa708 break kio's thumbcreator.h for multiple revdeps including kio-extras
https://bugs.kde.org/show_bug.cgi?id=436155 Friedrich W. H. Kossebau changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/extra-cmake-modules/ ||commit/dd91c16cbd6d73e065e7 ||d42923c8cc23fa3ef01a Resolution|--- |FIXED --- Comment #2 from Friedrich W. H. Kossebau --- Git commit dd91c16cbd6d73e065e7d42923c8cc23fa3ef01a by Friedrich W. H. Kossebau. Committed on 25/04/2021 at 17:01. Pushed by kossebau into branch 'master'. ECMGenerateExportHeader: unbreak builds by not mixing std & legacy attributes NO_CHANGELOG M +20 -36 modules/ECMGenerateExportHeader.cmake M +6-1tests/ECMGenerateExportHeaderTest/consumer/CMakeLists.txt https://invent.kde.org/frameworks/extra-cmake-modules/commit/dd91c16cbd6d73e065e7d42923c8cc23fa3ef01a -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 305534] Annotations don't show all non-ASCII letters
https://bugs.kde.org/show_bug.cgi?id=305534 Yuri Chornoivan changed: What|Removed |Added CC||kde.milr...@8shield.net --- Comment #50 from Yuri Chornoivan --- *** Bug 436173 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436173] Okular does not render Latin characters in annotation tools
https://bugs.kde.org/show_bug.cgi?id=436173 Yuri Chornoivan changed: What|Removed |Added CC||yurc...@ukr.net Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Yuri Chornoivan --- *** This bug has been marked as a duplicate of bug 305534 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436173] New: Okular does not render Latin characters in annotation tools
https://bugs.kde.org/show_bug.cgi?id=436173 Bug ID: 436173 Summary: Okular does not render Latin characters in annotation tools Product: okular Version: 21.04.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kde.milr...@8shield.net Target Milestone: --- Created attachment 137907 --> https://bugs.kde.org/attachment.cgi?id=137907=edit example STEPS TO REPRODUCE 1. try to write some text with Latin characters, such as "ç" and accented letters "á", "ã", "é", in the "inline note" and "popup note" annotation tools OBSERVED RESULT the letters are not rendered inside the pdf, but are still visible inside the edit popup SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.16 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 214636] updating tag to XMP/IPTC bug
https://bugs.kde.org/show_bug.cgi?id=214636 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|UPSTREAM|FIXED Version Fixed In||7.3.0 --- Comment #32 from caulier.gil...@gmail.com --- Thanks Olivier. Your feedback is very important as the UPSTREAM bug from Exiv2 project is done due to migration to github. Again, we are happy to see you a long time digiKam user. My best Gilles Cauier -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436170] LSP plugin auto-completion should follow "remove tail on complete" setting
https://bugs.kde.org/show_bug.cgi?id=436170 Waqar Ahmed changed: What|Removed |Added CC||waqar@gmail.com --- Comment #1 from Waqar Ahmed --- Can you elaborate on the "Removes the tail by default"? I don't understand what you mean by that. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436162] Use icons of the same type for toolbar and menu
https://bugs.kde.org/show_bug.cgi?id=436162 --- Comment #4 from Nate Graham --- Fair enough. It seems reasonable for the icon and text to match your default terminal app. So it would say, "Open Konsole" or "Open Terminator" or whatever. Can you file a new bug report for that? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417378] Plasma applet sub-menu of context menu appears as a separate window
https://bugs.kde.org/show_bug.cgi?id=417378 --- Comment #18 from Nate Graham --- Oops, that sould have been marked as a duplicate of Bug 430662, not this one. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430662] Kwin App menu opens in separate window in Wayland
https://bugs.kde.org/show_bug.cgi?id=430662 Nate Graham changed: What|Removed |Added CC||grzegorz.alibo...@gmail.com --- Comment #11 from Nate Graham --- *** Bug 423332 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423332] Global menu on wayland in new window
https://bugs.kde.org/show_bug.cgi?id=423332 --- Comment #4 from Nate Graham --- *** This bug has been marked as a duplicate of bug 430662 *** -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 436155] extra-cmake-modules commits 7f47f20ba / 834efa708 break kio's thumbcreator.h for multiple revdeps including kio-extras
https://bugs.kde.org/show_bug.cgi?id=436155 --- Comment #1 from Friedrich W. H. Kossebau --- Already on it, plan is to undo the usage of standard C++ attributes [[]] in ECMGenerateExportHeader, as they seem to not mix with compiler-specific __attribute___, which though is enforced by the current usage of CMake's GenerateExportHeader. Which opened the eyes about this being fragile from the start and needing some thoughts later as well once the next elephant enters the room. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436104] Skype creates hotspot in upper left corner of desktop in Plasma Wayland session
https://bugs.kde.org/show_bug.cgi?id=436104 Nate Graham changed: What|Removed |Added Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 436172] New: Crash when adding WMS URL
https://bugs.kde.org/show_bug.cgi?id=436172 Bug ID: 436172 Summary: Crash when adding WMS URL Product: marble Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: francois-...@rignat.fr Target Milestone: --- Application: marble (2.2.20 (2.3 development version)) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.11.15-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - What I was doing when the application crashed: Adding [https://wxs.ign.fr/beta/inspire/v/wms?SERVICE=WMS=GetCapabilities] for a new map. Nothing shown in the list of capabilities, clicking next is crashing Marble. The crash can be reproduced every time. -- Backtrace: Application: Marble Virtual Globe (marble), signal: Segmentation fault [KCrash Handler] #4 0x7f583f7155c9 in Marble::MapWizard::downloadLevelZero() () at /lib64/libmarblewidget-qt5.so.28 #5 0x7f583f720454 in Marble::MapWizard::validateCurrentPage() () at /lib64/libmarblewidget-qt5.so.28 #6 0x7f583e8b0dba in QWizard::next() () at /lib64/libQt5Widgets.so.5 #7 0x7f583dc0b3c0 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #8 0x7f583e760316 in QAbstractButton::clicked(bool) () at /lib64/libQt5Widgets.so.5 #9 0x7f583e760cde in QAbstractButtonPrivate::emitClicked() () at /lib64/libQt5Widgets.so.5 #10 0x7f583e762673 in QAbstractButtonPrivate::click() () at /lib64/libQt5Widgets.so.5 #11 0x7f583e762855 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #12 0x7f583e6b1b1e in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #13 0x7f583e670ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #14 0x7f583e677eeb in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7f583dbdbbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7f583e676efa in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #17 0x7f583e6ca375 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #18 0x7f583e6cd6be in QWidgetWindow::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #19 0x7f583e670ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #20 0x7f583dbdbbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #21 0x7f583e017143 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib64/libQt5Gui.so.5 #22 0x7f583dff88cc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib64/libQt5Gui.so.5 #23 0x7f581d78147e in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5XcbQpa.so.5 #24 0x7f583b97ca9f in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #25 0x7f583b9cea98 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #26 0x7f583b979e73 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #27 0x7f583dc286f3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #28 0x7f583dbda57b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #29 0x7f583e870f8f in QDialog::exec() () at /lib64/libQt5Widgets.so.5 #30 0x55c620325d3d in Marble::MarblePart::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.0] () #31 0x7f583dc0b3c0 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #32 0x7f583e66a646 in QAction::triggered(bool) () at /lib64/libQt5Widgets.so.5 #33 0x7f583e66cf31 in QAction::activate(QAction::ActionEvent) () at /lib64/libQt5Widgets.so.5 #34 0x7f583e7ebe9a in QMenuPrivate::activateCausedStack(QVector > const&, QAction*, QAction::ActionEvent, bool) () at /lib64/libQt5Widgets.so.5 #35 0x7f583e7f3512 in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) () at /lib64/libQt5Widgets.so.5 #36 0x7f583e6b1b1e in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #37 0x7f583e670ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #38 0x7f583e677eeb in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #39 0x7f583dbdbbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #40 0x7f583e676efa in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib64/libQt5Widgets.so.5 #41 0x7f583e6ca8e3 in
[extra-cmake-modules] [Bug 436155] extra-cmake-modules commits 7f47f20ba / 834efa708 break kio's thumbcreator.h for multiple revdeps including kio-extras
https://bugs.kde.org/show_bug.cgi?id=436155 Christophe Giboudeaux changed: What|Removed |Added CC||kosse...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 214636] updating tag to XMP/IPTC bug
https://bugs.kde.org/show_bug.cgi?id=214636 --- Comment #31 from Olivier Becquaert --- (In reply to caulier.gilles from comment #30) > Olivier, > > Are you able to reproduce this problem with recent digiKam 7.x version and > Exiv2 0.27.x ? > > Gilles Caulier Hello Gilles, Good news is 12 years later I still use Digikam :-). The bug is gone, you can close it. thank you for this great software ! Olivier (happy Digikam user since at least 12 years) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436171] New: Double commented line in Discover hides all valid entries from sources.list
https://bugs.kde.org/show_bug.cgi?id=436171 Bug ID: 436171 Summary: Double commented line in Discover hides all valid entries from sources.list Product: Discover Version: 5.21.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: k...@istiophorus.org CC: aleix...@kde.org Target Milestone: --- SUMMARY plasma-discover does not handle commented lines in /etc/apt/sources.list properly. STEPS TO REPRODUCE 1. add the following line to your sources.list: # deb file://archive.local/user/pervert_penguin ./ # test 2. Start `plasma-discover` from command line, switch to settings OBSERVED RESULT No sources are shown (besides snap, flatpak, ...) Get the terminal-message «Transaction error: PackageKit::Transaction::ErrorFailedConfigParsing "E: Syntax error in line # deb file://archive.local/user/pervert_panda ./ # test\nW: Ignoring invalid record(s) in sources.list file!\nE: Cannot read vendors.list file\n" PackageKit::Transaction(0x5634082d97b0)» EXPECTED RESULT The tool should ignore any line beginning with # SOFTWARE/OS VERSIONS Discover: 5.21.4 Linux/KDE Plasma: KDE neon KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The same behaviour occurs in Kubuntu 20.04 (Discover 5.18, KDE/Qt: ancientstable ;) ) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436162] Use icons of the same type for toolbar and menu
https://bugs.kde.org/show_bug.cgi?id=436162 --- Comment #3 from popov895 --- Let me disagree with you. "Open Terminal" action opens my default terminal app, which is not always Konsole. So, we need to either show the icon of my default terminal app or a generic icon for terminal apps. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436170] New: LSP plugin auto-completion should follow "remove tail on complete" setting
https://bugs.kde.org/show_bug.cgi?id=436170 Bug ID: 436170 Summary: LSP plugin auto-completion should follow "remove tail on complete" setting Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: a.samir...@gmail.com Target Milestone: --- It looks like when code auto-completion is done by the LSP plugin, it removes the tail by default and there is no setting to change that. Maybe it should follow the global setting in the auto-completion config dialog or have a separate option? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435882] Archiving a project that contains vidstab filters creates "cannot read results file" after restore
https://bugs.kde.org/show_bug.cgi?id=435882 Julius Künzel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/mult ||imedia/kdenlive/commit/80dc ||8d4e7afeaa24fac4cfc45cc2199 ||19ecd3eca Status|CONFIRMED |RESOLVED --- Comment #2 from Julius Künzel --- Git commit 80dc8d4e7afeaa24fac4cfc45cc219919ecd3eca by Julius Künzel. Committed on 25/04/2021 at 15:40. Pushed by jlskuz into branch 'release/21.04'. Fix several archiving issues with mlt files Related to #973 M +152 -107 src/project/dialogs/archivewidget.cpp M +19 -1src/project/dialogs/archivewidget.h M +19 -0src/project/dialogs/projectsettings.cpp https://invent.kde.org/multimedia/kdenlive/commit/80dc8d4e7afeaa24fac4cfc45cc219919ecd3eca -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 436155] extra-cmake-modules commits 7f47f20ba / 834efa708 break kio's thumbcreator.h for multiple revdeps including kio-extras
https://bugs.kde.org/show_bug.cgi?id=436155 shenlebantongying changed: What|Removed |Added CC||shenlebantongy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436169] The default font for Konsole is not monospaced
https://bugs.kde.org/show_bug.cgi?id=436169 Ahmad Samir changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||a.samir...@gmail.com --- Comment #1 from Ahmad Samir --- The built-in default font setting is: QFontDatabase::systemFont(QFontDatabase::FixedFont) so it's whatever the default Monospaced font on your system is. On my system this returns the same font returned by: fc-match monospace -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433557] AppImages Make System Tray Application Launcher Icons Invisible
https://bugs.kde.org/show_bug.cgi?id=433557 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.22.0 Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||40bf43ad57cc5be4172261f90d2 ||3785f76efb5a8 Status|ASSIGNED|RESOLVED --- Comment #4 from Nate Graham --- Git commit 40bf43ad57cc5be4172261f90d23785f76efb5a8 by Nate Graham, on behalf of Konrad Materka. Committed on 25/04/2021 at 15:11. Pushed by ngraham into branch 'master'. [dataengines/sni] Reapply IconThemePath on icon theme change SNI can have custom icon path in IconThemePath attribute. StatusNotifierItemSource uses custom KIconLoader to add this theme dir. KIconLoader forgets this path on any system change (for example when icon theme is change in system settings). Reapply custom theme path on KIconLoader::iconChanged. FIXED-IN: 5.22.0 M +5-0dataengines/statusnotifieritem/statusnotifieritemsource.cpp https://invent.kde.org/plasma/plasma-workspace/commit/40bf43ad57cc5be4172261f90d23785f76efb5a8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436142] If the user clicks in the first tab, the tab lines won't "connect" to the content box outline
https://bugs.kde.org/show_bug.cgi?id=436142 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Yeah, a new style for view tabs is needed here. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 119582] add full screen mode
https://bugs.kde.org/show_bug.cgi?id=119582 Luigi Toscano changed: What|Removed |Added Version Fixed In|5.22|5.7.6.21080 CC||luigi.tosc...@tiscali.it -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 436168] Segfault when optimized SVG file created in Inkscape is loaded either directly or in folder view
https://bugs.kde.org/show_bug.cgi?id=436168 Jeremy Nuttall changed: What|Removed |Added CC||jer...@jeremy-nuttall.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 436168] Segfault when optimized SVG file created in Inkscape is loaded either directly or in folder view
https://bugs.kde.org/show_bug.cgi?id=436168 --- Comment #1 from Jeremy Nuttall --- Power cycling has no effect. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 436169] New: The default font for Konsole is not monospaced
https://bugs.kde.org/show_bug.cgi?id=436169 Bug ID: 436169 Summary: The default font for Konsole is not monospaced Product: konsole Version: 21.04.0 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: omeritzicschwa...@gmail.com Target Milestone: --- SUMMARY The default font for Konsole is not monospaced. STEPS TO REPRODUCE 1. Configure Konsole to use the default settings. OBSERVED RESULT The default font for Konsole is not monospaced, and this make it harder to use Konsole. EXPECTED RESULT The default font for Konsole is monospaced. ADDITIONAL INFORMATION Switching to a monospaced font helps, but please set another monospaced font by default (like Noto Sans Mono). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 436136] Weird breaks and glitches when moving zoomed picture
https://bugs.kde.org/show_bug.cgi?id=436136 --- Comment #5 from Duncan <1i5t5.dun...@cox.net> --- Here's my X mode results, first some generic X/wayland scaling differences I discovered before I get into the gwenview-specific behavior: Scaling on X works a bit differently than it does on wayland. I've two monitors and on (kwin-)wayland scaling is per-monitor while on X it's global. And on X I have to restart the plasma session (which FWIW I do from a CLI login, no graphical display-manager login installed, so quitting a session quits to the CLI login from which I can run a new session) to have the new scaling settings take effect, while on wayland they take effect immediately. Also, on wayland it's possible to scale below 100%, effectively giving you more screen space for more windows at the cost of a smaller UI, if you can read it. On X the minimum is 100%, no way to "scale out" below that (tho on pure X it's possible to set an arbitrarily large X framebuffer and configure panning within it for a similar effect, but at least some years ago when I tried that with kde, it apparently reset the framebuffer to the bounding rectangle of the screens). And I'm not exactly sure of the technical details from the quick tests and don't want to spend more time back in X than I have to (at one point kwin-wayland wouldn't run due to a live-git bug between releases, and I was stuck on X only for a week or two! hey, at least X ran!), but best I could describe it, on X, "different things scale" than on wayland. I /think/ it's the UI that scales on wayland, while on X it's everything. So on wayland the buttons and text scale but for instance the image in gwenview, when set to 100%, is the same size (the same number of absolute screen pixels, 1:1 matched at 100%) either way. But I'd have to spend more time comparing them and perhaps reading some documentation to be sure. Of course you can always zoom either/both the whole display using kwin, or the gwenview zoom-factor and the gwenview zoom's what this bug is about, so... Confirming my suspicions on X moving the zoomed image around in 125% scaling mode was *much* faster than on wayland, near the speed of 100% tho I restarted kde-X a couple times at both 100 and higher scalefactors to better compare, and there was still /some/ scaling slowdown dragging the zoomed image around. And yes, I did see the block-artifacting on 125% scaled X, tho I was testing with a normal photo-image so it wasn't as noticeable as it was with the line-drawing in your video. Dragging back and forth as fast as I could actually left a detectable "smeared" image at one point, where the visible edge was obviously repeatedly redrawn, creating the smear-effect. Of course I tried it at 100% scale also, to compare. Try as I might I couldn't get that to artifact, so the result there was similar to on wayland. But I /did/ notice some "screen-tear" from redraw in the middle of a buffer-fill, something that's supposed to be difficult to avoid on X, while on wayland they use page-flipping and continue redrawing the old page until the app says the new one is ready. That reminded me that the xf86-video-amdgpu driver has a tearfree option, so I checked on it, and it was set to "auto", which is off at normal rotation and xrandr translation matrix, on if rotated or a non-identity xrandr translation matrix is applied. So I turned it on to see if that made a difference, of course restarting the kde session again in both 125% and 100% scaled modes. While turning the amdgpu tearfree on /did/ appear to eliminate the screen-tearing it didn't noticeably affect gwenview's zoomed-drag performance. But my "monitors" are actually TVs limited to 60 Hz refresh. If they were able to do 120 Hz @ the native 4k resolution the tearfree may have had a worse performance impact. Conclusion: X's graphics seem to be tuned for performance at the cost of artifacting if the gpu can't keep up, as seems to be the case for both of us with scaling. That's across graphics drivers and hardware. On wayland we only have my results as your drivers apparently don't have scaling enabled on wayland yet, but at least with my aging amd radeon rx460 graphics (I checked xorg.log for the tearfree setting and noticed the rx number there) wayland appears to go for quality over speed and scaling seems to make it work hard enough to really slow things down, but without the artifacting we both see on scaled-X. But I'd still urge you to try enabling and configuring the kwin zoom effect, setting up hotkeys so you can zoom in and out relatively easily. Then try leaving gwenview at 100% zoom so you don't have to deal with the artifacting there, and see if kwin's full-display zoom effect doesn't avoid the artifacting. Actually, I'd suggest trying 100% scaling and just using the kwin zoom effect for that as well. Among other things that gives you a bigger workspace that you can pan around, with return to "actual size" possible when you need
[gwenview] [Bug 436168] New: Segfault when optimized SVG file created in Inkscape is loaded either directly or in folder view
https://bugs.kde.org/show_bug.cgi?id=436168 Bug ID: 436168 Summary: Segfault when optimized SVG file created in Inkscape is loaded either directly or in folder view Product: gwenview Version: 21.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: jer...@jeremy-nuttall.com Target Milestone: --- Created attachment 137906 --> https://bugs.kde.org/attachment.cgi?id=137906=edit svg SUMMARY STEPS TO REPRODUCE 1. Download SVG data from attachment 2. Navigate to save directory in gwenview or open file directly OBSERVED RESULT segfault EXPECTED RESULT SVG viewing SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch 5.11.16-arch1-1 x86_64 KDE Plasma Version: 5.21.4-1 KDE Frameworks Version: 5.81.0-1 Qt Version: 5.15.2+kde+r180-1 ADDITIONAL INFORMATION Will power cycle later to be sure it's not an OS-side problem -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 0x7f62d8479a88 in fffi4u4 () from /usr/lib/libcfitsio.so.9 #5 0x7f62d847b1a5 in ?? () from /usr/lib/libcfitsio.so.9 #6 0x7f62d847b76b in ffgpvuj () from /usr/lib/libcfitsio.so.9 #7 0x7f62d84517d1 in ffgpv () from /usr/lib/libcfitsio.so.9 #8 0x7f62db00876a in ?? () from /usr/lib/libgwenviewlib.so.5 #9 0x7f62daffe6c9 in ?? () from /usr/lib/libgwenviewlib.so.5 #10 0x7f62d9b2370c in ?? () from /usr/lib/libQt5Gui.so.5 #11 0x7f62d9b24be4 in ?? () from /usr/lib/libQt5Gui.so.5 #12 0x7f62d9b2579c in QImageReader::canRead() const () from /usr/lib/libQt5Gui.so.5 #13 0x7f62dafda4f9 in ?? () from /usr/lib/libgwenviewlib.so.5 #14 0x7f62dafdae07 in ?? () from /usr/lib/libgwenviewlib.so.5 #15 0x7f62d931707f in ?? () from /usr/lib/libQt5Core.so.5 #16 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0 #17 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f6287fff640 (LWP 359770) "Gwenview::Thumb"): #1 0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0x7f62d931d244 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #3 0x7f62dafdaf62 in ?? () from /usr/lib/libgwenviewlib.so.5 #4 0x7f62d931707f in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f62a65a0640 (LWP 359757) "gwenvie:disk$3"): #1 0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so #4 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f62b8910640 (LWP 359756) "gwenvie:disk$2"): #1 0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so #4 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f62b9111640 (LWP 359755) "gwenvie:disk$1"): #1 0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so #4 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f62b9912640 (LWP 359754) "gwenvie:disk$0"): #1 0x7f62d7704260 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #2 0x7f62b9a65a1c in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f62b9a5f668 in ?? () from /usr/lib/dri/iris_dri.so #4 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f62c9d80640 (LWP 359752) "gwenview"): #1 0x7f62d418d524 in ?? () from /usr/lib/libusbmuxd-2.0.so.6 #2 0x7f62d418e8a9 in ?? () from /usr/lib/libusbmuxd-2.0.so.6 #3 0x7f62d76fe299 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f62d8f9e053 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f62d2257640 (LWP 359750) "QDBusConnection"): #1 0x7f62d6e2545d in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f62d6e78a8b in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f62d6e22781 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f62d95581ac in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5
[plasmashell] [Bug 436077] UX: Make "Tap to Click" the default option
https://bugs.kde.org/show_bug.cgi?id=436077 --- Comment #5 from guimarcalsi...@gmail.com --- (In reply to David Edmundson from comment #2) > Plasma should not override libinput defaults. I think in this case this request could be moved back to Neon as originally intended. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436167] Button to stop checksum calculation
https://bugs.kde.org/show_bug.cgi?id=436167 postix changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436167] Button to stop checksum calculation
https://bugs.kde.org/show_bug.cgi?id=436167 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436167] New: Button to stop checksum calculation
https://bugs.kde.org/show_bug.cgi?id=436167 Bug ID: 436167 Summary: Button to stop checksum calculation Product: dolphin Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: pos...@posteo.eu CC: kfm-de...@kde.org Target Milestone: --- If you right click on a file, open the details, you can calculate several checksums. However, you may calculate all checksums at once, simply by clicking on the buttons. In case you got a large file or a slow HDD, this may take a while. If you accidentially started a calculation, you may stop it by closing the dialog. However, if you already started one type of calculation and you accidentally hit another button to calculate a different checksum, you are can't simply disrupt either one. You need to wait until both calculation have finished or stop both by closing the dialog. Therefore a button to stop or pause a specific checksum calculation would be very convenient. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 119582] add full screen mode
https://bugs.kde.org/show_bug.cgi?id=119582 Nate Graham changed: What|Removed |Added Version Fixed In||5.22 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436077] UX: Make "Tap to Click" the default option
https://bugs.kde.org/show_bug.cgi?id=436077 --- Comment #4 from Fabian Vogt --- (In reply to Nate Graham from comment #3) > In other words, this should be done at the libinput level. > > https://gitlab.freedesktop.org/libinput/libinput/-/issues/ They won't change that, see https://wayland.freedesktop.org/libinput/doc/latest/tapping.html#tapping. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436077] UX: Make "Tap to Click" the default option
https://bugs.kde.org/show_bug.cgi?id=436077 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |UPSTREAM --- Comment #3 from Nate Graham --- In other words, this should be done at the libinput level. https://gitlab.freedesktop.org/libinput/libinput/-/issues/ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436162] Use icons of the same type for toolbar and menu
https://bugs.kde.org/show_bug.cgi?id=436162 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- It's colored because it actually opens another app, so we show the app's icon. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429366] Clicking table does not shift focus.
https://bugs.kde.org/show_bug.cgi?id=429366 --- Comment #7 from David Edmundson --- Split other report from Kai as 436166 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436166] New: Keyboard navigation and mouse over both move current index
https://bugs.kde.org/show_bug.cgi?id=436166 Bug ID: 436166 Summary: Keyboard navigation and mouse over both move current index Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: k...@davidedmundson.co.uk CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- If I have a list with 10 entries and I select item 5 by clicking (so it gets the dark blue selected) Then hover item 2. If I press down, on a widgets app I would move the selection to item 6. In plasma-system monitor we move selection to item 3 which is unexpected -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429366] Clicking table does not shift focus.
https://bugs.kde.org/show_bug.cgi?id=429366 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-systemmonitor/-/merge_requests/123 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436165] Some effects are not listed, except if I do a search
https://bugs.kde.org/show_bug.cgi?id=436165 Tobias Bora changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Tobias Bora --- Oups, I feel very stupid, I just forgot to click on the "Video" icon to show all effects. Sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436077] UX: Make "Tap to Click" the default option
https://bugs.kde.org/show_bug.cgi?id=436077 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Plasma should not override libinput defaults. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436165] Some effects are not listed, except if I do a search
https://bugs.kde.org/show_bug.cgi?id=436165 --- Comment #1 from Tobias Bora --- Created attachment 137905 --> https://bugs.kde.org/attachment.cgi?id=137905=edit After the search, many more items appear. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436165] New: Some effects are not listed, except if I do a search
https://bugs.kde.org/show_bug.cgi?id=436165 Bug ID: 436165 Summary: Some effects are not listed, except if I do a search Product: kdenlive Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: tobias.b...@gmail.com Target Milestone: --- Created attachment 137904 --> https://bugs.kde.org/attachment.cgi?id=137904=edit Before searching, many items are missing (alpha operation, alpha shape, auto mask, despill...) SUMMARY The list of effects does not displays all effects. For instance, alpha operation, alpha shape, auto mask, despill... are not listed, but appear if I search for them explicitely. STEPS TO REPRODUCE 1. Open kdenlive: see that few items are in "Alpha, Mask and Keying" 2. Type just "a" in the search bar: observe that many more effects appear Remark: I first discover the bug while I was using the french language, searching for a "sharp/unsharp" effect that appeared hidden. Then I changed languages back to english, thinking that the module may not be translated in french and could cause this hidding... SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOs, channel unstable, KDE Frameworks 5.79.0, (available in About System) KDE Plasma Version: plasmashell 5.20.5 KDE Frameworks Version: KDE Frameworks 5.79.0 Qt Version: Qt 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384782] Allow manually re-ordering tray icons
https://bugs.kde.org/show_bug.cgi?id=384782 --- Comment #18 from Nate Graham --- I think making it a drag-and-drop thing on the config page makes the most sense. The config page is the only place where you can see all entries--visible, hidden, and disabled--to be able to control the ordering of everything. It we implement drag-and-drop for the items themselves on the panel or in the popup, you would be unable to easily control the ordering for hidden or disabled items. And the ordering would change when a hidden item becomes visible, or vice versa. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436127] View Mode
https://bugs.kde.org/show_bug.cgi?id=436127 Nate Graham changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- It can be. Dolphin Settings window > General page > View: Remember display style for each folder -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429366] Clicking table does not shift focus.
https://bugs.kde.org/show_bug.cgi?id=429366 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Summary|Poor keyboard navigation|Clicking table does not ||shift focus. --- Comment #5 from David Edmundson --- Lets make sure we stick with one precise issue per bug report, it's important bug reports remain actionable. I will re-title this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436126] Dolphin crashes when browsing large directories in details view
https://bugs.kde.org/show_bug.cgi?id=436126 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 422282 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Tree View mode crashes in KFileItemModel::removeItems() and shows duplicate items
https://bugs.kde.org/show_bug.cgi?id=422282 Nate Graham changed: What|Removed |Added CC||d...@aninstanceofme.com --- Comment #73 from Nate Graham --- *** Bug 436126 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416516] Add ExifTool based wrapper to read and write metadata with video files
https://bugs.kde.org/show_bug.cgi?id=416516 --- Comment #15 from caulier.gil...@gmail.com --- Git commit c701f2a84df48a7526903768778991190b51f776 by Gilles Caulier. Committed on 25/04/2021 at 13:30. Pushed by cgilles into branch 'master'. ExifTool wrapper : introduce applyChanges() method to update existing tags or to add new tags. The method take a TagsMap hash-table to host ExifTool tag names as key and tag values. Typically, the key follow ExifTool CLI tool argument typo as EXIF:ImageDescription. The value is a UTF8 string. This method is not yet used, unit tests must be written in first. Related: bug 325458, bug 326408 M +167 -47 core/libs/metadataengine/exiftool/exiftoolparser.cpp M +23 -4core/libs/metadataengine/exiftool/exiftoolparser.h M +39 -27 core/libs/metadataengine/exiftool/exiftoolprocess.cpp M +15 -6core/libs/metadataengine/exiftool/exiftoolprocess.h https://invent.kde.org/graphics/digikam/commit/c701f2a84df48a7526903768778991190b51f776 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326408] Writing metadata corrupt or is not supported for RAW files using Exiv2 - Use ExifTool instead
https://bugs.kde.org/show_bug.cgi?id=326408 --- Comment #9 from caulier.gil...@gmail.com --- Git commit c701f2a84df48a7526903768778991190b51f776 by Gilles Caulier. Committed on 25/04/2021 at 13:30. Pushed by cgilles into branch 'master'. ExifTool wrapper : introduce applyChanges() method to update existing tags or to add new tags. The method take a TagsMap hash-table to host ExifTool tag names as key and tag values. Typically, the key follow ExifTool CLI tool argument typo as EXIF:ImageDescription. The value is a UTF8 string. This method is not yet used, unit tests must be written in first. Related: bug 325458, bug 416516 M +167 -47 core/libs/metadataengine/exiftool/exiftoolparser.cpp M +23 -4core/libs/metadataengine/exiftool/exiftoolparser.h M +39 -27 core/libs/metadataengine/exiftool/exiftoolprocess.cpp M +15 -6core/libs/metadataengine/exiftool/exiftoolprocess.h https://invent.kde.org/graphics/digikam/commit/c701f2a84df48a7526903768778991190b51f776 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 325458] Editing Exif information corrupts MPO 3D image with Exiv2 - Use ExifTool instead
https://bugs.kde.org/show_bug.cgi?id=325458 --- Comment #4 from caulier.gil...@gmail.com --- Git commit c701f2a84df48a7526903768778991190b51f776 by Gilles Caulier. Committed on 25/04/2021 at 13:30. Pushed by cgilles into branch 'master'. ExifTool wrapper : introduce applyChanges() method to update existing tags or to add new tags. The method take a TagsMap hash-table to host ExifTool tag names as key and tag values. Typically, the key follow ExifTool CLI tool argument typo as EXIF:ImageDescription. The value is a UTF8 string. This method is not yet used, unit tests must be written in first. Related: bug 326408, bug 416516 M +167 -47 core/libs/metadataengine/exiftool/exiftoolparser.cpp M +23 -4core/libs/metadataengine/exiftool/exiftoolparser.h M +39 -27 core/libs/metadataengine/exiftool/exiftoolprocess.cpp M +15 -6core/libs/metadataengine/exiftool/exiftoolprocess.h https://invent.kde.org/graphics/digikam/commit/c701f2a84df48a7526903768778991190b51f776 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425598] When the annotation toolbar is visible, quick annotations are less quick to access than other annotations
https://bugs.kde.org/show_bug.cgi?id=425598 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/414 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425438] About the new UI of Annotations tools.
https://bugs.kde.org/show_bug.cgi?id=425438 --- Comment #16 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/414 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 436163] no visible horizon
https://bugs.kde.org/show_bug.cgi?id=436163 Heiko Becker changed: What|Removed |Added Component|Context View/Wikipedia |general Product|amarok |kstars Assignee|amarok-bugs-d...@kde.org|mutla...@ikarustech.com CC||heiko.bec...@kde.org Target Milestone|kf5 |--- --- Comment #2 from Heiko Becker --- Moving to kstars -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 436164] New: nw manager strange behaviour is back
https://bugs.kde.org/show_bug.cgi?id=436164 Bug ID: 436164 Summary: nw manager strange behaviour is back Product: frameworks-networkmanager-qt Version: 5.81.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: michael.hm...@gmail.com CC: lamar...@kde.org, lukas.ti...@merlin.cz Target Milestone: --- the usb tethering connection is taking a lot of time to connect and "won" an intermediate step saying that the connection is too weak, this is apparently "bridging" the time dhcp needs for IP settings, it was so nice working before this last update ... now it interrupt constantly and take a lot of time to connect, but the connection is long before active and working Host: hm-mint Kernel: 5.11.16-hmich-tl-frt-2.59 x86_64 bits: 64 Desktop: KDE Plasma 5.21.4 Distro: Linux Mint 20.1 Ulyssa -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 436163] no visible horizon
https://bugs.kde.org/show_bug.cgi?id=436163 --- Comment #1 from jrc --- As I say in bug report, this bug system appears to inflexibly require reporting as 'amarok' and 'wikipedia', neither of which have anything (far as I know) to do with this product or problem. I'm sorry if I have not spent several days trying to learn your bug system to report such a simple, obvious, glaring error. jrc -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 436163] New: no visible horizon
https://bugs.kde.org/show_bug.cgi?id=436163 Bug ID: 436163 Summary: no visible horizon Product: amarok Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Context View/Wikipedia Assignee: amarok-bugs-d...@kde.org Reporter: jr...@littleappletech.com CC: stuffcor...@archlinux.us Target Milestone: kf5 Created attachment 137903 --> https://bugs.kde.org/attachment.cgi?id=137903=edit KSTARS showing NO HORIZON SUMMARY notice - I have *nothing to do* with (or interest in) 'wikipedia' or 'amarok'. This 'category' appeared when I tried to report the bug and appears unchangeable due to this inflexible system of bug reporting. I don't know what 'amarok' means, or where else to report this simple bug. Component Description 'Bug related to the Wikipedia Applet' seems irrelevant and not my choice but inflexibly demanded by your form Note using Kstars v 2.2.0, no way to enter this on report page. STEPS TO REPRODUCE 1. open kstars 2. turn on / off horizon button 3. change zoom from one extreme to other OBSERVED RESULT no visible horizon - screen all black except stars EXPECTED RESULT expect to see horizon or some kind- seen previously SOFTWARE/OS VERSIONS linux Slackware64 14.2 with kde; using xfce4 but seems to borrow from kde. NO related info at all in 'kde handbook' when displayed. Linux/KDE Plasma: (available in About System) - not in slackware it isn't KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 435919] Finding the right package to submit a bug on!
https://bugs.kde.org/show_bug.cgi?id=435919 --- Comment #2 from tbot...@gmail.com --- Yuri, Thanks! for your response! Will post in "plasmashell", but please add a "General Help" session to the app list, so all will know where to reach out for finding the right app to post a bug against! Cheers! TBNK -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436162] Use icons of the same type for toolbar and menu
https://bugs.kde.org/show_bug.cgi?id=436162 --- Comment #1 from popov895 --- Here's the commit that changed this icon: https://invent.kde.org/system/dolphin/commit/154843406de7855f845534f3e13612d258558827 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436162] New: Use icons of the same type for toolbar and menu
https://bugs.kde.org/show_bug.cgi?id=436162 Bug ID: 436162 Summary: Use icons of the same type for toolbar and menu Product: dolphin Version: 21.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: popov...@ukr.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 137902 --> https://bugs.kde.org/attachment.cgi?id=137902=edit Colored icon SUMMARY After updating to a KDE Gear 21.04.0, I noticed that the icon for "Open Terminal" action became colored, although before that it was monochrome. Please don't mix icon types, use either monochrome or color, otherwise it looks bad. https://develop.kde.org/hig/style/icons/monochrome/action/ SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.21 User Edition / X11 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 KDE Gear: 21.04.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 436162] Use icons of the same type for toolbar and menu
https://bugs.kde.org/show_bug.cgi?id=436162 popov895 changed: What|Removed |Added CC||popov...@ukr.net -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 436136] Weird breaks and glitches when moving zoomed picture
https://bugs.kde.org/show_bug.cgi?id=436136 --- Comment #4 from Duncan <1i5t5.dun...@cox.net> --- It's definitely a bug, tho I believe it's hardware/drivers dependent. I /had/ omitted to try with scaling (as you might have guessed seeing as I didn't mention it) as (to my embarrassment) I somehow missed that in your description. My bad! But I just tried it now, and at least here, scaling works on wayland. =:^) (Set in kde systemsettings, display and monitor, display configuration. I believe kscreen must be installed, however. That kcm's missing if it's not.) And I still didn't get artifacts but performance trying to move the image around was *dramatically* worse/slower, to the point that if that was my otherwise-normal setting I'd definitely be looking for faster alternatives as I'd have trouble working that way. System scaling with gwenview zooming and image-panning is definitely struggling. I wonder if amdgpu is set to continue rendering well in that case, or possibly it's kwin-wayland's or mesa's efforts to keep the "every frame perfect, skip frames if necessary" promise that's wayland's normal defined policy, while either X or your hardware makes the other choice and goes for speed over perfect rendering, with those artifacts you're getting the result? I'm going to have to restart kde/plasma in X mode and test scaling there. If the results match yours there and it's faster with artifacts on my amdgpu/radeon too we're looking at a rather different bug than if the results match my wayland results and it's slower but still correct on X for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcalendarcore] [Bug 436161] New: iCalendar files with attachments are read incorrectly (file name)
https://bugs.kde.org/show_bug.cgi?id=436161 Bug ID: 436161 Summary: iCalendar files with attachments are read incorrectly (file name) Product: frameworks-kcalendarcore Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@aschoettler.com Target Milestone: --- iCalendar files with attachments are read incorrectly and therefore the file name is not displayed in the calendar. Current implementation: ATTACH;VALUE=BINARY;FMTTYPE=application/zip;ENCODING=BASE64;X-LABEL=filename.zip: Expected implementation: ATTACH;VALUE=BINARY;FMTTYPE=application/zip;ENCODING=BASE64;FILENAME=filename.zip: Kontact/Calendar uses the property X-LABEL instead of FILENAME. Is that on purpose? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436077] UX: Make "Tap to Click" the default option
https://bugs.kde.org/show_bug.cgi?id=436077 Fabian Vogt changed: What|Removed |Added Product|neon|plasmashell Assignee|neon-b...@kde.org |plasma-b...@kde.org Component|general |Touchpad Target Milestone|--- |1.0 Summary|UX: Make "Tap to Click" the |UX: Make "Tap to Click" the |default option for KDE Neon |default option |on laptops | Version|unspecified |master --- Comment #1 from Fabian Vogt --- Reassigning to Plasma, this makes sense for all distros. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436077] UX: Make "Tap to Click" the default option for KDE Neon on laptops
https://bugs.kde.org/show_bug.cgi?id=436077 tr...@yandex.com changed: What|Removed |Added CC||fab...@ritter-vogt.de, ||tr...@yandex.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436024] [Wayland] multiple screen segfault
https://bugs.kde.org/show_bug.cgi?id=436024 --- Comment #7 from Anthony Delannoy --- Just tried this overlay, issue is still here. If i plug another screen a lot of things segfault and desktop becomes unusable, still caused by handle_geometry. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 434925] Date Field Narrow - missing one digit at end year after two digit day
https://bugs.kde.org/show_bug.cgi?id=434925 Thomas Baumgart changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 429366] Poor keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=429366 Anna changed: What|Removed |Added CC||cyber+...@sysrq.in --- Comment #4 from Anna --- Keyboard navigation is also poor in "Sensors" tab of plasmoid's settings. Moreover, it's unusable with a graphics tablet. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430540] Save annotation color
https://bugs.kde.org/show_bug.cgi?id=430540 Simone Gaiarin changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||simg...@gmail.com --- Comment #4 from Simone Gaiarin --- This seems not a bug. If usability is an issue, please open another dedicate bug report. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 436136] Weird breaks and glitches when moving zoomed picture
https://bugs.kde.org/show_bug.cgi?id=436136 --- Comment #3 from Artem Kliminskyi --- The problem was when KDE Plasma 5.21.4-1 and Xorg server 1.20.11-1 (125% scaling) Intel - UHD Graphics 620 Nvidia - GP108BM [GeForce MX250] - Xorg Intel (125% scaling) - issue! - Switched to Wayland Intel (100% scaling) - no issue! - Switched to Xorg Intel (100% scaling) - no issue! - Switched to Xorg Nvidia (100% scaling) - no issue! - Switched to Xorg Nvidia (125% scaling) - issue! - Can't switch to Wayland Nvidia - Can't switch to 125% scaling on Wayland As you can see, the problem appears only when 125% scaling is enabled. But I can't use 100% because it is too small for me. Also, effect disappears when zooming out -> zooming in without moving, but I still don't think this is not a bug -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 435294] Baloo crashes when creating multiple directories in an indexed path
https://bugs.kde.org/show_bug.cgi?id=435294 --- Comment #12 from tagwer...@innerjoin.org --- (In reply to Stefan Brüns from comment #10) > Thats wrong. Inotify uses pathes exclusively, so does any code in baloo > based on inotify. > > The storage backend in baloo uses inodes. I see "id's" listed in the journalctl messages, the 5714849124383745 and 5643818955242497 in Comment 2 above... I was assuming these were hashes of the filename or something in combination with a modification time but it seems that they are a construct of the dev number and inode. I assume the "renaming" messages appear because baloo has missed the inotify changes and, after having woken up, discovered that a file it thought it knew about is really a different file. So, not so much "detecting" a rename but realising that one has happened. What I don't know is whether this is bad(tm) (Thanks for the conversation, it helps...) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430018] Some KCMs do not display title
https://bugs.kde.org/show_bug.cgi?id=430018 Patrick Silva changed: What|Removed |Added Attachment #137901|screen recording|kinfocenter description|| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430018] Some KCMs do not display title
https://bugs.kde.org/show_bug.cgi?id=430018 --- Comment #3 from Patrick Silva --- Created attachment 137901 --> https://bugs.kde.org/attachment.cgi?id=137901=edit screen recording As we can see in the attached screen recording, kinfocenter is also affected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435812] Wrong scale for GDK app
https://bugs.kde.org/show_bug.cgi?id=435812 --- Comment #3 from sky96...@outlook.com --- (In reply to David Edmundson from comment #1) > Please include output of "env" Hello, it is my first time using this bug tracker and I attached my env without mention your reply early. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 435294] Baloo crashes when creating multiple directories in an indexed path
https://bugs.kde.org/show_bug.cgi?id=435294 --- Comment #11 from Oded Arbel --- (In reply to Stefan Brüns from comment #10) > Thats wrong. Inotify uses pathes [...] > The storage backend in baloo uses inodes. Yes, regards what I meant - I'm pretty sure that tagwerk19 was worried about using inodes for detecting renames, which is what I meant by "not using inodes". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436160] Wallpaper section of desktop settings is not highlighted in blue on opening nor after click on it
https://bugs.kde.org/show_bug.cgi?id=436160 Patrick Silva changed: What|Removed |Added Component|Clipboard |general Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 435294] Baloo crashes when creating multiple directories in an indexed path
https://bugs.kde.org/show_bug.cgi?id=435294 --- Comment #10 from Stefan Brüns --- (In reply to Oded Arbel from comment #7) > Baloo doesn't deal in inodes - it only cares about file paths, so unlikely > any shenanigans with inodes will cause baloo to misbehave. Thats wrong. Inotify uses pathes exclusively, so does any code in baloo based on inotify. The storage backend in baloo uses inodes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436160] New: Wallpaper section of desktop settings is not highlighted in blue on opening nor after click on it
https://bugs.kde.org/show_bug.cgi?id=436160 Bug ID: 436160 Summary: Wallpaper section of desktop settings is not highlighted in blue on opening nor after click on it Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: 1.0 Created attachment 137900 --> https://bugs.kde.org/attachment.cgi?id=137900=edit screen recording SUMMARY Title says it all. Please watch the attached screen recording. EXPECTED RESULT Wallpaper section should be highlighted in blue on opening and after click on it. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862 --- Comment #65 from Allexus J --- Delete folder ~.local/share/baloo/ solved this problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 435309] 3b06b6f22 makes selection near invisible with some foreground/background color combinations
https://bugs.kde.org/show_bug.cgi?id=435309 --- Comment #7 from Duncan <1i5t5.dun...@cox.net> --- (In reply to Ahmad Samir from comment #6) > Should be fixed by > https://invent.kde.org/utilities/konsole/-/merge_requests/380 Works for me! =:^) -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 119582] add full screen mode
https://bugs.kde.org/show_bug.cgi?id=119582 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/khelpcenter/commit/9b681 ||f6bbef323597c27b3f8cfd43405 ||18a8231e Status|ASSIGNED|RESOLVED --- Comment #4 from Albert Astals Cid --- Git commit 9b681f6bbef323597c27b3f8cfd4340518a8231e by Albert Astals Cid, on behalf of Yuri Chornoivan. Committed on 25/04/2021 at 10:28. Pushed by aacid into branch 'master'. Add the full screen mode M +14 -0doc/khelpcenter/index.docbook M +2-1khelpcenterui.rc M +15 -0mainwindow.cpp M +2-0mainwindow.h https://invent.kde.org/system/khelpcenter/commit/9b681f6bbef323597c27b3f8cfd4340518a8231e -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 357656] KOrganizer crashes when creating event
https://bugs.kde.org/show_bug.cgi?id=357656 d...@duradsl.duckdns.org changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from d...@duradsl.duckdns.org --- Hi everyone, This problems is solved for me by running /usr/bin/update-mime-database /usr/share/mime and /usr/bin/update-mime-database /usr/kde5/share/mime (as kde5 is installed under /usr/kde5 on my system). So this in not a KDE bug but an installation or distro issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 366348] WISH: Saving metadata to video files
https://bugs.kde.org/show_bug.cgi?id=366348 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|UPSTREAM|DUPLICATE --- Comment #2 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 416516 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416516] Add ExifTool based wrapper to read and write metadata with video files
https://bugs.kde.org/show_bug.cgi?id=416516 caulier.gil...@gmail.com changed: What|Removed |Added CC||aegor...@gmail.com --- Comment #14 from caulier.gil...@gmail.com --- *** Bug 366348 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 326408] Writing metadata corrupt or is not supported for RAW files using Exiv2 - Use ExifTool instead
https://bugs.kde.org/show_bug.cgi?id=326408 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Writing metadata is not |Writing metadata corrupt or |supported for RAW files |is not supported for RAW |using Exiv2 - Use ExifTool |files using Exiv2 - Use |instead |ExifTool instead -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338075] Tagging RAW images for Canon EOS-1Ds corrupts them
https://bugs.kde.org/show_bug.cgi?id=338075 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|UPSTREAM|DUPLICATE --- Comment #3 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 326408 *** -- You are receiving this mail because: You are watching all bug changes.
