Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.devel.testing > #986 > unrolled thread
| Started by | John DeVito <john.devito@yahoo.com> |
|---|---|
| First post | 2015-10-28 02:00 +0100 |
| Last post | 2015-10-28 20:30 +0100 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.debian.devel.testing
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Today (20151027) updates and XServer problem John DeVito <john.devito@yahoo.com> - 2015-10-28 02:00 +0100
Re: Today (20151027) updates and XServer problem Brad Rogers <brad@fineby.me.uk> - 2015-10-28 14:10 +0100
Re: Today (20151027) updates and XServer problem John DeVito <john.devito@yahoo.com> - 2015-10-28 18:00 +0100
Re: Today (20151027) updates and XServer problem Brad Rogers <brad@fineby.me.uk> - 2015-10-28 20:30 +0100
| From | John DeVito <john.devito@yahoo.com> |
|---|---|
| Date | 2015-10-28 02:00 +0100 |
| Subject | Today (20151027) updates and XServer problem |
| Message-ID | <qonfP-3X2-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Wondering if anyone else installed updates today to an x64 Stretch installation and had the XServer crash after a reboot. I am getting errors in the Xorg.0.log file stating that dbus-core encountered an error connecting to the system bus. 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'.
[toc] | [next] | [standalone]
| From | Brad Rogers <brad@fineby.me.uk> |
|---|---|
| Date | 2015-10-28 14:10 +0100 |
| Message-ID | <qoyEi-329-37@gated-at.bofh.it> |
| In reply to | #986 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, 28 Oct 2015 00:36:04 +0000 (UTC)
John DeVito <john.devito@yahoo.com> wrote:
Hello John,
>Wondering if anyone else installed updates today to an x64 Stretch
>installation and had the XServer crash after a reboot. I am getting
Yes, it's happening here, too. Can't get KDE up at all. In the short
term, I've installed LXDE, and now do a shell login and then run
'startx'.
>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'.
Once I get LXDE up, /var/run/dbus/system_bus_socket exists. I've not
checked for it before running startx, however.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
He looked the wrong way at a policeman
I Predict A Riot - Kaiser Chiefs
[toc] | [prev] | [next] | [standalone]
| From | John DeVito <john.devito@yahoo.com> |
|---|---|
| Date | 2015-10-28 18:00 +0100 |
| Message-ID | <qoCeS-5cz-15@gated-at.bofh.it> |
| In reply to | #987 |
[Multipart message — attachments visible in raw view] — view raw
I had tried to reinstall completely, selecting to install the KDE UI during the install and got the same results. No dbus directory in /run. I just installed with no UI and I have the /run/dbus directory and the socket file was there. Installing different components I came to the conclusion that sddm is the culprit. Using dpkg-reconfigure if I select sddm as the default display manager I get a cursor in the upper left hand corner when I should be getting a login screen. If I use kdm as the display manager I get the KDE logon screen as expected.
On Wednesday, October 28, 2015 8:22 AM, Brad Rogers <brad@fineby.me.uk> wrote:
On Wed, 28 Oct 2015 00:36:04 +0000 (UTC)
John DeVito <john.devito@yahoo.com> wrote:
Hello John,
>Wondering if anyone else installed updates today to an x64 Stretch
>installation and had the XServer crash after a reboot. I am getting
Yes, it's happening here, too. Can't get KDE up at all. In the short
term, I've installed LXDE, and now do a shell login and then run
'startx'.
>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'.
Once I get LXDE up, /var/run/dbus/system_bus_socket exists. I've not
checked for it before running startx, however.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
He looked the wrong way at a policeman
I Predict A Riot - Kaiser Chiefs
[toc] | [prev] | [next] | [standalone]
| From | Brad Rogers <brad@fineby.me.uk> |
|---|---|
| Date | 2015-10-28 20:30 +0100 |
| Message-ID | <qoEA2-6Ra-13@gated-at.bofh.it> |
| In reply to | #988 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, 28 Oct 2015 16:57:19 +0000 (UTC)
John DeVito <john.devito@yahoo.com> wrote:
Hello John,
>sddm is the culprit. Using dpkg-reconfigure if I select sddm as the
>default display manager I get a cursor in the upper left hand corner
>when I should be getting a login screen. If I use kdm as the display
>manager I get the KDE logon screen as expected.
Getting similar results here; With KDM, I can get a login screen, but I
just get a black screen with SDDM (not even a blinking cursor). Sadly, I
can't downgrade libqt5x11extras (no longer on disk locally, and not
available in the repos) to see if that gets KDE working again. I'm just
going to have to wait for the rest of Qt to get to 5.5.1 in Testing.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
It's becoming an obsession
Teenage Depression - Eddie & The Hot Rods
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.devel.testing
csiph-web