[16:53] <yano> fiber internet? where?
[17:29] <dzho> I only know from finding them through a web search but it looks like its centered around Toleda and spreading out from there, roughly speaking?
[17:29] <dzho> Toledo
[19:50] <yano> oh drats
[19:50] <yano> i'm just outside of Columbus
[23:14] <JackFrost> Down through Mansfield and whatnot, seems Shelby already has it.


[00:33] <user|29> el instalador encontro un error al copiar los archivos al disco duro
[06:34] <hydrogranat> Hi. I'd like to ask about the instalation of Kubuntu on Lenovo Yoga Slim 7 ProX laptop. The keyboard doesn't work. Do you have any advices what can be done in order to make it works?
[11:26] <xbesnard> Hello. I am testing kubuntu 24.04 dev. I would like to test also Plasma 6. Is there a backport or a ppa for that? Thanks for the answer. Cheers
[11:30] <RikMills> xbesnard: no. we can't package plasma 6 until Debian decide how they will proceed on it. since we have to match their source repo and package names to enable future import
[11:34] <xbesnard> Thanks for the answer. Just to be patient enough to discover Plasma 6 later in Kubuntu. Is it decided or not for integrating Plasma 6 in Kubuntu 24.04?. Have a nice day.
[11:43] <RikMills> xbesnard: plasma 6 will not be in 24.04 LTS. too new. too much an unknown. too little time. for a LTS that we have to support for 3 yeas
[11:43] <RikMills> hopefully 24.10 will be able to have it
[12:08] <xbesnard> Many thanks for the answer. I can understand the risk of introducing Plasma 6 in a LTS with a tight schedule within Kubuntu 24.04 and a great number of novelties with different level of maturity. Wait and see for further news about Plasma 6 in 2024....
 Hello all, today i wanted to install lxqt de on Kubuntu 22.04 (with plasma 5.27.9 using ppa backports), i don't know why I'm getting dependency problem with "lxqt-config" package with "libkf5screen7" version 4:5.6.2 (I think is a old version) this package is not installable, is anyone having the same problem? And if anyone knows the problem, can you help me?
[14:16] <BluesKaj> Hi all
[17:48] <SVKG8> Hello,I am trying to install a global theme with its aplication launcher,but when I go to widgets,it aint appearing nowhere.
[17:57] <user|4> Kubuntu auf Tablet Samsung SM-T561
[17:58] <user|4> installieren
[17:58] <user|4> ?


[12:35] <Shred00> am i misunderstanding believing that the mythbuntu master PPA at LP is rebuilt on every upstream commit?
[12:44] <Shred00> in any case, it seems it's been almost 36 hours since the last master build:
[12:44] <Shred00> Date: Thu, 15 Dec 2011  1:34:44 UTC
[12:44] <Shred00> is something gummed up?
[14:52] <mrand> Shred00: it is not built upon every upstream commit, but it should typically be built once a day (evening time in the USA) when there has been a new commit that has not been integrated into a build.  It last built 14 hours ago, so it looks like it is running fine.
[14:54] <Shred00> mrand: ahhh.  ok.  looking at http://ppa.launchpad.net/mythbuntu/0.25/ubuntu/dists/natty/Release it says:
[14:54] <Shred00> Date: Thu, 15 Dec 2011  1:34:44 UTC
[14:54] <Zinn> [ppa.launchpad.net] N/A
[14:58] <mrand> Shred00: Hmmm.... ok, I see what you're saying now.  https://launchpad.net/~pegasus+/+ppa-packages shows Lucid updated 14 hours ago, but the others (like Natty) did not update for some reason.  tgm4883?
[14:58] <Zinn> [launchpad.net] PPA packages : Mythbuntu Automated Package Builder
[16:08] <Shred00> tgm4883?
[16:08] <tgm4883> mrand, looks like there is new code to calculate the targets to build for, I didn't know about this code so I'll have to look into it
[16:08] <tgm4883> superm1, ^^
[16:10] <tgm4883> yea there looks to be some issues
[17:27] <Shred00> can the change that was made to calculating the targets be backed out until it's debugged?
[18:06] <tgm4883> Shred00, thats not what the problem is with, it's with something else
[18:06] <tgm4883> I'm looking into it
[18:08] <Shred00> tgm4883: ok.  thanks for the update.
[20:09] <tgm4883> Shred00, not sure what happened, but it seems to be building now
[20:09] <tgm4883> we'll see if it builds again later tonight or if it fails
[20:18] <Shred00> it didn't build the tip of HEAD though, which is the commit was looking for.  :-(
[20:26] <Shred00> why wouldn't it build on a commit that was done 19h ago but rather the commit before that ("1 day ago" according to github)?
[20:28] <tgm4883> Shred00, IDK, I didn't look into it that much. At work :(
[21:33] <Shred00> maybe i was just not patient enough.  the build for the tip seems to be there now.


[15:29] <sarnold> good morning
[15:29] <cpaelzer> o/
[15:30] <cpaelzer> pinging everyone else jamespage didrocks ddstreet doko
[15:30] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[15:30] <meetingology> Meeting started Tue Nov 17 15:30:20 2020 UTC.  The chair is cpaelzer. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:30] <meetingology> Available commands: action commands idea info link nick
[15:30] <cpaelzer> #topic Review of previous action items
[15:30] <ddstreet> o/
[15:30] <cpaelzer> no actions logged
[15:30] <cpaelzer> #topic current component mismatches
[15:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[15:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[15:30] <cpaelzer> let us also take some time here for everyone to see the ping / remember the meeting and show up :-)
[15:31] <cpaelzer> so what is in mismatches for us this week
[15:31] <didrocks> hey :)
[15:31] <cpaelzer> non proposed is clean
[15:31] <doko> o/
[15:31] <cpaelzer> with only known issues and known false positives
[15:31] <cpaelzer> thank jamespage for filing bugs on all the django triggere cases
[15:31] <sarnold> I think it's nothing new
[15:32] <cpaelzer> yeah I'm not identifying anything new on there either
[15:32] <cpaelzer> #topic New MIRs
[15:32] <cpaelzer> I've seen some in my inbox, this might be more today
[15:32] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[15:32] <doko> time to promote postgresql?
[15:32] <doko> -13
[15:32] <cpaelzer> doko: I'm working through the test issues currently
[15:32] <cpaelzer> two autopkgtest issues left and 4 dependencies that don't yet build against -13 right
[15:33] <cpaelzer> doko: I think we can promote it, to see next week if there are any new mismatched
[15:33] <doko> ok
[15:33] <cpaelzer> which would help me to get them tackled soon'ish
[15:33] <cpaelzer> no onto new MIRs
[15:33] <doko> sarnold: can you give a timeline for the discount review?
[15:34] <cpaelzer> holding back new MIRs for sarnold to answer
[15:34] <cpaelzer> jamespage: there are 5 new MIRs we need to handle - jamespage those are all openstack, are you intending to do the reivew on thise filed by Chris.MacNaughton ?
[15:35] <sarnold> doko: last I've heard, the google-osconfig-agent is the higher priority, and I've been handling tasks that were delayed for the previous release lately. I should return to doing MIRs this week, and the googly package gets first go
[15:36] <sarnold> doko: so probably next week (a short week for US holidays) or the week after, I think
[15:36] <doko> ok
[15:36] <cpaelzer> are there volunteers for the cases in https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[15:36] <cpaelzer> I gues it will be ~1 each
[15:37] <jamespage> cpaelzer: yes I can pick those up
[15:37] <cpaelzer> unless james wanted to handle thos himself to keep a short round trip
[15:37] <cpaelzer> ah ok
[15:37] <cpaelzer> jamespage: if you end up going crazy let us know and we can share
[15:37] <jamespage> multiple conversations result in limited effectiveness
[15:37] <cpaelzer> I'll assign them to you now to reflect that
[15:37] <jamespage> but yep I can do those
[15:38] <cpaelzer> assigned
[15:38] <cpaelzer> #topic Incomplete bugs / questions
[15:38] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir
[15:38] <cpaelzer> postgresql is under my control (see the discussion with doko a bit up in the log)
[15:39] <cpaelzer> but it will be with us a while until fully resolved
[15:39] <cpaelzer> no other very recent updates
[15:39] <cpaelzer> doko: anything on the lintian cases we/you need to do ?
[15:39] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/1899213
[15:39] <doko> no, just the security review
[15:40] <cpaelzer> do you have team news on https://bugs.launchpad.net/ubuntu/+source/raspberrypi-userland/+bug/1895137
[15:40] <cpaelzer> waveform: ^^ ?
[15:40] <cpaelzer> since the reivew of -userland there was no update anymore
[15:40] <cpaelzer> I wonder if this effort was aborted or just takes time?
[15:41] <doko> ok, I'll ask
[15:41] <cpaelzer> not super-important - mostyl I'm just curious what we should expect
[15:41] <cpaelzer> #topic Any other business?
[15:41] <cpaelzer> nothing else from the server Team
[15:41] <cpaelzer> anyone ?
[15:42] <didrocks> nothing for me
[15:42] <sarnold> nothing new from me
[15:43] <cpaelzer> ok - MIR status loks good for the week then
[15:43] <cpaelzer> thank you everybody
[15:43] <cpaelzer> #endmeeting
[15:43] <meetingology> Meeting ended Tue Nov 17 15:43:18 2020 UTC.
[15:43] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-11-17-15.30.moin.txt
[15:43] <sarnold> thanks cpaelzer, all :)
[15:43] <ddstreet> thanks all o/
[15:46] <didrocks> thanks :)


[10:54] <ssj6akshat> What should I name my post?
[10:54] <ssj6akshat> 'Ubuntu Cloud Portal is a one stop shop for all cloud enthusiasts'
[10:54] <ssj6akshat> ?
[12:37] <asac> http://twitter.com/asacasa/status/11397904388333568
[12:38] <asac> "would be precious if there was a 10GB official @ubuntucloud EBS AMI available for use with e.g. http://aws.amazon.com/free/ #ec2"
[12:41] <asac> maybe i am missing something and its easy to resize the EBS down form 15 to 10?
[12:41]  * asac the clueless cloudy
[13:08] <asac> ok got answer on twitter.... thx
[20:10] <kiall> So .. is there anything special that needs to be done to get a re-bundled ubuntu instance (on UEC) to boot? .. Every attempt so far has stalled during boot


[05:09] <_mup_> juju/expose-refactor r418 committed by<EMAIL_ADDRESS>[05:09] <_mup_> Verify FirewallManager is started and invoked
[05:11] <_mup_> juju/expose-refactor r419 committed by<EMAIL_ADDRESS>[05:11] <_mup_> PEP8, PyFlakes


[13:50] <smoser> has ayone seen a situation where a MP doesn't get updated correctly ?
[13:50] <smoser> https://code.launchpad.net/~redriver/cloud-init/+git/cloud-init/+merge/314895
[13:51] <smoser> is an MP based on branch at https://git.launchpad.net/~redriver/cloud-init/commit/?h=frbsd-azure-branch&id=f7992aea296be75ce511c6508707bdd6f5a885ee
[13:51] <smoser> but its out of date.
[13:59] <smoser> is there a way to kick that ?
[14:01] <rbasak> So the preview diff is against some old version in the to-be-merged-into branch, rather than the current state?
[14:02] <rbasak> I've seen that before.
[14:03] <rbasak> https://code.launchpad.net/~racb/usd-importer/+git/usd-importer/+merge/316208 is an example
[14:03] <rbasak> It never fixed itself.
[14:03] <rbasak> Time to file a bug perhaps?
[14:05] <cjwatson> there are occasional known outages
[14:06] <cjwatson> due to an fd leak in libgit2 we think
[14:06] <cjwatson> there'll be a way to kick it manually after the next LP deployment
[14:06] <cjwatson> (git_repository.rescan)
[14:06] <cjwatson> no need for a bug report at this time
[14:07] <rbasak> Ah great. Thanks!
[14:07] <rbasak> I've noticed some libgit2 issues in Xenial. nacc tells me it's fixed in more recent releases? Maybe not the same issue though.
[14:08] <cjwatson> probably not the same
[14:08] <cjwatson> we're on a backport anyway
[15:32] <oanson> Hello. I am trying to change the state of bug 1280522 to fix released for Dragonflow. I keep getting timeouts when I try  (Error ID: OOPS-47a844998688e9efa67ad964f42e472f) .
[23:53] <kyrofa> Urgh... the one-hour proxy timeout on the snap builders is killing me


[14:10] <Odd_Bloke> smoser: I'm looking at switching MBR disk setup to use sectors (rather than MB), because sfdisk in wily has dropped support for units other than sectors.
[14:11] <smoser> yes please.
[14:11] <Odd_Bloke> smoser: How would you suggest I test this?  I've done [33, [66, 82]], which is the canonical example we use.
[14:11] <Odd_Bloke> But I don't really know what corner cases we might have that I should look at.
[14:11] <smoser> mainly i think you dont have to care.
[14:11] <smoser> CHS is garbage.
[14:12] <smoser> thats waht you're asking about, right?
[14:12] <smoser> what did '33, 66, 82' mean ?
[14:13] <Odd_Bloke> smoser: No, at the moment we do (essentially) 'cat <list of partitions> | sfdisk -uM <device>'.
[14:13] <Odd_Bloke> smoser: But sfdisk no longer supports megabytes as units, so I'm switching to using sectors as the units.
[14:13] <Odd_Bloke> smoser: This is https://bugs.launchpad.net/cloud-init/+bug/1460715
[14:14] <smoser> ah. ok.
[14:14] <smoser> what did you mean 33, 66, 82 ?
[14:14] <Odd_Bloke> smoser: So I've tested using 'layout: [33, [66, 82]' (i.e. one-third ext4, two-thirds swap), but I don't really know what else to try to check that it works in practice.
[14:19] <smoser> Odd_Bloke, ok. now reading code and understand more.
[14:20] <smoser> well you basically have to turn everything into sectors.
[14:20] <smoser> now, to deal with sfdisk
[14:21] <Odd_Bloke> smoser: Yeah, it's actually surprisingly painless.
[14:21] <Odd_Bloke> smoser: I've got a branch prepped, I'm just trying to test it before pushing it up for review.
[14:21] <smoser> i've never really used that code.
[14:22] <smoser> in the future the plan is to support the disk layout settings taht curtin can do.
[14:22] <Odd_Bloke> smoser: OK, I'll just push this up for review then.
[14:22] <Odd_Bloke> I've done some basic testing.
[14:40] <Odd_Bloke> smoser: That's https://code.launchpad.net/~daniel-thewatkins/cloud-init/lp1460715/+merge/274897
[14:41] <smoser> Odd_Bloke, it'd be good to know if this code runs on old sfdisk
[14:42] <Odd_Bloke> smoser: Ah, good point.
[14:55] <Odd_Bloke> smoser: The existing trusty code doesn't work even without my changes. /o\
[14:56] <Odd_Bloke> Ah, I'm hitting https://bugs.launchpad.net/cloud-init/+bug/1311463.
[14:59] <smoser> Odd_Bloke, added a review
[15:06] <Odd_Bloke> smoser: Thanks!  Replied to the inline comment.
[15:07] <smoser> i've always been confused by sfdisk also
[15:08] <smoser> lets find the real ansewr.
[15:08] <smoser> but i suspect it is 512
[15:09] <Odd_Bloke> smoser: I've been poking around in that code; let me have a dig before you switch to this.
[15:09] <Odd_Bloke> (As in, I've been poking in the sfdisk code)
[15:10] <smoser> reading http://karelzak.blogspot.com/2014/10/new-sfdisk.html
[15:12] <Odd_Bloke> smoser: So my code doesn't backport to trusty nicely, because old 'sfdisk -l' output is different.
[15:13] <smoser> yeah. i'm aware of such pain .
[15:13] <smoser> from growpart
[15:13] <smoser> it does support both. but its a pita
[15:14] <smoser> http://bazaar.launchpad.net/~cloud-utils-dev/cloud-utils/trunk/view/head:/bin/growpart
[15:14] <smoser> Odd_Bloke, the thing is that if we update to only supporting new, then anyone who picks this up is busted on old sfdisk
[15:15] <smoser> in growpart, SFDISK_VERSION madness.
[15:16] <Odd_Bloke> smoser: ;.;
[15:19] <Odd_Bloke> smoser: So libfdisk definitely supports variable sector sizes; I don't know if we'd ever see them in practice.
[15:20] <smoser> but then its not clear to me if it woudl be used anyway.
[15:20] <smoser> logical sector size versus physical sector size
[15:22] <Odd_Bloke> smoser: Right.
[15:22] <Odd_Bloke> smoser: I have a meeting coming up, but I'll pick this up after that.
[16:56] <smoser> Odd_Bloke, so.
[16:56] <smoser> through some experimentation, i can verify that sfdisk uses 512 byte sectors
[16:59] <Odd_Bloke> smoser: You're sure we won't hit funky hardware somewhere where it doesn't?
[16:59] <smoser> i dont think so
[16:59] <smoser> http://paste.ubuntu.com/12863364/
[17:00] <smoser> Odd_Bloke, ^ that boots a guest with 4096 physical size and 512 logical (interestingly, it wont boot if you set logical to 4096).
[17:01] <smoser> verified that the kernel says my physical size is 4096
[17:01] <smoser> and that size reported (in your 'sfdisk --list') is in 512
[17:12] <smoser> Odd_Bloke,  http://paste.ubuntu.com/12863544/
[17:16] <harlowja> smoser https://github.com/openstack/cloud-init
[17:16] <harlowja> guess now cloud-init == openstack
[17:16] <harlowja> lol
[17:17] <harlowja> Odd_Bloke ^  claudiupopa
[17:17] <smoser> oh well. it is. as it is.
[17:17] <harlowja> :-P
[17:17] <natorious> oh wow
[17:17] <natorious> did they merge the stackforge org into openstack?
[17:17] <natorious> I suppose
[17:17] <harlowja> yup
[17:17] <harlowja> stackforge gone...
[17:18] <harlowja> and/or retired
[17:18] <natorious> fwiw, I report cloud-init hours worked as openstack dev hours
[17:18] <harlowja> nice
[17:18] <harlowja> well now u can do that without feeling bad, ha
[17:19] <natorious> lol, no bad feelings here :P
[17:19] <Odd_Bloke> smoser: So looking at the util-linux code; sector size defaults to 512, but it does do an 'ioctl(fd, BLKSSZGET, sector_size)' call to actually query the device (https://git.kernel.org/cgit/utils/util-linux/util-linux.git/tree/lib/blkdev.c#n193).
[17:20] <Odd_Bloke> smoser: But that does mean that a `blockdev --getss $DEVICE` is definitely going to return the same answer, which would save on parsing sfdisk output.
[17:21] <Odd_Bloke> Let me check that makes sense on trusty.
[17:50] <smoser> ok. i'm wrong
[17:50] <smoser> http://paste.ubuntu.com/12864078/
[17:51] <smoser> your'e right about blockdev --getss
[17:51] <smoser> but i think thats the same as woudl be returned by *logical*
[17:52] <smoser> http://paste.ubuntu.com/12864114/
[17:52] <smoser> ^--
[17:53] <smoser> so reading logical in sys shoudl give you what sfdisk does.
[17:53] <smoser> i managed to create a device with 4096 logical
[17:54] <smoser> so ... sfdisk uses logical sectors. not physical sectors.


[12:06] <ulrichard> How difficult is it to bring a javafx app to ubuntu phone? I managed to get it running with docker, but I never created a snap. https://github.com/jpasqua/VisibleTesla/pull/125
[14:11] <mterry> tedg_: I'm seeing some potentially UAL-related oddities.  With u8 now, some apps open and some don't.  Like, calculator opens but clock does not (both with devmode).  No logs that I can see.  But then when I run clock confined with my in-progress unity8 interface (and no unity7 interface), it does run.  So the app itself isn't borked.  I'm guessing that UAL
[14:11] <mterry> is doing something there?  Deciding between u7 and u8 modes and getting something wrong?  (even though the app can do both...)
[14:22] <mterry> tedg_: although... I had to rebuild the apps to test with a smaller interface footprint.  maybe rebuilding them fixed them too.  Like the ubuntu-app-platform qt-mismatch issue...
[14:23] <mterry> So maybe it was simply a rebuild that did it
[14:28] <dobey> mterry: yeah i think it's the rebuild that did it
[14:30] <tedg_> mterry: Seems likely there is a fix for apps that crash in silo 2434 which might help a couple of those cases.
[14:37] <dobey> tedg_: for that fix though, the app at least will run once from a new boot though, right? just fails later after the app had crashed previously in the session?
[14:38] <tedg_> dobey: Correct, so not all of mterry's issue, but it might be part of what's confusing him.
[18:38] <andybleaden> Quit
[20:02] <mterry> ogra_: you were getting some high load on a Pi from unity8-session restarting services a bunch, right?  I've tighted up our respawn limits in the latest snap, let me know if that works better for ya
[20:44] <mterry> tedg_: how are apps finding the right mir socket today?  (It ends up in /run/user/xxx/snap.unity8-session/mir_socket)
[20:46] <tedg_> mterry: We're pushing it into their environment when running. But when they have interface hooks we shouldn't do that. They should get it when connected.
[20:47] <tedg_> mterry: But I have a feeling we're gonna end up pushing it into their environment forever :-/ One of those things that we won't be able to drop.
[20:47] <mterry> tedg_: they want us to use /run/user/xxx/mir_socket (a global location)
[20:47] <mterry> So I can change that easily on u8 side...
[20:47] <mterry> But was curious how the apps got it
[20:47] <tedg_> mterry: That would be fine, then desktop-launch could set it.
[20:48] <mterry> True...
[20:48] <tedg_> mterry: Curious if it should be set per compositor, because you could nest them.
[20:48] <mterry> tedg_: who does the pushing today? UAL?
[20:48] <tedg_> mterry: Yeah, UAL.
[20:48] <mterry> tedg_: well...  I asked about nesting, but haven't gotten an answer back yet -- I suspect they don't care
[20:50] <tedg_> mterry: So, in a nutshell, I'm not sure I care that much. But I'd really rather we didn't provide it as an environment var. I'm most +1 on that, everything else is details :-)
[20:51] <mterry> tedg_: yeah it's hard to get away from doing it forever.  I was just thinking about doing it in desktop-launch instead, then realized that old apps would suddenly break once UAL stopped doing it
[20:51] <tedg_> mterry: We don't have that many old apps, and we've broken them twice in the last two weeks already :-)
[20:52] <mterry> tedg_: yeah -- just I don't like how fragile snaps sometimes seem, when we don't have good boundaries
[20:52] <mterry> Just need to nail down those boundaries
[20:52] <tedg_> And that's where I want to get to. I want to provide nothing that isn't detailed in the snap.yaml.
[20:52] <mterry> tedg_: I'll propose some changes
[20:57] <brunch875> does the ubuntu phone vibrate at some rate?
[20:58] <brunch875> it would be fun to use a ringtone which syncs with it
[20:58] <brunch875> have the phone dance to it :-)
[20:59] <dobey> i'm not sure the speed of vibration is controllable via software
[21:17] <mterry> tedg_: so I'm looking at UAL now -- if we go with a hardcoded path, we don't need any of this socket demangler complexity?  That'd be nice
[21:19] <tedg_> mterry: That's actually for the trusted prompt sessions, and we'd need that. Because it's a custom file handle that's part of the trusted prompts stuff.
[21:19] <tedg_> mterry: But yes, it would solve some complexity problems for us.
[21:20] <mterry> ah k


[05:24] <pwnguin> does anyone know what the hell is going on in bug #188787?
[05:27] <pwnguin> also, where'd the bot go?
[07:34] <tjaalton> pwnguin: didn't look at it closely, but the new package should fix that?
[07:36] <pwnguin> it might
[07:37] <pwnguin> wacom's changelogs are pretty vague and i dont build directly from them
[07:37] <pwnguin> is there a way to get a unified diff from a cvs repo?
[07:40] <pwnguin> reporter says it might not always work, but there's nothing in the upstream bugtracker
[08:20] <tjaalton> pwnguin: use -u
[09:02] <tjaalton> tseliot: what files/dirs were you referring to that nvidia can't ship?
[09:15] <tseliot> tjaalton: there are a few things
[09:15] <tseliot> too many "patches" dirs
[09:16] <tseliot> e.g. we don't need a patches dir in debian.binary
[09:16] <tseliot> we don't need a Makefile
[09:16] <tseliot> or a devfs.devices
[09:18] <tseliot> or nvidia_supported, etc.
[09:18] <tjaalton> you mean we don't have to patch the modules?
[09:19] <tjaalton> ever :)
[09:19] <tjaalton> if they don't break anything, I'd keep them there
[09:19] <tjaalton> to make the diff smaller
[09:19] <tjaalton> haven't looked inside the tarball yet
[09:20] <tseliot> we have a patches folder in debian.binary and 3 patches-related dirs in debian
[09:20] <tseliot> err not in debian
[09:20] <tseliot> in the main directory
[09:21] <tseliot> actually we might want to keep only the one in debian.binary
[09:22] <tseliot> and we'll also have to get rid of nvidia-settings since it's maintained separately
[09:23] <tjaalton> commented out already
[09:23] <tseliot> and I'm not comfortable with having a separate package such as nvidia-glx-ia32
[09:23] <tjaalton> the debian version does not have any debian/patches dir
[09:24] <tjaalton> it's not included in my version
[09:24] <tjaalton> if you looked at the diff
[09:24] <tseliot> I applied the diff. Maybe something went wrong
[09:24] <tjaalton> on top of which?
[09:24] <tjaalton> it's against the debian package
[09:25] <tseliot> the -4 revision of the package in unstable
[09:25] <tjaalton> right
[09:25] <tjaalton> look at debian/control
[09:25] <tseliot> control.in?
[09:25] <tjaalton> both
[09:26] <tseliot> you're right the ia32 package is commented out
[09:27] <tjaalton> patches.save or patches.dpatch.save are not used
[09:27] <tjaalton> the debian maintainer _might_ want to clean it up a bit..
[09:27] <tseliot> did you move such libraries to another dir in nvidia-glx in the debian/rules?
[09:27] <tjaalton> yes
[09:27] <tjaalton> usr/lib32
[09:27] <tseliot> ok, perfect
[09:27] <tjaalton> just open the diff, it's easier to see the changes :)
[09:30] <tseliot> ok, I'll use Kompare to do so
[09:30] <tjaalton> "less" is enough
[09:33] <tseliot> yes, I know but Kompare lets me browse through the files and see the changes, it's nice
[09:34] <tseliot> also we might want to remove the diversions created by both nvidia-glx-new and nvidia-glx-new-envy, etc.
[09:35] <tseliot> s/to remove/try to remove/
[09:36] <tseliot> since the -envy flavour should be a dummy package in Intrepid which will point to our packages (and to Mario's)
[09:36] <tjaalton> those should be removed by the packages itself
[09:36] <tjaalton> in postrm or so
[09:37] <tseliot> I was thinking of dist-upgrades, etc.
[09:37] <tseliot> I want to make sure that we don't break upgrades from Hardy to Intrepid, no matter what
[09:38] <tjaalton> ok so they are not touched on upgrade
[09:38] <tjaalton> currently
[09:40] <tseliot> and we'll have to be very careful about the Conflicts/Replaces in the control file
[09:40] <tseliot> not that I need to remind you of this
[09:40] <tseliot> ;)
[09:42] <tseliot> shall we make an additional package which contains a tarball such as the one which is currently provided by nvidia-kernel-source?
[09:42] <tjaalton> why?
[09:42] <tseliot> I'm asking you since nvidia-kernel-source will only contain the DKMS part
[09:42] <tjaalton> again, why? :)
[09:43] <tseliot> why what?
[09:43] <tjaalton> why can't it have both the source and dkms stuff?
[09:43] <tjaalton> why another package?
[09:44] <tseliot> should we put the same source twice in the same package?
[09:44] <tjaalton> I don't understand..
[09:44] <tseliot> the dkms source contains the content of that tarball + dkms.conf and other stuff
[09:44] <tjaalton> ah ok
[09:45] <tjaalton> that's enough imho
[09:45] <tseliot> and it will be installed to /usr/src
[09:45] <tseliot> ok, agreed
[09:46] <tseliot> do you think that Debian will ever accept our changes to this package?
[09:47] <tjaalton> no idea
[09:49] <tseliot> when the package is ready I would like to put the latest release of the nvidia driver since it removes the need of a hacky patch and improves hardware support
[10:32] <Q-FUNK> hm. seems that bryce's geode 2.9.0-1ubuntu2.1 doesn't work whereas my own package does.
[10:34] <Q-FUNK> this realy should have been done as per the debian 2.9.0-3 package
[10:34] <Q-FUNK> could video-all be updated to pull geode instead of amd?
[10:34] <Q-FUNK> amd really is a transitional package, nowadays
[10:35] <Q-FUNK> including in hardy
[10:36] <jcristau> what's the point? it's not like the transitional package is going away from hardy
[10:40] <Q-FUNK> removing the transitional package also removes -all
[10:41] <jcristau> then don't remove it :)
[10:41] <Q-FUNK> :-P
[10:41] <Q-FUNK> that kinda spoils the concept of transitional package now, doesn't it?
[10:43] <jcristau> maybe, but i don't quite see why that would warrant an update in a released version
[10:43] <jcristau> just my opinion, though
[13:02] <Q-FUNK> ok, it seems that the short answer is:  trying to maintain any sort of backward-compatibility with the old -amd driver makes LTSP fail on Geode hardware.
[13:04] <Q-FUNK> the simplest way to really fix hardy is to make video-all Depends on -geode >= 2.9.0-3 and Conflicts on -amd (any version)
[13:07] <jcristau> uh
[13:07] <jcristau> that sounds wrong
[13:09] <Q-FUNK> how so?
[13:10] <jcristau> how does ltsp fail?
[13:15] <Q-FUNK> jcristau: the reverse-compatibility links between amd_drv.so and geode_drv.so break it
[13:16] <Q-FUNK> ditto if there's a link between amd.ids and geode.ids
[13:17] <jcristau> there should not be an amd.ids
[13:18] <Q-FUNK> why not?
[13:19] <Q-FUNK> creates additional PCI ID conflicts as a result of the symbolic link?
[13:19] <jcristau> pci id conflicts are not an issue
[13:19] <jcristau> the server will just pick the first one it finds
[13:20] <Q-FUNK> why not then?
[13:20] <jcristau> you still haven't replied to my first question though. how does ltsp fail?
[13:20] <jcristau> because it's useless
[13:20] <Q-FUNK> fails to launch X
[13:20] <jcristau> how
[13:20] <jcristau> 'it fails' is somewhat vague...
[13:21] <Q-FUNK> if the symbolic links are there, X won't detect the Geode LX and falls back to console.
[13:21] <jcristau> meh
[13:21] <jcristau> that still doesn't give any detail
[13:21] <Q-FUNK> if the symbolic links are gone, X launches as expected
[13:21] <Q-FUNK> and uses the corrects driver
[13:22] <jcristau> have a log/config?
[13:22] <Q-FUNK> nope
[13:22] <jcristau> then get one
[13:22] <Q-FUNK> good luck on thta one. it all happens in a ramdisk.
[13:22] <jcristau> that's like the first step for any problem with x
[13:23] <Q-FUNK> except that here, simply A/B testing shows thta removing the symbolic links fixes it.
[13:23] <jcristau> you said you were dumped to the console. pretty sure you can get logs from there
[13:23] <Q-FUNK> no need to investigate any further.
[13:24] <Q-FUNK> no
[13:25] <Q-FUNK> LTSP disables console login and doesn't set any password for the squashfs that is used to get LDM
[13:43] <tjaalton> http://www.googlefight.com/index.php?lang=en_GB&word1=TTM&word2=GEM
[13:46] <tseliot> LOL
[13:47] <tjaalton> hmm, http://www.googlefight.com/index.php?lang=en_GB&word1=translation+table+maps&word2=graphics+execution+manager
[20:03] <jcristau> you might want to remove xserver-xorg-video-newport from ubuntu
[20:07] <jcristau> (see debian bug 393709)
[20:09] <tjaalton> x-x-v-all should be changed too
[20:10] <jcristau> right
[20:10] <bryce> I just checked in a change to s/-amd/-geode/ to that
[20:10] <jcristau> i removed the -newport dependency in 1:7.3+11
[21:09] <tormod> which package should ship xmesa.h from mesa? xserver needs it, but it was rejected for instance from mesa-common-dev in a Debian bug report.
[21:53] <bryce> tormod: I don't know...  I'd have guessed mesa
[21:53] <tormod> bryce: yes, but which binary package?
[21:54] <tormod> maybe it should be included in the server itself now
[22:30] <bryce> tormod: libgl1-mesa-dev maybe?
[22:30] <bryce> tormod: hmm mesa-common-dev might be better
[22:37] <tormod> bryce, yes other files from the same source dir ends up there.
[22:43] <bryce> maybe tjaalton or jcristau could have something more useful to advise
[23:08] <tormod> the related bug is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354019
[23:24] <Q-FUNK> howdy
[23:27] <Q-FUNK> http://mentors.debian.net/debian/pool/main/x/xserver-xorg-video-geode/xserver-xorg-video-geode_2.9.0-4.dsc
[23:28] <Q-FUNK> I'm thinking of removing the symbolic links to -amd completely and instead warn people who still have "amd" in their xorg.conf to change it to "geode".
[23:29] <bryce> o_O
[23:30] <Q-FUNK> I know
[23:31] <Q-FUNK> but further testing shows that 2.9.0-ubuntu2.1 doesn't fix it.  the real fix is to remove the symbolic links completely, otherwise LTSP still barfs
[23:32] <Q-FUNK> and it's easy enough to reply to eventual bug reports about standalone host by pointing to a simple Device change from "amd" to "geode" than to keep this in a half-broken state.
[23:33] <Q-FUNK> my first guess with 2.9.0-3 at debian was to move the symbolic links to the transitional -amd package, but this would only work if -video-all is made to no longer depend on -amd and instead depend on -geode
[23:34] <Q-FUNK> then people upgrading from Gutsy would get -geode as a byproduct up upgrading -amd and/or -all, would also get the symbolic links if they run on a standalone host, but since -all doesn't pull -amd anymore, then LTSP would always work
[23:35] <Q-FUNK> and so changing -all to depend only on geode, rather than -amd, and adopting 2.9.0-3 for hardy would be the most reasonable course of action.
[23:36] <Q-FUNK> for debian, the above -4 makes more sens,e since we've never had -amd in the first place.
[23:36] <bryce> I've checked in that change to git this morning
[23:37] <Q-FUNK> but we are too late for the hardy.1 release, right?
[23:37] <bryce> yup
[23:37] <Q-FUNK> :(
[23:38] <Q-FUNK> any way we can push 2.9.0-3 and -all with -geode instead of -amd into proposed for hardy.2 ?
[23:39] <bryce>  dunno
[23:39] <bryce> I guess I'd rather hold off until we know for certain what the fix is
[23:40] <bryce> it seems like there's been too many sru's for this -geode change, each time "this will definitely fix it", but it didn't
[23:41] <bryce> I don't know what the .2 release schedule is, but presumably it's a ways off.  So better to focus on getting this fixed properly in intrepid and validate the solution definitively on all affected hardware, and *then* do an SRU
[23:44] <Q-FUNK> well, changing the dependency in -all had been discussed before. I still don't even known how hardy.0 even shipped with the dependency still on -amd.
[23:45] <Q-FUNK> and keeping the symbolic links in -geode wasn't my idea of a fix either.
[23:46] <Q-FUNK> it rather was pitti's idea to keep all files within the established 2.8.0 packaging's idea.
[23:47] <Q-FUNK> and since 2.8.0 was released with the symbolic links in -geode rather than -amd, he opposed changing that for 2.9.0
[23:49] <bryce> nonetheless, I think we need to get it fixed and validated in intrepid before talking about sru's.
[23:50] <bryce> even if we know changes are needed (like the -all change), it should be easy enough to test in intrepid first.  If it turns out that more is needed, then there seems little point in pushing an incomplete solution to hardy, esp. since 8.04.2 is a ways off anyway.
[23:51] <Q-FUNK> true, that
[23:51] <Q-FUNK> I'm still sad that the -all change didn't go thru


[19:43] <eyicocko> and then the same message
[19:44] <pmcgowan> eyicocko, what does adb devices say
[19:44] <eyicocko> let me see
[19:45] <eyicocko> ubuntu@ubuntu:~$ adb devices List of devices attached
[19:45] <eyicocko> empty
[19:45] <pmcgowan> eyicocko, try simply reinserting the usb cable in the laptop/pc
[19:45] <pmcgowan> then look again
[19:45] <eyicocko> ok
[19:46] <pmcgowan> the phone is booted into android now?
[19:47] <eyicocko> yes
[19:47] <pmcgowan> eyicocko, if adb cant see it sounds like developer mode is not enabled
[19:48] <eyicocko> when i put the developer logo is in the notification bar
[19:48] <eyicocko> USB Debugging connected
[19:48] <pmcgowan> soudns good
[19:48] <pmcgowan> so adb devices should work
[19:48] <eyicocko> i rebooted the cellphone
[19:48] <eyicocko> ubuntu@ubuntu:~$ adb devices List of devices attached  0071aecbcc4ad189	offline
[19:49] <pmcgowan> ah thats good
[19:49] <pmcgowan> although not sure what offline is telling us
[19:50] <eyicocko> i unplugged and plugged
[19:50] <eyicocko> and now says
[19:50] <eyicocko> device
[19:51] <eyicocko> should i try again with the -d mako?
[19:51] <pmcgowan> no offline? then yes try
[19:51] <Saviq> ooh powerd broken on latest image?
[19:52] <popey> Saviq: yes
[19:52] <popey> on 12.2
[19:52] <Saviq> not my fault \o/
[19:52] <Saviq> or is it?...
[19:52] <eyicocko> The device needs to be unlocked for the following to work Flashing system to /home/ubuntu/Downloads/phablet-flash/ubuntu-touch/20130712.2/saucy-preinstalled-system-armel+mako.img < waiting for device >
[19:53] <sergiusens> pmcgowan: eyicocko offline means you need to accept the key from your phone for the adb connection to take place
[19:53] <eyicocko> but my N4 says Lock State - Unlocked
[19:53] <pmcgowan> sergiusens, seems we got by that
[19:53] <sergiusens> Saviq: if you have the latest and greatest phablet-tools you won't notice those anymore
[19:54] <Saviq> sergiusens, the powerd breakage?
[19:54] <pmcgowan> sergiusens, does that message mean its working or not unlocked?
[19:55] <sergiusens> Saviq: yeah, new builds go into a pending link and phablet-tools now pulls from current by default
[19:55] <sergiusens> needs to be manually promoted
[19:55] <Saviq> sergiusens, ah so I wouldn't get 12.2
[19:55] <Saviq> ok, didn't get how that was related :)
[19:56] <sergiusens> Saviq: unless someone promoted it, no
[19:56] <Saviq> sergiusens, yeah, got it
[19:56] <sergiusens> pmcgowan: developer mode and unlocked are different things
[19:56] <pmcgowan> sergiusens, well yes I know
[19:56] <sergiusens> eyicocko: waiting for device may be because you don't have permissions to talk to fastboot, do you have the latest android-tools-fastboot?
[19:56] <pmcgowan> sergiusens, what is The device needs to be unlocked for the following to work  telling us
[19:56] <eyicocko> yes
[19:56] <sergiusens> what does fastboot devices say?
[19:57] <eyicocko> i downloaded today
[19:58] <eyicocko> sergiusens says nothing in terminal
[19:58] <sergiusens> eyicocko: what about 'sudo fastboot devices'
[20:04] <eyicocko> sorry, lost signal in my lap
[20:05] <eyicocko> sergiusens
[20:05] <eyicocko> when i put sudo fastboot devices
[20:06] <eyicocko> says '0071asddsa4as234 fastboot'
[20:07] <sergiusens> eyicocko: that can only mean that your udev rules need to be updated
[20:10] <eyicocko> sergiusens: what do i need to do to update that udev rules?
[20:11] <flo__> hi! I was just wondering, is indicators-client really supposed to depend on indicator-power? it pulls in quite a few packages, like sound-theme-freedesktop, gnome-control-center and nautilus-data. Quite the surprise when apt-get upgrading :)
[20:15] <ph0ne> when i ctrl-x it asks me to save it in a format. what format should i choose?
[20:17] <popey> just press enter
[20:17] <ph0ne> does notting
[20:19] <ph0ne> http://paste.ubuntu.com/5869164/
[20:21] <flo__> ph0ne, are you in ./adb shell => ubuntu_chroot? somehow the enter key in nano doesn't work for me in there, too.
[20:21] <ph0ne>  no
[20:22] <popey> hmm, i had that too
[20:22] <popey> still a problem?
[20:22] <flo__> My phone is not officially supported, but yes, on my phone it's still a problem (and vi has problems too)
[20:23] <flo__> vi outside of the ubuntu chroot works though
[20:23] <flo__> and I guess it's fine when using SSH
[20:28] <bobweaver> popey,  pushing code now
[20:30] <mhall119> flo__: does it not put a \n into the file, or does it just not show it on screen?
[20:31] <bobweaver>  popey  Blazzing  Speeds  0kB/s
[20:31] <flo__> mhall119, sorry, I wasn't clear enough: It's only a problem when trying to save a file. like ctrl+o => "File Name to Write: /etc/apt/sources.list" is shown => enter/return does nothing
[20:31] <flo__> inserting \n works though :)
[20:31] <bobweaver> permissions ?
[20:32] <flo__> -rw-r--r-- 1 root root   and according to "whoami" and then shell # prompt, I'm root. :|
[20:33] <flo__> It's probably just my setup, bad adb version or something. You shouldn't care about it :)
[20:33] <mhall119> sorry, I saw you manually editing your sources.list and my brain halted for a minute
[20:33] <flo__> I thought that ph0ne might have the  same issue, but apparently it's not the same
[20:35] <bobweaver> There you go popey  a brnad spanking new gui for your scripts and it also installs the scripts and well playaround with it.  OH make sure that you re-edit set_pw.sh  I was debuggins when I commented it all out, aka making bash echo "hello Joseph" ;sleep 12 , any how enjoy
[20:35] <bobweaver> https://code.launchpad.net/~josephjamesmills/+junk/phablet-phalsh-wrapper-GUI
[20:36] <bobweaver> There is a INSTALL file in there that tells one how to install it
[20:38]  * mhall119 wishes he understood C++ better
[20:46] <ogra_> sigh, still no sign of powerd ?
[20:47] <ricmm_> ogra_: are you bored? help me test the session manager branch
[20:47] <ricmm_> in a flipped, non Mir image
[20:47] <ogra_> ricmm_, well, i'm waiting for a fix that was committed 16h ago and prevented us from having an image at all today
[20:47] <popey> ogra_: what are we waiting for?
[20:48] <ricmm_> binary bureucracy
[20:48] <ogra_> popey, for  https://code.launchpad.net/~sforshee/powerd/fix-power-button/+merge/174203 to hit the archive, build, go through britney and then the publisher
[20:49] <popey> can we light a fire under anything to accelerate that?
[20:49] <ogra_> ricmm, i actually had planned to end my day 3h ago, that CI shit really steals my life recently
[20:49]  * ogra_ massively pissed and angry
[20:49] <ricmm> I can get you a deb that you can dpkg -i and all will be fine
[20:50] <ricmm> http://people.canonical.com/~ricmm/ubuntu-touch-session_0.58_all.deb
[20:52] <ogra_> ricmm, rebooting
[20:53] <ogra_> ricmm, looks fine
[20:53] <ogra_> everything on screen that should
[20:53] <ricmm> ogra_: awesome, can you initctl list-sessions as phabet
[20:53] <ricmm> and see if you see the relevant upstart session
[20:53] <ricmm> export it as UPSTART_SESSION and then initctl list
[20:57] <ogra_> phablet@ubuntu-phablet:~$ initctl list-sessions
[20:57] <ogra_> initctl: Unable to query session directory
[20:58] <stgraber> ogra_: do you have XDG_RUNTIME_DIR set in the environment?
[20:58] <ogra_> i doubt that
[20:58] <stgraber> ogra_: it needs to point to /run/user/<uid> as that's where upstart will create the pid files by default
[20:59] <stgraber> libpam-systemd usually sets that when the session is first opened
[20:59] <stgraber> IIRC we fallback to the home directory if that's not the case (but I haven't used that in a while)
[20:59] <ogra_> ah
[20:59] <ogra_> yeah, no porper logind support yet
[21:00] <ogra_> phablet@ubuntu-phablet:~$ initctl list-sessions
[21:00] <ogra_> 555 unix:abstract=/com/ubuntu/upstart-session/32011/555
[21:00] <ogra_> yup, that looks better
[21:00] <ricmm> does it for me automatically somehow, maybe going via SSH actually picks it up
[21:01] <stgraber> if you ssh as phablet, I'd expect it to be set, yes
[21:01] <ricmm> anyways, looks like its working
[21:01] <stgraber> adb + su, probably not
[21:01] <ricmm> yup
[21:01] <ricmm> ogra_: export that session UPSTART_SESSION and try to start an application with $ start application APP_ID="gallery-app"
[21:02] <ogra_> http://paste.ubuntu.com/5869274/
[21:02] <ricmm> once you can initctl list, to confirm you joined the upstart session
[21:02] <ogra_> works fine
[21:02] <ricmm> awesome
[21:02] <ricmm> ship it
[21:02] <ogra_> ++
[21:02] <ogra_> great work
[21:03] <ricmm> can you bottom approve https://code.launchpad.net/~ricmm/session-manager-touch/migrate-to-upstart-session/+merge/172936
[21:03] <ricmm> ill wait for salveti to top it
[21:03] <ricmm> thx
[21:04] <dejello> Hey all
[21:13] <DJJeff> is there video on how to port ubuntu touch to other devices?
[21:15] <DJJeff> I dont have this program called "breakfast" ?
[21:17] <DJJeff> I got this far.... http://i.imgur.com/X5Fapqo.png
[21:18] <dejello> I learned a bit from building cm-10.1 first.  A brief glimpse of the porting page and I did not see it:  type ". build/envsetup.sh" without the quotes.  Yes, type the . as well
[21:18] <flo__> DJJeff, I've never used breakfast, but I guess you need ". build/envsetup.sh" (note the space between . and build)
[21:18] <flo__> uhm, yeah :)
[21:18] <dejello> breakfast, lunch, brunch, etc should work after that
[21:19] <dejello> :)
[21:20] <dejello> They changed the repos again and now I can't build >.<
[21:21] <dejello> make: *** No rule to make target `/media/jon/Build_Output/ut_cm/target/product/ovation/ubuntu-boot.img'...............   From what I recall from the first time they tried it, it should download something to make it but it's not
[21:21] <dejello> I could be mistaken though
[21:21] <DJJeff> ok I got this http://i.imgur.com/vxLZKZb.png
[21:22] <DJJeff> when do I get to choose that I want todo this for (p4wifi)
[21:23] <flo__> DJJeff, you should be able to use breakfast now. Not sure what p4wifi is (or whether it is supported by breakfast)
[21:24] <dejello> I kept getting that check signature error and it makes the hybris dir not update right after that, so I commented it out and have a script to update hybris and platform-api...  Is that an issue for everyone?
[21:24] <dejello> Never asked before, just been using my script
[21:24] <dejello> works great
[21:25] <flo__> dejello, I also have the warning about signature verification. I just ignore it :D
[21:25] <DJJeff>      69. cm_p4wifi-userdebug
[21:26] <dejello> :)
[21:27] <DJJeff> does this look correct? http://i.imgur.com/JnBvAs7.png
[21:27] <dejello> yep
[21:29] <dejello> You'll have to follow the porting guide now to make the proper changes to your local files and then see about building
[21:30] <dejello> I will say, some of the files may not be exactly the same, so you may end up having to search for what you need..
[21:32] <DJJeff> for extract-files.sh I need to have my device booted into CM10.1 ?
[21:35] <DJJeff> oh I guess it worked..... except these errors http://i.imgur.com/Qdg1Yko.png
[21:44] <mfisch> Can any app-devs tell me where LocalStorage databases end up, as in where in the filesystem.
[21:46] <popey> mfisch: .local/share/<appname>/.QtWebKit/LocalStorage/ for example
[21:47] <mfisch> I'm not seeing that for this app I'm running out of QtCreator
[21:47] <mfisch> but I think I see the DB issue with my code anyway
[22:03] <psusi> as I understand it, gnome is working on EGL support for wayland, which is also the graphics api on android, so when that is done, will that allow regular gnome gui apps to run on ubuntu touch?
[22:10] <ahayzen> Hi, just been hacking away on the music app and have managed to get seeking working on the now playing screen. Not sure if the design is correct but it is functional. If someone is interested find it here -  lp:~andrew-hayzen/music-app/now-playing-seeking
[22:15] <DJJeff> I think its broken waaaaaaaaah http://i.imgur.com/57nUHOw.png
[22:16] <popey> ahayzen: ooh
[22:16] <popey> ahayzen: will take a look in the morning, thanks
[22:18] <ahayzen> popey, its works quite well :)...haven't got seeking working on the main screen, only the now playing, but not sure if it should allow you to?
[22:39] <dejello> anyone else having the "no rule to make.... ubuntu-boot.img" problem?   I suppose I am going to start from a fresh directory with the current repos to see what happens
[22:41] <flo__> by doing "apt-get dist-upgrade && apt-get --prune autoremove", both indicator-time and indicator-battery were removed from my phone.. now I no longer have the nice battery icon and clock. Should indicator-power / indicator-datetime work on the phone? those are installed now
[23:56] <chipv12> hello