Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#897338: sddm: Cannot launch SDDM at boot time and from console
690 views
Skip to first unread message
Maximiliano Curia
May 2, 2018, 2:00:02 AM5/2/18
to
¡Hola Alexander!
El 2018-05-01 a las 17:12 +0300, Alexander Kernozhitsky escribió:
> Package: sddm
> Version: 0.17.0-1
> Severity: grave
> Justification: renders package unusable
> I tried to do a fresh install of Debian Testing with KDE. After installing
> it, SDDM did not launch. Launching it manually with "sudo systemctl start
> sddm" did not have effect also.
> "systemctl status sddm" shows the following:
> ● sddm.service - Simple Desktop Display Manager
> Loaded: loaded (/lib/systemd/system/sddm.service; indirect; vendor preset: enabled)
> Active: active (running) since Tue 2018-05-01 16:56:33 +03; 12min ago
> Docs: man:sddm(1)
> man:sddm.conf(5)
> Process: 412 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/
> Main PID: 421 (sddm)
> Tasks: 2 (limit: 1156)
> Memory: 11.7M
> CGroup: /system.slice/sddm.service
> └─421 /usr/bin/sddm
> Though I don't see the login screen, tty7 is blank.
> I tried to rebuild and install sddm from Ubuntu Bionic (where it works), but
> met the same problem. Installing sddm 0.14.0-4 from stable did solve the
> problem.
Is X started at all?
What's the output of `` update-alternatives --query sddm-debian-theme `` ?
It seems that there is a known issue upstream with some nvidia drivers:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1762885
https://github.com/sddm/sddm/issues/1019
Are you using a nvidia card? Can you please check if the problem goes away
with an older version of the nvidia drivers?
Happy hacking,
--
"Anytime you have a fifty-fifty chance of getting something right, there's a
90 percent probability you'll get it wrong."
-- The 50-50-90 rule
Saludos /\/\ /\ >< `/
El 2018-05-01 a las 17:12 +0300, Alexander Kernozhitsky escribió:
> Package: sddm
> Version: 0.17.0-1
> Severity: grave
> Justification: renders package unusable
> I tried to do a fresh install of Debian Testing with KDE. After installing
> it, SDDM did not launch. Launching it manually with "sudo systemctl start
> sddm" did not have effect also.
> "systemctl status sddm" shows the following:
> ● sddm.service - Simple Desktop Display Manager
> Loaded: loaded (/lib/systemd/system/sddm.service; indirect; vendor preset: enabled)
> Active: active (running) since Tue 2018-05-01 16:56:33 +03; 12min ago
> Docs: man:sddm(1)
> man:sddm.conf(5)
> Process: 412 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/
> Main PID: 421 (sddm)
> Tasks: 2 (limit: 1156)
> Memory: 11.7M
> CGroup: /system.slice/sddm.service
> └─421 /usr/bin/sddm
> Though I don't see the login screen, tty7 is blank.
> I tried to rebuild and install sddm from Ubuntu Bionic (where it works), but
> met the same problem. Installing sddm 0.14.0-4 from stable did solve the
> problem.
Is X started at all?
What's the output of `` update-alternatives --query sddm-debian-theme `` ?
It seems that there is a known issue upstream with some nvidia drivers:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1762885
https://github.com/sddm/sddm/issues/1019
Are you using a nvidia card? Can you please check if the problem goes away
with an older version of the nvidia drivers?
Happy hacking,
--
"Anytime you have a fifty-fifty chance of getting something right, there's a
90 percent probability you'll get it wrong."
-- The 50-50-90 rule
Saludos /\/\ /\ >< `/
Kevin Messer
May 29, 2018, 3:00:02 AM5/29/18
to
Hi, I am on Debian Unstable on real hardware and I have the same problem, SDDM launches but there is dark screen on TTY7 with only my mouse.
--
Kevin Messer
Jens Radloff
Jul 10, 2019, 3:30:03 AM7/10/19
to
Hi,
I installed Debian 10.0 ("Buster"), the current stable Debian release since
some days, on my testing machine using a Netinstall CD.
During the installation process I deactivated the installation of Gnome and
instead activated the installation of KDE Plasma. So this installation is no
upgrade from Debian 9.x ("Stretch"), but a new installation.
My testing machine has no Nvidia hardware. I did not install Debian Buster
into an instance of Virtualbox.
Debian Buster starts successfully but does not present a login manager to KDE
at the end of the boot/start process. Instead the console is shown on tty1.
Until here no /var/log/Xorg.0.log gets created. If I enter "startx" as root or
the normal user in the console, then KDE starts successfully.
The package sddm is installed.
The file /etc/X11/default-display-manager contains "/usr/bin/sddm".
I have an AMD Radeon graphic card, i.e. a Radeon HD 4350/4550.
Installing the package firmware-amd-graphics (thanks for this hint to user towo
from an Internet forum) does not resolve the behaviour.
The command "journalctl | grep sddm" (thanks for this hint to user MSfree from
an Internet forum) results in the following output ("startx" has not been
executed before):
--- Quote Beginning ---
root@xxx:/home/yyy# journalctl|grep sddm
Jul 09 13:16:06 shit sddm[401]: Initializing...
Jul 09 13:16:06 shit sddm[401]: Starting...
Jul 09 13:16:06 shit sddm[401]: Logind interface found
root@xxx:/home/yyy#
--- Quote End ---
The command "systemctl enable sddm" (thanks for this hint to user wanne from
an Internet forum) results in the following output:
--- Quote Beginning ---
Synchronizing state of sddm.service with SysV service script with /lib/
systemd/systemd-sysv-install
Executing: /lib/systemd/systemd-sys-install enable sddm
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
- A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
- A unit's purpose may be to act as a helper for some other unit which has a
requirement dependency on it
- A unit may be started when needed via activation (socket, path, timer, D-
Bus. udev, scripted systemctl call ...)
- In case of template units, the unit is meant to be enabled with some
instance name specified.
--- Quote End ---
Regards,
Jens
I installed Debian 10.0 ("Buster"), the current stable Debian release since
some days, on my testing machine using a Netinstall CD.
During the installation process I deactivated the installation of Gnome and
instead activated the installation of KDE Plasma. So this installation is no
upgrade from Debian 9.x ("Stretch"), but a new installation.
My testing machine has no Nvidia hardware. I did not install Debian Buster
into an instance of Virtualbox.
Debian Buster starts successfully but does not present a login manager to KDE
at the end of the boot/start process. Instead the console is shown on tty1.
Until here no /var/log/Xorg.0.log gets created. If I enter "startx" as root or
the normal user in the console, then KDE starts successfully.
The package sddm is installed.
The file /etc/X11/default-display-manager contains "/usr/bin/sddm".
I have an AMD Radeon graphic card, i.e. a Radeon HD 4350/4550.
Installing the package firmware-amd-graphics (thanks for this hint to user towo
from an Internet forum) does not resolve the behaviour.
The command "journalctl | grep sddm" (thanks for this hint to user MSfree from
an Internet forum) results in the following output ("startx" has not been
executed before):
--- Quote Beginning ---
root@xxx:/home/yyy# journalctl|grep sddm
Jul 09 13:16:06 shit sddm[401]: Initializing...
Jul 09 13:16:06 shit sddm[401]: Starting...
Jul 09 13:16:06 shit sddm[401]: Logind interface found
root@xxx:/home/yyy#
--- Quote End ---
The command "systemctl enable sddm" (thanks for this hint to user wanne from
an Internet forum) results in the following output:
--- Quote Beginning ---
Synchronizing state of sddm.service with SysV service script with /lib/
systemd/systemd-sysv-install
Executing: /lib/systemd/systemd-sys-install enable sddm
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
- A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
- A unit's purpose may be to act as a helper for some other unit which has a
requirement dependency on it
- A unit may be started when needed via activation (socket, path, timer, D-
Bus. udev, scripted systemctl call ...)
- In case of template units, the unit is meant to be enabled with some
instance name specified.
--- Quote End ---
Regards,
Jens
Jens Radloff
Jul 10, 2019, 1:40:02 PM7/10/19
to
Update:
I tried the following iso images:
a) the official Debian Buster Live DVD with KDE image at https://
cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/debian-
live-10.0.0-amd64-kde.iso
=> Running this image live results at the end of the loading process from DVD
in a console prompt. No graphical environment is shown. It seems to make no
sense to install this image to the hard drive.
b) the unofficial Debian Buster Live DVD with non-free packages and KDE at
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
current-live/amd64/iso-hybrid/debian-live-10.0.0-amd64-kde+nonfree.iso
=> Running this image live results at the end of the loading process from DVD
in displaying KDE. From there, if you install Debian Buster on the hard drive
running the graphical installation program you are not asked in that program
to enter the password for user root, only for the normal user. This results in
an installation in which you do not know the password for user root.
Regards,
Jens
I tried the following iso images:
a) the official Debian Buster Live DVD with KDE image at https://
cdimage.debian.org/cdimage/release/current-live/amd64/iso-hybrid/debian-
live-10.0.0-amd64-kde.iso
=> Running this image live results at the end of the loading process from DVD
in a console prompt. No graphical environment is shown. It seems to make no
sense to install this image to the hard drive.
b) the unofficial Debian Buster Live DVD with non-free packages and KDE at
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/
current-live/amd64/iso-hybrid/debian-live-10.0.0-amd64-kde+nonfree.iso
=> Running this image live results at the end of the loading process from DVD
in displaying KDE. From there, if you install Debian Buster on the hard drive
running the graphical installation program you are not asked in that program
to enter the password for user root, only for the normal user. This results in
an installation in which you do not know the password for user root.
Regards,
Jens
Jens Radloff
Jul 13, 2019, 11:50:03 AM7/13/19
to
Hi,
I have found a solution for the behaviour on my machine with an AMD Radeon
graphic card and with regard to Debian Buster 10.0, by doing a search on the
Internet.
The following packets need to be installed:
firmware-linux
firmware-linux-nonfree
libdrm-amdgpu1
xserver-xorg-video-amdgpu
I found this information at
https://linuxconfig.org/how-to-install-the-latest-amd-drivers-on-debian-10-buster
Two of these packets were already installed in my Debian Buster installation.
Now sddm is shown at the end of the start process of Debian Buster, and I can
successfully log into KDE.
Regards,
Jens
I have found a solution for the behaviour on my machine with an AMD Radeon
graphic card and with regard to Debian Buster 10.0, by doing a search on the
Internet.
The following packets need to be installed:
firmware-linux
firmware-linux-nonfree
libdrm-amdgpu1
xserver-xorg-video-amdgpu
I found this information at
https://linuxconfig.org/how-to-install-the-latest-amd-drivers-on-debian-10-buster
Two of these packets were already installed in my Debian Buster installation.
Now sddm is shown at the end of the start process of Debian Buster, and I can
successfully log into KDE.
Regards,
Jens
0 new messages