[krita] [Bug 445617] Gradient: Mesh Gradient is not responding at first time invocation
https://bugs.kde.org/show_bug.cgi?id=445617 Katus Lau changed: What|Removed |Added Version|5.0.0-beta1 |4.4.8 CC||katus...@yahoo.com.hk -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #10 from Jonathan Kamens --- Yup, that fixed it. I have no idea how I "canceled the face marking on the ignored tag," but :shrug:. Thank you for troubleshooting with me. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #9 from Maik Qualmann --- The ignored tag is virtual, there are no faces assigned, so the count is null. The information is stored differently. You canceled the face marking on the ignored tag, so it can no longer be seen (filtered) in the People view. Go to the normal tag view and mark it as a face again using the right mouse context menu. I will fix that the virtual tags can be unmarked as face tags. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 445825] Baloo indexer gives more priority to content rather than file name
https://bugs.kde.org/show_bug.cgi?id=445825 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445835] New: The gradient tool won't make smooth gradients. The transitions a jagged and choppy, often not even making the gradient the correct color.
https://bugs.kde.org/show_bug.cgi?id=445835 Bug ID: 445835 Summary: The gradient tool won't make smooth gradients. The transitions a jagged and choppy, often not even making the gradient the correct color. Product: krita Version: 4.4.8 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: katus...@yahoo.com.hk Target Milestone: --- Created attachment 143783 --> https://bugs.kde.org/attachment.cgi?id=143783=edit Attempt at using gradient tool on white backgound SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. select and use gradient tool OBSERVED RESULT choppy uneven gradient (not even a gradient) EXPECTED RESULT smooth color transitions gradient SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION I would like to add that this situation happens when im very far into my art and trying to recreate this with a new blank canvas doesn't provide the same results. In fact, the tool works perfectly on a new canvas or a not so tampered canvas. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #8 from Jonathan Kamens --- Also, I don't know if this is relevant, but despite the fact that I have marked faces as ignored in the Unknown person view, there don't appear to be any entries for tag ID 668 (the tag ID in the DB for the Ignored tag, as shown above) in the ImageTags table: ``` MariaDB [digikam]> select count(*) from ImageTags where tagid=668; +--+ | count(*) | +--+ |0 | +--+ 1 row in set (0.001 sec) ``` -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 444543] KOrganizer crashes when adding new event
https://bugs.kde.org/show_bug.cgi?id=444543 --- Comment #1 from Szőts Ákos --- Created attachment 143782 --> https://bugs.kde.org/attachment.cgi?id=143782=edit New crash information added by DrKonqi kontact (5.18.3 (21.08.3)) using Qt 5.15.2 - What I was doing when the application crashed: I created a new task (with recurrency). When I clicked OK, KOrganizer crashed. The event had been created successfully before, though. -- Backtrace (Reduced): #6 QSortFilterProxyModelPrivate::proxy_to_source (this=0x56554185b0d0, proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:571 #7 0x7f7138b6b2c9 in QSortFilterProxyModel::mapToSource (proxyIndex=..., this=0x5655419cc2c0) at itemmodels/qsortfilterproxymodel.cpp:3171 #8 QSortFilterProxyModelPrivate::store_persistent_indexes (this=) at itemmodels/qsortfilterproxymodel.cpp:1248 #9 0x7f7138b6cd5b in QSortFilterProxyModelPrivate::_q_sourceLayoutAboutToBeChanged (this=0x56554185b0d0, sourceParents=..., hint=) at itemmodels/qsortfilterproxymodel.cpp:1639 #10 0x7f7138bd5078 in doActivate (sender=0x5655419cb430, signal_index=9, argv=0x7fff36d06a30) at kernel/qobject.cpp:3898 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 444543] KOrganizer crashes when adding new event
https://bugs.kde.org/show_bug.cgi?id=444543 Szőts Ákos changed: What|Removed |Added CC||szots...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445834] New: Flipping too quickly causes displays incomplete canvas changes
https://bugs.kde.org/show_bug.cgi?id=445834 Bug ID: 445834 Summary: Flipping too quickly causes displays incomplete canvas changes Product: krita Version: 5.0.0-beta2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: symme...@gmail.com Target Milestone: --- Created attachment 143781 --> https://bugs.kde.org/attachment.cgi?id=143781=edit Tiles not synced. SUMMARY It is advised that beginners learning animation "flip" between "drawings" instead of using the onion skin. However, if one does this too quickly (at least on my computer), the screen appears to partially update to one frame before reversing to the other. STEPS TO REPRODUCE 1. Create an animation with two frames/"drawings": one with a scribble covering the canvas and one with a blank canvas. 2. Use the arrow keys or keys bound to "previous keyframe" and "next keyframe" to "flip" (switch) between the two frames/"drawings" rapidly. OBSERVED RESULT The screen will appear to be divided into "tiles", with some changing as expected while "flipping" and some failing to change. EXPECTED RESULT All "tiles" to be in sync and display the same frame/"drawing". SOFTWARE/OS VERSIONS Windows: 7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION The image attached shows a screenshot of Krita taken while "flipping". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445774] Terminal panel does not respect custom bash prompt consistently
https://bugs.kde.org/show_bug.cgi?id=445774 --- Comment #5 from Pranav Karande --- Is this a duplicate of https://bugs.kde.org/show_bug.cgi?id=279614 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #7 from Jonathan Kamens --- Digging into the database, as far as I can tell it exists but has the correct name but is not visible in the UI: ``` MariaDB [digikam]> select * from TagProperties where property='ignoredPerson'; +---+---+---+ | tagid | property | value | +---+---+---+ | 668 | ignoredPerson | NULL | +---+---+---+ 1 row in set (0.004 sec) MariaDB [digikam]> select * from Tags where id=668; +-+--+-+--+-+ | id | pid | name| icon | iconkde | +-+--+-+--+-+ | 668 |4 | Ignored | NULL | NULL| +-+--+-+--+-+ 1 row in set (0.000 sec) ``` It does not show up _at all_ in the people view, in the third position or anywhere else. When I enter "Ignored" in the search box underneath the people view there are no results. When I search for "Ignored" in the tag manager it _is_ visible there. Just not visible in the people view. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 445828] Activities Bar widget shows broken text when panel gets thinner
https://bugs.kde.org/show_bug.cgi?id=445828 --- Comment #1 from saif1...@gmail.com --- To add on top of the issue, the "clickable" area is only the text. So it makes the "column" space not useful to navigate. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #6 from Maik Qualmann --- If you have renamed it, it will still remain on the 3rd tag position from the top in the People view. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445833] custom hotkey command with "~" in path does not work
https://bugs.kde.org/show_bug.cgi?id=445833 --- Comment #1 from g...@netcologne.de --- One additional information: It is important to invoke the command with a parameter. Without a parameter it works with "~", too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445833] New: custom hotkey command with "~" in path does not work
https://bugs.kde.org/show_bug.cgi?id=445833 Bug ID: 445833 Summary: custom hotkey command with "~" in path does not work Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: g...@netcologne.de Target Milestone: --- SUMMARY I have placed a command in my ~/bin/ directory and wanted to configure a hotkey to execute this command with a parameter. So I configured the command/URL like "~/bin/foo --bla". When invoking the hotkey I have got an error requester that the command "/home/gert/bin/foo --bla" could not be executed: "Unable to run the command specified. The file or folder "/home/gert/bin/foo --bla" does not exist. So the "~" was correctly expanded but somehow not correctly executed. When changing the "~" to "/home/gert" everything did work fine. STEPS TO REPRODUCE 1. Place a programm in ~/bin/. E.g. a symlink: ln -s /usr/bin/xeyes ~/bin/ 2. Create a custom hotkey to envoke the command: ~/bin/xeyes -distance 3. Press the hotkey OBSERVED RESULT The mentioned error requester occurs. EXPECTED RESULT xeyes should open 4. Now change the command to: /home/XXX/bin/xeyes -distance (Where XXX is your user's home directory) => The hotkey does work SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 445832] New: When Akonadi is messed up, Kalendar just dies on start. Backtrace attached
https://bugs.kde.org/show_bug.cgi?id=445832 Bug ID: 445832 Summary: When Akonadi is messed up, Kalendar just dies on start. Backtrace attached Product: kalendar Version: 0.2.1 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: random1123581...@protonmail.com CC: c...@carlschwan.eu Target Milestone: --- Created attachment 143780 --> https://bugs.kde.org/attachment.cgi?id=143780=edit Backtrace SUMMARY The summary above. I deleted /home/user/.local/share/akonadi and then did some other things I should not have done to try and fix Akonadi, and I ended up having a pretty broken Akonadi. Now, Kalendar won't even start STEPS TO REPRODUCE 1. Mess up with Akonadi 2. Try to start Kalendar OBSERVED RESULT See backtrace attached EXPECTED RESULT It should open fine and then display an error or something, not just crash outright SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #5 from Maik Qualmann --- The tag is actually created when it doesn't exist, neither is it on a new database and is automatically created the first time a face is ignored. It is possible to rename the ignored tag (is by design), maybe you did. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 445792] Cannot properly configure tabs and spaces for project indentation settings
https://bugs.kde.org/show_bug.cgi?id=445792 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- > It basically totally screwed up my code in such a way that it will be very > painful for me to recover since I have made a lot of changes since my last > git commit. Don't experiment without a backup. You could have created a "WIP" commit or run `git diff > wip.patch` before reformatting the code with the tool you never used before. > Furthermore, there is no help. I have no idea what "Force tabs" does. http://astyle.sourceforge.net/astyle.html#_indent=force-tab > The project formatter should be consistent with the global format settings > but this is not the case. I see no reason why the confusing project source > format settings differ from the global editor indentation settings. The global formatting settings are from KTextEditor, and I suspect overriding them per-session or per-project is not supported by KTextEditor framework. > I also see no way to do tabs and spaces like is possible with the global > editor indentation settings. You could try Custom Script Formatter styles. Surely GNU Indent, Uncrustify or Clang-Format implement your preferred indentation style. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 430719] Navigate through emails in email message windows: next, previous, next unread, previous unread
https://bugs.kde.org/show_bug.cgi?id=430719 Achilleas Koutsou changed: What|Removed |Added CC||achillea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445831] New: Krita 5 crashes at "Convert to File Layer ..."
https://bugs.kde.org/show_bug.cgi?id=445831 Bug ID: 445831 Summary: Krita 5 crashes at "Convert to File Layer ..." Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: andr...@andreasresch.at Target Milestone: --- Krita 5 crashes when I choose the "Convert to File Layer ..." action from the layer docker. I can pick the path and adjust the settings, but after I click "OK", Krita crashes. There's nothing special about the file. I just created a new one, made a brush stroke and then tried to convert the layer. Here's the link to the crash log ... http://www.argfx.at/upload/kritacrash_01.zip SOFTWARE/OS VERSIONS Windows: 10 64-Bit 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 445830] New: Usually the app crashes when I select words individually in the program's text editor.
https://bugs.kde.org/show_bug.cgi?id=445830 Bug ID: 445830 Summary: Usually the app crashes when I select words individually in the program's text editor. Product: kdenlive Version: 20.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: gulhermeprado...@gmail.com Target Milestone: --- Created attachment 143779 --> https://bugs.kde.org/attachment.cgi?id=143779=edit Usually the app crashes when I select words individually in the program's text editor. Application: kdenlive (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-38-lowlatency x86_64 Windowing System: X11 Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: Usually the app crashes when I select words individually in the program's text editor. Something similar happens with Libre Office, however, in this last example, it happens more when I paste some text into the application. - Custom settings of the application: I don't remember doing any custom customization in any of the mentioned apps. The crash can be reproduced every time. -- Backtrace: Application: Kdenlive (kdenlive), signal: Segmentation fault [KCrash Handler] #4 0x7f82a677c9e0 in QWidget::window() const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f82a695456a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f82a6955eb9 in QWidgetTextControl::processEvent(QEvent*, QTransform const&, QWidget*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f82a694b31e in QWidgetTextControl::processEvent(QEvent*, QPointF const&, QWidget*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f82a6a63c0e in non-virtual thunk to QGraphicsTextItem::contextMenuEvent(QGraphicsSceneContextMenuEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f82a6a70d4a in QGraphicsItem::sceneEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f82a6a70ef8 in QGraphicsTextItem::sceneEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f82a6a94772 in QGraphicsScene::contextMenuEvent(QGraphicsSceneContextMenuEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f82a6aa6a88 in QGraphicsScene::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f82a6752783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f82a5c627ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f82a6ac5fdd in QGraphicsView::contextMenuEvent(QContextMenuEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f82a67955de in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f82a6843b32 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f82a5c6252b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f82a6752772 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f82a675ab01 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f82a5c627ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f82a67afad4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f82a67b2615 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f82a6752783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f82a5c627ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f82a6047b13 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #27 0x7f82a601ce2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #28 0x7f8291aa6a6e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #29 0x7f829c0de8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f829c131d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f829c0dc023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f82a5cbc204 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f82a5c6111b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f82a69646d2 in QDialog::exec() () from
[KOpeningHours] [Bug 445785] Add correction for Russian statements
https://bugs.kde.org/show_bug.cgi?id=445785 --- Comment #4 from Volker Krause --- (In reply to cal030 from comment #3) > I will look for actual examples. As I work with Osmose and when I encounter > those examples, can I correct them right away and send you a proposed UT, or > do you want to see them in live OSM data? That's perfectly fine, I just need something to actually test this with, doesn't need to be in OSM. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 445829] screen sharing on Plasma Wayland on Nixos unstable does not work
https://bugs.kde.org/show_bug.cgi?id=445829 p3dima...@hotmail.it changed: What|Removed |Added CC||p3dima...@hotmail.it -- You are receiving this mail because: You are watching all bug changes.
[KOpeningHours] [Bug 445824] Combine same day ranges
https://bugs.kde.org/show_bug.cgi?id=445824 Volker Krause changed: What|Removed |Added Assignee|vkra...@kde.org |fa...@kde.org Component|general |normalization -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 445829] New: screen sharing on Plasma Wayland on Nixos unstable does not work
https://bugs.kde.org/show_bug.cgi?id=445829 Bug ID: 445829 Summary: screen sharing on Plasma Wayland on Nixos unstable does not work Product: xdg-desktop-portal-kde Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: p3dima...@hotmail.it Target Milestone: --- SUMMARY As reported on https://github.com/NixOS/nixpkgs/issues/145174 screen sharing on Plasma Wayland on Nixos unstable does not work. STEPS TO REPRODUCE 1. Start plasma wayland session 2. Start OBS 3. Try to capture screen OBSERVED RESULT Nothing is captured and no dialog asking for screen/windoes to capture appears SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.1 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 445828] New: Activities Bar widget shows broken text when panel gets thinner
https://bugs.kde.org/show_bug.cgi?id=445828 Bug ID: 445828 Summary: Activities Bar widget shows broken text when panel gets thinner Product: frameworks-kactivities Version: 5.88.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: saif1...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 143778 --> https://bugs.kde.org/attachment.cgi?id=143778=edit Activity Bar text corruption SUMMARY Please see screenshot, bug is self described. STEPS TO REPRODUCE 1. Add the "Activity Bar" widget to a Panel, with a few activities created. Edit Panel and reduce its width, it is very early that Activities text gets broken like in the screenshot, and text becomes unreadable. OBSERVED RESULT See attachment EXPECTED RESULT Text should be readable with font size that adjusts to the panel size SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i7-10700KF CPU @ 3.80GHz Memory: 31,3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435415] On NixOS, notifications, OSDs, and KRunner appear in task manager and steal focus
https://bugs.kde.org/show_bug.cgi?id=435415 p3dima...@hotmail.it changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445827] New: Cannot navigate to next picture with arrow key if an unnamed face is displayed
https://bugs.kde.org/show_bug.cgi?id=445827 Bug ID: 445827 Summary: Cannot navigate to next picture with arrow key if an unnamed face is displayed Product: digikam Version: 7.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Preview-Image Assignee: digikam-bugs-n...@kde.org Reporter: nicoj...@free.fr Target Milestone: --- STEPS TO REPRODUCE 1. preview pictures with tagged people 2. display the faces/regions 3. navigate between pictures using arrow keys OBSERVED RESULT If there is an unnamed people in a picture, the focus will be automatically set on the text string of the label to name that person, so the arrow keys won't navigate between picture anymore but will move the cursor in the text. EXPECTED RESULT Arrows should still navigate to the next/previous picture (? or maybe is it done on purpose, a "face workflow" ?) SOFTWARE/OS VERSIONS macOS: 10.15.7 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445826] New: after undoing rename, dolphin view doesn't change
https://bugs.kde.org/show_bug.cgi?id=445826
Bug ID: 445826
Summary: after undoing rename, dolphin view doesn't change
Product: dolphin
Version: 21.04.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: glyphi...@gmail.com
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
In Dolphin, when you rename an item (file, folder, etc.) in a directory, the
item's icon or row may move to a different position based on the directory's
Sort By. If there are too many items to fit in the Dolphin window, when you
rename the item and its position changes, Dolphin's view changes to show the
file's new position. When you undo the rename, the item moves back to its
original position; however, Dolphin's view doesn't change -- the item is no
longer visible.
STEPS TO REPRODUCE
1. Run these commands:
```
mkdir tmp
cd tmp
for i in {1..20}; do touch "$i"; done
dolphin .
```
2. In the Dolphin window, sort by Name
3. If necessary, reduce the size of the Dolphin window until not all the files
are visible (i.e. the scrollbar appears)
4. Rename 1 to 21
5. Undo
OBSERVED RESULT
After 3, Dolphin view moved from the top of the directory to the bottom, but
after 4, view stayed at the bottom.
EXPECTED RESULT
After 4, Dolphin view should have returned to the top of the directory.
SOFTWARE/OS VERSIONS
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
Same behavior occurs in both Details view and Icons view.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-baloo] [Bug 445825] New: Baloo indexer gives more priority to content rather than file name
https://bugs.kde.org/show_bug.cgi?id=445825 Bug ID: 445825 Summary: Baloo indexer gives more priority to content rather than file name Product: frameworks-baloo Version: 5.88.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: saif1...@gmail.com Target Milestone: --- Created attachment 143777 --> https://bugs.kde.org/attachment.cgi?id=143777=edit Strange results SUMMARY As you can see in the picture, the results from Baloo are completely irrelevant to a first impression. It seems it is currently giving priority to weight based on the file contents rather than on the file name. For a further discussion and context, this reddit post can help: https://www.reddit.com/r/kde/comments/qwxmje/how_can_i_do_so_kde_file_search_brings_the/ in which t his Bug originated STEPS TO REPRODUCE Te reproduce it is tricky, as we would need specific files that contain keywords that we search for, in this case, it will happen than when searching for these keywords, the files containing them appear first, and the files that actually have these keywords on the file name, never show up, which is the assumed default. Check the image. OBSERVED RESULT In the picture, you can see the keyword being search brings very strange results Of course disabling "Content Index" solves it, but it is not an answer or a solution. Content Index is important but should not be first, IMHO. Also, disabling Content Index in KDE does not work well. User needs to disable, purge, logout and re-enable baloo for the changes to take effect. But this would be a separate issue. EXPECTED RESULT The first results should always be files whose filename contain the searched keyword SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.3 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION X11, EndeavourOS -- You are receiving this mail because: You are watching all bug changes.
[KOpeningHours] [Bug 445824] New: Combine same day ranges
https://bugs.kde.org/show_bug.cgi?id=445824 Bug ID: 445824 Summary: Combine same day ranges Product: KOpeningHours Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: vkra...@kde.org Reporter: cal...@outlook.com Target Milestone: --- Consider this actual value (multiple roads in Los Angeles): Mo-Fr 05:00-09:00; Mo-Fr 16:00-19:00; Mo-Fr 00:00-05:00; Mo-Fr 09:00-16:00; Mo-Fr 19:00-00:00; Sa-Su For insane values like these, it would be helpful if the ranges were (1) sorted and (2) combined: (1) sorted Mo-Fr 00:00-05:00,05:00-09:00,09:00-16:00,16:00-19:00,19:00-00:00; Sa-Su (2.a) combined: Mo-Fr 00:00-24:00; Sa-Su Note, I see a lot of strange examples with overlapping time ranges, suggesting editor may have missed day specifier. Do not combine times automatically if there is an overlap (too suspicious), for example: 10:00-13:00,12:00-15:00 (2.b) combined as a special case: 24/7 This is nice-to-have and probably hard to implement - setting a lower severity. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 441376] Extracting archives doesn't work
https://bugs.kde.org/show_bug.cgi?id=441376 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #12 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/krusader/-/merge_requests/73 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 445823] New: Get New [Stuff] window doesn't actually sort by Downloads when asked to
https://bugs.kde.org/show_bug.cgi?id=445823 Bug ID: 445823 Summary: Get New [Stuff] window doesn't actually sort by Downloads when asked to Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: random1123581...@protonmail.com Target Milestone: --- SUMMARY The Get New [Stuff] window that lets you install user-uploaded themes, scripts and widgets doesn't actually 'Show most downloaded first' when the option is ticked. Overall the items at the top are sorted by the most downloads, but there are some sorting errors at times, where an item with less users is shown above the item with more users. See screenshot. STEPS TO REPRODUCE 1. Go to any Get New [Stuff] window. 2. Sort by 'Show most downloaded first' OBSERVED RESULT The items are not always sorted by number of downloads EXPECTED RESULT The items are sorted by number of downloads SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION I don't know which category to file this in, so I've filed it in kde. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 445820] ConTeXt: Support highlighting for TABLEs
https://bugs.kde.org/show_bug.cgi?id=445820 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/275 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 445818] ConTeXt: Allow for nested verbatim
https://bugs.kde.org/show_bug.cgi?id=445818 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/275 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 445822] New: KMail currently at 5.18.3, but the bug reporter only has options upto 5.16.3
https://bugs.kde.org/show_bug.cgi?id=445822 Bug ID: 445822 Summary: KMail currently at 5.18.3, but the bug reporter only has options upto 5.16.3 Product: bugs.kde.org Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: random1123581...@protonmail.com CC: she...@kde.org Target Milestone: --- SUMMARY The summary above STEPS TO REPRODUCE 1. Try filing a bug in the KMail2 category OBSERVED RESULT There is no option to choose the current stable version 5.18.3 EXPECTED RESULT It should be updated to show the latest releases. SOFTWARE/OS VERSIONS n/a ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445821] New: KMail 5.18.3: Akonadi error 'Details' button doesn't work
https://bugs.kde.org/show_bug.cgi?id=445821 Bug ID: 445821 Summary: KMail 5.18.3: Akonadi error 'Details' button doesn't work Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: random1123581...@protonmail.com Target Milestone: --- SUMMARY Crash Akonadi (the way I did it: delete /home/user/.local/share/akonadi/ CAUTION: I still haven't found a way to fix Akonadi.) KMail will outright crash the first time, the next time it'll show a 'The Akonadi personal information management service is not operational', with a 'Details' button below it. Clicking on the 'Details' button does absolutely nothing. STEPS TO REPRODUCE 1. Somehow do stuff to Akonadi that prevents it from working 2. Run KMail 3. Click on the 'Details' button under the 'The Akonadi personal information management service is not operational' error message OBSERVED RESULT Nothing happens EXPECTED RESULT The error details should be shown SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445812] Renaming a custom default profile removes default-flag from this profile
https://bugs.kde.org/show_bug.cgi?id=445812 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #1 from Ahmad Samir --- This was fixed in master a while ago, should be in 21.12. To confirm, after step 6, close the current Konsole window, then open a new one, the renamed profile should be the default as expected. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439159] "Add widgets..." and "Show alternatives..." options from context menu stop working after manually restarting plasmashell process
https://bugs.kde.org/show_bug.cgi?id=439159 Patrick Silva changed: What|Removed |Added CC||deresi...@protonmail.ch --- Comment #16 from Patrick Silva --- *** Bug 445796 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445796] Show alternatives button does nothing
https://bugs.kde.org/show_bug.cgi?id=445796 --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 439159 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 445068] Some errors were found in the document
https://bugs.kde.org/show_bug.cgi?id=445068 --- Comment #3 from Albert Astals Cid --- To debug this you probably need to compile poppler [ https://poppler.freedesktop.org/ ] and debug it with gdb to figure out what is causing this, unless you're a C++ developer this is mostly outside things you can actually do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445796] Show alternatives button does nothing
https://bugs.kde.org/show_bug.cgi?id=445796 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 443647 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443647] "Add widgets" and "Show alternatives" sometimes stop working
https://bugs.kde.org/show_bug.cgi?id=443647 Patrick Silva changed: What|Removed |Added CC||deresi...@protonmail.ch --- Comment #4 from Patrick Silva --- *** Bug 445796 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443717] [workspace] Saving a new workspace doesn't appear in "Workspaces list", but in 'Windows layout" list.
https://bugs.kde.org/show_bug.cgi?id=443717 --- Comment #6 from David REVOY --- Thank you Bug Janitor for the reminder, good bot. Good news: I confirm this bug doesn't affect current 5.0beta/Krita Plus, I just tested. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #4 from Jonathan Kamens --- I will leave it to you whether to reopen this bug or just ignore the fact that the claims you made about it are directly at odds with my actual experience in the app. Whether you choose to actually listen to one of your users who has been developing open-source software for more than 30 years and therefore probably knows how to accurately describe a bug is your choice. :shrug: -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #3 from Jonathan Kamens --- I searched and did not find other bugs before filing this one. When I ignore a face in 7.3.0 the tag does not get recreated. You claim that it was impossible to delete the tag in 7.3.0 and yet I assure you that I deleted it and it is not there, so there is presumably a way to delete it of which you are unaware. I believe it happened to me in the tag manager, if that helps. -- You are receiving this mail because: You are watching all bug changes.
[KOpeningHours] [Bug 445785] Add correction for Russian statements
https://bugs.kde.org/show_bug.cgi?id=445785 --- Comment #3 from cal...@outlook.com --- Thank you for the quick change! I will look for actual examples. As I work with Osmose and when I encounter those examples, can I correct them right away and send you a proposed UT, or do you want to see them in live OSM data? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 445820] New: ConTeXt: Support highlighting for TABLEs
https://bugs.kde.org/show_bug.cgi?id=445820 Bug ID: 445820 Summary: ConTeXt: Support highlighting for TABLEs Product: frameworks-syntax-highlighting Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: jackhill3...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- Created attachment 143776 --> https://bugs.kde.org/attachment.cgi?id=143776=edit TABLE environment next to an xtable environment. The TABLE commands should be highlighted the same as the xtable commands. TABLEs use commands that are equivalent to start/stop pairs and so these commands should be highlighted the same as start/stop pairs. The commands equivalent to "\start()" are: \bTABLEhead \bTABLEnext \bTABLEbody \bTABLEfoot \bTR \bTD and the commands equivalent to "\stop()" are: \eTABLEhead \eTABLEnext \eTABLEbody \eTABLEfoot \eTR \eTD -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 --- Comment #2 from Maik Qualmann --- I have just tested it again, even in digiKam-7.3.0 the ignored tag could no longer be deleted. Maik -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445819] New: Discover crashes when I open the description page of a flatpak while it is removed
https://bugs.kde.org/show_bug.cgi?id=445819 Bug ID: 445819 Summary: Discover crashes when I open the description page of a flatpak while it is removed Product: Discover Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. open Discover 2. click on 'Applications' in the sidebar 3. find an installed flatpak and click on its 'Remove' button 4. click on the flatpak app while Discover removes it OBSERVED RESULT Discover crashes EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: Wayland Thread 13 (Thread 0x7f904e093640 (LWP 39212)): #0 0x7f905d9aa89c in read () at /usr/lib/libc.so.6 #1 0x7f905c70d8d5 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f905c7616cd in () at /usr/lib/libglib-2.0.so.0 #3 0x7f905c70abc1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f905c70ac12 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f905c73bce1 in () at /usr/lib/libglib-2.0.so.0 #6 0x7f905d1b0259 in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f905d9b95e3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f904fd08640 (LWP 39211)): #0 0x7f905c75b504 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f905c70d082 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f905c761646 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f905c70abc1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f905dfb109f in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f9044000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f905df56d6c in QEventLoop::exec(QFlags) (this=this@entry=0x7f904fd07a60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #6 0x7f905dd6be52 in QThread::exec() (this=this@entry=0x564aae197040) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f905ebfc509 in QQmlThreadPrivate::run() (this=0x564aae197040) at /usr/src/debug/qtdeclarative/src/qml/qml/ftw/qqmlthread.cpp:155 #8 0x7f905dd6d02f in QThreadPrivate::start(void*) (arg=0x564aae197040) at thread/qthread_unix.cpp:329 #9 0x7f905d1b0259 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f905d9b95e3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f9033346640 (LWP 39221)): #0 0x7f905c75b504 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f905c761799 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f905c70abc1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f905dfb109f in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f9024000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f905df56d6c in QEventLoop::exec(QFlags) (this=this@entry=0x7f9033345a80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #5 0x7f905dd6be52 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f905dd6d02f in QThreadPrivate::start(void*) (arg=0x564aae26c920) at thread/qthread_unix.cpp:329 #7 0x7f905d1b0259 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f905d9b95e3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f900d24f640 (LWP 39234)): #0 0x7f905d9aa89c in read () at /usr/lib/libc.so.6 #1 0x7f905c70d8d5 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #2 0x7f905c7616cd in () at /usr/lib/libglib-2.0.so.0 #3 0x7f905c70abc1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f905dfb109f in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f8fe0752050, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f905df56d6c in QEventLoop::exec(QFlags) (this=this@entry=0x7f900d24ea80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #6 0x7f905dd6be52 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f905dd6d02f in QThreadPrivate::start(void*) (arg=0x564ab26536e0) at thread/qthread_unix.cpp:329 #8 0x7f905d1b0259 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f905d9b95e3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f9055c1b640 (LWP 39210)): #0 0x7f905d1bc8ca in __futex_abstimed_wait_common64 () at /usr/lib/libpthread.so.0 #1 0x7f905d1b6270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #2 0x7f9055ffa32c in () at /usr/lib/dri/i965_dri.so #3 0x7f9055ff9d88 in () at /usr/lib/dri/i965_dri.so #4 0x7f905d1b0259 in
[digikam] [Bug 445817] "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.4.0 CC||metzping...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Maik Qualmann --- 1.) There are already bug reports on this. 2.) Already fixed in the pre-release of digiKam-7.4.0 3.) If you ignore a face, the tag will be generated again. For the DB it is still not good that the old tag was deleted. Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 445818] New: ConTeXt: Allow for nested verbatim
https://bugs.kde.org/show_bug.cgi?id=445818 Bug ID: 445818 Summary: ConTeXt: Allow for nested verbatim Product: frameworks-syntax-highlighting Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: jackhill3...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- Created attachment 143775 --> https://bugs.kde.org/attachment.cgi?id=143775=edit Highlighting stops after first \stopverbatim Currently, the snippet \startverbatim a \startverbatim b \stopverbatim c \stopverbatim will incorrectly stop highlighting after the first \stopverbatim. The highlighting should continue after the first \stopverbatim. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445817] New: "Ignored" under "People" can be deleted, can't be restored
https://bugs.kde.org/show_bug.cgi?id=445817 Bug ID: 445817 Summary: "Ignored" under "People" can be deleted, can't be restored Product: digikam Version: 7.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: j...@kamens.us Target Milestone: --- I was under the apparently mistaken impression that tagging faces with the label "Ignored" would cause them to be ignored. That didn't work, though, all it apparently did was create a person named "Ignored" over and above the actual "Ignored" category listed under people (FYI: the reason I was trying to do this is because there's no way to tag a face as ignored when looking at unconfirmed faces under a person, which is a significant UX issue in and of itself). I needed to clean this up, i.e., to remove the "Ignored" person, so I went to delete that tag in the tag manager, but somehow managed to delete both it and the _actual_, correct, "Ignored" tag that actually causes faces to be ignored. Now I can't find any way to get it back. I am able to mark faces as ignored by clicking the appropriate button when looking at Unknown faces, but I can't see which faces have been ignored because there's no "Ignored" under people and I can't find a way to restore it. I guess this is actually lots of different workflow issues all wrapped up in one: 1. There should be a way to mark faces ignored from any people view, not just from the Unknown view. 2. It should not be possible to delete the canonical "Ignored" tag. 3. It should be possible to restore the canonical "Ignored" tag if it somehow gets deleted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445816] Make thumbnails (previews) of copied images bigger in clipboard applet
https://bugs.kde.org/show_bug.cgi?id=445816 postix changed: What|Removed |Added Attachment #143773|0 |1 is obsolete|| --- Comment #2 from postix --- Created attachment 143774 --> https://bugs.kde.org/attachment.cgi?id=143774=edit Screenshot: Plasma 5.23.3 clipboard with previews of copied images -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445816] Make thumbnails (previews) of copied images bigger in clipboard applet
https://bugs.kde.org/show_bug.cgi?id=445816 --- Comment #1 from postix --- Created attachment 143773 --> https://bugs.kde.org/attachment.cgi?id=143773=edit Screenshot: Plasma 5.23.3 clipboard with previews of copied images For comparison: how Plasma currently displays copies images. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445644] timeline mess after re-open
https://bugs.kde.org/show_bug.cgi?id=445644 --- Comment #7 from Shachar Shemesh --- One last note: I used the following command to downgrade to kdenlive 21.08.2: sudo flatpak update --commit=ce0a122a8f5f6948991c3dffcb98e56559a2795ab608997021502f4bde076c1b org.kde.kdenlive The problem doesn't seem to happen there. It seems this is new for 21.08.3. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 340646] Fix issues reported by Coverity scan
https://bugs.kde.org/show_bug.cgi?id=340646
--- Comment #133 from Oliver Kellogg ---
Git commit 788fcb8b4f830ca617a4296442ac22c8c057f737 by Oliver Kellogg.
Committed on 20/11/2021 at 15:23.
Pushed by okellogg into branch 'master'.
https://scan.coverity.com/projects/3327 Coverity fixes listed by CID :
268381 Use after free in umlwidgets/diagramproxywidget.cpp
- In function slotMenuSelection case ListPopupMenu::mt_State_Diagram,
if `ok` is true after the do-while loop then
- assign d->view()->umlScene() to local variable `scene` before call
to UMLApp::app()->executeCommand(d);
- at calls to setDiagramLink and setWidgetLink use local `scene` in
lieu of d->view()->umlScene().
Reason: `d` may have been invalidated by the executeCommand call.
364153 Uninitialized scalar variable in dialogs/pages/
selectoperationpage.cpp
- In copy constructor initialize m_enableAutoIncrement to false.
- In function slotAutoIncrementChecked assign `state` to
m_enableAutoIncrement.
- As a related fix, in dialogs/selectoperationdialog.cpp function
slotAutoIncrementChecked assign `state` to m_enableAutoIncrement.
364158 Resource leak in docgenerators/docbookgeneratorjob.cpp
- In function xsltprocExternalEntityLoader split the statement
if (newURL != NULL && defaultEntityLoader != NULL) {
into two statements
if (newURL != NULL) {
if (defaultEntityLoader != NULL) {
such that xmlFree(newURL) is called regardless of the second
condition.
Thanks to Ralf H. for updating https://github.com/rhabacker/umbrello
M +4-2umbrello/dialogs/pages/selectoperationpage.cpp
M +2-1umbrello/dialogs/selectoperationdialog.cpp
M +11 -9umbrello/docgenerators/docbookgeneratorjob.cpp
M +4-3umbrello/umlwidgets/diagramproxywidget.cpp
https://invent.kde.org/sdk/umbrello/commit/788fcb8b4f830ca617a4296442ac22c8c057f737
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 445644] timeline mess after re-open
https://bugs.kde.org/show_bug.cgi?id=445644 --- Comment #6 from Shachar Shemesh --- Forgot to add: Running Kubuntu 21.10 with KDEnlive installed from flatpak. Version 21.08.3. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445815] Discover crashes on every start
https://bugs.kde.org/show_bug.cgi?id=445815 --- Comment #2 from Malte S. Stretz --- Well, looks like Discover still crashes when I click the "Installed" category/button on the left side. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445816] Make thumbnails (previews) of copied images bigger in clipboard applet
https://bugs.kde.org/show_bug.cgi?id=445816 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445644] timeline mess after re-open
https://bugs.kde.org/show_bug.cgi?id=445644 Shachar Shemesh changed: What|Removed |Added CC||shac...@shemesh.biz --- Comment #5 from Shachar Shemesh --- It happens to me even when the speeded videos are on top. It also happens with non-speeded videos. PNG image clips keep reverting to 5 seconds long. Videos show fine, preview fine, but when rendered behave shifted. Close and reopen, and the timeline looks like the rendered video. It's driving me insane. This is a highly critical bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445816] New: Make thumbnails (previews) of copied images bigger in clipboard applet
https://bugs.kde.org/show_bug.cgi?id=445816 Bug ID: 445816 Summary: Make thumbnails (previews) of copied images bigger in clipboard applet Product: plasmashell Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu Target Milestone: 1.0 Created attachment 143772 --> https://bugs.kde.org/attachment.cgi?id=143772=edit Screenshot: Windows 10 clipboard with preview of copied image SUMMARY It would be useful if thumbnails of copied images in the clipboard were bigger to better recognize and distinguish them. Please compare it to the screenshot attached. See also the discussion on https://www.reddit.com/r/kde/comments/qxja75/is_there_a_way_to_make_clipboard_image_previews/ -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445815] Discover crashes on every start
https://bugs.kde.org/show_bug.cgi?id=445815 --- Comment #1 from Malte S. Stretz --- I updated the flatpak packages via the CLI and now Discover doesn't crash anymore. :~ $ flatpak update Looking for updates… ID BranchOp RemoteDownload 1. [✓] org.chromium.Chromium.Codecsstableu flathub 322.0 kB / 1.1 MB 2. [✓] org.chromium.Chromium.Localestableu flathub 1.5 kB / 112.8 kB 3. [✓] org.freedesktop.Platform.GL.default 20.08 u flathub 3.9 MB / 106.4 MB 4. [✓] org.freedesktop.Platform.Locale 20.08 u flathub 103.5 kB / 322.3 MB 5. [✓] org.freedesktop.Platform.VAAPI.Intel20.08 u flathub 374.3 kB / 11.6 MB 6. [✓] org.chromium.Chromium stableu flathub88.3 MB / 117.9 MB 7. [✓] org.freedesktop.Platform20.08 u flathub 8.2 MB / 268.6 MB Updates complete. :~ $ plasma-discover kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86): This returns 1 when using Qt HiDPI scaling. adding empty sources model QStandardItemModel(0x55de2b445510) org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" Failed to refresh appstream metadata for flathub : "While pulling appstream2/x86_64 from remote flathub: No such metadata object 9177f9761b21c3c153e23870c7f9bb29ec56fe025194d2c020836bffcac8d00d.commit" qml: message: While pulling appstream2/x86_64 from remote flathub: No such metadata object 9177f9761b21c3c153e23870c7f9bb29ec56fe025194d2c020836bffcac8d00d.commit -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445815] New: Discover crashes on every start
https://bugs.kde.org/show_bug.cgi?id=445815 Bug ID: 445815 Summary: Discover crashes on every start Product: Discover Version: 5.23.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: m...@apache.org CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- SUMMARY Whenever I start Discover, it crashes. It actually nags me that there are updates available though all apt packages are up-to-date. Looks like it happens in the Flatpak backend, at least I was asked to install the debug symbols. When I start it from the shell the output is: kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86): This returns 1 when using Qt HiDPI scaling. adding empty sources model QStandardItemModel(0x560d75787ef0) org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" error: QSnapdRequest::ConnectionFailed "Unable to connect snapd socket: No such file or directory" Failed to refresh appstream metadata for flathub : "While pulling appstream2/x86_64 from remote flathub: No such metadata object 9177f9761b21c3c153e23870c7f9bb29ec56fe025194d2c020836bffcac8d00d.commit" qml: message: While pulling appstream2/x86_64 from remote flathub: No such metadata object 9177f9761b21c3c153e23870c7f9bb29ec56fe025194d2c020836bffcac8d00d.commit 29 -- exe=/usr/bin/plasma-discover 13 -- platform=xcb 11 -- display=:0 24 -- appname=plasma-discover 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=10705 18 -- appversion=5.23.3 21 -- programname=Discover 63 -- bugaddress=https://bugs.kde.org/enter_bug.cgi?product=Discover 30 -- productname=discover/discover 12 -- startupid=0 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = plasma-discover path = /usr/bin pid = 10705 KCrash: Arguments: /usr/bin/plasma-discover Unable to start Dr. Konqi Re-raising signal for core dump handling. Aborted (core dumped) STEPS TO REPRODUCE 1. Start plasma-discover OBSERVED RESULT The GUI shortly pops up and then it crashes EXPECTED RESULT Don't crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Application: plasma-discover (5.23.3) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.3 [CoredumpBackend] -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted [New LWP 10736] [New LWP 10711] [New LWP 10713] [New LWP 10710] [New LWP 10709] [New LWP 10714] [New LWP 10708] [New LWP 10723] [New LWP 10725] [New LWP 10717] [New LWP 10724] [New LWP 10722] [New LWP 10721] [New LWP 10729] [New LWP 10750] [New LWP 10720] [New LWP 10755] [New LWP 10719] [New LWP 10718] [New LWP 10716] [New LWP 10715] [New LWP 10712] [New LWP 10707] [New LWP 10705] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `plasma-discover'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f33221ca700 (LWP 10736))] __preamble__ [Current thread is 1 (Thread 0x7f33221ca700 (LWP 10736))] Thread 24 (Thread 0x7f3385ac0bc0 (LWP 10705)): [KCrash Handler] #4 FlatpakBackend::findSource (this=this@entry=0x560d75980310, installation=installation@entry=0x7f3334019210, origin=...) at ./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:113 #5 0x7f33503d5ffe in FlatpakBackend::getAppForInstalledRef (this=0x560d75980310, installation=installation@entry=0x7f3334019210, ref=0x7f3314329690) at ./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:352 #6 0x7f33503d8f00 in FlatpakBackendoperator() (__closure=0x560d75a8d750, __closure=0x560d75a8d750) at ./libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:1276 #7 QtPrivate::FunctorCall, QtPrivate::List<>, void, FlatpakBackend::search(const AbstractResourcesBackend::Filters&):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #8 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #9 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x560d75a8d740, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #10 0x7f338b13a949 in
[yakuake] [Bug 443275] Slide effect is broken after the first toggling on wayland
https://bugs.kde.org/show_bug.cgi?id=443275 Loïc Grobol changed: What|Removed |Added CC||loic.gro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 445814] 'Fusion' style looks out of place in dark themes
https://bugs.kde.org/show_bug.cgi?id=445814 Antonio Rojas changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- The Fusion style is not developed by KDE, it is the default Qt style. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 445814] New: 'Fusion' style looks out of place in dark themes
https://bugs.kde.org/show_bug.cgi?id=445814 Bug ID: 445814 Summary: 'Fusion' style looks out of place in dark themes Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY The "Fusion" style in Settings -> Appearance -> Application Style looks too bright in dark themes. All other built-in styles (breeze, oxygen, ms windows 9x) play along with a dark theme, but Fusion just looks out of place, as it has very light gray boxes. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 445813] KDE proxy settings are not picked up by libproxy
https://bugs.kde.org/show_bug.cgi?id=445813 --- Comment #1 from Malte S. Stretz --- Duh. As so often, I found that part of the issue is actually sitting in front of the screen: libproxy picks up the KDE settings totally fine as long as (a) the additonal package is installed and (b) the `proxy` test tool is executed properly. The following command actually gives me the proper result (a full URL is required, not only a hostname): proxy <<< https://example.com Feel free to close this report but there are two things I noticed while debugging this: (a) That additional package is required. I think it would make sense to install it (at least via a recommends dependency) on KDE neon per default (b) While stracing and looking at the code I saw that `qtpaths` is called at some point and some cache is maintained based on the result, if any. On my machine there is a `qtpaths` executable available but it seems to be some kind of multiplexer which doesn't find its actual implementation, cf. below. I didn't modify any global Qt related configs, this a standard KDE neon in regards to that (though upgraded from 18.04 at some point). # qtpaths --paths GenericConfigLocation /usr/lib/qt5/bin/qtpaths: command not found qtpaths: could not find a Qt installation of '' -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445774] Terminal panel does not respect custom bash prompt consistently
https://bugs.kde.org/show_bug.cgi?id=445774 Patrick Silva changed: What|Removed |Added Summary|Terminal panel does not |Terminal panel does not |respect custom bash prompt |respect custom bash prompt ||consistently --- Comment #4 from Patrick Silva --- You are right. On my system sometimes I need to restart Dolphin a few times with Terminal panel already enabled. Accurate steps to reproduce: 1. add the following line to your ~/.bashrc file: export PS1='\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ' 2. save ~/.bashrc file 3. open Dolphin and open its Terminal panel by pressing F4 (Terminal panel respects the custom bash prompt as expected) 4. restart Dolphin 5. if Terminal panel is still respecting the custom bash prompt, restart Dolphin repeatedly. At some point the custom bash prompt will not be respected. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 445813] New: KDE proxy settings are not picked up by libproxy
https://bugs.kde.org/show_bug.cgi?id=445813 Bug ID: 445813 Summary: KDE proxy settings are not picked up by libproxy Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: m...@apache.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY libproxy has support for KDE5/KF5 since 2016 or so. But on KDE neon it seems to ignore the KDE proxy settings whatever I do. The actual issue which made me look into this is because the Chromium flatpak package doesn't pick up my proxy settings properly even though I have the proper portal installed. I am not sure if that portal actually uses libproxy but the KDE neon libproxy is "broken" anyway. I have the bad feeling that this is some kind of rabbit hole and the bug is actually within the Debian libproxy package. But since I use KDE neon and you probably have better means of debugging this and better connections to Debian/Ubuntu than me, I start here. The reason I think this issue might be in the Debian packages are * There exists and additional package is called "libproxy1-plugin-kconfig" and its description was not updated for quite a while (still talks about KDE 4 only) * The version is not the newest but there are no relevant changes in https://github.com/libproxy/libproxy/compare/0.4.15...0.4.17?diff=split#diff-3dbb675e161f4d417c91967f12d5a0040becc75023d2931c890cce78d64e6eac (at least regarding the file libproxy/modules/config_kde.cpp) * Official support for KDE5/KF5 is already present in the version installed Side note: Shouldn't KDE neon install libproxy1-plugin-kconfig per default? (Assuming it works of course.) STEPS TO REPRODUCE 1. Install the libproxy tools and KConfig backend via `sudo apt install libproxy-tools libproxy1-plugin-kconfig` 2. Configure a proxy in KDE, for simplicity: 2.1 Use manually specific proxy configuration 2.2 HTTP Proxy: 127.0.0.1 Port: 8080 2.3 [x] Use this proxy server for all protocols 3. Open Konsole 3.1 Execute `proxy <<< example.org` OBSERVED RESULT Output is direct:// EXPECTED RESULT It should probably be something like http://127.0.0.1:8080 SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-40-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 19.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445812] New: Renaming a custom default profile removes default-flag from this profile
https://bugs.kde.org/show_bug.cgi?id=445812 Bug ID: 445812 Summary: Renaming a custom default profile removes default-flag from this profile Product: konsole Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: g...@netcologne.de Target Milestone: --- Hello, I have created a customized konsole profile and set this as default profile. Later I renamed this profile. This did remove the default flag from my profile. So when starting konsole the "Default [read-only]" profile was used instead of mine. STEPS TO REPRODUCE 1. Create your own profile 2. Set it as default profile 3. to be sure: close all konsole windows (this might not be necessary) 4. open a new konsole window 5. open the profile manager 6. edit your own profile and rename it 7. open a new window (in my case by using a hotkey that is configured for konsole) OBSERVED RESULT The new konsole windows is using the standard "Default [read-only]" profile. When opening the profile manager you see that the "Default [read-only]" profile is set as default again. EXPECTED RESULT The konsole window should continue to use my profile. (My profile should still be set as default profile.) SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445774] Terminal panel does not respect custom bash prompt
https://bugs.kde.org/show_bug.cgi?id=445774 --- Comment #3 from Pranav Karande --- Created attachment 143771 --> https://bugs.kde.org/attachment.cgi?id=143771=edit Video showing the problem -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 444330] Attaching a file to bug report via Chromium-based browsers + KDE file dialog causes tab crash
https://bugs.kde.org/show_bug.cgi?id=444330 Patrick Silva changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Patrick Silva --- I'm unable to reproduce on neon unstabe. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 --- Comment #37 from Bharadwaj Raju --- It is going to be redone in QML and brought back. The flip and cover switch effects even have am MR in progress. Adding comments here is not helping. Either write it, or wait and don't spam what basically everyone has already said again and again. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445774] Terminal panel does not respect custom bash prompt
https://bugs.kde.org/show_bug.cgi?id=445774 Pranav Karande changed: What|Removed |Added CC||pranav.3...@gmail.com --- Comment #2 from Pranav Karande --- I am facing same issue but it appears to occur only if terminal panel is already enabled and then dolphin is opened i.e. when dolphin is restarted after opening the panel. If the panel is opened by pressing F4 after launching dolphin, it respects the custom prompt. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376731] Odd numbering and listing of desktops.
https://bugs.kde.org/show_bug.cgi?id=376731 Kishore Gopalakrishnan changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #11 from Kishore Gopalakrishnan --- Still reproducible with Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443410] Please restore the Desktop Cube switching effect
https://bugs.kde.org/show_bug.cgi?id=443410 Laosom changed: What|Removed |Added CC||dellfirmw...@gmail.com --- Comment #36 from Laosom --- Please rewrite it in QML and restore the dropped effects. There are too many regressions in Plasma since 5.21. The best Linux desktop still, but please listen to the fans. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445811] Weird icons in places panel of Dolphin
https://bugs.kde.org/show_bug.cgi?id=445811 Pranav Karande changed: What|Removed |Added CC||pranav.3...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445811] Weird icons in places panel of Dolphin
https://bugs.kde.org/show_bug.cgi?id=445811 --- Comment #2 from Pranav Karande --- Created attachment 143770 --> https://bugs.kde.org/attachment.cgi?id=143770=edit observed icons when selected -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445811] Weird icons in places panel of Dolphin
https://bugs.kde.org/show_bug.cgi?id=445811 --- Comment #1 from Pranav Karande --- Created attachment 143769 --> https://bugs.kde.org/attachment.cgi?id=143769=edit observed icons -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445811] New: Weird icons in places panel of Dolphin
https://bugs.kde.org/show_bug.cgi?id=445811 Bug ID: 445811 Summary: Weird icons in places panel of Dolphin Product: dolphin Version: 21.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: pranav.3...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 143768 --> https://bugs.kde.org/attachment.cgi?id=143768=edit Expected icons SUMMARY The places tab in dolphin has the solid blue icon for folders and they become white on selection. OBSERVED RESULT Shown in observed.png and observed_selected.png EXPECTED RESULT Shown in expected.png SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION The wrong icons started appearing ever since Dolphin an updated to version 21.04.0 I think but I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445743] "The impossible happened: mutex is locked simultaneously by two threads" while using mutexes with priority inheritance and signals
https://bugs.kde.org/show_bug.cgi?id=445743 --- Comment #6 from Paul Floyd --- Unfortunately this doesn't seem to help on Linux. The problem seems to be that after the signal contender doesn't return to waiting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445810] Disk Quota icon should be updated in the system tray
https://bugs.kde.org/show_bug.cgi?id=445810 --- Comment #1 from Patrick Silva --- Created attachment 143767 --> https://bugs.kde.org/attachment.cgi?id=143767=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445810] New: Disk Quota icon should be updated in the system tray
https://bugs.kde.org/show_bug.cgi?id=445810 Bug ID: 445810 Summary: Disk Quota icon should be updated in the system tray Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Disk Quota icon was recently updated, but the old icon is still present in the system tray. Please see the attached screenshot. EXPECTED RESULT new Disk Quota icon in the system tray. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445809] Add left margin space to Menus without icons
https://bugs.kde.org/show_bug.cgi?id=445809 --- Comment #3 from Philip Murray --- Created attachment 143766 --> https://bugs.kde.org/attachment.cgi?id=143766=edit Dolphin right-click menu, no icons. Note more space at right of the arrows than left of the text. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445809] Add left margin space to Menus without icons
https://bugs.kde.org/show_bug.cgi?id=445809 --- Comment #2 from Philip Murray --- Created attachment 143765 --> https://bugs.kde.org/attachment.cgi?id=143765=edit Dolphin top menu, no icons. Note more space at right side than left. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445809] Add left margin space to Menus without icons
https://bugs.kde.org/show_bug.cgi?id=445809 --- Comment #1 from Philip Murray --- Also, right-click context menus have the same issue; the text is aligned too tightly to the left. It may be sufficient to just increase the left margin a bit, not necessarily equal to menus that have radio buttons. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425402] Application Dashboard doesn't cover Plasma panel on Wayland
https://bugs.kde.org/show_bug.cgi?id=425402 --- Comment #11 from Patrick Silva --- it's almost fixed on neon unstable. Sometimes the bug occurs after focusing a text box of a Xwayland app. 1. open this bug report with Opera internet browser running on Xwayland (I'm unable to reproduce with Firefox running on Xwayland) 2. click on the text box where we write comments 3. open Application Dashboard by clicking on its button and it will not cover the Plasma panel Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445809] New: Add left margin space to Menus without icons
https://bugs.kde.org/show_bug.cgi?id=445809 Bug ID: 445809 Summary: Add left margin space to Menus without icons Product: dolphin Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: philipihmur...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin & other applications, when icons are disabled in the menus, the position of the text is not consistently spaced from the left. Radio buttons still exist when icons are disabled & hence any menu with these are aligned further to the right than menus where there are no radio buttons (these are aligned very tightly to the left). STEPS TO REPRODUCE 1. System Settings > Application Style > Configure Icons and Toolbars > Show icons:L In menus (disable). 2. In Dolphin, view the left spacing of different menus. 3. Any menus that have a radio checkbox in them the menu options text is aligned to the right of them & any options with no radio buttons are aligned to the same point. 4. Any menus that do not have a radio checkbox the menu options text is aligned further to the left. 5. It would be nicer if the menus were consistently spaced from the left, i.e. provide an equal left margin on all menus. Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-9-amd64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4570 CPU @ 3.20GHz Memory: 7.7 GiB of RAM Graphics Processor: GeForce GTX 750 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442463] plasma crashes on startup in DBusMenuImporter::menu() while loading an SNI
https://bugs.kde.org/show_bug.cgi?id=442463 Nicolas Fella changed: What|Removed |Added CC||bo...@bori.org --- Comment #1 from Nicolas Fella --- *** Bug 441527 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441527] Plasma crashes in DBusMenuImporter::menu() after login
https://bugs.kde.org/show_bug.cgi?id=441527 Nicolas Fella changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 442463 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445516] Cache-related visual glitches when Plasma theme SVGs or Plasma Components are updated
https://bugs.kde.org/show_bug.cgi?id=445516 Konrad Materka changed: What|Removed |Added CC|mate...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 Fushan Wen changed: What|Removed |Added Version Fixed In||5.23.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 Fushan Wen changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |c0b8f6871e75bbc268165844ad5 |931a5441746daf10d9476409f34 |780f13a5f88ac |7263719ef6c63 --- Comment #23 from Fushan Wen --- Git commit 931a5441746daf10d9476409f347263719ef6c63 by Fushan Wen. Committed on 20/11/2021 at 13:17. Pushed by fusionfuture into branch 'Plasma/5.23'. systemtray: Check if a service is already added before processing QDBusReply Due to async nature of QDBusPendingReply, services could be already registered by QDBusServiceWatcher when the pending reply takes a long time to finish, so it's possible that QDBusServiceWatcher::serviceRegistered signal is emitted before the pending reply emits QDBusPendingCallWatcher::finished, which will make the same service added twice and crash plasmashell. We need to check if a service is already added in m_sniServices before processing registered items in QDBusReply. (cherry picked from commit c0b8f6871e75bbc268165844ad5780f13a5f88ac) M +3-1applets/systemtray/statusnotifieritemhost.cpp https://invent.kde.org/plasma/plasma-workspace/commit/931a5441746daf10d9476409f347263719ef6c63 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 Fushan Wen changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||c0b8f6871e75bbc268165844ad5 ||780f13a5f88ac Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #22 from Fushan Wen --- Git commit c0b8f6871e75bbc268165844ad5780f13a5f88ac by Fushan Wen. Committed on 20/11/2021 at 10:46. Pushed by fusionfuture into branch 'master'. systemtray: Check if a service is already added before processing QDBusReply Due to async nature of QDBusPendingReply, services could be already registered by QDBusServiceWatcher when the pending reply takes a long time to finish, so it's possible that QDBusServiceWatcher::serviceRegistered signal is emitted before the pending reply emits QDBusPendingCallWatcher::finished, which will make the same service added twice and crash plasmashell. We need to check if a service is already added in m_sniServices before processing registered items in QDBusReply. M +3-1applets/systemtray/statusnotifieritemhost.cpp https://invent.kde.org/plasma/plasma-workspace/commit/c0b8f6871e75bbc268165844ad5780f13a5f88ac -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445808] The area to set Keyboard shortcuts is not entirely visible when I open the window to configure a desktop effect
https://bugs.kde.org/show_bug.cgi?id=445808 --- Comment #1 from Patrick Silva --- Created attachment 143764 --> https://bugs.kde.org/attachment.cgi?id=143764=edit screen recording -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445808] New: The area to set Keyboard shortcuts is not entirely visible when I open the window to configure a desktop effect
https://bugs.kde.org/show_bug.cgi?id=445808 Bug ID: 445808 Summary: The area to set Keyboard shortcuts is not entirely visible when I open the window to configure a desktop effect Product: systemsettings Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_effects Assignee: kwin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Every time I open the window to configure a desktop effect, I need to resize the window manually to make the area to set keyboard shortcuts on bottom entirely visible. STEPS TO REPRODUCE 1. open Desktop Effects KCM 2. click on the button to configure an effect 3. OBSERVED RESULT the area to set keyboard shortcuts on bottom is not entirely visible. Please watch the attached screen recording. EXPECTED RESULT Default size of the window to configure a desktop effect should be enough to make the area to set keyboard shortcuts on bottom entirely visible. No manual resizing should be required. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443540] Dolphin glitch after packing directory to 7z
https://bugs.kde.org/show_bug.cgi?id=443540 Yaroslav Sidlovsky changed: What|Removed |Added CC||zawer...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 445603] usb-creator-kde missing python3-sip
https://bugs.kde.org/show_bug.cgi?id=445603 Carlo Vanini changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Carlo Vanini --- Hello, thank you for reporting. What you describe, a missing dependency, is a problem in packaging. You should report the bug to you distribution (Ubuntu) against the usb-creator-kde package. This is not something that can be fixed in Muon. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445297] Sensor system monitor prints NVMe drive temperature of ~50°C in text but draws graph at absolute zero / 0K / -273°C
https://bugs.kde.org/show_bug.cgi?id=445297 --- Comment #4 from Dennis Schridde --- (In reply to Dennis Schridde from comment #3) > nvme-pci-0900 > Adapter: PCI adapter > Composite:+44.9°C (low = -273.1°C, high = +83.8°C) >(crit = +83.8°C) > Sensor 1: +44.9°C (low = -273.1°C, high = +65261.8°C) > Sensor 2: +63.9°C (low = -273.1°C, high = +65261.8°C) So it seems that the display is actually correct, just that the numbers reported by the sensor are completely bonkers. -- You are receiving this mail because: You are watching all bug changes.
