Public bug reported:
The system was running in the background, and then I saw - maybe 12
hours later that it had crashed - but it appears that all the programs I
was running were till running!
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.
bionic/linux-azure 5.4.0-1047.49~18.04.1 sru-20210412
** Tags added: sru-20210412
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1884024
Title:
lxc-test-device-add-remove fro
bionic/linux-gke-5.4: 5.4.0-1043.45~18.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1884024
Title:
lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Status in
bionic/linux-oracle-5.4: 5.4.0-1044.47~18.04.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1884024
Title:
lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Status
Any update on this? Having issues with sound working for some time,
than suddenly stopping with a buzzing sound. Will attempt to modify
patch for most recent kernel, but my understanding is the kernel should
already be patched. Works fine on galliumos, but not with any other
distro or most recent
Public bug reported:
Just saw the bug notification, not sure how it happened.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4.4
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
** Tags added: sru-20210222
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1884024
Title:
lxc-test-device-add-remove from ubuntu_lxc failed on B-5.4
Status in ubuntu-kernel-t
$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
$ apt-cache policy pulseaudio
pulseaudio:
Installed: 1:13.0-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.la
Public bug reported:
Since upgrading to 19.10, the sound output on this PC stops.
Looking at the volume control's 'sound settings', the GP107GL High
Definition Audio Controller (digital stereo HMDI 2 output) is disabled.
Doing
pluseaudio -k
restores it.
Possibly relevant from syslog:
Nov 18
** Attachment added: "Output of pa-info for user1, currently with sound"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+attachment/5307312/+files/pa-info-user1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
** Attachment added: "Output of pa-info for user2, currently with sound card
showing as disabled"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+attachment/5307313/+files/pa-info-user2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Interestingly, at the moment if I start playing audio in user1 and
switch to user2, the audio is still audible.
Normally, it'd be silent unless user2 was playing something until
switched back to user1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Yes, it seems to be a 'multiple users logged in' thing.
Use the sound in one user, then - at some seemingly random point that's
NOT while something is actually playing - discover that the sound system
is disabled. It's possible that both users have it not working, or one
to work and one not to.
A
If I log out the first user, the second user suddenly has sound.
And it didn't do this on Friday, when the same programs were running
before the user switch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubunt
Here's another log: user2 logged in at 15:03 to discover that the sound
output was disabled (and stayed that way until user1 logged out, despite
it not playing any audio)
** Attachment added: "logs"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+attachment/5307982/+files/l
Interestingly, both PCs have webcams (both Logitech, but different
models) and if I unplug that on PC2 and switch, there isn't a problem.
I'll try doing it some more next week and see if that's consistent.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
No, it's not (just?) having a webcam.
Two new logs. In both cases user1 started the PC, played some music,
paused it, then switched to user2 - disabled sound output for them.
** Attachment added: "With a webcam plugged in.."
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+
** Attachment added: ".. and without it plugged in."
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+attachment/5309143/+files/soundlog-nowebcam
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio
Just in case it was a driver issue (affecting two different chipsets...)
I can report that it's still behaving like this with version 5.3.0-24.26
of the kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubu
After trying a number of things, deleting the bulk of ~/.config seems to
have worked, so it was probably some old setting from there.
--
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.laun
Attaching the error_log file for review
** Attachment added: "error_log file from cups tree"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1471602/+attachment/4424676/+files/error_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
HP Color LaserJet 2600N prints majority of files fine from Google, PDFs
etc. Example job of uploaded Word doc, converted to Google Doc then
printed to CUPs doesn't print and there are no errors in the logs from
the print job.
Current configuration answering questions from
h
Attaching the error_log file for review
** Attachment added: "error_log file from cups tree"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1471602/+attachment/4424677/+files/error_log.zip
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
** Changed in: linux (Ubuntu Xenial)
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.
https://bugs.launchpad.net/bugs/1891224
Title:
[Hyper-V] VSS and File Copy
Public bug reported:
Errors created when trying to install TeamViewer on Jetson Nano
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified:
usr/share/glvnd/egl_vendor.d/50_mesa.json]
Uname: Linux 4.9.140-tegra aarch64
.tmp.unity_support_test.0:
*** This bug is a duplicate of bug 815996 ***
https://bugs.launchpad.net/bugs/815996
I can confirm that disabeling window snapping in unity tweak tool fixes
this issue for me, I like my window snapping :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Another way that I have found to (temporary) resolve this problem is to
use ARandR. I used ARandR to create a shell script that disables all
displays on the system. I also created one to set each of my normal
display configurations and assigned keyboard shortcuts to each. When the
cursor disappears
Public bug reported:
After a clean install of Ubuntu 16.04.1 on Virtualbox, when I install
the guest additions to it and reboot the lightdm display manager
continually restarts and then errors out. I'm left the other tty
terminals which sometimes do not work. Uninstalling the guest addition
tools
I unchecked 'Enable-3D acceleration' in the VM settings then I
reinstalled Ubuntu 16.04.1 and installed the guest additions, rebooted,
lightdm did not crash at start up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm
** Changed in: lightdm (Ubuntu)
Status: Opinion => New
** Summary changed:
- Lightdm crashes on bootup after installing Virtualbox guest addition tools on
Ubuntu Desktop 16.04.1
+ Lightdm crashes on bootup after installing Virtualbox guest addition tools on
Ubuntu Desktop 16.04.1 when 3D
I had the same problem (phone not audibly ringing) on an Aquaris E5
running Ubuntu 15.04 OTA 11.
I also had another 'irritation' in that some websites overrode my volume
settings. Turn the volume right down, so as not to disturb others while
watching video clips, then open up YouTube in the browse
Are there any workarounds for this for already installed Ubuntu
installs?
I have a laptop user that is having 3+ minute shutdowns for this LUKS
timeout issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools i
Reboots now hang indefinitely with the laptop user. Any update on this?
--
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/1554795
Title:
timeout on restart or shutdow
Has anyone tried replicating #12?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1533251
Title:
Ubuntu phone / Aquaris E5: no ringtones when receiving calls, no sound
I have the same problem on an Aquaris E5 running Ubuntu 15.04 OTA-12.
Is there a config file somewhere that has become corrupted? If you let
me know where the files are I could have a look and see if I can edit
them accordingly and report back.
--
You received this bug notification because you a
Public bug reported:
Whenever I exit full screen in mpv (and presumably other applications
with an opengl context) I find myself with a frozen screen I cannot
interact with, and need to switch to another TTY to restart Unity or
lightdm.
Seems as though this has already been fixed in newer version
I'm also affected by this bug. After some (approx 5/6) disconnects and
re-connects to wifi no problems but then later the wifi network name is
not shown in network-manager applet. If I opt to connect to hidden
network then the network name is available from the dropdown but after
that is selected t
I thought I had changed the package, but dpkg reckons nm-applet is part
of network-manager-gnome rather than network-manager.
--
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.n
Public bug reported:
I'm using Lubuntu 15.04 on an EeePC 901. Using the home wireless network
is fine, but two times in two different places recently, the nm-applet
has seen all the networks for a few seconds after bootup and then
decided it cannot see any.
(Photos of this are available, but as I
This problem seems to be resolved for me with xubuntu 14.10. I did a
clean install and I have not had this problem since.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1297144
yaztromo (tromo): Did you do an upgrade install or a clean install?
There are some packages that were swapped out for 14.10 (especially
related to power management) that you don't get if you do an upgrade
install.
--
You received this bug notification because you are a member of Ubuntu
Touch seed
Public bug reported:
I've been debugging PostgreSQL REL_14_STABLE branch authentication code
starting the postgres postmaster, running psql and then connecting to a
new process using `sudo gdb -p `. After a long day of it, I met
this segmentation fault. This message says, that it is definitely a b
Verified that the package was called xorg and not X11
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2055351
Title:
firefox scree
It is similar but not identical.
I just updated Snap, Firefox, and Chromium, and, currently, Firefox with
hardware acceleration works fine using wayland, but not X11. Firefox
without hardware acceleration works on either.
I am attaching a screenshot of unaccelerated Firefox beside (corrupted)
acc
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753643/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.l
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753642/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753645/+files/Lspci.txt
--
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/bu
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753649/+files/Lsusb-v.txt
--
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.n
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753647/+files/Lsusb.txt
--
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/bu
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753648/+files/Lsusb-t.txt
--
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.n
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753650/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753651/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
ht
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753654/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753655/+files/UdevDb.txt
--
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/
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753644/+files/DpkgLog.txt
--
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.n
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753646/+files/Lspci-vt.txt
--
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
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753657/+files/XorgLog.txt
--
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.n
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753653/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753652/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753660/+files/acpidump.txt
--
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
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753658/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753659/+files/Xrandr.txt
--
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/
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/2055351/+attachment/5753661/+files/xdpyinfo.txt
--
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
Similar hardware:
R7 240 graphics card (previous generation graphics cores) on Athlon
200GE: everything works fine on X11
Plugged SSD from Athlon install into 5600G (Vega 6 graphics instead of
Vega 3): everything works fine on X11.
So it seems to be something weird about Vega 3 graphics in relat
After kernel + x.org updates this week, firefox is now displaying
properly using xserver-xorg on the Athlon 200GE.
--
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/2055351
Title:
Public bug reported:
For more information, please see
https://github.com/notroj/neon/issues/102.
The 22.04 built package of neon lacks GSSAPI support, whereas previous
versions (e.g. 18.04) had this support built-in. This appears to be due
to a recent-ish change in the build logic for neon, which
Public bug reported:
Automatic upgrade failed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0 2.48.2-0ubuntu4.8
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
Date:
** Changed in: snapd
Assignee: Ian Johnson (anonymouse67) => (unassigned)
--
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/1902748
Title:
ubuntu-seed / ubuntu-b
What is the output of these commands:
ps -o cmd fp 1
sudo ls -lah /proc/1/exe
cat /proc/cmdline
--
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/1961418
Title:
snap failed
So indeed your system is still using upstart, in order to use snapd you
will need to switch your system over to use systemd instead. Likely one
of the upgrade scripts from 10.04 to 16.04 did not transition from
upstart to systemd the way a fresh install of 16.04 would default to.
** Changed in: sn
to make sure the message no longer appears
snap refresh snapd --stable
# to go back to tracking stable, as edge sometimes can have unstable changes on
it
```
Thanks,
Ian
** Changed in: snapd (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: snapd (Ubuntu)
Importa
@iogui could you try again? snapd on the edge channel may not have
finished building by the time you tried, but I see that there was an
update pushed out this morning.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-p
@iogui, hmm it could be that our fix isn't working, can you show the
output of these commands:
snap version
snap list
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-pt-base in
Ubuntu.
https://bugs.launchpad.net
Ah Miguel, thanks for realizing my error, I should have probably just
said something like
sudo snap install snapd --edge; sudo snap refresh snapd --edge
which will ensure that it's always installed and gets refreshed.
--
You received this bug notification because you are a member of Ubuntu
Touc
As seb128 found, the issue is also affecting the debian package of snapd
since when we call mksquashfs, we actually have code which specifically
calls mksquashfs from the "system" snap which is either the snapd snap
or the core snap, this is presumably to ensure that a consistent
mksquashfs is used
Also I'm not sure I agree with jdstrand's apparmor profile which
includes:
/run/snapd.socket rw,
which I don't think we want to grant to any PDF file opened with evince?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ap
Dan, note that although we set the SNAP_REEXEC environment variable in
that integration test, that environment variable is actually not obeyed
when it comes to the mksquashfs command which is called here:
https://github.com/snapcore/snapd/blob/dfba7de59a41bc22786d87f53b20deea14240713/snap/squashfs
@slyon could you make available the core18 snap you built with this
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/1949089
Title:
systemd randomly fails to activ
Public bug reported:
While upgrading my Raspberry Pi 3 running 21.04 to 21.10, the upgrade
failed
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-1011-raspi 5.13.0-1011.13
ProcVersionSignature: Ubuntu 5.11.0-1023.25-raspi 5.11.22
Uname: Linux 5.11.0-1023-raspi aarch64
Still exists in Ubuntu 22.04 with NVidia driver 390.157 DP works HDMI
shows as connected, but no output to monitor. HDMI cable works with Mac
Monterey but DP does not.
Nouveau driver works with both ports but the external display speed is
very slow and choppy even if I add PiP and use both ports
s/pull/687
Cheers,
Ian.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
New
Status in atril
FWIW I know what the snapd issue is, the issue is that snapd does not
and will not work in a nested LXD container, we need to add code to make
snapd.seeded.service die/exit gracefully in this situation.
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Changed in: snapd
Importance: Undecided => High
** Changed in: snapd
Assignee: (unassigned) => Maciej Borzecki (maciek-borzecki)
--
You received this bug notificat
Public bug reported:
This happened a little while back and it other than not being able to
boot into the new kernel, it hasn't been a problem (at least for the old
5.4.0-58) It exits on the plymouth hook
Ubuntu 20.04.1 LTS
initramfs-tools 0.136ubuntu6.3
I expected the update-initramfs to rebuild
Is there any timeline on when this will be considered for SRU'ing back
to focal so it is usable in i.e. UC20?
--
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/1878969
Title:
Public bug reported:
package linux-image-5.11.0-25-generic 5.11.0-25.27 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1
ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-25-generic 5.11.0-25.27
ProcVersionSignature:
This systemd bug can be problematic for snapd as well, leading to the
sort of situation in https://bugs.launchpad.net/snapd/+bug/1928806,
where running snap commands frequently leads to many many many leftover
scopes like this
** Also affects: snapd
Importance: Undecided
Status: New
--
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.3 LTS
initramfs-tools:
Installed: 0.136ubuntu6.6
Candidate: 0.136ubuntu6.6
Version table:
*** 0.136ubuntu6.6 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
500 http://archive
SMBSPOOL_KRB5 -
AUTH_INFO_REQUIRED=negotiate
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set
As I said earlier this all works perfectly on Xenial and Trusty.
(A similar AuthInfo
EQUIRED=negotiate
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set
As I said earlier this all works perfectly on Xenial and Trusty.
(A similar AuthInfoRequired negotiate setup also works i
NFO_REQUIRED=negotiate
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set
As I said earlier this all works perfectly on Xenial and Trusty.
(A similar AuthInfoRequired negotiate setup also works in cu
Hi Paul
Ubuntu 18.10 runs fine - the only issue it has is to run SciLab - never
opens, however on Mint no problem. I've reported this earlier.
Ian
On Wed, Dec 5, 2018 at 3:30 AM Paul White <1228...@bugs.launchpad.net>
wrote:
> We are sorry that we do not always have the capacity
Public bug reported:
On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk, my
system was unable to finish booting and I had to go into recovery mode
and remove a number of files before the system would boot. After doing
so I discovered that now the apparmor.service systemd unit alw
FWIW this could be a snapd bug, because while my system was unable to
boot, I disabled all the snaps I had installed except the core snap, and
then after being able to reboot I now re-enable all the snaps and see
some warnings:
May 25 17:32:16 systemd[1]: Starting AppArmor initialization...
May 25
Well I tried restarting AppArmor using `systemctl start apparmor` while
running `dmesg -w -k` and got the following log:
https://pastebin.ubuntu.com/p/98zXMsr6Sy/ I don't see a stack trace for
apparmor itself, just for chrome and pulseaudio.
Is there anyway to have apparmor.service show what profi
How would you recommend I go about checking which profiles are actually
loaded and which profiles are reported as loaded? I have this from aa-
status: https://pastebin.ubuntu.com/p/c2FbrndDzs/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
So I ran your snippet to determine which profiles weren't loaded and the
only one which wasn't loaded was:
```
$ sudo cat /sys/kernel/security/apparmor/profiles | awk '{ print $1 }' >
/tmp/foo ; sudo apparmor_parser -N /etc/apparmor.d/
/var/lib/snapd/apparmor/profiles/ >> /tmp/foo ; sort /tmp/fo
Ah actually, if I move that profile out of the way, then `systemctl
start apparmor` starts immediately. So the issue must be with that
profile being too large (and indeed it is 4-5 MB).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Yes, certainly use the profile for whatever you can use it for. Would
you like me to edit the description on this bug to reflect the actual
underlying cause here or should I just close this and file a new bug for
the memory usage of this profile? I'm no expert here but I think 15.4 GB
memory usage
@Jamie yes this was generated by snapd, the original snapcraft.yaml is
attached.
And also yes I fully understand this was an atypical usage of layouts, I
was experimenting with using layouts to make it seem to a snap
application that an additional package was installed in the base snap. I
generate
1 - 100 of 397 matches
Mail list logo
