Bookworm/xfce + nvidia drivers -- blank after light-locker-command

[bitrat]

Hi,

for some background, check this thread: viewtopic.php?p=797055

I've installed the non-free nvidia video driver because my card doesn't support the open source offering. Nor does nouveau function correctly on my system.

Now, the graphics seem to be working, except that the desktop remains blank with a (sometimes laggy) mouse pointer after screen locking.

The screen locker in use is `light-locker-command` via `xflock4`

It was with some corresponding shock that I read this (somewhat fatuously shocked) rebuke here:

the machine is purpose-built for CUDA programming

Then why are you using a distribution that has no official support for non-free video drivers?
Can you please confirm that nouveau fixes this for the benefit of those who run Debian as the developers intend?

Just to save my doing the kind of minutely detailed research required before risking a plunge into Debian that @micon expects from @Head_on_a_Stick, could anybody tell me if these caveats for Debian 9 are also true for Debian 12?

I'd just like to lock my screen. I don't care about powering anything off. I don't see why this should involve the video driver. Wouldn't a modal dialog, always on top, and requiring a password to close, pretty much accomplish the same thing? Is there an option like this already, or will I have to write one?

Sorry if this seems like a strange mix of experience and naivete, and for any passive aggressive jibes, but my patience is wearing thin. No blame or responsibility is implied toward anybody other than myself!

Ps: Might this advice be useful?

You need to add bookworm-updates to your sources and install the nvidia-driver from there, currently v.525.147.05-7~deb12u1

Code: Select all

deb https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware

[Linuxgaming1824]

If your graphics driver is functioning normally, as you expect it should, and you are having problems with your lock screen, than you should focus your attention on the lock screen.

There are apps for configuring your lock screens behavior. On xfce the login/lock screen is dealt with via lightlocker, so look into the apps for configuring lightlocker and see if they help fix your problem.

If you can't fix your problem, after searching and trying ways to configure lightlockers behavior, you
can try to ask for help again, and report the changes you have made, what you tried, why you tried it,
you might also report some basic details, in a simple fashion about your overall system. What kind of computer? Desktop, laptop? Special monitor? You say you have...Bookworm (xfce)

but...

how did you install your graphics drivers?
how did you perform updates?
what kind of computer do you have?
any other important information related to your problem you can think of?
what's your specific problem? (lightlocker?)

[bitrat]

If your graphics driver is functioning normally, as you expect it should, and you are having problems with your lock screen, than you should focus your attention on the lock screen.

There are apps for configuring your lock screens behavior. On xfce the login/lock screen is dealt with via lightlocker, so look into the apps for configuring lightlocker and see if they help fix your problem.

If you can't fix your problem, after searching and trying ways to configure lightlockers behavior, you
can try to ask for help again, and report the changes you have made, what you tried, why you tried it,
you might also report some basic details, in a simple fashion about your overall system. What kind of computer? Desktop, laptop? Special monitor? You say you have...Bookworm (xfce)

but...

how did you install your graphics drivers?
how did you perform updates?
what kind of computer do you have?
any other important information related to your problem you can think of?
what's your specific problem? (lightlocker?)

Thanks.

I've since discovered the desktop also remains blank after switching to a different terminal and back, so I don't think it's the locker. The other details are in the links to previous threads.

I've bought an ssd and I'll install ubuntu and use that for a while, just to see if there's still a graphics problem. I feel as if I've solved the root problem with my graphics on Debian (by installing non-open source nvidia drivers) but that my driver reinstallation has left some glitches somewhere. I think there may be a remaining nouveau km involved but don't have time to spelunk it right now.

I'd just do a fresh Debian install, but I need to document the process first and maybe script it. What I have now is a long way from a bare system...

[Linuxgaming1824]

Do you know what your power management settings are set to?

Lightlocker interacts with a few limited processes such as power manager

(i think you're actually describing normal lock screen behavior, but are jumping to conclusions about how it should work, and talking about a variety of unrelated issues and repeatedly pointing to them...and now you've logged off and can't respond so....)

[bitrat]

Do you know what your power management settings are set to?

Lightlocker interacts with a few limited processes such as power manager

(i think you're actually describing normal lock screen behavior, but are jumping to conclusions about how it should work, and talking about a variety of unrelated issues and repeatedly pointing to them...and now you've logged off and can't respond so....)

Oh, sorry, must have timed out.

All my power manager settings are do nothing and never.

I just did

Code: Select all

sudo apt autoremove *nouveau* --purge

which has removed a huge amount of stuff including a few things I've reinstalled. I'll see what happens when I reboot, lol.

[sunrat]

I just did

Code: Select all

sudo apt autoremove *nouveau* --purge

which has removed a huge amount of stuff including a few things I've reinstalled. I'll see what happens when I reboot, lol.

That was probably a Really Bad Idea™.
I just did a simulated purge of *nouveau* and it would have pretty much deleted the whole system.
Nouveau is usually simply blacklisted by creating a blacklist file which is done automatically by nvidia-driver installation process.

[bitrat]

I just did

Code: Select all

sudo apt autoremove *nouveau* --purge

which has removed a huge amount of stuff including a few things I've reinstalled. I'll see what happens when I reboot, lol.

That was probably a Really Bad Idea™.
I just did a simulated purge of *nouveau* and it would have pretty much deleted the whole system.
Nouveau is usually simply blacklisted by creating a blacklist file which is done automatically by nvidia-driver installation process.

Haha, yes it was a bit impulsive...

If it manages to start after a reboot, I'll be happy. Otherwise I'll just be forced to rebuild.

The nvidia install didn't blacklist nouveau for some reason, but I did it manually. It didn't fix the problem so I reverted, but I should have persisted with that approach, as you say.

Can you explain exactly what apt did with that command. I was initially expecting it to just remove nouveau packages, rather than everything configured to depend on them. When I saw what it was going to do I decided to take the nuclear approach anyway.

Just out of interest, do you know if I can make the Debian install use the nvidia drivers from the start, without installing nouveau?

[sunrat]

Can you explain exactly what apt did with that command. I was initially expecting it to just remove nouveau packages, rather than everything configured to depend on them.

Can't explain, the output was way too long to read. When I read how many packages where flagged to remove I just thought "Nah, don't do that".
And yes, it's all about dependencies.

[bitrat]

Can you explain exactly what apt did with that command. I was initially expecting it to just remove nouveau packages, rather than everything configured to depend on them.

Can't explain, the output was way too long to read. When I read how many packages where flagged to remove I just thought "Nah, don't do that".
And yes, it's all about dependencies.

The bottom line is that I don't want applications silently loading nouveau libraries. Anyway, we'll see what happens.

My goal is to have a system that works with my hardware etc, that I can wipe and reinstall with minimal effort. Ultimately, I'd like my home directory to be distro agnostic, but that may be a bit of a pipe dream...


Another question:
I get this...

Code: Select all

$ atril all.pdf
atril: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory

It looks like installing the nvidia drivers put the library here:

Code: Select all

/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.7.0

..and this works:

Code: Select all

LD_PRELOAD=/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1 atril all.pdf

There are a bunch of libGL's, but only a libGL.so in /usr/lib/mesa-diverted

Code: Select all

$ sudo find /usr/lib -name libGL*.so*
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2.1.0
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLX_indirect.so.0
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.7.0
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
/usr/lib/x86_64-linux-gnu/libGLU.so.1.3.1
/usr/lib/x86_64-linux-gnu/libGLU.so.1
/usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
/usr/lib/x86_64-linux-gnu/libGLdispatch.so.0.0.0
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2
/usr/lib/x86_64-linux-gnu/libGLX.so.0
/usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0.0.0
/usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0

Not sure if I should manually add a link from (I suppose) /usr/lib/x86_64-linux-gnu/libGL.so.1

Anyway, I'll try a restart first as it may not even boot...

UPDATE: after reboot...

No X server, with lots of stuff missing....

After reinstalling X (details to come) I managed to get my desktop back...

Now I'll see if it returns after switching terminals ..or screen lock. Hold your breath...

No! Still losing the window manager after lock, but I think this (from /var/log/Xorg.0.log) is the smoking gun:

Code: Select all

[   102.447] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[   102.491] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[   102.491] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[   102.491] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[   102.491] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[   102.491] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[   102.491] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[   102.491] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[   102.491] (II) NVIDIA(0):     Config Options in the README.

I'll investigate once I figure out what particular 'README' they're referring to... There being a mere 3418 files named README on my system.

Also, I'm getting both a /var/log/Xorg.0.log and a /var/log/Xorg.1.log

This thread confirms my suspicion that a second X server is being started. I need to look more closely at the start times. They both have identical contents and NVIDIA info as below.

$ grep 'NVIDIA(0):' /var/log/Xorg.0.log

Code: Select all

[    32.388] (II) NVIDIA(0): Creating default Display subsection in Screen section
[    32.388] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    32.388] (==) NVIDIA(0): RGB weight 888
[    32.388] (==) NVIDIA(0): Default visual is TrueColor
[    32.388] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    32.505] (**) NVIDIA(0): Enabling 2D acceleration
[    38.152] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[    38.152] (--) NVIDIA(0):     CRT-0
[    38.152] (--) NVIDIA(0):     DFP-0
[    38.152] (--) NVIDIA(0):     DFP-1 (boot)
[    38.152] (--) NVIDIA(0):     DFP-2
[    38.152] (--) NVIDIA(0):     DFP-3
[    38.152] (--) NVIDIA(0):     DFP-4
[    38.155] (II) NVIDIA(0): NVIDIA GPU Quadro K2200 (GM107GL-A) at PCI:1:0:0 (GPU-0)
[    38.155] (--) NVIDIA(0): Memory: 4194304 kBytes
[    38.155] (--) NVIDIA(0): VideoBIOS: 82.07.5a.00.0a
[    38.155] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    38.222] (==) NVIDIA(0): 
[    38.222] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    38.222] (==) NVIDIA(0):     will be used as the requested mode.
[    38.222] (==) NVIDIA(0): 
[    38.223] (II) NVIDIA(0): Validated MetaModes:
[    38.223] (II) NVIDIA(0):     "DFP-1:nvidia-auto-select"
[    38.223] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[    38.229] (--) NVIDIA(0): DPI set to (93, 94); computed from "UseEdidDpi" X config
[    38.229] (--) NVIDIA(0):     option
[    38.232] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    38.232] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    38.232] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    38.232] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    38.232] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    38.232] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    38.232] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    38.232] (II) NVIDIA(0):     Config Options in the README.
[    38.399] (II) NVIDIA(0): Setting mode "DFP-1:nvidia-auto-select"
[    38.557] (==) NVIDIA(0): Disabling shared memory pixmaps
[    38.557] (==) NVIDIA(0): Backing store enabled
[    38.557] (==) NVIDIA(0): Silken mouse enabled
[    38.560] (==) NVIDIA(0): DPMS enabled
[    38.561] (II) NVIDIA(0): [DRI2] Setup complete
[    38.561] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia

$ diff <(grep 'NVIDIA(0):' /var/log/Xorg.0.log | sed -E 's/[ .0-9]{10}]//') <(grep 'NVIDIA(0):' /var/log/Xorg.1.log | sed -E 's/[ .0-9]{10}]//')
...returns no difference.

Looks like Xorg.1.log is created and written to first, followed immediately by Xorg.0.log

Is the ordinal a log roll number? I thought it was the screen number...

Code: Select all

$ stat /var/log/Xorg.0.log
  File: /var/log/Xorg.0.log
  Size: 27222     	Blocks: 56         IO Block: 4096   regular file
Device: 8,20	Inode: 1442215     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-04-19 17:57:52.548940834 +1200
Modify: 2024-04-19 17:58:44.388941324 +1200
Change: 2024-04-19 17:58:44.388941324 +1200
 Birth: 2024-04-19 17:57:52.548940834 +1200

$ stat /var/log/Xorg.1.log
  File: /var/log/Xorg.1.log
  Size: 25334     	Blocks: 56         IO Block: 4096   regular file
Device: 8,20	Inode: 1443006     Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2024-04-19 17:36:52.029107407 +1200
Modify: 2024-04-19 17:11:31.456510876 +1200
Change: 2024-04-19 17:11:31.456510876 +1200
 Birth: 2024-04-19 17:11:12.872510816 +1200

pstree -a

Code: Select all

systemd
  .
  .
  .
  |-lightdm
  |   |-Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  |   |   `-{Xorg}
  |   |-lightdm --session-child 15 26
  |   |   |-xfce4-session
  |   |   |   |-applet.py /usr/share/system-config-printer/applet.py
  |   |   |   |-light-locker
  |   |   |   |   `-3*[{light-locker}]
  |   |   |   |-nm-applet
  |   |   |   |   `-3*[{nm-applet}]
  |   |   |   |-polkit-gnome-au
  |   |   |   |   `-2*[{polkit-gnome-au}]
  |   |   |   |-ssh-agent /usr/bin/im-launch x-session-manager
  |   |   |   |-xfce4-panel --display :0.0 --sm-client-id 279b59ed8-b008-4b98-aa07-a6febdd4f62f
  |   |   |   |   |-panel-10-notifi /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libnotification-plugin.so 102516583
  |   |   |   |   |   `-2*[{panel-10-notifi}]
  |   |   |   |   .
  |   |   |   |   .
  |   |   |   |   .
  |   |   |   |   |-panel-9-power-m /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libxfce4powermanager.so 9 25165838p
  |   |   |   |   |   `-2*[{panel-9-power-m}]
  |   |   |   |   `-10*[{xfce4-panel}]
  |   |   |   |-xfce4-power-man --restart --sm-client-id 257eb3672-4484-42d9-a39c-6767d910ffc0
  |   |   |   |   `-2*[{xfce4-power-man}]
  |   |   |   |-xfdesktop --display :0.0 --sm-client-id 2a6ab4c16-27a5-4077-9ff5-35244d2fb038
  |   |   |   |   `-2*[{xfdesktop}]
  |   |   |   |-xfsettingsd --display :0.0 --sm-client-id 284d5fbc5-3d81-42a9-9925-f80929e2d9b4
  |   |   |   |   `-2*[{xfsettingsd}]
  |   |   |   |-xfwm4 --display :0.0 --sm-client-id 2decb237a-c158-4437-a79a-d2d9a76cafdd
  |   |   |   |   `-2*[{xfwm4}]
  |   |   |   |-xiccd
  |   |   |   |   `-2*[{xiccd}]
  |   |   |   `-2*[{xfce4-session}]
  |   |   `-2*[{lightdm}]
  |   `-2*[{lightdm}]