Kernel needs this patch for maxim98090 to work on cyan and some baytrail
chromebooks:
https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
As it didn't make to 5.3 on time, would be nice if it were backported by
ubuntu devs
--
You received this bug notification
Thanks Dan for going deeper on these logs - interesting path differences
that you have spotted!
Thanks Laney for the info on recent changes!
I subscribed stgraber and will give him and the other LXD folks a ping
to chime in here if the mentioned configs/updates ring a bell in regard
to the paths
If you are lazy to look for these commits, feel free to use these links
https://github.com/systemd/systemd/commit/7da377ef16a2112a673247b39041a180b07e973a
https://github.com/systemd/systemd/commit/95355a281c06c5970b7355c38b066910c3be4958
** Changed in: mesa
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1222602
Title:
[regression] [gen3] Mesa 9.2 makes Unity unusable on Atom
Hey thanks for subscribing me!
We haven't had an LXD update recently (the instances are using LXD from
bionic-updates and that's not been changed for a long time). The only
things I can think of is that Adam recently deployed a config change to
set 'security.nesting=true' on our instances
I can't identify when it was fixed, but can confirm this is not
happening any more in grep 3.1-2build1 in Ubuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1769941
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
** Summary changed:
- [master] Restarting systemd-networkd breaks keepalived clusters
+ [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync,
pacemaker (interface aliases are restarted)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
front green jack not working
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 5.3.0-050300-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
** Changed in: xserver-xorg-video-intel (Fedora)
Status: Incomplete => Unknown
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #1680
https://gitlab.freedesktop.org/mesa/mesa/issues/1680
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
https://ikepanhc.wordpress.com/2019/09/26/unpack-initrd-on-x86-platform/
Perhaps this can help you.
--
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/1640152
Title:
The commits bellow implement support to "keep configuration":
commit 1e498853a39b46155cb89b5c9e74ecb27aaba3ed
Author: Yu Watanabe
Date: Mon Jun 3 01:21:13 2019
test-network: add tests for KeepConfiguration=
commit c98d78d32abba6aadbe89eece7acf0742f59047c
Author: Yu Watanabe
Date: Mon
Public bug reported:
Hardware: Lenovo T590
OS: 19.10
When the power is not connected when the laptop boots, and then
connected, the power icon in the top bar does not change to indicate
that the laptop is now charging.
$ upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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/1769297
Title:
Thank you so much for the quick response!
I switched "Keyboard input method system" to "XIM" as you suggested and
now everything works fine.
However, I have a few questions about it.
>> That wiki page you referred to was last edited 11 years ago and is
obsolete to a large extent.
Is it
I believe this will be fixed in v2.41 snapd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767
Title:
Default cron PATH does not include /snap/bin
Status in cron
** Changed in: cron (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779767
Title:
Default cron PATH does not include /snap/bin
I think this should land in Ubuntu as part of a regular snapshot upload
of binutils. I.e. without any special cherrypicking.
This may or might not be fixed in Eoan or f-cycle.
** Changed in: binutils (Ubuntu)
Importance: High => Wishlist
--
You received this bug notification because you are
@yura9, @mauromol, or anyone experiencing this, if you are running
Bionic or Disco, can you please test with the 'bluez' package currently
in -proposed? See the previous 2 comments for instructions how.
This bug does need someone affected by this bug (i.e. with the affected
hardware) to verify
See: https://github.com/lxc/lxd/issues/4656#issuecomment-535531229
In https://github.com/lxc/lxd/blob/master/lxd/storage_zfs_utils.go#L255
the umount is done by
err := unix.Unmount(mountpoint, unix.MNT_DETACH)
The umount2(2) manpage writes about MNT_DETACH:
Perform a lazy unmount: make
This issue is completely reproducible for me. Digging into the
journalctl logs around when the system is rebooting without power
plugged in, here are some lines that stand out and might be useful:
Note that the system was sent to reboot at 10:53:00
...
Sep 26 10:53:37 fenrir systemd[2088]:
There is various expansive work I'm doing upstream on the entire test
framework, so I'll eventually get to cleaning up all the tests in our
sru releases. Closing this as I don't need it to track any failures
currently, I'll open new sru bugs when ready to fix tests.
** Changed in: systemd
** Tags removed: sts-sponsor
--
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/1668771
Title:
[SRU] systemd-resolved negative caching for extended period of time
Status in
(re-opening and tagging as blocked by ff for our tracking script)
** Changed in: pango1.0 (Ubuntu)
Status: Won't Fix => Triaged
** Summary changed:
- [ffe] Update to 1.44.6
+ Don't update to 1.44.6 this cycle
--
You received this bug notification because you are a member of Ubuntu
I suspect you've been able to resolve this, sorry we never got back to
you about it.
I'm closing it as "Won't fix", because we didn't do anything about this,
but if you're still stuck there's probably a cause for this that isn't
necessarily snapd itself and we can probably figure it out.
Again,
Workaround is to hold previous gdb version in apt.
apt purge gdb
apt install gdb=8.1-0ubuntu3
echo "gdb hold" | sudo dpkg --set-selections
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
Public bug reported:
gdb 8.1ubuntu3.1 run binary 64bit without problem.
If compile for 32bit target (g++ -m32 ..) then it can't load libraries
before call main(), i mean it gets frozen.
gdb 8.1-0ubuntu3 works with 32 and 64 bit binaries without problem.
Here is log:
g++ -m32 -o test test.cpp
gdb
*** This bug is a duplicate of bug 1494230 ***
https://bugs.launchpad.net/bugs/1494230
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
I kicked off another ~20K reboot tests with Standard_B2S instances and
hit hangs again:
IP addr Mac AddrKernel Reboots
104.42.3.16100:0d:3a:37:82:ee 5.0.0-1020-azure100
13.91.5.23 00:0d:3a:5a:74:23 5.0.0-1020-azure57
So the best way to reproduce this issue is to run ~500 reboots across
multiple instances rather than 5000-1 reboots on once instance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I tested an upgrade from Ubuntu 18.10 to Ubuntu 19.04 today with some of
the packages from the DuplicateSignature.txt installed e.g.:
Start-Date: 2019-09-25 17:14:37
Commandline: apt-get install bamfdaemon mime-support
Requested-By: bdmurray (1000)
Install: bamfdaemon:amd64
Great, thanks Stephane for confirming that.
@Rbalinx / @xnox - would you want to fix that up as part of the next
systemd upload to Disco then?
Until then we could mark it badtest on armhf as that reflects the
current state correctly and unblocks others until fixed.
--
You received this bug
/dev/.lxc/* shows up when nesting is enabled, so that's indeed related
to the change Adam did.
--
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/1845337
Title:
Disco
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1845190
Title:
binutils nm wrong output format breaks
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_with-power-connected-on-boot.out"
So, am I understanding right that such a system will have two ethernet
interfaces with identical mac addresses? Isn't that an obvious problem
that should be fixed instead?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I tried this in a 19.04 live boot from a usb stick and the behavior was
correct: if the system was booted without power, the charging symbol was
not there. Then when I connected the power, the charging symbol
appeared.
Also, when booting 19.04 without power connected, there is only the one
Do you have DNSSEC enabled? There is a known bug 1796501 that may be
causing your problem.
--
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/1843352
Title:
systemd package
Eric, thanks! Really appreciate your help debugging this issue.
Per Colin's comment, he mentions on #launchpad-ops (internal)
when there are launchpad chroot changes -- so we can confirm
it's been updated after the package becomes Fix Released.
--
You received this bug notification because you
** Tags added: next-ddstreet systemd
--
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/1845337
Title:
Disco autopkgtest @ armhf fails root-unittests -> test-execute ->
The real fix for the openpty() problem on Launchpad xenial buildd
is in livecd-rootfs currently in xenial-proposed, and is verified.
(LP 1844504 comment 15)
Once the Launchpad builders are updated with that, we can proceed
with another build attempt, and hopefully move this SRU forward.
Thanks
On 2019-09-26 18:51, Oryganum wrote:
>> That wiki page you referred to was last edited 11 years ago and is
>> obsolete to a large extent.
>
> Is it possible to contact someone to ask to update this page?
The simple answer to that question is no.
There is a similar page which is somewhat less
The only difference in journalctl between when the system boots with
power and without is that when the system boots without power, I see two
journalctl messages:
Sep 26 10:53:27 fenrir dbus-daemon[793]: [system] Activating via systemd:
service name='org.freedesktop.UPower' unit='upower.service'
The following is the output of `journalctl | grep -i power` that covers
the duration between the reboot command and login times.
** Attachment added: "journal-power-keyword_no-power-connected-on-boot.out"
@mfo,
I will gladly resume the sponsoring as soon as LP: #1844504 is "Fix
Released" and util-linux builds fine.
Thanks for your good work on this Mauricio !
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in
But it should be persisted by default in /var/log, so there should be a
unit somewhere that if the log has information then it appends it in a
file and gets logrotated.
That way, if a server or PC is acting strange, one could look there to
see if something strange happened to the filesystem and
iptables was reverted back to using iptables-legacy by default in bug
1843468 so this should not be an issue (by default) in Eoan, though it
might be in the future when iptables does default to iptables-nft.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
In 19.10, with the error state, restarting upower fixes the issue. So if
you've booted without power connected, then connect power and don't see
the charging icon, execute `sudo systemctl restart upower` and see the
charging symbol.
--
You received this bug notification because you are a member
** Information type changed from Public to Public Security
--
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/1759950
Title:
Lid-close suspend: blank screen when switching to
Impressively quick fix indeed, thanks!
I haven't seen any test added though. While such ELF files shouldn't be common,
it's a fairly basic feature and doesn't seem like requiring any complex test
fixture, does it?
Relying on diffoscope's test suite doesn't feel right.
--
You received this bug
** Tags removed: rls-xx-incoming
** Tags added: rls-x-incoming
--
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/1839290
Title:
systemd doesn't restart a service after
On Thu, 26 Sep 2019 at 20:11, Dan Streetman wrote:
>
> So, am I understanding right that such a system will have two ethernet
> interfaces with identical mac addresses? Isn't that an obvious problem
> that should be fixed instead?
Digging into this, It seems that it is an explicitly supported
** Bug watch added: bugzilla.gnome.org/ #670999
https://bugzilla.gnome.org/show_bug.cgi?id=670999
** Changed in: network-manager
Importance: Wishlist => Unknown
** Changed in: network-manager
Status: Confirmed => Unknown
** Changed in: network-manager
Remote watch: GNOME Bug
** Changed in: ibus
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Very often the users are coming across this common Printing error as
they are not able to locate a Remote Printer at the time of running a
printing process. I have a blog https://printerssupport.co/canon-
printer-not-responding/ along with such Printing solutions which will
help them surely.
--
55 matches
Mail list logo
