Public bug reported:
When installing libvirt-dev, it is not possible to use -lvirt-lxc, as
that symlink is not installed.
The symlink /usr/lib/liblxc-qemu.so is properly installed, it's just the
lxc that's missing.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
I'm not confident yet we're seeing the exact same problem, but it is
pretty close. We're running a somewhat wide range of hyperisor kernels,
these are our observations so far.
node-1-1 3.13.0-24-generic is affected for 0% of vms
node-1-3 3.13.0-24-generic is affected for 0% of vms
node-1-5
Note that my list of affected nodes also include migrated VMs, so there
are some false positives (VMs that came from an affected node). The
affected VMs on node 1-8 all seem to be migrated from another node.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
We haven't been able to reproduce the issues under lab conditions, and
I'm not willing to use our production setup as a guinypig anymore. These
issues have cost me too much credibility already.
We believe #1326367 is causing this, as we've bisected this issue to be
between 3.13.0-27.50 and
We've resolved our issues by disabling KSM on the affected nodes. All of
the non-affected nodes didn't have KSM enabled (due to a packaging bug
elsewhere). After disabling KSM, our problems went away gradually in ~3
days.
This means we're no longer affected by this issue (and given the other
Just saw an identical error in the current daily quantal build.
Steps to reproduce:
- download current daily build for ubuntu desktop amd64 pc. (01-Sep-2012 08:38)
- Create a virtualbox configuration (use defaults for ubuntu64)
- Attach iso
- Boot VM
- choose 'install ubuntu'.
--
You received
Public bug reported:
Simply starting thg causes the issue, even after rm -rf
~/.config/TortoiseHg
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: tortoisehg 2.8-1
ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
Uname: Linux 3.11.0-9-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
** Also affects: python-qt4 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234566
Title:
thg crashed with SIGSEGV in QMetaObject::methodOffset()
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980031
Title:
crash after typing two letter in the 'alt'- osd
To manage notifications about this bug go to:
** Bug watch added: SourceForge.net Tracker #3514402
http://sourceforge.net/support/tracker.php?aid=3514402
** Also affects: remmina via
http://sourceforge.net/support/tracker.php?aid=3514402
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Public bug reported:
Python-keystoneclient uses python-requests, but the current keystoneclient
(1:0.2.2-0ubuntu1) is incompatible with requests (1.1.0-1), as explained in bug
#1116740.
An upgrade to a more recent python-keystoneclient would fix this.
Symptoms:
File
Version 1:0.2.2.28.gff24716+git201302071635~raring-0ubuntu1 from grizzly
ppa 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/1122146
Title:
python-keystoneclient conflicts with
I've tested remmina 1.0.0-1ubuntu6dupondje5.
Clipboard sync works, but is not 100% reliable. I've seen one crash
(when pasting), and a few instances where the clipboard isn't synced.
Unfortunately I haven't been able to reproduce the crash with gdb attached.
I'll start using remmina again for my
Dupondje released a new version ( 1.0.0-1ubuntu6dupondje6), which solved
the crashes i had with 1.0.0-1ubuntu6dupondje5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937522
Title:
rdp clipboard
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078947
Title:
auth_token failure if signing_dir not specified running under
More details here.
http://www.mail-archive.com/openstack@lists.launchpad.net/msg16973.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057322
Title:
Image fails to upload to swift: TypeError:
I agree that fixing a bug by introducing several new ones is not a good
idea, especially if these are worse than the original problem.
However, I disagree that not fixing this bug is the way to go. Earlier
on, adding an object expiry to the container schema was deemed too
complex. These new
grub2 is the messenger, it might not be the cause.
** Package changed: ubuntu = grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973095
Title:
GRUB error: out of partition after a
Affects me as well. I have the following layout:
sda (HDD):
/dev/sda1* 100G ext4 (unused)
/dev/sda2 10G swap
/dev/sda4 100G ext4 /
/dev/sda3 Extended
/dev/sda5 500G ext4 /home
sdb (SSD):
/dev/sdb1 6G swap
/dev/sdb2* 2G /boot
(*=partition marked bootable)
Grub is installed on /dev/sda and
There was an IO error with your memory card, most likely due to harware failure.
Could you try to boot from it again, and choose 'verify' in the boot menu? (and
of course share the results)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
From Debian maintainers guide, chapter 4:
Recommends: Use this for packages that are not strictly necessary but are
typically used with your program. When a user installs your program, all
front-ends will probably prompt them to install the recommended packages.
aptitude and apt-get install
** Changed in: quickly (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/979692
Title:
python-support should be replaced with dh_python2
To manage notifications
** Changed in: remmina
Importance: Undecided = Unknown
** Changed in: remmina
Status: New = Unknown
** Changed in: remmina
Remote watch: None = Debian Bug tracker #659755
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have installed 1.0.0-1ubuntu6.1. I've worked through the crash scenarios
mentioned earlier, and I can not reproduce any of them.
Copying text (the primary use case) works fine in both directions.
Copying files doesn't work, but it never has, so that's not a regression.
--
You received this
libvirt-lxc was introduced in raring, and the dev-symlink is missing in
saucy and raring.
In saucy: http://packages.ubuntu.com/saucy/amd64/libvirt-dev/filelist
In saucy-updates:
http://packages.ubuntu.com/saucy-updates/amd64/libvirt-dev/filelist
In raring:
Public bug reported:
When installing libvirt-dev, it is not possible to use -lvirt-lxc, as
that symlink is not installed.
The symlink /usr/lib/liblxc-qemu.so is properly installed, it's just the
lxc that's missing.
** Affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
I'm seeing the same symptoms:
I created an image using 14.10 (fully updated) amd64 desktop
Target iso was 14.04.1 i386 desktop.
The 'live' workaround worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just successfully booted my new zenbook with this mainline kernel.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/
This suggests this fix (or a fix anyway) has been merged into the stable kernel.
The default 14.04 kernel is still broken, though.
--
You received this bug
I'm not confident yet we're seeing the exact same problem, but it is
pretty close. We're running a somewhat wide range of hyperisor kernels,
these are our observations so far.
node-1-1 3.13.0-24-generic is affected for 0% of vms
node-1-3 3.13.0-24-generic is affected for 0% of vms
node-1-5
Note that my list of affected nodes also include migrated VMs, so there
are some false positives (VMs that came from an affected node). The
affected VMs on node 1-8 all seem to be migrated from another node.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This fix seems to trigger problems with virtualization LP #1307473.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326367
Title:
exploitable futex vulnerability
To manage notifications about this
We haven't been able to reproduce the issues under lab conditions, and
I'm not willing to use our production setup as a guinypig anymore. These
issues have cost me too much credibility already.
We believe #1326367 is causing this, as we've bisected this issue to be
between 3.13.0-27.50 and
We've resolved our issues by disabling KSM on the affected nodes. All of
the non-affected nodes didn't have KSM enabled (due to a packaging bug
elsewhere). After disabling KSM, our problems went away gradually in ~3
days.
This means we're no longer affected by this issue (and given the other
Workaround:
WEBKIT_DISABLE_COMPOSITING_MODE=1 surf https://google.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850650
Title:
webkit-gtk crash on nvdia closed-source driver
To manage
Public bug reported:
When I start "surf https://www.google.com; surf reports a webkit crash:
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 264 error_code 2 request_code 152 (GLX) minor_code 34)
(Note to
Ubuntu is currently shipping a broken version (0.8.04). That's the bug
being reported.
This LP bugtracker tracks both duplicity and it's ubuntu packaging,
right?
On Thu, Jan 2, 2020 at 1:30 PM Kenneth Loafman
wrote:
> This bug was fixed in rev 1344, current rev is 1533.
>
> It looks like a
Public bug reported:
The webdav backend calls base64.encodestring, which (counterintuitively)
expects a bytes input in python3.
# duplicity incremental \
--asynchronous-upload \
--full-if-older-than 1M \
-v 9 \
--exclude='./Documents/google_drive/**' \
--include='./src/**' \
37 matches
Mail list logo
