Skip to content

Conversation

@timon-schelling
Copy link
Member

@timon-schelling timon-schelling commented Jan 21, 2026

Part of #3667

@timon-schelling timon-schelling force-pushed the desktop-linux-ui-fallback-restart branch from 375cda1 to b3dc155 Compare January 22, 2026 13:33
@Keavon Keavon changed the title Desktop: Restart without UI Acceleration when it fails on Linux Desktop: Restart without UI acceleration when it fails on Linux Jan 26, 2026
let (cef_view_info_sender, cef_view_info_receiver) = std::sync::mpsc::channel();

if cli.disable_ui_acceleration {
println!("UI acceleration is disabled");
Copy link
Member

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 ?

Copy link
Member Author

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).

Copy link
Member

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

Copy link
Member Author

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.

Copy link
Member

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.

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

Successfully merging this pull request may close these issues.

4 participants