That's the same as bug 2112493. It makes sense Mutter could be causing
both.
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Milestone: None => ubuntu-25.10
** Changed in: mutter (Ubuntu)
Importance: Undecided => Criti
** Changed in: mutter (Ubuntu)
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2112491
Title:
mutter: FTBFS with coreutils-from
To manage notific
I tried in a PPA with -proposed enabled and saw the following:
native | [module-protocol-: 812 socket_data()] server 0x2aa4079b340: failed to
accept: Invalid argument
[E][02151.048565] mod.protocol-native | [module-protocol-: 812 socket_data()]
server 0x2aa4079b910: failed to accept: Invalid arg
Again there are no build logs, so no evidence that the Mutter build even
started. I think you'll need to identify the first part of the rebuild
that actually has a build log.
** Changed in: mutter (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a memb
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2112491
Title:
mutter: FTBFS with coreutils-from
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
