Re: Digital clock widget and 24-hour format

Mar 20, 2022, 18:59 by inkbottle...@gmail.com: > > I've fixed that issue on my box about 6 month ago, I can't remember how I did > that exactly. The core of it however was that the `locales` were defined in > several places, like 2 or 3, and that one of them was inconsistent with the > others.

Re: Digital clock wizard and 24-hour format

Mar 20, 2022, 17:29 by s...@platonix.com: > FWIW, my digital clock's "Time display" is set to "Use Region > Defaults", not "24 hours", and I do get a 24 hour clock (which is what > my region defines). > Tried it, doesn't work for me, still shows time in the AM/PM format.

Re: Digital clock wizard and 24-hour format

Mar 20, 2022, 16:52 by ago...@gmail.com: > and if you try with a different Region? > I tried setting "osa_US" -- which also uses 24-hour time format -- as the time format in KDE but "Copy to Clipboard" still showed time in the AM/PM format. Regards,

Bug#1008033: please make a new upload leveraging recent Poppler

Source: okular Version: 4:21.12.3-1 Severity: wishlist Okular and the version of Poppler now in unstable both support digital signing of PDFs, which is awesome. However, Okular checks at build time whether Poppler provides the functions necessary for PDF signing. It is sufficient to make a new

Re: Mail-Server response: A000002 NO Authentication failed

Dear hefee, I thank you very much for being patient. > logging is done under the logging tab. (the next tab). YES, I have wachted the LOG of akonadiconsole but too cannot find any characteristic message in there. So today a installed in an VM -Linux and ONLY set up the only one mail-account

Re: Digital clock wizard and 24-hour format

On Sunday, 20 March 2022 18:29:54 CET Shai Berger wrote: > FWIW, my digital clock's "Time display" is set to "Use Region > Defaults", not "24 hours", and I do get a 24 hour clock (which is what > my region defines). I've fixed that issue on my box about 6 month ago, I can't remember how I did

Re: Digital clock wizard and 24-hour format

FWIW, my digital clock's "Time display" is set to "Use Region Defaults", not "24 hours", and I do get a 24 hour clock (which is what my region defines).

Re: Digital clock wizard and 24-hour format

Il 20/03/22 13:39, local10 ha scritto: Hi, Am struggling to get the KDE Digital clock wizard to use the 24-hour format when using the "Copy to clipboard" menu option. See [1] and [2] for my settings. The Digital Clock wizard uses 24-hour format when it shows the time in the panel but when

Digital clock wizard and 24-hour format

Hi, Am struggling to get the KDE Digital clock wizard to use the 24-hour format when using the "Copy to clipboard" menu option. See [1] and [2] for my settings. The Digital Clock wizard uses 24-hour format when it shows the time in the panel but when using its "Copy to clipboard" option it

calligra_3.2.1+dfsg-5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Mar 2022 11:47:04 +0100 Source: calligra Architecture: source Version: 1:3.2.1+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 1007891

Processing of calligra_3.2.1+dfsg-5_source.changes

calligra_3.2.1+dfsg-5_source.changes uploaded successfully to localhost along with the files: calligra_3.2.1+dfsg-5.dsc calligra_3.2.1+dfsg-5.debian.tar.xz calligra_3.2.1+dfsg-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#1007891: marked as done (calligra FTBFS with poppler 22.02)

Your message dated Sun, 20 Mar 2022 11:03:50 + with message-id and subject line Bug#1007891: fixed in calligra 1:3.2.1+dfsg-5 has caused the Debian Bug report #1007891, regarding calligra FTBFS with poppler 22.02 to be marked as done. This means that you claim that the problem has been dealt

Processed: tagging 1007891

Processing commands for cont...@bugs.debian.org: > tags 1007891 + pending Bug #1007891 [src:calligra] calligra FTBFS with poppler 22.02 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1007891:

Processed: qtpaths is broken for cross compilation

Processing control commands: > affects -1 + src:qt5ct Bug #1007994 [qttools5-dev-tools] qtpaths is broken for cross compilation Added indication that 1007994 affects src:qt5ct -- 1007994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007994 Debian Bug Tracking System Contact

Bug#1007994: qtpaths is broken for cross compilation

Package: qttools5-dev-tools Version: 5.15.2-5+b1 Severity: important Justification: multiarch violation User: debian-cr...@lists.debian.org Usertags: ftcbfs Control: affects -1 + src:qt5ct Dear qt maintainers, we have a bigger problem about qtpaths. I haven't checked, but I think it also affects