Wayland's Weston Gets Output Configuration File

[Teho]

I don't care if KMS remembers the resolution or not after restart, I don't want to be editing a config file like a fucking idiot for something basic as setting the resolution.

Did you fucking read the comment you were responding to? By default it does everything for you but if you need to you can change it yourself. This can only be better than situation where you are stuck with KMS even when the results are not ideal.

[asdx]

E.g. KMS knows how to change resolution, but needs to be told what resolution the user wants to use. This is just one way of telling it, one that persists over a reboot. Dynamic (xrandr-style) resolution changes will of course also be supported.

What makes you think that as a user I care about that? I FUCKING DONT.

I bet some grandma using Ubuntu probably doesn't also.

Information about resolution or whatever is the job for EDID and KMS to handle: http://en.wikipedia.org/wiki/EDID

I don't want to bother to edit a fucking text file.

WTF, it seems like Wayland hasn't learned anything from X.

[asdx]

Did you fucking read the comment you were responding to? By default it does everything for you but if you need to you can change it yourself. This can only be better than situation where you are stuck with KMS even when the results are not ideal.

Bullshit.

Go fix what is broken and stop giving me shitty workarounds like this.

Fucking idiots.

[ChrisXY]

Information about resolution or whatever is the job for EDID and KMS to handle: http://en.wikipedia.org/wiki/EDID

Well, I have an old KVM switch that in fact does not relay that information correctly. I also still have a very old monitor right in my house that apparently doesn't advertise hsync/vsync correctly.

It's not in there yet but in the future this could be a good place to set in what directions the screens should be rotated by default.

If you have two or more screens, how exactly does weston decide how to place them per default? Could go in this config file.

I don't want to bother to edit a fucking text file.

Then write a fucking gui. I could probably do it in less than 10 minutes with a bit of pyqt.

WTF, it seems like Wayland hasn't learned anything from X.

How do I set in X that when my external screen is connected that the external screen should be left from LVDS and that the external screen should be the primary screen? X doesn't do that without a config file. At the moment KDE does it for me.


Lastly I don't see why weston should not use that or a similar file to automatically save whatever you change in your current session so you never even have to touch it.

[asdx]

Then write a fucking gui. I could probably do it in less than 10 minutes with a bit of pyqt.

Thanks but no thanks. I won't bother with any of that bullshit.

I will just say this loud and clearly.

If I have to open a terminal or my editor to configure something as basic as the resolution, then wayland is an uber failure.

If KMS can't set my resolution on the fly then it's a failure too.

It's incredibly annoying that something as basic as this still can't "just work" without user intervention. WTF?

WHY DO WE STILL NEED TO SET THE FUCKING RESOLUTION MANUALLY?!?!

[daniels]

That's my question, why are Wayland developers reintroducing a feature (configuration file) when Xorg devs tried to get rid of it?

Wrong.

What we did in X.Org was make the configuration file optional. The problem with xorg.conf wasn't that it existed, but instead that you could not start up a server without it. We spent a lot of time making the server do the right thing by default and making sure that most people would never have to touch it. But we retained the option for people who had different needs from the default heuristics.

You should also probably look into therapy if something as basic as a new entry in weston.ini makes you this angry.

[Darxus]

<Darxus> This isn't a feature most people are expected to use, right? For most people this stuff will just be automatic, like it is for X?
<krh> Darxus: right

^ Creator of Wayland.

[Jonno]

WHY DO WE STILL NEED TO SET THE FUCKING RESOLUTION MANUALLY?!?!

YOU DON'T!!!

Wayland uses KMS which defaults to the auto-detected native resolution, which will be just fine for ~99% of use-cases (including the Ubuntu-using grandmother you mentioned). This is for the ~1% of users where the default won't be enough...

[asdx]

Wrong.

What we did in X.Org was make the configuration file optional. The problem with xorg.conf wasn't that it existed, but instead that you could not start up a server without it. We spent a lot of time making the server do the right thing by default and making sure that most people would never have to touch it. But we retained the option for people who had different needs from the default heuristics.

You should also probably look into therapy if something as basic as a new entry in weston.ini makes you this angry.

@daniels:

I apologize for expressing myself that way, but I have this huge PTSD that comes from a few years ago (before we had KMS) when X would require a xorg.conf to even start (if you were lucky), and I would have to help people over SSH with their xorg.conf. It was terrible. This probably was before (or after) the XFree86/Xorg fork.

I simply don't want that to happen to Wayland/Weston and I'm worried about similar experiences happening again.

Why can't we have things just work?

You are probably right about therapy, I need it *sigh*.

[asdx]

YOU DON'T!!!

Wayland uses KMS which defaults to the auto-detected native resolution, which will be just fine for ~99% of use-cases (including the Ubuntu-using grandmother you mentioned). This is for the ~1% of users where the default won't be enough...

Ok sorry.

I'm really sorry for expressing myself that way above. I retract from what I've said (the insults).

/me goes to seek therapy.