Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-20 Thread Brian
On Mon 19 Jun 2017 at 14:43:08 -0400, Felix Miata wrote: > Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400): > > > On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote: > . > >> I have a dozen machines with Stretch installed, most with Jessie and/or > >> Sid as > >> well. Only

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-19 Thread Felix Miata
Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400): > On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote: . >> I have a dozen machines with Stretch installed, most with Jessie and/or Sid >> as >> well. Only Stretch on host big41 produces the subject problem. . > According to a

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-19 Thread Henrique de Moraes Holschuh
On Mon, 19 Jun 2017, Brian wrote: > The same experience as yours on tty1 to tty6. Except a couple of days > ago when I used nouveau.modeset=0 on GRUB's linux line and got what is > in the subject header. Kernel modeset must be enabled non-root X to work, as you found out... -- Henrique

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-19 Thread Greg Wooledge
On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote: > I have a dozen machines with Stretch installed, most with Jessie and/or Sid as > well. Only Stretch on host big41 produces the subject problem. According to a previous message in this thread, it could be triggered by a specific kernel

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-19 Thread Felix Miata
Greg Wooledge composed on 2017-06-19 09:29 (UTC-0400): . > On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote: . >> When I try as ordinary user (on host big41), I get the subject message. >> Anyone >> know how to get startx to work in Stretch, either on :0, :1 or :2, with or >> without a

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-19 Thread Brian
On Mon 19 Jun 2017 at 09:29:40 -0400, Greg Wooledge wrote: > On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote: > > When I try as ordinary user (on host big41), I get the subject message. > > Anyone > > know how to get startx to work in Stretch, either on :0, :1 or :2, with or > >

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-19 Thread Greg Wooledge
On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote: > When I try as ordinary user (on host big41), I get the subject message. Anyone > know how to get startx to work in Stretch, either on :0, :1 or :2, with or > without a greeter running (multi-user.targer vs. graphical.target)? I've

[Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

2017-06-18 Thread Felix Miata
>From the release notes: 2.2.10. The Xorg server no longer requires root In the stretch version of Xorg, it is possible to run the Xorg server as a regular user rather than as root. This reduces the risk of privilege escalation via bugs in the X server. However, it has some

Re: dist-upgrades on sid (was: X server: connection refused SOLVED)

2012-05-07 Thread Andrei POPESCU
On Du, 06 mai 12, 22:23:56, Charles Kroeger wrote: anyway, I couldn't get the X back up until I created that /etc/X11/xorg.conf file again. (a very simple one) but after that, all was once again well. If you want any help with this please attach the full /var/log/Xorg.0.log when you try to

Re: dist-upgrades on sid (was: X server: connection refused SOLVED)

2012-05-07 Thread Charles Kroeger
On Mon, 07 May 2012 20:50:01 +0200 Andrei POPESCU andreimpope...@gmail.com wrote: On Du, 06 mai 12, 22:23:56, Charles Kroeger wrote: anyway, I couldn't get the X back up until I created that /etc/X11/xorg.conf file again. (a very simple one) but after that, all was once again well. If

Re: dist-upgrades on sid (was: X server: connection refused SOLVED)

2012-05-06 Thread Andrei POPESCU
On Vi, 04 mai 12, 20:07:57, Charles Kroeger wrote: After the dist-upgrade on sid during the 'transitions' I noticed there was 'no' /etc/X11/xorg.conf file at all so I created one If you did fine without one before it should work now as well. Kind regards, Andrei -- Offtopic discussions among

Re: dist-upgrades on sid (was: X server: connection refused SOLVED)

2012-05-06 Thread Charles Kroeger
On Sun, 06 May 2012 11:30:02 +0200 Andrei POPESCU andreimpope...@gmail.com wrote: If you did fine without one before it should work now as well. It is curious to be sure. But when I tried to edit the /etc/X11/xorg.conf 'after the dist-upgrade' when startx failed to start the nvidia driver,

Re: dist-upgrades on sid (was: X server: connection refused SOLVED)

2012-05-04 Thread Charles Kroeger
After the dist-upgrade on sid during the 'transitions' I noticed there was 'no' /etc/X11/xorg.conf file at all so I created one I also added the meta package: xorg also there was no xserver-xorg package after the dist-upgrade this was the reason I was seeing in my error message after startx:

Re: X server: connection refused

2012-05-02 Thread Bob Proulx
Indulekha wrote: Charles Kroeger wrote: $startx /etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found Appears you no longer have the xserver installed. Upgrade get interrupted, or finish with errors perhaps? I noticed today that an 'apt-get dist-upgrade' in Sid wanted to remove

Re: X server: connection refused

2012-05-02 Thread Tom H
On Tue, May 1, 2012 at 7:13 PM, Charles Kroeger ckro...@frankensteinface.com wrote: After a dist-upgrade to an AMD64 wheezy/sid installation I get the following: $startx /etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found xinit: giving up xinit: unable to connect to X server

dist-upgrades on sid (was: X server: connection refused)

2012-05-02 Thread Jochen Spieker
Bob Proulx: I noticed today that an 'apt-get dist-upgrade' in Sid wanted to remove xserver-xorg and much of the rest of the X system. That's why I habitually only run 'apt-get upgrade', as it will never remove any packages and you can use it more or less blindly in order to receive

Re: dist-upgrades on sid (was: X server: connection refused)

2012-05-02 Thread Cyril Brulebois
Jochen Spieker m...@well-adjusted.de (02/05/2012): Incidentally, apt-get dist-upgrade is less disastrous in this case. It only suggests to remove xserver-xorg-video-all, xserver-xorg-video-s3virge and xserver-xorg-video-tdfx while keeping all important X related packages for my system.

X server: connection refused

2012-05-01 Thread Charles Kroeger
After a dist-upgrade to an AMD64 wheezy/sid installation I get the following: $startx /etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found xinit: giving up xinit: unable to connect to X server: connection refused xinit: server error I had a look at /etc/X11/xinit/xserverrc #!/bin/sh exec

Re: X server: connection refused

2012-05-01 Thread Indulekha
On Tue, May 01, 2012 at 06:13:51PM -0500, Charles Kroeger wrote: After a dist-upgrade to an AMD64 wheezy/sid installation I get the following: $startx /etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found xinit: giving up xinit: unable to connect to X server: connection refused xinit

Re: X server: connection refused

2012-05-01 Thread Charles Kroeger
On Wed, 02 May 2012 02:00:02 +0200 Indulekha indule...@theunworthy.com wrote: Appears you no longer have the xserver installed. Upgrade get interrupted, or finish with errors perhaps? Thanks for your response however I'm not sure it isn't something else as all the nividia-glx 295.40-1

Re: X server: connection refused

2012-05-01 Thread Indulekha
On Tue, May 01, 2012 at 09:53:55PM -0500, Charles Kroeger wrote: On Wed, 02 May 2012 02:00:02 +0200 Indulekha indule...@theunworthy.com wrote: Appears you no longer have the xserver installed. Upgrade get interrupted, or finish with errors perhaps? Thanks for your response however