 Is the "Cisco UCS Manager" power type completely equivalent to the "UCS Chassis Manager" chassis type?
[15:54] <karunamon> I can control individual UCS blades perfectly, but I'm getting "Failed to probe and enlist UCS nodes: Admin implicit props cannot be modified, class=lsbootVirtualMedia, prop=propAcl" in my region log
[15:54] <karunamon> when trying to add the entire chassis
[16:33] <roaksoax> karunamon: yes, it is the same thing, the problem may be that the API changing since first enabled and maas cannot discover all available machines
[18:39] <jac_cplane> looking for parted, fdisk in maas-enlist  when enlisting a node drops into initramfs  - any help on how I can repartion the disk when this happens
[18:39] <jac_cplane> in busybox
[18:39] <bladernr> roaksoax, blake_r how exactly does MAAS determine whether we're booted in legacy or EFI mode during commissioning?
[18:40] <bladernr> does it look for EFIVARs or is it some other method?
[18:42] <roaksoax> bladernr: in <2.3 we look at how the machine is booting *e.g. if it pxe boots and requests efi stuff
[18:42] <roaksoax> bladernr: in 2.4+ we look at /sys/firmware/efi
[18:42] <roaksoax> in thepehemral environment
[18:42] <roaksoax> + what it boots
[18:43] <bladernr> hrmmm... so does that mean it checks that every time the node boots? or still only at commissioning time?
[18:43] <roaksoax> bladernr: every time, but with newer firmware they have broken stuff
[18:43] <roaksoax> bladernr: making it non-backwards compat
[18:43] <roaksoax> which the system can be EFI but it can boot on legacy
[18:43] <roaksoax> but still require efi
[18:43] <roaksoax> so we added an ptpion to force the boot method in 2.4
[18:44] <bladernr> yeah, that seems to be the case here, trying to determine if they broke something in firmware (which is likely).
[18:45] <bladernr> is it possible to try 2.4?
[18:46] <bladernr> maas/next is showing me the same 2.3 that is in xenial-updates
[18:47] <roaksoax> bladernr: that's strange
[18:47] <roaksoax> bladernr: and beta1 goes out today
[18:47] <roaksoax> bladernr: which will have the efi stuff
[18:47] <roaksoax> bladernr: and they have regressed firmware
[18:47] <roaksoax> bladernr: but manufacturesrs say they dont change it
[18:47] <roaksoax> because the ipmi spec has updated as such
[18:48] <bladernr> https://pastebin.ubuntu.com/p/BphvFT6bjW/
[18:48] <bladernr> that's what apt-cache is telling me after updating it
[18:49] <roaksoax> bladernr: ah, you are running xneial ?
[18:50] <bladernr> yeah
[18:50] <roaksoax> bladernr: 2.4 is bionic+
[18:50] <bladernr> ugh...
[18:55] <jac_cplane> MAAS enlists gives sda: unknown partition level.   Any help on how to resolve?
[18:55] <jac_cplane> level=table
[19:48] <mup> Bug #1760191 opened: maas-ipmi-autodetect-tool fails during enlistment for cavium thunder 88xx crb v2 <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:Incomplete> <https://launchpad.net/bugs/1760191>
[20:03] <mup> Bug #1760191 changed: maas-ipmi-autodetect-tool fails during enlistment for cavium thunder 88xx crb v2 <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1760191>
[20:09] <mup> Bug #1760191 opened: maas-ipmi-autodetect-tool fails during enlistment for cavium thunder 88xx crb v2 <cdo-qa> <cdo-qa-blocker> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1760191>


[17:39] <gnucat[m]> https://en.wikipedia.org/wiki/RIAA_equalization#The_RIAA_curve
[17:39] <gnucat[m]> is there any Linux plugin to slow down tracks so they sound like a slowed down vinyl? 75% slowdown+riaa-equalization I suppose would do the trick
[19:25] <tarzeau> sure, opencubicplayer can do that, for realtime playback, speed/pitch separate
[19:25] <tarzeau> not sure if you can render it to wav when changing speed/pitch


[01:46] <highvoltage> ScottK: what's an AM?
[02:38] <ScottK> highvoltage: Application Manager (for Debian New Maintainer process)
[03:00] <highvoltage> ScottK: thanks. stgraber showed me how to google that properly :)
[06:45] <dholbach> good morning!
[06:47] <didrocks> good morning
[06:47] <dholbach> salut didrocks
[06:48] <didrocks> hey dholbach, did you have a good week-end?
[06:49] <dholbach> yes, I did - how about you?
[06:49] <didrocks> nice, snowy and cold :)
[06:51] <dholbach> yeah, same here - I did a long walk with the dog through a forest yesterday - it was great :)
[06:51] <didrocks> nice! :)
[06:51] <RAOF> A white dog in a snowy forest? :)\
[06:52] <dholbach> the dog was a bit whiter afterwards, yes :)
[06:58] <lifeless> how does one manually trigger a pyshared update?
[09:05] <mdz> pitti, I finally got a full retrace on my g-s-d crasher (bug 685785)
[09:25] <geser> did the plymouth theme dropped on quality? it looks pixelized to me
[09:32] <tumbleweed> geser: mine appears to have a corrupt pallete, so it could be that the anti-aliasing is using the wrong colours.
[09:33] <geser> I don't know what exactly happened, but the "ubuntu" doesn't look as smooth as before
[09:35] <tumbleweed> geser: yeah, the same, but the "waiting for foo to be mounted" text is completely unreadable (and I get a brief flash of a yellow-text tty0)
[09:36] <geser> yes, I saw that too. It looks like some ASCII block chars got displayed on top the text
[10:05] <micahg> can an AA please delete aspell-id from NEW, the packager is working on getting it in through Debian
[10:07] <micahg> slangasek: or james_w ^^ re aspell-id in NEW
[10:10] <c2tarun> can anyone please tell me about some small packaging bugs like spelling mistakes of something like that. i want to work on them.
[10:15] <geser> try one of the "bitesize" tagged bugs: https://launchpad.net/ubuntu/+bugs?field.tag=bitesize
[10:20] <dnivra> hello. I am running apt in gdb and when i print the value of a variable, output is "value optimized out". what does this mean?
[10:25] <geser> that the compiler (gcc) got rid of the variable in the optimization stage during compilation
[10:26] <dnivra> so that variable is not necessary for the correct functioning of the program?
[10:28] <Chipzz> no
[10:28] <Chipzz> it is
[10:28] <dnivra> then what did geser mean by "got rid of the variable"?
[10:29] <dnivra> so is there a way for me to get the value of a variable? normal printing out doesn't seem to work: using cout.
[10:30] <geser> dnivra: you have to rebuild without optimization (-O0)
[10:30] <Chipzz> dnivra: let me try to give a stupid example. lets say you write a program to print the value 2
[10:31] <dnivra> geser, there's a small problem with that. how do I specify that? I did in the makefile but it shows an error. hold on let me tell you what the exact error is.
[10:31] <Chipzz> int willbegone=1; printf("%i\n", i+1);
[10:31] <dnivra> okay.
[10:31] <Chipzz> i is constant so can be optimized away
[10:31] <dnivra> wait i isn't declared is it?
[10:31] <Chipzz> but it is still necessary to calculate 2
[10:31] <Chipzz> euh
[10:31] <Chipzz> sigh
[10:32] <Chipzz> int willbegone=1; printf("%i\n", willbegone+1);
[10:32] <Chipzz> s/i/willbegone
[10:32] <dnivra> oh okay i see. sorry should've seen through that.
[10:32] <Chipzz> that being said
[10:32] <Chipzz> your question is off-topic here ;)
[10:33] <dnivra> sure sure. no more on this. but i can still ask doubts on how to compile apt without optimization right?
[10:34] <Chipzz> my example is contrived, but a better example would be inline functions
[10:35] <geser> dnivra: use 'DEB_BUILD_OPTIONS="noopt"' when rebuilding apt
[10:36] <dnivra> use this option with './configure'?
[10:37] <geser> I'd use the apt source package for rebuilding (and get .deb without optimization)
[10:38] <Chipzz> dnivra: no, you have to change/add that Makefile
[10:38] <Chipzz> debian/rules
[10:38] <dnivra> i have actually been compiling that source to get the binary direct and not the deb.
[10:42] <dnivra> i just have to add " export DEB_BUILD_OPTIONS="noopt"" to debian/rules?
[10:44] <geser> in that case using "DEB_BUILD_OPTIONS="noopt" debian/rules build" should be enough to get the binary
[10:49] <dnivra> this is a very beginner question i know. where am i supposed to specify that option?
[10:58] <dnivra> where am i supposed to specify DEB_BUILD_OPTIONS="noopt"? i added it to debian/rules still am getting optimized output.
[11:02] <geser> it's an environmental variable which gets checked in debian/rules
[11:02] <geser> set it before you build the package
[11:03] <geser> if you have the apt source package and the build-depends for apt installed then the command I posted should get you an apt binary without optimization
[11:04] <dnivra> did you mean build-essential?
[11:05] <geser> build-essential and the packages listed in debian/control (Build-Depends and Build-Depends-Indep)
[11:05] <Chipzz> geser: shouldn't that work if you put it at the top of debian/rules too?
[11:05] <dnivra> i don't think it does in my case cos I don't have those packages listed in debian/control installed perhaps. lemme check.
[11:06] <Chipzz> anyway I think you have 4 options: put it in the makefile, DEB_BUILD_OPTIONS="noopt" debian/rules, debian/rules DEB_BUILD_OPTIONS="noopt", export DEB_BUILD_OPTIONS="noopt"; debian/rules
[11:10] <dnivra> Chipzz, yeah got it! i did export DEB_BUILD_OPTIONS="noopt";debian/rules. it worked. thanks! i'll keep this in mind. thanks to you too geser. now to understand and try to fix the bug.
[11:13] <\sh> moins
[13:05] <mdeslaur> @pilot in
[13:15] <sebner> slangasek: hi, on archive duty today? Mind rejecting one of the two monobristol uploads (maverick-proposed), and if bored approve it? :)
[13:18]  * dholbach hugs mdeslaur
[13:18] <dholbach> enjoy your flight with mdeslaur airlines :)
[13:38] <ScottK> micahg: If you still need something rejected, let me know what.
[13:39] <ScottK> sebner: I can reject one.  Which one?
[13:39] <sebner> ScottK: doesn't matter, both are the same
[13:43] <ScottK> sebner: Done.
[13:43] <bdrung> persia: around?
[13:43] <sebner> ScottK: take my thanks :)
[13:44] <persia> bdrung, What's up?
[13:45] <bdrung> persia: what are the responsibilities for the chair (except leading the meeting)?
[13:46] <persia> bdrung, Typically handling admin stuff (group adds, etc.), sending announcements, and writing minutes.
[13:46] <bdrung> persia: do we have a wiki page for that?
[13:47] <persia> Not to my knowledge.
[13:47] <bdrung> persia: then we need one
[13:47] <persia> I think there was one for the MC though.
[13:50] <persia> I think that got cleaned up when MC went away.  Why do we need one?  99% is self-evident from the meeting results (stuff being agreed), and the rest is just minutes.
[13:51] <persia> Ah, digging about, I think I agree we need one :)  There's some fair inconsistency historically.
[13:55] <ScottK> cjwatson: Nice post (and nice work) on fixing time synchronization.
[13:55] <cjwatson> thanks.  apparently I offended s-t-b upstream by not waiting for the upload :-/
[13:58] <bdrung> cjwatson: s-t-b?
[14:00] <cjwatson> system-tools-backends
[14:02] <bdrung> cjwatson: a, i got the mail.
[14:04] <zaytsev> [FAILEDTOUPLOAD] Failed to upload on litembilla (virtual) Retry this build
[14:04] <zaytsev> anybody has a clue what's wrong with this builder?
[14:05] <persia> zaytsev, #launchpad often is able to answer that sort of question.  I recommend providing a link to the LP page for the build.
[14:05] <zaytsev> persia, thanks
[14:22] <bigbrovar_> Hi guys, I installed Ubuntu 10.04 on a friend's sony vaio and sound did not work, even after installing all the restricted/backport modules for linux and alsa. The only thing which worked was compiling the latest stable version of alsa. Now is there a way I can write a dkms script to compile auto compile the module so that the next kernel updates wont break sound again.
[14:22] <bigbrovar_> would appreciate if anyone could point me to a doc somewhere google didn't help
[14:27] <geser> persia, bdrung: don't forget the update of the TeamReport wiki page
[14:29] <bdrung> geser: that demonstrates that we need a wiki page for it
[14:30] <geser> bdrung: updating the TeamReport is mentioned on the Agenda page
[14:31] <persia> geser, Good point.  Perhaps rather than a new page, we just need to break out the last bullet point a bit.
[14:32] <geser> what we regularly miss is mailing the outcomes of the applications to devel-permissions@ (see https://wiki.ubuntu.com/DeveloperMembershipBoard/)
[14:38] <persia> geser, Good point.  I've been sending individual announcements to u-d@ and minutes to d-p@+u-d-a@, which doesn't match what is written there.
[14:44] <bigbrovar_> are there docs on how to create dkms script to auto compile alsa modules I compiled on Ubuntu whenever I do a kernel upgrade, or am I asking a dumb question?
[14:45] <TeTeT> bigbrovar_: I'm only aware of http://linux.dell.com/dkms/, not sure if there's a better guide
[14:46] <bigbrovar_> thanks :)
[15:00] <didrocks> cjwatson: hey, is grub 1.99~20101126 is known to not starting X/gdm with nvidia proprieraty driver? I didn't find a bug in LP about it
[15:00] <didrocks> I think that dholbach got that as well
[15:00] <dholbach> didrocks, yes, same problem - but I'm not close to the machine right now
[15:01] <cjwatson> didrocks: not specifically, but please see https://blueprints.launchpad.net/ubuntu/+spec/packageselection-foundations-n-grub2-boot-framebuffer
[15:02] <cjwatson> didrocks: we knew we were going to trigger some kernel problems with this change; we deliberately changed it early in natty so that the kernel problems could be worked out.  thus, please raise this with the kernel people
[15:02] <didrocks> ahah gfxpayload=keep, I already got that issue in maverick IIRC
[15:02] <cjwatson> yes
[15:02] <cjwatson> but please do raise it on the kernel side rather than just working around it and forgetting about it
[15:02] <dholbach> didrocks, I didn't use the 'nvidia' driver in maverick, so I probably wouldn't have noticed :)
[15:02] <didrocks> cjwatson: ok, I'll raise that with kernel people then just now. I'm not changing the config file to keep it in mind :)
[15:03] <didrocks> cjwatson: thanks :)
[15:22] <SpamapS> ari-tczew: to answer your question from a couple of days ago: yes I do these patches primarily as an employee of canonical.
[15:23] <ari-tczew> SpamapS: thanks
[15:30] <smoser> cjwatson, i'm sure you've got good reasoning for this, but I wondered why openssh-server installs both /etc/init.d/ssh and /etc/init/ssh.conf rather than using dh_installinit
[15:30] <cjwatson> smoser: bug 531912
[15:31] <cjwatson> (tl;dr: upstart can't supervise services in chroots yet)
[15:50] <nemo>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
[15:50] <nemo>  2287 nemo      20   0 1562m 657m  13m S    0 17.2  25:16.21 nautilus
[15:50] <nemo>  1239 root      20   0  861m 515m 100m S    7 13.4 246:16.89 Xorg
[15:50] <nemo> looks like it is time for my bi-weekly ubuntu 10.10 reboot
[15:51] <jdstrand> didrocks: hey, so I am going through the unity bugs that affect me and commenting on them as well as filing my own. so, one thing that I think is a design decision (and therefore a bug would be possibly pointless) is not being able to use applets in the panel
[15:52] <jdstrand> didrocks: I typically use a hardware sensors, a system monitor and the hamster-applet (time tracker)
[15:52] <didrocks> jdstrand: yeah, it's a design decision. what you need is indicators
[15:52] <seb128> jdstrand, right, applet are deprecated in GNOME3
[15:53] <didrocks> and gnome-shell either won't support applets
[15:53] <jdstrand> didrocks: in Unity, I can no longer use these. I depended on the hardware sensors one for keeping tabs on my temp so my laptop doesn't melt
[15:53] <jdstrand> seb128: so all that code is now dead?
[15:53] <seb128> well you can use the logic and write an indicator
[15:53] <seb128> but it needs work yes
[15:53] <jdstrand> seb128: or is there some other way that I can use it in the new Unity world
[15:53] <seb128> no
[15:53] <jdstrand> *sigh*
[15:54] <jdstrand> seb128: so for my 3 favorite panel applets, I need to write the code to make them appindictor aware?
[15:54] <didrocks> jdstrand: right
[15:54] <Laney> could you have a panel-indicator? ;)
[15:54] <jdstrand> man...
[15:55] <jdstrand> didrocks: what is gnome3 doing about this?
[15:55] <didrocks> jdstrand: exactly the same, there is still gnome-panel for non accelerated support cases which still have applets
[15:55] <jdstrand> I mean surely, they plan to have some sort of equivalent functionality? I mean to just say "yeah, nobody uses the applets" is a little hard to swallow
[15:56] <seb128> they don't
[15:56] <jdstrand> didrocks: can I launch a gnome-panel in unity?
[15:56] <seb128> you can
[15:56] <seb128> you can put a gnome-panel at the bottom of screen if you want
[15:56] <didrocks> jdstrand: well, you can, but you will have conflicts as there will be two pagers (if you still keep the appplet)
[15:57] <jdstrand> I know you guys didn't design this, but this decision really sucks
[15:57] <jdstrand> there is good stuff in the old panel applets...
[15:58] <seb128> GNOME did a review by then
[15:58] <jdstrand> seb128, didrocks: again, I am not criticizing your decisions, just venting at the state of affairs
[15:58] <seb128> there was not so many things in applets that useful
[15:58] <seb128> not sure applets are the right way to display those infos
[15:58] <seb128> it's just that they are there
[15:58] <didrocks> most of applets are geeky, I agree
[15:58] <seb128> but maybe gadgets on the desktop would make sense
[15:59] <didrocks> I kept the default one + tomboy in my case, which is now an indicator
[15:59] <seb128> or you can write indicators as well
[15:59] <jdstrand> well, developers are geeky and need a dev environment. I would use the system monitor to make sure I didn't have runaway process
[15:59] <jdstrand> processes
[15:59] <didrocks> seb128: isn't why "The board" is aiming at, don't you think?
[15:59] <seb128> didrocks, sort of yes
[15:59] <mvo> yep, system monitor, network load, all useful info
[15:59] <jdstrand> I would use the hardware sensors to make sure my system didn't melt when compiling code
[15:59] <mvo> geeky, true
[15:59] <jdstrand> and hamster applet is a wonderful time tracking tool
[15:59] <mvo> timetracker
[15:59] <mvo> ++
[16:00] <seb128> nothing stop porting those to indicators
[16:00] <jdstrand> and arguably not geeky
[16:00] <jdstrand> sure, except time
[16:00] <jdstrand> (which is scarce in these parts)
[16:00] <seb128> well, nobody forces anybody to stop running gnome-panel
[16:01] <jdstrand> seb128: except that didrocks said there are conflicts in unity
[16:01] <seb128> it's just that standard users should not need them so it's not a priority
[16:01] <didrocks> jdstrand: the pager one (the window list)
[16:01] <seb128> jdstrand, if you keep the gnome-panel pager applet and run unity
[16:01] <seb128> just don't set any pager on gnome-panel
[16:01] <jdstrand> I'd like to run unity. I want to know what people see and file bugs so it is great by release
[16:01] <seb128> ok, so add an extra panel with only what you need
[16:01] <jdstrand> ah, just the window list
[16:01] <seb128> then put it at the bottom or something
[16:02] <jdstrand> well, maybe I can just do that then
[16:02] <didrocks> jdstrand: the good news is that you will have then alt + F2 before it's implemented in unity :)
[16:02] <jdstrand> \o/
[16:02] <jdstrand> (another annoying bug :)
[16:02] <jdstrand> didrocks, seb128: so how do I autostart the gnome-panel in the unity world?
[16:02] <seb128> jdstrand, go to system, preferences, session softwares and add a gnome-panel
[16:03]  * jdstrand doesn't see a System anymore
[16:03] <didrocks> hum, thinking about that, the new system session won't allow that…
[16:03] <jdstrand> I'll admit, I am fairly confused by Unity's organization. maybe it'll be better when Places is around
[16:04] <seb128> run gnome-session-properties
[16:04] <didrocks> jdstrand: yeah, without place, is harder :) ctrl + alt + t to open a terminal and then the command seb128 told ^
[16:04] <jdstrand> yes that works
[16:04] <seb128> jdstrand, there is no organisation yet, and yes should be better once you get the dash and places done
[16:04] <jdstrand> didrocks: are you saying that gnome-panel will not be able to be launched in the future?
[16:04] <jdstrand> autolaunched that is
[16:05] <didrocks> jdstrand: well, I'm thinking about the new session system I'm backporting and as unity will be told as providing a panel, that can be annoying
[16:05] <didrocks> jdstrand: so I'll get some test and work with upstream on it
[16:05] <didrocks> (upstream being there gnome-session)
[16:06] <seb128> didrocks, jdstrand: the way I described just adds an autostart desktop to the session
[16:06] <seb128> there is no reason that should stop working
[16:06] <seb128> that's how you would run your im client as well
[16:06] <seb128> or other things you want to start with your session
[16:07] <didrocks> seb128: not exactly, as unity will provide:panel now with the new system
[16:07] <jdstrand> seb128: ok, so if I do that, then make sure that I don't use the window list, I should be fine to sue my applets for the forseeable, yes?
[16:07] <didrocks> seb128: so gnome-panel will maybe tell "there is already a panel in that session"
[16:07] <seb128> didrocks, well, I described a way that doesn't touch required components
[16:07] <didrocks> seb128: hence the fact I'm thinking about it
[16:08] <didrocks> seb128: I'm talking about the new system which needs to touch required components
[16:08]  * jdstrand is worried
[16:08] <seb128> hum ok
[16:08] <seb128> I will let you sort that
[16:08] <seb128> jdstrand, yes
[16:08] <bdrung> cjwatson, cody-somerville, geser, persia, soren, stgraber: Quick reminder: DMB meeting it three hours.
[16:08] <didrocks> jdstrand: no worry, I'll look at that
[16:13] <jdstrand> didrocks: thanks. please at least allow for a way for us geeky developers to run some of our stuff, even if we have to jump a hoop or two to get there :)
[16:14] <didrocks> jdstrand: well, I think adding to the session is a reasonable tradeoff
[16:14] <didrocks> jdstrand: the thing is that it will impact your ubuntu classic session
[16:14] <jdstrand> didrocks: I am totally fine with that
[16:14] <didrocks> jdstrand: so, you will get the same one panel, and such…
[16:23] <jdstrand> hmmm, I am going to really screw up my Classic Desktop if I fiddle with this enough...
[16:24] <sebner> jdstrand: without using compiz \o/
[16:24] <didrocks> jdstrand: yeah, the configuration is common, it's basically the same issue I got in lucid for UNE vs gnome session
[16:26] <jdstrand> I wonder if I can just remove top_panel_screen0 from the /apps/panel/general/toplevel/toplevel_id_list...
[16:28] <didrocks> jdstrand: you can, but it will still impact both sessions
[16:29] <jdstrand> well, I can at least do gconftool-2 --dump /apps/panel > classic-panel.xml
[16:29] <jdstrand> and then use --load to get it back
[16:29] <jdstrand> that should be ok
[16:29] <didrocks> jdstrand: quite hackish but yeah :)
[16:29] <jdstrand> didrocks: sound reasonable?
[16:30] <didrocks> that should work :)
[16:30] <jdstrand> I hope to not go back. I just want a safety net :)
[16:30] <didrocks> in fact, it's not very different to what compiz is currently doing with the gconf backend on profile change
[16:34] <doko> ScottK: any progress on 661901?
[16:52] <hallyn_> hm, if i don't miss my guess, installing banshee caused me to lose all my radio links in rhythmbox
[16:54] <micahg> ScottK: aspell-id, the packager is going through Debian instead and the version should've been different
[16:55] <ScottK> Looking
[16:56] <ScottK> micahg: Looks like someone got it already.
[16:57] <micahg> ScottK: ok, great, thanks
[17:01] <ScottK> doko: Updated.
[17:02] <mdeslaur> @pilot out
[17:04] <doko> ScottK: did you look at these packages at all?
[17:05] <ScottK> doko: I did not review the source.  I was just trying to help clear up component mismatches and Main depwait when I filed the original bug.
[17:26] <ScottK> doko or barry: Will you merge python-defaults from Experimental (I don't have time to look at it this week, but it would enable me to sync the last non-dh_python2 Python package I maintain in Debian).
[17:27] <doko> I can do this this week
[17:33] <cjwatson> ScottK: if it helps any by way of motivation, I just merged ebroder's backport-helper branch into ubuntu-archive-tools
[17:33] <ScottK> cjwatson: That's great news.
[17:33] <cjwatson> I would love to have a real backport request to try it out on. :-)
[17:39] <ScottK> cjwatson: Bug #685982
[17:40] <ScottK> That should be good to go.
[17:40]  * cjwatson gives it a go
[17:43] <cjwatson> (looks ok, I'm just beefing up the script a bit in light of that)
[17:44]  * ScottK nods
[17:50] <quadrispro> hi all!
[17:50] <quadrispro> ScottK, thanks for bug #685982
[17:53] <cjwatson> quadrispro: we're running it as a test case for the new archive admin backport-helper tool
[17:53] <quadrispro> good to know
[18:05] <cjwatson> ScottK,ebroder: excellent.  I made some extensions (although ebroder's initial version was perfectly functional), and this seems to be working quite smoothly now.
[18:05] <cjwatson> ScottK,ebroder: I think I can commit to running this just as frequently as I run sync-helper now, which is normally at least once per working day.
[18:06] <ScottK> cjwatson: Great.  It seems then that some documentation on the archive-admin page and we're done.
[18:06] <ScottK> cjwatson: Thanks.  That will help a lot.
[18:06] <cjwatson> yep, off to do that now
[18:06] <cjwatson> mind you, sync-helper isn't documented either
[18:08] <ScottK> Ah.  Good point.
[18:14] <cjwatson> done now
[18:14] <cjwatson> ebroder: the one thing this doesn't get quite right is that it uses the requestor as the Changed-By, rather than the backport-approver as specified in ArchiveAdministration.  Maybe this needs to scan through comments for a backports team member or something?
[18:15] <cjwatson> (Changed-By> i.e. -b in mass-sync.py input)
[18:23] <tkamppeter> pitti, I have loaded a bug fix on the PDF filters into the CUPS repo, please take it into account when uploading.
[18:24] <mterry> RoAkSoAx, were you going to do the -V thing for cluster-glue or were you still waiting on feedback?
[18:26] <pitti> tkamppeter: why did you "merge" the new upstream release commit?
[18:29] <tkamppeter> pitti, I did the following:
[18:30] <tkamppeter> I did "bzr pull" and got "up to date", then I applied the patch from Koji Otani and tested it, taking something like half an hour. Then I made a debian/changelog entry.
[18:31] <pitti> tkamppeter: ok, I cleaned up; can you please do "bzr pull --overwrite" in your checkout?
[18:31] <tkamppeter> pitti, after that I did "bzr commit" and "bzr push"
[18:32] <pitti> tkamppeter: oops, forgot something; fixed, please pull --overwrite again
[18:32] <tkamppeter> So my patch is now in the repo, too?
[18:32] <\sh> micahg: I'm preparing zend-framework 1.11.1 for upload...could you do the backport stuff later on? :)
[18:33] <pitti> tkamppeter: yes
[18:33] <tkamppeter> pitti, thank, and sorry, it was really a coincidence, we worked on CUPS exactly at the same time.
[18:33] <micahg> \sh: yep, thanks
[18:33] <pitti> tkamppeter: right, apparently; sorry for the mid-air collision
[18:33] <pitti> tkamppeter: do you have other things you want to land in cups, or should I do an upload?
[18:33] <\sh> micahg: thx a lot :)
[18:35] <tkamppeter> pitti, now you can do it, thanks.
[18:35] <pitti> ok
[18:44] <\sh> micahg: uploaded
[18:47] <RoAkSoAx> mterry: I'm doing the -V thing, I just wanted to test some other unrelated stuff before uploading
[18:55] <mterry> RoAkSoAx, OK, no rush.  Just wanted to make sure you weren't waiting on me
[18:58] <RoAkSoAx> mterry: ok :). Will let you know when I upload! Thanks!
[19:14] <kees> @pilot in
[19:36] <ari-tczew> kees: could you sponsor this one? https://code.launchpad.net/~clint-fewbar/ubuntu/natty/php5/fix-mssql-segfault/+merge/42705
[19:37] <kees> ari-tczew: sure, let me take a look at it. thanks for bringing it up. :)
[19:39] <kees> ari-tczew: can you flip your review to "approved" for that one, if you're okay with it?
[19:41] <ari-tczew> kees: for above case I need again testbuild, let me look
[19:41] <kees> ari-tczew: oh, I thought your review comments were mostly about the patch format?
[19:42] <ari-tczew> kees: quite. why you ask?
[19:42] <kees> ari-tczew: I guess I meant, it doesn't need a rebuild test if it was just the patch formatting you wanted to see changed. if the way it looks is good with you, I can upload it.
[19:43] <kees> ari-tczew: but I was hoping you could change your review from "Needs Fixing" to "Approved"
[19:43] <ari-tczew> kees: aha, I would like test build again.
[19:43] <kees> ari-tczew: okay, sounds good
[19:43] <ari-tczew> to make sure
[19:44]  * kees nods. good idea
[19:45] <ari-tczew> kees: so for time building, could you sponsor my merge? bug 684874
[19:45] <kees> ari-tczew: sure! let me go read that one too.
[19:48] <ari-tczew> kees: btw I had an a case to security team and I would to be on meeting, but I've falled asleep :/
[19:48] <ari-tczew> fallen *
[19:48] <kees> ari-tczew: no worries, feel free to email too.
[19:49] <ari-tczew> kees: nothing important
[19:49] <kees> ari-tczew: so, for rabbitmq-server, did you review the diff between 2.2.0-0ubuntu1 and 2.2.0-1 ?
[19:49] <ari-tczew> kees: yes
[19:49] <ari-tczew> I have it on disk
[19:50] <kees> okay, cool.
[19:50] <lifeless> kees: hey hey
[19:50] <kees> let me finish the php5 thing, and I'll do this one next. one moment...
[19:50] <lifeless> kees: so, i didn't hear back
[19:50] <kees> heya lifeless
[19:50] <lifeless> kees: hows the performance?
[19:50] <kees> lifeless: let me start a quick download, one sec.
[19:55] <kees> lifeless: reasonably fast, no 503s. I remain happy. :)
[19:56] <lifeless> :)
[20:00] <zzak> Hello everyone, I was wondering where might be the best place to ask about maintaining an out of date package for ubuntu? It's been over 2 years since the last release.
[20:05] <kees> ari-tczew: okay, looking at rabbitmq-server closely now. Usually, it's easier to review a debdiff between the Debian package version and the to-be-uploaded Ubuntu package version. In this case, 2.2.0-1 vs 2.2.0-1ubuntu1. Your debdiff is between 2.2.0-0ubuntu1 and 2.2.0-1ubuntu1.
[20:06] <kees> I think what you've got is very close to correct if not already 100% correct, but I'm just poking at it from the other direction now.
[20:07] <mterry> lifeless, ping about python package names
[20:09] <vorian>  /12
[20:09] <lifeless> mterry: hi
[20:10] <mterry> lifeless, I just fixed a bug you filed about the name of python-quickly-widgets (nee quickly-widgets).  But realized that in your bug, you recommended python-quickly.widgets.  Is that right?  With the period instead of a dash?
[20:11] <lifeless> mterry: foo-bar isn't a valid python module name
[20:11] <lifeless> mterry: is the code accessed via 'import quickly.widgets' ?
[20:12] <lifeless> mterry: if so then the package/module *is* 'quickly.widgets' and the package name should be python-$packagename -> python-quickly.widgets
[20:12] <lifeless> mterry: see e.g. python-zope.interfaces
[20:12] <kees> ari-tczew: I'll be uploading this shortly; have you forwarded the delta to Debian for rabbitmq-server by any chance?
[20:13] <ari-tczew> kees: I thought that this is Ubuntu-related delta.
[20:13] <kees> ari-tczew: there's a debian change to the watch file too, which I figure should probably track Debian.
[20:13] <mterry> lifeless, understood.  I just had a hard time finding that in the policy manual, so I thought I'd ping you.  This package also provides quickly.prompts, but that is a secondary smaller module, so I believe the policy says it can just be subsumed into the more important quickly.widgets package?
[20:13] <kees> ari-tczew: it's not clear to me. neither Ubuntu nor Debian had rabbitmq-server packages prior to version 1.6.0, so I'm not sure why that delta is there at all.
[20:13] <lifeless> mterry: policy is pretty flexible here, for good or bad :)
[20:14] <ari-tczew> kees: I also dunno.
[20:14] <ebroder> mterry: It's in the Python policy. http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names
[20:14] <ebroder> Err...I thought it was. Maybe it's not
[20:14] <lifeless> ebroder: its not precise enough to disambiguate
[20:15] <lifeless> ebroder: perhaps we should propose a patch to clarfiy
[20:15] <ScottK> Patches welcome.
[20:15] <lifeless> ebroder: the handling of multiple modules is there.
[20:15] <ebroder> lifeless: I definitely saw something somewhere recently that wasn't ambiguous...
[20:15] <mterry> lifeless, a simple example would be good
[20:16] <kees> ari-tczew: actually, based on bug #506985, I think this delta should have been dropping in maverick/
[20:16] <kees> zul: can you verify that to be true?
[20:16] <kees> zul, ari-tczew: if so, this should just be a sync.
[20:17] <zul> reading backlog
[20:17] <ari-tczew> +1
[20:18] <zul> kees: yeah it was in the release notes when they upgraded from the previous verison they get a warning
[20:18] <lifeless> mterry: anyhow, long answer short: the . is deliberate and appropriate
[20:18] <kees> zul: right, but it should have only been for Lucid, right? If that's true, we can just drop this delta and sync?
[20:18] <mterry> lifeless, gotcha, will fix
[20:18] <zul> kees: right
[20:19] <kees> zul: sync it is. :)
[20:20] <kees> jdstrand: can I borrow you for a moment to perform a sync for me? rabbitmq-server care of bug #684874?
[20:20] <jdstrand> kees: sure
[20:20] <ari-tczew> kees: or you can use script syncpackage :)
[20:21] <kees> ari-tczew: that just creates a new bug; I wanted to actually close the merge you had open (I converted that merge bug into a sync bug)
[20:22] <ari-tczew> kees: syncpackage rabbitmq-server -b 684874
[20:23] <ebroder> kees: You're confusing requestsync and syncpackage
[20:23] <ari-tczew> kees: however, I'm fine with converted request. let's jdstrand do this (:
[20:24] <kees> ebroder: ah, so I am. what does syncpackage actually do? isn't it preferred for archive admins to do the sync?
[20:24] <cjwatson> It is.
[20:24] <cjwatson> syncs happen in <1 working day nowadays.
[20:24] <kees> ah, righto. quick read of the code shows that syncpackage is just a manual sync. I'll wait for jdstrand to DTRT instead. :)
[20:25] <ebroder> cjwatson: Is there an interesting difference in end result between the archive admins doing a sync and syncpackage doing a sync?
[20:26] <kees> SpamapS: I'll be uploading your php5 merge in a few minutes; waiting for the testsuite to finish now.
[20:26] <ebroder> cjwatson: Oh, also - I'll take a look at fixing the uploaded-by for backport-helper. I wasn't paying attention when I picked what name to use there. Something like looking for the "last backports team member that set the bug to IN PROGRESS" should be easy
[20:26] <cjwatson> ebroder: we might be willing to debug it if something went wrong with the former. :)
[20:26] <cjwatson> (it's a verbatim copy and there are essentially no checks that it really is verbatim - having it be server-side is more robust)
[20:26] <cjwatson> ebroder: cool, thanks
[20:33] <SpamapS> kees: awesome thanks! :)
[20:37] <kees> jdstrand: thanks!
[20:39] <kees> ari-tczew: thanks for the help! php5 has been uploaded, and rabbitmq-server synced. :)
[20:40] <jdstrand> kees: sure!
[20:44] <ari-tczew> kees: np. I want to review also main requests as it's helpful to clean up SQ.
[20:49] <ari-tczew> kees: every patch pilot from Canonical works on cleaning up ?
[20:49] <smoser> cjwatson, you have a suggestion about how i can put a change into /etc/grub/default and register that change such that subsequent 'update-grub' will not prompt user for merge ?
[20:49] <smoser> (this is on lucid)
[20:49] <kees> ari-tczew: well, I'm just trying to knock items off the sponsor queue, yeah
[20:50] <cjwatson> smoser: update-grub never prompts for mergign
[20:50] <cjwatson> *merging
[20:51] <smoser> oh. you're right. it does not. i should have subsequent grub-pc install/upgrade
[20:51] <cjwatson> smoser: you can't, then, it's a dpkg conffile
[20:51] <cjwatson> trying to muck with that makes the problem worse
[20:51] <cjwatson> it's best to keep conffile changes simple
[20:51] <smoser> hm... well, maybe you can suggest a different path for me then.
[20:52] <cjwatson> currently in an overrunning meeting and with a splitting headache ... not really in the right frame of mind to be able to think creatively :)
[20:52] <smoser> alright. i'll send a mail then.
[20:57] <ari-tczew> kees: btw, you have 2 things sponsored for me (non-security stuff), I'm curious whether this number will grow up. (:
[21:24] <soren> cjwatson, smoser: /etc/default/grub isn't a conffile.
[21:24] <soren> (assuming that's what is meant when you say /etc/grub/default)
[21:25] <smoser> soren, (at least on lucid) try changing a value there, and then 'apt-get install --reinstall grub-pc'. you'll get a prompt that is a result of
[21:25] <smoser>     ucf --three-way --debconf-ok --sum-file=/usr/share/grub/default/grub.md5sum ${tmp_default_grub} /etc/default/grub
[21:26] <soren> Precisely.
[21:26] <smoser> so no, not a conf file, but that is my issue.
[21:26] <soren> ucf => not a conffile
[21:26] <smoser> you're right.
[21:27] <soren> I've seen various tricks applied for this sort of thing.
[21:27] <soren> grub (old grub) had some magic for it.
[21:28] <ebroder> soren, smoser: I thought the fact that ucf is doing a 3-way meant that you should only get prompted once (at least until the next time upstream /etc/default/grub changed)
[21:29] <soren> True.
[21:29] <smoser> ebroder, while that may be the case, its still less than ideal for me.
[21:29] <soren> There's a command line option to update ucf's cache.
[21:29] <smoser> it doesn't work here, as far as I can tell. i've tried.
[21:29] <soren> smoser: Really? Sorry, I must have misunderstood what you're trying to achive?
[21:29] <kees> jdstrand: can I bug you for another sync? this time from experimental? bug #686099, request from the debian maintainer.
[21:30] <smoser> because sum-file comes from /usr/share/grub/default/grub.md5sum (which is part of the package, and will contain the new version).
[21:30] <jdstrand> kees: sure
[21:30] <kees> jdstrand: thanks!
[21:30] <ebroder> smoser: That's only for versions of the file that existed before the package switched to ucf. ucf also maintains its own cache
[21:31] <smoser> i've tried, mabye i'm missing something.
[21:31] <soren> Explain what you've tried.
[21:31] <smoser> sudo ucfr --debug --verbose grub-pc /etc/default/grub
[21:32] <smoser> ie, a.) make change to /etc/default/grub b.) run ucfr grub-pc /etc/default/grub c.) run sudo apt-get install --reinstall grub-pc
[21:32] <smoser> d.) get prompted
[21:34] <smoser> soren, is that not what i should expect would tell ucf that I have updated that file?
[21:34] <soren> smoser: Er... Even on reinstall?
[21:34] <jdstrand> kees: done
[21:35] <soren> smoser: That should never trigger a prompt. Even if you didn't muck about with ucfr.
[21:36]  * jdstrand waves hi to soren
[21:36] <soren> smoser: If the package being installed doesn't contain a change to the contents of the file compared to the last installed version of the same package, any changes you made to the file are just kept.
[21:36] <soren> jdstrand: dude!
[21:36] <jdstrand> :)
[21:37] <soren> smoser: That's what dpkg does (and ucf attempts to mimic).
[21:37] <smoser> well, it is doing that for me. on ec2 instance.  possibly i'm doing something terribly rude in image build
[21:38] <soren> smoser: Possibly.
[21:38] <soren> smoser: Can you reproduce it on your laptop?
[21:38] <soren> smoser: My test involes changing one of the comments in the file.
[21:38] <smoser> comment wont work.
[21:39] <soren> Oh, it's filtered?
[21:39] <smoser> has to be somethign that will get through to /boot/grub/grub.cfg
[21:39] <soren> Bah, of course.
[21:39] <soren> Same thing.
[21:39] <soren> Oh, hang on.
[21:40] <smoser> the thing i'm changing is '#GRUB_TERMINAL=console'
[21:40] <smoser> uncommenting
[21:40] <smoser> but also changes to GRUB_CMDLINE_LINUX_DEFAULT= like adding 'foo=bar' affect it (on 10.04)
[21:41] <soren> On 10.10 as well.
[21:42] <soren> That shouldn't happen.
[21:42] <smoser> tried on natty, and do not get prompted
[21:44] <soren> Aah...
[21:44] <soren> Ok.
[21:47] <smoser> its strange, i'm not seeing the issue now though. soren did you have an explanation ?
[21:47] <soren> Half.
[21:49] <smoser> do you care to share ?
[21:49] <soren> I'm trying to :)
[21:50]  * smoser puts hands to temples and attempts to get soren's mind message
[21:50] <soren> Don't. You'll be as confused as I am.
[21:51] <RoAkSoAx> slangasek: howdy!! I have a question regaring a library split. In debian/rules, there's a binary-common: target on which dh_makeshlibs is without the -V option. This -V is necessary if there are no .symbols files, right?
[21:53] <mdeslaur> cjwatson: we're not installing gnome-system-tools anymore in natty? no more graphical tool to add a second user?
[21:57] <soren> smoser: Sorry, I don't think I can wrap my head around this at this hour.
[21:58] <smoser> no problem. have a nice night soren.
[21:58] <RoAkSoAx> win 5
[22:15] <SpamapS> woohoo.. cassandra packages running unit tests. :)
[22:16] <lifeless> nice
[22:34] <RoAkSoAx> mterry: ok I think i'm ready to upload. Were you able to get feedback for the -V to dh_makeshlibs?
[22:35] <mterry> RoAkSoAx, oh no, I wasn't yet.  I'll ping tomorrow
[22:35] <RoAkSoAx> mterry: should I wait to upload, or should I just go ahead and do it?
[22:37] <mterry> RoAkSoAx, uh I guess upload and we can always back it out.  I think the assumption was that if this other package did it, it was the correct thing, right?  I'm just double-confirming with someone who would actually konw
[22:48] <RoAkSoAx> mterry: alright then. it is done :)!
[22:51] <Sarvatt> nasty, I've counted at least 150 bugs here so far caused by this limitation not being more common knowledge - https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/562312/comments/7
[22:53] <ebroder> Sarvatt: Workaround: use a USB drive larger than 4G, so that the FAT file size limitations prevent users from actually using all remaining space
[22:54]  * ebroder ducks
[23:48] <bdrung> persia: around?


[10:23] <santa_> good morning everybody
[10:23] <santa_> RikMills: I've just pushed to git a hotfix for akonadi installed files
[10:23] <santa_> (that package was the only one in red in my latest test rebuild)
[11:27] <santa_> also I see kaccounts-integration probably needs a git push ;)
[11:41] <RikMills> done
[11:46] <santa_> thanks a lot, btw I'm considering to get a very powerful machine to do the test rebuilds, upgrade the thing to 20.04 and if I have enough time continue the work on the docs so you could replicate it in a professionally hosted infra
[12:54] <BluesKaj> Hi all


[00:09] <eggy18> LRH OFFICIAL: We are not spamming you | https://www.youtube.com/watch?v=_utMUBnl3nk
[00:33] <swapgs0> LRH OFFICIAL: We are not spamming you | https://www.youtube.com/watch?v=_utMUBnl3nk
[02:21] <cheshire_cat> LRH OFFICIAL: We are not spamming you | https://www.youtube.com/watch?v=_utMUBnl3nk
[03:05] <fford26> LRH OFFICIAL: We are not spamming you | https://www.youtube.com/watch?v=_utMUBnl3nk
[06:19] <Guest11868> LRH OFFICIAL: We are not spamming you | https://www.youtube.com/watch?v=_utMUBnl3nk


[00:02] <robru> mterry (or anybody really), I need a bit of help with a packaging issue. I need to know the difference between debian/tmp and debian/binary-package-name and what kind of logic DH uses to pick which of those it uses. I've got a package where I'm trying to build multiple binary packages and dh_install is dumping files from both binary packages into debian/tmp where they clobber each other. Some documentation indicates that
[00:02] <robru> debian/[binary-package-name] is the default, but it's not using that and I'm not sure how to make it use that.
[00:04] <TheMuso> robru: I think dh checks to see if there are multiple binary packages defined in the control file. If so, then by default, debian/tmp is used as the temporary install location.
[00:04] <TheMuso> robru: If there is only one package, then the files are just put into debian/binary-package-name.
[00:05] <TheMuso> robru: You may need to tell dh_install to use a different location to dump files for each binary package.
[00:06] <robru> TheMuso, oooooooh, ok. what I'm doing is trying to build two different binaries (with different ./config opts) from a single source tree, and then dh_install is just dumping the results of both into the same debian/tmp, one clobbering the other. so I guess I'll have to use the -P option to force it to build in separate tmpdirs to avoid clobbering each toehr
[00:06] <robru> TheMuso, heh, yeah.
[00:06] <robru> TheMuso, thanks
[00:06] <TheMuso> robru: np.
[00:07] <robru> TheMuso, for some reason I was expecting debian/tmp to be used for a single binary package, and that if you had multiple packages it would be smart enough to start using debian/binary-package-name but I guess my situation seems to be opposite of what the debian developers were anticipating (multiple different builds VS. one build split into separate packages)
[00:07] <TheMuso> robru: Yeah, but thats what overrides are for right, to deal with those odd situations. :(
[00:07] <TheMuso> s/:(/:)
[00:08] <robru> TheMuso, yeah for sure, just a matter of correcting my expectations. was confused about why it was doing certain things certain ways
[00:09] <TheMuso> Right.
[00:26] <robert_ancell> GunnarHj, ping
[03:18] <darkxst> pitti, Laney https://bugs.launchpad.net/ubuntu-gnome/+bug/1172105
[03:18] <ubot2> Launchpad bug 1172105 in systemd (Ubuntu) "org.freedesktop.login1.PowerOff() call doesnt work" [Undecided,New]
[05:33] <pitti> Good morning
[05:34] <pitti> darkxst: duped to bug 1171504, that one already has a patch
[05:34] <ubot2> Launchpad bug 1171504 in systemd (Ubuntu) "org.freedesktop.login1.Manager.PowerOff doesn't work" [Medium,Triaged] https://launchpad.net/bugs/1171504
[05:34] <pitti> (just blocked by freeze)
[05:38] <pitti> darkxst: ah, pretty much the same patch as Laney wrote :/
[05:42] <darkxst> ok
[06:00] <darkxst> pitti, no luck with the suspend on lid close bug though, it really looks like it should be handled by logind but doesnt
[06:00] <pitti> darkxst: right, we need a bug for this
[06:00] <darkxst> https://bugs.launchpad.net/ubuntu-gnome/+bug/1160995
[06:00] <ubot2> Launchpad bug 1160995 in Ubuntu GNOME "Suspend isn't triggered by lid close" [Medium,Confirmed]
[06:01] <pitti> thanks
[06:01] <pitti> darkxst: adjusted to be on my May queue
[06:02] <pitti> darkxst: if you want to fix that in raring, I think it's a lot easier to just call .Suspend from the power plugin
[06:02] <mlankhorst> tkamppeter_: if you're feeling lucky try the new touch branch
[06:02] <pitti> I expect the systemd patch to be quite intrusive, as we have to introduce listening to evdev, etc.
[06:04] <mlankhorst> dont add patches on top of it, it shouldn't be needed
[06:04] <darkxst> pitti, ok, can do that easy enough
[06:06] <darkxst> pitti, also https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1172062
[06:06] <ubot2> Launchpad bug 1172062 in systemd (Ubuntu) "network manager icon does not correctly display status" [Undecided,Confirmed]
[06:07] <pitti> darkxst: do you have ConsoleKit installed?
[06:07] <pitti> argh, phone
[06:07] <darkxst> pitti, yes
[06:21] <darkxst> pitti, not sure how, systemd session tracking ever worked, given the broken configure.ac
[06:22] <pitti> darkxst: did you rebuild it to use logind?
[06:22] <pitti> https://launchpad.net/~ubuntu-core-dev/+archive/logind has packages for dbus and NM (you'll need both for NM)
[06:22] <darkxst> pitti, yes I just rebased your packages against the current raring versions
[06:23] <darkxst> well for NM
[06:23] <darkxst> and pulseaudio also
[07:16] <tkamppeter_> mlankhorst, are there .deb packages anywhere of this branch? Is it 1.13 or 1.14?
[07:18] <mlankhorst> tkamppeter_: just the git branch, the debian packaging of 1.14 xserver will work on it
[07:46] <seb128> hey desktopers
[07:46] <pitti> bonjour seb128
[07:46] <seb128> pitti, salut, ça va ?
[07:47] <pitti> seb128: ça va bien !
[07:47]  * pitti aime le soleil
[07:47]  * seb128 aussi
[07:48] <seb128> 21°C sunny forcasted today, 24°C sunny tomorrow, 13°C rainy friday, 8°C rainy saturday
[07:49] <didrocks> hey seb128, pitti
[07:50] <pitti> so *just* when it starts to get really nice, we go to California
[07:50] <seb128> lut didrocks
[07:50] <seb128> pitti, it's "8°C rainy saturday" that you call really nice? ;-)
[07:50] <seb128> it seems like it's going to be ~15°C and rainy all week next week here
[07:51] <pitti> well, at least for the next few days
[07:52] <seb128> yeah, this week is great ;-)
[07:52] <pitti> oh, it doesn't actually seem to be that warm in Oakland either
[07:52] <seb128> I should get some icecream this afternoon
[07:52] <pitti> 10 (night) to 19 (day) degrees
[07:53] <seb128> http://www.weather.com/weather/tenday/94607
[07:53] <seb128> has 21-24°C next week
[07:53] <seb128> which is just perfect
[07:53] <pitti> indeed
[07:54]  * didrocks is going to enjoy today and tomorrow on the balconey, surely
[07:59] <darkxst> pitti, any idea why systemd fails to build on ppa? https://launchpadlibrarian.net/138154145/buildlog_ubuntu-raring-i386.systemd_198-0ubuntu11~raring1_FAILEDTOBUILD.txt.gz
[08:00] <pitti> darkxst: I didn't see that one yet; perhaps that sched_prio test doesn't work in kvm in general, or it's just a glitch?
[08:01] <pitti> I certainly built systemd in my logind PPA, but I think that was before runnign the tests during build
[08:01] <darkxst> pitti, ok I will just disable the tests then
[08:02] <pitti> darkxst: just append a || true after the "make check"  call in override_dh_auto_test?
[08:02] <darkxst> pitti, ok
[08:03] <Laney> morning
[08:03] <seb128> Laney, good morning
[08:04] <Laney> hey seb128
[08:08] <seb128> mvo, hey
[08:23] <mvo> hey seb128
[08:23] <seb128> mvo, wie gehts?
[08:23] <mvo> seb128: gut, danke!
[08:23] <mvo> seb128: how are yoU?
[08:23] <seb128> mvo, I'm good, thanks ;-)
[08:24] <seb128> mvo, I tested your small patch for s-c/unity-app-lens ddtp translations, works fine here ... will you submit a mr for it?
[08:25] <mvo> seb128: cool, will do
[08:25] <mvo> seb128: thanks a bunch!
[08:25] <seb128> mvo, danke
[08:25] <seb128> mvo, I was looking a bit at the preview and had some extra small questions
[08:25] <mvo> seb128: sure
[08:25] <seb128> 1- where is stored the license info? in the xapian db?
[08:25] <seb128> in what format? is that a flag or text?
[08:26] <seb128> that's not translated in the ui atm, I wonder if there is a way to get it out translated or if the lens should just do
[08:26] <seb128> if strcmp(license, "free); then license = _("Free")
[08:26] <seb128> or something
[08:28] <mvo> seb128: give me a sec (or two) and I check
[08:28] <seb128> mvo, danke
[08:28] <seb128> mvo, and second question was: where do you get the "installed on" info from? it's displaying "None" for quite some apps for me
[08:30] <mvo> seb128: ok, once I wrote the MP I will look at this as well
[08:31] <seb128> mvo, thanks
[08:31] <seb128> mvo, feel free to ignore me if you are work or other stuff to do, there is no hurry ;-)
[08:31] <seb128> mvo, I just tracked some code bugs in the lenses and unity to fix some of the translation issues in the preview code and hit those on the way
[08:32] <mvo> seb128: https://code.launchpad.net/~mvo/software-center/fix-data-provider-i18n/+merge/160565
[08:32] <mvo> seb128: I would never ignore you :)
[08:32]  * seb128 hugs mvo
[08:32]  * mvo hugs seb128
[08:45] <darkxst> pitti, more fun I guess :( Rejected:
[08:45] <darkxst> Orphaned debug packages: udev-udeb-dbgsym 198-0ubuntu12~raring2 (amd64), udev-dbgsym 198-0ubuntu12~raring2 (amd64), systemd-dbgsym 198-0ubuntu12~raring2 (amd64)
[08:50] <pitti> darkxst: can you please ask in #u-devel about this? infinity might know what's going on there
[09:19] <Sweetshark> moin everyone!
[09:33] <mlankhorst> g'day mate
[09:35] <Sweetshark> seb128: So LO 4.0.3 is likely getting tagged today. _If_ we SRU anyway for bug 1085169, I wonder if we should carry that along as it brings along some ~100 fixes: https://wiki.documentfoundation.org/Releases/4.0.3/RC1
[09:35] <ubot2> Launchpad bug 1085169 in indicator-appmenu (Ubuntu) "LibreOffice Menus Stop Working even with libreoffice>=1:3.6.2~rc2-0ubuntu4 and indicator-appmenu>=12.10.3-0ubuntu2.1" [Undecided,Confirmed] https://launchpad.net/bugs/1085169
[09:39] <Sweetshark> mlankhorst: hah, while I have one of you gnome guys here: bug 1153350 comment 16 suggests it is a gnome 3.6->3.8 update regression. Any suspicions or hint at what it might be?
[09:39] <ubot2> Launchpad bug 1153350 in indicator-appmenu (Ubuntu) "LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover" [High,Confirmed] https://launchpad.net/bugs/1153350
[09:39] <mlankhorst> wait, I'm gnome now?
[09:40] <mlankhorst> sorry to disappoint you :-)
[09:41] <Sweetshark> mlankhorst: hrhr, everyone ever having used glib is a gnome guy from my POV ;)
[09:41] <Sweetshark> mlankhorst: k, nevermind
[09:41] <mlankhorst> I'm on the other side of X
[10:21] <mvo> seb128: sorry for the delay - so just to clarify, even with my patch the "Free" is not translated?
[10:22] <mvo> seb128: the installed-on is taken from /var/log/apt/history.log, so very old entries will not be there
[10:22] <mvo> seb128: I need to double check, but do you get very new entries?
[10:28] <tkamppeter> mlankhorst, can I install xserver 1.14 simply into a Raring system without half the system getting uninstalled (or replaced by highly unstable packages of the next generation)?
[10:34] <tkamppeter> mlankhorst, the branch does not build on my Raring system, see http://paste.ubuntu.com/5597997/
[10:37] <tkamppeter> mlankhorst, the Debian packaging of xorg-server I have taken from xorg-server_1.14.0-0ubuntu0.1 from https://launchpad.net/~canonical-x/+archive/x-staging, I have taken the source package and uupdated to the GIT branch.
[10:51] <mlankhorst> just wipe 02 patch
[10:52] <mlankhorst> 02_hide_panoramix_symbol.diff will not apply, and is unneeded
[10:53] <mlankhorst> I don't see why you would lack  hw/xfree86/common/xf86Module.h though
[11:04] <tkamppeter> mlankhorst, I did the packaging of the .orig.tar.gz wrong. Rebuilt it, retrying ...
[11:08] <mlankhorst> ah, I just build from git directly :-)
[11:09] <mlankhorst> debuild -b, or if I need a source package..
[11:09] <mlankhorst> alias git-bpx='git-buildpackage --git-upstream-branch=upstream-experimental --git-upstream-tree=branch --git-ignore-branch --git-ignore-new --git-no-pristine-tar'
[11:12] <tkamppeter> mlankhorst, my git has no debian/ directory. Are you in the same branch as me?
[11:12] <tkamppeter> ls
[11:12] <mlankhorst> it doesn't, but you can copy it over
[11:16] <tkamppeter> mlankhorst, I am starting over with everything now, re-downloading cleanly and retrying ...
[11:26] <tkamppeter> mlankhorst, I tried the debian of xorg-server_1.14.1-0ubuntu0.1 from the PPA but there os-use-libunwind-to-generate-backtraces.patch deos not apply. From which package version did you take the debian/dir?
[11:27] <mlankhorst> just drop it
[11:27] <mlankhorst> that's upstream
[11:29] <tkamppeter> mlankhorst, yes, now it builds.
[11:32] <tkamppeter> mlankhorst, I think, now I have the path. I will cleanly re-download everything and start over ...
[11:32] <seb128> Sweetshark, hey, sorry I was out for some errand and lunch
[11:32] <seb128> Sweetshark, we should SRU 4.0.3 directly imho
[11:32] <seb128> Sweetshark, about the indicator bug, try pinging larsu and attente
[11:32] <mlankhorst> tkamppeter: but looks like it still triggers a bug for me in the first touch I do :-)
[11:32]  * mlankhorst practiced
[11:33] <seb128> mvo, hey, my turn to be delayed :p
[11:33] <tkamppeter> mlankhorst, what bug? Does it simply stuck down the left button as stock Raring does?
[11:34] <mvo> seb128: no worries
[11:34] <mvo> seb128: i have a meeting soon too but some minutes left
[11:34] <seb128> mvo, the license seems still untranslated to me
[11:34] <mlankhorst> tkamppeter: yeah, but fixing that was kind of the point of that branch
[11:34] <mlankhorst> ah well!
[11:35] <mlankhorst> it no longer corrupts or leaks memory any more, at least
[11:35] <seb128> mvo, history.log ... does it count upgrades?
[11:35] <seb128> mvo, my laptop is an years old install :p
[11:35] <tkamppeter> mlankhorst, so the branch contains a lot of shots at the bug but no hit at all?
[11:35] <mlankhorst> tkamppeter: no it does fix a lot of cases, just not the one I'm hitting
[11:36] <mlankhorst> I tried making sense of the touch code myself.. lets just say it's complicated
[11:36] <seb128> mvo, the oldest entry in history.log.gz* is 2012-07-02 for me
[11:36] <seb128> mvo, and my install is from 2010
[11:42] <tkamppeter> mlankhorst, Now I am stuck with http://paste.ubuntu.com/5598089/
[11:42] <Sweetshark> seb128: k, thanks!
[11:43] <tkamppeter> mlankhorst, perhaps the solution for touch on the desktop is Wayland or MIR. Perhaps X has grown too complicated to add this new technology ...
[11:44] <mlankhorst> nah it was layered wrongly, that's all
[11:45] <mlankhorst> And yeah lets just throw away everything to end up with something unproven, untested and not debugged instead because 1 thing is wrong, makes sense.. ._.
[11:46] <mlankhorst> tkamppeter: well something is still messed up there, I'm fairly sure video abi is not 7, and input abi is not 9..
[11:51] <tkamppeter> mlankhorst, next try, I forgot to switch the branch, I hope in some days I will not forget anything of this complicated build sequence ...
[11:53] <mlankhorst> http://people.canonical.com/~mlankhorst/xorg-server_1.14.1-0ubuntu0.2.diff.gz
[11:54] <mlankhorst> git checkout ubuntu+1; git merge whot/touch-grab-race-condition-56578-v2; git checkout whot/touch-grab-race-condition-56578-v2 .; git checkout HEAD debian ChangeLog; git commit; dch 'yadda yadda'
[11:54] <mlankhorst> something like that
[11:55] <mlankhorst> and then git-bpx -S to create the diff
[12:01] <tkamppeter> I am compiling now, finally!
[12:01] <tkamppeter> mlankhorst, ^^
[12:01] <tkamppeter> mlankhorst, I did
[12:01] <tkamppeter> mlankhorst, git clone ... to get the GIT
[12:01] <tkamppeter> mlankhorst, git checkout -b ... ... to switch to the branch
[12:01]  * mlankhorst only has 1 xserver git tree
[12:02] <mlankhorst> you can have multiple remotes in 1 git tree
[12:02] <tkamppeter> mlankhorst, emacs configure.ac, to allow inputproto 2.2.99
[12:03] <tkamppeter> mlankhorst, cp -a ../../ ...  /debian . to get a debian/ directory
[12:03] <tkamppeter> mlankhorst, emacs debian/control to allow inputproto 2.2.99
[12:03] <tkamppeter> mlankhorst, emacs debian/patches/series to exclude the upstreamized patch
[12:04] <tkamppeter> mlankhorst, debuild -b and it is building.
[12:12] <tkamppeter> mlankhorst, compiles bug breaks after compiling as follows: http://paste.ubuntu.com/5598177/
[12:14] <mlankhorst> oh right
[12:14] <mlankhorst> git log > ChangeLog, done..
[12:15] <mlankhorst> or touch ChangeLog, it doesn't matter
[12:21] <tkamppeter> mlankhorst, trying to build again ...
[12:22] <tkamppeter> mlankhorst, where do I have to apply the patch http://people.canonical.com/~mlankhorst/xorg-server_1.14.1-0ubuntu0.2.diff.gz?
[12:22] <tkamppeter> mlankhorst, in which directory/branch/repo do I have to be to run "git checkout ubuntu+1; git merge whot/touch-grab-race-condition-56578-v2; git checkout whot/touch-grab-race-condition-56578-v2 .; git checkout HEAD debian ChangeLog; git commit; dch 'yadda yadda'"
[12:23] <mlankhorst> http://people.canonical.com/~mlankhorst/xorg-server_1.14.1-0ubuntu0.2.diff.gz
[12:24] <mlankhorst> repost, but grab that, apply that to 1.14.1, fixup inputproto, done..
[12:24] <mlankhorst> it was the result of me doing pretty much that
[12:31] <mvo> seb128: sorry, meeting again, I look at why its untranslated
[12:31] <seb128> mvo, thansk
[12:31] <mvo> seb128: as for the history-its only kept for ~6 month iirc via logrotate :/
[12:32] <mvo> seb128: one more question, is it normal that I don't have virtual desktops anymore after the raring upgrade?
[12:32] <seb128> mvo, no
[12:32] <mvo> seb128: I "fixed" it via the unity tweak tool
[12:32] <seb128> mvo, it's normal for new installs, not upgrades
[12:32] <mvo> seb128: oh
[12:32]  * ogra_ had the same
[12:32] <seb128> mvo, oh, if you never changed your settings and were on the 2x2 default it might be normal
[12:32] <seb128> ogra_, ^
[12:32] <ogra_> yeah
[12:33] <ogra_> i thought so
[12:33] <seb128> we don't overwrite user settings
[12:33] <mvo> seb128: yeah, never changed my setting
[12:33] <ogra_> well, you do ... for the ones i never changed :P
[12:33] <seb128> but if you didn't set a specific value and were using the default you get the new default
[12:33] <mvo> seb128: 2x2 is fine for me
[12:33] <seb128> right
[12:33] <seb128> mvo, you can enable them back from system settings, appearance
[12:33] <mvo> its ok, I don't mind (too) much, it was just unexpected, maybe worth noting in the upgrade notes or something
[12:34] <ogra_> i wonder if we can actually keep that habit in the converged world
[12:34] <mvo> seb128: aha, indeed, under "behavior", i overlooked this earlier
[12:34] <ogra_> might be that we need to start transitioning user settings on upgrades of phones
[12:34] <ogra_> (sounds like a good bar topic at the sprint :) )
[12:35] <seb128> ogra_, yeah, buy some drinks and we can discuss it ;-)
[12:35] <ogra_> :)
[12:35] <ogra_> will do
[12:35] <seb128> ogra_, as an user there are some settings I would not be happy to have to reconfigure after every upgrade
[12:35] <seb128> the number of workspaces being one :p
[12:35] <seb128> keybindings being another one
[12:35] <ogra_> well, but what if i was happy with the default and didnt change it
[12:36] <ogra_> it is confusing that it suddenly changes
[12:36] <seb128> right
[12:36] <seb128> our golden rule by then was to never mess with user settings :p
[12:37] <ogra_> right
[12:38] <pitti> Laney: ah, thanks for https://blueprints.launchpad.net/ubuntu/+spec/suspend-hibernate-upower-logind
[12:38] <pitti> Laney: count me in with helping out, but I propose to stage this after the logind transition
[12:38] <pitti> (during which a good chunk of the upower rdeps will already be handled)
[12:39] <seb128> that might be another topic for next week
[12:39] <ogra_> did we plan to have another cobvergence power meeting too ?
[12:39] <ogra_> *con
[12:39] <pitti> I didn't hear about one
[12:39] <ogra_> seems related
[12:40] <pitti> but this was certainly discussed there, yes
[12:40] <ogra_> well, we probably should
[12:40] <pitti> to reduce the number of plumbing daemons
[12:40] <ogra_> yeah
[12:51] <pstolowski> mvo: ping
[13:11] <attente> Sweetshark, comment #16 seems to say upgrading to gnome 3.8 fixes it
[13:15] <Sweetshark> attente: whops, indeed. so the bug does not reproduce in quantal, but it does in plain raring, but is gone again with gnome 3.8?
[13:15] <Sweetshark> attente: does that give you any clue?
[13:16] <attente> Sweetshark, not really, i'll purge the desktop ppa to see if that reproduces
[13:21] <attente> ok, i see it now
[13:37] <Laney> pitti: yeah, they don't need to be entangled
[13:38] <Laney> doesn't remove a daemon though, of course
[13:40] <rickspencer3> hey seb128, Laney what's the word on the street regarding the release tomorrow?
[13:44] <tkamppeter> mlankhorst, I have built xserver 1.14 now, but it seems not to be compatible with lightdm, "sudo restart lightdm" says "lightdm start/running, process XXX" but the screen stays black.
[13:47] <gema> rickspencer3: it sounds to me like it's going well
[13:47] <rickspencer3> hi gema
[13:47] <gema> hello
[13:47] <Laney> hey rickspencer3, I'm not too connected with the street myself but it should go down well
[13:47] <Laney> http://iso.qa.ubuntu.com/qatracker/milestones/269/builds isn't too bad
[13:47] <gema> it's quite good
[13:48] <mlankhorst> tkamppeter: probably some abi incompatibility, just dig through your xorg log
[13:48] <tkamppeter> mlankhorst, I have run "startx" on a console of the machine and there I get the error "(EE) module ABI major version (13) doesn't match the server's version (14)". Does this mean that the whole distro needs to be rebuilt for the new X ABI generation?
[13:48] <Laney> didrocks is quite in touch with the french forum so he might know what those guys are thinking
[13:49] <seb128> rickspencer3, hey, release seems to be mostly fine/on track
[13:49] <rickspencer3> hi seb128
[13:49] <rickspencer3> good news
[13:50] <rickspencer3> seb128, I replaced 12.04 on my newer laptop yesterday
[13:50] <rickspencer3> I did a full reinstall
[13:50] <rickspencer3> I had been running 13.04 on my slow desktop and netbook
[13:50] <rickspencer3> on this computer, it flies
[13:50] <rickspencer3> it's fine on my slow 'puters, but on this one ... wow
[13:51] <mlankhorst> tkamppeter: are you using nvidia drivers?
[13:51] <Laney> Getting an SSD was the best single upgrade I've ever done
[13:51] <Trevinho> rickspencer3: great to read!
[13:51] <ogra_> ++
[13:51] <Laney> unity is zippy as anything on it
[13:51] <Trevinho> rickspencer3: about bug 1087534
[13:51] <ubot2> Launchpad bug 1087534 in unity (Ubuntu Raring) "[regression] Corrupted blurred overlays" [Critical,In progress] https://launchpad.net/bugs/1087534
[13:52] <Trevinho> rickspencer3: could you take with you your affected notebook in Oakland?
[13:52] <rickspencer3> Trevinho, absolutely
[13:52] <rickspencer3> in fact, it will be my only 'puter :)
[13:52] <rickspencer3> I like to travel light
[13:52] <rickspencer3> keeps us honest
[13:52] <Trevinho> rickspencer3: oh... and we need to break it :D
[13:52] <tkamppeter> mlankhorst, no, my system has an i7 with on-chip Intel GPU.
[13:53] <rickspencer3> Trevinho, well, maybe we can break it with a USB key
[13:53] <rickspencer3> :)
[13:53] <rickspencer3> (as in make a USB key to boot it for testing)
[13:53] <seb128> Trevinho, rickspencer3: I'm upgrading my 10v to raring, if that has the issue I will bring it as a test box
[13:53] <Trevinho> rickspencer3: yeah, what we need is to bisect nux to find at which revision this problem started...
[13:53] <tjaalton> tkamppeter: install drivers from ppa:canonical-x/x-staging
[13:53] <tjaalton> tkamppeter: and unity
[13:54] <Trevinho> rickspencer3: and afaik that's the only netbook affected in the team
[13:54] <rickspencer3> Trevinho, ack
[13:54] <Trevinho> great
[14:02] <tkamppeter> tjaalton, mlankhorst, which drivers do I need? I have loaded now intel for the GPU, kbd for the keyboard, mouse for the external mouse and synaptics for the laptop touchpad. Which one do I need for the multitouch screen and which additional ones do I need?
[14:02] <mlankhorst> you just evdev, synaptics, and intel
[14:04] <mlankhorst> mouse and kbd are unneeded
[14:05] <tjaalton> unused even
[14:05] <tkamppeter> mlankhorst, yes, these three drivers make the UI of lightdm working again.
[14:05] <tjaalton> you also need unity from the ppa, or it won't load
[14:06] <tkamppeter> mlankhorst, lightdm UI, internal mouse, external mouse, real keyboard, onboard, and touch work.
[14:07] <tkamppeter> mlankhorst, tjaalton, now I will install unity and afterwards I will log in.
[14:19] <tkamppeter> mlankhorst, tjaalton, I have installed unity, libunity-core-6.0-5, unity-common, and unity-services from the PPA, restarted lightdm again, and logged in, now I get only the background image, no launcher and no top bar. After a minute or so I got a crash report from compiz. Clicking OK on it lets the crash report (without decorations) disappear and nothing happens.
[14:19] <mlankhorst> .. how much do you have installed with --force all?
[14:20] <tkamppeter> mlankhorst, tjaalton, also no right-button menu when clicking the right button of the internal or external mouse. Mouse pointer is there and can be moved by internal and external mouse and by touch.
[14:21] <tkamppeter> mlankhorst, no --force used at all. All PPA packages and all X packages built by me installed seamlessly.
[14:23] <mlankhorst> well just updating to the ppa should just work
[14:23] <mlankhorst> apart from the xserver which would require a manual rebuild, but that's about
[14:23] <mlankhorst> it*
[14:24] <tkamppeter> mlankhorst, tjaalton, I did not install any Unity packages with 2d in their names and I did not install unity-autopilot, as I did not have installed tyhese packages before, nor I installed any -dev or -dbg packages.
[14:25] <mlankhorst> tkamppeter: I mean why wouldn't just enabling that ppa work?
[14:25] <mlankhorst> try it, then dist-upgrade
[14:31] <mlankhorst> when we say enable that ppa it's because at least of 3 of the problems you've hit until now would have not happened had you simply installed that ppa before trying to build first (inputproto fix, libs required for unity, manual unity installation, abi versions of drivers)
[14:38] <tkamppeter> mlankhorst, I tried the minimum-invasive approach, by installing a number of packages as small as possible.
[14:39] <ChrisTownsend> mterry: Hi
[14:39] <tkamppeter> mlankhorst, so I upgrade to the PPA now, check whether trhe system works with it and then I uupdate the xserver package to the GIT branch.
[14:41] <mlankhorst> tkamppeter: well in this case it was better to just install the ppa, fwiw you were lakcing libxi/libxfixes from there
[14:47] <tkamppeter> mlankhorst, a simply update to the PPA makes X and Unity working again, now all based on 1.14.
[14:48] <mlankhorst> yeah, the xserver debs you created should still work though
[14:48] <mlankhorst> input/video abi wasn't bumped for that git tree
[14:49] <mlankhorst> install xserver-common, xserver-xorg-core core-dbg and -dev
[14:52] <balloons> mhall119, there's a terminal app now for ubuntu touch?!
[14:52] <balloons> I'm sold.. pls I wantz now
[14:53] <mhall119> balloons: yeah, should be in the PPA soon
[14:54] <mhall119> it's rough, but still so nice to have
[14:54] <mterry> ChrisTownsend, hello
[14:55] <ChrisTownsend> mterry: Hey!  Who is responsible for merging https://code.launchpad.net/~townsend/duplicity/fix-1161599/+merge/159849 ?  I think this would quite a few users who back up to U1 and would be a great SRU candidate.
[14:57] <mterry> ChrisTownsend, one of the duplicity developers, including the guy who approved you.  He must have just forgot
[14:57] <mterry> ChrisTownsend, but I can merge it for you
[14:57] <ChrisTownsend> mterry: Ah, ok.  Thanks!
[14:59] <tkamppeter> mlankhorst, I have now installed xserver-common and xserver-xorg-core of my build before updating to the PPA but not the -dev and -dbg as I did not have installed this before.
[14:59] <mlankhorst> ok that should be good enough then
[15:00] <tkamppeter> mlankhorst, After that I have restarted lightdm and logged in. I can navigate by touch without problem after many (~20) left clicks no stuck button.
[15:01] <tkamppeter> mlankhorst, I tried also the onboard-based right click which leads to immediately getting stuck, It still does not work, but at least I do not get a stuck left button.
[15:02] <tkamppeter> mlankhorst, I start onboard, then Firefox, in Firefox I visit an arbitrary site and click the URL bar to pop up onboard.
[15:02] <mlankhorst> tkamppeter: touch screen right?
[15:02] <tkamppeter> mlankhorst, all touch, "click" is tapping with the finger onto the screen.
[15:03] <mlankhorst> sounds about right
[15:03] <tkamppeter> In onboard I click the button with the mouse pointer pointing to the upper right so that this button gets light grey.
[15:03] <tkamppeter> mlankhorst, then I click somewhere onto the web page, where there is no link.
[15:04] <tkamppeter> mlankhorst, I expect a menu popping up, what I get is no reaction, but at least I do not get a stuck left button.
[15:05] <mlankhorst> on my nexus 7 i managed to get it stuck in a single click :p
[15:05] <tkamppeter> mlankhorst, if I do the onboard-based right click on a link, the link gets followed instead of a menu popping up, meaning that the right-click facility is ignored and the tap is interpreted as left click.
[15:06] <mlankhorst> is that new?
[15:08] <tkamppeter> mlankhorst, this is the first time trying 1.14 for me. Before I had used 1.13 of Raring with the patches which I mentioned in the bug report. That made the left click reliable and the right click made the butoon getting stuck immediately.
[15:09] <tkamppeter> mlankhorst, right click with the internal or external mouse works.
[15:11] <tkamppeter> mlankhorst, State of the art of 1.14, touch-grab-race-condition-56578-v2 branch from GIT, is that tapping the touch screen does not lead to a stuck button any more, left click is absolutely reliable and right click via onboard does not work.
[15:22] <tkamppeter> mlankhorst, you mean that on your N7 you get the GIT branch, which says it has the stuck button fixed, stuck with the first click?
[15:25] <mlankhorst> tkamppeter: I'm just more skilled at locking things up ;P
[15:25] <mlankhorst> try hitting the dash icon, then release finger just a little and hit it again
[15:30] <tkamppeter> mlankhorst, I do not get it stuck even quickly rapid-firing on the dash icon.
[15:30] <mlankhorst> mm I didn't really rapid fire, I did have valgrind though :P
[15:35] <tkamppeter> mlankhorst, probably I do not get into that timing issue as I am in "real-live" mode, running the stuff without valgrind.
[15:37] <tkamppeter> mlankhorst, I have downloaded the source package for xorg-server_1.14.1-0ubuntu0.1 from the PPA now and applied your patch xorg-server_1.14.1-0ubuntu0.1, downloaded a few minutes ago. It does not build on my PPAed system, I get http://paste.ubuntu.com/5598641/.
[15:38] <mlankhorst> tkamppeter: ignore, that was my own attempt
[15:38] <mlankhorst> it's identical mostly
[15:38] <tkamppeter> mlankhorst, but how can I deactivate the check then so that it simply builds?
[15:39] <mlankhorst> it's not any different from what you just build yourself
[15:40] <mlankhorst> so please dont
[15:43] <tkamppeter> mlankhorst, OK.
[15:44] <tkamppeter> mlankhorst, so I simply leave it as it is now and update if there are updates on the bug report or on the PPA.
[15:44] <mlankhorst> you can leave a message on the fd.org bug if you want
[15:48] <tkamppeter> mlankhorst, this is whjat I did now, see https://bugs.freedesktop.org/show_bug.cgi?id=56578
[15:48] <ubot2> Freedesktop bug 56578 in Server/Input/Core "race condition with active/passive grabs when opening menus with touch" [Normal,Assigned]
[15:49] <tkamppeter> mlankhorst, thank you very much for the help on upgrading to 1.14. This way I can follow the development now.
[17:04]  * didrocks waves good evening
[17:49] <seb128> attente, hey, did you get anywhere with that libreoffice/appmenu issue?
[17:53] <attente> seb128, still looking into it
[17:54] <seb128> attente, it's larsu's fault
[17:54] <seb128> attente, it's due to https://code.launchpad.net/~larsu/unity/panel-service-menu-style-fix-again/+merge/151329
[17:55] <seb128> attente, at least I think (just tried with the binary from before that commit was merged, and it doesn't have the bug)
[17:55] <seb128> attente, I hope that helps you as a pointer ;-)
[17:56] <attente> seb128, that looks very helpful, thanks!
[17:56] <seb128> attente, yw
[18:24] <larsu> seb128: the code I removed there was a workaround anyway... what's the bug attente is trying to fix?
[18:34] <attente> larsu, it's to do with the highlighting of the menu items in libreoffice
[18:35] <larsu> attente: interesting. My patch fixed exactly that problem for the indicators...
[18:35] <larsu> attente: so if you find a solution, please test whether it doesn
[18:35] <larsu> ... doesn't break indicators
[18:50] <seb128> larsu, hey
[18:51] <seb128> larsu, your patch broke gtk 3.6/libreoffice to fix gtk 3
[18:51] <seb128> .8
[18:51] <seb128> larsu, since we didn't land the new gtk in raring we have broken menus for libreoffice
[18:52] <larsu> seb128: ugh :-(
[18:53] <seb128> larsu, I'm suggesting we revert in the raring unity branch and keep it in trunk
[18:53] <larsu> seb128: sounds good to me
[18:53] <seb128> we will land gtk 3.8 next cycle for pretty sure (the only blocker I know about is overlay scrollbars working only once)
[19:02] <GunnarHj> Will next release be 13.10? I have never seen any conclusion from the discussions on rolling releases etc.
[19:04] <GunnarHj> seb128: ^
[19:07] <seb128> GunnarHj, yes
[19:07] <seb128> GunnarHj, conclusions are on https://lists.ubuntu.com/archives/technical-board/2013-March/001566.html
[19:08] <GunnarHj> seb128: Thanks, Seb. Guess that should be annonced somewhere, or...?
[19:11] <seb128> GunnarHj, that's a good point
[19:11] <seb128> stgraber, ^
[19:13] <stgraber> seb128: that e-mail was sent at the request of the news team, so I'm pretty sure the announce was forwarded to the fridge, weekly news, ... the usual places. The minutes of the TB meeting were sent to ubuntu-devel-announce and we made the needed changes on the wiki (support duration) and I believe the 13.04 announcement will clearly say it's supported only for 9 months.
[19:14] <seb128> GunnarHj, ^
[19:14] <seb128> stgraber, sorry, I read the infos a few times on a few places but didn't pay attention of what the places were
[19:14] <seb128> stgraber, but it seems it was properly communicated
[19:14] <seb128> stgraber, so, unping
[19:14] <seb128> ;-)
[19:15] <stgraber> seb128: well, the problem is that various websites picked up the discussion on ubuntu-devel as being an announcement which it clearly wasn't. From the TB perspective it feels a bit weird making a lot of noise saying "we changed nothing" :)
[19:15] <GunnarHj> stgraber: Thanks for calling my attention to the fridge. ;-)
[19:17] <sarnold> (though you did change something, the support lifetime, from 18 to 9 months..)
[19:18] <seb128> seems like the security team care somewhat...
[19:18] <seb128> ;-)
[19:18] <stgraber> sarnold: true and I fully expect that change to be made pretty clear in the announcement
[19:18] <sarnold> seb128: i'll be happier to retire hardy .. :)
[19:18] <stgraber> *release announcement
[19:18] <seb128> waouh, hardy, brings back memory
[19:19] <sarnold> Yes. :) It was good for its time, but a lot of the packaging feels .. like there are special cases for no particularly good reason. Things have improved quite a lot in newer releases. :)
[23:49] <AndChat690900> Ma oe :)


[09:41] <YoY> Hello all, i have an aspire one d255e with intel atom 1.66ghz , 2 gb of ram ... i saw on the internet that 32bit are no longer supported, what happens if i install the last 32bit version ? thanks in advance.
[09:42] <YoY> and what are the alternatives please.
[09:55] <LimeOn> Hello YoY, consider it as installing windows xp and surfing the net
[09:56] <erichvk> I have a few intel atom netbooks running 64 bit lubuntu
[09:56] <LimeOn> its insecure
[09:56] <LimeOn> if you have x64 processor, install x64
[09:56] <erichvk> if it boots the 64 bit lubuntu installier on USB, you should be fine to install
[09:56] <LimeOn> if not, i could suggest debian 32 bits
[09:57] <YoY> debian 32 ...
[09:57] <YoY> is it installed manually or the easy way ?
[09:58] <erichvk> I have been using lubuntu on the netbooks for many years, as lxde is pretty good on the low end hardware, and lxqt is not bad either
[09:58] <LimeOn> YoY: it has an installer too
[09:58] <LimeOn> from what i heard and remember, it uses the same setup, calamares
[09:58] <YoY> installer , community ..etc ?
[09:58] <LimeOn> which is very intuitive
[09:59] <YoY> i will install lxqt on it
[09:59] <LimeOn> That is my suggestion ::) YoY
[10:00] <YoY> thank you LimeOn for your suggestions now it is clear :)
[10:01] <LimeOn> Your welcome, good luck ^^
[12:34]  * guiverc whispers to YoY, fyi:  Debian offers two installers, the *live* ISOs use calamares, and the traditional installer uses di (debian-installer); you pick which you use at download time


[08:28] <glitchd> anyone know what the deal with xubuntu-desktop and not saving desktop icon locations is?
[09:11] <glitchd> is there a workaround for getting the desktop icons to save their positions between reboots?
[09:46] <ottoshmidt> Hi, is it just me or log out/shutdown/restart buttons don't work?
[10:02] <knome> probably just you