I can confirm that the package from eoan fixes the xpresent
compatibility error with marco/compton on 18.04 (and consequently
compositing actually works).
I hope this qualifies as a potential SRU for 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Summary changed:
- virt-make-fs fails with: "libguestfs: error: tar_in: write error on
directory: /:"
+ Missing /bin/sh (dash) in supermin appliance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
As stated in the upstream report, the bug is really caused by /bin/sh
missing in the supermin appliance. This was fixed upstream in
https://github.com/libguestfs/libguestfs/commit/0cca7f9061455d29a7f893e715028cd3e75c19fd
and downstream in Debian in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug
I can confirm that trusty + linux-generic-lts-xenial from -proposed
looks good. I can now run sbuild with a tmpfs overlay, with
4.4.0-36-generic debconf would die with ESTALE during chroot setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
4.2.0-42 was built without CONFIG_MODULE_SIG_UEFI so the kernel ignores
the SecureBoot certificates and the user certificates enrolled as MOKs
for module signature validation, forcing the user to either disable
validation in shim through mokutil or disabling SecureB
Public bug reported:
4.2.0-42 was built without CONFIG_MODULE_SIG_UEFI so the kernel ignores
the SecureBoot certificates and the user certificates enrolled as MOKs
for module signature validation, forcing the user to either disable
validation in shim through mokutil or disabling SecureBoot altoget
> Can you see if this solves the issue on your computers?
No luck here (Xubuntu 14.04), what actually did fix the issue was
installing the latest stable release of lightdm-gtk-indicator from the
upstream ppa. This caused a few hiccups with the Greybird theme, but at
least the ghost sessions are go
It looks like that nobody is actually issuing the indicator-services-end
upstart signal, so the stop events of *all* indicators for lightdm
sessions never get fired. The other indicators just die because the
session bus disappears under their feet, but indicator-sound-service
keeps hanging around (
I don't have a KVM-capable machine with Wily ready at hand, sorry. I'll
try to get one ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393842
Title:
libvirt does not grant qemu-guest-agent chan
I'm getting the same build errors on 14.04 systems with the vivid HWE.
Coupled with lp:1433411, this makes impossible running OpenAFS on
machines which require post-3.2 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
(I meant post-3.13 kernels in the previous comment, sorry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476607
Title:
openafs-modules-dkms 1.6.7-1ubuntu1: openafs kernel module failed to
build
Hi Serge,
at first glance the libvirt version in -proposed works when the profile
is generated, but virt-aa-helper chokes on profile updates (e.g. media
change via virt-manager):
virt-aa-helper: error:
/var/lib/libvirt/qemu/channel/target/guineapig.org.qemu.guest_agent.0
virt-aa-helper: error: s
Could this please be nominated for a 14.04.3 SRU instead of being pushed
to the next point release? Using the current point release/vivid HWE
makes union-type=overlayfs completely unusable (which is a regression
from the previous point release/utopic HWE).
--
You received this bug notification be
The issue is present in the trusty version as well and it's a regression after
the last round of updates.
Since I can't pinpoint the exact package, I attached an extract of dpkg.log
showing the MATE-related packages which were updated.
** Attachment added: "dpkg.log"
https://bugs.launchpad.n
Reassigning to sysvinit to keep it in sync with the upstream issue.
Also, it makes more sense given that changes should happen in files shipped by
sysvinit-utils and sysv-rc.
** Package changed: systemd-shim (Debian) => sysvinit (Debian)
** Package changed: systemd-shim (Ubuntu) => sysvinit (Ubu
Public bug reported:
(forwarded from the relevant bug report raised in Debian BTS and adapted
for upstart as PID1)
Daemons which are not spawned via an upstart job (eg. those with
initscripts, ifupdown hooks and similar) are not detached from the
current logind session cgroups. This causes the se
I can confirm that software-properties 0.92.37.2 fixes the original
issue on trusty, leaving "verification-needed" as-is since I performed
only limited testing for the issue at hand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
@Tom:
I can just report that the package is in a "worksforme" status as far as the
issue is concerned, I'm in no way affiliated with Canonical or the SRU Team :-)
If at least another user could verify it and comment on the issue (per
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification ) thin
As far as software-properties is concerned, the issue is being tracked
in lp:1350291 (perhaps this issue should be marked as a duplicate of
that one for software-properties and Invalid for ubuntu-cloud-archive).
The updated package is in trusty-proposed and I can confirm it works, it
only needs ve
Right now, the only way of getting Juno on 14.04 is by using the old
manual method (eg. install ubuntu-cloud-keyring and create a listfile in
/etc/apt/sources.list.d).
I'd wait for the greenlight from Canonical, though: the last upload
happened two days ago, so the archive might still not be ready
Unfortunately, it appears that the culprit is the nvidia binary blob,
switching to nouveau made the system reboot without a hitch. I did a bit
of housekeeping on the bug and marked the nvidia binary driver as
affected.
Sorry for the line noise.
** Changed in: linux (Ubuntu)
Status: Incompl
Tested on 3.17-rc5-utopic as instructed, I observed the same behaviour:
all reset methods except writing to CF9 result in the system getting
stuck after the kernel issues the "Restarting System" message, then the
machine powers down suddenly.
Resetting via CF9 still results in disks going into eme
** Attachment added: "fwts test results"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371911/+attachment/4209689/+files/results.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371911
T
Public bug reported:
All reset methods on a fully updated L702X with BIOS A19 (latest available
release) fail except for the PCI reset through CF9.
This is a regression from the 12.04 LTS kernel, and other OSes (namely, Windows
7) can reboot without problems.
The problem with writing to CF9 is
I did a bit of sleuth work and traced the issue as far back as the version
shipped with quantal (2.34.8-0ubuntu4).
This should probably qualify as a regression, and the range is somewhat narrow
(the last unaffected version is 2.34.1-1ubuntu11, which is shipped in precise).
Can someone from the m
** Branch linked: lp:~ubuntu-desktop/metacity/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357634
Title:
Maximized window has line of white pixels on left
To manage notifications about thi
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274844
Title:
Signal processing broken on x86_64 with version 331.20
To manage notifications about this bug go to:
https://bugs
Possibly a duplicate of lp:1274844
Driver version 331.20 has a known bug which breaks signal processing entirely,
resulting in various abnormal behaviours.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
lsb_release -rd:
Description:Ubuntu 12.04.4 LTS
Release:12.04
Package version: 331.20-0ubuntu0.0.1
On precise with linux-generic-lts-raring signal processing is broken by the
latest available version (331.20).
This is a known bug fixed in upstream release 331.38
I second @jesse-pretorius' request: the upstart job definitely needs to
be backported to Precise once it hits Saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based int
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898739
Title:
Dangling symlinks for precat.1 and preunzip.1 manpages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
Public bug reported:
The packages mistakenly includes two dangling symlinks for precat.1 and
preunzip.1 manpages, both targeting prezip.1 (which does not exists and
it's not a member of the package).
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: aspell 0.60.6-6
ProcVersionSignature: Ubunt
Err, I meant bug #897156.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897153
Title:
xul-ext-calendar-timezones: Timezone Definitions for Mozilla Calendar
is incompatible with Thunderbird 8
To m
This looks like fallout from #897156 .
After applying the patch in said bugreport, xul-ext-calendar-timezones is
recognized as compatible with Thunderbird 8.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Hi
I just hit this regression with an instance of prestashop (segfault in
zend_object_store_get_object).
I'm currently testing the updated packages in security-proposed PPA and they
seem to work fine for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
35 matches
Mail list logo