Linux Mint Forums

The zoom "process" is marked Z for zombie, that means it's not a process any longer, just an empty shell so to speak. The reason it still shows up is that its parent process has not picked up its remains. It will not be doing anything or using any resources apart from that entry in the process table...

To count the files, you can try this command in a terminal (after cd to the photos folder): find . -type f | grep -c .thumbs The find command simply prints the names of all files at all levels inside the current directory, one per line. The grep -c then counts how many of those have .thumbs in the f...

Update: it's not the kernel's fault and it's not firefox. I have a memory fault. :( I rebooted after getting a kernel upgrade, and after that, I started my two firefoxes first and then the VirtualBox VM, which is opposite of what I did last time. This time FF was OK but inside the VM, both FF and Vi...

But the OP said it still did not work after a reboot, so this can't be caused by any lingering processes. I agree it's most likely some config file left in an inconsistent state.

I did reboot after that upgrade, but I did not reboot after the upgrade before that. Could that have somehow caused some internal corruption: not rebooting after a kernel upgrade and then getting another upgrade? If so then I can always hope it'll go away if I make sure to reboot after the next one....

Thanks for the tip. My previous kernel was 5.3.0.40.97 so there's something with the latest update. BTW before that update, firefox was eating up memory so fast (with youtube) that I had to restart it every day, that problem has gone away now. Maybe I can hope for a fix soon, but otherwise I may try...

Recently I've had issues with firefox which I first attributed to other causes but I've since eliminated those and also looked closer at when it happened. I now find it started happening within an hour after I had updated the kernel to 5.3.0-42.99 (package linux-generic-hwe-18.04) last Tuesday. This...

Or just do if you're sure it does not contain any files you want to keep.

I had a related issue with my new Mint 19.3 desktop. Not long after everything was set up and running fine, all of a sudden the 412G /home partition was full. :shock: It turned out Timeshift had started to backup the HDD on my other desktop, which I had NFS mounted as /dstore but neglected to put on...

After some time I was again able to start firefox. But now all files and dirs belonging to one of the two users were wiped, and around that time I see this in the syslog: Mar 18 22:41:39 moog systemd[1]: Created slice User Slice of bjorn. Mar 18 22:41:39 moog systemd[1]: Starting User Manager for UI...

OK here are details: System: Host: moog Kernel: 5.3.0-42-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Console: tty 7 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B360M-A v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 2602 dat...

I use directories under /dev/shm for caches to save on writes to the SSD. E.g. I have made .cache/mozilla/firefox into a softlink to /dev/shm/cache/firefox. Of course I have to remember re-creating those after boot but I reboot very seldom. Yesterday morning I had a very mysterious crash of Firefox ...

Gaaaah, so simple and yet so hard to spot: I have moved some cache directories, including those for firefox, to ramdisk to save on disk usage. So e.g. ~/.cache/mozilla/firefox is a softlink to /dev/shm/cache/firefox. Of course I have to recreate those directories after a boot and this is what I hadn...

There is more... If I run firefox -P foo where foo is a profile that does not exist, it does in fact open the Profile Wizard. If I try to start an existing profile, it just exits (exit code 1) but if instead I try to create a new profile, enter a name and click Finish, I get a window with this crypt...

More info. I can run firefox -g and when I say 'run' I get this: [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff69ff700 (LWP 8291)] [Thread 0x7ffff69ff700 (LWP 8291) exited] warning: Corrupted shared library...

I hit the reload on a page right now and FF crashed. So it did when I tried to restart. And the same happens for two different users on the same box. I run Linux Mint 19.3 Mate. When I tried to start firefox from the command line, it said something about not being able to load curl from the binary. ...

I know this is old but I just figured it out: The local directory on the client host that serves as the mount point must be owned by the same user as the directory on the NFS server. Apparently this changed some time between Mint 14 and Mint 19. But I had created that mount point under / as root, so...

Success! :D Although a bit of frustration at first. :? I got an update to the "bleeding edge" sane-backends and noticed the sane-pixma man page was updated with info that Pixma TS5100 was on the list of scanner series that were now recognized, though not guaranteed to be fully supported. So I turned...

A-ha, now I see that I had added this repo on the Mint 17 box to get the latest sane. That explains why I got so frequent updates and why it had a newer version. Now I added this on the Mint 19 and got the same version of sane-pixma. BUT xsane still cannot find the scanner! Something more fundamenta...

Ok it just seems a bit odd that my Mint 17 (based on Ubuntu 14.04) has a more updated sane library. I have noticed that the sane-backends get updated quite often. Yes I installed the drivers from Canon but these are not of any help for using xsane. I also tried to download Vuescan which was mentione...