This is a new and bug release in the 560.xx series. Bug fixes: https://www.nvidia.com/en-us/drivers/details/230918/
(In reply to Giuseppe Ghibò from comment #0) > This is a new and bug release in the 560.xx series. Bug fixes: s/bug release/bug fix release/
Created attachment 14675 [details] files list files list
Keywords: (none) => advisory
MGA9-64 Plasma, i5-7500, Nvidia Quadro K620 graphics, server and desktop kernels. Updated nvidia-current first, and that was OK with both kernels, but... When I attempted to use MCC to switch to the newfeature driver, I get a message that x11-driver-video-nvidia-newfeature cannot be installed due to unsatisfied libgbm.so.1. So I didn't get very far.
CC: (none) => andrewsfarm
(In reply to Thomas Andrews from comment #3) > MGA9-64 Plasma, i5-7500, Nvidia Quadro K620 graphics, server and desktop > kernels. > > Updated nvidia-current first, and that was OK with both kernels, but... > > When I attempted to use MCC to switch to the newfeature driver, I get a > message that x11-driver-video-nvidia-newfeature cannot be installed due to > unsatisfied libgbm.so.1. > > So I didn't get very far. Looks like this need mesa packages in testing
Depends on: (none) => 33571
I see that as a possibility, after a bit of investigation. But should it be needing that specific libgbm.so.1? The current tainted version of the package is installed, and the nvidia-current candidate was OK with it.
that libgbm.so.1 required should be in the 32bit repo (either core or tainted).
So in order to install the newfeature driver on a 64-bit system, you have to activate the 32-bit repos? It can't use the libgbm.so.1 that's a file in the lib64gbm1 (tainted or core) package? That doesn't sound right.
I updated to the 64-bit core mesa packages, and tried installing the newfeature driver again without activating the 32-bit repos. Now it says it needs libdrm.so.2. There's one of them in the lib64drm2 package, installed in /usr/lib64, as is libgbm.so.1. Could it be looking for these libraries in the wrong spot?
Have to figure out why it triggered a new dep of a 32bit library, at least for the non-full package, and eventually filter out the dependency from the main package, also because *-newfeature would be, at some point, the next *-current series. In the meanwhile see if adding 32bit repos would fix the problem.
After adding the 32-bit repos, XFdrake downloaded some 32-bit packages, but it happened too fast to see what they were. The newfeature driver installed successfully, and looks OK on a quick check after the reboot, except that autologin was again disabled, like it was the last time we tried a newfeature driver.
It's weird the autologin missed. Maybe crashed some process. We might try to collect some core, enabling core generation with: sysctl -w kernel.core_uses_pid=0 sysctl -w kernel.core_pattern="/var/tmp/%e_%t_%s_uid%u.core" [this is volatile, so next boot is disabled] then try to see whether with autologin, some core, in /var/tmp/ is generated.
(In reply to Thomas Andrews from comment #10) > it happened too fast to see what they were. The newfeature driver installed journalctl -b | grep -e \\[RPM\\] should show what happening on package installing (but I'm pretty sure there is some other "proper" journalctl option to see that info in a more fashioned way...).
(In reply to Giuseppe Ghibò from comment #11) > It's weird the autologin missed. Maybe crashed some process. We might try to > collect some core, enabling core generation with: > > sysctl -w kernel.core_uses_pid=0 > sysctl -w kernel.core_pattern="/var/tmp/%e_%t_%s_uid%u.core" > > [this is volatile, so next boot is disabled] > > then try to see whether with autologin, some core, in /var/tmp/ is generated. Oops, I forgot that at the autologin you won't have the console prompt where to type such commands, so we have to find another way...
Created attachment 14682 [details] journal with autologin disabled For what it's worth, a journal created within a few minutes of booting with autologin having been disabled
(In reply to Giuseppe Ghibò from comment #11) > It's weird the autologin missed. Maybe crashed some process. We might try to > collect some core, enabling core generation with: > > sysctl -w kernel.core_uses_pid=0 > sysctl -w kernel.core_pattern="/var/tmp/%e_%t_%s_uid%u.core" > > [this is volatile, so next boot is disabled] > > then try to see whether with autologin, some core, in /var/tmp/ is generated. While digging into this I found a sort of bug in our systemd package that made our core dump experience "incomplete". We had this line: https://svnweb.mageia.org/packages/updates/9/systemd/current/SPECS/systemd.spec?revision=2087162&view=markup#l405 (ditto for cauldron) which we disabled proper systemd core dumps at some point (probably because at that time that feature was incomplete in systemd) and then remained as is our next releases. This feature has been perfectioned in systemd upstream so I think we should re-enable it in next systemd builds. Anyway, for now to get coredumps just add a file /etc/sysctl.d/99-coredump.conf containing the lines: kernel.core_pattern=|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h kernel.core_pipe_limit=16 fs.suid_dumpable=2 then reboot. If some program crashes it creates a core, and you can catch with coredumpctl list
Sorry this took so long, but I did as suggested, and this is the result: # coredumpctl list TIME PID UID GID SIG COREFILE EXE SIZE Mon 2024-10-14 20:28:33 EDT 3001 0 0 SIGABRT present /usr/libexec/Xorg 1.8M
(In reply to Giuseppe Ghibò from comment #15) > While digging into this I found a sort of bug in our systemd package that > made our core dump experience "incomplete". We had this line: > > https://svnweb.mageia.org/packages/updates/9/systemd/current/SPECS/systemd. > spec?revision=2087162&view=markup#l405 > > (ditto for cauldron) which we disabled proper systemd core dumps at some > point (probably because at that time that feature was incomplete in systemd) > and then remained as is our next releases. This feature has been > perfectioned in systemd upstream so I think we should re-enable it in next > systemd builds. If not already implemented, please open a bug on it so it do not get forgotten!
CC: (none) => fri
thanks for reminding. done. now there are new commands: coredumpctl list # list dump collected coredumpctl info <PID> # show infos about a PID listed in coredumpctl list coredumpctl debug <PID> # list debugging informations (requires -debug packages for getting full verbose debugging) for the crashes whose coredump has not yet been discarded/cleaned.
There is a new version nvidia-newfeature-560.35.03-2.mga9.nonfree which should address, at least, the gbm 32bit deps.
Source RPM: nvidia-newfeature-560.35.03-1.mga9.nonfree => nvidia-newfeature-560.35.03-2.mga9.nonfree
Comment on attachment 14675 [details] files list Release 9 Source RPMS nvidia-newfeature-560.35.03-2.mga9.nonfree Binaries RPMS in x86_64 Repository: 9-x86_64-nonfree-updates_testing dkms-nvidia-newfeature-560.35.03-2.mga9.nonfree nvidia-newfeature-all-560.35.03-2.mga9.nonfree nvidia-newfeature-cuda-opencl-560.35.03-2.mga9.nonfree nvidia-newfeature-devel-560.35.03-2.mga9.nonfree nvidia-newfeature-doc-html-560.35.03-2.mga9.nonfree nvidia-newfeature-lib32-560.35.03-2.mga9.nonfree nvidia-newfeature-utils-560.35.03-2.mga9.nonfree x11-driver-video-nvidia-newfeature-560.35.03-2.mga9.nonfree
This system has both server and desktop kernels installed. Booted into the server kernel, got updates (included systemd), used MCC to switch to nvidia-current, rebooted into the desktop kernel, nvidia-current built and installed, and autologin function was restored. Updated to the 6.6.58 kernels currently under test, rebooted into the desktop kernel, downloaded newfeature packages using qarepo, used XFdrake from the command line to switch to the newfeature driver, rebooted into the desktop kernel again, and autologin had been disabled. Other than disabling autologin, I don't see any problems with this on this hardware. [tom@localhost ~]$ inxi -MCG Machine: Type: Desktop Mobo: ASUSTeK model: PRIME Q270M-C v: Rev X.0x serial: <superuser required> UEFI: American Megatrends v: 2201 date: 12/21/2023 CPU: Info: quad core model: Intel Core i5-7500 bits: 64 type: MCP cache: L2: 1024 KiB Speed (MHz): avg: 3717 min/max: 800/3800 cores: 1: 3690 2: 3796 3: 3686 4: 3699 Graphics: Device-1: NVIDIA GM107GL [Quadro K620] driver: nvidia v: 560.35.03 Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: nvidia,v4l gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz API: OpenGL v: 4.6.0 NVIDIA 560.35.03 renderer: Quadro K620/PCIe/SSE2
(In reply to Giuseppe Ghibò from comment #18) > thanks for reminding. done. now there are new commands: > > coredumpctl list # list dump collected > coredumpctl info <PID> # show infos about a PID listed in coredumpctl list > coredumpctl debug <PID> # list debugging informations (requires -debug > packages for getting full verbose debugging) for the crashes whose coredump > has not yet been discarded/cleaned. OK, here goes: [root@localhost ~]# coredumpctl list TIME PID UID GID SIG COREFILE EXE SIZE Mon 2024-10-14 20:28:33 EDT 3001 0 0 SIGABRT missing /usr/libexec/Xorg - Fri 2024-11-01 18:47:42 EDT 3053 0 0 SIGABRT present /usr/libexec/Xorg 2.8M Fri 2024-11-01 19:35:02 EDT 3087 0 0 SIGABRT present /usr/libexec/Xorg 2.8M The first two are from before I installed this latest newfeature driver; the last is the relevant one: [root@localhost ~]# coredumpctl info 3087 PID: 3087 (Xorg) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Fri 2024-11-01 19:35:02 EDT (6min ago) Command Line: /usr/libexec/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_RpENJu> Executable: /usr/libexec/Xorg Control Group: /system.slice/sddm.service Unit: sddm.service Slice: system.slice Boot ID: dbcf2f734df545b58346d4adc56e47ea Machine ID: 2b0c959528964fd7a2bd2c6263efd2cb Hostname: localhost Storage: /var/lib/systemd/coredump/core.Xorg.0.dbcf2f734df545b58346d4adc56e47ea.3087.1730504102000000.> Size on Disk: 2.8M Message: Process 3087 (Xorg) of user 0 dumped core. Stack trace of thread 3087: #0 0x00007f8901d064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #1 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) #2 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) #3 0x00000000005a887a OsAbort (Xorg + 0x1a887a) #4 0x00000000005adca3 AbortServer (Xorg + 0x1adca3) #5 0x00000000005aec60 FatalError (Xorg + 0x1aec60) #6 0x00000000005a5df8 OsSigHandler (Xorg + 0x1a5df8) #7 0x00007f8901cb79e0 __restore_rt (libc.so.6 + 0x369e0) #8 0x00007f8901d064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #9 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) PID: 3087 (Xorg) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Fri 2024-11-01 19:35:02 EDT (6min ago) Command Line: /usr/libexec/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_RpENJu> Executable: /usr/libexec/Xorg Control Group: /system.slice/sddm.service Unit: sddm.service Slice: system.slice Boot ID: dbcf2f734df545b58346d4adc56e47ea Machine ID: 2b0c959528964fd7a2bd2c6263efd2cb Hostname: localhost Storage: /var/lib/systemd/coredump/core.Xorg.0.dbcf2f734df545b58346d4adc56e47ea.3087.1730504102000000.> Size on Disk: 2.8M Message: Process 3087 (Xorg) of user 0 dumped core. Stack trace of thread 3087: #0 0x00007f8901d064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #1 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) #2 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) #3 0x00000000005a887a OsAbort (Xorg + 0x1a887a) #4 0x00000000005adca3 AbortServer (Xorg + 0x1adca3) #5 0x00000000005aec60 FatalError (Xorg + 0x1aec60) #6 0x00000000005a5df8 OsSigHandler (Xorg + 0x1a5df8) #7 0x00007f8901cb79e0 __restore_rt (libc.so.6 + 0x369e0) #8 0x00007f8901d064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #9 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) #10 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) #11 0x00007f8901ca3395 __assert_fail_base.cold (libc.so.6 + 0x22395) #12 0x00007f8901cb08d2 __assert_fail (libc.so.6 + 0x2f8d2) #13 0x000000000045eaee dixRegisterPrivateKey (Xorg + 0x5eaee) #14 0x00007f88fd94ac5a glamor_init (libglamoregl.so + 0xac5a) #15 0x00007f88fd988b30 drmmode_init (modesetting_drv.so + 0x12b30) #16 0x00007f88fd97f0a6 ScreenInit (modesetting_drv.so + 0x90a6) #17 0x000000000043f73d AddGPUScreen (Xorg + 0x3f73d) #18 0x000000000049a12d xf86platformAddDevice (Xorg + 0x9a12d) #19 0x000000000049fd91 NewGPUDeviceRequest (Xorg + 0x9fd91) #20 0x000000000049c222 device_added (Xorg + 0x9c222) #21 0x000000000049c7c0 socket_handler (Xorg + 0x9c7c0) #22 0x00000000005a66ba ospoll_wait (Xorg + 0x1a66ba) #23 0x000000000059faf3 WaitForSomething (Xorg + 0x19faf3) #24 0x000000000043f173 Dispatch (Xorg + 0x3f173) #25 0x000000000044318c dix_main (Xorg + 0x4318c) #26 0x00007f8901ca4737 __libc_start_call_main (libc.so.6 + 0x23737) #27 0x00007f8901ca47f5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x237f5) #28 0x000000000042d3a1 _start (Xorg + 0x2d3a1) Stack trace of thread 3378: #0 0x00007f8901d7fb96 epoll_wait (libc.so.6 + 0xfeb96) #1 0x00000000005a6674 ospoll_wait (Xorg + 0x1a6674) #2 0x00000000005a3fb9 InputThreadDoWork (Xorg + 0x1a3fb9) #3 0x00007f8901d049ca start_thread (libc.so.6 + 0x839ca) #4 0x00007f8901d8061c __clone3 (libc.so.6 + 0xff61c) ELF object binary architecture: AMD x86-64 Not sure what "debug" packages you meant, so they aren't installed, but I ran the debug command anyway: [root@localhost ~]# coredumpctl debug 3087 PID: 3087 (Xorg) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Fri 2024-11-01 19:35:02 EDT (13min ago) Command Line: /usr/libexec/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_RpENJu -noreset -displayfd 15 Executable: /usr/libexec/Xorg Control Group: /system.slice/sddm.service Unit: sddm.service Slice: system.slice Boot ID: dbcf2f734df545b58346d4adc56e47ea Machine ID: 2b0c959528964fd7a2bd2c6263efd2cb Hostname: localhost Storage: /var/lib/systemd/coredump/core.Xorg.0.dbcf2f734df545b58346d4adc56e47ea.3087.1730504102000000.zst (present) Size on Disk: 2.8M Message: Process 3087 (Xorg) of user 0 dumped core. Stack trace of thread 3087: #0 0x00007f8901d064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #1 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) #2 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) #3 0x00000000005a887a OsAbort (Xorg + 0x1a887a) #4 0x00000000005adca3 AbortServer (Xorg + 0x1adca3) #5 0x00000000005aec60 FatalError (Xorg + 0x1aec60) #6 0x00000000005a5df8 OsSigHandler (Xorg + 0x1a5df8) #7 0x00007f8901cb79e0 __restore_rt (libc.so.6 + 0x369e0) #8 0x00007f8901d064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #9 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) #10 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) #11 0x00007f8901ca3395 __assert_fail_base.cold (libc.so.6 + 0x22395) #12 0x00007f8901cb08d2 __assert_fail (libc.so.6 + 0x2f8d2) #13 0x000000000045eaee dixRegisterPrivateKey (Xorg + 0x5eaee) #14 0x00007f88fd94ac5a glamor_init (libglamoregl.so + 0xac5a) #15 0x00007f88fd988b30 drmmode_init (modesetting_drv.so + 0x12b30) #16 0x00007f88fd97f0a6 ScreenInit (modesetting_drv.so + 0x90a6) #17 0x000000000043f73d AddGPUScreen (Xorg + 0x3f73d) #18 0x000000000049a12d xf86platformAddDevice (Xorg + 0x9a12d) #19 0x000000000049fd91 NewGPUDeviceRequest (Xorg + 0x9fd91) #20 0x000000000049c222 device_added (Xorg + 0x9c222) #21 0x000000000049c7c0 socket_handler (Xorg + 0x9c7c0) #22 0x00000000005a66ba ospoll_wait (Xorg + 0x1a66ba) #23 0x000000000059faf3 WaitForSomething (Xorg + 0x19faf3) #24 0x000000000043f173 Dispatch (Xorg + 0x3f173) #25 0x000000000044318c dix_main (Xorg + 0x4318c) #26 0x00007f8901ca4737 __libc_start_call_main (libc.so.6 + 0x23737) #27 0x00007f8901ca47f5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x237f5) #28 0x000000000042d3a1 _start (Xorg + 0x2d3a1) Stack trace of thread 3378: #0 0x00007f8901d7fb96 epoll_wait (libc.so.6 + 0xfeb96) #1 0x00000000005a6674 ospoll_wait (Xorg + 0x1a6674) #2 0x00000000005a3fb9 InputThreadDoWork (Xorg + 0x1a3fb9) #3 0x00007f8901d049ca start_thread (libc.so.6 + 0x839ca) #4 0x00007f8901d8061c __clone3 (libc.so.6 + 0xff61c) ELF object binary architecture: AMD x86-64 Failed to invoke gdb: No such file or directory
(In reply to Thomas Andrews from comment #22) > The first two are from before I installed this latest newfeature driver; the > last is the relevant one: > > [root@localhost ~]# coredumpctl info 3087 > PID: 3087 (Xorg) > UID: 0 (root) > GID: 0 (root) > Signal: 6 (ABRT) > Timestamp: Fri 2024-11-01 19:35:02 EDT (6min ago) > Command Line: /usr/libexec/Xorg -nolisten tcp -background none -seat seat0 > vt2 -auth /run/sddm/xauth_RpENJu> > Executable: /usr/libexec/Xorg > Control Group: /system.slice/sddm.service > Unit: sddm.service > Slice: system.slice > Boot ID: dbcf2f734df545b58346d4adc56e47ea > Machine ID: 2b0c959528964fd7a2bd2c6263efd2cb > Hostname: localhost > Storage: > /var/lib/systemd/coredump/core.Xorg.0.dbcf2f734df545b58346d4adc56e47ea.3087. > 1730504102000000.> > Size on Disk: 2.8M > Message: Process 3087 (Xorg) of user 0 dumped core. > > Stack trace of thread 3087: > #0 0x00007f8901d064bc __pthread_kill_implementation > (libc.so.6 + 0x854bc) > #1 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) > #2 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) > #3 0x00000000005a887a OsAbort (Xorg + 0x1a887a) > #4 0x00000000005adca3 AbortServer (Xorg + 0x1adca3) > #5 0x00000000005aec60 FatalError (Xorg + 0x1aec60) > #6 0x00000000005a5df8 OsSigHandler (Xorg + 0x1a5df8) > #7 0x00007f8901cb79e0 __restore_rt (libc.so.6 + 0x369e0) > #8 0x00007f8901d064bc __pthread_kill_implementation > (libc.so.6 + 0x854bc) > #9 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) > PID: 3087 (Xorg) > UID: 0 (root) > GID: 0 (root) > Signal: 6 (ABRT) > Timestamp: Fri 2024-11-01 19:35:02 EDT (6min ago) > Command Line: /usr/libexec/Xorg -nolisten tcp -background none -seat seat0 > vt2 -auth /run/sddm/xauth_RpENJu> > Executable: /usr/libexec/Xorg > Control Group: /system.slice/sddm.service > Unit: sddm.service > Slice: system.slice > Boot ID: dbcf2f734df545b58346d4adc56e47ea > Machine ID: 2b0c959528964fd7a2bd2c6263efd2cb > Hostname: localhost > Storage: > /var/lib/systemd/coredump/core.Xorg.0.dbcf2f734df545b58346d4adc56e47ea.3087. > 1730504102000000.> > Size on Disk: 2.8M > Message: Process 3087 (Xorg) of user 0 dumped core. > > Stack trace of thread 3087: > #0 0x00007f8901d064bc __pthread_kill_implementation > (libc.so.6 + 0x854bc) > #1 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) > #2 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) > #3 0x00000000005a887a OsAbort (Xorg + 0x1a887a) > #4 0x00000000005adca3 AbortServer (Xorg + 0x1adca3) > #5 0x00000000005aec60 FatalError (Xorg + 0x1aec60) > #6 0x00000000005a5df8 OsSigHandler (Xorg + 0x1a5df8) > #7 0x00007f8901cb79e0 __restore_rt (libc.so.6 + 0x369e0) > #8 0x00007f8901d064bc __pthread_kill_implementation > (libc.so.6 + 0x854bc) > #9 0x00007f8901cb7932 raise (libc.so.6 + 0x36932) > #10 0x00007f8901ca3464 abort (libc.so.6 + 0x22464) > #11 0x00007f8901ca3395 __assert_fail_base.cold (libc.so.6 + > 0x22395) > #12 0x00007f8901cb08d2 __assert_fail (libc.so.6 + 0x2f8d2) > #13 0x000000000045eaee dixRegisterPrivateKey (Xorg + 0x5eaee) > #14 0x00007f88fd94ac5a glamor_init (libglamoregl.so + 0xac5a) > #15 0x00007f88fd988b30 drmmode_init (modesetting_drv.so + > 0x12b30) > #16 0x00007f88fd97f0a6 ScreenInit (modesetting_drv.so + > 0x90a6) > #17 0x000000000043f73d AddGPUScreen (Xorg + 0x3f73d) > #18 0x000000000049a12d xf86platformAddDevice (Xorg + 0x9a12d) > #19 0x000000000049fd91 NewGPUDeviceRequest (Xorg + 0x9fd91) > #20 0x000000000049c222 device_added (Xorg + 0x9c222) > #21 0x000000000049c7c0 socket_handler (Xorg + 0x9c7c0) > #22 0x00000000005a66ba ospoll_wait (Xorg + 0x1a66ba) > #23 0x000000000059faf3 WaitForSomething (Xorg + 0x19faf3) > #24 0x000000000043f173 Dispatch (Xorg + 0x3f173) > #25 0x000000000044318c dix_main (Xorg + 0x4318c) > #26 0x00007f8901ca4737 __libc_start_call_main (libc.so.6 + > 0x23737) > #27 0x00007f8901ca47f5 __libc_start_main@@GLIBC_2.34 > (libc.so.6 + 0x237f5) > #28 0x000000000042d3a1 _start (Xorg + 0x2d3a1) > > Stack trace of thread 3378: > #0 0x00007f8901d7fb96 epoll_wait (libc.so.6 + 0xfeb96) > #1 0x00000000005a6674 ospoll_wait (Xorg + 0x1a6674) > #2 0x00000000005a3fb9 InputThreadDoWork (Xorg + 0x1a3fb9) > #3 0x00007f8901d049ca start_thread (libc.so.6 + 0x839ca) > #4 0x00007f8901d8061c __clone3 (libc.so.6 + 0xff61c) > ELF object binary architecture: AMD x86-64 > > Not sure what "debug" packages you meant, so they aren't installed, but I > ran the debug command anyway: debug package means: a) install package gdb b) enable the -debug repository(ies) [e.g. debug/core/updates|debug/core/updates_testing] and install the -debug* packages of the packages (at least the top ones) involved in the trace, in this case might be useful x11-xserver-debuginfo|debugsource, x11-server-xorg-debuginfo, glibc-debuginfo, sddm-debuginfo, then repeat the command.
Apparently, might be similar to this one upstream: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1304, related to xorg.
On a whim, I tried switching from sddm to xdm. Resetting autologin from MCC asked to install something called "autologin" and I allowed it. Rebooted - didn't help. Still no autologin. I had installed just the packages that XFdrake demands, meaning not the cuda or 32-bit packages. (That's always been good with nvidia-current) Thinking the newfeature driver might need something more, I went to drakrpm and found the nvidia-newfeature-all metapackage, which was supposed to install extra dependencies and reccommends. I took a chance and installed that. Unexpectedly, it activated the 32-bit repos and installed a bunch of packages from both arches. And of course that didn't help, either. Now I need to know how to get rid of all this extra junk that I didn't actually need, or want. Come to think of it, a fresh netinstall of MGA9, with no old baggage, might not be a bad idea...
I'm pretty sure there is some urpmi option to do in one shot..., however, to get the latest installed packages within 1 hours might be: journalctl --since '1 hours ago'| grep RPM |grep install |awk '{print $7}' |sort -u | sed -e 's@:$@@g' then remove those unwanted from the list. For the fresh install IMHO we might do a new set of ISO (but we need to pay attention to the BS for the space if can sustain it). IMHO I'd limit only for x86_64, and maybe limiting the live to 1 set only (e.g. Plasma). Instead what could be useful, but I've already discussed somewhere, would be a feature inspired to the live and persistent partition, using the overlayfs. That would be very useful for testing. So one can boot a working system, do the tests installing all packages in the overlayfs, then get rid of them in one shot, removing the overlay dirs. We might have more than one overlaydir, each with a name, to be showed after boot, where at some point one can choose one of them, by just typing the corresponding number.
That system has two installs on it, one my main production, the other used for QA testing. There is enough free space on the NVME drive, after a bit of adjustment of that second install, for a third one. I'll use the new install for working with the newfeature stuff, freeing up the QA install for that work. It'll be better all the way around. But give me a few days to get it done.
I created a new install of MGA9-64 Plasma on some unused space, and tried again. I installed the specified debug packages (it was x11-server, not x11-xserver), and this is what I got: [root@localhost ~]# coredumpctl list TIME PID UID GID SIG COREFILE EXE SIZE Sun 2024-11-24 10:41:07 EST 2658 0 0 SIGABRT present /usr/libexec/Xorg 2.8M Sun 2024-11-24 10:53:31 EST 2733 0 0 SIGABRT present /usr/libexec/Xorg 2.8M [root@localhost ~]# coredumpctl info 2733 PID: 2733 (Xorg) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Sun 2024-11-24 10:53:31 EST (4min 49s ago) Command Line: /usr/libexec/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_VqJgXI> Executable: /usr/libexec/Xorg Control Group: /system.slice/sddm.service Unit: sddm.service Slice: system.slice Boot ID: 83a3966e1eb143f9b684a37752f85eed Machine ID: 583fe8a811e742ee99c45cda3d90b617 Hostname: localhost.localdomain Storage: /var/lib/systemd/coredump/core.Xorg.0.83a3966e1eb143f9b684a37752f85eed.2733.1732463611000000.> Size on Disk: 2.8M Message: Process 2733 (Xorg) of user 0 dumped core. Stack trace of thread 2733: #0 0x00007f7cad6064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #1 0x00007f7cad5b7932 raise (libc.so.6 + 0x36932) #2 0x00007f7cad5a3464 abort (libc.so.6 + 0x22464) #3 0x00000000005a888a OsAbort (Xorg + 0x1a888a) #4 0x00000000005adcb3 AbortServer (Xorg + 0x1adcb3) #5 0x00000000005aec70 FatalError (Xorg + 0x1aec70) #6 0x00000000005a5e08 OsSigHandler (Xorg + 0x1a5e08) #7 0x00007f7cad5b79e0 __restore_rt (libc.so.6 + 0x369e0) #8 0x00007f7cad6064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #9 0x00007f7cad5b7932 raise (libc.so.6 + 0x36932) #10 0x00007f7cad5a3464 abort (libc.so.6 + 0x22464) #11 0x00007f7cad5a3395 __assert_fail_base.cold (libc.so.6 + 0x22395) #12 0x00007f7cad5b08d2 __assert_fail (libc.so.6 + 0x2f8d2) #13 0x000000000045eaee dixRegisterPrivateKey (Xorg + 0x5eaee) #14 0x00007f7cab2e8c5a glamor_init (libglamoregl.so + 0xac5a) #15 0x00007f7cab326b30 drmmode_init (modesetting_drv.so + 0x12b30) #16 0x00007f7cab31d0a6 ScreenInit (modesetting_drv.so + 0x90a6) #17 0x000000000043f73d AddGPUScreen (Xorg + 0x3f73d) #18 0x000000000049a12d xf86platformAddDevice (Xorg + 0x9a12d) #19 0x000000000049fd91 NewGPUDeviceRequest (Xorg + 0x9fd91) #20 0x000000000049c222 device_added (Xorg + 0x9c222) #21 0x000000000049c7c0 socket_handler (Xorg + 0x9c7c0) #22 0x00000000005a66ca ospoll_wait (Xorg + 0x1a66ca) #23 0x000000000059fb03 WaitForSomething (Xorg + 0x19fb03) #24 0x000000000043f173 Dispatch (Xorg + 0x3f173) #25 0x000000000044318c dix_main (Xorg + 0x4318c) #26 0x00007f7cad5a4737 __libc_start_call_main (libc.so.6 + 0x23737) #27 0x00007f7cad5a47f5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x237f5) #28 0x000000000042d3a1 _start (Xorg + 0x2d3a1) Stack trace of thread 3016: #0 0x00007f7cad67fb96 epoll_wait (libc.so.6 + 0xfeb96) #1 0x00000000005a6684 ospoll_wait (Xorg + 0x1a6684) #2 0x00000000005a3fc9 InputThreadDoWork (Xorg + 0x1a3fc9) #3 0x00007f7cad6049ca start_thread (libc.so.6 + 0x839ca) #4 0x00007f7cad68061c __clone3 (libc.so.6 + 0xff61c) ELF object binary architecture: AMD x86-64 [root@localhost ~]# coredumpctl debug 2733 PID: 2733 (Xorg) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Sun 2024-11-24 10:53:31 EST (5min ago) Command Line: /usr/libexec/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_VqJgXI -noreset -displayfd 15 Executable: /usr/libexec/Xorg Control Group: /system.slice/sddm.service Unit: sddm.service Slice: system.slice Boot ID: 83a3966e1eb143f9b684a37752f85eed Machine ID: 583fe8a811e742ee99c45cda3d90b617 Hostname: localhost.localdomain Storage: /var/lib/systemd/coredump/core.Xorg.0.83a3966e1eb143f9b684a37752f85eed.2733.1732463611000000.zst (present) Size on Disk: 2.8M Message: Process 2733 (Xorg) of user 0 dumped core. Stack trace of thread 2733: #0 0x00007f7cad6064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #1 0x00007f7cad5b7932 raise (libc.so.6 + 0x36932) #2 0x00007f7cad5a3464 abort (libc.so.6 + 0x22464) #3 0x00000000005a888a OsAbort (Xorg + 0x1a888a) #4 0x00000000005adcb3 AbortServer (Xorg + 0x1adcb3) #5 0x00000000005aec70 FatalError (Xorg + 0x1aec70) #6 0x00000000005a5e08 OsSigHandler (Xorg + 0x1a5e08) #7 0x00007f7cad5b79e0 __restore_rt (libc.so.6 + 0x369e0) #8 0x00007f7cad6064bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #9 0x00007f7cad5b7932 raise (libc.so.6 + 0x36932) #10 0x00007f7cad5a3464 abort (libc.so.6 + 0x22464) #11 0x00007f7cad5a3395 __assert_fail_base.cold (libc.so.6 + 0x22395) #12 0x00007f7cad5b08d2 __assert_fail (libc.so.6 + 0x2f8d2) #13 0x000000000045eaee dixRegisterPrivateKey (Xorg + 0x5eaee) #14 0x00007f7cab2e8c5a glamor_init (libglamoregl.so + 0xac5a) #15 0x00007f7cab326b30 drmmode_init (modesetting_drv.so + 0x12b30) #16 0x00007f7cab31d0a6 ScreenInit (modesetting_drv.so + 0x90a6) #17 0x000000000043f73d AddGPUScreen (Xorg + 0x3f73d) #18 0x000000000049a12d xf86platformAddDevice (Xorg + 0x9a12d) #19 0x000000000049fd91 NewGPUDeviceRequest (Xorg + 0x9fd91) #20 0x000000000049c222 device_added (Xorg + 0x9c222) #21 0x000000000049c7c0 socket_handler (Xorg + 0x9c7c0) #22 0x00000000005a66ca ospoll_wait (Xorg + 0x1a66ca) #23 0x000000000059fb03 WaitForSomething (Xorg + 0x19fb03) #24 0x000000000043f173 Dispatch (Xorg + 0x3f173) #25 0x000000000044318c dix_main (Xorg + 0x4318c) #26 0x00007f7cad5a4737 __libc_start_call_main (libc.so.6 + 0x23737) #27 0x00007f7cad5a47f5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x237f5) #28 0x000000000042d3a1 _start (Xorg + 0x2d3a1) Stack trace of thread 3016: #0 0x00007f7cad67fb96 epoll_wait (libc.so.6 + 0xfeb96) #1 0x00000000005a6684 ospoll_wait (Xorg + 0x1a6684) #2 0x00000000005a3fc9 InputThreadDoWork (Xorg + 0x1a3fc9) #3 0x00007f7cad6049ca start_thread (libc.so.6 + 0x839ca) #4 0x00007f7cad68061c __clone3 (libc.so.6 + 0xff61c) ELF object binary architecture: AMD x86-64 GNU gdb (GDB) 12.1-7.1.mga9 (Mageia release 9) Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/libexec/Xorg... Reading symbols from /usr/lib/debug/usr/libexec/Xorg-21.1.8-7.6.mga9.x86_64.debug... warning: Can't open file /memfd:/.glXXXXXX (deleted) during file-backed mapping note processing warning: Can't open file /memfd:/.nvidia_drv.XXXXXX (deleted) during file-backed mapping note processing [New LWP 2733] [New LWP 3016] Missing separate debuginfo for /usr/lib64/xorg/modules/extensions/libglx.so Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/02/03d1a8b759732bca45101b86ca5d4ad3b4e660.debug Missing separate debuginfo for /usr/lib64/xorg/modules/libwfb.so Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/a8/ac947028389024dccb5d641e54cb668c20dffe.debug Missing separate debuginfo for /usr/lib64/xorg/modules/drivers/modesetting_drv.so Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/b2/c56139a8357008a1c46366725db4717c1fdffb.debug Missing separate debuginfo for /usr/lib64/xorg/modules/libglamoregl.so Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/7d/094dc3b4fa76685b13a1aed5461283c7492a0e.debug [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib64/libthread_db.so.1". Core was generated by `/usr/libexec/Xorg -nolisten tcp -background none -seat seat0 vt2 -auth /run/sdd'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f7cad6064bc in __pthread_kill_implementation () from /usr/lib64/libc.so.6 [Current thread is 1 (Thread 0x7f7cace302c0 (LWP 2733))] Missing separate debuginfos, use: debuginfo-install glibc-2.36-54.mga9.x86_64 lib64brotlicommon1-1.0.9-5.mga9.x86_64 lib64brotlidec1-1.0.9-5.mga9.x86_64 lib64bz2_1-1.0.8-5.mga9.x86_64 lib64dbus1_3-1.14.6-1.mga9.x86_64 lib64dri-drivers-24.2.7-1.mga9.tainted.x86_64 lib64drm2-2.4.123-1.mga9.x86_64 lib64drm_amdgpu1-2.4.123-1.mga9.x86_64 lib64drm_intel1-2.4.123-1.mga9.x86_64 lib64drm_radeon1-2.4.123-1.mga9.x86_64 lib64edit0-3.1-0.20221030.1.mga9.x86_64 lib64egl1-1.6.0-1.mga9.x86_64 lib64elfutils1-0.189-1.mga9.x86_64 lib64epoxy0-1.5.10-1.mga9.x86_64 lib64evdev2-1.13.1-1.mga9.x86_64 lib64expat1-2.6.4-1.mga9.x86_64 lib64ffi8-3.4.4-1.mga9.x86_64 lib64fontenc1-1.1.7-1.mga9.x86_64 lib64freetype6-2.13.0-1.mga9.tainted.x86_64 lib64gcrypt20-1.10.2-2.mga9.x86_64 lib64gl1-1.6.0-1.mga9.x86_64 lib64glapi0-24.2.7-1.mga9.tainted.x86_64 lib64glib2.0_0-2.76.3-1.2.mga9.x86_64 lib64gpg-error0-1.47-1.mga9.x86_64 lib64graphite2_3-1.3.14-2.mga9.x86_64 lib64gudev1.0_0-237-1.mga9.x86_64 lib64harfbuzz0-7.0.1-1.mga9.x86_64 lib64input10-1.23.0-2.mga9.x86_64 lib64llvm15.0-15.0.6-1.mga9.x86_64 lib64lz4_1-1.9.4-1.mga9.x86_64 lib64lzma5-5.4.3-1.mga9.x86_64 lib64mesaegl1-24.2.7-1.mga9.tainted.x86_64 lib64mtdev1-1.1.6-3.mga9.x86_64 lib64openssl3-3.0.15-1.1.mga9.x86_64 lib64pciaccess0-0.17-1.mga9.x86_64 lib64pcre2_0-10.42-1.mga9.x86_64 lib64pixman1_0-0.42.2-1.mga9.x86_64 lib64png16_16-1.6.38-1.mga9.x86_64 lib64systemd0-253.24-3.mga9.x86_64 lib64udev1-253.24-3.mga9.x86_64 lib64unwind8-1.6.2-3.mga9.x86_64 lib64wayland-server0-1.21.0-1.mga9.x86_64 lib64x11_6-1.8.6-1.1.mga9.x86_64 lib64xau6-1.0.11-1.mga9.x86_64 lib64xcb-dri2_0-1.15-2.mga9.x86_64 lib64xcb-dri3_0-1.15-2.mga9.x86_64 lib64xcb-present0-1.15-2.mga9.x86_64 lib64xcb-xfixes0-1.15-2.mga9.x86_64 lib64xcb1-1.15-2.mga9.x86_64 lib64xcvt0-0.1.2-1.mga9.x86_64 lib64xdmcp6-1.1.4-1.mga9.x86_64 lib64xfont2_2-2.0.6-2.mga9.x86_64 lib64xshmfence1-1.3.2-1.mga9.x86_64 lib64zlib1-1.2.13-1.2.mga9.x86_64 libgcc1-12.3.0-3.mga9.x86_64 x11-driver-video-nvidia-newfeature-560.35.03-2.mga9.nonfree.x86_64 x11-driver-video-v4l-0.3.0-6.mga9.x86_64 I'm pretty much completely lost here, but it appears that the more debug packages I install, the more it wants.
@Thomas Is not really necessary to install the debug packages, just type bt or bt full and hit enter, paste her or in file the output, that should provide a hint about the fail
Since it remains only the autologin problems, I'd push the package. According to debug seems pretty similar to this one: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1304 about screen numbering, for which has been proposed a patch for Xorg (so the bug might be in Xorg): https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/869 which seems not accepted. Indeed the thread itself seems pretty confusing. BTW, does it changes something if you, if under /etc/X11/xorg.conf changes the entries in ServerLayout, from something like: Section "ServerLayout" Identifier "layout1" Screen "screen1" EndSection to something like: Section "ServerLayout" Identifier "layout1" Screen 0 "screen1" EndSection ?
No apparent difference. "Since it remains only the autologin problems, I'd push the package." OK. Validating.
Keywords: (none) => validated_updateWhiteboard: (none) => MGA9-64-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2024-0237.html
Status: NEW => RESOLVEDResolution: (none) => FIXED