Public bug reported:
There is an AppArmor regression in current noble. In cockpit we recently
started to test on noble (to prevent the "major regressions after
release" fiasco from 23.10 again).
For some weird reason, rsyslog is installed *by default* [1] in the
cloud images. That is a rather poi
Just to make sure that we really talk about the same thing: This bug
sounds like it is *intended* that
unshare --user --map-root-user /bin/bash -c whoami
(as unpriv user) now fails in current Ubuntu 24.04 noble. That still
worked in released 23.10.
I am starting to test Cockpit on the curren
** Changed in: chrony (Ubuntu)
Status: New => Won't Fix
** Changed in: gnutls28 (Ubuntu)
Status: New => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
Public bug reported:
For the last two weeks, building noble VM images for our CI has been
broken. Most of it was uninstallability due to the xz reset, but for the
last three days, `pbuilder --create` has failed [2] because it gets perl
and perl-modules-5.38 in two different versions:
2024-04-08 0
I wonder where that comes from --
https://launchpad.net/ubuntu/+source/perl/+publishinghistory says that
5.38.2-3 was deleted, but only from noble-updates. In noble proper it is
merely "superseded". https://launchpad.net/ubuntu/+source/perl/5.38.2-3
doesn't show it being published anyway, and it's
Aside from curl this can be reproduced most quickly with
sudo /usr/sbin/debootstrap --include=build-essential noble /tmp/n
http://archive.ubuntu.com/ubuntu
Errors were encountered while processing:
perl
libdpkg-perl
libperl5.38t64:amd64
dpkg-dev
build-essential
These are all ultimately du
Yay, today this is finally fixed, pbuilder creation and building a noble
VM image finally works again \o/ Thanks!
** Changed in: perl (Ubuntu Noble)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Public bug reported:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
tries to restart sshd, but that fails as "sshd.service" is not a thing
on Ubuntu:
2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl', 'is-act
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/s
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Public bug reported:
One of our Cockpit integration tests [1] spotted an AppArmor regression
in rsyslogd. This is coincidental, the test passes and it doesn't do
anything with rsyslogd -- just something happens to happen in the
background to trigger this (and I can actually reproduce it locally
qu
Public bug reported:
I am in the process of updating our CI for Cockpit to kinetic [1]. I get
a lot of test failures because SSH password login is broken.
This can be replicated with a clean cloud instance, so it's not
something that our VM build scripts do:
curl -L -O
https://cloud-images.ub
I set LogLevel=DEBUG in /etc/ssh/sshd_config, systemctl restart sshd,
and I'm none the wiser:
debug1: Forked child 1652.
debug1: Set /proc/self/oom_score_adj to 0
debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8
debug1: inetd sockets after dupping: 4, 4
Connection from 127.0.0.1 port 45396 o
D'oh!
# cat /etc/ssh/sshd_config.d/10-cloudimg-settings.conf
PasswordAuthentication no
rm + restart sshd, everything is hunky-dory. Sorry for the noise!
** Changed in: openssh (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
OK, thanks for confirming!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
nsswitch.con
I tried a more targeted workaround, with
aa-complain /etc/apparmor.d/usr.bin.crun
or alternatively (without apparmor-utils, which isn't on the default
cloud image):
sed -i '/flags=/ s/unconfined/complain/' /etc/apparmor.d/usr.bin.crun
but for some reason that breaks podman entirely:
# podm
I also tried
aa-disable usr.bin.crun
but that doesn't work either. I guess it's not really crun, but
profile="containers-default-0.50.1", but that is created dynamically --
it's not anywhere in /etc/apparmor.d/. I grepped the whole file system
for that:
grep: /usr/lib/podman/rootlessport: bi
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
- ren
Excellent, thanks Danilo for the super fast fix! ⭐
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong def
We just ran into this in https://github.com/cockpit-
project/bots/issues/5691 when trying to refresh our Ubuntu 23.10 mantic
VM image. It starts with the current cloud image and then apt upgrades
it, with "DEBIAN_FRONTEND=noninteractive". openssh was updated a few
days ago indeed:
Setting up ope
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-reconfigure openssh-server doesn't ask questions again
Status in openssh package in Ubuntu:
New
Bug d
Public bug reported:
In our project we regularly build Ubuntu VM images for current 23.10
(stable). In https://github.com/cockpit-project/bots/issues/5691 we ran
into an upgrade failure of openssh-server. It starts with the current
cloud image and then apt upgrades it, with
"DEBIAN_FRONTEND=nonint
Argh -- I missed the alternative truth in that rescue-ssh.target shell
code. So this message should pretty much *always* appear -- it's
nonsense to actually try and restart rescue-ssh.target in the postinst,
*always*.
But it is a red herring due to the || true. The upgrade failed on
something else
Fun, this isn't even reliable. The first atttempt failed:
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-
logs/ubuntu-stable-20231219-223939.log
I retried the build now, no package or environment changes. Only daytime
and timing (race conditions). Perhaps some interaction with
Public bug reported:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libpam-modules 1.4.0-11ubuntu1
I just noticed that Ubuntu 22.04 changed from the old pam_tally2 module
to the more widespread pam_faillock one. \o/
However, locking (denying logins) does not actually seem to work.
Accordi
Ouch, thanks Marc! Indeed our previous seddery was broken, it should
have left the pam_deny/pam_permit lines. With this it works just fine:
--- /tmp/common-auth.orig 2022-04-01 07:16:26.072608984 +0200
+++ /tmp/common-auth.faillock 2022-04-01 07:14:20.246707861 +0200
@@ -16,6 +16,8 @@
#
** Bug watch added: Debian Bug tracker #1006324
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006324
** Also affects: apparmor (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006324
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
tall test --wait -1
--noautoconsole --cdrom /var/lib/libvirt/novell.iso --autostart
** Package changed: apparmor (Ubuntu) => libvirt (Ubuntu)
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti
n: bolt (Ubuntu)
Status: New => In Progress
** Changed in: bolt (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: umockdev (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Christian, as I write above I believe this really needs to be fixed in
bolt's tests. The umockdev change was a bug fix which bolt's tests
(incorrectly) worked around. So I hope you don't mind that I flipped the
affected package around? I am in contact with Christian now, and hope to
sort this out s
> I am in contact with Christian now, and hope to sort this out soon.
Sorry -- I meant Christian Kellner, bolt's upstream, not you :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad
https://github.com/martinpitt/umockdev/issues/208
Thanks Heinrich!
** Bug watch added: github.com/martinpitt/umockdev/issues #208
https://github.com/martinpitt/umockdev/issues/208
** Changed in: umockdev (Ubuntu)
Status: New => In Progress
--
You received this bug notification becaus
I've been scratching my head over this regression [1] for a while now,
in the context of running a hirsute container on a 20.04 host (in
particular, a GitHub workflow machine) In my case, the symptom is that
after upgrading glibc, `which` is broken; that of course also uses
faccessat(), similar to
Dang, we already found a ppc64el SIGBUS issue in 0.16.0, which got fixed
in https://github.com/martinpitt/umockdev/commit/277c80243a . But this
is reported against 0.16.1 already.
There is a tiny chance that
https://github.com/martinpitt/umockdev/commit/264cabbb will magically
fix this, but otherw
Indeed the open(2) manpage is misleading in that regard. The actual
definition in fcntl.h is like this:
extern int open (const char *__file, int __oflag, ...) __nonnull
((1));
(with a few variants, but they all use varargs). So I did the same in
umockdev for full header compatibility.
--
Yo
Similar issue: https://gitlab.com/libvirt/libvirt/-/issues/548 . These
two may want a common fix with "allow qemu to read sysfs"?
** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #548
https://gitlab.com/libvirt/libvirt/-/issues/548
--
You received this bug notification because you are
It seems to me that the logs are internally consistent, i. e. the
mentioned UPSTREAM_PULL_REQUEST in the log does match the test results.
But they get sent to the wrong PR, i. e. to the wrong statuses API.
E. g.
https://api.github.com/repos/systemd/systemd/commits/99894b867f1293f56d181d62f5015c5a0
Another example: https://github.com/systemd/systemd/pull/11802 refers to
the correct amd64 log
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/amd64/s
/systemd-upstream/20190222_161608_7fe1f@/log.gz
Thanks Iain! I'll keep an eye on this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817344
Title:
Ubuntu CI that runs tests via autopkgtest for systemd on GitHub
repo
Should be fixed with https://salsa.debian.org/systemd-
team/systemd/commit/bd89a706b18796074d50bcf2a0cbd29de56ac542 . I'll
close this once the retried PRs go green.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
That worked.
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1819589
Title:
Ubuntu CI is broke
I confirm this on Ubuntu 18.04 (bionic) with 4.15.0-2ubuntu1. It is
fixed in 18.10 (cosmic) with 4.18.0-1ubuntu2.
** Also affects: iproute2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: iproute2
Indeed the downstream tests fail like this as well:
http://autopkgtest.ubuntu.com/packages/systemd/eoan/amd64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1829829
Title:
Thanks Dan! I landed your PR, so it should apply to the next upstream CI
run.
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
mac
I confirm that using a valid IP works better:
In the config:
route1=fe80:2::/60,fe80::99,42
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
fe80:2::/60 via fe80::99 proto static metric 42 pref medium
It's still missing the
The journal says why:
NetworkManager[1295]: [1563552648.1667] platform: route-sync: failure
to add IPv6 route: 1:2::/60 via 1:2::3 dev 6 metric 42 mss 0 rt-src user: No
route to host (113)
NetworkManager[1295]: [1563552648.1672] device (eth2): failed to apply
manual IPv6 configuration
Appa
Nevermind then, this is working well enough for a stable release.
** Changed in: network-manager (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https
Once you do this, these fallbacks should be cleaned up:
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L30
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/crashdb_impl/launchpad.py#L137
--
You received this bug noti
Thanks Christian! Indeed this is rather hard to reproduce locally, but
that PR seems to address this. I'll let you know if it doesn't after it
lands.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.
I locally ran Cockpit tests on our current Ubuntu 17.10 image and re-
confirm that I got the "disconnected path" error. I then upgraded the
ntp package to artful-proposed, and *that* violation is now gone. As
others already saw, I now get a test failure on
apparmor="DENIED" operation="open" pro
The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The most plausible explanation for enumerating /usr/local/bin/ is that
ntpd has some hooks.d/ mechanism which gets called after syncing the
time, and that runs a shell in between. So IMHO this should be allowed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@Gunnar: This patch does not actually work:
❱❱❱ xgettext -f "po/POTFILES.in" -o "build-deb/po/systemd.pot" --join-existing
xgettext: warning: file 'src/core/org.freedesktop.systemd1.policy.in.in'
extension 'policy' is unknown; will try C
xgettext: warning: file 'src/hostname/org.freedesktop.hostn
Thanks Gunnar for tracking this down! Adding a policykit-1 build
dependency requires some thought, as that also build-depends on systemd
[1], thus this is circular. Also, there was a lot of effort with making
systemd bootstrappable without excessive dependencies. But I think it's
fine to add this a
I confirmed that the current "ninja -C build-deb/ systemd-pot" command
also builds a complete .pot file with policykit-1 installed
(unsurprisingly, as this also just calls gettext). So that part is fine.
What is really bad however, is to build-depend against policykit-1:
The following NEW package
Thanks Gunnar, nice work! I cherry-picked the patches in
https://salsa.debian.org/systemd-team/systemd/commit/87f54958bc24 . The
debian/ changes were already in Debian master.
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification becaus
Public bug reported:
As per documentation, the `-B best` option should automatically select
the best backingstore, falling back all the way to dir.
But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1:
$ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial
lxc-c
I committed the first hunk to Debian, this makes sense:
https://salsa.debian.org/systemd-team/systemd/commit/18d8c2df133b8af
The second is too hackish for a permanent downstream delta, IMHO: This
should rather be fixed upstream, as upstream polkit (as well as Debian's
and Ubuntu's older versions)
Public bug reported:
Merely installing and starting ntp.service in Ubuntu 17.10 now causes
this AppArmor violation:
audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
operation="sendmsg" info="Failed name lookup - disconnected path"
error=-13 profile="/usr/sbin/ntpd" name="run/systemd/j
Patches backported into Debian packaging git:
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=9bba5469f2b95ea9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/b
Can you please boot without the "quiet", and add "debug" on the kernel
command line? The CurrentDmesg attachment looks normal, so I figure this
was from a clean boot. Right now we have zero information what goes
wrong here, I'm afraid. Thanks!
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1032823 ***
https://bugs.launchpad.net/bugs/1032823
** This bug has been marked a duplicate of bug 1032823
package libdevmapper-event1.02.1 2:1.02.48-4ubuntu7.1 failed to
install/upgrade: ErrorMessage: dependency problems - leaving unconfigured
--
You r
*** This bug is a duplicate of bug 1447654 ***
https://bugs.launchpad.net/bugs/1447654
Yes, this is indeed a duplicate of bug 1447654, and the first attempt at
fixing that was not sufficient. policykit-1 did get installed as per the
log in the description.
I have a gut feeling that this is re
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu Vivid)
Status: New => Triaged
** Changed in: policykit-1 (Ubuntu)
Status: Confirmed => Triaged
** Changed in:
*** This bug is a duplicate of bug 1447654 ***
https://bugs.launchpad.net/bugs/1447654
** This bug is no longer a duplicate of bug 1436448
Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was
reached (g-io-error-quark, 24)
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 1447654 ***
https://bugs.launchpad.net/bugs/1447654
** This bug has been marked a duplicate of bug 1447654
installing policykit-1 hangs under systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Bug watch added: Debian Bug tracker #794723
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794723
** Also affects: policykit-1 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794723
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
I think I know what's going on:
Unpacking apport (2.19.1-0ubuntu2) ...
Selecting previously unselected package policykit-1.
Preparing to unpack .../policykit-1_0.105-11ubuntu1_amd64.deb ...
Unpacking policykit-1 (0.105-11ubuntu1) ...
Processing triggers for shared-mime-info (1.3-1) ...
Processing
** Description changed:
I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 =
6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting
errors installing packages (such as lubuntu-core).
Last few lines from apt-get:
Processing triggers for systemd (219-7ubuntu3
I uploaded a fix for wily (at this point it'll probably become an SRU,
though), and also an SRU for vivid in case anyone still cares.
** Changed in: policykit-1 (Ubuntu Vivid)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch see
For the record, this reproduces perfectly well in local QEMU:
adt-run --apt-pocket=proposed -U -s --testname testsuite python3.4 ---
qemu /srv/vm/adt-trusty-amd64-cloud.img
so this is not specific to the production CI environment. -s starts a
shell after failure; after that the failure can be r
Even faster:
$ python3.4 -W default -bb -E -R -m test -j 1 -v -m testRecvmsgPeek
-uall,-network,-urlfetch,-gui test.test_socket
Attaching strace for one of the failed tests. The interesting part:
[pid 10253] socket(PF_INET6, SOCK_DGRAM|SOCK_CLOEXEC, IPPROTO_IP) = 4
[pid 10253] bind(4, {sa_family
*** This bug is a duplicate of bug 1447654 ***
https://bugs.launchpad.net/bugs/1447654
The solution was much simpler; I uploaded a fix to the SRU review queues
for vivid and wily. It's not available in the archive yet, it needs to
be reviewed/accepted by the SRU team first.
--
You received t
Trivially reproduces on e. g. the cloud images, but for completeness:
$ sudo systemctl status -l bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue 201
> There is nothing we can do from bluez side.
Perhaps not from the daemon itself, but the packaging certainly needs to
be fixed. It could be that the .service file grows some Condition*= to
not start if we already know that it won't work; or the .postinst
shouldn't fail when the service fails (e.
Even if we would change our kernel package to always include bluetooth,
that still would make the package fail for custom/third-party kernels,
so I'd say this is neither required nor sufficient. Let's fix the bluez
packaging instead.
** Changed in: linux (Ubuntu Wily)
Status: New => Won't F
> ConditionPathIsDirectory=/sys/class/bluetooth
Sounds perfect!
** Changed in: bluez (Ubuntu Wily)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.n
** Changed in: policykit-1 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1447654
Title:
installing policykit-1 ha
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regr
I'm expediting the usual 7 day maturing period; this is a rather grave
regression and apparently the new kernel didn't get around to add a
Breaks: to the previous LXC version. Thanks for verifying!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
Wily fix uploaded (might end up as an SRU, though). I also sent the
patch upstream, will add a link once it hits the upstream ML archives.
** Changed in: bluez (Ubuntu Wily)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Forwarded upstream:
http://article.gmane.org/gmane.linux.bluez.kernel/65182
** Changed in: bluez (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: bluez (Ubuntu Wily)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because y
*** This bug is a duplicate of bug 1431582 ***
https://bugs.launchpad.net/bugs/1431582
** This bug has been marked a duplicate of bug 1431582
there is no wi-fi after hybernate mode
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** This bug is no longer a duplicate of bug 1270257
NetworkManager failed to function after suspend and resume
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/14315
I sponsored this a while ago, unsubscribing sponsors. This is in the
hands of the SRU team now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lsb in Ubuntu.
https://bugs.launchpad.net/bugs/1273462
Title:
Users can mistake
Unsubscribing sponsors for now. Let's please not change this until we
have some clarity about the broadcom drivers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs
Subscribing kernel team. Is this driver really something which we should
offer to users via graphical means (and thus make it very easy)? It
seems we've had three drivers (b43 with fwcutter, bcmwl, and now the
relatively new bcma one). Which of these do we actually still support?
We can't expect t
** Changed in: systemd (Ubuntu)
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1467173
Title:
poweroff or reboot hangs
Status in syst
*** This bug is a duplicate of bug 1422143 ***
https://bugs.launchpad.net/bugs/1422143
** This bug has been marked a duplicate of bug 1422143
No wifi connection after suspend with systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
The main difference in this regard between upstart and systemd is that
during suspend the pm-utils quirks are not run any more. Can you please
check (under systemd) that running "sudo pm-suspend" instead of closing
the lid or using the indicator fixes this problem?
I'm fairly sure that it does. I
I tried today's ISO: Ubuntu 15.10 "Wily Werewolf" - Release amd64
(20151020)
On my UEFI laptop I don't get the graphical "Try Ubuntu / Install
Ubuntu" picker, just the grub one. I tried all four cases of "try"
(live session) and "install" (ubiquity-only) and connect via indicator
vs. connect in ub
Another thing to try: Replace
pkill --signal HUP polkitd
with
systemctl try-restart polkitd.service
in /usr/lib/udisks2/udisks2-inhibit. That will immediately restart it,
instead of waiting for another d-bus activation cycle (which might
confuse existing clients).
** Package changed: pol
Thanks Mathieu; all your traces indeed have
+++ killed by SIGHUP +++
which is from /usr/lib/udisks2/udisks2-inhibit. This is a race
condition, when polkit gets killed at the wrong time while a request is
pending it would behave that way. Curious that this only surfaces right
now, /usr/lib/udis
nit (Ubuntu X-series)
Importance: Undecided
Status: New
** Also affects: sysvinit (Ubuntu Wily)
Importance: High
Assignee: Martin Pitt (pitti)
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Changed in: sysvinit (Ubuntu X-series)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1504897
Title:
packages with only upstart+system
*** This bug is a duplicate of bug 1504897 ***
https://bugs.launchpad.net/bugs/1504897
** This bug has been marked a duplicate of bug 1504897
packages with only upstart+systemd without sysvinit fail to upgrade:
subprocess installed post-installation script returned error exit status 100
-
tion of start.
** Changed in: sysvinit (Ubuntu Wily)
Status: Incomplete => In Progress
** Changed in: sysvinit (Ubuntu X-series)
Status: Confirmed => In Progress
** Changed in: sysvinit (Ubuntu X-series)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received
*** This bug is a duplicate of bug 1504897 ***
https://bugs.launchpad.net/bugs/1504897
** This bug has been marked a duplicate of bug 1504897
packages with only upstart+systemd without sysvinit fail to upgrade with
do-release-upgrade: upgrade tarballs ship obsolete invoke-rc.d
--
You rec
1 - 100 of 4146 matches
Mail list logo
