Public bug reported:
On ubuntu 18.04, opening the default terminal (gnome-terminal
3.28.2-1ubuntu1~18.04.1), ssh'ing to an up-to-date ubuntu 20.04 system,
running 'vi', and pressing 'i' shows the unwelcome garbage ESC [>4;m.
Pressing ESC emits more garbage: ESC [>4;2m
Focal's default vi is
Filed https://gitlab.gnome.org/GNOME/gtk/issues/2221 in case it's an upstream
bug.
I'll probably regret that.
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2221
https://gitlab.gnome.org/GNOME/gtk/issues/2221
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
To reproduce:
sudo apt install libgtk2.0-dev && echo "#include " > foo.c &&
gcc -Werror -c foo.c $(pkg-config --cflags gtk+-2.0) || echo FAIL
Should complete silently and produce foo.o, but instead, fails as
follows:
Reading package lists... Done
Building dependency tree
FWIW, I ran into this after updating to 19.04 from 18.04.
Audio working fine with HDMI (yay) but not with back panel audio (boo)
unless I ran aplay as root, e.g.
sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav
ps showed timidity running. 'sudo apt remove timidity; sudo
(although on ubuntu 18.04 desktop, the underlying network system might
be systemd rather than dhclient; it's hard to tell, there are so many
layers to keep track of, and they keep changing)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This affects me on Ubuntu 18.04 desktop. After changing hostname, I
have to use nmcli c down... nmcli c up... to update the dynamic DNS
entry.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
Public bug reported:
I've been testing as follows:
- install chromium (or chrome, or chrome beta)
- open http://fishgl.com
- crank up number of fish to 325 (or as high as it'll go and sustain 60 fps)
- after fish are happily swimming, watch them swim for 60 seconds, and count
number of times the
Public bug reported:
I've been testing Ubuntu 18.04.1 with Hades Canyon using the recipe
https://mzwiki.oblong.com/wiki/Hades_Canyon
My smoke test is:
- install chromium (or chrome, or chrome beta)
- open http://fishgl.com
- crank up number of fish to 325 (or as high as it'll go and sustain 60
correct, apt-cache policy did show two sources. I wasn't paying
attention.
Invalid.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1804343
Title:
apt: Misleadingly reports
Public bug reported:
I'm using reprepro to maintain a local repository. It doesn't compute SHA512
hashes.
This worked fine until today, when I got this error:
buildbot@workstation:~/src/python-modules-deps/old$ apt download
python-swagger-spec-validator
Get:1
I should have mentioned, my Hades has 32GB of RAM.
With 8GB or less of RAM, the problem might persist (if I understand the mailing
list posts).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
This just changed for me... but the hardware may matter, as I'm on Hades
Canyon, using the amd gpu, not HD graphics.
A few days ago I updated to the then-latest 4.19-rc2
(and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting
exactly what I did).
Using plain old X (no desktop) on
Still in ubuntu 17.10 with nvidia card.
--
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/1655709
Title:
Spurious crash report dialog on every login
Status in xorg package in
Public bug reported:
For the last few years, on nearly all my computers, ubuntu has
rewarded my logging in with a crash dialog. Nothing's actually
wrong; xorg probably trips over its shoelaces every time it
shuts down, but so late in the process that it doesn't matter.
Today I went through the
@Martin: the problem doesn't reproduce for me if lxd.socket isn't running
before installing lxd.
That's why I posted the script along with output for the ls -l, to show what
happens for me in the two cases.
Purging lxd should stop lxd and lxd.socket, shouldn't it?
Thanks!
--
You received
@martin: I'm on desktop, fwiw. I think you nailed it:
apt-cache policy lxd systemd
# lxd:
# Candidate: 2.0.0-0ubuntu4
# systemd:
# Installed: 229-4ubuntu4
# Clean initial conditions
sudo apt purge -y lxd || true
sudo systemctl stop lxd.socket || true
sudo rm -f /var/lib/lxd/unix.socket
https://help.ubuntu.com/lts/serverguide/lxc.html did provide a workaround: in
the section on nesting, it mentioned
that enabling nesting allowed all sorts of mounts. So I added
lxc.mount.auto = cgroup
lxc.aa_profile = lxc-container-default-with-nesting
to the container's config file, restarted
Public bug reported:
I'm trying to virtualize a package that depends on NFS by installing it
in an LXC container.
The commands
sudo apt-get install nfs-kernel-server
sudo lxc-create -n nfstest -t download -- -d ubuntu -r xenial -a amd64
sudo lxc-start -n nfstest
sudo lxc-attach -n nfstest
Hah. Invalid. The confusion came from another package that had been
built against the earlier ssl. Rebuilding all old packages built
against the earlier beta seems to have solved things.
So at worst, apt's error messages are hard to decipher... but we already
knew that.
Please close and
Sorry for the messy bug. I'll try to narrow it down some more.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1571087
Title:
apt gets confused about a dependency's version,
Public bug reported:
This problem affects today's Xenial release candidate.
I generated a package with mk-build-deps, and tried installing it.
Here's its control file:
Package: foo-blort3.23-build-deps
Version: 3.23.1-76
Architecture: all
Maintainer: Buildus Bottus
If it were a warning, I'd agree with you... but it's an error, and it
stops my scripts cold.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1554223
Title:
apt-get update
I reported this upstream as https://gitlab.com/gnutls/gnutls/issues/49
and it was fixed upstream with
https://gitlab.com/gnutls/gnutls/commit/28e0716146530ff5e9b2041c52f78a9ecc7f63b5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Package changed: ubuntu => gnutls26 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnutls26 in Ubuntu.
https://bugs.launchpad.net/bugs/1557836
Title:
gnutls.pc contains unrecognized command line option -R
Chrome's going to fix it on their end,
https://bugs.chromium.org/p/chromium/issues/detail?id=591480
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1554223
Title:
apt-get
Oh, this is on ubuntu 15.10 (i.e. apt 1.0.10.2.ubuntu1), and probably all
previous versions.
It does not seem to affect ubuntu 16.04 beta 1 (i.e. apt 1.2.3).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Public bug reported:
(ubuntu-bug wouldn't let me report bugs against apt, go figure.)
I run my own apt repo for a third-party app, and I have to include a
dummy i386 package to avoid an error from apt-get.
Along comes Chrome's decision to desupport i386, and suddenly this problem
matters to a
Still present in Ubuntu 15.10. To reproduce:
$ dash -x -c 'test !'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1372529
Title:
dash crashes in 'test !'; fixed upstream;
Public bug reported:
A library which is being developed against the nvidia libGL.so fails to link
against mesa's libGL.so.
The linker complains:
foo: undefined reference to `glProgramUniform1fv'
foo: undefined reference to `glProgramUniform1i'
foo: undefined reference to `glProgramUniform2fv'
Bug 1271839 may be related. I saw both the high CPU usage and extreme RAM
usage (about 1 megabyte/second leak).
It happened when I minimized Chrome, but continued long after I killed all the
chrome processes.
ibus-ui-gtk3 got up to 2+ gigabytes of ram pretty quickly.
Putting more details at
Bug 1276186 may be an acute form of this bug.
I saw both the high CPU usage and extreme RAM usage (about 1 megabyte/second
leak).
It happened when I minimized Chrome, but continued long after I killed all the
chrome processes.
ibus-ui-gtk3 got up to 2+ gigabytes of ram pretty quickly. I'll
fwiw: I hit this using the latest from Nvidia's download site, and
also using the xorg-edgers ppa ( 346.47-0ubuntu1-xedgers14.04.1 ).
The flipping in the terminal seems to be at the same speed as the cursor blink.
I only noticed it in gnome terminal. xterm does not exhibit the problem.
My
Public bug reported:
This is probably a dup of bug 1240757, created just so I could upload
the data requested in that bug report.
On a fresh, probably vanilla, ubuntu 14.04 server, I tried using ubuntu 14.04's
default lxc.
It created containers fine, but they failed to start, complaining
33 matches
Mail list logo