Public bug reported:
While running HexChat in a snap Seccomp kicked-in on the attempt issued
by HexChat via GLib's g_file_replace_contents() and g_file_append_to()
functions with the flag G_FILE_CREATE_PRIVATE to use the syscall
fchown(). This kills the application requiring force-close.
I believe the most appropriate response is to slacken the restrictions
by Seccomp to allow fchown() provided that the user-id and/or group-id
to change ownership to are of the current-user the application is
running-as.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: snappy (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 21 15:18:38 2016
InstallationDate: Installed on 2016-07-19 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: snappy-player
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug snapd-interface xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605273
Title:
Seccomp should allow fchown() with current userid/groupid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1605273/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
