[plasmashell] [Bug 449029] New: Chrome and Firefox notifications appear violating do-not-disturb
https://bugs.kde.org/show_bug.cgi?id=449029 Bug ID: 449029 Summary: Chrome and Firefox notifications appear violating do-not-disturb Product: plasmashell Version: master Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: derb...@interia.pl CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 145813 --> https://bugs.kde.org/attachment.cgi?id=145813&action=edit Notification from Firefox STEPS TO REPRODUCE 1. Make sure you have Plasma Integration add-on installed in Firefox (https://addons.mozilla.org/pl/firefox/addon/plasma-integration/) 2. Click Plasma notifications icon, enable 'Do not disturb' for 4 hours 3. Open any web page in Firefox, right-click any link, choose 'Save Link As…' , KDE file chooser dialog appears, select any location then choose save OBSERVED RESULT Two notifications appear: first about transfer progress, second about download finish. EXPECTED RESULT No notification appears. The add on is prepared by KDE team, the notifications it show should behave like proper KDE notifications. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Firefox: 96.0+build2-0ubuntu0.21.10.1 Plasma Integration add-on: 1.8.1 ADDITIONAL INFORMATION Probably this is not just a problem in the Firefox add-on, but a wrong way of handling notifications in KDE in general. I think so because also Chromium/Chrome shows notifications violating KDE do-not disturb. To reproduce, open calendar.google.com, there enable desktop notifications, set up an event with a notification. Wait for the notification - you will see it despite do-not-disturb enabled. The notification will never disappear, which is very frustrating. Reproduced in Chromium 97.0.4692.99. This is not a regression. As far as I remember, browser notifications violated KDE do-not-disturb ever since do-not-disturb feature appeared. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449029] Chrome and Firefox notifications appear violating do-not-disturb
https://bugs.kde.org/show_bug.cgi?id=449029 --- Comment #1 from Piotr Kubowicz --- Created attachment 145814 --> https://bugs.kde.org/attachment.cgi?id=145814&action=edit Notification from Chromium -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 449030] New: Spectacle saves screenshot copy when exporting despite autosave being disabled
https://bugs.kde.org/show_bug.cgi?id=449030 Bug ID: 449030 Summary: Spectacle saves screenshot copy when exporting despite autosave being disabled Product: Spectacle Version: 21.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: derb...@interia.pl CC: k...@david-redondo.de Target Milestone: --- Created attachment 145815 --> https://bugs.kde.org/attachment.cgi?id=145815&action=edit Spectacle at the moment of reproducing the bug STEPS TO REPRODUCE 1. Open Spectacle configuration, go to General, disable 'After tasking screenshot: Autosave file to default folder', confirm 2. Press PrtSc or other screenshot hot key 3. When Spectacle appears, choose Export > GNU Image Manipulation Program OBSERVED RESULT A Spectacle message says 'The screenshot was saved as ScreenshotXYZ.png', the file appears in ~/Pictures. EXPECTED RESULT No files are created. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449029] Chrome and Firefox notifications appear violating do-not-disturb
https://bugs.kde.org/show_bug.cgi?id=449029
--- Comment #3 from Piotr Kubowicz ---
Thinking this way, you can dismiss any bug in do-not-disturb: the user turned
on the computer and started some programs, it was their intention to receive
the notification, so we show the notification, gotcha!
No, if I set 'do not disturb', I don't want any notifications flying around my
desktop. Maybe I am sharing my screen during an important event. Then I don't
want anything covering my desktop, and I don't want to move my mouse to close
notifications.
I cannot see how 'download finished' notification could count as an urgent or
important event. If I set 'do not disturb', I'm doing some deep work and
probably don't need to be immediately reminded a download is finished. With
current Internet speed, most downloads finish in a few seconds. 'Download
finished' notification is redundant. The file will be usually available after I
take a deep breath. If I miss the notification, nothing wrong happens. The
notification is still available in KDE notification list.
The whole principle of deep work and 'do not disturb' is replacing push ('here
is your download, it's finished, look at me, I am a very important
notification!') with pull (I deliberately decide to open the list of emails,
instant messages, transfers).
You mistake dialogs ('Do you really want to replace this file?') with
notifications ('It is finished! See what is new!'). 'Choose download location'
requires user input to do its job, thus has to be shown even in do-not-disturb
mode. 'Download finished' is a notification and should not be shown. Download
progress is also a notification.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 449029] Chrome and Firefox notifications appear violating do-not-disturb
https://bugs.kde.org/show_bug.cgi?id=449029 --- Comment #4 from Piotr Kubowicz --- Similarly, I don't understand why KDE shows Chromium notifications during do-not-disturb just because Chromium claims its notifications are 'urgent'. How can anything be urgent in do-not-disturb mode? Maybe KDE should not trust third-party applications about urgency. If you have known use cases where a notification is in some way critical (which ones? why?), maybe you should just whitelist a subset of software you control (KDE-owned applications) and block all the rest. -- 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
Piotr Kubowicz changed:
What|Removed |Added
CC||derb...@interia.pl
--- Comment #28 from Piotr Kubowicz ---
I have this problem in Kubuntu 20.04 after upgrading from Kubuntu 19.10.
Removing the wallet does not help, so some packages are clearly conflicting
with each other. However, a 'fresh' wallet works fine if you just log out and
log in, without restarting.
1. Set up a WiFi connection using Network Manager, choose 'Store password for
this user only (encrypted)', you will have only 1 entry in KDE wallet:
Network Management
Name-Value Map 802-11-wireless-security
key: psk
2. rm -r ~/.local/share/kwalletd
3. restart computer
4. a dialog appears asking you to create KDE Wallet using classic blowfish or
GPG, choose classic
5. enter wifi password to the Network Manager dialog
% journalctl -b | grep kwallet
cze 20 08:23:26 bazyliszek sddm-helper[1638]: pam_kwallet5(sddm:auth): (null):
pam_sm_authenticate
cze 20 08:23:26 bazyliszek sddm-helper[1638]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
cze 20 08:23:26 bazyliszek sddm-helper[1638]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_open_session
cze 20 08:23:26 bazyliszek sddm-helper[1651]: pam_kwallet5: final socket path:
/run/user/1000/kwallet5.socket
cze 20 08:23:30 bazyliszek dbus-daemon[1661]: [session uid=1000 pid=1661]
Activating service name='org.kde.kwalletd5' requested by ':1.9' (uid=1000
pid=1721 comm="kded5 " label="unconfined")
cze 20 08:23:30 bazyliszek dbus-daemon[1661]: [session uid=1000 pid=1661]
Successfully activated service 'org.kde.kwalletd5'
cze 20 08:23:30 bazyliszek org.kde.kwalletd5[1768]: kf5.ki18n: "0 instead of 1
arguments to message {<...} supplied before conversion."
cze 20 08:23:30 bazyliszek org.kde.kwalletd5[1768]: Application ' "kded5" '
using kwallet without parent window!
cze 20 08:23:33 bazyliszek sddm[1652]: kwalletd5: Checking for pam module
cze 20 08:23:33 bazyliszek sddm[1652]: kwalletd5: Got pam-login param
cze 20 08:23:33 bazyliszek sddm[1652]: kwalletd5: Waiting for hash on 7-
cze 20 08:23:33 bazyliszek sddm[1652]: kwalletd5: waitingForEnvironment on: 3
cze 20 08:23:33 bazyliszek sddm[1652]: kwalletd5: client connected
cze 20 08:23:33 bazyliszek sddm[1652]: kwalletd5: client disconnected
cze 20 08:23:53 bazyliszek org.kde.kwalletd5[1768]: QWizard::field: No such
field 'key'
cze 20 08:23:53 bazyliszek org.kde.kwalletd5[1768]: Application ' "kded5" '
using kwallet without parent window!
6. log out, log in
% journalctl -b | grep kwallet
cze 20 08:13:25 bazyliszek sddm[3393]: kwalletd5: Checking for pam module
cze 20 08:13:25 bazyliszek sddm[3393]: kwalletd5: Got pam-login param
cze 20 08:13:25 bazyliszek sddm[3393]: kwalletd5: Waiting for hash on 7-
cze 20 08:13:25 bazyliszek sddm[3393]: kwalletd5: waitingForEnvironment on: 3
cze 20 08:13:25 bazyliszek sddm[3393]: kwalletd5: client connected
cze 20 08:13:25 bazyliszek sddm[3393]: kwalletd5: client disconnected
cze 20 08:13:28 bazyliszek sddm-helper[3389]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_close_session
cze 20 08:13:28 bazyliszek sddm-helper[3389]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
cze 20 08:14:06 bazyliszek sddm-helper[4239]: pam_kwallet5(sddm:auth): (null):
pam_sm_authenticate
cze 20 08:14:06 bazyliszek sddm-helper[4239]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
cze 20 08:14:06 bazyliszek sddm-helper[4239]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_open_session
cze 20 08:14:07 bazyliszek sddm-helper[4256]: pam_kwallet5: final socket path:
/run/user/1000/kwallet5.socket
7. OK: wifi connects automatically
8. restart computer, log in with your password
9. BUG: a dialog appears saying "The application 'kded5' has requested to open
the wallet 'kdewallet'.", wifi connection hangs
10. after opening kwallet, wifi connects correctly
% journalctl -b | grep kwallet
cze 20 08:26:50 bazyliszek sddm-helper[1655]: pam_kwallet5(sddm:auth): (null):
pam_sm_authenticate
cze 20 08:26:50 bazyliszek sddm-helper[1655]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
cze 20 08:26:50 bazyliszek sddm-helper[1655]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_open_session
cze 20 08:26:50 bazyliszek sddm-helper[1688]: pam_kwallet5: final socket path:
/run/user/1000/kwallet5.socket
cze 20 08:26:54 bazyliszek dbus-daemon[1704]: [session uid=1000 pid=1704]
Activating service name='org.kde.kwalletd5' requested by ':1.9' (uid=1000
pid=1758 comm="kded5 " label="unconfined")
cze 20 08:26:54 bazyliszek dbus-daemon[1704]: [session uid=1000 pid=1704]
Successfully activated service 'org.kde.kwall
[digikam] [Bug 399762] New: Digikam Geolocation Correlator ignores time offset
https://bugs.kde.org/show_bug.cgi?id=399762 Bug ID: 399762 Summary: Digikam Geolocation Correlator ignores time offset Product: digikam Version: 5.9.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Geolocation-Correlator Assignee: digikam-bugs-n...@kde.org Reporter: derb...@interia.pl Target Milestone: --- Created attachment 115628 --> https://bugs.kde.org/attachment.cgi?id=115628&action=edit original GPX file used to reproduce the bug SUMMARY STEPS TO REPRODUCE 1. Open attached .jpg file 2. Choose Item -> Edit Geolocation 3. Add attached .gpx file 4. Choose offset of +03:00 (Sofia summer time is GMT+03:00) and click Correlate 5. Change to -03:00 or any other offset OBSERVED RESULT No matter what offset is chosen (+03:00, -03:00 or _any_ other value), photo taken on 10:42 local time is assigned to position at 2018-09-30T08:39:48Z. This is completely absurd, it is not even +04:00 being selected by mistake, but some uneven number. EXPECTED RESULT I want to be able to match photo time of 10:42 to GPS point at 2018-09-30T07:42:05Z, for example by setting offset of +03:00. Currently Digikam is not a tool that will allow me to achieve this. SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.12.6 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION Checked on digikam-5.9.0-01-x86-64.appimage. Reproduces also on Digikam 5.6.0 available from Kubuntu Backports repository. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399762] Digikam Geolocation Correlator ignores time offset
https://bugs.kde.org/show_bug.cgi?id=399762 --- Comment #1 from Piotr Kubowicz --- Created attachment 115629 --> https://bugs.kde.org/attachment.cgi?id=115629&action=edit original JPG file used to reproduce the bug Please feel free to use the image to investigate the bug. Just in case someone is bothered by legal reasons, I hereby release it under CC-BY 4.0. It shows National Palace of Culture in Sofia. The bug causes it to be correlated to a park near Vasil Levski stadium, which is clearly wrong if you take a look at Google Maps. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399762] Digikam Geolocation Correlator ignores time offset
https://bugs.kde.org/show_bug.cgi?id=399762
--- Comment #3 from Piotr Kubowicz ---
I don't live in Sofia. I set my camera to Sofia local time during my travel.
For GPS recording local time is not taken into account. I have just tried
setting the offset to 00:00 but the correlator still chooses the wrong
position, as before.
I was able to set the position correctly using:
exiftool -overwrite_original -geotag '*.gpx' '-geotime<${CreateDate}+03:00' .
so my files are not corrupted and other tools are able to yield correct result.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 399762] Digikam Geolocation Correlator ignores time offset
https://bugs.kde.org/show_bug.cgi?id=399762 --- Comment #5 from Piotr Kubowicz --- UTC+02:00, Europe/Warsaw -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399762] Digikam Geolocation Correlator ignores time offset
https://bugs.kde.org/show_bug.cgi?id=399762 --- Comment #7 from Piotr Kubowicz --- For me it is very counter-intuitive that the offset is counted relative to my current local time. Documentation (https://docs.kde.org/trunk5/en/extragear-graphics/digikam/tool-geolocation.html#geolocation-correlator) is outdated, the GUI says only 'offset', which is ambiguous. I have never seen any place where I was forced to count difference between my current local time and time zone of photos. This means I would need a different setting today and a week from now, since there is a DST change! It looks absurd to me. Anyway, I still think it's a bug that changing the value of the offset has no effect, and that the non-customizable offset used under the hood by Digikam is not in round hours. Have you tried reproducing this bug on your machine? I know for certain that it appears on mine. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399762] Digikam Geolocation Correlator ignores time offset
https://bugs.kde.org/show_bug.cgi?id=399762 --- Comment #10 from Piotr Kubowicz --- One issue may not be clear from the original report. Photo taken on 10:42:49 local time (+03:00) is assigned to position on 2018-09-30T08:39:48Z. Assuming that application uses my machine's local time zone (+02:00) it should choose GPS point on 08:42 UTC. It chooses a track point on 08:39:48 instead, although there are 4 track points between 08:42:09 and 08:42:56. Why? -- You are receiving this mail because: You are watching all bug changes.
