[00:02] <cozziemoto> yofel,  the issues i had with not being able to boot after updates...is this only with the nvidia driver installed?
[00:03] <cozziemoto> cozziemoto,  = coz_
[00:03] <yofel> I assume it's the nvidia driver and vesafb not playing well together, but I don't know enough about the topic to give any guarantees
[00:04] <cozziemoto> yofel,  ok  reinstalled  doing updates now...will reboot before installing nvidia driver to test
[00:05] <cozziemoto> i am wondering if the beta driver would be better ... I might test that as well
[00:08] <cozziemoto> yofel,  asking in #nvidia just for kicks...I see you are there as well :)
[00:24] <penguin42> yofel is everywhere
[00:26] <yofel> pretty much, need to clean up my channel list sometime..
[00:29] <Ohelig> ok so I was all like "zomg ubuntu alpha, MUST HAVE" and I haved it. but then it was all like "Do you want to log in as 'Zach' or 'proxy'?" and I'm like "who teh fux is proxy"
[00:29] <Ohelig> Translation: a new user, proxy, showed up after installing.
[00:30] <yofel> hm, *that* should be disabled
[00:30] <yofel> all users with an UID <1000 shouldn't show up on the login screen at all
[00:30] <Ohelig> is this happening to everyone?
[00:30] <yofel> not here, but I use KDM
[00:31] <Ohelig> if it matters, I'm using the AMD 64bit version
[00:31] <Ohelig> proxy also does not have a folder in /home
[00:39] <cozziemoto> ok that didnt work again...and I didnt install the nvidia driver  ... oh boy  I will try again
[01:13]  * penguin42 got an error during an update I just did where it didn't properly create an initrd because of a missing /etc/default/keyboard - which I now seem to have
[01:15] <yofel> yep, got that too, first I got a prompt for a keyboard layout switch combination, then an initrd error, the dpkg --configure -a after that ran fine though
[01:15] <penguin42> not entirely sure what to report that against
[01:16] <BUGabundo> damn it :| pidgin is still broken
[01:16] <BUGabundo> and borking my upgrades
[01:16] <yofel> I think they're waiting for debian to fix that
[01:16] <BUGabundo> I'm getting the one of the keyboard too
[01:16] <BUGabundo> yofel: which one ?
[01:16] <yofel> pidgin
[01:17] <BUGabundo> ahh if I downgrade pidgin, I can upgrade Data ... wth
[01:34] <Ohelig> ugh
[01:34] <Ohelig> I hate unity because it's ALWAYS there. there should be a little button to click in the bottom/top left corner to hide and reveal it
[01:35] <Ohelig> button is hidden when bar is hidden
[01:36] <penguin42> Ohelig: You can configure it to hide
[01:39] <Ohelig> :| where
[01:40] <penguin42> if you get up the compiz configuration manager, select the unity plugin there are a couple of options, one of which is autohide
[01:40] <Ohelig> k, well i also hate it because 1: I don't know where to find my programs other than that ubuntu-logo button
[01:40] <Ohelig> and 2: there's no organization
[01:41] <penguin42> yeh
[04:06] <h00k> Alright, so, my Empathy keeps opening links in Firefox, even though chromium-browser is my default browser
[04:06] <h00k> any protips?
[04:07] <h00k> oop, apparently it's anything opening a link.
[04:07] <h00k> aaand apparently it really *wasn't* the default.
[04:08] <h00k> ...fix'd. Thanks all! You rock.
[04:55] <Ohelig> @h00k, you're welcome
[04:55] <h00k> Ohelig: I had set it to be default, anyway.
[04:56] <h00k> but apparently it wasn't!
[11:02] <AnAnt> how do I activate unity in alpha1 ?
[11:10] <rork> AnAnt: If I remember correctly you can choose between Unity and Desktop on the login screen
[11:10] <sagaci> AnAnt, have a decent graphics card
[11:10] <sagaci> and do what rork said
[11:15] <AnAnt> rork: aha
[11:17] <AnAnt> rork: I am using the Live CD, I don't see the option on login screen
[11:18] <rork> AnAnt: I have no experience with the live-cd, but someone else will know how to do it.
[11:47] <sagaci> AnAnt, try typing unity into the terminal
[12:37] <vita_> Hello. I have issue with Thumbnails in Dolphin in Natty. I have installed mplayerthumbs (or something like that), enabled it in Dolphin, but thumbnails are not created. What should I do next? I tried to google for some info, but no success. It used to work for me. I even purged KDE configs (made backups, of course) and started from a new. :-(
[12:38] <penguin42> vita_: Report the bug with ubuntu-bug 1st, then ask on \kubuntu I'd suggest
[12:39] <vita_> lol
[12:39] <penguin42> bad bot!
[12:39] <vita_> penguin42: OK. I'll do. I thought I did something wrong.
[12:39] <penguin42> not sure, I've not done anything with the thumbnails
[12:45] <vita_> I'm at https://bugs.launchpad.net/ and cannot find button for reportiung bug. Am I blind? Any hints?
[12:46] <penguin42> vita_: Do it from a command line on your machine; just run ubuntu-bug and the package name
[12:47] <vita_> ok, thanks
[13:17] <h4f> Hi all. my microphone stopped working recently.
[13:18] <h4f> I have Acer Aspire 5720 laptop
[13:18] <h4f> with built in microphone
[13:18] <h4f> Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
[13:19] <h4f> actually the microphone is working but the sound is so low that you hardly can hear.
[13:27] <h4f> any one know what does  "(rev 03)" mean ?
[13:27] <vita_> revision
[13:27] <h4f> yea but what is revision ?
[13:27] <vita_> 3rd revision
[13:28] <vita_> it means, that they found flaws in some hw, so they fixed them
[13:28] <h4f> because I found on internet some people have (rev 04)
[13:28] <h4f> why do I still have 03?
[13:29] <vita_> think
[13:30] <coz_> hey guys
[13:34] <coz_> good day
[13:58] <knittl> hi. i got a lot of unmet dependencies
[13:58] <knittl> known issues? i couldn't find a bug
[13:59] <knittl> bootchart, ibus-pinyin, initramfs-tools, libwnck-dev, mercurial, openoffice.org-gnome
[14:00] <knittl> 2 depend on klibc-utils
[14:12] <penguin42> knittl: Seemed mostly OK last night, it hit a problem with some unconfigured packages
[14:13] <knittl> penguin42: i have it since yesterday morning /me thinks
[14:20] <penguin42> sigh, KDE is actually ending up using the us,af selection of keyboard that appared in /etc/default/keyboard as of yesterday
[14:22] <knittl> i also have keyboard problems. keyrepeat of left mod4
[14:22] <knittl> didn't happen before :(
[14:22] <knittl> wtf. is that file new?
[14:22] <knittl> i think it might be related to my problem
[14:36] <penguin42> yeh I reckon it is - but I can't figure out what created it, dpkg -S doesn't find an owner
[14:37] <knittl> weird
[14:40] <BluesKaj> Hiyas
[14:43] <slitbits> hellos
[14:49]  * BluesKaj is fed up with google chrome/chromium and google earth ..the toolbars and bookmark toolbars etc don't integrate at all with desktop environment settings.
[14:50] <zniavre> i can understand for the tabs (notebook) of the webbrowser
[15:04] <penguin42> knittl: I've confirmed and subscribed to bug 698263
[15:04] <knittl> penguin42: oh, you are german :]
[15:04] <penguin42> knittl: No, UK - the original reporter was German I think
[15:04] <knittl> eh yeah. mixed that up
[15:05] <penguin42> knittl: Keyboard conf things I'm joint US, Afghani
[15:05] <knittl> i'm selecting 'affects me'
[15:27] <knittl> i think the package that installed that file is 'keyboard-configuration'
[15:27] <knittl> sadly i cannot reconfigure it, because my dpkg database is broken …
[15:33] <penguin42> yeh someone on #ubuntu-dev suggested that package, but it seems to be that bug either way
[15:39] <BUGabundo> good afternoon
[15:55] <hackeron> hey, is ruby 1.9.2 included in natty?
[16:01] <BUGabundo> !search ruby
[16:01] <BUGabundo> fail bot
[16:02] <IdleOne> !info ruby
[16:02] <BUGabundo>   Candidate: <IP_ADDRESS>-2
[16:02] <BUGabundo> hackeron: yes
[16:02] <hackeron> awesome, thanks :)
[16:02] <hackeron> !info ruby-full
[16:21] <yofel> penguin42: KDE will use whatever X has as default if you don't set any other keyboard layout by hand, and the new settings are set on X level
[16:22] <penguin42> yofel: Any idea where from?  I can't see any xorg.conf stuff in /etc/X11 or /usr/share/X11/xorg.conf.d
[16:23] <penguin42> yofel: Whereever /etc/default/keyboard came from, it's matching what KDE is doing
[16:24] <yofel> the new /etc/default/keyboard I assume, since those are XKB settings, and I first noticed this on my login screen, while my session was fine
[16:24] <penguin42> yofel: Yeh
[16:24] <yofel> *how* it reads those I don't know
[16:26] <penguin42> yofel: thing is it wouldn't surprise me if it came from evdev or something like that; there is also some mumbling about it reading /var/lib/xkb/server-* files not that I understand why
[16:30] <hackeron> BUGabundo: where did you see that? - when I run apt-get show ruby-full, it show dependencies for 1.8
[16:30] <hackeron> BUGabundo: same for apt-cache show ruby
[16:31] <hackeron> BUGabundo: and only thing I can see is 1.9.1 when I search for 1.9
[16:31] <yofel> you're probably right, since evdev does show that it reads the settings from some config file [   321.270] (**) Option "xkb_layout" "de"
[16:31] <yofel> (see Xorg.0.log)
[16:31] <BUGabundo> hackeron: apt-cache policy
[16:32] <BUGabundo> $ apt-cache policy ruby1.9.1
[16:32] <penguin42> yofel: Things are too damn complicated; so many indirections
[16:32] <hackeron> BUGabundo: that's a pre-repease of 1.9.2, it isn't 1.9.2 and very buggy :(
[16:32] <BUGabundo> you asked for it
[16:33] <yofel> !info ruby1.9.1 | hackeron
[16:33] <yofel> messed up version, but should be 1.9.2
[16:33] <hackeron> yofel: it isn't :(
[16:34] <hackeron> yofel: it shows 1.9.2p0 when the 1.9.2 release is p136
[16:34] <yofel> oh, don't know it that detailed I fear
[16:34] <hackeron> :(
[16:35] <hackeron> guess I'll usr rvm
[16:35] <yofel> you could request an update in the Debian BTS, we just sync ruby from them
[16:35] <hackeron> use*
[16:43] <knittl> any idea how to fix up my broken dpkg/apt?
[16:44] <knittl> http://paste2.org/p/1184632
[16:44] <BUGabundo> I have pidgin broken
[16:44] <BUGabundo> and haven't been able to fix it :(
[16:44] <knittl> i can't update …
[16:45] <BUGabundo> knittl: $ sudo aptitude update; sudo aptitude safe-upgrade
[16:45] <BUGabundo> what does that give you ?
[16:45] <knittl> the same
[16:45] <BUGabundo> beside the usual, its not installed :)
[16:46] <knittl> BUGabundo: http://paste2.org/p/1184635
[16:46] <BUGabundo> yay
[16:46] <BUGabundo> postfix is broken too
[16:46] <knittl> i think it's mostly postfix
[16:47] <BUGabundo> do you use it?
[16:47] <knittl> its a dependence of nvidia-173 iirc
[16:48] <knittl> i could play chuck norris and manually add a description text
[16:48] <Guest78077> postfix? think not..
[16:48] <knittl> BUGabundo: is it safe? to add a Description: dummy text line?
[16:49] <knittl> Guest78077: it was a bug somewhere sometime
[16:49] <knittl> what the heck, i'll just try :D
[16:49] <BUGabundo> how can that be a depency ?
[16:50] <BUGabundo> apt-get force it out :)
[16:50] <knittl> apt-get force?
[16:50] <knittl> i tried apt-get install -f and aptitidu install
[16:50] <knittl> did not help
[16:50] <knittl> but yay, it seems to fix it
[16:50] <knittl> now i need to fix up those other duplicate entries …
[16:51] <knittl> WOAH
[16:51] <knittl> it seems like this file is broken
[16:51] <knittl> there'? some garbage in vim
[16:51] <knittl> ^@^@^@^@^@^@…
[16:51] <knittl> ARGS
[16:52] <knittl> :'(
[16:52] <knittl> some entries simply stop and the next starts somewhere in the middle
[16:54] <knittl> looks like a broken lock. how can i fix it? can i fix it at all?
[17:05] <coz_> yofel,   when I am wrong I am definitly wrong... I  uncommented the   GRUB_GFXMODE=640x480   and it works...
[17:06] <yofel> ok, so the VBE mode auto detection breaks your card, grrrr.... too many settings
[17:06] <coz_> yofel,  yes but only the one card
[17:06] <coz_> the 7400gt   but not the 6600gt
[17:07] <yofel> yes, they actually added a blacklist list for cards that have issues with vbe graphics mode, file a bug so your card get's blacklisted for auto detection at least
[17:08] <coz_> yofel, ok thanks... I certainly appreciate it... saves the pain of resinstallation each time :(
[17:09] <yofel> knittl: there should be a status-old that you can try to use to recover dpkg
[17:10] <yofel> the lockfile is /var/lib/dpkg/lock
[17:10] <yofel> 212484 0 -rw-r----- 1 root root 0 2011-01-08 20:13 /var/lib/dpkg/lock
[17:29] <knittl> yofel: do you think status-old is good?
[17:30] <knittl> yofel: thanks!!!
[17:30] <yofel> it should be the status from before dpkg broke it, try to make a diff of both
[17:31] <knittl>  1 files changed, 164 insertions(+), 27 deletions(-)
[17:32] <knittl> wheeeee :)
[17:43] <h00k> Is there anything else I can add to bug #692823?
[17:44] <h00k> Unity dies on my EEE, apport says this ^
[17:53] <alex_mayorga> is there a bug for right clicking not showing a visible menu on a nvidia 320m when running the new desktop using nouveau?
[17:54] <charlie-tca> unity desktop or classic desktop?
[17:56] <alex_mayorga> charlie-tca: unity is the only showing the problem
[17:57] <charlie-tca> Did they upgrade the nouveau driver to the 3d driver now/
[17:57] <alex_mayorga> the regular desktop showed right click menus as of yesterday
[17:57] <alex_mayorga> but honestly this is my 1st or 2nd try at unity so I can't really tell
[17:58] <charlie-tca> Don't think unity works with nouveau yet
[17:58] <alex_mayorga> all the menus when I click a panel are invisible too
[17:58] <charlie-tca> Requires 3d which requires the hardware driver be installed
[17:59] <alex_mayorga> charlie-tca: well I'm on unity using nouveau as we "speak"
[17:59] <alex_mayorga> but these two annoyances I describe seriously kill the usability for now
[18:00] <alex_mayorga> should I bug unity or nouveau on this one?
[18:04] <alex_mayorga> how does one reports nouveau bugs?
[18:06] <charlie-tca> and it is not working. It is not a bug because nouveau is not compatible with unity and is not supposed to be working with it.
[18:06] <JadenKorn> 3D acceleration could be initialized with a different package by still using Nouveau.
[18:07] <yofel> alex_mayorga: ubuntu-bug xserver-xorg-video-nouveau
[18:07] <yofel> ah wait
[18:07] <alex_mayorga> I was thinking it might be of value to tell them "it kind of works, except for XYZ"
[18:07] <charlie-tca> If it is a bug against unity on nouveau it will be invalid
[18:08] <alex_mayorga> but maybe charlie-tca is right and I should just stay mum on it
[18:08] <yofel> alex_mayorga: you can try to install libgl1-mesa-dri-experimental, but there is no official 3D support for nouveau, thus you can't use unity with nvidia cards by default
[18:09] <JadenKorn> By default no, but with that package, it should work (works for me).
[18:09] <bjsnider> depends on the card
[18:09] <alex_mayorga> as I said, all works but right clicking
[18:10] <JadenKorn> I don't have problems with the Nouveau one, but the nvidia-current one definitely has a problem (or a bug) with mine.
[18:10] <alex_mayorga> how can one tell what's the exact video configuration at any given point?
[18:11] <charlie-tca> look in syslog, ???
[18:16] <charlie-tca> It is also in xorg log
[18:17] <BUGabundo> buuuuuuu
[18:17] <BUGabundo> opening openoffice crashed my system :(
[18:18] <BUGabundo> bad natty bad
[18:18] <charlie-tca> BUGabundo: that seems wrong
[18:20] <h00k> Yeah, context menus on natty/unity are showing up behind appilcations (right click).
[18:20] <BUGabundo> back
[18:20] <BUGabundo> its not system
[18:20] <BUGabundo> its UI
[18:20] <BUGabundo> probably Compiz
[18:20] <BUGabundo> doesn't like OOo
[18:20] <BUGabundo> ffuuuuuuuuuuuu
[18:21] <BUGabundo> so how do I open OOo now?
[18:21] <BUGabundo> maybe on a nexted X
[18:22] <bjsnider> actualy this is an impressive new feature of openoffice
[18:22] <bjsnider> it crashes your system unless you pay ransom money to oracle
[18:22] <h00k> I have the nvidia driver installed, I'm not sure if I'm using it, or of Unity is using nouveau. Anyway, I can't see any right-click context-menus because they show up behind applications. Any protips?
[18:23] <charlie-tca> hm, that seems to work will, bjsnider ;-)
[18:23] <charlie-tca> s/will/well
[18:23] <yofel> h00k: xorg log will tell if you're using it, can't help with unity though
[18:23] <h00k> yofel: why didn't I think of that!
[18:24] <charlie-tca> h00k: that is a unity bug, already reported, as I recall
[18:24] <h00k> charlie-tca: Probably, yeah.
[18:25] <h00k> I think it's loading...yeah, NVIDIA GLX Module 260.19.29
[18:26] <BUGabundo> bjsnider: ahh thanks... let me.... aptitude purger *oracle* ; aptitude install LibreOffice  :D
[18:54] <LinuxRULES> hello
[18:54] <LinuxRULES> I updated my ubuntu 10.10 now I have 11.04? :S
[18:56] <BUGabundo> ahaha
[18:56] <BUGabundo> welcome :)
[18:56] <BUGabundo> how did you upgrade?
[18:57] <yofel> bug 690248 maybe
[19:01] <yofel> LinuxRULES: ^
[19:02] <LinuxRULES> haha yeah its a bug
[19:02] <LinuxRULES> thx man
[19:15] <gnomefreak> my terminal is huge :(
[19:15] <BUGabundo> yo gnomefreak
[19:16] <BUGabundo> long time no see
[19:16] <gnomefreak> hi BUGabundo
[19:16] <gnomefreak> i took some time off that i needed
[19:17] <BUGabundo> good for you
[19:17] <BUGabundo> how is your health?
[19:17] <gnomefreak> BUGabundo: im ok for the most part
[19:18] <gnomefreak> i hate using apport-collect it asks too many questions
[19:29] <gnomefreak> today is starting to suck already, i have been online for only a little while, i cant find the dmesg file i need for the failed boots. ill be back need a smoke
[19:29] <yofel> apport-collect will ask as many questions as apport-bug, blame the package hook
[19:31] <alex_mayorga1> ups my X locked up again
[19:31] <alex_mayorga1> bug 696104
[19:32] <alex_mayorga1> yofel: what to gather? now I can ssh into it
[19:33] <yofel> well, as bryce said, nouveau doesn't log any usefull information beside the crash, so describe as accurately as possible what you were doing the moment it froze
[19:36] <MTecknology> trying to compile vbox modules is so super fun right now; it's taking a crap ton longer than it's supposed to... as in about 15min so far
[19:40] <gnomefreak> i only have 3 bugs, however they suck. cant boot with 2.6.37-10 *-11 *-12, cant load Unity, due to timing out, there is another bug cant recall off hand
[19:41]  * gnomefreak goes to load gnome-shell for now
[19:42] <gnomefreak> gconftool-2 --set /desktop/gnome/session/required_components/windowmanager gnome-shell --type string
[19:42] <gnomefreak> damnit wrong window
[19:43] <gnomefreak> thats odd
[19:43] <BUGabundo> ahahha gnomefreak
[19:44] <BUGabundo> I only have 4 bugs :)
[19:44] <BUGabundo> a very old one with kmail
[19:44] <BUGabundo> e-sata no automount (old one too)
[19:44] <BUGabundo> compiz not starting on boot
[19:44] <BUGabundo> and broken upgrade of pidgin
[19:45] <penguin42> BUGabundo: you on kde?
[19:45] <gnomefreak> well the package kmail is a _bug_
[19:45] <BUGabundo> does it mather?
[19:45] <penguin42> BUGabundo: For the automount
[19:45] <BUGabundo> I'm on gnome :) and I've filed it one or two cycles ago
[19:46] <gnomefreak> stay with gnome and your kmail bugs will go away, try using evo or thunderbird or even claws
[19:46] <penguin42> ah ok, on KDE you can in principal to set up device notifier to mount non-removable drives at startup
[19:46] <penguin42> BUGabundo: You could always slap it in fstab
[19:47] <BUGabundo> I could
[19:47] <gnomefreak> be back going to reboot see if i cant find more bugs
[19:47] <BUGabundo> but that would not fix it for EVERYONE else
[19:47] <BUGabundo> I don't really like to work around "bugs"
[19:47] <BUGabundo> unless they are *my* bugs
[19:47] <penguin42> BUGabundo: So, the problem (which I don't know of a fix for) is that with eSATA I don't think there is a way for the machine to know it's not an internal drive which don't get automounted
[19:48] <BUGabundo> but usb pen drives works
[19:48] <BUGabundo> why won't a plug device like e-sata work too?
[19:48] <BUGabundo> fire up UDEV and let it do its magic
[19:48] <penguin42> BUGabundo: Because I don't think the e-sata looks any different to the hardware from an internal sata drive
[19:54] <penguin42> BUGabundo: do udisks --enumerate-device-files, find your e-sata drive and then do udisks --show-info devicename      and see what the 'system internal' 'removable' 'presentation hide' and 'presentation nopolicy' are
[19:54] <penguin42> BUGabundo: I bet they're the same as an internal partition
[19:54] <BUGabundo> don't have any e-sata drive next to me
[19:54] <BUGabundo> I mean, I do, but its powerd off
[19:55] <BUGabundo> give me a few min to test
[19:59] <gnomefreak> bug #3 i have is thunderbird not moving mail marked as junk to junk folder. if it sees a junk message on its own it will move it to junk folder
[20:00] <gnomefreak> oh well that wasnt supposed to happen
[20:03] <gnomefreak> ok i feel eally stupid but what is the command to file a bug. im drawing a blank
[20:03] <gnomefreak> s/eally/really
[20:04] <yofel> ubuntu-bug
[20:04] <gnomefreak> yofel: thanks
[20:15] <gnomefreak> it seems gnome-shell is broken too
[20:16]  * penguin42 goes
[20:18] <gnomefreak> seems browser + terminal causes gnome-shell to repeatedly redraw, i lose panel and windows and it keeps doing it until i close browser
[20:18] <gnomefreak> this didnt happen friday
[20:36] <uponit12> I have recently installed Ubuntu 11.04 on a MacBookPro 5,3 and have been trying to get the left-side fan1 to operate. For somereason only right-side fan2 works. I have installed lm-sensors, and attempted to run several scripts found on the internet regarding the manual control of the fans, and it seems there are a large number of sensors which are not operational. How do I get all of the sensors on the macbook to function as they should, as I suspect that
[20:36] <uponit12>  is why the fan1 will not operate?
[20:50] <alex_mayorga1> anyway yo attach files to a bug report from a ssh console?
[20:50] <yofel> hm, ubuntu-bug did support ssh at some point, try with X forwarding (ssh -X)
[20:51] <guntbert> alex_mayorga: you can use a pastebin from almost everywhere :-)
[20:54] <ratcheer> Has anyone tried booting directly to root on a btrfs, yet? If so, how did it go? My install ran perfectly, but it will not boot.
[20:55] <Volkodav> ratcheer: I do not beleive it is supported yet
[20:56] <Volkodav> still needs /boot partition
[20:57] <ratcheer> As of 9-Jan, it is supposed to be supported, per the grub2 update log.
[20:57] <Volkodav> hmm have a link handy ?
[20:59] <ratcheer> grub2 (1.99~20110106-1) experimental; urgency=low ... - Fix grub-probe when btrfs is on / without a separate /boot.
[21:03] <uponit12> I have recently installed Ubuntu 11.04 on a MacBookPro 5,3 and have been trying to get the left-side fan1 to operate. For somereason only right-side fan2 works. I have installed lm-sensors, and attempted to run several scripts found on the internet regarding the manual control of the fans, and it seems there are a large number of sensors which are not operational. How do I get all of the sensors on the macbook to function as they should, as I suspect that
[21:03] <uponit12>  is why fan1 will not work?
[21:04] <ratcheer> Volkodav: Here is a link http://permalink.gmane.org/gmane.linux.debian.devel.changes.unstable/224589
[21:11] <Volkodav> uponit12: did you install mac specific repos ?
[21:13] <uponit12> Volkodav: I don't think I have located that installation information yet, where can that information be found?
[21:13] <Volkodav> https://help.ubuntu.com/community/MacBookPro
[21:15] <Volkodav> looks like maverick is all dandy on your laptop - I have lucid on MBP5.2 running perfect as well
[21:15] <Volkodav> There is a section about sensors too
[21:15] <gnomefreak> well i figured out why unity wont load, new computer will fix that i hope
[21:28] <charlie-tca> um, Ubuntu live cd gives a message in VBox 4 today...
[21:29] <charlie-tca> You do not have 3d capability, please restart and choose classic desktop
[21:29] <charlie-tca> Unfortunately, restarting still doesn't let me choose the desktop on the live cd!
[23:49] <cozziemoto> yofel,  ok did a test...first install I used the 6600gt  did updates...rebooted...changed  grub  ..shutdown...swapped cards for the 7300gt   and all worked well...  just reinstalled with the 7300gt..did updates  ,,,,changed grub...rebooted...and although I am not getting that same issue it is now booting to black screen with blinking marker
[23:49] <cozziemoto> any suggestions?
[23:54] <smallfoot-> wayland is not in repo?


[00:00] <workthrick> jelmer: thanks for your help, I'll come with more substantial questions tomorrow or thereabouts
[00:00] <jelmer> workthrick: sure
[00:04]  * workthrick reboots
[00:17] <poolie> hi all
[00:19] <jelmer> 'morning poolie
[00:20] <poolie> hi jelmer
[01:06] <spiv> Good morning
[02:19] <wgrant> spiv, poolie: We had some odd branch corruption on the db-devel builder on Friday.
[02:20] <wgrant> http://people.canonical.com/~wgrant/launchpad/pygettextpo.tar.gz is the branch. An upgrade to 2a works, then pulling lp:~launchpad-pqm/pygettextpo/trunk crashes with BzrCheckError: Internal check failed: Cannot add revision(s) to repository: missing referenced chk root keys: [StaticTuple('sha1:d34f39faee56e120a83e7cec4fe01c4fd5fd32f6',)]
[02:20] <wgrant> A fresh checkout works fine.
[02:21] <wgrant> Still broken on a daily 2.4 build.
[02:26] <spiv> wgrant: hmm
[02:27] <wgrant> Yes.
[02:27] <spiv> I don't think we've had a report of that error from a fresh upgrade before.
[02:27] <wgrant> check/reconcile are happy.
[02:27] <wgrant> So perhaps the remote branch is bad or something...
[02:28] <spiv> Oh, it's probably not upgrade then, problem an issue in the remote
[02:28] <wgrant> Only just saw that they're happy now.
[02:28] <wgrant> But the remote branch hasn't changed in a year...
[02:29] <spiv> *or* if the remote is fine in isolation too (passes check), then you've possibly got a example that pinpoints a bug in fetch.
[02:30] <spiv> Oh, if the remote is that old, possibly it has the non-canonical-chks issue
[02:30] <spiv> wgrant: try 'bzr check-chk' from the lp:bzr-repodebug plugin on the remote
[02:32] <wgrant> Hmmmmmm.
[02:32] <wgrant> bzr was upgraded in devel recently.
[02:32] <wgrant> But one revision after what's in db-devel at the moment.
[02:33] <wgrant> Rather suspicious timing.
[02:33] <spiv> wgrant: ah, yes, check-chk finds *many* issues in lp:~launchpad-pqm/pygettextpo/trunk
[02:33] <wgrant> I don't see how the db-devel slave would be using the devel bzr, though...
[02:34] <wgrant> spiv: How do we fix that?
[02:34] <spiv> bzr reconcile --canonicalize-chks
[02:35] <spiv> (it's a hidden option, it's specifically for repairing damage from bug 522637)
[02:35] <wgrant> Time for some PQM fun, I guess...
[02:35] <wgrant> Thanks.
[02:35] <spiv> And must be run on the actual damaged repo, not just done elsewhere and pulled, due to the nature of the problem.
[02:35] <wgrant> Yep.
[02:36] <spiv> It's pretty impressive, actually.
[02:36] <spiv> I'm not sure I've seen a branch with so many non-canonical-form CHK maps before!
[02:39] <spiv> wgrant: thanks for reminding me of that issue!
[02:39] <spiv> wgrant: I just realised it accounts for some package import failures :)
[02:39] <wgrant> spiv: Ah!
[02:50] <poolie> hi spiv, wgrant
[03:16] <spiv> Hmm.
[03:16] <spiv> Non-canonical CHKs were *part* of what was breaking libffi
[03:16] <spiv> But there's still something funky going on.
[03:51] <poolie> lifeless: in https://code.launchpad.net/~mbp/bzr/220464-stale-locks/+merge/62582 what do you mean by something stronger?
[04:53] <lifeless> poolie: well, you mentioned putting a machine identifying hash in or something
[04:54] <poolie> mm
[04:54] <poolie> it could go in /home
[04:54] <poolie> a lot of the problem cases have shared disks so that may not help
[06:31] <shadeslayer> https://code.launchpad.net/~neon/+recipe/project-neon-calligra << bzr runs out of memory on that recipe, could someone look at it? IIRC this bug was fixed a couple of months ago right?
[06:33] <spiv> shadeslayer: well, bzr memory usage has typically been improving with every major release
[06:33] <shadeslayer> spiv: i agree, but that branch is like 97 MB's in xz format :)
[06:33] <spiv> Whether that means your particular out of memory case has been fixed I couldn't immediately say.
[06:34] <shadeslayer> any ideas when it'll be able to build that particular size?
[06:34] <spiv> Depends on what the problem is, and what version of bzr (and maybe bzr-builder) the buildslave is running.
[06:35] <shadeslayer> i guess, whatever launchpad uses
[06:35] <spiv> It *might* be as simple as getting bzr upgraded there.
[06:35] <spiv> Well, I say âââ"simple" but I'm sure wgrant will correct me...
[06:36] <shadeslayer> well .. the source code import uses git->bzr conversion, but i have no idea what the bzr branch format is ... will look into it later this evening then
[06:37] <spiv> I don't mean upgrading the repo/branch format being used
[06:37] <spiv> Those are already current
[06:37] <spiv> I mean the version of the 'bzr' program being used.
[06:37] <shadeslayer> ah
[06:38] <poolie> i think jelmer and others  have a project underway to upgrade bzr
[06:38] <poolie> i don't think it's all done yet
[06:42] <poolie> according to https://code.launchpad.net/ lp is still using bzr 2.2.3
[06:43] <fullermd> Headers: {'Software version': '2.2.3dev'}
[06:45] <spiv> I don't think the PPA builders are necessarily using the same version of bzr as the rest of Launchpad.  I might be wrong.
[06:50] <wgrant> poolie, spiv, shadeslayer: The bzr upgrade has landed, and I'm QAing it now. Will be deployed in a couple of days.
[06:50] <wgrant> But spiv is right.
[06:50] <wgrant> The buildds don't use the same version.
[06:50] <wgrant> They use packages.
[06:50] <wgrant> I may converse with lamont.
[06:52] <lifeless> poolie: re: locks - I want to avoid us trashing repositories in the lp deployed configuration which will be N hosts, one cluster FS for storage
[06:53] <poolie> i want that too :)
[06:54] <poolie> having multiple hosts, one filesystem should be safe
[06:54] <poolie> s//should actually be safe in the patch as proposed
[06:54] <poolie> i'm going to check the server side behaviour though
[07:10] <spiv> shadeslayer: and fwiw that branch is much larger than your xz'd 97MB.  'du -hs .bzr' says 509M.
[08:09] <maxb> spiv: Hi. Do you think I should file a bug for "Please upgrade bzr-builddeb on jubany", or is it not worth the process?
[08:10] <maxb> We should be in the clear to redo the sysvinit import as soon as current trunk of builddeb & udd are deployed, which would be nice, as it's a user request
[08:11] <spiv> Hmm, a lot of changes since r494
[08:12] <maxb> oh yes :-)
[08:14] <spiv> It sounds like a good idea, and I think I'd be happy to just do it, but not at 5pm :)
[08:14] <spiv> So probably worth filing a bug
[08:14] <maxb> rihgt
[08:21]  * maxb is intrigued by the cpuarrayd failur
[08:22] <maxb> Somehow the importer has decided to import a package name which does not exist
[08:23] <spiv> maxb: yeah, I was wondering about that one too
[09:27] <poolie> hello vila
[09:28] <vila> poolie: hey !
[09:28] <poolie> hi
[09:28] <poolie> :)
[09:28] <poolie> i like your mails-
[09:28] <poolie> i might need subtitles though :)
[09:29] <vila> http://www.youtube.com/watch?v=CN666q3ptAU
[09:30] <vila> :)
[09:34] <vila> poolie: corrections welcome nevertheless ;)
[10:05] <poolie> vila so actually more seriously i don't know what spam you're talking about
[10:06] <poolie> did people object to the previous message/
[10:07] <vila> hmm, right, so what's the saying about explaining jokes ? ;)
[10:08] <vila> this was just a way to roll the drums about the policy change, people should know that there is something going on with reviews and subscriptions by now
[10:09] <vila> I probably viewed too much monty python lately: http://www.imdb.com/title/tt0071853/crazycredits
[10:09] <poolie> i like the humour
[10:09] <poolie> i think perhaps a subtitle saying what's actually happening would help
[10:10] <vila> right, the link to maxb message was supposed to give the serious info
[10:11] <poolie> well, just something to think about
[10:33] <poolie> vila, whoa, you sent through my stale lock branch?
[10:33] <poolie> i was just drafting a reply to robert
[10:33] <vila> mgz approved it...
[10:33] <vila> :-/
[10:33] <poolie> i think it's probably ok but i was going to look at it again
[10:33] <vila> did I miss a reply from Robert ?
[10:33] <poolie> i do appreciate you trying to flush the queue
[10:34] <poolie> he asked if it's safe wrt server side operations
[10:34] <vila> May be I over interpreted but I read mgz's last comment as: that's fine as it is, we can do a further proposal
[10:35] <vila> poolie: oh right, but this won't be deployed on lp then ?
[10:36] <poolie> why not?
[10:37] <vila> meh, if you think you need a further proposal, this don't *have* to be deployed on lp
[10:37] <vila> if you're ok, I don't have objections myself
[10:38] <poolie> well
[10:38] <poolie> on the whole we should probably land it and perhaps do follow up
[10:38] <poolie> i wouldn't mind brainstorming other things we could check, with you
[10:40] <poolie> what do you think we should do about matching up the host names?
[10:42] <poolie> i'm tempted to also ask a losa to kill the pqm job until we're agreed on how to do it
[10:47] <vila> how about a grace period before stealing the lock ?
[10:48] <vila> The issues you and Robert raised still exist with break-lock no ?
[10:50] <poolie> ok, i replied
[10:50] <poolie> a grace period could be another option
[10:50] <vila> I can't think of a good way to make the host name check stronger that can't be defeated either so I'm not sure about that
[10:54] <poolie> ok, good night!
[10:54] <vila> g'night !
[10:59] <vila> poolie: pqm failure anyway, so no worries
[11:00] <jelmer> g'night poolie
[11:07] <lifeless> vila: poolie: re: landing and iterating; If landing something that makes server deployment risky, how would we identify that this blocks a release/deploy to lp ?
[11:08] <lifeless> not saying you should or shouldn't, just wondering what the process to avoid mistakes further down the line is
[11:12] <vila> lifeless: add more tests ? ;) Anyway, there was a pqm failure for this proposal so it didn't land
[11:38] <bigjools> hi all, I'm doing a "bzr shelve --all" and getting this error, what can I do to fix it?
[11:38] <bigjools> bzr: ERROR: Could not acquire lock "/home/ed/canonical/lp-branches/copies-must-use-queue-bug-789502/.bzr/checkout/dirstate": [Errno 11] Resource temporarily unavailable
[11:39] <jelmer> bigjools: there's no other bzr instance trying to access that branch at the same time?
[11:39] <bigjools> jelmer: I hope not, I've not touched bzr since I booted the box, that's the first thing I typed
[11:40] <bigjools> ah, there's a bzr grep running ...
[11:40] <bigjools> jelmer: that was it :/
[11:40] <bigjools> I didn't think it'd do an exclusive lock
[11:40] <bigjools> thanks
[11:41] <jelmer> not one of our best error messages..
[11:41] <bigjools> no :)
[12:09] <quicksilver> does anyone use reviewboard with bzr? or alternatively, have suggestions on tools in this area? That is, support for code review workflows
[12:10] <ScottK> quicksilver: I've used it.
[12:11] <quicksilver> ScottK: works well?
[12:11] <ScottK> You need a patch and then it works.
[12:11] <ScottK> Let me see if I can find it.
[12:11] <quicksilver> the bzr-diff-revid stuff?
[12:12] <ScottK> Yes.
[12:12] <quicksilver> found that already in my initial researches.
[12:12] <quicksilver> trying to find a bit of automation for a good merge-request/code-review workflow.
[12:12] <ScottK> There's also a patch to rbtools we needed.
[12:13] <ScottK> I think that may just be because we were on an older version.
[12:14] <quicksilver> I really want something which can work on the output of "bzr merge --preview"
[12:14] <quicksilver> that is, the diff between unmerged branches.
[12:14] <quicksilver> most code review tools seem to want to work on diffs between versions of a particular branch
[12:15] <ScottK> I don't think I've used it that way.
[12:16]  * quicksilver nods
[12:16] <quicksilver> maybe my workflow is odd
[12:16] <quicksilver> but I like to review changes before we pull them into mainline.
[12:17] <spiv> quicksilver: that's not odd at all; it's how Launchpad's code review workflow works for example.
[12:17] <quicksilver> spiv: hmm maybe running an internal launchpad instance is a better idea then?
[12:17]  * quicksilver tries to google info about lp code review
[12:18] <spiv> quicksilver: but I guess the thing is if you have a branch that's simply a bunch of revisions on top of the target branch (i.e. no merges from the target onto the branch-for-review part way through its new commits) then diff-between-versions-of-branch is the same.
[12:19] <quicksilver> right. but we always have those (merges from target onto branch-for-review)
[12:19] <quicksilver> apart from anything else it's the branch-developers obligation to keep testing against latest mainline and ensure there are no conflicts
[12:19] <quicksilver> so there should be regular merges in that direction.
[12:19]  * spiv nods
[12:20] <quicksilver> spiv: seems lp code review gives you a workflow and an interface to browse merge candidates, btu doesn't actually support the process of annotating the diffs?
[12:21] <spiv> It gives you a place to add comments about the whole diff, but no way to directly annotate a part of the diff with a particular comment, no.
[12:21]  * quicksilver nods
[12:21] <quicksilver> currently I review the entire output of bzr merge --preview in emacs, make notes and then discuss those notes with the developer.
[12:21] <spiv> (I think there was some discussion recently about maybe adding something like that)
[12:21] <quicksilver> it works OK but I was wondering if I could automate some of those parts
[12:22] <quicksilver> and having it on the intranet lets the rest of the team get some idea what's going on
[12:22] <quicksilver> which is nice.
[12:22] <spiv> My usual way to do reviews with Launchpad is I get the email sayingg
[12:22] <spiv> "review this, here's the diff" and I reply to that email, quoting the bits of the diff I'm commenting on and following them with my remarks.
[12:23] <spiv> s/to do/I do/
[12:23]  * quicksilver nods
[12:23] <spiv> I don't mean to suggest my preferences are universal :)
[12:23] <spiv> Part of the difficulty of directly annotating LP's diffs is that they are updated automatically as the branch changes
[12:24] <spiv> So the comments on a review may be interleaved with "New revision: Add more comments, fix typo." etc
[12:25] <quicksilver> spiv: reviewboard (which ScottK and I were just discussing) claims to understand about different versions of diff.
[12:25] <quicksilver> I'm not sure what it looks like in practice.
[12:26] <spiv> I'm not either, I haven't taken a close look at reviewboard recently at all.
[12:27] <ScottK> I think you'll have to try it to know if it fits your workflow.
[12:29]  * quicksilver nods
[14:32] <niemeyer> Greetings!
[14:33] <niemeyer> I faced an issue with bzr over the weekend that prevented importing some code on it.  Wondering if someone already had a look at something similar:
[14:33] <niemeyer> bzr: ERROR: An inconsistent delta was supplied involving '<unknown>', 'hg:usr_sgri'
[14:33] <niemeyer> reason: Parent is not present in resulting inventory.
[14:34] <niemeyer> This was a simple non-fancy import of about 8600 revisions, just one commit after the other
[14:40] <niemeyer> This seems to be the same bug as this one:
[14:40] <niemeyer> https://bugs.launchpad.net/bzr-hg/+bug/513368
[14:41] <niemeyer> What surprised me is that I'm hitting the bug just with plain command line interaction
[14:54] <maxb> niemeyer: It's not that surprising, bzr-hg is somewhat less developed that other bzr foreign plugins
[14:55] <niemeyer> maxb: I'm not using bzr-hg
[14:55] <niemeyer> maxb: bzr is crashing all by itself
[14:56] <niemeyer> maxb: I go 8600 revisions doing "bzr add; bzr remove; bzr commit"
[14:56] <niemeyer> and the resulting repository has this bug
[14:57] <maxb> The string 'hg:usr_sgri' from your error message is *highly* suggestive of bzr-hg being involved
[14:57] <niemeyer> maxb: Ouch.. maybe the plugin is kicking in just because there's an .hg directory?
[14:57] <maxb> Entirely possible
[14:57] <niemeyer> Ugh
[14:57] <niemeyer> Ok, that'd explain a lot
[14:58] <niemeyer> maxb: ...and I had it installed. I'll try to reproduce the bug without it, but it looks like you're right. That was very helpful, thanks!
[15:17] <niemeyer> maxb: OMG.. not only it works, but it's also several orders of magnitude faster
[15:17]  * niemeyer hugs maxb
[15:17] <maxb> :-)
[15:17] <maxb> Did you try using bzr-hg to import the branch first?
[15:18] <maxb> It would be somewhat simpler than an add/commit loop
[15:29] <gour> reddit story about bzr - http://www.reddit.com/r/programming/comments/hseul/do_you_like_bzr_were_working_on_the_github_for/
[15:37] <asabil> mergebox sounds like something that would probably help increasing bzr adoption
[15:45] <niemeyer> maxb: Heh
[15:46] <niemeyer> maxb: I'm sure it's simpler when it works
[15:46] <niemeyer> maxb: This bug is around for more than a year
[15:56] <shadeslayer> wgrant: thanks!
[15:56] <shadeslayer> spiv: alright, i
[15:56] <shadeslayer> +i'll test it out when its rolled out
[16:08] <shadeslayer> wgrant: is the new bzr out on production servers?
[23:18] <poolie> hi maxb, all
[23:18] <maxb> hello
[23:27] <jelmer> hi poolie, maxb
[23:29] <poolie> hey there
[23:35] <wizonesolutions> Anyone know if Bazaar has something similar to git-submodule?
[23:44] <lifeless> there is a plugin


[07:58] <MooDoo> howdy all
[08:47] <brobostigon> morning boys and girls.
[08:47] <MooDoo> morning brobostigon
[08:48] <brobostigon> morning MooDoo
[08:48] <MooDoo> how are you brobostigon ?
[08:49] <brobostigon> not bad, and you?
[08:49] <zmoylan-samj3> morning mammals
[08:49] <MooDoo> brobostigon: yeah good thanks
[09:49] <diplo> Morning all
[09:51] <daftykins> \o good morn
[09:53] <zmoylan-samj3> o/
[09:54] <daftykins> there are folk working on my house again \o/
[10:01] <diplo> Not good... but hey :) stag weekend has ruined me
[10:35] <daftykins> ooh-err
[10:35] <daftykins> diplo: was it your own?
[10:45] <diplo> Nah, not sure I'd go through that marriage thing again
[10:46] <diplo> A friends, although he's 10 years younger than me and so are all his friends, I'm 41, the youngest there was 26/27
[10:46] <diplo> They were all ruined :)
[10:50] <daftykins> tsk tsk
[10:57] <bigcalm> o/
[10:58] <daftykins> morn
[11:01] <diplo> Good experience though, in my day we didn't do these abroad stag do's - was beautiful in Barcelona, and oh my, the ladies...
[11:06] <daftykins> haha i see, i remember a mate getting pickpocketed in Barcelona's gothic quarter
[11:15] <diplo> yeah, a lad lost a phone but we think he was pick pocketed, he was to drunk to know though
[11:16] <daftykins> mmm my telco text me on the last trip to Spain warning about phone theft
[11:16] <daftykins> ho-hum
[13:08] <awilkins> Heh, this is why I keep my Moto RAZR in my sock drawer.
[13:08] <awilkins> Stag Weekend Phone.
[13:08] <awilkins> It's been there for 8 years now :'-(
[13:37] <foobarry> looking for a reasonably secure LAMP solution for a file repository that allows users to upload files and set permissions for others to access the files etc
[13:38] <m0nkey_> nextcloud with the 'group permissions' plugin?
[13:39] <foobarry> probably something like the web only aspect of owncloud's file mamangement, which makes me think there must be simpler tools out there
[13:51] <m0nkey_> what about seafile?
[13:51] <m0nkey_> It's self contained, doesn't require apache or anything.
[14:24] <diplo> awilkins: or just don't get so drunk you don't understand what's going on :)
[14:31] <zmoylan-pixi> then why have a stag party??
[15:01] <diplo> I don't need to be blind drunk to have a laugh and enjoy myself :)
[15:24] <zmoylan-pixi> me neither, but getting pics pf your mates who do can fund your retirement... :-)
[15:57] <diplo> You really don't want to see the photos scrolling through the whatsapp group
[16:38] <foobarry> "“An unauthorised voucher code has been used on this transaction”. - reason for not getting my cashback :|
[16:38] <foobarry> For future reference, any code that is used, but is not advertised by ourselves, on a merchant''s page, on our site, is likely to invalidate your cashback.
[20:05] <penguin42> there's a new Manc<->Leeds bus service doing £1 journeys this week
[20:06] <daftykins> crikey
[20:06] <daftykins> that's the price over here to ride a bus
[20:07] <penguin42> the normal price will be £9/return
[20:08] <penguin42> but Leeds is a nice city and I'm on hols this week
[20:09] <daftykins> huzzah!
[20:09] <daftykins> i still haven't been truly north
[20:10] <penguin42> how North have you got?
[20:11] <daftykins> err, hmm i might have to consult a map
[20:11] <daftykins> it begins with B north of London, but i forget
[20:11] <daftykins> Bedford, there we go
[20:11] <Richard_Cavell> Hi everyone!
[20:12] <daftykins> hello
[20:12] <penguin42> daftykins: Similarly I don't go south very often
[20:12] <Richard_Cavell> I'm from St Anne's, near Blackpool in the northwest
[20:13] <penguin42> Richard_Cavell: Ah with your windmill
[20:13] <daftykins> ah ha, i'm in the Channel Islands
[20:15] <Richard_Cavell> windmill?  I don't know any windmill
[20:15] <penguin42> Richard_Cavell: https://photos.app.goo.gl/U0PbwhnIO54tQwCk2
[20:16] <Richard_Cavell> oh that damn thing
[20:16] <Richard_Cavell> I've been there. There's nothing impressive about it
[20:17] <daftykins> it's got some wiggly lines on it
[20:17] <daftykins> so there's that
[20:18] <Richard_Cavell> yep
[20:18] <Richard_Cavell> And it's painted white
[20:20] <penguin42> Richard_Cavell: Well yes, it's the only landmark I know in Lytham
[20:23] <Richard_Cavell> I use Ubuntu, gcc, make, VICE-emu, mame, and I'm learning C, C++ and vintage computers
[20:24] <daftykins> funky
[20:32]  * penguin42 sends Electricity north west a message asking why I was notified of a power outage when I didn't have one
[20:33] <penguin42> I mean that's the better direction, but still odd
[20:33] <daftykins> *lights die*
[20:33] <penguin42> daftykins: 'Yeh, we've now addressed the problem and caused a power outage'
[20:33] <daftykins> :D
[20:46] <penguin42> hmm, I bet they've still got me down as the contact number for the company I was IT manager for ~10 years ago
[20:47] <penguin42> but hmm, they don't show any outages there either
[23:17] <diddledan> that windmill seems lop-sided
[23:19] <penguin42> it's seen better days
[23:20] <daftykins> still 50% effective!
[23:20] <daftykins> maybe
[23:21] <diddledan> so you only get half a bag of flour instead of a full one?
[23:21] <daftykins> yep
[23:21] <daftykins> the rest is made up of squiggles
[23:25] <diddledan> I believe those are called weavils


[06:17] <RaymondX1> testing
[06:18] <RaymondX1> testing
[06:21] <RaymondX> testing
[06:27] <RaymondX> testing
[06:32] <RaymondX> testing
[10:49] <zakame> hola


[00:26] <valorie> just sent out the email asking for testers
[00:26] <valorie> not sure how much we want to publicize this?
[00:30] <tsimonq2> valorie: a lot
[00:31] <tsimonq2> <shameless plug> asknoahshow.com is tonight at 9 PM, he'll be talking about it :) </shameless plug>
[00:31] <valorie> cool
[00:31] <valorie> well, would could put it on the website
[00:32] <valorie> it was so hush hush until now I didn't know
[00:32] <valorie> and the kernel patch is not yet available, correct?
[00:35] <wxl> keep an eye out for anyone that has problems with their machine because of Dot One
[00:35] <wxl> there are solutions, even if it appears BIOS is borked
[00:37] <valorie> like what, wxl?
[00:37] <valorie> I thought it required a bios flasher gizmo?
[00:37] <wxl> no
[00:37] <wxl> the problem was caused by flipping the wrong bit. flipping the bit back can fix it and you can do it with software
[00:38] <wxl> you can also do it with a flasher, but that's not required
[00:38] <valorie> so why is that not being done in the respin?
[00:38] <wxl> it is
[00:38] <wxl> but whether or not it's been fully tested on every single piece of hardware it could affect?
[00:38] <valorie> so then, why would people have a problem?
[00:38] <valorie> got it
[00:38] <wxl> it affected 3 chipsets and like 20 different serial flashes
[00:39] <valorie> so how would a person fix the problem if their BIOS was borked?
[00:39] <wxl> admittedly though this update should also NOT include any SPI stuff, so if it's not broken they shouldn't be again, but who knows
[00:39] <wxl> can't save BIOS settings
[00:39] <wxl> can't boot to USB
[00:39] <wxl> e.g.
[00:40] <valorie> if there is even a chance I will not be using this machine to test
[00:41] <wxl> again, the issue was caused by the SPI being compiled into the kernel and that in turn having some bugs in it that caused issues
[00:41] <wxl> since then, there have also been improvements to the module to repair issues
[00:41] <wxl> BUT the new stuff should not even have SPI compiled in
 Lubuntu published a blog post including an FAQ: http://lubuntu.me/lubuntu-17-04-eol-and-lubuntu-17-10-respins/
 It's licensed under https://creativecommons.org/licenses/by-nc-nd/4.0/ so feel free to grab it and give us credit ;)
[00:44] <valorie> thank you
[00:44] <valorie> I have some other stuff cooking so perhaps tomorrow!
[00:44] <tsimonq2> Awesome :)
[00:44] <tsimonq2> valorie: The only thing is it's noderiv so you have to quote it word-for-word
[00:44] <valorie> pfff
[00:44] <valorie> that I will not do!
[00:45] <valorie> you do a good job of lubuntu missionary work on your own
[00:45] <tsimonq2> Put it in quotation marks and then give us credit, that's what the license is ;)
[00:46] <valorie> well, your info is not my info so I'll have to be "inspired by" instead
[00:46] <valorie> :-)
[00:46] <tsimonq2> Right :)
[00:46] <tsimonq2> Or you could link to our post ;)
[00:46] <valorie> I will
[12:11] <BluesKaj> Hey folks
[13:27] <mparillo> Hey BluesKaj. New spins of 17.10 are out to address the BIOS bug. In a VM, I tested the whole disk test cases. I know you have done partitioning in the past.
[13:39] <BluesKaj> mparillo, i haven't seen the UEFI/BIOS bug on my laptop
[13:39] <BluesKaj> on 17.10
[13:40] <mparillo> I sure hope not. As far as I know it most commonly hits consumer-grade Lenovos. But valorie sent a e-mail last night asking us to treat it as a release candidate.
[13:40] <acheronuk> BluesKaj: testing is not for the bug. just to make sure the new iso doesn't regress on the usual iso tests
[13:42] <acheronuk> from release " No need to test on affected machines, we're 99.783% sure that not compiling in the spi driver into the kernel at all will prevent that driver from breaking your bios"
[13:43] <BluesKaj> well my Lenovo G500 is a consumer grade laptop
[13:47] <BluesKaj> mparillo, I normally prepartition with gparted and use the manual partitioning when installing to / and then setting the /home mount point
[13:48] <BluesKaj> guess I'm missing the point about the kernel causing the bios to break
[13:50] <mparillo> I do not think any of us can creditably test that bug...It is more a sanity check that 17.10.1 is basically as good as 17.10 was.
[13:52] <acheronuk> also, it's not mandatory that flavours do these QA tests. but it's best policy for our users to run them
[15:58] <DarinMiller> I can test 17.10 iso.  Is download location hidden or is it just the standard download location?
[15:59] <acheronuk> DarinMiller: http://cdimage.ubuntu.com/kubuntu/artful/daily-live/20180105.2/
[15:59] <acheronuk> the link on the iso tracker is broken
[16:00] <acheronuk> hopefully will be fixed later
[16:00] <acheronuk> thanks :)
[17:00] <blaze> any chance lp builder will be up online soon?
[17:20] <acheronuk> blaze: [22:10] <cjwatson> we'll hopefully be able to get things running again early next week; apologies for the inconvenience
 @acheronuk> blaze: [22:10] <cjwatson, few days to go ...


[06:07] <dlfmf> I have chosen the "vanilla gnome system" during install, but there is nothing installed
[06:08] <dlfmf> bare console