Further, even the ppa suggested here doesn't have support for oneiric.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/723796
Title:
Enable spice in kvm
To manage notifications abo
Doesn't "fix released" imply that it's fixed in a released version of
qemu-kvm in Ubuntu? That's not the case today.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/723796
Title:
En
Is this an Ubuntu bug? Is there a configuration problem in Ubuntu?
Upstart problem? Or is it an upstream issue? This has been kicking
around for over 5 years now.
How does the workaround in post #25 work? It seems like that would start
autofs as soon as any network device comes up, when what you'd
Still hitting this bug under natty as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/40189
Title:
autofs needs to be restarted to pick up some shares
--
Ubuntu-server-bugs ma
Workaround not working here:
t...@katran:~$ cat /proc/cmdline
root=UUID=af655e0f-6e77-4305-8c6d-5a92ef317d3e ro acpi_enforce_resources=lax
splash
t...@katran:~$ dmesg
...
...
[368848.890310] i801_smbus :00:1f.3: PCI INT B -> GSI 19 (level, low) ->
IRQ 19
[368848.890317] ACPI: I/O resource
Hrm, nevermind, after adding the lax option, sensors-detect found a
module to load. Odd.
--
lm-sensors don't work
https://bugs.launchpad.net/bugs/478762
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lm-sensors in ubuntu.
--
Ubuntu-serv
That's a work-around... but the warning would seem to suggest that this
isn't safe. Is there an API/ABI/socket/sysfile that we're supposed to
used? Until that's the case, this is a regression. Given that, and that
people might be using this to tell if a system is running at a safe
temperature, this
Hypothetically, what's the right way to get temperature data if the
module isn't supposed to be used anymore? Is it safe to use LAX here?
** Changed in: lm-sensors (Ubuntu)
Status: Incomplete => Confirmed
--
lm-sensors don't work
https://bugs.launchpad.net/bugs/478762
You received this bu
Has anybody gotten these patches to apply to karmic's openssh? I've been
trying to build a package for this, but so far no luck applying the
patch.
--
openssh: want hpn-ssh for 20x speed improvement!
https://bugs.launchpad.net/bugs/162253
You received this bug notification because you are a membe
For lack of a functioning driver, all sensors reports:
t...@katran:~$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1: +60.0°C (crit = +255.0°C)
t...@katran:~$
temp1 always reads 60, whereas the temperature that was read with other
drivers pre-karmic always varied
To be clear, sensors-detect worked under hardy through jaunty.
** Also affects: lm-sensors (Ubuntu)
Importance: Undecided
Status: New
--
Can't read temperature with i2c_i801 anymore
https://bugs.launchpad.net/bugs/481510
You received this bug notification because you are a member of Ub
11 matches
Mail list logo
