[kleopatra] [Bug 484435] Icon in notification area does not match other icons
https://bugs.kde.org/show_bug.cgi?id=484435 --- Comment #4 from Ingo Klöcker --- Further data point: I'm using X11. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 484435] Icon in notification area does not match other icons
https://bugs.kde.org/show_bug.cgi?id=484435 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #3 from Ingo Klöcker --- I cannot reproduce this with Plasma 5 on Tumbleweed. I'm seeing the symbolic icon in the notification area with both Plasma Styles/Themes Breeze and Breeze Dark. Do you see the colored icon also with Breeze? -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 485564] Workspace build fails on Neon developer version when trying to build gpgme
https://bugs.kde.org/show_bug.cgi?id=485564 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #5 from Ingo Klöcker --- Just a heads-up: I have raised the required version of libgpg-error in gpgme to 1.47 (which added the new error code). No idea how to get kdesrc-build/kde-builder to build libgpg-error. Maybe it relies on the version provided by your distribution. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435761] No gpg support for kmymoney available from CI builds
https://bugs.kde.org/show_bug.cgi?id=435761 --- Comment #13 from Ingo Klöcker --- I think we have found the cause for the missing gpg executable. See https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/858 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435761] No gpg support for kmymoney available from CI builds
https://bugs.kde.org/show_bug.cgi?id=435761 --- Comment #12 from Ingo Klöcker --- Git commit 203ad70e20af968d6ee76b67a87ad34a6ce93eee by Ingo Klöcker, on behalf of Thomas Baumgart. Committed on 01/05/2024 at 10:17. Pushed by kloecker into branch 'qt5-lts'. [kmymoney] Try to fix gpg support Add proposed fix (cherry picked from commit a8488c6711148f6efeea006f426da2bcd74f9cf4) M +2-1extragear/kmymoney/kmymoney.py https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/203ad70e20af968d6ee76b67a87ad34a6ce93eee -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435761] No gpg support for kmymoney available from CI builds
https://bugs.kde.org/show_bug.cgi?id=435761 --- Comment #10 from Ingo Klöcker --- Bumping the patchLevel is only needed for packages that are cached. libalkimia may be cached, but applications are never cached. Hence, bumping the patchLevel of an application isn't necessary. Regarding the missing gnupg, try if adding libs/gnupg as direct dependency of kmymoney helps. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435761] No gpg support for kmymoney available from CI builds
https://bugs.kde.org/show_bug.cgi?id=435761 --- Comment #6 from Ingo Klöcker --- (In reply to Ralf Habacker from comment #5) > gpg2 is still not included in the portable package. Try depending on libs/gpgme/gpgme and libs/gpgme/gpgmepp instead of on libs/gpgme in the blueprint. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 484680] Investment quantity does not support decimal numbers
https://bugs.kde.org/show_bug.cgi?id=484680 --- Comment #3 from Ingo Klöcker --- You have to edit the investment in the Investment view. Check the manual if you don't find it. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 484680] Investment quantity does not support decimal numbers
https://bugs.kde.org/show_bug.cgi?id=484680 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- I'm entering fractional share quantities all of the time. Check the Fraction configured for the investment. Maybe it's set to 1/1. I think it defaults to 1/100 and I change it to 1/1000 for every new investment I add (because there doesn't seem to be a way to change the default). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 435761] No gpg support for kmymoney available from binary factory
https://bugs.kde.org/show_bug.cgi?id=435761 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #3 from Ingo Klöcker --- It's not suprising that gpg2.exe is missing if you have the following in kmymoney's exclude list: > # strip most executables > bin/(?!(kmymoney|sqlcipher|kbuildsycoca5|update-mime-database|kioslave|ofxdump|kconf_update|QtWebEngineProcess)).*\.exe -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 484507] No more current binary packages for umbrello available
https://bugs.kde.org/show_bug.cgi?id=484507 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #5 from Ingo Klöcker --- (In reply to Ralf Habacker from comment #4) > For the stable branch an update of craft blueprints was required and has > been applied : > > https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/ > cc4b08e645f05fab3c04eb7e1e192b1b3c70e6ad > https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/ > c3c99957de0af4a5c45d33f873eb1d7df7a71152 > > but it looks like these changes are not (yet) included in the Docker image > used to build the packages, see > https://invent.kde.org/sdk/umbrello/-/jobs/1682886#L112 You need to set/increase the patch level of kdevelop. Otherwise, Craft assumes that the cached build (which doesn't include the patch) can be used. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 --- Comment #5 from Ingo Klöcker --- (In reply to Ralf Habacker from comment #3) > (In reply to Ingo Klöcker from comment #1) > > You have to rename the blue print and all references to it to make the the > > CI templates work for alkimia. > > Thanks for your investigation > > I still have a question about the next steps: How do the updated blueprints > get into the CI images that are used for building? (In reply to Ralf Habacker from comment #4) > (In reply to Ralf Habacker from comment #3) > > I still have a question about the next steps: How do the updated blueprints > > get into the CI images that are used for building? Automatically. > I ask because I had the case in another ticket that they are not updated by > default, https://bugs.kde.org/show_bug.cgi?id=484507 I think in this case the problem was/is that a patch was added to the blueprint of kdevelop, but the patch level of kdevelop wasn't set/increased. Craft uses the patch level to determine if a build can be taken from the cache or if it needs to be rebuilt. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484634] CI job failed to register option: The setting useBreezeDark is already registered.
https://bugs.kde.org/show_bug.cgi?id=484634 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- The actual error is bug 484633. This "bug" here is just the result of suboptimal error handling. I'd close it as "not worth fixing". -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 484633] Craft was unable to find alkimia
https://bugs.kde.org/show_bug.cgi?id=484633 Ingo Klöcker changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- The CI templates expect that the project name "alkimia" matches the name of the Craft blue print. (How else should they know the name of the blue print?) Unfortunately, the blue print is named "libalkimia" (probably for historic reasons). You have to rename the blue print and all references to it to make the the CI templates work for alkimia. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 426724] Missing support for adding dependencies to a specific package version
https://bugs.kde.org/show_bug.cgi?id=426724 --- Comment #7 from Ingo Klöcker --- Re-reading the code that evaluates the dependencies, I saw that one can specify a version number to ensure a minimum version of some dependency, but one cannot specify what version of a dependency is used. The selection of the dependency version that's used for a build happens before and independently of the specified version number. https://invent.kde.org/packaging/craft/-/blob/master/bin/Blueprints/CraftDependencyPackage.py?ref_type=heads#L101 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 426724] Missing support for adding dependencies to a specific package version
https://bugs.kde.org/show_bug.cgi?id=426724 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #5 from Ingo Klöcker --- Setting self.runtimeDependencies["extragear/libalkimia"] to anything other than None makes no sense. The only thing that's relevant is the keys of the dependencies dict. The values are ignored. In KDE's GitLab you can request a specific version by setting this version in the .craft.ini file, e.g. add the following to the .craft.ini file in KMyMoney's master branch to request the master version of libalkimia: ``` [BlueprintSettings] extragear/libalkimia.version=master ``` When you run craft manually you can achieve the same with the command line option `--options extragear/libalkimia.version=master`. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 481980] neochat and kcalc fail to build out of the box on MacOS
https://bugs.kde.org/show_bug.cgi?id=481980 Ingo Klöcker changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- I guess you told Craft that you want Qt 6 when you installed it. The problem is that the latest stable versions of neochat and every other KDE application which for many is still the 23.08 release are using Qt 5. Now that KDE has released version 24.02 of many applications Craft will soon be switched to this version. So, either you completely reinstall Craft and choose Qt 5 or you wait until we have switched Craft to version 24.02 of neochat and kcalc. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 481455] kiconthemes master failed
https://bugs.kde.org/show_bug.cgi?id=481455 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- kontact master requests master of frameworks and libs via the blueprint settings in its `.craft.ini`: ``` kde/frameworks.version=master kde/pim.version=master kde/libs.version=master ``` Don't do this. On Binary Factory Craft builds always used the latest released versions of all dependencies (with very few exceptions). This isn't going to change with GitLab because compiling everything from master is prohibitively expensive. We have a cache for Craft with the latest stable releases for a reason. The Craft people only update the patches when they switch to a new released version of frameworks. Feel free to submit an MR for the blueprint of kiconthemes which doesn't apply the patch to the master version. Even better: Remove all those `kde/*=master` lines kontact's .craft.ini. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 --- Comment #5 from Ingo Klöcker --- I think a good name for the NSS backend depends on how it behaves on different OSes, i.e. if it uses the Windows/macOS certificate store on Windows/macOS then "Firefox Certificate store" is probably not a good name. And I guess most people don't know that Mozilla Firefox was once called Netscape. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481262] option GPG, does not list my gpg certificate
https://bugs.kde.org/show_bug.cgi?id=481262 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #2 from Ingo Klöcker --- Maybe we should change the name of the backend to "GnuPG (S/MIME)" (or "GPGSM", but many won't understand this) to make this more obvious. "GPG" is actually very wrong because gpg is the name of the OpenPGP tool of the GnuPG suite. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 479056] AppImage5.1 531c98b7 fails to start on Ubuntu 20.04: CXXABI_1.3.13, GLIBCXX_3.4.29 and GLIBCXX_3.4.30 not found
https://bugs.kde.org/show_bug.cgi?id=479056 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #4 from Ingo Klöcker --- Previously, AppImages were based on CentOS 7 which used very old base libraries, so that those AppImages ran on most older still supported versions of different distributions. Unfortunately, CentOS 7 is now so old that we couldn't build some of our software anymore with it. Therefore, we switched to SLES-15 as base for our AppImages assuming that it was old enough, so that it works with most supported distributions. But, unfortunately, SLES-15 uses some base libraries that are newer than what some older distributions like Ubuntu 20.04 support. I don't think there's much we can do. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 478260] New: All episodes marked as played after adding new pod cast
https://bugs.kde.org/show_bug.cgi?id=478260 Bug ID: 478260 Summary: All episodes marked as played after adding new pod cast Classification: Applications Product: kasts Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: kloec...@kde.org Target Milestone: --- After adding a pod cast I found all episodes marked as played. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install the sideload APPX built on GitLab on Windows and start the app. 2. Search for the "Stay Forever" pod cast and subscribe to it. 3. Switch to Episodes. OBSERVED RESULT All episodes are marked with a check mark and "Abgespielt" (German for "Played"). EXPECTED RESULT All episodes are marked as "not yet played". SOFTWARE/OS VERSIONS Windows: Windows 10 VM KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Maybe I'm misunderstanding the check mark and "Abgespielt". -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 478257] New: Copy a URL mentioned in a message
https://bugs.kde.org/show_bug.cgi?id=478257 Bug ID: 478257 Summary: Copy a URL mentioned in a message Classification: Applications Product: NeoChat Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: kloec...@kde.org CC: c...@carlschwan.eu Target Milestone: --- I would like to be able to copy a URL mentioned in a message via the context menu. There is a "Copy Link" in the context menu, but it adds a matrix.to link for the message itself to the clipboard (which is sometimes useful). STEPS TO REPRODUCE 1. Look for a message with a URL. 2. Right click on the URL and select Copy Link. OBSERVED RESULT A matrix.to link for the message itself is added to the clipboard. EXPECTED RESULT The URL is added to the clipboard. or There are two actions in the context menu: "Copy Message Link" (Element on Android names this action "Permalink" which seems rather technical) and "Copy Web Link" (KMail names this action "Copy Link Address"). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475391] Tray doesn't show PSI and Nextcloud anymore
https://bugs.kde.org/show_bug.cgi?id=475391 Ingo Klöcker changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Ingo Klöcker --- Today the Nextcloud icon was shown in the tray. The PSI+ icon wasn't shown after login, but I'm not entirely sure that it had been started automatically. After starting PSI+ manually the icon appeared in the system tray. Closing as worksforme because I cannot reproduce it anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475391] New: Tray doesn't show PSI and Nextcloud anymore
https://bugs.kde.org/show_bug.cgi?id=475391 Bug ID: 475391 Summary: Tray doesn't show PSI and Nextcloud anymore Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: kloec...@kde.org CC: mate...@gmail.com Target Milestone: 1.0 Tray doesn't show PSI and Nextcloud anymore. This is a regression. This has worked for years. STEPS TO REPRODUCE 1. Start PSI and/or Nextcloud client (Note: PSI and Nextcloud client are started by the session manager automatically on my system. I haven't tested whether the problem only occurs in this case.) OBSERVED RESULT Neither the PSI icon nor the Nextcloud icon are displayed in the system tray. EXPECTED RESULT The PSI icon and the Nextcloud icon are displayed in the system tray (as before the last update). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Tumbleweed 20231005 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 472056] accessiblevaluelabel.cpp fails to build with Clang 16
https://bugs.kde.org/show_bug.cgi?id=472056 --- Comment #5 from Ingo Klöcker --- Upstream bug report for Qt: https://bugreports.qt.io/browse/QTBUG-117517 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 472056] accessiblevaluelabel.cpp fails to build with Clang 16
https://bugs.kde.org/show_bug.cgi?id=472056 Ingo Klöcker changed: What|Removed |Added Assignee|aheine...@gnupg.org |kloec...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 472056] accessiblevaluelabel.cpp fails to build with Clang 16
https://bugs.kde.org/show_bug.cgi?id=472056
--- Comment #4 from Ingo Klöcker ---
It's on my todo list to open an upstream bug for this. The old bug was mainly
about int vs. unsigned int.
For now the fix is to patch
enum Role {
to
enum Role : int {
in src/gui/accessible/qaccessible_base.h of qtbase.
--
You are receiving this mail because:
You are watching all bug changes.
[kleopatra] [Bug 472056] accessiblevaluelabel.cpp fails to build with Clang 16
https://bugs.kde.org/show_bug.cgi?id=472056
Ingo Klöcker changed:
What|Removed |Added
CC||kloec...@kde.org
Resolution|--- |UPSTREAM
Status|REPORTED|RESOLVED
--- Comment #2 from Ingo Klöcker ---
QAccessible::UserRole is documented as "The first value to be used for user
defined roles.". Hence, we are supposed to use QAccessible::UserRole + n for
user defined roles. I'm using QAccessible::UserRole + 1.
Unfortunately, Qt chose 0x as value for QAccessible::UserRole, so that
all values of the QAccessible::Role enum fit into uint16 and apparently clang
16 chooses uint16 as underlying type (because the "underlying type is an
implementation-defined integral type that can represent all enumerator
values").
I consider this a bug in Qt. To me, Qt clearly intends QAccessible::Role as a
32-bit enum (apparent from the 32-bit hex notation used for the enum values)
and therefore needs to state int (or unsigned int) explicitly as underlying
type of QAccessible::Role:
```
enum Role {
NoRole = 0x,
TitleBar = 0x0001,
MenuBar= 0x0002,
```
https://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/accessible/qaccessible_base.h
This is related to bug https://bugreports.qt.io/browse/QTBUG-64962 which was
closed as invalid without addressing the issue that compilers can choose
smaller underlying types than (seemingly) intended by Qt.
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 474505] Kate auto-detects unsuitable indentation
https://bugs.kde.org/show_bug.cgi?id=474505 Ingo Klöcker changed: What|Removed |Added Summary|Kate auto-detects wrong |Kate auto-detects |indentation |unsuitable indentation -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 474505] New: Kate auto-detects wrong indentation
https://bugs.kde.org/show_bug.cgi?id=474505 Bug ID: 474505 Summary: Kate auto-detects wrong indentation Classification: Applications Product: kate Version: 23.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: indentation Assignee: kwrite-bugs-n...@kde.org Reporter: kloec...@kde.org Target Milestone: --- Created attachment 161612 --> https://bugs.kde.org/attachment.cgi?id=161612=edit Markdown file for which Kate auto-detects indentation width 7 For the attached file Kate auto-detects an indentation of 7. I think it shouldn't assume any indentation width for this file and instead use the default. STEPS TO REPRODUCE 1. Enable "Automatically detect file indentation" 2. Open the attached file OBSERVED RESULT Kate automatically sets indentation to 7. Shows "Soft Tabs: 7 (4)" in the status bar. EXPECTED RESULT Kate uses standard indentation, i.e. 4. Even though the file ends with many lines which seem to suggest an indentation of 7, there are many other lines which suggest indentations of 4, 12, 32. I think, in case of an indentation histogram with multiple peaks without a common divisor, Kate shouldn't assume a non-standard indentation. Or it should switch from fixed width indentation to "smart indentation" (i.e. indentation based on the next non-empty line above the cursor). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 471061] Installation for /usr/local installs plugins into incorrect path
https://bugs.kde.org/show_bug.cgi?id=471061 --- Comment #5 from Ingo Klöcker --- prefix.sh being installed for root only looks like a bug. This is probably caused by the assumption that nowadays people install into ~/.local (which is the default prefix used by kdesrc-build if I remember correctly) with their normal user instead of installing as root into something like /usr/local which requires root permissions. One more thing: I just remembered that there is another script accompanying kdesrc-build: kdesrc-run. Those two scripts are meant to be used in combination. kdesrc-build to build and install an application and kdesrc-run to run it. So, in your case `kdesrc-run kmymoney` should run your self-built kmymoney with correctly setup environment. Another thing to note is that kdesrc-build is primarily a tool for developers. It wasn't developed as tool for end users to simplify building, installing and running a KDE application. It can be used by end users who want to run the latest bleeding-edge development version of an application, but it's just not optimized for this. Having said this I expect merge requests which, optionally, make kdesrc-build install a wrapper similar to what you did to be considered for inclusion. https://invent.kde.org/sdk/kdesrc-build -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 471061] Installation for /usr/local installs plugins into incorrect path
https://bugs.kde.org/show_bug.cgi?id=471061 Ingo Klöcker changed: What|Removed |Added Resolution|--- |NOT A BUG CC||kloec...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Ingo Klöcker --- Qt applications look for plugins in the paths specified by the QT_PLUGIN_PATH environment variable (additionally to a few built-in default locations). If you install to a different prefix, you are responsible for telling the system where to look for certain files. The helper script prefix.sh created by kdesrc-build sets the following environment variables: PATH, XDG_DATA_DIRS, XDG_CONFIG_DIRS, QT_PLUGIN_PATH, QML2_IMPORT_PATH, QT_QUICK_CONTROLS_STYLE_PATH Not all of them are relevant for kmymoney (e.g. the last two) and PATH most likely already contains /usr/local/bin, but you will have to set the other ones if you expect kmymoney to work properly when installed outside of the standard location. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 470246] kf.dbusaddons: Couldn't register name 'local.kleopatra' with DBUS - another process owns it already!
https://bugs.kde.org/show_bug.cgi?id=470246 --- Comment #3 from Ingo Klöcker --- Git commit 9557e5ec15997ff0bd712c7d4b7016b98c2e9651 by Ingo Klöcker, on behalf of Timothée Ravier. Committed on 30/05/2023 at 12:38. Pushed by kloecker into branch 'release/23.04'. Set OrganizationDomain before registering the DBus service The OrganizationDomain is used by KDBusAddons to generate the service name used to register on the session bus so we need to set it up before we try registering on the bus. See: https://bugs.kde.org/show_bug.cgi?id=470246 See: https://github.com/flathub/org.kde.kleopatra/issues/34 (cherry picked from commit 66753b1e0d306d589f17c5dfd55e51e45d818ec2) M +3-0src/main.cpp https://invent.kde.org/pim/kleopatra/-/commit/9557e5ec15997ff0bd712c7d4b7016b98c2e9651 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 470246] kf.dbusaddons: Couldn't register name 'local.kleopatra' with DBUS - another process owns it already!
https://bugs.kde.org/show_bug.cgi?id=470246 --- Comment #2 from Ingo Klöcker --- Git commit 66753b1e0d306d589f17c5dfd55e51e45d818ec2 by Ingo Klöcker, on behalf of Timothée Ravier. Committed on 30/05/2023 at 12:31. Pushed by kloecker into branch 'master'. Set OrganizationDomain before registering the DBus service The OrganizationDomain is used by KDBusAddons to generate the service name used to register on the session bus so we need to set it up before we try registering on the bus. See: https://bugs.kde.org/show_bug.cgi?id=470246 See: https://github.com/flathub/org.kde.kleopatra/issues/34 M +3-0src/main.cpp https://invent.kde.org/pim/kleopatra/-/commit/66753b1e0d306d589f17c5dfd55e51e45d818ec2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392804] Kmail 5.7.3 does not import joined gpg key
https://bugs.kde.org/show_bug.cgi?id=392804 --- Comment #4 from Ingo Klöcker --- You may be missing a plugin. Make sure that all kdepim addons are installed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463089] macOS (and Windows?): Kdenlive UI does not show all localized strings from po files (especially in Preferences)
https://bugs.kde.org/show_bug.cgi?id=463089 --- Comment #10 from Ingo Klöcker --- (In reply to emohr from comment #9) > I can confirm that on Slovenian the Qt-Icons are not translated on Mac and > Windows (as you show on your screenshot) . But Italian and Hebrew (for > example), the Qt-Icons are translated. Maybe some Qt settings are not proper > done: sl,Slovenian? I checked that Qt does have Slovenian translations (see https://code.qt.io/cgit/qt/qttranslations.git/tree/translations). One difference to most other languages is that for Slovenian the "base" translations are all in qt_sl.ts while for example for Italian qt_it.ts is just a dummy file that includes qtbase_it.ts and a few other .ts files. If this difference causes the problem then it should be reproducible with other languages using just the qt_LL.ts file, e.g. gl, lt, pt_PT, sv. If you add `kf5.ki18n.debug=true` to the qtlogging.ini (for details see https://doc.qt.io/qt-5/qloggingcategory.html#logging-rules), then you'll get debug output if loading a language catalog fails. Moreover, on Windows, you could use Process Monitor to check which .qm files kdenlive loads. I won't have time to look into this for the next few weeks. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469383] Importing an OpenPGP key attached to an encrypted message doesn't work
https://bugs.kde.org/show_bug.cgi?id=469383 Ingo Klöcker changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |messagelib/commit/925db3260 |messagelib/commit/b6e4d5323 |235192df76d6585e6e01ee9973e |f8b9af11e72ec3fb32946ff0036 |d1cf|188e --- Comment #4 from Ingo Klöcker --- Git commit b6e4d5323f8b9af11e72ec3fb32946ff0036188e by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 05/05/2023 at 14:43. Pushed by kloecker into branch 'master'. Fix references to message parts in encrypted messages For a content node in the decrypted mime tree of an encrypted message content()->index() gives a wrong "relative" index inside the decrypted mime tree. NodeHelper::fromHREF() which is used to get the content node for the reference has no idea that is need to look inside the decrypted message and returns the content node of the encrypted message corresponding to the reference which is most likely the encrypted message part. As a result importing an OpenPGP key or a vCard attached to an encrypted message failed because the wrong message part was passed to the corresponding URL handlers. Using (a simpler overload of) NodeHelper::asHREF() (i.e. the counter part for NodeHelper::fromHREF()) for generating the reference fixes those problems. I have verified that this change is safe for all users of MessagePart::makeLink (which all live in kdepim-addons) and I have tested that it fixes importing OpenPGP keys and vCards attached to encrypted messages. FIXED-IN: 5.23.1 (cherry picked from commit 925db3260235192df76d6585e6e01ee9973ed1cf) M +1-1mimetreeparser/src/messagepart.cpp M +5-0mimetreeparser/src/nodehelper.cpp M +3-0mimetreeparser/src/nodehelper.h https://invent.kde.org/pim/messagelib/commit/b6e4d5323f8b9af11e72ec3fb32946ff0036188e -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469383] Importing an OpenPGP key attached to an encrypted message doesn't work
https://bugs.kde.org/show_bug.cgi?id=469383 Ingo Klöcker changed: What|Removed |Added Version Fixed In||5.23.1 Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pim/ ||messagelib/commit/925db3260 ||235192df76d6585e6e01ee9973e ||d1cf Resolution|--- |FIXED --- Comment #3 from Ingo Klöcker --- Git commit 925db3260235192df76d6585e6e01ee9973ed1cf by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 05/05/2023 at 14:30. Pushed by kloecker into branch 'release/23.04'. Fix references to message parts in encrypted messages For a content node in the decrypted mime tree of an encrypted message content()->index() gives a wrong "relative" index inside the decrypted mime tree. NodeHelper::fromHREF() which is used to get the content node for the reference has no idea that is need to look inside the decrypted message and returns the content node of the encrypted message corresponding to the reference which is most likely the encrypted message part. As a result importing an OpenPGP key or a vCard attached to an encrypted message failed because the wrong message part was passed to the corresponding URL handlers. Using (a simpler overload of) NodeHelper::asHREF() (i.e. the counter part for NodeHelper::fromHREF()) for generating the reference fixes those problems. I have verified that this change is safe for all users of MessagePart::makeLink (which all live in kdepim-addons) and I have tested that it fixes importing OpenPGP keys and vCards attached to encrypted messages. FIXED-IN: 5.23.1 M +1-1mimetreeparser/src/messagepart.cpp M +5-0mimetreeparser/src/nodehelper.cpp M +3-0mimetreeparser/src/nodehelper.h https://invent.kde.org/pim/messagelib/commit/925db3260235192df76d6585e6e01ee9973ed1cf -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469383] Importing an OpenPGP key attached to an encrypted message doesn't work
https://bugs.kde.org/show_bug.cgi?id=469383 --- Comment #2 from Ingo Klöcker --- Git commit eb0f9afecdd29387f2c65c07e8c20445226e17a9 by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 05/05/2023 at 14:41. Pushed by kloecker into branch 'master'. Do not report success if no keys where considered for import M +2-0 plugins/messageviewer/bodypartformatter/gnupgwks/pgpkeyurlhandler.cpp https://invent.kde.org/pim/kdepim-addons/commit/eb0f9afecdd29387f2c65c07e8c20445226e17a9 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469383] Importing an OpenPGP key attached to an encrypted message doesn't work
https://bugs.kde.org/show_bug.cgi?id=469383 Ingo Klöcker changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469383] Importing an OpenPGP key attached to an encrypted message doesn't work
https://bugs.kde.org/show_bug.cgi?id=469383 Ingo Klöcker changed: What|Removed |Added Assignee|kdepim-b...@kde.org |kloec...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392804] Kmail 5.7.3 does not import joined gpg key
https://bugs.kde.org/show_bug.cgi?id=392804 Ingo Klöcker changed: What|Removed |Added Resolution|--- |WORKSFORME CC||kloec...@kde.org Status|CONFIRMED |RESOLVED --- Comment #2 from Ingo Klöcker --- I cannot reproduce this. I get the message "The key has been successfully imported" after clicking on "Import key". Even for an encrypted message with attached OpenPGP key I get this message although the actual import fails (see bug 469383). Since your report says that "clicking on it does nothing", I assume that your problem has been fixed because in the current version the import is at least attempted and the result is reported. If the problem still persists for you with the latest version of KMail (currently 5.23.0 in KDE Gear release 23.04.0), then please run KMail with GpgME debugging like this `GPGME_DEBUG=8 kmail` in Konsole. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 409851] "Import key" link in mails with attached PGP key doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=409851 Ingo Klöcker changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- I cannot reproduce this. I get the message "The key has been successfully imported" after clicking on "Import key". Even for an encrypted message with attached OpenPGP key I get this message although the actual import fails (see bug 469383). Since your report says that "nothing happens at all", I assume that your problem has been fixed because in the current version the import is at least attempted and the result is reported. If the problem still persists for you with the latest version of KMail (currently 5.23.0 in KDE Gear release 23.04.0), then please run KMail with GpgME debugging like this `GPGME_DEBUG=8 kmail` in Konsole. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469383] New: Importing an OpenPGP key attached to an encrypted message doesn't work
https://bugs.kde.org/show_bug.cgi?id=469383 Bug ID: 469383 Summary: Importing an OpenPGP key attached to an encrypted message doesn't work Classification: Applications Product: kmail2 Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: kloec...@kde.org Target Milestone: --- SUMMARY Importing an OpenPGP key attached to an encrypted message doesn't work. STEPS TO REPRODUCE 1. You need an encrypted message with an attached OpenPGP key. 2. Open the message, decrypt it, and click on "Import key". OBSERVED RESULT KMail reports "The key has been successfully imported.". But gpg and Kleopatra don't list the key. EXPECTED RESULT Importing the key works. And KMail should report a failure if the import failed for some reason (e.g. corrupt OpenPGP key). ADDITIONAL INFORMATION Running kmail with `GPGME_DEBUG=8` I get the following ``` 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_write: check: -BEGIN PGP MESSAGE- 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_write: check: 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_write: check: hF4D0z8hfWyIqqISAQdARIzZlxp2IopOOxw8pVC8L+NV3yCu 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_write: check: Fgmuk1yDG66tmR4w [...] 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_write: check: =/TYt 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_write: check: -END PGP MESSAGE- [...] 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_read: check: [GNUPG:] NODATA 1 2023-05-05 10:21:51 gpgme[19116.4aac] _gpgme_io_read: check: [GNUPG:] IMPORT_RES 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ``` This shows two things: * KMail passes the encrypted message body instead of the attached key to the crypto backend. * The crypto backend reports that no data was found, but KMail still reports success. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469304] KMail does not find the key used to sign a message if a signing subkey was used
https://bugs.kde.org/show_bug.cgi?id=469304 Ingo Klöcker changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |messagelib/commit/606ea1478 |messagelib/commit/70f392567 |d2d5b5aacdc6ef3f050655fe035 |84280d2034aa7bf1c4765f606c2 |2d87|2d56 --- Comment #2 from Ingo Klöcker --- Git commit 70f39256784280d2034aa7bf1c4765f606c22d56 by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 03/05/2023 at 15:47. Pushed by kloecker into branch 'master'. Look for matching subkey if no key was found for fingerprint If the message was signed with a signing subkey instead of with the primary key of an OpenPGP certificate, then we won't find a key with findByFingerprint(). To look for a matching subkey we need to use findSubkeysByKeyID(). FIXED-IN: 5.23.1 (cherry picked from commit 606ea1478d2d5b5aacdc6ef3f050655fe0352d87) M +11 -1mimetreeparser/src/messagepart.cpp https://invent.kde.org/pim/messagelib/commit/70f39256784280d2034aa7bf1c4765f606c22d56 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469304] KMail does not find the key used to sign a message if a signing subkey was used
https://bugs.kde.org/show_bug.cgi?id=469304 Ingo Klöcker changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.23.1 Latest Commit||https://invent.kde.org/pim/ ||messagelib/commit/606ea1478 ||d2d5b5aacdc6ef3f050655fe035 ||2d87 --- Comment #1 from Ingo Klöcker --- Git commit 606ea1478d2d5b5aacdc6ef3f050655fe0352d87 by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 03/05/2023 at 12:51. Pushed by kloecker into branch 'release/23.04'. Look for matching subkey if no key was found for fingerprint If the message was signed with a signing subkey instead of with the primary key of an OpenPGP certificate, then we won't find a key with findByFingerprint(). To look for a matching subkey we need to use findSubkeysByKeyID(). FIXED-IN: 5.23.1 M +11 -1mimetreeparser/src/messagepart.cpp https://invent.kde.org/pim/messagelib/commit/606ea1478d2d5b5aacdc6ef3f050655fe0352d87 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469304] KMail does not find the key used to sign a message if a signing subkey was used
https://bugs.kde.org/show_bug.cgi?id=469304 Ingo Klöcker changed: What|Removed |Added Assignee|kdepim-b...@kde.org |kloec...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469304] New: KMail does not find the key used to sign a message if a signing subkey was used
https://bugs.kde.org/show_bug.cgi?id=469304 Bug ID: 469304 Summary: KMail does not find the key used to sign a message if a signing subkey was used Classification: Applications Product: kmail2 Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: kloec...@kde.org Target Milestone: --- SUMMARY KMail claims that messages signed with a subkey of my own key are signed with an unknown key. STEPS TO REPRODUCE 1. You need an OpenPGP certficate with a signing subkey. 2. Sign a message with this key and send it to yourself (or use Send Later to put it in your outbox). 3. View the message. OBSERVED RESULT I have an OpenPGP certficate with a signing subkey that is used to sign my messages. KMail has no problem signing my messages, but when viewing my messages KMail says: > Message was signed on 25.04.23 18:24 with unknown key > 0xDB8E020E328C30942060BF21B16F599516474ABA. > The validity of the signature cannot be verified. > Status: Good signature Obviously, this doesn't make any sense because how can the signature be good if it was signed with an unknown key. It turns out that gpg which is used to verify the signature very well knows the key, but KMail is not able to find it. EXPECTED RESULT KMail should say something like: > Message was signed by *@ingo-kloecker.de (Key ID: 0xE375339BF4C51840). > The signature is valid and the key is ultimately trusted. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466673] Add ability to save highlighting and annotations in file
https://bugs.kde.org/show_bug.cgi?id=466673 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #7 from Ingo Klöcker --- (In reply to JDT from comment #6) > So, I'm puzzled. Why does the documentation still speak of the problem. I > checked and this page is in the current manual: > https://docs.kde.org/stable5/en/okular/okular/annotations.html I had a quick look and I don't see what you mean (but maybe I have missed it or someone has silently changed/removed it). Anyway. Yes, the page talks about an Okular-specific document archive that can be used for file formats that do not support annotations directly. But the page also reads > You can also save annotations directly into PDF files. > You can use File → Save to save it over the current file > or File → Save As... to save it to a new file. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438703] Missing translations for a few common buttons like OK and Cancel (Kate official builds only)
https://bugs.kde.org/show_bug.cgi?id=438703 --- Comment #22 from Ingo Klöcker --- If the user has configured a different language than the system language for Kate, then the problem could most likely still be experienced (see bug 464694). This remaining issue has now been fixed, so that also this bug should now really be fixed (if kate uses the upcoming KF5 1.104). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463089] macOS (and Windows?): Kdenlive UI does not show all localized strings from po files (especially in Preferences)
https://bugs.kde.org/show_bug.cgi?id=463089 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #3 from Ingo Klöcker --- With the fix of bug 464694, translated UI texts coming from Qt or from KF libraries should now be displayed in the correct language (if kdenlive uses the upcoming KF5 1.104). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 Ingo Klöcker changed: What|Removed |Added Version Fixed In||5.104 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 Ingo Klöcker changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #12 from Ingo Klöcker --- This issue is now fixed in ki18n and in the code generated by ecm_create_qm_loader for libraries using Qt's translation functionality. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 --- Comment #11 from Ingo Klöcker --- Git commit bc92a8611b2c93ec0c4b3ae13b7b8c021845f483 by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 27/02/2023 at 08:15. Pushed by kloecker into branch 'master'. Load translations for application-specific language also on Win and Mac On Windows and Apple OSs, we cannot use QLocale::system() because on those OSs Qt ignores LANGUAGE (which is set by kxmlgui to the application-specific languages configured by the user). We need to check LANGUAGE ourselves. M +24 -4modules/ECMQmLoader.cpp.in https://invent.kde.org/frameworks/extra-cmake-modules/commit/bc92a8611b2c93ec0c4b3ae13b7b8c021845f483 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 --- Comment #10 from Ingo Klöcker --- Git commit 7cdbd9789d3b7beeb5acda22c3e940f0235f438a by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 27/02/2023 at 08:19. Pushed by kloecker into branch 'kf5'. Load translations for application-specific language also on Win and Mac On Windows and Apple OSs, we cannot use QLocale::system() because on those OSs Qt ignores LANGUAGE (which is set by kxmlgui to the application-specific languages configured by the user). We need to check LANGUAGE ourselves. (cherry picked from commit bc92a8611b2c93ec0c4b3ae13b7b8c021845f483) M +24 -4modules/ECMQmLoader.cpp.in https://invent.kde.org/frameworks/extra-cmake-modules/commit/7cdbd9789d3b7beeb5acda22c3e940f0235f438a -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 --- Comment #8 from Ingo Klöcker --- Git commit fb5d9bdbdc6fb832c53078cd72a6b4b62660c9e6 by Ingo Klöcker. Committed on 21/02/2023 at 16:26. Pushed by kloecker into branch 'kf5'. Load translations for application-specific language also on Win and Mac On Windows and Apple OSs, we cannot use QLocale::system() because on those OSs Qt ignores LANGUAGE (which is set by kxmlgui to the application-specific languages configured by the user). We need to check LANGUAGE ourselves. (cherry picked from commit fb7d5e2a0433f171229ef58393cbfbf0e23ab2b6) M +20 -2src/i18n/main.cpp https://invent.kde.org/frameworks/ki18n/commit/fb5d9bdbdc6fb832c53078cd72a6b4b62660c9e6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 --- Comment #7 from Ingo Klöcker --- Git commit fb7d5e2a0433f171229ef58393cbfbf0e23ab2b6 by Ingo Klöcker. Committed on 21/02/2023 at 16:17. Pushed by kloecker into branch 'master'. Load translations for application-specific language also on Win and Mac On Windows and Apple OSs, we cannot use QLocale::system() because on those OSs Qt ignores LANGUAGE (which is set by kxmlgui to the application-specific languages configured by the user). We need to check LANGUAGE ourselves. This MR replaces kxmlgui!145. It fixes the bug for the translations provided by Qt. To fix the bug also for translations coming from .qm files in KF libraries a similar change in ecm is needed. I have tested this MR (for KF5) with Kate on Windows. M +20 -2src/i18n/main.cpp https://invent.kde.org/frameworks/ki18n/commit/fb7d5e2a0433f171229ef58393cbfbf0e23ab2b6 -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 465192] F-Droid repository advertises obsolete URL
https://bugs.kde.org/show_bug.cgi?id=465192 Ingo Klöcker changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Ingo Klöcker --- Should be fixed for both repos. Moreover, they should now have a KDE gear icon (whereever that is displayed). -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 465192] F-Droid repository advertises obsolete URL
https://bugs.kde.org/show_bug.cgi?id=465192 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- Most likely, we need to update the value of `repo_url` in the `config.yml` of our repo(s). The next run of `fdroid deploy` (which is run by binary factory) should update the advertised URL. See https://f-droid.org/en/docs/Setup_an_F-Droid_App_Repo/#customization. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 --- Comment #4 from Ingo Klöcker --- Git commit b614a60a2e5bcca6c40675e3a1a9de3000911066 by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 30/01/2023 at 14:35. Pushed by kloecker into branch 'fix-language-override-on-win-and-mac'. Load translations for application-specific language also on Win and Mac On Windows and Apple OSs, we cannot use QLocale::system() because on those OSs Qt ignores LANGUAGE (which is set by kxmlgui to the application-specific languages configured by the user). We need to check LANGUAGE ourselves. M +19 -1src/i18n/main.cpp https://invent.kde.org/frameworks/ki18n/commit/b614a60a2e5bcca6c40675e3a1a9de3000911066 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 --- Comment #3 from Ingo Klöcker --- Analysis: * kxmlgui prepends the application-specific languages to the LANGUAGE environment variable. * ki18n uses QLocale::system().name() to know which translations to load. * This works on Unix because Qt considers LANGUAGE when (re-)initializing the system locale. * This doesn't work on Windows because Qt completely ignores LANGUAGE on Windows. On Windows, Qt does consider LANG, but unfortunately LANG is stored in a function static, i.e. once it has been initialized changes to LANG will be ignored. Therefore, my naïve attempt with https://invent.kde.org/frameworks/kxmlgui/-/merge_requests/145 doesn't work. The result is that on Windows all .qm files are loaded for the system language and not for the application-specific language. Possible (Windows-specific) solutions: a) Replace all usage of QLocale::system().name() in ki18n and in the ECM-generated qm loader with QLocale(first language in LANGUAGE).name(). This could be a performance problem if creating a custom QLocale is very slow. (QLocale::system() is a singleton.) b) Set LANG before QLocale::system() is initialized the first time which means before Q*Application is created. This creates a chicken-egg-problem which may not be solvable without touching all applications because the code that loads the application-specific language needs to know the name of the application (and currently uses qAppName() which requires Q*Application to be created already). I'll go for a). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694 --- Comment #1 from Ingo Klöcker --- This problem does not exist in Krita 5.1.5 (which uses copies of many KF5 frameworks). On startup Krita also first loads the German (and English) .qm files, but later it also loads the Spanish .qm files. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 464694] New: Mixed language in UI when using application-specific override language on Windows
https://bugs.kde.org/show_bug.cgi?id=464694
Bug ID: 464694
Summary: Mixed language in UI when using application-specific
override language on Windows
Classification: Frameworks and Libraries
Product: frameworks-kxmlgui
Version: unspecified
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: kloec...@kde.org
Target Milestone: ---
Created attachment 155529
--> https://bugs.kde.org/attachment.cgi?id=155529=edit
Configure Language dialog in Kate showing mixed language UI
On Windows, changing the application language results in a mixed language UI
STEPS TO REPRODUCE
1. Start Kate on Windows
2. Open Settings->Configure Language and select a different primary language
(should be different from the system language).
3. Close the dialog with OK and restart Kate.
4. Open Settings->Configure Language dialog
OBSERVED RESULT
The Configure Language dialog is partially using German translation (German is
the Windows system language) and partially using the configure language (e.g.
Spanish).
EXPECTED RESULT
The configured language is used for the whole UI.
SOFTWARE/OS VERSIONS
Windows: 10
KDE Frameworks Version: 5.102
Qt Version: 5.15.8
ADDITIONAL INFORMATION
Looks like the system language is used for translations coming from Qt while
the configured language is used for translations coming from KDE.
With procmon I checked which language files Kate loads (in which order):
* Kate looks for/loads .qm files from bin\data\locale\{en,de}, i.e. English and
German translations, for some KF5 libraries
* Kate looks for/loads qt*_en.qm and qt*_de.qm files from bin\translations for
the Qt libraries
* Kate looks for/loads .mo files from bin\data\locale\es, i.e. Spanish
translations
This confirms my assumption that all Qt translations (.qm) are German, the
system language, (with English as fallback) while all KDE/gettext translations
(.mo) are Spanish, i.e. the configured language.
Hypothesis: KXMLGui's initializeLanguages() runs after the initialization
function of ki18n and therefore ki18n loads the German translations.
--
You are receiving this mail because:
You are watching all bug changes.
[kleopatra] [Bug 464229] mainwindow icon bug
https://bugs.kde.org/show_bug.cgi?id=464229 Ingo Klöcker changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||kleopatra/commit/9dfe6709cf ||f75f777310968bb30151599e68d ||d0c Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Ingo Klöcker --- Git commit 9dfe6709cff75f777310968bb30151599e68dd0c by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 20/01/2023 at 14:14. Pushed by kloecker into branch 'master'. Explicitly set the window icon Apparently, some window managers need the icon to be set explicitly. M +2-0src/main.cpp https://invent.kde.org/pim/kleopatra/commit/9dfe6709cff75f777310968bb30151599e68dd0c -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 463727] New: KTimeTracker opened 600+ questions about idle desktop while session was locked
https://bugs.kde.org/show_bug.cgi?id=463727 Bug ID: 463727 Summary: KTimeTracker opened 600+ questions about idle desktop while session was locked Classification: Applications Product: ktimetracker Version: 5.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aspotas...@gmail.com Reporter: kloec...@kde.org Target Milestone: --- I have enabled automatic tracking. Worked for some hours. Then I locked the screen and went for lunch. When I came back the screen locker was unresponsive and didn't show the password prompt. After unlocking the session via the command line, I could see that KTimeTracker had opened about 620 message boxes telling me that the desktop session was idle since whatever and whether I wanted to continue. The system reacted extremely slow, so that quickly closing the 600+ message boxes wasn't an option. Even terminating the session via the command line and logging in again didn't recover the session, so that I resorted to a reboot. I have uninstalled KTimeTracker again. I anyway need time tracking by virtual desktop and not by application window which KTimeTracker doesn't provide. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 463548] update option
https://bugs.kde.org/show_bug.cgi?id=463548 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- Please install Okular from the Microsoft Store. Then you will automatically be notified if updates are available. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463139] Plasma session restore no longer opens files in kwrite
https://bugs.kde.org/show_bug.cgi?id=463139 --- Comment #4 from Ingo Klöcker --- Yes, for Kate it works as good as before the upgrade regardless of whether I use a named session or just a bunch of files. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463139] Plasma session restore no longer opens files in kwrite
https://bugs.kde.org/show_bug.cgi?id=463139 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #2 from Ingo Klöcker --- This looks very much like a regression of the new tab support in KWrite. On the first login after the upgrade to 22.12, I had hoped that this is just a one-off problem because each instance of KWrite now has to remember a list of open documents instead of just one document. But apparently, this is just broken and not just an upgrade issue. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 461509] AppImage: Plugins fail to load because of wrong rpath
https://bugs.kde.org/show_bug.cgi?id=461509 Ingo Klöcker changed: What|Removed |Added Assignee|vonr...@kde.org |kloec...@kde.org --- Comment #1 from Ingo Klöcker --- taking -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 461509] New: AppImage: Plugins fail to load because of wrong rpath
https://bugs.kde.org/show_bug.cgi?id=461509 Bug ID: 461509 Summary: AppImage: Plugins fail to load because of wrong rpath Classification: Developer tools Product: Craft Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Core Assignee: vonr...@kde.org Reporter: kloec...@kde.org CC: kde-wind...@kde.org Target Milestone: --- Some plugins used by applications packaged as AppImage fail to load because of missing symbols. The root cause is an incorrect rpath of the plugins. The rpath has to be set, so that the plugin finds the matching libraries in the AppImage instead of on the host system. Examples of reported bugs: https://bugs.kde.org/show_bug.cgi?id=448308 https://bugs.kde.org/show_bug.cgi?id=454699 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 459682] kateprojectplugin.so undefined symbol error in AppImage
https://bugs.kde.org/show_bug.cgi?id=459682 --- Comment #6 from Ingo Klöcker --- (In reply to Christoph Cullmann from comment #4) > (In reply to Ingo Klöcker from comment #3) > > (In reply to Christoph Cullmann from comment #2) > > > And I assume this here > > > > > > https://invent.kde.org/packaging/appimage-packaging > > > > > > is not the current state of the tooling for this? > > > > Correct. This project is dead. > > Could we let sysadmin archive the repo/project then to not confuse people? When I asked Ben about appimage-packaging (I think last week), he said that he should probably archive it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 459682] kateprojectplugin.so undefined symbol error in AppImage
https://bugs.kde.org/show_bug.cgi?id=459682 --- Comment #5 from Ingo Klöcker --- (In reply to Christoph Cullmann from comment #1) > Ingo, is there one component for this where we collect such issues? It's a problem in the AppImagePackager of craft. The rpath of the plugins need to be rewritten for the AppImage. craft/core is the best component for this. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 459682] kateprojectplugin.so undefined symbol error in AppImage
https://bugs.kde.org/show_bug.cgi?id=459682 --- Comment #3 from Ingo Klöcker --- (In reply to Christoph Cullmann from comment #2) > And I assume this here > > https://invent.kde.org/packaging/appimage-packaging > > is not the current state of the tooling for this? Correct. This project is dead. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459333] Errors with media files
https://bugs.kde.org/show_bug.cgi?id=459333 --- Comment #3 from Ingo Klöcker --- Please check if the latest build available at https://binary-factory.kde.org/view/Windows%2064-bit/job/Okular_Release_win64/1167/ i.e. the installer okular-22.08.1-1167-windows-msvc2019_64-cl.exe works for you. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459333] Errors with media files
https://bugs.kde.org/show_bug.cgi?id=459333 --- Comment #2 from Ingo Klöcker --- Git commit 4ed46915beb076631985510f8bdbb30bc0e1f0de by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 12/10/2022 at 14:00. Pushed by kloecker into branch 'master'. okular: Add the phonon-vlc backend Hopefully, this will make it possible to play multimedia files embedded in PDFs on Windows. Disabled for macOS (as in kstars) and for Android. M +2-0kde/applications/okular/okular.py https://invent.kde.org/packaging/craft-blueprints-kde/commit/4ed46915beb076631985510f8bdbb30bc0e1f0de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 459341] Kmail crash when trying to write recipent address in the new mail window
https://bugs.kde.org/show_bug.cgi?id=459341 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Ingo Klöcker --- qgpgme 1.17.0 was binary incompatible. Please file a bug with Fedora that they need to skip 1.17.0 and use at least 1.17.1. See https://dev.gnupg.org/T5872. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 440177] no kconf_update5 support on binary factory
https://bugs.kde.org/show_bug.cgi?id=440177 --- Comment #3 from Ingo Klöcker --- kconf_update.exe should now be included in the kmymoney installers, but I couldn't test it because kmymoney doesn't build on binary factory since the update of libofx. As written before it's now your responsibility in kmymoney to actually apply kmymoney's config updates with appropriate calls of `KConfig::checkUpdate()` for the Windows (and macOS) builds. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 426400] Fix KF5 issues on Windows
https://bugs.kde.org/show_bug.cgi?id=426400 Bug 426400 depends on bug 440177, which changed state. Bug 440177 Summary: no kconf_update5 support on binary factory https://bugs.kde.org/show_bug.cgi?id=440177 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 440177] no kconf_update5 support on binary factory
https://bugs.kde.org/show_bug.cgi?id=440177 Ingo Klöcker changed: What|Removed |Added Latest Commit||https://invent.kde.org/pack ||aging/craft-blueprints-kde/ ||commit/c726dc3f0cdcf6f9a632 ||910b90840c6725e5c6fd Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Ingo Klöcker --- Git commit c726dc3f0cdcf6f9a632910b90840c6725e5c6fd by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 13/09/2022 at 15:50. Pushed by kloecker into branch 'master'. kmymoney: Do not blacklist kconf_update.exe M +1-1extragear/kmymoney/blacklist.txt https://invent.kde.org/packaging/craft-blueprints-kde/commit/c726dc3f0cdcf6f9a632910b90840c6725e5c6fd -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 440177] no kconf_update5 support on binary factory
https://bugs.kde.org/show_bug.cgi?id=440177 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #1 from Ingo Klöcker --- kded is Linux/FreeBSD-only. As written on the page you linked you can start kconf_update manually using `KConfig::checkUpdate()`. Of course, kconf_update.exe still needs to be packaged by craft. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438703] Missing translations for a few common buttons like OK and Cancel (Kate official builds only)
https://bugs.kde.org/show_bug.cgi?id=438703 Ingo Klöcker changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://invent.kde.org/pack |https://invent.kde.org/pack |aging/craft/commit/2df2d522 |aging/craft/commit/1b1a8817 |29f14db93f97011dcacf52368e8 |11b0db1569517f65ddeec7fc153 |ab621 |f31cd Status|ASSIGNED|RESOLVED --- Comment #21 from Ingo Klöcker --- Git commit 1b1a881711b0db1569517f65ddeec7fc153f31cd by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 12/09/2022 at 13:07. Pushed by vonreth into branch 'master'. Fix moving of translations folder into bin folder I misunderstood what is done for the plugins and the qml files. We need to move the translations folder into the bin folder, so that the *.qm files end up in bin/translations. The previous change moved the *.qm files into the bin folder which is wrong. M +7-3bin/Packager/CollectionPackagerBase.py https://invent.kde.org/packaging/craft/commit/1b1a881711b0db1569517f65ddeec7fc153f31cd -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438703] Missing translations for a few common buttons like OK and Cancel (Kate official builds only)
https://bugs.kde.org/show_bug.cgi?id=438703 Ingo Klöcker changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #19 from Ingo Klöcker --- The fix is wrong. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438703] Missing translations for a few common buttons like OK and Cancel (Kate official builds only)
https://bugs.kde.org/show_bug.cgi?id=438703 Ingo Klöcker changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/pack ||aging/craft/commit/2df2d522 ||29f14db93f97011dcacf52368e8 ||ab621 Resolution|--- |FIXED --- Comment #18 from Ingo Klöcker --- Git commit 2df2d52229f14db93f97011dcacf52368e8ab621 by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 09/09/2022 at 15:28. Pushed by kloecker into branch 'master'. On Windows, Qt expects translations files below bin Therefore, on Windows, we move the translations folder below the bin folder (similar as for the plugins and qml folders). M +11 -6bin/Packager/CollectionPackagerBase.py M +2-0bin/options.py https://invent.kde.org/packaging/craft/commit/2df2d52229f14db93f97011dcacf52368e8ab621 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458859] Many icons are invisible or nearly invisible.
https://bugs.kde.org/show_bug.cgi?id=458859 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #3 from Ingo Klöcker --- Hmm, the problem seems to be that the Mint-Y-Dark-Red icon theme lacks many icons that Okular needs. Therefore icons from an icon theme that is optimized for light background seems to be used. If the Mint-Y-Dark-Red icon theme is selected, then it should switch to another dark icon theme as fallback. Not sure whether this is a problem of Mint or in Okular (resp. the underlying libraries) or a gap in the icon theme specification. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438703] Missing translations for a few common buttons like OK and Cancel (Kate official builds only)
https://bugs.kde.org/show_bug.cgi?id=438703 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org --- Comment #15 from Ingo Klöcker --- For what it's worth, the gpg4win installer (which includes Kleopatra) installs all translations in "$INSTDIR\bin\translations". So putting the translations there seems to be the most sensible solution for Windows builds. For the AppImage of Kleopatra the linuxdeploy tool puts the translations into [.../AppDir]/usr/translations. One problem with this was that linuxdeploy only included the translations of Qt libraries that are actually used, but that the qt.qm meta translation file also included .qm files of unused Qt libraries. This made the loading of qt.qm fail, so that all Qt translations were missing even though all needed qt_foo.qm files were there. I have fixed this problem with https://invent.kde.org/frameworks/ki18n/-/commit/98e9a57b677441fd2efa2c2c17993ab7622bb275. I have just tested this with the latest Kate Release AppImage. The Qt translations seems to work now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 440729] KDatePicker does not support 4 digit year entry in its lineedit
https://bugs.kde.org/show_bug.cgi?id=440729 Ingo Klöcker changed: What|Removed |Added CC|ingo.kloec...@matha.rwth-aa |kloec...@kde.org |chen.de | Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.98 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 457058] Keyserver not functioning
https://bugs.kde.org/show_bug.cgi?id=457058 Ingo Klöcker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #5 from Ingo Klöcker --- You have to enable the option auto-key-retrieve for GnuPG. If you do not want to edit the GnuPG configuration files manually, then you can find this setting in the configuration dialog of Kleopatra under GnuPG System->OpenPGP->Options controlling key import and export. The option auto-key-locate controls automatic retrieval of keys needed for encryption. The option "Automatically import keys and certificate" most likely applies to keys attached to email messages, but I haven't really verified this. I'll close the report because this is very likely a setup issue on your side. "auto-key-retrieve" is disabled by default (in the GnuPG backend) because automatic lookup of keys obviously leaks information about your communication partners. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 457058] Keyserver not functioning
https://bugs.kde.org/show_bug.cgi?id=457058 Ingo Klöcker changed: What|Removed |Added Assignee|aheine...@gnupg.org |kdepim-b...@kde.org Version|3.1.21.220403 |unspecified Product|kleopatra |kmail2 CC||kloec...@kde.org Component|general |crypto --- Comment #4 from Ingo Klöcker --- Moving to KMail because the original issue seems to be that the key that a message was signed with is not fetched automatically. This has nothing to do with Kleopatra (except that Kleopatra can be used to configure the GnuPG backend that is used by KMail). -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 458044] Doesn't build with qgpgme 1.18.0
https://bugs.kde.org/show_bug.cgi?id=458044 Ingo Klöcker changed: What|Removed |Added CC||kloec...@kde.org Version|git master |3.1.22.220800 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 458044] Doesn't build with qgpgme 1.18.0
https://bugs.kde.org/show_bug.cgi?id=458044 Ingo Klöcker changed: What|Removed |Added Version Fixed In||22.08.1 Latest Commit||https://invent.kde.org/pim/ ||kleopatra/commit/a3684049dd ||4f0d2d47dcc6605ff31ce753254 ||ef9 --- Comment #2 from Ingo Klöcker --- Git commit a3684049dd4f0d2d47dcc6605ff31ce753254ef9 by Ingo Klöcker, on behalf of Ingo Klöcker. Committed on 19/08/2022 at 11:43. Pushed by kloecker into branch 'release/22.08'. Use ReceiveKeysJob for refreshing OpenPGP keys This refreshes the OpenPGP key from the configured key server. GnuPG-bug-id: 5903 CHANGELOG: Fix building against QGpgME 1.18.0 FIXED-IN: 22.08.1 (cherry picked from commit 87d8b00d4b2286489d5fadc9cfa07f1d721cdfe3) M +6-6src/commands/refreshcertificatecommand.cpp https://invent.kde.org/pim/kleopatra/commit/a3684049dd4f0d2d47dcc6605ff31ce753254ef9 -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 455369] Calendar event notifications lead to segfault if closed by notification button
https://bugs.kde.org/show_bug.cgi?id=455369 Ingo Klöcker changed: What|Removed |Added Version|unspecified |5.20.2 Assignee|claudio.cam...@gmail.com|kdepim-b...@kde.org Product|kalendar|Reminder Daemon Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 454386] Title and description of QCommandLinkButton is painted with wrong (too large) font which causes clipping
https://bugs.kde.org/show_bug.cgi?id=454386 --- Comment #1 from Ingo Klöcker --- Created attachment 149204 --> https://bugs.kde.org/attachment.cgi?id=149204=edit The same dialog painted using plastique style Note the smaller font size used by the plastique style. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 454386] New: Title and description of QCommandLinkButton is painted with wrong (too large) font which causes clipping
https://bugs.kde.org/show_bug.cgi?id=454386 Bug ID: 454386 Summary: Title and description of QCommandLinkButton is painted with wrong (too large) font which causes clipping Product: Breeze Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: kloec...@kde.org CC: noaha...@gmail.com Target Milestone: --- Created attachment 149203 --> https://bugs.kde.org/attachment.cgi?id=149203=edit Example of clipped description with Breeze style QCommandLinkButton (from Qt 5 at least) uses font size 9pt for the title (unless Vista style is used) and the description. In particular, this hardcoded font size is used for calculating the size hints. The Breeze style paints title and description with the button font without adjusting the font size. Depending on the length of the text and the width of the button (i.e. if the description fits in two lines with 9pt, but needs three lines with the normal font size) this causes clipping of the description. Unfortunately, QCommandLinkButton hardcodes the font used for title and description. Moreover, it hides this implementation detail in the cpp file. Breeze either needs to make use of QCommandLinkButton's paintEvent or it needs to copy QCommandLinkButtonPrivate::titleFont() and ::descriptionFont() to use the correct font for painting. Simply using a larger font because it matches the Breeze style is no option unless you find a way to make the calculation of the size hints match the sizes used for painting. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 390002] Message viewer: attached .doc file is shown as encrypted
https://bugs.kde.org/show_bug.cgi?id=390002 Ingo Klöcker changed: What|Removed |Added Latest Commit||https://invent.kde.org/pim/ ||messagelib/commit/3f53b7394 ||ffc75264442a2dd09e845a7a80f ||3dae Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Ingo Klöcker --- Git commit 3f53b7394ffc75264442a2dd09e845a7a80f3dae by Ingo Klöcker, on behalf of Jonathan Marten. Committed on 22/02/2022 at 07:51. Pushed by kloecker into branch 'master'. Fix MS Word attachments being detected as encrypted Caused by EncryptedBodyPartFormatter (via GpgME upstream) being too enthusiastic and detecting the binary data as PGP encrypted. Only enable this formatter for binary body parts explicitly declared as encrypted by their MIME type. See the referenced bug for more information. M +17 -0mimetreeparser/autotests/basicobjecttreeparsertest.cpp M +1-0mimetreeparser/autotests/basicobjecttreeparsertest.h A +61 -0mimetreeparser/autotests/data/binary-attachment-not-pgp.mbox M +2-3 mimetreeparser/autotests/data/openpgp-inline-encrypted-with-attachment.mbox.tree M +27 -10 mimetreeparser/src/bodyformatter/encrypted.cpp M +12 -4mimetreeparser/src/bodyformatter/encrypted.h M +2-2mimetreeparser/src/bodypartformatter.cpp https://invent.kde.org/pim/messagelib/commit/3f53b7394ffc75264442a2dd09e845a7a80f3dae -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450297] Focussed QCommandLinkButton lacks focus indicator when window is opened or regains focus
https://bugs.kde.org/show_bug.cgi?id=450297 --- Comment #3 from Ingo Klöcker --- Created attachment 146761 --> https://bugs.kde.org/attachment.cgi?id=146761=edit After pressing Down to move focus to second radio button -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450297] Focussed QCommandLinkButton lacks focus indicator when window is opened or regains focus
https://bugs.kde.org/show_bug.cgi?id=450297 --- Comment #2 from Ingo Klöcker --- Created attachment 146760 --> https://bugs.kde.org/attachment.cgi?id=146760=edit Kleopatra's New Key Pair wizard after opening with radio buttons -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450297] Focussed QCommandLinkButton lacks focus indicator when window is opened or regains focus
https://bugs.kde.org/show_bug.cgi?id=450297 --- Comment #1 from Ingo Klöcker --- Created attachment 146759 --> https://bugs.kde.org/attachment.cgi?id=146759=edit After pressing Down to move focus to second button -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 450297] New: Focussed QCommandLinkButton lacks focus indicator when window is opened or regains focus
https://bugs.kde.org/show_bug.cgi?id=450297 Bug ID: 450297 Summary: Focussed QCommandLinkButton lacks focus indicator when window is opened or regains focus Product: Breeze Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: plasma-b...@kde.org Reporter: kloec...@kde.org CC: noaha...@gmail.com Target Milestone: --- Created attachment 146758 --> https://bugs.kde.org/attachment.cgi?id=146758=edit Kleopatra's New Key Pair wizard immediately after opening SUMMARY *** Focussed QCommandLinkButton lacks focus indicator when window is opened or regains focus. This can be reproduced with Kleopatra. This problems affects all widgets that use a focus frame. *** STEPS TO REPRODUCE 1. Start Kleopatra. 2. Select File->New Key Pair... OBSERVED RESULT A dialog opens with two large buttons (QCommandLinkButton). The first button does have input focus, but there is no visual focus indicator. If you press Tab or Down, then you will observe that the second button is now marked as having focus. EXPECTED RESULT The first button should indicate that it has focus when the dialog is opened. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20220210 (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'll add some screenshots. I also add screenshots showing a similar issue for radio buttons (I patched Kleopatra to use radio buttons instead of QCommandLinkButtons in order to check whether the problem is specific for QCommandLinkButton or not). -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 434301] Inconsistent theme
https://bugs.kde.org/show_bug.cgi?id=434301 Ingo Klöcker changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #3 from Ingo Klöcker --- Well, obviously your distribution prefers the Gtk-variant (/usr/bin/pinentry-gtk-2) of pinentry instead of the Qt-variant. So, please take this bug to your distribution. That Kleopatra could maybe allow you to change the pinentry variant to use via its configuration dialog is a wish. So feel free to open a separate wish/feature request for this. I will close this bug again because a) I have told you how to fix the problem on your system, b) I have told you that you need to talk to your distribution, if you want to have the proper pinentry for your KDE Plasma desktop by default, c) Kleopatra has no influence on the pinentry provided by your distribution and/or configured for the underlying GnuPG. -- You are receiving this mail because: You are watching all bug changes.
