[00:59] <lazyPower> hnix: o/
[01:00] <lazyPower> there's some interesting behavior at play here with the rails charm. In its current incantation - rbenv is being used as a "wrapped command" - meaning it only exists within teh context of the charm hooks. This has some implications with the current documentation, and usage patterns
[01:00] <lazyPower> hnix: what i suggest is attempting to do the following: "juju run rake db:migrate" instead of juju ssh - if that fails, there is a rewrite in progress of moving the rails charm from rvm to rbenv
[01:01] <lazyPower> and i dont have an ETA on when I will be finished with that, however - all contributions/testing are welcome :)
[01:04] <hnix> LazyPower : Thank u !
[01:05] <lazyPower> hnix: if you're interested in following along with that migration effort i have a github branch you can watch - https://github.com/chuckbutler/rails-charm/tree/rbenv_migration
[01:08] <hnix> im a new GoLang Programmer about 2 weeks ago. i want really to contribute on an effort to extend my programming skills .... this is way im playning with this project ( #juju ) so i want learing basics as soon as possible then contribute activly in such as project or docker
[01:09] <lazyPower> We welcome all the help we can get hnix. Are you looking to learn how juju works then contribute to juju-core?
[01:09] <hnix> lazypower : i will check this now and see ! i appreciate any advice
[01:11] <hnix> lazypower : Yeah i want to contribute to juju-core
[01:11] <jw4> hnix: welcome - have you checked out CONTRIBUTING.md in the juju-core repo?
[01:11] <thumper> hnix: o/
[01:11] <thumper> hnix: what sort of contributions are you interested in offering?
[01:11] <thumper> hnix: what floats your boat?
[01:16] <hnix> lazypower : yeah i checked it CONTRIBUTING.md + i cloned the git repo ... any taks that i can do i will do it ... fo now i dont know what but, along my learning and Juju discovery i will figure out what type of contribute i can
[01:16] <lazyPower> hnix: jw4 and thumper are both core contributors. They're helpful in finding bitesized bugs to fix :)
[01:17] <lazyPower> we have a fairly large landscape in terms of contributions - juju-core is great if you want to sharpen your go, or if you're looking for general contributions we have a large collection (260 +) of charms (services) that are always up for contributions of any kind, between docs to actual orchestration logic contributions
[01:18] <lazyPower> hnix: if you're main focus is to contribute to core, reading the Contributing doc and joining #juju-dev would be my recommendation. Learn the lay of the land - find your first bitesized bug and dive in.
[01:18] <jw4> hnix: bit of a firehose, but this is the list of high priority bugs in juju-core https://bugs.launchpad.net/juju-core/+bugs?search=Search&field.importance=High&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed
[01:20] <hnix> Whoaa! take it easy men ... im a new Golang dev. you scaring me  +_+
[01:20] <jw4> hnix: once you're able to build and run all the tests you should be ready to start tackling bugs ;)
[01:21] <jw4> hnix: lol - I think lazyPower may know of some charms that are written in Go (right lazyPower ?) those might be bite sized too
[01:21] <lazyPower> we dont have charms in go atm
[01:21] <lazyPower> but it would be an interesting take on charming
[01:21] <hnix> is this a fast track to dive in a new lang.
[01:21] <jw4> lazyPower, hnix strike that then
[01:21] <sarnold> ISTR someone gave that a shot a few months back..
[01:21] <lazyPower> natefinch i think
[01:21] <lazyPower> or at least he was talking about it
[01:22] <lazyPower> my problem with a golang charm is how do you debug a binary when things go sideways?
[01:22] <jw4> hnix: there is some good go code in juju-core, but it is fairly sophisticated - depends on how big of a bite you want to take I guess
[01:22] <sarnold> lazyPower: yeah, I wouldn't want to maintain it myself :)
[01:22] <jw4> lazyPower: +1
[01:22] <lazyPower> jw4: would be good if we had some small things like localizations, or output corrections.
[01:22] <lazyPower> tag those as bitsized - as we have a page that links to a zero output bug tracker list
[01:23] <lazyPower> https://juju.ubuntu.com/resources/easy-tasks-for-new-developers/ <-- the juju-core list is empty
[01:23] <jw4> lazyPower: yeah - that's a great idea.   Hmm...
[01:23] <sarnold> this one feels like it's probably approachable by a new dev https://bugs.launchpad.net/juju-core/+bug/1420057
[01:23] <mup> Bug #1420057: agents see "too many open files" errors after many failed API attempts <juju-core:Triaged> <https://launchpad.net/bugs/1420057>
[01:24] <hnix> Lazypower : so  trynig out with Charms is easy to beging with ? than the juju-core
[01:24] <sarnold> strace agents to find out which operations open but don't close file descritprors...
[01:24] <hnix> it it the case ( advice )
[01:24] <lazyPower> hnix: charms aren't go-lang specific, but they are a great place to start contributing
[01:24] <lazyPower> sarnold: you love pain
[01:25] <sarnold> lazyPower: I figured it wouldn't take much 'internal' knowledge of juju to get started on it
[01:25] <sarnold> lazyPower: .. and perhaps the agents are easier than the orchestrator
[01:25] <lazyPower> thats a fair assumption
[01:25] <hnix> lazypower : hhhhhh we love fast bootstrap
[01:26] <lazyPower> https://bugs.launchpad.net/juju-core/+bug/1273216
[01:26] <mup> Bug #1273216: unknown --series to add-machine breaks provisioner <juju-core:Triaged> <https://launchpad.net/bugs/1273216>
[01:26] <lazyPower> that looks like it would be a good one to add to as well - as you can define a list of we support, and do dict lookup
[01:26] <sarnold> oh, that one looks easier
[01:26] <sarnold> juts on a blind guess, anyway :)
[01:30] <lazyPower> https://bugs.launchpad.net/juju-core/+bugs?field.tag=bitesized
[01:30] <lazyPower> there's some
[01:31] <lazyPower> https://bugs.launchpad.net/juju-core/+bug/1320218 - probably being the easiest out of all that i found... yaml lint + error message
[01:31] <mup> Bug #1320218: can't read environment file no hint of actual yaml error <bitesize> <config> <ui> <juju-core:Triaged> <https://launchpad.net/bugs/1320218>
[01:32] <hnix> lazypower : i think that i follow https://github.com/chuckbutler/rails-charm/tree/rbenv_migration : 1 week ago and also the steps do not  work for me . it think it a bad start with .
[01:32] <sarnold> maybe... I can imagine getting a few of those cases would be easy but 'solving' that in full generality might take some work
[01:33] <lazyPower> hnix: i'm not sure i parsed that - you tried the branch and it failed yes? thats known - its still WIP as there's quite a bit to be done to fully triage a migration from rvm => rbenv
[01:33] <lazyPower> plus we're going from a localized ruby installation to a system wide rbenv installation that scopes to users so you're not installing system wide
[01:33] <lazyPower> the idea is to move to a 'bullet proof deployment' model where binstubs are used, and localized ruby copies can be embedded in the application itself
[01:34] <lazyPower> i see no reason to 'hide ruby' on the system which is what the current charm does, it creates rvm wrappers - which are nearly impossible to consume outside of the charm hook context.
[01:47] <hnix> the app that im trying to deploy  https://github.com/ziralabs/E-learing-app it's a learning app created to Get  my master Degree in education ... so after that i lunch it public for any one who want to know how to integrate  a REPL build with NodeJS into a Rails APP
[01:49] <stokachu> tvansteenburgh: do you know if python3 version of jujuclient is making its way into the archive soon?
[01:55] <lazyPower> stokachu: hazmat's latest release of jujuclient is py2 and py3 compliant
[01:55] <lazyPower> stokachu: https://github.com/kapilt/python-jujuclient/blob/master/jujuclient.py#L35
[01:56] <lazyPower> oh you asked if it was getting into the archive - sorry jumped the gun there.
[06:21] <toyo|work> I cant seem to get juju to bootstrap on version 1.20.11
[06:22] <toyo|work> Juju cannot bootstrap because no tools are available for your environment.
[09:11] <gnuoy> jamespage, would you mind takine a look at https://code.launchpad.net/~gnuoy/charm-helpers/1422386/+merge/249837 if/when you have a moment ?
[09:32] <jamespage> gnuoy, to my unaware brain it looks OK
[09:34] <stub> gnuoy: Did you fix https://bugs.launchpad.net/charm-helpers/+bug/1423176 with your nrpe landing?
[09:34] <mup> Bug #1423176: test_nrpe tests broken on trunk <Charm Helpers:New> <https://launchpad.net/bugs/1423176>
[09:38] <gnuoy> stub, yes, it fixed and I'm hanging my head in shame for not having spotted the unit test break
[09:45] <Murali> hi jamespage I deployed using lxc like juju deploy --to lxc:0 openstack-dashboard
[09:45] <Murali> my juju status is pending frol long time
[09:46] <Murali> am I missing something here
[09:46] <jamespage> Murali, the first container can take a bit of time on each physical host depending on how fast your internet connection is
[09:46] <jamespage> it was to pull down the right cloud image and unpack it for use locally
[09:47] <Murali> ok
[10:15] <Murali> Hi jamespage
[10:17] <Murali> even when i deploy keystone and dashboard on different nodes, the login prompts an error saying "authentication failed for admin. please try again ".. been stuck on this since some time
[10:18] <Murali> Is there any logs which could give me some hints.. No errors found on juju debug logs
[10:40] <jamespage> Murali, so I'd check the keystone log files (/var/log/keystone) and anything in /var/log/apache (on the dashboard unit)
[10:41] <Murali> On apache , we get a log saying, login failed for user.. and on keystone logs also we couldnt find any thing
[10:42] <jamespage> Murali, OK - so lets bypass the dashboard and make sure that you can actually access keystone from the cli
[10:43] <jamespage> Murali, http://paste.ubuntu.com/10306078/
[10:43] <jamespage> Murali, please adapt that for your environment - specifically the password
[10:43] <Murali> ok
[10:45] <jamespage> Murali, you can then source that file and try a 'keystone catalog' from a command line please
[10:45] <jamespage> Murali, trying to see if you have a keystone problem or a dashboard problem
[10:46] <Murali> Ok
[10:48] <jamespage> Murali, fyi I have a few errands to run in about 15 mins which means you won't get responses from me for about 1.5-2hrs
[10:48] <jamespage> (not ignoring you :-))
[10:49] <Murali> thanks for your helps.. we will try out the steps you mentioned...
[10:53] <jamespage> Murali, I'll ask the question but you have added a relation between keystone and the dashboard right?
[10:53] <jamespage> Murali, just checking ;-)
[10:58] <Murali> yes jamespage added the relation
[10:58] <jamespage> good
[11:11] <Murali> http://paste.ubuntu.com/10306455/ .. this works fine :P
[12:28] <valentyn> Hey, i know that it is possible to deploy to a running juju machine, but is it possible to start a "clean" instance (without any service) and to deploy services to that machine afterwards? thanks
[12:45] <stub> tvansteenburgh: If you are able I'd love another run of lp:~stub/charms/trusty/cassandra/spike on the new Jenkins - I'm hoping all is good now with the 2GB VMs.
[12:45] <tvansteenburgh> stub: will od
[12:45] <tvansteenburgh> do
[12:46] <stub> yeah, please don't OD on me.
[12:46] <tvansteenburgh> hahah
[12:48] <tvansteenburgh> stub: running now
[12:48] <stub> ta muchly
[12:48] <tvansteenburgh> you bet
[13:57] <lazyPower> valentyn: juju add-machine will allocate it in the unit pool, and you can juju deploy --to afterwords.
[15:00] <Crypticus> hello all
[15:00] <Crypticus> I have an issue with Juju I was hoping someone might have some insight
[15:01] <Crypticus> quantum-gateway has bee in the "agent-state: installed" for over 12 hours
[15:01] <Crypticus> I checked the logs and there were no errors.
[15:01] <Crypticus> Is this normal? for this charm? I didn't want to add the relationships until I was sure this was not broken
[15:11] <Murali> hi jamespage
[15:11] <jamespage> Murali, o/
[15:22] <Murali> http://paste.ubuntu.com/10309259/
[15:22] <Murali> we got this error while following the https://jujucharms.com/openstack/
[15:23] <Murali> still installation is going on
[15:37] <Murali> jamespage all the lxc containers status is in pending
[15:37] <Murali> but the internet is at good spped
[15:37] <Murali> speed
[15:37] <jamespage> Murali, does your hardware match the requirements in the README for that bundle?
[15:37] <Murali> is there anything we are missing
[15:38] <jamespage> Murali, I'd drop onto one of the machines and check in /var/log/juju/*
[15:38] <Murali> yes hardware matches 8 gb ram
[15:45] <jamespage> Murali, and the network and disk requirements?
[15:45] <jamespage> Murali, the error you detail above would indicate that maybe your servers don't have two network ports?
[15:45] <Murali> we have 2 disks
[15:45] <jamespage> Murali, good - that enables the ceph bits
[15:45] <Murali> we have 2 nics but name is em1
[15:45] <jamespage> Murali, ah right
[15:45] <Murali> not eth0 and eth1
[15:46] <jamespage> Murali, this is tricky - but not hard to fix - I'd just grab the bundle itself and change it so that the reference to 'eth1' is switch to em1
[15:46] <jamespage> Murali, you can use juju-deployer to deploy the bundle
[15:46] <jamespage> Murali, or you can do a juju set neutron-gateway ext-port=em1 now
[15:46] <jamespage> and then resolve the error
[15:46] <jamespage> juju resolved --retry neutron-gateway/0
[15:46] <Murali> ohh that problem is fine
[15:47] <Murali> But we are seeing the lxc container is in pending state let me send you
[15:48] <jamespage> Murali, ok
[15:48] <jamespage> Murali, checkout the logs in /var/log/juju
[15:48] <Murali> http://paste.ubuntu.com/10309730
[15:48] <jamespage> and checkout "sudo lxc-ls -f" on any of the physical hosts
[15:48] <Murali> ok
[15:50] <Murali> http://paste.ubuntu.com/10309745
[15:56] <Murali> now we are not seeing any activity on debug logs also
[16:02] <Murali> jamespage its late night for us. leaving now I will be  off from network
[16:03] <Murali> thanks a lot for help
[16:03] <jamespage> Murali, hmm - they are not getting ip address - check out the bridge configuration on the boxes - specifically juju-br0
[16:03] <Murali> ohh ok
[16:04] <Murali> so who will allocate IP address for lxc
[16:06] <jamespage> Murali, well actually MAAS and the lxc containers just boot off standard DHCP on the network
[16:06] <jamespage> Murali, are you using MAAS DHCP?
[16:07] <Murali> yes we are using MAAS-DHCP
[16:09] <jamespage> Murali, are you ok for a few minutes - I think we nearly ahve the root cause
[16:09] <jamespage> ?
[16:09] <jamespage> Murali, can you check the bridge configuration - using brctl show
[16:10] <jamespage> juju-br0 should have all of the lxc container ports listed and the right external port - which for your system is em0 I think
[16:10] <Murali> sure jamespage
[16:10] <jamespage> Murali, don't want to keep you from required beer after a long day of hacking :-)
[16:11] <jamespage> beer/<insert your drink of choice here>
[16:11] <Murali> :P
[16:11] <jamespage> hmm beer
[16:11] <Murali> http://paste.ubuntu.com/10310014
[16:12] <jamespage> only 4pm my time
[16:12] <jamespage> Murali, ok this is the problem
[16:12] <jamespage> Murali, can you do me an ip addr on that box as well
[16:12] <jamespage> dimitern, ^^ eek
[16:12] <jamespage> Murali, can you also confirm which juju and maas versions you are using
[16:13] <jamespage> Murali, juju-br0 is normally wired to eth0
[16:13] <jamespage> Murali, but it looks like juju is not dealing well with emX naming
[16:13] <Murali> ok
[16:14] <jamespage> Murali, that's a healthy one - http://paste.ubuntu.com/10310039/
[16:14] <Murali> maas version is 1.5.4
[16:16] <Murali> is there any way to come out of this issue
[16:16] <Murali> or resolve it
[16:17] <jamespage> Murali, probably
[16:17] <jamespage> I'm just pondering it now
[16:17] <jamespage> Murali, also hunting down the juju dev I know who does networking bits like this
[16:18] <Murali> thanks jamespage
[16:18] <Murali> our juju version is 1.21.1
[16:24] <jamespage> Murali, can you also pastebin ip addr and /etc/network/interfaces please
[16:26] <dimitern> Murali, jamespage, hey guys
[16:27] <jamespage> dimitern, Murali is right at the end of day
[16:27] <dimitern> Murali, can you also paste the contents of the maas lshw XML dump of the machine in question (the one done during commissioning by maas)?
[16:28] <jamespage> thanks for helping out dimitern
[16:28] <dimitern> jamespage, np
[16:29] <dimitern> IIRC there was a bug filed about having emX instead of ethX NICs
[16:29] <Murali> http://paste.ubuntu.com/10310220/
[16:30] <Murali> maas lshw and ifconfig are as per the above pated
[16:30] <Murali> maas is reading eth1 eventhough it is em1 in ifconfig
[16:31] <dimitern> Murali, I knew something like that might be the issue
[16:31] <dimitern> Murali, how come that /etc/network/interfaces config is using other names?
[16:32] <dimitern> Murali, is it something done during the node deployment (by maas) or something done later (after juju started on it - maybe a charm?)
[16:32] <jamespage> dimitern, this is a bundle deploy of openstack from the charmstore
[16:33] <jamespage> hey scuttlemonkey
[16:33] <Murali> http://paste.ubuntu.com/10310282
[16:34] <dimitern> Murali, yeah, can you paste the contents of /etc/udev/rules.d/* ?
[16:34] <dimitern> Murali, esp. the persistent net rules
[16:35] <scuttlemonkey> jamespage: hola senor
[16:35] <dimitern> Murali, /var/log/cloud-init*.log will be useful to check as well
[16:35] <jamespage> scuttlemonkey, hows that calamari charm coming along? ;-)
[16:36] <scuttlemonkey> jamespage: hehe, no idea :)
[16:36] <scuttlemonkey> I'm drowning in a sea of bureaucracy...my stack doesn't seem to be getting shorter
[16:37] <jamespage> scuttlemonkey, no worries :-)
[16:39] <jamespage> beisner, not sure that we're testig on tyan's - those are the dev boards
[16:39] <Murali> http://paste.ubuntu.com/10310379
[16:40] <beisner> jamespage, ah good point.
[16:41] <Murali> in "etc/udev/rules/"  we have only README file exists
[16:43] <jamespage> dimitern, I think this is a situation that can occur depending on the type of network cards you are using
[16:49] <Murali> is there any way get rid of this issue jamespage/dimitern
[16:50] <dimitern> Murali, jamespage, well, if it's the NIC drivers that are causing this, you might want to try disabling them and using generic ones
[16:50] <jamespage> Murali, to unblock you I'd suggest rewriting the network configuration manually on the physical servers switching eth0 -> em1 and then restart the networking
[16:50] <jamespage> dimitern, I think this is stock kernel behaviour ;-)
[16:50] <dimitern> jamespage, oh boy :/
[16:50] <jamespage> Murali, you may need to nudge the lxc containers manually
[16:50] <jamespage> lxc-stop --name xxx && lxc-start --name xxx
[16:50] <jamespage> afterwards
[16:50] <dimitern> Murali, yes, s/eth1/em1/ in /etc/network/interfaces + reboot should do the trick
[16:51] <Murali> ok
[16:52] <dimitern> Murali, first try fixing the host machines, then if the containers haven't come up, try juju retry-provisioning 0/lxc/0 (one by one)
[16:53] <dimitern> Murali, alternatively :) you could just change the lshw XML dump for these nodes in maas.. or perhaps use a third-party drivers for your hardware, so maas will properly discover the NICs during commissioning
[16:56] <Murali> Where will be this lshw xml file .. path ??
[16:59] <jamespage> Murali, can you check "apt-cache policy biosdevname" on those machines please?
[17:00] <jamespage> Murali, oh wait - I bet that is installed
[17:00] <jamespage> Murali, dimitern: can you confirm whether your machines where installed with the fast installer? its an option that I think in 1.5.x of MAAS you have to enable
[17:00] <Murali> http://paste.ubuntu.com/10310654
[17:01] <jamespage> Murali, dimitern: I suspect a standard d-i based install installs biosdevname which does this remapping magic
[17:01] <dimitern> jamespage, all 4 of my local maas kvms are using the fast installer
[17:01] <jamespage> Murali, the option is in the MAAS UI - you can turn fast installer on/off for any machine
[17:01] <dimitern> jamespage, good catch! this sounds like the likely cause
[17:02] <jamespage> dimitern, well if it is the cause then yes
[17:02] <jamespage> dimitern, I checked on our MAAS based openstack installs == no biosdevname
[17:02] <Murali> we were not using the fastinstaller till now
[17:02] <jamespage> my local dhcp/dns server installed from usb stick has em1
[17:03] <jamespage> Murali, switching to the fast installer should fix this problem - but we need a bug for this
[17:03] <jamespage> I'll raise one now
[17:03] <dimitern> jamespage, awesome! I'll do a quick test with one of my machines to see if switching off curtin will reproduce it
[17:05] <Murali> jamespage are you suggesting to use "use the fast installer" or default one
[17:06] <jamespage> Murali, use the fast installer for all of them
[17:06] <jamespage> all machines that is
[17:06] <jamespage> Murali, its an image based install - no biosdevname so it should match the data reported in MAAS which juju uses.
[17:08] <jamespage> dimitern, https://bugs.launchpad.net/juju-core/+bug/1423626
[17:08] <mup> Bug #1423626: Inconsistent device naming depending on install method <juju-core:New> <MAAS:New> <maas (Ubuntu):New> <https://launchpad.net/bugs/1423626>
[17:09] <dimitern> jamespage, ta
[17:09] <jamespage> dimitern, I pinged the maas guys as well
[17:10] <dimitern> jamespage, cheers - I'm updating bug 1423372 with this info
[17:10] <mup> Bug #1423372: juju-br0 is not configured correctly on machines without ethX interfaces <jujud> <network> <juju-core:New> <https://launchpad.net/bugs/1423372>
[17:15] <Murali> thanks a lot for great help jamespage/dimitern
[17:15] <Murali> we are now re-bootstraping using the fast installer option
[17:16] <jamespage> Murali, hopefully that will sort you out
[17:16] <Murali> ok
[17:16] <dimitern> Murali, np, glad we could help!
[17:16] <jamespage> dimitern, how about using the mac address to id the interface - then you don't need to worry about renaming
[17:17] <jamespage> dimitern, fyi this will get worse under systemd
[17:17] <jamespage> which I think does all this anyway
[17:19] <dimitern> jamespage, I've responded in #maas as well - I don't know how to discover the NIC name (which I need to generate /etc/n/i file at the time userdata for cloud-init is generated) from its MAC address
[17:22] <jamespage> dimitern, ah yes tricky
[17:23] <jamespage> dimitern, I guess you'd have to inject a script that runs and interrogates the interfaces and then writes the config as part of cloud-init
[17:24] <dimitern> jamespage, good idea - a bootcmd that does that can work not only for maas
[17:40] <lazyPower> o/ tvansteenburgh
[17:40] <lazyPower> can i bother you for a moment regarding what you did yesterday to kick off that passing test? i tried to reproduce it and i got a failure in ci, so i didnt apply the magic tim seasoning
[18:01] <tvansteenburgh> lp|charm-school: looking now
[18:02] <tvansteenburgh> lp|charm-school: actually i'm not sure which build it it, send me a link when you have a sec
[18:03] <tvansteenburgh> s/it it/it is/
[18:03] <jw4> tvansteenburgh: nice palindrome
[18:04] <tvansteenburgh> omg
[18:04] <jw4> hehe
[18:10] <lazyPower> nice!
[18:10] <lazyPower> tvansteenburgh: sure, did you needt he passing build or the repository?
[18:10] <tvansteenburgh> a link to the build that failed
[18:11] <lazyPower> oh :( that i dont have, let me kick it off again and i'll ship it over. sorry - i didnt think to save it
[18:11] <tvansteenburgh> surely we can find it
[18:11] <lazyPower> i think it was build 87
[18:11] <tvansteenburgh> which job name?
[18:11] <tvansteenburgh> the new or old one
[18:11] <lazyPower> nope, thats the pass
[18:11] <lazyPower> 1 sec
[18:12] <lazyPower> http://juju-ci.vapour.ws:8080/job/charm-bundle-test-aws/86/console
[18:13] <tvansteenburgh> lazyPower: ok so that was just before the one that passed
[18:13] <lazyPower> yeah i cannot find the azure job i kicked off that failed, i just realized that was an aws substrate
[18:13] <lazyPower> it vanished...
[18:13] <lazyPower> 88 is a cassandra test
[18:14] <lazyPower> let me kick another oen off and get fresh results, sorry about this :( i should have had that in hand
[18:14] <tvansteenburgh> this one? http://juju-ci.vapour.ws:8080/job/charm-bundle-test-azure/41/console
[18:15] <tvansteenburgh> anyway, feel free to run another one if you want
[18:24] <jw4> Who are the senior architects of Canonicals Openstack strategy that will be presenting the product roadmap in San Fancisco on March 11th?  The OpenStack Roadshow...
[20:19] <hazmat> jw4: probably not the best place to ask
[20:20] <jw4> hazmat: hrm, yeah. (better suggestion?)
[20:50] <hazmat> via pm
[20:50] <jw4> yep, tx hazmat
[22:05] <mbruzek> tvansteenburgh: Can you review https://github.com/juju-solutions/bundletester/pull/11 when you get a chance?
[22:06] <tvansteenburgh> mbruzek: yup
[22:06] <mbruzek> tvansteenburgh: thank you, I am going to change the kubernetes tests to look for the BUNDLE environment variable so our tests run successfully.
[22:09] <tvansteenburgh> mbruzek: merged and jenkins updated
[22:09] <mbruzek> tvansteenburgh: Thank you
[22:09] <mbruzek> tvansteenburgh: just on aws?
[22:09] <tvansteenburgh> mbruzek: no, all
[22:10] <mbruzek> tvansteenburgh: sweet
[22:10] <mbruzek> Thank you
[22:17] <lazyPower> tvansteenburgh: sorry i failed on following up with that job run i got seriously sidetracked. I'll send something over tomorrow morning after i've done my due dilligence
[22:17] <lazyPower> try and sneak that in before you get moving on your daily tasks
[22:17] <lazyPower> o/ enjoy your evening
[22:17] <tvansteenburgh> lazyPower: sure, sounds good , thanks


[04:58] <bullgard4> I obtained a message "panic occurred, switching back to text console". What Natty log file should reflect that?
[05:48] <RedSingularity> hggdh: If the user did not attach a dmesg to a bug that was reported a while ago, could I have them try to reproduce the error again and then attach the dmesg log so its current.  Is there an easier way?
[14:18] <hggdh> RedSingularity: if the dmesg provides critical data, yes.
[15:29] <brendand> https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/799725
[15:29] <ubot4> Launchpad bug 799725 in jockey (Ubuntu) (and 1 other project) ""System policy prevents installation/removal of device drivers" - no it doesn't (affects: 1) (heat: 8)" [Undecided,Confirmed]
[15:29] <brendand> Looks like Importance should be set to Low?
[15:31] <charlie-tca> I agree, but the title should be made more clear
[15:31] <charlie-tca> something like "warning for driver installation is wrong"
[15:33] <brendand> charlie-tca - just updated
[15:35] <charlie-tca> brendand: thanks. done now
[17:55] <bdmurray> cyphermox: I'm having an issue with oneiric and connecting to a wpa2 wireless network
[17:55] <cyphermox> bdmurray: ah! please tell me more
[17:55] <bdmurray> cyphermox: in syslog I'm seeing 'wpa_supplicant .. autentication request to the driver failed'
[17:55] <cyphermox> bdmurray: ok
[17:55] <bdmurray> its using iwlagn for the driver
[17:56] <cyphermox> oh, I was about to ask
[17:56] <bdmurray> and it seems to have worked and then stopped working
[17:56] <cyphermox> did you try to just reboot to see if it did the same?
[17:57] <cyphermox> I've seen this on my system a few times with a different driver... that doesn't necessarily mean it's the same issue though
[18:00] <bdmurray> cyphermox: I'll try that now
[18:03] <cyphermox> bdmurray: sorry I can't offer much more guidance just now. if that works I'd file a bug against the kernel
[18:06] <bdmurray> cyphermox: I do see a kernel message one time regarding 'denied authentication (status 13)
[18:06] <cyphermox> ah
[18:07] <cyphermox> let me try to dig up that status code
[18:23] <cyphermox> bdmurray: I'm not having much luck making sure I got thing
[18:23] <cyphermox> bdmurray: did rebooting help at all?
[18:25] <bdmurray> cyphermox: no, it didn't help
[18:25] <cyphermox> :/
[18:25] <cyphermox> is it with a newly upgraded system?
[18:26] <cyphermox> (or one that hasn't been updated in a while, e.g. hadn't got the NM 0.9 update yet)
[18:27] <bdmurray> it looks like I upgraded on the 6th
[20:09] <cyphermox> bdmurray: have you filed the issue in LP?
[20:12] <bdmurray> cyphermox: not yet - I'd need to go plug in my system
[20:13] <cyphermox> bdmurray: ah ok
[20:13] <bdmurray> cyphermox: I also was thinking about testing it without wpa-psk
[20:13] <bdmurray> cyphermox: what package should I report it on?
[20:14] <cyphermox> bdmurray: file it against NM, its has a fair amount of info with the apport hook, so it's a good start even if we reassign it later
[20:14] <bdmurray> cyphermox: okay, thanks
[20:14] <cyphermox> (so that's "network-manager" )
[21:08] <roadmr> this bug report rocks: bug 799708
[21:08] <ubot4> Launchpad bug 799708 in nautilus (Ubuntu) "greek philosopher on screen (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/799708
[21:10] <paultag> Hahahaha
[21:10] <paultag> I'm so triaging this
[21:10] <joumetal> no screenshot :(
[21:10] <paultag> +1 joumetal
[21:10] <paultag> I'm asking for one now
[21:13] <roadmr> I tried to reproduce locally, no dice - I can't see the philosopher
[21:14] <paultag> roadmr: me neither, but if it's true, this sounds like a high priority bug to me
[21:15] <paultag> He's upgraded since Karmic
[21:15] <paultag> wonder what icon set he's using
[21:29] <charlie-tca> seems to me if a single icon is enough for a a user to say no to ubuntu, it won't matter what anyone does.
[21:29] <paultag> charlie-tca: oh, don't be so serious :)
[21:29] <paultag> he's clearly not :)
[21:53] <bdmurray> cyphermox: I reported bug 799937
[21:53] <ubot4> Launchpad bug 799937 in network-manager (Ubuntu) "unable to connect to a WPA PSK network (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/799937


[04:31] <P3L|C4N0> greetings
[04:32] <LaserJock> hi
[04:42] <nixternal> http://www.kde-look.org/content/show.php?content=51229&PHPSESSID=0d06dc11332341280d5dd4f4e6720974
[04:42] <nixternal> have no idea wth that link is so long compared to others from that site
[04:45] <LaserJock> nixternal: interesting
[04:45] <LaserJock> I certainly appreciate the subject ;-)
[04:45] <nixternal> ya, don't know why it was on kde look, but i figured it was something different
[04:45] <LaserJock> doesn't fit with most edubuntu themes though
[04:45] <nixternal> i don't like the edubuntu text, but the rest isn't all that shabby
[06:02] <dougb> has anyone here used the LTSP feature?
[09:12] <edubuntugirl> HEELP!! HELP!! nixternal wants to steal my RAM!!
[09:13] <highvoltage> relax edubuntugirl. he's on the other side of the planet.


[02:35] <JontheEchidna> oh my: http://www.youtube.com/watch?v=Pube5Aynsls
[02:46] <ScottK> One of those times I'm glad Quassel has web preview so I don't actually click on the link.
[02:49] <JontheEchidna> just be glad the preview doesn't have flash support :P
[02:49] <JontheEchidna> or does it? That'd be annoying
[02:51] <ScottK> It doesn't.
[08:22]  * Sput thinks it does
[09:30] <ScottK> I probably fled in horror before it finished.
[09:54] <Riddell> morning happy testers
[10:00] <Sput> ScottK: I'm not 100% sure, but I think I've seen flash in the preview (maybe there's some configuration for QtWebkit too?)
[10:31] <Lex79> ScottK: no svn found for kgmailnotifier, I sent an email to author hoping he responds today
[12:27] <Half-Left> I've just logged results of the ISO testing and it's all good. :)
[12:36] <ghostcube> ehlo folks
[12:36] <Tm_T> Half-Left: nice (:
[12:38] <Half-Left> Would be good to have a nice picture in the background, instead of a white screen while it's installing. :)
[12:46] <ubuntu_> hi. i want to contribute to beta testing the karmic koala RC
[12:46] <ubuntu_> I am backing up my old home directory while I am running from the live CD
[12:47] <ubuntu_> as the regular update just destroyed the systems ability to boot
[12:48] <worufu> I did the update the day before yesterday (from 9.04 to 9.10)
[12:48] <worufu> sind then it was kind of a lottery game when booting
[12:49] <worufu> every 10th time or so it went through to KDM
[12:49] <worufu> when running almost everything was perfect
[12:49] <worufu> but today I never was able to get KDM running
[12:50] <worufu> it does some boot routine though.... but it is difficult to see what's going on... as there are many blank screens stealing the focus during boot process
[12:50] <worufu> is there any way I can contribute interesting data?
[12:50] <worufu> or shall I just proceed overwriting the existing install with an install from the live CD?
[12:55] <worufu> uhm.... #ubuntu-1 ?
[12:55] <worufu> #ubuntu+1
[13:02] <Riddell> hi worufu
[13:02] <Riddell> if you have logs in /var/log/syslog that would be useful for a bug report
[13:06] <Riddell> going back to testing now but if you also are able to test installs that would be great
[13:07] <rgreening> o/
[13:08]  * rgreening is a good looking developer.. ('notices topic')
[13:08] <worufu> Riddell: I have syslogs available. but I have no clue where to contribute and post them
[13:09] <worufu> Riddell: just printed the syslog on the screen and noticed that the last lines were full of not human readable bytecode
[13:16] <worufu> sorry for starting off in the wrong channel... will hang around in #ubuntu+1 for a while
[13:16] <worufu> good luck with the upcoming release. I love your work.
[13:22] <seele> ScottK: you going to the md loco party saturday?
[13:28] <EagleScreen> is it expected to have video preview thumbnails in karmic?
[13:28] <rgreening> wow.. kmail imap is crashy
[13:29] <JontheEchidna> EagleScreen: if you install mplayerthumbs, yes
[13:30] <EagleScreen> anything else to do after installing it?
[13:30] <JontheEchidna> might have to enable plugins for videos in dolphin config
[13:31] <jussi01> rgreening: use disconnected IMAP, works much better imho.
[13:32] <EagleScreen> yes, JontheEchidna, after changing configuration it is working
[14:35] <rgreening> mmm... bluetooth mouse... makes the mini10v touchpad issues irrelevant :)
[14:35] <jjesse> yes it does :)
[14:37] <rgreening> :)
[14:38]  * claydoh is jealous of y'all and  your fancy netbooks :)
[14:42] <claydoh> tho a 6 y/old laptop is nice enough for testing out kubuntu netbook :)
[14:47] <agateau> ScottK: ping
[15:10] <mcas> after the cd rebuild i'll start to test kubuntu i386 cd
[15:11] <mcas> one question about the iso testing...
[15:12] <mcas> why is the kubuntu testing organized here and not in ubuntu testing? only because of the "ubuntu"?
[15:24] <rgreening> is random playlist generation broken in amarok?
[15:29] <davmor2> rgreening: it's only random it you have more than 1 track dude ;)
[15:30] <rgreening> lol.
[15:30] <rgreening> I have 5000
[15:30] <rgreening> however, the random population doesn't happen and repopulate is greyed out.
[15:34] <neversfelde> agateau: the new plasma-widget-networkmanagment package breaks my wireless connection on two different laptops. They do not reconnect after suspend. It worked on both with 0.9~svn1029786-0ubuntu1.
[15:42] <agateau> neversfelde: oh, I thought it always "featured" this bug :/
[15:42] <agateau> mmm
[15:45] <agateau> neversfelde: can you test the packages from https://launchpad.net/~agateau/+archive/ppa/+builds?build_text=plasma-widget-networkmanagement&build_state=built to pinpoint which one did introduce the breakage?
[15:46] <neversfelde> agateau: sure
[15:46] <agateau> neversfelde: thanks!
[15:57] <bbigras> I can't restart X with kdm with the RC.
[15:57] <bbigras> are you guys aware of this?
[16:01] <bbigras> also, the facebook plugin makes Kopete crash on exit
[16:09] <Riddell> bbigras: facebook plugin got moved to universe because of that crash and other issues
[16:09] <Riddell> bbigras: kdm's interaction with X seems to depend on X drivers as much as anything, what graphics card?
[16:09] <bbigras> Riddell: nvidia
[16:10] <Riddell> bbigras: restarting from the kdm login screen?
[16:10] <bbigras> Riddell: yes
[16:11] <Riddell> works fine here with intel
[16:12] <Riddell> so I'd suspect it's an issue with nvidia drivers
[16:12] <bbigras> Riddell: would .xsession-errors provide any hints?
[16:12] <Riddell> possibly
[16:13] <bbigras> One of the last thing I saw in this file was kwin crashing. I'll try it again in 5-10 minutes
[16:17] <rgreening> hey Riddell
[16:18] <Riddell> hi rgreening
[16:18] <rgreening> how are things coming along since Ive been away Riddell
[16:18] <Riddell> well we fixed all the bugs and we're almost set to do a release :)
[16:19] <rgreening> all the bugs :)
[16:19] <rgreening> haha
[16:19] <rgreening> funny man
[16:19] <rgreening> :)
[16:19] <rgreening> even bug #1
[16:19] <rgreening> lol
[16:19] <claydoh> hey, I can connect to my wireless, that must count for half the problems/gripes :)
[16:20] <Riddell> well obviously that'll only get fixed after release
[16:21] <rgreening> hahah
[16:21] <rgreening> I think I have more converts since my trip to winnipeg. :)
[16:21] <bbigras> Why on my laptop (1920x1200) I need to set the font size to 96 ppp to avoid weird big font problem and not on the other computers (with lower resolution) I have?
[16:21]  * rgreening spreads kubu love
[16:21] <claydoh> Riddell: for the final release notes, should we try for a user-oriented type of format?
[16:22] <claydoh> Riddell: I am trying to come up with something more fun and interesting than the usual version-number-is-now-bigger sort of thing
[16:23] <claydoh> I converted a bud to Kubuntu this weekend :)
[16:23] <bbigras> btw I'm asking for the font size thing because the ubiquity is not really pretty with big fonts.
[16:24] <Riddell> claydoh: what would be changed?
[16:24] <claydoh> Riddell: dunno yet, brainstorming right now
[16:25] <Riddell> but yes it should be user feature orientated as much as possible
[16:25] <claydoh> maybe just list the improvements and additions, highlight what those features
[16:25] <claydoh> that have changed/improved/benn added
[16:26] <claydoh> I know I shoulda kept a jaunty somewhere for comparison :)
[16:59] <bbigras> Riddell: I didn't see anything in .xsession-erros when trying to restart X. The last thing I see in that file is kwin crashing
[17:01] <JontheEchidna> the kwin crash on logout is a known, separate issue that's been around since KDE 4.1 times
[17:01] <JontheEchidna> /var/log/Xorg.0.log.old may be of use
[17:02] <mgraesslin> kwin crash on logout?
[17:02] <mgraesslin> NVIDIA driver?
[17:02] <bbigras> yes nvidia
[17:02] <JontheEchidna> yeah, nvidia
[17:02] <bbigras> http://pastebin.ca/1645342
[17:03] <bbigras> JontheEchidna: I'll check /var/log/Xorg.0 brb
[17:08] <JontheEchidna> anybody want to take care of bug 460984?
[17:26] <Sime> is there anything sinister lying in the 9.10 upgrade process that I need to be aware of before upgrading my machine here?
[17:26] <smarter> monsters
[17:27] <smarter> well, the boot system now relies completely on upstart scripts, it's supposed to work reliably but you never know what could happen :p
[17:28] <smarter> Grub --> Grub2 transition could also potientially causes problems
[17:28] <bbigras> JontheEchidna: I didn't see anything special in the log file except maybe "ddxSigGiveUp: Closing log" at the end
[17:29] <JontheEchidna> bbigras: yeah, X is crashing then
[17:29] <Sime> smarter: are the configs kind of the same?
[17:29] <smarter> Sime: for grub2? not at all
[17:29] <smarter> it's in /boot/grub/grub.cfg now, instead of menu.lst
[17:29] <Sime> ok, coz my grub config is pretty nutty
[17:30] <smarter> and it's automatically generated by scripts in /etc/grub.d
[17:31] <bbigras> JontheEchidna: btw I'm able to log back in. only restart X don't works. do you have ideas where else I could also look?
[17:31] <JontheEchidna> not really, sorry :(
[17:32] <bbigras> thanks anyways for the help.
[17:40] <Sime> ok, upgrade aborts if ubuntu-minimal is not installed...
[17:44] <bbigras> I reported the X restart issue with kdm, should I link the bug on the iso testing website even if I'm using the RC iso which I guess is not the latest one?
[17:51] <djsiegel> seele: hey
[18:01] <Riddell> Sime: there is a potential issue with upgrade caused by pykde, but it's a packaging issue and should only affect people with conf files that get upgraded after pykde which won't be many, I'm fixing it now
[18:02] <Sime> Riddell: does that mean I will have a bad evening??
[18:03] <Riddell> Sime: it's very unlikely
[18:03]  * Sime happily clicks on the next step of the upgrade process.
[18:04] <Sime> "Error authenticating some packages"... mmm
[18:04] <Sime> expected?
[18:04] <Riddell> nope
[18:04] <Riddell> do you have something strange in your sources.list ?
[18:05] <Sime> it has listed a mega-ton of packages
[18:05] <Sime> all of them I think.
[18:06] <Riddell> Sime: is apt's gpg setup broken?  what happened when you installed ubuntu-minimal?
[18:07] <Riddell> davmor2: can you say what you upgraded from when you report upgrade results in e.g. http://iso.qa.ubuntu.com/qatracker/result/3313/85
[18:07] <davmor2> jaunty
[18:08] <Sime> Riddell: nothing exciting happened.
[18:08] <Riddell> Sime: did it moan about being unable to authenticate?
[18:09] <Sime> Riddell: no, but I did have some network trouble with nl.archive.ubuntu.com.
[18:09] <Sime> Also, is it normal that the upgrader be so slow at d/l'ing files?
[18:10] <Riddell> that just depends on your mirror and internet connection
[18:12] <Sime> it is faster now (caching??)
[18:12] <Riddell> it's just an http connection, nothing unusual about it
[18:14] <Sime> it is now threaten to upgrade. ;-) There must have been a network "glitch".
[18:16] <Sime> it is now warming up my ADSL modem. :)
[18:17] <Riddell> if you have cats be careful, they'll go to sleep on it and it'll overheat
[18:20] <Riddell> davmor2: the test machine I have with windows xp on it has had windows xp destroying the grub setup after it boots, this doesn't happen with jaunty's grub, have you seen anything like that?
[18:21] <davmor2> nope
[18:23] <davmor2> Riddell: I'll have a look in a minute though
[18:25] <Riddell> davmor2: I suspect it'll be a feak issue with this windows xp install but would be a problem if it was a general issue
[18:27] <davmor2> Riddell: I has a new compaq110 with xp preinstalled I'm about to test kne and unr so we'll soon know :)
[18:28] <jussi01> Hrm, anyone got a simple way of discovering other linux machines on a home network?
[18:29] <davmor2> jussi01: walk up to the box?
[18:30] <Riddell> jussi01: avahi-browse -a
[18:31] <Riddell> zeroconf:/ will show if anything is advertising http or ssh but most don't unfortunately
[18:32] <jussi01> hrm. is there a way I can get it to advertise ssh?
[18:34] <Riddell> avahi-publish-service "crack me" _ssh._tcp 22
[18:35] <jussi01> hehe :)
[18:36] <jussi01> 1 last quick question, behind a firewalled router, thatll only advertise on the local network? (its my media pc...)
[18:37] <Riddell> yes it's local network only
[18:38] <jussi01> yay, thanks :)
[18:45] <Riddell> hi nookie^, how's that banner coming along?
[18:48] <nookie^> hi Riddell! hehehe actually im just now looking how to create it =)
[18:48] <nookie^> have been thinking now for an hour how i can create it =)
[19:46] <Mamarok> hm, I just had a look at the Software Center, so one can only select one single item, installs that and goes to the next? That takes ages
[19:49] <davmor2> Mamarok: no you install one move back select the next etc
[19:49] <Sime> upgrade got 404 on a couple packages. I'm guessing a mirror sync issue.
[19:50] <Mamarok> davmor2: that is lame
[19:50] <Mamarok> no way to preselect and then isntall all in one go?
[19:50] <Mamarok> install*
[19:51] <skreech> Wait I should be using grub2?
[19:51] <skreech>  I upgraded and I'm still on grub 1
[19:51] <skreech> bbigras: hi
[20:27] <Sime> shit, kdesudo crashed.
[20:29] <Sime> how now brown cow??
[20:29] <Sime> segfault
[20:33] <nookie^> Riddell: so far like this: http://imagebin.ca/view/wwWopm2.html
[20:44] <skreech> Sime: sudo start it back?
[20:45] <Sime> skreech: I'm running dpkg configure manually
[20:48] <skreech> ok
[21:03] <maco> anyone having issues with power devil on karmic? its timing seems off. i have it set to display dim after 1 minute of idle, but instead it dims immediately  (ie, not a full minute)
[21:03] <dtchen> reproducible with a fresh user account?
[21:04] <dtchen> I can't reproduce the symptom you describe in vbox with the 20091027 desktop image.
[21:04] <dtchen> granted, I don't know offhand if I need to run it on bare metal.
[21:06] <Sime> anyone know a simple way of updating grub and its config?
[21:06] <LaserJock> what are the menu steps to get to kpackagekit?
[21:08] <maco> dtchen: mm nope. now i wonder whats wrong with mine
[21:08] <maco> LaserJock: kickoff -> computer -> kpackagekit
[21:08] <LaserJock> maco: s/kickoff/K menu/ ?
[21:09] <LaserJock> maco: it's for documentation
[21:09] <dtchen> maco: looks like you have conffile cruft
[21:09] <maco> LaserJock:  or kickoff -> applications -> system -> kpackagekit
[21:09] <maco> LaserJock: dunno what its called elsewhere in docs, but it doesnt act the same as the k menu did...
[21:09] <maco> i think its "application launcher" or something
[21:09] <LaserJock> maco: is it actually listed as "kpackagekit"?
[21:10] <maco> LaserJock: it says "KPackageKit" and then as a subtitle "Software Management" when you look in "Computer"
[21:10] <LaserJock> awesome, thanks
[21:10] <maco> which is the name and which is the subtitle are reversed in System
[21:10] <skreech> Others have the same issue with failsafe bombing.
[21:11] <maco> LaserJock: got that?
[21:11] <LaserJock> maco: yep
[21:11] <maco> ok
[21:17] <skreech> and not being able to get to TTYs as well
[21:18] <skreech> Konsole doesn't work for failsafe
[21:21] <skreech> well as x-terminal-emulator
[21:25] <Sime> wish me luck. [attempting reboot]
[21:29] <maco> dtchen: i lied
[21:29] <maco> apparently when i dont sleep one night, the effects last > 1 day, because i was reading the wrong line
[21:29] <davmor2> Riddell: just to confirm that xp and grub work fine here
[21:29] <maco> though that was only 22 mississippis, not 50-70-ish whe the screen dimmed for the new user, so it was still odd
[21:31] <maco> well, my conffile doesnt look broken. and this started happening a few days ago without any changes to my configuration. so im confused
[21:36] <maco> *shrug* works if i change it to 2min instead of 1. whatver.
[21:36] <dtchen> what in the world does "i lied" refer to?
[21:36] <maco> dtchen: apparently that message didnt send
[21:36] <maco> oh well
[21:37] <maco> i said that the new user dint have that problem but that the conf file wasnt updating when i changed settings in power devil. then i realized i was reading the wrong line of the conf file
[21:37] <maco> so then i said "i lied"
[21:38] <dtchen> ok, that's only slightly less befuddling
[21:41] <dmatt> screech: your theory is not right, I could get to TTY before I attempted the failsafe login
[21:42] <skreech> dmatt: Then you couldn't afterwards?
[21:42] <dmatt> yes
[21:43] <maco> yikes
[21:44] <skreech> When you tried to switch to TTY you get a black screen?
[21:44] <dmatt> skreech: yes, without cursor
[21:45] <skreech> Did you try to get back to TTY7 ?
[21:45] <dmatt> screech: but session still existed, it promted me to close it when I went for restart
[21:46] <dmatt> skreech, yes, I chose to restart there
[21:46] <skreech> Yep me too
[21:47] <skreech> I did it again and got the same thing
[21:47] <skreech> I went through the motions of logging in then I touched a file in ~ and rebooted
[21:47] <skreech> When it came back up the file existed so I know that things are working but you just can't see anything
[21:47] <skreech> Logging in as failsafe throws a X driver error
[21:48] <skreech> well it does for me
[21:49] <skreech> But whatever Konsole is doing is messing with X pretty bad
[21:49] <dmatt> screech: you still can perfectly work and see everything, if you do not attempt any login and go straight to tty
[21:49] <skreech> dmatt: I know
[21:49] <skreech> and You can fix the failsafe pretty easy
[21:49] <skreech> well for me it's a fix
[21:49] <dmatt> skreech: (i finally got your nick right)
[21:50] <skreech> Workaround for others I suppose
[21:50] <skreech> Yay! :)
[21:50] <dmatt> skreech: why does it work on that old computer then, even after failsafe login?
[21:51] <dmatt> it has old ATI card with open driver
[21:51] <skreech> Probably it
[21:51] <skreech> 9600 ?
[21:52] <dmatt> IGP 350M
[21:52] <dmatt> skreech: IGP 340M, sorry
[21:52] <dmatt> it is notebook
[21:53] <skreech> Hmm ok
[21:53] <skreech> I'm using nvidia right now I've not had any issues with my older ATI and the open driver
[21:54] <skreech> what video card are you using on the newer one?
[21:54] <dmatt> ATI 3400 (it is notebook HP 6930p)
[21:54] <skreech> Which driver?
[21:55] <dmatt> open
[21:55] <skreech> Hmm that's not helpful then
[21:55] <skreech> Kernel difference ?
[21:57] <dmatt> both are on 31-14, but old one is x86 and new one is 64
[22:00] <dmatt> skreech: that might be something...
[22:05] <skreech> Hmm ok
[22:05] <skreech> I'm x86 so maybe not
[22:16] <dmatt> skreech: old one was installed while connected to internet, new one entirely from cd an later upgraded
[22:17] <skreech> This is a straight upgrade from Jackalope
[22:17] <skreech> Kpackagekit has the most aggravating errors
[22:17] <skreech> There are broken dependecies on your system. Please use an advanced package manage e.g. Synaptic or aptitude to resolve this situation.
[22:41] <Riddell> nookie^: that seems good
[22:45] <Riddell> Sime: how was the upgrade?
[23:35] <davmor2> ScottK: I left you kne manual :)
[23:55] <Riddell> apachelogger: do I know Christopher Eberl ?