[03:25] <snadge> has there been a kernel update lately that may fix intel dual screen issues?
[03:25] <snadge> in installed a mainline kernel with drm next (random choice) .. but that worked around the issue
[03:25] <snadge> and i haven't been bothered to try and fix it properly
[03:26] <snadge> ... look into it myself.. answer: no
[03:27] <snadge> damn.. i should've reported this issue earlier
=== arun_ is now known as run
=== run is now known as arun
[04:34] <snadge> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243524
[04:34] <ubot2> Launchpad bug 1243524 in linux (Ubuntu) "Dual Display not working on Mac Mini" [Undecided,Confirmed]
[04:34] <snadge> :D
[04:34] <snadge> at least this one is simple
[04:35] <snadge> we have a problem.. easy to confirm.. and there's definitely a fix for it
[04:35] <snadge> i just dont want to run dodgy mainline nightly kernels on my work desktop.. if i can help ti
[04:39] <snadge> the problem is.. mac mini's should just die in a fire
[05:08] <snadge> how can a bot confirm my bug report
[05:09] <snadge> its almost offensive :P
[06:15] <bjf> snadge, a bot can confirm that you have submitted all the logs that we require. that's what 'confirmed' means to us
[06:16] <snadge> i guess that is a bit of a boring task for a human to do just that
[06:16] <bjf> yes, the turn around was a pain for a dev to then ask and wait. now a bot does it.
[06:16] <snadge> im tempted to mark the bug as minor.. or dont care.. it sounds like a random Mac UEFI issue
[06:17] <snadge> but who knows.. ubuntu is very popular these days.. if it was fedora.. i wouldn't bother at all
[06:18] <snadge> thats the whole reason this mac is running ubuntu in the first place.. fedora simply wouldn't install.. known issue.. marked as wontfix for f19.. issue still open in rawhide.. *shrug*
[06:18] <bjf> it will take a little work to bisect it to find the actual commit that fixes the issue
[06:18] <snadge> unfortunately.. its not completely fixed by mainline either
[06:18] <bjf> however, there will be a new kernel in -proposed this week that would be worth testing to see if it helps
[06:20] <snadge> i'll give that a go.. thats probably the easiest thing to do for now, there wont be much heat on this issue
[08:11] <larsduesing> Good morning or such :)
[08:12] <larsduesing> Where should I report problems with ecryptfs to? kernel? ecryptfs-utils? ecryptfs directly on launchpad?
[08:14] <apw> larsduesing, to some degree that depends where the bug seems to be, if its a userspace issue ecryptfs-utils, if it is anything else against 'linux' the kernel
[08:14] <larsduesing> On creating files >4GB  data gets corrupt. Up to 4GB size everything is ok, but on appending any more data the whole file gets corrupted...
[08:14] <apw> that sounds kernel side to me
[08:14] <larsduesing> yes, to me too.
[08:15] <larsduesing> so, thats clear. Thanks apw.
[08:15] <apw> then kernel it is, and paste the bug number in here, so i can get it some attention, as data corruption == bad
[08:15] <apw> larsduesing, which release are you seeing this on
[08:16] <larsduesing> saucy - 3.11.0-031100rc7-generic (apw@gomeisa)
[08:17] <apw> hmmm a test build, ok
[08:17] <apw> anyhow, its likley in all of them, so file it anyhow
[08:18] <larsduesing> oh. right
[08:18] <apw> its not very common for people to make large files in ecryptfs luckily, but also likely it has gone unnoticed for a long time as well
[08:18] <apw> anyhow, let me know the bug#
[08:18] <larsduesing> I got an .iso.bz2 file, and decompressed it.
[08:18] <larsduesing> sure
[08:19] <larsduesing> At first, I'll try to update kernel, and retest
[08:19] <larsduesing> oh, there is no newer kernel?
[08:19] <apw> larsduesing, sure, though if it is in 3.11. its in everything most likely so a bug so we cna check sounds good
[08:20] <larsduesing> ok
[08:25] <larsduesing> apw - sorry.. but where should I report the bug? https://launchpad.net/linux -> Launchpad needs to know where the user can report a bug
[08:28] <apw> run "ubuntu-bug linux" in a terminal
[08:28] <apw> larsduesing, the linux you have there is the linux project not the linux package, LP is rather opaque at times
[08:29] <larsduesing> ah... ok
[08:30] <larsduesing> thats no official ubuntu package. 
[08:30] <larsduesing> I DO love software :)
[08:31] <larsduesing> (I sort things out on my side... give me a few minutes, please...)
[08:32] <apw> np
[08:48] <larsduesing> apw - btw - kernel - package naming is a bit confusing:
[08:48] <larsduesing> linux-headers-3.11.0-12-generic_3.11.0-12.19_i386.deb
[08:48] <larsduesing> linux-headers-generic_3.11.0.12.13_i386.deb
[08:48] <larsduesing> 3.11.0.12 <-> 2.11.0-12
[08:49] <tyhicks> larsduesing: Hi - upstream eCryptfs kernel maintainer here - please ping me with the bug number when you open the bug
[08:49] <tyhicks> I'm off to bed, but I'll have a look first thing in the morning
[08:50] <larsduesing> tyhicks: sure - atm i'm installing current mainline kernel, rebooting, retesting and then I'll report.
[08:51] <larsduesing> tyhicks: Have a good night :)
[08:51] <tyhicks> thanks for testing mainline
[08:51] <larsduesing> tyhicks: thats the minimum I could do.
[08:52] <larsduesing> *rebooting* away for some minutes... :)
[09:01] <larsduesing> I'm back. Now testing.
[09:06] <larsduesing> cute. NOW IT WORKS.
[09:13] <larsduesing> apw: Now it works. strange.
[09:14] <larsduesing> two different files which won't work with old kernel do work now.
[09:20] <larsduesing> tyhicks: Sorry, cannot reproduce with current mainline-kernel
=== psivaa is now known as psivaa-afk
[10:05] <larsduesing> Ok, all back...
[10:07] <larsduesing> this time the curruption is much more cryptic
[10:08] <larsduesing> apw, tyhicks Sorry.. Bug is reproducible
[10:09] <larsduesing> in the 3.11.0-031100rc7-generic kernel even the header of the file was currupted
[10:10] <larsduesing> but in 3.11.0-12-generic the header is ok...
[10:11] <larsduesing> (as opposed the full file)
[10:11] <larsduesing> ok, filing bug
[10:21] <larsduesing> apw, tyhicks : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243636
[10:21] <ubot2> Launchpad bug 1243636 in linux (Ubuntu) "ecryptfs currupts files over 4GB size" [Undecided,New]
=== psivaa-afk is now known as psivaa
[14:52] <coredump> Hmm. was the linux-tools-<version> package supposed to be created when compiling the kernel from source?
[16:11] <brendand> does anyone know how rtcwake could be able to work without the presence of /sys/class/rtc/rtc0/wakealarm interface?
[16:11] <brendand> it seems to be able to on ARM
[16:15] <ppisati> brendand: strace it
[16:16] <brendand> found it!
[16:19] <brendand> well, sort of
[17:27] <apb> Hello...So I went to bed last night and I woke up this morning to a blank screen - normal after 5 or so minutes of inactivity - moved my mouse... hit keys on my keyboard... no reaction.  I was forced to power down and reboot.  This is the first time this has happened and the primary thing that changed was... the kernel.  ubuntu 12.04, kernel 3.2.0-55-generic-pae 
[19:40] <rostam> HI I have custom card which we build a driver for it. The original implementation was in Redhtat 6.4 which is based on linux 2.6.28 (old) now I am porting the driver to ubuntu and I get ioctl errors (unknown ioctl number). Has there been a change in ioctl framework ? thx
[19:58] <infinity> rostam: If you google for the exact compile/runtime erorrs you're seeing, it'll probably shed some light.
[19:58] <rostam> infinity, thanks will do that
[20:09] <larsduesing> tyhicks: If I can be of any help, tell me please.
[20:17] <BjoernC> sforshee: hi
[20:20] <BjoernC> sforshee: FYI: I'm now trying to rebuild the kernel with your patch active and deactivating the other patch; However, I've managed to control the backlight by Software (By using the KDE-slider it works on both kernels (reverted OOB, unreverted only with the option acpi_osi="Windows 2012")) writing directly into /sys/classes/.../brightness doesn't work at both kernels - it's a little bit weird...
[20:20] <BjoernC> I will post the update when i've rebuild the kernel and have the results...
[20:21] <BjoernC> but it may take some time.
[20:21] <BjoernC> hopefully, my bug report is a little bit helpfull for you
[21:12] <tyhicks> larsduesing: thanks - this is easy to reproduce so I shouldn't need much help outside of testing a potential fix
[21:12] <tyhicks> larsduesing: I'll ping you when I have a test kernel ready
[21:24] <rostam> HI I have installed ubuntu 12.04 update 3 on my system. All the sudden I get the following messages in the /var/log/messages:  init: serial-ttyS0 main process (1129) terminated with status 1     any idea why?
=== apb_ is now known as apb1963
[21:51] <apw> rostam, do you have a serial port on this system?  and have you lost any functionality