Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #161348 > unrolled thread

Can't startx as normal user

Back to article view | Back to linux.debian.user

Contents

  Can't startx as normal user Draco Metallium(Rodrigo S. Cañibano) <draco.kun@gmail.com> - 2015-11-30 05:50 +0100
    Re: Can't startx as normal user Charlie <ariestao@ipstarmail.com.au> - 2015-11-30 06:10 +0100
    Re: Can't startx as normal user Ansgar Burchardt <"Ansgar Burchardt"@43-1.org> - 2015-11-30 10:20 +0100
      Re: Can't startx as normal user Draco Metallium(Rodrigo S. Cañibano) <draco.kun@gmail.com> - 2015-11-30 23:30 +0100
        Re: Can't startx as normal user Sven Arvidsson <sa@whiz.se> - 2015-12-01 20:50 +0100
          Re: Can't startx as normal user Draco Metallium(Rodrigo S. Cañibano) <draco.kun@gmail.com> - 2015-12-02 02:30 +0100
            Re: Can't startx as normal user Sven Arvidsson <sa@whiz.se> - 2015-12-02 15:50 +0100
    Re: Can't startx as normal user Harald Dunkel <harald.dunkel@aixigo.de> - 2015-11-30 11:40 +0100

#161348 — Can't startx as normal user

[Multipart message — attachments visible in raw view] — view raw

Hi!

Today I made a dist-upgrade and everything worked fine until I rebooted.

No only root can run startx. If a user tries the following error appears:

"(EE) AddScreen/ScreenInit failed for driver 0"

(I will attach the full log).

Does anyone have any idea what might be the source of this problem?

Thanks and sorry for the bad English!

--
Draco Metallium

[toc] | [next] | [standalone]

#161349

On Mon, 30 Nov 2015 01:48:40 -0300 Draco Metallium(Rodrigo S. Cañibano)
sent:

> Today I made a dist-upgrade and everything worked fine until I
> rebooted.
> 
> No only root can run startx. If a user tries the following error
> appears:
> 
> "(EE) AddScreen/ScreenInit failed for driver 0"
> 
> (I will attach the full log).
> 
> Does anyone have any idea what might be the source of this problem?

Could this be of help?

https://bbs.archlinux.org/viewtopic.php?id=170860

Charlie

-- 
	Registered Linux User:- 329524
	***********************************************

	If I shall sell both my forenoons and afternoons to society, as
	most appear to do, I'm sure that, for me, there would be
	nothing left worth living
	for. .............................Henry David Thoreau

	***********************************************

	Debian GNU/Linux - Magic indeed.

	-----------------------------------------------------

[toc] | [prev] | [next] | [standalone]

#161352

"Draco Metallium(Rodrigo S. Cañibano)" <draco.kun@gmail.com> writes:
> No only root can run startx. If a user tries the following error appears:
>
> "(EE) AddScreen/ScreenInit failed for driver 0"

The first error in the log you attached is:

> [  4203.010] (EE) systemd-logind: failed to get session: Rejected send message, 1 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=18022 comm="/usr/lib/xorg/Xorg -nolisten tcp :1 vt2 -keeptty -") interface="org.freedesktop.login1.Manager" member="GetSessionByPID" error name="(unset)" requested_reply="0" destination="org.freedesktop.login1" (uid=0 pid=5989 comm="/lib/systemd/systemd-logind ")

which looks like some DBus policy forbids Xorg to talk to logind. Xorg
does so in order to get access to devices w/o being setuid root since
recently.

I remember users having problems with DBus policies when old version of
systemd-shim were installed (it has been fixed some time ago),
cf. https://bugs.debian.org/746242

Please make sure that either systemd-shim is purged (not only removed),
e.g. by running "apt-get purge systemd-shim", or that at least version
6-3 of systemd-shim is installed (if you don't use systemd as init).

Ansgar

[toc] | [prev] | [next] | [standalone]

#161377

On 30 November 2015 at 06:10, Ansgar Burchardt <"Ansgar
Burchardt"@43-1.org> wrote:
> which looks like some DBus policy forbids Xorg to talk to logind. Xorg
> does so in order to get access to devices w/o being setuid root since
> recently.

It could be that, since I don't have systemd, nor systemd-shim
installed (I just checked again).

I had to install xserver-xorg-legacy, just as Harald Dunkel suggested.

Should't apt-get have warned me that there were unmet dependencies?

Wasn't systemd just an init?

Thanks to all of you!

[toc] | [prev] | [next] | [standalone]

#161436

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2015-11-30 at 19:20 -0300, Draco Metallium(Rodrigo S. Cañibano)
wrote:
> It could be that, since I don't have systemd, nor systemd-shim
> installed (I just checked again).
> 
> I had to install xserver-xorg-legacy, just as Harald Dunkel
> suggested.
> 
> Should't apt-get have warned me that there were unmet dependencies?

The NEWS entry should have been picked up by apt-listchanges:
https://sources.debian.net/src/xorg-server/2:1.17.3-2/debian/xserver-xorg-core.NEWS/

(And will probably also be mentioned in the release docs)

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5

[toc] | [prev] | [next] | [standalone]

#161443

On 1 December 2015 at 16:47, Sven Arvidsson <sa@whiz.se> wrote:
> The NEWS entry should have been picked up by apt-listchanges:

I must have missed it. Thanks!

[toc] | [prev] | [next] | [standalone]

#161455

[Multipart message — attachments visible in raw view] — view raw

On Tue, 2015-12-01 at 22:23 -0300, Draco Metallium(Rodrigo S. Cañibano)
> > The NEWS entry should have been picked up by apt-listchanges:
> 
> I must have missed it. Thanks!

Looks like it was added after the change was made, so it's possible
that you made the upgrade before it was added.

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5

[toc] | [prev] | [next] | [standalone]

#161353

If you are using startx/xinit: Try installing xserver-xorg-legacy.
I had the same problem.

Good luck
Harri

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web