Just to clarify, does this mean root can't use snaps too, or is /root
handled specially?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867921
Title:
cannot create user data directory:
Public bug reported:
A while ago I installed ripgrep on a server with
sudo apt install snapd
sudo snap install ripgrep --classic
sudo snap alias ripgrep.rg rg
and it didn't work for me:
$ rg --help
cannot create user data directory: /home/mg/snap/ripgrep/4: Too many levels
*** This bug is a duplicate of bug 1083038 ***
https://bugs.launchpad.net/bugs/1083038
** This bug has been marked a duplicate of bug 1083038
Encrypted LVM in Ubiquity unavailable when installing alongside an existing
OS
--
You received this bug notification because you are a member of
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318203/+files/Snap.Info.chromium.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318206/+files/Snap.Info.gtk-common-themes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318199/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.Info.core18.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318205/+files/Snap.Info.core18.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318200/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318197/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318202/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318196/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318195/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318207/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318204/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318201/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318194/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318193/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318198/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Public bug reported:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com/3 renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1858636/+attachment/5318192/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1598995
(same steps to reproduce, and I see the same "runtime check failed:
(impl->staging_cairo_surface != cairo_surface)" errors in my journal
that correspond to Firefox crashes)
** Bug watch added: Mozilla Bugzilla #1598995
Public bug reported:
Steps to reproduce:
- make sure Firefox is not running
- export MOZ_ENABLE_WAYLAND=1
- firefox
then in a new terminal
- export MOZ_ENABLE_WAYLAND=1
- firefox www.google.com
Expectation:
- a new tab opens in the Firefox window, loading google
Actual result:
- firefox
Public bug reported:
I see this on my machine when I try to report a Firefox bug:
$ ubuntu-bug firefox
ERROR: hook /usr/share/apport/package-hooks/source_firefox.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook
Unfortunately I was unable to reproduce the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851528
Title:
JS ERROR: TypeError: malformed UTF-8 character sequence at offset 0
and segfault in
Duplicate of bug 574287?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1338223
Title:
Tasksel has deleted all my data!
To manage notifications about this bug go to:
Duplicate of bug 574287?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779645
Title:
Critical bug in tasksel: `tasksel remove task-name` removes whole
system
To manage notifications about this
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1870
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1870
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1870
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The JS traceback points to this line:
https://gitlab.gnome.org/GNOME/gnome-shell/blob/3913fa5044b2cd1d5abadc9b4254d06215491458/js/ui/windowManager.js#L1771
(GitLab commit doesn't match gnome-shell from Ubuntu 19.10, sorry! I
didn't have the time to go hunt for the exact commit that corresponds
apport-retrace --gdb --sandbox system --cache ~/.cache/apport-retrace
/var/crash/_usr_bin_gnome-shell.1000.crash
...
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Toks failas
Public bug reported:
I was trying to bring my Firefox window to front by pressing Super+2
(it's my second pinned launcher), and gnome-shell crashed.
journalctl shows this:
lapkr. 06 16:38:58 blynas gnome-shell[3417]: JS ERROR: TypeError: malformed
UTF-8 character sequence at offset 0
The patch from https://bugs.debian.org/cgi-
bin/bugreport.cgi?att=1;bug=934068;filename=postgrey_init.patch;msg=
fixes the reload problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842432
Title:
This is still a problem in 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842432
Title:
service postgrey reload fails
To manage notifications about this bug go to:
I can confirm that the fix works with chromium snap 78.0.3904.70 (rev
909).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849105
Title:
[snap] cannot pause video with bluetooth headset buttons any
Duplicate of bug 1844805?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848006
Title:
package virtualbox-dkms 6.0.12-dfsg-1 failed to install/upgrade:
installed virtualbox-dkms package
I've been googling, and it appears that Chromium should enable the mpris
interface in the snapcraft YAML for this to work:
https://snapcraft.io/docs/mpris-interface
Except if Chromium actually uses what looks like a dynamic part
("instance" + pid) in the dbus interface name, can it be made to
I'm seeing this in journalctl -b -g chromium:
spal. 19 15:00:35 blynas dbus-daemon[4473]: apparmor="DENIED"
operation="dbus_bind" bus="session"
name="org.mpris.MediaPlayer2.chromium.instance5306" mask="bind" pid=5306
label="snap.chromium.chromium"
spal. 19 15:00:35 blynas
This is fixed on Ubuntu 19.10, where journalctl -g works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751657
Title:
man journalctl gives info about -g option not present in command
To
journactl --grep works in Ubuntu 19.10 (but not 19.04 or older
versions).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751006
Title:
Journalctl compiled without pattern matching support, pcre2 is
Public bug reported:
On Ubuntu 19.04 I could press the button on my Bluetooth headset and the
YouTube video playing in my Chromium would pause/resume. This no longer
works in 19.10. What happens instead is I get an OSD popup with a NO
ENTRY symbol (circle with a diagonal backslash) from
So, uh, I tried another reboot so I could debug the problem some more,
and ... well ... the machine booted. No problems. I've no idea what's
going on, feel free to close this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oops, I didn't read the error messages closely enough, sorry!
(Also the mirror came back up right when I applied the
Acquire::ForceIPv4 "true"; workaround, making me think my initial
analysis was right. What a coincidence!)
--
You received this bug notification because you are a member of
In case this might be relevant:
- /var is a separate partition (/dev/md1)
- /var/cache is a separate partition (an LVM volume)
- /tmp is a separate partition (an LVM volume)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW journalctl -b is showing a bunch of
Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for
cmd.
Sep 11 19:16:30 fridge lvmetad[457]: WARNING: Ignoring unsupported value for
cmd.
before systemd unit timeouts that are about those missing partitions
failing to mount.
If I run pvscan --cache -aay in the systemd emergency console, all
logical volumes get activated and the system then proceeds to boot
normally.
It seems like for some reason udev is not running pvscan for me?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
I've upgraded a server from Ubuntu 16.04 LTS to 18.04 LTS and now it
fails to activate LVM volumes during boot (which causes systemd to stop
in the middle of the boot process and ask me to fix this on the console
without starting up services like SSH).
The root partition,
So I see
Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
rehash: error: skipping dovecot.pem, cannot open file
rehash: warning: skipping duplicate certificate in AlphaSSL_root.crt
dpkg: error processing package ca-certificates
Public bug reported:
I was upgrading an Ubuntu 16.04 LTS server to 18.04 with sudo do-
release-upgrade and it crashed.
I did not see where the error was because etckeeper's messages made them
scroll too far back, and do-release-upgrade sets up screen in a way that
makes it impossible for me to
Public bug reported:
Today I've discovered that I cannot use apt-get any more:
apt update
Hit:1 http://ppa.launchpad.net/mgedmin/ppa/ubuntu disco InRelease
Ign:2 http://ddebs.ubuntu.com disco InRelease
Ign:3 http://ddebs.ubuntu.com disco-updates InRelease
Hit:4
Forwarded upstream: https://github.com/karelzak/util-linux/issues/857
** Bug watch added: github.com/karelzak/util-linux/issues #857
https://github.com/karelzak/util-linux/issues/857
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1589289 ***
https://bugs.launchpad.net/bugs/1589289
** This bug has been marked a duplicate of bug 1589289
fstrim: cannot open /dev/.lxd-mounts: Permission denied
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Possibly related: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=934068 (I'm not sure if that start-stop-daemon
issue is merely cosmetic or the actual cause of this problem, and the
upstream issue doesn't say).
** Bug watch added: Debian Bug tracker #934068
Public bug reported:
$ sudo service postgrey reload
Job for postgrey.service failed because the control process exited with error
code.
See "systemctl status postgrey.service" and "journalctl -xe" for details.
$ service postgrey status
● postgrey.service - LSB: Start/stop the postgrey daemon
Additional information:
- the container is a "VPS" provided by a popular local hosting company
Interneto Vizija (https://iv.lt)
- they have their own patched 2.6.32-042stab138.1 kernel that I have no
capability of upgrading
- the upgrade process shows a fancy ncurses warning that libc6 requires
I asked the DC support about Ubuntu 18.04 LTS support and apparently
it's not supported on their OpenVZ offerings.
I suppose this bug can be closed? Unless you'd prefer to detect the
situation and abort the upgrade, to prevent users from shooting their
feet off?
--
You received this bug
Public bug reported:
do-release-upgrade of Ubuntu 16.04 to 18.04 inside an OpenVZ container
fails rather early in the upgrade process with this error.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libc6 2.23-0ubuntu11
Uname: Linux 2.6.32-042stab138.1 x86_64
ApportVersion:
Possibly related to https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/17
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #17
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17
--
You received this bug notification because you are a member of Ubuntu
Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903737
This appears to have been fixed in 1.80, which is already present in
eoan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828587
Public bug reported:
Every cloc invocation produces the following warning:
$ cloc --version
Unescaped left brace in regex is deprecated here (and will be fatal in Perl
5.32), passed through in regex; marked by <-- HERE in m/({ <-- HERE |})/ at
/usr/bin/cloc line 8555.
1.76
I personally do not see this bug on disco (19.04).
According to the Debian bug this should be fixed in bionic (18.04 LTS)
and later versions. Looks like only xenial is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The gnome-bugs link is broken. Working links:
- https://bugzilla.gnome.org/show_bug.cgi?id=525574 (old bugzilla)
- https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5 (new gitlab)
** Bug watch added: bugzilla.gnome.org/ #525574
https://bugzilla.gnome.org/show_bug.cgi?id=525574
** Bug
> This is a bug, but i'm not sure if we want our defaut to be larger as
it will take up more excess space on other isos
The comment in /etc/testdriverc says
# Note that this will be a sparse, qcow2 file, so it should not actually
# take that much space on the filesystem.
so it shouldn't
(Of course I forgot to mention the relevant bit: I'm on Ubuntu 18.10
with kernel 4.18.0-16-generic (version 4.18.0-16.17).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389077
Title:
[HP ProBook
Happened to my Lenovo ThinkPad X220. Yesterday I was playing Factorio,
with the laptop fan spinning full-throttle, and intel_powerclamp started
idle injection, which, ok, fair enough. Factorio is very CPU hungry and
this laptop model is like 6 years old.
What is a problem is that today I'm not
*** This bug is a duplicate of bug 1819977 ***
https://bugs.launchpad.net/bugs/1819977
** This bug has been marked a duplicate of bug 1819977
razor2 had unknown error during get_server_info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Starting with March 14 I'm getting two or three emails a day that look
like this:
From: Cron Daemon
To: ama...@fridge.pov.lt
Subject: Cron test -e /usr/sbin/amavisd-new-cronjob &&
/usr/sbin/amavisd-new-cronjob sa-clean
Date: Thu, 14 Mar 2019 01:24:10 +0200 (EET)
razor2:
Tried this again on Ubuntu 18.10, and I'm happy to report that almost
everything works fine!
- "Other locations" in Nautilus shows my Samba server (after a couple of
seconds)
- I can click on it, get an authentication dialog, then see the shares
- I can click on a share and see the files
- I can
Public bug reported:
Whenever cups-daemon is upgraded (by unattended-upgrades usually), it
stops cups-browsed as a side effect of the upgrade. While cups.service
itself is restarted by the time the upgrade process is done, cups-
browsed.service remains stopped until manual admin intervention,
Saw this crash for the first time.
I'm on Ubuntu 18.10. Every time I ask gnome-software to check for
updates, the number of open files (watch 'ls /proc/$(pidof gnome-
software)/fd') grows by 25, then drops a bit and settles down to 7
higher than it was before.
I'm attaching two snapshots of ls
** Attachment added: "after-update-later.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+attachment/5220141/+files/after-update-later.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is still a problem on Ubuntu 18.10:
- search spins forever
- clicking on a category shows a bunch of empty boxes with an ellipsis in it
- fetching updates also seems to spin forever
journalctl _EXE=/usr/bin/gnome-software shows nothing today; the last
log entries were from Nov 9:
lapkr. 09
Apparently journalctl --grep requires pcre2 too (bug 1751006).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163
Title:
[MIR] pcre2
To manage notifications about this bug go to:
Public bug reported:
My journalctl is full of these:
lapkr. 09 16:18:30 platonas org.gnome.SettingsDaemon.MediaKeys.desktop[5239]:
[5695:5695:1109/161830.225054:ERROR:gl_surface_presentation_helper.cc(237)]
GetVSyncParametersIfAvailable() failed!
lapkr. 09 16:18:30 platonas
Public bug reported:
I've started getting weekly cron emails starting on Oct 7, 2018 that say
/etc/cron.weekly/fstrim:
fstrim: /var/spool/postfix/etc/sasldb2: not a directory
The previous week's email did not have any complaints from fstrim, and
I'm not sure what changed since then.
Public bug reported:
I was upgrading my laptop from 18.04 LTS to 18.10 with
apt update
apt upgrade
do-release-upgrade
and it failed, due to
dpkg: dependency problems prevent processing triggers for gconf2:
gconf2 priklauso nuo psmisc; tačiau:
Paketas psmisc dar
gconf2 broke my 18.04 -> 18.10 upgrade with
dpkg: dependency problems prevent processing triggers for gconf2:
gconf2 priklauso nuo psmisc; tačiau:
Paketas psmisc dar nekonfigūruotas.
dpkg: klaida, apdorojant paketą gconf2 (--configure):
dependency problems - leaving
Upstream bug: http://bugs.debian.org/877279
Upstream fix: https://salsa.debian.org/perl-
team/modules/packages/ciderwebmail/commit/6f5ca5f9ebd42d309b20fa844c0a18f1458c001a
** Bug watch added: Debian Bug tracker #877279
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877279
--
You received
I've submitted a merge request to the Debian packaging repository:
https://salsa.debian.org/perl-
team/modules/packages/ciderwebmail/merge_requests/1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The instructions in README.Debian, which are
Included are snippets for production use integrating with Apache2 via
uWSGI, enabled like this as root:
apt install apache2 uwsgi uwsgi-plugin-psgi
Public bug reported:
The ciderwebmail package ships /etc/apache2/conf-
available/ciderwebmail.conf as a broken symlink, pointing to
../../ciderwebmail/apache-uwsgi.conf.
It should be pointing to ../../ciderwebmail/apache2-uwsgi.conf.
This breaks installation instructions as specified in
FWIW a cleaner workaround that also works is creating a /etc/Muttrc.d/00
-fix-black-bar.rc that does
color normal default default
This way you don't have to deal with conffile changes on next upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I launched virt-manager and connected to libvirtd running on a local
server via an SSH connection. I got an unexpected error dialog
Error launching host dialog: 'NoneType' object has no attribute
'__getitem__'
I have a screenshot of the last part of the traceback
Public bug reported:
mg@platonas: ~ $ ubuntu-support-status --show-unsupported
„platonas“ palaikymo būsenos santrauka:
Jūs turite 459 paketų (11.7 %) palaikomų iki balandžio 2021 (Bendruomenė - 3y)
Jūs turite 2565 paketų (65.4 %) palaikomų iki balandžio 2023 (Canonical - 5y)
Jūs turite 11 paketų
Public bug reported:
I ran debsums -ac and it printed this error
debsums: Error: symlink loop detected in path 'usr/share/doc/module-
init-tools/changelog.Debian.gz'. Please file a bug again module-init-
tools.
So here I am, filing a bug against module-init-tools.
ProblemType: Bug
(TBH I've no idea what debsums is nattering about, /usr/share/doc
/module-init-tools/changelog.Debian.gz is a regular file, and no parent
directory is a symlink.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I was upgrading a laptop with Ubuntu 16.04 LTS to 18.04 LTS using sudo
do-release-upgrade over SSH and the upgrade failed and prompted me to
send this bug report.
Hope the logs contain sufficient information; the UnicodeDecodeError
from an apport hook that scrolled past the
Public bug reported:
I've a bunch of these "virtual private servers" (actually from OpenVZ
containers) from iv.lt. I've been upgrading them from Ubuntu 14.04 to
16.04. Every time the upgrade hangs in libc6. First, it shows a
warning in a nice colourful ncurses dialog
Kernel version not
** Description changed:
I'm trying to build a Debian package that uses dh-python, pybuild, and
tox.
debuild -i runs dpkg-buildpackage, which runs debian/rules build, which
runs dh build --with python2,python3 --buildsystem=pybuild, which runs
dh_auto_test -O--buildsystem=pybuild,
Public bug reported:
I tried to upgrade my laptop today with 'sudo do-release-upgrade -d',
and the upgrade failed with the following error messages:
Errors were encountered while processing:
python-gi-cairo
klibc-utils
curl
initramfs-tools-core
I'm testing a bootable USB key with
udisksctl unmount -b /dev/sdb1
sudo setfacl -m user:$USER:rw /dev/sdb
kvm -drive format=raw,file=/dev/sdb -m 2048
and I get the GRUB menu in the KVM window just fine, but arrow keys do
not work (and I have to use Ctrl+N/Ctrl+P to select the GRUB
This is a very annoying bug. Last morning unattended-upgrade failed on
a machine, so I set APT::Periodic::Verbose to "3" and this morning I got
a very verbose email showing that it succeeded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yurii: can you clarify how that broke unattended upgrades?
I also don't see how a cron script might get different PATH values from one day
to the other.
I just had another instance of this bug on a third Ubuntu 14.04 LTS server
(this one a physical machine, not a VPS) where unattended-upgrades
Duplicate of bug 1022865?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1730027
Title:
trap divide error
To manage notifications about this bug go to:
The nightly unattended-upgrade (which I've configured to Unattended-
Upgrade::Remove-Unused-Dependencies "true";) removed the .old kernel on
two different 14.04 LTS servers last night, leaving both with no backup
kernel at all.
In fact now that I'm paying attention again, I have quite a number of
Yes, etckeeper shows that xinetd was installed in a separate apt
transaction, after cups-bsd. Both happened in 2009.
I suspect I don't need lpd compatibility -- I expect any users who use
the print queue access it over IPP. I think I'll remove xinetd entirely
and forget about this issue.
--
Yes, this system has been continuously upgraded from older Ubuntu
versions (starting with 9.04). It acts as a print server for the
office. I've no memory of manually setting up xinetd for cups-lpd. I
always assumed it was pulled in automatically as a dependency.
/etc/xinetd.d/printer looks
The last line of the log excerpt has a suspiciously low PID number
Feb 16 07:03:30 fridge xinetd[2756]: Exiting...
I took that to be a clue that this is the old instance of xinetd, that
was supposed to be stopped by the two lines above:
Feb 16 07:03:29 fridge xinetd[24720]: * Stopping
In case this might be relevant: the only service xinetd is serving on
this machine is /usr/lib/cups/daemon/cups-lpd (via
/etc/xinetd.d/printer).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750387
Public bug reported:
This has happened twice now: xinetd dies during an unattended-upgrade
process and I have to restart it manually.
/var/log/syslog contains
Feb 16 07:03:28 fridge systemd[1]: Reloading.
Feb 16 07:03:28 fridge systemd[1]: Started ACPI event daemon.
Feb 16 07:03:28
Well, I got the debug output this time (a whole megabyte of it, split in
two different emails), but unattended-upgrades succeeded, so I still
don't know what the original problem was.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The good news is the problem is reproducible.
The bad news is APT::Periodic::Verbose "1" doesn't make unattended-
upgrade produce any more output in its failure email:
Unattended upgrade returned: False
Packages that attempted to upgrade:
dh-apparmor libapparmor1
101 - 200 of 1540 matches
Mail list logo
