fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.7K
active users

Is #Tenacity on the #Flatpak store malware? Apparently it was running in the bg AS IF it was an invincible #Gnome extension so SystemMonitor/htop would NOT see it as a process. But #MissionCenter (also from flatpak store) saw it as an app running on startup! Killing it killed Gnome session! It was also spiking wifi, and was leaking the Gnome gjs service from 4MB RAM to 120MB.

Third party flatpak/snaps should be vetted.

UPDATE: mystery solved in the comments. Not malware.

@eugenialoli That behavior sounds very suspicious. We'll check it out whenever we can.

Tenacity does NOT, or should not, use ANY networking. To have Internet usage in general is extremely suspicious.

Also, the Tenacity Flatpak is official. We maintain it ourselves.

Tenacity Audio Editor

@eugenialoli To further add, Tenacity itself doesn't interact with gjs, so maybe it's some component inside the Flatpak.

@tenacity @sonny
I see. Thank you for the reply. Yes, it's possible that it's something inside flatpak that did all that. I don't know. I wish I had taken some screenshots, or used wireshark before uninstalling the app. I thought of it afterwards...

@eugenialoli @sonny No worries!

When did you notice any of these symptoms? Did you notice them when you first installed Tenacity or after a period of usage?

@tenacity @sonny I only noticed it today. I have had tenacity installed for months now, but I hadn't really used it, as I don't use this laptop much. I noticed it after gjs was bloating to 120 mb of ram out of nowhere, and after happened to load Mission Center app and noticed that Tenacity was running, even if I had not load it for ages (and have had many reboots in the meantime).

@eugenialoli @sonny Tenacity has no reason to run in the background either. It shouldn't have background permissions either, but we'll investigate accordingly.