The xenial backport is non-functional due to a symbol collision between
libjson-c.so (required by libpulse) and libjson-glib.so (required by
snapd-glib). This doesn't affect the Bionic backport though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello Dan, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dan, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Paul, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Steven, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal unlinked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
> it will prevent udevd from running the rules against it. Thus
effectively the event will be fired and done, but nothing actually
executed for it.
Interesting, I suspect this is the race we see. The events emitted but
no actions taken (ie we didn't get our by-partuuid symlink created.
> I
** Tags removed: server-triage-discuss ubuntu-server
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine
I have a very similar issue with another Samsung laptop:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
> So that means we have this sequence of events:
> a.) growpart change partition table
> b.) growpart call partx
> c.) udev created and events being processed
That is not true. whilst sfdisk is deleting, creating, finishing
partition table (a) and partx is called (b), udev events are already
Public bug reported:
nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf:
autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest
autopkgtest [09:46:25]: test command1: [---
[info] Testing github.com/theupdateframework/notary...
[info] Source code
Build issue is reproducible on arm64 LP infrastructure builds.
I spawned a canonistack arm64 system to check if it is reproducible
there as well for some debugging how we could fix it.
Interestingly, it does NOT FAIL on focal as-is when building on aarch64.
But as LP builds are against
** Changed in: ubuntu-power-systems
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1657646
Title:
[20.04] Missing
Hello Matthias, or anyone else affected,
Accepted python3.7 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.7/3.7.5-2~18.04 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matthias, or anyone else affected,
Accepted python3.6 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.6/3.6.9-1~18.04 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Just curious, did anyone actually test with my suggestion from comment
40? That is, just make your partition table change (and update the
kernel with partx or whatever, of course), and after it's done trigger
--settle udev for the device. Be interesting to know if that actually
fixes it or not.
This bug has a lot of troubleshooting comments, but lacks a good summary
about what is going on. I don't expect the xenial installer to be
changed anymore, short of critical bugs affecting it.
@tcstone, you say you hit something similar with 18.04.2. Current bionic
release is 18.04.3, would you
** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan
--
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/1847896
Arm64:
$ grep NR_open $(dpkg -L linux-libc-dev | xargs) 2>/dev/null
/usr/include/asm-generic/unistd.h:#define __NR_openat 56
/usr/include/asm-generic/unistd.h:__SYSCALL(__NR_openat, sys_openat)
/usr/include/asm-generic/unistd.h:#define __NR_open_by_handle_at 265
I really think you are all *way* over thinking this.
a. growpart made a change to the partition table (using sfdisk)
b. growpart called partx --update --nr 3 /dev/sda
c. growpart exited
With a and b growpart created udev events. If you create udev events,
you really need to wait for those
The feature works now. You might want to release it earlier than 7 days.
--
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/1847896
Title:
Unable to shutdown or restart from
Looks like I was a little slow in testing and changing the tags but for
the record:
Rebooted into Ubuntu 19.10 to confirm Restart and Poweroff options were not
working
Logged in, enabled -proposed, updated systemd to version 242-7ubuntu3.2
Logged out and confirmed 'Poweroff' now works
Started PC
@ddstreet
Yes, settle does not help.
Re-triggering udevadm trigger --action=add /sys/class/block/sda
Would re-run all of them after the partition change has occurred, which
is what I'm currently suggesting as a heavy-handed workaround.
I would like to understand *why* the udevd/kernel pair
This bug was fixed in the package python3-stdlib-extensions -
3.7.5-1build1
---
python3-stdlib-extensions (3.7.5-1build1) eoan; urgency=medium
* SRU: LP: #1835738.
python3-stdlib-extensions (3.7.5-1) unstable; urgency=medium
* Update 3.7 extensions and modules to 3.7.5 release.
This bug was fixed in the package gdb - 8.1-0ubuntu3.2
---
gdb (8.1-0ubuntu3.2) bionic; urgency=medium
* Fix 32-bit ARM tagged pointer support. Addresses a regression
introduced in the previous version which broke breakpoint
support in 32-bit programs. LP: #1848200.
--
The verification of the Stable Release Update for gdb has completed
successfully and the package is now being 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
Hello Balint, or anyone else affected,
Accepted klibc into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/klibc/2.0.6-1ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package python3-stdlib-extensions -
3.7.5-1~19.04
---
python3-stdlib-extensions (3.7.5-1~19.04) disco-proposed; urgency=medium
* SRU: LP: #1835737. Backport the final Python 3.8.0 release.
* Also update the 3.7 modules to 3.7.5.
Continues to FTFBS in LP infra today :-/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1849785
Title:
FTBFS on i386/ppc64/s390x (Eoan+Focal)
Status in libseccomp:
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1850986
Title:
many problems:
Status in apport
** Description changed:
[impact]
- ip addresses managed by keepalived are lost across networkd restarts
+ - ALL related HA software has a small problem if interfaces are being
+ managed by systemd-networkd: nic restarts/reconfigs are always going to
+ wipe all interfaces aliases when HA
Attached is a debdiff for the bionic backport. I've run through
@jdstrand's test plan on a clean Ubuntu 18.04 install, and everything
appears to be behaving as expected.
pulseaudio (1:11.1-1ubuntu7.5) bionic; urgency=medium
* Update snap policy to make access to audio recording conditional on
The backlight device only gets registered after it's opened by graphical
session.
And the backlight gets unregistered when graphical session stops, hence
when systemd-backight@.service's "Conflicts=shutdown.target" triggers,
the backlight is already gone so the brightness wasn't saved.
Since
Well, apparently Nvidia driver doesn't do that.
--
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/1840592
Title:
systemd-backlight does not save and restore brightness for
The name says it all, remote printing means usage of a computer with a
distant printer.This facility is available on almost all computers.But
sometimes the users have faced the issue to locate remote printer when
printing which really slows down the work especially for those who are
traveling.To
I suggest that you upgrade to 19.10 and replace light-locker with the
new xfce4-screensaver.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1830408
Title:
[nouveau][XFCE]
Hello Leroy, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello jowfdoijdfdwfwdf, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
** Description changed:
+ [impact]
+
+ ip addresses managed by keepalived are lost across networkd restarts
+
+ [test case]
+
+ see original description below
+
+ [regression potential]
+
+ this backports KeepConfiguration parameter, which adds some significant
+ complexity to networkd's
** Merge proposal unlinked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/nss/+git/nss/+merge/375115
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1837734
Public bug reported:
I couldn't change brightness. Probably this bug is related to the
problem.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion:
Public bug reported:
I've written an issue here:
https://github.com/stuartlangridge/ColourPicker/issues/63
Pick (a color picker distributed as a snap) will not launch. The creator
of the application believes this to be a problem with my system, not
with their app. Apparently, AppArmor is
Hello Ante, or anyone else affected,
Accepted systemd into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/242-7ubuntu3.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
On Thu, Nov 7, 2019 at 11:30 AM Dimitri John Ledkov
wrote:
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
>
> That is not true. whilst sfdisk is deleting, creating,
*** This bug is a duplicate of bug 1846557 ***
https://bugs.launchpad.net/bugs/1846557
** This bug has been marked a duplicate of bug 1846557
Unable to debug any kernel on i386 qemu machine
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
> Issuing a second
> trigger will repeat this.
> IMO, that's a non-zero amount of time that slows the boot down, so I'd like
> to avoid that.
systemd-udev-trigger.serivce retriggers *everything* at boot (except in
an unprivileged container where it can't), so I'm not sure how much
added time
A fix was released after bug #1848200, reporting the same problem, was
opened.
** Changed in: gdb (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
On Thu, Nov 7, 2019 at 2:41 PM Dan Streetman
wrote:
> > Issuing a second
> > trigger will repeat this.
> > IMO, that's a non-zero amount of time that slows the boot down, so I'd
> like
> > to avoid that.
>
> systemd-udev-trigger.serivce retriggers *everything* at boot (except in
>
an
Public bug reported:
Every time I adjust my laptop's screen brightness using the dedicated
brightness keys, there is a substantial delay between when I press the
button and the screen adjusts. Sometimes it even "twitches" and
decreasing the brightness by tapping the button two times will quickly
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
> Yes, settle does not help.
Well, I didn't suggest just to settle ;-)
> I'm currently suggesting as a heavy-handed workaround.
I don't really see why you think this is heavy-handed, but I must be
missing something.
> I would like to understand *why* the udevd/kernel pair exhibits this racy
>
On Thu, Nov 7, 2019 at 1:30 PM Dan Streetman
wrote:
> > Yes, settle does not help.
>
> Well, I didn't suggest just to settle ;-)
>
Sorry; long bug thread.
> > I'm currently suggesting as a heavy-handed workaround.
>
> I don't really see why you think this is heavy-handed, but I must be
>
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
> That is not true. whilst sfdisk is deleting, creating, finishing
> partition table (a) and partx is called (b), udev events
I could resolve this issue by upgrading the printer firmware to latest
version 1.40. No idea, why Ubuntu 19.04 printed happily with older
printer firmware, but as of Ubuntu 19.10 new printer firmware (can be
installed through printer web interface) is needed.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
Hi,
Since recently, I can't import a VPN connection in NetworkManager and store my
credentials.
NetworkManager will systematically forget the password, despite a log entry
confirming that the operation was a success:
nov. 07 22:26:52 NetworkManager[1518]:
** Changed in: gnome-online-accounts
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1847597
Title:
gnome-control-center cannot
All autopkgtests for the newly accepted python3.6 (3.6.9-1~18.04) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
pybigwig/0.3.2-1ubuntu5 (armhf)
Please visit the excuses page listed below and investigate the failures,
On Thu, 7 Nov 2019 at 17:50, Ryan Harper <1834...@bugs.launchpad.net> wrote:
>
> @ddstreet
>
> Yes, settle does not help.
>
> Re-triggering udevadm trigger --action=add /sys/class/block/sda
>
> Would re-run all of them after the partition change has occurred, which
> is what I'm currently
You have been subscribed to a public bug:
This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have
logs going back to mid august. The message is repeated for each
calendar at various times.
Nov 06 13:49:13 dipper gnome-calendar[8681]:
source_credentials_required_cb: Failed to
The bug here is old, rather than reopening it please open a new one
using 'ubuntu-bug ibus' with a detailled description of the issue and
how to trigger it
** Changed in: ibus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Thank you for your bug report, it's probably
https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42 , GNOME
failing to get their API key re-approved by Google, hopefully they sort
it out soon though
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42
The GNOME key expired this week, that's bug #1851564. The issue there is
older so it can't be the same issue
** Changed in: gnome-online-accounts
Importance: Unknown => Undecided
** Changed in: gnome-online-accounts
Remote watch: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42 =>
Thanks for the fix. I tested it on my end and I confirmed this bug as
being fixed. I can now restart and shutdown via gdm.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hello Douglas, thanks for the report. AppArmor is one of several tools
the snap packaging system uses to enforce confinement on packages. The
AppArmor project doesn't supply the policy though, just the enforcement
mechanism. I believe you'll need to talk to whoever wrote the snap
package, as they
Public bug reported:
on login to laptop.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libssl1.1:i386 1.1.1-1ubuntu2.1~18.04.4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic i686
ApportVersion: 2.20.9-0ubuntu7
Architecture: i386
Date: Thu Nov
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1851714
Title:
package libssl1.1:i386 1.1.1-1ubuntu2.1~18.04.4 failed to
I have tested with a second google account (my canonical one, as opposed
to my personal one) and get the exact same error.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42
https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42
** Also affects:
I'm seeing the same error.
Steps to reproduce:
Open System Settings
Go to Online Accounts
Add a google account
Enter username / password
I then get the same dialog as the reporter of this bug.
I'm on Ubuntu 19.10.
This smacks of our online accounts api key being revoked / rate-limited
or
*** This bug is a duplicate of bug 1846557 ***
https://bugs.launchpad.net/bugs/1846557
Thanks Miroslav for opening this bug, two weeks after me opening bug #1846557.
Unfortunately, it took proving that gdb couldn't debug properly _any_ 32-bit
program, not just kernels running on QEMU, in
** Changed in: gnome-online-accounts (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
Ubuntu.
https://bugs.launchpad.net/bugs/1847597
Title:
> We can't know how many devices are in the system. It maybe nearly zero,
> it could be minutes.
I'm not suggesting you trigger uevents for all devices, just the one
you're repartitioning...
> The cold plug is required (initramfs may or maynot
> have ran
> scripts/udevd etc but kernel events
On Thu, 7 Nov 2019 at 20:05, Scott Moser wrote:
>
> > > So that means we have this sequence of events:
> > > a.) growpart change partition table
> > > b.) growpart call partx
> > > c.) udev created and events being processed
>
> > That is not true. whilst sfdisk is deleting, creating,
80 matches
Mail list logo
