Package Details: qtalarm 4700238.2.3.1-1

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.000085
First Submitted: 2012-10-14 23:04 (UTC)
Last Updated: 2022-02-28 22:34 (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

CountMurphy commented on 2022-02-28 22:18 (UTC)

@frankspace, that's odd. You did clone the aur repo and not just download the PKGBUILD right? Just installed it chrooted without issue.

frankspace commented on 2022-02-28 14:41 (UTC)

Building this in a chroot fails because it can't find qtalarm.desktop. May I respectfully recommend adding that specifically to the sources array, and then changing the final line in package() to specify srcdir instead of BUILDDIR?

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.

mosgerila commented on 2020-11-03 16:18 (UTC)

PGP keys are wrong!!!____gpg --recv-keys E41FF9C889B141CC ─╯ gpg: keyserver receive failed: General error

CountMurphy commented on 2020-10-13 18:54 (UTC)

@gardotd426, not sure what to tell you. The PKGBUILD works fine both manually and with yay. Something on your system is definitely not running default settings. BUILDDIR should not contain /makepkg/qtalarm. It should only contain PKGBUILD and qtalarm.desktop before running makepkg. I've tested this on three Arch installations, one of which being a fresh build.

That said, I have changed '../qtalarm.desktop' to 'BUIDDIR/qtalarm.desktop.' If you think you know a way to edit the PKGBUILD that will universally work, I'd be open to changing it, but as is I cannot reproduce what you are reporting.

gardotd426 commented on 2020-10-13 09:11 (UTC)

PKGBUILD is broken.


install: cannot stat '../qtalarm.desktop': No such file or directory

I've tried with an AUR helper and by manually cloning and running makepkg.

The issue is that there's no qtalarm.desktop file in BUILDDIR/makepkg/qtalarm. Just makepkg/qtalarm/pkg and makepkg/qtalarm/src. The directory containing the .desktop file gets put in BUILDDIR/qtalarm. I had to prepend makepkg with a BUILDDIR envvar and edit the PKGBUILD to even get it to build.

simona commented on 2020-09-28 09:14 (UTC)

perfect.

CountMurphy commented on 2020-07-17 13:46 (UTC)

You have to add the public key to your keyring. To have gpg automatically add it, run "gpg --recv-keys E41FF9C889B141CC"

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.

CountMurphy commented on 2017-10-09 12:32 (UTC)

tobias.bln, what Desktop environment are you using? That message should only pop up if the DE in question doesn't have a system tray. And just to clarify, if you use this build https://aur.archlinux.org/cgit/aur.git/commit/?h=qtalarm&id=99b50844e969b46b8048505034fe6a04daefee88 it does work?

tobias.bln commented on 2017-10-09 06:20 (UTC)

After the start of qtalarm over the command line I get the error message: "Unsupported Desktop Environment. Exiting" QT and the QT libraries are installed and up-to-date. ==> qtalarm dependencies: - qt5-base (already installed) - qt5-multimedia (already installed) - gst-plugins-base (already installed) - gst-plugins-good (already installed) - make (already installed) [makedepend] - gcc (already installed) [makedepend] This occurs since the last update.

CountMurphy commented on 2017-05-16 16:36 (UTC)

That is odd. I've had pacaur fail on me for other packages in the past that build fine on their own. Just tried installing with pacaur and couldn't reproduce. Glad you got it working!

martynjy commented on 2017-05-16 16:27 (UTC)

@CountMurphy Strange. I tried twice using 'pacaur 4.7.8-1' and got the error. Gave up and installed manually with no problem!

CountMurphy commented on 2017-05-16 12:35 (UTC)

@martynjy, how are you building the package? Are you using an aur helper or doing it manually? If you are building manually and *only* downloading the PKGBUILD, you will get the error you are describing. You will need to either, clone the git url and build, download the snapshot and build, or build using some kind of aur helper.

martynjy commented on 2017-05-16 07:55 (UTC)

==> Entering fakeroot environment... ==> Starting package()... install: cannot stat '../qtalarm.desktop': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... :: failed to build qtalarm package(s)

leledumbo commented on 2017-03-18 08:38 (UTC)

@CountMurphy sorry for the late reply. Confirming that works, thanks.

CountMurphy commented on 2017-02-28 14:41 (UTC)

@Leledumbo run "gpg --recv-keys E41FF9C889B141CC" to have gpg automatically fetch the public key. Or if you are the type of person who enjoys pain, you can import the key manually from https://www.random-hackery.net/wp-content/uploads/2015/02/gpg.asc :)

leledumbo commented on 2017-02-28 08:41 (UTC)

Verifying source file signatures with gpg... QTalarm-1.9.2.tar.gz ... FAILED (unknown public key E41FF9C889B141CC) Looks like the key has gone unknown...

CountMurphy commented on 2014-05-02 00:04 (UTC)

This issue has been resolved

CountMurphy commented on 2014-04-23 15:06 (UTC)

QTalarm currently wont play audio. Bug has been noted here: https://bbs.archlinux.org/viewtopic.php?pid=1408020#p1408020