Re: Confused?

2013-10-03 Thread Phill Whiteside
Hi Jack, I'm that busy between 13.10 and 14.04 I get the releases mixed up! the last one should read 13.10 :) Regards, Phill. On 4 October 2013 04:52, Jack Trice wrote: > Hi Phill, > > I was confused seeing your email with Subject: Re: AW: zRAM broken on > Raring? > > and content: > > "I've

Re: AW: zRAM broken on Raring?

2013-10-03 Thread Phill Whiteside
Hi, I've asked Joe (kernel team) about what plans the kernel team have for the kernel that will be shipped with 14.04 LTS. I've also stressed that this is not an urgent request! Kernel freeze is about NOW! That team have been working flat out to get as many gremlins sorted as possible. They are en

Re: AW: zRAM broken on Raring?

2013-10-03 Thread John Hupp
Good to hear, thanks! On 10/3/2013 3:04 PM, Leszek Lesner wrote: It is already fixed for/in saucy *Von: *John Hupp *Gesendet: *Donnerstag, 3. Oktober 2013 21:00 *An: *Phill Whiteside *Cc: *Leszek Lesner; lubuntu-users@lists.ubuntu.com *Betreff: *Re: AW: zRAM broken on Raring? Does that also m

Re: zRAM broken on Raring?

2013-10-03 Thread Phill Whiteside
Indeed it is :) The concentrated effort was the crashing / freezing bug. The parted -l is a different bug and will be looked into once we get some time. I'm guessing that as it's been around since raring (at least) and is not reported in the development kernel it will depend upon if the kernel tea

AW: zRAM broken on Raring?

2013-10-03 Thread Leszek Lesner
It is already fixed for/in saucy

Re: AW: zRAM broken on Raring?

2013-10-03 Thread John Hupp
Does that also mean that zram will not be fixed in time for the Saucy release? On 10/3/2013 1:38 PM, Phill Whiteside wrote: I strongly suspect that the the 'sudo parted -l' output of 'Error: /dev/zram1: unrecognised disk label', has been around for quite some time. I think it was found when p

Re: AW: zRAM broken on Raring?

2013-10-03 Thread Phill Whiteside
I strongly suspect that the the 'sudo parted -l' output of 'Error: /dev/zram1: unrecognised disk label', has been around for quite some time. I think it was found when people went digging into the issue with zram freezing. The good news is that that particular error is not seen in the 3.12rc1 and