#1 27.01.2019 02:02:39

drei86er
Mitglied

LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

Hi bin relativ neu im ARCH Linux Umfeld, habe jedoch einige Erfahrung im RedHat LinuxServer Umfeld.

Habe lightdm als DisplayManager installiert. Wenn dieser enabled ist, wird mein Bildschirm beim starten schwarz und reagiert nicht mehr.

Wenn ich lightdm jedoch manuell starte, kann ich es ausführen. Mein Desktop Theme xfce kann ich ebenfalls manuell starten.

Hat jemand eine Idee woran es liegen könnte?

Hierzu ein paar logs:

/var/log/lightdm/lightdm.log

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.28.0, UID=0 PID=512
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.00s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.00s] DEBUG: Could not run plymouth --ping: Failed to execute child process plymouth (No such file or directory)
[+0.00s] DEBUG: Using VT 7
[+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.00s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.00s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.00s] DEBUG: XServer 0: Launching X Server
[+0.00s] DEBUG: Launching process 518: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.00s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
[+0.01s] DEBUG: Loading user config from /etc/lightdm/users.conf
[+0.01s] DEBUG: User tobias added
[+0.13s] DEBUG: Seat seat0 changes active session to 
[+1.19s] DEBUG: Got signal 10 from process 518
[+1.19s] DEBUG: XServer 0: Got signal from X server :0
[+1.19s] DEBUG: XServer 0: Connecting to XServer :0
[+1.23s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 
[+1.24s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+1.24s] DEBUG: Session pid=531: Started with service 'lightdm-greeter', username 'lightdm'
[+1.24s] DEBUG: Session pid=531: Authentication complete with return value 0: Success
[+1.24s] DEBUG: Seat seat0: Session authenticated, running command
[+1.24s] DEBUG: Session pid=531: Running command /usr/bin/lightdm-gtk-greeter
[+1.24s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+1.24s] DEBUG: Session pid=531: Logging to /var/log/lightdm/seat0-greeter.log
[+1.25s] DEBUG: Activating VT 7
[+1.34s] DEBUG: Greeter connected version=1.28.0 api=1 resettable=false
[+1.80s] DEBUG: Greeter start authentication for tobias
[+1.80s] DEBUG: Session pid=541: Started with service 'lightdm', username 'tobias'
[+1.81s] DEBUG: Session pid=541: Got 1 message(s) from PAM
[+1.81s] DEBUG: Prompt greeter with 1 message(s)
[+9.32s] DEBUG: Continue authentication
[+9.36s] DEBUG: Session pid=541: Authentication complete with return value 0: Success
[+9.36s] DEBUG: Authenticate result for user tobias: Success
[+9.36s] DEBUG: User tobias authorized
[+9.37s] DEBUG: Greeter requests session xfce
[+9.37s] CRITICAL: g_dbus_connection_call_sync_internal: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
[+9.37s] DEBUG: Writing /home/tobias/.dmrc
[+9.37s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
[+9.37s] DEBUG: Session pid=531: Sending SIGTERM
[+9.38s] DEBUG: Greeter closed communication channel
[+9.38s] DEBUG: Session pid=531: Exited with return value 0
[+9.38s] DEBUG: Seat seat0: Session stopped
[+9.38s] DEBUG: Seat seat0: Greeter stopped, running session
[+9.38s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+9.38s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 
[+9.38s] DEBUG: Session pid=541: Running command /etc/lightdm/Xsession startxfce4
[+9.38s] DEBUG: Creating shared data directory /var/lib/lightdm-data/tobias
[+9.38s] DEBUG: Session pid=541: Logging to .xsession-errors
[+9.39s] DEBUG: Activating VT 7
[+16.16s] DEBUG: Session pid=541: Exited with return value 0
[+16.16s] DEBUG: Seat seat0: Session stopped
[+16.16s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+16.16s] DEBUG: Sending signal 15 to process 518
[+16.56s] DEBUG: Process 518 exited with return value 0
[+16.56s] DEBUG: XServer 0: X server stopped
[+16.56s] DEBUG: Releasing VT 7
[+16.56s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+16.56s] DEBUG: Seat seat0: Display server stopped
[+16.56s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+16.56s] DEBUG: Seat seat0: Creating greeter session
[+16.56s] DEBUG: Seat seat0: Creating display server of type x
[+16.56s] DEBUG: Using VT 7
[+16.56s] DEBUG: Seat seat0: Starting local X display on VT 7
[+16.56s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+16.56s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+16.56s] DEBUG: XServer 0: Launching X Server
[+16.56s] DEBUG: Launching process 572: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+16.56s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+17.47s] DEBUG: Got signal 10 from process 572
[+17.47s] DEBUG: XServer 0: Got signal from X server :0
[+17.47s] DEBUG: XServer 0: Connecting to XServer :0
[+17.50s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified) 
[+17.50s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+17.50s] DEBUG: Session pid=582: Started with service 'lightdm-greeter', username 'lightdm'
[+17.51s] DEBUG: Session pid=582: Authentication complete with return value 0: Success
[+17.51s] DEBUG: Seat seat0: Session authenticated, running command
[+17.51s] DEBUG: Session pid=582: Running command /usr/bin/lightdm-gtk-greeter
[+17.51s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+17.51s] DEBUG: Session pid=582: Logging to /var/log/lightdm/seat0-greeter.log
[+17.51s] DEBUG: Activating VT 7
[+17.57s] DEBUG: Greeter connected version=1.28.0 api=1 resettable=false
[+17.60s] DEBUG: Greeter start authentication for tobias
[+17.60s] DEBUG: Session pid=592: Started with service 'lightdm', username 'tobias'
[+17.61s] DEBUG: Session pid=592: Got 1 message(s) from PAM
[+17.61s] DEBUG: Prompt greeter with 1 message(s)
[+32.64s] DEBUG: Got signal 15 from process 1
[+32.64s] DEBUG: Caught Terminated signal, shutting down
[+32.64s] DEBUG: Stopping display manager
[+32.64s] DEBUG: Seat seat0: Stopping
[+32.64s] DEBUG: Seat seat0: Stopping display server
[+32.64s] DEBUG: Sending signal 15 to process 572
[+32.64s] DEBUG: Seat seat0: Stopping session
[+32.64s] DEBUG: Session pid=582: Sending SIGTERM
[+32.64s] DEBUG: Seat seat0: Stopping session
[+32.64s] DEBUG: Session pid=592: Sending SIGTERM
[+32.64s] DEBUG: Got signal 15 from process 511
[+32.64s] DEBUG: Caught Terminated signal, shutting down
[+32.64s] DEBUG: Session pid=592: Terminated with signal 15
[+32.64s] DEBUG: Session: Failed during authentication
[+32.64s] DEBUG: Seat seat0: Session stopped
[+32.68s] DEBUG: Greeter closed communication channel
[+32.68s] DEBUG: Session pid=582: Exited with return value 1
[+32.68s] DEBUG: Seat seat0: Session stopped
[+33.00s] DEBUG: Process 572 exited with return value 0
[+33.00s] DEBUG: XServer 0: X server stopped
[+33.00s] DEBUG: Releasing VT 7
[+33.00s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+33.00s] DEBUG: Seat seat0: Display server stopped
[+33.00s] DEBUG: Seat seat0: Stopped
[+33.00s] DEBUG: Display manager stopped
[+33.00s] DEBUG: Stopping daemon
[+33.00s] DEBUG: Exiting with return value 0

seat0-greeter.log

** (process:582): WARNING **: 01:35:15.209: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
** Message: 01:35:15.224: Starting lightdm-gtk-greeter 2.0.6 (Sep 30 2018, 09:14:12)
** Message: 01:35:15.226: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf

** (lightdm-gtk-greeter:585): WARNING **: 01:35:15.262: [PIDs] Failed to execute command: /usr/lib/at-spi2-core/at-spi-bus-launcher

** (lightdm-gtk-greeter:585): WARNING **: 01:35:15.263: [PIDs] Failed to execute command: upstart

** (lightdm-gtk-greeter:585): WARNING **: 01:35:15.291: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:15.305: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:16.953: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:17.599: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:17.629: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:18.239: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:21.956: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:27.965: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:27.981: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.000: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.016: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.033: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.049: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.065: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.083: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.098: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.115: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.132: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:28.148: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:30.268: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:30.285: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:30.302: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:585): Gtk-WARNING **: 01:35:30.339: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)
Gdk-Message: 01:35:30.340: lightdm-gtk-greeter: Fatal IO error 4 (Interrupted system call) on X server :0.

inxi -Fxzb

System:    Host: archPC Kernel: 4.20.4-arch1-1-ARCH x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Xfce 4.12.4 
           Distro: Arch Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF Z370-PRO GAMING v: Rev 1.xx serial: <filter> UEFI: American Megatrends 
           v: 0215 date: 09/05/2017 
CPU:       Topology: 6-Core model: Intel Core i5-8400 bits: 64 type: MCP arch: Kaby Lake rev: A L2 cache: 9216 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 33708 
           Speed: 800 MHz min/max: 800/4000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 801 6: 800 
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nouveau v: kernel bus ID: 01:00.0 
           Display: tty server: X.Org 1.20.3 driver: modesetting unloaded: vesa resolution: 1920x1080~60Hz 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k4.20.4-arch1-1-ARCH 
Network:   Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: f000 bus ID: 00:1f.6 
           IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.14 TiB used: 3.55 GiB (0.3%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 850 PRO 256GB size: 238.47 GiB 
           ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-75WN4A0 size: 931.51 GiB 
Partition: ID-1: / size: 19.56 GiB used: 3.48 GiB (17.8%) fs: ext4 dev: /dev/sda5 
           ID-2: /boot size: 96.0 MiB used: 64.4 MiB (67.1%) fs: vfat dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 32.0 C mobo: N/A gpu: nouveau temp: 32 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 164 Uptime: 23m Memory: 7.72 GiB used: 950.7 MiB (12.0%) Init: systemd Compilers: gcc: 8.2.1 Shell: bash 
           v: 5.0.0 inxi: 3.0.30 

systemctl status lightdm

* lightdm.service - Light Display Manager
   Loaded: loaded (/usr/lib/systemd/system/lightdm.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:lightdm(1)

Beitrag geändert von drei86er (27.01.2019 02:04:06)

Offline

#2 29.01.2019 00:20:39

tmvx
Mitglied

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

hast du das ganze xorg paket installiert bei mir wars auch so ging aber nach dem installieren von xorg ohne probleme

Offline

#3 29.01.2019 11:03:33

GerBra(offline)
Gast

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

drei86er schrieb:

Habe lightdm als DisplayManager installiert. Wenn dieser enabled ist, wird mein Bildschirm beim starten schwarz und reagiert nicht mehr.
Wenn ich lightdm jedoch manuell starte, kann ich es ausführen. Mein Desktop Theme xfce kann ich ebenfalls manuell starten.

Hat jemand eine Idee woran es liegen könnte?

Ich kenne mich mit ligthdm nicht aus, aber im Wiki gibt es einen Tip, der ggf. auch auf dein Problem passen könnte:
https://wiki.archlinux.org/index.php/Li … TTY_output
Auch wenn du keine TTYs siehst, sondern "nur schwarz"<g> wäre es ein Versuch wert.

#4 29.01.2019 11:24:35

primus
Mitglied

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

Hallo drei86er,

[Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf

Poste mal deine: /etc/lightdm/lightdm-gtk-greeter.conf

Gruß/Primus

Beitrag geändert von primus (29.01.2019 11:25:15)

Offline

#5 29.01.2019 11:42:03

primus
Mitglied

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

Evtl.ist hier was dabei was zur Lösung beiträgt:  "LightDM Black Screen on Start [Solved]"
https://bbs.archlinux.org/viewtopic.php?id=242232

Beitrag geändert von primus (29.01.2019 14:21:25)

Offline

#6 29.01.2019 18:58:05

schard
Mitglied

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

Was sagt, unmittelbar nach dem Start

cat /proc/sys/kernel/random/entropy_avail 

Beitrag geändert von schard (29.01.2019 18:58:40)

Offline

#7 03.02.2019 17:42:31

drei86er
Mitglied

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

Hallo allerseits,

vielen Dank für alle die sich bereits geäußert haben. Ich war letzte Woche verreicht und hatte keine Möglichkeit an dem Problem zu arbeiten.

@primus

# LightDM GTK+ Configuration
# Available configuration options listed below.
#
# Appearance:
#  theme-name = GTK+ theme to use
#  icon-theme-name = Icon theme to use
#  cursor-theme-name = Cursor theme to use
#  cursor-theme-size = Cursor size to use
#  background = Background file to use, either an image path or a color (e.g. #772953)
#  user-background = false|true ("true" by default)  Display user background (if available)
#  transition-duration = Length of time (in milliseconds) to transition between background images ("500" by default)
#  transition-type = ease-in-out|linear|none  ("ease-in-out" by default)
#
# Fonts:
#  font-name = Font to use
#  xft-antialias = false|true  Whether to antialias Xft fonts
#  xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
#  xft-hintstyle = none|slight|medium|hintfull  What degree of hinting to use
#  xft-rgba = none|rgb|bgr|vrgb|vbgr  Type of subpixel antialiasing
#
# Login window:
#  active-monitor = Monitor to display greeter window (name or number). Use #cursor value to display greeter at monitor with cursor. Can be a semicolon separated list
#  position = x y ("50% 50%" by default)  Login window position
#  default-user-image = Image used as default user icon, path or #icon-name
#  hide-user-image = false|true ("false" by default)
#
# Panel:
#  panel-position = top|bottom ("top" by default)
#  clock-format = strftime-format string, e.g. %H:%M
#  indicators = semi-colon ";" separated list of allowed indicator modules. Built-in indicators include "~a11y", "~language", "~session", "~power", "~clock", "~host", "~spacer". Unity indicators can be represented by short name (e.g. "sound", "power"), service file name, or absolute path
#
# Accessibility:
#  a11y-states = states of accessibility features: "name" - save state on exit, "-name" - disabled at start (default value for unlisted), "+name" - enabled at start. Allowed names: contrast, font, keyboard, reader.
#  keyboard = command to launch on-screen keyboard (e.g. "onboard")
#  keyboard-position = x y[;width height] ("50%,center -0;50% 25%" by default)  Works only for "onboard"
#  reader = command to launch screen reader (e.g. "orca")
#  at-spi-enabled = false|true ("true" by default) Enables accessibility at-spi-command if the greeter is built with it enabled
#
# Security:
#  allow-debugging = false|true ("false" by default)
#  screensaver-timeout = Timeout (in seconds) until the screen blanks when the greeter is called as lockscreen
#
# Template for per-monitor configuration:
#  [monitor: name]
#  background = overrides default value
#  user-background = overrides default value
#  laptop = false|true ("false" by default) Marks monitor as laptop display
#  transition-duration = overrides default value
#
[greeter]
#background=
#user-background=
#theme-name=
#icon-theme-name=
#font-name=
#xft-antialias=
#xft-dpi=
#xft-hintstyle=
#xft-rgba=
#indicators=
#clock-format=
#keyboard=
#reader=
#position=
#screensaver-timeout=

Offline

#8 03.02.2019 17:52:14

drei86er
Mitglied

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

schard schrieb:

Was sagt, unmittelbar nach dem Start

cat /proc/sys/kernel/random/entropy_avail 

Hi schard,


cat /proc/sys/kernel/random/entropy_avail -> 430 (direkt nach login mit meinem user)


Steigt dann relativ schnell und ist nach ca. 30 Sekunden bei knapp 900


Gruß,

Tobias

Offline

#9 04.02.2019 11:46:22

schard
Mitglied

Re: LightDM startet nicht beim Bootvorgang -> Schwarzer Bildschirm

Das ist zu wenig.
Installiere und aktiviere haveged.

pacman -Syu haveged
systemctl enable --now haveged

Dass die Entropie bei weiterer Benutzung steigt, ist normal, da der Kernel sie aus System Interrupts (Tastatureingaben und Mausevents, etc.) generiert.

Beitrag geändert von schard (04.02.2019 11:47:52)

Offline

Schnellantwort auf dieses Thema

Schreibe deinen Beitrag und versende ihn
Deine Antwort

Fußzeile des Forums