[kdeconnect] [Bug 433051] New: disable send completed notification when already notified by other means
https://bugs.kde.org/show_bug.cgi?id=433051 Bug ID: 433051 Summary: disable send completed notification when already notified by other means Product: kdeconnect Version: unspecified Platform: Android OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: gwmeeqqhvjyhpan...@ttirv.org Target Milestone: --- A successful send makes a phone notification, which persists until removed manually, but it is often unnecessary for me, as I mostly use Send file as a quick alternative to bluetooth/cable to exchange files with the PC. For example: - if I have the PC in front of me, the PC notification is enough and auto-destroys after a few seconds; - if the file is not to be used right away after receiving, e.g. I send and forget it, or send a big file and do another task. What about an option to disable the notification or make it time-based? For clarity, I do not ask for a general "don't disturb" mode (in fact I want other notifications), but to disable it when already notified by other means. I'm on kde connect 1.16 (not available as an option in bugzilla's form) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 433052] New: Feature request: numeric keypad
https://bugs.kde.org/show_bug.cgi?id=433052 Bug ID: 433052 Summary: Feature request: numeric keypad Product: kdeconnect Version: unspecified Platform: Android OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: gwmeeqqhvjyhpan...@ttirv.org Target Milestone: --- It would be a nice addition when entering a lot of numbers on a netbook or small Mac. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 433053] New: krunner prefers to open scripts as text files
https://bugs.kde.org/show_bug.cgi?id=433053 Bug ID: 433053 Summary: krunner prefers to open scripts as text files Product: krunner Version: 5.21.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: locations Assignee: alexander.loh...@gmx.de Reporter: fab...@ritter-vogt.de CC: plasma-b...@kde.org Target Milestone: --- Found by openQA: https://openqa.opensuse.org/tests/1632489#step/libqt5_qtbase/25 It types "/usr/sbin/yast2 inst_release_notes" to run that as a command, but krunner defaults to open /usr/sbin/yast2 in kate instead. The second argument is ignored. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426280] Animation speed in System Settings has no effect
https://bugs.kde.org/show_bug.cgi?id=426280 --- Comment #14 from Till Schäfer --- Can we just delete that line whenever the animation time in the kcm is changed? This would be somewhat self-healing. Is that setting still in use for something? Otherwise, is it possible to autoremove/ignore that line? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 433054] New: impossible unlock screen after upgrade to plasma 5.21
https://bugs.kde.org/show_bug.cgi?id=433054 Bug ID: 433054 Summary: impossible unlock screen after upgrade to plasma 5.21 Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: w...@culturanuova.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. lock the screen (meta+L) 2. doesn't appear any place to type the password, only cursor arrow is visible 3. impossible unlock the screen OBSERVED RESULT as I said: because it is impossible unlock the screen, I am forced to reboot EXPECTED RESULT a field where insert the password should appear and, after inserted the pws, the screen should be unlocked SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Graphics Platform: X11 Processors: 2 × Intel® Core™ i3-7100 CPU @ 3.90GHz Memory: 7,7 GiB of RAM Graphics Processor: GeForce GT 710/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 398465] Tray of optical device closes itself when a disc is ejected
https://bugs.kde.org/show_bug.cgi?id=398465 Matevž Jekovec changed: What|Removed |Added CC||matevz.jeko...@gmail.com --- Comment #22 from Matevž Jekovec --- Confirming this bug in updated KUbuntu 20.04. Workaround from comment 6 https://bugs.kde.org/show_bug.cgi?id=398465#c6 works. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433017] plasma-firewall depends on python2 instead of python3
https://bugs.kde.org/show_bug.cgi?id=433017 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com --- Comment #2 from Manuel Geißer --- Yeah, I can confim that - It even seems to depend on the python-is-python2 symlink regulation package... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431147] [Wayland] Right click menu disappears on mouse hover
https://bugs.kde.org/show_bug.cgi?id=431147 --- Comment #7 from tro...@free.fr --- Nope, it is not fixed in 5.21, still happening. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 433055] New: warn prominently to only pair to trusted devices
https://bugs.kde.org/show_bug.cgi?id=433055 Bug ID: 433055 Summary: warn prominently to only pair to trusted devices Product: kdeconnect Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: gwmeeqqhvjyhpan...@ttirv.org Target Milestone: --- The security model is well-known among developers to be "based on the assumption that 1) you only pair with a device you trust" (quote from #424889 comment 3). This should be displayed prominently prior to pairing. It is not self-evident in the GUI. The need to explain in the bugzilla and the various open bugreports based on the wrong assumption are proof. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433042] Intrack transition doesnt work properly
https://bugs.kde.org/show_bug.cgi?id=433042 Mohammed changed: What|Removed |Added Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #2 from Mohammed --- (In reply to Vincent PINON from comment #1) > There should be a warning message in the status bar that to create a > cross-fade you need extra-frames available after the end of 1st clip and > before the beginning of 2nd clip, so both must have been cut before trying > to apply the fade... Hi Sir:- Why should I cut both clips? sometimes I had no warning. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] New: Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 Bug ID: 433056 Summary: Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates) Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: geisse...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Before the updates from 16th Feb afternoon, when holding down a key for a longer time, it got correctly interpreted as repeated key presses, so that holding down a key would repeat that character or action with a fixed speed as long as the key is pressed. This is very useful for del/backspace in particular and definetely the desired behaviour. Yesterday's updates to Plasma 5.21 broke that. Holding down a key only triggers the action one time, and does not recognise that it should actually be repeated. I personally find this behaviour rather disturbing for my workflow. STEPS TO REPRODUCE 1. Use up-to-date KDE Neon User 2. hold down a key (space or backspace, for instance) -> the action won't be repeated as it should OBSERVED RESULT When holding down a key, it gets interpreted as one single key press and is not repeated EXPECTED RESULT While a key is held down, its actions should be repeated. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Graphics Platform: Wayland ADDITIONAL INFORMATION Both Wayland and X11 are affected My input method is set to ibus as described in https://bugs.kde.org/show_bug.cgi?id=411729#c4 (but reverting the environment variables related to ibus didn't change anything) Since I have no clue which of the many packages updated with the move to Plasma 5.21 is causing this bug, I decided to report this here in Neon issues. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433056] Holding down a key doesn't get interpreted as key repetition (broken by yesterday's plasma updates)
https://bugs.kde.org/show_bug.cgi?id=433056 Manuel Geißer changed: What|Removed |Added CC||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 433057] New: Error 1050 when writing SQL-Database
https://bugs.kde.org/show_bug.cgi?id=433057 Bug ID: 433057 Summary: Error 1050 when writing SQL-Database Product: kmymoney Version: 5.0.6 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: major Priority: NOR Component: database Assignee: kmymoney-de...@kde.org Reporter: thomas.conzelm...@gmx.net Target Milestone: --- Created attachment 135753 --> https://bugs.kde.org/attachment.cgi?id=135753&action=edit Details Error Description and settings SUMMARY When writing the Database into an SQL MariaDB DB, subject error occurs. The complete message is: In die aktuelle Datenbank kann nicht geschrieben werden: Error in function void MyMoneyStorageSqlPrivate::createTable(const MyMoneyDbTable&, int) : creating table/index kmmAccounts Driver = QODBC, Host = 192.168.2.39, User = _kmy_db_test, Database = _kmy_db_test Driver Error: Database Error No -1: Text: Error type 0 Executed: Query error No 1050: [ma-3.1.11][10.3.21-MariaDB-log]Table 'kmmAccounts' already exists QODBC3: Unable to execute statement Error type 2 /home/abuild/rpmbuild/BUILD/kmymoney-5.0.6/kmymoney/plugins/sql/mymoneystoragesql_p.h:2582 The database "_kmy_db_test" on the MariaDB server exists. I was able to create the tables with KMyMoney, which is an indication to me, that the connection to the database is successfully established (see Details in the Attachment) and the user "_kmy_db_test" has sufficient rights. STEPS TO REPRODUCE 1. Menue File - Save as - Format = "SQL" - Databasetype ="Open Database Connectivity" OBSERVED RESULT Subject error message, no record is written into the database. Writing the data into a SQLite Format is succfussful as well writing into XML. EXPECTED RESULT Data should be written into the MariaDB database. SOFTWARE/OS VERSIONS Windows: 10, 64bit macOS: na Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: KDE Frameworks 5.47.0 Qt Version: Qt 5.9.1 (kompiliert gegen 5.9.1) ADDITIONAL INFORMATION MariaDB is running on a remote Linux NAS (Synology DS). Port 3307 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 432474] baloo_file core dump on every system boot
https://bugs.kde.org/show_bug.cgi?id=432474 --- Comment #2 from Amin Vakil --- I asked this on archlinux irc channels and someone replied me: "known issue, it's fixed in 5.78 but you need to regenerate the index balooctl purge" And it got fixed for me. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 433057] Error 1050 when writing SQL-Database
https://bugs.kde.org/show_bug.cgi?id=433057 Thomas_C changed: What|Removed |Added CC||thomas.conzelm...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 432699] Effects list's filter field does not work for CJK characters
https://bugs.kde.org/show_bug.cgi?id=432699 --- Comment #2 from Tyson Tan --- Krita 4.4.x haven't yet support unicode for its resource items. The upcoming Krita 5.0.0 was said to have unicode support, but the lastest nightly version still haven't implemented the feature. digiKam have a working implementation of CJK-enabled text filter. I've just tested it on digiKam 7.2.0 RC. I can assign a CJK tag, then filter the result using the text filter. But I'm not sure the differences between a user-assigned tag and resource names. I'm not a programmer, so I might not be of much help here. Last time something similar happened on https://docs.krita.org/ , which was built using Sphinx. It can't tell a keyword without space, or it can't search letter by letter (which is how CJK search behaves) which might be a common cause of this kind of bugs. The bug report can be found here: https://bugs.kde.org/show_bug.cgi?id=419321 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 432888] Impossible to install two or more variants of an addon from KDE Store
https://bugs.kde.org/show_bug.cgi?id=432888 Dan Leinir Turthra Jensen changed: What|Removed |Added Severity|normal |wishlist Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Dan Leinir Turthra Jensen --- Entirely correct, and i do want to make it possible to co-install multiple things. However, it is annoyingly not a straightforward problem, as we cannot simply assume that co-installability is a given for all types of content. But, it's something that definitely wants to be possible, so i'll mark this as a wishlist item and confirmed. Also, in case you think you remember that this used to be possible with the old dialog - yes, it was possible to pick a new thing in the UI, but what would in reality happen is that knewstuff would leave a pile of stuff on your system that it no longer knew about, and which was then no longer managed by something on the system. Littering systems with unmanaged data isn't really an acceptable thing to do, so we didn't implement that particular misfeature in the qtquick components :) -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 433058] New: Event view box remains empty after cliking on an event / right-clicking and clicking on "view"
https://bugs.kde.org/show_bug.cgi?id=433058 Bug ID: 433058 Summary: Event view box remains empty after cliking on an event / right-clicking and clicking on "view" Product: korganizer Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: warbea...@pm.me Target Milestone: --- Created attachment 135754 --> https://bugs.kde.org/attachment.cgi?id=135754&action=edit Right-click pop-up is empty. STEPS TO REPRODUCE 1. Open KOrganizer. 2. Click on any event / right-click on any event and click on "view" in the contextual menu. OBSERVED RESULT The event details viewer box on the left remains empty, as the pop-up appearing when right-clicking. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.15-1-MANJARO KOrganizer Version 5.16.2 (20.12.2) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 402244] breeze.so breaks Qt application layout settings
https://bugs.kde.org/show_bug.cgi?id=402244 --- Comment #3 from mathieu.westp...@kitware.com --- Tbh I have no idea. You can try with an old version of ParaView, eg ParaView 5.5. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433059] New: Can no longer change the "Active\Inactive Titlebar" color of Breeze Dark (Plasma 5.21)
https://bugs.kde.org/show_bug.cgi?id=433059 Bug ID: 433059 Summary: Can no longer change the "Active\Inactive Titlebar" color of Breeze Dark (Plasma 5.21) Product: Breeze Version: 5.21.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: window decoration Assignee: plasma-b...@kde.org Reporter: anon...@openmailbox.org CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY Sorry if I worded this in an odd way, English is not my primary language. That being said, something I always did was clone the default Breeze Dark theme and then edit it. One thing I like is having two very different active and inactive titlebar colors. In Plasma 5.21 the titlebar color can no longer be changed from what I can tell, because the changes to the color do not apply. STEPS TO REPRODUCE 1. Edit Breeze Dark by changing the active titlebar color 2. save the changed theme 3. Apply the theme OBSERVED RESULT Titlebar color setting is ignored EXPECTED RESULT Titlebar color setting is applied SOFTWARE/OS VERSIONS ADDITIONAL INFORMATION It seems like this only affects Breeze Dark and copies of it. Other color schemes will apply changed titlebar colors. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433060] New: inconsistency between metadata displayed and metadata taken in account to rename
https://bugs.kde.org/show_bug.cgi?id=433060 Bug ID: 433060 Summary: inconsistency between metadata displayed and metadata taken in account to rename Product: digikam Version: 7.2.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: AdvancedRename Assignee: digikam-bugs-n...@kde.org Reporter: digi...@donaflor.fr Target Milestone: --- SUMMARY inconsistency between metadata displayed and metadata taken in account to rename STEPS TO REPRODUCE 1. modify DateTimeoriginal of a photo of a Digikam album with an external tool 2. scan for new items 3. to display DateTimeoriginal of the photo into metadata panel/exif 4. to rename the photo (F2) with [date:-MM-dd_hh'h'mm-ss] option OBSERVED RESULT DateTimeOriginal displayed into the metadata panel/exif is the new date the new name of the photo is unchanged (it is based on the old date) EXPECTED RESULT consistency between metadata displayed and metadata taken in account to rename SOFTWARE/OS VERSIONS: Linux/KDE Plasma: Manjaro/KDE KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION re-read metadata from file solves the problem -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432970] Tab bar now shows the end of the hostname
https://bugs.kde.org/show_bug.cgi?id=432970 --- Comment #4 from ric...@nakts.net --- Right, I thought you had a specific request/commit in mind :) Although, if we cannot find specific reasons, perhaps the change was accidental after all? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 432460] Logout sometimes doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=432460 Fabian Vogt changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||81d61861608012e4d7a19e6f85b ||8d136c298f31f --- Comment #12 from Fabian Vogt --- Git commit 81d61861608012e4d7a19e6f85b8d136c298f31f by Fabian Vogt, on behalf of David Edmundson. Committed on 16/02/2021 at 16:46. Pushed by davidedmundson into branch 'master'. [libkworkspace] Interim fix for the logout issue Calls to a DBus activated service can fail if the sender quits whilst the service is spawning (https://gitlab.freedesktop.org/dbus/dbus/-/issues/72) and using dbus-daemon. This is a lazy interim fix that just makes these calls block as proper fixes will require more work. M +6-6libkworkspace/sessionmanagement.cpp https://invent.kde.org/plasma/plasma-workspace/commit/81d61861608012e4d7a19e6f85b8d136c298f31f -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 432460] Logout sometimes doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=432460 David Edmundson changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |81d61861608012e4d7a19e6f85b |74fef0a9973e62df16ff8fc97a7 |8d136c298f31f |95bce1fa2a273 --- Comment #13 from David Edmundson --- Git commit 74fef0a9973e62df16ff8fc97a795bce1fa2a273 by David Edmundson. Committed on 17/02/2021 at 09:32. Pushed by davidedmundson into branch 'Plasma/5.21'. [libkworkspace] Interim fix for the logout issue Calls to a DBus activated service can fail if the sender quits whilst the service is spawning (https://gitlab.freedesktop.org/dbus/dbus/-/issues/72) and using dbus-daemon. This is a lazy interim fix that just makes these calls block as proper fixes will require more work. (cherry picked from commit 81d61861608012e4d7a19e6f85b8d136c298f31f) M +6-6libkworkspace/sessionmanagement.cpp https://invent.kde.org/plasma/plasma-workspace/commit/74fef0a9973e62df16ff8fc97a795bce1fa2a273 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432970] Tab bar now shows the end of the hostname
https://bugs.kde.org/show_bug.cgi?id=432970 tcanabr...@kde.org changed: What|Removed |Added CC||tcanabr...@kde.org --- Comment #5 from tcanabr...@kde.org --- perhaps it's a longshot, but have you considered to use colors, or split screen for those? tabs *will* be to crowded and we will need to remove parts of the name. on the splits, if you open them horizontally, you will have the full name of the sessions at all times, and you can expand / shrink them when you need to work on something fullscreen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430622] Panel applet margins are bigger with compositing turned on than with it turned off
https://bugs.kde.org/show_bug.cgi?id=430622 --- Comment #19 from Serdar Tasel --- Created attachment 135755 --> https://bugs.kde.org/attachment.cgi?id=135755&action=edit Icon size 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 430622] Panel applet margins are bigger with compositing turned on than with it turned off
https://bugs.kde.org/show_bug.cgi?id=430622 --- Comment #20 from Serdar Tasel --- Apparently, the problem persists with the update to Plasma version 5.21. Morever, the space between icons increased. Disabling compositor changes the icon size to the expected height as the spacing between icons remain. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432364] [systemd] plasma-ksmserver.service blocks boot if ksplash is disabled
https://bugs.kde.org/show_bug.cgi?id=432364 hchain changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||e7e49916712d2d8efc65d7da172 ||1eb1d31dc65d6 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from hchain --- Git commit e7e49916712d2d8efc65d7da1721eb1d31dc65d6 by Henri Chain, on behalf of David Edmundson. Committed on 17/02/2021 at 09:53. Pushed by davidedmundson into branch 'master'. Move ksmserver's ksplash notifying to ksmserver Previously the call to ksplash was being emitted by plasma-session. This isn't used in the systemd startup so it was introduced in a somewhat messy script. This script has an issue: If ksplash is disabled the bus name won't be registered. Typically this isn't an issue. However to avoid a race condition ksplash registers itself as being DBus activatable, so that the dbus server holds dispatching the message. This combo means ksmserver our unit is considered as not running until our script times out. This then defers other things in the chain that depend on ksmserver. Moving the call into the relevant piece of code into ksmserver unifies things into a single path and gives us more control. M +0-2ksmserver/plasma-ksmserver.service.in M +7-0ksmserver/server.cpp M +0-1startkde/plasma-session/startup.cpp https://invent.kde.org/plasma/plasma-workspace/commit/e7e49916712d2d8efc65d7da1721eb1d31dc65d6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432364] [systemd] plasma-ksmserver.service blocks boot if ksplash is disabled
https://bugs.kde.org/show_bug.cgi?id=432364 David Edmundson changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |e7e49916712d2d8efc65d7da172 |a3f5ac1296e93eefaca1f70d48c |1eb1d31dc65d6 |6c03c688f3946 --- Comment #7 from David Edmundson --- Git commit a3f5ac1296e93eefaca1f70d48c6c03c688f3946 by David Edmundson. Committed on 17/02/2021 at 09:58. Pushed by davidedmundson into branch 'Plasma/5.21'. Move ksmserver's ksplash notifying to ksmserver Previously the call to ksplash was being emitted by plasma-session. This isn't used in the systemd startup so it was introduced in a somewhat messy script. This script has an issue: If ksplash is disabled the bus name won't be registered. Typically this isn't an issue. However to avoid a race condition ksplash registers itself as being DBus activatable, so that the dbus server holds dispatching the message. This combo means ksmserver our unit is considered as not running until our script times out. This then defers other things in the chain that depend on ksmserver. Moving the call into the relevant piece of code into ksmserver unifies things into a single path and gives us more control. (cherry picked from commit e7e49916712d2d8efc65d7da1721eb1d31dc65d6) M +0-2ksmserver/plasma-ksmserver.service.in M +7-0ksmserver/server.cpp M +0-1startkde/plasma-session/startup.cpp https://invent.kde.org/plasma/plasma-workspace/commit/a3f5ac1296e93eefaca1f70d48c6c03c688f3946 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 279592] Allow per-application color scheme
https://bugs.kde.org/show_bug.cgi?id=279592 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 433061] New: mixed order of math excersizes
https://bugs.kde.org/show_bug.cgi?id=433061 Bug ID: 433061 Summary: mixed order of math excersizes Product: gcompris Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: rolasor...@gmail.com Target Milestone: --- Created attachment 135756 --> https://bugs.kde.org/attachment.cgi?id=135756&action=edit order of math excersizes the order of the tasks maybe better "Addition memory game" (memory-math-add-tux) should follow immediately after "Addition memory game against Tux" (memory-math-add)? usually everywhere there is subtraction first, followed by multiplication and division is there a specially mixed order arithmetic action exercises? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419421] QML timers go too fast with multi-threaded render loop when using mixed 240hz + 60hz refresh rate screens on X11
https://bugs.kde.org/show_bug.cgi?id=419421 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432970] Tab bar now shows the end of the hostname
https://bugs.kde.org/show_bug.cgi?id=432970 --- Comment #6 from ric...@nakts.net --- Colours wouldn't work, as I open SSH sessions to many different hosts, it's not a smaller set. Splitting wouldn't work as I prefer to work with fullscreen windows 99% of the time. Showing the beginning on the tab title was perfect for me - but I do appreciate the suggestions for possible changes in the workflow/habits :) -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 433048] KDE initial startup takes 30-50 seconds when autostarting apps (with and without KSplash)
https://bugs.kde.org/show_bug.cgi?id=433048 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO --- Comment #2 from David Edmundson --- >Systemd Bootchart was compiled from David Edmundson's repo. Appreciated, it helps a lot. ksplashqml is the splash. It shows it closes after 7.2s. That's when we think we're up. It also means plasma has reported that it has loaded everything. Can you expand a bit on what you're seeing on the screen during this 50s. A wallpaper with no panels visible at all? Then later they magically arrive? Does it also happen if you run plasmashell --replace? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433048] KDE initial startup takes 30-50 seconds when autostarting apps (with and without KSplash)
https://bugs.kde.org/show_bug.cgi?id=433048 David Edmundson changed: What|Removed |Added Assignee|plasma-b...@kde.org |k...@davidedmundson.co.uk Component|general |general Product|ksplash |plasmashell Target Milestone|--- |1.0 CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 433050] Latte Dock crashes randomly in Kwin Wayland session
https://bugs.kde.org/show_bug.cgi?id=433050 Kyle Devir changed: What|Removed |Added Summary|Crashes randomly in Kwin|Latte Dock crashes randomly |Wayland session |in Kwin Wayland session -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 433050] Latte Dock crashes randomly in Kwin Wayland session
https://bugs.kde.org/show_bug.cgi?id=433050 Kyle Devir changed: What|Removed |Added CC||kyle.de...@mykolab.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433062] New: wrong go_back Icon
https://bugs.kde.org/show_bug.cgi?id=433062 Bug ID: 433062 Summary: wrong go_back Icon Product: systemsettings Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: michael.hm...@gmail.com Target Milestone: --- Created attachment 135757 --> https://bugs.kde.org/attachment.cgi?id=135757&action=edit wrong arrow in system settings all tabs show on arrow on the upper left corner, but it's pointing forward (to the right) System: Host: hm-mint Kernel: 5.10.13-hmich-tl-frt-2.39 x86_64 bits: 64 Desktop: KDE Plasma 5.21.0 Distro: Linux Mint 20.1 Ulyssa CPU: Topology: Quad Core model: AMD Phenom 9550 bits: 64 type: MCP L2 cache: 2048 KiB Speed: 1100 MHz min/max: 1100/2200 MHz Core speeds (MHz): 1: 2200 2: 1100 3: 1100 4: 1100 Graphics: Device-1: NVIDIA GK208 [GeForce GT 710] driver: nvidia v: 390.141 Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1360x768~60Hz OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 390.141 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433063] New: Network Speed widget is not working
https://bugs.kde.org/show_bug.cgi?id=433063 Bug ID: 433063 Summary: Network Speed widget is not working Product: plasmashell Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: tniag...@gmail.com CC: ahiems...@heimr.nl, a...@1stleg.com, bhol...@interactive.com.au, bugs.kde@trimoon.cloudns.eu, bugsefor...@gmx.com, darkt...@gmail.com, francogpellegr...@gmail.com, fuc...@ukr.net, jan-b...@gmx.co.uk, jonzn4s...@hotmail.com, k...@david-redondo.de, k...@davidedmundson.co.uk, mmboss...@gmail.com, n...@kde.org, nicolam...@aol.com, notm...@gmail.com, nroycea+...@gmail.com, plasma-b...@kde.org, s_chriscoll...@hotmail.com, tniag...@gmail.com, vega...@yandex.ru Depends on: 425992 Target Milestone: 1.0 +++ This bug was initially created as a clone of Bug #425992 +++ SUMMARY I just updated to 5.21 and added a "Network speed" widget. I was set to Line Chart, and working ok. Some minutes later, nothing - flat lines and no traffic visible. STEPS TO REPRODUCE 1. Add "Network speed" widget to desktop. Set to "Line Chart". OBSERVED RESULT Widget will only work if the system tray "Networks" popup is visible. If the popup is pinned, then the widget continues to work. Hide the popup, and the widget lines stay at zero. EXPECTED RESULT Widget should always display network data. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.21 User Edition KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Is the widget missing a step to enable/subscribe to network data? Something that the popup does do, as it also shows network speed. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=425992 [Bug 425992] Network Speed widget is not working on neon unstable -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 steveb changed: What|Removed |Added Blocks||433063 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=433063 [Bug 433063] Network Speed widget is not working -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433064] New: systemmonitor line chart "amount of history to keep" has no effect
https://bugs.kde.org/show_bug.cgi?id=433064 Bug ID: 433064 Summary: systemmonitor line chart "amount of history to keep" has no effect Product: plasma-systemmonitor Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: till2.schae...@uni-dortmund.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- When using the line chart, the setting "amount of history to keep" does not seem to have any effect. I expect this setting to influence the amount of data that is displayed in the plasmoid. Thus the line chart should squeeze more data in the visible area. But this is not the case, the data is rushing through the area (in about 25 seconds) regardless of the history amount. Operating System: Gentoo Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-gentoo OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433065] New: set time below clock show am/pm time but my time setting is 24h
https://bugs.kde.org/show_bug.cgi?id=433065 Bug ID: 433065 Summary: set time below clock show am/pm time but my time setting is 24h Product: systemsettings Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_clock Assignee: p...@taniwha.com Reporter: michael.hm...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 135758 --> https://bugs.kde.org/attachment.cgi?id=135758&action=edit clock setting am/pm in regional settings -> date & time tab the clock setting is showing am/pm time and not 24h as in my general date;time settings System: Host: hm-mint Kernel: 5.10.13-hmich-tl-frt-2.39 x86_64 bits: 64 Desktop: KDE Plasma 5.21.0 Distro: Linux Mint 20.1 Ulyssa CPU: Topology: Quad Core model: AMD Phenom 9550 bits: 64 type: MCP L2 cache: 2048 KiB Speed: 1100 MHz min/max: 1100/2200 MHz Core speeds (MHz): 1: 2200 2: 1100 3: 1100 4: 1100 Graphics: Device-1: NVIDIA GK208 [GeForce GT 710] driver: nvidia v: 390.141 Display: x11 server: X.Org 1.20.9 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1360x768~60Hz OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 390.141 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433063] Network Speed widget is not working
https://bugs.kde.org/show_bug.cgi?id=433063 --- Comment #1 from steveb --- The "Network Rates" display in "System Monitor" is also affected the same way. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432638] unable to run okular installed via snapd
https://bugs.kde.org/show_bug.cgi?id=432638 Lamba Chandi changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #2 from Lamba Chandi --- Hello Jonathan Riddell, Thanks for your comment. I did not manage to run it yet. So should I just ditch snapcraft and try something else? Also, what is the correct way of installation if not via snapcraft.io page that i shared? Btw what is neon here? Warm regards, -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433066] system monitor: Chart Details: Text box changes cannot be applied until focus was moved to another object
https://bugs.kde.org/show_bug.cgi?id=433066 Till Schäfer changed: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433066] New: system monitor: Chart Details: Text box changes cannot be applied until focus was moved to another object
https://bugs.kde.org/show_bug.cgi?id=433066 Bug ID: 433066 Summary: system monitor: Chart Details: Text box changes cannot be applied until focus was moved to another object Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: till2.schae...@uni-dortmund.de CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- I am unable to press the apply button in the chart details settings, whenever I change a value in some value fields by hand. E.g., when is change the occupacy by typing in a value in line chart details, I have to click the some other field first (e.g., ammout of history kept) in order to press the apply button. Operating System: Gentoo Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-gentoo OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431729] Visual issues after hibernation with multi monitor setup: Panel spans over to 2nd monitor and wallpapers change
https://bugs.kde.org/show_bug.cgi?id=431729 postix changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #7 from postix --- Still an issue, also on boot; I will check it again and try to get the relevant debug info once I reinstalled the system after Plasma 5.21.1 comes out. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 425637] kscreenlocker doesn't respect the energy saving setting
https://bugs.kde.org/show_bug.cgi?id=425637 Don Curtis changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Don Curtis --- As of 2021-02-03, having setup the Audio to use both the Analogue and HDMI outputs in parallel and, changed the Monitor settings to no longer automatically choose which Input - HDMI-1, HDMI-2, Display Port - shall be used - it's now set to use the HDMI-1 input only - * The issue has disappeared . . . -- Whether or not, a recent or, not so recent, patch played a role in the behaviour change, is something I can not prove . . . -- I'm closing this Bug Report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433067] New: Application Menu suddenly restart
https://bugs.kde.org/show_bug.cgi?id=433067 Bug ID: 433067 Summary: Application Menu suddenly restart Product: plasmashell Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: deocleciofre...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-14-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: - What I was doing when the application crashed: I was hovering mouse through options, going to sub menus e back. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 28return SYSCALL_CANCEL (nanosleep, requested_time, remaining); [Current thread is 1 (Thread 0x7fc6ac9dc840 (LWP 1645))] Thread 24 (Thread 0x7fc63e30b700 (LWP 2109)): #0 0x7fc6b19df819 in __GI___poll (fds=0x7fc63400ad10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc6afad4136 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc6afad425c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc6b1ef1743 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc6b1e9f15b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc6b1ceee76 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc6b38a4476 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fc6b1cf8a67 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fc6b0c14fa3 in start_thread (arg=) at pthread_create.c:486 #9 0x7fc6b19ea4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fc674ff9700 (LWP 2089)): #0 0x7fc6b0c1b00c in futex_wait_cancelable (private=0, expected=0, futex_word=0x555cfe66afd8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc6b0c1b00c in __pthread_cond_wait_common (abstime=0x0, mutex=0x555cfe66af88, cond=0x555cfe66afb0) at pthread_cond_wait.c:502 #2 0x7fc6b0c1b00c in __pthread_cond_wait (cond=0x555cfe66afb0, mutex=0x555cfe66af88) at pthread_cond_wait.c:655 #3 0x7fc69b798b23 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc69b798877 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc6b0c14fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7fc6b19ea4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fc6757fa700 (LWP 1940)): #0 0x7fc6b0c1b00c in futex_wait_cancelable (private=0, expected=0, futex_word=0x555cfd9cb1d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc6b0c1b00c in __pthread_cond_wait_common (abstime=0x0, mutex=0x555cfd9cb180, cond=0x555cfd9cb1a8) at pthread_cond_wait.c:502 #2 0x7fc6b0c1b00c in __pthread_cond_wait (cond=0x555cfd9cb1a8, mutex=0x555cfd9cb180) at pthread_cond_wait.c:655 #3 0x7fc69b798b23 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc69b798877 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc6b0c14fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7fc6b19ea4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7fc675ffb700 (LWP 1939)): #0 0x7fc6b0c1b00c in futex_wait_cancelable (private=0, expected=0, futex_word=0x555cfd9cb1d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc6b0c1b00c in __pthread_cond_wait_common (abstime=0x0, mutex=0x555cfd9cb180, cond=0x555cfd9cb1a8) at pthread_cond_wait.c:502 #2 0x7fc6b0c1b00c in __pthread_cond_wait (cond=0x555cfd9cb1a8, mutex=0x555cfd9cb180) at pthread_cond_wait.c:655 #3 0x7fc69b798b23 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc69b798877 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fc6b0c14fa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7fc6b19ea4cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fc6767fc700 (LWP 1938)): #0 0x7fc6b0c1b00c in futex_wait_cancelable (private=0, expected=0, futex_word=0x555cfd9cb1d0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fc6b0c1b00c in __pthread_cond_wait_common (abstime=0x0, mutex=0x555cfd9cb180, cond=0x555cfd9cb1a8) at pthread_cond_wait.c:502 #2 0x7fc6b0c1b00c in __pthread_cond_wait (cond=0x555cfd9cb1a8, mutex=0x555cfd9cb180) at pthread_cond_wait.c:655 #3 0x7fc69b798b23 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fc69b798877 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0
[kwin] [Bug 433011] Firefox Wayland context menus don't properly display updates for cursor movement
https://bugs.kde.org/show_bug.cgi?id=433011 Schlaefer changed: What|Removed |Added CC||openmail+...@siezi.com --- Comment #3 from Schlaefer --- Created attachment 135759 --> https://bugs.kde.org/attachment.cgi?id=135759&action=edit Shows menu issue difference between FF85 and FF86 I experience the same issue. It's not flickering as in FF85 or earlier anymore. In FF86 the menu is drawn stable, but it doesn't properly update when the pointer is moved over it (e.g. invert menu item under pointer). See attached video for comparison. Operating System: EndeavourOS KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-zen1-1-zen OS Type: 64-bit Graphics Platform: Wayland - Multiple screens with different scaling factors -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433062] wrong go_back Icon
https://bugs.kde.org/show_bug.cgi?id=433062 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Looks correct in breeze -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433059] Can no longer change the "Active\Inactive Titlebar" color of Breeze Dark (Plasma 5.21)
https://bugs.kde.org/show_bug.cgi?id=433059 Schlaefer changed: What|Removed |Added CC||openmail+...@siezi.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432867] crash in TaskManager::servicesFromPid() after start wine application without SOCK_RAW permission
https://bugs.kde.org/show_bug.cgi?id=432867 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #2 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 431334 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431334] Plasma crashes in TaskManager::servicesFromPid() while installing a Windows app using WINE
https://bugs.kde.org/show_bug.cgi?id=431334 Kai Uwe Broulik changed: What|Removed |Added CC||cjaushe...@pm.me --- Comment #2 from Kai Uwe Broulik --- *** Bug 432867 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 432870] gdbserver_tests:nlcontrolc hangs with newest glibc2.33 x86-64
https://bugs.kde.org/show_bug.cgi?id=432870 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #2 from Mark Wielaard --- Thanks for tracking this down to that specific glibc commit. It changes which select system call is called depending on the architecture and kernel version. This might be related to https://bugs.kde.org/show_bug.cgi?id=338633 where we disable the nlcontrolc.vgtest on arm64 because it hangs (speculated to be because arm64 doesn't provide a traditional select system call). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 433069] New: Folder name doesn't appear on first opening of the Archive Agent set-up
https://bugs.kde.org/show_bug.cgi?id=433069 Bug ID: 433069 Summary: Folder name doesn't appear on first opening of the Archive Agent set-up Product: Akonadi Version: 5.14.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Archive Mail Agent Assignee: kdepim-b...@kde.org Reporter: bugrprt21...@online.de Target Milestone: --- SUMMARY When setting up the KMail folders to be archived, when the Archive Mail Agent is first opened, the folders being archived are not displayed. * Closing the Agent and then starting it again displays the folders currently being archived. STEPS TO REPRODUCE 1. From within KMail, open the Archive Agent set-up. 2. Close the Archive Agent set-up window. 3. Re-open the Archive Agent set-up. OBSERVED RESULT On first opening the Archive Agent set-up, the names of the folders currently being archived are not displayed. Close and then re-open the Archive Agent set-up – the names of the folders currently being archived are displayed. EXPECTED RESULT When the Archive Agent set-up is opened, the names of the folders currently being archived should be displayed – on the first time – not on subsequent times. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-lp152.63-default OS Type: 64-bit Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics Memory: 13,6 GiB ADDITIONAL INFORMATION It's been this way for quite a while now – only recently realised that, closing and then re-opening the Archive Agent set-up causes the Folders currently being archived to be displayed … -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431334] Plasma crashes in TaskManager::servicesFromPid() while installing a Windows app using WINE
https://bugs.kde.org/show_bug.cgi?id=431334 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/75 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433070] New: Empty Database - Network Volume
https://bugs.kde.org/show_bug.cgi?id=433070 Bug ID: 433070 Summary: Empty Database - Network Volume Product: digikam Version: 7.2.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: major Priority: NOR Component: Database Assignee: digikam-bugs-n...@kde.org Reporter: elmarku...@web.de Target Milestone: --- SUMMARY I saved my Pictures on a OMV Server in my private Home-Network. The Database is on a local Volume on my IMac (MacBook) STEPS TO REPRODUCE 1. Connect the Mac to the Network-Volume 2. Import Pictures 3. Restart the Mac (network Volume is not connected) 4. Start Digikam 5. No Preview, Albums or somethng like that are Dinsplayed in Digikam - No Error 6. Peopöes are still there but no Pictures OBSERVED RESULT Error Message: "Volume is Missing" or something like that EXPECTED RESULT SOFTWARE/OS VERSIONS macOS: 10.14.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433070] Empty Database - Network Volume
https://bugs.kde.org/show_bug.cgi?id=433070 caulier.gil...@gmail.com changed: What|Removed |Added Component|Database|Database-Media CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 431334] Plasma crashes in TaskManager::servicesFromPid() while installing a Windows app using WINE
https://bugs.kde.org/show_bug.cgi?id=431334 Kai Uwe Broulik changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kcoreaddons/commit/b ||f1825812fac68184781ad4f5321 ||b0b631367784 --- Comment #4 from Kai Uwe Broulik --- Git commit bf1825812fac68184781ad4f5321b0b631367784 by Kai Uwe Broulik. Committed on 17/02/2021 at 11:20. Pushed by broulik into branch 'master'. [KProcessList] Check size of data before accessing it M +3-0src/lib/util/kprocesslist_unix.cpp https://invent.kde.org/frameworks/kcoreaddons/commit/bf1825812fac68184781ad4f5321b0b631367784 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433070] Empty Database - Network Volume
https://bugs.kde.org/show_bug.cgi?id=433070 --- Comment #1 from caulier.gil...@gmail.com --- What's a OMV Server exactly ? It use a Mysql or Mariadb database internally ? Which version of the database engine is used ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433070] Empty Database - Network Volume
https://bugs.kde.org/show_bug.cgi?id=433070 Maik Qualmann changed: What|Removed |Added Component|Database-Media |Database Severity|major |normal CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- A network drive must also be added as a network drive type in the digikam collection settings so that digiKam knows that it is not always available and cleans up the database. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433060] inconsistency between metadata displayed and metadata taken in account to rename
https://bugs.kde.org/show_bug.cgi?id=433060 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- There are many dates in photos. The question is which one did you change with the external program? Has the date under the thumbnail been updated to the new one? They may need to reread the metadata from the image. You should use digiKam's TimeAdjust Tool. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433060] inconsistency between metadata displayed and metadata taken in account to rename
https://bugs.kde.org/show_bug.cgi?id=433060 --- Comment #2 from Maik Qualmann --- In order to be able to narrow down the problem further, we need 2 images, namely before and after processing in the external tool. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406793] Cannot close cash and saving accounts even with balance=0
https://bugs.kde.org/show_bug.cgi?id=406793 --- Comment #11 from antoine --- (In reply to Jack from comment #10) > Antoine - in order to close the investment account, you must also first > close all the stock accounts in it. Have you done this? Yes and it solved my issue, thank you Jack. It was not easy for me to guess that I had to close all the stock account in it because some of the stock account are in multiple investment account. https://forum.kde.org/viewtopic.php?f=69&t=164623 This bug was initially reported by lp.allard.1, I do not know if he solved his issue -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433070] Empty Database - Network Volume
https://bugs.kde.org/show_bug.cgi?id=433070 Maik Qualmann changed: What|Removed |Added Component|Database|Database-Media -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432904] App crashes if Layers is selected from 3 bar menu Top right of screen
https://bugs.kde.org/show_bug.cgi?id=432904 Anna Medonosova changed: What|Removed |Added CC||anna.medonosova@protonmail. ||com --- Comment #2 from Anna Medonosova --- Created attachment 135761 --> https://bugs.kde.org/attachment.cgi?id=135761&action=edit backtrace of the crash I can reproduce the crash on current stable branch and master. I'm attaching a backtrace. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432852] Digikam crashes when attempting to modify geolocation data
https://bugs.kde.org/show_bug.cgi?id=432852 --- Comment #11 from caulier.gil...@gmail.com --- Arthur, The new pre-release is published online, and i'm sure that the PKG build is correct now. If you have a recent PKG version of digiKam installed you can use the "Online Version Checker" feature introduced with 7.2.0. > Go to Setup/Miscs/Behaviour/Updates > Switch to check new version as "Weekly Pre-release" > Press "Check Now..." the tool must check last online version, download PKG, and propose to install it. Best Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433071] New: No background Wallpapers in Desktop Grid on Wayland
https://bugs.kde.org/show_bug.cgi?id=433071 Bug ID: 433071 Summary: No background Wallpapers in Desktop Grid on Wayland Product: kwin Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: geisse...@gmail.com Target Milestone: --- Created attachment 135762 --> https://bugs.kde.org/attachment.cgi?id=135762&action=edit no wallpapers shown SUMMARY Wallpapers are black/invisible in the Show Desktop Grid effect (on Wayland only, Screenshot attached) STEPS TO REPRODUCE 1. Login to a Wayland session 2. Trigger the "Show Desktop Grid" effect (via button or keyboard shortcut) -> the open windows of the various virtual desktops are visible, but not the backgrounds/wallpapers, they're just black. OBSERVED RESULT black/no Wallappers in Show Desktop Grid effect on Wayland EXPECTED RESULT Wallpapers should show up correctly for all virtual desktops, as they do in X11 SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Graphics Platform: Wayland ADDITIONAL INFORMATION The Present Windows effect correctly shows the wallpaper -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433070] Empty Database - Network Volume
https://bugs.kde.org/show_bug.cgi?id=433070 --- Comment #3 from Ette --- @Gilles: OMV is a Server-Software running on a Raspi 4. https://www.openmediavault.org/ It provides me a cheap TimeMachine Volume, a DLNA Player for ripped CDs an now a Network Volume for my Pictures. @Maik: I will test that. thx for your Tips Ette -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433070] Empty Database - Network Volume
https://bugs.kde.org/show_bug.cgi?id=433070 --- Comment #4 from caulier.gil...@gmail.com --- Ah great. The TimeMachine feature is very interesting. I'm a big fan of PI computers. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432208] Win10Pro 64bit: Okular crash without saving the modified PDF file.
https://bugs.kde.org/show_bug.cgi?id=432208 Enrico changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Enrico --- After the 20.12.2 update the bug was solved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433072] New: Allow dragging widndows from empty space in Panel
https://bugs.kde.org/show_bug.cgi?id=433072 Bug ID: 433072 Summary: Allow dragging widndows from empty space in Panel Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mufeed.666...@gmail.com Target Milestone: 1.0 SUMMARY When using a top panel, it can be very helpful to be able to drag the empty space in the panel to drag the window title bar. It's especially useful when using BorderlessMaximizedWindows. STEPS TO REPRODUCE 1. Setup a top Plasma panel. 2. Use BorderlessMaximizedWindows in KWin. 3. Maximize a window. 4. Drag from the empty space in the top panel. OBSERVED RESULT No action. EXPECTED RESULT Unmaximize and drag window with cursor on the now visible titlebar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.2 ADDITIONAL INFORMATION There was some discussion about implementing this in the Active Window Control plasmoid here: https://github.com/kotelnik/plasma-applet-active-window-control/issues/30 The feature is also present in Latte. But Latte also faces this bug on Wayland: https://bugs.kde.org/show_bug.cgi?id=419442 . -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432454] System Settings crashed after exiting lockscreen appearance settings
https://bugs.kde.org/show_bug.cgi?id=432454 --- Comment #2 from dragan_jovic1...@outlook.com --- Created attachment 135763 --> https://bugs.kde.org/attachment.cgi?id=135763&action=edit New crash information added by DrKonqi systemsettings5 (5.20.5) using Qt 5.15.2 - What I was doing when the application crashed: Changed the wallpaper for the lockscreen. Clicked apply, and closed the settings window. Crash popped up but the setting is applied since the new background is correctly set. -- Backtrace (Reduced): #4 0x7fd95d8f9a0e in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib64/libQt5Qml.so.5 #5 0x7fd95d8dd491 in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5 #6 0x7fd95d8dee63 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) () from /lib64/libQt5Qml.so.5 #7 0x7fd95d913310 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5 #9 0x7fd95d8b87bd in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432454] System Settings crashed after exiting lockscreen appearance settings
https://bugs.kde.org/show_bug.cgi?id=432454 dragan_jovic1...@outlook.com changed: What|Removed |Added CC||dragan_jovic1...@outlook.co ||m -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432852] Digikam crashes when attempting to modify geolocation data
https://bugs.kde.org/show_bug.cgi?id=432852 --- Comment #12 from art...@vandeloo.org --- Sadly, the problem still persist, even on the latest version. Do you want me to post the log file again? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433073] New: Pinned applications immediately terminate upon launch if launched from pinned icon.
https://bugs.kde.org/show_bug.cgi?id=433073 Bug ID: 433073 Summary: Pinned applications immediately terminate upon launch if launched from pinned icon. Product: plasmashell Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: soos.ger...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Launching an application from it's respective pinned icon on the task manager results in the application briefly launching, then terminating before it's window can show up. Launching the application afterwards from the Application Launcher results in as many instances of it being launched as the number of times a launch was attempted from the task manager +1. STEPS TO REPRODUCE 1. Pin app to task manager 2. Launch via pinned icon 3. Launch same app from application launcher OBSERVED RESULT Said application launches and terminates before window appears. If the user were to attempt a launch of an application x number of times, x+1 instances will launch upon doing so from application manager. EXPECTED RESULT Application should launch upon having it's icon clicked in task manager without terminating itself. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 393423] "Use the terminal color scheme for the scrollbar" doesn't work with non-Breeze widget styles; consider making it optional
https://bugs.kde.org/show_bug.cgi?id=393423 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433031] libkf5purpose-bin should not recommend nodejs anymore
https://bugs.kde.org/show_bug.cgi?id=433031 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/neon ||/kde/purpose/commit/fb66be6 ||df516cc1b00b245b09fa5aa9966 ||8fe22c --- Comment #1 from Harald Sitter --- Git commit fb66be6df516cc1b00b245b09fa5aa99668fe22c by Harald Sitter. Committed on 17/02/2021 at 12:11. Pushed by sitter into branch 'Neon/release-lts'. begone, foul nodejs twas dropped in the code along with the twitter support a while ago M +1-1debian/control https://invent.kde.org/neon/kde/purpose/commit/fb66be6df516cc1b00b245b09fa5aa99668fe22c -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433063] Network Speed widget is not working
https://bugs.kde.org/show_bug.cgi?id=433063 David Redondo changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from David Redondo --- This is because the applet sets the statistics refresh rate to 0 upon hiding -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 217695] realloc failure doesn't set errno to ENOMEM
https://bugs.kde.org/show_bug.cgi?id=217695 Mark Wielaard changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Mark Wielaard --- commit 1c9a0bf58a47e855e6e5bf78a30bcee0af835804 Author: Mark Wielaard Date: Fri Feb 12 23:29:34 2021 +0100 PR217695 malloc/calloc/realloc/memalign failure doesn't set errno to ENOMEM When one of the allocation functions in vg_replace_malloc failed they return NULL, but didn't set errno. This is slightly tricky since errno is implementation defined and might be a macro. In the case of glibc ernno is defined as: extern int *__errno_location (void) __THROW __attribute__ ((__const__)); #define errno (*__errno_location ()) We can use the same trick as we use for __libc_freeres in coregrind/vg_preloaded.c. Define the function as "weak". This means it will only be defined if another library (glibc in this case) actually provides a definition. Otherwise it will be NULL. So we will only call it if it is defined and one of the allocation functions failed, returned NULL. Include a new linux only memcheck testcase, enomem.vgtest. https://bugs.kde.org/show_bug.cgi?id=217695 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432852] Digikam crashes when attempting to modify geolocation data
https://bugs.kde.org/show_bug.cgi?id=432852 --- Comment #13 from caulier.gil...@gmail.com --- Hum. Do you have something installed in /opt/digikam on your computer ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432852] Digikam crashes when attempting to modify geolocation data
https://bugs.kde.org/show_bug.cgi?id=432852 --- Comment #14 from Maik Qualmann --- Gilles, what's the old path to digiKam so that Arthur can see if he still has an older version of digiKam on his Mac. The marble plugins should definitely be present twice in the search path. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433074] New: Wayland does not support "primary" monitor setup
https://bugs.kde.org/show_bug.cgi?id=433074 Bug ID: 433074 Summary: Wayland does not support "primary" monitor setup Product: kwin Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: francogpellegr...@gmail.com Target Milestone: --- SUMMARY Cannot set primary monitor using wayland. There's no such option, like in X11 STEPS TO REPRODUCE 1. switch to wailand 2. try to setup the main monitor OBSERVED RESULT No configuration to change EXPECTED RESULT "primary" checkbox, like with X11 SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-65-generic OS Type: 64-bit Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 22.9 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433074] Wayland does not support "primary" monitor setup
https://bugs.kde.org/show_bug.cgi?id=433074 Nicolas Fella changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||nicolas.fe...@gmx.de Resolution|--- |WAITINGFORINFO --- Comment #1 from Nicolas Fella --- Wayland has no concept of a "primary screen". What is it that you want to achieve? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431374] Being able to disable the white circle around the "X" button at the top right corner of the Breeze-Dark-Gtk Window borders
https://bugs.kde.org/show_bug.cgi?id=431374 --- Comment #14 from Toadfield --- (In reply to Nate Graham from comment #13) > How did you download it? From where? I go to System Settings>Application Style>Configure Gnome/GTK Application Style>Get new Gnome/GTK Application Styles,then download the theme Breeze-GTK (https://store.kde.org/p/1197982) and then select the GTK theme "Breeze-Dark-GTK". -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433017] plasma-firewall depends on python2 instead of python3
https://bugs.kde.org/show_bug.cgi?id=433017 --- Comment #3 from Harald Sitter --- I rather thought Jon had fixed that already -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433017] plasma-firewall depends on python2 instead of python3
https://bugs.kde.org/show_bug.cgi?id=433017 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Harald Sitter --- When filing a bug report please make sure it's actually affecting the latest version. The problem had been fixed 1.5 hours before you filed the bug report even ;) Rolled out as per this snapshot https://mail.kde.org/pipermail/neon-notifications/2021-February/008278.html plasma-firewall_5.21.0-0xneon+20.04+focal+build4_amd64.deb: new Debian package, version 2.0. size 409240 bytes: control archive=2284 bytes. 684 bytes,12 lines control 4965 bytes,57 lines md5sums Package: plasma-firewall Version: 5.21.0-0xneon+20.04+focal+build4 Architecture: amd64 Maintainer: Neon CI Installed-Size: 1182 Depends: iproute2, netstat-nat, python3, ufw, libc6 (>= 2.14), libkf5authcore5, libkf5configcore5, libkf5coreaddons5, libkf5i18n5, libkf5quickaddons5, libqt5core5a (>= 5.15.2+dfsg), libqt5dbus5 (>= 5.15.2+dfsg), libqt5network5 (>= 5.15.2+dfsg), libqt5qml5 (>= 5.15.2+dfsg), libstdc++6 (>= 4.1.1) Section: KDE Priority: optional Description: NX Firewall - Protect your workstation! NX Firewall allows you to protect your workstation from network atacks and also to avoid your data to be exposed on the network by an imprudent application. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432957] Some tags appear beneath "People" parent tag in People view/panel
https://bugs.kde.org/show_bug.cgi?id=432957 --- Comment #20 from José Oliver-Didier --- Fixed: Able to move tags, changes persist after closing and re-opening digiKam. Tested on 7.2.0-rc (46fd680f) 2/16/2021 build with MySQL 8.0.23 on Windows 10. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432852] Digikam crashes when attempting to modify geolocation data
https://bugs.kde.org/show_bug.cgi?id=432852 --- Comment #15 from caulier.gil...@gmail.com --- Hi Maik, The old path is /opt/digikam aka with digiKam version <= 7.2.0-beta1 (perhaps beta2 pre-version, i'm not sure) The new path is /Applications/digiKam.org. /Applications is the stadard place to host macOS applications. Gilles -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 433075] New: Unattended updates not available on OpenSUSE Tumbleweed
https://bugs.kde.org/show_bug.cgi?id=433075 Bug ID: 433075 Summary: Unattended updates not available on OpenSUSE Tumbleweed Product: Discover Version: 5.21.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: lei...@leinir.dk Reporter: tobi.goerg...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Hey guys, I just updated Plasma to 5.21 on OpenSUSE Tumbleweed, but the unattended update option is not shown. Can this be confirmed? OpenSUSE uses packagekit. STEPS TO REPRODUCE 1. Update to Plasma 5.21 2. Go to system settings 3. look for Updates under system administration OBSERVED RESULT there's no entry for unattended updates EXPECTED RESULT There should be an entry for unattended updates SOFTWARE/OS VERSIONS Windows: macOS: Operating System: openSUSE Tumbleweed 20210212 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.14-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION Unfortunately, I don't know which component is responsible for this misbehavior (except it's wanted for any reason :D) so I selected "Updater". Should that be wrong, I'd be happy to change it to the correct one. :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 433017] plasma-firewall depends on python2 instead of python3
https://bugs.kde.org/show_bug.cgi?id=433017 --- Comment #5 from Manuel Geißer --- Indeed, it had already been fixed. Sorry I failed to notice the update because I uninstalled it as I saw it depends on python-is-python2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433060] inconsistency between metadata displayed and metadata taken in account to rename
https://bugs.kde.org/show_bug.cgi?id=433060 --- Comment #3 from mahikeulbody --- (In reply to Maik Qualmann from comment #1) > There are many dates in photos. The question is which one did you change > with the external program ? I provided this information : Image Information/DateTimeoriginal (the one displayed which this name in the Digiakm Metadada Exif panel > Has the date under the thumbnail been updated to the new one ? I don't know since only seconds part changed in my try. But I think it is irrelevant : I change Image Information/DateTimeoriginal with an external tool and this change appears in the Image Information/DateTimeoriginal into the Digiakm Metadada Exif panel after to scan for new items. > They may need to reread the metadata from the image. I said that in the ADDITIONAL INFORMATION part. I know the solution to solve the inconsistency but it would be better if there was not inconsistency at all : at the same time, Digikam provide a DateTimeoriginal A into the Metadata Panel and a DateTimeoriginal B into the renaming panel (F2). It would be fine either A or B, but for both panels. > You should use digiKam's TimeAdjust Tool. Of course but in this case I had a good reason to do it outside Digikam. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406793] Cannot close cash and saving accounts even with balance=0
https://bugs.kde.org/show_bug.cgi?id=406793 --- Comment #12 from Thomas Baumgart --- > because some of the stock account are in multiple investment account This cannot be! An account (stock account here) cannot have multiple parent accounts (investment account here) but only one. What you mean is the security in which the account is denominated. That can be used by multiple accounts in parallel. In case an account object is listed as sub-account to two different accounts the consistency check will fail and the user will be informed that something is wrong. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 133927] Tileable windows with split bar between them
https://bugs.kde.org/show_bug.cgi?id=133927 rolodoph...@gmail.com changed: What|Removed |Added CC||rolodoph...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433074] Wayland does not support "primary" monitor setup
https://bugs.kde.org/show_bug.cgi?id=433074 --- Comment #2 from Franco Pellegrini --- (In reply to Nicolas Fella from comment #1) > Wayland has no concept of a "primary screen". > > What is it that you want to achieve? All my notifications appear on the wrong monitor, and all my panels too. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 186616] Entering negative amounts in Split window
https://bugs.kde.org/show_bug.cgi?id=186616 --- Comment #5 from Thomas Baumgart --- The link Ralf provided produces "The search named version_5_relevant does not exist." for me. Maybe it is private to the user logged in. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432904] App crashes if Layers is selected from 3 bar menu Top right of screen
https://bugs.kde.org/show_bug.cgi?id=432904 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/cff721114 ||01bb5e50c65d93655a660b9ca9d ||0e31 Resolution|--- |FIXED --- Comment #3 from Dmitry Kazakov --- Git commit cff72111401bb5e50c65d93655a660b9ca9d0e31 by Dmitry Kazakov, on behalf of Sharaf Zaman. Committed on 17/02/2021 at 13:02. Pushed by dkazakov into branch 'master'. Android: Add key functions to psd_layer_effects_shadow_base .. hierarchy. M +35 -0libs/psd/psd.cpp M +11 -7libs/psd/psd.h https://invent.kde.org/graphics/krita/commit/cff72111401bb5e50c65d93655a660b9ca9d0e31 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433060] inconsistency between metadata displayed and metadata taken in account to rename
https://bugs.kde.org/show_bug.cgi?id=433060 --- Comment #4 from Maik Qualmann --- If the date is displayed in the metadata panel, it does not mean that it has also been changed in the digiKam database. The metadata panel shows the "live" status of the metadata of the image. You may also have to activate the digiKam metadata settings to re-read the metadata after changes. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432904] App crashes if Layers is selected from 3 bar menu Top right of screen
https://bugs.kde.org/show_bug.cgi?id=432904 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/cff721114 |hics/krita/commit/c97c2b2fd |01bb5e50c65d93655a660b9ca9d |50ae021dcd60d90ed5ac437cb72 |0e31|480d --- Comment #4 from Dmitry Kazakov --- Git commit c97c2b2fd50ae021dcd60d90ed5ac437cb72480d by Dmitry Kazakov, on behalf of Sharaf Zaman. Committed on 17/02/2021 at 13:03. Pushed by dkazakov into branch 'krita/4.3'. Android: Add key functions to psd_layer_effects_shadow_base .. hierarchy. M +35 -0libs/psd/psd.cpp M +11 -7libs/psd/psd.h https://invent.kde.org/graphics/krita/commit/c97c2b2fd50ae021dcd60d90ed5ac437cb72480d -- You are receiving this mail because: You are watching all bug changes.
