Thanks Lucas. I'm installing the version you prepared and will run it
for a few days to see if it's stable, and then report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976307
Title:
Stack s
Public bug reported:
The gamatronic UPS driver in nut 2.7.4-14ubuntu2 randomly crashes after
a memory violation attempt. This usually happens after many hours of
operation, typically after 20h or more, and started after the update to
jammy. No similar problems happened on focal.
116159.602986 U
** Changed in: snapd
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668891
Title:
Can install non classic snap with --classic, but classic flag isn't
set
To man
@didrocks: installing a non-classic snap with --classic with current
snapd issues the following warning. (Using --classic shouldn't override
the package confinement, the flag is still ignored but not silently.)
$ snap install word-salad --classic
Warning: flag --classic ignored for strictly confin
Michael, could you confirm this was a cosmic-specific bug as there's a
report of a similar problem with an upgrade from eoan to focal?
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Assignee: (unassigned) => Michael Vogt (mvo)
--
You received this bug notificati
This is a collection of bug reports and it seems that at least some of
them are already solved either by manually enabling services or using
newer versions of snapd. Are any of these issues still happening?
** Changed in: snapd
Status: Confirmed => Incomplete
--
You received this bug noti
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886113
Title:
snap-store Does Not Run with XAUTHORITY error
To manage notifications abo
Thanks for reporting and sorry for not getting back to you earlier. It
seems that we have a mismatch between the contents of the XAUTHORITY
environment variable (under /home/william) and the actual location of
the file on the filesystem (under /Moort/home/william) after resolving
symlinks and clean
** Changed in: snapd
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881588
Title:
pre-seeding lxd on Core appliances breaks console-conf user creation
To manage notifi
Result of systemd-analyze in both systems on the Thinkcentre machine:
uc18:
Startup finished in 30.880s (kernel) + 4.727s (userspace) = 35.608s
graphical.target reached after 4.721s in userspace
uc20:
Startup finished in 38.338s (kernel) + 17.902s (userspace) = 56.240s
graphical.target reached a
I tested the chromium snap (1165) on a focal machine with IPv6 and
couldn't reproduce DNS lookup problems. I did, however, find a
difference between this chromium and unconfined chrome when handling
IPv6 large packets (unconfined chrome works as expects and chromium
times out).
Unconfined chrome o
** Changed in: snapd
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879630
Title:
No sound output from HDMI audio
To manage notifications about this bug go to:
http
Thanks Vic. I see from logs that the HDA codec is an ALC 233, which
happens to be the same Realtek HDA codec I have in my Lenovo Thinkcentre
machine that's running UC20 20200529.3. Unfortunately my Thinkcentre
doesn't have any HDMI ports, but I was able to send sound through one of
the displayports
Chris Coulson's patch should also solve the problem that breaks install
on the Thinkcentre m920s with TPM enabled. The last printed message when
booting with grub debug enabled is the type of the loopback file, and
nothing happens after that. It finishes installing if you rmmod tpm.
--
You receiv
I experienced a similar problem, with constant disk writing at low rate
(few hundred KB/s) and after inspecting the snapd process running on a
container we found the following:
root@focal:/# snap changes
Systems tested: qemu, rpi4 (1GB)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878928
Title:
Call trace occurred when running `netplan apply` after an yaml is
removed
To manage notifications abo
Fix seems good, I couldn't reproduce this bug using core20 663/665 from
edge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878928
Title:
Call trace occurred when running `netplan apply` after an y
UC18 on the same hardware starts to display kernel messages at the 14s
mark. UC18 logs shows no delay between the "console [tty1] enabled" and
"console [ttyS0] enabled" messages, but otherwise the behavior is
similar (blank screen for some time and slow output rate).
[0.00] console [tty1]
I finally managed to install a beta image on a Thinkcentre m920 (by
removing the tpm module in grub before booting). Console output appears
at the 32s mark, see full dmesg below. Some interesting console-related
excerpts:
[0.049211] printk: console [tty1] enabled
[ 14.088918] printk: console
Also please include any additional information, if any, on how to
reproduce this problem. Just downloading/opening a file worked correctly
for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870861
Thanks for reporting. The invalid opcode error seems odd, are you
running on an uncommon architecture/cpu? Could you provide more
information about the hardware you're running on such as the
/proc/cpuinfo output?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this
Assigned to Ian as a reminder to unblock PR #7904 once the prerequisites
are cleared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862642
Title:
cannot use snapcraft to build snapd on focal
To ma
** Changed in: snapd
Status: New => In Progress
** Changed in: snapd
Assignee: (unassigned) => Ian Johnson (anonymouse67)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862642
Title:
ca
This model file is used to build both the spread test image and the
manually built image. The two generated images, however, seem to behave
differently regarding the conditions leading to the crash: while it
always happen in the spread test, higher KDF iteration times values
allow the encrypted dev
Snap versions used to build the image:
pc-kernel_374.snap
pc_83.snap
snapd_6113.snap
core20_322.snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860231
Title:
5.4.0-11 crash on cryptsetup open
** Attachment added: "Screenshot of the procedure to trigger the crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+attachment/5321426/+files/Screenshot%20from%202020-01-18%2016-16-19.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
An attempt to run cryptsetup open on a newly created LUKS partition on
Ubuntu Core 20 causes a kernel crash. This happens in 100% of the
attempts on the snapd Core 20 installation test, but on an image created
to reproduce this bug it happens only when certain parameters are p
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853730
Title:
package snapd (not installed) failed to install/upgrade: подпроцесс
уста
Interesting. This is what I see here with Ksystemlog.
** Attachment added: "Screenshot from 2019-11-04 20-01-25.png"
https://bugs.launchpad.net/snapd/+bug/1830183/+attachment/5302839/+files/Screenshot%20from%202019-11-04%2020-01-25.png
--
You received this bug notification because you are a
Oh, but I see you read from `/var/log/syslog` instead of the systemd
journal. I don't have snapd entries in the syslog file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830183
Title:
Absence of u
** Changed in: snapd
Status: Incomplete => Triaged
** Changed in: snapd (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830183
Title:
Absence of
Could you confirm this still happens with snapd 2.42? I quickly tested
it and this type of message was logged in the system journal as `info`
(level 6).
** Changed in: snapd
Status: Triaged => Incomplete
** Changed in: snapd (Ubuntu)
Status: Triaged => Incomplete
--
You received t
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I've been informed that all tests should be working correctly with the
current snapd version, so this bug will be closed. Please reopen if this
problem is still happening.
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue is still happening with the current
snapd version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue still happening with the current snapd
version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue still happening with the current snapd
version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Thanks for reporting this bug, sorry it's taken this long to respond.
Could you confirm if this issue still happening with the current snapd
version?
** Changed in: snapd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Just adding a quick note that I experienced this problem on a Thinkpad
T480 running 18.04, after updating to 4.15.0-62-generic. Going back to
4.15.0-55-generic fixes the issue. I didn't check -58 and -60 to see how
they behave, but I should do that as soon as I have time for that. Note
that it may
Just adding a quick note that I experienced this problem on a Thinkpad
T480 running 18.04, after updating to 4.15.0-62-generic. Going back to
4.15.0-55-generic fixes the issue. I didn't check -58 and -60 to see how
they behave, but I should do that as soon as I have time for that. Note
that it may
I tested the eoan kernel 5.2.0-10-generic and the suspected problems in
the block layer didn't happen anymore after removing the workarounds
(artificial delays and module insertion) needed by the bionic kernel
4.15.0-54-generic used in core18. 5.3.0-050300rc4-generic also works
without any immediat
Thanks Connor. My test configuration is a custom core system using the
official core18 kernel snap on a KVM-based virtual machine. The kernel
snap is installed from channel 18 (snap download --channel 18 pc-kernel)
and my current revision is 240. That said, it's easy to test new kernels
as long as
Thanks. I tested the proposed kernel and it does not prevent the crash,
which still occurs under the same circumstances when cryptsetup open
runs. It's possible, however, that the patch decreases the likehood of a
crash. In a very un-scientific test the latest patched kernel crashed in
3 out of 10
The udev workaround preloading is unrelated and can be removed, crashes
will also happen without using it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835279
Title:
4.15.0-54.58-generic 4.15.18:
** Attachment added: "4.15.0-54-generic #58+lp1835279 kernel log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+attachment/5277230/+files/kernel-arighi.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
We're now opening the LUKS device using the master key directly and the
crash is happening again in both the original 4.15.0-54-generic
(buildd@lgw01-amd64-014) kernel or the patched 4.15.0-54-generic
(arighi@kathleen) kernel. The backtrace is very similar but unlike the
previous scenario it happen
Thanks Andrea. The new kernel seems to address the problem in such a way
that the block device made available is still not immediately usable,
but the kernel crash is prevented (at least in the test runs so far).
Now errors can be handled from userspace to retry the operation in case
of failure.
-
Further testing suggests that the problem is caused by the kernel not
having enough time to settle after partx -u exits (race between
acknowledging the new block device and actually having it available?).
Adding a 1s pause after the partition table is re-read seems to prevent
this crash.
--
You r
This problem happens on Ubuntu Core (Core 20 development branch based on
Core 18) and apport is not available.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Description changed:
This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24
10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc-
kernel_240.snap
Version signature: 4.15.0-54.58-gene
Public bug reported:
This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24
10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc-
kernel_240.snap
Version signature: 4.15.0-54.58-generic 4.15.18
Is
67 matches
Mail list logo
