[03:53] <smspillaz>  /join #bzr
[03:56] <RAOF> :)
[03:57] <RAOF> GggrrGIT!
[03:59] <lifeless> RAOF: ohhai, are you a good person to talk to about unity theme bugs ?
[03:59] <lifeless> RAOF: specifically bug 920746
[03:59] <ubot2`> Launchpad bug 920746 in unity "themes wonky - looks bad" [Undecided,Confirmed] https://launchpad.net/bugs/920746
[04:00] <RAOF> lifeless: No, not really.  Urgh, sympathies.  That looks really annoying.
[04:01] <RAOF> Something would appear to have gone weird in your gnome-settings-daemon, though.
[04:03] <RAOF> lifeless: Could you install dconf-tools and check out the org/gnome/settings-daemon/plugins tree?  Particularly xsettings?
[04:04] <RAOF> (Oh, with dconf-editor)
[04:05] <lifeless> RAOF: what things from there do you want to know ?
[04:05] <RAOF> lifeless: If I disable the xsettings plugin I get something that looks a lot like what you've got.  Is the xsettings plugin enabled?
[04:06] <lifeless> inactive, grayscale, nothing disabled, nothing enabled, medium hinting,  priority 2, rgb
[04:06] <RAOF> Tick the button to activate it.
[04:06] <lifeless> theme works
[04:07] <lifeless> but I cannot move windows
[04:07] <RAOF> Right.
[04:07] <RAOF> Wait for compiz to finish its screaming hissy fit.
[04:07] <lifeless> wow thats a long hissy fit
[04:08] <RAOF> It's finished restarting after its crash?
[04:08] <lifeless> I presume so
[04:08] <lifeless> I can alt-tab now
[04:09] <lifeless> sloppy-focus isn't anymore, but at least it looks nice ;)
[04:09] <RAOF> :)
[04:09] <lifeless> what other plugins should be on by default?
[04:10] <RAOF> Everything.
[04:10] <lifeless> hah
[04:10] <lifeless> very very very much not the case
[04:10] <RAOF> Are there any which are disabled?
[04:11] <RAOF> Oh.  gconf is the only one of mine which is disabled.
[04:11] <RAOF> And that's just a migrate-from-gconf thing, so it probably turns itself off.
[04:11] <lifeless> background, clipboard, font, gconf, housekeeping, keybindings, keyboard, media-keys, mouse, print-notifications, smartcard, sound, wacom, xrandr
[04:12] <lifeless> (and xsettings, but its on now)
[04:12] <RAOF> Ah.
[04:12] <RAOF> So, your system is not so much of the working then.
[04:12] <lifeless> should I turn them all (but gconf) on ?
[04:12] <RAOF> Yes.
[04:12] <lifeless> RAOF: well, I *live* in uxterm + firefox + tomboy, so I've been piqued but not destroyed
[04:13] <lifeless> the collapsing of titles in to the top left was really getting on my tits though :)
[04:14] <lifeless> can't move my mouse now
[04:14] <lifeless> can still click
[04:14] <lifeless> and evince segfaulted :)
[04:16] <RAOF> :D
[04:16] <RAOF> The GNOME stack really loves settings changes.
[04:16] <lifeless> seriously, can I get my mouse back ?
[04:16] <RAOF> It should come back by itself?
[04:16] <lifeless> cursor is there, won't move
[04:17] <lifeless> hmm, plugged in usb mouse, which works...
[04:17] <lifeless> driver has shat itself?
[04:17] <lifeless> anoting in dmesg to suggest that
[04:18] <RAOF> Probably one of the plugins you enabled caused g-s-d to suddenly discover your touchpad and think it should be disabled.
[04:19] <lifeless> peripherals touchpad thingy shows enabled
[04:19] <RAOF> “xinput list” followed by “xinput list-props $TOUCHPAD_DEVICEID” could indicate that the enabled property has been toggled.
[04:20] <lifeless> TPPS/2 IBM TrackPoint                     id=12   [slave  pointer  (2)]
[04:20] <lifeless> -> id is 12 ?
[04:20] <RAOF> Yup.
[04:20] <lifeless> erm no
[04:20] <lifeless> perhaps SynPS/2 Synaptics TouchPad                id=10   [slave  pointer  (2)]
[04:20] <RAOF> Hm.  It shouldn't have turned off the nubbin.
[04:20] <lifeless> which ?
[04:20] <RAOF> Which one(s) isn't(aren't) working?  Or both!
[04:20] <lifeless> pad only
[04:21] <RAOF> Then 10
[04:21] <lifeless> I forgot I had a nipple
[04:21] <lifeless> so, list-props, and look for ?
[04:21] <RAOF> Synaptics Off (276)
[04:21] <lifeless>         Device Enabled (132):   1
[04:21] <RAOF> Well, there are two things; one is Device Enabled, and one is Synaptics Off.
[04:21] <lifeless>         Synaptics Off (274):    1
[04:22] <lifeless> RAOF: how do I tell it to be alive?
[04:23] <RAOF> xinput set-int-prop 10 274 8 0
[04:23] <lifeless> ahha
[04:23] <lifeless> thanks
[04:23] <RAOF> (For those playing at home, that's $DEVICE_ID, $PROPERTY, 8-just-because, $VALUE
[04:26] <lifeless> thanks a lot
[04:26] <lifeless> is sloppy focus still available for those that want it ?
[04:26] <lifeless> (and if so, how does one get it ?)
[04:26] <RAOF> I think so; you'd need to venture in to the ccsm swamp to manage that.
[04:30] <lifeless> doth not seem like it
[04:33] <RAOF> Huh.  I don't even have ccsm installed on this system.
[04:33] <lifeless> ahh,
[04:33] <lifeless> this still works:
[04:33] <lifeless> http://askubuntu.com/questions/64605/how-do-i-set-focus-follows-mouse
[04:35] <lifeless> right, thats enough spelunking
[04:36] <lifeless> optimalish systme, back to work ;)
[05:53] <RAOF> Oh, ah.  Yeah, uploading a 170MB attachment to launchpad aint happening.
[05:54] <RAOF> lifeless: Might I point you towards https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/930252
[05:54] <ubot2`> RAOF: Error: <Bugtracker.plugin.Launchpad instance at 0xa5ae8cc> bug 930252 not found
[05:55] <RAOF> lifeless: It's me and Sidnei wondering why squid's trying to allocate 10PB of memory for the swap.
[06:52] <didrocks> good morning
[06:53] <RAOF> didrocks: Heya!
[06:54] <didrocks> hey RAOF, how are you?
[06:56] <RAOF> I'm *awesome*
[06:57] <RAOF> Much like weasels.  They're also awesome.
[06:57] <RAOF> Like little orange ferrets!  How adorable!
[07:02] <didrocks> heh :)
[07:02] <RAOF> Hows about yourself?
[07:02] <pitti> Good morning
[07:05] <pitti> erk, the HUD gets in the way everytime I change virtual desktops
[07:06] <didrocks> pitti: yeah, there was work to avoid that in compiz, but it's part of the patch I had to revert on Friday morning
[07:07] <didrocks> pitti: it needs a patch in compiz (the new one is in a better shape) and a patch in unity
[07:07] <pitti> didrocks: ah, thanks
[07:07] <RAOF> Thank you for doing that, by the way.  My keyboard shortcuts work :)
[07:10] <didrocks> RAOF: my pleasure to make your day better! :)
[07:15] <lifeless> RAOF: -> upstream :)
[07:15] <RAOF> lifeless: Urgh.  I need to duplicate that on a bugzilla? :(
[07:16] <lifeless> RAOF: that or convince squid to move to LP for bugs;)
[07:17] <RAOF> lifeless: Or convince *you* to duplicate that on a bugzilla /-?
[07:20] <lifeless> join #squid-dewv
[07:20] <lifeless> join #squid-dev please
[07:20] <RAOF> On freenode?
[07:20] <lifeless> bah, no 0
[07:20] <lifeless> no -
[07:21] <lifeless> squiddev
[07:36] <RAOF> lifeless: You maintain squid in Debian/Ubuntu, right?  You saw that?
[07:37] <lifeless> RAOF: I don't
[07:37] <lifeless> RAOF: I try hard not to mix up upstream + packaging
[07:38] <RAOF> Ok.
[07:38] <lifeless> one or t'other, avoids circular reasoning
[07:38] <lifeless> (I fail on some stuff, buf if you ever need another hting to maintain, just shout)
[07:39] <RAOF> Heh.
[07:39] <RAOF> Ok.  Debian's got 3.1.19.  Time for a merge.
[08:06] <RAOF> We're not at a stage where merging a new upstream squid3 (3.1.19-1) requires a FFe much more than “fixes bug #930252 which prevents squid working at all”, right? :)
[08:06] <ubot2`> Launchpad bug 930252 in squid3 "squid3 crashed with SIGABRT in fatal_dump()" [Critical,Triaged] https://launchpad.net/bugs/930252
[08:09] <GunnarHj> pitti: Hi Martin! Did you see my explanation at https://code.launchpad.net/~gunnarhj/ubuntu/precise/accountsservice/locale-test/+merge/93404 ?
[08:11] <pitti> hello GunnarHj
[08:11] <pitti> yes
[08:11] <pitti> GunnarHj: I was on holiday yesterday, catching up with my huge inbox now
[08:12] <GunnarHj> pitti: Ok. :)
[08:30] <chrisccoulson> good morning everyone
[08:32] <pitti> hey chrisccoulson
[08:32] <chrisccoulson> hi pitti, how are you?
[08:32] <pitti> chrisccoulson: quite fine, thanks! we spent three nice days in Berlin
[08:40] <didrocks> no snow anymore? :)
[08:40] <pitti> it's almost entirely gone
[08:41] <didrocks> pitti: oh, btw, reminder about reminding for the week report minder :p
[08:41]  * pitti hugs didrocks
[08:41]  * didrocks hugs pitti back
[08:43] <chrisccoulson> the snow here was a bit of an anti-climax. we only had a little bit :(
[08:46] <didrocks> ah pitti launched the retracer :)
[08:46] <pitti> it keeps breaking on duplicate signature confusion
[08:46] <didrocks> chrisccoulson: you are more in rain, isn't it? :)
[08:46] <didrocks> ah :/
[08:46] <pitti> one of these days I need to fix this properly
[08:46] <didrocks> it's launchpad timing out?
[08:47] <chrisccoulson> didrocks, apparently not: http://www.bbc.co.uk/news/uk-england-17102615 ;)
[08:48] <didrocks> chrisccoulson: who do you think will believe this? It's obviously a fake :)
[08:48] <chrisccoulson> heh
[09:09] <rye> If firefox/icedtea in precise is hanging on my banking site (and breaking firefox after this) - where do I start with debugging - the vm does not crash, it simply does not work
[09:12] <micahg> rye: is the banking site java?
[09:12] <micahg> ah, icedtea, yeah, there's a known crasher ATM, but IIRC, there's an icedtea plugin log
[09:13] <micahg> I have to go through the open bugs later today, there are quite a few about java plugins ATM
[09:13] <rye> micahg, what i am worried - it renders firefox unusable until restart
[09:13] <rye> which is kind of strange given that plugin runs in separate process
[09:14] <micahg> there used to be a java error console, I don't know if that still exists
[09:14] <micahg> is there anything in the firefox error console?
[09:15] <rye> The program 'java' received an X Window System error.
[09:15] <rye> oh shiny
[09:16] <rye> and then firefox fails to redraw the UI, it fits
[09:30] <seb128> hey
[09:31] <seb128> sorry, I'm a bit later than usual today
[09:31] <seb128> (had a bank appointment and time to come back)
[09:36] <Daviey> Is anyone else finding X really unstable this week?
[09:36] <Daviey> multi-touch mouse also not responding as you expect?
[09:39] <seb128> Daviey, try #ubuntu-x, didn't notice any issue but I use a normal 3 buttons usb mouse
[09:39] <seb128> no xorg issue
[09:39] <seb128> is pitti back?
[09:39] <seb128> pitti, it's meeting reminder day!
[09:40] <Daviey> seb128: thanks
[09:41] <pitti> hey seb128
[09:41] <pitti> seb128: thanks! will do ASAP, just finishing up something
[09:41] <seb128> oh, a pitti ;-)
[09:41] <seb128> pitti, hello, wie gets? had a good w.e?
[09:41] <pitti> seb128: yes, indeed! we spent three nice days in Berlin
[09:46] <seb128> pitti, great ;-)
[10:02] <chrisccoulson> hey seb128
[10:03] <seb128> hey chrisccoulson, how are you?
[10:03] <chrisccoulson> seb128, yeah, not too bad thanks. although, i would have been better had i not trodden on the pins of an electrical plug first thing this morning :(
[10:04] <seb128> ouch :(
[10:04] <chrisccoulson> yeah, i split the bottom of one of my toes
[10:04] <seb128> see at least european plugs are round :p
[10:04] <chrisccoulson> but, the plug ended up worse off ;)
[10:15] <pitti> didrocks: meh @ unity-lens-video
[10:15] <pitti> python again
[10:16] <davidcalle> pitti, my bad
[10:16] <pitti> we just dropped system-config-printer applet, and now it's again back..
[10:16] <didrocks> pitti: yeah, I know…
[10:16] <pitti> didrocks: (not your fault, sorry, I'm just venting)
[10:16] <pitti> didrocks: are we requrired to install this by default?
[10:17] <seb128> pitti, what's the issue with python?
[10:17] <pitti> (also, it's currently crashing like mad, but that'll get fixed)
[10:17] <seb128> pitti, shouldn't be an issue once bug #929506 is fixed
[10:17] <ubot2`> Launchpad bug 929506 in unity "lenses are loaded on start, should be lazy loaded" [High,In progress] https://launchpad.net/bugs/929506
[10:17] <didrocks> pitti: seems so that it's the default that the u1 team requires
[10:17] <seb128> pitti, lens shouldn't load on login but lazy load on dash use
[10:17] <pitti> seb128: yes, but currently they don't it seems
[10:17] <didrocks> davidcalle: btw, on the music lens + rhythmbox, where are we at?
[10:17] <seb128> pitti, that got broken in precise and it's on the high bug list
[10:17] <seb128> pitti, cf the bug I just pointed
[10:17] <didrocks> pitti: they don't, but it's hihgh in the priority list
[10:18] <didrocks> high*
[10:18] <pitti> ah, thanks
[10:18] <davidcalle> didrocks, wip, the db parsing is done, mhr3 might take over the remaining bits.
[10:19] <pitti> davidcalle, didrocks: OOI, are the music/video lenses for buying only? they don't seem to find any of my local music/videos
[10:19] <seb128> pitti, btw cr3 was asking yesterday that we switch from checkbox-gtk to checkbox-qt
[10:19] <pitti> seb128: right, I commented on bug 937189
[10:19] <ubot2`> Launchpad bug 937189 in checkbox "checkbox-gtk should be replaced with checkbox-qt on the desktop image" [Undecided,Incomplete] https://launchpad.net/bugs/937189
[10:19] <seb128> pitti, it indexes XDG_VIDEO_DIR, are your video in ~Video?
[10:19] <seb128> or whatever is the dir in german
[10:19] <didrocks> pitti: they look at your video dir
[10:19] <pitti> seb128: no, in ~/download/
[10:20] <pitti> but my music is in teh standard dir
[10:20] <seb128> pitti, so that's why
[10:20] <seb128> pitti, well it's a "video" lens ;-)
[10:20] <seb128> not a music one
[10:20] <didrocks> pitti: for the music one, nothing is shown right now as we dropped banshee
[10:20] <pitti> didrocks: ah, the music one only supports banshee?
[10:20] <didrocks> and the rhythmbox scope isn't ready
[10:20] <pitti> ok, that explains both, thanks
[10:20] <davidcalle> pitti, the music lens should pickup your currently Banshe/soon Rbox library.
[10:20] <didrocks> well, I made it clear during the UDS session :)
[10:21] <didrocks> davidcalle: you will need to require a FFe
[10:21] <pitti> well, it's currently a bug that it doesn't show any results
[10:21] <seb128> I doubt that ffe will be refused :p
[10:21] <pitti> so, filing an FFE is good for tracking, but there's no reason to deny it
[10:21] <didrocks> agreed, just that will need to do the paperwork :)
[10:21] <davidcalle> didrocks, pitti, ok
[10:22] <pitti> so don't worry too much about this
[10:22] <didrocks> davidcalle: this rb scope is in the unity-lens, not a separate source?
[10:22] <davidcalle> didrocks, in the music lens, even if I would prefer an external scope.
[10:23] <davidcalle> didrocks, for people upgrading from Oneiric, and using Banshee.
[10:23] <didrocks> davidcalle: well, otherwise, we would have the music lens supporting by default banshee + u1, and another source
[10:23] <didrocks> davidcalle: you keep the banshee support?
[10:23] <didrocks> isn't it?
[10:24] <davidcalle> didrocks, it should, but I need mhr3 input on doing it cleanly.
[10:24] <didrocks> ok :)
[10:24] <davidcalle> didrocks, I'd prefer to have rb and banshee as external scopes and music players recommending them.
[10:24] <davidcalle> didrocks, but it's not my call.
[10:25] <didrocks> mhr3: ? ^
[10:26]  * mhr3 reads backlog
[10:27] <mhr3> didrocks, yes, we want to keep the banshee scope
[10:27] <didrocks> mhr3: great, thanks :)
[10:35] <Sweetshark> pitti: didrocks is a real man now, he sponsored his first LibreOffice upload.
[10:36] <didrocks> Sweetshark: well, I uploaded and updated some OOo in karmic time :)
[10:37] <pitti> hey Sweetshark
[10:37] <pitti> I saw, thanks!
[10:38] <Sweetshark> didrocks: ah, ok. ;) btw I by now (3.5) LO is saner than it was in the 3.3/3.4 series so hopefully a bit more time to really take care about the details too.
[11:31] <s9iper1> recently update remove the windows  menu any body know where to file the bug
[11:31] <s9iper1> ?
[11:32] <pitti> s9iper1: it's by design now; right-click on window title bar or alt+space
[11:35] <s9iper1> pitti: its not a good change  its confusing if we have an other application running in the background
[11:35] <s9iper1> like i have opened xchat and chrome is running behind it
[11:37] <pitti> what's that to do with the windows menu?
[11:38] <s9iper1> its mixing with each other now  wait i give you a screenshot
[11:38] <pitti> cyphermox: FYI, holding your wpasupplicant lucid-proposed upload until bug 528087 is fixed in precise
[11:38] <ubot2`> Launchpad bug 528087 in wpasupplicant "merge patch for segfault when using smartcards with NetworkManager" [Medium,Triaged] https://launchpad.net/bugs/528087
[11:40] <s9iper1> pitti: see the mixing and now there is a confusion here http://imagebin.org/200004
[11:41] <seb128> pitti, thanks for fixing the retracer, I untagged a bug and deleted the lock yesterday but that was apparently not enough
[11:41] <pitti> s9iper1: that looks like a compiz/unity window drawing bug; but it's got nothing to do with the alt+space window menu?
[11:41] <pitti> seb128: it hit another weird dupe detection case
[11:41] <pitti> seb128: some day I need to track it down properly, but for now I just wrote a bug pattern and restarted manually
[11:42] <seb128> pitti, ok, thanks
[11:42] <s9iper1> pitti: thanks
[11:44] <smspillaz> seb128: do you know where I'd find the packaging for libindicator-appmenu ?
[11:44]  * smspillaz be making daily builds
[11:44] <seb128> smspillaz, there is no such lib?
[11:44] <smspillaz> seb128: err, indicator-appmenu ?
[11:44] <smspillaz> or whatever provides appmenus ?
[11:44] <seb128> smspillaz, lp:~ubuntu-desktop/indicator-appmenu/ubuntu
[11:45] <smspillaz> great, thanks :)
[11:45] <seb128> yw
[11:45] <tkamppeter> pitti, hi
[11:46] <pitti> hello tkamppeter
[11:48] <tkamppeter> pitti, about bug 936629, the process where gs wants to look into /proc/<no>/auxv seems to live only while the print job is living, so I could not find out which process it is. It happens with the pnm2ppa driver, one can simply reproduce it by creating a queue for this driver (printing into a file) and printing a test page on this queue.
[11:48] <ubot2`> Launchpad bug 936629 in cups "Printing fails after printing first document " [Undecided,Incomplete] https://launchpad.net/bugs/936629
[11:50] <pitti> tkamppeter: so that'll need some stracing then to find out
[11:50] <pitti> tkamppeter: perhaps you can put the commands how to create this fake queue into the bug?
[11:51] <tkamppeter> pitti, will this help? Will it not also only tell that "gs" accessed /proc/<no>/auxv?
[11:51]  * pitti ^5s seb128 on http://reports.qa.ubuntu.com/reports/bug-fixing/precise-fixes-report.html - nice work!
[11:51] <pitti> tkamppeter: well, we need to know whether it's gs or something launched by gs
[11:51] <seb128> pitti, oh, I tied you, great ;-) thanks! nice work for you as well!
[11:51] <pitti> tkamppeter: if you are sure that this pid was gs, then we don't need further strace
[11:52]  * pitti grabs the gauntlet -- it's on!
[11:52] <pitti> ... after lunch, bbl
[12:45] <ronoc> chrisccoulson, on thunderbird the send button has disappeared from the email window
[12:45] <ronoc> as a result i can't send emails
[12:45] <ronoc> any ideas
[12:49] <jbicha> seb128: good morning
[12:51] <chrisccoulson> ronoc - can you add it back to the toolbar (right click -> Customize)?
[12:51] <jbicha> https://bugzilla.gnome.org/show_bug.cgi?id=670472 says we need the new vte3 & gtk to fix
[12:51] <ubot2`> Gnome bug 670472 in HighContrast and LowContrast "High Contrast 3.3.90 (rewrite) breaks gnome-terminal, other apps" [Critical,Needinfo]
[12:53] <ronoc> chrisccoulson, I open a draft email and right click where
[12:53] <ronoc> it pops up the edit email window
[12:53] <ronoc> before there was a big send button
[12:53] <chrisccoulson> ronoc, on the toolbar in the compose window
[12:54] <ronoc> chrisccoulson, right click doesn't bring up and options
[12:54] <ronoc> any even
[12:54] <chrisccoulson> ronoc, does the toolbar exist at all?
[12:55] <ronoc> chrisccoulson, yes with font size etc - is that where you mean ?
[12:55] <chrisccoulson> ronoc, no, the one which normally has the send button on it :)
[12:55] <chrisccoulson> or is that one missing?
[12:56] <ronoc> must be missing
[12:56] <ronoc> how do i restore it
[12:56] <chrisccoulson> ronoc, does it come back if you go to View -> Toolbars and make sure that Composition Toolbar is checked?
[12:56] <ronoc> chrisccoulson, ah that was it :)
[12:57] <ronoc> chrisccoulson, thanks
[12:57] <chrisccoulson> :)
[12:57] <ronoc> silly me
[13:10] <seb128> jbicha, hey
[13:10] <seb128> jbicha, gtk is on my update list for today, it's next in fact ;-)
[13:12] <seb128> jbicha, pitti: do you guys work(ed) with the debian remmina maintainer? not sure how to handle bug #931336 and bug #926619
[13:12] <ubot2`> Launchpad bug 931336 in remmina "Remmina package doesn't provide .desktop file" [Undecided,Confirmed] https://launchpad.net/bugs/931336
[13:12] <ubot2`> Launchpad bug 926619 in remmina "no tray icon in untity" [Undecided,Confirmed] https://launchpad.net/bugs/926619
[13:13] <seb128> jbicha, pitti: especiall the second (indicator support), do we want an ubuntu diff for that?
[13:18]  * didrocks taking a break, back in an hour
[13:18] <smspillaz> seb128: do you know if kenvandine will be in today ?
[13:19] <seb128> smspillaz, he should be
[13:19] <seb128> smspillaz, yesterway was an u.s holiday but he should be there today
[13:20] <smspillaz> hmm ok
[13:21] <smspillaz> seb128: it seems like indicator-appmenu's packaging is pretty out of date. and it uses merge-source
[13:21] <seb128> smspillaz, I did the recent update so it shouldn't be outdated and yes it use merge upstream as most dx sources, it allows to backport upstream commits in one command
[13:21] <jbicha> seb128: the missing .desktop is fixed in trunk, not sure about the appindicator but we'd probably have a diff for LPI anyway, right?
[13:21] <smspillaz> hmm
[13:22] <seb128> jbicha, well, we could in theory have a series.ubuntu in the debian package with those
[13:22] <smspillaz> seb128: ok, I guess there are just conflicts when attempting to merge this local menus branch. its probably the case that this one is out of sync with trunk
[13:22] <smspillaz> seb128: would I be safe if I were to just cp in the debian directory and debuild with that ? (assuming no files have been added / removed?)
[13:23] <seb128> smspillaz, https://code.launchpad.net/~ubuntu-desktop/indicator-appmenu/ubuntu is less that a week old and has 0.3.91
[13:23] <seb128> smspillaz, yes, copying the debian dir should be fine
[13:23] <smspillaz> ok :)
[13:31] <pgraner> didrocks, did anything in unity change over the weekend that would affect the launcher revealing on multi-mon setups?
[13:32] <pitti> seb128: I actually tried to enable indicator support, it's in the ubuntu-desktop PPA
[13:32] <pitti> seb128: but it doesn't seem to work
[13:32] <seb128> pitti, hum, ok
[13:33] <seb128> pitti, I will have a look to that, adding to my todo
[13:33] <jbicha> pitti: it didn't seem to work here either
[13:33] <pitti> seb128: hm, I just changed -DWITH_APPINDICATOR=ON
[13:33] <pitti> I didn't try the patch
[13:33] <pitti> but that patch doesn't seem to actually fix indicator support
[13:33] <seb128> pitti, did you add the build-depends as well?
[13:34] <pitti> yes
[13:34] <seb128> pitti, jbicha: ok, I will have a look
[13:34] <pitti> and it builds fine, and links to indicator etc.
[13:34] <pitti> but I still never saw it
[13:34] <pitti> I enabled the options in the "applet" tab
[13:34] <pitti> and tried ssh and VNC
[13:34] <seb128> pitti, ok, thanks
[13:34] <seb128> I will debug
[13:34] <seb128> pitti, btw do you have an opinion on new poppler from Debian and if we should merge this cycle?
[13:35] <seb128> they added a new binary from private .h files and multiarched it
[13:35] <pitti> oh, they have 0.18.4 now, nice
[13:35] <seb128> yes, in experimental
[13:36] <pitti> seb128: looks like an easy merge
[13:36] <pitti> seb128: want me to look into it?
[13:36] <seb128> pitti, well I think slangasek said that multiarching libs was a ffe
[13:36] <seb128> so I prefer to ask before
[13:36] <pitti> oh, I see
[13:37] <seb128> pitti, if you want to, sure, I've enough to keep busy with GNOME today (and this week) ;-)
[13:37] <pitti> I thought that was mostly for natty when we introduced it
[13:37] <seb128> pitti, well maybe it's not ffe material, I seemed to remember that
[13:37] <seb128> but maybe it was natty yes ;-)
[13:38] <seb128> pitti, well in any case I think we should merge on them if we can, especially for the new binary, avoid having to deal with a transition starting next cycle and having the keep compat until the next lts
[13:39] <pitti> right
[13:39] <pitti> seb128: I asked in #u-release
[13:39] <seb128> pitti, danke
[13:40] <pgraner> didrocks, I think the latest gnome-control-center broke the launcher, I filed https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/937792
[13:40] <ubot2`> Launchpad bug 937792 in gnome-control-center "Left launcher does not revel when in autohide mode on multi-monitor setups" [Undecided,New]
[13:41] <seb128> pgraner, you didn't get the new control center it seems from that bug
[13:41] <seb128> gnome-control-center (1:3.3.5-0ubuntu4) precise; urgency=low
[13:41] <seb128> ii gnome-control-center 1:3.3.5-0ubuntu3 utilities to configure the GNOME desktop
[13:41] <seb128>
[13:41] <seb128> pgraner, it was just uploaded
[13:41] <seb128> pgraner, also the control center has nothing to do with behaviours, it just applies configurations
[13:42] <seb128> pgraner, i.e if you didn't change a config, you could as well have g-c-c not installed, it's not impacting on any runtime behaviour
[13:42] <pgraner> seb128, ok, sorry missed the digit on ubuntu...
[13:42] <seb128> pgraner, that seems an unity or compiz bug
[13:42] <seb128> pgraner, do you use nvidia?
[13:42] <pgraner> seb128, yep nvidia
[13:42] <seb128> pgraner, DBO mentioned yesterday that the new nvidia drivers broke the barrier
[13:42] <seb128> pgraner, ok, reassigning to nvidia then
[13:43] <pgraner> seb128, great, I'll edit and take out the other bits in the description
[13:44] <seb128> pgraner, I reassigned with a comment
[13:45] <pitti> seb128: oh, and gir bindings, too
[13:45] <seb128> pitti, oh, right
[13:45] <pgraner> thanks seb128
[13:45] <seb128> pgraner, yw
[13:45] <seb128> didrocks, ^ btw handle the bug so unping for you
[13:59] <didrocks> back
[13:59] <didrocks> ok, seb128 sorted it out with pgraner, thanks :)
[14:00] <seb128> didrocks, wb, yw ;-)
[14:01] <seb128> didrocks, btw thanks for uploading g-c-c under my feet, need to rebase my update :p
[14:01] <seb128> (doing the new tarball update)
[14:01] <didrocks> seb128: my pleasure :-) sorry for this!
[14:01] <seb128> didrocks, no worry ;-)
[14:02] <didrocks> blame design who pinged me all of the sudden ;)
[14:02] <seb128> one day design will start using the bug tracker rather than IRC pings...
[14:02]  * didrocks will bless that day
[14:03] <didrocks> ok, now let's see this "primary" things regarding compiz
[14:03] <pitti> well, as long as IRC works, there is no reason for them to change
[14:03] <pitti> people don't voluntarily make it more difficult for them :)
[14:04] <seb128> pitti, that's the issue with people :p
[14:04] <pitti> https://bugs.launchpad.net/humans/+filebug
[14:05] <bil21al> any body tell me to which package does this bug belong https://bugs.launchpad.net/ubuntu/+source/unity/+bug/933841
[14:05] <ubot2`> Launchpad bug 933841 in unity "Ugly context menu" [Low,Confirmed]
[14:05] <didrocks> waow bug #868423, didn't see that before :)
[14:05] <ubot2`> Launchpad bug 868423 in ayatana-design "Launcher - Workspace switcher should not be in the Launcher by default" [High,Fix committed] https://launchpad.net/bugs/868423
[14:05] <seb128> bil21al, light-themes
[14:06] <bil21al> hmm ok  thanks
[14:07] <seb128> didrocks, yeah, I'm unsure about it, I'm fine with the idea but the implementation is non trivial
[14:08] <seb128> i.e dynamically blocking keybindings etc when the launcher is not there
[14:09] <didrocks> seb128: seems to be P+1 to me
[14:09] <didrocks> defintively doable, but too late for now
[14:09] <seb128> right
[14:09] <didrocks> (weird that only the unity guys was aware)
[14:09] <seb128> well I guess we could drop the icon from the launcher by default
[14:09] <seb128> not sure how much it would help though
[14:10] <seb128> didrocks, well, I knew about it, if you notice I set it to triaged by then ;-)
[14:10] <cyphermox> pitti: please see https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/528087 again, I commented -- the changes for that SRU are already in precise
[14:10] <pitti> cc1plus: error: debug output level 11 is too high
[14:10] <pitti> Sweetshark: ^ WTF
[14:11] <ubot2`> Launchpad bug 528087 in wpasupplicant "merge patch for segfault when using smartcards with NetworkManager" [Medium,Triaged]
[14:11] <didrocks> seb128: hum, ok, but you know how it is to look at all the unity bug mails, too easy to miss one :)
[14:11] <pitti> cyphermox: ah, thanks; I closed the precise task then
[14:11] <didrocks> and now that coverity is spamming us:p
[14:11] <Sweetshark> pitti: link?
[14:11] <pitti> https://launchpadlibrarian.net/93544875/buildlog_ubuntu-precise-powerpc.libreoffice_1%3A3.5.0-1ubuntu1_FAILEDTOBUILD.txt.gz
[14:11] <pitti> Sweetshark: ^
[14:11] <pitti> Sweetshark: not that I care much about ppc, but it does seem strange
[14:12] <pitti> i386/amd64 built and are in binNEW, looking
[14:12] <Sweetshark> indeed
[14:12] <cyphermox> pitti: fwiw, the fix is in maverick as well :)
[14:13] <pitti> Sweetshark: this doesn't seem to build libreoffice-report-builder again; will the next version, or should we fix the transitional openoffice.org-report-builder package?
[14:13] <Sweetshark> pitti: _rene_ just noted me that there is a Replaces: missing because I move unopkg from -common to -core.
[14:13] <pitti> oh
[14:14] <pitti> Sweetshark: so I better not binNEW them, to avoid upgrade errors?
[14:16] <Sweetshark> yes, I didnt enable report-builder yet to get the package out and I did not want to recheck if all the MIR have gone through before (so just enabled mediawiki and evo2)
[14:16] <Sweetshark> pitti: I guess so :(
[14:16] <pitti> right, understood
[14:16] <pitti> Sweetshark: does it have a versioned Breaks:?
[14:17] <pitti> Sweetshark: usually when moving a file from pkg foo to bar in version N, bar should have Breaks:/Replaces: foo (<< N)
[14:17] <Sweetshark> pitti: dunno.
[14:17]  * Sweetshark checks
[14:17] <pitti> seb128: poppler merge done, working nicely here
[14:18]  * pitti uploads
[14:18] <seb128> pitti, \o/
[14:18] <seb128> pitti, danke
[14:20] <rye> erm, guys, is it known that gnome-terminal in maximized mode gets a scrollbar thumb on the left which does not doo anything?
[14:21] <pitti> not here
[14:21] <pitti> hm, I think I entirely disabled scrollbars in my g-t years ago
[14:22] <jbicha> rye: I can confirm that bug, I don't know if it's been reported yet
[14:22] <rye> initially 2 are being shown - http://ubuntuone.com/2uqK1MnRrLINfcuG19f0Zm
[14:23] <rye> that's the same pic, not uploaded yet, sorry
[14:24] <rye> http://ubuntuone.com/5gx7bTSxGFJxgcvUSlPnLW - here's double scrollbar
[14:25] <pitti> seb128: can we switch versions.html from armel to armhf?
[14:25] <pitti> it's the new "supported" arch instead of armel
[14:25] <seb128> pitti, sure
[14:25]  * pitti does the change to the other reports
[14:25] <seb128> pitti, I didn't even realize we hardcoded archs there
[14:25] <pitti> seb128: if we don't, ignore me
[14:25] <pitti> seb128: but I was looking at http://people.canonical.com/~ubuntu-archive/testing-ports/precise_probs.html
[14:25] <pitti> and it has tons of armel stuff
[14:26] <pitti> drilling down now
[14:27] <seb128> pitti, right, we don't hardcode anything
[14:27] <pitti> seb128: ok; presumably not, as we even show powerpc
[14:27] <seb128> pitti, but feel free to put "        p.build_failures.append((record.arch_tag, record.build_log_url))" in a if arch_tag...
[14:27] <Sweetshark> pitti: http://pastebin.ubuntu.com/851419/ like this?
[14:27] <seb128> pitti, yeah, I wanted to filter ppc out for some time as well
[14:27] <pitti> seb128: most of the ppc ones are easy to fxi, though
[14:27] <pitti> it's a good reminder for which packages to give back when gtk is out of sync on arches
[14:28] <seb128> pitti, well, it's just that we don't care enough to score that to the top of version I think
[14:28] <seb128> pitti, firefox keeps sitting there for example
[14:28] <pitti> Sweetshark: looks fine
[14:28] <pitti> Sweetshark: for extra cookies, use (<< 1:3.5.0-1ubuntu1~)
[14:29] <pitti> Sweetshark: this will then DTRT for backports, PPA uploads etc. as well (which usually use a ~backports1 etc. suffix)
[14:37] <didrocks> ok, primary key back, people can enjoy again again ctrl + whatever in g-c-c :)
[14:37]  * pitti hugs didrocks
[14:37]  * didrocks hugs pitti back :)
[14:38] <didrocks> it looks a little bit fancy in ccsm, but who cares :)
[14:40] <mterry> Is someone on the cheese file override?
[14:40] <pitti> mterry: if so, nobody mentioned it here
[14:41]  * mterry is in the middle of something, but can fix it later if no one else does
[14:42] <rye> jbicha, now i can't reproduce it, hmmm
[14:42] <rye> aand now i can again
[14:42] <didrocks> hum, gconf-editor is segfault every 30s :/
[14:43] <mterry> didrocks, didn't we tell you?  that's the new Ubuntu clock; we're dropping indicator-datetime
[14:44] <didrocks> mterry: interesting, and then, I wc -l on "core dumped" to know how many ticks happened? :p
[14:44] <mterry> didrocks, apport will tell you as time passes
[14:44] <didrocks> oh, can't wait to see it! :)
[14:44] <didrocks> hum, so for all those new keybindings using super
[14:44] <didrocks> like super + arrows to switch ws
[14:44] <didrocks> I need to change the metacity keys
[14:45] <didrocks> I'm wondering if I should do that in the metacity package (which would make sense for 2D and 3D)
[14:45] <didrocks> or if we should do it "depending on session" again to preserve the fallback session
[14:54] <didrocks> let's try to have the same value for the whole distro I guess
[14:56] <cyphermox> fyi, I'll add a patch to g-c-c to allow hiding nm-applet as well, since there's a bug open about this and it's already there for bluetooth and sound as well
[14:58] <Sweetshark> pitti: I grabbed the extra cookies, currently building ...
[15:09] <Sweetshark> pitti: (although I dont think anybody will backport 1ubuntu1 ;) )
[15:09] <pitti> Sweetshark: right; it's more like a good habit to get into
[15:10] <Sweetshark> pitti: yep
[16:03] <pitti> dpm: wrt. your question from the other day: https://translations.launchpad.net/ubuntu/precise/+language-packs
[16:03] <pitti> dpm: there haven't been any delta packs for precise since Feb 09
[16:03] <pitti> dpm: that's why they are out of date, and the cronjobs keep uploading broken packages
[16:04] <dpm> pitti, argh, thanks for the heads up. Let me talk to someone on #launchpad
[16:04] <pitti> dpm: we want to upload a fresh -base set on Thursday evening for beta-1
[16:04] <pitti> dpm: I was just about to request it
[16:08]  * didrocks did some Quickly today, good old times!
[16:08]  * didrocks looks at #quickly and even don't see rickspencer3 around! ;-)
[16:09] <pitti> dpm: I requested a full update now
[16:09] <rickspencer3> didrocks, ok, loko now
[16:09] <didrocks> rickspencer3: that's because I put my glasses, isn't it? :)
[16:10] <rickspencer3> yes
[16:14] <dpm> pitti, I've just had a chat with thedac on #launchpad, he's going to look into it
[16:14] <pitti> dpm: thanks
[16:19] <dpm> pitti, if there is no notification about failed exports from LP, do you think it would be possible to detect if a langpack is broken (as in what's happening now) and get an e-mail sent to the ubuntu-translations-coordinators list from the langpacks server?
[16:19] <pitti> rickspencer3: don't get a heart attack on http://people.canonical.com/~ubuntu-archive/testing/precise_probs.html
[16:19] <pitti> rickspencer3: I just switched armhf to supported and armel to ports on /testing/
[16:20] <pitti> rickspencer3: all of it is due to the long-standing bug of LibO not building on armhf, but the one currently building ought to work
[16:20] <rickspencer3> pitti, ok, I won't look ;)
[16:20] <pitti> rickspencer3: "armhf: 111Ä
[16:34] <pitti> so, no agenda items, so no meeting today
[16:37] <seb128> pitti, great ;-)
[16:37] <seb128> <- busy
[16:37] <chrisccoulson> nice :)
[16:37] <seb128> if somebody wants to help on desktop updates feel free to pick some on the etherpad
[16:37] <chrisccoulson> i'd love to actually do some precise work this week :)
[16:38] <pitti> oh, gnome 3.3.5?
[16:38] <kenvandine> seb128, reverting the GtkDrawingArea bg_color change seems to be harmless to me, i can't find any regessions
[16:38] <seb128> kenvandine, excellent, do it!
[16:38] <kenvandine> seb128, can you think of anything besides shotwell that uses that heavily?
[16:38] <seb128> pitti, 3.3.90
[16:39] <seb128> kenvandine, no
[16:39] <kenvandine> ok
[16:39]  * kenvandine does it
[16:40] <pitti> seb128: do we need a new GTK first? (3.3.16)
[16:40] <pitti> seb128: well, that was put badly
[16:41] <pitti> seb128: I mean, it's likely that some updates do; want to work on it, or sohuld I look into it?
[16:41] <seb128> + gtk_color_chooser_add_palette@Base 3.3.16
[16:41] <seb128> + gtk_color_chooser_dialog_get_type@Base 3.3.16
[16:41] <seb128> + gtk_color_chooser_dialog_new@Base 3.3.16
[16:41]  * seb128 applies diff
[16:41] <seb128> pitti, sorry, just finishing gtk, I doubt anything needs it
[16:41] <seb128> they didn't add much
[16:41] <pitti> ah, splendid
[16:42] <seb128> that's mostly the new color chooser stuff that nothing used it yet
[16:45] <rickspencer3> Sweetshark, https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/937922
[16:45] <ubot2`> Launchpad bug 937922 in libreoffice "soffice.bin crashed with SIGSEGV in X11SalGraphics::GetResolution() (dup-of: 916357)" [Undecided,New]
[16:45] <rickspencer3> fyi
[16:45] <ubot2`> Launchpad bug 916357 in libreoffice "[Upstream] soffice.bin crashed with SIGSEGV in X11SalGraphics::GetResolution()" [Medium,Fix committed]
[16:51] <rickspencer3> Sweetshark, nevermind, I guess it was a dupe :)
[17:27]  * didrocks waves good evening, having to take the repaired heater back home :)
[17:34] <dpm> pitti, a full langpack export for precise is underway (i.e. manually started already)
[17:40] <Sweetshark> pitti: still around for a 3.5.0-1ubuntu2?
[17:48] <pitti> Sweetshark: for another 5 mins, yes
[17:49] <Sweetshark> pitti: ok
[17:49]  * Sweetshark gives it a try
[18:02] <tkamppeter> pitti, can you upload CUPS to Debian and Ubuntu? I have fixed auto-configuration of PS printers, http://www.cups.org/str.php?L4028.
[18:08] <Sweetshark> pitti: uploaded
[18:08] <Sweetshark> (to chinstrap)
[18:09] <chrisccoulson> hmmm, biking with the cut in the bottom of my big toe is quite uncomfortable
[18:14] <seb128> mterry, there?
[18:15] <mterry> seb128, yar
[18:15] <seb128> mterry, hey
[18:15] <seb128> mterry, quick question on your 97_unity_power_ui.patch
[18:15] <mterry> k
[18:15] <seb128> mterry, it seems quite complex...that's because you switched to a gtkgrid to be able to align as you wanted?
[18:16] <mterry> yeah and because I kept it dynamic (i.e. in GNOME3 you don't get the change)
[18:16] <seb128> mterry, the dynamic is check the session and call show,hide according to it?
[18:17] <seb128> mterry, just checking because I'm doing the new version update, upstream switched to gtkgrid so I think I can simplify that patch quite a while, but I wanted to check with you if I overlook something
[18:17] <mterry> seb128, yeah.  But it meant that I couldn't just make glade changes.  I had to be able to switch from boxes to grids in C
[18:17] <mterry> ooh
[18:17] <mterry> nice
[18:17] <mterry> seb128, yeah, then the majority of the complexity was just in reparenting all the widgets
[18:18] <seb128> mterry, ok, great, I like simplification
[18:18] <seb128> thanks ;-)
[18:56] <kenvandine> seb128, are you working on g-c-c right now?
[19:24] <seb128> kenvandine, trying to
[19:24] <seb128> kenvandine, but people keep uploading under my feet, first didrocks, then cyphermox, I can see you coming next ;-)
[19:24] <cyphermox> ahaha, sorry :)
[19:25] <seb128> kenvandine, joke aside the update is quite some work, upstream changed layouts and gtkbuilder files and that's no fun for our ui patches
[19:25] <seb128> kenvandine, I'm almost there, should upload in half an hour
[19:25] <seb128> cyphermox, no worry ;-)
[19:25] <cyphermox> I mentioned it this morning but I guess you had already started before then anyway
[19:25] <seb128> cyphermox, I reassigned some g-c-c but to n-m yesterday, that's making up for it ;-)
[19:26] <cyphermox> fun
[19:26] <seb128> cyphermox, I started midday but decided to get gtk and some other stuff out first and then came back to it
[19:26] <seb128> cyphermox, no worry your patch doesn't conflict with anything I was doing
[19:27] <cyphermox> ok good
[19:34] <kenvandine> seb128, ok, i'll wait until after you upload :)
[19:34] <kenvandine> although looks like cyphermox's upload has broken it for me
[19:34] <kenvandine> clicking on network just causes g-c-c to respawn over and over
[19:34] <seb128> kenvandine, what work do you plan? is that sound-nua update? if so please commit your patch before I upload, it won't conflict with other changes, the sound capplet didn't change
[19:34] <kenvandine> yeah, that is it
[19:34] <seb128> kenvandine, I bet it depends on a gsettings key and cyphermox didn't add the depends
[19:34] <kenvandine> ok... i can push my branch :)
[19:35] <seb128> cyphermox, ^ booooouh
[19:35] <seb128> kenvandine, i.e you probably need a new nm-applet with an update gsettings schemas
[19:36] <seb128> hum, no, that's still gconf
[19:36] <seb128> no gsettings abort on missing key there
[19:36] <seb128> dunno then
[19:36] <kenvandine> spawns so fast i can't kill it
[19:37] <seb128> kenvandine, kill the applet
[19:37] <seb128> it will stop the respawning :p
[19:40] <cyphermox> kenvandine: err, no
[19:40] <cyphermox> kenvandine: it depends on a gconf key, but that should be provided by nm-applet already
[19:40] <cyphermox> I uploaded nm-applet with that new key before the g-c-c changes
[19:41] <kenvandine> i am completely updated, but haven't restarted
[19:41] <kenvandine> if that matters
[19:41] <cyphermox> it shouldn't
[19:41] <seb128> kenvandine, stacktrace of the issue?
[19:42] <kenvandine> i can't tell... i get a apport dialog but it keeps getting pushed behind g-c-c :)
[19:42] <seb128> kenvandine, gdb -p $(pidof gnome-control-center)?
[19:43] <seb128> kenvandine, killing the indicator you used to open the g-c-c should stop the respawning
[19:43] <cyphermox> I've reverted these changes on my system, I'm going to reproduce it now
[19:43] <seb128> it happened to me with indicator-sound earlier, stopping indicator-sound-service did it
[19:43] <kenvandine> i ran it from a terminal!
[19:43] <seb128> it shouldn't respawn then
[19:43] <seb128> weird
[19:43] <seb128> well any gdb it?
[19:44] <cyphermox> I can't reproduce it :?
[19:45] <kenvandine> the stacktrace looks like icontheme related stuff
[19:46] <kenvandine> http://paste.ubuntu.com/851754/
[19:48] <kenvandine> doesn't actually look network panel related
[19:48] <kenvandine> but it happened when i clicked it
[19:51] <kenvandine> actually i  might have clicked on it from the session indicator while it was blowing up from my terminal session
[19:51] <kenvandine> now that i think of it
[19:52] <kenvandine> it was spewing gconf output to my terminal and i couldn't close the window
[19:53] <seb128> kenvandine, try stopping it an see if the respawns ends
[19:53] <kenvandine> i did, and it didn't
[19:54] <kenvandine> also, this is weird
[19:54] <kenvandine> attaching to the new process with gdb
[19:54] <kenvandine> i get different stacktraces
[19:54] <seb128> kenvandine, you get a SIGSEGV there?
[19:55] <kenvandine> no
[19:55] <kenvandine> it isn't crashing
[19:55] <kenvandine> it is exiting normally
[19:56] <kenvandine> so weird!
[19:56] <seb128> kenvandine, do you have several instances running?
[19:56] <kenvandine> ah, 2
[19:56]  * kenvandine connects to the other one
[19:56] <seb128> how did that happen?
[19:58] <kenvandine> one is just running, working fine
[19:58] <kenvandine> the other keeps restarting very fast
[19:58]  * kenvandine restarts :)
[19:59] <kenvandine> /usr/lib/control-center-1/panels/libnetwork.so: undefined symbol: cc_shell_embed_widget_in_header
[20:00] <seb128> kenvandine, dpkg -l libgnome-control-center1?
[20:00] <seb128> kenvandine, ldd on  the .so and grep for control-center?
[20:00] <kenvandine> well, i have my local build installed
[20:01] <kenvandine> maybe i need to rebuild now that i have all the updates
[20:01] <seb128> kenvandine, it seems you screwed your local build
[20:01] <bryceh> heh, something wants to rename /home/bryce to /home/bryce/Music
[20:01] <seb128> kenvandine, that symbol is new in the new serie
[20:02] <seb128> bryceh, I guess it's bug #540567 or equivalent
[20:02] <ubot2`> Launchpad bug 540567 in xdg-user-dirs-gtk "Dialog on login that wants to change "/home/egon/Desktop" to "/home/egon/Download"" [Low,New] https://launchpad.net/bugs/540567
[20:02] <seb128> bryceh, did you change locale? usually is a mismatch between your .config/user-dirs.dirs config and your existant dirs
[20:03] <seb128> bryceh, can you pastebin the config in that file?
[20:03] <bryceh> seb128, yeah somehow I'd gotten set to canadian or uk somewhere along the line, and returned it to usa yesterday (prior to today's update/reboot)
[20:04] <seb128> bryceh, you get that dialog on locale change
[20:04] <seb128> bryceh, it's supposed to let you rename your music, video etc to the wording matching your locale
[20:04] <bryceh> http://paste.ubuntu.com/851767/
[20:04] <seb128> bryceh, XDG_MUSIC_DIR="$HOME/"
[20:04] <seb128> that's where the message come from
[20:04] <seb128> what it wants to say is that it's going to make your xdg music dir be ~/Music and no your user dir
[20:05] <seb128> hate those bugs
[20:05] <seb128> we need a way to prevent people to delete xdg dirs :-(
[20:05] <seb128> I was discussing it with apw yesterday
[20:05] <seb128> he deleted Videos and the video lens was indexing the whole user dir for him
[20:05] <bryceh> ah, yeah I thought it might be wanting to mv $HOME $HOME/Music, which would be Fun
[20:06] <seb128> since it does index the xdg video dir, and they fallback to the dir bellow them when you delete the dir
[20:06] <bryceh> probably less fragile to fix apps to not assume xdg dirs are always going to be present
[20:06] <seb128> if that wasn't linux we would hardcode the xdg dirs on the filesystem and prevent user to deleting them :p
[20:06] <seb128> bryceh, xdg are always present, they fallback to the dir below the one which is not there
[20:07] <seb128> bryceh, that's how you got your user dir set I guess, you probably deleted the music dir
[20:07] <seb128> it fallbacked
[20:07] <kenvandine> ldd /usr/lib/control-center-1/panels/libnetwork.so |grep control
[20:07] <kenvandine> 	libgnome-control-center.so.1 => /usr/local/lib/libgnome-control-center.so.1 (0x00007f7b525bd000)
[20:07] <seb128> kenvandine, haha
[20:07] <kenvandine> damn local installs... that is why I never do that!
[20:07] <seb128> it's not only dx then :p
[20:07] <seb128> one day I will write an email to ubuntu-devel to suggest that we drop /usr/local support
[20:07] <seb128> or stop ranking it before /usr
[20:07] <kenvandine> i did it a while ago to get debug symbols for ronoc :)
[20:07] <seb128> that bites so many users
[20:08] <kenvandine> indeed
[20:08] <kenvandine> I always build packages for testing, but needed a quick way to get symbols for gdb :/
[20:08] <seb128> kenvandine, LD_LIBRARY_PATH=.libs gdb ...
[20:09] <seb128> that's how I do it
[20:09] <seb128> or for the g-c-c stuff sometime I cp the non stripped .so over the system one
[20:10] <kenvandine> setting the path wasn't working in g-c-c, it is weird behavior
[20:10] <kenvandine> anyway... whew!
[20:10] <seb128> kenvandine, right, for non libs you want to cp over the system one
[20:10] <seb128> rather than use /usr/local
[20:10] <kenvandine> so evil!
[20:10] <seb128> ;-)
[20:10] <seb128> will teach you to use /usr/local ;-)
[20:11] <seb128> that directory is reserved for men (tm) :p
[20:11] <kenvandine> i know... i promised myself i would rm -rf that right away... and forgot :)
[20:12]  * kenvandine thinks g-c-c is way too fragile
[20:12] <seb128> it is
[20:12] <seb128> this if any .so has an issue g-s-d or g-c-c is down is an issue
[20:13] <kenvandine> seb128, i'll push my branch in a few minutes :)
[20:15] <seb128> kenvandine, ok
[20:17] <kenvandine> seb128, pushed, thanks!
[20:17] <seb128> kenvandine, thank you!
[20:47] <seb128> kenvandine, still around?
[20:50] <seb128> kenvandine, unping, merge conflict resolved, it was on my side
[20:55] <kenvandine> :)
[21:18] <TheMuso> grrr is there any way one can turn off the HUD?
[21:21] <lifeless> TheMuso: not blind-friendly?
[21:27] <TheMuso> lifeless: Not accessible currently, but its not that, its that I use my alt key rather a lot, and the hud trigger is too sensative.
[21:27] <TheMuso> So using alt to switch between channels in irssi, or terminal tabs, and I find myself caught in the hud when I don't want to be.
[21:27] <lifeless> ah
[21:30] <dobey> TheMuso: i changed they keybinding to <Alt><Super> in gconf-editor
[21:30] <dobey> TheMuso: might help
[21:30] <dobey> TheMuso: it effectively disables it, anyway :)
[21:30] <soren> Is the HUD in standard UBuntu now, or is it still in a PPA?
[21:30] <TheMuso> dobey: Ah thanks, IMO thats what it should be.
[21:31] <dobey> TheMuso: well, except that super is handled by the dash, so you just get the dash with alt+super
[21:31] <dobey> soren: yes
[21:31] <TheMuso> dobey: Right.
[21:31] <soren> dobey: Yes, it's still in a PPA?
[21:31] <dobey> soren: yes it's in ubuntu
[21:31] <soren> dobey: Hm... I wonder why I'm not seeing it.
[21:31] <kenvandine> TheMuso, on my desktop it isn't sensitive enough, i have a hard time hitting alt quick enough to get the HUD to raise
[21:32] <dobey> soren: press and release left alt really fast?
[21:32] <kenvandine> on my laptop it comes up fine
[21:32] <kenvandine> but i have to press and release really fast on my desktop
[21:32] <soren> dobey: Doing so.. Nothing.
[21:32] <soren> dobey: I'm half a day behind on updates. Could that be it?
[21:32] <kenvandine> soren, no
[21:32] <dobey> soren: it's been in for a few days
[21:32] <soren> Oh, I'm on unity-2d, come to think of it.
[21:33] <dobey> that would be it
[21:33] <soren> I guess it's not supported there?
[21:33] <dobey> i don't think it's been implemented there yet perhpas
[21:34] <TheMuso> Its coming for unity-2d though afaik.
[21:35]  * soren switches to unity 3d to get in on the new hawtness
[21:43] <jbicha> my compiz has been broken since last weekend :( bug 932125
[21:43] <ubot2`> Launchpad bug 932125 in compiz "compiz crashed with SIGSEGV in Glib::Source::prepare_vfunc()" [Medium,Confirmed] https://launchpad.net/bugs/932125
[22:18] <bryceh> jasoncwarner_, btw the rhythmbox instabilities I mentioned the other day, I traced down to that RB had gotten set to scanning my entire system for music rather than just ~/Music.  It's working much better now.
[22:22] <seb128> bryceh, that seems to be another side effect of your xdg broken configuration
[22:22] <seb128> bryceh, rb watches the xdg music dir
[22:23] <seb128> bryceh, btw did you delete the music dir from the disk yourself? or did that get screwed somewhere?
[22:25] <bryceh> seb128, yes, I had deleted it some time ago (I don't use it, and it conflicts for tab completion with another M folder I do use)
[22:26] <bryceh> looks like the directory got recreated when I upgraded though
[22:26] <bryceh> (11 days ago)
[22:27] <robert_ancell> desrt, hey, do you know why GMenu no longer seems to work in Unity?
[22:33] <bryceh> seb128, btw gentle reminder about bug #934445 that you were going to take a peek at this week
[22:33] <ubot2`> Launchpad bug 934445 in gnome-settings-daemon "hits g_assert (device->priv->styli) when my Wacom Bamboo 2FG 4x5 is plugged in" [Medium,Confirmed] https://launchpad.net/bugs/934445
[22:38] <jasoncwarner_> bryceh: is that default behavior?
[22:42] <bryceh> jasoncwarner_, heya
[22:42] <bryceh> jasoncwarner_, I guess so, but removing ~/Music is definitely self-inflicted, so didn't investigate too far.
[22:42] <jasoncwarner_> bryceh: hey
[22:43] <jasoncwarner_> bryceh: what I meant was if it defaults to entire home directory or ~/music...me thinks ~/music shoudl be default ;)
[22:43] <bryceh> jasoncwarner_, oh, right yes ~/Music is the default
[22:43] <jasoncwarner_> ah, ok
[22:43] <jasoncwarner_> thanks
[22:44] <bryceh> seb128 said that removing ~/Music probably screwed up the XDG settings
[22:47] <seb128> robert_ancell, hey, how doesn't work?
[22:47] <seb128> bryceh, yeah, I upstream it yesterday
[22:48] <seb128> bryceh, still on my list but I wanted to get the updates out first
[22:48] <bryceh> great, thanks
[22:48] <seb128> bryceh, thanks for the reminder though ;-)
[22:48] <seb128> jasoncwarner_, hey
[22:48] <robert_ancell> seb128, I don't see any menus when using GMenu
[22:48] <jasoncwarner_> hey seb128 !
[22:49] <seb128> robert_ancell, right, indicator-appmenu doesn't consume gmenus... (i.e didn't get teached about them yet)
[22:49] <robert_ancell> seb128, it used to work though
[22:49] <seb128> robert_ancell, desrt is working on fixing that for hud, not sure that will fix it for the panel as well though
[22:50] <seb128> robert_ancell, right, before that we moved the hidding menu in gtk with gnome-settings-daemon settings the xsettings
[22:50] <seb128> robert_ancell, they use to show in the application as fallback (as under gnome fallback), the fallback menu would get stripped by unity and put at the top
[22:51] <seb128> used
[22:51] <robert_ancell> ah
[22:51] <seb128> robert_ancell, now gtk hide them when the xsettings is set and there is nothing for appmenu to strip and export
[22:51] <bryceh> jasoncwarner_, btw we scared up a possible patch to test for that mightymouse bug.
[22:51] <jasoncwarner_> bryceh: Awesome!
[22:52] <jasoncwarner_> bryceh: is it specific to the mighty mouse?
[22:52] <seb128> jasoncwarner_, bryceh: btw that issue of people deleting xdg dirs is a real one, not sure where to discuss it or how to solve it though
[22:52] <seb128> jasoncwarner_, we got pinged by people with issues with the video lens this week (it was going through all the user dir for the same reason, they deleted the video xdg dir)
[22:52] <bryceh> jasoncwarner_, Timo has HW and will be testing the patch, but he's going to be on travel so may be a bit
[22:52] <seb128> the screenshot application breaks when you delete the xdg dir
[22:53] <seb128> nautilus goes to cpu waste trying to build a template menu with all your user dir content if you delete the templates xdg dir
[22:53] <seb128> etc
[22:53] <bryceh> jasoncwarner_, if it is this patch, the regression affects more mice than just mightymouse
[22:53] <jasoncwarner_> bryceh: cool, thanks
[22:53] <jasoncwarner_> seb128: that sounds like something we should be working to fix?
[22:54] <seb128> jasoncwarner_, yeah, that's why I'm mentioning those issues and raising it
[22:54] <seb128> well it's an issue if you shoot yourself in the foot and delete a standard dir
[22:54] <seb128> but seems like quite some people do...
[22:54] <jasoncwarner_> seb128: do you know if we have bugs anywhere for those?
[22:55] <bryceh> jasoncwarner_, anyway, we just uncovered it; more sleuthing to come before we have something to try.
[22:55] <jasoncwarner_> thanks, bryceh
[22:58] <seb128> jasoncwarner_, yes, all those issues have been reported
[23:00] <jasoncwarner_> thanks seb128
[23:01] <seb128> yw
[23:14] <jasoncwarner_> bryceh and RAOF - thumper and lamalex have reports of X crashing for them yesterday and today and causing some general grief...could you guys ping them and have a look?
[23:17] <bryceh> jasoncwarner_, ah, I'll look for their reports in LP
[23:17] <thumper> bryceh: didn't get to LP
[23:17] <thumper> bryceh: as running nux from source
[23:18] <thumper> but normally if we crash compiz
[23:18] <thumper> we don't crash X
[23:18] <RAOF> What's it crashing in?
[23:18] <thumper> but I'm getting logged out
[23:18] <thumper> umm...
[23:18] <jasoncwarner_> thanks, bryceh
[23:18] <thumper> today it may have crashed during the upgrade
[23:18] <thumper> as it happened I was talking in a google hangout
[23:18] <thumper> I remembered that I was doing an upgrade though
[23:18] <thumper> yesterday I was just editing a google doc in chromium
[23:19] <thumper> then boom, login screen
[23:19] <RAOF> I'm sure this is the point where I wish again that I had fixed the xserver apport integration to work more reliably.
[23:19] <bryceh> if it's returning you to login screen, probably an xserver crash, so we'd need a backtrace.  See http://wiki.ubuntu.com/X/Backtracing for collecting manually, if apport isn't doing it.
[23:20] <seb128> bryceh,could well be the mesa issue you said might be fixed in the edger
[23:20] <seb128> bryceh, the retracers catch quite some dups on that one
[23:20] <seb128> bryceh, seems lot of users run into it
[23:20] <seb128> hint: we should really land that fix in precise ;-)
[23:20] <bryceh> seb128, could be, yeah.  That mesa bug sounds like it has some fairly widespread effects.
[23:20]  * thumper is on intel graphics
[23:21] <thumper> bryceh: I'll take a look at the backtrace as soon as I get a break in other work
[23:21] <seb128> thumper, do you have anything in /var/crash?
[23:21] <RAOF> thumper: Is there an Xorg.0.log.old available showing the crash?
[23:21] <thumper> seb128: yep, 6 things
[23:22] <RAOF> Any of them Xorg? :/
[23:22] <bryceh> seb128, unfortunately it sounds like the patch hasn't gotten a lot of QA upstream yet, so we're hesistant to just slap it in until we've had someone confirm it does fix things
[23:22] <thumper> nothing Xorg
[23:22] <thumper> compiz for today
[23:22] <bryceh> pastebinit /var/log/Xorg.0.log.old
[23:22] <thumper> so maybe it is us?
[23:22] <bryceh> thumper, grep intel_ from your compiz backtrace
[23:23] <thumper> bryceh: Caught signal 11 (Segmentation fault). Server aborting
[23:23] <thumper> bryceh: I'll pastebin it
[23:23] <bryceh> ok
[23:23] <thumper> http://paste.ubuntu.com/852010/
[23:24] <RAOF> Oh, that one.
[23:24] <bryceh> ok this looks different than the mesa bugs I mentioned
[23:26] <bryceh> looks more like bug #925341
[23:26] <ubot2`> Launchpad bug 925341 in xorg-server "Xorg crashed with SIGSEGV in WriteToClient()" [High,Confirmed] https://launchpad.net/bugs/925341
[23:26] <lamalex> RAOF, i have the same symptoms as thumper
[23:27] <RAOF> Ah, you've found it faster than me.
[23:27] <bryceh> see my comment #5 there
[23:28] <seb128> lamalex, same errors in Xorg.0.log.old?
[23:28] <lamalex> seb128, what should i grep for
[23:29] <lamalex> sorry i was reading the older stuff about being logged out and such
[23:29] <seb128> lamalex, look for Backtrace
[23:29] <seb128> lamalex, in /var/log/Xorg.0.log.old
[23:29] <bryceh> it'd be at the tail end of /var/log/Xorg.0.log*
[23:29] <lamalex> indeed
[23:30] <lamalex> [  7573.623] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7fba66cf41b6]
[23:30] <RAOF> I suspect we're corrupting some buffer somewhere; a version of my barrier patch that never hit the archive did that, but I'm pretty sure the version in the archive isn't doing that.
[23:30] <seb128> lamalex, what lines after that?
[23:30] <RAOF> Chase was chasing down a synaptics crash which was due to buffer corruption; that might be the cause of this, too?
[23:31] <seb128> RAOF, he uploaded a fix for that today I think
[23:31] <RAOF> seb128: Yeah, I think that's right.
[23:31] <Sarvatt> no synaptics being used in that Xorg.0.log
[23:31] <lamalex> seb128, http://paste.ubuntu.com/852021/
[23:32] <seb128> seems a different one
[23:32] <seb128> [  7573.623] 3: /usr/bin/X (MakeAtom+0x89) [0x7fba66ba9a69]
[23:33] <seb128> lamalex, yours seems to be bug #936758
[23:33] <Sarvatt> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/936758 seems a dupe of that paste
[23:33] <ubot2`> Launchpad bug 936758 in xorg-server "Xorg crashed with SIGSEGV in MakeAtom()" [Medium,New] https://launchpad.net/bugs/936758
[23:33] <ubot2`> Launchpad bug 936758 in xorg-server "Xorg crashed with SIGSEGV in MakeAtom()" [Medium,New]
[23:33] <bryceh> bug #936758
[23:33] <bryceh> hah Sarvatt beat me
[23:33] <Sarvatt> lol
[23:33] <Sarvatt> seb beat me :)
[23:33] <seb128> ;-)
[23:33] <bryceh> I was distracted copying mesa ;-)
[23:34] <bryceh> Fwiw we've got a few handfuls of xserver crashes since we updated - https://bugs.launchpad.net/ubuntu/+source/xorg-server?field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.tag=precise&field.tags_combinator=ALL
[23:34] <Sarvatt> what the heck is compiz doing there
[23:35] <thumper> ah fark
[23:35] <thumper> there was a change recently to add an atom for focused (I think)
[23:35] <thumper> I
[23:35] <thumper> I'll get sam to come and chat when he is around.
[23:36] <RAOF> No matter how mad compiz is being it shouldn't crash the server.
[23:36] <Sarvatt> it shouldn't crash the server regardless so still an x bug
[23:36] <Sarvatt> what he said
[23:37] <RAOF> That might have a similar cause to the WriteToClient thing; XInternAtom requires a reply.
[23:39] <RAOF> thumper, lamalex: Do you have any steps to reproduce?  Poking around in the core would be nice.
[23:39] <thumper> RAOF: not at this stage
[23:40] <bryceh> RAOF, yeah the WriteToClient thing is due to invalid data getting into the server somehow, and pinballing around until it crashes there.  I could imagine whatever causes that might have multiple ways to crash.
[23:40] <RAOF> bryceh: And I'm wondering whether the synaptics driver is the thing feeding the invalid data...
[23:40] <RAOF> Let's look at Chase's change...
[23:41] <bryceh> thumper, if RAOF's right, then poking your touchpad a lot might repo it.
[23:42] <RAOF> Except that it doesn't for me; I've been solely using a synaptics touchpad, and X hasn't crashed.
[23:42] <thumper> poking in what way?
[23:42] <RAOF> So there's got to be something more.
[23:42] <Sarvatt> yeah synaptics is fine here too
[23:44] <bryceh> RAOF, yep been banging on synaptics a lot here, no crashes
[23:44] <bryceh> but I think we've established that X maintainers have magical hardware
[23:45] <RAOF> Ah, ok.  Chase's fix only applies to multitouch touchpads.
[23:45]  * Sarvatt is using a multitouch synaptics
[23:48] <RAOF> So, the trigger for Chase's bug is performing touches on the touchpad while the device is disabled.
[23:49] <RAOF> In particular, if you start touch while it's disabled and then release after it's been ree
[23:49] <RAOF> re-enabled, you'll decrement a counter that hasn't been incremented.  If you keep doing this it'll end up negative, and then synaptics will start writing data outside the buffer.
[23:53] <RAOF> Ok, and this is a semi-multitouch pad, which doesn't count.
[23:56] <seb128> RAOF, btw just saw your comment on that barrier bug about nvidia issues, we have bug #937792
[23:56] <ubot2`> Launchpad bug 937792 in nvidia-graphics-drivers "Left launcher does not revel when in autohide mode on multi-monitor setups" [Undecided,Confirmed] https://launchpad.net/bugs/937792
[23:57] <seb128> RAOF, which is the issue DBO said was due to new nvidia drivers
[23:57] <RAOF> Ta.
[23:57] <seb128> yw


[05:58] <xnox> slangasek: 3.13.0-4-generic is known to be buggy in a few ways. -1 or -5 are all fixed.
[06:08] <pvl1> if im going to compile a custom kernel, should i use the ubuntu kernel's instead of kernel.orgs?
[12:06] <apw> jarkko_, "hard patching" assuming you mean "is every ubuntu kernel patched relative to its mainline equivalent" then that is a yes
[12:07] <jarkko_> what those patches usually are? fixes or drivers?
[12:07] <apw> jarkko_, and we use ufw by default (for network security) which uses a simple "DENY everything EXCEPT" framework using iptables at the kernel level
[12:07] <apw> jarkko_, fixes which arn't yet upstream yet, extra drivers not yet upstream, that is about it, plus our own configs
[12:19] <slangasek> xnox: yah, that's what rtg tells me


[00:22] <lamont> infinity/cjwatson "any soyuz host" is what I was told.
[00:23] <infinity> lamont: Yeah, that seems to be correct. :)
[00:45] <directhex> hm. is it slangasek or pitti whom i was talking to about /usr/share/doc/monofoo issues before jaunty released? i don't remember
[00:45] <slangasek> yes
[00:47] <directhex> i've convinced meebey to allow me to push a solution to clearing symlinks on upgrade to align with debian into the debian packages, on the proviso that i keep those changes strictly to ubuntu-only when building. that much i've done. so now i just want to get the preinst "right".
[00:47] <directhex> iirc you weren't too happy with a blind "if [ -L /usr/share/doc/foo ] then rm -rf"
[00:48] <slangasek> I prefer to have it guarded by a version check
[00:48] <directhex> which is $2, isn't it?
[00:48] <slangasek> also, there was some inconsistent use of quoting conventions
[00:48] <slangasek> yes
[00:48] <slangasek> (I think my comments on this were in the log of the sponsorship bug?)
[00:48] <directhex> let me find the appropriate bug
[00:49] <slangasek> bug #344750?
[00:50] <directhex> yeah, just re-reading it
[00:51]  * directhex pulls out dpkg --compare-versions
[01:38] <cjwatson> infinity: for armel, in case you hadn't noticed, note that the kernel is still in NEW - I'm sorting out its overrides now
[01:38] <cjwatson> (I see gcc-4.4 is still building anyway)
[01:52] <infinity> cjwatson: GCC will be at it for a long while still.  But thanks for sorting the kernel.
[01:54] <cjwatson> kernel's accepted now
[03:16] <geiseri_> cjwatson: hrm, how do i make sure my packages file is sorted alphabetically?
[03:16] <geiseri_> sort doesnt seem to cut it on multiple lines
[03:19] <calc> geiseri_: sort-dctrl?
[03:20] <geiseri_> will that work on a Packages file that i generate with apt-ftparchive?
[03:20] <calc> geiseri_: i think so... you can try it anyway
[03:20]  * geiseri_ will
[03:21] <geiseri_> calc: like a dream
[03:23] <geiseri_> do i need to make sure all of my Packages files are sorted, or just the one for the installer?
[03:24] <calc> well regular apt-get doesn't need them to be sorted afaik
[03:24] <geiseri_> okay
[03:25] <calc> but i don't know about the installer
[03:25] <geiseri_> cjwatson seemed to think that there was a bug associated with an unsorted Packages file
[03:26] <calc> oh maybe there is, he would more likely know than me :)
[03:27] <geiseri_> well everyone seems to know more than me when it comes to the guts of what is going on in the installer process
[03:27] <geiseri_> :D
[03:28] <calc> i used to know the guts of the installer process back around 2001
[03:28] <calc> heh, but that was pre-Ubuntu and d-i
[03:28] <calc> back with original debian boot-floppies, ugh
[03:28] <geiseri_> haha, well at that point i was still drinking suse coolaid...
[03:29] <geiseri_> i could tell you all sorts of things to do with that installer process :D
[03:29] <geiseri_> the d-i stuff is very slick though from what i can see
[03:30] <geiseri_> and the preseed is also very nice
[03:30] <calc> yea it works much better than the old debian install process anyway :)
[03:31] <geiseri_> well when you spend hours a day doing winders slipstream installers, this is a dream come true :D
[03:32] <geiseri_> crap, even with the sorted package list it still blows up on the setting up of ppoe...
[03:33] <geiseri_> hrm the real error is required package netcfg is not installed
[03:35] <geiseri_> is the order in the Packages file the order udebs are installed on the system, or is that defined somewhere else?
[03:35] <xee> Hi, I had some questions about creating a Ubuntu derivative, is this the correct place to ask?
[03:46] <geiseri_> is there a way to set the order that the install steps are performed?  so that netcfg is installed and running?
[03:57] <geiseri_> how does the debian installer decide what udebs to load and in what order?  Is that what the Packages file does?
[05:19] <ia> hello. i have a question about apport - please, correct me, if i wrong. as far as i understand, if my app provides /usr/share/apport/package-hooks/<my_app>.py file, then, if my app will crash, apport will notify of such crash automatically and offer to send bug report, so i don't need to worry about adding in my app some extra code for bug reporting in crash cases, right?
[05:23] <sbeattie> ia: not quite. apport collection of crash information is only enabled during the development cycle; it's disabled by default for releases.
[05:24] <ia> sbeattie: yep, i know about it. so, in everything else am i right?
[05:25] <sbeattie> ia: apport will do the collection for crashes or if ubuntu-bug is invoked on your software package and offer to submit it to launchpad regardless of whether /usr/share/apport/package-hooks/<my_app>.py exists or not; what adding it lets you do is automatically collect relevant information about your software and attach it to the bug report.
[05:25] <sbeattie> ia: for example, you can attach your app's logfiles or configuration settings, which apport normally would not attach.
[05:27] <sbeattie> ia: does that make sense?
[05:32] <ia> sbeattie: yes :-)
[05:33] <lifeless> ia: note that my_app is actually a package name
[05:33] <lifeless> sometimes the package name differs from your app name, if your app is named generically, or with a name another package already has
[05:40] <mpontillo> Do I understand correctly that when translating software into another language, the goal is to contribute to upstream as much as possible? (rather than cluttering debian/patches?) I'm thinking about how to best fix a bug that requires a change to a user-visible string. It's in the po files, but likely shouldn't have been. (string just "SSH")
[05:43] <lifeless> mpontillo: 'ssh' or 'SSH' ?
[05:43] <lifeless> 'ssh' is a command line tool name, and I'd agree with you, but 'SSH' is more of a noun..
[05:43] <mpontillo> lifeless: "SSH". It's a string in a dialog box. It's "translated" into "SSH" for all languages except one, where it has some additional descriptive text in parentheses.
[05:44] <lifeless> mpontillo: and whats the change you need to make to it to fix the bug?
[05:44] <mpontillo> the bug description asks to change the text "SSH" to "SFTP".
[05:44] <mpontillo> sounds simple enough ;)
[05:45] <lifeless> assuming thats correct, do it ;)
[05:45] <lifeless> if there are po files in the source package, updating their translations would seem appropriate to me. however! be aware that be build translations out of rosetta for Ubuntu main
[05:45] <mpontillo> lifeless: right, so there are two strategies. I could s/SSH/SFTP/ in all the .po files. Or I could just change _("SSH") to "SSH"...
[05:46] <mpontillo> *SFTP.
[05:46] <lifeless> ITYM _("SSH") -> "SFTP"
[05:46] <lifeless> right
[05:46] <lifeless> I'd talk to the author about the _() removal
[05:50] <ia> lifeless: yes, i know it. in fact, as far as i know, if my_app package is not part of ubuntu packages, opening page for bug reporting will looks like https://bugs.launchpad.net/ubuntu/+source/my_app/+filebug but should as https://launchpad.net/my_app/+filebug , right? if am i right, how i can change such behavior? latest version of apport have key for 3rd party software (if run it from terminal), but how i can enable "3rd-party-mode" for apport in my app, i
[05:50] <ia> f it crashes incidentally and apport starts sending bug for this?
[05:50] <mpontillo> lifeless: right. so I'd say that's a good plan, except for one fatal flaw. what if the text (written in Georgian (./po/ka.po:msgstr "SSH (უხიფათო შელი)") says "SFTP". then I'd be making a big mistake!
[05:51] <mpontillo> sigh, I guess that's what I get for trying to pick something easy to learn how bzr package maintenance is done ;)
[05:53] <lifeless> ia: I'm not sure
[05:53] <lifeless> mpontillo: there is a translation today; only the ones that are identical can be machine updated to SFTP
[05:53] <lifeless> mpontillo: the other one you should mark 'fuzzy' and machine update
[05:54] <lifeless> that will indicate it needs review
[05:56] <mpontillo> lifeless: ah, makes sense. where do I go to mark it "fuzzy"? is that directly in the .po file, or on a webapp on Launchpad somewhere? sorry for my ignorance; I've been reading docs, and have found pages on "how to translate", but not the process for manipulating strings as a developer that require translations
[05:57] <lifeless> if you're patching at this level, I'd say the po file
[05:57] <lifeless> but consider mailing rosetta-users, or lp-users or ubuntu-devel or ubuntu-motu for clarification
[06:00] <ia> and another question - could anyone tell me, please, where i can find example snippets (on python and c will be more interesting), which sending crash information, even if crash haven't been occured? I'm talking about implementing "Report a Problem" menu item behavior. Of cource, i can use something like os.system('apport-gtk -f -p my_app'), but i think, that there is a little bit more elegant solution :-)
[06:03] <mpontillo> lifeless: thanks, will do... looking at a .po file, I see there are translation notes in "#" comments (starting with "Translators:", etc) above each line to be translated, and they match /* */ comments above each string. now, I imagine those are all auto-generated, so I wouldn't want to break that process. I'll look around a bit to see how this works...
[06:25] <mpontillo> ia: you could just do "apt-get source gedit", which has the "report a problem" menu item. looks like it calls out to /usr/share/gedit-2/gedit-bugreport, a script referenced by its .desktop.in.in file.
[07:03] <lifeless> TheMuso: I've gotten some time to poke more at my raid signature
[07:03] <lifeless> TheMuso: feedback solicited.
[09:09] <cjwatson> mpontillo: maintainers don't normally edit .po files by hand. See the gettext documentation, but normally you can just edit the original source and then some Makefile will take care of it ...
[09:10] <cjwatson> mpontillo: if you find you need to force it for some reason, then the command to update a .po file from newer source strings in a .pot file is 'msgmerge'
[09:10] <cjwatson> mpontillo: you definitely shouldn't go about marking strings as fuzzy by hand
[09:12] <cjwatson> infinity: artigas and sejong are both stuck building debian-installer, I think because silo.postinst is prompting
[09:25] <infinity> cjwatson: \o/
[09:26] <infinity> cjwatson: Words can't describe how awesome that is...
[09:28] <cjwatson> and yet silo has not changed
[09:29] <cjwatson> since, like, intrepid
[09:29] <cjwatson> oh well, not going to debug it today
[09:29] <infinity> The postinst unconditionally calls silo.conf if it's not an upgrade...
[09:29] <infinity> And I've never had silo installed in the chroots.
[09:29] <infinity> So...
[09:29] <infinity> I'm at a loss.
[09:32] <infinity> Setting up silo (1.4.13a+git20070930-1ubuntu1) ...
[09:32] <infinity> Non-interactive, skipping silo configuration.
[09:32] <infinity> And that's... Not happening anymore?
[09:37] <infinity> cjwatson: Entirely possible that the chroots got their debconf frontend mangled at some point.  Let me kill these off and investigate that theory.
[09:37] <infinity> cjwatson: If that seems to be the case, I'll upload fixed ones and retry the builds.
[09:39]  * infinity scratches his head.
[09:41] <infinity> cjwatson: This is kinda messed up.  Debconf is set correctly, and sbuild exports $ENV{'DEBIAN_FRONTEND'} = "noninteractive"
[09:43] <cjwatson> I don't know of any debconf changes that might break that ...
[09:44] <infinity> cjwatson: It's not a debconf issue.  Debconf isn't even running.
[09:44] <cjwatson> indeed debconf hasn't changed since jaunty anyway :)
[09:44] <infinity> cjwatson: /usr/sbin/siloconfig just checks $ENV{'DEBIAN_FRONTEND'
[09:44] <infinity> }
[09:44] <infinity> And sbuild hasn't changed in eons.
[09:44] <infinity> Grr.
[09:45] <infinity> Certainly not that part of it anyway.
[09:45] <cjwatson> indeed it can hardly be a distro change since intrepid-proposed is breaking too
[09:45] <infinity> Yeah.
[09:45] <infinity> And I assume intrepid-release worked.
[09:46] <infinity> I'm at a loss for it being a buildd change too, though, since they... Haven't changed since the last successful d-i build.
[09:46] <cjwatson> let's check, best not assume sparc worked
[09:46] <infinity> So utterly confused right now.
[09:46] <cjwatson> but yeah, https://edge.launchpad.net/ubuntu/+source/debian-installer/20080522ubuntu28/+build/888434
[09:47] <infinity> And an entirely unrelated failure in jaunty not that long ago.  But silo installed fine.
[09:50] <infinity> Hrm.  I bet I know what it is.
[09:50] <infinity> cjwatson: Upgraded the buildds from dapper to hardy in that timeframe.
[09:50] <infinity> cjwatson: I *bet* that sudo is no longer allowed the environment leak to the apt call.
[09:50] <infinity> s/allowed/allowing/
[09:55] <lifeless> random question, joining two pipes in shell, I've either forgotten how or its not as easy as it should be
[09:55] <lifeless> (I have to processes A and B, I want all the output from A and then all that from B, to be piped into C)
[09:58] <infinity> cjwatson: Testing a fix.
[09:59] <infinity> cjwatson: (I'm shocked this is the first we've seen of this, if this is what I think it is...)
[09:59] <infinity> cjwatson: Given that the x86 buildds have been hardy for two cycles now.
[10:00] <lifeless> bah, I'm silly. (A; B) | C
[10:01] <lifeless> bai
[10:05] <infinity> cjwatson: Fixed on artigas, cowboying on sejong.  Will commit to rocketfuel when I'm more awake.
[10:06] <infinity> cjwatson: Looks like sudo got a lot more strict about environment leak, and apparently NOTHING ACTUALLY CARED except for silo's postinst. :P
[10:12] <infinity> cjwatson: Of course, your karmic build failed anyway, but not my fault this time. :P
[10:16] <slangasek> so why is siloconfig not using debconf?
[10:17] <infinity> Don't know and don't care?
[10:17] <infinity> Though, I suppose that invoking debconf even just to check for the frontend is still saner than relying on magic environment.
[10:17] <infinity> But whatever.
[10:17] <infinity> Checking DEBIAN_FRONTEND in the environment isn't exactly unheard of. :P
[10:18] <infinity> Just odd that nothing else cared enough to break.
[10:18] <slangasek> sure - four years ago.  These days things are supposed to be using debconf, not just checking the variable. :)
[10:18] <slangasek> that's why nothing else broke :)
[10:19] <infinity> Oh, debconf got promoted to Required somewhere in the last century.  That does make the argument seem saner.
[10:20] <infinity> I'm still living in the distant past where debconf was something "extra" I installed in my chroots. :P
[10:20] <infinity> slangasek: If you want to fix silo, be my guest.  Since we still build for dapper, though, I'm going to keep my sbuild fix. :P
[10:20] <slangasek> no, I don't want to go anywhere near silo :)
[10:21] <infinity> No sense of adventure.
[10:21] <slangasek> I'm afraid I'll fall in and suffocate to death amid the grain
[10:21] <infinity> I find your pun unsatisfactory.
[10:21] <infinity> Perhaps you need sleep?
[10:22] <slangasek> perhaps
[10:23] <infinity> I was tempted to stay up until armel's gcc build was done, but I can just sort all that in the morning...
[10:23] <infinity> cjwatson: Please don't re-auto the armel buildds, even after GCC is in.  The current armel chroot has all sorts of mangling done to it, and I'm going to replace it with something saner in the morning.
[10:24] <infinity> cjwatson: And your intrepid-proposed/sparc debian-installer built happily.
[10:34] <cjwatson> infinity: impressively limited breakage. Thanks
[10:35] <infinity> cjwatson: Yeah, in spite of vorlon's explanation, I'm still surprised that nothing else has exploded due to the variable going poof.
[10:35] <infinity> cjwatson: But, whatever.  I'm happy it hasn't.
[10:36] <cjwatson> I'm not likely to reauto the armel buildds anyway - I'm away until end of Sunday
[10:36] <infinity> cjwatson: Works for me.
[10:37] <mdke> When a point release is issued, does the proper name for a particular release include the point version? So is hardy called 8.04.2 or 8.04?
[10:37] <mdke> the latter still, right?
[10:38] <infinity> mdke: Depends on which proper name you're looking at.
[10:38] <infinity> mdke: Check "lsb_release -a" on a hardy system, for instance.
[10:38] <infinity> Description:    Ubuntu 8.04.2
[10:38] <infinity> Release:        8.04
[10:39] <infinity> mdke: The former is the official name/version, which includes the .2
[10:39] <infinity> mdke: But the release version doesn't increment for the sake of sanity of any tools that might check against that number.
[10:39] <Amaranth> 8.04.2 sounds like it should have been released 2 April 2008 :P
[10:40] <mdke> I see that http://www.ubuntu.com/getubuntu/download uses 8.04
[10:40] <mdke> what I'm looking at is whether, and if so when, in the documentation we should update version numbers
[10:40] <infinity> mdke: In the docs?  Never, IMO.
[10:40] <mdke> in some cases it's essential, because links to isos are broken (the iso has .2 in the name)
[10:41] <infinity> mdke: Any links to download stuff end up symlinked with 8.04->8.04.$current anyway.
[10:41] <mdke> http://cdimage.ubuntu.com/jeos/releases/8.04/release/ubuntu-8.04-jeos-i386.iso doesn't
[10:41] <infinity> mdke: And do docs actually link directly to ISOs, rather than pages listing said ISOs?
[10:41] <mdke> in one place, I think, bug 371773
[10:42] <cjwatson> the directory is symlinked but the ISO basename isn't
[10:42] <infinity> mdke: Yeah, I'd call that a bug in the way the docs are written, IMO...
[10:43] <mdke> perhaps linking to the directory is a better solution, even if it requires the user to do a bit more work
[10:43] <cjwatson> anyway, in general I think of 8.04 as the "series" and 8.04.2 as identifying a specific point
[10:43] <mdke> doing a SRU for the serverguide each time a point release is released is a bit of a pain, especially because it requires translators to redo that particular string too
[10:44] <mdke> or at least running sed over the translations
[10:45] <mdke> infinity: so you'd recommend simply pointing to the directory and telling the user to wget the relevant file from the directory?
[10:46] <infinity> mdke: As much as that's less hand-holdy, I'm seriously failing to see how someone who's expected to understand a CLI-based server with almost nothing installed (JeOS is very minimal) wouldn't be able to sort out an http directory listing.
[10:46] <mdke> yes, I don't think there is a risk that someone could get that wrong
[10:47] <infinity> Oh, there's always a risk.
[10:47] <mdke> heh
[10:47] <infinity> But, I'm in the "let them keep both halves" camp when it's not a desktop/simple use case.
[10:48] <mdke> ok. And it seems clear that generally in other cases, 8.04 should be used
[10:48] <mdke> as the generic name for the distribution
[10:48] <infinity> I see no reason to document 8.04.2 as a version number anywhere, except to name images, and in base-files, no.
[10:49] <infinity> It would be about as silly as the Apache section in the server-guide talking about apache_2.2.8-4ubuntu2, and needing an update on every security release.
[10:49] <infinity> (Well, not quite, but you get the absurdity reduction there, I guess)
[10:49] <mdke> not quite that silly, surely, but I get the point
[10:49] <mdke> :)
[10:50] <mdke> thanks for the assistanced
[10:50] <mdke> -d
[11:26] <popogomomo> one of ubuntu machines on network is throwing tons of dhcp inform packets making entire network slow
[11:26] <popogomomo> how to disable it
[11:27] <popogomomo> i have already disabled ip6 and sytem is using static address
[11:27] <popogomomo> why its throwinhg dhcp inform packets
[11:35] <popogomomo> how do i permanently disable dhcp in ubuntu
[11:35] <popogomomo> how do i permanently disable dhcp in ubuntu
[11:36] <popogomomo> its drwoning my network
[11:36] <Chipzz> popogomomo: wrong channel
[11:36] <popogomomo> i tried in ubuntu channel also
[11:36] <popogomomo> looks like a bug
[11:37] <Chipzz> not getting an answer in #ubuntu doesn't mean this is the place to ask; this is not an overflow channel for #ubuntu
[11:38] <Chipzz> and te fact that it "looks like a bug to you" doesn't make this the right channel either
[12:02] <popogomomo> is there any way stop ubuntu send dhcp infor packets ?
[12:02] <popogomomo> i have removed dhcp client
[12:22] <ia> hello. could anyone, point me, please, at python snippets, which sending crash information, even if crash haven't been occured? I'm talking about implementing "Report a Problem" menu item behavior. Of cource, i can use something like os.system('apport-gtk -f -p my_app'), but i think, that there is a little bit more elegant solution :-) results like this http://www.google.com/search?hl=en&newwindow=1&q=usage+python-apport tells me nothing, but i suppose, tha
[12:22] <ia> t for adding apport support i should write in my py file something like "import apport" and add calls of functions from apport python module, but how exactly i should do this? i will be very appreciate for any clues. and, probably, such information will be very useful for apport's ubuntu wiki page. and excuse me for annoying.
[13:05] <popogomomo> why dont ububtu dev write utility in java rather slow and wiered python
[13:05] <popogomomo> python sucks
[13:06] <trip0> hmm... that's really subjective
[13:07] <trip0> as a developer who doesn't regularly use either, I can appreciate both
[13:08] <trip0> python syntax requires getting used to... especially if you are coming from a  c style language like java.
[13:09] <popogomomo> i find java more productive and easy
[13:09] <popogomomo> also much more easy to maintain
[13:10] <trip0> both are very productive, 4th gen languages.
[13:10] <trip0> depends on how much experience you have though
[13:11] <trip0> a VB.NET programmer may be more productive in VB than he would in java
[13:12] <popogomomo> quality of code and maintainability is always better in java .......................
[13:12] <popogomomo> also tools like IDE , frameworks impact productivity which is ample in java world
[14:44] <jdstrand> slangasek, Riddell, kirkland, StevenK: syncbugbot still causing me problems. maybe launchpadbugs needs an update?
[14:45] <jdstrand> slangasek, Riddell, kirkland, StevenK: the problematic lines are:
[14:45] <jdstrand> b.comments.add(Bug.NewComment(text=''.join(output), subject=b.title))
[14:45] <jdstrand> task.set_status("Fix Released")
[14:46] <jdstrand> slangasek, Riddell, kirkland, StevenK: fyi, if you hit this I worked around it by commented those out and closing the bugs manually
[14:46] <jdstrand> slangasek, Riddell, kirkland, StevenK: the problematic lines are: well, I also commented out 'b.commit()' immediately after the above two lines, since there was nothing to commit
[14:47] <jdstrand> s/the problematic lines  are:
[14:47] <jdstrand> meh
[16:13] <kirkland> jdstrand: ah, i hit that too, on Wednesday, was asking about it
[16:14] <kirkland> jdstrand: i tried updating my launchpad cookie, as it was obviously a problem in the launchpad communications
[16:14] <kirkland> jdstrand: i gave up on syncbugbot, and just did the syncs manually
[16:14] <kirkland> jdstrand: and the bug closes
[16:15] <kirkland> jdstrand: i think it might be worth getting pitti  to have a look at it :-)
[16:27] <directhex> slangasek, are you here today? can you give me feedback on a preinst before i commit to git?
[16:59] <jdstrand> kirkland: I think it may be a simple as updating python-launchpadbugs, but we'll see
[17:00] <kirkland> jdstrand: bdmurray is pretty good with python-launchpadbugs, as I understand it :-)
[17:01] <jdstrand> kirkland: I familiar with it too, the issue isn't the use of it, but rather plb itself is dying
[17:01] <jdstrand> I'm
[17:01] <jdstrand> kirkland: but, we can see on monday
[17:12] <calc> it looks like armel needs to be set back to auto
[17:18] <Q-FUNK> I welcome suggestions for an appropriate package to reassign bug #374140 to. :)
[17:22] <ash211> Q-FUNK: looks like a driver issue to me
[17:22] <ash211> ask the poster for the relevant info in https://wiki.ubuntu.com/X/Reporting
[17:22] <ash211> I think by "frezz" they mean "freeze" :)
[17:23] <Q-FUNK> yup, it indeed looks like one, but it was reported against the entirely wrong package
[17:23] <Q-FUNK> yup
[17:23] <ash211> it's understandable why it went against upgrade-system instead of any driver package
[17:23] <ash211> that's the program the person used right before it messed everything up
[17:24] <ash211> (oh nvm, that's the only bug reported against that package, so it must not do what I think it does)
[17:29] <jdstrand> slangasek, Riddell, kirkland, StevenK, pitti: it just occurred to me that I have some launchpad api code I can steal/use to get syncbugbot working again-- I'll do that first thing on monday
[17:33] <Q-FUNK> ash211: people regurlary report whatever went wrong during an upgrade against package 'upgrade-system', when there instead should be a separate task to report failed upgrades against.
[17:33] <Q-FUNK> this is just one of many such occurences
[17:36] <Q-FUNK> I get a bunch of similar reportes every 6 months, whenever a new ubuntu release comes out - always against package 'upgrade-system'
[18:20] <a|wen> what is the status of libboost1.37 in karmic, can see that it is in main now ... is it okay to use, encouraged to use, or ?
[18:21] <james_w> encouraged
[18:23] <a|wen> okay, thx
[18:35] <calc> a|wen: we will hopefully get boost1.38 working as well to transition to for karmic
[18:36] <a|wen> calc: okay... you are the person to talk to for boost?
[18:44] <calc> a|wen: no, i just looked into it since OOo uses it also
[18:45] <calc> a|wen: debian wasn't to transition off of boost1.37 so it would be good once boost1.38 can actually build to switch to using it
[18:45] <a|wen> calc: okay ... thx for info :)
[18:46] <calc> a|wen: its probably failing to build for us due to using gcc 4.4
[18:46] <a|wen> calc: most likely ... boost 1.35 looks to be busted as well :(
[18:46] <calc> yea
[18:47] <calc> i had to switch OOo to use 1.37 which is why it is in main now
[18:47] <a|wen> calc: okay; then no wonder i can't make it due much
[18:47] <a|wen> do even
[18:48] <calc> they already released 1.39 upstream but still haven't apparently tested it against gcc 4.4 yet
[18:49] <a|wen> we'll see what happens; i'll switch to 1.37 for now as well then
[18:51] <calc> there is at least one patch in their bug tracker to fix gcc 4.4 issues
[18:51] <ScottK> That might be what 1.38 needs.
[18:52] <calc> hopefully the debian boost people package 1.39 soon then we could just jump to that after any needed gcc 4.4 fixups
[18:52] <calc> it was released a week ago
[18:53] <a|wen> 1.37 seems to work "okay" at least
[18:53] <calc> https://svn.boost.org/trac/boost/ticket/3008 <- gcc 4.4 bug i found
[18:54] <a|wen> calc: well, compared to 1.35 it is luxury ... this is the file failing for me on 1.35 http://pastebin.com/f44e80488 :(
[18:54] <calc> heh
[18:55] <LaserJock> ScottK: any chance of having 1.38 or so in -backports?
[18:56]  * calc thinks he knows a way to club OOo into building on i386/lpia
[18:57] <calc> i can just disable gcj entirely, heh :-\
[18:58] <highvoltage> hey LaserJock
[18:59] <LaserJock> highvoltage: hola
[19:51] <kklimonda> what was called the utility which manipulates .diff files?
[20:06] <geser> in which way manipulate?
[20:07] <kklimonda> I have a big diff and I'd like to get part of it (only diff for .cc files to be exact)
[20:07] <geser> filterdiff
[20:07] <kklimonda> thanks
[20:47] <Draconicus> I have a small suggestion for the #ubuntu channel's management, and this is the only sane place I can think to present it.
[20:48] <Draconicus> Ever thought of splitting the channel up with freenode managing an automatic redirect based on a user cap?
[20:48] <Draconicus> Like #ubuntu1 #ubuntu2 and #ubuntu3 - you already have an overflow channel, but #ubuntu remains massively overpopulated and very difficult to work in. There are plenty of assistants to go around these days.
[20:49] <Draconicus> I'm sure I'm not the first to suggest this... Perhaps it's futile to try.
[20:56] <LaserJock> Draconicus: I think #ubuntu-irc might be a better place
[20:56] <Draconicus> Oho. Sorry. :P
[21:02] <Nafallo> LaserJock: #ubuntu isn't a loco channel, no :-)
[21:02] <Nafallo> LaserJock: #ubuntu-ops
[21:42] <slangasek> jdstrand: hrm, it's still not working for you?  works fine here - you know that you need a cookie for !edge, right?
[21:43] <slangasek> jdstrand: anyway, launchpadlib isn't really an option, you can't sanely run launchpadlib stuff remotely...
[22:02] <kklimonda> #ubuntu-irc will be a better place for this discussion