[03:39] <Linden940> Ahmuck, what part of texas are you in? I could take them off your hands
[03:39] <spridel> really?  i remember taking a TV for $15 or $25
[03:40] <spridel> yeah what mrand said
[03:40] <Linden940> best buy got smart lmao
[03:40] <Linden940> what alot of people use to do was fill a 18wheeler and ship them to CA
[03:40] <Linden940> down in CA the state will PAY you for them
[03:41] <spridel> well you put in $10 and get a $10 gift card
[03:41] <Linden940> it was a really good cash amount...i don't remember it anymore tho.
[03:41] <Linden940> but now you have to show proof that they came from CA and thats hard to do...so you cant ship them there anymore and get paid the big bucks
[03:41] <Linden940> so the only other place you can send them is over seas to china where they turn them into tvs
[03:42] <Linden940> If bring them to me I will buy them off of you lol
[03:42] <Linden940> i'm only paying like $0.25 but I don't charge
[03:44] <Linden940> well...i am off to bed..i am flat out dead on my feet...I lost two pallets of computers down the road today from the rain and some asshole who cut me off that I had to slam on the brakes
[03:44] <Linden940> that was a fun clean up job with it raining
[03:44] <Linden940> so good night ya'll
[21:18] <tp0x45> anyone here from Central Texas?
[21:21] <tp0x45> Bryan/College Station?
[21:47] <mrand> is anyone really /from/ BCS?
[21:47] <mrand> I mean, I went to school there and all, but I don't remember meeting anyone  actually born there.  Most people move there.
[22:15] <NicolaeDebevec> it's a college town, like others it exists to serve the school


[14:06] <p3lim> hi, I've set up a 22.04 server and I'm getting completely messed up results from /usr/bin/hostname
[14:06] <p3lim> `hostname` = <hostname>.<domain>, `hostname -f` = <hostname>, and `hostname -d` returns nothing
[14:09] <p3lim> it should obviously be: `hostname` = <hostname>, `hostname -f` = <hostname>.<domain>, and `hostname -d` = <domain>
[14:17] <p3lim> ah, entries in /etc/hosts were backwards
[15:16] <ckode_> Hi, has anyone installed freeradius on Ubuntu 22 server?   I just tried on CentOS 9 only to find out there are unreleased official packages for CentOS 9 and I don't want to run into a similar issue with Ubuntu 22 given it's somewhat recent (April 2022) release.  hah.   Thanks for any heads up
[15:55] <lotuspsychje> ckode_: launchpad doesnt seem to list a lot of bugs there; https://bugs.launchpad.net/ubuntu/+source/freeradius
[16:00] <lotuspsychje> ckode_: another idea would be reading the !jammy releasenotes, usualy they hold a lot of information and known bugs (not sure if freeradius is mentioned)
[16:13] <ahasenack> freeradius in jammy is a git snapshot, something between 3.0.25 and 3.0.26 which wasn't released at the time
[16:13] <ahasenack> it was needed because of openssl3 support
[16:14] <ahasenack> there is a test suite that is run, with some basic authentication mechanisms (that were failing in 3.0.25, hence the git snapshot)
[16:14] <lotuspsychje> ckode_: ^
[16:19] <ahasenack> we test pap, chap, mschap and eap-md5
[16:20] <ahasenack> https://git.launchpad.net/ubuntu/+source/freeradius/tree/debian/tests/test-freeradius.py?h=ubuntu/jammy-devel#n70
[16:20] <ahasenack> and many other things, of course, see https://git.launchpad.net/ubuntu/+source/freeradius/tree/debian/tests?h=ubuntu/jammy-devel for details
[17:13] <ckode_> @ahasenack Thank you!  That is very enlightening!
[17:13] <ckode_> @lotuspsychje, thank you also
[17:14] <lotuspsychje> cookie is for you ahasenack
[17:59] <ahasenack> thx


[08:39] <roxan> can i get a ubuntu member cloak?
[08:44] <jussi01> roxan: are you an ubuntu member?
[08:46] <jussi01> roxan: if the answer is yes, please make certain you have set up you nick according to http://freenode.net/faq.shtml#nicksetup and provide your launchpad page.
[09:04] <roxan> jussi01, ubuntu member in launchpad?
[09:05] <jussi01> !member | roxan
[09:08] <roxan> jussi01, i'm member of ubuntu nepal
[09:08] <roxan> loco team
[09:09] <jussi01> roxan: but have you been accepted as a memeber like the process above?
[09:10] <roxan> jussi01, not yet on ubuntu.
[09:10] <roxan> jussi01, this means ubuntu nepal loco team is not enough?
[09:10] <jussi01> roxan: correct.
[09:11] <jussi01> roxan: you might be accepted on the basis of your work there, but you need to still apply centrally for membership
[09:12] <roxan> jussi01, all i want is a ubuntu cloak
[09:12] <jussi01> roxan: and ubuntu cloaks are only for ubuntu members
[09:12] <roxan> jussi01, :(
[09:13] <roxan> jussi01, and its not easy to be a ubuntu member oto
[09:13] <roxan> too*
[10:35] <roxan> jussi01, are you a bot?
[10:35] <jussi01> roxan: no, why do you ask?
[10:36] <roxan> jussi01, sorry. you are only involve in bot team. o
[10:36] <roxan> ok
[10:36] <jussi01> heh
[10:36] <roxan> jussi01, i thought you were a female
[10:36] <erUSUL> jussi01: becouse you have a version number LOL XD
[10:36] <erUSUL> jussi01: next bot jussi02-rc ;P
[10:36] <roxan> erUSUL, yeah that also can be a erason
[10:37] <jussi01> rofl
[10:37] <jussi01> !owner
[10:37] <jussi01> so no, im not a bot, but I own a bot...
[10:37] <jussi01> :D
[10:37] <roxan> !owner
[10:38] <roxan> jussi01, you code it?
[10:38] <jussi01> roxan: no, its a
[10:38] <jussi01> !info supybot
[10:39] <roxan> jussi01, ok
[10:39] <roxan> jussi01, you use screen?
[10:39] <jussi01> for?
[10:39] <roxan> jussi01, for your daily work
[10:39] <jussi01> roxan: please these questions should be in #ubuntu-bots, not here
[10:39] <roxan> jussi01, oh sorry
[10:40] <roxan> jussi01, what is this channel is used for.
[10:40] <roxan> ?
[10:40] <jussi01> roxan: type: /topic
[10:40] <roxan> jussi01, ok.
[10:40] <jussi01> anyway, back to work with me...
[20:04] <[NikO]> !members > [NikO]
[20:04] <[NikO]> !cloak > [NikO]
[20:05] <nalioth> ubottu: tell [NikO] about member
[20:06] <[NikO]> thanks :)
[22:58] <LjL> Helminthe: not sure what you meant that - IRC resource, or other support resources, or what?
[22:59] <Helminthe> irc, of course, the rest being already established as forums, wikis, whatever
[22:59] <LjL> Helminthe, well, none of them is directly supported by canonical
[23:00] <LjL> but all the localized #ubuntu-* IRC channels on this network are somewhat endorsed by canonical
[23:00] <LjL> note, *somewhat*. we're still just all volunteers with little supervision
[23:00] <Helminthe> what triggered my reply was: "salve" means something in Romanian too, what if there was a community of such users around?
[23:00] <LjL> sure
[23:00] <LjL> !ro
[23:01] <Helminthe> "supported", or "endorsed"  - of course not , I don't expect someone to be liable for random internet chats
[23:01] <Helminthe> wow, this is good news for me
[23:02] <LjL> Helminthe: this is the homepage of the Romanian LoCo Team: http://www.ubuntu.ro/
[23:02] <LjL> but i'm sure they can point to all their resources on the channel itself
[23:03] <LjL> it's an approved LoCo team, which means it's not just a bunch of people put together, but it's been approved by the Community Council
[23:03] <LjL> this is what i meant when i said "somewhat endorsed" (the CC is not Canonical, though)
[23:03] <LjL> !loco
[23:03] <Helminthe> thank you
[23:04] <Helminthe> this is surely more than what I expected
[23:06] <Helminthe> I have been using ubuntu for more than one year, linux for 10, and had no idea that serious effort is involved in having a romanian version of the eb pages
[23:06] <Helminthe> +w
[23:06] <Helminthe> I will make sure to contribute to this effort for future releases
[23:07] <Helminthe> there was an InstallFest in Bucharest?
[23:07] <Helminthe> damn
[23:07] <Helminthe> ok, just thanks for the pointers
[23:10] <LjL> Helminthe: Ubuntu is a lot about doing things internationally
[23:11] <LjL> Helminthe: also, that team is the one responsible for translating Ubuntu itself into Romanian. that's an important task.
[23:13] <Helminthe> downloading Kiwi linux right now :)


[02:48] <wat> so
[02:48] <wat> ubuntu mobilwe
[02:48] <wat> mobile*
[02:48] <wat> when will it be available ?_?
[02:48] <wat> An iPhone flash for it would be hella cool'
[08:30] <lool> Morning
[09:24] <lool> asac: Hey, around?
[09:25] <lool> asac: I tested langpacks and they work with up-to-date midbrowser and xulrunner; however some strings are missing (e.g. Characted Encoding in the menu)
[09:26] <lool> Also parts of the Extensions dialogs aren't translated, but I don't know whether these were translated in the past
[09:27] <lool> I have language-pack-gnome-fr 1:8.04+20080527.0ume2 and language-pack-gnome-fr-base 1:8.04+20080527
[09:28] <lool> asac: On an unrelated topic, you might recall I poked you for comments on an evolution-rss patch; did I miss your reply?
[09:43] <asac> lool: err, i think i replied in the bug
[09:44] <asac> lool: did you upgrade the language-pack-base and language-pack packages as well? which version do you have there?
[09:46] <lool> asac: language-pack-fr 1:8.04+20080527 and language-pack-fr-base 1:8.04+20080527
[09:47] <asac> those are too old
[09:48] <asac> hmm
[09:48] <asac> no
[09:48] <asac> look good
[09:48] <asac> what version do you see for xulrunner translation in the addons dialog?
[09:49] <lool> asac: 1.9
[09:49] <lool> asac: I don't have any language-pack-fr or language-pack-fr-base in ppa
[09:50] <asac> lool: true <IP_ADDRESS> it should be though
[09:50] <asac> what is in /usr/lib/xulrunner-addons/extensions/langpack*fr*/install.rdf `
[09:50] <asac> ?
[09:50] <asac> as version?
[09:51] <lool>                em:version="1.9"
[09:51] <asac> should be <IP_ADDRESS>
[09:52] <asac> please check if you have all from -updates
[09:52] <lool> The only French langpack is language-pack-gnome-fr AFAICS
[09:52] <asac> you need language-pack-fr and language-pack-fr-base
[09:52] <lool> asac: Ah you want me to try the hardy-updates version of the langpacks?
[09:55] <asac> you need them yes
[09:55] <asac> is that an issue?
[09:56] <lool> asac: It's fine if these weren't forked for ume
[09:56] <lool> I have language-pack-fr 1:8.04+20080708 now
[09:58] <lool> asac: Extension version is good now, but most items in the menu aren't translated anymore
[09:58] <lool> Only "Encoding" is, the rest isn't (e.g. "new tab")
[09:59] <lool> Oh I upgraded language-pack-gnome-fr but shouldn't have
[09:59] <lool> asac: I think we need a language-pack-gnome-fr update in ppa
[09:59] <asac> yes. i think all lang-packs need to be updated.
[09:59] <asac> i have a call in a minute. will ping you when back
[09:59] <lool> Ok
[10:01] <lool> asac: Everything is fine now
[10:01] <lool> asac: So we just need a refresh of language-pack-gnome-* in ppa AIUI
[10:02] <asac> yes. we just need to put the midbrowser bits from ppa into the lates from -updates
[10:02] <lool> asac: I'm happy to follow your instructions for the update as to allow me to repeat this for the next langpack updates
[10:03] <asac> look in mozilla.tar.gz in ppa version
[10:03] <asac> there is midbrowser/extensions directory
[10:03] <asac> that one needs to be added to mozilla.tar.gz of -updates one
[10:04]  * lool gets http://ppa.launchpad.net/ubuntu-mobile/ubuntu/pool/main/m/midbrowser/midbrowser_0.3.0release-1~8.04.1.dsc and http://archive.ubuntu.com/ubuntu/pool/main/l/language-pack-gnome-fr/language-pack-gnome-fr_8.04+20080708.dsc
[10:05] <lool> Oh the data/mozilla.tar.gz from ppa's language-pack-gnome-fr
[10:05] <asac> yes
[10:06] <lool> asac: Kyle did some changes as well in ume2
[10:06] <lool>   * Replace grabanddrag.jar and modify chrome.manifest accordingly to add
[10:06] <lool>     grabanddrag fr (French) translations.
[10:06] <lool> Do we need to repeat these as well?
[10:06] <asac> those should be in mozilla.tar.gz alrewady
[10:06] <asac> if you use the latest from ppa
[10:07] <lool> asac: And you're repeating this for all langs?
[10:08] <asac> yes
[10:08] <asac> thats simple. just copy the usr/lib/midbrowser directory from ppa mozilla.tar.gz to new one
[10:09] <asac> i think there even is no mozilla.tar.gz in new -gnome langpacks
[10:09] <asac> so you can just copy it over
[10:09] <asac> but take care that only usr/lib/midbrowser directory tree is in there
[10:11] <lool> Ah some are ume1, I'll need to do this properly it seems
[10:13] <lool> There are some differences in the tarballs, but I don't think they matter
[10:13] <lool> drwxr-xr-x asac/asac         0 2008-06-10 22:39 ./usr/
[10:13] <lool> drwxr-xr-x asac/asac         0 2008-06-10 22:39 ./usr/lib/
[10:13] <lool> drwxr-xr-x kyle/kyle         0 2008-06-10 22:39 usr/
[10:13] <lool> drwxr-xr-x kyle/kyle         0 2008-06-10 22:39 usr/lib/
[10:14] <asac> shouldnt matter
[10:28]  * lool pushes langpacks
[10:30] <asac> uh
[10:30] <asac> rock
[10:30] <asac> lool: do they work?
[10:34] <lool> asac: Well I see everything translated in the menu, and I see a midbrowser (fr) extension in the list
[10:34] <lool> version 0.3.0
[10:34] <lool> asac: is there a particular string I could use to check whether this works?
[10:34] <asac> if the menu is completely translated
[10:34] <asac> and the preferences dialog as well
[10:34] <asac> then all should be fine
[10:35] <lool> Yes, both of these are translated
[10:39] <asac> lool: to QA this, go to every tab in the preferences.
[10:39] <asac> if nothing is broken it should be fine
[10:39] <asac> ask kylem to verify that there are no regressions for him maybe
[10:41] <lool> asac: Oh I wanted to tell you about that: kyleN confirmed yesterday evening that he used your instructions for customer builds
[10:41] <lool> Not for the ppa
[10:41] <asac> look at ppa ... it was him uploading the last ones ;)
[10:41] <asac> but well. i dont get why he didnt upload to ppa though
[10:41] <lool> I don't think he cares directly about the ppa, nor are USG people pulling directly from it into their builds -- they snapshot from time to time and review the package updates
[10:42] <lool> asac: Yes, I saw him as uploader of some updates, I don't reconcile the two things though
[10:42] <lool> 22:22 < kyleN> lool.updating langpacks? first I herd of it
[10:42] <lool> 22:22 < kyleN> heard
[10:42] <lool> 22:23 < kyleN> I did some manual modifications to get a required build out
[10:42] <lool> 22:23 < lool> 12:25 < asac> lool: i told kylem how to update them before i left  for the summit
[10:42] <lool> 22:24 < kyleN> lool, he meant me, but what I did was a one time update needed  for a custom project
[10:53] <lool> asac: On another topic, persia wondered whether liferea would need an update at the same time as xulrunner >= <IP_ADDRESS>; I suggested that probably not as liferea wasn't updated in hardy-security/-updates
[10:53] <lool> asac: But in the end we thought we would double-check with you :-)
[10:55] <asac> lool: if its not in "Breaks:" then it shouldnt be required from what i can tell
[10:56] <lool> asac: Great
[10:59] <lool> asac: Re: GNOME #541872 thanks for your comment, I didn't see it as I wasn't subscribed to the bug, sorry; I am now
[11:00] <asac> lool: try to start it ;)
[11:00] <asac> (liferea)
[11:14] <lool> asac: Yeah it WFM
[11:17] <asac> lool: the patch?
[11:19] <lool> asac: liferea
[11:25] <asac> ah
[12:56] <persia> Team meeting in #ubuntu-meeting in 5 minutes
[12:56] <persia> Err. 4 :)
[14:02] <lool> persia: So you wanted to clear up my thoughts on squashfs support in ubiquity?
[14:02] <persia> lool: Re: GTK support for em: That actually doesn't help very much: it makes apps bigger in high-DPI environments.
[14:03] <persia> Getting proper resolution independence is about creating guidelines for size, and checking the current environment for display.
[14:04] <persia> As an example, if I've a 596 x 480 viewport (default Ubuntu viewport at 640x480), I need to pick a size for a terminal that fits there, which means picking the right font size, etc.
[14:04] <ogra> right
[14:04] <lool> persia: I think GTK support for em is just the start
[14:04] <ogra> we need a 480px min height policy :)
[14:04] <persia> If I then define the window decoration in "em" units, I have even less to play with when I'm using a 200DPI device.
[14:05] <lool> persia: It will force Gtk+ application writers to think about their UI size-independence, and move them away of pixel driven UI sizes
[14:05] <lool> The point here is that you can nicely "scale the application by changing the font size"
[14:05] <persia> lool: Well, not being pixel driven helps, but swapping pixels for ems is actively harmful for the high-dpi low-resolution environment.
[14:05] <lool> This is a huge step forward IMO
[14:06] <ogra> but if the window has a min height of 600px set you dont gain much
[14:06] <persia> Yeah, at least is means there is some thought involved.
[14:06] <lool> It moves the problem to "scaling ems" for us, which can be done centrally
[14:06] <lool> The kludge will be much smaller to maintain :-)
[14:06] <ogra> or graphics content forces the 600px
[14:06] <persia> True, although I wouldn't want everyone to become as myopic as I from looking at the results :)
[14:06] <persia> Anyway, about the installer.
[14:07] <lool> Anyway, there's no perfect solution; you can have a 24" screen in front of you, or at the other end of a room, and you will have different requirements for the displayed size of apps and fonts
[14:07] <persia> Basically, if the HW has sufficient secondary storage to support expected regular use without unionfs, it makes life *lots* easier not to install that.
[14:07] <persia> So, for 4G+ devices (based on Ubuntu Desktop HW requirements), it's best to just copy the contents of the squashfs onto a target partition on the device.
[14:08] <persia> That gives us small size increase for updates, simplified support matrix, compatibility with alternate metas for people who want to switch between -mid and -mobile, etc.
[14:09] <persia> But, for devices without that much secondary storage, such a model quickly becomes unsuitable.  Just unpacking the livecd takes about 2G.
[14:09] <persia> With the smaller seed, we can probably take that down to 1.5G, but it's still insufficient for basic use.
[14:09] <persia> (not enough space for user data)
[14:09] <persia> So, we'd need to have a squashfs.
[14:10] <lool> persia: Ack; that's actually the reason hardy's images install squashfs
[14:10] <lool> (in UME)
[14:10] <persia> It's not reasonable to ask these devices to build such a squashfs at install time, because it's painfully time consuming, and requires lots of disk space somewhere.
[14:10] <persia> (Yes, I wanted to do it that way, but I was unable to find any believeable reason it would work)
[14:11] <persia> So, the trick is to use the squashfs used on the installer image itself.
[14:11] <ogra> right
[14:11] <lool> Sure, I came so far
[14:11] <ogra> which is since we use livefs.sh for building it already configured in an ideal way
[14:11] <persia> So, what one does is to copy the install image livefs onto the device, and construct it as a unionfs.
[14:12] <lool> Agreed; that's the only way I imaginated it as well
[14:12] <ogra> ubiquity currently only supports the 4G case
[14:12] <persia> Where this gets tricky is that the configuration of the livefs for the install image, for the installed image, and the contents of the root filesystem for the >4G case are all subtly different.
[14:12] <ogra> (copy content)
[14:12] <ogra> huh ?
[14:13] <ogra> they arent
[14:13] <persia> Yes they are.  Hold on...
[14:13] <ogra> only the fs setup is
[14:13] <ogra> you need to have the copy/setup unionfs etc stage before the config stage
[14:13] <persia> config stage?
[14:13] <ogra> then ubiquity can do everything the same way in both cases
[14:14] <ogra> applying the config
[14:14] <ogra> for the target content
[14:14] <persia> ubiquity doesn't apply a config: it just copies the contents of the live image.
[14:14] <ogra> and configures /target according to your preseeding
[14:14] <lool> So I still think we can do the same thing in the two cases
[14:15] <persia> ogra: Except you don't run most of d-i, because you've already got that in the livefs.
[14:15] <lool> Instead of formatting and copying files to the new partitions, you partition, setup unionfs, and copy only differing files over
[14:15] <ogra> right
[14:15] <persia> lool: Well, not quite, because you need to support the reset-to-original-state use-case.
[14:15] <ogra> rm -rf /cow/* ?
[14:16] <persia> Anyway, please object when I get to that point, rather than getting ahead :)
[14:16] <ogra> and reapply the defaults
[14:16] <persia> So, the first interesting difference is between the installer livefs and the installed filesystem for the >4G case.
[14:16] <persia> ubiquity has a hook to remove the things one doesn't want post-install, such as ubiquity itself.
[14:17] <ogra> and unused langpacks
[14:17] <persia> (it's a little odd to have a "click here to install" button on an installed system)
[14:17] <persia> Yes, and unused langpacks, and other bits.
[14:17] <ogra> right, we need to exclude that in livefs.sh
[14:17] <ogra> and apply at bootime
[14:17] <lool> persia: Sure
[14:17] <lool> That's all possible in the target fs in the same way i would guess
[14:18] <lool> You might want to exclude this from the original squashfs though
[14:18] <persia> Right, it's just python to adjust the final image before first boot.
[14:18] <ogra> right
[14:18] <ogra> that should be handled by the image builder
[14:18] <persia> Where this gets especially interesting is when you consider the same situation for the 2G case.
[14:19] <persia> The same model doesn't work, because the stuff to be removed would only be marked unused in the overlay, and get restored when the overlay is wiped on device reset.
[14:19] <ogra> the image builder should a) build a squashfs without these contents for us ... b) set up a unionfs at buildtime c) copy all langpacks and ubiquity inot that
[14:19] <ogra> and then copy cow.img and squashfs.img into the dd'able image
[14:20] <persia> You're getting ahead again :)  Precisely.
[14:20] <ogra> (btw we use aufs now, no uniofs available anymore, we should adjust our wording ;) )
[14:20] <ogra> persia, the above works for both models
[14:21] <persia> The last interesting thing is that the squashfs to be deployed in the 2G case should have an initramfs pre-configured to continue to use squashfs as it gets adjusted.
[14:21] <lool> persia: Why would you reset the overlay?
[14:21] <persia> This then needs to be adjusted to not look that way in a final state in the >4G case.
[14:21] <ogra> right
[14:22] <ogra> but thats a single initramfs script
[14:22] <persia> lool: To restore the device to "factory settings".  It's an OEM requirement that is commonly used in consumer devices.
[14:22] <ogra> well, have a spare partition where you tar up the content of /cow
[14:22] <persia> Personally, I find it useless, but since it's not that hard to do if we're fiddling around to handle splitting out ubiquity and langpacks, etc. anyway, there's no reason not to do it.
[14:22] <ogra> the reset funtion wipes /cow and extracts the tar back
[14:22] <ogra> no magic
[14:23] <persia> Mind you, I'm never likely to get a <4G device again (even the thing I use for a phone as >4G), but for those that do...
[14:23] <ogra> we need something like mem=256M dfor disks in the kernel :P
[14:23] <persia> ogra: No magic, as long as we make sure that the squashfs as deployed exactly matches the environment we want on device reset.
[14:23]  * ogra is joking indeed
[14:24] <ogra> persia, my expectation would be that we can offer install to external devices .. so you could install to a 2G USB key
[14:24] <ogra> for testing purposes
[14:24] <ogra> all that is done by my classmate installer already we can steal code from there as we want
[14:25] <ogra> (the same counts for the image building process, all the above exists)
[14:25] <ogra> sadly the installer is 100% shell ... so for ubiquity that needs lots of adjustment
[14:25] <persia> ogra: Absolutely: it's not for testing purposes, but rather for support of various devices.  I've two different devices that have very small flash as primary secondary storage and moderate sized secondary secondary storage.  I'd probably want /boot on the flash, but install to the HD or slower flash (depending on which of my devices is being considered)
[14:26] <persia> That means having the ability to use a partition tool and install to arbitrary partitions on the target device, including, if so desired, USB keys.
[14:26] <lool> persia: That 'reset to factory settings' feature is new to me, and seem completely orthogonal
[14:26] <ogra> for 2G we shuld have a fixed partitioning scheme anyway
[14:26] <persia> lool: orthogonal to what?
[14:27] <persia> Essentially, implementation only means that we don't leave a crufty /cow at install time.
[14:27] <persia> (or rather, immediately post-install)
[14:27] <lool> persia: Orthogonal to squashfs installation
[14:27] <persia> Not leaving a mess seems more technically correct to me anyway.
[14:28] <persia> lool: Remember that the filesystem as viewed from the installer is not the same as the filesystem as viewed from the installed system (or oughtn't be).
[14:28] <lool> To me it just sound like in both the squash and non-squash cases you need to record the initial state of the system in the less space possible to allow restoring to this factory state
[14:28] <persia> To do this, we either need to double-layer the installer image, or fake deletion on the target device.
[14:28] <persia> In the non-squash case, there is no "reset" option available.
[14:29] <persia> Anything more complicated than wiping /cow isn't worth doing.
[14:29] <lool> persia: Sure, so we have state A: booted live system for installation, state B: initially installed system, state C: current system, and you want a way to reset from C to B; this is orthogonal to whether B and C are squashfs based or not
[14:29] <persia> lool: No.
[14:29] <lool> Just like the way state A is implemented, except that if it's not squashfs based, it's hard to generate
[14:30] <persia> In the squashfs case, you should be able to get from C to B by clearing the overlay.  In the non-squashfs case, you need to somehow track initial system state.
[14:30] <lool> I disagree
[14:30] <lool> You make up that requirement
[14:30] <lool> There's no reason you need to implement restore to factory by clearing the overlay
[14:30] <persia> lool: You'd rather that the initially installed system in the squashfs case required addition information to be in place in the overlay to work cleanly?
[14:31] <lool> You can have a double overlay and you lose no space
[14:31] <lool> That is, install squashfs read-only on partition 1, setup an overlay for state B in partition 2, and setup partition 3 as user overlay
[14:31] <persia> OK.  Do you agree or disagree with the statement that the initially installed system should have only that information that is required to be installed.
[14:32] <lool> You can clear partition 3 to restore to factory
[14:32] <lool> I don't understand your question
[14:32] <persia> Right.
[14:32] <persia> OK.  My contention is that in the squashfs case, the initial overlay should be compeltely empty.
[14:32] <lool> I don't think you need that requirement
[14:33] <persia> Maybe not, but is it better to have it be non-empty?
[14:33] <lool> It's desirable that it be small, but it wont be empty unless the squashfs is what gets used initially
[14:33] <persia> So, we make the squashfs be what gets used initially, no?
[14:33] <lool> I think generating the squashfs is out of the question, and having zero customization would mean creating one CD per install
[14:34] <lool> Well we should make it as close as possible (by excluding ubiquity for instance), but we wont ever make it exactly what gets installed unless there are no installation options
[14:34] <persia> Well, there's oem-config...
[14:35] <lool> Typically, I don't see how you'll manage to not install the langpack in some target overlay, unless you have on squashfs for language
[14:35] <persia> True.  I don't imagine any sane end-users will ever use the squashfs option.  I'm only bothering to consider it because ogra wants it for cmpc stuff.
[14:36] <lool> Well it's an interesting option for devices with little disk space
[14:36] <lool> I find it challenging to support, and hence interesting
[14:36] <ogra> i dont want to see any cmpc ever again
[14:36] <persia> As a result, I don't mind only having one langpack, as from an OEM perspective, devices should be pre-installed with the language for the target market.
[14:36] <lool> ogra: haha
[14:36] <ogra> what makes you think i would want it for cmcp :)
[14:36] <ogra> but i am sure yu will still find devices with 2G disks out there
[14:37] <persia> ogra: OK.  You pointed out that things like cmpc needed it.  Perhaps "want" is too strong a word.
[14:37] <lool> ogra: http://images.google.fr/images?q=classmate+pc
[14:37] <ogra> *like* :)
[14:37] <persia> (don't click that)
[14:37] <lool> It's work safe I promess!
[14:37] <ogra> heh
[14:37] <ogra> MY EYES !
[14:37] <persia> you clicked, didn't you.
[14:38] <lool> Before building a squashfs aware installer, we should find some cmpc-protection goggles for ogra
[14:38] <persia> Right, which is why the plan is to first finish the non-squashfs aware installer, and then look at the possibility of having one.
[14:39] <lool> persia: That's a reasonable way of ordering your priorities if you ask me
[14:39] <ogra> persia, i couldnt resist :)
[14:40] <persia> lool: Mind you, I won't complain if other things get in the way of a squashfs installer, but if one is done, I think it ought be optimised for the OEM case, as I feel very strongly that the price of disks and flash is low enough that most end-users would prefer a larger device if available, especially the class of end-users that would install an alternate OS.
[14:40] <persia> (and larger devices *are* available: lots of 10G stuff out now, and 20 is becoming less uncommon)
[14:41] <lool> persia: That's a sensible way to present it; however you need to consider the possibility of preinstalling Ubuntu on the devices too
[14:41] <lool> Typically, our USG team might have interest in such support
[14:41] <persia> For flash devices, it's still 4/8/16/32 (and mostly 4/8), but those are still 4.
[14:41] <persia> lool: Sure.  The USG team would be an example of a target audience who would need an OEM-optimised installer.
[14:41]  * ogra likes to note *again* that the squashfs installer exists already as cmpcinstaller ... its work of one afternoon to rip out the cmpc cpecifics there ... its not gtk based but if we need t it can be used worst case
[14:42] <persia> For the >4G case, it's more interesting to look at the ways that e.g. System76 or Dell do installs.
[14:42] <persia> ogra: There's MIC too, so using the cmpc installer isn't *worst* case.
[14:43] <ogra> heh
[14:43] <lool> Hmm we'll need some MIC goggles too
[14:44]  * persia has arranged for a special MIC visor, and is willing to be responsible for all the necessary looking at it whilst trying to make it less likely to be used.
[14:45] <persia> Anyway, I need to prep for my next meeting.  Any last minute questions about the ideas for squashfs installers?
[14:45] <persia> (or catch me another day)
[14:47] <lool> persia: I think we covered the side questions
[14:47] <lool> persia: Thanks!
[14:48] <persia> lool: Happy to share: it's been something I've thought a lot about, but don't have much code for, so can't just reference something.
[14:49] <ogra> go coding !
[14:49] <ogra> :)


[03:34] <ball> Any thoughts on AMD Zacate Vs. something like an Ivy Bridge Pentium for an HTPC?
[22:55] <DarthFrog>  Hi.  I upgraded Mythbuntu to 12.04.1 (from 10.04).  now when I use the remote control (msceusb), a single key press is treated as if I pressed twice.  Nuisance.
[22:56] <DarthFrog>  Has anyone encountered this behaviour?  Any ideas for a solution?


[00:14] <karpatil> nik90: yes, your build is working fine
[00:15] <nik90> karpatil: hmm not sure why your build isnt working
[00:15] <nik90> karpatil: I built it using my 14.04 laptop and a 15.04 chroot (qtc)
[00:16] <nik90> I will have to install ubutnu 15.04 on my other laptop to check if anything is wrong there
[00:18] <nik90> karpatil: but its getting late now here (01:18 AM) .. so I will be going offline soon
[00:19] <karpatil> sure, thank you for your time
[00:19] <nik90> yw
[00:19] <karpatil> nik90: i will look after it
[00:20] <karpatil> nik90: maybe something with my system env settings
[00:25] <mariogrip_> what do you guys think about this? http://ubports.com/ good or bad idea?
[00:49] <dobey> mariogrip: buying a domain and setting all that stuff up was probably a bit much. :)
[00:51] <mariogrip_> dobey, maybe :P
[00:52] <dobey> mariogrip_: it /is/ possible to edit or create pages on the ubuntu wiki and use existing code hosting and such :)
[00:56] <mariogrip_> dobey, i know, but i think this will be easier for developers where we can provide ota server, build servers and knowledge about porting.
[00:57] <mariogrip_> and when (if) we get many devices ported, a place to find downloads and support
[00:58] <dobey> i've actually been thinking of setting up a system-image server of my own
[00:59] <mariogrip_> :)
[01:01] <dobey> with a valid ssl cert
[05:55] <jcbjoe> hola
[05:55] <jcbjoe> what is the latest ubuntu-touch stable version ?
[05:56] <DonkeyHotei> 14.09
[05:56] <jcbjoe> is it still r12 or is it something else now ?
[05:56] <jcbjoe> yes 14.09 r12 ?
[05:56] <jcbjoe> i forgot where you get the r12 from its in the about section i think
[08:31] <lotuspsychje> ogra_: morning
[11:14] <adrian47> Is possible to install apps from store with apparmor disabled?
[12:17] <studio_> hi
[13:07] <studio_> that is the name for the settings-manager in ubuntu touch? i have a problem in a xfce-profile and don't know ho to delete it, rm .config/xfce4 is not working, it allways comes back.
[13:07] <studio_> sorry, i a mean what
[13:21] <studio_> solved
[14:19] <taiebot> Hey i am unable to update kodiscope to version 4.0 it downloads from the store but does not install.
[14:19] <studio_> i have seen, that there are 2 new branches under ubuntu-touch/devel-proposed, krillin.en and krillin.es where is the different to the normal devel-proposed ?
[14:20] <atya> hi all
[14:20] <studio_> hi
[14:21] <atya> is anybody here, who use N4 with latest devel version of Ubutnu Touch?
[14:22] <taiebot> atya I am
[14:24] <atya> taiebot:  can U tell me, is the agps works well with the latest dev version? if it isn't, is there any hope, it will works perfectly anytime?
[14:24] <taiebot> agps you mean location based on gps + wifi?
[14:24] <atya> taiebot:  when I tried it with my N4, the GPS was terribly slow
[14:25] <taiebot> gps is always slow.
[14:25] <atya> taiebot:  ok, the real question is: is the GPS usable on N4 now? how much time to find itself?
[14:26] <atya> taiebot:  not always. with Android it works well
[14:26] <taiebot> almost 2min to get a location
[14:26] <atya> taiebot:  can U tell me, what is the cause of this? is it driver problem or Ubuntu error?
[14:27] <taiebot> i do not know on this you can download an app to help you sensor status
[14:28] <atya> taiebot:  from where? what is that's name?
[14:28] <taiebot> where it tells you if the backend is found and gives you your location
[14:28] <taiebot> app store
[14:29] <taiebot> the name is sensorsstatus
[14:29] <atya> taiebot:  thank a lot, I will try it soon
[14:30] <atya> taiebot:  is the GPS _always_ finds the location in 2 minutes?
[14:31] <taiebot> depends where you are. It is normally not recommended to be inside
[14:31] <studio_> btw. what navigation software are you all using? never tied that and in the new image isn't the "here" anymore ... can you please give me an advice?
[14:31] <atya> taiebot:  it would be acceptable
[14:32] <taiebot> . agps does not seems to work here as it did not find my position yet.
[14:33] <atya> taiebot:  I tried it outside in my car, but I can't wait for half an hour :S
[14:33] <taiebot> studio_ i still have the here maps web app installed and osm
[14:34] <studio_> what version (image) do you use?
[14:34] <atya> studio_:  I want to develop one :D But I have to buy a Meizu MX4 before, I'm affraid :D
[14:34] <taiebot> 15.04 r126
[14:35] <taiebot> i think the web app was removed from the store.
[14:36] <studio_> i have 15.04 r137 (krillin) but without here?!
[14:36] <taiebot> i would like to know what ships with the BQ and the meizu?
[14:37] <taiebot> atya it looks like it s not working here either so must be a ubuntu bug
[14:37] <atya> taiebot:  can anybody browse the Ubuntu Store without Touch? Is there any webapp?
[14:38] <taiebot> atya https://appstore.bhdouglass.com/apps
[14:39] <atya> taiebot:  tnx
[14:39] <studio_> is there via command line a test tool for gps?
[14:42] <atya> thans for your help, bye all!
[15:30] <adrian47> I have some problems with adb, but wifi works, ssh should start automatically? I cant connect to it (ssh: connect to host <IP_ADDRESS> port 22: Connection refused)
[15:35] <studio_> adrian47, did you enabled ssh?
[15:37] <adrian47> when i connect adb unity is not usable, but i start ssh now for test and.. :Permission denied (publickey).
[15:38] <adrian47> How can i start ssh automatically?
[15:38] <studio_> hehe, i had the same problem in the beginning, you have to change keys
[15:39] <studio_> username is not working
[15:40] <adrian47> oh, thanks but how? :)
[15:41] <studio_> http://askubuntu.com/questions/563573/cant-ssh-into-ubuntu-touch-device
[15:41] <studio_> :)
[15:52] <studio_> hmm, i still can't connect via mtp to my phone (15.04 - r137) and there is also still an empty vendor/device on lsusb on 2a47:0c02 is that normal?
[16:18] <studio_> is there a "trick" to enable the mtp-client on the device?
[16:20] <adrian47> studio_ you editet ssh.override file?
[16:21] <adrian47> with ssh problem :)
[16:21] <studio_> no, just made the keys and imported them
[16:23] <studio_> was a little bit "tricky" with adb get or wget (from my server) to get it to the ubuntu-touch device. could be made more easy ... :(
[16:35] <studio_> but what about the mtp problem? on two computers no connection via mtp to the ubuntu-touch device. so it must be a problem with the software on the device. where can i find the changelog or diff to the software about changeings in the  mt-protocol?
[16:49] <studio_> is still someone here who is using the bq e4.5 and can "maybe" help?
[17:05] <adrian47> studio_, i made key and flashed it, now whe i try ssh it want's password but phablet doesn't work
[17:12] <studio_> adrian47, i am flashing my device right now back, because i have unsolved problems. but for ssh-connection you do not need to "flash" your device. "just" import the right ssh-key ...
[17:20] <studio_> adrian47, as the guy in the url wrote "Paste your public key to /home/phablet/.ssh/authorized_keys2" ... did you made that?
[17:25] <adrian47> studio_, yes, there wasn't .ssh folder so I created it
[17:27] <adrian47> and after this, when trying to connect I have to enter password<EMAIL_ADDRESS>password: '
[17:27] <studio_> ok, "cd ~/.ssh" then "ssh-keygen" and change the keys on both sides :)
[17:28] <studio_> the password is normally the phrase you set ...
[17:29] <studio_> isn't it?
[17:29] <adrian47> i set empty password
[17:29] <adrian47> and it not works
[17:30] <adrian47> it's better to set it?
[17:31] <studio_> i never worked with an empty phrase ... try one.
[17:34] <studio_> ssh is for beginners "not so nice". needs an easy how-to ...
[17:37] <studio_> most windows users use putty and when they try to connect to their ubuntu-touch device with ssh, then they have their first big problem ...
[17:40] <digim0nk> Is the new music app released .. Running stable .. Will the new music app be released for 14.10
[17:40] <ahayzen_> digim0nk, define 'new' music app? and do you mean desktop/phone ?
[17:55] <studio_> i am back on 14.10 on my device and mtp is working again. the error must be on 15.04!
[17:57] <adrian47> hmm, i have ported 15.04 and here mtp works, it must be device specific
[17:57] <studio_> on what device?
[17:57] <adrian47> HTC Desire HD
[17:58] <adrian47> old one but i love him :)
[17:58] <studio_> i use a bq 4.5 :)
[17:58] <studio_> e4.5
[17:59] <studio_> i also think now it is device specific ... :(
[17:59] <dobey> there are some known issues with vivid images that came up as people were concentrating on the rtm release for the bq phone. they should be getting fixed soon
[18:00] <studio_> import contacts from the sim card was not working on the 14.10, but on 15.04 it works...
[18:00] <dobey> the branch to fix that was only for vivid, yes
[18:00] <studio_> ahh ok
[18:01] <studio_> but on 14.10 i have nokia here?
[18:02] <studio_> why it was removed from 15.04?
[18:04] <k1l_> are you mixing ports and official images?
[18:05] <studio_> no, from bq there is no official image. that was what Víctor González told me ...
[18:08] <g105b> how long do I have to wait for my bq :( still not got it
[18:09] <k1l_> best is to ask the bq guys :)
[18:11] <studio_> g105b, they still have no release for the software :)
[18:11] <g105b> studio_: oh so there isn't any made yet? I thought I was waiting for the shipping...
[18:12] <studio_> made, maybe, but not public ...
[18:13] <Elleo> g105b: last thing I saw on G+ seemed to indicate there was some issue with the cases that was holding up shipping
[18:13] <Elleo> g105b: no idea how reliable that is though
[18:13] <g105b> aha there's me rushing to the mailbox every afternoon after work and they haven't finished building it yet :D
[18:14] <Elleo> g105b: https://plus.google.com/110395302661228413735/posts/jaZeyc2DiuW
[18:14] <Elleo> g105b: but like I say, no idea how reliable that is
[18:14] <studio_> if they use 14.10 i ask myself how user can import contacts from the sim card, when this is only possible with the 15.04?
[18:14] <g105b> hmm, very concerned about "unable to say if other devices will be shipped with Ubuntu or not"
[18:17] <dobey> studio_: no. the rtm image has what's on the phone that's shipped by bq
[18:17] <dobey> studio_: the vivid images are developer builds
[18:17] <dobey> studio_: you were told this already
[18:18] <dobey> studio_: also as arleady told to you, sim contacts import is not supported yet
[18:19] <dobey> g105b: why the concern? that's about whether they will product ubuntu versions of their other existing phone models
[18:19] <studio_> that will be a problem on the "release" when the users will figure out that ...
[18:20] <g105b> dobey: Oh, I read it as "we might not even send you the phone with Ubuntu on it"
[18:20] <dobey> studio_: no it won't. you are not all users. stop trying to act like you speak for everyone.
[18:20] <dobey> g105b: no, the ubuntu version of the phone will be shipped to those who bought it. there is apparently just some delay in shipment.
[18:21] <g105b> I see
[18:21] <digim0nk> Contact and Calendar sync from Google worked like a charm .. Impressive.
[18:21] <studio_> dobey, ok how can new users import their contacts to the ubuntu-phone?
[18:21] <dobey> studio_: google? anyone using an android phone will almost certainl have their contacts in google already
[18:22] <studio_> why google? thei do not use google !!!
[18:22] <studio_> thay
[18:22] <dobey> who do not use google?
[18:23] <adrian47> studio_, i tried but still the same error
[18:23] <k1l_> everyone with an android uses google.
[18:23] <g105b> everyone with an android phone is used by google.
[18:23] <dobey> i don't use google contacts. but i don't use android either
[18:23] <k1l_> and all the nerds who dont use google because "google is evil" know how to handle their stuff with other services.
[18:24] <studio_> they use a phone with contacts on it, som also uses old phones without android ios or windows ... so how to import via th "normal" way from the sim card?
[18:24] <dobey> and i imported the contacts from my webos phone through a vcf export
[18:24] <dobey> studio_: who is "they" ?
[18:24] <studio_> pplz
[18:24] <dobey> studio_: 14:18 < dobey> studio_: no it won't. you are not all users. stop trying to act like you speak for everyone.
[18:24] <k1l_> so there is no "dumb user" who knows that "google is evil" but doesnt know how to setup stuff without google. so dont pretend that is a usecase for 99% of the users.
[18:25] <Elleo> studio_: SIM card import is under development, so it'll be available for users who can't use the existing methods when vivid becomes stable
[18:27] <studio_> Elleo, i understood under development, but is there an alternative way, not google, for exchange contacts? a tool for windows for example?
[18:27] <dobey> no there is no tool for windows
[18:28] <Elleo> studio_: the contacts app can import vcf files (which most things can export)
[18:30] <studio_> Elleo, on the 14.10 is only import via google, nothing more.
[18:31] <Elleo> studio_: you can do vcf imports on 14.10 as well
[18:31] <studio_> where?
[18:31] <dobey> Elleo: how?
[18:31] <Elleo> studio_: just email yourself a vcf file for example, or download one through the browser and it'll let you open it in the contacts app
[18:32] <Elleo> at least I'm pretty sure that's the case
[18:32] <Elleo> it's possible that there's only vcf export, but I think there's import as well
[18:32] <dobey> Elleo: you cana't copy a vcf onto the phone via mtp and open it afaik
[18:33] <dobey> you can import a vcf as a new address book in evolution, and then copy the contacts.db onto the phone and overwrite whatever contacts you already have on the phone, with that
[18:34] <dobey> but there's no "import" button in the contacts app
[18:34] <Elleo> dobey: no button, but import is available via content-hub
[18:34] <Elleo> dobey: e.g. just visit http://mikeasoft.com/~mike/test.vcf in the browser
[18:34] <Elleo> dobey: and it should provide contacts as a destination
[18:34] <dobey> Elleo: if there's no button, there's no way to copy your vcf onto the phone and import it
[18:35] <dobey> Elleo: that's fine, but that's different from importing a local vcf
[18:35] <Elleo> dobey: it's still a non-google way of importing contacts
[18:35] <dobey> sure, but it's a very roundabout way of doing it which involves putting your contacts list somewhere on the internet
[18:37] <Elleo> dobey: it'll work if you email them to yourself as well, uploading it was just the fastest public example
[18:37] <dobey> Elleo: yes, and e-mail == internet
[18:37] <Elleo> dobey: and if it doesn't work from the file manager then that's a bug in the file manager that needs fixing
[18:38] <dobey> Elleo: there is no file manager on the retail phone
[18:38] <dobey> that's an app you have to install from the store
[18:38] <Elleo> dobey: I don't really see installing an app as being an insurmountable challenge
[18:38] <dobey> even if it does work from the file manager "install this extra app that has nothing to do with contacts, to be able to import your contacts" is not a nice solution
[18:38] <Elleo> dobey: I'm not saying the current solutions are perfect, but they do exist
[18:38] <dobey> Elleo: it's not about being a surmountable challenge or not. it's about user experience
[18:39] <Elleo> you don't have to be tied to gmail to import contacts (it's the easiest way, but it's not the only one)
[18:39] <dobey> importing contacts from google or a web site, is the only thing that gives a halfway decent user experience right now though
[18:41] <Elleo> dobey: I'm not saying it's the best user experience; someone asked how to import contacts without google and I was simply explaining how it can be done currently
[18:42] <Elleo> dobey: I don't think that'll always be the way to do it (for one thing sim imports are landing in devel at the moment), but it's the way you can do it currently
[18:58] <adrian47> i need help with ssh :D
[19:00] <adrian47> Is there a way to hack it? I am usign it on private network so I don't need any security
[19:03] <studio_> Elleo, thanks for help with the vcard import, but that did/should not be the "common way" ... it must be more easy
[19:12] <popey> adrian47: what do you mean "hack"?
[19:13] <adrian47> popey, I'm not sure, do something to get it work :)
[19:14] <adrian47> i added authorized_keys2 to /home/phablet/.ssh, but still getting Permission denied (publickey).
[19:15] <popey> did you set permissions correctly?
[19:16] <popey> and why authorized_keys2  and not authorized_keys?
[19:17] <adrian47> studio gives me this link: http://askubuntu.com/questions/563573/cant-ssh-into-ubuntu-touch-device
[19:17] <adrian47> i tried with authorized_keys too
[19:17] <popey> 19:15 < popey> did you set permissions correctly?
[19:17] <studio_> for me that was working ...
[19:17] <adrian47> where?
[19:17] <popey> for the .ssh folder and the authorized_keys file
[19:17] <popey> they have to have specific authorisations to work correctly
[19:17] <popey> drwx------ 2 phablet phablet 4096 Jan  8 15:32 .ssh
[19:17] <adrian47> give me a second
[19:17] <popey> -rw------- 1 phablet phablet  799 Mar  8 19:16 authorized_keys
[19:18] <popey> this is the #1 reason why ssh with keys fails on every single platform
[19:18] <popey> (that and people putting the wrong key on the machine)
[19:18] <studio_> popey, why now "authorized_keys" ?
[19:19] <popey> studio_: that's easily found out by a simple online search
[19:20] <studio_> i made it with the authorized_keys2 and it worked ?
[19:21] <studio_> "by a simple online search" is http://askubuntu.com/questions/563573/cant-ssh-into-ubuntu-touch-device
[19:21] <adrian47> .ssh has drwxrwxrwx, and authorized_keys has -rw-rw-rw-
[19:21] <studio_> isn't it?
[19:21] <popey> adrian47: thats wronger than wrong
[19:22] <popey> see mine above
[19:24] <adrian47> popey, ok, so i changed it now and rebooting
[19:24] <popey> rebooting!?
[19:24] <popey> you dont need to reboot, this isn't windows
[19:25] <adrian47> i have problems with adb
[19:25] <adrian47> i need made changes from recovery
[19:25] <popey> O_O
[19:27] <adrian47> adb works but when i turn developer mode, unity is completely not usable  (respond to touch after 10 minutes) until restart
[19:28] <popey> what device is this and what image you running?
[19:28] <adrian47> HTC DHD, my vivid port
[19:28] <popey> ah
[19:29] <adrian47> still the same error
[19:29] <popey> what error?
[19:29] <adrian47> Permission denied (publickey).
[19:29] <popey> do "ssh -vvvv<EMAIL_ADDRESS>[19:29] <popey> and pastebin the result
[19:30] <adrian47> http://pastebin.com/fXmpHkW6
[19:31] <popey> you're logged into your machine as root?
[19:31] <popey> and you copied the key from the /root/.ssh/ directory to the device?
[19:32] <adrian47> yes
[19:32] <popey> not "your" key, but "root" key?
[19:32] <adrian47> hmm, i was doing everything from 'sudo su' terminal session
[19:33] <popey> i wouldn't do that :)
[19:33] <popey> copy your own personal normal user key to the authorized keys file on the device and ssh as you, not root
[19:33] <popey> looks like you may have copied the wrong key over
[19:34] <popey> look at the end of the authorized_keys file on the device and you'll see the username @ hostname which owns the key
[19:44] <adrian47> http://pastebin.com/ghxeRHVQ
[19:44] <adrian47> the same
[19:45] <adrian47> PasswordAuthentication should be yes or no?
[19:46] <popey> you should not need to fiddle with the ssh config
[19:46] <popey> adrian47: so, permissions are 100% correct, same as mine on .ssh and authorized_keys?
[19:46] <popey> and you have the correct contents of authorized_keys?
[19:46] <wolflarson> pooooooooooooooooooopey!
[19:48] <l3on> debug apparmor group is auto-added by ubutnu-sdk, how can I disable this behaviour?
[19:51] <adrian47> popey, seeecond, from recovery adb the file was there but now when I connected adb when running i dont see it
[19:51] <popey> wolflarson: good evening
[19:57] <adrian47> my adb works sooo slooooow :(
[19:58] <ogra_> use ssh ;)
[19:58] <adrian47> hahah :D
[19:59] <adrian47> I want! But ssh don't want work with me :)
[19:59] <popey> configure it correctly then :)
[20:00] <ogra_> does you wlan work ?
[20:00] <ogra_> *your
[20:00] <adrian47> but how without working adb?
[20:00] <adrian47> ogra_, yes
[20:01] <adrian47> i need restart it now, adb blocked UT completely
[20:01] <ogra_> put "true" into /userdata/android-data/property/persist.service.ssh
[20:02] <ogra_> at least if your property system in the container works properly that should trigger ssh to start on boot
[20:03] <adrian47> i inserted 'service ssh start' into /etc/rc.local (found it somewhere)
[20:03] <adrian47> and it boots, but i am getting Permission denied (publickey).
[20:04] <ogra_> ah, yeah, that would indeed work too ... (ugly, but works)
[20:04] <ogra_> well, make sure the permissions are correct
[20:04] <ogra_> for your public key and the ~/.ssh dir )
[20:06] <adrian47> trying and trying but it's hard with my adb
[20:11] <ogra_> phablet@ubuntu-phablet:~$ ls -lhd .ssh/
[20:11] <ogra_> drwxr-xr-x 2 phablet phablet 4,0K Feb 25 13:00 .ssh/
[20:11] <ogra_> phablet@ubuntu-phablet:~$ ls -lh .ssh/
[20:11] <ogra_> -rw------- 1 phablet phablet 221 Mär  6 16:50 authorized_keys
[20:11] <ogra_> -rw-r--r-- 1 phablet phablet 222 Feb 25 13:00 known_hosts
[20:11] <ogra_> these are my permissions
[20:12] <ogra_> (on a working ssh)
[20:17] <adrian47> changing permissions from recovery adb will affect?
[20:18] <ogra_> yes, but i'mm not sure your recovery shell allows UIDs that dont exist ...
[20:18] <ogra_> phablet has 32011 or some such
[20:18] <studio_> guys, i figured out the problem with the ssh, because i made it new ...
[20:21] <studio_> adrian47, do you have the public key from your PC, example: "pc_id_rsa.pub" in /home/phablet/.ssh?
[20:21] <adrian47> studio_ yes generated by ssh-keygen
[20:22] <adrian47> and then  'cat id_rsa.pub >> authorized_keys'
[20:22] <ogra_> heh, you could just cp :)
[20:22] <studio_> if yes, make "cat pc_id_rsa.pub >> authorized_key" in /home/phablet/.ssh
[20:23] <studio_> if yes, make "cat pc_id_rsa.pub >> authorized_keys" in /home/phablet/.ssh
[20:23] <studio_> "S" sorry
[20:24] <adrian47> studio_ i made it on pc and then pushed with adb to /data/home/phablet/.ssh  (data because i pushed it from recovery
[20:25] <studio_> hope it is a different name? id_rsa.pub is standard ...
[20:26] <popey> if you adb push it, it will have the wrong owner and wrong permissions
[20:26] <popey> which you need to fix
[20:28] <studio_> adrian47, use mtp and but it into Downloads, then adb to copy it from Downloads to /home/phablet/.ssh/pc_id_rsa.pub or what ever
[20:29] <popey> this is confusing advice.
[20:29] <studio_> i know, but it is working
[20:30] <popey> not with that filename it aint
[20:30] <popey> It's been explained multiple times now by 3 people what needs to be done. It's really very simple.
[20:31] <adrian47> it's hard because i don't have good working adb
[20:31] <ogra_> did you use my hacked adbd binary ?
[20:32] <adrian47> ogra_, yes it worked until i get working unity
[20:32] <studio_> the problem is, how to push the id_rsa.pub from the pc to the .ssh-folder with a different name than id_rsa.pub and then to add to the authorized_key
[20:32] <ogra_> adrian47, oh ?
[20:32] <ogra_> for that binary unity shouldnt make any difference
[20:32] <popey> studio_: that is not remotely hard at all
[20:33] <ogra_> and given that you are unlikely to have more keys on the device you can just cp id_rsa.pub authorized_keys
[20:33] <ogra_> no need to cat
[20:33] <popey> on pc, "cat ~/.ssh/id_rsa.pub". On phone, "vim ~/.ssh/authorized_keys" and then "i" and then paste it in, save it, set permissions, _done_
[20:33] <popey> there is nothing else which needs doing.
[20:33] <studio_> popey, if you understand "how-to" it is easy, but most ppls do not understand
[20:34] <popey> I disagree, but hey ho.
[20:34] <popey> you're giving incorrect advice which is muddying the waters.
[20:34] <ogra_> this is why phablet-shell does it automatically for you ... ;)
[20:34] <popey> indeed
[20:34] <ogra_> (but phablet-shell needs adb )
[20:35] <n-iCe> hi guys, long time no see you
[20:36] <n-iCe> what's new?
[20:36] <studio_> the phablet shell can connect without problems to an ubuntu-server or RPI-Device. the problem is the other way
[20:36] <ogra_> "the phablet shell" ?
[20:36] <studio_> terminal
[20:36] <ogra_> i'm talking about the phablet-shell command :)
[20:36] <ogra_> that you run on the PC to connect
[20:37] <ogra_> (from the phablet-tools PPA ... it gives you a far advanced adb session ... (with working nano support for example ... and not limited to 80x24 chars))
[20:39] <n-iCe> is whatsapp supported yet?
[20:39] <studio_> "that you run on the PC to connect" ok ... but i use ssh
[20:39] <popey> n-iCe: no
[20:39] <n-iCe> sad
[20:39] <ogra_> studio_, because you have working wlan :)
[20:39] <ogra_> phablet-shell uses an ssh connection on top of adb ... doesnt need any network
[20:40] <studio_> the problem is to get ssh working for a beginner
[20:40] <ogra_> a beginner should just install phablet-shell and call it once
[20:40] <popey> or just follow one of a million ssh guides online
[20:40] <ogra_> after that your ssh is completely set up .. nothing to do
[20:40] <popey> they're all the same.
[20:41] <popey> copy key to authorized_keys, set permissions. _done_
[20:41] <studio_> a beginner is using putty on windows ...
[20:41] <popey> nope
[20:41] <popey> a beginner on ubuntu phone is almost certainly using ubuntu
[20:41] <popey> (or some other linux)
[20:41] <popey> in the future that will chage
[20:41] <popey> *change
[20:41] <studio_> popey, beleve me, you are wrong
[20:41] <popey> and again, there's a million "how to setup ssh" tutorials online
[20:42] <popey> you don't know what you're talking about :)
[20:42] <popey> right now, the vast majority of ubuntu phone users are ubuntu users
[20:42] <popey> in the future that will change, but right now, I'm confident that's the case.
[20:43] <studio_> fist, the rpi was new land for windows users, but now they want more ...
[20:45] <adrian47> ogra_, at boot i have few seconds when adb works fine but, next it slows down (very) and slows whole system (10mins for response)
[20:45] <popey> ouch
[20:48] <adrian47> now after few restarts, used every second, I pushed id_rsa.pub to device, cat it to authorized_keys, and set permissions (600 for authorized_keys, and 700 for .ssh)
[20:48] <adrian47> still the same error :(
[20:49] <studio_> "id_rsa.pub" same name as your device made???
[20:50] <popey> you do not need id_rsa.pub on the device.
[20:50] <studio_> why not?
[20:51] <popey> you need authorized_keys on the device
[20:51] <adrian47> there wasn't .ssh folder in /home/phablet/, so i created it and there is "id_rsa.pub" and "authorized_keys"
[20:52] <popey> adrian47: ok
[20:52] <adrian47> http://pastebin.com/rUpvgYAd
[20:52] <popey> adrian47: can you show us "ls -ld /home/phablet/.ssh" and "ls -l /home/phablet/.ssh/"?
[20:53] <popey> adrian47: on your pc, do you have a ~/.ssh/id_rsa file?
[20:53] <popey> debug3: Could not load "/home/adrian/.ssh/id_rsa" as a RSA1 public key
[20:54] <taiebot> Anyone having networking issues? on vivid r126. I have been having multiple issues. Wifi i can have up to 100+ wifi network available in the dash when i walk around my house. 3g does not work very well i need to restart ofono multiple times before getting a network connection it looks like it conflicts with wifi network. The toogle which switch of the wifi does toggle as well the 3g network off. i have had few times at s
[20:54] <adrian47> yes, it's in default dir: /home/adrian/.ssh , generated with ssh-keygen
[20:54] <popey> ok
[20:54] <popey> can you do those two ls commands above?
[20:54] <adrian47> popey, yes
[20:54] <popey> and also ls -l /home/adrian/.ssh  on your pc
[20:56]  * ogra_ bets your ownership is still not right
[20:56] <popey> +1
[20:58] <studio_> popey, please again why he do not need the "id_rsa.pub" from his device?
[20:59] <popey> I said he doesn't need id_rsa.pub _on_ his device.
[20:59] <popey> "device" in this context meaning "phone"
[20:59] <adrian47> http://pastebin.com/Sy9n9ZfJ
[21:00] <studio_> and when i like to connect to other devices by a shared key?
[21:00] <adrian47> http://pastebin.com/0cI1EIxc
[21:00] <ogra_> adrian47, root.root ...
[21:00] <ogra_> thats your prob
[21:00] <popey> +1
[21:00] <adrian47> oh
[21:01] <popey> 20:26 < popey> if you adb push it, it will have the wrong owner and wrong permissions
[21:01] <ogra_> :)
[21:01] <ogra_> * ogra_ bets your ownership is still not right
[21:01] <popey> \o/
[21:01] <popey> 19:18 < popey> this is the #1 reason why ssh with keys fails on every single platform
[21:01] <popey> (just to keep rubbing it in there) :D
[21:01] <ogra_> haha
[21:02] <adrian47> hahah I missed it :D
[21:02] <popey> it happens to everyone
[21:02] <popey> at least once
[21:03] <adrian47> when i remove authorized_keys file only, and then create it and cat as phablet user it should work?
[21:03] <popey> just chown it
[21:04] <popey> chown -R phablet:phablet /home/phablet/.ssh
[21:11] <ogra_> popey, tricky if the phablet user doesnt exist ;)
[21:11] <ogra_> (in recovery)
[21:11] <popey> ooh, fun.
[21:11] <popey> 1000?
[21:12] <popey> 32011?
[21:12] <popey> so chown -R 32011 instead of phablet?
[21:12] <ogra_> 32011
[21:12] <ogra_> if the recovery chwon allows that
[21:12] <ogra_> it is busybox ... not sure
[21:14] <stigray> Hi, I'm fairly new to porting and want to port utouch to LG G2. So far I followed the porting guide(advanced) and i'm able to build images for mako.
[21:14] <stigray> After that the guide says Add your device specific git repositories under phablet/device ("phablet" is the repository you cloned by following the previous build example and/or Touch/Building).  Make sure it's respecting the format used by AOSP (device/<vendor>/<device name>).
[21:14] <stigray> Can anyone help me what it exactly means and how do i add git repo for LG G2 D800
[21:15] <ogra_> right, you need an AOSP tree and the AOSP binary drivers
[21:16] <stigray> So I have this https://github.com/G2-AOSP/android_device_lge_d800
[21:16] <stigray> so where do I add it
[21:17] <adrian47> I did it at boot time, when adb worked, but now i have problem to boot it :)
[21:17] <ogra_> i have never done an AOSP port ... before you just added the different trees for your devices to the manifext file
[21:17] <stigray> manifest file
[21:18] <stigray> Thanks I'll give it a try
[21:18] <ogra_> back then we were suing CM still though ...
[21:18] <ogra_> not sure how much AOSP differs
[21:36] <studio_> ok, now i understood why "here" was removed ...
[21:40] <studio_> what is the best offline navigation software in the moment with osm for ubuntu touch?
[21:42] <dobey> there is no offline navigation software on ubuntu
[21:42] <dobey> at the moment
[21:44] <studio_> all the software cant't store the os-maps?
[21:45] <dobey> storing maps offline is one thing. doing navigation is something completely different
[21:45] <dobey> i don't know if any support offline caching of just the map tiles
[22:23] <studio_> ok guys, thanks for help for today, have to go to sleep. bye ...
[22:23] <adrian47> i am trying and trying, but after used adb, system hangs, and after reboot (adb reboot or battery pull) system doesn't start...