While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- GE-Proton 9-3 and 9-4 released with a new option to help with modded games
- MineClone2, inspired by Minecraft, gets renamed to VoxeLibre
- Bazzite v2.5 has fixes for Lenovo Legion Go and ASUS ROG Ally, plus smoother installs
- Half-Life remake Black Mesa has a big upgrade with DXVK 2.3.1, optimizations and bug fixes
- OpenTTD 14.0 brings a scalable font, a new ship pathfinder, social platform integration
- > See more over 30 days here
-
Former Nouveau driver lead joins NVIDIA and sent a mass…
- LoudTechie -
Free Stars: Children of Infinity coming to Linux after …
- Eike -
Former Nouveau driver lead joins NVIDIA and sent a mass…
- slaapliedje -
Team Fortress 2 64bit support released, plus Vulkan for…
- chickenb00 -
Former Nouveau driver lead joins NVIDIA and sent a mass…
- kokoko3k - > See more comments
Latest Forum Posts
- Weekend Players' Club 4/19/2024
- Pengling - The Evercade Outpost!
- Pengling - What sorta display and audio setup do you folks got?
- Shmerl - Weekend Players' Club 4/12/2024
- Pengling - Deus Ex GOTY Weird Resolution Issue on Steam But Not GOG…
- Vortex_Acherontic - See more posts
audit: type=1400 audit(1527966934.264:44308): apparmor="DENIED" operation="ptrace" profile="snap.discord.discord" pid=15446 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
[37158.620284] audit: type=1400 audit(1527966934.264:44309): apparmor="DENIED" operation="open" profile="snap.discord.discord" name="/proc/2521/cmdline" pid=15446 comm="Discord" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[37158.620292] audit: type=1400 audit(1527966934.264:44310): apparmor="DENIED" operation="open" profile="snap.discord.discord" name="/proc/2539/cmdline" pid=15446 comm="Discord" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[37158.620297] audit: type=1400 audit(1527966934.264:44311): apparmor="DENIED" operation="ptrace" profile="snap.discord.discord" pid=15446 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
[37158.620313] audit: type=1400 audit(1527966934.264:44312): apparmor="DENIED" operation="ptrace" profile="snap.discord.discord" pid=15446 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
[37158.620331] audit: type=1400 audit(1527966934.264:44313): apparmor="DENIED" operation="open" profile="snap.discord.discord" name="/proc/2634/cmdline" pid=15446 comm="Discord" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[37158.620336] audit: type=1400 audit(1527966934.264:44314): apparmor="DENIED" operation="ptrace" profile="snap.discord.discord" pid=15446 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
[37158.620350] audit: type=1400 audit(1527966934.264:44315): apparmor="DENIED" operation="ptrace" profile="snap.discord.discord" pid=15446 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
[37158.620361] audit: type=1400 audit(1527966934.264:44316): apparmor="DENIED" operation="ptrace" profile="snap.discord.discord" pid=15446 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
[37158.620372] audit: type=1400 audit(1527966934.264:44317): apparmor="DENIED" operation="ptrace" profile="snap.discord.discord" pid=15446 comm="Discord" requested_mask="trace" denied_mask="trace" peer="unconfined"
PID2Process:
15446 = discord
2521 = (sd-pam)
2539 = gnome-keyring-daemon
2634 = ssh-agent
It spams up the kernel buffer. I'm not the first to notice that:
https://github.com/snapcrafters/discord/issues/2
Sorry, never done anything with snaps before.
View PC info
View PC info
And devnull... I tried to report an issue to them, it was a frustrating experience...
How they did this? By IP or username or what means "banned"?
I normally only use Mumble. But everyone always asks for Discord.
The client is running. I wonder why it's constantly trying to access the gnome key ring. Is there a way to turn that off?
View PC info
Username.
Ironically debian is part of the problem, false sense of security. AFAIK the same telemetry applies to you anyway unless debian completely recompiled the client? Hit F12 to watch the console or look at your firewall.
Could it be because you enabled save password? Honestly don't know, didn't do that.
I think Discord just does it for whatever reason. If you install it normally via the package manager like nox, there is maybe no AppAmor profile for the application in this case.
I have not been able to determine any functional limitations so far. But Discord tries the calls every few seconds. And I wonder what they're good for. I haven't found anything useful on the net yet. Not a big problem, I guess. But annoying.
However, I would be interested to know why they banned you. That's a bit of a serious problem if that happens.
Discord has a "feature" where it automatically tells all your Discord friends what game you're playing, with a "Playing World of Warcraft" (or whatever game) below your name on your friend's Discord panel(s).
Discord implements this feature by doing a scan, once every five seconds, of every numeric entry in the /proc file system. Let's say your current Linux user id is "joe", and one (of hundreds) of processes you are running is process pid == 999. Then Discord will first stat "/proc/999", and if that proc directory is owned by yourself, "joe", it will then further try to "open /proc/999/cmdline" and " readlink /proc/999/exe", in an effort to see if you're also running a recognized game executable. If (for example) it sees that you're running a World of Warcraft executable, it will tell your connected friend's Discords to add the "Playing ..." annotation below your name "Joe" on their Discord. The above stat of "/proc/999" call does not generate an error (when run by Discord inside a snap sandbox), but the additional two " open /proc/999/cmd" and "readlink /proc/999/exe" do generate EACCES (Permission denied) errors. If the only entries that Discord found matching the pattern "/proc/NNN", for some decimal number NNN, were not owned by the current Discord user, then I imagine that Discord would quietly decide that you're not running any recognized games and go on about its other business, until the next five second loop.
So ... question for snap experts. Could the Discord snap be packaged with a fake "/proc" file system, that contained exactly one entry, an empty directory "/proc/1", owned by uid 65535 (nobody)? I'd wager that Discord would cease flooding my log files with these error messages.
View PC info
That only makes it stop showing it, it still logs everything. If you let it. :D
View PC info