Linux Lite Forums
Software - Support => Installing Linux Lite => Topic started by: lintek on April 26, 2021, 10:46:02 AM
-
I just recently installed the latest (?) version of Lite and have had a problem of the system freezing up completely.
May be related to Firefox, not sure. Sometimes when I click a button and sometimes just out of the blue, (usually while on Firefox) the system will freeze. Cursor freezes, and nothing works. I have waited in the hopes it will un-freeze but it doesn't. The only way I can fix it is to re-boot.
Any ideas?
-
I just recently installed the latest (?) version of Lite and have had a problem of the system freezing up completely.
May be related to Firefox, not sure. Sometimes when I click a button and sometimes just out of the blue, (usually while on Firefox) the system will freeze. Cursor freezes, and nothing works. I have waited in the hopes it will un-freeze but it doesn't. The only way I can fix it is to re-boot.
Any ideas?
What FF version? While not exactly a solution, you may try launching FF from the terminal and check for any errors, thus to confirm whether is indeed FF's to blame, then you can copy/paste those errors here.
-
How do I launch FF from terminal? I have never done that before.
Thanks
-
Hello lintek,
in terminal, just type firefox then hit your enter key.
-
:011: ok thanks
(sometimes I feel SO dumb...)
-
RESULTS
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
-
RESULTS
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
Well, one thing I can tell you is that you're not alone with this issue, a web search on IPDL protocol error: Handler returned error code! returns result on FF, most of them https://www.google.com/search?client=firefox-b-d&q=IPDL+protocol+error%3A+Handler+returned+error+code%21
One thing you can try to troubleshoot and narrow down the issue, is download Firefox https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
Once you do:
1. Extract the contents of the .tar.gz file, this will result in a folder named firefox
2. Open the firefox folder and locate firefox and firefox-bin files, select each at a time, hit left Alt + Enter, this will open the properties' dialog, check the box that reads make this file executable or some similar wording.
3. Right-click in a blank space within the firefox folder and from the context menu select open terminal here
4. In the terminal type ./firefox and hit Enter to launch the browser, check if you get any errors this time, if you do, then there might be something wrong with your xfce4-session. If you don't, that is, no freezes and FF behaves as expected, then the FF's version installed might be corrupted or something.
EDIT: I just thought of another way:
1. Before downloading FF, open thunar, the file manager.
2. Hit Ctrl + h to show the hidden files.
3. Locate the .mozilla folder.
4. Select it and rename it to something like .mozilla.old
5. Launch Firefox from terminal.
What this will do is launch FF anew; no profile, and will create a new .mozilla folder. So, in theory, if something's wrong with your FF's profile, you shouldn't get any errors. In short, this procedure is to check that your FF's profile isn't corrupted or something, and if you don't get any errors, you could delete .mozilla.old. If you do get the same behavior, the download FF and proceed as explained above.
-
EDIT: I just thought of another way:
1. Before downloading FF, open thunar, the file manager.
2. Hit Ctrl + h to show the hidden files.
3. Locate the .mozilla folder.
4. Select it and rename it to something like .mozilla.old
5. Launch Firefox from terminal.
What this will do is launch FF anew; no profile, and will create a new .mozilla folder. So, in theory, if something's wrong with your FF's profile, you shouldn't get any errors. In short, this procedure is to check that your FF's profile isn't corrupted or something, and if you don't get any errors, you could delete .mozilla.old. If you do get the same behavior, the download FF and proceed as explained above.
I finally had time to try this (1-5, that is). I thought it had worked but after a bit the system froze again. And I am not sure if it is Firefox or not. When it happens it is usually associated with a mouse click or movement. All of a sudden it just freezes.
IT'S MADDENING... :banghead
-
EDIT: I just thought of another way:
1. Before downloading FF, open thunar, the file manager.
2. Hit Ctrl + h to show the hidden files.
3. Locate the .mozilla folder.
4. Select it and rename it to something like .mozilla.old
5. Launch Firefox from terminal.
What this will do is launch FF anew; no profile, and will create a new .mozilla folder. So, in theory, if something's wrong with your FF's profile, you shouldn't get any errors. In short, this procedure is to check that your FF's profile isn't corrupted or something, and if you don't get any errors, you could delete .mozilla.old. If you do get the same behavior, the download FF and proceed as explained above.
I finally had time to try this (1-5, that is). I thought it had worked but after a bit the system froze again. And I am not sure if it is Firefox or not. When it happens it is usually associated with a mouse click or movement. All of a sudden it just freezes.
IT'S MADDENING... :banghead
Did you get any errors in the terminal? You might try my other suggestion on downloading FF from its website, extract and run, and I suggest that you rename the .mozilla folder before doing it, to avoid it gets corrupted(it shouldn't happen, but just in case) and by doing so and launching a fresh FF session, might be better to troubleshoot. All of this is to try and narrow down the problem to discover the possible root of the cause.
-
I didn't get any errors in the terminal so I closed it and deleted mozilla.old and started Firefox from the taskbar like usual. Soon after that it froze. But... like I said - I am not sure if it is the fault of FF - I am just assuming it might be. It also might NOT be...?
-
I didn't get any errors in the terminal so I closed it and deleted mozilla.old and started Firefox from the taskbar like usual. Soon after that it froze. But... like I said - I am not sure if it is the fault of FF - I am just assuming it might be. It also might NOT be...?
I see. Sure, it can be a number of things other than FF, but since you mentioned it, it's a good starting point. That's why I suggested you to download it, to try and see whether it is the installed version the culprit. If it's not, then you can start looking somewhere else, and we can help you do that. :)
-
Hi @lintek ,
As a regular FF user on LL, I guess you have tried to purge the history on FF and also run Lite Tweaks and remove the FF cache.
I could suggest to give a try in order to see whether it solves your problem.
Regards
-
Hi @lintek ,
As a regular FF user on LL, I guess you have tried to purge the history on FF and also run Lite Tweaks and remove the FF cache.
I could suggest to give a try in order to see whether it solves your problem.
Regards
Thanks for the advice - I am not really a regular user AND I am a true novice at Linux, even though I've been using it for a while... ;D
-
Well... I don't think it is Firefox anymore.
I decided to try using it without using Firefox. After a couple minutes, it froze up.
Maybe Jerry has an idea? Maybe it is just a bad install? I just don't get it... :012:
-
Open the terminal and run this
sudo journalctl priority err --since "10 min ago"
You can replace "10 min ago" if you want by another time, i.e. "20 min ago", and look for any error messages in the output, you can also copy/paste the output here in your reply. If you get -- no entries try running it without the "--since "10 min ago"". For more info run man journalctl
-
Tried line 1 - got this
"Failed to add match 'priority': Invalid argument"
Also tried upgrading from 5.2 to 5.4
NO LUCK. I am about ready to just reinstall.
-
Tried line 1 - got this
"Failed to add match 'priority': Invalid argument"
Also tried upgrading from 5.2 to 5.4
NO LUCK. I am about ready to just reinstall.
Oops! Sorry, my bad! I missed "--" before and "=" after priority this is the correct command
sudo journalctl --priority=err --since "10 min ago"
Again, really sorry I didn't realize that earlier when I posted. Try again, it should work this time.
-
I am about ready to shoot my Linux Lite.
Since I can barely try any of the things you suggest due to freezing up, I decided to drop in a new hard rive and load a fresh copy of 5.4 onto it.
AND IT STILL FROZE UP. With Firefox on, with firefox off, with chromium on with chromium off, with a different mouse, etc etc.
At this point I cannot imagine what is causing this.
But this is a dual boot computer and luckily my old copy of Windows 7 works.
-
While in the desktop, xfce, press Ctrl + Alt + F1 to jump to a TTY(command line mode) login with your credentials; username and password. Then run the journalctl command, but since you can't copy/paste the output in that mode, you'll have to redirect it to a file, like this
sudo journalctl --priority=err --since "30 min ago" > journalctl_output name it whatever else you want to, the file will be saved in your home directory, if by any chance you get no output, or it is too short, like 3 lines short or something like that, you can, 1) increase the time, i.e. "60", 2) run without time which will print the whole thing in which case you'll have to attach the file in your reply since it'll be very long for coping/pasting, once you've done that, press Ctrl + d to logout from that session, then press Ctrl + Alt + F7 to return to the desktop session, find the file, open it in a text editor and copy/paste the output here, or attach it if it is too long as explained above. The system shouldn't freeze in that mode, and if it does, then the problem might be a graphics related thing, I think. The output of journalctl might give us a hint whether it is or not.
-
journalctl_output
-- Logs begin at Sat 2021-05-08 00:08:36 CDT, end at Tue 2021-05-11 23:47:25 CDT. --
May 11 23:42:54 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:42:59 linux-DX4860 ntpd[1214]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:00 linux-DX4860 /hpfax[1260]: [1260]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:43:00 linux-DX4860 ntpd[1214]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:01 linux-DX4860 ntpd[1214]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:01 linux-DX4860 nmbd[1301]: [2021/05/11 23:43:01.784944, 0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:43:01 linux-DX4860 nmbd[1301]: daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:43:01 linux-DX4860 nmbd[1301]: [2021/05/11 23:43:01.785037, 0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:43:01 linux-DX4860 nmbd[1301]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:43:02 linux-DX4860 ntpd[1214]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:03 linux-DX4860 ntpd[1214]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:43:32 linux-DX4860 pulseaudio[1287]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
-- Reboot --
May 11 23:44:22 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:44:26 linux-DX4860 ntpd[1169]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:27 linux-DX4860 ntpd[1169]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:27 linux-DX4860 /hpfax[1211]: [1211]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:44:28 linux-DX4860 ntpd[1169]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:29 linux-DX4860 nmbd[1227]: [2021/05/11 23:44:29.407539, 0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:44:29 linux-DX4860 nmbd[1227]: daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:44:29 linux-DX4860 nmbd[1227]: [2021/05/11 23:44:29.407610, 0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:44:29 linux-DX4860 nmbd[1227]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:44:29 linux-DX4860 ntpd[1169]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:30 linux-DX4860 ntpd[1169]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:45:00 linux-DX4860 pulseaudio[1245]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
-- Reboot --
May 11 23:45:57 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:46:01 linux-DX4860 ntpd[1173]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:02 linux-DX4860 ntpd[1173]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:02 linux-DX4860 /hpfax[1222]: [1222]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:46:03 linux-DX4860 ntpd[1173]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:04 linux-DX4860 nmbd[1231]: [2021/05/11 23:46:04.320142, 0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:46:04 linux-DX4860 nmbd[1231]: daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:46:04 linux-DX4860 nmbd[1231]: [2021/05/11 23:46:04.320892, 0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:46:04 linux-DX4860 nmbd[1231]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:46:04 linux-DX4860 ntpd[1173]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:05 linux-DX4860 ntpd[1173]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:46:35 linux-DX4860 pulseaudio[1249]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May 11 23:47:05 linux-DX4860 ntpd[1173]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:08 linux-DX4860 ntpd[1173]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:08 linux-DX4860 ntpd[1173]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:10 linux-DX4860 ntpd[1173]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:11 linux-DX4860 ntpd[1173]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
-
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.
-
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.
-
Hi @lintek ,
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
-
I tried what you said - this is what happened.
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. :shrug
-
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.
-
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.
-
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.
-
Ok - I will try when I have a bit of time. I do appreciate all of your help!
-
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!
-
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, @lintek . It has all your old desktop settings and stuff, and saving them from one distro to another can foul up any desktop.