Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cosmic-greeter-daemon prevents cosmic-greeter from starting #36

Open
Quackdoc opened this issue May 5, 2024 · 3 comments
Open

cosmic-greeter-daemon prevents cosmic-greeter from starting #36

Quackdoc opened this issue May 5, 2024 · 3 comments

Comments

@Quackdoc
Copy link

Quackdoc commented May 5, 2024

I only updated recently so I didn't realize I had didn't have cosmic-greeter-daemon running. But with the latest commit it implicitly enabled it.

I did downgrade/remove the want section, try it again, and it worked, manually enabled cosmic-greeter-daemon and it indeed just left me with a gray screen. Once cosmic-greeter-daemon breaks cosmic, a downgrade and restart is needed simply restarting cosmic-greeter is not good enough.

Logs were made using journalctl --boot -g cosmic > logs/cosmic-greeter-good.txt

good log:
cosmic-greeter-good.txt

bad log:
cosmic-greeter-bad.txt

@colemickens
Copy link

colemickens commented May 5, 2024

I wonder if this is the behavior I've been seeing, it sounds very similar. I did notice this in the logs:
May 02 13:50:11 zeph systemd[1]: cosmic-greeter-daemon.service: Consumed 1.455s CPU time, no IP traffic.
May 02 13:50:11 zeph systemd[1]: Stopped cosmic-greeter-daemon.service.
May 02 13:50:11 zeph systemd[1]: cosmic-greeter-daemon.service: Deactivated successfully.
May 02 13:50:11 zeph systemd[1]: Stopping cosmic-greeter-daemon.service...
May 02 13:49:55 zeph cosmic-greeter-daemon[1638]: [2024-05-02T18:49:55Z ERROR cosmic_greeter_daemon] failed to load cosmic-theme config: [RonSpanned(SpannedError { code: MissingStructField { field: "small_widget", outer: Some("Container") }, position: Position { line: 1, col: 1013 } }), RonSpanned(SpannedError { code: MissingStructField { field: "small_widget", outer: Some("Container") }, position: Position { line: 1, col: 1004 } }), RonSpanned(SpannedError { code: MissingStructField { field: "small_widget", outer: Some("Container") }, position: Position { line: 1, col: 1011 } })]

but I'm not sure if that's related or fatal, since the service stays in a running state.

I see these log lines even in a working vm configuration. Minimizing my comment.

@ryanabx
Copy link
Contributor

ryanabx commented May 5, 2024

When did this start occurring?

@Quackdoc
Copy link
Author

Quackdoc commented May 6, 2024

I went back and tested the commit it was added in and it still didn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants