This bug was fixed in the package libvirt - 0.7.5-5ubuntu7
---
libvirt (0.7.5-5ubuntu7) lucid; urgency=low
* debian/patches/0010-Use-base-16-for-product-vendor.patch: parse the USB
and PCI product and vendor ids in hexadecimal. This fixes incorrect
USB ids being used in virt
This is actually a libvirt bug.
** Package changed: virt-manager (Ubuntu) => libvirt (Ubuntu)
--
USB passthrough device ID interpreted as decimal instead of hex
https://bugs.launchpad.net/bugs/514610
You received this bug notification because you are a member of Ubuntu
Server Team, which is subs
You have been subscribed to a public bug:
Binary package hint: virt-manager
In 10.04, at least, when adding a device, the second half of lsusb's output is
interpreted as decimal, when it is in fact hexidecimal.
As a result, to make a USB passthrough device work, I had to edit the XML file
from
Bump, I'm having this problem in 9.10 as well :( .. Will 3.4.2 be in
9.10 or should I just go and get the samba source? PPA?
--
smbclient fails with SMBecho failed. Maybe server has closed the connection
https://bugs.launchpad.net/bugs/445595
You received this bug notification because you are a
Public bug reported:
libopie.a exports the functions md5_init, md5_append and md5_finish.
These are quite common names that should be avoided by a central
library. The problem arises when any binary that also uses these symbol
names is linked to libopie.a, especially when this happens indirectly.
Hi,
On Fri, Feb 05, 2010 at 05:18:48PM -, Saku Ytti wrote:
>
> Configuration file is located in /var/lib/ntp/ntp.conf.dhcp
Which component/process is generating this configuration file?
status incomplete
priority low
--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com
** Changed
The bug is regarding SDL implementation, SDL report keydown on first time
caps-lock press and keyup only the second time caps-lock press.
Qemu upstream use this "wrong behavior" and generate up event for caps-lock
(it's work fine in Fedora and RHEL).
Attach patch for Ubuntu (tested on Ubuntu 9.1
Another side-affect of this is, that after installing winbindd, samba
tries to authenticate every connecting user though winbind, which
effectively renders security=share nonfunctional.
It took quite some time to debug what’s wrong with samba, so installing
wine shouldn’t break samba-shares!
--
I am still having this problem. In my latest system updates, I got the
same failure. I then tried to complete uninstall samba-common and samba-
common-bin. The uninstall failed with the same error, as listed above.
update-alternatives: error: /var/lib/dpkg/alternatives/nmblookup
corrupt: invalid s
I just checked the code about this --part thingy.
I think it needs some rewrite, regarding syntax etc.
If I have the time, I'll come up with something
--
lacks ext4 support
https://bugs.launchpad.net/bugs/494804
You received this bug notification because you are a member of Ubuntu
Server Team, w
Got it. The changelog says 3.0.3 (2008-09-28) added support for the
IT8720F.
I installed version 3.1.2 from debian unstable and it correctly
identified the IT8720F.
Thanks for your help.
--
IT8720F chip not recognized by lm-sensors
https://bugs.launchpad.net/bugs/518211
You received this bug no
*** This bug is a duplicate of bug 512096 ***
https://bugs.launchpad.net/bugs/512096
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 512096, so it is being marked as such. Please look at
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38858207/Dependencies.txt
** Attachment added: "VarLogDistupgradeAptlog.gz"
http://launchpadlibrarian.net/38858208/VarLogDistupgradeAptlog.gz
** Attachment added: "VarLogDistupgradeApttermlog.gz"
http://launchpadlibra
Public bug reported:
Binary package hint: clamav
Failed tu install package clamav/freshclam, failed to repair, failed to remove.
No one of these opearion fished always I receivet the signal that error 1 or
error 2 stopped the execution of the operation.
ProblemType: Package
Architecture: amd64
>From lm-sensors releases page (http://dl.lm-sensors.org/lm-sensors/releases/) :
- karmic version is pretty old (3.0.2, 2008-05-08) and doesn't know about 0x8720
- last release of lm-sensors (3.1.2, 2010-02-02) can detect 0x8720
debian testing & unstable have lm-sensors 3.1.1 (2009-06-21), which sh
You have been subscribed to a public bug:
This may be related to Bug #357766 -- which was fixed in Jaunty.
The problem shows up when running sensors-detect:
Trying family `ITE'... Yes
Found unknown chip with ID 0x8720
In short, it doesn't recognize the chip
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38855221/Dependencies.txt
--
CURLOPT_WRITEHEADER fails
https://bugs.launchpad.net/bugs/518355
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ub
Public bug reported:
Binary package hint: php5
A bug in PHP 5.2.9 and 5.2.10 causes curl_setopt($ch, CURLOPT_WRITEHEADER,
$fp_header)
to issue a warning:
Warning: curl_setopt(): the provided file handle is not writable in
/curl.php on line x
A fix is available in the PHP CVS: http://bugs.ph
Public bug reported:
Binary package hint: kvm
I'm running a handful of Jaunty systems and this bug appears in kvm 1:84
+dfsg-0ubuntu12.4
Host:
$ lsb_release -rd
Description:Ubuntu 9.04
Release:9.04
$
Description of bug:
If you start a FreeBSD 8.0 guest with "-serial
telnet:127.0.0
I have now built and tested several maven projects under all of my three
systems: karmic production, minimal karmic schroot and lucid schroot.
All of them worked exactly as expected. As far as I am concerned, the
latest maven2 distributions are acceptable. My evidence suggests that
the original bu
20 matches
Mail list logo
