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

Autodetection fails if "default" profile is deleted #411

Open
rolandu opened this issue Feb 18, 2025 · 0 comments
Open

Autodetection fails if "default" profile is deleted #411

rolandu opened this issue Feb 18, 2025 · 0 comments

Comments

@rolandu
Copy link

rolandu commented Feb 18, 2025

Here is what I think happened - and I don't want to try to replicate the behavior:

  • started using a new laptop running Linux Mint Cinnamon 22.0
  • as it's a laptop, it was frequently connected to different screen setups at home and at work
  • initially had occasional problems with screen setups not being detected, so I started to use the autorandr console (not sure if autorandr came installed by default in Mint or whether I installed it
  • my initial setup was (and I think this was the mistake): deleted the profile "default" and created new ones for "laptop", "work" and "home"
  • had a terrible experience for many months, screens were almost never properly detected, after each connect or disconnect to a screen I ended up with an unusable minimal resolution and had to manually call autorandr <profile> to set my profile, could not find any solution to this
  • then I discovered that my startup items contains the item /usr/bin/autorandr -c --default default
  • I got an idea: I detached the screen, deleted my "laptop" profile, set it the resolution manually and saved it as "default"; so now I have "default", "work" and "home"
  • much better experience now - almost all the time, the correct profile is loaded

I don't fully understand what the startup item does or whether it keeps autorandr running in the background. I am also not sure what the "default" item does. However it seems to me that not having a default profile messes with autorandr's method of detecting the current setup.

Could this be a bug?

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

1 participant