Public bug reported:
In the K3b settings, CDDB would not work. I was able to get it to work
by installing kdemultimedia and kio-audiocd. I'm not sure which package
provides the needed capability, but I think at least one of these should
be added to the dependencies for K3b, maybe as a
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
I think we are off on the wrong track. This is fundamentally a CVE
against Insyde Software BIOS and possibly other vendors. Any attacker
with kernel mode access could do the same thing, regardless of Linux
install. I am not sure, but it is possible someone with admin access to
Windows could
Can anyone confirm whether this only happens with laptops with Insyde
Software based BIOS? Or does it effect BIOS derived from AMI/Pheonix?
My Dell had Insyde Software BIOS instead of normal Dell AMI based BIOS
seen on business class laptops/desktops.
--
You received this bug notification
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
I also have this issue with a PyQt application I have written (A guitar
synthesiser). As well as the window becoming really large (and causing
compiz/unity to crash) as soon as the application is started, X begins
to use 100% of CPU.
--
You received this bug notification because you are a member
Hola Fran, actually, it;s a big deal, support and service with Linux is
very intense.
Allen
On Fri, Sep 26, 2008 at 11:14 PM, Fran McLoughlin
[EMAIL PROTECTED]wrote:
Here we go - Tiger Direct Canada doing it's bit to endorse Linux...
I know its not much but here is a company willing
