[kleopatra] [Bug 459041] New: Kleopatra Flatpak needs a running gpg-agent from host to work
https://bugs.kde.org/show_bug.cgi?id=459041 Bug ID: 459041 Summary: Kleopatra Flatpak needs a running gpg-agent from host to work Product: kleopatra Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: imbearch...@outlook.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY (This bug is filed for informational purpose, not a real bug) Kleopatra Flatpak may not work out of box. It needs an running gpg-agent from host to work, and here are some instruction for this. In order to run gpg-agent in the background, you can run following command from your terminal: ``` gpg-agent --daemon ``` You can add this line in your `~/.bashrc` or `~/.profile`, so that gpg-agent can start on your login. Or you can utilize systemd to start it. See this for more infomation: https://sources.debian.org/src/gnupg2/2.2.39-1/doc/examples/systemd-user/README/ -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 458688] New: No notification of event will be sent on Flatpak platform
https://bugs.kde.org/show_bug.cgi?id=458688 Bug ID: 458688 Summary: No notification of event will be sent on Flatpak platform Product: Reminder Daemon Version: unspecified Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: imbearch...@outlook.com Target Milestone: --- SUMMARY When using flatpak version of KDE PIM (org.kde.kontact), no notification of calender event will be sent to user's desktop, despite the org.kde.kontact is acutally running in the background. STEPS TO REPRODUCE 1. Run `flatpak install flathub org.kde.kontact` to install Kontact and Kalendar. 2. Add a calender source to Akonadi, by using Kontact or Kalendar from flathub. And different type of calender source will make no difference, I've tested this with local ICS file and remote Caldav source, both behave in the same way. 3. Add a event with reminder to the calender. 4. Wait until when the reminder should show in notification. OBSERVED RESULT No notification of event will be sent on Flatpak platform EXPECTED RESULT Make reminder function works. SOFTWARE/OS VERSIONS Operating System: openSUSE MicroOS 20220829 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.2-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION And I've found Plasma Applets of KDE PIM (such as `Calender` and `Digital Clock` ) will not show calenders created in Flatpak, maybe this is related. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443215] GDK_SCALE and GDK_DPI_SCALE are hard coded and overwrite user config
https://bugs.kde.org/show_bug.cgi?id=443215 Yao Nianqing changed: What|Removed |Added CC||imbearch...@gmail.com Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #4 from Yao Nianqing --- (In reply to David Edmundson from comment #1) > They are hardcoded to fix a bug. > > On wayland scaling is set via the wayland protocol and there is no need for > this. Actually, hard-coding GDK_DPI_SCALE will make GTK applications not scaled when using DPI settings of "Font" KCM. Under this case, QT applications will scale normally, while GTK applications won't. So Firefox is affected by this, and an improperly scaled browser should considered a bug too. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 445264] New: Decode decrypted message with wrong character encoding method
https://bugs.kde.org/show_bug.cgi?id=445264 Bug ID: 445264 Summary: Decode decrypted message with wrong character encoding method Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: imbearch...@gmail.com Target Milestone: --- When KMail received an encrypted mail, it will use GnuPG to decrypt it,and GnuPG will send decrypted data back in UTF-8 (As long as that is text message), so KMail should display those data in UTF-8, too. But sometimes, while there's a header line that indicates charset, for example, `Content-Type: text/plain; charset="gb2312"`, KMail will display the decrypted data in that charset, not UTF-8. So that message will be unreadable. STEPS TO REPRODUCE 1. Received an encrypted mail which indicates its non-UTF-8 charset. You can send a email with inline GPG meaasge from a Chinese Win10 machine with built-in mail client of Win10 to make this. Or you can send a mail to yourself and move it to local maildir, then modify its header. 2. Decrypt it in KMail. OBSERVED RESULT Unreadable characters will display as decrypted message. EXPECTED RESULT Decode it properly. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211105 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 GnuPG: 2.2.27 libgcrypt: 1.9.4 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 394404] baloo file indexer crashes after some runtime
https://bugs.kde.org/show_bug.cgi?id=394404 Yao Nianqing changed: What|Removed |Added CC||imbearch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 394404] baloo file indexer crashes after some runtime
https://bugs.kde.org/show_bug.cgi?id=394404 --- Comment #5 from Yao Nianqing --- Created attachment 114282 --> https://bugs.kde.org/attachment.cgi?id=114282&action=edit New crash information added by DrKonqi baloo_file (5.45.0) using Qt 5.9.4 - What I was doing when the application crashed: When I saved a .odt file, which includes some chinese characters , it crashed. And the file's name includes chinese character ,too. -- Backtrace (Reduced): #7 0x7fe4fa1cea93 in memcpy (__len=18446744073601460320, __src=, __dest=) at /usr/include/bits/string_fortified.h:34 #8 Baloo::PostingCodec::decode (this=this@entry=0x7fa4ebcfc8f7, arr=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/codecs/postingcodec.cpp:42 #9 0x7fe4fa1bff64 in Baloo::PostingDB::get (this=this@entry=0x7fa4ebcfc9e0, term=...) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/postingdb.cpp:100 #10 0x7fe4fa1cc180 in Baloo::WriteTransaction::commit (this=0x7fa4e4004da0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/writetransaction.cpp:259 #11 0x7fe4fa1c54c2 in Baloo::Transaction::commit (this=this@entry=0x7fa4ebcfcaf0) at /usr/src/debug/baloo5-5.45.0-lp150.2.1.x86_64/src/engine/transaction.cpp:262 -- You are receiving this mail because: You are watching all bug changes.
