Debian Bug report logs - #873262
user cannot startx session

Reply or subscribe to this bug.

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Eggert Ehmke <eggert@eehmke.de>

To: submit@bugs.debian.org

Subject: user cannot startx session

Date: Fri, 25 Aug 2017 23:10:40 +0200

[Message part 1 (text/plain, inline)]

Package: xorg

I upgraded a system from jessie to stretch. It is a kiosk system without a window 
manager that starts one single application directly via startx. The dedicated user could 
not start the session after the upgrade.

With Debian jessie, there were no problems.

I got these errors:
Fatal server error:(EE) xf86OpenConsole: Cannot open virtual console 1 (Permission 
denied)(EE)(EE)Please consult the The X.Org Foundation support         at http://wiki.x.org[1]


The solution was to issue this command:
chmod ug+s /usr/lib/xorg/Xorg

I found it in a related Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1562219

Regards
Eggert

--------
[1] http://wiki.x.org

[Message part 2 (text/html, inline)]

Message #10 received at 873262@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Eggert Ehmke <eggert@eehmke.de>, 873262@bugs.debian.org

Subject: Re: Bug#873262: user cannot startx session

Date: Mon, 28 Aug 2017 09:23:11 +0200

Control: tags -1 moreinfo

On 08/25/2017 11:10 PM, Eggert Ehmke wrote:
> Package: xorg
> 
>  
> 
> I upgraded a system from jessie to stretch. It is a kiosk system without
> a window manager that starts one single application directly via startx.
> The dedicated user could not start the session after the upgrade.
> 
>  
> 
> With Debian jessie, there were no problems.
> 
>  
> 
> I got these errors:
> 
> Fatal server error:
> (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
> (EE)
> (EE)
> Please consult the The X.Org Foundation support
>          at http://wiki.x.org
>  for help.
> (EE) Please also check the log file at
> "/home/arch/.local/share/xorg/Xorg.0.log" for additional information.
> (EE)
> (EE) Server terminated with error (1). Closing log file.
> xinit: giving up
> xinit: unable to connect to X server: Connection refused
> 
>  
> 
> The solution was to issue this command:
> 
> chmod ug+s /usr/lib/xorg/Xorg
> 
>  
This is not a solution at all, it's opening a glaring security hold on
your machine.

Please show the full Xorg log file.

Cheers,
Julien

Message #17 received at 873262@bugs.debian.org (full text, mbox, reply):

From: Eggert Ehmke <eggert@eehmke.de>

To: Julien Cristau <jcristau@debian.org>

Cc: 873262@bugs.debian.org

Subject: Re: Bug#873262: user cannot startx session

Date: Mon, 28 Aug 2017 12:13:52 +0200

Am Montag, 28. August 2017, 09:23:11 CEST schrieb Julien Cristau:
> Control: tags -1 moreinfo
> 
> On 08/25/2017 11:10 PM, Eggert Ehmke wrote:
> > Package: xorg
> > 
> > 
> > 
> > I upgraded a system from jessie to stretch. It is a kiosk system without
> > a window manager that starts one single application directly via startx.
> > The dedicated user could not start the session after the upgrade.
> > 
> > 
> > 
> > With Debian jessie, there were no problems.
> > 
> > 
> > 
> > I got these errors:
> > 
> > Fatal server error:
> > (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
> > (EE)
> > (EE)
> > Please consult the The X.Org Foundation support
> > 
> >          at http://wiki.x.org
> >  
> >  for help.
> > 
> > (EE) Please also check the log file at
> > "/home/arch/.local/share/xorg/Xorg.0.log" for additional information.
> > (EE)
> > (EE) Server terminated with error (1). Closing log file.
> > xinit: giving up
> > xinit: unable to connect to X server: Connection refused
> > 
> > 
> > 
> > The solution was to issue this command:
> > 
> > chmod ug+s /usr/lib/xorg/Xorg
> 
> This is not a solution at all, it's opening a glaring security hold on
> your machine.
> 
> Please show the full Xorg log file.

I know that is not a good solution, but I had to keep the machine running. It 
is an isolated system with no other user interaction.

Will get the log ASAP. I do not have permanently access to is so it can take 
some days.

Regards
Eggert

Message #22 received at 873262@bugs.debian.org (full text, mbox, reply):

From: eggert@eehmke.de

To: 873262@bugs.debian.org

Subject: Bug#873262: Info received (Bug#873262: user cannot startx session)

Date: Tue, 05 Sep 2017 22:38:21 +0200

[Message part 1 (text/plain, inline)]

I tried to reproduce the error. As a result to restart my service, I get this message:
 
$ sudo systemctl status startkladde.service 
● startkladde.service - Startkladde 
  Loaded: loaded (/etc/systemd/system/startkladde.service; enabled; vendor preset: 
enabled) 
  Active: failed (Result: exit-code) since Fri 2017-09-01 20:40:20 CEST; 27s ago 
 Process: 16377 ExecStart=/usr/bin/sudo -u startkladde startx /usr/local/bin/
startkladde_wrapper (code=exited, status=1/FAILURE) 
Main PID: 16377 (code=exited, status=1/FAILURE) 

Sep 01 20:40:05 startkladde sudo[16377]: (EE) Please also check the log file at "/home/
startkladde/.local/share/xorg/Xorg.0.log" for additional information. 
Sep 01 20:40:05 startkladde sudo[16377]: (EE) 
Sep 01 20:40:05 startkladde sudo[16377]: (EE) Server terminated with error (1). Closing log 
file. 
Sep 01 20:40:20 startkladde sudo[16377]: xinit: giving up 
Sep 01 20:40:20 startkladde sudo[16377]: xinit: unable to connect to X server: Connection 
refused 
Sep 01 20:40:20 startkladde sudo[16377]: xinit: server error 
Sep 01 20:40:20 startkladde systemd[1]: startkladde.service: Main process exited, 
code=exited, status=1/FAILURE 
Sep 01 20:40:20 startkladde systemd[1]: Failed to start Startkladde. 
Sep 01 20:40:20 startkladde systemd[1]: startkladde.service: Unit entered failed state. 
Sep 01 20:40:20 startkladde systemd[1]: startkladde.service: Failed with result 'exit-code'.

File Xorg.0.log is attached. I guess the fault is here:
Fatal server error:
[  9889.428] (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
 
This system has be fresh upgraded from Debian 8.9 to 9.1. Before the upgrade this was 
working.
 

[Message part 2 (text/html, inline)]

Message #27 received at 873262@bugs.debian.org (full text, mbox, reply):

From: "Eggert (FTV)" <eggert.ehmke@ftv-spandau.de>

To: 873262@bugs.debian.org

Subject: Bug#873262: Info received (Bug#873262: user cannot startx session)

Date: Tue, 05 Sep 2017 22:43:43 +0200

[Message part 1 (text/plain, inline)]

(Attached file was missing in last mail)

I tried to reproduce the error. As a result to restart my service, I get this message:
 
$ sudo systemctl status startkladde.service 
● startkladde.service - Startkladde 
  Loaded: loaded (/etc/systemd/system/startkladde.service; enabled; vendor preset: 
enabled) 
  Active: failed (Result: exit-code) since Fri 2017-09-01 20:40:20 CEST; 27s ago 
 Process: 16377 ExecStart=/usr/bin/sudo -u startkladde startx /usr/local/bin/
startkladde_wrapper (code=exited, status=1/FAILURE) 
Main PID: 16377 (code=exited, status=1/FAILURE) 

Sep 01 20:40:05 startkladde sudo[16377]: (EE) Please also check the log file at "/home/
startkladde/.local/share/xorg/Xorg.0.log" for additional information. 
Sep 01 20:40:05 startkladde sudo[16377]: (EE) 
Sep 01 20:40:05 startkladde sudo[16377]: (EE) Server terminated with error (1). Closing log 
file. 
Sep 01 20:40:20 startkladde sudo[16377]: xinit: giving up 
Sep 01 20:40:20 startkladde sudo[16377]: xinit: unable to connect to X server: Connection 
refused 
Sep 01 20:40:20 startkladde sudo[16377]: xinit: server error 
Sep 01 20:40:20 startkladde systemd[1]: startkladde.service: Main process exited, 
code=exited, status=1/FAILURE 
Sep 01 20:40:20 startkladde systemd[1]: Failed to start Startkladde. 
Sep 01 20:40:20 startkladde systemd[1]: startkladde.service: Unit entered failed state. 
Sep 01 20:40:20 startkladde systemd[1]: startkladde.service: Failed with result 'exit-code'.

File Xorg.0.log is attached. I guess the fault is here:
Fatal server error:
[  9889.428] (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
 
This system has be fresh upgraded from Debian 8.9 to 9.1. Before the upgrade this was 
working.
 

[Message part 2 (text/html, inline)]

[Xorg.0.log (text/x-log, attachment)]

Send a report that this bug log contains spam.