Permissions of executables pointing to "buildd"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
ccache (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
fuse3 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
lzma (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
netstat-nat (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
openssh (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
pipewire (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
psensor (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
screen (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
snap (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
sudo (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
wireshark (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
xz-utils (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've noticed this issue already with other applications, which have been updated recently, too.
This morning I've updated the sudo package and it broke, too.
The common issue is that fakeroot gets omitted or faulty in your build environment somehow.
After looking into the current sudo package I've noticed that all files are owned by "buildd:buildd", which doesn't exist on my computer and thus the 2001:2501 on my local machine.
I'll try to collect some other packages, too, which have the same problem.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: sudo 1.9.5p2-2ubuntu1
ProcVersionSign
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu58
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: KDE
Date: Tue Feb 16 08:33:27 2021
InstallationDate: Installed on 2020-01-27 (385 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: sudo
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
/etc/sudoers: parsed OK
/etc/sudoers.
Changed in snap (Ubuntu): | |
status: | New → Fix Released |
Changed in wireshark (Ubuntu): | |
status: | New → Fix Released |
hi, thanks, the team are already tracking this in bug #1915250 and said they are working on fixing everything