** These bugs are fixed upstream in OpenSSH 4.9 and OpenSSL 0.9.8h **
You can apply the fix to OpenSSH 4.7 from Ubuntu just fine:
https://bugzilla.mindrot.org/attachment.cgi?id=1458 . It applies cleanly
except for two rejects at points where the changes have already been
applied, so the rejects
Quick instructions on rebuilding openssh and openssl to include the fix,
for those not used to patching Debian packages:
pre
mkdir wrk
cd wrk
sudo apt-get install build-essential fakeroot wget
sudo apt-get build-dep openssl openssh
apt-get source openssl openssh
cd openssl-0.9.8g
wget --quiet -O
That patch applies to openssl as shipped in Hardy, but doesn't appear to
have any effect. After patching openssl, rebuilding the packages and
installing them, `openssl engine padlock' reports:
(padlock) VIA PadLock (no-RNG, ACE)
on my C3 thin clients. That should get me at least accelerated
Confirmed: openssl is using x86 crypto even with -engine padlock, both
in latest upstream and in the current hardy packages.
If I interrupt a debug build of openssl while running openssl speed
aes-128-cbc -engnie padlock on a C3 gdb generally reports that it's
been interrupted in:
** These bugs are fixed upstream in OpenSSH 4.9 and OpenSSL 0.9.8h **
You can apply the fix to OpenSSH 4.7 from Ubuntu just fine:
https://bugzilla.mindrot.org/attachment.cgi?id=1458 . It applies cleanly
except for two rejects at points where the changes have already been
applied, so the rejects
Quick instructions on rebuilding openssh and openssl to include the fix,
for those not used to patching Debian packages:
pre
mkdir wrk
cd wrk
sudo apt-get install build-essential fakeroot wget
sudo apt-get build-dep openssl openssh
apt-get source openssl openssh
cd openssl-0.9.8g
wget --quiet -O
This performance regression is *exciting* when you run an LTSP thin
client network. The almost constant fsync() calls and resulting I/O
stalls cause users' GUIs to slow down or freeze fairly frequently.
I'm testing the update in -proposed now.
--
Firefox keeps forcing disk to spin up when
This performance regression is *exciting* when you run an LTSP thin
client network. The almost constant fsync() calls and resulting I/O
stalls cause users' GUIs to slow down or freeze fairly frequently.
I'm testing the update in -proposed now.
--
Firefox keeps forcing disk to spin up when
Possible fix:
Create the file /etc/modprobe.d/iwl4965:
options iwl4965 disable_hw_scan=1
--
iwl4965 unstable on Dell XPS M1330
https://bugs.launchpad.net/bugs/137565
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Create the file /etc/modprobe.d/iwl4965:
options iwl4965 disable_hw_scan=1
then unload and reload iwl4965. This may well help.
--
iwl4965 drops out from time to time (Santa Rosa)
https://bugs.launchpad.net/bugs/144621
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: linux-ubuntu-modules-2.6.22-14-generic
The iwl4965 driver (for Intel 802.11AGN products) may not function
correctly out of the box on some Gutsy RC1 systems, as the background
hardware scanning for networks appears to interfere with the normal
operation
I'm encountering an apparently similar issue with a Dell wireless
bluetooth mouse under the 7.10 rc 1 build. The same laptop and same
mouse worked fine with 7.04 (out of the box, in fact). The mouse does
not require a passkey.
If I try to use the GNOME bluetooth applet to enable the mouse (with
Please disregard the last comment; it's caused by a mixture of bad UI
and my misunderstanding.
I do think the UI isn't doing the right thing - it should pick a default
action based on class(es) provided by the device, not just try to use
obex to do file exchange. It also doesn't provide ANY
be possible to just scroll through the
font list and see what ones get complained about (again, to stderr).
--
Craig Ringer
--
Lohit Punjabi Regular font is broken (Can't enter text into textboxes)
https://launchpad.net/bugs/45565
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
The default font is determined via the app prefs. You'll find the
initial setting (for when no prefs yet exist) in the prefs loading code.
Search for scribus*.rc . (This is certainly correct for Scribus 1.3.x,
and I think it should be right for 1.2.x; I don't have 1.2.x code on
hand to check and
201 - 215 of 215 matches
Mail list logo
