Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
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 Stretch on host big41 produces the subject problem. > . > > According to a previous message in this thread, it could be triggered > > by a specific kernel boot parameter. Can you show us "cat /proc/cmdline" > > from big41? > . > Current boot, not exactly the same as the default Grub stanza, but virtually > the > same as my other Stretch installations that work as expected: > ro root=LABEL=debian9sv5 net.ifnames=0 ipv6.disable=1 noresume > plymouth.enable=0 > vga=791 video=1440x900@60 3 There doesn't appear to be anything there which could cause a problem, but me being me I'd try without the fluff. Jessie working is not a good comparison because it doesn't run X for a user without X having root privileges. DMs working are likewise not a good guide to a solution because they often interact gracefully with logind. How about the logs? They should be in ~/.local/share/xorg. Are they? Do they help? -- Brian.
Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
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 previous message in this thread, it could be triggered > by a specific kernel boot parameter. Can you show us "cat /proc/cmdline" > from big41? . Current boot, not exactly the same as the default Grub stanza, but virtually the same as my other Stretch installations that work as expected: ro root=LABEL=debian9sv5 net.ifnames=0 ipv6.disable=1 noresume plymouth.enable=0 vga=791 video=1440x900@60 3 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
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 Holschuh
Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
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 boot parameter. Can you show us "cat /proc/cmdline" from big41? > # inxi -c0 -v4 > System:Host: big41 Kernel: 4.9.0-3-amd64 x86_64 (64 bit gcc: 6.3.0) > Console: > tty 3 >Distro: Debian GNU/Linux 9 > Machine: Mobo: TAR model: T41 HD v: ' ' Bios: American Megatrends v: 080015 > date: 09/22/2009 > CPU: Dual core Intel Core2 Duo E7600 (-MCP-) cache: 3072 KB >flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 12237 >clock speeds: max: 3066 MHz 1: 1603 MHz 2: 1603 MHz > Graphics: Card: Intel 4 Series Integrated Graphics Controller bus-ID: 00:02.0 >Display Server: X.org 1.19.2 drivers: (unloaded: fbdev,vesa) >tty size: 180x56 Advanced Data: N/A for root out of X [snip]
Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
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 greeter running (multi-user.targer vs. graphical.target)? . > I've been using startx on stretch for a couple months, with no problems. > I login as my non-root user on tty1, and run 'startx', and it just works. . > This is on two different machines, both using Intel graphics. Here's one > of them: . 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. It has Intel Eagle Lake X4500 video attached via HDMI. It's Jessie works as expected, while its Sid halts at an initramfs prompt. Big41 with kernel 4.9.0-3-amd64 works as expected for root only. Ordinary users produce subject errors only by attempting startx. Login from TDM greeter works as expected for all users. . > wooledg:~$ uname -a > Linux wooledg 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) x86_64 > GNU/Linux > > wooledg:~$ lspci -nn | grep VGA > 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 > [8086:1912] (rev 06) > > wooledg:~$ sudo dmesg | grep firmware > [3.796473] [drm] GuC firmware load skipped > [3.802454] i915 :00:02.0: firmware: direct-loading firmware > i915/skl_dmc_ver1_26.bin . # inxi -c0 -v4 System:Host: big41 Kernel: 4.9.0-3-amd64 x86_64 (64 bit gcc: 6.3.0) Console: tty 3 Distro: Debian GNU/Linux 9 Machine: Mobo: TAR model: T41 HD v: ' ' Bios: American Megatrends v: 080015 date: 09/22/2009 CPU: Dual core Intel Core2 Duo E7600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 12237 clock speeds: max: 3066 MHz 1: 1603 MHz 2: 1603 MHz Graphics: Card: Intel 4 Series Integrated Graphics Controller bus-ID: 00:02.0 Display Server: X.org 1.19.2 drivers: (unloaded: fbdev,vesa) tty size: 180x56 Advanced Data: N/A for root out of X Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: d800 bus-ID: 01:00.0 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:30:67:3a:a0:06 Drives:HDD Total Size: 500.1GB (7.4% used) ID-1: /dev/sda model: ST3500411SV size: 500.1GB Partition: ID-1: / size: 5.4G used: 3.5G (67%) fs: ext3 dev: /dev/sda27 ID-2: /home size: 4.3G used: 810M (19%) fs: ext3 dev: /dev/sda9 ID-3: swap-1 size: 1.57GB used: 0.00GB (0%) fs: swap dev: /dev/sda5 Info: Processes: 139 Uptime: 28 min Memory: 161.8/3731.4MB Init: systemd runlevel: 5 Gcc sys: 6.3.0 Client: Shell (bash 4.4.121) inxi: 2.2.28 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
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 > > without a greeter running (multi-user.targer vs. graphical.target)? > > I've been using startx on stretch for a couple months, with no problems. > I login as my non-root user on tty1, and run 'startx', and it just works. 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.
Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
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 been using startx on stretch for a couple months, with no problems. I login as my non-root user on tty1, and run 'startx', and it just works. This is on two different machines, both using Intel graphics. Here's one of them: wooledg:~$ uname -a Linux wooledg 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) x86_64 GNU/Linux wooledg:~$ lspci -nn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) wooledg:~$ sudo dmesg | grep firmware [3.796473] [drm] GuC firmware load skipped [3.802454] i915 :00:02.0: firmware: direct-loading firmware i915/skl_dmc_ver1_26.bin
[Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused
>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 requirements for working: * It needs logind and libpam-systemd. * The system needs to support Kernel Mode Setting (KMS). Therefore, it may not work in some virtualization environments (e.g. virtualbox) or if the kernel has no driver that supports your graphics card. * It needs to run on the virtual console it was started from. * Only the gdm3 display manager supports running X as a non-privileged user in stretch. Other display managers will always run X as root. Alternatively, you can also start X manually as a non-root user on a virtual terminal via startx. 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)? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
