Cannot enter OS

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
mahnwp
Posts: 19
Joined: Fri Nov 04, 2022 4:59 am

Cannot enter OS

#1 Post by mahnwp »

Hello. Please help! Earlier several times there was a message like "systray... missing... restart..." with options to execute and remove. The point is the interference with the tray icon. Some icons are missing. Several times I used MX Tweak to return to default settings and it worked but only for a while. Such incidents occurred several times.
I kept using my laptop until some time later. Then comes the disappearance of the icon but this time it's on the panel (taskbar), not the tray icon anymore. This results in the loss of all currently open windows. When I try to open or run a new program, it works. But I tried minimizing it, I can't bring up the window again because it's not in the panel.
Then I turn it off. I let it rest for about 5 minutes. I restarted hoping it was back to normal. When it's on, the login page appears. But my username doesn't appear. Like a fresh OS install. I tried several accesses like root, demo, etc. Login failed.
The changes that have occurred on my laptop recently are limited to using VSCode, Jupyterlab, Conda, installing or updating Python and its derivatives. So all the changes are just about that because I'm learning Python and Data Analysis.
I can only attach the OS and device info of the first copy. Maybe there will be a difference but I believe not much will change. A significant change like a different version of MX Linux, I updated from 21.2 to 21.3 about a month ago.
Please help what should I do?

Code: Select all

 System:    Kernel: 5.10.0-19-amd64 [5.10.149-2] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21.2.1_x64 Wildflower September 18  2022 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: LENOVO product: 81MU v: Lenovo IdeaPad S145-14IWL serial: <filter> 
           Chassis: type: 10 v: Lenovo IdeaPad S145-14IWL serial: <filter> 
           Mobo: LENOVO model: LNVNB161216 v: SDK0Q55754 WIN serial: <filter> UEFI: LENOVO 
           v: ASCN51WW date: 05/14/2021 
Battery:   ID-1: BAT0 charge: 18.8 Wh (74.9%) condition: 25.1/30.0 Wh (83.7%) volts: 7.8 min: 7.5 
           model: SMP L16M2PB1 type: Li-poly serial: <filter> status: Discharging cycles: 418 
CPU:       Info: Dual Core model: Intel Celeron 4205U bits: 64 type: MCP arch: Kaby Lake 
           note: check family: 6 model-id: 8E (142) stepping: B (11) microcode: F0 cache: 
           L2: 2 MiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 7200 
           Speed: 1194 MHz min/max: 400/1800 MHz Core speeds (MHz): 1: 1194 2: 1194 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf status: Not affected 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown status: Not affected 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled 
           Type: retbleed mitigation: IBRS 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel vendor: Lenovo driver: i915 v: kernel bus-ID: 00:02.0 
           chip-ID: 8086:3ea1 class-ID: 0300 
           Device-2: Syntek Integrated Camera type: USB driver: uvcvideo bus-ID: 1-7:2 
           chip-ID: 174f:1176 class-ID: 0e02 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") 
           s-diag: 414mm (16.3") 
           Monitor-1: eDP-1 res: 1366x768 hz: 60 dpi: 112 size: 309x173mm (12.2x6.8") 
           diag: 354mm (13.9") 
           OpenGL: renderer: Mesa Intel UHD Graphics 610 (WHL GT1) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio vendor: Lenovo 
           driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci bus-ID: 00:1f.3 
           chip-ID: 8086:9dc8 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-19-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Lenovo 
           driver: ath10k_pci v: kernel modules: wl port: 3040 bus-ID: 01:00.0 chip-ID: 168c:0042 
           class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:3 
           chip-ID: 0cf3:e500 class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 3 state: down bt-service: N/A rfk-block: 
           hardware: no software: yes address: <filter> 
           Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff 
           link-mode: slave accept 
Drives:    Local Storage: total: 238.47 GiB used: 24.28 GiB (10.2%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Ramaxel model: RTOTJ256VGD2MYX size: 238.47 GiB 
           block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> 
           rev: 1 scheme: GPT 
Partition: ID-1: / raw-size: 132.58 GiB size: 129.44 GiB (97.63%) used: 10.91 GiB (8.4%) fs: ext4 
           dev: /dev/sda2 maj-min: 8:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat 
           dev: /dev/sda1 maj-min: 8:1 
           ID-3: /home raw-size: 100.01 GiB size: 97.88 GiB (97.87%) used: 13.37 GiB (13.7%) 
           fs: ext4 dev: /dev/sda4 maj-min: 8:4 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 5.62 GiB used: 2.5 MiB (0.0%) priority: -2 
           dev: /dev/sda3 maj-min: 8:3 
Sensors:   System Temperatures: cpu: 41.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2263 lib: 1195 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/megasync.list 
           1: deb [signed-by=/usr/share/keyrings/meganz-archive-keyring.gpg] https://mega.nz/linux/repo/Debian_11/ ./
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://kartolo.sby.datautama.net.id/mx-packages/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list 
           1: deb https://download.onlyoffice.com/repo/debian squeeze main
           Active apt repos in: /etc/apt/sources.list.d/slack.list 
           1: deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 215 Uptime: 2h 21m wakeups: 2 Memory: 3.72 GiB used: 2.16 GiB (57.9%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: N/A 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

User avatar
j2mcgreg
Global Moderator
Posts: 7233
Joined: Tue Oct 23, 2007 12:04 pm

Re: Cannot enter OS

#2 Post by j2mcgreg »

A couple of things to try:
-- if you can access a terminal, run this command:

Code: Select all

sudo adduser username
Give "username" a password and accept the defaults for the prompts that follow. Once the procedure is complete, close the terminal, reboot and try to login as the new user. If you can successfully login and the desktop is back to normal, you can copy the contents of your old home folder to the new one and then delete the old user.

If the above is not successful for any reason, you should first check the SMART status of your SSD in the bios, and if it passes you need to seriously consider a reinstall.

Note: Upgrading from MX 21.2 to MX 21.3 would have no bearing on this mess.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

mahnwp
Posts: 19
Joined: Fri Nov 04, 2022 4:59 am

Re: Cannot enter OS

#3 Post by mahnwp »

j2mcgreg wrote: Sat Apr 29, 2023 9:46 am A couple of things to try:
-- if you can access a terminal, run this command:

Code: Select all

sudo adduser username
Give "username" a password and accept the defaults for the prompts that follow. Once the procedure is complete, close the terminal, reboot and try to login as the new user. If you can successfully login and the desktop is back to normal, you can copy the contents of your old home folder to the new one and then delete the old user.

If the above is not successful for any reason, you should first check the SMART status of your SSD in the bios, and if it passes you need to seriously consider a reinstall.

Note: Upgrading from MX 21.2 to MX 21.3 would have no bearing on this mess.
Thank you for replying. I want to correct the information that I "should" be able to enter. But the description on the login page is "failed to start session". Earlier I was also able to enter the terminal by CTRL + ALT + F9. Next, what should I do?

mahnwp
Posts: 19
Joined: Fri Nov 04, 2022 4:59 am

Re: Cannot enter OS

#4 Post by mahnwp »

I try to do

Code: Select all

df
di terminal,
/dev/loop0 and /dev/loop1 Its usage is already 100%. Does it affect?

User avatar
j2mcgreg
Global Moderator
Posts: 7233
Joined: Tue Oct 23, 2007 12:04 pm

Re: Cannot enter OS

#5 Post by j2mcgreg »

mahnwp wrote: Sat Apr 29, 2023 10:07 am I try to do

Code: Select all

df
di terminal,
/dev/loop0 and /dev/loop1 Its usage is already 100%. Does it affect?
That generally means that your home partition is full, but your QSI shows only 13.7% usage, so it's clearly not the case..

You really need to check the status of your SSD in the bios and replace it if it is going bad. It's seven years old and that's in the age range where they start to fail. In any event, I think that you are going to have to reinstall because there is no way we will be able to determine what Python commands you ran and in what sequence in order to undo the damage. I also think that you should acquire a second laptop that you can use as a test bed.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
CharlesV
Administrator
Posts: 8101
Joined: Sun Jul 07, 2019 5:11 pm

Re: Cannot enter OS

#6 Post by CharlesV »

I can only attach the OS and device info of the first copy.
That QSI was taken on the first MX load?

If so, much could have transpired since when ever that was. I think @j2mcgreg is right about space. Try to make some space on your home partition. Maybe start with the area you put your last data you have been working with for data analysis ( real data sets can get large, and if your saving results...?
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

mahnwp
Posts: 19
Joined: Fri Nov 04, 2022 4:59 am

Re: Cannot enter OS

#7 Post by mahnwp »

Code: Select all

df
You do not have the required permissions to view the files attached to this post.

mahnwp
Posts: 19
Joined: Fri Nov 04, 2022 4:59 am

Re: Cannot enter OS

#8 Post by mahnwp »

j2mcgreg wrote: Sat Apr 29, 2023 10:54 am
mahnwp wrote: Sat Apr 29, 2023 10:07 am I try to do

Code: Select all

df
di terminal,
/dev/loop0 and /dev/loop1 Its usage is already 100%. Does it affect?
That generally means that your home partition is full, but your QSI shows only 13.7% usage, so it's clearly not the case..

You really need to check the status of your SSD in the bios and replace it if it is going bad. It's seven years old and that's in the age range where they start to fail. In any event, I think that you are going to have to reinstall because there is no way we will be able to determine what Python commands you ran and in what sequence in order to undo the damage. I also think that you should acquire a second laptop that you can use as a test bed.
Thank you for replying. I just ran a SMART test through the terminal and was asked to wait 15 minutes for the test to finish. I chose /dev/sda4/ directory is it correct? Even though I'm a newbie to Linux, I'm not sure that any Python-related activity is causing an interruption.

mahnwp
Posts: 19
Joined: Fri Nov 04, 2022 4:59 am

Re: Cannot enter OS

#9 Post by mahnwp »

CharlesV wrote: Sat Apr 29, 2023 11:05 am
I can only attach the OS and device info of the first copy.
That QSI was taken on the first MX load?

If so, much could have transpired since when ever that was. I think @j2mcgreg is right about space. Try to make some space on your home partition. Maybe start with the area you put your last data you have been working with for data analysis ( real data sets can get large, and if your saving results...?
Thank you for replying. I mean, the QSI that I attached is the QSI some time ago before this problem occurred and before updating to the latest MX. I'm attaching it because I don't know how to attach the latest QSI--if it's still possible, even though I can't enter the interface. The capacity of /home is 82% used. Any suggestions?

User avatar
CharlesV
Administrator
Posts: 8101
Joined: Sun Jul 07, 2019 5:11 pm

Re: Cannot enter OS

#10 Post by CharlesV »

if you try to start xfce manually do you see any error messages ?

Code: Select all

startx
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

Post Reply

Return to “MX Help”