Re: X not working after apt-get upgrade on sid

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: X not working after apt-get upgrade on sid

John DeVito
I ran into an issue today where X is not working after and upgrade of Stretch.  The pervasive error I am seeing is related to dbus-core.  Xorg.0.log says ... Failed to connect to socket /var/run/dbus/system_bus_socket.  Manual attempts to navigate to that directory shows that /var/run exists, but the dbus directory is not below 'run'.  If I try to run startx it briefly brings up the initial screen but then X crashes and results in a command prompt environment again.  I am also getting errors when trying to use apt, saying that no sources can be resolved.  Seems like this latest round of updates really introduced some issues.
Reply | Threaded
Open this post in threaded view
|

Re: X not working after apt-get upgrade on sid

Alex Moonshine-2
On Wed, 28 Oct 2015 02:44:10 +0000 (UTC)
John DeVito <[hidden email]> wrote:

> I ran into an issue today where X is not working after andupgrade of
> Stretch.  The pervasive errorI am seeing is related to dbus-core.
> Xorg.0.log says ... Failed to connect to
> socket /var/run/dbus/system_bus_socket.  Manual attempts to navigate
> to that directory shows that /var/run exists, but the dbus directory
> is not below 'run'.  If I try to run startx it briefly brings up the
> initial screen but then X crashes and results in a command prompt
> environment again.  I am also getting errors when trying to use apt,
> saying that no sources can be resolved.  Seems like this latest round
> of updates really introduced some issues.

1. Your subject says sid and in the message you say stretch. Which one
did you upgrade?

2. Do you have systemd intalled? There was a recent update to
xorg-server in sid, which makes it run under a regular user instead of
root, so now it relies on logind. If you do not have systemd installed,
you need to install xserver-xorg-legacy, which contains the setuid
wrapper used to run X as root (as before).

Of course, your apt problem can't be related to this upgrade.

--
Time is an illusion. Lunchtime doubly so.

Best wishes,
Alex S.