Piorities are a bit odd, eventually all packages affected (low prio as
they can't do much about it) actually depend on lightdm to resolve it
(prio medium) which depends on accountsservive to implement some shell-
filter feature (prio high).
TL;DR as there was a lot of discussion up to now:
-
The Dup 1667113 had tracked some more affected packages - since all are
dupped on this bug here let me add those tasks here so that all
component owners are aware.
** Also affects: ceph (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ifmail (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 857651 ***
https://bugs.launchpad.net/bugs/857651
** This bug has been marked a duplicate of bug 857651
Unable to hide users from login screen / user switcher
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1817507
Title:
package unattended-upgrades 0.90ubuntu0.10 failed to
Public bug reported:
I accidentally deleted the dpkg folder.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.10
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
This bug was fixed in the package libsoup2.4 - 2.65.91-2
---
libsoup2.4 (2.65.91-2) experimental; urgency=medium
* Have libsoup2.4-dev depend on libpsl-dev & libsqlite3-dev
-- Jeremy Bicha Sun, 24 Feb 2019 19:19:55 -0500
** Changed in: libsoup2.4 (Ubuntu)
Status:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
It seems you have made some changes to the sound configuration, so can
you please first try live booting:
http://releases.ubuntu.com/18.10/
and 19.04:
http://cdimages.ubuntu.com/daily-live/current/
then tell us if they have the same problem in a live session?
** Also affects: pulseaudio
Can you please clarify what the "add-ons" are whose removal fixes the
problem?
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
It's expected that HDMI output has fewer configurable options.
Can you explain in different words what's not working? Do you have
speakers connected to your HDMI monitor that have stopped working?
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug
Please run this command to send us more information about the system:
apport-collect 1817208
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: bionic
** Changed in: ubuntubudgie
Status: New => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: New =>
Thanks.
You say 18.10 is broken but 19.04 works, however 'bluez' did not change
between those versions. So this sounds more likely to be a kernel bug
(which was fixed in later versions).
Next step:
On the 18.04 installation with the bug, please try some newer kernel
versions:
You can use bug 1809856 for the 9370.
** Summary changed:
- Dell XPS 13 9350, 9360 and 9370 headphone audio hiss
+ Dell XPS 13 9350/9360 headphone audio hiss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
** This bug is no longer a duplicate of bug 1654448
Dell XPS 13 9350, 9360 and 9370 headphone audio hiss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1809856
Public bug reported:
This system reports /dev/sda5 will be checked on the next reboot. Maybe
it is (it's EXT4 on as SSD drive, so it could be too fast to notice),
but the message persists even after such a reboot.
I would expect it to go away.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
*** This bug is a duplicate of bug 1781440 ***
https://bugs.launchpad.net/bugs/1781440
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1781440, so it is being marked as such. Please
Still actual in 18.04.
This looks scary.
--
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/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
Status
openssl1.0 is removed from disco.
** Also affects: openssl (Ubuntu Disco)
Importance: Undecided
Assignee: Canonical Foundations Team (canonical-foundations)
Status: Fix Released
** Also affects: openssl1.0 (Ubuntu Disco)
Importance: Undecided
Status: Confirmed
**
Public bug reported:
libsoup changed its .pc file so we have to add a few more dependencies
(as seen in the failed midori build).
Please sync libsoup2.4 2.65.91-2 from experimental when it's available.
** Affects: libsoup2.4 (Ubuntu)
Importance: High
Status: Triaged
** Tags:
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
Done. Please let me know here if this is still a problem.
** Project changed: autopkgtest-cloud => auto-package-testing
** Changed in: auto-package-testing
Status: New => Fix Released
** Changed in: auto-package-testing
Assignee: (unassigned) => Iain Lane (laney)
--
You received
Yeah OK, I'm pretty sure that change is bogus. I think it'll mean that
if we hit the 'cache' we'll post back to the wrong status URL, since we
don't check the environment matches.
I'll just revert that for now. Sorry again.
--
You received this bug notification because you are a member of
The bionic fix is included in the upstream 1.10.14 release:
https://launchpad.net/ubuntu/+source/network-manager/1.10.14-0ubuntu1
1.12.6 has the fix for cosmic.
** Changed in: network-manager (Ubuntu Cosmic)
Importance: Undecided => High
--
You received this bug notification because you are
This is fixed in Disco; I opened Bionic and Cosmic tasks since the bug
needs to be open in some way for it to be tracked.
** Changed in: network-manager (Ubuntu Disco)
Status: Fix Committed => Fix Released
** Also affects: network-manager (Ubuntu Cosmic)
Importance: Undecided
Thanks, I would guess that I broke this somehow in
https://git.launchpad.net/autopkgtest-
cloud/commit/?id=58adff467c108506f979e229aa8e9e955a7d0d0a - which was a
commit I made because systemd PRs were taking a long time after their
jobs finished (several hours) to report any results due to that
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1817475
Title:
package libwayland-dev 1.14.0-2 failed to install/upgrade: trying to
Public bug reported:
nonelse
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libwayland-dev 1.14.0-2
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for
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
This bug was fixed in the package network-manager - 1.15.2-0ubuntu2
---
network-manager (1.15.2-0ubuntu2) disco; urgency=medium
* debian/patches/git_ifupdown_segfault.patch:
- 'settings/ifupdown: fix ifupdown plugin after merging eni_ifaces and
connections hashes' (lp:
Hi @stephane-guillou,
I also do have ubuntu 18.04 and I can't see this issue there.
helio@xps13ubuntu:~$ python3
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> help('modules')
Please wait a moment
Still present in Ubuntu 18.04, using the python3.6 prompt in the shell:
```
>>> help('modules')
Please wait a moment while I gather a list of all available modules...
[ecc] warning: libsecp256k1 library not available, falling back to python-ecdsa
WARNING:root:can not import unity GI Namespace
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013
Bug report did not expire due to bug watches
No reply to comment #91 five years ago
Marking as "Invalid" to close
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you
No reply to comment #5 so will assume problem was fixed long ago.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
No reply to comment #6 or any further comments for nearly 9 years so
closing.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
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.
35 matches
Mail list logo
