Also filed (and fixed!) in Arch Linux:
https://bugs.archlinux.org/task/63073
A build switch was introduced in Vim 8.1.1529, so vim can be built with
--disable-canberra.
Commit
https://github.com/vim/vim/commit/21606676d9ebc6f159c56ee90733e5d5720ab3d7
Even though it is technically "no X", I
Note that this is not limited to metadata_csum_seed, other "recently"
added ext4 features cannot be used on the system partition (and maybe
the whole system disk, if you have other ext4 partitions there with such
features).
At least confirmed to not work with GRUB:
- metadata_csum_seed
-
The bug is still present in version 2.04-1ubuntu26.6 in focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844012
Title:
grub2 doesn't recognize ext4 with metadata_csum_seed enabled
To manage
** Bug watch added: Debian Bug tracker #866603
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866603
** Also affects: grub2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866603
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Norbert, it is *extremely* inappropriate to edit the bug description to
publicize your workaround. Adding instructions to set the sandbox user
to "root" at the start of the bug description is quite simply awful.
I have reverted that change.
** Description changed:
READ ME FIRST
@Chelmite The double slash is equivalent to a single slash, so there is
not much of a problem here, just a very minor cosmetic issue. Synaptic
is certainly the one who told APT to download stuff in
/root/.synaptic/tmp, so it is the one which should have changed the
ownership to _apt beforehand.
@Uqbar The microcode update is fine and exactly as expected. 2018-01-08
is the release date of the microcode *bundle*, which contains 20
microcodes updated at various times around late November, mid-December
2017.
In the case of his 0x406e3 CPU, the microcode is from 2017-11-16, which
is exactly
Public bug reported:
For several versions now, apt has introduced a system user named _apt.
When downloading files, it tries to switch to this user in order to
limit the attack surface; downloading files as root is quite simply
dangerous. If the user _apt cannot write to the target directory,
Duplicate of bug #1589083
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637856
Title:
Cryptsetup freezes if the package cryptsetup is not installed
To manage notifications about this bug go to:
Sorry for the double-posting, the idea only occurred to me after sending
my first comment.
Installing the "cryptsetup" package installs several dependencies,
including a lot of boot-time stuff I do not need. I wondered if one of
the dependencies could solve the problem by itself, and it turns out
I can confirm this on 16.04 32bit from a fresh minimal install.
* The container had been working fine for many years on 12.04 32bit
* The container was still working a few days ago before switching to 16.04
* cryptsetup luksOpen hangs without further notification
More accurately, using strace,
Public bug reported:
I first encountered this bug in nvidia-375, everything was fine in
nvidia-367. Here is a previous bug report, which was marked as fixed
(but only in Zesty, if I understand correctly):
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-367/+bug/1674677
Here is
Came here to report this very bug, which I encountered when upgrading to
2.0.12-5ubuntu3.1.
** Summary changed:
- incorrect postinstall script
+ Syntax error in postinstall script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
DESKTOP_SESSION is created by the display manager.
In particular, SDDM puts an absolute path in DESKTOP_SESSION, which seem
to be quite distinct from what other managers are doing. I have opened
https://github.com/sddm/sddm/issues/852 about that matter.
However, the 60x11-common_xdg_path could
Another test, this time on a NUC with a Pentium N3700 Braswell CPU under
Xenial.
$ uname -a
Linux 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:19:48 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/cpuinfo
(...)vendor_id : GenuineIntel
cpu family : 6
model : 76
Here is a successful test of a Core i5-6600 Skylake CPU under Xenial.
$ uname -a
Linux 4.10.0-28-generic #32~16.04.2-Ubuntu SMP Thu Jul 20 10:19:48 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/cpuinfo
(...)
vendor_id : GenuineIntel
cpu family : 6
model : 94
model
Uqbar, what version of Ubuntu are you using, and what kernel version?
> I cannot see any possibility that "any non-Ubuntu container" (actually
anything else) is started earlier than this. Isn't it?
Quite simply, the machine could be running any kind of supervisor (Xen,
Hyper-V, ESX...), which
Dave, not all vendors ship updated microcode in a timely manner. This is
rarely the case on consumer motherboards, hopefully the situation is
better on servers.
Also, there is a debate here, between the maintainer of the package and
the SRU team. If I understand correctly, the package includes
I accidentally wrote a duplicate report of this bug: I had checked the
bug list before reporting, but this bug was not visible because it was
already marked as fixed (in Arty).
Since this bug will be used for Stable Release Updates, is there a way
to still list it (with the default Launchpad
Public bug reported:
As reported by Henrique de Moraes Holschuh from Debian, there is a
hyperthreading-related bug in recent Skylake and Kaby Lake processors that can,
when triggered, cause unpredictable system
behavior (application and system misbehavior, data corruption and data loss in
the
I came to this issue from another route: ever since installing package
nvidia-375, I have the following warnings every time APT runs the libc-
bin trigger:
Processing triggers for libc-bin (2.23-0ubuntu7) ...
/sbin/ldconfig.real: /usr/lib/nvidia-375/libEGL.so.1 is not a symbolic link
Martin, I think you should file a new issue for what you described.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651923
Title:
apt https method decodes redirect locations and sends them to the
I have tested the new package on Xenial, following the instructions in
https://wiki.ubuntu.com/Testing/EnableProposed
APT packages installed before updating:
apt 1.2.18
apt-transport-https 1.2.18
apt-utils1.2.18
libapt-inst2.0 1.2.18
libapt-pkg5.0
As written in comment #50, this problem is in the apt package. Also, it
is specific to 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607535
Title:
ttf-mscorefonts-installer 3.4+nmu1ubuntu2
Public bug reported:
* OS release: Ubuntu 16.04.1 LTS
* Package version: 3.168.3
/usr/lib/update-notifier/package-data-downloader runs /usr/lib/apt/apt-
helper in a subprocess call. apt-helper is provided by the apt package.
Since update-notifier-common will fail to perform one of its core
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
I am certain the redirect was there before.
The redirector and the mirrors are listed in the Debian package ttf-
mscorefonts-installer version 3.6, and were added back in 2013 or 2014,
with a comment
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
I strongly disagree!
The space was put in the URL by the original corefonts SourceForge
project way back in 2002, and has been there since then!
The space was there when apt 1.2.12~ubuntu16.04.1
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Investigations (comments #1 and #5) indicate that the apt package is the
most likely culprit. Quite possibly the update to 1.2.15 on Xenial
caused the regression.
** Package changed: update-notifier
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Investigating further, it is quite possible the problem appeared in APT
1.2.15. Timeline of install and updates on my machine:
* 2016-07-19: U apt:amd64 1.2.10ubuntu1 -> 1.2.12~ubuntu16.04.1 # OS install
*
The core issue is that ttf-mscorefonts-installer files are repeatedly
failing to download, so you are repeatedly emailed about it. (The email
sure could be improved.)
update-notifier handles the downloads, but the actual downloads are
performed by apt-helper, and that program has trouble
This bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source
/update-notifier/+bug/1641671
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646737
Title:
Annoying "processing..." mails
To
Hello everybody that recently commented on this issue (starting with
comment #10)!
I believe the core issue is in not in the msttcorefonts package: it is
modified on Ubuntu to delegate all downloads to the update-notifier
package, which is the one having issues. (That is why installing the
Debian
The following recent bugs are quite likely related to this one:
* https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1646737
* https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1641671
* https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1607535 (huge,
hot one)
Digging into update-notifier-common, it appears the actual failure can
be reduced to the following command-line (for 1 of the 11 downloads):
/usr/lib/apt/apt-helper \
download-file \
http://downloads.sourceforge.net/corefonts/andale32.exe \
/tmp/andale32.exe \
** Description changed:
* OS release: Ubuntu 16.04.1 LTS
* Package version: 3.168.3
For the past few days (maybe even weeks for other users), update-
notifier has been very repeatedly failing to handle the downloads for
ttf-mscorefonts-installer. Previously it was working fine on the
Public bug reported:
* OS release: Ubuntu 16.04.1 LTS
* Package version: 3.168.3
For the past few days (maybe even weeks for other users), update-
notifier has been very repeatedly failing to handle the downloads for
ttf-mscorefonts-installer. Previously it was working fine on the same
system.
Problem still present in 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478408
Title:
There is no colord-kde entry in System Settings
To manage notifications about this bug go to:
The bug is still present in 4.2.0-38, and also in 4.4.0-24 (Xenial
kernel).
I have found a way to reliably trigger it: bring the cursor to the left
side of the screen. As long as the cursor never touches that edge, it
does not leave old copies behind. As soon as the cursor touches that
edge, the
Second screen capture.
** Attachment added: "Cursor corruption over the Dolphin file manager"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1584453/+attachment/4668018/+files/corruption-2.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Third and final screen capture.
** Attachment added: "Cursor corruption over xeyes"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1584453/+attachment/4668019/+files/corruption-3.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
After upgrading from 4.2.0-35 to 4.2.0-36, the mouse cursor leaves old
copies behind, mostly over interactive elements (web links, forms,
window menus, etc.). See attached photographs for examples.
The bug keeps occurring after reboots and cold starts, and occurs on
every
Version 6.30.223.248+bdcom-0ubuntu0.2 is now available in trusty-updates
and solves the issue.
** Changed in: bcmwl (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: upgrade-software-version
** Bug watch added: Debian Bug tracker #813730
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813730
** Also affects: mcomix via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813730
Importance: Unknown
Status: Unknown
--
You received
Public bug reported:
Development of MComix has been rekindled. Version 1.2 was released at
the end of January, containing significant fixes and improvements.
Version 1.2.1 is a Windows-focused bugfix release.
I have tested MComix on Kubuntu 14.04.4, running it from its unpackaged
source code, as
** Attachment added: "Failed DKMS build under Linux 4.2"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1528225/+attachment/4572685/+files/bcmwl-kernel-source.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bcmwl module in Trusty does not build with Linux 4.2 (Wily kernel).
Apparently the API changed a bit (two constants are unknown during the
build process, and one function receives too few arguments). I have
attached the automatically-generated crash file.
--
You received this bug
Public bug reported:
Likely scenario (unless I missed a crucial piece of information):
- User has a working persistency file (or partition), with an Ubuntu 14.04.2 ISO
- User upgrades to an Ubuntu 14.04.3 ISO, and boots it with the same
persistency settings
Likely result:
- It appears to the
Adding tag regression-update as per comment #7 of bug #1401620
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481117
Title:
casper 1.340.1 breaks previous
Public bug reported:
In Ubuntu 12.04.5 LTS (procps 1:3.2.8-11ubuntu6.3), the following worked
fine:
$ export PS_FORMAT=thcount
$ ps
THCNT
1
1
In Ubuntu 14.04.1 LTS (procps 1:3.3.9-1ubuntu2), it does not work
anymore:
$ export PS_FORMAT=thcount
$ ps
warning: $PS_FORMAT ignored. (unknown
On 2014-06-10, Barry Warsaw wrote:
It's a bit of a long, complicated process, but rest assured we are on it.
It's been three weeks since the status of this bug was changed to Fix
Released, but it is apparently still not available in Ubuntu 14.04. In
what time frame can we expect to see it land
2:4.1.6+dfsg-1ubuntu2 is in LTS, this bug should be closed.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1277432
Title:
Please update to samba 4.1.x from Debian/sid for trusty
To
This bug is still present in 14.04 LTS. Putting the following line in
/etc/init/smbd.override solves it for me:
start on (local-filesystems and net-device-up IFACE!=lo)
(Putting this line in /etc/init/smbd.conf also works of course.)
Why can't this line be included in the standard smbd.conf
By the way, this bug seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/951087
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/996968
Title:
Samba needs
Note that instead of editing /etc/init/smbd.conf (which can mess up
package upgrades), you can create a file named /etc/init/smbd.override
and put the line there. Works fine for me, and solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
2:4.1.6+dfsg-1ubuntu2 is in LTS, this bug should be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277432
Title:
Please update to samba 4.1.x from Debian/sid for trusty
To manage
By the way, this bug seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/951087
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996968
Title:
Samba needs to be stopped and
This bug is still present in 14.04 LTS. Putting the following line in
/etc/init/smbd.override solves it for me:
start on (local-filesystems and net-device-up IFACE!=lo)
(Putting this line in /etc/init/smbd.conf also works of course.)
Why can't this line be included in the standard smbd.conf
Note that instead of editing /etc/init/smbd.conf (which can mess up
package upgrades), you can create a file named /etc/init/smbd.override
and put the line there. Works fine for me, and solved the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have just encountered this while testing Kubuntu 14.04 Beta 2. (I
booted the amd64 ISO from a USB key, on an Intel-based EFI laptop.)
When started with a click on any audio file in Dolphin, Amarok crashes
upon start. When started from the command line (using Konsole), using
commands in the form
I have noticed this issue, too, on three different machines, all running
12.04.1 LTS. Two of them are Kubuntu desktops installed by me, one other
is an Ubuntu Server installed by my service provider.
Actually, /etc/apt/apt.conf.d/00aptitude is not the only surprising
file, there is also
I was affected by this bug too, using Ubuntu Server 12.04.1 LTS, with
openssh-server 1:5.9p1-5ubuntu1. Using the following command line solved
the issue:
sudo ssh-keygen -f /etc/ssh/ssh_host_ecdsa_key -N '' -t ecdsa
I think it is important to note the following:
-- I did not install Ubuntu
I was affected by this bug too, using Ubuntu Server 12.04.1 LTS, with
openssh-server 1:5.9p1-5ubuntu1. Using the following command line solved
the issue:
sudo ssh-keygen -f /etc/ssh/ssh_host_ecdsa_key -N '' -t ecdsa
I think it is important to note the following:
-- I did not install Ubuntu
Public bug reported:
kubuntu version: 12.04.1 LTS
amarok version: 2:2.5.0-0ubuntu6
phonon-backend-gstreamer version: 4:4.7.0really4.6.2-0ubuntu0.1
I set the playlist Track Progression to Standard. I expect playback to
go through the playlist and then stop when the end of the last song is
** Bug watch added: KDE Bug Tracking System #300884
https://bugs.kde.org/show_bug.cgi?id=300884
** Also affects: amarok via
https://bugs.kde.org/show_bug.cgi?id=300884
Importance: Unknown
Status: Unknown
** Description changed:
kubuntu version: 12.04.1 LTS
amarok version:
*** This bug is a duplicate of bug 858622 ***
https://bugs.launchpad.net/bugs/858622
** This bug has been marked a duplicate of bug 858622
package digikam-doc (not installed) failed to install/upgrade: trying to
overwrite '/usr/share/doc/kde/HTML/en/digikam/index.cache.bz2', which is also
At least with aptitude, after the install failure, the package remains
in a to be installed state, which means all further install/updates
will end with a failure status because of this package. (Thankfully,
other packages still install successfully, but the overall state of the
install/upgrade
I'm still learning about the Ubuntu processes, so I may be wrong, but it
seems to me that this version update falls squarely under the
FeatureFreeze for bugfix-only updates section of the page you linked
to, and therefore does not require an exception request.
I have diffed the Unison source
Looking at the build log, I understood why the /usr/share/doc/unison
/unison-manual.txt file is empty. It is quite simply generated from the
output of unison -doc all. The core issue is that this command does
not output anything.
...
I think I found the root cause of the issue. The Unison
The bug is still present in Precise beta 2.
I noticed the /usr/share/doc/unison/unison-manual.txt file is empty (one
single 0x0a character), while it is rather big in previous versions
(/usr/share/doc/unison2.32.52/unison-manual.txt.gz is 66419 bytes,
inflating to 216202 bytes uncompressed).
I
Public bug reported:
Ubuntu release: Kubuntu 12.04 LTS Precise Pangolin - Beta i386
Package version: 2.40.63-2ubuntu1
Most likely, this does not depend on the Ubuntu flavor being used or the
front-end used to install Unison, but just in case, here is what I did
this morning:
* Boot Kubuntu
** Attachment added: Montage of output from three versions of unison
https://bugs.launchpad.net/bugs/949895/+attachment/2834057/+files/unison-2.40-missing-doc.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: precise regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949895
Title:
Unison 2.40 doc is missing
To manage notifications about this bug go to:
Unison 2.40.63-2 has been uploaded to Debian testing. What needs to
happen to include it in Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769479
Title:
Unison version not up-to-date
To
Version 2.40.x is a major release, as can be seen in the ChangeLog:
http://www.cis.upenn.edu/~bcpierce/unison/download/releases/stable
/unison-manual.html#news (scroll down to Changes since 2.32).
Notably, from my point of view as a regular Unison user:
* Unicode support, necessary for proper
74 matches
Mail list logo
