This debdiff contains the patch for trusty. I have tested it, built it
in a ppa and run autopkgtest, and things look fine to me.
** Patch added: "sysvinit debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1827172/+attachment/5260712/+files/lp1827172_trusty.debdiff
I have developed a patch which I believe fixes the problem.
https://paste.ubuntu.com/p/QRw4XTkXkV/
** Description changed:
[Impact]
* update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.
- * update-rc.d incorrectly modifies symlinks when enabling or disabling
-
Please:
1. Reproduce the problem. Wait a minute or two and then turn the power
off.
2. Turn the power on again.
3. Run this command:
journalctl -b-1 > prevboot.txt
and then send us the resulting file 'prevboot.txt'.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => New
--
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/1805077
Title:
[ASUS X555YI] the audio pause and
** Tags added: autofs
--
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/1827286
Title:
autofs - "Too many levels of symbolic links" after apt upgrade
Status in systemd
Public bug reported:
Description:Ubuntu 16.04.6 LTS
Release:16.04
I moved to autofs this week as a workaround for Bug #1577575 failing to
mount NFS entries at boot. This worked file until I ran 'apt upgrade'
today.
Now trying to access /vol/home mount results in the following error:
Adding new autopkgtests in devel series - good.
Adding new autopkgtests in stable series - not good.
Fixing regressions that got introduced during the lifetime of a stable
series - good.
The only times when we introduced new autopkgtests in stable series, is
when we upload fixes for regressions
Quick update - switched to autofs as a workaround for this 16.04 issue.
That was fine until I ran 'apt upgrade' today. Now I get the following
error:
root@chi:~# ls -la /vol/home/
ls: cannot access '/vol/home/': Too many levels of symbolic links
root@chi:~#
I'll be opening a new bug for
This bug was fixed in the package cups - 2.2.10-6ubuntu1
---
cups (2.2.10-6ubuntu1) eoan; urgency=medium
* d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)
-- Victor Tapia Wed, 24 Apr 2019 17:04:55
+0200
** Changed in: cups
Public bug reported:
Since upgrading to 1.1ubuntu1.18.04.9 on several servers (VMs) unattended
upgrades stopped to run successfully an did not report any errors (via mail).
If I run it manually it errors out as follows:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade",
zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which
states:
* [92175749] Revert "Switch from the deprecated libpcre3 to the newer
(!) libpcre2." libpcre2 is not a drop-in replacement and not detected
by zsh's configure script. (Closes: #909084, reopens LP#1792544)
Thanks for the update, I missed that comment (again). I guess it can be
moved back to "triaged" then.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:
“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this
Seeing the same issue on 18.04.2LTS Aarch64. How can I get arround it?
Commercial software.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to readline6 in Ubuntu.
https://bugs.launchpad.net/bugs/1805040
Title:
Apparently
> > Reassigning to the kernel
>
> please don't. This is a bug in systemd
with that said - that we believe this should stay open against systemd
so end users can configure ondemand - there certainly may also be a bug
in the kernel causing the slowness; if anyone (@lathiat?) has found
that's the
costales writes:
> Would this hack fix the issue? (Add/Remove xhost +si:localuser:root to the
> launcher)
> I don't know if this could means something dangerous in Wayland.
I'm not sure if it will fix things run as root via pkexec but it will if
you manually run gui programs as root. There's
Public bug reported:
Apache Module mod_brotli
Description:Compress content via Brotli before it is delivered to the client
Status: Extension
Module Identifier: brotli_module
Source File:mod_brotli.c
Compatibility: Available in version 2.4.26 and later.
See
** Merge proposal linked:
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/366779
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1827253
Regarding apache2, https://bz.apache.org/bugzilla/show_bug.cgi?id=57471
is still open, and I just tried a 2.4.38 build with pcre2, and it
doesn't work. Switching the task back to incomplete according to the bug
instructions.
** Changed in: apache2 (Ubuntu)
Status: Triaged => Incomplete
--
yparitcher, thank you for the upstream bug report. As soon as upstream
finds a (backportable) solution we will add it to this SRU and report
back here.
** Changed in: modemmanager (Ubuntu Bionic)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a
On Wed, May 01, 2019 at 05:25:22PM -, Robie Basak wrote:
> Will this also need addressing in the development release?
It looks like it to me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Public bug reported:
Issue description:
Enabling the rsyslog (disabled by default) Apparmor profile causes
rsyslog to fail to start when running *inside a container*.
Steps to reproduce:
1) Create a 'eoan' container called rs1 here:
lxc launch ubuntu-daily:e rs1
2) Enter the container
lxc
It is normally always preferable to use the intel-pstate driver compared
to pcc-cpufreq or acpi-cpufreq on modern Intel hardware.
Some HP ProLiant platforms implement the PCC interface [1] which can be
disabled by a BIOS setting in which case the PCC driver will not load
and the acpi-cpufreq
Will this also need addressing in the development release?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1825194
Title:
[SRU] resolvconf is racy, which leads to
> Setting the governor to performance 'fixes' it.
> I don't know if this is *this* issue or another one, so happy to open a new
> issue if you prefer.
we will be changing the built-in 'ondemand' systemd service (set-cpufreq
script, technically) to allow end-user configuration instead of using
> Reassigning to the kernel
please don't. This is a bug in systemd because its set-cpufreq script
provides no way for the user to override its hardcoded values of what
governor it select. We will be providing a systemd patch to add user
configurability.
** Package changed: linux (Ubuntu) =>
You have been subscribed to a public bug:
Whilst debugging 'slow instance performance' on a Ubuntu Bionic based
cloud, I observed that the default cpu governor configuration was set to
'powersave'; toggling this to 'performance' (while in not anyway a
particularly green thing todo) resulted in
Based on the analysis in the log, there does not appear to be a bug in
systemd - which is behaving as intended, and defaulting to the best
available cpufreq governor for low power consumption - but there may be
a bug in the kernel resulting in the wrong scaling driver being used on
the hardware in
** Tags added: cosmic disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1631246
Title:
package kaccounts-providers (not installed) failed to install/upgrade:
The last outstanding open task for sysvinit/xenial is also invalid, to
my understanding. Both /etc/init.d/ondemand in <= xenial and
/lib/systemd/set-cpufreq in >= bionic implement the intended default
policy of interactive/ondemand/powersave, not performance.
** Changed in: sysvinit (Ubuntu
Balint, can you comment here on the unattended-upgrades autoremoval
behavior? I think the intended behavior is only to remove packages that
have newly become unused as part of an upgrade, is that correct?
** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
Thanks Robie, that's a very good point and something I didn't notice
while sponsoring. Alfonso, do you want to adjust the patch to address
this? (That will also give us a chance to reupload the SRU and remove
the misapplied diff cruft.)
--
You received this bug notification because you are a
> Please don't mischaracterise my position like this
That's why I specifically said:
"Please correct me if I'm mischaracterizing your argument"
I read your email, and that was truly the position that I took from it.
If I'm misunderstood it, as I said, please correct me.
> I find it upsetting,
Public bug reported:
Lors de la déonnection de l'ordinteur, l'ordinateur ne s'éteint pas et
reste figé sur les points sous le logo Ubuntu
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux
On Wed, May 01, 2019 at 02:10:52PM -, Dan Streetman wrote:
> Can you explain in more detail why you believe it's better to leave
> broken autopkgtests broken?
Please don't mischaracterise my position like this. I find it upsetting,
disrespectful and unconstructive. For an example of how this
Public bug reported:
Upgrading from 14.04 to 16.04 got the error at install time and then
after restart
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: upower 0.99.4-2ubuntu0.3
ProcVersionSignature: Ubuntu 4.4.0-147.173-generic 4.4.177
Uname: Linux 4.4.0-147-generic i686
ApportVersion:
Same just happened to me on Ubuntu 18.10 after console-setup-linux was
updated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1787879
Title:
kbd_mode resets on
I was asking about how the points raised in the mailing list thread
specifically apply to this particular case.
It sounds like you object more in principle to the general points
raised. In that case I suggest you participate in the thread in
ubuntu-release@ instead, so we don't silo that
description updated to explain the problem.
** Description changed:
[impact]
both the 'gnupg' and 'gnupg2' sources build 'gpgv-udeb' for xenial.
+
+ therefore, gnupg FTUFS since its version is < gnupg2 version.
[test case]
attempt to upload 'gnupg' and 'gnupg2' into a PPA.
+
Review question: what ensures that /run/resolvconf exists before flock
is called? I only see an "mkdir -p" inside the block, not outside it.
flock doesn't seem to create parent directories automatically in my
test, and I don't see a tmpfiles.d entry.
--
You received this bug notification because
What's the actual impact please? What you've written describes the
problem but I don't understand how this is a problem for users from that
description.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
Thank you for working on improving our test suites.
This upload is only to fix dep8 tests, right? If so, please could you
assess this against the concerns raised in the thread here:
https://lists.ubuntu.com/archives/ubuntu-release/2018-March/004352.html
? It seems to me that this upload falls on
Hello Toru, or anyone else affected,
Accepted pam into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/pam/1.1.8-3.2ubuntu2.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: ubuntu-themes (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1740709
Title:
GtkSpinButton's '+' changes
** Tags added: id-5cc7cd7240bb30199b95cc32
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gzip in Ubuntu.
https://bugs.launchpad.net/bugs/1825350
Title:
[19.10 FEAT] gzip compression improvements
Status in Ubuntu on IBM
** Tags added: id-5cc72cfe22e00d7a830c4ce4
--
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/1671951
Title:
networkd should allow configuring IPV6 MTU
Status in cloud-init
Sponsored for 'Eoan'. Let's start the SRU once cups land in eoan-
releases (Fix Released).
Thanks Victor !
- Eric
** Changed in: cups (Ubuntu Eoan)
Status: In Progress => Fix Committed
** Changed in: cups (Ubuntu Disco)
Status: New => In Progress
** Changed in: cups (Ubuntu
This bug happens dozens of times a day after I upgrade to ubuntu19.04.
Please do not let this bug to expire.
--
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/1805077
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hi,
Would this hack fix the issue? (Add/Remove xhost +si:localuser:root to the
launcher)
I don't know if this could means something dangerous in Wayland.
https://bazaar.launchpad.net/~costales/gui-ufw/wayland/revision/19
Thanks in advance.
--
You received this bug notification because you
+1 @teo1978 (teo8976)
Users will decide. The most radical solution would be purging the whole
GNOME desktop and install MATE DE instead. I switched to MATE in 2013
and I'm completely happy with it.
In MATE the Caja file-manager (fork of Nautilus) has normal search even in
19.04. Also it has
March 2019 may mean the problem started with the released of:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.2
But maybe not. Some other package (like the kernel) might also have
changed around then. To test this theory, please try installing the
previous version *.deb files
Public bug reported:
When I start my computer (running Ubuntu 18.04.2 LTS), there is no sound
from the speakers plugged into the line-out jack.
In order to get sound, I need to run the following sequence of commands:
sudo apt-get update && sudo apt-get upgrade
sudo apt-get remove --purge
regression submitted upstream see
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
for further details
** Bug watch added: gitlab.freedesktop.org/mobile-broadband/ModemManager/issues
#119
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119
--
You
55 matches
Mail list logo
