X Server 1.6.0 Has Been Released

z0phi3l · 2009-02-28 13:06:41

I've pretty much given up hope that ATI will ever properly support Linux, be it from the closed source or open source drivers, too bad I'm stuck with a decent laptop with an ATI card

Themaister · 2009-02-28 13:29:19

dolby wrote:

iBertus wrote:
Any word on what will happen with nvidia users? I seem to remember waiting forever for the binary blob to support the last release of X. Or was that two releases back?
the latest nvidia drivers 180.35 IIRC already support xorg-server 1.6 \o/

Works flawlessly here in 180.29 too.

dolby · 2009-02-28 13:58:48

At last, ctrl+alt+backspace has been dropped.

Oxyd · 2009-02-28 14:56:06

dolby wrote:

At last, ctrl+alt+backspace has been dropped.

It has? I would use it sometimes.

Anyway, there was an Xorg.conf option to disable C-A-Backspace for as long as I can remember.

foutrelis · 2009-02-28 19:33:12

Oxyd wrote:

dolby wrote:
At last, ctrl+alt+backspace has been dropped.
It has? I would use it sometimes.
Anyway, there was an Xorg.conf option to disable C-A-Backspace for as long as I can remember.

Now it's disabled by default with the option to enable it by adding Option "DontZap" "false" to the ServerFlags section in xorg.conf.

CheesyBeef · 2009-03-01 00:56:31

foutrelis wrote:

Oxyd wrote:
dolby wrote:
At last, ctrl+alt+backspace has been dropped.
It has? I would use it sometimes.
Anyway, there was an Xorg.conf option to disable C-A-Backspace for as long as I can remember.
Now it's disabled by default with the option to enable it by adding Option "DontZap" "false" to the ServerFlags section in xorg.conf.

Why?? What else can you do to get out of X without a usable interface (as in frozen desktop). Now you have to go to vc/1 and do what? vc/2 and killall X?

venky80 · 2009-03-01 01:08:52

CheesyBeef wrote:

foutrelis wrote:
Oxyd wrote:
It has? I would use it sometimes.
Anyway, there was an Xorg.conf option to disable C-A-Backspace for as long as I can remember.
Now it's disabled by default with the option to enable it by adding Option "DontZap" "false" to the ServerFlags section in xorg.conf.
Why?? What else can you do to get out of X without a usable interface (as in frozen desktop). Now you have to go to vc/1 and do what? vc/2 and killall X?

Ya I was thinking the same, could someone educate us?

dolby · 2009-03-01 03:39:42

https://fedoraproject.org/wiki/Fedora_1 … s#X_Server

http://lists.freedesktop.org/archives/x … 38786.html

Last edited by dolby (2009-03-01 03:43:01)

venky80 · 2009-03-01 04:07:38

dolby wrote:

https://fedoraproject.org/wiki/Fedora_1 … s#X_Server
http://lists.freedesktop.org/archives/x … 38786.html

still does not answer as to what a person should do if X freezes and zapping is disabled

fijam · 2009-03-01 13:54:48

Well, we got media coverage regarding the problems with ATI drivers: http://www.phoronix.com/scan.php?page=n … &px=NzEwMg

R00KIE · 2009-03-01 15:02:22

venky80 wrote:

dolby wrote:
https://fedoraproject.org/wiki/Fedora_1 … s#X_Server
http://lists.freedesktop.org/archives/x … 38786.html
still does not answer as to what a person should do if X freezes and zapping is disabled

An even better question is how this fits into the new evdev scheme of things as with certain drivers you don't even need a xorg.conf. Do I need a xorg.conf just with that setting to override that? Will that even work? This is another sort of regression even they say its to prevent accidental killing of X. More, someone that doesn't know of this change will probably get stuck after doing X -config xorg.conf.new or whatever (I haven't tested it though) ....

What on earth is going on with certain parts of the linux community as more and more brain-dead solutions are coming out resembling the sort of stuff we see in one very popular OS from a big software company.

moljac024 · 2009-03-01 15:17:23

It does seem rather silly but if you can still enable it yourself then it shouldn't be a problem.
Perhaps it would have been better if they left it on by default and allowed the choice of turning it off, since I imagine fewer people have killed X by accident this way than those that had done so on purpose..

R00KIE · 2009-03-01 15:42:33

Leaving it off by default will be a major problem for us that rely on it to kill X when things go wrong. I don't know if this is true but as it seems the option to turn it off was already there for some time and no one cared enough to use it.
Distros that are targeted for the hapless john doe fresh out of windows user can enable this in the xorg.conf and and everyone will be happy. These users will never look at xorg.conf or even remotely think of changing it so why should we have to deal with one more thing that really isn't a problem? I've it C-A-B once or twice by mistake and I've learned my lesson end of story.
I've changed to linux (first ubuntu and now Arch (and I will not be leaving for the foreseeable future)) because I didn't want to put up with this kind of crap, my computer should do what I tell it to and not what someone else thinks it should do and I like to rely on certain things like C-A-B, thats one of the first things I've learned, how to kill X if it forgets where it's backside is, having to learn it all again because of the whim of some developer and then see it changed to what it was before is not my idea of fun.
Don't get me wrong, I don't mind changes, they are good and necessary but if something isn't broken don't try to fix it, it's enough already when C-A-B doesn't work no matter how many times we press it, having to press it twice or some other far fetched key combination will be a new problem instead of a solution.
Oh and the ideas posted on the mailing list ... they sure are hard to press accidentally alright and also hard to remember.

ConnorBehan · 2009-03-01 22:43:38

Yeah it's pretty dumb. I also thought the magic SysRq key being disabled by default was pretty dumb.

But you don't need the C-A-B combo to get out of X -configure do you? I'm pretty sure you can get X -configure to make an xorg.conf.new file and then you can add Option "DontZap" "false" to it. If you have to use C-A-B to even get X -configure to make you an xorg.conf.new in the first place, that's a much bigger problem.

CheesyBeef · 2009-03-01 22:59:04

moljac024 wrote:

It does seem rather silly but if you can still enable it yourself then it shouldn't be a problem.
Perhaps it would have been better if they left it on by default and allowed the choice of turning it off, since I imagine fewer people have killed X by accident this way than those that had done so on purpose..

Yes, but you better remember to enable it before you go testing out your new system and get stuck with a frozen desktop. But then again, like I said, you could probably go to vc/2 and login to kill X...

I just hope they see some of our gripe and change it back. I think the ctrl-alt-backspace is a good and unique feature for Linux. *sigh*

Nezmer · 2009-03-01 23:57:33

Is it really complicated going to vc/1 and 'C-c'ing ?

Hide · 2009-03-02 13:31:01

It's not about being simple or not, it's about kicking out an obviously necessary and useful option.

b9anders · 2009-03-02 13:42:57

Hide wrote:

It's not about being simple or not, it's about kicking out an obviously necessary and useful option.

It's not kicked, just not enabled by default.

Linux users who find this very necessary will probably be comfortable editing xorg.conf anyway. The noobs who go 'wtf just happened?!?' probably don't even know what xorg.conf is.

Arkane · 2009-03-02 14:12:04

And without even talking about the noobs at all, why are you guys caring so much about a mere config file option?

CheesyBeef · 2009-03-02 18:42:21

Arkane wrote:

And without even talking about the noobs at all, why are you guys caring so much about a mere config file option?

Because, even as a very new user not used to X and xorg.conf, I found ctrl-alt-backspace very useful when I was learning about Linux and frequently messing up my system. It is not that I now will have to go edit xorg.conf when I get X Server 1.6.0, it is that new linux users, joining after 1.6.0, will have to know how to edit xorg.conf for a feature I thought to be so useful.

There really have been many times that I have booted into a crapped out X session and needed to use ctrl-alt-backspace. It was probably the first keyboard shortcut I learned as a Linux user (At first, I didn't even know that ctrl-alt-del worked outside of Windows).

Arkane · 2009-03-02 19:50:09

Okay, i can understand this better. Sorry.

b9anders · 2009-03-03 10:15:51

CheesyBeef wrote:

Arkane wrote:
And without even talking about the noobs at all, why are you guys caring so much about a mere config file option?
Because, even as a very new user not used to X and xorg.conf, I found ctrl-alt-backspace very useful when I was learning about Linux and frequently messing up my system. It is not that I now will have to go edit xorg.conf when I get X Server 1.6.0, it is that new linux users, joining after 1.6.0, will have to know how to edit xorg.conf for a feature I thought to be so useful.
There really have been many times that I have booted into a crapped out X session and needed to use ctrl-alt-backspace. It was probably the first keyboard shortcut I learned as a Linux user (At first, I didn't even know that ctrl-alt-del worked outside of Windows).

You were messing up your system - It is to be expected such users can learn how to edit a simply config then as well. And if not, they had it coming for messing up their system.

Last edited by b9anders (2009-03-03 10:17:22)

jack.mitchell · 2009-03-03 11:27:08

C-A-B has saved me many times from Xorg.conf trial and error runs. However at the end of the day it is just an option to enable. It will just annoy me on each new build the first time I try to do it and have forgotten to enable it.

Jack.

Dieter@be · 2009-03-03 12:16:51

imho leaving Zap enabled is a security risk. if you lock your screen and someone zaps it you remain logged in.

I rather just ssh to my machine from another box, or as mentioned before use sysrq but people can also harm your system with sysrq..

CheesyBeef · 2009-03-03 14:21:04

Using X server 1.6.0, I had my first encounter with ctrl-alt-backspace disabled. I forgot to enable it after I downloaded the new version. My desktop froze when trying to shutdown, so I had to go to vc/1 and use Ctrl-c.

Arch Linux

#26 2009-02-28 13:06:41

Re: X Server 1.6.0 Has Been Released

#27 2009-02-28 13:29:19

Re: X Server 1.6.0 Has Been Released

#28 2009-02-28 13:58:48

Re: X Server 1.6.0 Has Been Released

#29 2009-02-28 14:56:06

Re: X Server 1.6.0 Has Been Released

#30 2009-02-28 19:33:12

Re: X Server 1.6.0 Has Been Released

#31 2009-03-01 00:56:31

Re: X Server 1.6.0 Has Been Released

#32 2009-03-01 01:08:52

Re: X Server 1.6.0 Has Been Released

#33 2009-03-01 03:39:42

Re: X Server 1.6.0 Has Been Released

#34 2009-03-01 04:07:38

Re: X Server 1.6.0 Has Been Released

#35 2009-03-01 13:54:48

Re: X Server 1.6.0 Has Been Released

#36 2009-03-01 15:02:22

Re: X Server 1.6.0 Has Been Released

#37 2009-03-01 15:17:23

Re: X Server 1.6.0 Has Been Released

#38 2009-03-01 15:42:33

Re: X Server 1.6.0 Has Been Released

#39 2009-03-01 22:43:38

Re: X Server 1.6.0 Has Been Released

#40 2009-03-01 22:59:04

Re: X Server 1.6.0 Has Been Released

#41 2009-03-01 23:57:33

Re: X Server 1.6.0 Has Been Released

#42 2009-03-02 13:31:01

Re: X Server 1.6.0 Has Been Released

#43 2009-03-02 13:42:57

Re: X Server 1.6.0 Has Been Released

#44 2009-03-02 14:12:04

Re: X Server 1.6.0 Has Been Released

#45 2009-03-02 18:42:21

Re: X Server 1.6.0 Has Been Released

#46 2009-03-02 19:50:09

Re: X Server 1.6.0 Has Been Released

#47 2009-03-03 10:15:51

Re: X Server 1.6.0 Has Been Released

#48 2009-03-03 11:27:08

Re: X Server 1.6.0 Has Been Released

#49 2009-03-03 12:16:51

Re: X Server 1.6.0 Has Been Released

#50 2009-03-03 14:21:04

Re: X Server 1.6.0 Has Been Released

Board footer