[04:41] <doctormo> pleia2: Hmm, I'm not sure why we're having lots of C# lessons for Ubuntu, I though C# was just to get windows apps to Linux.


[02:19] <waigani> wallyworld_: I forgot to grab that example before leaving the standup. Can I grab it again please?
[02:19] <wallyworld_> for loop starts at line 548 in state.go
[02:23] <waigani> wallyworld_: cheers
[02:23] <wallyworld_> np
[02:33] <axw> wallyworld_: you did a fix to the unit upgrader... did it fix https://bugs.launchpad.net/juju-core/+bug/1284502?
[02:33] <_mup_> Bug #1284502: upgrader: cannot read tools metadata (in unit agent) <local-provider> <juju-core:Triaged> <https://launchpad.net/bugs/1284502>
[02:36] <wallyworld_> axw: i think so
[02:36] <wallyworld_> yes
[02:36] <wallyworld_> that branch is in the queue to land
[02:37] <axw> ok
[02:41] <wallyworld_> thumper: so i can't push to lp:~go-bot/juju-core/trunk. says it's read only
[02:41] <thumper> ah...
[02:41]  * thumper thinks
[02:42] <thumper> wallyworld_: you need to do this:
[02:42] <thumper> bzr push<EMAIL_ADDRESS>[02:42] <thumper> your ssh key is loaded against the go-bot user
[02:42] <wallyworld_> ah ffs. i tried that but forgot the go-bot@ bit
[02:43] <thumper> :)
[02:43] <thumper> wallyworld_: are you setting the author on the merge?
[02:43] <wallyworld_> what's the way to do that?
[02:43] <thumper> when you have a merge
[02:43] <thumper> run the tests
[02:43] <wallyworld_> yep
[02:44] <thumper> bzr commit -m "blah blah" --author "Firsrt Last <email addr>"
[02:44] <wallyworld_> ah --author, ok
[02:49] <axw> thumper: https://codereview.appspot.com/67870045/    -- the change in AddScripts fixes the log dir permissions. Did this as a drive-by in a larger fix
[02:50] <thumper> ok
[02:51] <thumper> hmm...
[02:52] <thumper> axw: actually I ment to ask you earlier today
[02:52] <thumper> how the juju-db upstart job was getting removed
[02:55] <axw> thumper: the machine agent removes it on tear down
[02:55] <axw> pkill -SIGABRT kills the machine agent, which stops and removes the jobs
[02:56] <thumper> axw: so the machine agent also brings down the mongo job?
[02:56] <axw> thumper: yep, that bit is now shared between local and manual providers.
[02:57] <axw> thumper: see uninstallAgent in cmd/jujud/machine.go if you care to see where
[02:58] <thumper> ok
[03:11] <thumper> wallyworld_: I don't want to see the asserts removed
[03:11] <thumper> wallyworld_: just moved to an explicit test
[03:11] <wallyworld_> thumper: but it's part of the setup
[03:12] <wallyworld_> not prt of what is being tested
[03:12] <thumper> wallyworld_: if something from setup is tested in one test, you don't need to do it in every test
[03:12] <thumper> I disagree
[03:12] <thumper> the setup it the setup
[03:12] <thumper> the test checks the setup did it right
[03:12] <thumper> what you have
[03:12] <wallyworld_> it is to ensure the setup does what we think
[03:12] <thumper> is the test that it worked every time done every time
[03:12] <thumper> IMO this is overkill
[03:12] <wallyworld_> i've seen tests before where setup was faulty and we didn't know it
[03:12] <thumper> just what I was brought up with, blame mwhudson
[03:13] <thumper> wallyworld_: I'm not saying don't test that setup did it right
[03:13] <thumper> what I am saying is don't do that assertion *in* setup
[03:13] <wallyworld_> so you want a TestSetuptest()
[03:13] <thumper> have a test for the purpose of making sure that setup did it right
[03:14] <thumper> FFS, do what you like
[03:14]  * thumper gives up
[03:14] <wallyworld_> no, it's ok, i'll change it
[03:14] <wallyworld_> just trying to understand yout pov
[03:14] <axw> I don't know the context, but that sounds like a recipe for difficult to debug test errors when TestSetuptest doesn't run before the other tests
[03:14] <wallyworld_> there isn't a TestSetuptest yet
[03:15] <wallyworld_> i was doing asserts in Setup() to ensure that the test setup was done right
[03:15] <wallyworld_> or more to the point, did what we thought it did so that subsequent tests could be assured of testing the right thing
[03:16] <wallyworld_> but i can add an explicit test to check the behaviour of SetUp()
[03:16]  * wallyworld_ -> lunch
[03:16] <thumper> I guess this is why having lots of setup in setup is not good
[03:17] <thumper> wallyworld_: look, the overhead of running it every time is insignificant
[03:17] <axw> hmm, I don't see the need for the assertions at all really. this is testing that SetEnvironConfig does its job
[03:17] <thumper> just keep them in setup
[03:17] <axw> that should be done in state
[03:17]  * axw shrugs
[03:31] <thumper> axw: what was the failure here: https://code.launchpad.net/~axwalk/juju-core/local-prereq-rsyslog-gnutls/+merge/208545
[03:31] <thumper> intermittant?
[03:31] <axw> thumper: pretty sure it's because the bot was in a bad way
[03:32]  * thumper nods
[03:49] <mwhudson> thumper: wat
[03:55] <wallyworld_> axw: the assertions were not to check that SetEnvironConfig did it's job, but that there weren't typos in hgow it was invoked such the the expected config attrs were set, since the test checks for their removal
[03:56] <axw> wallyworld_: if you're making assertions about how the tests work, then when do you stop?
[03:56] <wallyworld_> i only do it for selected cases
[03:56] <wallyworld_> on a subjectively as needed basis where there's some risk
[04:02] <thumper> mwhudson: oh hai
[04:02] <thumper> mwhudson: just taking your name in vain
[04:02] <mwhudson> thumper: cool
[04:02] <mwhudson> :)
[04:02] <thumper> mwhudson: for teaching me about tests
[04:03] <thumper> in a good way
[04:05] <wallyworld_> waigani: tests on your branch fail so i can't land it for you:  policy-based-config-validation
[04:05] <waigani> wallyworld_: doh
[04:05] <waigani> okay, I'll check
[04:06] <wallyworld_> ok, ta
[04:13] <wallyworld_> axw: i get test failures in ~axwalk/juju-core/local-prereq-rsyslog-gnutls
[04:13] <wallyworld_> ah
[04:14] <wallyworld_> cause i don't have syslog-gnutls installed
[04:14] <wallyworld_> let me install that and retry
[04:19] <wallyworld_> right, that's much better
[04:24] <axw> wallyworld_: hrm, that's actually a problem :)
[04:24] <axw> tests shouldn't rely on the package being there
[04:24] <wallyworld_> i guess we need to add it to the packaging stuff
[04:24] <wallyworld_> i think it's reasonable the deps are expected
[04:24] <wallyworld_> eg tests will fail if no mongo
[04:25] <axw> true
[04:25] <wallyworld_> i'd send an email to the list to let people know they need to install it
[04:25] <axw> wallyworld_: I actually thought I had isolated this one, so I'll see if it's easy to fix... otherwise I will email the list
[04:25] <wallyworld_> and let curtis know so he can get the ppa sorted
[04:26] <axw> juju-local should be updated tho, there's a bug for that
[04:26] <wallyworld_> regardless for the next release the packaging needs to be changed
[04:27] <axw> wallyworld_: what do you mean by the packaging?
[04:27] <wallyworld_> that fact that juju-core depends on this new package
[04:27] <axw> wallyworld_: the client doesn't need rsyslog-gnutls, and it will be installed by bootstrap
[04:27] <axw> no, only local requires it to be pre-existing
[04:27] <wallyworld_> oh ok
[04:27] <wallyworld_> but that's still juju-core
[04:28] <axw> there's a meta package for the prereqs
[04:28] <wallyworld_> so if one installs juju-core, it should pull down this new dep
[04:28] <wallyworld_> sure, the dependencies need to be updated
[04:28] <axw> yep, there's a bug for it against 1.18
[04:29] <wallyworld_> ok, that's great
[04:29] <wallyworld_> just wanted to double check
[04:46] <axw> wallyworld_: when you have a moment, can you please review https://codereview.appspot.com/71050043?
[04:46] <wallyworld_> sure
[04:47] <wallyworld_> just landing the rsyslog port branch
[05:03] <wallyworld_> axw: all approved mps landed \o/
[05:03] <axw> thanks wallyworld_  :)
[05:03] <wallyworld_> i'm pleased too
[09:41] <bloodearnest> hazmat: re install.sh, sure, I didn't exec it, but it was useful as a crib sheet for set up steps
[09:54] <natefinch> mgz, rogpeppe, dimitern: o/
[09:55] <dimitern> natefinch, morning!
[09:55] <natefinch> dimitern:  morning :)
[09:57] <mgz> natefinch: we're getting wwitzel3 to g+ you now for the hangout
[09:57] <natefinch> mgz: cool
[10:48] <natefinch> jam: https://plus.google.com/hangouts/_/76cpirbanp35boic60gobgfltc?authuser=1&hl=en
[10:51] <mgz> http://en.wikipedia.org/wiki/Shrove_Tuesday
[10:54] <natefinch> mgz: I didn't know they had a whole week of this stuff.
[10:59] <mgz> the feasting bit is only today, the following period is fasting
[11:08] <wallyworld_> mgz: from what i can tell, juju trunk  canonistack don't like each other because port 17070 can't get routed via chinstrap like port 22 can for ssh
[11:09] <wallyworld_> or am i missing something?
[11:09] <wallyworld_> i was hoping to try and get the landing bot running
[11:09] <wallyworld_> but i ended up testing a bunch of branches and landing manually
[11:10] <wallyworld_> at least the backlog of approved mps is now in trunk
[11:33] <mgz> wallyworld_: you can always route via sshuttle to the bootstrap node, but I think going via chinstrap should be fine
[11:33] <mgz> wallyworld_: I saw you'd landed a bunch of branches, thanks
[11:33] <wallyworld_> mgz: i tried using shuttle, no good
[11:33] <wallyworld_> i must have been doing it wrong
[11:33] <mgz> the main issue is lcy02 is just hosed, but I will probably try bring up a new bot on lcy01
[11:34] <wallyworld_> ok
[11:34] <mgz> or fall back to ec2 if needed
[11:34] <wallyworld_> previously lyc02 was better
[11:34] <dimitern> LXC is now fixed on trusty for me - local provider works again! \o/
[11:34] <wallyworld_> dimitern: yeah, i landed a fix today
[11:35] <wallyworld_> it was broken for trusty host and precise charms
[11:35] <wallyworld_> but worked if host and charms were the same
[11:35] <wallyworld_> well, the upgrader bounced anyway
[11:37] <bloodearnest> wallyworld_: huh, that explains this mornings issues, thanks :)
[11:37] <wallyworld_> bloodearnest: ah, sorry about that. fixed now :-) a fix for one problem broken something else so needed a second fix :-/
[11:39] <bloodearnest> wallyworld_: no worries, seems good now. I thought I'd broken things by having 4 active local envs at once
[11:40] <wallyworld_> nah :-)
[11:42] <bloodearnest> I get warnings for shared-storage-port env config - can I just drop that now?
[11:43] <wallyworld_> not sure about that one off hand, let me check
[11:45] <wallyworld_> bloodearnest: i think you can delete that one
[11:46] <bloodearnest> wallyworld_: great - the warnings interfere with my bash auto-completion
[12:08] <dimitern> wallyworld_, awesome! 10x
[13:17] <ahasenack> does anyone know what the hook behavior is when a unit is rebooted?
[13:17] <ahasenack> I'm seeing that in 1.16.6 the config-changed hook is run, for example. Is that expected?
[13:47] <natefinch> dimitern, rogpeppe:  I think john dropped out of the hangout btw
[13:55] <ev> hi guys. Is anyone working on https://bugs.launchpad.net/juju-core/+bug/1284183? It's causing us a lot of pain as we try to deliver some customer work and we've got a big deadline coming up in a couple of weeks
[13:55] <_mup_> Bug #1284183: jujuclient.EnvError: <Env Error - Details:  {   u'Error': u'watcher was stopped', u'RequestId': 9, u'Response': {   }} <api> <status> <juju-core:Triaged> <https://launchpad.net/bugs/1284183>
[13:57] <natefinch> ev: we're actually triaging bugs today, so we can look at that one and see what's up with it. Roger knows the most about it, but is out to lunch, he should be back shortly, however
[13:58] <ev> cool, thanks natefinch
[14:38] <mgz> bug 1287147 for the FFE
[14:38] <_mup_> Bug #1287147: [FFe] juju-core 1.18/2.0 <juju-core (Ubuntu):New> <https://launchpad.net/bugs/1287147>
[14:42] <natefinch> rogpeppe: when you get a chance, I committed fixes for the issues you brought up in the code review: https://codereview.appspot.com/69600043/
[14:43] <rogpeppe> natefinch: will look in a mo
[15:17] <ev> rogpeppe: also if you could have a look at bug 1284183 whenever you get a chance, I'd greatly appreciate it. My team at Canonical keeps hitting it and its killing our velocity as we try to deliver a contract over the next two weeks
[15:17] <_mup_> Bug #1284183: jujuclient.EnvError: <Env Error - Details:  {   u'Error': u'watcher was stopped', u'RequestId': 9, u'Response': {   }} <api> <status> <juju-core:Triaged> <https://launchpad.net/bugs/1284183>
[16:10] <natefinch> jam: https://plus.google.com/hangouts/_/76cpirbanp35boic60gobgfltc?authuser=1&hl=en
[16:38] <rogpeppe> ev: i've just been looking at that bug with a view to trying to repro it
[16:39] <ev> rogpeppe: yay! cjohnston can probably help get logs and things if you need them
[16:39] <rogpeppe> ev: the repro instructions don't seem to work for me
[16:39] <ev> he experiences it quite often
[16:39] <ev> doanac and urshina as well, who I'll tell to join this channel
[16:39] <rogpeppe> cjohnston: you've got a bare "sshuttle" line there, but sshuttle just gives me a usage message there
[16:40] <cjohnston> rogpeppe: you will need to do sshuttle for an instance you have.. I couldn't give you the exact command I use because it wont work for you
[16:40] <rogpeppe> cjohnston: a sample command line? (i haven't used sshuttle before)
[16:41] <rogpeppe> cjohnston: (and i'm not sure what you wanted it to do here)
[16:41] <ev> Ursinha: just reproduced it
[16:41] <cjohnston> rogpeppe: sshuttle -r<EMAIL_ADDRESS><IP_ADDRESS>/16
[16:41] <cjohnston> rogpeppe: when using something like HP cloud you don't need it.. but you need it to use canonistack
[16:41] <rogpeppe> cjohnston: i'm using ec2
[16:41] <cjohnston> rogpeppe: we dont use ec2 because of the api
[16:41] <rogpeppe> cjohnston: or the local provider
[16:42] <rogpeppe> cjohnston: which api?
[16:42] <cjohnston> the ec2 api is different from hp/canonistack
[16:43] <ev> (openstack API - we use glance and swift)
[16:43] <Ursinha> ev: it seems I hit the watcher bug every time I try to deploy using a fresh bootstrapped environment
[17:14] <natefinch> mgz, jam1, fwereade: is the bot working yet?  Just realized I marked stuff for merge, but there may be no bot to merge it
[17:29] <mgz> natefinch: nope
[17:29] <mgz> was going to fix today but have been under the weather
[17:30] <natefinch> mgz: ok, no problem, just wanted to know what the plan was.
[17:30] <mgz> you can manually land things if needed urgently
[17:31] <hazmat> ahasenack, no config-changed hook was being executed gratitiously.. there's a bug against that, i think its fixed in trunk
[17:31] <hazmat> er. 1.17
[17:31] <natefinch> mgz: nothing's terribly urgent, it just would be nice, since I have other stuff that depends on it.
[17:31] <hazmat> bloodearnest, the other crib sheet item is using the lxc stable ppa if not on trusty for aufs
[17:34] <bloodearnest> hazmat: yeah, am on trusty so skipped
[17:35] <hazmat> bloodearnest, so it worked out for you?
[17:35] <bloodearnest> hazmat: I needed jujuclient 0.17 from PyPI (0.15 in trusty seems to have bug)
[17:36] <bloodearnest> hazmat: and I could jlxc-add machines, buit the didn't come up properly - I think I may have encountered an issue in trust with local provider that was fixed today
[17:36] <bloodearnest> hazmat: I will try again tomorrow sometime
[17:36] <hazmat> bloodearnest, this doesn't use local provider
[17:37] <hazmat> bloodearnest, jlxc that is
[17:37] <bloodearnest> hazmat: good point, not sure why it didn't work then
[17:37] <hazmat> bloodearnest, probably missing packages in your base snapshot
[17:38] <hazmat> bloodearnest, needs git, cpu-checker at min
[17:38] <ahasenack> hazmat: it highlighted a bug in our charm anyway, someone rebooted a node and config-changed ran and highlighted an issue
[17:38] <ahasenack> same thing happens with a juju set, just turns out a reboot triggered it :)
[17:39] <hazmat> fuzz testing
[17:52] <mgz> http://godoc.org/github.com/loggo/loggo#Formatter
[18:09] <bloodearnest> hazmat - makes sense - will try again later
[18:15] <hazmat> half of all open bugs marked high
[18:15] <hazmat> hmm
[18:24] <natefinch> hazmat: if they weren't important bugs, they wouldn't have bothered to log them
[18:24] <natefinch> hazmat: I wonder what portion of the non-high bugs were created as high
[18:29] <hazmat> natefinch, almost zero
[18:29] <hazmat> sinzui, https://bugs.launchpad.net/juju-core/+bug/1219441 is fix committed or released (dev version) afaik
[18:29] <_mup_> Bug #1219441: juju cli should cache api endpoint, saves up to 75% of run time <papercut> <performance> <juju-core:Triaged by rogpeppe> <https://launchpad.net/bugs/1219441>
[18:29]  * hazmat goes bug weeding
[18:30] <sinzui> hazmat, thank you very much! I too and looking for fixed or now wint fix bugs
[18:31] <hazmat> sinzui, re high philosophy. are you abiding by lp severity help/description guidelines? or something else
[18:31] <hazmat> ie. high for next release?
[18:31] <sinzui> high is fix in the next 6 months
[18:31] <sinzui> hazmat, If we want it fixed for 14.04, we should target to 2.0
[18:32] <ev> does juju work on rackspace? I can't find any documentation for it
[18:32] <ev> or are my options HP and AWS
[18:32] <hazmat> ev no
[18:32] <hazmat> ev or digitalocean ;-) .. ie manual provider works everywhere.
[18:33] <ev> hazmat: we need openstack APIs as we use glance and swift as part of this project
[18:33] <ev> otherwise I'd be all over the AWS goodness
[18:33] <hazmat> ev, there are some issues with rackspace and openstack provider due to lack of images, lack of security groups, etc.
[18:34] <ev> ick, I'll cancel the account then
[18:34] <ev> I wonder why there are other accounts inside canonical then?
[18:34]  * hazmat draws blanks
[18:34] <hazmat> they gave some freebie accounts for ostack devs
[18:35] <ev> ^ cjohnston don't bother with rackspace
[18:35] <cjohnston> ev: I saw
[18:36] <ev> cool
[19:07] <waigani> wallyworld_: thanks for landing the branches yesterday
[20:46] <thumper> gah
[20:48] <thumper> niemeyer: do you know why this fails? args = append(args, "--", templateArgs...)
[20:48] <thumper> both args and templateArgs are []string
[20:48] <niemeyer> thumper: The variadic parameter must match the variadic parameter of the function
[20:49] <thumper> I would have thought that would work
[20:49] <thumper> so it isn't unpacking and repacking
[20:49] <thumper> just passing throughj
[20:49] <niemeyer> thumper: Right
[20:49] <thumper> hmm...
[20:49] <thumper> ok
[20:49] <niemeyer> thumper: I'm not sure if that's a good thing or not, or if eventually it'll just be more flexible
[20:49] <niemeyer> thumper: I suspect it's one of these "let's see how it goes" cases
[20:50] <thumper> it is just one of those "I would expect this to work and it doesn't" moments
[20:50] <niemeyer> thumper: I agree
[21:03]  * thumper falls foul of the fix bug and try again without rebuilding issue
[21:15] <thumper> ok, that isn't too crazy
[22:30] <waigani> thumper: go newbie question?
[22:31] <thumper> shoot
[22:31] <waigani> http://paste.ubuntu.com/7035472/ I'm getting the error: newConfig declared and not used on line 16
[22:31] <waigani> At first, I thought block scope was stopping me from conditionally setting the variable.
[22:31] <waigani> But as long as I declare the var in the parent scope, it should work. I did a simple test in the playground: http://play.golang.org/p/rhxBZjqexA
[22:31] <waigani> So I'm stumped.
[22:32]  * thumper thinks he knows without looking
[22:32] <thumper> but looks anyway
[22:32] <thumper> right
[22:32] <thumper> you hit the same issue as wallyworld yesterday
[22:32] <waigani> newConfig should be used on line 38?
[22:32] <thumper> since you are using := it creates a new one
[22:32] <thumper> in that scope
[22:32] <thumper> you need to use =
[22:32] <waigani> aahhh
[22:32] <thumper> which may mean you need to declare
[22:32] <waigani> thanks
[22:32] <thumper> var err error
[22:33] <waigani> yep
[22:33] <waigani> cheers
[22:33] <thumper> np
[23:16] <waigani> wallyworld: I'm getting the following test failure:
[23:17] <waigani> # launchpad.net/juju-core/worker/rsyslog
[23:17] <waigani> worker/rsyslog/worker.go:19: import ...go/pkg/linux_amd64/launchpad.net/juju-core/log/syslog.a: object is [linux amd64 go1.1.2 X:none] expected [linux amd64 go1.2 X:none]
[23:17] <waigani> yet go version returns: go version go1.2 linux/amd64
[23:17] <waigani> Any hints, off the top of your head?
[23:18] <wallyworld> try deleting your pkg directory to force it to recompile everything. i think you must have upgraded your go version and have old compiled artefacts hanging around
[23:18] <waigani> wallyworld: will do, thanks
[23:34] <waigani> wallyworld: 5min hangout?
[23:35] <wallyworld> waigani: i'm sitting in the tyre shop getting some tyres fitted. so i can't really do it now sorry
[23:35] <waigani> np
[23:35] <wallyworld> hopefully it will be finished soon
[23:35] <waigani> so I rm -rf pkg
[23:35] <wallyworld> it's quite an open office so i can't reslly talk
[23:36] <waigani> sure
[23:36] <waigani> now when I make check I get a LOT of those wrong go version errors
[23:36] <wallyworld> which pkg dir did you remove
[23:37] <waigani> ~/go/pkg
[23:37] <wallyworld> so your juju src lives under ~/go/src
[23:37] <waigani> yep
[23:38] <wallyworld> and if you go build ./... it fails?
[23:38] <wallyworld> did you recently install a new version of go
[23:38] <waigani> yes
[23:38] <waigani> well, a few weeks ago
[23:38] <waigani> this is the first time I've seen this error though
[23:39] <wallyworld> hmmm. it should have shown up immediately so there's something else at play
[23:39] <wallyworld> what else has changed?
[23:39] <waigani> hmmm...
[23:41] <waigani> wallyworld: go build ./... throws a whole bunch of the same errors
[23:41] <waigani> http://pastebin.ubuntu.com/7035788/
[23:42] <waigani> a path problem maybe?
[23:42] <waigani> i.e. two different go excs running?
[23:42] <wallyworld> seems like it what does "which go" say
[23:43] <waigani> /home/jesse/go/src/code.google.com/p/go/bin/go
[23:43] <wallyworld> and that's where you installed go 1.2 to?
[23:43] <waigani> i think so, go I'll retrace my steps
[23:44] <wallyworld> what version does that report?
[23:44] <waigani> 1.2
[23:44] <wallyworld> cause there will also be a /usr/bin/go
[23:44] <waigani> ah
[23:45] <wallyworld> why didn't you install to /usr/bin?
[23:45] <waigani> /usr/bin/go = 1.1.2
[23:45] <waigani> wallyworld: good question!
[23:45] <wallyworld> there should be a ubuntu package for it
[23:45] <waigani> I'll do that now and see if it fixes it
[23:45] <wallyworld> there's something hppening i don't fully understand
[23:46] <wallyworld> but yeah, try and get only one version installed and see if tha helps
[23:46] <wallyworld> "go build -a" could also be tried
[23:47] <waigani> what does that do?
[23:47] <waigani> it just returned without output
[23:49] <wallyworld> you still need to tell it what to build
[23:50] <wallyworld> i was just saying use the -a param to force a rebuild of everything even if it thinks it's not out of date
[23:50] <wallyworld> iow go build -a ./...


[00:02] <maxb> tretle: Because the hardware and software both support multitouch, I guess. What is there to explain!?
[00:03] <tretle> inspiron 6400 doesnt ship with a multitouch trackpad
[00:04] <maxb> Well, if it's successfully detecting multiple touches, I guess it does actually?
[00:06] <elvirolo> hi everyone
[00:07] <elvirolo> does anyone use kubuntu?
[00:07] <elvirolo> because i just installed the latest updates and now i can't start kde anymore
[00:12] <arooni> what will jaunty have
[00:12] <arooni> that ibex doesnt
[00:26] <ph03n1ks_> hey
[00:26] <ph03n1ks_> ne1 home? :)
[00:27] <ph03n1ks_> never been to a ubuntu irc room be, new to irc.
[00:27] <ph03n1ks_> i read the mark shuttleworth bit on slashdot about the kola
[00:27] <ph03n1ks_> release
[00:28] <ph03n1ks_> and it mentioned how the plan was for jaunty to have a 25 second boot time on a netbook and how they were looking for bug reports.
[00:28] <ph03n1ks_> im using the netbook remiximage for 8.04, i just tried installing the netbook remix image for jaunty but cant :(
[00:29] <ph03n1ks_> i cant find a bug report, thought i could check in here to see if its a known issue?
[00:41] <ph03n1ks_> anyone here used jaunty netbook remix image?
[00:43] <Turl> hi, can anyone reproduce https://bugs.launchpad.net/bugs/332343 ?
[00:48] <ph03n1ks_> can anyone advise me on how to get the jaunty netbook remix image to install on my aspire one? the install gui is the wrong size, i cant use the buttons
[01:13] <savvas> menu System > Shutdown is removed?
[01:14] <Turl> savvas: seems so :p
[01:14] <Turl> so when the fast user swithing thingy crashes, you can't shut it down easily :(
[01:14] <Turl> can anyone reproduce https://bugs.launchpad.net/bugs/332343 ?
[01:14] <savvas> Turl: i think you can use alt+F4 :)
[01:15] <Turl> alt+f4 is suspend iirc
[01:15] <savvas> i mean ctrl+alt+f4
[01:15] <savvas> grr
[01:15] <savvas> i mean ctrl+alt+del
[01:15] <Turl> yeah, that makes the dialog appear
[01:15] <Turl> but it's really ugly :p
[01:17] <ph03n1ks_> hey guys, any of ye know anything about the jaunty netbook remix image?
[01:22] <Stralytic> karmic koala... is mr shuttleworth on drugs? the names keep getting weirder
[01:29] <charlie-tca> description/animal is the same as always
[01:30] <ian1> what's up with with the "evolution-indicator" dialog on new email?  gah that's ugly :)
[01:30] <ian1> it duplicates the nice looking popup in the corner, too.  I imagine it can be disabled but why did it just turn on?
[01:31] <Stralytic> i think the pulseaudio fix has finally made it to lpia
[02:02] <scopecreep> can anyone help me get my alps touchpad scrolling working?  i installed gsynaptics and it enables/disables the touchpad, but scrolling no worky
[02:02] <scopecreep> it mouses and clicks fine though
[03:09] <usser> hey guys
[03:09] <usser> my synaptics touchpad scroll doesnt work in jaunty, and during bootup it says something like: "synaptics failed to start from resume"
[03:09] <usser> anyone have a similar issue?
[03:10] <usser> also on intel driver the windows redraw slowly. Appear slowly rather there's like a 1 sec delay between clicking on minimized window and it appearing, 3d games work fine glxinfo reports direct rendering enabled
[04:14] <lws> hI
[04:15] <lws> I am trying to turn on ATheros 802.11 wireless lan card drivers within Jockey
[04:15] <lws> and it's saying "THis driver was just disbaled, but is still in use"
[04:15] <lws> right after I *enable* it
[04:15] <lws> any idears?
[04:17] <crdlb> I'm not sure, but I don't think you want to enable that driver
[04:18] <crdlb> the ath5k driver appears to be included in jaunty's kernel now
[04:18] <crdlb> the one in jockey is madwifi, which is being replaced by ath5k
[04:19] <lws> does ath5k reliably support AP mode?
[04:19] <lws> I bought a DWA-552 and ath9k was extremely crappy on it.
[04:19] <lws> so I switched back to my old card that I had madwifi running on my old server with
[04:21] <crdlb> you want to be an access point?
[04:21] <lws> yes
[04:21] <crdlb> never tried that :)
[04:22] <lws> had the DWA_552 working with ath9k
[04:22] <lws> but it was just operating like absolute crud
[04:22] <lws> madwifi at least worked reasonably
[04:23] <lws> for this other trendnet card that was about 1/4th the price of the DWA_552
[04:26] <lws> hmm WPA2 is broken in the jaunty hostapd apparently
[04:59] <chu_> Hi - as I understand Jaunty will ship with 2.6.28, correct?
[05:01] <crdlb> yes
[05:04] <ziroday> chu_: but the kernel team cherry pick patches from .29
[05:04] <chu_> Oh sweet.
[05:04] <chu_> If I *need* some aspect from .29, can I request it be added to 9.04? :D
[05:05] <ziroday> chu_: usually its only for bugs
[05:05] <ziroday> err bug fixes
[05:05] <chu_> Well, acpi support is broken on .28, but there's a fix in .29.. what are the odds?
[05:05] <ziroday> chu_: is a bug filed?
[05:06] <chu_> I've seen the bug on bugzilla... and have seen it on launchpad (actually how I found out there was a fix in .29)
[05:06] <ziroday> chu_: well I would talk to the kernel team and watch the LP bug
[05:07] <chu_> Ok thanks, pretty much exactly what I wanted to hear.
[05:10] <dfgas> so, jaunty works extrememly well with netbooks ehh?
[05:42] <TuTUXG> when there gonna be a 2.6.28 rt kernel in the official repo?
[05:42] <AnAnt> what is kernel mode setting ?
[05:42] <TuTUXG> !rt
[05:43] <AnAnt> !modesetting
[05:43] <AnAnt> !mode-setting
[05:45] <maco> !kms
[05:45] <maco> ok nvm
[05:46] <Daemonbuntu> are DNS lookups working slowly for everyone on Jaunty?
[05:46] <ziroday> AnAnt: KMS is what is needed for plymouth
[05:47] <ziroday> Daemonbuntu: it could be an ipv6 issue
[05:47] <AnAnt> ziroday: plymouth is like usplash ?
[05:47] <Daemonbuntu> is that a system service I can turn off?
[05:48] <ziroday> AnAnt: yep
[05:48] <ziroday> Daemonbuntu: you can try http://www.ubuntugeek.com/how-to-disable-ipv6-in-ubuntu.html
[05:50] <AnAnt> ziroday: before final release of intrepid developement , there was a different way to set the VT resolution, was that KMS ?
[05:50] <ziroday> AnAnt: not quite sure what you're talking about that, but I don't think so
[05:50] <AnAnt> ok
[05:51]  * Daemonbuntu curses at IPv6 by default
[05:51] <AnAnt> I just saw a vid. of switching between X & VT using KMS ! fast indeed !
[05:51] <maco> Daemonbuntu: cjwatson has a libc6 that fixes it in his ppa
[05:51] <Daemonbuntu> at least Windows has a reasonable wrapper for it that most users won't notice
[05:51] <ziroday> AnAnt: see https://wiki.ubuntu.com/UDSJaunty/Report/Desktop#Plymouth
[05:51] <maco> Daemonbuntu: he's asking for testers, though so far all results have been positive
[05:51] <maco> Daemonbuntu: let me find the bug
[05:52] <maco> Daemonbuntu: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/313218/comments/47
[05:53] <Daemonbuntu> thanks for the suggestion, I'll reboot after my movie is over
[05:53] <AnAnt> man, if only intel driver supports KMS, that's a problem ! I wonder if ATI/NVIDIA proprietary drivers will ever support that
[05:54] <ziroday> AnAnt: there are plans for both ati/nvidia drivers to support kms. There is a plymouth package if you want to try it out
[05:55] <AnAnt> ziroday: will it be easy to make plymouth themes ?
[05:56] <ziroday> AnAnt: not sure, never tried it
[05:59] <AnAnt> well, thanks
[06:03] <Daemonbuntu> well, disabling ipv6 worked, I don't care about patching it cause nothing I have is even ipv6 compatible
[06:04] <helo> i have no oss/alsa audio, but the console echo '\a' is incredibly loud heh
[06:09] <dtchen> helo: we need more info than that
[06:11] <helo> intel 82801g audio chipset (hp mini)
[06:11] <helo> it worked fine with intrepid
[06:12] <dtchen> please run http://www.alsa-project.org/alsa-info.sh
[06:12] <dtchen> (using bash)
[06:13] <hanasaki> can the "create boot usb " be used once booted to install ubuntu on a pc?  what program do I run?
[06:14] <maco> hanasaki: it should still be in the menu, i think
[06:15] <hanasaki> thakns.. I do not see it.. can you tell me what menu and what program name?
[06:15] <ziroday> hanasaki: System > Administration > Create a USB Boot Disk
[06:16] <hanasaki> ziroday:  yes.. I have that.. once I boot.. where is the  option to install ubuntu  on the system I booted the usb on?
[06:16] <ziroday> hanasaki: you have to configure your bios to boot from the USB disk
[06:17] <hanasaki> I have that covered.  the usb is booted.  what menu item do I need to run to install ubuntu on the HD of the system I booted the usb on?>
[06:18] <ziroday> hanasaki: ah! I'm not sure if the USB install can do that :P, if its anywhere it'll be in System > Administration > Install
[06:18] <hanasaki> hmmm what progam can I apt-get that is the installer?
[06:19] <ziroday> hanasaki: ubiquity, not sure if it will work though
[06:19] <hanasaki> thanks. i will try it.  dont have a cdrom drive to boot..... any other suggestions?
[06:19] <chronic> how can i adjust contrast in kde4?
[06:20] <ziroday> !install | hanasaki read this
[06:20] <chronic> can fglrx be installed on 9.04?
[06:21] <helo> http://www.alsa-project.org/db/?f=5b16b616be59357bc56167043598356fc7134a7d
[06:22] <ziroday> chronic: I believe so
[06:22] <ziroday> helo: you might want to show dtchen
[06:23] <chronic> ziroday: will it work if i install it with aptitude or is there anything else i need to do to configure it?
[06:23] <ziroday> chronic: jockey should detect it
[06:24] <chronic> well, i guess the only way to find out is to do it, as always
[06:24] <dtchen> helo: is `speaker-test -c2 -Dplughw:0' likewise inaudible? can you mute (set nocap) the 'Analog Loopback's?
[06:28] <chronic> ziroday: thanks, got to reboot
[06:30] <helo> hnmm
[06:30] <helo> Playback open error: -16,Device or resource busy
[06:30] <dtchen> sudo fuser -v /dev/dsp* /dev/snd/* /dev/seq*
[06:30] <Daemonbuntu> is there any way to fix KDE not being able to mount audio CDs?
[06:31] <Stralytic> didn't know you could mount an audio cd
[06:31] <Daemonbuntu> KDE doesn't recognize audio discs, only data ones
[06:33] <maco> Daemonbuntu: audio disks dont get mounted
[06:33] <maco> Daemonbuntu: but um, yeah, amarok2 doesn't do CDs i heard
[06:33] <maco> someone was complaining about the decision to have it not do CDs the other day
[06:33] <Daemonbuntu> maco: My GNOME apps can't recognize the discs in KDE, but can under GNOME
[06:34] <maco> oh well that's shiny
[06:35] <helo> http://helo.org/fuser-alsa.txt
[06:35] <dtchen> helo: close rhythmbox first, then retry the speaker-test
[06:36] <helo> it acts like it is working, but no sound
[06:37] <helo> well, no errors at least
[06:37] <dtchen> does `sudo /etc/init.d/alsa-utils reset' help?
[06:40] <helo> resetting alsa... Invalid card number.
[06:44] <helo> (and many other errors)
[06:45] <helo> looks like --help output from alsactl repeated several times
[06:47] <chronic> was the alt+f2 changed to something else for lounching apps?
[06:48] <helo> works for me
[06:48] <chronic> not for me
[06:48] <chronic> must be keyboard problem
[06:49] <chronic> what's the name of that app?
[06:51] <maco> chronic: its part of gnome-panel. if kde user, krunner
[06:51] <chronic> thanks
[07:18] <DanaG> ugh, try hitting "previous track" over and over so notifications for the first track repeat.........
[07:18] <DanaG> it goes on and on and on and on and  on and  on and  on and  on and  on and
[07:18] <DanaG> ... and so on.
[07:18] <DanaG> And there's no way to dismiss them.
[07:21] <Stralytic> why doesn't the installer add the user it creates to the audio group?
[07:22] <helo> audio can be dangerous for mere mortals to use
[07:22] <Stralytic> so a user migrating from windows is expected to know that they have to add their user to the audio group to get sound to work?
[07:24] <dtchen> Stralytic: no, that's a bug when it occurs. Normally it does not occur.
[07:24] <Stralytic> so sound should work  without being in the audio group?
[07:24] <dtchen> no, your user normally is added to the audio group
[07:25] <Stralytic> ic
[07:25] <Stralytic> i wasn't added to the video group either
[07:33] <orgthingy> Which version of debian is it based on?
[07:33] <dtchen> to what does "it" refer?
[07:34] <orgthingy> 9.04, dtchen
[07:39] <dtchen> orgthingy: Debian testing/unstable
[07:39] <orgthingy> testing as in when Lenny was testing?
[07:39] <dtchen> orgthingy: there is no specific version on which jaunty/9.04 is based
[07:39] <dtchen> no
[07:39] <orgthingy> or just sid-of-that time?
[07:39] <dtchen> source packages are synced from sid automatically until DebianImportFreeze
[07:39] <orgthingy> dtchen: ah, so best of whatever-it-should-do? neat
[07:40] <dtchen> at anytime, source packages can be synced from wherever
[09:07] <bernard__> Anyone else's system become 'sluggish'?
[09:08] <bernard__> Like, three second pauses between switching windows, that sort of thing?
[09:08] <bernard__> It's not like anything's eating up excess CPU or anything.
[09:15] <idorock89> so i resisted the temptation of upgrading to jaunty till now but now with the notifications being stable and all i think i want to upgrade.
[09:16] <idorock89>  so first a few questions is jaunty stable enough? this is the only machine i have so cant deal with huge problems.
[09:16] <bazhang> alpha4?
[09:16] <idorock89> 2nd ly i have a nvidia graphics card so are the resticted drivers released and are they stable enugh?
[09:16] <idorock89> bazhang: yeah
[09:16] <bazhang> from the topic:
[09:17] <bazhang> "it will most certainly break your system in bad ways"
[09:17] <idorock89> bazhang: i am ready to deal with few minor issues cant have huge problems. i have read that topic want to know from other users's experience do they find it stable somewhat atleast
[09:17] <idorock89> and also the nvidia drivers issue?
[09:17] <bazhang> break your system does not seem minor
[09:18] <bazhang> I would run in vm or wait for late beta/RC
[09:19] <idorock89> hmm... alright. but i thought that we are nearly at alpha 5 so it might be rid of most of the major problems
[09:19] <idorock89> and would someone pls tell me the situation of the nvidia drivers?
[09:20] <bernard__> I think they're supposed to work if you tell them to ignore the ABI.
[09:20] <bernard__> But I have ATI, so I'm not 100%.
[09:22] <idorock89> oh i thought that abi issue waas solved . could someone with nvidia card and on with latest updates please confirm the status?
[09:31] <ziroday> idorock89: get the livecd and try it out
[09:41] <idorock89> ziroday: but frm the livecd i cant try out the nvida restricted drivers
[09:42] <ziroday> idorock89: yes you can...
[09:44] <idorock89> ziroday: that will a little difficult as i will have to set up my net connection as it requires some work for ti.
[09:44] <ziroday> idorock89: well that is the best way to see if your card works. There were a couple of nvidia related uploads on Feb 1st if that helps
[09:45] <idorock89> so if someone already on the alpha latest could tell me the situation that would be really nice
[09:57] <lukehasnoname> Question (I know you guys have probably heard this a lot) but how is X and the drivers in Jaunty? Is .29 kernel expected to make it? And are there any other showstoppers I should know about?
[09:57] <lukehasnoname> I want to install it (I installed Intrepid around Alpha 5 with little trouble, and for testing, but this is my main machine).
[09:58] <dns53> they tend to get x and the kernel all fixed in the last week or two
[09:59] <Stralytic> i've read they're sticking with 2.6.28, and X is stable as long as you dont have ati/nvidia graphics
[09:59] <dns53> the proprietary nvidia drivers did not work for me last week
[10:00] <SwedeMike> lukehasnoname: I started with 8.10 around alpha2, so far 9.04 alphas have had more problems than 8.10 had during that development cycle
[10:00] <Stralytic> dns53,  there aren't any proprietary drivers written for the new version of X
[10:02] <lukehasnoname> Hm
[10:05] <twager> lukehasnoname: Just come i=on the channel but have you tried it in a v/b ?
[10:06] <lukehasnoname> My laptop doesn't support virt
[10:06] <lukehasnoname> I haven't tried paravirt
[10:07] <twager> lukehasnoname: Sorry..Did not realise  you were talking abt a laptop..
[10:25] <idorock89> it is stupid to say tath all except ati/nvidia work. dont u realise that aorund 90% people have a ati/nvidia card it aint like we r talking of small minority taht no one knows abt
[10:28] <Unggnu> hi all
[10:29] <Unggnu> Does anyone uses Kubuntu Jaunty on a Sony laptop?
[10:31] <crdlb> idorock89: intel is the number one GPU vendor
[10:32] <idorock89> anyone who has half a decent computer has a nvidia or ati card. only reason for intel to be major is that it comes onboard by default on many motherboards.
[10:32] <idorock89> and anyways my point is there is a VERY VERY large no. of users of ati/nvidia to be ignored
[10:32] <crdlb> intel is perfectly adequate for laptops
[10:33] <idorock89> crdlb: yeah if u never want to play any games
[10:34] <crdlb> if you want to play games on a laptop, why did you get a laptop? :>
[10:34] <idorock89> even then  a good graphix card improves video playback and many other things , blue ray is another eg
[10:34] <crdlb> anyway, most ATI cards are reasonably supported (in 2D and some 3D) via the radeon driver
[10:34] <crdlb> and nv provides nvidia 2D
[10:35] <idorock89> crdlb: this is a pointless debate if i have a graphix card i should be use it to maximum of its capabilities .  and not being able to do so is a problem
[10:35] <bazhang> in an alpha?
[10:35] <crdlb> for an alpha release
[10:35] <idorock89> dont tell me propriteary problems and all it is a problem currently and we should accept that
[10:35] <idorock89> anyways lets change the topic
[10:35] <crdlb> this is not ubuntu's fault
[10:36] <bazhang> certainly !ot for this channel
[10:36] <crdlb> intrepid came extremely close to not having a fglrx at release :/
[10:47] <Unggnu> crdlb: FGLRX is only an option if there is no alternative
[10:47] <Unggnu> which is the case for new Ati cards
[10:48] <crdlb> how new? does radeonhd provide 2d at least?
[10:56] <Unggnu> crdlb: radeonhd doesn't work at all and radeon can only support 2d in newer versions
[10:57] <Unggnu> 4870
[10:57] <crdlb> that's good at least
[10:57] <Unggnu> and the most downpoint is that both drivers doesn't support powerplay which results in enormous noise
[10:57] <Unggnu> *biggest
[10:57] <crdlb> ouch
[10:58] <Unggnu> yeah and I guess this will remain for quiet some time
[10:58] <crdlb> my old radeon 7500 has no heatsink even :)
[10:58] <Unggnu> cool but 7800 was hot too
[10:58] <crdlb> it's the mobile version (M7)
[10:59] <Unggnu> AIGLX implementation of FGLRX doesn't support many kwin features, crashes often and tears with XV
[10:59] <Unggnu> and the openGL video output which doesn't tear with some optimizations is grainy
[11:10] <Unggnu> crdlb: but at least it works and is quiet :)
[11:12] <Unggnu> Does anybody uses Kubuntu on a Sony laptop?
[12:07] <Oli``> is deluge being a CPU hog for anybody else since yesterday's updates?
[12:38] <WT-Udev> Udev seems to be taking ~50% of a core, lots of events like... UEVENT[1235217664.224111] change   /devices/pci0000:00/0000:00:09.0/host0/target0:0:0/0:0:0:0/block/sda (block)
[12:39] <cumulus007> Hi, I'm on Kubuntu jaunty with backports on, and I'm having a problem
[12:39] <cumulus007> there are weird black borders around plasma applets
[12:39] <cumulus007> http://imagebin.ca/view/hB5VIAEG.html
[12:40] <BUGabundo> where are the logs of this channel?
[12:42] <WT-Udev> cumulus007: Might those be window-edges in the shape of a box?  Do you have (IIRC) compositing enabled?
[12:42] <BUGabundo> cumulus007: there are NO backports for jaunty
[12:43] <cumulus007> okay
[12:43] <cumulus007> compositing is disabled
[12:43] <cumulus007> it might be a problem of nv
[12:43] <cumulus007> will try nvidia now
[12:43] <cumulus007> hmm
[12:43] <cumulus007> how to enable ctrl+alt+backspace in Jaunty :P
[12:44] <BUGabundo> dontzap -d
[12:44] <BUGabundo> $ dontzap -d
[12:44] <cumulus007> I tried to grant myself in the configuration dialog of PolicyKit, but that didn't work
[12:44] <WT-Udev> Strange... that actually works for me
[12:44] <chu_> Such a useful command, why would they disable it by default :(
[12:44] <BUGabundo> chu_: upstream decision
[12:44] <BUGabundo> will be changed on all distros
[12:45] <BUGabundo> unless they delta it their selfs
[12:45] <cumulus007> that command didn't make sense
[12:45] <WT-Udev> dontzap doesn't exist as a command under xubuntu
[12:45] <BUGabundo> install it ?
[12:45] <cumulus007> it is installed
[12:45] <chu_> Oh, makes sense when in that context I guess, I heard they disabled it because users would mistake it... Mistake it for what? It's not like you can ctrl+alt+backspace by accident, can you?
[12:45] <WT-Udev> You'd think if they disabled it it would be installed.
[12:46] <WT-Udev> As if they were going for delete instead?
[12:46] <WT-Udev> I dunno
[12:46] <WT-Udev> Those 'across the keyboard' commands are chosen for a reason
[12:46] <cumulus007> LOL, to apply the effect of DontZap, I need to restart X :P
[12:46] <chu_> Well, even if you were going for delete, there's the option of rebooting, idk
[12:46] <chu_> In the login screen I mean.
[12:47] <WT-Udev> Anyway, no one has any idea about tons of Udev spam, near 50% of a single core use etc?
[12:47] <BUGabundo> guys
[12:47] <WT-Udev> I don't have EVMS, but I do have an LVM cryto-root setup (only boot's not encrypted)
[12:47] <BUGabundo> don't discuss this anymore
[12:47] <BUGabundo> there were enough of it on the MLs
[12:48] <chu_> MLs?
[12:48] <BUGabundo> and there are bugs and blue prints
[12:48] <chu_> Sorry :p
[12:48] <WT-Udev> Mailing List?
[12:48] <chu_> Oh, obvious.
[12:48] <chu_> lol
[12:48] <BUGabundo> MLs = mailingst
[12:48] <WT-Udev> https://bugs.launchpad.net/ubuntu/ << is (or was) offline, otherwise I'd be searching it for things to look at
[12:48] <BUGabundo> RT  asac:might be that you haven't heard it yet; so, the next name for 9.10 is announced: "Karmic Koala" http://is.gd/kg1K
[12:49] <chu_> WT-Udev, it seems offline for me too
[12:49] <WT-Udev> That's too close to comic Koala
[12:49] <WT-Udev> (Error ID: OOPS-1148C1473) << message from the last version of the bugs page that loaded
[12:49] <BUGabundo> bbl
[12:50] <WT-Udev> Guess I don't have even read only access to that
[12:51] <WT-Udev> Oh yeah, it also took me like... 40 min to boot in to my laptop x.x  TONS of disk thrashing before the crypto-devs were even unlocked
[12:52] <askand1> Does googlecalendar in evolution work for anyone in Jaunty?
[13:15] <DrHalan1> hey, can i report a bug taht on ubuntu qt4.5 doesnt have the gtk+ theem by default?
[13:21] <jpds> DrHalan1: Erm, they're both different technologies.
[13:22] <DrHalan1> jpds
[13:22] <DrHalan1> you didint understand what i mean
[13:22] <DrHalan1> qt 4.5 is now able to use gtk+ to draw its elements
[13:22] <DrHalan1> if you set the theme to gtk+ all qt app look like native gtk+ apps
[13:23] <DrHalan1> but it is not the default setup :(
[13:32] <WT-Udev> DrHalan1: Maybe the look of QT4 is prefered over gtk+?  Though if you change the setting it should look like that.
[13:32] <DrHalan1> yeah it does
[13:32] <DrHalan1> but would be cool if it would detect the gnome session
[13:33] <DrHalan1> so all users have the same look all over their desktop
[13:33] <WT-Udev> Oh, yeah.  I see what you mean there, but I think that's beyond current configurations
[13:33] <WT-Udev> You mean using QT4 aps UNDER gnome it might have different settings, or at least ask.
[13:36] <DrHalan1> jap
[13:36] <DrHalan1> there are some apps taht are commonly used on gnome
[13:36] <DrHalan1> like mumble
[13:38] <WT-Udev> I don't even know what mumble is
[13:41] <DrHalan1> its like teamspeak but open source
[13:41] <DrHalan1> well whatever :D
[14:04] <WT-Udev> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/332270/comments/11 << I might have a problem here.  aptitude reinstall udev isn't populating what I think should be there (more than I see here)
[14:06] <dfgas> jaunty is made for netbooks as well too ehh? and boots fast?
[14:07] <tommi_> Has anyone had a problem with fonts defaulting to sans in kub jaunty after last nights updates?
[14:09] <WT-Udev> dfgas: Well, I can't really compare as I'm running an LVM+crypto setup for everything important.... and a bit that's not so critical to be encrypted.
[14:10] <WT-Udev> However it was 'fast enough' until recent udev (symptoms/probems)
[14:20] <TuTUXG> !ubuntustudio
[14:37] <albert23> WT-Udev: udev rules are now in /lib/udev/rules.d
[14:37] <WT-Udev> albert23: Ahh, that really scared me not seeing them where I expected them.
[14:39] <WT-Udev> I see, there's a readme... My flaw was being too worried about files not existing to read what did exist
[15:09] <savvas> anyone using jaunty and vlc?
[15:10] <savvas> bug 314038 - I made some test packages to fix the not embedded video problem
[15:16] <siegie> Sakarias: i'm using jaunty and vlc, are the packages in your ppa save?
[15:18] <siegie> ah srry i was talking to savvas
[15:18] <savvas> siegie: not all of them
[15:18] <savvas> use the link to the vlc directly
[15:19] <savvas> http://ppa.launchpad.net/medigeek/ppa/ubuntu/pool/main/v/vlc/
[15:20] <siegie> savvas: thanks it seems to work :)
[15:27] <savvas> siegie: please add a comment to the bug report :)
[15:27] <siegie> already done
[15:27] <savvas> thanks.. and stress-test it a bit, I don't want to be blamed afterwards heh
[16:04] <salty-horse> hi. anyone noticing a bug where when windows change their icon it is not updated on the window decoration (metacity) or the window list? and sometimes it updates only in one of them? (it's visible with pidgin status icons)
[16:05] <triggerhapp> I actually dont use a single program that changes its icon while running o.o
[16:09]  * tritium hopes today's daily build's partitioner is fixed
[16:13] <TuTUXG> tritium, what was wrong with it?
[16:14] <tritium> TuTUXG: partitioner hung and would not proceed to next phase of install.
[16:15] <tritium> I had 1 swap, 2 ext3, and 1 XFS partition, and it sat all night.
[16:15] <WT-Udev> tritium: Booting an already installed laptop that used to take <5 min now takes nearly an hour...w ith -tons- of udev messagex x.x
[16:16] <tritium> WT-Udev: hmm, wow
[16:16] <TuTUXG> ext4?
[16:16] <WT-Udev> ext3
[16:16] <WT-Udev> LVM and crypto though
[16:17] <WT-Udev> At least, I think I picked ext3... I was sick of reiserfs3 (and the last time I used 4 I ended up loosing lots of data before I realized it...)
[16:18] <WT-Udev> XFS doesn't make much sense on a laptop...
[16:18] <TuTUXG> WT-Udev, y?
[16:19] <TuTUXG> in my case, xfs was much faster than ext3 on my laptop
[16:20] <WT-Udev> Actually I might be wrong, I can't think of anything but a gut instinct on why.  However single, slow, disk... but the most major problem.  XFS doesn't have a shrink option and I've found out that I could really use one for migrations.  It's not something I've needed on my laptop yet, but in other places it's been an issue.
[16:42]  * BUGabundo wonders what was decided about UM checking for ubuntu-desktop.... I had to leave the roam in the middle of the discussion!
[16:44] <WT-Udev> BUGabundo: from what I can see at a glance... it stopped dead when you left
[16:45] <BUGabundo> eheh
[16:45] <BUGabundo> mvo and fte were making a new WAR
[16:45] <BUGabundo> so I ended up not knowing what is the current state
[16:45] <BUGabundo> bug or no bug
[16:46] <BUGabundo> I'll have to wait for mvo to come back
[16:46] <BUGabundo> but thanks WT-Udev
[16:46] <BUGabundo> are there any logs of this #?
[16:46] <WT-Udev> I always autolog irc
[16:46] <WT-Udev> I can't recall doing anything important in here (security wise)
[16:47] <WT-Udev> However I've been in here for about 5-6 hours now
[16:47] <WT-Udev> so that might not be very useful for you
[16:47] <IntuitiveNipple> WT-Udev: Did you solve the slow disk/udev issue?
[16:48] <WT-Udev> IntuitiveNipple: I don't even have a clue where to start, so I posted what little I'd done to the bug-thread and shut my laptop down for the 'night'
[16:49] <WT-Udev> I'm really starting to get sleepy too, so I probably won't be awake for much more than an hour, and I'd barely rate my self as lucid at the moment.
[16:49] <charlie-tca> BUGabundo: This channel is officially logged at http://irclogs.ubuntu.com/
[16:49] <IntuitiveNipple> WT-Udev: same here... got up at about 2am and didn't go back to bed.
[16:49] <IntuitiveNipple> WT-Udev: What is the 'bug- thread' ?
[16:50] <WT-Udev> IntuitiveNipple: Working night shift ATM...
[16:50] <WT-Udev> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/332270
[16:50] <IntuitiveNipple> Thanks
[16:50] <WT-Udev> IntuitiveNipple: BTW, if you boot with an older kernel it may (slowly) work
[16:50] <BUGabundo> thanks charlie-tca
[16:51] <charlie-tca> no problem.
[16:51] <WT-Udev> If that doesn't work, I'm going to have to look up the crypt-setup luks stuff again when I boot off pxe or a flash drive.
[16:52] <IntuitiveNipple> WT-Udev: see https://bugs.edge.launchpad.net/ubuntu/+source/udev/+bug/332416
[16:53] <IntuitiveNipple> If you can apply the down-grade fix you might be safe for now
[16:56] <WT-Udev> IntuitiveNipple: don't have dailys and I don't have much space set aside to cache old packages so it wouldn't be in there.  It'd be easier to just check for an update when I wake up again.
[16:56] <WT-Udev> Besides, if I still have the problem and can boot in to it I can help test it.
[16:57] <IntuitiveNipple> I'm patching it now
[16:57] <IntuitiveNipple> It's the inotify by the look of it
[16:58] <WT-Udev> Notify FOREVER?
[17:04] <soc1> hi
[17:04] <soc1> just tested the live-cd from yetserday
[17:04] <soc1> install fails after committing the manual partitioning
[17:04] <soc1> is there already a launchpad bug for it?
[17:04] <soc1> or is this new?
[17:05] <WT-Udev> I think I heard someone else mention the problem last night.
[17:05] <IntuitiveNipple> WT-Udev: I'm uploading a test package of udev to my PPA shortly
[17:05] <soc1> when i click "next" in step 5 (manual setup of partitions) the mouse keeps spinning but doesn't do anything anymore ...
[17:05] <WT-Udev> 20090221-08:09:32  * tritium hopes today's daily build's partitioner is fixed
[17:05] <WT-Udev> 20090221-08:14:47 < tritium> TuTUXG: partitioner hung and would not proceed to next phase of install.
[17:06] <WT-Udev> 20090221-08:15:11 < tritium> I had 1 swap, 2 ext3, and 1 XFS partition, and it sat all night.
[17:06] <soc1> WT-Udev: do you know more?
[17:06] <dudus> WT-Udev: I'm intended to try the daily-live tonight, I wonder if there is a bug repport somewhere
[17:06] <WT-Udev> Sat Feb 21 09:06:25 PST 2009
[17:06] <WT-Udev> Nope
[17:06] <WT-Udev> You can try searching for it
[17:06] <soc1> mhh, but the update should be installable with the live-cd running?
[17:06] <WT-Udev> soc1: whatever live cd you have will not work that way
[17:07] <WT-Udev> You may be able to get the same result on a console though... I'm unsure.
[17:08] <pranith> hello
[17:08] <tritium> WT-Udev: who knows why I had trouble.  Could be something with XFS, or who knows what.  Perhaps it'll work better for you.
[17:09] <WT-Udev> soc1: in other words, the code you have right now is either on CD-R (Write Once Read Many) or CD-RW (re-writable...) and is 'broken'
[17:09] <WT-Udev> tritium: it's not me installing
[17:10] <soc1> WT-Udev: but an update with apt of the broken component could fix it (as long as i don't have to reboot), right?
[17:12] <WT-Udev> soc1: Hum... I don't know.  If the cd uses unionfs or something similar you might be able to fit that update in to ram and run with it.  It's a -maybe-.
[17:13] <WT-Udev> I assume it would fail pretty quickly if that wouldn't work so good luck
[17:19] <WT-Udev> You know... I try to keep my name different every time I have a problem and rejoin freenode.  This time I was WTFing at udev...
[17:21] <BUGabundo> ahh ok
[17:21] <vbgunz> anybody know why toolbar icons default size is bigger than I actually set?
[17:22] <WT-Udev> vbgunz: can you be slightly more specific?
[17:22] <vbgunz> toolbar icons default size seems to be medium. under my systemsettings toolbar and main toolbar icon sizes are set to small
[17:23] <vbgunz> konqueror, kmail, etc all have bigger icons on there toolbars than they're supposed to
[17:23] <WT-Udev> thank you, I don't know what's wrong, but that is probably specific enough for you to search bug reports or get an answer from someone that does know.
[17:34] <BUGabundo> does any one knows where to had apps that need patching, to the new notifications?
[17:34] <BUGabundo> is it the wiki (https://wiki.ubuntu.com/NotifyOSD/Comments) or LP?
[18:06] <IntuitiveNipple> WT-Udev: udev 138-2~tj~ppa1j is in my PPA for testing (https://edge.launchpad.net/~intuitivenipple/+archive/ppa/)
[18:08] <WT-Udev> I should be asleep... but... may as well give that a try
[18:08] <WT-Udev> Oh crap, IntuitiveNipple do you know a kernel param i can add to disable inotify?
[18:09] <WT-Udev> Hoping recovery mode bypasses it by being single user
[18:09] <IntuitiveNipple> No, you would need to disable the udev service :)
[18:10] <BUGabundo> funny enough PA 9.14 makes my pidgin crash much more then 9.15~test2
[18:11] <WT-Udev> IntuitiveNipple: I've not done that in quite a while, would I be able to get a console and ethernet with that?
[18:14] <WT-Udev> Right, forget waiting for the system.  The last time I booted that it took 45 min.
[18:17] <SiDi> hey peeps, do you know if the UDS are public events ?
[18:17] <IntuitiveNipple> WT-Udev: Easy way to do it. Start from a live-CD, unlock the encrypted volume(s), vgscan + vgchange, then create a chroot and update the package that way
[18:19] <WT-Udev> IntuitiveNipple: I had a flash drive with systemrecovery'cd' on it.  I'm chrooted in to my / partition now (no seperate /usr), I didn't bind mount dev or proc though.
[18:19] <WT-Udev> IS there an env-update command like gentoo has?
[18:20] <IntuitiveNipple> It would help to bind /proc /dev /sys just in case
[18:20] <IntuitiveNipple> The you can add my PPA, update, and then apt-get the package
[18:20] <IntuitiveNipple> s/The/Then/
[18:21] <WT-Udev> Ah forgot /sys
[18:21] <IntuitiveNipple> This may help: http://tjworld.net/wiki/Linux/Ubuntu/Packages/MyPPA
[18:25] <WT-Udev> What a pain...  I think I got the network setup right
[18:25] <WT-Udev> trying to recall this at your equivilent of 1am is not fun
[18:26] <WT-Udev> IntuitiveNipple: Your quotes are wrong
[18:28] <WT-Udev> IntuitiveNipple: Also, doesn't tee default to over-write?  Or does it -a by defautl?
[18:29] <salty-horse> can anyone confirm this? https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/332624
[18:29] <IntuitiveNipple> tee overwrites which is what it is intended to do
[18:29] <WT-Udev> echo "deb http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu $(lsb_release -sc) main' | sudo tee /etc/apt/sources.list.d/intuitivenipple.list"
[18:29] <WT-Udev> echo 'deb-src http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu $(lsb_release -sc) main' | sudo tee /etc/apt/sources.list.d/intuitivenipple.list"
[18:29] <WT-Udev> So I should have only done the second?
[18:29] <IntuitiveNipple> I've updated the quotes, thanks
[18:29] <BUGabundo> what was that bug, for system to be SLOWWWWWWW?
[18:30] <IntuitiveNipple> No, the first... you don't need the deb-src
[18:30] <WT-Udev> two python updates are going in with the update as well
[18:30] <BUGabundo> I'm being aftected by it, after the last batch of updates
[18:30] <IntuitiveNipple> you should just need to do apt-get install udev=138-2~tj~ppa1j
[18:30]  * WT-Udev shrugs
[18:31] <WT-Udev> those three are going in as well
[18:31] <IntuitiveNipple> BUGabundo: This? https://bugs.edge.launchpad.net/ubuntu/+source/udev/+bug/332270/comments/13
[18:31] <WT-Udev> Hum... this could be a problem... but it's my problem.
[18:31] <WT-Udev> device-mapper: table ioctl failed: No such device or address
[18:32] <miik> anyone noticed that playing mp3 in totem sometime very laggy?
[18:32] <miik> then i close totem, and start again, then its laggy again
[18:32] <miik> then i close and start again, this time it works and play music nice
[18:37] <WT-Udev> IntuitiveNipple: failed to boot with -8, but that may be because the initrd creation might have failed and left me with a stale initrd (and old udev inside it)
[18:38] <WT-Udev> -7 is booting and seems to be proceeding more rapidly
[18:38] <WT-Udev> I'll try updating the initrd and rebooting after it's loaded
[18:38] <IntuitiveNipple> OK
[18:38] <IntuitiveNipple> I'm trying not to have to restart for now because I've got so much to do, I don't want to be chasing another bug just to be able to work :)
[18:39] <WT-Udev> I know the feeling... I -loathed- the prospect of a 45 min boot time
[18:40] <WT-Udev> Already your patch has cut that to about 5-10
[18:43] <FFForever> how do i disable the crash manager in kde?
[18:44] <FFForever> also dtchen if ur around any idea when the audio kernel fix will make it to the repo's?
[18:45] <WT-Udev> IntuitiveNipple: I see some of the errors still, and it's not at full speed but it is much faster than earlier.  Still major hard disk activity.  I think it's only partly installed though, so I'm going to try re-installing it and rebuilding the initrd when I finally do get in.
[18:46] <IntuitiveNipple> WT-Udev: OK, thanks. I picked the most obvious-looking commit in git and reverted it, so there could be more to do
[18:48] <WT-Udev> I'll update again once I give it a full test
[18:54] <WT-Udev> I may have spoken too soon.  / and /home mounted fairly quickly but my 'large files' partition for projects and such is taking forever.... and wired networking seems to start after that...
[18:55] <pavs> I have jaunty running and I want to know how I can enable the new notification option notify-osd?
[18:55] <dudus> I'm downloading daily-live from cdimages. But it's damn slow... is there a mirror for these files?
[18:56] <pavs> will just installing the new updates do?
[18:57] <BUGabundo> dudus: NO
[18:57] <BUGabundo> pavs: check if you have ubuntu-desktop installed (if you are on ubuntu/gnome)
[18:57] <BUGabundo> it should pull indicator-applet
[18:57] <pavs> yes I do
[18:58] <BUGabundo> pavs: $ apt-cache policy indicator-applet
[19:00] <WT-Udev> well... here goes the test
[19:02] <WT-Udev> IntuitiveNipple: it doesn't look hopeful now that I'm watching 'the pot' (waiting for it to boil...)
[19:02] <IntuitiveNipple> WT-Udev: Thanks... I'll test it in a VM
[19:03] <IntuitiveNipple> I'm juggling so many bugs today I'm losing track of where I am :D
[19:03] <WT-Udev> IntuitiveNipple: A note, It -really- seems to be agrivated by the -8 version of the kernel.
[19:03] <WT-Udev> Oh, and it finally unlocked /
[19:04] <WT-Udev> that's about 5 min, between normal lines.
[19:04] <IntuitiveNipple> hmmm
[19:04] <WT-Udev> Who knows how many of /sys/devices/pci0000:00/0000:00:09.0/host0/target0:0:0/0:0:0:0/block/sda/sda1 (numbers counting down) it printed...
[19:09] <albert23> IntuitiveNipple: you need to drop the OPTIONS+="watch" line from 60-persistent-storage.rules. That's the one causing trouble with lvm. See comment 10 in the bug.
[19:10] <IntuitiveNipple> albert23: Thanks. I'll revisit the git commits in a few moments
[19:12] <WT-Udev> this is painful...
[19:12] <WT-Udev> 'waiting for the root filesystem' x.x
[19:13] <WT-Udev> IntuitiveNipple: yeah, I'm using 'the kitchen sink' less raid.
[19:14] <WT-Udev> That's only because it's a laptop and has a single drive.
[19:14] <IntuitiveNipple> Booting my crypt+LVM virtual machine now
[19:17] <IntuitiveNipple> I have this laptop with LVM + encryption. About 17 LVs of which 4 are encrypted
[19:17] <WT-Udev> Fun
[19:17] <IntuitiveNipple> makes it easier to manage space with LVs
[19:17] <WT-Udev> I only have /, /home, and another partition.
[19:17] <WT-Udev> Indeed
[19:18] <WT-Udev> Though I haven't felt the desire to resize and install another system... 9.04's teething pains are making me consider it (probably 8.10 next to it... but then the config files...)
[19:19] <IntuitiveNipple> I split things down. I keep a /home/all/ where I mount file-systems for things like Media, SourceCode, VirtualMachines and so forth.
[19:19] <pavs> BUGabundo it say "Unable to locate package indicator-applet". just finished installing all the latest updates...
[19:24] <albert23> hmm, udev on bzr is not up to date: 137-3 unreleased...
[19:25] <albert23> that's why it doesn't show the watch option in 60-persistent-storage.rules
[19:27] <WT-Udev> IntuitiveNipple: I just told my laptop to mount the last partition.  Using -7 since it has slightly less of a headache booting.
[19:28] <IntuitiveNipple> okay... best to revert to udev 137-2 then
[19:29] <WT-Udev> So, testing pattern, ssh in, disable new sources, update udev, modify the rule file to remove watch, then re-create the initrds then test?
[19:30] <IntuitiveNipple> To revert, just do "sudo apt-get install udev=137-2"
[19:30] <WT-Udev> ok
[19:30] <WT-Udev> as soon as I can login...
[19:31] <IntuitiveNipple> :)
[19:31] <IntuitiveNipple> The VM here is just applying the updates
[19:32] <WT-Udev> Miles faster than this on real 'metal'
[19:32] <WT-Udev> It probably doesn't have disk-seeking to contend with
[19:33] <WT-Udev> uggh it's fscking /home
[19:34] <IntuitiveNipple> ok, I've found the commit that applies the watch: f24036d
[19:37] <WT-Udev> You may have a live package for me to test by the time I can login
[19:42] <IntuitiveNipple> Just once, it would be a surprise to find that developers would actually document the new keywords in their documentation!
[19:43] <WT-Udev> If it isn't documented it must not be intended for widespread use.
[19:45] <IntuitiveNipple> hah... the docs don't have it, the NEWS does.
[19:45] <IntuitiveNipple> "Device nodes can be watched for changes with inotify with OPTIONS="watch". If closed after being opened for writing, a "change" uevent will occur."
[19:45] <IntuitiveNipple> No explanation of what kind of inotify it is
[19:46] <WT-Udev> So... any time a close event happens a change event will be triggered... and presumably logged?
[19:46] <WT-Udev> Which could then re-open and ...
[19:47] <WT-Udev> fsck finally done...
[19:47] <WT-Udev> hammering ssh
[19:47] <WT-Udev> You know, if I could make stuff startup at arbitrary points, I'd put SSH just after / was rw
[19:48] <WT-Udev> Ok, I'm in.  Is there a package up for testing or should I manually do it?
[19:49] <IntuitiveNipple> Not yet, but just delete the watch and restart udev
[19:49] <WT-Udev> E: Version '137-2' for 'udev' was not found
[19:50] <WT-Udev> commented out repository, updating/upgrading
[19:53] <IntuitiveNipple> Here's the patch: http://paste.ubuntu.com/121162/
[19:53] <IntuitiveNipple> save it to a file (fix-watch.patch)
[19:54] <IntuitiveNipple> then change to the udev directory (/lib/udev/rules.d/)
[19:54] <IntuitiveNipple> and do sudo patch -p3 < path/to/fix-watch.patch
[19:55] <IntuitiveNipple> If that patch applies ok, you can restart udev: sudo /etc/init.d/udev restart
[19:55] <WT-Udev> I'm currently having issues downgrading
[19:56] <IntuitiveNipple> this avoids the downgrade
[19:57] <WT-Udev> I have a custom version of udev from you though
[19:57] <IntuitiveNipple> It will apply to that, the reverted patch didn't touch that rule I don't think... runs off to check!
[19:59] <IntuitiveNipple> no, that revert didn't touch 60-
[19:59] <WT-Udev> It doesn't seem to on mine...
[19:59] <WT-Udev> 1 out of 1 hunk FAILED -- saving rejects to file 60-persistent-storage.rules.rej
[19:59] <IntuitiveNipple> darn. sorry about that. I'm rushing too much here I guess.
[20:01] <WT-Udev> I just need to revert to the normal package... but can't seem to muddle in to it in my tired state
[20:02] <WT-Udev> apt-get install udev=138-1
[20:04] <WT-Udev> KERNEL!="sr*", OPTIONS+="watch"
[20:04] <WT-Udev> Get rid of that...
[20:04] <albert23> WT-Udev: and update-initramfs -u ...
[20:06] <WT-Udev> update-initramfs -c -k all << I have to use -c otherwise it screws up cryptsetup: NOTE: using /dev/mapper/ubuntu-encryptedroot instead of /dev/ubuntu/encryptedroot for rootvolume
[20:06] <WT-Udev> and skips that
[20:06] <IntuitiveNipple> that'll do it... in the original commit the option was on the same line as the IMPORT
[20:06] <WT-Udev> very painful to get back in
[20:06] <IntuitiveNipple> I posted a fix for cryptsetup initramfs issues last week
[20:07] <IntuitiveNipple> To use UUID and LABEL in crypttab
[20:08] <WT-Udev> Oh YES it works
[20:10] <IntuitiveNipple> I'll update my package then
[20:11] <WT-Udev> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/332270/+editstatus << IntuitiveNipple In Progress?
[20:13] <IntuitiveNipple> Sure... you do that, I'll do the new package and test it in the VM
[20:19] <IntuitiveNipple> what I've done is create a new branch, reset it to before the rules changes and cherry-picked the commits that don't involve the watch rules
[20:21] <tretle> just heard some horrible rumour that canonical are thinking of inlcuding wine with ubuntu? is this true? i hope not
[20:22] <WT-Udev> I rarely if ever use it, but what's so bad about wine?
[20:25] <IntuitiveNipple> There was discussion a while back on the -devel mailing list
[20:31] <IntuitiveNipple> build_test successful. Now to try it in the VM
[20:33] <WT-Udev> what lesson did this illustrate: Never inotify for normal operations of a special device file...
[20:35] <BUGabundo> eheh
[20:36] <IntuitiveNipple> What is interesting is, on the VM, it didn't trigger.
[20:37] <IntuitiveNipple> I wonder what testing was done?
[20:37] <IntuitiveNipple> New version has just gone up to my PPA
[20:37] <WT-Udev> My laptop is already shut down... but it starts quickly.  Would you prefer a test?
[20:38] <IntuitiveNipple> Yes please
[20:39] <IntuitiveNipple> Since I can't get the VM to trigger it
[20:39] <IntuitiveNipple> might have to wait a few minutes for the PPA to build the packages
[20:39] <WT-Udev> Well I can certify it's horrid when it rears it's head on my laptop
[20:39] <WT-Udev> on -8 it even went so far as to crash something with a dump of some kind to the console
[20:43] <WT-Udev> IntuitiveNipple: echo "deb http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/intuitivenipple.list"
[20:43] <WT-Udev> it has an uneven number of "
[20:45] <IntuitiveNipple> eeek
[20:45] <IntuitiveNipple> sorted. thanks.
[20:45] <WT-Udev> ... darn, it hadn't gotten upgraded yet
[20:45] <WT-Udev> the listing page shows you have ppa2j but my laptop put in ppa1j
[20:47] <WT-Udev> IntuitiveNipple: any idea how I can force the sync of the package list?
[20:49] <IntuitiveNipple> sudo apt-get update
[20:50] <WT-Udev> alrady did that and...
[20:50] <WT-Udev> apt-get install udev=138-2~tj~ppa2j
[20:50] <WT-Udev> E: Version '138-2~tj~ppa2j' for 'udev' was not found
[20:51] <IntuitiveNipple> you shouldn't need to specify the version now... it's later than others so should be pulled in
[20:51] <WT-Udev> it's not
[20:51] <IntuitiveNipple> It might be that the archives haven't received the file yet
[20:51] <WT-Udev> besides that, the version isn't found... meaning it wouldn't find it the other way either.
[20:52] <IntuitiveNipple> yes, it is in the archive: http://ppa.launchpad.net/intuitivenipple/ppa/ubuntu/pool/main/u/udev/
[20:53] <IntuitiveNipple> Did you remove my PPA list from apt?
[20:53] <WT-Udev> I added it back
[20:53] <WT-Udev> apt-get install udev=138-2~tj~ppa1j doesn't complain
[20:54] <IntuitiveNipple> sorry no, it isn't in the archive yet. I was getting the "2" confused
[20:54] <WT-Udev> Does that update on the hour?
[20:57] <IntuitiveNipple> I think it just depends on workload of the buildd machines
[20:58] <IntuitiveNipple> Looking at other directories it might be every 20 mins
[20:58] <WT-Udev> Hum... i386, amd64, and Ipia?
[20:58] <WT-Udev> lpia?
[20:59] <WT-Udev> is that for atom processors?
[20:59] <IntuitiveNipple> Low Power Intel Architecture
[21:01] <IntuitiveNipple> They've just arrived in the archive
[21:01] <WT-Udev> Figures
[21:01] <WT-Udev> I was 30 seconds too early on the sleep
[21:04] <WT-Udev> Wow, that's not good.
[21:04] <WT-Udev> Trying again
[21:05] <WT-Udev> first time I did something wrong, probably console suspend or some crap like that
[21:07] <WT-Udev> bug updated
[21:09] <WT-Udev> IntuitiveNipple: do I need to do anything else?  This is the first time I've actually tested a package.
[21:10] <IntuitiveNipple> Maybe report back to the bug report that this package appears to prevent the problem
[21:10] <WT-Udev> 20090221-13:07:03 < WT-Udev> bug updated
[21:10] <WT-Udev> 20090221-13:07:07 -!- Klanticus<EMAIL_ADDRESS>has quit [Read error: 60 (Operation timed out)]
[21:10] <WT-Udev> you mean that?
[21:10] <WT-Udev> https://bugs.launchpad.net/ubuntu/+source/udev/+bug/332270
[21:11] <IntuitiveNipple> That's fine thanks
[21:17] <usser> anybody has a problem with their touchpad, scroll doesnt work in jaunty
[21:19] <LinkinX64> usser, yea i know
[21:19] <IntuitiveNipple> usser: ALPS touchpad here is scrolling
[21:19] <LinkinX64> mine doesnt
[21:19] <LinkinX64> but i am not using jaunty atm
[21:19] <usser> LinkinX64, you have synaptics?
[21:20] <usser> on bootup i notice an error that goes like: synaptics failed to turn on from suspend/resume. Something to that extend, even when doing the cold boot
[21:25] <WT-Udev> usser: I have a synaptics one, the odd thing is the tapping part worked (which I hated) until I diabled it in a config file... but it's never shown up as something I'd be able to reccognize when xinput devices are listed.
[22:00] <Ape> Is there issues with Jaunty and ext4? Should ext4 be stable enough for heavy use when Jaunty is released?
[22:01] <IntuitiveNipple> So far so good, some false alarms but its been okay
[22:01] <Ape> I heard that there might be data loss issues
[22:03] <maco> Ape: right data loss issues still there, i belive
[22:09] <untitled> hello :)
[22:09] <untitled> a little problem here with xorg 1.6.0 RC2
[22:10] <untitled> from jaunty repo
[22:10] <untitled> mouse and keyboard dont work
[22:10] <untitled> is there any magic to fix that? :)
[22:19] <derekS> hey, is there a channel for the new notification system?
[22:20] <Ienorand> derekS: Um, I think this would be the place if any...
[22:20] <derekS> Ienorand: ok
[22:23] <untitled> no? no ideas about xorg and input devices?
[22:28] <Neonexus> anyone having trouble with network manager not connection after recent update?
[22:30] <BUGabundo1> Neonexus: yeah
[22:30] <BUGabundo1> try to restart it or networking
[22:30] <Neonexus> any idea whats up?
[22:30] <BUGabundo1> $ sudo /etc/init.d/NetworkManager restart
[22:30] <BUGabundo1> $ sudo /etc/init.d/networking restart
[22:30] <BUGabundo1> no idea
[22:30] <Neonexus> I have
[22:30] <BUGabundo1> just asked asac about it
[22:31] <Neonexus> weird that my 3g still works
[22:31] <Neonexus> I thought it might be a DHCP issue
[22:32] <untitled> ok, I'll ask in a different way. How can I bypass hal and use xorg.conf again with xorg 1.6?
[22:33] <BUGabundo1> Neonexus: if you have it too, I think we better file a bug
[22:33] <BUGabundo1> so that asac can request info for debugging
[22:33] <BUGabundo1> fileing now
[22:36] <BUGabundo1> Neonexus: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/332706
[22:36] <BUGabundo1> fill free to subscribe and add your system details
[22:36] <BUGabundo1> via apport-collect 332706
[22:44] <danbas> Are there going to be official blu ray isos of the entire jaunty repo for AMD64?
[22:44] <ikonia> danbas: nope, not that I've read
[22:44] <BUGabundo1> NO
[22:44] <ikonia> danbas: no plans to distribute anything on bluray
[22:44] <BUGabundo1> why would there be?
[22:44] <danbas> coz Lenny does?
[22:44] <BUGabundo1> DVD is enough
[22:44] <ikonia> danbas: ubuntu isn't debian
[22:45] <BUGabundo1> the rest you get from archive
[22:45] <BUGabundo1> if you have net access
[23:09] <pavs> so can anyone tell me if how I can install notify-osd on jaunty ?
[23:12] <Neonexus> pavs : aint it in the packages?
[23:13] <Neonexus> System > Admin > Packager Manager  search for and install notify-osd
[23:14] <pavs> it wasn there last time I tried it let me try again
[23:16] <BUGabundo> pavs: $ apt-cache policy ubuntu-desktop libindicate0
[23:17] <Neonexus> BUG I cant get networkmanager working
[23:18] <pavs>  Unable to locate package libindicate0
[23:18] <pavs> Unable to locate package libindicate0
[23:18] <pavs> oops
[23:18] <pavs> sorry for the double
[23:20] <BUGabundo> libindicate0:  Installed: 0.1.1-0ubuntu2
[23:20] <BUGabundo> pavs: are you on jaunty?
[23:20] <BUGabundo> and fully updated?
[23:20] <pavs> yes
[23:20] <BUGabundo> do you have ubuntu-desktop installed (if you are on ubuntu/gnome) ?
[23:20] <BUGabundo> Neonexus: not working?
[23:20] <Neonexus> nope
[23:21] <Neonexus> restarted
[23:21] <Neonexus> everything looks fine
[23:21] <pavs> ok hold on.... I am very sorry I am logged in to the wrong VM I am actually on ibex. very sorry about that
[23:21] <BUGabundo> DUH
[23:21] <BUGabundo> eheh
[23:22] <pavs> its looks the same hard to tell :)
[23:22] <Neonexus> cant see why 3g works fine, yet wired ethernet and wifi dont
[23:22] <BUGabundo> its not friday, but its always fun : http://www.funtasticus.com/20090220/friday-wild-girls-february-20-2009/
[23:23] <BUGabundo> pavs: change the background or cli color?
[23:23] <BUGabundo> lol
[23:23] <BUGabundo> 3G works but no wire/wifi?
[23:23] <BUGabundo> really strange
[23:24] <pavs> they are all on VM for testing purpose. my original workstation looks different from default ubuntu
[23:25] <Neonexus> and it was working fine, until an update few days ago
[23:26] <siegie> Is there anyone using kubuntu jaunty? In dolphin the icons are flickering verry fast, when using a specific window size
[23:31] <BUGabundo>      2   0.00s   1.92s 360.1M 16504K      0     0    0    0  96% metacity
[23:31] <BUGabundo> metacity just went crazy
[23:40] <hggdh> anybody having problems on boot (loooong delay, udev-related, probably)?
[23:42] <BUGabundo> hggdh: not here
[23:42] <BUGabundo> / ext3 /home xfs
[23:42] <BUGabundo> 64 bits
[23:42] <hggdh> same
[23:43] <BUGabundo> exacly the same?
[23:43] <BUGabundo> LOL
[23:43] <hggdh> when I boot I have to magic-key into and (it seems) kill udevadm
[23:45] <hggdh> no, not exactly the same, but similar: ext3 all partitions, AMD64x2
[23:45] <BUGabundo> ahh
[23:45] <BUGabundo> Intel C2D
[23:45] <hggdh> well, starting to be not so similar ;-)
[23:46] <hggdh> brb


[09:25] <oSoMoN> sil2100, hey, would you mind publishing silo 80 on my behalf? it has (approved) packaging changes, so I won’t be allowed to do it myself
[09:33] <sil2100> oSoMoN: let me take a look
[09:36] <sil2100> oSoMoN: ok, looks good, wanted to ask you (or actually Kaleo) to mention packaging changes in the changelog but! Actually you guys did that, but the train just truncated the commitmessage
[09:36] <sil2100> oSoMoN: so all good
[09:36] <sil2100> :)
[09:36] <sil2100> (we just need to poke robru about this)
[09:45] <oSoMoN> sil2100, thanks!
[09:47] <sil2100> yw!
[13:49] <rvr> lpotter: ping
[14:59] <rvr> lpotter: jhodapp: Silo 55 approved
[14:59] <jhodapp> rvr, nice thanks!
[15:01] <jhodapp> sil2100, would you mind publishing: https://requests.ci-train.ubuntu.com/#/ticket/1533
[15:05] <sil2100> jhodapp: on it!
[15:06] <jhodapp> thanks sil2100
[15:31] <robru> morphis: Hiya.
[15:32] <morphis> robru: hey
[15:32] <robru> morphis: I see you have a trio ticket with an MP targetted at a branch with 15.04 in the name
[15:32] <robru> morphis: that sounds wrong
[15:33] <morphis> robru: it failed to build otherwise
[15:33] <morphis> look at the changelog in that branch
[15:33] <morphis> looks like it was released for yakkety last time too
[15:33] <robru> morphis: right. I also saw you fail to build it for just vivid
[15:33] <morphis> robru: I tried to build is just for vivid as that is what the branch is for
[15:34] <morphis> but actually citrain wasn't happy with that
[15:34] <robru> morphis: what you need to do is make sure your vivid target branch has a vivid version number
[15:34] <morphis> because of the changelog
[15:34] <morphis> robru: ah
[15:35] <robru> morphis: then you can build just vivid. It deliberately prevents you from doing a vivid landing on the normal trunk because going backwards with version numbers isn't allowed
[15:35] <morphis> right
[15:35] <morphis> robru: let me change that
[15:36] <robru> morphis: but in this case your vivid target branch is misconfigured
[15:36] <morphis> in which way?
[15:40] <robru> morphis: I just mean the wrong version is in the changelog so it isn't really a vivid branch at all
[15:40] <morphis> ah ok
[15:41] <morphis> robru: I think this branch was created from a previously used triple-landing branch and then never correctly setup
[15:41] <robru> You just need to change the version on the first line of the changelog to be a vivid one
[15:43] <robru> dbarth: same to you. If you want to do a vivid only click landing you need to fork trunk and fix the changelog to have a vivid version. You can't do a vivid landing targetted at trunk because that will break the trunk changelog
[15:45] <robru> morphis: dbarth: and when I say fix the changelog I mean you need to commit the fix directly to the target branch, it won't work to include the fix in your MP,  I don't think
[15:45] <morphis> robru: aye
[15:46] <robru> Well it might work in the MP now that I think about it. But it'll definitely work if you fix the target first so that's safer
[16:17] <dbarth> robru: ack (just reading the logs)
[16:18] <dbarth> alex-abreu: ^^ fyi just in case
[16:23] <dbarth> robru: btw, we're preparing that SRU silo with mardy: https://requests.ci-train.ubuntu.com/#/ticket/1669
[16:24] <dbarth> ie, targetting 16.04 specific branches; hope we're doing that the right way
[16:26] <robru> dbarth: well if it's wrong you'll see the same error about failing to add the changelog message
[16:26] <robru> So just keep an eye for that
[16:26] <dbarth> ok
[16:26] <dbarth> robru: well, after spinning around for a bit, i'm trying to do a bileto hook for that click silo; which changes build deps in the control file
[16:27] <dbarth> robru: if i do that in a 3-release silo, i assume i can count on the changelog to be updated in one go and be proper, right?
[16:30] <robru> dbarth: yes, a trio silo targetting trunk will always work
[16:30] <robru> dbarth: the thing is you can't target trunk with vivid because vivid version numbers are lower than yakkety, which is what's in trunk. so you just need a separate lp:click/vivid with a modified changelog for it to work
[16:30] <robru> dbarth: but anyways yeah, the hook idea in a trio silo would be better anyway
[16:31] <dbarth> ok
[17:31] <dobey> robru: i think we have a problem when things want to be SRUs
[17:32] <robru> dobey: the PPA dependency you mean?
[17:32] <dobey> robru: yeah
[17:32] <dobey> things still get built against the overlay
[17:33] <robru> dobey: yes https://bugs.launchpad.net/bugs/1600188
[17:35] <dobey> hmm, and i don't see a good way to solve this, without ephemeral PPAs
[17:36] <dobey> because, even Y has the PPA still
[17:36] <robru> dobey: yeah but stable overlay shouldn' have any yakkety packages so it doesn't hurt anything
[17:36] <robru> dobey: is there a specific ticket you want the PPA dependency changed on?
[17:39] <dobey> robru: just saw the backlog and dbarth talking about an SRU silo; and realized that Wellark had one as well for an indicator-power change (but he already ran publish on it, so i'm not sure if it's broken or not)
[17:39] <robru> hm
[17:40] <robru> well if there's an issue I'm sure they'll find it during SRU verification
[19:43] <fginther> dobey, did you get your jenkins-launchpad-plugin question resolved?
[19:44] <dobey> fginther: not yet. put that issue in the background for now
[19:44] <fginther> ok


[00:53] <micahg> I have a crazy memory leak in unity-2d panel, how can I help debug
[02:19] <Viper550> Hello
[04:09] <DBO> Trevinho, present?
[04:24] <Trevinho> DBO: here I am
[04:24] <Trevinho> also if it's 6am here..
[04:24] <Trevinho> :P
[04:24] <DBO> Trevinho, I have reviewed your branches
[04:24] <Trevinho> I saw your reviews
[04:25] <Trevinho> I fix the menu hacks getter thing
[04:25] <Trevinho> then I'll merge it with the other branch to check the issues
[04:26] <Trevinho> I should have had done just one branch, but I didn't since I hoped you would have merged at least the first one, before :P
[04:27] <Amaranth> DBO: I forget, was there a reason the panel shadow couldn't use nux for drawing?
[04:28] <Trevinho> anyway thank you DBO... I'll let you know when I'm done
[04:32] <DBO> Amaranth, stacking
[04:32] <Amaranth> ah
[04:55] <Trevinho> DBO: lp:~3v1n0/unity/menus-switching-hacks should be fine now
[05:35] <didrocks> good morning
[06:53] <Trevinho> DBO, I should have fixed lp:~3v1n0/unity/panelmenu-fixes Now you should be able to merge it in  lp:~3v1n0/unity/menus-switching-hacks
[07:05] <oSoMoN> good morning
[07:40] <andyrock> didrocks, if ti requires an FFe should i remove the assigment from myself?
[07:40] <didrocks> andyrock: no, you sould maybe ask for it, but TBH, I really doubt it will be acked for O
[07:43] <andyrock> didrocks, but the current behavior, TBH, really sucks :)
[07:43] <didrocks> andyrock: I really like it though
[07:44] <didrocks> andyrock: if you just want to focus an app or open it, you click on it
[07:44] <didrocks> then, the launcher will hide
[07:44] <didrocks> if you want to open more than one, especially when the session starts, you click on one
[07:44] <didrocks> then move the mouse
[07:44] <didrocks> and the launcher stays
[07:44] <didrocks> andyrock: took more than 10 hours to get the right behavior, quite tricky
[07:45] <andyrock> indeed... but when sometimes happens that i want to focus the app A but i focus the app B for error
[07:45] <andyrock> and i should move again the mouse to the right than to the left
[07:46] <didrocks> andyrock: well, 1s timeout is not enough for you? :)
[07:46] <andyrock> didrocks, i've not a 1s timeout :)
[07:47] <didrocks> andyrock: hum, you mean, it immediatly hides?
[07:47] <andyrock> didrocks, yes...
[07:48] <didrocks> andyrock: because you put your mouse outside of the launcher, isn't it?
[07:48] <andyrock> didrocks, let me try (i should revert my branch)
[07:48] <andyrock> give me a moment
[07:48] <didrocks> andyrock: it should only hide immediatly if you click on something and put the mouse outside of the launcher
[07:49] <didrocks> andyrock: the behavior (apart from the bug I mentionned), is the same than in natty
[07:49] <andyrock> didrocks, the super bug is a low one...
[07:49] <andyrock> i mean is not so critical
[07:49] <andyrock> but should be tricky to solve
[07:50] <didrocks> it's annoying
[07:50] <didrocks> especially if you are using touch device
[07:51] <andyrock> didrocks, i've not touch device :/
[07:52] <didrocks> andyrock: basically, the mouse will still be "under" the launcher area
[07:53] <andyrock> i got it
[07:54] <andyrock> didrocks, the timeout works well sorry :)
[07:56] <didrocks> ahah! :-)
[07:56] <didrocks> andyrock: see, your branch broke that! :p
[07:56] <didrocks> that's why the hide machine can be quite tricky :-)
[07:57] <andyrock> didrocks, i've just delete my branch
[07:57] <andyrock> well with my branch the launcher never hides when the mouse is over the launcher
[07:57] <didrocks> andyrock: if you want to have a look at the super issue, you're more than welcome :)
[07:57] <andyrock> maybe the bug title is not so correct
[07:58] <andyrock> Launcher - Launcher should never autohide when the cursor is positioned over the Launcher
[07:58] <andyrock> https://bugs.launchpad.net/unity/+bug/745707
[07:58] <andyrock> in the bug description is cleaner bug the title doesn't refert to the spread
[07:59] <andyrock> and i've read just the bug title :)
[13:45] <andyrock> smstacking, compiz action works as aspected only for super / alt / ctrl
[13:46] <andyrock> for other key it's like a loop
[13:47] <smstacking> ah right
[13:48] <smstacking> hrm, I seem to recall that it didn't work for keys that didn't have a modifier because of the way that we release grabs now
[13:48] <smstacking> racarr fixed that in trunk recently
[13:48] <smstacking> dunno if I've backported the fix to oneiric yet
[13:52] <andyrock> smstacking, so it is/was a compiz bug... thx for the info
[13:56] <smstacking> andyrock: maybe
[13:58] <andyrock> smstacking, i think the patch is not in oneiric yet
[13:59] <andyrock> using apt-get source compiz
[13:59] <andyrock> in event.cpp i still have
[13:59] <andyrock> 	switch (event->type)
[13:59] <andyrock> 	{
[13:59] <andyrock> 	    case KeyPress:
[13:59] <andyrock> 		XUngrabKeyboard (priv->dpy, event->xkey.time);
[13:59] <andyrock> 		break;
[13:59] <andyrock> 	    default:
[13:59] <andyrock> 		break;
[13:59] <andyrock> 	}
[14:00] <andyrock> assuming that this is the patch: http://git.compiz.org/compiz/core/commit/?id=6b8ecb998ce409462cfd72343696f4925aa33fdb
[14:40] <greyback> mardy: hey, is the legacytray disabled for you?
[14:41] <greyback> Saviq: ^^
[14:42] <Saviq> greyback: yes
[14:42] <greyback> Saviq: hmm, ok thanks. I guess it's intentional then
[14:42] <Saviq> not sure it is
[14:42] <Saviq> https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/779382
[14:47] <greyback> Saviq: I've just enabled it and it doesn't appear to be working. Get X Error: BadWindow.
[14:48] <Saviq> greyback: how do you enable it?
[14:49] <greyback> dconf, in com.canonical.unity-2d.panel
[14:50] <greyback> oh wait, no I'm completely wrong.
[14:50] <greyback> The ! is not to disable, but to force on left-most screen only
[14:51] <greyback> It must be enabled so. Last commit adds white-listing of apps, so better see what they are to test
[15:29] <andyrock> didrocks, I'm on "super bug"
[15:30] <andyrock> well, as you said the problem is that RecvMouseEnter is called...
[15:31] <andyrock> we can make RecvMouseEnter useless checking that if TRIGGER_BUTTON_SHOW is true
[15:31] <andyrock> s\that\
[15:32] <andyrock> the problem is that not only recvmouseenter is called but also recvmouseenter
[15:32] <andyrock> sorry recvmousemove
[15:33] <andyrock> and i really don't want to use another variable to check inside recvmousemove if it's a fake one :)
[15:37] <didrocks> DBO: ^
[15:38] <didrocks> andyrock: yeah, we fixed that in nux for natty, but seems it regressed
[15:38] <didrocks> basically, the idea was to not got any mousemove if the launcher is moving, but not the mouse
[15:38] <DBO> im confused
[15:38] <didrocks> DBO: put the mouse under the launcher area, launcher hidden
[15:38] <didrocks> press super to show the launcher
[15:38] <didrocks> release
[15:39] <DBO> yeah
[15:39] <didrocks> then, the launcher stays
[15:39] <DBO> it doesn't re-hide
[15:39] <didrocks> indeed, that's because we receive a mousemove when the launcher is showing (moving)
[15:39] <didrocks> as in natty before the fix
[15:39] <didrocks> so MOUSE_POST_REVEAL (or whatever is called) it set to 1
[15:39] <didrocks> it's*
[15:39] <didrocks> and is* ;)
[15:40] <DBO> okay looking it it
[15:40] <didrocks> thanks DBO :)
[15:40] <DBO> andyrock, sorry about your other branch dude, you saw my comment on why we cant merge it right?
[15:40] <andyrock> DBO, yeah
[15:40] <andyrock> np
[15:40] <andyrock> :)
[15:40] <andyrock> i've already deleted it
[15:49] <andyrock> didrocks, just another quick question
[15:49] <andyrock> it's too late for this bug? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/713423
[15:52] <didrocks> andyrock: need a FFe as well
[15:53] <didrocks> andyrock: TBH, I think bug #814610 (which needs a FFe as well) will be more useful
[15:56] <andyrock> didrocks, a quicklist item should be added only to usb icon?
[15:56] <andyrock> *icons
[15:58] <didrocks> andyrock: seems the easiest to me, wdyt?
[15:58] <didrocks> andyrock: but if you don't feel it, I think I'll give it a shot next week, just something I don't want we forget for finale :)
[15:59] <andyrock> the device icon stuff should be redesigned for P
[15:59] <andyrock> i've my private branch
[16:00] <andyrock> (according to design decisions)
[16:00] <andyrock> so i can try to fix that bug
[16:00] <andyrock> becuase i've already played with device icons :)
[16:06] <didrocks> andyrock: yeah, that was my thought, hence the fact I propose that to you :è)
[16:31] <czajkowski> aloha
[17:16] <jono> gord, around?
[17:16] <jono> or maybe MacSlow
[17:16] <jono> are you guys familiar with that the sizes don't show in the buttons in the file lens filter?
[17:16] <MacSlow> jono, what's up?
[17:17] <MacSlow> jono, I know about it... is in the works to being fixed.
[17:17] <jono> cool, thanks MacSlow :-)
[17:17] <MacSlow> jono, you mean the ellipsisze showing instead of the sizes?!
[17:18] <jono> MacSlow, yup
[17:18] <MacSlow> jono, btw... do you know if that's has a bug filed on it... I'm a bit lost in the pile atm :)
[17:20] <jono> MacSlow, I haven't seen one
[17:20] <MacSlow> ok
[17:24] <htorque> jono: hi! have you maybe seen a bug report about the "Science & Engin..." button in the filter? :)
[17:24] <MacSlow> htorque, that should be fixed
[17:25] <MacSlow> in unity trunk (and release) already... since two weeks or so
[17:25] <htorque> MacSlow: should it be in trunk?
[17:25] <htorque> oh
[17:25] <MacSlow> htorque, yeah I fixed and merged that for sure
[17:25] <MacSlow> htorque, do you still get that?
[17:25] <htorque> MacSlow: yes, i'm on trunk from a few hours ago.
[17:25] <MacSlow> wtf?!
[17:25] <htorque> let me check the beta 2 cd
[17:26] <jono> what is the bug?
[17:26]  * MacSlow restarts unity with english locale
[17:26] <htorque> jono: super + a → filters. you should see  "Science & Engin..." even if there's enough room to show the whole thing.
[17:27] <jono> htorque, I see that
[17:27] <jono> Science & Engin...
[17:28] <htorque> MacSlow: ok, then that seems to still be there :-(
[17:29] <MacSlow> htorque, well my fix is in there... but we can't do magic there since the string is so long and the filter-buttons are not meant to be bigger
[17:29] <MacSlow> htorque, I shrinked the left and right margin in the buttons... it used to be worse
[17:32] <htorque> MacSlow: shouldn't the german terms be even longer? you don't see it with german locals, right? it's no catastrophe, it's just not very nice to look at, if you have enough room to the left. :)
[17:33] <MacSlow> htorque, asthetics-wise there should be some padding in the filter-buttons...
[17:34] <htorque> MacSlow: no, i meant left of the filter area (i'm opening it fullscreen on my 1600x900 screen).
[17:35] <MacSlow> htorque, hm... there goes the man that could have answered this thing :)
[17:35] <htorque> hehe
[17:36] <htorque> would have been boring if you had no tasks left for P, wouldn't it ;-)
[17:37] <ach1m> MacSlow, you asked if there is a bug filed, there you go → https://bugs.launchpad.net/unity/+bug/851359
[17:37] <MacSlow> htorque, I can easily occupy myself for two cycles with no new feature work... I'm not kidding
[17:38] <htorque> MacSlow: that doesn't sound too good. try not to burn out! :)
[17:41] <MacSlow> htorque, too late... that already happend once
[17:41] <MacSlow> ach1m, thanks... commented on the bug
[17:42] <htorque> MacSlow: :-( at least you now know the signs...
[17:42] <MacSlow> htorque, yeah... thanks to a talk jono once did at Guadec ... about two years ago... that was a shocking eye-opener I can tell
[17:43] <jono> :-)(
[17:43] <jono> :-)
[17:45] <MacSlow> this is my way to fight it atm: http://macslow.net/images/wheelie-12.jpg :)
[18:41] <mterry> smstacking, :)  heyo -- remember how I was testing the PPA version of compiz for its stacking fixes?  The recent oneiric version doesn't fix as many issues as i remember the PPA version fixing.  Are there more in the pipeline?  Is it a known issue?
[19:05] <htorque> mterry: anything reproducible (then let's open a bug report)? i've only seen xchat causing trouble since the update from the ppa to oneiric.
[19:05] <mterry> htorque, not reproducible yet
[19:09] <htorque> mterry: yeah, that's the big problem with those bugs - i'm not sure how useful bug reports without a test case are. :-/
[21:58] <AlanBell> anyone looking at bug 851694