[00:41]  * penguin42 wonders about bug 745350
[00:41] <ubot4`> Launchpad bug 745350 in firefox (Ubuntu) "while working on Firefox/Gmail, my cat sit down on keyboard (affects: 2) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/745350
[06:28] <trinikrono> is there any active mentors around?
=== yofel_ is now known as yofel
[13:22] <Abhijit> hi
[13:22] <Abhijit> someone please triage this bug
[13:22] <Abhijit> https://bugs.launchpad.net/ubuntu/+source/rednotebook/+bug/745657
[13:22] <ubot4`> Launchpad bug 745657 in rednotebook (Ubuntu) "no password protection (affects: 1) (heat: 6)" [Undecided,New]
=== BUGabundo is now known as BUGa_jobIntervie
[15:08] <hggdh> trinikrono: there are always at least one experienced triager here (and, probably, also a mentor)
[16:27] <Tetsuo55> hello i was asked to test with a mainline kernel
[16:27] <Tetsuo55> Does that mean i use this one http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
[16:28] <Tetsuo55> i am on a fully updated 10.10 ubuntu
[16:31] <charlie-tca> Tetsuo55: yes, that is the correct one
[16:32] <Tetsuo55> it says my boot is full
[16:32] <Tetsuo55> damn
[16:32] <Tetsuo55> need to clean up
[16:39] <Tetsuo55> will this now automatically be my new default kernel?
[16:39] <Tetsuo55> or do i need to choose it from the boot menu
[16:40] <Tetsuo55> i guess ill find out
[16:47] <Tetsuo55> hmm
[16:47] <Tetsuo55> with the daily kernel my screen problems are even worse
[16:47] <Tetsuo55> now the monitor is stuck on 1024x768, and it hasnt even detected the laptop monitor
[16:48] <Tetsuo55> does ubuntu add special patches for laptops and their ability to display on external monitors?
[16:48] <Tetsuo55> (to the kernel)
[16:50] <hggdh> Tetsuo55: the Ubuntu kernel may have patches from upstream to address specific issues. The best way to find out is to look at the source package diff
[16:50] <Tetsuo55> i just installed the kernel that was compiled today from git
[16:50] <Tetsuo55> so that seems unlikely to me
[16:50] <Tetsuo55> unless by upstream you mean not-yet-committed-to-kernel.org
[16:51] <hggdh> Tetsuo55: if you installed a kernel from the kernel ppa, then there are no Ubuntu patches
[16:52] <Tetsuo55> yes
[16:52] <Tetsuo55> ok finished burning natty nightly cd
[16:52] <Tetsuo55> so lets see what happens there
[17:29] <Tetsuo55> back, same problem on the latest natty build with regards to my hardware button not working
[17:29] <Tetsuo55> now on to the problem with 10.10 where my monitors are not correctly detected by the daily mainline kernel
[17:29] <Tetsuo55> i quickly saw an error flash by before the ubuntu desktop appeard
[17:30] <Tetsuo55> is that logged somewhere so i can find it?
[17:35] <Tetsuo55> could this be relevant? [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer
[17:38] <roadmr> Tetsuo55: use the dmesg command and see if your error is there
[17:41] <Tetsuo55> mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
[17:41] <Tetsuo55> [drm] MTRR allocation failed.  Graphics performance may suffer.
[17:41] <Tetsuo55> lp: driver loaded but no devices found
[17:41] <Tetsuo55>  [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[17:42] <Tetsuo55> [drm:i915_gem_mmap_gtt] *ERROR* Attempting to mmap a purgeable buffer (6 times)
[17:43] <Tetsuo55> those are the errors i get, sorry for not using pastebin but my screen is tiny
[17:43] <Tetsuo55> i also get a lot more warnigns and even a segfault for other hardware
[17:47] <charlie-tca> QA Weekly meeting in #ubuntu-quality in 14 minutes
[18:09] <Tetsuo55> Does this error suggest i need to install the kernel-matching headers??  bluetoothd[1281]: segfault at 7f4fdbbe4450 ip 00007f4ed9881664 sp 00007fff40f4d520 error 4 in libc-2.12.1.so[7f4ed980a000+17a000]
[18:34] <penguin42> just looks like a bug in bluetoothd
[18:37] <cyphermox> Tetsuo55, you should probably open a bug against 'linux' about the i915 errors, and one different one for bluez if you can find a .crash file under /var/crash relating to the segfault line you copied
[18:37] <Tetsuo55> i may have found a fix
[18:37] <Tetsuo55> on google
[18:37] <Tetsuo55> just 2 more unfixed errors left
[18:37] <Tetsuo55> can i change this somewhere
[18:38] <Tetsuo55> ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[18:38] <Tetsuo55> ill report them all once i finish trying the workarounds
[18:38] <Tetsuo55> or does the ACPI thing require a recompile of the kernel
[18:40] <Tetsuo55> thats one and the other (MTRR) is supposedly solved by doing this http://ubuntuforums.org/archive/index.php/t-1285176.html
[18:40] <Tetsuo55> brb
[18:44] <Tetsuo55> ok better, many errors are gone now
[18:44] <Tetsuo55> but one thing has failed to work
[18:45] <Tetsuo55> disabling all animation fixed the errors i was having (that appeared 6 times)
[18:52] <Tetsuo55> ohh i see my mistake
[18:52] <Tetsuo55> rebooting again
[20:08] <Tetsuo55> allright ive made some progress
[20:08] <Tetsuo55> the videocard problems are being caused by MTRR mismapping (for some reason it thinks i have 32gb of ram and the resulting mapping is blocking videocard memory from being writable or something)
[20:09] <Tetsuo55> now to fix it i need some way to specify the MTRR settings during bootup
[20:09] <Tetsuo55> i have used a tool to generate the exact settings for my systems. but i dont know where to specify them
[20:12] <Tetsuo55> hmm looks like there have been 9 bioses released since the current one i am using, and one contains a firmware update for the videocard
[20:12] <Tetsuo55> that might fix the problem
[20:16] <Tetsuo55> hmm how to run a windows bios update utility from ubuntu....
[22:23] <trinikrono> can someone tell me what is the purpose of that depenencies.txt that are on all the bug reports, i realised it does not just list installed packages on a system , is the dependencies of the package itself?
[22:24] <micahg> trinikrono: yes, it should be the dependency tree of the package
[22:25] <trinikrono> oh cool :D
[22:51] <trinikrono> can bug 646699 be set to fix released since it is so in maverick
[22:51] <ubot4`> Launchpad bug 646699 in nautilus (Ubuntu) (and 1 other project) "Nautilus; unclear whether cut or copy used (affects: 1) (heat: 21)" [Low,New] https://launchpad.net/bugs/646699
[22:54] <yofel> trinikrono: hm true, they seem to be highlighted now, so setting to fixed is ok
[22:54] <yofel> it would be nice to have a changelog that says that it was fixed, but that's probably not the case here
[22:56] <trinikrono> yes because it was implemented without considering the bug
[22:56] <trinikrono> yofel: what about if the reporter wanted this feature in lucid, would that be considered a backport?
[22:58] <yofel> hm, I don't think nautilus is really backportable (https://help.ubuntu.com/community/UbuntuBackports) and we don't SRU new features
[22:58] <yofel> if anything it would be a backport
[23:00] <trinikrono> ok i will set as fix released and put a link to a article i found, http://www.omgubuntu.co.uk/2010/08/nautilus-update-in-maverick-bring-many-new-fixes-changes/
[23:04] <trinikrono> If a bug is fixed in the current development release, it is Fix Released. If the bug also needs to be fixed in a stable release, use the "Target to release" link to nominate it for that release.
[23:05] <trinikrono> yofel: can i do that?
[23:05] <yofel> trinikrono: that's used for SRU tracking https://wiki.ubuntu.com/StableReleaseUpdates
[23:05] <yofel> read the "When" and decide if that applies here
[23:07] <trinikrono> oho so only serious bugs, i will tell him to request a backport if he really wants then
[23:22] <micahg> trinikrono: backports are for new features generally, FYI
[23:46] <Tetsuo55> turns out the ubuntu kernel is heavily patched to work-around issues with my motherboard/videocard
[23:46] <Tetsuo55> so the vanilla mainline builds are unusable
[23:47] <Tetsuo55> the error still occurs, but in the official ubuntu kernel a few lines later a workaround is apploed
[23:47] <Tetsuo55> applied*
[23:48] <Tetsuo55> its the same for all the errors i had, they all have a workaround in place
[23:48] <Tetsuo55> so i updated my tickets :)
[23:57] <penguin42> Tetsuo55: Hey well it's good those fixes are there and work
[23:58] <Tetsuo55> indeed
[23:59] <Tetsuo55> unfortunately they are still required with current kernel git-head/tip
[23:59] <Tetsuo55> its too bad because i wopuld like the wonders patch (new group scheduling)