-
Notifications
You must be signed in to change notification settings - Fork 19
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
ReGreet fails to start #95
Comments
Similar issue, I'll note that the demo works if I run it under my local user, but not under root or greeter - with the same issue as OP. Similarly also on arch. |
Sadly, I think this is due to the super old version of the gtk4 crate. ReGreet didn't update on arch (last update 2024-06-28) and I didn't change the config, so that's likely where the issue lies. Will probably have to switch to another greeter since it doesn't seem like this will be fixed anytime soon. |
There is a PR with updated dependencies, you could try that and see if the issue is fixed - would be more of a reason to merge it. You have to appply this patch to get it to run tho: cmdline_fix.patch: diff --git a/src/main.rs b/src/main.rs
index f714232..71df388 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -42,11 +42,11 @@ enum LogLevel {
#[command(author, version, about)]
struct Args {
/// The path to the log file
- #[arg(short, long, value_name = "PATH", default_value = LOG_PATH)]
+ #[arg(short = 'l', long, value_name = "PATH", default_value = LOG_PATH)]
logs: PathBuf,
/// The verbosity level of the logs
- #[arg(short, long, value_name = "LEVEL", default_value = "info")]
+ #[arg(short = 'L', long, value_name = "LEVEL", default_value = "info")]
log_level: LogLevel,
/// Output all logs to stdout
@@ -71,7 +71,7 @@ fn main() {
// Keep the guard alive till the end of the function, since logging depends on this.
let _guard = init_logging(&args.logs, &args.log_level, args.verbose);
- let app = relm4::RelmApp::new(APP_ID);
+ let app = relm4::RelmApp::new(APP_ID).with_args(vec![]);
app.run_async::<Greeter>(GreeterInit {
config_path: args.config,
css_path: args.style,
Although, I dont know if newer GTK dep. would necessarily fix the issue. |
So I tried the new patch, which didn't work, but I did find a solution. The TLDR is use |
Very interesting. I didn't get a chance to try the patch but sounds like that's okay. This should be significantly less work so I might have time this evening, else over the weekend. |
I've been running regreet for just about a year with a mostly static config file. The latest release appears to have broken on both my systems (I'm using sway to run regreet, willing to try cage). I'm fairly sure sway isn't the issue, as the sway config works if I remove regreet. There's nothing in the logs, but if I try and run the demo, I get:
Running ArchLinux, and I get the same failure with both the version in extra and the git version on AUR. I've tried to debug this issue, but there's nothing in the logs.
Configs:
config.toml
:sway-config
:regreet.toml
:The text was updated successfully, but these errors were encountered: