Skip to main content

WTF? 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 it is: 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. Uninstalling fixed the prob

Third party flatpak/snaps should be vetted.

#security #opensource #linux #foss

#linux #foss #opensource #security #gnome #Flatpak #malware #Tenacity #missioncenter
in reply to Eugenia L

Tenacity Audio Editor
Tenacity Audio Editor
• •

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.

in reply to Tenacity Audio Editor

Sonny
Sonny
• •

Alright so I couldn't reproduce much except ending Tenacity from MissionCenter does kill the GNOME Session somehow. I'll dig.

Other than that, Tenacity is behaving perfectly fine so I think we can eliminate the malware suspicion for them 😅

Altough it would be awesome to get those permissions in order. @tenacity Let me know if I can help!

Note that with something like htop the process might show under brwap.

@Tenacity Audio Editor
This entry was edited (1 week ago)
in reply to Sonny

Sonny
Sonny
• •

@tenacity
hehe fun bug - for some reason Mission Center associates gnome-session-binary with Tenacity

I filed a bug here https://gitlab.com/mission-center-devs/mission-center/-/issues/190 - consider subscribing to updates in case they need more info.


Mission Center kills the GNOME session when stopping app Tenacity (#190) · Issues · mission-center-devs / Mission Center · GitLab

On Ubuntu 23.10 (GNOME Boxes VM) with Tenacity + Mission Center flatpaks It looks like Mission Center associates Tenacity with gnome-session-binary somehow. Stopping Tenacity kills the...
GitLab
@Tenacity Audio Editor
in reply to Sonny

Sonny
Sonny
• •

@tenacity ok and now I can reproduce "ghost Tenacity" but it's an issue in Mission Control.

After killing Tenacity, Mission Center still shows it even though it's not running.

Killing it ends the user session because because of the bug mentionned above.

@Tenacity Audio Editor
in reply to Sonny

Eugenia L
Eugenia L
• •
@sonny @tenacity Thank you! I have just reinstalled Tenacity and was able to reproduce it as you mentioned (mission control saying that tenacity is open and killing it kills gnome). But I wasn't able to get gjs bloating to 120 MB of RAM. Not sure what was causing that part, might have been coincidental that both things happened around the same time (and resolved together...). I also ran Wireshark just now, didn't see anything out of the ordinary.
@Tenacity Audio Editor @Sonny
in reply to Sonny

Eugenia L
Eugenia L
• •

@sonny @tenacity I have edited the original post to not be so dramatic. :-)

Thank you for your work!

@Tenacity Audio Editor @Sonny
in reply to Sonny

Eugenia L
Eugenia L
• •

@sonny @tenacity I was now able to reproduce the gjs bug where it's using lots of ram (currently using 200 MB of RAM). It wasn't Tenacity's problem. The problem is that every time I open the "Dash to Panel Settings" window, it adds about 30 MB of RAM in the main gjs service.

I'll file a bug with dash-to-panel extension, but i wonder if i should do it for gjs too.

@Tenacity Audio Editor @Sonny
⇧