[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

[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

[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:

[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=edit Notification from Chromium -- You are receiving this mail because: You are watching all bug changes.

[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

[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

[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

[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

[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 #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

[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=edit original JPG file used to reproduce the bug Please feel free to use the image to investigate the bug. Just in case some

[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