Xfce: Black screen after resuming and unlocking from standby

If none of the more specific forums is the right place to ask

Xfce: Black screen after resuming and unlocking from standby

Postby klapstul » 2019-08-31 07:46

After the upgrade to Debian 10, standby no longer works as it was working. I am using Xfce and lightdm. Xfce is configured to go to standby after closing the lid. When I open it again, the lightdm login screen shows up as expected, but once I submit my credentials, the screen suddenly turns black. However, I am still able to login into a terminal via Ctrl + Alt + F1.

The strange thing is that once I trigger standby mode via the application menu and then close and reopen my lid again, unlocking the screen works totally fine. Any ideas of what is going on here?
klapstul
 
Posts: 22
Joined: 2013-10-04 15:23

Re: Xfce: Black screen after resuming and unlocking from sta

Postby klapstul » 2019-08-31 07:56

When I set the action for closing the lid to "lock screen", I seem to encounter this bug: https://github.com/the-cavalry/light-locker/issues/114.
klapstul
 
Posts: 22
Joined: 2013-10-04 15:23

Re: Xfce: Black screen after resuming and unlocking from sta

Postby esp7 » 2019-09-20 21:04

klapstul wrote:When I set the action for closing the lid to "lock screen", I seem to encounter this bug: https://github.com/the-cavalry/light-locker/issues/114.


I just posted this in another topic as well. This issue has an easy fix. Create 20-intel.conf under /etc/X11/xorg.conf.d/ It is possible you have as well to create directory xorg.conf.d
Code: Select all
/etc/X11/xorg.conf.d/20-intel.conf

Then you add the following in 20-intel.conf and reboot your machine to have the issue solved.
Code: Select all
Section "Device"
 Identifier "Intel Graphics"
 Driver "intel"
EndSection
ThinkPad X220: i5-2520M CPU 2.5GHz - 8GB RAM 1333 MHz - SSD 860 EVO 250GB - Debian Stable - ME_cleaned
ThinkPad X230: i5-3320M CPU 3.3GHz - 8GB RAM 1600 MHz - SSD 860 EVO 500GB - Debian Stable - ME_cleaned
User avatar
esp7
 
Posts: 154
Joined: 2013-06-23 20:31

Re: Xfce: Black screen after resuming and unlocking from sta

Postby klapstul » 2019-09-29 06:58

This will make X11 fail to start on my machine. Here is the /var/log/Xorg.0.log file:

Code: Select all
[     6.825]
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[     6.826] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[     6.826] Current Operating System: Linux jens-laptop 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64
[     6.826] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 root=UUID=4b82f90b-8a7b-4f7d-bfbd-3b555c0fd0a9 ro text no_console_suspend systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
[     6.826] Build Date: 05 March 2019  08:11:12PM
[     6.826] xorg-server 2:1.20.4-1 (https://www.debian.org/support)
[     6.826] Current version of pixman: 0.36.0
[     6.826]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[     6.826] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     6.826] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 29 09:41:06 2019
[     6.826] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     6.826] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     6.826] (==) No Layout section.  Using the first Screen section.
[     6.826] (==) No screen section available. Using defaults.
[     6.826] (**) |-->Screen "Default Screen Section" (0)
[     6.826] (**) |   |-->Monitor "<default monitor>"
[     6.827] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
[     6.827] (**) |   |-->Device "Intel Graphics"
[     6.827] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
[     6.827] (==) Automatically adding devices
[     6.827] (==) Automatically enabling devices
[     6.827] (==) Automatically adding GPU devices
[     6.827] (==) Max clients allowed: 256, resource mask: 0x1fffff
[     6.827] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     6.827]    Entry deleted from font path.
[     6.827] (==) FontPath set to:
   /usr/share/fonts/X11/misc,
   /usr/share/fonts/X11/100dpi/:unscaled,
   /usr/share/fonts/X11/75dpi/:unscaled,
   /usr/share/fonts/X11/Type1,
   /usr/share/fonts/X11/100dpi,
   /usr/share/fonts/X11/75dpi,
   built-ins
[     6.827] (==) ModulePath set to "/usr/lib/xorg/modules"
[     6.827] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[     6.827] (II) Loader magic: 0x5603dca07e20
[     6.827] (II) Module ABI versions:
[     6.827]    X.Org ANSI C Emulation: 0.4
[     6.827]    X.Org Video Driver: 24.0
[     6.827]    X.Org XInput driver : 24.1
[     6.827]    X.Org Server Extension : 10.0
[     6.828] (++) using VT number 7

[     6.828] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     6.829] (II) xfree86: Adding drm device (/dev/dri/card0)
[     6.838] (--) PCI:*(0@0:2:0) 8086:1616:17aa:2226 rev 9, Mem @ 0xf0000000/16777216, 0xe0000000/268435456, I/O @ 0x00003000/64, BIOS @ 0x????????/131072
[     6.838] (II) LoadModule: "glx"
[     6.838] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     6.840] (II) Module glx: vendor="X.Org Foundation"
[     6.840]    compiled for 1.20.4, module version = 1.0.0
[     6.840]    ABI class: X.Org Server Extension, version 10.0
[     6.840] (II) LoadModule: "intel"
[     6.840] (WW) Warning, couldn't open module intel
[     6.840] (EE) Failed to load module "intel" (module does not exist, 0)
[     6.840] (EE) No drivers available.
[     6.840] (EE)
Fatal server error:
[     6.840] (EE) no screens found(EE)
[     6.840] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[     6.840] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[     6.840] (EE)
[     6.840] (EE) Server terminated with error (1). Closing log file.
klapstul
 
Posts: 22
Joined: 2013-10-04 15:23

Re: Xfce: Black screen after resuming and unlocking from sta

Postby CwF » 2019-09-29 15:55

esp7 wrote:Create 20-intel.conf under /etc/X11/xorg.conf.d/ It is possible you have as well to create directory xorg.conf.d


better to put such hint file in /usr/share/X11/xorg.conf.d/ with the others...
CwF
 
Posts: 502
Joined: 2018-06-20 15:16

Re: Xfce: Black screen after resuming and unlocking from sta

Postby reinob » 2019-09-29 17:41

klapstul wrote:This will make X11 fail to start on my machine. Here is the /var/log/Xorg.0.log file:


do you have an intel gpu? the given advice will only work in that case. for that, you'll also need to apt-get install xserver-xorg-video-intel.

and yes, if the above is all correct, you should place the file in /etc/X11/xorg.conf.d/

/usr/share/X11/xorg.conf.d/ is only touched by installing packages, you should not (have to) touch anything there. user (admin) configuration goes in /etc.
reinob
 
Posts: 743
Joined: 2014-06-30 11:42

Re: Xfce: Black screen after resuming and unlocking from sta

Postby CwF » 2019-09-29 18:44

Obviously, it's touched at every boot
Code: Select all
[     6.826] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     6.826] (==) Using system config directory "/usr/share/X11/xorg.conf.d"

I wasn't commenting on the solution, just going with my evidence...
Code: Select all
user@vm:~$ ls /usr/share/X11/xorg.conf.d/
10-amdgpu.conf  10-quirks.conf  40-libinput.conf   70-wacom.conf
10-evdev.conf   10-radeon.conf  70-synaptics.conf
user@vm:~$ ls /etc/X11/xorg.conf.d/
ls: cannot access '/etc/X11/xorg.conf.d/': No such file or directory

You can go ahead and make a new directory, or just add them to the 'others'.
This is where I put 52.vm.conf if passing a card, it will stop the boot if there is no card, etc...
CwF
 
Posts: 502
Joined: 2018-06-20 15:16

Re: Xfce: Black screen after resuming and unlocking from sta

Postby Head_on_a_Stick » 2019-09-29 18:51

CwF wrote:just going with my evidence...

How about this evidence:
Code: Select all
E485:~$ grep -iA2 'do not edit' /usr/share/X11/xorg.conf.d/70-synaptics.conf                        <
# DO NOT EDIT THIS FILE, your distribution will likely overwrite
# it when updating. Copy (and rename) this file into
# /etc/X11/xorg.conf.d first.
E485:~$

See also hier(7).
Don't break DebianHow to report bugs

SharpBang GNU/Linux — a pre-configured Openbox/Tint2 desktop running on Debian stable
User avatar
Head_on_a_Stick
 
Posts: 10613
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Xfce: Black screen after resuming and unlocking from sta

Postby CwF » 2019-09-29 19:01

If you edit a file there, it can and will be updated by a system update at any time, thereby wiping out a user edit. Duh? That's not what I said. I've had no issue adding a file there, adding and not editing...
CwF
 
Posts: 502
Joined: 2018-06-20 15:16

Re: Xfce: Black screen after resuming and unlocking from sta

Postby Head_on_a_Stick » 2019-09-29 19:07

The "correct" location for local configuration files is /etc/X11, as stated in hier(7). Putting the files in /usr/share/X11 certainly works but it's not where they're supposed to go.

Anyway, this is all off-topic because the configuration file breaks the OP's desktop.

@OP: have you checked the LightDM logs?
Don't break DebianHow to report bugs

SharpBang GNU/Linux — a pre-configured Openbox/Tint2 desktop running on Debian stable
User avatar
Head_on_a_Stick
 
Posts: 10613
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Xfce: Black screen after resuming and unlocking from sta

Postby stevepusser » 2019-09-30 00:31

OP, what is your GPU, anyway?
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Clipgrab 3.8.6, Hedgewars 1.0.0, PulseEffects 4.6.8, Telegram-desktop 1.8.15, Pale Moon 28.7.2, KeepassXC 2.5.1
User avatar
stevepusser
 
Posts: 11259
Joined: 2009-10-06 05:53

Re: Xfce: Black screen after resuming and unlocking from sta

Postby klapstul » 2019-09-30 05:48

Indeed I have an Intel GPU.

Code: Select all
$ lspci|grep -i vga
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09)
klapstul
 
Posts: 22
Joined: 2013-10-04 15:23

Re: Xfce: Black screen after resuming and unlocking from sta

Postby klapstul » 2019-09-30 06:04

I had already inspected the lightdm log earlier with no really helpful finding. This is the output upon closing, re-opening the lid and logging in again:

Code: Select all
[+16590.94s] DEBUG: Seat seat0 changes active session to 13
[+16590.94s] DEBUG: Session 13 is already active
[+16592.60s] DEBUG: Seat seat0: Creating greeter session
[+16592.61s] DEBUG: Seat seat0: Creating display server of type x
[+16592.61s] DEBUG: Using VT 8
[+16592.61s] DEBUG: Seat seat0: Starting local X display on VT 8
[+16592.61s] DEBUG: XServer 1: Logging to /var/log/lightdm/x-1.log
[+16592.61s] DEBUG: XServer 1: Writing X server authority to /var/run/lightdm/root/:1
[+16592.61s] DEBUG: XServer 1: Launching X Server
[+16592.61s] DEBUG: Launching process 6591: /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
[+16592.61s] DEBUG: XServer 1: Waiting for ready signal from X server :1
[+16592.96s] DEBUG: Seat seat0 changes active session to
[+16594.32s] DEBUG: Got signal 10 from process 6591
[+16594.32s] DEBUG: XServer 1: Got signal from X server :1
[+16594.32s] DEBUG: XServer 1: Connecting to XServer :1
[+16594.34s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified)
[+16594.35s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+16594.35s] DEBUG: Session pid=6600: Started with service 'lightdm-greeter', username 'lightdm'
[+16594.36s] DEBUG: Session pid=6600: Authentication complete with return value 0: Success
[+16594.36s] DEBUG: Seat seat0: Session authenticated, running command
[+16594.36s] DEBUG: Session pid=6600: Running command /usr/sbin/lightdm-gtk-greeter
[+16594.36s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+16594.36s] DEBUG: Session pid=6600: Logging to /var/log/lightdm/seat0-greeter.log
[+16594.56s] DEBUG: Activating VT 8
[+16594.56s] DEBUG: Locking login1 session 13
[+16594.56s] DEBUG: Activating login1 session c5
[+16594.56s] DEBUG: Seat seat0 changes active session to c5
[+16594.56s] DEBUG: Session c5 is already active
[+16594.81s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false
[+16595.11s] DEBUG: Greeter start authentication
[+16595.11s] DEBUG: Session pid=6645: Started with service 'lightdm', username '(null)'
[+16595.12s] DEBUG: Session pid=6645: Got 1 message(s) from PAM
[+16595.12s] DEBUG: Prompt greeter with 1 message(s)
[+16596.29s] DEBUG: Greeter start authentication for xyz
[+16596.29s] DEBUG: Session pid=6645: Sending SIGTERM
[+16596.29s] DEBUG: Session pid=6647: Started with service 'lightdm', username 'xyz'
[+16596.29s] DEBUG: Session pid=6645: Terminated with signal 15
[+16596.29s] DEBUG: Session: Failed during authentication
[+16596.29s] DEBUG: Seat seat0: Session stopped
[+16596.30s] DEBUG: Session pid=6647: Got 1 message(s) from PAM
[+16596.30s] DEBUG: Prompt greeter with 1 message(s)
[+16598.59s] DEBUG: Continue authentication
[+16598.61s] DEBUG: Session pid=6647: Authentication complete with return value 0: Success
[+16598.61s] DEBUG: Authenticate result for user xyz: Success
[+16598.61s] DEBUG: User xyz authorized
[+16598.62s] DEBUG: Greeter sets language de_DE.utf8
[+16598.65s] DEBUG: Greeter requests session xfce
[+16598.65s] DEBUG: Seat seat0: Returning to existing user session xyz
[+16598.65s] DEBUG: Unlocking login1 session 13
[+16598.65s] DEBUG: Activating VT 7
[+16598.99s] DEBUG: Seat seat0: Stopping greeter
[+16598.99s] DEBUG: Terminating login1 session c5
[+16599.01s] DEBUG: Session pid=6600: Sending SIGTERM
[+16599.01s] DEBUG: Activating login1 session 13
[+16599.02s] DEBUG: Session pid=6647: Exited with return value 0
[+16599.02s] DEBUG: Seat seat0: Session stopped
[+16599.02s] DEBUG: Seat seat0 changes active session to 13
[+16599.02s] DEBUG: Session 13 is already active
[+16599.04s] DEBUG: Greeter closed communication channel
[+16599.04s] DEBUG: Session pid=6600: Exited with return value 0
[+16599.04s] DEBUG: Seat seat0: Session stopped
[+16599.04s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+16599.04s] DEBUG: Sending signal 15 to process 6591
[+16599.30s] DEBUG: Process 6591 exited with return value 0
[+16599.30s] DEBUG: XServer 1: X server stopped
[+16599.30s] DEBUG: Releasing VT 8
[+16599.30s] DEBUG: XServer 1: Removing X server authority /var/run/lightdm/root/:1
[+16599.30s] DEBUG: Seat seat0: Display server stopped
[+16604.50s] DEBUG: Seat seat0 changes active session to 10


The line
Code: Select all
[+16596.29s] DEBUG: Session pid=6645: Terminated with signal 15

probably just indicates normal behaviour as written here: https://access.redhat.com/solutions/737033.
klapstul
 
Posts: 22
Joined: 2013-10-04 15:23

Re: Xfce: Black screen after resuming and unlocking from sta

Postby klapstul » 2019-09-30 08:28

The reason why this intel config file broke my Xorg server is because for some reason I had uninstalled xserver-xorg-video-intel as described here: https://wiki.debian.org/GraphicsCard#Intel. This didn't actually make any sense so I installed the package back again and now X starts flawlessly and even the issue with the lock screen not being shown after opening the lid whilst not coming from standby mode is solved (except I have to hit a single key or a mouse button to make the screen show up again).

However, if I set the action for closing the lid to "go to standby mode" (which is the way I want it to behave), the problem still persists.
klapstul
 
Posts: 22
Joined: 2013-10-04 15:23

Re: Xfce: Black screen after resuming and unlocking from sta

Postby klapstul » 2019-09-30 09:08

When I extend my /etc/X11/xorg.conf.d/20-intel.conf as described here https://bbs.archlinux.org/viewtopic.php?pid=1581078#p1581078 and turn off the option "lock screen when system is put into power save mode" from the Xfce power setting menu, then – but only then – wakeup from standby mode works. If I omit either the additional line denoting a specific "acceleration mode" (only god knows what it means) or turn the locking feature on again, I will be locked out from my X session with no way to access it but to force-ably restart lightdm.

This sucks ...
klapstul
 
Posts: 22
Joined: 2013-10-04 15:23

Next

Return to General Questions

Who is online

Users browsing this forum: No registered users and 13 guests

fashionable