[01:01] <CoJaBo> Whelp. Kubuntu Bionic 32-bit does not even make it to desktop :/
[01:02] <CoJaBo> And I haven't even installed the Plasma beta yet <_<
[02:20] <valorie> CoJaBo: we will have i386 if we get testers for the alpha 2, the betas, and the RC
[02:21] <valorie> we must have i386 testers on 386 systems or it is not worth the trouble
[02:21] <valorie> for Kubuntu -- not ubuntu, which will not ship i386 for the lts
[02:47] <CoJaBo> valorie: I'm hoping to run Kubuntu on i386; if I can get it to run, that is..
[02:48] <CoJaBo> valorie: Plasmashell and the splash screen process both segfault, so it never gets to the desktop >_>
[02:50] <valorie> oh geez
[02:50] <valorie> this is on bionic?
[02:51] <CoJaBo> Yep
[02:51] <valorie> did it run for you on artful?
[02:51] <CoJaBo> Not sure, I never tried it on 386 before
[02:52] <valorie> can you retry with the artful ISO?
[02:52] <valorie> 17.10.1
[02:52] <valorie> be sure to use that, and hopefully upgrade immediately
[02:52] <CoJaBo> Not easily; I'm having trouble getting the system to boot from USB
[02:53] <valorie> damn
[02:54] <valorie> this is why we needed more testing of the beta 2 and RC ON i386
[02:54] <valorie> which we didn't get
[02:54] <valorie> I had to do VMs
[02:54] <valorie> which is not ideal
[02:55] <valorie> I begged and begged
[03:04] <valorie> CoJaBo: it was running and passing on the alphas and maybe the first beta on actual i386 though
[06:15] <flocculant> valorie: just tried 32 bit kubuntu - vbox boots (eventually) from usb, starting to boot,  it just reboots machine here
[06:16] <valorie> :(
[06:16] <flocculant> yup not too good indeed
[06:16] <flocculant> thought I'd check it out
[06:16] <valorie> I'm gonna have to write to the kubuntu-users mail list
[06:17] <valorie> and ask for help from people with those older machines
[06:17]  * flocculant wanders back off to xubuntu world :)
[06:17] <valorie> gosh
[06:17] <valorie> because otherwise we aren't gonna put it out
[06:17] <valorie> non-working stuff shouldn't be released
[06:18] <flocculant> valorie: I'll just check xubuntu 32 bit - might be a *buntu thing - at that point of the boot we're likely much the same
[06:19] <valorie> flocculant: I would love to hear the results
[06:19] <flocculant> valorie: of course :)
[06:19] <flocculant> that's why I told you ;)
[06:20] <valorie> the flavors who want to provide this are sort of on our own now
[06:20] <flocculant> won't be doing more than trying to boot it - work soon ...
[06:20] <valorie> since Ubuntu has stopped building or distributing them anymore
[06:21] <flocculant> valorie: well - I'm sure that if it's been broken by ubuntu then they'll fix it
[06:22] <valorie> ::fingers crossed::
[06:28] <flocculant> valorie: well ... good news for you :(
[06:29] <valorie> broken for y'all as well?
[06:29] <flocculant> run out of time now - but this afternoon I'll dd the iso's instead of using gnome-disks
[06:29] <flocculant> yup
[06:29] <flocculant> I'll do that to check it's not the tool I used
[06:30] <flocculant> I'll also double check with an artful iso
[06:30]  * flocculant is Uk/UTC time
[06:30] <flocculant> valorie: I will ping you with what I find unless you ping me to say someone has worked it out
[06:30] <valorie> thank you, flocculant!
[06:31] <flocculant> np - always try to help other flavours when I can :)
[06:31] <valorie> finding out *what* the problem is would be good
[06:31] <flocculant> time to skedaddle now though
[06:31] <flocculant> valorie: ack :p
[06:31] <valorie> ciao and thanks again
[06:32] <flocculant> valorie: I'll try lubuntu as well - they'll jump up and down for weeks if 32 bit doesn't boot for them :D
[06:33] <valorie> :-)
[06:33] <valorie> so true
[06:33] <valorie> tsimonq2: ^^^
[06:48] <tsimonq2> ack
[08:14] <gnomethrower> hey guys
[08:14] <gnomethrower> if I installed a daily build of +1 about a week ago
[08:14] <gnomethrower> can I update all the packages and be current, or do I need to redownload?
[08:15] <gnomethrower> and reinstall
[08:15] <gnomethrower> sorry if that's a stupid question
[08:15] <tsimonq2> Nope, just update the packages and you'll continue to be on the daily
[08:15] <gnomethrower> tsimonq2: Perfect, thank you :)
[08:15] <tsimonq2> The ISOs are provided for your convenience ;)
[08:15] <tsimonq2> No problem gnomethrower :)
[08:15] <gnomethrower> I love LTS releases :D
[08:16] <gnomethrower> for some reason they excite me much more than regular ones
[08:16] <gnomethrower> I guess because as a sysadmin it means new toys...
[08:17] <tsimonq2> :D
[08:18] <gnomethrower> whoa... clicking the help icon really slowed my computer
[08:18] <tsimonq2> You just on stock?
[08:18] <gnomethrower> yeah
[08:18] <gnomethrower> January 5th build
[08:18] <gnomethrower> thus my questions ;)
[08:18] <tsimonq2> I really highly suggest making sure your system's up-to-date and filing a bug
[08:19] <gnomethrower> I doubt I can repro
[08:19] <tsimonq2> ("build" is irrelevant, just make sure your system's current with updates :) )
[08:19] <tsimonq2> You sure?
[08:19] <tsimonq2> Try :D
[08:19] <gnomethrower> I am :P
[08:19] <gnomethrower> Nope, all is good.
[08:20] <tsimonq2> huh
[08:20] <tsimonq2> Weird :)
[08:20] <gnomethrower> I was updating packages at the same time
[08:20] <gnomethrower> so my theory is that I opened it while a package related to it was being updated
[08:22] <tsimonq2> huh
[08:22] <tsimonq2> weird :)
[08:22] <gnomethrower> Anyways
[08:23] <gnomethrower> Feels pretty snappy and the UI is decent
[08:23] <gnomethrower> I pretty much gave up on stock when Unity came out, I'm afraid
[08:23] <gnomethrower> been running a frankensystem, Cinnamon running on Ubuntu 16.04
[08:23] <gnomethrower> but hoping to give the stock desktop another try
[08:24] <tsimonq2> Have you tried any of the flavors?
[08:25] <gnomethrower> Like Kubuntu and Xubuntu?
[08:25] <gnomethrower> I hate KDE, dislike XFCE, tolerate LXDE... :P
[08:26] <tsimonq2> When's the last time you've tried all of these? :)
[08:27] <tsimonq2> And have you tried LXQt?
[08:29] <gnomethrower> Admittedly a few years back
[08:29] <gnomethrower> and I haven't actually heard of LXQt, might give it a try
[08:29] <gnomethrower> honestly Cinnamon has worked so well for me that I've just stuck with it
[08:29] <tsimonq2> ¯\_(ツ)_/¯
[08:29] <tsimonq2> To each their own
[08:29] <gnomethrower> but I don't want to run Linux Mint (various reasons) and Cinnamon on Ubuntu is slightly buggy
[08:29] <gnomethrower> so I'm open to exploring the flavours more
[08:29] <tsimonq2> Ok cool :D
[08:35] <gnomethrower> Huh!
[08:35] <gnomethrower> Budgie actually looks cool
[16:54] <flocculant> valorie tsimonq2 - did some testing, reported crtitical fails on Live Sessions for Kubuntu, Lubuntu and Xubuntu - bug 1744357
[16:55] <flocculant> following up with Mate and Budgie now
[17:01] <flocculant> tsimonq2: bit nasty for sure - and I know Lubuntu would hate it - some of Xubuntu would too, I'm *shrug* about 32 bit tbh
[17:02] <flocculant> just dd'ing Mate - that zsynced first :D
[17:07] <flocculant> mmm - redoing dd - different error with Mate
[17:07] <flocculant> at least it said something
[17:13] <flocculant> funnily enough - since all the bios hoohaa we've all gone through, I've noticed that now when I F12 for boot menu - it responds a whole lot faster than it did before
[17:35] <flocculant> if anyone's following - and wonders what happened to Mate and Budgie - they faired no better ...
[17:40] <TJ-> flocculant: what's the error though?
[17:41] <flocculant> TJ-: other than none of them booting - and just rebooting the machine - no idea
[17:41] <TJ-> flocculant: best to capture the boot console via a VM
[17:44] <flocculant> TJ-: probably - someone else can do that if it's needed
[17:48] <tsimonq2> heh
[17:54] <flocculant> I see tsimonq2 volunteered then :p
[17:55] <tsimonq2> nooooooooo
[17:55] <tsimonq2> :)
[17:55] <flocculant> :)
[17:55] <flocculant> bbl
[20:00] <CoJaBo> flocculant: have you tested with the Plasma beta PPA yet, in Kubuntu on 32bit? Mine won't boot either, wondering if I should try that as a next step..
[20:02] <CoJaBo> (not sure if it's hanging at the same point tho; mine bails right before it gets to the desktop, where Plasma segfaults)
[20:04] <flocculant> CoJaBo: not at all - I've actually no real interest in kubuntu - I do xubuntu and am in the xubuntu team, I got involved because not only does the kubuntu 32 bit iso fail - so does xubuntu, and in fact all those I checked out
[20:04] <flocculant> sorry for you thinking I was using kubuntu
[20:23] <flocculant> valorie tsimonq2: awesome - didn't think about vm's ... mostly because it's usually MY VM fails :( ... works on hardware
[20:24] <valorie> I don't have quite the knowledge to do such a test and get good logs
[20:24] <valorie> should learn -- would welcome docs on how to do that
[20:25] <valorie> no time for a few days to do that though
[20:25] <flocculant> oh right docs ...
[20:25] <flocculant> if you find them - please tell me where :D
[20:26] <flocculant> valorie: anyway - upshot is we boot in vm, not on hardware
[20:26] <valorie> right, I did all my artful testing on my travel laptop, which is not powerful enough for a vm
[20:27] <flocculant> valorie: did you try not virtualbox ?
[20:27] <valorie> I didn't
[20:27] <flocculant> I use kvm a(which you can do from a terminal) and virt-manager which is a gui front-end
[20:28]  * flocculant digs out the old wiki page
[20:28] <flocculant> https://help.ubuntu.com/community/KVM/Installation
[20:29] <valorie> I've made VMs before, although not kvm
[20:29] <valorie> but I don't know the bit about fetching the logs when the boot fails
[20:29] <nacc> virt-manager is the easiest way (IMO) to test install off an ISO
[20:29] <flocculant> and from a terminal - a dead simple boot an iso line I use is, for instance "kvm -m 2048 -cdrom /mnt/Data/iso/18.04_Other/Kubuntu/bionic-desktop-i386.iso"
[20:29] <nacc> and or that :)
[20:29] <valorie> thanks for that
[20:30] <flocculant> nacc: yup - though I'm finding that very very slow with bionic iso's atm - bug report on lp for stuff I find
[20:30] <flocculant> valorie: np - just ask :)
[20:30] <valorie> ok, then what if it fails?
[20:31] <valorie> how does one get the log?
[20:31] <nacc> flocculant: ah i haven't tested that specifically
[20:31] <flocculant> nacc: I actually prefer to gui it :) but I have a script to zsync my iso's, do some copying etc and then run those lines quickly
[20:32] <valorie> I mean I always try to file bugs via cli if possible
[20:32] <flocculant> valorie: which log?
[20:32] <valorie> "TJ-> flocculant: best to capture the boot console via a VM "
[20:33] <valorie> and I assume associated logs?
[20:33] <nacc> kvm/qemu do log somewhere, iirc
[20:33] <flocculant> oh right - not sure tbh, but I think this is too soon to even do that, can't remember the new-fangled way to get the same as ye olde text boot
[20:34] <nacc> there is also, iirc, a flag to qemu/kvm to log the serial console to a file
[20:34] <flocculant> nacc: this is stuff I've never needed - so hence ... ;)
[20:34] <nacc> flocculant: :)
[20:35] <flocculant> perhaps in /var/log/libvirt/qemu/
[20:35] <valorie> like doing pastebinit ?
[20:35] <nacc> flocculant: only if using libvirt :)
[20:35] <flocculant> nacc: not a clue - I followed the wiki page I gave valorie :D
[20:37] <flocculant> sigh
[20:37] <flocculant> friday evening - and after all this mucking about - no beer :(
[20:37] <flocculant> and it's raining
[20:41] <flocculant> nacc: this stuff? https://help.ubuntu.com/lts/serverguide/libvirt.html
[20:41] <nacc> flocculant: i just ment that libvirt qemu logs only apply to libvirt qemu instances )
[20:42] <flocculant> yea realised that, but if I did it that way I assume I'd see logs (though I did have some in ^^ so I assume at some point ...)
[20:42] <nacc> yeah
[20:43] <flocculant> mmmm - might look into that a bit then (tomorrow :D)
[20:43] <flocculant> I hate not being able to give as much info as I can on a bug report like this
[20:44] <flocculant> that said infinity is looking :D
[20:44] <TJ-> flocculant: here's an article I wrote about 10 years ago on how to use qemu/kvm to capture console to a log file http://tjworld.net/wiki/Linux/KvmQemuSerialMonitor
[20:44] <flocculant> nacc: oh yea - usually the other way around for me - but it's hardware failing this sime :D
[20:45] <nacc> flocculant: fun :)
[20:45] <flocculant> TJ-: awesome - I WILL read it, but I've been up since 0500 utc and it's almost 2100 on a Friday night :)
[20:45] <flocculant> more for tomorrow :)
[20:46] <TJ-> flocculant: same here :)
[20:46] <flocculant> right now - I'm off to the shop :D
[20:46] <flocculant> with a hat on ...
[20:49] <valorie> thanks to y'all for the above info!


[03:28] <iluminator105> has anyone installed ubuntu on asus zenfone 2
[07:00] <dholbach> good morning
[07:04] <sturmflut-work> dholbach: Morning!
[07:06] <dholbach> hi sturmflut2
[07:19] <mcphail> lotuspsychje: we were talking yesterday about the volume slider not working for OpenAL apps. I created a test app, and the volume slider, silent mode, backgrounding the app or switching off the screen cannot silence it:  http://themcphails.uk/altest.njmcphail_0.1_armhf.click
[07:21] <davidcalle> Good morning all
[07:29] <liuxg> I have defined a property in one QML element. I find that in some cases, I can refer to it without using the id, but in some cases, I have to refer to it by using the id. Does anyone know what are the differences?
[07:52] <nerochiaro> oSoMoN: good morning. in case you have not seen it, i pushed this yesterday: https://code.launchpad.net/~uriboni/webbrowser-app/keyboard-navigation/+merge/260183
[08:01] <tsdgeos> oSoMoN: any idea about https://bugs.launchpad.net/oxide/+bug/1459142 ?
[08:35] <JamesTait> Good morning all; happy Senior Health & Fitness Day! 😃
[09:06] <folf> /msg NickServ help
[09:06] <folf>
[10:57] <mpt> seb128, it needs design review, but I’ve just completed a draft of the display settings for pocket PC. <https://wiki.ubuntu.com/BrightnessAndDisplays?action=diff&rev2=23&rev1=19>
[10:57] <seb128> mpt, thanks
[10:57] <mpt> Let me know if you spot any huge mistakes :-)
[10:59] <mandel> ogra_, have we changed the way we write the logs from daemons started via upstart?
[11:00] <mandel> ogra_, I'm starting location and /var/log/ubuntu-location-service.log is not created.. I'm very puzzled
[11:03] <ogra_> mandel, we added a workaround for the boot loop issue ... which results in upstart not logging any system job output ... the upstart fix has landed but the kernel cmdline option to enable logging again has not been dropped yet
[11:04] <ogra_> mandel, ondra shold know when it is planned to be dropped
[11:04] <mandel> ogra_, Iyou just made me swear in spanish, so that you know it
[11:04] <ogra_> do you swear in other languages usually ? :)
[11:04] <mandel> ogra_, making me got crazy for the last hours or so.. ok I'll do a workaround for my tests
[11:05] <mandel> ogra_, yes, in german.. Kartoffelkloesse!!!!!!!!!!!
[11:05] <ogra_> lol
[11:05]  * ogra_ can see how "Potato Dumplings" might be a swear word for some :)
[11:07] <seb128> mpt, k, looks good from a first glance but the "what to display on the external monitor" is a bit tricky, you drafted an UI that looks like the current desktop UI, but we can't really use that, we are going to need to add a desktopUI mode to the phone settings ... should we use the exact same design than on the desktop?
[11:08] <mandel> ogra_, that is ofcourse in all devices, right? or can I grab another one?? Although I need to test a specific one.. :-/
[11:10] <ogra_> mandel, technically only bq
[11:11] <mandel> ogra_, sweet, thx
[11:11] <ogra_> i'm not sure if ondra somehow applied it to other devices too
[11:22] <mpt> seb128, I just asked around, and the short answer is, nobody knows
[11:23] <seb128> mpt, k :-/
[11:39] <joc_> davmor2: ping
[11:39] <davmor2> joc_: what
[11:40] <joc_> davmor2: you know if there is an "owner" of the pages at https://wiki.ubuntu.com/Process/Merges/TestPlan/...
[11:41] <joc_> davmor2: wondered if could get some notes on debugging Bluetooth issues put up there
[11:41] <davmor2> joc_: it's not a page as far as I know it's just a way to search other pages
[11:42] <davmor2> joc_: bluetooth I this is covered in 2 parts the indicator and then system-settings
[11:43] <joc_> davmor2: yep, so for instance the location-service page has a section about debugging things
[11:43] <joc_> davmor2: could we have a similar section for Bluetooth stuff on one of these pages - can then refer people filling bugs to that for instructions
[11:44] <davmor2> joc_: it's a wiki ;)
[11:45] <davmor2> joc_: I don't know who works on bluetooth now, but the pages were written by the devs.  So they would be the people to talk to I guess
[11:46] <joc_> davmor2: hmm thought i didnt have permissions to edit, but appears i do :)
[11:46] <davmor2> joc_: haha :)
[11:46] <dholbach> fgimenez, brendand:  do you plan to upload a newer selenium to the archive?
[11:49] <fgimenez> dholbach, yes, we have that in our backlog
[11:49] <fgimenez> dholbach, we are trying to move it forward in debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770232
[11:51] <fgimenez> dholbach, if it doesn't work we would try to upload a new version to the archive
[11:53] <dholbach> brilliant, thanks
[12:01] <brendand> fgimenez, in tnt's backlog?
[12:02] <fgimenez> brendand, don't know about tnt :) i mean this card https://trello.com/c/LOJr6jU5/166-push-python3-selenium
[12:03] <brendand> fgimenez, ok i just wonder if anyone is still using it - maybe tnt have taken ownership
[12:03] <brendand> fgimenez, better ask jfunk
[12:03] <dholbach> fgimenez, do we know folks in Debian who can help getting the patch in?
[12:04] <dholbach> fgimenez, it looks like the package didn't see an update since 30 Jul 2011
[12:04] <fgimenez> brendand, yep, zigo is at it
[12:04] <dholbach> oh ok
[12:04] <dholbach> ah no, that was meant for brendand
[12:04] <fgimenez> dholbach, no, sorry, was for you ;)
[12:05] <dholbach> ok, excellent
[12:05] <dholbach> thanks a bunch fgimenez and friends! :)
[12:38] <dholbach> is changing to development mode broken for anyone else?
[12:42] <ogra_> dholbach, broken in what way ?
[12:44] <dholbach> ogra_, I tried to change to developer mode, so I picked a PIN number and after confirming the number it said "can't change to security number" (or something along those lines)
[12:44] <ogra_> ah, thats not a developer mode issue then, phew
[13:31] <czajkowski> I'm having a bit of a moment here with the Bq phone trying to share multiple images to FB or to twitter, but it will only let me select one.  Also no way to share via email
[13:31] <czajkowski> is this right ?
[13:31] <ogra_> czajkowski, patches welcome :)
[13:32] <ogra_> (i think multi selection isnt possible yet, please file a bug ... )
[13:32] <czajkowski> ogra_: I'm just checking this is the expected outcome :)
[13:33] <ogra_> tedg, ^^^ should content-hub already be able to do multi select transfers ?
[13:33]  * ogra_ bets he mixed up kenvandine and tedg again ... i always do that if it comes to that sharing SW ...
[13:33] <kenvandine> haha
[13:34] <kenvandine> yes you can do multi select transfers
[13:34] <ogra_> ah, probably the app cant then ...
[13:34] <czajkowski> kenvandine: ohh
[13:34] <kenvandine> czajkowski, but the app can't :)
[13:34] <czajkowski> *mutters*
[13:34] <czajkowski> which app the gallery  on the phone ?
[13:34] <ogra_> facebook ...
[13:34] <czajkowski> kenvandine: also how are you :)
[13:35] <czajkowski> ogra_: this is from the gallery I've seleted 3-4 pics and click share
[13:35] <czajkowski> share refuses to work
[13:35] <kenvandine> gallery doesn't have multi-select share UI and the facebook webapp doesn't allow multiple yet
[13:35] <kenvandine> oh... it does have that?
[13:35] <kenvandine> cool
[13:35] <kenvandine> so it's just the facebook webapp that isn't handling multi
[13:35] <ogra_> czajkowski, yeah, the FB app refuses then ...
[13:35] <czajkowski> lol so not me going insane
[13:35] <czajkowski> ogra_: aye saw that on the app
[13:35] <czajkowski> but figured I could at lest share multiple pics to mail
[13:36] <ogra_> just go and convince that zuckerberg guy to support ubuntu ;)
[13:36] <kenvandine> czajkowski, so file a bug against the facebook webapp
[13:36] <czajkowski> one way to get themj off the phone and to G+ :D
[13:36]  * kenvandine tries to remember the project
[13:36] <czajkowski> ogra_: it's not to FB I want them, it's to my email
[13:36] <ogra_> ah
[13:36] <kenvandine> webapps-core project on LP
[13:36] <kenvandine> oh
[13:37] <kenvandine> we don't have a share handler for the gmail webapp yet
[13:37] <czajkowski> sorry wasn't clearer, it's been a long few days
[13:37] <ogra_> whio uses that anyway
[13:37] <czajkowski> ogra_: me!
[13:37] <ogra_> use dekko !
[13:37] <kenvandine> but... it should support multi-select if you try to pick from the gmail webapp to add an attachment
[13:37] <czajkowski> ahhhh
[13:37] <czajkowski> lemmie try that
[13:37] <czajkowski> plan B
[13:38] <mcphail> Any idea against which package I should file a bug about the volume controls not working for apps using OpenAL?
[13:38] <ogra_> mcphail, did you try out a fully confined app with OpenAL ?
[13:38] <ogra_> it shouldnt be able to play any sound at all
[13:38] <ogra_> unless it routes through pulse
[13:39] <mcphail> ogra_: if you give access to "audio" you can play, even when screen is off
[13:39] <ogra_> else there is a security bu i'd say
[13:39] <ogra_> jdstrand, ^^^ should apps be able to directly access audio HW ?
[13:40] <CoZo_> poukram j arrive pas a modifié sur jamendo
[13:40] <CoZo_> ce site est compliqué a utiliser pour les zicos ;o)
[13:40] <mcphail> ogra_: http://themcphails.uk/altest.njmcphail_0.1_armhf.click
[13:40] <ogra_> mcphail, i belive you that it works ... :)
[13:40] <mcphail> ogra_: sound will still play when backgrounded, screen off or silent mode
[13:40] <CoZo_> oups chan error sorry
[13:40] <popey> confirmed this
[13:40] <ogra_> just trying to find out if it is a security hole ... looks to me like it is
[13:41] <popey> hadn't considered it might be a security issue
[13:41] <ogra_> apps should not be able to directly access any hardware
[13:41] <ogra_> which i guess OpenAL does here
[13:41] <popey> mcphail: file a bug against apparmor maybe?
[13:41] <czajkowski> kenvandine: ogra_ Plan B works!
[13:41]  * ogra_ hugs czajkowski
[13:41] <mcphail> popey: was thinking the fact it plays despite backgrounding might be because there is no graphical UI. App stays on splash screen
[13:41] <czajkowski> although I think I just crashed the phone
[13:42] <czajkowski> *mutters*
[13:42] <ogra_> i guess you used up all rem
[13:42] <ogra_> *ram
[13:42] <czajkowski> yeah it's now hung
[13:42] <czajkowski> and unresponsive
[13:42] <ogra_> (though that should only kill apps, not the phone)
[13:43] <czajkowski> ogra_: I'm special with my phone
[13:43] <czajkowski> I can kill it
[13:43] <ogra_> well, leave it for a moment ... might just be apparmor collecting stuff
[13:43] <ogra_> err
[13:43] <ogra_> apport
[13:46] <popey> mcphail: maybe file it at https://launchpad.net/ubuntu/+source/apparmor/+bugs and poke jdstrand :)
[13:46] <popey> I'll confirm
[13:47] <mcphail> popey: will do
[13:47] <popey> ta
[13:49] <czajkowski> ogra_: 4 pics is the max
[13:49] <czajkowski> at least I know this now
[13:49] <czajkowski> cheers for he tip kenvandine
[13:49] <kenvandine> np
[14:02] <mcphail> popey: I (possibly mistakenly) reported it as a security problem, which makes the bug private by default. Do you think I should switch it to public?
[14:02] <popey> i would
[14:02] <popey> then give us the bug number
[14:03] <peat-psuwit> awe: How can radio-settings notify ofono core that technologyPreference has been changed?
[14:03] <mcphail> https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1459259
[14:04] <popey> thanks
[14:04] <mcphail> popey: cheers
[14:08] <awe> peat-psuwit, take a look at rilmodem/radio-settings.c
[14:08] <awe> pretty sure there's no asynchronous way to do this.  The core queries the driver, which responds with the pref
[14:15] <sturmflut2> Oh wow. The Document Viewer now supports SD cards and renders PDF documents at lightning speed! Who do I have to thank for this?
[14:17] <jgdx> sturmflut2, Stefano Verzegnassi for sd it seems.
[14:17] <peat-psuwit> awe: I can't find such code.
[14:18] <awe> peat-psuwit, what exactly are you trying to do?
[14:18] <sturmflut2> jgdx: Thanks!
[14:19] <awe> if you're talking about RadioSettings::TechnologyPreference
[14:19] <awe> my point was that the driver notifies the core, only when the core makes a query
[14:19] <awe> it's not event-based
[14:19] <awe> and the code that handles these queries is in rilmodem/radio-settings.c
[14:19] <peat-psuwit> awe: If someone set TechnologyPreference to 3G in one sim, TechnologyPreference for another sim have to change.
[14:20] <awe> sure, and I explained to you that you'd need to implement some kind of mechanism in your device plugin
[14:20] <awe> eg. if the user sets a pref for SIM1, then you'd need to catch this and call into the device plugin to handle changing the pref for the other SIM
[14:21] <awe> again, we do similar things for handling GPRS 'Attached'
[14:21] <awe> please take a look at the mtk device plugin, and the mtkmodem gprs code for an example
[14:21] <peat-psuwit> I see in src/radio-settings.c that this settings is cached. I can't see how I can make it uncache and re-query radio settings driver.
[14:26] <awe> peat-psuwit, so the rates supported by the modem aren't supposed to change.  I believe the way this works in the MTK impl is that the modem is restarted when the 3g capability is switched from one modem to the other
[14:26] <awe> abeato, ^^ can you confirm?
[14:26] <awe> peat-psuwit, I never promised this was easy...
[14:26] <awe> ;)
[14:27] <peat-psuwit> awe: And I never thing it is.LOL
[14:33] <abeato> peat-psuwit, so for your dual SIM phone, you can have 3G only for one of the slots?
[14:33] <peat-psuwit> abeato: Yes.
[14:34] <jgdx> abeato, awe, when nuntium sees a preferred Internet context with MMSC, does it treat it as a preferred MMS context?
[14:34] <abeato> jgdx, yes
[14:35] <jgdx> abeato, great, thanks
[14:35] <abeato> peat-psuwit, ok, interesting... first thing, note that TechnologyPreference is not about changing the slot with 3G capabilities, but about forcing the modem to register for a certain technology
[14:35] <awe> jgdx, so does my original reply make sense now?
[14:36] <awe> abeato, I think we were mixing ModemTechnologies and TechnologyPref
[14:36] <abeato> peat-psuwit, so you want something different... in the case of MTK modems we created a specific DBus interface to handle swithcing the slot with 3G caps
[14:36] <awe> abeato, the modem does indeed cache the ModemTechs
[14:36] <jgdx> awe, yes sir
[14:36] <awe> s/the modem/ofono/
[14:37] <awe> abeato, the modem he's working with only allows one modem to have 3g
[14:37] <awe> ( sound familiar )
[14:38] <awe> and he needs to implement something similar to our attach logic
[14:38] <mpt> seb128, I just hung System Settings by tapping the Back button. This time it’s still running. What can I do to debug it?
[14:38] <awe> where radio-settings would notify the device plugin, and cause the other modem to set it's pref to 2g
[14:38] <seb128> mpt, https://wiki.ubuntu.com/Backtrace#Already_running_programs
[14:39] <mpt> thanks
[14:39] <abeato> awe, right, that's what I am trying to explain
[14:39] <mpt> (I’m assuming all that works on the phone too)
[14:39] <abeato> peat-psuwit, check doc/mtk-settings-api.txt
[14:40] <abeato> peat-psuwit, awe there is a property called Has3G, when set it resets the modem to change the slot that has 3G caps
[14:40] <awe> abeato, this causes a modem reset, correcT?
[14:40] <abeato> peat-psuwit, take a look at the implementation you might need something similar, bit for rilmodem
[14:40] <abeato> awe, yes
[14:41] <awe> abeato, which then causes the ofono core to re-query the supported rates
[14:41] <awe> peat-psuwit, does that make sense ^^
[14:41] <abeato> awe, right
[14:41] <abeato> peat-psuwit, for MTK changing the slot with 3G needs a modem reset, don't now if it is the same for qualcomm modems
[14:41] <peat-psuwit> abeato: my modem doesn't reset when this setting is changed.
[14:42] <abeato> peat-psuwit, then it should be easier ;)
[14:42] <awe> peat-psuwit, OK, that's good news.  That said, you might leverage the Set3G work still... just minus the reset logic
[14:42] <abeato> peat-psuwit, but in any case you need something specific for your driver
[14:42] <awe> +1
[14:42] <abeato> peat-psuwit, a specific DBus interface as we did for MTK
[14:43] <abeato> peat-psuwit, note that this is very device-dependent... as you see for MTK a reset is needed, in your case is not
[15:06] <peat-psuwit> abeato: When a value is set on a modem, should ModemTechnologies change? How about TechnologyPreference?
[15:07] <abeato> peat-psuwit, TechnologyPreference tells the modem the preferred radio technology, to force, for instance, using 2G instead of 3G
[15:07] <peat-psuwit> abeato: s/a value/the has3G property/
[15:07] <abeato> peat-psuwit, ModemTechnologies is the list of avialable technologies for that modem
[15:07] <abeato> it is supposed to be kind of static
[15:08] <abeato> peat-psuwit, a very different thing is to change the slot with *3G capabilities*
[15:08] <abeato> peat-psuwit, in the case of MTK that is set with Has3G
[15:08] <abeato> peat-psuwit, as a modem reset is needed, most ofono atoms are restarted
[15:09] <abeato> peat-psuwit, and ModemTechnologies changes to reflect the change on slot with 3G caps
[15:09] <abeato> peat-psuwit, to be cleat ModemTechnologies has the set of values that TechnologyPreference can have
[15:10] <peat-psuwit> abeato: If one modem has 3G capabilities, another modem can't has umts in ModemTechnologies
[15:10] <abeato> peat-psuwit, correct
[15:10] <abeato> (well, if the modem has that limitation obviously)
[15:11] <peat-psuwit> abeato: On MTK, that happens when the modem is reset. When should it happen in my case.
[15:12] <abeato> peat-psuwit, what I am trying to say is that we do *not* use TechnologyPreference to change the current capabilities of the slot: we thought about that, but taking into account that it was very specific to our hardware we implemented the MtkSettings interface
[15:13] <peat-psuwit> abeato: I mean, how should ModemTechnologies be changed?
[15:14] <abeato> peat-psuwit, it should reflect which radio techs you can register to without affecting the other slot... maybe that works as a definition for you
[15:30] <peat-psuwit> abeato: As ModemTechnologies should be static, then modem should restart when 3G capabilities change, right?
[15:33] <abeato> peat-psuwit, well for MTK it was the case... do not take this as something you necessarily must do the same way. Maybe in your case ModemTechnologies could be always 2G,3G for both slots, and when you set TechPreference to 3G for slot 1, slot 2 notices, changes TechPreference and  emits a PropertyChanged signal
[15:34] <abeato> peat-psuwit, if you do not need to reset that's what I would do
[15:35] <peat-psuwit> abeato: That is my initial plan. But I'm finding the way to "changes TechPreference and  emits a PropertyChanged signal"
[15:35] <abeato> peat-psuwit, what you certainly need to do is to enable some communication mean between the driver instances for each of your slots, probably using your modem plugin
[15:36] <abeato> peat-psuwit, take a look to mtk.c:mtk_set_attach_state
[15:36] <abeato> peat-psuwit, it solves a similar communication issue
[15:36] <abeato> peat-psuwit, and mtk_detach_received
[15:37] <abeato> basically you call them from a driver atom instance, then the plugin calls the other driver atom instance
[15:54] <peat-psuwit> abeato: Well, in that case, when the sim data service is enabled, another sim data service will be disabled too.
[15:56] <abeato> peat-psuwit, yep, for MTK we could have only one modem attached at a time... but again I pointed this out as an example of how to do communication between different driver instances
[15:56] <abeato> peat-psuwit, ymmv
[15:56] <peat-psuwit> abeato: I have the plan for that now.
[15:57] <peat-psuwit> abeato:  I'm finding the way to change TechnologyPreference in dbus.
[15:57] <abeato> peat-psuwit, great, looking forward to see the patches ;)
[15:59] <peat-psuwit> abeato: What I'm finding is how notify radio-settings atom when TechnologyPreference changes.
[15:59] <peat-psuwit> s/how/how to/
[16:51] <jgdx> seb128, thanks!
[16:59] <seb128> jgdx, yw!
[17:00] <brunch875> Ugh I wonder if the IRC protocol needs to be revitalized
[17:27] <brunch875> damn
[17:27] <brunch875> Project ERROR: Unknown module(s) in QT: declarative
[17:27] <brunch875> qtdeclarative5-dev
[17:28] <brunch875> is installed, what could be the issue?
[17:42] <brunch875> AH it seems to be deprecated... I wish there were more recent tutorials laying around :/
[18:19] <Guest29395> Hello there, is there anyone here I can ask about installing Umbuntu for the first time over a previous Windows install?
[18:20] <k1l_> on a smartphone or desktop/laptop?
[18:21] <Guest29395> On a desktop PC (64 bit) with either Windows 8 or 7. We want to go Linux, but are nervous as we've never left Windows behind before. We already use LibreOffice for every doc/spreadsheet but use Windows Live mail for e-mail.
[18:23] <k1l_> Guest29395: ok, then better come to #ubuntu to ask there. this here is the ubuntu-touch channel which is more smartphone focused right now.
[18:23] <Guest29395> OK, which URL link should I go to?
[18:23] <Guest29395> Sorry, if I landed in the wrong place
[18:24] <k1l_> Guest29395: and best way is to make live usb ubuntu to start that ubuntu from that usb wihtout touching the disk. so you can have a look and test.
[18:24] <k1l_> Guest29395: /join #ubuntu
[18:24] <k1l_> then you will come to the channel #ubuntu. or (depending on your irc client you use) click on the #ubuntu
[18:24] <Guest29395> So we shouldn't make a bootable DVD? As discussed here: http://www.ubuntu.com/download/desktop/burn-a-dvd-on-windows
[18:25] <k1l_> Guest29395: i prefer to use a 2-4GB usb pendrive
[18:25] <k1l_> but dvd would work too
[19:08] <jdstrand> I changed channels from 14.09 to rc-proposed and now I have two music-app entries in the apps scope-- one has no icon and doesn't work, one does have an icon and does work. possibly related, if I pin the music-app to the launcher, it doesn't have an icon, but it works
[19:09] <ahayzen> jdstrand, i've had that happen before when sideloading the music-app not sure what caused it lol
[19:10] <jdstrand> I did sideload the music-app back when a call for testing went out for the new one
[19:10] <jdstrand> I forgot about that
[19:10] <jdstrand> ok, this is probably a local thing then that I can figure out
[19:10] <jdstrand> ahayzen: thanks!
[19:10] <ahayzen> sometimes i think it can get confused and just removing all of them and reinstalling from the store seemed to resolve it
[19:11] <jdstrand> yeah, that is what I was thinking
[19:11] <jdstrand> I was concerned that ota4 might be affected by something more serious, but now I doubt it
[19:53] <yak_> hello everybody, I'm trying to connect my ubuntu touch on my hotspot I created on my ubuntu desktop, but it doesn't work :( have you any idea why?
[19:53] <yak_> I'm on the aquaris E4.5
[19:54] <yak_> my computer is connected on ethernet
[19:56] <davmor2> yak_: might be an issue on the computer does anything else connect to the hotspot?
[19:56] <yak_> no
[19:57] <yak_> I didn't try
[19:57] <yak_> maybe I could try connecting another smartphone to test it
[19:58] <davmor2> yak_: I would try that first, if that fails it then I guess the hotspot isn't working as expected.  It would lower down to a piece of hardware
[20:08] <yak_> I try on  an old android smartphone and it doesn't detect the hotspot. Maybe it's the version, I will try with the other one. But I already done it before with this computer. I think it's the software...


[00:09] <alkisg> stgraber: https://bugs.launchpad.net/ltsp/+bug/979472
[07:59] <stgraber> alkisg: ouch, yeah, that code was indeed quite wrong, thanks for fixing
[08:04] <alkisg> stgraber: if vagrantc uploads LDM today, should I sync it, or leave it up to you?
[08:06] <stgraber> alkisg: you can sync it, I'll let it through the queue as it's critical for LTSP
[08:17] <alkisg> stgraber: once Precise is out, would you mind me pushing many changes to ltsp-upstream, such as e.g. the ltsp-pnp code?
[08:18] <stgraber> should be fine, we'll have enough time to make it all look good before 12.10
[08:19] <alkisg> Right, and whenever sbalneav has libpam-ssh* ready, we can move towards LTSP 6, without LDM.
[08:20] <alkisg> (that one for 13.04 probably/hopefully though)
[08:21] <stgraber> yeah
[09:03] <stgraber> alkisg: are you planning another epoptes upload today (for translations) or are you good for 12.04?
[09:03] <alkisg> stgraber: no I'm good, one translation has been committed after last release, but I don't want to bother vagrantc again
[09:05] <alkisg> Eh actually it's 3 new translations... hmm, no not worth it, they came too late :)
[09:07] <stgraber> k
[09:07] <alkisg> Wow, epoptes has been translated to 26 languages before even its first official release... a good sign that such a program was actually needed.
[10:43] <alkisg> stgraber: will X51-opengl break opengl for fat clients when the user happens to have LDM_DIRECTX=True ?
[10:44] <alkisg> Maybe we need to check for fat clients setup there too?
[10:44] <stgraber> it shouldn't break all of opengl but it'd likely break unity at least
[10:44] <stgraber> so yeah, adding a check for fat client would make sense
[10:44] <alkisg> OK, doing so...
[10:44] <stgraber> there's no reason to set that variable when running something locally
[10:45] <alkisg> Unfortunately we can't separate localapps from normal remote apps
[10:45] <stgraber> can't we?
[10:45] <stgraber> we could unset the variable in the localapps script
[10:46] <alkisg> Yes, we could do that
[10:46] <alkisg> I meant from that X51 script
[10:46] <stgraber> right
[10:46] <alkisg> Hmmm actually... I'm not sure if that's needed
[10:46] <alkisg> Localapps don't have the same env as the server apps, do they?
[10:47]  * alkisg checks
[10:47] <stgraber> they don't need to indeed, but I'm not completely sure that they don't ;)
[10:47] <alkisg> (btw unity is indeed broken, a black overlay on top of the usable area)
[10:49] <stgraber> do you have the latest ldm?
[10:49] <stgraber> the black overlay was caused by xcompmgr last I checked
[10:50] <alkisg> I have the latest precise updates, but I didn't compile anything or use a ppa... /me checks...
[10:50] <alkisg> Ah yeah
[10:50]  * alkisg puts DISABLE_XCOMPMGR=True in lts.conf...
[10:51] <stgraber> isn't off by default now?
[10:51] <alkisg> We didn't do an ldm release, did we?
[10:51] <stgraber> I think we did (2.2.8)
[10:52] <stgraber> oh, or not
[10:52] <stgraber> nevermind
[10:52] <stgraber> or maybe we did ... /me updates the branches
[10:52] <alkisg> In http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ldm-trunk/changes I see that we needed one after r1429, and we didn't
[10:53] <stgraber> right, we didn't :) we really need vagrant to do it then
[10:53] <alkisg> OK I'll put the fat client check in x51 and ask vagrantc if I see him
[10:53] <stgraber> I dropped xcompmgr from depends in ltsp-client-core with the latest ltsp release but that only works for new chroots, not for updated ones
[10:53] <alkisg> Right I have an updated one
[12:38] <mgariepy> good morning everyone
[13:06] <highvoltage> good morning
[14:11] <highvoltage> edubuntu-live (12.04.1) precise; urgency=low
[14:11] <highvoltage> * Update translations.
[14:11] <highvoltage> whohoo
[14:12] <highvoltage> stgraber: did the call for translations seem to help?
[14:13] <stgraber> highvoltage: yes
[14:13] <stgraber> highvoltage: we had an extra 4-5 languages and a lot of other changes
[14:13] <stgraber> highvoltage: https://translations.launchpad.net/ubuntu/precise/+source/edubuntu-live/+pots/edubuntu-live
[14:13] <highvoltage> nice.
[14:14] <stgraber> I'll check again next week and potentially re-update right before release week if it's worth it
[14:17]  * highvoltage should've done the Afrikaans one
[14:17] <highvoltage> (doing it now hoping it might still make it in with another update)
[14:17] <highvoltage> "gebruikerskoppelvlak". Afrikaans IT terms get way too long sometimes :)
[22:40] <droppy> How does a edubuntu LSTP fat client work?