[arch-announce] xorg-server 1.16 is now available

[ichase]

Laurent Carlier wrote:

 

The new version comes with the following changes:

 

* X is now rootless with the help of systemd-logind, this also means that it

must be launched from the same virtual terminal as was used to log in,

redirecting stderr also breaks rootless login. The old root execution behavior

can be restored through the Xorg.wrap config file (man xorg.wrap). Please note

that launching X through a login-manager (gdm, kdm, ...) doesn't yet provide

rootless access.

 

* The default configuration files are now in /usr/share/X11/xorg.conf.d, all

host configurations are still taking place in /etc/X11/xorg.conf.d/ directory.

Please note that files 10-evdev.conf and 10-quirks.conf in /etc/X11/xorg.conf.d

could be renamed with .pacsave suffix, which could break your configuration,

then just rename them and remove the .pacsave suffix.

 

* Better glamor accelerated rendering, deprecating `glamor-egl` package.

 

* A new package `xorg-server-xwayland` that allows running X applications

inside a wayland session.

 

* The `xf86-video-intel` package doesn't provide dri3 support anymore because

of multiple rendering bugs.

 

URL: https://www.archlinux.org/news/xorg-server-116-is-now-available/

[securitybreach]

Dang, you beat me.... Deleting my post.

 

BTW I have been running the new version for about a week on my machines since I run the testing branch on them. I have not had any issues with my netbook running the xf86-video-intel driver

[saturnian]

This one seemed a bit scary to me. So, I decided to try bringing in the updates in my Bridge installation first, to see what would happen. Everything looks fine, though. I'll try it in Arch tomorrow.

[ichase]

Ran the update, and at first everything seemed to work fine as I am also using the xf86-video-intel driver. But when I opened up vitual box, all I got was a white box and an error stating something along the lines that it could not paint the screen. Will have to post the exact errors when I get back to the house. Now this is what is strange. I have not taken the time to troubleshoot this, but when I installed the SSD drive on the laptop and moved all of my VMs to an external drive except for one (XP) I could only run the VMs as root. The XP VM which is installed on the SSD drive (because it's only a 20 GB VM) I can run that as user. Plus, when I run VBox as user, the VBox interface screen comes up. Not sure if this has anything to do with the new xorg upgrade or not, but I find it rather strange it did not start happening until AFTER ran the updates. I'm pretty sure the "root" issue is because the external HDD does not have rw permissions for "user"

 

Edit, this is a portion of the error I am now getting when trying to open VBox from terminal as root

Qt WARNING: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
 Major opcode: 62 (X_CopyArea)
 Resource id:  0x240000e
Qt WARNING: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
 Major opcode: 62 (X_CopyArea)
 Resource id:  0x240000e
Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile
Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile
Qt WARNING: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
 Major opcode: 62 (X_CopyArea)
 Resource id:  0x240000e
Qt WARNING: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
 Major opcode: 62 (X_CopyArea)
 Resource id:  0x240000e
Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile
Qt WARNING: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
 Major opcode: 62 (X_CopyArea)
 Resource id:  0x240000e
Qt WARNING: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
 Major opcode: 62 (X_CopyArea)
 Resource id:  0x240000e
Qt WARNING: X Error: BadDrawable (invalid Pixmap or Window parameter) 9
 Major opcode: 62 (X_CopyArea)
 Resource id:  0x240000e

 

Not sure what is up

Edited July 30, 2014 by ichase