Package Details: cosmic-greeter-git 1.8.0.r2.g06a762c-1

Git Clone URL: https://aur.archlinux.org/cosmic-greeter-git.git (read-only, click to copy)
Package Base: cosmic-greeter-git
Description: COSMIC greeter for greetd
Upstream URL: https://github.com/pop-os/cosmic-greeter
Licenses: GPL-3.0-only
Conflicts: cosmic-greeter
Provides: cosmic-greeter
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 5
Popularity: 0.003788
First Submitted: 2024-02-21 00:36 (UTC)
Last Updated: 2026-09-14 15:33 (UTC)

Latest Comments

1 2 3 4 Next › Last »

ragusa87 commented on 2026-08-01 08:06 (UTC) (edited on 2026-08-01 08:11 (UTC) by ragusa87)

Thanks @yochananmarqos, The existing MR is close, though it needs a couple of fixes. Mainly, /etc/pam.d/cosmic-greeter ends up as a directory because of a stray -t in the install command, but that's not the only thing to fix. To be continued directly on GitLab once my account is approved (I requested approval in April and just re-sent the request).

yochananmarqos commented on 2026-07-31 15:30 (UTC)

@ragusa87: Peter is doing the same thing with the cosmic-greeter package. I suggest creating an issue--or better yet, an MR with your proposed changes.

ragusa87 commented on 2026-07-31 13:27 (UTC) (edited on 2026-07-31 13:32 (UTC) by ragusa87)

This package reverts commit ef1253aa2393666bb2a0b0132b722f51ec7ebbf3, and I think there's an opportunity to improve on that approach.

cosmic-greeter hard-codes the PAM context to cosmic-greeter for the lock screen, and expects a different context (login) at login time. Reusing the same PAM context for both means fingerprint unlock can't be enabled for the lock screen alone, which is a useful configuration to support.

Rather than reverting the commit, it would make sense to ship a /etc/pam.d/cosmic-greeter file. That avoids the crash while keeping the two PAM contexts distinct. The file will be used for the lock screen only, and the login will rely on /etc/pam.d/login (or whatever is configured in /etc/greetd/cosmic-greeter.toml)

sdmcclain commented on 2025-01-03 01:05 (UTC)

@baba99j, I had the same issue. These settings in my ~/.gitconfig worked for me.

[filter "lfs"]
    clean = git-lfs clean -- %f
    smudge = git-lfs smudge --skip -- %f
    process = git-lfs filter-process --skip
    required = true

I find it a little odd that I needed to update my .gitconfig to get the build to work (whereas I haven't had to do this for any other AUR packages), but don't know enough to say whether this package could be updated to be more robust to different git configs.

yochananmarqos commented on 2024-11-28 21:58 (UTC)

@baba99j: Check your ~/.gitconfig. Not a packaging issue.

baba99j commented on 2024-11-28 14:50 (UTC)

Hi there, git-lfs constantly failed to download res/background.jpg:

Error downloading object: res/background.jpg (7500f70): Smudge error: Error downloading res/background.jpg (7500f702f0488d4a8df2c5abeb7ca9107a7ca7998e0441727cbaf79465b02388): error transferring "7500f702f0488d4a8df2c5abeb7ca9107a7ca7998e0441727cbaf79465b02388": [0] remote missing object 7500f702f0488d4a8df2c5abeb7ca9107a7ca7998e0441727cbaf79465b02388

any solution?

yochananmarqos commented on 2024-09-14 00:47 (UTC) (edited on 2024-09-14 00:49 (UTC) by yochananmarqos)

@Riggs9715 Whoops, typo. I'll fix it here in a few minutes.

Riggs9715 commented on 2024-09-14 00:41 (UTC) (edited on 2024-09-14 00:42 (UTC) by Riggs9715)

trying to check if its on my end now, but thats not building any more.

ls: cannot access '/home/riggs/.cache/paru/clone/cosmic-greeter-git/pkg/cosmic-greeter-git/etc/pam.d/cosmic-greeter': No such file or directory 4 /etc/pam.d/login ==> ERROR: A failure occurred in package(). Aborting...

EDIT: just checked pkg build. im assuming the ls should be ln

yochananmarqos commented on 2024-09-13 23:53 (UTC) (edited on 2024-09-13 23:55 (UTC) by yochananmarqos)

Please see the latest commit. I've symlinked the PAM login config instead of shipping upstream greeter config for now.

EDIT: Well, the commit before last.

Riggs9715 commented on 2024-09-13 23:45 (UTC) (edited on 2024-09-13 23:46 (UTC) by Riggs9715)

as well as lockscreen issues, it wont run on boot. the problem appears to be the PAM file wants to include other files which arch doesnt have. relevant logs below. it is looking for common-auth common account common-session and common-password

Sep 13 23:17:12 arch-laptop greetd[605]: PAM (cosmic-greeter) illegal module type: @include

Sep 13 23:17:12 arch-laptop greetd[605]: PAM (cosmic-greeter) no module name supplied

repeated 4 times in journal. presumaly one for each @include line

1 2 3 4 Next › Last »