[digikam] [Bug 420865] "Labels" tab in left menu shows unexpected behavior
https://bugs.kde.org/show_bug.cgi?id=420865 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- I am actually aware of the problem. For no color label and flag, a database operation is whether entries are present. This function does not work safely. Deleting a color label / flag / rating leaves an entry in the DB. So we have to check the value. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420865] "Labels" tab in left menu shows unexpected behavior
https://bugs.kde.org/show_bug.cgi?id=420865 Maik Qualmann changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415044] Kdenlive does not handle image sequences correctly
https://bugs.kde.org/show_bug.cgi?id=415044 --- Comment #2 from Paul Brown --- The bug is back in 20.04 on Linux. The bahviour has been observed both in the most recent Appimages and the Flatpaks. WORKAROUND When Kdenlive complains about not finding the sequenceof images, click on the "Use placeholders for missing clips" and thne back on "Search recursively". Finally click "Ok" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420541] Critical notifications (and *only* critical notifications) should be more attention-getting
https://bugs.kde.org/show_bug.cgi?id=420541 --- Comment #9 from RaitaroH --- (In reply to Nate Graham from comment #8) > Great, now all that's left to do here is to (maybe) improve the visibility > of critical notifications. Moving to the appropriate place where we would > implement that. Can't wait to see this issue in "Adventures in Linux and KDE" Sir! :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 419719] Crash when repeating pgrep operation back-to-back
https://bugs.kde.org/show_bug.cgi?id=419719 Kåre Särs changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||kate/commit/54b730ac6c28d0d ||ddac5e8c583e6ed0b3a0941fb --- Comment #8 from Kåre Särs --- Git commit 54b730ac6c28d0dddac5e8c583e6ed0b3a0941fb by Kåre Särs. Committed on 02/05/2020 at 06:26. Pushed by sars into branch 'Improve--thread-safety-in-search-plugin'. Fix crash if search command is used while searching Thread safety was only provided by disabling the UI and that breaks if we use the commands. Add terminateSearch functions that stop the search without sending signals and prevent already queued signals from adding matches in the matches tree. M +11 -1addons/search/FolderFilesList.cpp M +3-0addons/search/FolderFilesList.h M +17 -3addons/search/SearchDiskFiles.cpp M +2-0addons/search/SearchDiskFiles.h M +27 -14 addons/search/plugin_search.cpp M +10 -8addons/search/plugin_search.h M +11 -0addons/search/replace_matches.cpp M +2-0addons/search/replace_matches.h M +27 -13 addons/search/search_open_files.cpp M +7-3addons/search/search_open_files.h https://invent.kde.org/kde/kate/commit/54b730ac6c28d0dddac5e8c583e6ed0b3a0941fb -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 292583] Wish: access to KDE services 'Actions' menu in context menu
https://bugs.kde.org/show_bug.cgi?id=292583 Jonathan Farley changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Jonathan Farley --- Neat, but not what I was asking for: I was asking for the ability to use custom scripts within Gwenview, so being able to access what would be the same as the 'actions' menu in Dolphin, is what I was after, not using the same 'share' protocols as Dolphin. In dolphin, by placing a .desktop file in ~/.local/share/Kservices5/ServiceMenu/ you can pass parameters to and run any script or application you wish to achieve any purpose you desire. It was being able to utilise this same process in Gwenview that I was hoping for. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784 --- Comment #4 from Ivan Čukić --- If I'm not mistaken (some parts are missing in you response, so I'm making an educated guess :) ), you haven't restored activity configuration and your vault is assigned to an activity with an id of "5e847ac8-3735-4647-ad07-ac753d5" which no longer exists. Try to do this - open konsole and: killall kded5 cd ~/.config mv plasmavaultrc plasmavaultrc.backup grep -v 5e847ac8-3735-4647 plasmavaultrc.backup > plasmavaultrc kded5 & -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420880] add hotkeys and saving individual view settings for documents
https://bugs.kde.org/show_bug.cgi?id=420880 Yuri Chornoivan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||yurc...@ukr.net --- Comment #1 from Yuri Chornoivan --- The first (Settings -> Configure shortcuts... just broken for the one minor release 20.04.0) and third (Settings -> Show Page Bar) of these wishes have already been implemented. The second wish has been implemented from the beginning. Thanks in advance for understanding. *** This bug has been marked as a duplicate of bug 420525 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420525] missing keyboard shotcuts since 20.04
https://bugs.kde.org/show_bug.cgi?id=420525 Yuri Chornoivan changed: What|Removed |Added CC||sordessor...@gmail.com --- Comment #9 from Yuri Chornoivan --- *** Bug 420880 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420875] Assigning Tag/Label makes thumbnail disappear
https://bugs.kde.org/show_bug.cgi?id=420875 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- Changing the metadata in the database triggers the creation of a new thumbnail. We have to check if the collection is available. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420767] Incorrect ordinate axis labels when zooming a chart
https://bugs.kde.org/show_bug.cgi?id=420767
Thomas Baumgart changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kmy
||money/5e4c8322fbefcb6cdaf1c
||51f6204986946ca0ba4
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Thomas Baumgart ---
Git commit 5e4c8322fbefcb6cdaf1c51f6204986946ca0ba4 by Thomas Baumgart, on
behalf of Robert Szczesiak.
Committed on 02/05/2020 at 05:11.
Pushed by tbaumgart into branch 'master'.
Fix ordinate axis labels when zooming
Summary:
If I understand the intent of the author correctly, the sole purpose of
`KReportChartView::slotNeedUpdate()` was one-time customization of
ordinate axis labels at the time of chart creation. The fact that signal
is disconnected immediately after execution of slot starts seems to
confirm my understanding.
The problem begins when one zooms the chart (using so-called rubber band
zooming feature from KDiagram project). Axis ticks and labels are
recalculated but still they are overridden with "hard labels" defined in
the slot body. The number of axis ticks increases and is grater than the
number of hard labels, so the labels are repeated in cycle. In and of
itself it is really a feature rather than a bug but the feature works to
our disadvantage in this case.
Please find below a quote from AbstractAxis Class documentation:
> void AbstractAxis::setLabels( const QStringList & list )
> Use this to specify your own set of strings, to be used as axis
labels.
> Labels specified via setLabels take precedence: If a non-empty list is
passed, KD Chart will use these strings as axis labels, **instead of
calculating them.**
> **If you pass a smaller number of strings than the number of labels
drawn at this axis, KD Chart will repeat the strings until all labels
are drawn**. As an example you could specify the seven days of the week
as abscissa labels, which would be repeatedly used then.
Unfortunately, mere removal of disconnect method call does not solve the
problem but the same documentation provides a way to customize axis
labels when needed. It is done through overriding of `const QString
AbstractAxis::customizedLabel( const QString & label ) const`
My solution proposed in attached patch goes this way and also simplifies
calculations where they seemed over-complicated to me. Please correct my
understanding if i missed the point of removed lines.
Please find attached screenshots before and after the fix.
Balance history chart before fix with no zoom:
{F8268351}
Balance history chart before fix with zoom::
{F8268353}
Balance history chart after fix with no zoom:
{F8268359}
Balance history chart after fix with zoom::
{F8268358}
As a footnote, I would like to sincerely thank to all the people who
have contributed to this project. I started to use KMyMoney recently and
I am surprised how good it is, especially for an open-source project run
by the community. It suits my need for personal finance and
investment-supporting software amazingly well. If you find my
contribution valuable, I would love to provide more patches in the
future if I find more bugs or feel that some feature is missing. In
fact, I have little to no industrial experience in C++ as I work mostly
in Java. Please let me know if I broke any C++ coding rules.
Reviewers: #kmymoney, tbaumgart
Reviewed By: #kmymoney, tbaumgart
Subscribers: tbaumgart
Tags: #kmymoney, #kdiagram
Differential Revision: https://phabricator.kde.org/D29255
M +1-0kmymoney/plugins/views/reports/core/CMakeLists.txt
A +57 -0kmymoney/plugins/views/reports/core/kreportcartesianaxis.cpp
[License: GPL (v2+)]
A +48 -0kmymoney/plugins/views/reports/core/kreportcartesianaxis.h
[License: GPL (v2+)]
M +26 -56 kmymoney/plugins/views/reports/core/kreportchartview.cpp
M +6-2kmymoney/plugins/views/reports/core/kreportchartview.h
M +1-1kmymoney/plugins/views/reports/reporttabimpl.cpp
https://commits.kde.org/kmymoney/5e4c8322fbefcb6cdaf1c51f6204986946ca0ba4
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-nm] [Bug 420887] New: Available connections are mixed with saved connections without order
https://bugs.kde.org/show_bug.cgi?id=420887 Bug ID: 420887 Summary: Available connections are mixed with saved connections without order Product: plasma-nm Version: 5.17.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: j...@ganomi.com Target Milestone: --- SUMMARY Available connections are mixed with saved connections and are out of other. Saved connections should precede a list of all other available connections. IMPACT When I click network applet in the pannel all available connection are mixed with my saved connections. Often they start moving in the list and I have wait until its organized that I can start looking for my connection. This is very frustrating. STEPS TO REPRODUCE 1. Save some connections and create VPN connections and return back to the 2. Click on networks in panel 3. See Active and Available connections 4. Available connections are mixed without any order. Wifi connection are mixed with VPN connections without any specific order. Other wifi connection might be also in the mix. OBSERVED RESULT Available connections are mixed with saved connections without order EXPECTED RESULT Saved connections should have its own category All other available connections, mostly other Wireless connection should be in its own category. SOFTWARE/OS VERSIONS Debian Unstable KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.62 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 --- Comment #4 from caulier.gil...@gmail.com --- Use the 64 bits version, especially if you handle large tiff files. Remember that 32 bits version is limited to 4Gb or RAM. This is for the old computers. All desktop/laptop computers are based on 64 bits processor now. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 76380] Trashing files on other partitions and disks that are mounted without UID=USERID, GID=USERGROUPID, FMASK=177, DMASK=077 copies them to the Trash directory on /
https://bugs.kde.org/show_bug.cgi?id=76380 Daniel changed: What|Removed |Added CC||danlemn...@gmail.com --- Comment #62 from Daniel --- I took a look at the Freedestop specifications. I'm sorry David (Faure), but there's something in KDE code that isn't right. To quote the freedesktop specifications for Trash, regarding the .Trash-userid folder: https://specifications.freedesktop.org/trash-spec/trashspec-latest.html "(2) If an $topdir/.Trash directory is absent, an $topdir/.Trash-$uid directory is to be used as the user's trash directory for this device/partition. $uid is the user's numeric identifier. The following paragraph applies ONLY to the case when the implementation supports trashing in the top directory, and a $topdir/.Trash does not exist or has not passed the checks: When trashing a file, if an $topdir/.Trash-$uid directory does not exist, the implementation MUST immediately create it, without any warnings or delays for the user. When trashing a file, if this directory does not exist for the current user, the implementation MUST immediately create it, without any warnings or delays for the user." There is no requirement there about certain restrictive folder permissions when it comes to .Trash-uid folders (unlike the .Trash), there is only an underlining of the immediacy of creating the necessary folder. Other DEs simply ensure that the folder will be fit to write into. That's it. Your implementation is just stricter than necessary. I did a comparison with Gnome's approach. See Gnome's relevant code here: https://gitlab.gnome.org/GNOME/glib/blob/glib-2-56/gio/glocalfile.c#L2083 And here's KDE's (thanks Fikri Muhammad Iqbal): https://code.woboq.org/qt5/kf5/kio/src/ioslaves/trash/trashimpl.cpp.html#1190 While Gnome does try to make the folder 0700, they will still use it as long as the uid is correct as they will be able to write into the folder, being aware that for a FAT partition for example, permissions will not work. Even if you are particularly sensitive about the security implications of such a trash folder, you must admit that no major issue has arisen in more than 10 years since other DEs have implemented it. I think this really should be moving forward after 10 years. If one searches online, there are many instances of users complaining about this issue, and trying to find some kind of workaround. Some use /etc/fstab, others stick to a straight delete policy (no moving to trash), which obviously is not ideal. Keep in mind that most USB sticks and external HDDs, and even internal data disks/partitions will use windows compatible file systems by default. And many users will keep them that way because they dual boot or also use them with Windows systems. Copying every deleted file from "data" to their /home Trash is just the wrong approach, of which the freedesktop specifications seem well aware. Many will have hundreds of GBs of data, but limited size SSDs for their OS. An eventual HDD cleanup of old data will burn through their SSD writes, take ages to complete, and eventually result in "/" being filled, with possible stability consequences, because not everybody uses a separate /home partition. In the mean time, for anyone bumping into this bug report, some workaround tips, based on what was said by others above (the instructions do assume you're using a Debian/Ubuntu based distro, unfortunately): I. Using the terminal: sudo nano /etc/fstab Then add something like this to the file (edited of course to fit your particular system, so you will need the Label or the UUID of your partition) LABEL=LG /mnt/LG auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=1000,umask=077,noauto 0 0 or UUID=cea8b9a9-9fd9-4e38-842c-57b9bdbdffdc /mnt/LG auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=1000,umask=077,noauto 0 0 Then press Ctrl-o - to save the file Enter - to confirm the file name Ctrl-x - to exit the editing session For those not familiar with the terminal, there's GNOME Disks. sudo apt install gnome-disk-utility Once installed, look for the "Disks" app. Find the partition you need to operate on, click on the button that says "Additional Partition Options" when you hover over it, disable "User Session defaults" then add "uid=1000,gid=1000,umask=077,noauto" to the mount options. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420003] Global shortcut: show windows from all desktops has no effect
https://bugs.kde.org/show_bug.cgi?id=420003 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418451] Systems Setting not opening up
https://bugs.kde.org/show_bug.cgi?id=418451 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 368759] KTurtle: lack of translation of Polish command ustalKierunek
https://bugs.kde.org/show_bug.cgi?id=368759 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420225] the programme shuts down often without warning and i am unable to save my work
https://bugs.kde.org/show_bug.cgi?id=420225 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420886] New: Unable to use
https://bugs.kde.org/show_bug.cgi?id=420886 Bug ID: 420886 Summary: Unable to use Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: messaging-application Assignee: si...@ergotech.com Reporter: jameseyoung...@gmail.com Target Milestone: --- Flags: Usability+ SUMMARY Using KDE Connect on my Android device as well as my Pop!_OS linux laptop. When I receive a message on my phone the notification comes up but when I try to select reply it doesn't open anything for me to replay with. I open KDE Connect SMS and it is acting like it is searching for SMS messages from my phone but never sees any even though I have several on there and get them on a regular occasion. STEPS TO REPRODUCE 1. Receive a text 2. Try to reply 3. open KDE Connect SMS OBSERVED RESULT Unable to reply messages do not show up in KDE Connect SMS EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Pop!_OS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 The XCB windowing system ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420886] Unable to use
https://bugs.kde.org/show_bug.cgi?id=420886 jameseyoung...@gmail.com changed: What|Removed |Added CC||jameseyoung...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420885] New: Plasmashell keep crashing repeatdly: QSocketNotifier: Invalid socket
https://bugs.kde.org/show_bug.cgi?id=420885 Bug ID: 420885 Summary: Plasmashell keep crashing repeatdly: QSocketNotifier: Invalid socket Product: plasmashell Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: abhinic...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-28-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: Logged in to the system, It crashed. Manually restarting service also fails each time. Log: $ kstart5 plasmashell org.kde.plasmaquick: Applet preload policy set to 1 kf5.kpackage: No metadata file in the package, expected it at: "/home/abhasker/Pictures/" kf5.kpackage: No metadata file in the package, expected it at: "/home/abhasker/Pictures/" kf5.kpackage: No metadata file in the package, expected it at: "/home/abhasker/Pictures/" file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList kf5.kservice.sycoca: Parse error in "/home/abhasker/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line 1 , col 1 : "unexpected end of file" trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" Plasma Shell startup completed file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:306:17: QML QQuickText: Binding loop detected for property "width" file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:306:17: QML QQuickText: Binding loop detected for property "width" file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:306:17: QML QQuickText: Binding loop detected for property "width" file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:306:17: QML QQuickText: Binding loop detected for property "width" Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Loading Calendar plugin HolidaysEventsPlugin(0x55d34a65a6d0) Loading Calendar plugin PimEventsPlugin(0x55d34a652270) Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. trying to show an empty dialog trying to show an empty dialog QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_285(0x55d34aaba5f0, parent=0x55d34a153640, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_285(0x55d34aa3aad0), which must be a sibling QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_285(0x55d34aa35090, parent=0x55d34a153640, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_285(0x55d34aaba5f0), which must be a sibling Both point size and pixel size set. Using pixel size. trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" KAStatsFavoritesModel::setFavorites is ignored trying to show an empty dialog Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. Both point size and pixel size set. Using pixel size. trying
[krusader] [Bug 419097] Wrong icon for Raku/perl6
https://bugs.kde.org/show_bug.cgi?id=419097 --- Comment #13 from Todd --- Wrong icon for Perl6 / Raku: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/133 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier
https://bugs.kde.org/show_bug.cgi?id=420635 --- Comment #21 from Brian Wright --- (In reply to Konrad Materka from comment #20) > > Conditions: PrivateInternetAccess not running. Booted KDE Neon @ Runlevel > > 3. Started KDE via "exec startx" > Why did you change runlevel? Just to perform this test? That's usual :) SDDM was broken, and I temporarily set my system to runlevel 3 until I fixed SDDM. :) > > > Results: All icons displayed except Slack, hp-systray and DiscoverNotifer > > ((confirmed that they were running via ps aux). Odd effect: pasystray, > > indicator-sound-switcher, and skype are duplicated. > > * You have 3 icons missing and 3 duplicated - this is probably be a > coincidence, but can you perform more tests? Yes - I plan to do more tests this weekend. > * Are this duplicated icons behaving the same? For example, if you > left/right click on Skype icon, to you have the same behavior? Yes, the duplicated icons behave the same. > * Duplicated icons does not look the same - maybe one is new SNI and second > old legacy? What happens if you kill xembedsniproxy? Do duplicated icons > dissappear? What happens when you run xembedsniproxy again (after kill)? Duplicated icons don't disappear. When I ran xembedsniproxy, the command seemed to hang. I did not get a message about the container. So I had to re-run xembedsniproxy as a background process. > * For missing icons, what happens when you kill app and run it again? For > example, kill Slack and run it again - do you have proper tray icon? Yes, that happens with all the affected apps. Once I kill the apps and restart them, they work perfectly. This is the only way to resolve the issue. > * The indicator-sound-switcher is not in a default repository, it requires > ppa. Do you have many ppa configured? Did you do many changes into default > installation and configuration? My point is, maybe on fresh system (or just > fresh user) problem does not occur? I installed Neon on Virtualbox, and then created a test user account. Everything worked as it should with the affected apps. I'm beginning to strongly suspect that my KDE Plasma profile was corrupted. I'm going to see about doing a "factory reset" on the KDE Plasma profile and run more tests. As far as changes to the configuration, I can't recall specifics. > * Are you using snap or flatpack for any of affected application? No, they were all .deb packages. > > > listIcons.sh output: > I see duplicated entries for indicator-sound-switcher, pasystray and skype. > Skype is particularly interesting because it has different names in output. > My guess is on icon is SNI, second legacy icon translated by xembedsniproxy. Interesting! > > org.kde.StatusNotifierItem-19688-1/StatusNotifierItem > > .. > > The error is probably being caused by the Google Hangouts extension in > > Chrome. I had NetworkManager run via systemd, but the NetworkManager icon > > was disabled in the system tray. > NetworkManager icon is an applet to show and manipulate NetworkManager > daemon, disabling it should not affect anything. > Error is interesting, but probably this is unrelated - it might be a > separate issue. Agreed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 420884] New: Cannot discover Linux
https://bugs.kde.org/show_bug.cgi?id=420884 Bug ID: 420884 Summary: Cannot discover Linux Product: kdeconnect Version: 1.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: jgra...@mailbox.org Target Milestone: --- SUMMARY KDEConnect instantly discover all Android devices on the Nextwork but cannot see Linux devices. STEPS TO REPRODUCE 1. Open KDEConnect 2. look at Available devices - only Android devices show 3. Click + Find Devices - only Android devices show OBSERVED RESULT Linux devices do not appear in Pair list EXPECTED RESULT Both Android and Linux devices to appear in Pair list SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-28-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31.2 GiB of RAM KDE Connect version: 1.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #20 from Musikolo --- Created attachment 128091 --> https://bugs.kde.org/attachment.cgi?id=128091&action=edit strace_kstart5_plasmashell.log Hi guys, I've been looking into the issue with plasmashell, this is what I found: 1.- I stop it with: kbuildsycoca5 && kquitapp5 plasmashell 2.- I start it with: strace kstart5 plasmashell As you can see at the very end of the attached strace_kstart5_plasmashell.log file, there are a bunch of error with SystemLoadViewer plasma, then it does nothing for ~24 seconds, and then it prints the following error and plasmashell shows up: trying to show an empty dialog file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:146:19: QML Loader: Binding loop detected for property "height" I wonder whether the "Binding loop" error found in the Desktop.qml file could be the root cause. That file belongs to the plasma-desktop 5.18.4.1-1 package in ArchLinux. I hope it helps! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420883] New: Kmail: 5.13.3 send fail
https://bugs.kde.org/show_bug.cgi?id=420883 Bug ID: 420883 Summary: Kmail: 5.13.3 send fail Product: kmail2 Version: 5.13.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: jgra...@mailbox.org CC: a...@kde.org, mon...@kde.org, vkra...@kde.org Target Milestone: --- SUMMARY Install Kmail 5.13.3 in Kubuntu 20.04 via Muon. Setup Kmail with two accounts - as per working settings with Kmail 5.11.3 on Kubuntu 19.10. Kmail receives mail from both accounts but cannot send from either. STEPS TO REPRODUCE 1. Start laptop - Message displays: The mail dispatcher is offline, so mails cannot be sent. Do you want to make it online? -Clicking yes. 2. Mail will not send. Mail goes to Local folder - Outbox 3. Open Akonadi Console. Toggle Mail dispatcher offline and back online. 4. Go to Outbox and send mail. 5 Recieve message: E-Mail sending failed. Failed to transport message. Server error 5.7.8 Error authentication failed. UGFvcmQ6zc3d OBSERVED RESULT Failure to send EXPECTED RESULT Messages send as per 19.10 configuration SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-28-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31.2 GiB of RAM Kmail: 5.13.3 (19.12.3) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415044] Kdenlive does not handle image sequences correctly
https://bugs.kde.org/show_bug.cgi?id=415044 tonton changed: What|Removed |Added CC||samyticha...@gmail.com --- Comment #1 from tonton --- Hi, This bugs also exists on version stable 20.04 for windows 10 (setup version, not portable), any news ? This is a deal breaker for any project involving animation and 3d... thanks for your hard work ! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 404625] When text labels have a maximum line count, items with elided text should display full text when hovered or selected
https://bugs.kde.org/show_bug.cgi?id=404625 Christian Christiansen changed: What|Removed |Added CC||christian.l.christiansen@gm ||ail.com --- Comment #6 from Christian Christiansen --- Created attachment 128090 --> https://bugs.kde.org/attachment.cgi?id=128090&action=edit Multiple files selected for dolphin without elided filenames What should happen when multiple files with long filenames are selected? One trouble with allowing longer filenames to overflow is that files underneath end up covered by the text and can no longer be seen. (Attachment included) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 420784] Restore of Vaults fail
https://bugs.kde.org/show_bug.cgi?id=420784
Justin changed:
What|Removed |Added
Alias||jgra...@mailbox.org
--- Comment #3 from Justin ---
Hello Ivan,
I created a new vault called 'Safe'. I attempted to place it in the same
directory as my previous vault called 'Vault'at /home/anarcho/Personal/Vault It
said the directory was not empty. I clicked Ok and it created 'Safe' at
/home/anarcho/Vault. My previous vault still would not show in the taskbar
icon. I ran the command:
anarcho@LuNoHo:~$ qdbus --literal org.kde.kded5 /modules/plasmavault av
[Argument: a(sssqsasb) {[Argument: (sssqsasb) "Safe",
"/home/anarcho/.lt/Safe.enc", "", 2, "", {}, false], [Argument: (sssqsasb)
"Vault", "/hoe/plasma-vault/Vault.enc", "", 2, "",
{"5e847ac8-3735-4647-ad07-ac753d5
anarcho@LuNoHo:~$
I did a sudo apt update.
Trying to open the old vault via Dolphin, brought a pop up saying cryfs needed
to be updated. I clicked ok. I was then able to access the vault!
'Safe' appears under the taskbar icon but 'Vault' seems to not always be there,
yet I can access it through Dolphin.
I ran the command again:
anarcho@LuNoHo:~$ anarcho@LuNoHo:~$ qdbus --literal org.kde.kded5
/modules/plasmavault
anarcho@LuNoHo:~$: command not found
anarcho@LuNoHo:~$ qdbus --literal org.kde.kded5 /modules/plasmavault
signal void org.kde.plasmavault.hasOpenVaultsChanged(bool hasOpenVaults)
signal void org.kde.plasmavault.vaultAdded({D-Bus type "(sssqsasb)"} vaultData)
signal void org.kde.plasmavault.vaultChanged({D-Bus type "(sssqsasb)"}
vaultData)
signal void org.kde.plasmavault.vaultRemoved(QString device)
method {D-Bus type "a(sssqsasb)"} org.kde.plasmavault.availableDevices()
method void org.kde.plasmavault.closeAllVaults()
method void org.kde.plasmavault.closeVault(QString device)
method void org.kde.plasmavault.configureVault(QString device)
method void org.kde.plasmavault.deleteVault(QString device, QString name)
method void org.kde.plasmavault.forceCloseAllVaults()
method void org.kde.plasmavault.forceCloseVault(QString device)
method bool org.kde.plasmavault.hasOpenVaults()
method void org.kde.plasmavault.openVault(QString device)
method void org.kde.plasmavault.openVaultInFileManager(QString device)
method void org.kde.plasmavault.requestImportVault()
method void org.kde.plasmavault.requestNewVault()
method void org.kde.plasmavault.updateStatus()
signal void org.freedesktop.DBus.Properties.PropertiesChanged(QString
interface_name, QVariantMap changed_properties, QStringList
invalidated_properties)
method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name,
QString property_name)
method QVariantMap org.freedesktop.DBus.Properties.GetAll(QString
interface_name)
method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString
property_name, QDBusVariant value)
method QString org.freedesktop.DBus.Introspectable.Introspect()
method QString org.freedesktop.DBus.Peer.GetMachineId()
method void org.freedesktop.DBus.Peer.Ping()
Thanks for the help Ivan (and Nate)!
You may mark this as solved and close if you think there is nothing more to
explore!
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 420882] New: Wish: Add a command line argument to start dolphin maximized
https://bugs.kde.org/show_bug.cgi?id=420882 Bug ID: 420882 Summary: Wish: Add a command line argument to start dolphin maximized Product: dolphin Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: myndstr...@protonmail.ch CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Could you please add a command-line argument to start dolphin maximized? (e.g. -m or --maximized) This would allow users to create more useful shortcuts for dolphin. One example would be using dolphin for a media center as described here: https://unix.stackexchange.com/a/582832/233262 Additional view options for dolphin would also be useful. As of version 18.08, which is the version that's currently packaged on latest Debian stable, the only view option when starting from command line is --split which starts dolphin with a split view. I previously asked about the same thing for a fullscreen mode here: https://bugs.kde.org/show_bug.cgi?id=420851 (And in case anybody needs this feature now: a temporary/suboptimal workaround would be to use wmctrl as described at the link above.) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.5 KDE Plasma Version: 5.14 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420851] Wish: Add a command line argument to start dolphin in fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=420851 --- Comment #3 from myndstr...@protonmail.ch --- Thanks, you two. After installing wmctrl this is the full command which worked to start dolphin to open a directory in fullscreen mode and with larger icons (I also added this to the StackExchange question linked above): QT_SCALE_FACTOR=2 dolphin ~/Foldername & sleep 0.8 && wmctrl -r "Foldername — Dolphin" -b add,fullscreen To start it maximized instead of fullscreen just replace "fullscreen" with "maximized_horz,maximized_vert" I opened a new issue for a command-line argument to start dolphin maximized: https://bugs.kde.org/show_bug.cgi?id=420882 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420881] In case two screens and after very first start of Plasma, window of application appears on not primary screen
https://bugs.kde.org/show_bug.cgi?id=420881 Piotr Mierzwinski changed: What|Removed |Added Summary|In case two screens and |In case two screens and |after very first start of |after very first start of |Plasma windows appear on|Plasma, window of |not primary screen |application appears on not ||primary screen Target Milestone|1.0 |--- Product|plasmashell |kwin Component|general |general Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420881] In case two screens and after very first start of Plasma windows appear on not primary screen
https://bugs.kde.org/show_bug.cgi?id=420881 --- Comment #2 from Piotr Mierzwinski --- Similar issue I reported here: #416556 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420881] In case two screens and after very first start of Plasma windows appear on not primary screen
https://bugs.kde.org/show_bug.cgi?id=420881 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 128089 --> https://bugs.kde.org/attachment.cgi?id=128089&action=edit kscreen configuration for 2 displays -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420881] New: In case two screens and after very first start of Plasma windows appear on not primary screen
https://bugs.kde.org/show_bug.cgi?id=420881 Bug ID: 420881 Summary: In case two screens and after very first start of Plasma windows appear on not primary screen Product: plasmashell Version: 5.18.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY As in subject. I have 2 displays connected to my PC. First is monitor (primary screen) and second projector, which usually is working in standy mode. Plasma detected both. I tested this issue with two live distributions. I mean KaOS 2020.02 (Plasma 5.18.1) and Manjaro 20 (Plasma 5.18.4). Also I tested this with older KaOS with Plasma 5.17. The same result. After plasma session was started I run System Setting and/or KInfoCenter and/or Konsole. Window of started application appeared on not primary screen. To use/get it I needed blindly catch and move (holding Alt) window to my primary screen or just turn on projector. BTW. Unfortunately icon of running application placed on bar where windows are minimized doesn't have option "Move to Screen", whereas this option is present in context menu of title bar of window. Therefore isn't comfortable move window to other screen. Sometimes after moving window to primary screen issue disappear. Sometimes after opening Display settings in System Setting issue disappear. I'm not sure what exactly it depends on. STEPS TO REPRODUCE Having two screens connected to PC. 1. Start live distribution like KaOS or Manjaro 2. Using Kickoff start System Settings or KInfoCenter or Konsole 3. OBSERVED RESULT Window appears on not primary screen. EXPECTED RESULT Window should appear on primary screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION mesa 20.0.5-1 xf86-video-intel 1:2.99.917+906+g846b53da-1 xorg 1.20.8 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420880] New: add hotkeys and saving individual view settings for documents
https://bugs.kde.org/show_bug.cgi?id=420880 Bug ID: 420880 Summary: add hotkeys and saving individual view settings for documents Product: okular Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: New backend wishes Assignee: okular-de...@kde.org Reporter: sordessor...@gmail.com Target Milestone: --- hello! can you please make hotkeys for switching viev mode (single/double page), like in evince? and it would be cool if okular could remember the settings for each document. and instead of a panel with a page number -- a small indicator somewhere in the corner (this would save a little space for displaying pages). thank you! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 --- Comment #3 from Josec --- FYI, I can be working for hours on the applicaiton and once the error occurs, all I have to do is select my root picture directory after restarting the app and it will crash within a minute. I know that I have some very large TIFF files, could that be the source of the issue? Jose -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 364838] Folders with spaces are ignored in the exclude list
https://bugs.kde.org/show_bug.cgi?id=364838 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org --- Comment #1 from Davide Gianforte --- On a recent version, it seems that all excluded folder are ignored, can you confirm? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Ongun Kanat changed: What|Removed |Added CC||ongun.ka...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 k...@trummer.xyz changed: What|Removed |Added CC||k...@trummer.xyz --- Comment #4 from k...@trummer.xyz --- KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 I can also reliably crash Dolphin by right-clicking the terminal window and selecting close or hitting Ctrl-Shift-W. Hitting Ctrl-D also makes it crash. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 420879] Space for Dictionary results is too short to be useful
https://bugs.kde.org/show_bug.cgi?id=420879 Gustavo Castro changed: What|Removed |Added Summary|Space for Dictionary|Space for Dictionary |results are too short |results is too short to be ||useful -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 420879] New: Space for Dictionary results are too short
https://bugs.kde.org/show_bug.cgi?id=420879 Bug ID: 420879 Summary: Space for Dictionary results are too short Product: krunner Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: gusta...@gmail.com Target Milestone: --- SUMMARY When using the "define" option in Krunner, only one line is shown, resulting in trimmed definitions. STEPS TO REPRODUCE 1. Open Krunner 2. Use the "define" option 3. Wait for the results OBSERVED RESULT The reserved space for results is too short and the definitions are trimmed. EXPECTED RESULT The complete definition should be shown, either by allowing Krunner to use more than one line per item, showing the full result when hovering or copying it to the clipboard if selected. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Operating System: Arch Linux KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 280020] No info about alternate deletion shortcut
https://bugs.kde.org/show_bug.cgi?id=280020 Davide Gianforte changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kru ||sader/2ab9de1d6bc234cbc558e ||dcdc21e301ad5075bbe --- Comment #2 from Davide Gianforte --- Git commit 2ab9de1d6bc234cbc558edcdc21e301ad5075bbe by Davide Gianforte. Committed on 01/05/2020 at 22:48. Pushed by gengisdave into branch 'master'. Update documentation for file deletion Update the documentation to the correct file deletion shortcuts. Ctrl+Del does always the alternate delete from F8/Del. FIXED: [ 280020 ] No info about alternate deletion shortcut Differential Revision: https://phabricator.kde.org/D29350 M +4-2doc/basic-functions.docbook M +2-2doc/keyboard-commands.docbook https://commits.kde.org/krusader/2ab9de1d6bc234cbc558edcdc21e301ad5075bbe -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 419465] Wallet failed to get opened by PAM, error code is -9
https://bugs.kde.org/show_bug.cgi?id=419465 --- Comment #8 from Albert Astals Cid --- @Andre how does your encrypfs setup works? It gets un-encrypted after you put the password using pam? I wonder how this may work at all with 5.18.3 since your user dir is still encrypted and thus it can not read from it. Is it possible that there's a .local/share/kwalletd/kdewallet.salt in your home "outside" the encrypted data? I've no idea how encrypfs works, but if it works by mounting something on top of your existing home dir, i can envision the fact that there's a /home/youruser/.local/share/kwalletd/kdewallet.salt "outside" your encrypted data and then another one inside. Can you try that? e.g. by logging as root or as another user and checking if the file is there? If that's the case, that's unfortunately a bug of how kwallet-pam used to work, that file should be *inside* your encrypted data and not outside, so a way to fix this would be copying that file from outside your encrypted data to the inside (keep copy of the old one just in case). Am i making sense? -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 420878] Problems in KDE-Plasma Online Accounts in Fedora 32
https://bugs.kde.org/show_bug.cgi?id=420878 Hugo Leonardo R. D. Lopes changed: What|Removed |Added CC||64bit_fed...@comcast.net, ||aol...@redhat.com, ||b...@redhat.de, ||fedora.ru...@gmail.com, ||fedora...@bigorange.org, ||hlo...@gmail.com, ||jwrdego...@fedoraproject.or ||g, kde-bugzi...@plasma.cx, ||mschwe...@fedoraproject.org ||, ||nuell@mnredhat7.lethbridgec ||ollege.ab.ca, ||pga...@redhat.com, ||reveal@bungiesoft.org, ||yna...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 420878] New: Problems in KDE-Plasma Online Accounts in Fedora 32
https://bugs.kde.org/show_bug.cgi?id=420878 Bug ID: 420878 Summary: Problems in KDE-Plasma Online Accounts in Fedora 32 Product: KAccounts Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: hlo...@gmail.com Target Milestone: --- Created attachment 128088 --> https://bugs.kde.org/attachment.cgi?id=128088&action=edit Short video from Online Accounts < 1min. Problems in KDE-Plasma Online Accounts in Fedora 32 x86_64 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420877] New: Discover crashed when launching
https://bugs.kde.org/show_bug.cgi?id=420877 Bug ID: 420877 Summary: Discover crashed when launching Product: Discover Version: 5.18.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ryu.ketsu...@outlook.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.18.3) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.6-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I simply tried to open Discover. It crashed right after the window show then closed The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f820d40e500 in QQmlRefPointer::QQmlRefPointer(QQmlRefPointer const&) (other=..., this=0x7f8204888f90) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/include/QtQml/5.14.1/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:152 #5 0x7f820d40e500 in QQmlType::QQmlType(QQmlType const&) (this=0x7f8204888f90) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/include/QtQml/5.14.1/QtQml/private/../../../../../src/qml/qml/qqmltype_p.h:78 #6 0x7f820d4803d9 in QQmlPropertyCacheCreator::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlJS::DiagnosticMessage*) const (this=this@entry=0x7f8204889290, obj=obj@entry=0x7f81fc35f700, context=..., error=error@entry=0x7f8204889050) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/include/QtQml/5.14.1/QtQml/private/../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:95 #7 0x7f820d48359a in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f8204889290, objectIndex=, context=...) at /usr/include/qt5/QtCore/qarraydata.h:257 #8 0x7f820d483a0b in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f8204889290, objectIndex=, context=...) at /usr/include/c++/9/bits/atomic_base.h:326 #9 0x7f820d483a0b in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&) (this=this@entry=0x7f8204889290, objectIndex=objectIndex@entry=0, context=...) at /usr/include/c++/9/bits/atomic_base.h:326 #10 0x7f820d47f0f5 in QQmlPropertyCacheCreator::buildMetaObjects() (this=0x7f8204889290) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/include/QtQml/5.14.1/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:138 #11 0x7f820d47f0f5 in QQmlTypeCompiler::compile() (this=this@entry=0x7f8204889450) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/qqmltypecompiler.cpp:85 #12 0x7f820d3ca457 in QQmlTypeData::compile(QQmlRefPointer const&, QV4::ResolvedTypeReferenceMap*, std::function const&) (this=this@entry=0x55cfffa64590, typeNameCache=..., resolvedTypeCache=resolvedTypeCache@entry=0x7f8204889528, dependencyHasher=...) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/qqmltypedata.cpp:613 #13 0x7f820d3ce8ed in QQmlTypeData::done() (this=0x55cfffa64590) at /usr/include/c++/9/bits/std_function.h:87 #14 0x7f820d3ba765 in QQmlDataBlob::tryDone() (this=0x55cfffa64590) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/include/QtQml/5.14.1/QtQml/private/../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:116 #15 0x7f820d3ba765 in QQmlDataBlob::tryDone() (this=0x55cfffa64590) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/qqmldatablob.cpp:509 #16 0x7f820d41ac33 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) (this=this@entry=0x55cffe5359a0, blob=blob@entry=0x55cfffa64590, d=...) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/qqmltypeloader.cpp:443 #17 0x7f820d41af94 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) (this=this@entry=0x55cffe5359a0, blob=blob@entry=0x55cfffa64590, fileName=...) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/qqmltypeloader.cpp:424 #18 0x7f820d41b6f0 in QQmlTypeLoader::loadThread(QQmlDataBlob*) (this=0x55cffe5359a0, blob=blob@entry=0x55cfffa64590) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/qqmltypeloader.cpp:296 #19 0x7f820d3d648d in QQmlTypeLoaderThread::loadThread(QQmlDataBlob*) (this=, b=0x55cfffa64590) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.x86_64/src/qml/qml/qqmltypeloaderthread.cpp:156 #20 0x7f820d49ca28 in QQmlThreadPrivate::threadEvent() (this=this@entry=0x55cffe3859d0) at /usr/src/debug/libqt5-qtdeclarative-5.14.1-ku.1.3.
[krusader] [Bug 325422] First archive encountered during a text search is searched even when "search in archives" check box is not checked
https://bugs.kde.org/show_bug.cgi?id=325422 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #2 from Toni Asensi Esteve --- The bug was not seen in some tests using the git version of Krusader. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier
https://bugs.kde.org/show_bug.cgi?id=420635 --- Comment #20 from Konrad Materka --- > I had also uninstalled libayatana-appindicator3-1 and associated dependencies You didn't need to do that, but probably it was not used anyway and it has no influence. > Conditions: PrivateInternetAccess not running. Booted KDE Neon @ Runlevel > 3. Started KDE via "exec startx" Why did you change runlevel? Just to perform this test? That's usual :) > Results: All icons displayed except Slack, hp-systray and DiscoverNotifer > ((confirmed that they were running via ps aux). Odd effect: pasystray, > indicator-sound-switcher, and skype are duplicated. * You have 3 icons missing and 3 duplicated - this is probably be a coincidence, but can you perform more tests? * Are this duplicated icons behaving the same? For example, if you left/right click on Skype icon, to you have the same behavior? * Duplicated icons does not look the same - maybe one is new SNI and second old legacy? What happens if you kill xembedsniproxy? Do duplicated icons dissappear? What happens when you run xembedsniproxy again (after kill)? * For missing icons, what happens when you kill app and run it again? For example, kill Slack and run it again - do you have proper tray icon? * The indicator-sound-switcher is not in a default repository, it requires ppa. Do you have many ppa configured? Did you do many changes into default installation and configuration? My point is, maybe on fresh system (or just fresh user) problem does not occur? * Are you using snap or flatpack for any of affected application? > listIcons.sh output: I see duplicated entries for indicator-sound-switcher, pasystray and skype. Skype is particularly interesting because it has different names in output. My guess is on icon is SNI, second legacy icon translated by xembedsniproxy. > org.kde.StatusNotifierItem-19688-1/StatusNotifierItem > .. > The error is probably being caused by the Google Hangouts extension in > Chrome. I had NetworkManager run via systemd, but the NetworkManager icon > was disabled in the system tray. NetworkManager icon is an applet to show and manipulate NetworkManager daemon, disabling it should not affect anything. Error is interesting, but probably this is unrelated - it might be a separate issue. > See "Latest Test" attachment for a visual on the current system tray. Thanks! Images always help :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420819] error while opening database digikam will try to automatically reconnect to the database
https://bugs.kde.org/show_bug.cgi?id=420819 --- Comment #6 from Carlo Gioia --- Definitely No ... under the Tools tab, select Maintenance, one of the options is Sync metadata Database box is not green meaning not selected On Fri, May 1, 2020 at 5:47 PM Carlo Gioia wrote: > 4.0 I don't think so ... under meta data I dont see such an optio > looking through and searching The digiKam Handbook ... I only find mention > of databases on Pages 18,30,31,102 so NO > If I search under sync database in section 12.2.8 of manual says TODO > so my answer is NO > > > On Fri, May 1, 2020 at 4:36 PM wrote: > >> https://bugs.kde.org/show_bug.cgi?id=420819 >> >> caulier.gil...@gmail.com changed: >> >>What|Removed |Added >> >> >> CC||caulier.gil...@gmail.com >> >> --- Comment #4 from caulier.gil...@gmail.com --- >> Did you enable Baloo database syc in digiKam setup Metadata page ? >> >> Gilles Caulier >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420819] error while opening database digikam will try to automatically reconnect to the database
https://bugs.kde.org/show_bug.cgi?id=420819 --- Comment #5 from Carlo Gioia --- 4.0 I don't think so ... under meta data I dont see such an optio looking through and searching The digiKam Handbook ... I only find mention of databases on Pages 18,30,31,102 so NO If I search under sync database in section 12.2.8 of manual says TODO so my answer is NO On Fri, May 1, 2020 at 4:36 PM wrote: > https://bugs.kde.org/show_bug.cgi?id=420819 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > CC||caulier.gil...@gmail.com > > --- Comment #4 from caulier.gil...@gmail.com --- > Did you enable Baloo database syc in digiKam setup Metadata page ? > > Gilles Caulier > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 --- Comment #3 from Colin J Thomson --- FYI I have the same KF5 version but my my Qt Version is 5.13.2 on this F32 box and I can produce the same crash 99% of the time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 420835] Plasmashell crashes in DeclarativeMimeData::DeclarativeMimeData() on mouse hover over panel during drag & drop
https://bugs.kde.org/show_bug.cgi?id=420835 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- it seems related to bug 398440 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 --- Comment #2 from Josec --- (In reply to caulier.gilles from comment #1) > In DK 7.0.0, i recently updated the libtiff used internally. Can you > reproduce the crash with the last RC published here : > > https://files.kde.org/digikam/ > > Gilles Caulier I assume you are referring to this build? Or should I install the latest Win64 build? digiKam-7.0.0-rc-20200501T104952-Win32.exe Any issues moving from a Win64 build to a Win32 build? I am currently on: digiKam-6.4.0-Win64.exe Thx, Jose -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420875] Assigning Tag/Label makes thumbnail disappear
https://bugs.kde.org/show_bug.cgi?id=420875 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Run digiKam from a console and reproduce the dysfunction. Attach the debug trace in this file to investigate. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 420876] New: Print window too large for screen, KDE panel covers print buttons at bottom of screen
https://bugs.kde.org/show_bug.cgi?id=420876 Bug ID: 420876 Summary: Print window too large for screen, KDE panel covers print buttons at bottom of screen Product: print-manager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: jbfm...@rochester.rr.com Target Milestone: --- Created attachment 128085 --> https://bugs.kde.org/attachment.cgi?id=128085&action=edit full screen capture of Libreoffice and prin manager SUMMARY I attempted to print from a Dell Vostro 3550 laptop with Fedora 32 / KDE Spin installed; however the print window extended off the bottom of the screen (see attached print screen file) and I was only able to get to a piece of the PRINT button by auto-hiding the panel. (A scroll bar would come in handy.) I don't know if this is a general problem or one due to the specific printer addressed (its designation is shown in the attached print screen file). The printer driver selected was "Toshiba 220 gutenprint" STEPS TO REPRODUCE 1. Select and install printer driver 2. Load Document 3. Attempt to print OBSERVED RESULT Print (manager?) window extends beyond Panel and bottom of screen, where it's inaccessible. EXPECTED RESULT Entire print (manager?) would be accessible. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 - KDE Spin (installed yesterday). (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- In DK 7.0.0, i recently updated the libtiff used internally. Can you reproduce the crash with the last RC published here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420860] Widgets are bigger on Wayland with the same fractional scaling settings
https://bugs.kde.org/show_bug.cgi?id=420860 --- Comment #5 from David Edmundson --- Where is this coming from? QT_DEVICE_PIXEL_RATIO=auto that's not us. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420662] unable to type æøå in konsole
https://bugs.kde.org/show_bug.cgi?id=420662 --- Comment #2 from weeda...@gmail.com --- This seems to have fixed the problems in the console include the danish language in /etc/locale.gen file , uncomment sudo locale-gen run the system settings regional settings, formats Danmark-dansk(da_DK) reboot System language us_english format regional settings set to da_DK æøå works in console -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420875] New: Assigning Tag/Label makes thumbnail disappear
https://bugs.kde.org/show_bug.cgi?id=420875 Bug ID: 420875 Summary: Assigning Tag/Label makes thumbnail disappear Product: digikam Version: 6.4.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbs-Image Assignee: digikam-bugs-n...@kde.org Reporter: ayr...@gmail.com Target Milestone: --- SUMMARY I manage most of my photos on external hard drives. Often, I have tried to organize my collection whenever my hard drives are disconnected. However, attempting to set a tag or label on an image that resides on a disconnected drive makes the thumbnail disappear. IMO, this severely impacts the usefulness of digikam supporting removable media. STEPS TO REPRODUCE 1. Have a collection on removable media with thumbnails. 2. Add a label to an image on a removable media. 3. Observe that the thumbnail disappears. OBSERVED RESULT The thumbnail disappears. The missing thumbnail icon replaces it. EXPECTED RESULT I expect the thumbnail to remain. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 400889] View panel focuses parent on right click
https://bugs.kde.org/show_bug.cgi?id=400889 Davide Gianforte changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||dav...@gengisdave.org --- Comment #3 from Davide Gianforte --- Can you confirm on a newer version (2.7+)? Thanks -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 420807] Krusader crashes when editing a text file
https://bugs.kde.org/show_bug.cgi?id=420807 Davide Gianforte changed: What|Removed |Added CC||dav...@gengisdave.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Davide Gianforte --- Can you post the file you are editing? The use of QML is strange. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420870] Long tabs get too much of the space in tab bar
https://bugs.kde.org/show_bug.cgi?id=420870 --- Comment #6 from Christoph Feck --- Default tab widths for KDE applications are computed in QTabBar from QtWidgets library. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 415512] Krusader fails to copy files to "full" btrfs filesystem but with enough unallocated space
https://bugs.kde.org/show_bug.cgi?id=415512 Davide Gianforte changed: What|Removed |Added Version|2.7.2 |5.65.0 CC||dav...@gengisdave.org, ||kdelibs-b...@kde.org Product|krusader|frameworks-kio Component|disk-usage |general Assignee|krusader-bugs-n...@kde.org |fa...@kde.org --- Comment #1 from Davide Gianforte --- Copy operations are handled through KIO (Dolphin is affected too), moving. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 amrith changed: What|Removed |Added CC||k...@thefifthcontinent.com --- Comment #6 from amrith --- *** Bug 416155 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416155] Mouse cursor changes to a default
https://bugs.kde.org/show_bug.cgi?id=416155 amrith changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||amrith...@gmail.com --- Comment #3 from amrith --- *** This bug has been marked as a duplicate of bug 420872 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420870] Long tabs get too much of the space in tab bar
https://bugs.kde.org/show_bug.cgi?id=420870 --- Comment #5 from sdfjsfjaei-h...@yahoo.de --- Thanks for the quick response Nate! Is this actually a general Plasma thing that could be addressed? (So that all KDE apps could benefit from such a change. If that would be reasonable..) I wondered about that after having written the bug report, but wasn't sure which project to choose besides Dolphin for the report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420819] error while opening database digikam will try to automatically reconnect to the database
https://bugs.kde.org/show_bug.cgi?id=420819 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #4 from caulier.gil...@gmail.com --- Did you enable Baloo database syc in digiKam setup Metadata page ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 325422] First archive encountered during a text search is searched even when "search in archives" check box is not checked
https://bugs.kde.org/show_bug.cgi?id=325422 Davide Gianforte changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||dav...@gengisdave.org --- Comment #1 from Davide Gianforte --- Can you reproduce in a recent version (2.7+)? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 amrith changed: What|Removed |Added Flags||X11+, dpi+, Intel+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 --- Comment #4 from amrith --- Created attachment 128083 --> https://bugs.kde.org/attachment.cgi?id=128083&action=edit mouse pinter -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 --- Comment #5 from amrith --- Created attachment 128084 --> https://bugs.kde.org/attachment.cgi?id=128084&action=edit mouse pinter -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420874] New: Dolphin crashes while mooving files
https://bugs.kde.org/show_bug.cgi?id=420874 Bug ID: 420874 Summary: Dolphin crashes while mooving files Product: dolphin Version: 17.12.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 7ete...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (17.12.3) (Compiled from sources) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 5.3.0-51-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: I was moving several files from one folder to another. Folders are located on different physical disks (HDD, SATA). These both disks have NTFS file system. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc6956136c0 (LWP 27747))] Thread 7 (Thread 0x7fc653fff700 (LWP 27754)): #0 0x7fc68f0a41a0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fc68f0a29f9 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc68f0a2fd5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc68f0a461e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc687de9b28 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc687dea4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc687dea6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fc68f0a48ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc68f04990a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc68ee6823a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc68ee6d17d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fc689f5d6db in start_thread (arg=0x7fc653fff700) at pthread_create.c:463 #12 0x7fc694e9d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fc668e2e700 (LWP 27753)): #0 0x7fc689f639f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b634c3c530) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b634c3c4e0, cond=0x55b634c3c508) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b634c3c508, mutex=0x55b634c3c4e0) at pthread_cond_wait.c:655 #3 0x7fc66f0cfa0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc66f0cf607 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc689f5d6db in start_thread (arg=0x7fc668e2e700) at pthread_create.c:463 #6 0x7fc694e9d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fc66962f700 (LWP 27752)): #0 0x7fc689f639f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b634c3be30) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b634c3bde0, cond=0x55b634c3be08) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b634c3be08, mutex=0x55b634c3bde0) at pthread_cond_wait.c:655 #3 0x7fc66f0cfa0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc66f0cf607 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc689f5d6db in start_thread (arg=0x7fc66962f700) at pthread_create.c:463 #6 0x7fc694e9d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fc669e30700 (LWP 27751)): #0 0x7fc689f639f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b634a12be8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b634a12b98, cond=0x55b634a12bc0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55b634a12bc0, mutex=0x55b634a12b98) at pthread_cond_wait.c:655 #3 0x7fc66f0cfa0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc66f0cf607 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc689f5d6db in start_thread (arg=0x7fc669e30700) at pthread_create.c:463 #6 0x7fc694e9d88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fc66a631700 (LWP 27750)): #0 0x7fc689f639f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55b634c3ae80) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55b634c3ae30, cond=0x55b634c3ae58) at pthread_cond_wait.c:502 #2 __p
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 --- Comment #3 from amrith --- Created attachment 128082 --> https://bugs.kde.org/attachment.cgi?id=128082&action=edit mouse hover small -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 --- Comment #2 from amrith --- Created attachment 128081 --> https://bugs.kde.org/attachment.cgi?id=128081&action=edit mouse cursor large -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 amrith changed: What|Removed |Added CC||amrith...@gmail.com --- Comment #1 from amrith --- Created attachment 128080 --> https://bugs.kde.org/attachment.cgi?id=128080&action=edit Mouse cursor small on 150% scaling but becomes scaled on hovering over widgets or buttons -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 331576] password needed at dialog every connect
https://bugs.kde.org/show_bug.cgi?id=331576 --- Comment #5 from Achmad Fathoni --- KRDC still asking password everytime in KDE Neon 18.04. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420870] Long tabs get too much of the space in tab bar
https://bugs.kde.org/show_bug.cgi?id=420870 sdfjsfjaei-h...@yahoo.de changed: What|Removed |Added Attachment #128074|0 |1 is obsolete|| --- Comment #4 from sdfjsfjaei-h...@yahoo.de --- Created attachment 128079 --> https://bugs.kde.org/attachment.cgi?id=128079&action=edit Python program to illustrate how the size could be calculated (bug fixed) removed the default complex part that was actually buggy for very very long tab names. Now all it does is append 'current + (average - current)*0.65' to a list, and then use that list as weights for the tab size. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 331576] password needed at dialog every connect
https://bugs.kde.org/show_bug.cgi?id=331576 Achmad Fathoni changed: What|Removed |Added Platform|Ubuntu Packages |Neon Packages Version|4.11.3 |19.12 CC||fathoni...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416814] Krita crashes when using spray brush on a alpha-locked layer converted from a vector layer
https://bugs.kde.org/show_bug.cgi?id=416814 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|ASSIGNED|RESOLVED --- Comment #5 from Dmitry Kazakov --- Well, I think I'll better just close the bug. We don't really support building Krita in Debug mode :) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 314416] repeated reload on sftp folder may lead to connection loss
https://bugs.kde.org/show_bug.cgi?id=314416 Davide Gianforte changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||dav...@gengisdave.org --- Comment #2 from Davide Gianforte --- Can you reproduce with a recent version (2.7+)? I tried on the latest code and I never lost the connection. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420727] digiKam-Window and all Sub-Windows are enlarged too much
https://bugs.kde.org/show_bug.cgi?id=420727 Peter Eszlari changed: What|Removed |Added CC||peter.eszl...@gmail.com --- Comment #25 from Peter Eszlari --- Why not use C++ instead? QCoreApplication::setAttribute(Qt::AA_UseHighDpiPixmaps, true); QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling, true); Krita makes this configurable through the GUI: https://invent.kde.org/kde/krita/-/blob/ae915410fea8ce5a6024689dd19df763b08386d4/krita/main.cc#L239 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420831] Dolphin can't copy files and directories to a symlinked directory
https://bugs.kde.org/show_bug.cgi?id=420831 techxga...@outlook.com changed: What|Removed |Added Summary|Dolphin can't copy folders |Dolphin can't copy files |to another directory|and directories to a ||symlinked directory -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420831] Dolphin can't copy folders to another directory
https://bugs.kde.org/show_bug.cgi?id=420831 --- Comment #3 from techxga...@outlook.com --- Created attachment 128078 --> https://bugs.kde.org/attachment.cgi?id=128078&action=edit Files and directories can't copy to symlink directory The only way it'll work is if I go DIRECTLY to the directory. When I tried forcing it, the symlink got deleted, and I had to redo it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420819] error while opening database digikam will try to automatically reconnect to the database
https://bugs.kde.org/show_bug.cgi?id=420819 --- Comment #3 from Carlo Gioia --- Maik i am attaching a 2nd log ... this time I opened Konsole, started Dolphin, from Dolphin selected directory, then I chose to open using dijikam this is how I do not get the database error I hope this helps On Fri, May 1, 2020 at 3:33 PM Carlo Gioia wrote: > Good day Maik, and thank you for helping. > 1.0 Based on your question I did some checking and found that i did have > the restore previous session option on ... I changed the option to start > with empty session shut down restarted and came up clean (dijikan did > not start until I clicked to start program > 2.0 Using Image editor, settings, configure digikam, database, type says > SQLite > 3.0 started using Konsole ran app ... after waiting a while I cancelled > app so you would see rest of text text is attached > > Regards Carlo > > > On Thu, Apr 30, 2020 at 4:14 PM Maik Qualmann > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=420819 >> >> Maik Qualmann changed: >> >>What|Removed |Added >> >> >> CC||metzping...@gmail.com >> Status|REPORTED|NEEDSINFO >> Resolution|--- |WAITINGFORINFO >> >> --- Comment #1 from Maik Qualmann --- >> I can't do much with the bug report ... Let's start: >> 1. Why is digiKam running when Manjaro is started? Did you activate any >> session >> management? >> 2. What type of database are you using? SQLite or MySQL? >> 3. Please start digiKam in the console and post the log. >> >> If the database is on a drive that has not yet been mounted, the error >> message >> would be normal. Make sure that the database is available when digiKam is >> started. Deactivate session management so that not all programs are >> restarted. >> >> Maik >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 419465] Wallet failed to get opened by PAM, error code is -9
https://bugs.kde.org/show_bug.cgi?id=419465 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org --- Comment #7 from Andre Woebbeking --- I've this problem after updating Kubuntu 18.04 to 20.04. I also get error code -9. My home folder is encrypted with encrypfs and libpam-wallet* is version 5.18.4. After reading this I also downgraded libpam-wallet* to 5.18.3 (from eoan updates) and it works. But only when I login the first time after booting. When I logout and relogin I get error code -9 again. So I tried 5.18.4 again but that seems to be broken first and second login (I rebooted after upgrading). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420873] New: Lockscreen: external 4k monitor background image not scaled by my global x11 scalefactor of 150%
https://bugs.kde.org/show_bug.cgi?id=420873 Bug ID: 420873 Summary: Lockscreen: external 4k monitor background image not scaled by my global x11 scalefactor of 150% Product: plasmashell Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: a...@mpe.mpg.de Target Milestone: 1.0 Created attachment 128076 --> https://bugs.kde.org/attachment.cgi?id=128076&action=edit xrandr output off laptop screen off, external 4k Monitor on SUMMARY I've a 4k monitor connected to a laptop (laptop display turned off). xrandr output attached. My global x11 scale factor is 150 %. Plasma is configured to not goto sleep when connected to power. STEPS TO REPRODUCE 1. do noting until lockscreen is shown OBSERVED RESULT 1/3 on the right and lower part of the 4k Monitor is black. Other 2/3 shows the my background picture (kite) EXPECTED RESULT lock screen shows the kite background picture scaled 150% and therefore fills the complete screen size (as done when the Plasma session is active). SOFTWARE/OS VERSIONS Linux: KDE Neon User Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-46-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION When I turn of the monitor when I stop working (xrandr output does not change!) and turn it on later, the lock screen fills the complete external monitor size as it should be. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420872] New: Incorrect scaling of mouse cursor on 150%
https://bugs.kde.org/show_bug.cgi?id=420872 Bug ID: 420872 Summary: Incorrect scaling of mouse cursor on 150% Product: kwin Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: vit...@easycoding.org Target Milestone: --- SUMMARY Incorrect scaling of mouse pointer on 150% on mouse over window title, on desktop widget and some window controls, like checkboxes. Screenshots: https://imgur.com/a/OziChRx Regression in 5.18.x. On 5.17.5 everything works fine. STEPS TO REPRODUCE 1. Set screen scaling to 150%. 2. Navigate mouse pointer to window title or desktop widget. 3. OBSERVED RESULT Very small mouse pointer. EXPECTED RESULT Scaled mouse pointer. SOFTWARE/OS VERSIONS Operating System: Fedora 32 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 Kernel Version: 5.6.7-300.fc32.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420831] Dolphin can't copy folders to another directory
https://bugs.kde.org/show_bug.cgi?id=420831 --- Comment #2 from techxga...@outlook.com --- Tried that and it won't work. Then I remembered that ~/Music is a symlink to /home/HDD/$USER/Music. That's when it didn't work -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420843] Easy Working with clip and offset timestamps
https://bugs.kde.org/show_bug.cgi?id=420843 emohr changed: What|Removed |Added Flags||Brainstorm+ CC||fritzib...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420870] Long tabs get too much of the space in tab bar
https://bugs.kde.org/show_bug.cgi?id=420870 Nate Graham changed: What|Removed |Added Keywords||usability CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Nate Graham --- Yeah I agree this could use a bit of polishing to make sure that tabs with long text can't infinitely expand. One solution could be to make all tabs auto-expand so they're all the same width. I'm sure there are other options. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420819] error while opening database digikam will try to automatically reconnect to the database
https://bugs.kde.org/show_bug.cgi?id=420819 --- Comment #2 from Carlo Gioia --- Good day Maik, and thank you for helping. 1.0 Based on your question I did some checking and found that i did have the restore previous session option on ... I changed the option to start with empty session shut down restarted and came up clean (dijikan did not start until I clicked to start program 2.0 Using Image editor, settings, configure digikam, database, type says SQLite 3.0 started using Konsole ran app ... after waiting a while I cancelled app so you would see rest of text text is attached Regards Carlo On Thu, Apr 30, 2020 at 4:14 PM Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=420819 > > Maik Qualmann changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Maik Qualmann --- > I can't do much with the bug report ... Let's start: > 1. Why is digiKam running when Manjaro is started? Did you activate any > session > management? > 2. What type of database are you using? SQLite or MySQL? > 3. Please start digiKam in the console and post the log. > > If the database is on a drive that has not yet been mounted, the error > message > would be normal. Make sure that the database is available when digiKam is > started. Deactivate session management so that not all programs are > restarted. > > Maik > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420871] New: Dolphin freezes when cut+pasting a file onto an identically named file while android is connected
https://bugs.kde.org/show_bug.cgi?id=420871 Bug ID: 420871 Summary: Dolphin freezes when cut+pasting a file onto an identically named file while android is connected Product: dolphin Version: 20.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: antti.s...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Demonstrative video: https://youtu.be/YFic0U8QPa8 In that video I first demonstrate that copy+paste and cut+paste works perfectly fine. Then I connect an android device and open up the location once (this will not work if you do not open the device location) and do the same copy+paste and cut+paste demonstration again. The program freezes. The transferred files don't have to be on the android device. STEPS TO REPRODUCE 1. Open dolphin 2. Connect an android device in file transfer mode 3. Open the android file location once 4. Cut a file from a location to another location that already contain that file OBSERVED RESULT Dolphin freezes for a good minute EXPECTED RESULT No freeze should happen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, updated on 2020-04-30 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420870] Long tabs get too much of the space in tab bar
https://bugs.kde.org/show_bug.cgi?id=420870 --- Comment #2 from sdfjsfjaei-h...@yahoo.de --- Created attachment 128074 --> https://bugs.kde.org/attachment.cgi?id=128074&action=edit Python program to illustrate how the size could be calculated -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420870] Long tabs get too much of the space in tab bar
https://bugs.kde.org/show_bug.cgi?id=420870 --- Comment #1 from sdfjsfjaei-h...@yahoo.de --- Created attachment 128073 --> https://bugs.kde.org/attachment.cgi?id=128073&action=edit window with multiple tabs open (wide window) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420870] New: Long tabs get too much of the space in tab bar
https://bugs.kde.org/show_bug.cgi?id=420870 Bug ID: 420870 Summary: Long tabs get too much of the space in tab bar Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: sdfjsfjaei-h...@yahoo.de CC: kfm-de...@kde.org Target Milestone: --- Created attachment 128072 --> https://bugs.kde.org/attachment.cgi?id=128072&action=edit window with multiple tabs open (thin window) SUMMARY While it totally makes sense that tabs with a lot of text get a lot of the space, there should be some limit, because the shorter the tab text, the more important each letter is for recognizing which folder that tab corresponds to. STEPS TO REPRODUCE 1. on command line: cd /tmp && mkdir test && cd test && mkdir "2019 - normal folder name" && mkdir "relatively short folder name" && mkdir "this is a very long folder name that dominates all other tabs which seems a bit suboptimal since the user probably would be okay with just the beginning" This is what the directory tree looks like: /tmp/test ├── 2019 - normal folder name ├── relatively short folder name └── this is a very long folder name that dominates all other tabs which seems a bit suboptimal since the user probably would be okay with just the beginning 2. Enter /tmp/test in Dolphin and open the tabs in Dolphin OBSERVED RESULT The tab for the folder with the very long name takes almost all the space of the tab bar. Resizing the window gives the tab that's already pretty long even more space. (See attachments.) EXPECTED RESULT For the tabs with little text to get enough space to make them (more) readable. I actually had the problem where a long folder name was making it hard to discern what the other tabs contain. I've attached a Python file to illustrate how that algorithm could work. (Basically it adds the length of each tab text to a list. Then it brings each length in that list nearer to the average of said list.) This is the output: # length name 25:2019 - normal folder name 28:relatively short folder name 152:this is a very long folder name that dominates all other tabs which seems a bit suboptimal since the user probably would be okay with just the beginning average tab length: 68.33 43.78:2019 - normal folder name 44.27:relatively short folder name 82.00:this is a very long folder name that dominates all other tabs which seems a bit suboptimal since the user probably would be okay with just the beginning Simulate tab bar (I know it's a lot more complex in reality) | 2019 - normal fold… | relatively short f… | this is a very long folder name t… | SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 It would be cool if someone could test if this is still an issue in the latest version. (following the above steps to reproduce). Thanks for KDE =) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420869] New: Certain Tray icons using wrong color from system color scheme
https://bugs.kde.org/show_bug.cgi?id=420869 Bug ID: 420869 Summary: Certain Tray icons using wrong color from system color scheme Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: osman.keshaw...@gmail.com Target Milestone: 1.0 Created attachment 128071 --> https://bugs.kde.org/attachment.cgi?id=128071&action=edit Dropbox and Steam icons change based on color scheme, not panel color SUMMARY Yet another infuriating icon color problem with Dropbox and Steam (and likely other status icons). When using a dark panel with a dark color scheme (In this case, Breeze Dark for the Plasma theme and Breeze for the color scheme, but I tried a number of different dark-light combinations), all of tray icons will switch to the correct color, except for Dropbox and Steam. When using a dark color scheme with a dark panel, the icons are fine. This seems to happen for all icon themes that draw from the system color scheme (I tried with Breeze and Papirus), so it doesn't seem to be a problem with the icons themselves. This persists even after logout, etc. I initially thought that this might be related to https://bugs.kde.org/show_bug.cgi?id=418662, but I can reproduce it very reliably and the icons haven't disappeared-- they just take the wrong color. STEPS TO REPRODUCE 1. Choose a dark panel with dark colors (e.g., Breeze Dark for both). Icons show normally. 2. Switch to a light color scheme OBSERVED RESULT see attachment EXPECTED RESULT Dropbox and Steam icons should match the other tray icons SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Unstable KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420854] Add an option for task manager to sync pinned programs across containments
https://bugs.kde.org/show_bug.cgi?id=420854 --- Comment #2 from qik0...@gmail.com --- (In reply to Nate Graham from comment #1) > Is the use case that you would like for each of your monitors to show an > identical panel? Yes, this is specifically for multi-monitor users -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 420094] No blur in menus
https://bugs.kde.org/show_bug.cgi?id=420094 Rolf Eike Beer changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Rolf Eike Beer --- Thanks for reporting that back. I honestly had no idea what could have caused this either. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420868] New: Random crashes, no error messages. Windows event report follows, suspect TIFF plugin
https://bugs.kde.org/show_bug.cgi?id=420868 Bug ID: 420868 Summary: Random crashes, no error messages. Windows event report follows, suspect TIFF plugin Product: digikam Version: 6.4.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Plugin-FilesIO-TIFF Assignee: digikam-bugs-n...@kde.org Reporter: jose...@hotmail.com Target Milestone: --- Created attachment 128070 --> https://bugs.kde.org/attachment.cgi?id=128070&action=edit AppCrash_digikam.exe_a87d1e1185b15a95c10681922e9142fba9f2de9_c7f11afd_ed8f20f2-9109-4a94-8e25-1c259616768b SUMMARY DigiKam randomly shuts down in middle of operation, Windows event viewer reports crash. Noticed when browsing photos and assigning tags, thankfully have not noticed data loss. STEPS TO REPRODUCE 1. Happens randomly, have not noticed a specific scenario which consistently crashes. 2. So far have only noticed it when browsing photos and assigning, editing tags. 3. OBSERVED RESULT program randomly shuts down EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Windows Error Report: Fault bucket 1571343157546872218, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: digikam.exe P2: 0.0.0.0 P3: 5db9dcc2 P4: DImg_TIFF_Plugin.dll P5: 0.0.0.0 P6: 5db9dbe1 P7: c005 P8: 49b0 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB433.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB8E7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB907.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB905.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB926.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_digikam.exe_a87d1e1185b15a95c10681922e9142fba9f2de9_c7f11afd_e5ba78da-4899-4a1a-9221-df312fe418bb Analysis symbol: Rechecking for solution: 0 Report Id: 9112c18d-7b9a-41d6-9c45-7d76c4954f77 Report Status: 268435456 Hashed bucket: df429d41379e121e45ce8846c5d26d9a Cab Guid: 0 Windows Application Error: Faulting application name: digikam.exe, version: 0.0.0.0, time stamp: 0x5db9dcc2 Faulting module name: DImg_TIFF_Plugin.dll, version: 0.0.0.0, time stamp: 0x5db9dbe1 Exception code: 0xc005 Fault offset: 0x49b0 Faulting process id: 0x2cb8 Faulting application start time: 0x01d61f872be1b561 Faulting application path: C:\Program Files\digiKam\digikam.exe Faulting module path: C:\Program Files\digiKam\plugins\digikam\dimg\DImg_TIFF_Plugin.dll Report Id: 24917a6c-ff25-4167-aed6-652e45852d4b Faulting package full name: Faulting package-relative application ID: -- You are receiving this mail because: You are watching all bug changes.
