-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Desktop: Restart without UI acceleration when it fails on Linux #3668
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
Conversation
375cda1 to
b3dc155
Compare
| let (cef_view_info_sender, cef_view_info_receiver) = std::sync::mpsc::channel(); | ||
|
|
||
| if cli.disable_ui_acceleration { | ||
| println!("UI acceleration is disabled"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be an eprintln ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
more of an info that an error, so in my opinion no.
but this will only stay for a couple of weeks anyways (until rc4).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The question is more if it should be included if I pipe the output of graphite to a file, and I'd think it should probably not. E.g. the dbg! macro also outputs to stderr, and I would argue that is similar in nature
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then we should also change the Available GPU lines?
I would merge this and we can decide later for all similar cases, currently most stuff ends up in stdout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, we should, from man stderr
Under normal circumstances every UNIX program has three streams opened for it when
it starts up, one for input, one for output, and one for printing diagnostic or
error messages.
b3dc155 to
062c6d5
Compare
Part of #3667