Package Details: qtalarm 1:2.5.1-3

Git Clone URL: https://aur.archlinux.org/qtalarm.git (read-only, click to copy)
Package Base: qtalarm
Description: Cross-platform Alarm Clock written with QT5
Upstream URL: https://random-hackery.net/page/qtalarm/
Licenses: GPL3
Submitter: CountMurphy
Maintainer: CountMurphy
Last Packager: CountMurphy
Votes: 14
Popularity: 0.000006
First Submitted: 2012-10-14 23:04 (UTC)
Last Updated: 2024-01-31 16:57 (UTC)

Pinned Comments

CountMurphy commented on 2020-11-03 16:30 (UTC) (edited on 2020-11-03 17:16 (UTC) by CountMurphy)

@mosgerila. This is odd. I'm getting the same error, though the keys do exist on the MIT keyserver. I'll work on figuring out whats wrong, but in the mean time you can import the key manually yourself. You can find a copy at https://random-hackery.net/data/gpg.asc

EDIT: Ok, I got it working. According to https://wiki.archlinux.org/index.php/GnuPG#Use_a_keyserver (the tip section),

hkp-cacert /usr/share/gnupg/sks-keyservers.netCA.pem

must be added to your ~/.gnupg/dirmngr.conf file, and then kill the old dirmngr process. After that gpg --recv-keys E41FF9C889B141CC works.

Why the hell arch doesn't have this config by default I don't know. But I can confirm this fixed it for me.

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

GregTheHun commented on 2020-07-17 13:15 (UTC)

I think I'm having the same problem as the last commenter, it seems the PGP keys are wrong.

simona commented on 2019-08-21 17:02 (UTC)

==> Validazione delle firme dei sorgenti con gpg in corso... QTalarm-2.0.1.tar.gz ... NON RIUSCITO (chiave pubblica sconosciuta E41FF9C889B141CC) ==> ERRORE: Una o più firme PGP non possono essere verificate!

CountMurphy commented on 2017-10-12 14:27 (UTC)

All reported issues should be fixed now.

CountMurphy commented on 2017-10-11 19:02 (UTC)

well damn, never occurred to me to hit enter in that field (time is accepted currently once another field gets cursor focus). I will definitely add that to the bug list. Thanks again!

tobias.bln commented on 2017-10-11 18:44 (UTC)

When I wanted to set an alarm time and confirmed with return, the program crashed with Segmentation fault (core dumped).

CountMurphy commented on 2017-10-11 18:26 (UTC)

The calendar bug I am familiar with (crashed when clicking on the calendar when there is no alarm selected). That one popped up with the 2.0 release, was going to patch it, and then forgot about it. The setting time one is new to me. Will look into it. In the mean time at least you have something that runs (mostly) until I get the official fix out this week. Thanks for your help in debugging.

tobias.bln commented on 2017-10-11 18:17 (UTC)

Hello CountMurphy, qtalarm still started. Unfortunately, it crashes occasionally. Times it was a click in the calendar, times it was when setting the alarm time. Segmentation fault (core dumped). And sometimes it worked fine.

CountMurphy commented on 2017-10-10 02:59 (UTC)

tobias.bln, I think I have a fix ready. Would you be willing to run an experimental branch to test it? https://github.com/CountMurphy/QTalarm/tree/gnome If not, no problem. I'll spend a few days testing it further myself before releasing it.

CountMurphy commented on 2017-10-09 17:55 (UTC)

Thanks for the information. I'll try to have this patched within a few days. I've also created a bug in github for the project (https://github.com/CountMurphy/QTalarm/issues/5). If I come across more information I'll post it there.

tobias.bln commented on 2017-10-09 16:50 (UTC) (edited on 2017-10-11 19:32 (UTC) by tobias.bln)

Hello CountMurphy, I use gnome (with wayland) as desktop environment. The version you posted also says: "Unsupported Desktop Environment. Exiting". Recently, qtalarm still worked and I used it.

« First ‹ Previous 1 2 3 4 5 Next › Last »