Fossapup is randomly unable to save to the pupsave and power down.

[RadoslavL]

Sometimes when I run Puppy Linux for a long time, it starts being unable to save to the save file and to power off. I noticed it happens everytime I lock the session, even if I don't actually lock it, but rather just press the X on the popup after pressing the lock screen button. That's the only persistent thing I noticed about it. After I found it out I decided to not lock the screen and see if it happens again and it did. After it starts happening some programs just fail to launch (such as Firefox), and when I open htop, I can see that all "sync" processes have hanged with a 'D' next to them (I think it means it is stuck while executed by the kernel, but am not sure). What does this mean and is there any explanation to it? I can provide any further information you need.

[bigpup]

Has Fossapup64 9.5 been updated?

Quickpet -> Info -> Fossapup updates

[bigpup]

Sometimes when I run Puppy Linux for a long time, it starts being unable to save to the save file and to power off.

What are you typically doing when running for a long time?

Does it have a save icon on the desktop?
If yes.

What settings do you have in the Puppy Event Manger -> Save Session?

[RadoslavL]

Has Fossapup64 9.5 been updated?

Quickpet -> Info -> Fossapup updates

Yes, I have the latest version.

[RadoslavL]

Sometimes when I run Puppy Linux for a long time, it starts being unable to save to the save file and to power off.

What are you typically doing when running for a long time?

Does it have a save icon on the desktop?
If yes.

What settings do you have in the Puppy Event Manger -> Save Session?

I just used Firefox and qBittorrent and left them running and when I came back, it started happening. It was also occuring everytime I lock the screen.
Edit: Nevermind, it happens completely randomly.

Yes, I have a save icon on my desktop.

My current save settings are:
"Save interval: 0 (never)"
"Ask to save session at shutdown: yes"
"Show tray icon: yes"

[mikewalsh]

Don't understand THIS one!

I often have the same Puppy "up" for a couple of weeks at a time, only suspending overnight. I've never had anything like the issue described here, not in almost 10 years of using Puppy.

Yes, I get the odd freeze here & there, but more often than not it's my own doing.....a result of some change or other that I made, manually, through a conscious decision to do so.

The only thing I can think of is that the OP has had a bad download, or something didn't go quite right during the install. Possibly RAM is starting to go bad, though MemTest+ may be able to lay that one to rest.....

Maybe dirty contacts, or......? Sorry, run out of ideas.

Mike.

[bigpup]

I just used Firefox and qBittorrent and left them running

Try not having qBittorrent running and see if this stops the issue.

With the save settings you have.

qBittorrent could be filling up memory.

what version of Firefox?

Could have Firefox leaking memory or doing Internet accessing in the background (prefetching) that is using up the memory.

[RadoslavL]

I just used Firefox and qBittorrent and left them running

Try not having qBittorrent running and see if this stops the issue.

With the save settings you have.

qBittorrent could be filling up memory.

what version of Firefox?

Could have Firefox leaking memory or doing Internet accessing in the background (prefetching) that is using up the memory.

I reinstalled with a newly downloaded iso, and it stopped happening. I don't have qBittorrent installed yet.

[RadoslavL]

It started happening again and I think it is caused by qBittorrent. I just left it for a couple of minutes and it still happened.

[pp4mnklinux]

The same happened to me, but now I discovered what was my problem.

It happened when I wrote info from my puppy to an USB.

If I coppied a big file, although the USB is not reading/writing , I can't turn off o suspend or reboot my computer, so I need to unmount it.

[RadoslavL]

The same happened to me, but now I discovered what was my problem.

It happened when I wrote info from my puppy to an USB.

If I coppied a big file, although the USB is not reading/writing , I can't turn off o suspend or reboot my computer, so I need to unmount it.

What did you do to solve it? I might have the same problem. I am using qBittorrent to download a file on my USB drive and that could be the reason.

[pp4mnklinux]

Hi @RadoslavL :

What I did is go to my file browser (PcManFm) and right click on the USB icon, and choose unmount.

I must tell you that this frequently takes a lot of time, and it is possible you must use your pc button to restar it.

I don't know what happen this, but makes impossible to shutdown.

I'll try later and tell u a more specific answer.... I hope

Have a nice day.-

[RadoslavL]

Update: It is surely because of qBittorrent, as without it nothing like this occurs.

Is this a problem with qBittorrent or with Puppy Linux? Is there any way I can fix it? It is consistently happening with the latest Fossapup64 iso.

[pp4mnklinux]

I modified this to allow suspend, take a look to the acpi folder and delete options that dont allow shutdown if media mounted.

viewtopic.php?t=8463#p86634

[d-pupp]

This is just a thought but if you are downloading big files your memory it filling up as pups using usb are set to write to the drive only when you click save or at whatever time interval you have it set at.
This is to reduce the number of writes to the usb and increase it's life. However it will also use up all you memory causing the computer to act up and freeze.
How much memory do you have by the way?

[RadoslavL]

How much memory do you have by the way?

To be honest I am not sure. I think I have 4GB.

I've noticed this occurs when I write big files to my Puppy Linux USB. Any program that does this freezes the system (all sync processes simply hang and that makes shutting down and saving not possible).

[pp4mnklinux]

Yeah this happens (for me) when there is not enough space to save the file in the USB.

My puppy goes crazy and blocked, haha.

[RadoslavL]

Yeah this happens (for me) when there is not enough space to save the file in the USB.

My puppy goes crazy and blocked, haha.

It happens when I write a big file to the USB drive (not the filesystem in memory) and shouldn't result in this behavior. It even happens with the bittorrent program shipped with Fossapup64. This shouldn't be happening.

When it happens there are a bunch of sync processes that just hang and don't allow powering off and even restarting X11. The system is still usable if you don't want to power it off and save (all of the functions that call the sync process).

[bigpup]

Is Fossapup64 running from the USB drive?
If yes.

When doing the downloads, what location are you downloading to?
If it is not /mnt/home try to make the downloads go to this location.

/mnt/home is the top layer of the USB drive partition and is not a location in the fossapupsave.
So the download should go directly written to the USB drive partition and not go into memory, to later be written to the save.

any help?

I am not using these torrent programs and know little about them.
But do seem to remember ones I have used.
They can be set to allow people to access stuff on your computer to download to theirs.
So the program, could be downloading from your computer to others, and using memory and CPU processing, in the background.
Thus using up memory and CPU processes.

[RadoslavL]

Is Fossapup64 running from the USB drive?

When doing the downloads, what location are you downloading to?

So the program, could be downloading from your computer to others, and using memory and CPU processing, in the background.
Thus using up memory and CPU processes.

It is running from the USB drive.

I am downloading to /mnt/home. I think downloading to a location that is a part of the save file, wouldn't make this issue happen.

Yes, I understand it could be using up resources, but I don't think there is anything I could do about it. It happens with the bittorrent program shipped with Fossapup64 and that makes me think that this is a bug (why would a bittorrent program be shipped with the distro, if it doesn't work with it in particular).

[bigpup]

I am downloading to /mnt/home. I think downloading to a location that is a part of the save file, wouldn't make this issue happen

/mnt/home is the correct location to download to.

Downloading to a location in the save is going to eat up RAM memory.
Puppy booting from a USB and having the save on the USB, is running in pupmode 13.
Stuff going into the save, is first placed in a saveramdisk (section of RAM) and later actually written to the save. Cuts down on number of writes to the USB, to make it last longer.
USB drives have a max number of writes before they start going bad.

[d-pupp]

This may be a memory leak in qbit
A quick search of "qbittorrent memory leak" show a lot of other's with the same problem

[bigpup]

qBittorrent has a lot of options in it's preferences settings. (tools -> Preferences)

Many of them could be affecting this issue.

Sorry, but I no longer use these type programs and do not know what most of these options do or do not do.

But from past use of torrent programs.

The preference settings can have a big affect on how the operation works and affects the computer.

[bigpup]

It happens with the bittorrent program shipped with Fossapup64 and that makes me think that this is a bug (why would a bittorrent program be shipped with the distro,
if it doesn't work with it in particular).

qBittorrent did not come preinstalled in Fossapup64 9.5.

But it is available in the Puppy Package Manager (PPM)
I see that PPM is getting it from a Ubuntu repository.
qBittorrent v4.1.7
So Ubuntu is providing the program not Fossapup64.

When you find a software program, that gets released, with 100% no bugs in it.
Never going to happen!
Bug fixing is what program updates is all about.

Here is a newer version of qBittorrent v4.5.2
https://www.fosshub.com/qBittorrent.htm ... 4.AppImage

It is an appimage package.

Do you know how to use and run appimages?

[RadoslavL]

It happens with the bittorrent program shipped with Fossapup64 and that makes me think that this is a bug (why would a bittorrent program be shipped with the distro,
if it doesn't work with it in particular).

qBittorrent did not come preinstalled in Fossapup64 9.5.

Do you know how to use and run appimages?

I was talking about uGet, as it is available in Fossapup64, and the bug happens with it as well.

I know how to use AppImages, but I don't think the newer version will fix it.

[bigpup]

Remember we only know what you tell us.

So you are not going to try the newer version of qBittorrent?

I was talking about uGet, as it is available in Fossapup64, and the bug happens with it as well.

That requires a new topic to talk about it's issue.