Linux Lite Forums

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?

(04-26-2021, 02:46 PM)lintek link Wrote: [ -> ]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

(04-27-2021, 04:11 AM)lintek link Wrote: [ -> ]RESULTS

Code:

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=fir...or+code%21
One thing you can try to troubleshoot and narrow down the issue, is download Firefox https://www.mozilla.org/en-US/firefox/al...op-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 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.

(04-27-2021, 02:17 PM)Moltke link Wrote: [ -> ]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

(05-04-2021, 03:00 PM)lintek link Wrote: [ -> ][quote author=Moltke link=topic=8111.msg55753#msg55753 date=1619533041]
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
[/quote]

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...?