/srv/irclogs.ubuntu.com/2013/08/26/#ubuntu-devel.txt

TheMuso/c/c00:03
RAOFIs there some particular reason that armhf annoyingly languishes on ports.ubuntu.com, making it really annoying to have as a dpkg foreign architecture?01:34
stgraberI believe not enough space on the archive mirrors (not those from IS, those in universities, ISPs, ...) was the usual response to that question.01:35
stgraberbasically adding armhf there would make us loose a potentially significant number of our current mirrors01:36
RAOFAh, of course.01:37
RAOFI don't suppose they support any "don't mirror this, kthxbye" metadata? That would be too convenient.01:37
StevenKRAOF: Which is difficult, due to pool/01:38
stgraberRAOF: they'd need to run something like debmirror to achieve that, which they usually don't (most mirrors are simply straight rsync from archive.u.c)01:39
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== [ESphynx] is now known as ESphynx
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== shang_ is now known as shang
infinityRAOF: It's a traffic/space tradeoff.  If and when armhf represents a significant portion of our traffic, we'd consider bloating mirrors and moving it.03:47
infinityRAOF: Agreed on the awkward apt foreign arch setup, though, we could perhaps do something to make that less irritating.03:48
infinityRAOF: (ie: if x86 mirror is *.ubuntu.com, use ports for !x86 automagically)03:49
RAOFOr support [arch=!armhf] in sources.list03:52
RAOFHm. Or have an option requiring an explicit opt-in for non-native archs.03:53
pittiGood morning04:43
pittislangasek: I tried upgrading without the transitional package (I didn't have that at first); the upgrade worked in some cases (my test in a chroot), but in others (me on work station and seb128) apt just held back stuff04:44
slangasekpitti: well, but the transitional package appears to be incorrect, it doesn't implement the interface... so any third-party packages will be broken04:45
pittihm, if we can do something about /usr/lib/x86_64-linux-gnu/libgphoto2/print-camera-list it should actually be possible to make them co-installable04:47
pittibut libgphoto2-portX aren't co-installable04:47
pittior wait, unless the /usr/lib/x86_64-linux-gnu/libgphoto2_port/0.10.0 is different in the older version04:48
pittislangasek: fix uploaded05:12
StevenKpitti: Have you heard anything about calibre SEGVing on startup on current saucy?05:13
pittiStevenK: not yet, but it seems I can reproduce05:13
pittiI guess there's a new sip ABI once again05:13
pittiStevenK: it'll need a rebuild, but I'll package 1.0 while I'm at it05:14
StevenKpitti: Sounds excellent, thanks.05:14
=== dayangkun is now known as dayangkun_715
dholbachgood morning07:05
mlankhorstg'day07:06
dholbachhi mlankhorst07:07
mlankhorstheya07:07
=== smb` is now known as smb
dholbachsalut lool - ça va?07:23
dholbachlool, did you file the bug on click regarding permissions?07:23
=== iahmad is now known as iahmad|lunch
hyperairany archive admins around? messagingmenu-sharp is waiting for an ack. :)08:42
hyperair(for several months now)08:42
seb128hyperair, hey, didn't infinity said he would do it on friday?08:42
hyperairyeah, but i forgot to ping him08:43
hyperairi think i pinged yesterday or the day before, but didn't get a response08:43
seb128that was w.e08:43
seb128jibel, hey, welcome back, did you have good holidays?08:59
jibelSalut seb128 , holidays were great, thanks09:00
seb128jibel, nice!09:00
seb128jibel, so, since you are back ... not sure anyone pinged you about that, but autopkgtest/britney seems unhappy for a week (and nobody was able to debug it with you and Colin not there)09:01
seb128jibel, tests stay in RUNNING state09:01
seb128eg http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html has cups -> chromium-browser RUNNING09:01
seb128or dh-python -> dh-python RUNNING09:01
seb128jibel, could you help there? ;-)09:02
jibelseb128, yes, pitti told me, I'm looking at this this morning09:03
seb128jibel, thanks09:04
seb128xnox, hey, did you see that your ardour uploads failed to build?09:17
Noskcajdoko, Do you mind if i merge the latest debian revisions of python2.7 and 3.2?09:19
Noskcajoops, 3.309:19
Noskcajdoko, or more accurately, sync them, as i can't find a reason to keep the delta09:42
siretartinfinity: how do you think about doing the libav9 transition for saucy? I've noticed micahg and jbicha chatting about that yesterday in #ubuntu-motu09:57
ari-tczewNoskcaj: don't you use requestsync script for syncs?10:03
smartboyhwari-tczew, I think Noskcaj's requestsync keep crashing10:06
smartboyhwThat's what I heard from him10:06
ari-tczewsmartboyhw: ok10:06
looldholbach: salut ! sorry, missed your ping; I doubt there is a permission issue with click, at least I couldn't reproduce it; I had other minor permission issues (due to adb shell's umask) which I reported, but the main being issue is packagekit crashing on installation10:08
dholbachok10:09
looldholbach: I started gdb-ing this a bit on friday, but was lacking -dbgsym for packagekit; resuming today I've seen there's packagekit-dbg which might be enough10:09
loolthe packagekit log dies with some warnings on percent count decreasing10:09
loolbut nothing interesting there10:09
infinitysiretart: I'd love to slide it in before feature freeze.  It'll be tight timing to get us to finish the transition, but I'd rather have it done and out of the way before we open 14.04 than agonize over whether or not we do it in an LTS cycle.10:14
infinitysiretart: I'm heading to bed right now (It's 4am), but if you want to start without me, you have my blessing, or we can discuss it when I wake up. :P10:14
jibelseb128, incorrect RUNNING state is fixed, I'm now trying to understand the cause.10:16
seb128jibel, thanks!10:17
pittijibel: was it due to per-arch tests arriving at differnt times?10:17
jibelpitti, I do not know yet, I'll tell you when I'm sure.10:18
pittiStevenK: ah, calibre 1.0.0 finally got imported, synced10:31
StevenKpitti: Nice, thanks!10:34
=== Sweetsha1k is now known as Sweetshark
dholbachmitya57, 1180067 uploaded11:25
dholbachmitya57, the test build took a while ;-)11:25
mitya57dholbach: BIG thanks!11:39
dholbachmitya57, no worries11:40
pittihm, what's the easiest way to find out why signond-dev isn't installable on powerpc?11:47
pitti(https://launchpadlibrarian.net/148449058/buildlog_ubuntu-saucy-powerpc.shotwell_0.14.1-3ubuntu3_FAILEDTOBUILD.txt.gz)11:47
pittiit's not on http://people.canonical.com/~ubuntu-archive/testing/saucy-proposed_probs.html11:48
pittibut perhaps related to these qt depwaits11:48
pittihm, how did https://launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+changelog get into saucy in the first place? it didn't build on powerpc (depwait), thus it shouldn't have migrated?11:49
pittiah, https://launchpad.net/ubuntu/+source/qtjsbackend-opensource-src/5.0.2-3 isn't supported on ppc -- so how did that stack propagate, was it forced?11:51
seb128pitti, yes, it was, and signon was deleted on ppc11:55
seb128pitti, that stack can't exist on ppc, qtdeclarative uses v8 that's not available on ppc11:56
seb128pitti, we had to do some forcing since some of those sources existed before (qt4 was available on ppc)11:56
pittiseb128: but libsignon-glib-dev still exists on ppc and is now uninstallable11:57
seb128pitti, drop ppc?11:57
pittiseb128: it sounds wrong to drop shotwell on ppc, it doesn't use any of this?11:57
pittinot that I care about ppc in any way, but changing all transitive reverse deps of that to drop ppc sounds very intrusive11:58
seb128pitti, reality is that modern desktop don't run on ppc11:58
seb128pitti, well, we patch shotwell to use ubuntu-online-accounts, which create that depends11:59
pittiseb128: i. e. libsignon-glib binaries shoudl be dropped from ppc, and shotwell not built against it on ppc?11:59
pittiah11:59
seb128pitti, we should probably stop doing that11:59
pittiseb128: i. e. we somehow need to apply debian/patches/06_uoa.patch on !powerpc only?12:00
seb128pitti, right12:01
pittipain12:01
seb128pitti, but that's the tip of the mountain I think12:01
pittiI guess I'd rather drop ppc from shotwell's arch:12:01
seb128pitti, you are going to have similar issues in lot of desktopish components12:02
seb128pitti, yeah, that might be easier12:02
seb128pitti, and to reply to your britney comment, britney prevent increasing the number of issues, it doesn't enforce it to be 012:02
seb128pitti, e.g if a package never existed in an arch it's fine for it to migrate without that arch12:03
pittiah, so if I remove shotwell ppc from saucy and reupload with arch: i386 amd64 armhf, it ought to work?12:03
seb128pitti, which is the case of qt5 and its rdepends12:03
pittiah, I don't even need to touch the arch: field then12:03
pittiif that should ever get fixed, it'll just build again on ppc12:03
seb128pitti, right, just deleting the binary should be enough (unless something depends on shotwell)12:03
seb128pitti, correct, that's the best way (and why we keep other packages depwaiting on ppc)12:04
pittiquite some meta packages do12:04
seb128they depends or recommends?12:04
pittiah, recommends12:04
seb128well, let's try deleting the binary on ppc and see what britney says12:04
pittidone12:05
pittiseb128: thanks for the explanation12:05
seb128pitti, yw!12:05
ari-tczewdo we need to keep patches to fix DSO linking (in my case, patch from natty) in saucy?12:20
geserif it's still needed then yes12:21
pittiari-tczew: just try p/sbuilding it without; you'll see if it still fails12:27
ari-tczewpitti: without that one builds fine, just asking to make sure12:27
ari-tczewbut it's odd described in d/changelog: Resolve unresolved symbols in shared library.12:28
pittiari-tczew: these kinds of patches usually fixed build failures like "link failure: unresolved symbol blabla"12:29
pittiari-tczew: so it looks like you can drop it12:29
ari-tczewthanks pitti!12:29
tvoss__pitti, ping12:34
pittitvoss__: I just spoke 5 mins ago :)12:35
pittitvoss__: hey, wie gehts?12:35
ari-tczewtjaalton: you have dropped a part of changes in merge libxvmc, but there is no info about that in d/changelog. could you explain me why these changes have been dropped?12:49
ari-tczew(http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/libxvmc/saucy/revision/16)12:50
tjaaltonari-tczew: what changes?12:56
=== psivaa is now known as psivaa-afk
ari-tczewtjaalton: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/libxvmc/saucy/revision/16 that's the merge done by doko13:00
ari-tczewin your merge there are no changes in files d/rules and d/libxvmc1.install anymore13:00
ari-tczewthat's merge done by you http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/libxvmc/saucy/revision/1813:01
=== tkamppeter__ is now known as tkamppeter
ari-tczewtjaalton: i'm going to merge latest libxvmc from Debian and I can re-add the dropped changes, but I'm asking whether there is a reason to drop them or it was a false13:07
pittiseb128: ah, shotwell propagated now, good13:10
seb128pitti, excellent ;-)13:10
pittiit seems britney doesn't wait for a successful autopkgtest, though13:10
seb128pitti, is that how jibel fixed the "waiting for ever"? ;-)13:11
pittino, I think it's always been that (buggy) way13:11
pittiif you introduce a new autopkgtest, then that won't be considered for propagation, only from the second time on13:11
pittilike, if it would only consider tests which already exist in saucy13:12
seb128oh, right13:12
pittiwhich is how all these broken autopgktests make it into saucy in the first place13:12
tjaaltonari-tczew: it was a year ago, no idea13:31
tjaaltonari-tczew: do whatever works, but we'd like to host the diff in git.debian.org13:31
sil2100slangasek: hi! Are you around?13:48
sil2100slangasek: I think we'll have to schedule a meeting for UDS that would discuss the issue of FFe for Ubuntu Touch packages13:50
sil2100slangasek: Didier asked me to make sure it's discussed on UDS anywhere13:50
sil2100slangasek: we can of course attach it to some other meeting, but I guess we need to figure out to which13:51
=== barry` is now known as barry_
=== barry_ is now known as barry
xnoxseb128: yes, i know. I fixed 1 out of 2 problems with it, to make FTBFS more obvious.14:29
ari-tczewtjaalton: you mean forward that change to Debian?14:37
=== freeflying is now known as freeflying_away
slangaseksil2100: I don't understand why we would need a UDS session to talk about an FFe for Ubuntu Touch packages; the FFe bug is already opened?15:01
=== _salem is now known as salem_
sil2100slangasek: because we want people to be aware that not only touch packages will need FFe's - since there are many many components that are shared between desktop and touch15:13
sil2100slangasek: those might need FFe's as well15:13
sil2100slangasek: for instance libunity is used for both, and most probably there will be changes needed for touch in it15:14
sil2100So libunity, as one example, will also need FFe's - and I am to make sure that it will be clear to everyone15:14
spindritfI need some packages that are not available in the official repo, I though I would use a PPA for that -- is this http://developer.ubuntu.com/packaging/html/ up-to-date documentation I should peruse for that?15:17
smartboyhwspindritf, yes15:25
spindritfthanks, smartboyhw15:31
roadmrxnox: hello, sorry to trouble you, could you please have a look at bug 1216853? pxe installs over nfs are broken in 12.04.3 :(15:32
ubottubug 1216853 in casper (Ubuntu) "During PXE booting failed to mount nfs directory" [Undecided,New] https://launchpad.net/bugs/121685315:32
janimoogra_, do you think it would make sense to take $ARCH into account in livecd-rootfs's auto/config and pass it to lb config?15:32
janimoogra_, I am again trying to build i386 touch image equivalents on an amd64 host15:33
ogra_dont we take ARCH into account ?15:33
ogra_i thought BuildLiveCD does15:33
ogra_and calls live-build appropriately15:33
ogra_janimo, you have to do it from a wrapper i guess15:34
janimoogra_, it is looked at in auto/build but apparently not in auto/config15:34
ogra_janimo, i was actually pondering rootstock-ng :) which would be such a wrapper around the live-build calls15:34
janimoogra_, as an alternative to livecd-rootfs?15:34
ogra_no15:35
janimoaren't there too many scripts already?15:35
ogra_as an alternative to BuildLiveCD15:35
ogra_which is the actual master script15:35
janimoand still no one-liner to exactly reproduce all our images15:35
ogra_thats why15:35
ogra_rootstock-ng --seed=ubuntu ...15:35
ogra_something like that would be what i aim for15:36
janimoogra_, the android package in multiverse is the contents of the LXC container packaged as a deb?15:59
ogra_i think thats just the binary blobs15:59
ogra_xnox could help you with more details ... but UK is on a pleasure trip today :)16:01
mterryxnox, will upstart 1.10 be pushed to saucy this week?16:03
slangasekmterry: should be, but today's a bank holiday in the UK16:04
mterryslangasek, gotcha16:05
=== rickspencer3_ is now known as rickspencer3
=== jasoncwarner__ is now known as jasoncwarner
slangasekogra_: https://blueprints.launchpad.net/ubuntu/+spec/foundations-s-phone-usb-shell looks like it may be a duplicate of https://blueprints.launchpad.net/ubuntu/+spec/appdev-1308-app-developer-mode; do you think we need two sessions about this?16:12
ogra_slangasek, we surely dont, i was asked by plenty of people to register this spec though16:13
ogra_so i think we definitely need one16:14
slangasekogra_: ok, marked as superseded16:19
xnoxmterry: it should be. jodh will be merging it and it should hit saucy this week, before thursday.16:19
=== Guest92436 is now known as nitrodex
ogra_slangasek, which one ?16:20
xnoxjanimo: ogra_: the android package ships system.img both as .img and .zip, so yes that's LXC container contents, in a deb.16:20
ogra_slangasek, mhall119 doesnt relly go into technical detail16:20
ogra_xnox, ah, i thought that was in main16:21
janimoxnox, thnanks16:21
slangasekogra_: marked yours as superseded by the other, if more technical details need to be added feel free to take over the blueprint? :)16:21
ogra_nah, i'm fine16:22
slangasekogra_: but if we're agreed that we don't need two separate sessions, let's use the one session to the fullest16:22
xnoxogra_: it's in multiverse with M.I.R. for restricted in progress.16:22
ogra_that at least means i dont have to run the session now :P16:22
ogra_xnox, ah, ok ... now go away from your keyboard ! :)16:22
xnoxogra_: =)16:23
xnoxogra_: i don't want to cook bbq, so i'll just wait here until it's all done =))))16:23
ogra_haha16:23
ogra_enjoy16:23
slangaseksil2100: so I still don't understand how it's useful/relevant to have a UDS session about this; the FFe process is that you file bug reports, say what you need, and discuss with the release team in the bug log16:41
slangaseksil2100: if you already know what FFes you need, just file the bugs and subscribe ubuntu-release16:43
sil2100slangasek: ok then, if you say it's not needed then let's not - just passing down what Didier asked me to do, we'll still have to identify the components that might change in the process16:43
roadmrstgraber: hello, sorry to trouble you, could you please have a look at bug 1216853? pxe installs over nfs are broken in 12.04.3 :(16:44
ubottubug 1216853 in casper (Ubuntu) "During PXE booting failed to mount nfs directory" [Undecided,New] https://launchpad.net/bugs/121685316:44
sarnoldpitti: is the retracer alive and well? e.g 1216923 and 1216924 are both over three hours old without a re-trace yet17:14
seb128sarnold, no, retracers were down, I'm restarting them17:25
sarnoldseb128: thank you :)17:26
bdmurraytjaalton: do you have any plans to fix bug 1159983?17:31
ubottubug 1159983 in sssd (Ubuntu Precise) "[regression-update] Can't change local users password" [Undecided,Triaged] https://launchpad.net/bugs/115998317:31
tjaaltonbdmurray: yes, i'll revert the change17:33
bdmurraytjaalton: okay, thanks17:36
sarnoldpitti: seb 128 has handled the retracer problems, thanks :)18:04
pepper_chicoI have a bounty here guys, a bounty! http://askubuntu.com/q/33548920:01
sorenkees, stgraber, pitti, cjwatson: TB meeting, anyone?20:06
cjwatsonsoren: bank holiday, on vacation, sorry20:12
sorenGuess not.20:13
sorencjwatson: np. Enjoy!20:16
roadmrxnox: thanks for poking the pxe/nfs bug!!20:20
=== cjwatson_ is now known as cjwatson
=== sraue_ is now known as sraue
stgrabersoren: hmm, isn't the TB meeting next week anyway?20:25
robert_ancellmterry, hey20:33
mterryrobert_ancell, hello20:33
robert_ancellmterry, you forgot to put the .conf in tests/Makefile.am in that MP, otherwise ready to land!20:33
robert_ancellnice work btw!20:34
mterryrobbiew, oh shoot, will fix20:34
mterryrobert_ancell, done20:35
mterryrobert_ancell, thanks.  I can prepare the other bits (actually using depthId and naming sessions) once support for nested mir happens, I suppose20:36
robert_ancellmterry, approved - I'll release it into archive in a few days unless you need it earlier20:39
mterryrobert_ancell, no20:40
hallyn_should isc-dhcp-client's Depends not be switched from iproute to iproute2?20:40
sorenstgraber: Totally. My bad.20:41
hallyn_bc as it is, in saucy, if i apt-get install isc-dhcp-client:i386, it fails due to irpoute:i386 not being installed, but that no longer exists - only iproute2 is multiarch20:41
pepper_chicowhoever answered the bounty tks =)20:41
stgraberhallyn_: yeah, we need to move everything to iproute2. I'll have ifupdown down pretty soon (I believe it's part of the merge I'm doing at the moment), I'll take a look at the rest too.20:45
hallyn_stgraber: ok, thanks.20:45
stgraberhallyn_: the list of rdepends on iproute is pretty long and I don't think there's a good reason to carry the delta of moving them all to iproute2, but for the usual ones (isc-dhcp, ifupdown, vlan, ifenslave-2.6,... sure)20:46
hallyn_stgraber: or maybe iproute could just be made per-arch or something (so i can install iproute:i386).  or apt be taught not to care in that case20:49
* hallyn_ is out of his depths20:49
stgraberhallyn_: we could mark it foreign, but doing so wouldn't help with lxc as we'd then get the armhf version of iproute2, which we don't want20:52
hallyn_stgraber: right if isc-dhcp-client actually needs iproute2:arch then it just needs to depend on that.  anyway, since you say you're on it i've closed the bugs.lp.net page and wno't file a bug for it :)20:56
hallyn_thx20:56
infinityYour versioning of your initramfs-tools upload is going to confuse the crap out of me.  Now you've pretty much forced me to merge, so I don't forget. :P20:56
hallyn_success?20:57
robert_ancellmterry, did you just accidentally set https://code.launchpad.net/~mterry/lightdm/greeter-api/+merge/173794 to merged?20:57
robert_ancellit doesn't seem to have merged, but the status changed20:58
mterryrobert_ancell, it got merged because I based the branch you had off of it, but reverted some of the changes that weren't ready20:58
robert_ancellah, confusing :)20:59
mterryyaeh20:59
slangasekstgraber: why would you get the armhf version of iproute2?21:03
stgraberslangasek: the use case is an armhf container in which we install isc-dhcp-client:<host architecture> which depends on iproute which is a transitional arch:all package depending on iproute221:05
stgraberslangasek: if we make iproute multi-arch:foreign, the existing iproute2:armhf will satisfy the dependency (as it should) and so the container will be stuck with the armhf version21:06
slangasekhmm21:06
stgraberhmm, actually, none of that matters since iproute2 itself is multi-arch:foreign21:07
slangasekI was going to say21:07
stgraberLXC explciitly installs iproute2:amd64 and isc-dhcp-client:amd64, so having iproute foreign would work21:08
stgraberI guess I should do that AND move our core packages to using iproute2, there's no good reason to have those depend on a transitional package21:08
stgraberand maybe spend some time next cycle to see if we can kick the transitional package out entirely (one can hope, the rdepends list is pretty long)21:09
infinitystgraber: We can't kick the transitional package out until 14.10, but we can certainly make things stop depending on it.21:18
stgraberinfinity: right, have it there for upgrades in 14.04 and have it gone for good in 14.10 would be reasonable21:20
=== salem_ is now known as _salem
stgraberhallyn_: uploaded the new ifupdown and updated all the packages I had on my system which were directly depending on iproute. That should be enough to clear the transitional package from most default installs.22:40
hallyn_stgraber: ok, i'll retry building an armhf saucy container tomorrow then (or have all the pkgs already finished building? :)22:41
=== jbicha is now known as Guest27918
stgraberhallyn_: will likely be an hour or so because they're published in the release pocket (build + autopkgtest + ...)22:41
hallyn_ok, thanks22:42
hallyn_now if only my ipxe build would get going  - cmon, lil doggie...  go on...22:43
darkxstxnox, I need to reset some gsettings on the live session that are set by ubiquity-dm, where is the best place to do this? _on_try_ubuntu_clicked?23:02
darkxstbug 120431223:02
ubottubug 1204312 in ubiquity (Ubuntu) "ubuntu GNOME live session background not set correctly" [Medium,New] https://launchpad.net/bugs/120431223:02
xnoxdarkxst: actually ubiquity-dm should be showing the correct background.23:03
xnoxdarkxst: look in ubiquity-dm for list of background, or I should finally stop ubiquity from manually forcing a background url, and instead simply use gsettings (if available on a given flavour)23:04
darkxstxnox, there are two issues, one our background is not listed23:04
xnox... and ubiquity force sets picture-uri which points to non-existing file.23:04
darkxstthe other is that we actually use an animated background so that is an xml file that only gnome-shell can display23:04
darkxstso we would set to a static image in ubiquity, but still need to reset the key23:05
xnoxdarkxst: gnome-shell or gnome-settings-daemon? as far as I know gnome-settings-daemon is the thing that displays the background picture both in ubiquity, unity and gnome.23:06
xnoxdarkxst: or is really gnome-settings-daemon not used anymore to display background under gnome-shell?23:06
darkxstxnox, backgrounds are in mutter23:06
darkxstunity still uses  g-s-d background plugin however23:07
xnoxdarkxst: comment out picutre-options & picture-uri in gesettings_keys list. And try both unity & your session. Everything should just work.23:08
xnoxdarkxst: cause at the moment ubiquity is not settings any colors, so what you see is fallback already.23:09
xnoxarr.. "and try both ubiquity & your gnome-shell session" is what I meant.23:09
=== jbicha_ is now known as jbicha
darkxstoh I guess the animated backgrounds do work there after all23:20
darkxstthere is also the 'num-workspaces' setting which is not ideal23:21
xnoxdarkxst: I guess we could reset the keys to default on exit.23:26
=== freeflying_away is now known as freeflying
darkxstxnox, that seems reasonable23:40
darkxstxnox, btw didnt have any luck getting gnome-shell to run under raring cd. It complains about not being able to find ck session there.23:42
darkxstIt does run on saucy though if I borrow the vt logind session23:42
xnoxdarkxst: how do you "borrow the vt logind session"?23:45
xnoxdarkxst: cause that's really all that is needed to be added to saucy cd to work.23:46
darkxstxnox, I just hardcoded XDG_SESSION_ID23:46
xnoxdarkxst: *cough* is that really all that's needed?! =) excellent.23:47
xnoxLaney: see ^ darkxst - the easy way to integrate logind.... =)23:47
xnoxdarkxst: does it make network-manager indicator work as well?23:47
darkxstxnox, I didn't test that, but will check23:48
darkxstxnox, yes it does23:50
xnoxdarkxst: so what do you hardcode? XDG_SESSION_ID=c2 ?23:51
xnoxor XDG_SESSION_ID=c0 ?23:52
darkxstXDG_SESSION_ID=c123:52
darkxstit seems sessions c1 - c6 always exist23:53
xnoxdarkxst: of-course they do.23:53
darkxstalthough actually network applet always works fine here23:54
darkxstI suppose its wifi that had problems?23:54
xnoxdarkxst: tty1-6 autologin into the default account.23:54
xnoxdarkxst: wifi page within ubiquity & the wifi indicator had troubles.23:54
* xnox actually likes that.23:54
darkxstok I can't actually test that23:54
xnoxdarkxst: but c1 session wouldn't be a tty/graphical session. I wonder if that matters at all.23:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!