Whatever was going on here, seems not to be the case with
6.8.0-54-generic, may also be that the modules-extra package was not
installed. In any case, this particular report can be closed for now,
fairly sure!.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Right; I can confirm FIXED with :-
linux-image-6.11.0-17-generic 6.11.0-17.17~24.04.2
ALSO I can confirm that fixes ANOTHER issue we were having with
inability to wake up from screen power-off on Thinkpad T490s .
My main concern is that all Ubuntu Desktop variants (official and
unof
** Description changed:
- Testing 6.8.0-53-generic (noble-proposed) on a Thinkpad t490s running
Cinnamon desktop causes X11 session crash when 'cheese' and
'gnome-sound-recorder' programs started. Similarly, they do not appear within
firefox and so-forth!.
+ Testing 6.8.0-53-generic (noble-pro
Public bug reported:
Testing 6.8.0-53-generic (noble-proposed) on a Thinkpad t490s running Cinnamon
desktop causes X11 session crash when 'cheese' and 'gnome-sound-recorder'
programs started. Similarly, they do not appear within firefox and so-forth!.
I've attempted to look for any xorg log err
This is confirmed and fixed upstream,
https://sourceforge.net/p/gscan2pdf/bugs/430/#0abb.
I concur, Ubuntu just need that tiny patch in their universe gscan2pdf package,
so it works on ubuntu and ubuntu derivatives.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I had noticed, on packages.ubuntu.com/thunderbird -- that the new
91.5 wasn't on all architectures, however it is now. Potentially I was
noticing what is still the case, that base versions of distro
focal,hirsute,impish have an old version in [ports] but an updated
single version in -updates on
Hrrm, I was about to test and then discovered package released already,
though can say all is good so-far. I notice ports (e.g. arm64) not all
getting new build... Hope situation is now improved for ongoing
updates, at least.
--
You received this bug notification because you are a member of Ubu
Debian now have 91.5.0-2 in sid and seem to have long since sorted the
portability/architecture issues.
@osomon -- Please let us all have a test-package for Ubuntu update testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Thunderbird (and Firefox-ESR) 91.4 has been released by Debian with no
problems, I believe either current or LTS or both had another package
updated in order to support these updates, though I can't seem to find
which it is now.
--
You received this bug notification because you are a member of Ub
Both debian and ubuntu seem to have some sort of problem with Thunderbird not
managing to build on all architectures, or so, in the latest versions in
packages. databases.
I notice launchpad has built 91.3.0 packages for ubuntu jamil (presumably
equivalent to debian sid or so)...
Do let us all k
For what its' worth, the Focal system's provided packages do not meet
the following build-deps of the *debian* Thunderbird 91.3.0 package;-
cbindgen (>= 0.19)
debhelper-compat (= 13)
libnspr4-dev (>= 2:4.32~)
libnss3-dev (>= 2:3.68~)
nodejs (>= 10.19.0)
Merely overriding the version dependencies
For what it is worth, this problem is now back -- very soon need the
Thunderbird 91.3 installed into Ubuntu as 78.x is about at EOL. Debian
have already prepared their packages in Sid (91.2.1 and 91.3.x no doubt
shortly to follow). They also offer firefox-esr and do similar work
with that packagi
virtualbox-dkms binary package comes from the same source package virtualbox.
See https://packages.ubuntu.com/source/focal-updates/virtualbox -- this is a
one-to-many mapping.
virtualbox-ext-pack and virtualbox-guest-additions-iso are separate.
In any case, al the 6.1.26 packages for 20.04 L
I can further confirm that this escl buggy driver affects other
scanners, e.g. Epson XP-830 just to name *one* but there are endless
Escl network printers/scanners these days.
Using the PPA:-
https://launchpad.net/~sane-project/+archive/ubuntu/sane-release
version 1.0.32 *does* work a lot better!.
** Changed in: thunderbird (Ubuntu Bionic)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895643
Title:
Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
To man
** Changed in: jsunit (Ubuntu Bionic)
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/1895643
Title:
Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
To manage notif
For those curious, focal unapproved-queue is here:-
https://launchpad.net/ubuntu/focal/+queue?queue_state=1
I notice on the linked ubuntu security team ppa, now is
78.7.1+build1-0ubuntu0.20.04.1 in fact...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Although in this bug, marked 'fix committed' for focal a while now, I can't
find the new thunderbird package in either focal-proposed nor focal-security .
Also not shown on https://launchpad.net/ubuntu/focal/+queue Any ideas?
-- be useful to see what package queues/links should be kno
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724872
Title:
nvidia-graphics-drivers-340 340.102-0ubunt
The pathway by which this error can occur, is installing package
"samba-common-bin" on focal20.04 with no previous samba installation ... --
although there is a /usr/lib/tmpfiles.d/samba.conf installed, the package
installer seems to end up creating the above error due to not having /run/samba
This seems to be related to important suggestion to merge packaging
efforts as best as possible:-
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1894090
...Not sure if merging-efforts will help with this specific bug, or
otherwise, Debian can be learned-from somehow-or-other!.
--
Yo
@Meluco I don't in any way think nvidia-340 likely to affect wifi, but test
your wifi on all the kernels, especially 5.4.0-62-generic and 5.8.0-38-generic.
Do hold down shift early at system startup to get in GRUB boot menu (exact
timing depends upon system), you should be able to get into "Adva
As per tjaalton's link -- new nvidia-340 in focal-proposed for 20.04 users:-
https://launchpad.net/bugs/1910709
Needs testing, especially for regressions for those still on Kernel 5.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
This appears to be imminent update-release for groovy and focal users, packages
available:-
https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages
Apparently, 'fix committed' in part, which presumably means focal-proposed
package now here:-
https://bugs.launchpad.net/ubuntu
@ihler [and same comment may apply to others...]
How have you ended up with -hwe kernel getting installed anyhow?
Default behaviour of particular install iso image? Because clicked some
option somewhere? Some sort of 'unintended/accident' and only later
found the consequence of k5.8 auto-insta
Also: For those stuck without Nvidia working on k5.8 -- simple short-
term thing to do, is hold down SHIFT at system startup (exact timing
depends upon system) to get to the GRUB boot-menu, and then select
"Advanced options for Ubuntu" (or thereabouts) submenu and then you
should be able to boot fr
For what its' worth, I built the nvidia-340_340.108-0ubuntu5 package
(includes patches to go up to kernel 5.9 apparently) on Focal20.04 --
just using the groovy-updates version and renumbering it back to
20.04.0test0 instead of a 20.10. version.
The full source and set of debs is here:-
https://w
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910709
Title:
DKMS linux-headers-5.8.0-34-generic update bro
I can confirm that there is not yet a new 'nvidia-340' in focal-proposed.
Looking at the changelogs this *should* be a very simple case of backporting
existing gutsy-updates source to focal just naming it .20.04.1 on the end
instead of 20.10.2, in short.
I think this needs to be done promptly a
I can confirm virtualbox-6.1.16-dfsg-6 packages (including -ext-pack and
-guest-additions-iso) seem to be working well, even succeeds in 'resuming' a VM
that was "saved" under 6.1.10 . Exercised many functions and having no issues
as-yet.
I tested against the focal-proposed kernel 5.4.0-61, ver
@koparebu -- You will need liblzf1 manually downloaded too in order to
manually download like that.
In any case, once manually installed, unless you went out of your way to 'pin'
or 'hold' the packages, apt/update-manager will happily "upgrade" them in
future if they are superseded by newer pa
@daniel-banobre-dopico
Can you confirm this affects the 'released' (focal-updates) kernel
5.8.0-36-generic (install linux-generic-hwe-20.04) ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1910709
@rivpelle
There are quite a lot of Audio-fixes in Kernel 5.4.0-59-generic which is coming
to 20.04LTS imminently, changelog here:-
https://paste.ubuntu.com/p/vdw94dvHTy/
Additionally, it seems from focal-proposed packages, linux-generic-
hwe-20.04 is about to cause install of 5.8.0-34-generic,
@illweckz
Please try to close the bug as it seems to apply only to unsupported ubuntu
versions and fixed on current LTS kernel (5.4).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813509
Title:
[i
Fwiw, this is likely to be such a common usability problem, LinuxMint decided
to provide more useful sane-airscan version directly in their repositories for
mint20.1 based open focal20.04.
https://github.com/linuxmint/linuxmint/issues/327
Since, Focal 20.04LTS does not have 'sane-airscan' packag
For what its' worth, the sane escl is buggy even in 1.0.29, installing 1.0.31
improves matters !.
Example bug/failure is here, but NOTE is not actually limited to the titled
printer:-
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1897962
--
You received this bug notification beca
For what its' worth -- r.e. groovy release..
libsane1 (1.0.31-2) seems to include libsane-escl listed normally in
dll.conf (i.e. likely a reasonable version of escl, better than focal
known-buggy version).
sane-airscan 0.99.15-1 is in gusty universe, so will require an SRU in
order to be chang
>From what I can tell, actually the escl buggy driver affects a wide range of
Brother, Canon, Epson, HP, Ricoh, Xerox, apple-protocol scanners ..,
although
Mick reported his specific scanner, indications from sane devs and from debian
bugs and other anecdotes suggest 'escl' 1.0.29 proble
I can confirm my specific failure was fixed with kernel 5.4.0-48 ...
Question for original reporter Dan -- is this issue (slow btrfs
scanning) still occuring for you? Now fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Just for completeness, Mick (original reporting on issue in different
forum) said:-
$ scanimage -L
device `escl:http://192.168.1.94:80' is a ESCL Brother DCP-J772DW flatbed
scanner
$ scanimage -T
Output format is not set, using pnm as a default.
Capability : [(null)]
Capability : [image/jpeg]
s
OK Turns out my btrfs+floppy bug is indeed a kernel floppy matter, and
the btrfs scan just 'triggers' the fault.
The new kernel floppy maintainer says:-
This patch should fix the problem:
263c61581a38 ("block/floppy: fix contended case in floppy_queue_rq()")
The commit id in stable tree is 29ed456
I can further confirm that taking out the btrfs scan in /usr/share
/initramfs-tools/scripts/local-premount/btrfs fixes the intermittent
boot issue for me. For me, this causes some deadlock between btfs scan
and floppy driver and requires reboot, not just slow!. This may be a
case of 'separate b
This issue, or variant thereof, has been observed on Ubuntu 20.04 and Linux
Mint 20.
I'm not 100% sure yet but it SEEMS to be affecting systems with a floppy drive.
Can end up with bootup-messages:-
[timestamp] Btrfs loaded, crc32c=crc32c-generic
Scanning for Btrfs filesystems
[timestamp] floppy
Oh, and to be clear, both said machines floppy working properly! Not
just faulty drive giving timeouts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460447
Title:
Boot slow, "scanning for btrfs f
*** This bug is a duplicate of bug 1876065 ***
https://bugs.launchpad.net/bugs/1876065
Have observed what appears to be this same bug, on a Dell Latitude D620
laptop!.
E.g. using a live-usb, Speakers do not work (though headphones plugged in 3.5mm
headphone-jack do!) until pulseaudio upda
FWIW, upstream just released *likely* final version 5.2.44:-
VirtualBox 5.2.44 (released July 14 2020)
This is a maintenance release. The following items were fixed and/or added:
API: Fix unintentionally enabled audio due to a settings file version dependent
bug
VBoxManage: Fix crash of 'VBoxM
Thankyou for helpful answer, from what I can see new-features are minor,
and there are likely to be many significant bugfixes ongoing that will
need including one way or another.
In any case, I note neither focal 3.0.1-0ubuntu1 package, nor
debian-unstable 3.0.2-1 package succeed in compiling
FWIW, Upstream and Debian-"unstable" have now released 3.0.2 ...
May be worth Updating now, in any-case keep an eye on upstream bug-fixes
ongoing...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18710
Bionic-proposed repository, now has Virtualbox 5.2.32 in there...
Can you confirm this fixes the above issue over the bionic 5.2.18 version?
If not, it may be possible (if hurry!) to get the community maintainer/updater
to fix that issue in proposed update as well.
--
You received this bug noti
I can confirm Virtualbox 5.2.32 working at least as well as 5.2.18, but
now builds on newer kernels. I note this also fixes some security
vulnerabilities.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
FWIW this seems to be the same as issue:-
https://forums.linuxmint.com/viewtopic.php?t=272956
Also known to affect MATE not just xfce ... Seems like issue in this
evdev<>libinput underpinning x.org infrastructure, likely?
--
You received this bug notification because you are a member of Ubuntu
Right -- systemd have just-now agreed to set the change in their upstream
systemd sysctl files :-
https://github.com/systemd/systemd/commit/6f130e85c76cfc2c58ba31f90d2ac3800866c1dd
I notice, however, that ubuntu's systemd pkg 'strips most those settings
out', in 18.04 currently only carrying the
It would appear that the path-of-least-resistance at present, is
systemd, poettering which is what is (for systemd-booters) where
fq_codel is getting turned-on in ubuntu.
This raises a wider-issue about bringing systemd-provided sysctl-
defaults into procps more widely [systemd has introduced many
FWIW: e2fsprogs PPA created and discussion of backports/updates should happen
on this linked-bug:-
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874 -- if you are
interested in xenial/older e2fsprogs compatibility please subscribe to that bug
#1365874 .
I also spotted e2fsprogs
Here is the PPA for all architectures, please test :-
https://launchpad.net/~ubuntu-iremonger/+archive/ubuntu/e2fsprogs-xenial
That is currently a backport of the version in bionic release itself,
but maintains the xenial mke2fs.conf defaults [creating filesystems
without 64bit,metadata_csum] for
Marc, Briefly just to let you know I'm working on a PPA for bionic e2fsprogs
backport to xenial, will update when thats' ready. Turns out that:-
(a) Ubuntu devs are rather tied-up fixing bionic18.04 bugs, and
(b) to do a good SRU would need much regression-testing and somebody to push it
forwar
@ahasenack
Andreas, your linked-bug has supposedly been fixed, can you check this autofs
bug has therefore also been fixed and comment-further or close again...? Be
good to get this sorted-out before 18.04.1, with thanks!.
--
You received this bug notification because you are a member of Ubunt
Launchpad issue link didn't come out -- LP #1773157
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1773157
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940541
Title:
[needs-packaging] Buffer
Launchpad issue link didn't come out -- LP #1773157
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1773157
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436945
Title:
devel: consider fq_code
A lot of comments here seem outdated, however things have moved on in a
good-way!
Taking reference of
https://www.bufferbloat.net/projects/bloat/wiki/Linux_Tips/ -- would
now seem that many of the bufferbloat fixes HAVE been implemented --
Upstream kernel changes have now introduced tcp_sack tcp
Interestingly, turns out that seemingly systemd is what is (currently)
responsible for turning on fq_codel by default. See:-
https://github.com/systemd/systemd/commit/e6c253e363dee77ef7e5c5f44c4ca55cded3fd47
Be nice to then get that suggested into upstream linux as a default
and/or procps for 'n
(fwiw, fq_codel queuing is now being turned-on in bionic (at least) by systemd,
confusingly!).
https://github.com/systemd/systemd/commit/e6c253e363dee77ef7e5c5f44c4ca55cded3fd47
Possibly, turning on ECN might more likely happen there first, but I would like
the procps updated for those using upst
** Changed in: ubuntu
Assignee: (unassigned) => Simon Iremonger (ubuntu-iremonger)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940541
Title:
[needs-packaging] Bufferbloat: Ubuntu does
FWIW Although syncookies has long-since been enabled upstream, the
outdated comments in sysctl about syncookies still persist, I have now
created new ubuntu bug #1773157 [please comment there].
[This also requests ECN-on-outgoing enablement which has similarly
matured etc.].
--
You receive
>From what I can see, updates in ubuntu have now fixed this, bionic
system certainly seems to now be booting with
/proc/sys/net/core/default_qdisc = fq_codel now!.
Can somebody confirm this and close this bug as 'fixed' ?
SECONDLY, Related bufferbloat-matter to make fq_codel work better to avo
Public bug reported:
The ubuntu version of procps carries it's own /etc/sysctl.d/10-network-
security.conf file explicitly that appears not to be part of debian
procps version.
Firstly, the section about "# Turn on SYN-flood protections." (came from LP
#57091 ) is now entirely outdated, upstr
HOWEVER, Trusty e2fsprogs backporting situation actually seems to be that, some
change between 1.43.3-1~bpo8+1 and 1.43.4-2 is where the
trusty-incompatibility has accrued, 1.43.9-2 does NOT build on trusty! :-
https://www.iremonger.me.uk/noidx/e2fs/e2fsprogs-1.43.9_trusty_build-fail.log
A s
OK On further investigation, I have confirmed a lot of key-facts (1 of 2
linked comments).
e2fsprogs 1.44.0-1 backports to xenial with no difficulty whatsoever,
passes "make fullcheck" and works in every way I can tell, lots of
resizing and checking and use within gparted, etc, all (apparently)
be
FWIW 'this seems to WORK in bionic, including "make fullcheck" on the
source, system able to check itself on boot, resizing other system
disks, no issues so far as I can. Thankyou for agreeing//doing this so
quickly.
Backporting related matters to be discussed separately in:-
https://bugs.launchp
e2fsprogs 1.44.0 for bionic18.04 has apparently been agreed:-
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1756177
[launchpad build-logs suggest its' been built for PROPOSED but not yet
seen it 'come through' as a package or appear on 'packages.ubuntu.com'
...].
Hopefully that will go
See linked bug 1601997, response seems to be to accept your 'new'
defaults for ext4 in 18.04. I note, particularly -- your request about
1.44.0 inclusion doesn't yet seem to be addressed [maybe it requires a
separate bug//issue] ;-(. Do expand on that point if you can.
--
You received this bug n
Steve:
Given what you say, can you consider Tytso's request to put 1.44.0
e2fsprogs into Bionic. This allows for not-enabled-by-default for
support of 2 extra ext4 flags in e2fsprogs, thereby avoiding this
situation happening again for 20.04 with respect to THOSE flags...
As TJ- said, be good t
Initial comments from the email:-
a) There is some confusion over "metadata_csum" with/without "64bit". -- Those
who have 'reverted' are usually reverting BOTH flags [as I've done some
places], not just metadata_csum.
My understanding is 64bit is of no benefit except support >16TB fs and to
st
FWIW, As was discussed, I checked into Grub2 and os-prober in older supported
ubuntu (which may have similar incompatibility to e2fsprogs, thereby creating a
multibooting issue with 18.04).
After experimenting carefully with a 14.04+16.04+18.04 (GA kernels, no HWE
specifically) BIOS-style triple
Can we pay-attention, to this thread (now) being about considering the
feature-flags 'used by default' in mke2fs.conf, in consideration to
18.04 -- [linked bug for e2fsprogs].
We know massive 'compatibility'/portability benefit of formatting the
same as previous-LTS by default, as the required e2
Given your other comment (which I think may have been posted to the wrong
thread):-
[E2fsprogs 1.44.0 now depends on dpkg build-profiles, which means that getting
it backported to 14.04 LTS would require adjusting debian/control and
debian/rules a bit. For 14.04 LTS, I'd urge consideration of go
Canonical please read Theodore Tso's Comment #4 above, and consider for
Ubuntu 18.04 LTS!
This "64bit,metadata_csum" creates compatibility-issues even with 16.04
LTS, and does not seem to provide a huge benefit [>16TB fs support,
slightly stronger metadata checksumming].
This creates all sorts of
Ubuntu 18.04 may well enable (under review) 64bit,metadata_csum by
default, thereby creating ext4 filesystems that are not compatible with
e2fsck on Ubuntu-16.04 LTS (or 14.04)?
This creates all sorts of problems for compatibility/portability of
filesystems, for e.g.:-
* dual-booting 18.04 and ol
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> Bog standard 16.04 has it turned on (from the above referenced 10
> -network-security.conf).
> But, if you then enabled ufw, it gets disabled, due to the default
> setting in /etc/ufw/sysctl.conf.
> There seems to be serious debate as to whether o
Upstream kernel have decided to enable syncookies by default (according to that
debian bug, since Linux 2.6.37!).
This makes sense, as the main downsides have already been resolved (especially
window scaling even under syncookies-activation), and this feature only
kicks-in if the SYN-queue is ov
There have been various upstream ipv6 related fixes in the debian/ubuntu
changelogs,, imported from upstream and otherwise.
Is this bug still present in debian stretch and ubuntu xenial with newer autofs
packages ? I'd suggest testing ubuntu-xenial in particular as the next LTS
release (underp
Public bug reported:
This bug:-
http://bugs.squid-cache.org/show_bug.cgi?id=3326
Is still present in the Precise12.04-LTS squid3, 3.1.15-1ubuntu2, which has
become the main version of squid as of Precise12.04.
This is a one-line-fix (though I had to merge it manually):-
http://www.squid-cache.or
There is a PPA of the 1.0.0-rc versions that may be acceptable to you
...
https://launchpad.net/~savoirfairelinux/+archive/sflphone-nightly
But this is a nightly-build, not a release-version as such...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 842586 ***
https://bugs.launchpad.net/bugs/842586
** This bug has been marked a duplicate of bug 842586
sflphone FTBFS (unavail. b-d libedateserverui1.2-dev) and is NBS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The fundamental problem here, seems to be, that sflphone is built
against gnome2 style 'libedataserverui1.2-dev' and this is not available
with Gnome-3 (although some of the other libraries such as
libedataserver1.2 ARE still there).
I'm not 100% sure but I think the 'right thing to do' is make sf
As far as I can tell, this is now in the motions of being fixed via
lucid-proposed.
linux-headers-2.6.35-30 ver 2.6.35-30.58~lucid1 is there and
2.6.35-30.59 will be soon apparently.
I guess when it appears, a good idea would be to test the version in
lucid-proposed and report back on Bug 838043
Please take note of related bug, which is collecting many duplicates etc.
https://bugs.launchpad.net/bugs/824080
With thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/829658
Title:
linux-lts-ba
On Fri, 9 Oct 2009, Olaf van der Spek wrote:
> Has this request been forwarded upstream (lkml)?
Not that I am aware of.
It would be good for this confusion/misinformation to get sorted
out properly.
Why is it that some wish to make sweeping statements and not
understand the whole situation?
>> Ah, nice. I kinda expected a link to the package version in which it
got fixed.
The silly thing is
There is misinformation in the /etc/sysctl.conf now!
It says:-
"# This disables TCP Window Scaling (http://lkml.org/lkml/2008/2/5/167)"
First of all that is incorrect as a blanket statement.
> Thanks for your quick response, here are the 3 pieces of information you
> requested.
> DISTRIB_DESCRIPTION="Ubuntu 8.04.2" [...]i686 GNU/Linux
> ||/ Naam Versie Omschrijving
> +++-==-==-
> ii php5-imagick
> Looks like the latest updates to the php5 packages broke it again. The
> symlink solution doesn't work and I have the latest version of the
> package installed.
What release / architechure are you using?
(cat /etc/lsb-release);(uname -a)
What version of php5-imagick has just got installed?
I'm getting a similar error but different problem ;-).
All worked fine on Ubuntu 8.04 LTS (actually I think I got warnings in
the dmesg, but it all still *worked*).
This machine has:-
00:02.0 VGA compatible controller: Intel Corporation 82815 Chipset Graphics
Controller (CGC) (rev 04)
Under Ubu
On Thu, 23 Oct 2008, KimOlsen wrote:
>> "...option causes the system to violate the TCP standard..."
> I do not think this is the case. If you check RFC4732 they list this as
> a possible way to help against DoS attacks.
> I also believe that window scaling is not affected, but large windows
> are
On Fri, 12 Sep 2008, Kees Cook wrote:
> Enabling syncookies disables TCP window scaling[1],
I think this is incorrect as-stated But this should be
confirmed/proved/disproved.
As far as I have found out elsewhere, the syn-cookies support
in Linux is adaptive, and does NOT come into play u
94 matches
Mail list logo
