LINUX LITE 7.4 FINAL RELEASED - SEE RELEASE ANNOUNCEMENTS SECTION FOR DETAILS


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
System freeze-up
#21
Just to be clear, is that output from right after the system froze? If it is, there are some errors that might explain the freezing issue.
Without each others help there ain't no hope for us Smile
Need a translation service? https://www.deepl.com/es/translator
Reply
#22
That is the output before the system had a chance to freeze.  If I hit Ctrl+Alt+F1 then the only thing that happens is I lose my cursor and can't do anything (much like when the system freezes) and I have to hold down power button to reboot.
Reply
#23
Hi [member=9729]lintek[/member] ,
I think you have the Network Manager down which can be solved whether you could type the folloswing command in a terminal:
systemctl status avahi-daemon.service

The output text on the terminal looks like this:

systemctl status avahi-daemon.service
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
    Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor >
    Active: active (running) since Wed 2021-05-12 15:43:13 -03; 12min ago
TriggeredBy: ● avahi-daemon.socket
  Main PID: 655 (avahi-daemon)
    Status: "avahi-daemon 0.7 starting up."
      Tasks: 2 (limit: 9042)
    Memory: 2.1M
    CGroup: /system.slice/avahi-daemon.service
            ├─655 avahi-daemon: running [jochoa-pc.local]
            └─730 avahi-daemon: chroot helper
.......

Then, go to your Network Manager icon on the task bar and click on it and disable Enable Networking (whichi is ticked).
Afterwards, click on the icon and check the Enable Networking.


Hope this help, regards
Reply
#24
I tried what you said - this is what happened.
Code:
May 12 14:24:42 linux-DX4860 avahi-daemon[906]: New relevant interface wlp3s0.IPv6 for mDNS.
May 12 14:24:42 linux-DX4860 avahi-daemon[906]: Registering new address record for fe80::7253:5e21:7b24:bc66 on wlp3s0.*.
May 12 14:24:43 linux-DX4860 avahi-daemon[906]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.2.
May 12 14:24:43 linux-DX4860 avahi-daemon[906]: New relevant interface wlp3s0.IPv4 for mDNS.
May 12 14:24:43 linux-DX4860 avahi-daemon[906]: Registering new address record for 192.168.1.2 on wlp3s0.IPv4.
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::7253:5e21:7b24:bc66.
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address 2600:100c:b01e:66ac:fd3a:2>
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Registering new address record for 2600:100c:b01e:66ac:fd3a:2c53:888e:fa8f on wlp3s0.*.
May 12 14:24:49 linux-DX4860 avahi-daemon[906]: Withdrawing address record for fe80::7253:5e21:7b24:bc66 on wlp3s0.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~

linux  ~  130 

Not sure if it worked or not, because now Linux won't even log into the network connections that I have been using.  I have two and I have used both with Linux, now it fails to log into them.

Also, I really don't understand how I still have the same problem I started with considering I uploaded a complete fresh install of 5.4, on a NEW hard drive.    Confusedhrug

Reply
#25
(05-12-2021, 03:43 PM)lintek link Wrote: That is the output before the system had a chance to freeze.  If I hit Ctrl+Alt+F1 then the only thing that happens is I lose my cursor and can't do anything (much like when the system freezes) and I have to hold down power button to reboot.

Ok, I'll try to explain better this time:
1. By pressing Ctrl + Alt + F1 you'll be dropped to a console; a black screen with a blinking cursor, give it a few seconds and you'll see login type in your username and password, press enter and you'll be logged in a  TTY, you can issue commands from there, navigate the system, and do pretty much the same things you can in a terminal from the desktop, but the mouse won't work while in there, that's normal.
2. In that console run the journalctl command, because the messages you posted are from when you rebooted the machine.
3. It would be better if you did this when the system freezes, just be patient after pressing those keys and wait until the TTY starts, then proceed as explained above.
Without each others help there ain't no hope for us Smile
Need a translation service? https://www.deepl.com/es/translator
Reply
#26
What I am saying is I did hit CTRL+ALT+F1 and I did NOT get the terminal.  The cursor disappeared and that was it.  I had to reboot.
Reply
#27
(05-13-2021, 04:59 AM)lintek link Wrote: What I am saying is I did hit CTRL+ALT+F1 and I did NOT get the terminal.  The cursor disappeared and that was it.  I had to reboot.

Hmmm ... Well, try with Ctrl + Alt + F3 you have 6 TTYs to open from F1-F6. Maybe F1 was busy. However, like I said, give it a few seconds for the TTY to start, just don't reboot right away. If you can't do that, open a file manager, navigate to /var/log/, locate the messages file and copy it to your /home directory, and attach the file in your reply.
Without each others help there ain't no hope for us Smile
Need a translation service? https://www.deepl.com/es/translator
Reply
#28
Ok - I will try when I have a bit of time.  I do appreciate all of your help!
Reply
#29
At least for now I am abandoning this thread - I fixed the problem by installing Linux Mint.

I haven't ever spent much time with Mint and since LL doesn't like my computer right now (and Mint does) I will see how this works for me.  I really appreciate all of the help from you guys and I'm not going anywhere because I have a few computers with  LL on them.

THANKS!
Reply
#30
Try out the Xfce flavor. It may be better on resources than the standard Mint. But I still think preserving the /home partition is what messed you up, [member=9729]lintek[/member] . It has all your old desktop settings and stuff, and saving them from one distro to another can foul up any desktop.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)