Xorg-server 2:1.18.3-1ubuntu2.2 (For technical support please see com/support) Thanks for your time and efforts xinit /home/mikr/ bin/WoWrun64 - :1 -brīuild Operating System: Linux 3.13.0-86-generic x86_64 UbuntuĬurrent Operating System: Linux scrat 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27: x86_64 Although my knowledge of X is very limited, I'd love to contribute with some testing as far as I can go. The program I want to run in its own Xserver is a game, so all the systemd stuff in the workaround is not that relevant to me. Perhaps someone can give suggestions to me based on the posted workaround. I have looked at the workaround for koda posted above, but I am unable to extract the bits that may make it help in my case. config I have tried to replacedīut both attempts had no visible consequences. I am affected by the same bug, although the X error message is slightly different ("parse_ vt_settings: Cannot open /dev/tty0" instead of "xf86OpenConsole: ". Input AT Translated Set 2 keyboard KEYBOARD, id 10 xserver- xorg-video- nouveau: xserver- xorg-video- nouveau 1:1.0.12-1build2 xserver- xorg-video- intel: xserver- xorg-video- intel 2:2.99. xserver- xorg-video- ati: xserver- xorg-video- ati 1:7.6.1-1ubuntu2 xserver- xorg-input- evdev: xserver- xorg-input- evdev 1:2.10.1-1ubuntu2 xserver- xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 libgl1- mesa-dri- experimental: libgl1- mesa-dri- experimental N/A M.:ct3: cvrToBeFilledBy O.E.M.:ĭmi.product. E.M.:rvnASRock: rnH97MPro4: rvr:cvnToBeFill edByO.E. version: To Be Filled By O.E.M.ĭmi.modalias: dmi:bvnAmerican MegatrendsInc. asset.tag: To Be Filled By O.E.M.ĭmi.chassis.vendor: To Be Filled By O.E.M.ĭmi.chassis. UpgradeStatus: Upgraded to xenial on (0 days ago)ĭmi.bios.vendor: American Megatrends Inc.ĭmi.chassis. InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) InstallationDate: Installed on (467 days ago) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 ) ProcVersionSign ature: Ubuntu 4.4.0-15.31-generic 4.4.6ĬompizPlugins: No value set for `/apps/ compiz- 1/general/ screen0/ options/ active_ plugins'ĭistUpgraded: 09:16:37,728 DEBUG enabling apt cron jobĭkmsStatus: oem-audio- hda-daily, 0.201412181801~ ubuntu14. I have tried numerous workarounds including reinstalling xorg, removing all x-related files in my profile, and creating a new user. Xinit: unable to connect to X server: Connection refused (EE) Please also check the log file at "/home/ arch/.local/ share/xorg/ Xorg.0. Please consult the The X.Org Foundation support (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied) (=) Using system config directory "/usr/share/ X11/xorg. (=) Log file: "/home/ arch/.local/ share/xorg/ Xorg.0. (WW) warning, (EE) error, (NI) not implemented, (?) unknown. (++) from command line, (!!) notice, (II) informational, Markers: (-) probed, (**) from config file, (=) default setting, To make sure that you have the latest version. Xorg-server 2:1.18.1-1ubuntu4 (For technical support please see com/support)īefore reporting problems, check wiki.x. Xinit /usr/bin/kodi -standalone -nocursor :0īuild Operating System: Linux 3.13.0-79-generic x86_64 UbuntuĬurrent Operating System: Linux hostname 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:08: x86_64 com/questions/ 749370/ ubuntu- 16-04-xf86openc onsole- cannot- open-virtual- console- 2?newreg= ba376d7a182d446 08ed4675346b1ed 74Īn example is when attempting to launch kodi, which worked prior to the upgrade: I have seen another person with this issue as well here: There seems to be some sort of permission issue. When attempting to run xinit or startx after upgrading from 14.04 to 16.04 it will not work. For many this makes running X unprivileged unworkable.
The only exception appears to be if the vt you attempt to launch X onto is already logged into by that user. If as an unprivileged user you launch xinit (or startx) to any vt (EVEN IF UNALLOCATED BY SYSTEMD) it will fail as described below.
0 kommentar(er)
