View Issue Details

IDProjectCategoryView StatusLast Update
0009215Kali LinuxKali Package Bugpublic2025-06-11 08:28
ReporterArszilla Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Summary0009215: nvidia-driver Breaks LightDM TTY7
Description

I recently created a new somewhat personally customized Kali i3 ISO, which was meant for my desktop system. Beyond a few custom packages (such as virt-manager related ones), only a few modifications were made using .chroot hooks (such as the installation of 1Password, which required a temp

The ISO installed perfectly fine, and had linux-headers-amd64 pre-installed. I ensured that the headers were installed prior to installing nvidia-driver and nvidia-cuda-toolkit. However, after installing the aforementioned packages, upon rebooting the PC, it kicks into TTY1, instead of TTY7 - for whatever reason.

I have confirmed that the issue is related to nvidia related packages, as I reinstalled my system using the same ISO, and only ran apt install -y nvidia-driver nvidia-cuda-toolkit upon booting up for the first time.

Activities

kali-bugreport

kali-bugreport

2025-06-10 19:15

reporter   ~0020667

Report a bug to Nvidia?

Arszilla

Arszilla

2025-06-10 20:28

reporter   ~0020668

Will do - but since I could only replicate this on my desktop (as I have no other Nvidia device), I was posting here for a few reasons:

  1. To see if anyone else faces the same end result as I do.
  2. To see if this is common, and gather as much info before reaching out to Nvidia
  3. To see if Kali can possibly introduce a patch to temporarily mitigate the issue if it is common (very unlikely, but still worth asking)
arnaudr

arnaudr

2025-06-11 03:43

manager   ~0020669

Last edited: 2025-06-11 03:44

it kicks into TTY1, instead of TTY7 - for whatever reason.

There must be logs somewhere :) Maybe when you install the nvidia packages (I suppose it should rebuild the initrd, does that appear in the log, no error?). And then on reboot, if it goes to TTY, it probably means the initrd fails, and there should be logs (I guess /var/log/syslog, or journalctl or somewhere else).

We can't give support for hardware-related problems (no bandwidth), but if you find and paste the offending logs here, someone might be able to help.

kali-bugreport

kali-bugreport

2025-06-11 08:28

reporter   ~0020670

For No.1 and No.2 https://forums.kali.org/ could have wider audience

Issue History

Date Modified Username Field Change
2025-06-10 17:50 Arszilla New Issue
2025-06-10 19:15 kali-bugreport Note Added: 0020667
2025-06-10 20:28 Arszilla Note Added: 0020668
2025-06-11 03:43 arnaudr Note Added: 0020669
2025-06-11 03:44 arnaudr Note Edited: 0020669
2025-06-11 08:28 kali-bugreport Note Added: 0020670