[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 :)