Public bug reported:
$ sudo systemctl status apparmor
● apparmor.service - AppArmor initialization
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-05-26 10:36:35 BST; 38s ago
Docs: man:apparmor(7)
Public bug reported:
This issue has come up from trying to install Mixxx from their official
LaunchPad host ppa and it appears to reference libtag1-vanilla, which
does appear to exist in 16.04 but I believe should be superseded by
libtag1v5-vanilla, yet it doesn't seem to recognise as such. As it
Ahhh obviously fully Mixxx's fault, just realised the libtag version it
fails to downgrade to is in their ppa and not the Ubuntu repo looking at
the apt-cache policy output.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tagl
Why does Launchpad not recognise Launchpad's bug tracker when you try
and associate another package as being affected? I wanted to correctly
link this bug on the Mixxx tracker but it throws up an error of
unrecognise bug tracker!!
https://bugs.launchpad.net/mixxx/+bug/1778950
--
You received thi
This problem has hit me in the last two weeks (Meizu MX4), and I can't
install *any* upgrades. HELP!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntuone-credentials in
Ubuntu.
https://bugs.launchpad.net/bugs/1553150
Ti
Argh... after reading the above (yeh, I know...) I went into the
accounts settings and put my credentials in there, then returning to the
updates page I could request the updates only to be hit by a 401
UNAUTHORIZED error.
--
You received this bug notification because you are a member of Ubuntu
T
Can confirm that this is affecting VLC as well.
** Changed in: vlc (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1374825
Title:
Public bug reported:
My Python application works in 18.10 fine, but when upgrading to 19.10
for development reasons the same script produces the errors reported
below. I have checked on the Python bug tracker and there are no related
bug reports.
Traceback (most recent call last):
File "/usr/li
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1821822
Title:
Temporary failure in name resolution in Python 3.7.2
Status in python3-default
** Description changed:
My Python application works in 18.10 fine, but when upgrading to 19.10
for development reasons the same script produces the errors reported
below. I have checked on the Python bug tracker and there are no related
bug reports.
Traceback (most recent call last):
** Description changed:
- My Python application works in 18.10 fine, but when upgrading to 19.10
- for development reasons the same script produces the errors reported
- below. I have checked on the Python bug tracker and there are no related
- bug reports.
-
- Traceback (most recent call last):
Public bug reported:
Description:Ubuntu 18.04.3 LTS
Release:18.04
uname -a: Linux dtsmith-vallum 4.15.0-65-generic #74-Ubuntu SMP Tue Sep
17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
All updates available to date have been applied.
Command is "sudo apt-get install libglib2.0-
This may be a teamviewer problem. I don't know if it is relevant, but when
searching /var/log for any mention of munmap, I got the following results:
dvs4@dvs4-E6540:/var/log$ sudo grep -R munmap *
auth.log:Dec 7 08:31:22 dvs4-E6540 sudo: dvs4 : TTY=pt
I don't know whether we've had a regression here, but I started seeing
what looks like this exact same problem this morning.
--
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/130364
Marcelo,
Thanks for the information. My system was unresponsive enough that
diagnosing the problem was a huge pain. I decided to back up /home and
do an install of 16.04 from scratch since I'd been intending to do an
upgrade soon anyway.
I was also using the "proposed" repo, so I should have be
Serge,
I am not seeing anything like this with 16.04.4. Since I did a full
wipe and reinstall, I didn't expect to. Yes, I definitely saw it with
14.04.5 with "proposed" enabled. And the packages Marcelo indicated
were among the most recently installed. I think you can treat his
system as repre
Yes, I was using -backports. I dumped a list of everything I had
installed before I reinstalled, and I had cgmanager/trusty-updates
0.24-0ubuntu7.5 installed right before the I wiped my system. I was
still experiencing the problem.
--
You received this bug notification because you are a member
Public bug reported:
Description:Ubuntu 12.04.4 LTS
Release:12.04
lsb-base:
Installed: 4.0-0ubuntu20.3
Candidate: 4.0-0ubuntu20.3
Version table:
*** 4.0-0ubuntu20.3 0
500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64
Packages
100 /var/lib/dpkg
I had a copy paste error with that patch. Adding another.
** Patch added: "init-functions.patch"
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+attachment/4159603/+files/init-functions.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pa
I removed "A proposed patch", it was bad.
** Patch removed: "A proposed patch"
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1346646/+attachment/4159596/+files/init-functions.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Nevermind this is in error, I just noticed the:
if [ -n "$pidfile" ]; then
pidfile="-p $pidfile"
fi
bit in there.
So there is no bug. You can close this, if I can't.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Public bug reported:
Just an overall problem with apt-update from the CL after a fresh
install.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.
If it helps, I had success configuring a Google account with GOA on
Unity yesterday afternoon. Today, setting up the same with Ubuntu-Gnome
no longer works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts
Public bug reported:
unity8 will freeze up from time to time during operation of xterm or
other x11 legacy apps. This freeze up was reported by htop running in an
instance on tty1. It will show two sessions of unity8 running at 100%.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity8 8
Public bug reported:
I updated 16.04 and rebooted. No sound on any applications. Checked to
see if sound card was detected with aplay. None detected. Ran lspci.
Shows audio device Intel Corporation Sunrise Point-H HD Audio (rev 31)
Sound working prior to installing last updates. No hardware change
I ran ubuntu 16.04 live from usb and it has sound. I installed it with
updates and no sound. I installed it without updates and sound works.
Conclusion? The updates nuked the sound.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
Public bug reported:
Installing Mate desktop on Ubuntu Studio.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-google (not installed)
ProcVersionSignature: Ubuntu 4.4.0-34.53-lowlatency 4.4.15
Uname: Linux 4.4.0-34-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Archit
Public bug reported:
Installing Mate desktop on Ubuntu Studio.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-facebook (not installed)
ProcVersionSignature: Ubuntu 4.4.0-34.53-lowlatency 4.4.15
Uname: Linux 4.4.0-34-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Arch
28 matches
Mail list logo
