View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007970||Kali Linux||General Bug||public||2022-09-30 22:00||2023-05-31 14:56|
|Summary||0007970: Kali Linux CRASHES during BOOT.|
Kali Linux crashes on 'startup'. (dual boot MacBook Pro (mid 2012)) Everything seemed fine just past the Kali emblem/logo BUT then gives the "Oh No! Something has gone wrong. A problem has occurred and the system can't recover. Please contact a system administrator" SCREEN *(see attached screenshot). When I last shutdown Kali (2 days ago), everything was cool/seemed fine+normal with ZERO issues/problems.
I update/upgrade on a regular basis and this has not happened in a long while. So, I then entered 'recovery mode' and I updated/upgraded right away. Everything seemed to go perfectly, all updated/upgraded fine. BUT WHEN I REBOOTED, the same "Oh no!" SCREEN appeared as it had before.
I then went into my VMware Fusion of Kali (2022.3) in my MacBook Pro, started it up... AND ALL WORKED PERFECTLY with NO ISSUES!
–I appreciate your time, thank you!
|Steps To Reproduce|
Boot Kali Linux
"When I last shutdown Kali (2 days ago), everything was cool/seemed fine+normal with ZERO issues/problems" ––all I had done was startup Kali, log in, update/upgrade, then IMMEDIATELY shutdown/powered off. I DID NOT run anything, only shut it down. Then, as I stated above, booted it up 2 days later to have it crash ("Oh no!" screen) just after the Kali emblem/logo and just prior to the login screen...
I am assuming the issue has something to do with what had been updated/upgraded.
My GRAPHICS hardware is Intel HD Graphics 4000. Maybe this could be causing this CRASH?! Graphics driver issue? But, I am able to go into 'Recovery Mode', log in as root, and then startxfce4. I usually use GNOME, so could it be a GNOME issue *(GNOME 43 had been working fine and I verified that it exists and is latest version) that makes this CRASH occur (following the update/upgrade just days prior.)?
––thanks for your time.
Boot into recovery, pull the latest package upgrades (gnome extensions should be in those), and you should be good to go. I've had issues with Gnome over the past few days due to outdated extensions, but the latest upgrades (gnome extensions) should validate versions. Everything's working perfectly for me right now.
Thanks for the feedback. I just checked (in 'recovery') but there weren't any updates/upgrades... of any kind so far today. If, in fact, that was even a GNOME problem.
So, the CRASHing continues. I went in and all of my USER + ROOT seems intact... + up-to-date.
Thanks again, hopefully this will be solved ASAP––
In this kind of situation, when you are at the screen "Oh no...", you would press <Ctrl+Alt+Fx>, with Fx being either F1, F2 or F3 or whatever takes you to a console. Then you enter the login/pass, and then you'd have a look at the logs with the command
If you can locate the error, please paste it here. Thanks!
Yes, I'm running GNOME. And I've gotten into the console with Ctrl+Alt+F3/logged in. But I have NOT checked the logs as of yet. But I will definitely, ASAP!
If I locate the error, I'll paste post it. Thanks again! ––very much appreciate your feedback_
I started it up, Ctrl+Alt+F2 and for the first time the actual log in screen appeared, not the console. BUT then I entered my login info and THEN the "Oh No!" screen appeared. So, I Ctrl+Alt+F2 to console, logged in again, and 'journalctl -b' to check the logs. I found ERRORS "Failed to start GNOME Shell on X11" toward the end of the log. See screenshot
Thanks for your time––
Kali Linux - GNOME LOG ERROR - IMG_4937.JPG (734,134 bytes)
I need also the last lines of the logs, from line 1560 t0 1596 it seems.
Additionally, you can try to disable the gnome extensions with the command " gsettings set org.gnome.shell disable-user-extensions true ". Then try to login again.
Yes, every Fx is a different screen, and the login screen is one of them. So if you go to the console with, for example, Ctrl+Alt+F3, then you can go back to the login scree anytime with Ctrl+Alt+F2, and then back to the console with Ctrl+Alt+F3.
I first started it up into recovery to update/upgrade. Everything went fine (seemingly). I then tried it but it crashed. ––then went into via 'recovery' to disable the GNOME extensions BUT it wouldn't allow me so I attempted by starting xfce4 and trying the console there. And THAT seemed to work (disabling GNOME extensions). ––started it up again as I would normally BUT it crashed. So I ENABLED the GNOME extension as they had originally been via the console after reboot After that, I booted normally and did Ctrl+Alt+F2 which allowed me to log in as USER. ––checked the log ('journalctl -b) which had fewer lines this time to then take 3 screenshots (01 just prior to the "Failed to start GNOME Shell on X11" error, 02 of the ERROR, 03 the remaining lines following the error.)
01 - IMG_4940 copy.jpg (1,551,647 bytes)
02 - IMG_4941 copy.jpg (1,505,842 bytes)
03 - IMG_4942 copy.jpg (1,584,210 bytes)
Alright, so now I remember. The reason why Xorg crashes doesn't appear in the journal, it's is another log file. Can you try " cat /var/log/Xorg.0.log " and post the output? (I'm not even sure this file is named exactly this way, if ever it doesn't exists, look into /var/log for anything named xorg or x11).
I am pasting 2 log files. '/var/log/Xorg.0.log' AND '/var/log/Xorg.1.log'.
root@kali:/home/atdtphreaker# cat /var/log/Xorg.0.log
[ 128.387] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
root@kali:/home/atdtphreaker# cat /var/log/Xorg.1.log
[ 148.702] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32
I hope this helps, thank you.
The Oh Snap, something went wrong window is Gnome crashing, not Xorg - typically it means something in the graphic stack has stopped working.
The journal should have that information. You should be looking for messages from gnome-shell
Additionally, if you can, try updating and full-upgrade as some parts of gnome 43 hadn’t made it in.
What graphics card is your Apple machine using?
So the error is in your 2nd screenshot (in your series of 3 screenshots):
There's nothing that I can see in the Xorg logs. So my guess is that it's not Xorg crashing, but really the gnome-shell process.
So in this case you really want to disable all extensions - again: hit Ctrl+Alt+F2 when you're at the login screen, then login as your usual user (NOT root), then type « gsettings set org.gnome.shell disable-user-extensions true ». Then try to login again.
Other than that, there's not much else I can do. I will give it a try, in case I can reproduce the crash.
Can you please confirm a few things:
Thanks for the feedback. My graphics card is 'Intel HD Graphics 4000'.
I can log in XFCE ('startxfce4') via 'recovery mode' but nowhere else. In XFCE, I checked if my system was up--to-date having GNOME 43.
I did the full-upgrade and everything seems to be up-to-date, nothing was changed.
I tried disabling the extensions (via USER), tried to log in again but it crashed.
I ALSO did 'dpkg -l | grep gnome-shell' as USER took a screenshot. Everything seems to be up-to-date.
I appreciate your time and effort...I'm not sure what the hell is going on with this crash. Again, thank you.
USER-GNOME-(dpkg)output-IMG_4956.jpg (915,846 bytes)
If you update / upgrade again, there is a new revision of gnome-shell (gnome-shell 43.0-2) that should be available. So you can try to update your system (« apt update && apt full-upgrade » as root), then reboot and try to login again.
To be honest, I don't think it will fix anything, but if you have a bit of spare time, please try it and tell us if it works. Thanks!
Yes, I updated/upgraded (gnome-shell 43.0-2) and as you suspected, nothing was fixed. *There are others having similar issues as mine over on Kali Linux Troubleshooting. Some believe it has something to do with the video cards/drivers. I'm beginning to think the same. Mine=(Intel HD Graphics 4000) Nvidia is discussed over in the troubleshooting discussions.
I also wanted to mention that as I startup Kali, everything is loading/etc past the logo and then the screen goes blank/black and it seems the computer goes to sleep because all USB/laptop LEDs switch OFF along with the monitor. (screenshot 01) NOT until I tap any key that they then all switch on again, waking up the computer to continue starting up. The screen continues to be blank/black EXCEPT FOR my mouse pointer is visible and can be moved around as it continues to load (not locking up...never has locked up). After about 10 seconds, the "Oh No" screen appears with the (still functioning) mouse pointer (screenshot 02) BUT that is all that works, graphically. I then <press> CTRL-ALT-F2 OR F3 which takes me to a black screen with a blinking curser in the upper left corner, NO CONSOLE. (screenshot 03) This flashes forever, never stops... CTRL+ALT+F1 takes me back to the "Oh No" screen. I'm never able to make it to the console UNLESS I pop my MacBook Pro open and tap the POWER button, which has the console appear as it SHUTS DOWN. (screenshot 04)
I hope this helps + thanks for your assistance!
01-blackSCREEN-IMG_4975-1200x.jpg (606,039 bytes)
02-followingKEYTAP-IMG_4981-1200x.jpg (593,773 bytes)
03-CTRL-ALT-F2-IMG_4978-1200x.jpg (667,383 bytes)
04-MBP-powerbutton-shutsDOWN-IMG_4982-1200x.jpg (1,247,984 bytes)
Okay, so I did a clean install, did the updates and everything was going perfectly fine until a warning was given that the i915 firmware was missing (around 9+ warnings in a row). This apparently controls/handles my 'Intel HD Graphics 4000' capabilities. I then restarted Kali, everything loaded as before (as it did prior to the clean install) and right back to the "Oh No!" screen...as it had been doing every time.
The issue must have something to do with the missing firmware/driver. I hope this get rectified ASAP.
Heya, unfortunately this issue is getting out of our area. In this bug tracker we try to identify Kali-specific issues, and fix it if we can. But we can't provide support for hardware-related problems. We simply don't have the bandwidth for that. So in your case, the problem might be already reported in upstream projects (ie. a component of gnome such as gnome-shell or mutter), or in the Linux kernel itself, or somewhere in the Debian bugtracker... If it's not, you should report it. Finding the right place to report might be challenging, I know. It seems to me that it's related to GNOME (I think you said that XFCE works fine). But it's not the Kali bugtracker, I've been as far as I could on the issue. Sorry.
Another thing you could try is to do a fresh install of Debian testing from here: https://www.debian.org/devel/debian-installer/. Make sure to do all the updates. Then if you have the same issue, then it's definitely not related to Kali. If you don't have the issue, then we can investigate further.
This is usual harmless. But just in case, you can try to install the package
Okay, I appreciate it. Thank you—
Just a heads up. --I did yet another clean install BUT DID NOT install GNOME, only xfce and there were ZERO ISSUES following update/upgrade. So the CRASH must have something to do with the updating of GNOME 43.
This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity.
Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)?
If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
|2022-09-30 22:00||atdtphreaker||New Issue|
|2022-09-30 22:00||atdtphreaker||File Added: IMG_4900-1200x.jpg|
|2022-10-01 07:15||atdtphreaker||Note Added: 0016903|
|2022-10-04 08:10||atdtphreaker||Note Added: 0016908|
|2022-10-04 14:00||X0RW3LL||Note Added: 0016915|
|2022-10-04 22:18||atdtphreaker||Note Added: 0016916|
|2022-10-05 06:11||arnaudr||Note Added: 0016918|
|2022-10-05 06:35||atdtphreaker||Note Added: 0016919|
|2022-10-05 07:12||atdtphreaker||File Added: Kali Linux - GNOME LOG ERROR - IMG_4937.JPG|
|2022-10-05 07:12||atdtphreaker||Note Added: 0016920|
|2022-10-05 07:56||arnaudr||Note Added: 0016921|
|2022-10-05 10:09||atdtphreaker||File Added: 01 - IMG_4940 copy.jpg|
|2022-10-05 10:09||atdtphreaker||File Added: 02 - IMG_4941 copy.jpg|
|2022-10-05 10:09||atdtphreaker||File Added: 03 - IMG_4942 copy.jpg|
|2022-10-05 10:09||atdtphreaker||Note Added: 0016922|
|2022-10-05 13:16||arnaudr||Note Added: 0016925|
|2022-10-06 00:23||atdtphreaker||Note Added: 0016927|
|2022-10-06 01:37||steev||Note Added: 0016928|
|2022-10-06 01:37||steev||Note Edited: 0016928|
|2022-10-06 01:41||arnaudr||Note Added: 0016929|
|2022-10-06 02:36||atdtphreaker||Note Added: 0016930|
|2022-10-06 04:02||atdtphreaker||Note Added: 0016931|
|2022-10-06 04:24||atdtphreaker||Note Added: 0016932|
|2022-10-06 04:30||atdtphreaker||File Added: USER-GNOME-(dpkg)output-IMG_4956.jpg|
|2022-10-06 04:30||atdtphreaker||Note Added: 0016933|
|2022-10-10 12:22||arnaudr||Note Added: 0016951|
|2022-10-10 20:48||atdtphreaker||File Added: 01-blackSCREEN-IMG_4975-1200x.jpg|
|2022-10-10 20:48||atdtphreaker||File Added: 02-followingKEYTAP-IMG_4981-1200x.jpg|
|2022-10-10 20:48||atdtphreaker||File Added: 03-CTRL-ALT-F2-IMG_4978-1200x.jpg|
|2022-10-10 20:48||atdtphreaker||File Added: 04-MBP-powerbutton-shutsDOWN-IMG_4982-1200x.jpg|
|2022-10-10 20:48||atdtphreaker||Note Added: 0016953|
|2022-10-21 08:34||atdtphreaker||Note Added: 0016987|
|2022-10-21 08:59||arnaudr||Note Added: 0016988|
|2022-10-21 10:11||atdtphreaker||Note Added: 0016989|
|2022-10-22 01:53||atdtphreaker||Note Added: 0016990|
|2023-05-31 14:56||g0tmi1k||Note Added: 0018079|
|2023-05-31 14:56||g0tmi1k||Status||new => closed|