[00:00] <moocow1452> cyphermox, is there anywhere else I should go with this, or keep on bugging you and the irc?
[00:01] <cyphermox> lines 262-265 are the issue
[00:02] <cyphermox> I think you're missing something in the files you added for your device
[00:02] <cyphermox> either as an include that is missing, or something else
[00:02] <cyphermox> AID_NET_RAW is undeclared
[00:02] <cyphermox> oh wait, is that a kernel thing?
[00:04] <moocow1452> Do I need to specify those in the kernel?
[00:06] <mhall119> Saviq: because you don't sleep, I'll ping you about this
[00:07] <mhall119> I got the new QML shell, and app search works, but the on screen keyboard lets press events fall through, so it'll select something under the keyboard when I try to search
[00:07] <Saviq> mhall119, flash your device
[00:07] <moocow1452> defconfig makes no reference to AID_NET_RAW. Should I try y'ing it in the kernel, or do I need a file transplant of some sort?
[00:07] <Saviq> mhall119, there were problems on the other side with keyboard recently
[00:07] <mhall119> dang, you really are awake?  What's the matter with you?
[00:08] <moocow1452> cyphermox?
[00:08]  * mhall119 phablet-flashes
[00:09] <Saviq> mhall119, fixing something we broke yesterday
[00:09] <moocow1452> anyone?
[00:09] <Saviq> mhall119, you did ask whether the SideStage hint is going to affect the phone...
[00:09] <Saviq> well it shouldn't, but it did :/
[00:10] <mhall119> oops
[00:13] <cyphermox> moocow1452: check kernel/wherever your kernel code is for encore/include/linux/android_aid.h
[00:13] <cyphermox> that file should be there and include AID_NET_RAW
[00:14] <cyphermox> so under kernel/bn/encore
[00:15] <mhall119> I hope the keyboard fix works on apps too, that was bugging me
[00:28] <mhall119> Saviq: image 56 doesn't fix the keyboard issue
[00:29] <Saviq> mhall119, hum, what's your steps? and on what device?
[00:29]  * Saviq tries image 56
[00:30] <mhall119> nexus 7 (grouper I think)
[00:30] <mhall119> /home/mhall/Downloads/phablet-flash/56/quantal-preinstalled-armel+grouper
[00:31] <geeknux> as you are saying about keyboard, i wonder is there any way to add another language to the keyboard?
[00:31] <mhall119> I go to dash, apps lens, press the search at the top and the keyboard comes up.  The R is above one of the installed apps (ebay in my case), so when I press R it registers the keyboard press, and also registers a press on the ebay launcher
[00:37] <bobweaver> ping Saviq
[00:38] <Saviq> mhall119, can't reproduce here
[00:39] <Saviq> mhall119, freshly flashed 56 on Galaxy Nexus
[00:39] <Saviq> bobweaver, hey
[00:41] <bobweaver> hello Saviq  how to make dafault satae of text edit String ? I know vague got time for gH ?
[00:42] <Saviq> bobweaver, E_SYNTAXERROR
[00:42] <bobweaver> lol
[00:42] <bobweaver> let me paste some code
[00:44] <bobweaver> http://pastebin.com/CXSyjxTh
[00:44] <bobweaver> line 10
[00:44] <bobweaver> tried to make into case still no good
[00:44] <bobweaver> can not figure it out
[00:47] <bobweaver> so if you lokk at video you can see that there i is missing soace in text so user can not click to edit
[00:47] <bobweaver> Saviq, http://www.youtube.com/watch?v=H05mT0jStgM
[00:48] <bobweaver> frontend info it is a component well kinda
[00:48] <bobweaver> model / delegant
[00:49] <bobweaver> that dumps sqlight data to local storage
[00:49] <Saviq> bobweaver, «DataBase.frontendPort1() !== "6547" || ""» looks wrong
[00:49] <Saviq> bobweaver, "" is always false
[00:50] <bobweaver> that is what I am talking about
[00:50] <bobweaver> so is NULL thwen false ?
[00:51] <mhall119> bobweaver: did you mean to do (DataBase.frontendPort1() !== "6547" || DataBase.frontendPort1() !== "") ?
[00:52] <bobweaver> also look at ip
[00:52] <bobweaver> http://pastebin.com/nffsBcbH
[00:52] <bobweaver> like to have default state that is there unless sqling ihas info
[00:52] <bobweaver> if DataBase.whatever = error then ....
[00:52] <mhall119> bobweaver: I've been using placeholderText on TextField to display something when the text input has no value
[00:53] <mhall119> then logic elsewhere to do the "right thing" when there is no specific value
[00:53] <bobweaver> mhall119,  yes user needs to be able to click info
[00:53] <bobweaver> if there is not String in the textedit feild then they can not clickaroo
[00:57] <Saviq> bobweaver, you shouldn't bind TextInput.text - the binding gets broken as soon as you enter anything in the field
[00:59] <bobweaver> But I dont care about that allI care about is if sqllight db has nothing then have default text:
[00:59] <bobweaver> Saviq,
[00:59] <Saviq> bobweaver, then use what mhall119 said - there's a placeholderText property on a TextField
[01:00] <bobweaver> Saviq,  you think that i should make a binding statement ? I am sorry I am a noob just trying to make things that work for me in my house
[01:00] <bobweaver> Saviq,  what about qt4 supported ?
[01:00] <Saviq> bobweaver, not gonna happen
[01:00] <bobweaver> for necessitia and what not ?
[01:01] <bobweaver> :*(
[01:01] <Saviq> bobweaver, we rely on Qt5 for too many things
[01:02] <Saviq> bobweaver, unless you mean support for Qt4 apps on Ubuntu Touch? then that will probably come at some point
[01:02] <bobweaver> not just you YOU but for every one
[01:02] <Saviq> but we won't support it
[01:02] <bobweaver> like I can make qt5 app and also qt4 for other sdk like making dsk in necessitia
[01:03] <bobweaver> that is great but would be cool if you did
[01:03] <bobweaver> would make sort term opp faster
[01:03] <bobweaver> jmo
[01:03] <Saviq> bobweaver, necessitas will port to Qt5 soon enough, I'd say
[01:03] <bobweaver> +1
[01:04] <bobweaver> I mean +2
[03:17]  * sergiusens is running a raring build
[03:17] <sergiusens> rsalveti: boots, launches, runs apps... most of it works on raring :-)
[04:07] <Mirv> mhall119: you can find an example with apt-get source qtsensors-opensource-src (the plugin part)
[04:08] <Mirv> sergiusens: awesome! :)
[04:09] <sergiusens> Mirv: posting the image out of band soon for people to play with
[04:09] <sergiusens> :-)
[04:09]  * sergiusens was expecting to boot into a black screen :-P
[04:20] <Mirv> sergiusens: I'd have guessed it'd work quite far, since we rely so heavily on Qt and it's the exact same Qt in both
[04:21] <Mirv> sergiusens: for raring there's a newer qtwebkit build in qt5-proper PPA (pixel ratio patches etc), otherwise everything's in the raring archives
[04:22] <Mirv> but it's great if there's also nothing major in the other stack that breaks with raring
[04:25] <sergiusens> Mirv: well somethings are broken as they are in raring and still need to be overriden
[04:29] <Mirv> sergiusens: regarding parts of Qt or something else?
[04:32] <sergiusens> Mirv: not, Qt is fine :-)
[04:32] <Mirv> ok, just double-checking :)
[04:32] <sergiusens> Mirv: network is broken, running out of memory with media...
[05:16] <sergiusens> Mirv: in case you are interested, just sent an email to he list
[05:48] <Mirv> looks interesting
[07:11] <dholbach> good morning
[07:53] <dim319> Hi! Is there some progress on Terminal App?
[08:19] <kvarley> Is it possible to switch Ubuntu Touch onto a shell like the desktop Ubuntu?
[08:19] <ogra_> "onto a shell" ?
[08:20] <ogra_> it is/has a shell
[08:20] <kvarley> ogra_: Sorry I mean like on Ubuntu it runs the GUI by default but if you press Ctrl Alt + F1, etc you can login in text based mode
[08:21] <ogra_> ah, you want tty consoles ... no , by design it supports adb shell from a remote machine though
[08:22] <kvarley> ogra_: Will it be possible in the future?
[08:22] <kvarley> ogra_: Or rather, will there be a Terminal app in the future?
[08:23] <kvarley> Oh well in the future it will support docking won't it so that'd solve that problem
[08:23] <ogra_> there will be a terminal app by default (at least in the images we publish, i doubt if a carrier ships a phone he will allow that)
[08:23] <kvarley> ogra_: Ok, thanks for the help. Just looking at replacing my work setup with a single device running Ubuntu Touch :)
[08:24] <ogra_> heh, we will di that for you in 14.04 :)
[08:24] <ogra_> *do
[08:24] <ogra_> unity next (which is what you currently know as ubuntu touch UI) will move to the desktop too
[08:25] <ogra_> (it will still look like todays desktop ... or similar at least, thats why it takes a bit to port it)
[08:26] <kvarley> ogra_: Will switching to QT improve performance? Or is it a switch to improve development?
[08:26] <ogra_> both :)
[08:27] <kvarley> :D
[08:56] <nik90> Saviq: ping
[08:57] <Saviq> nik90, wassup?
[08:57] <nik90> Saviq: I saw your MP https://code.launchpad.net/~saviq/ubuntu-clock-app/fix-desktop-and-arch/+merge/156952
[08:58] <nik90> since the desktop file is doing all the work to execute the clock app, do we need the ubuntu-clock-app file?
[08:58] <Saviq> nik90, yeah, it's not needed
[08:58] <Saviq> nik90, but doesn't really hurt when you launch from the console
[08:58] <nik90> Saviq, is this how the other core apps are doing it as well?
[08:59] <Saviq> nik90, although I'd add the --desktop_file_hint=... --stage_hint=side_stage hints to the script
[08:59] <Saviq> nik90, or at least pass $@ in there
[08:59] <Saviq> nik90, yes, that's common
[09:00] <nik90> Saviq: alrite, so do you recommend letting the ubuntu-clock-app file remain with the additional commands you mentioned?
[09:01] <Saviq> nik90, it won't hurt, but will only be used when you launch from the console
[09:01] <kvarley> Given that the Samsung Chromebook and Nexus 10 have the same SoC, would it be possible for me to boot Ubuntu on my Nexus 10? I know that the I/O is different, but if Ubuntu booted off the Android kernel that would solve the issue. The video drivers are available for the SoC in the 13.04 repos so the only issue would be GPU access.
[09:01] <nik90> Saviq: ok...thnx
[09:02] <Saviq> kvarley, if you mean Ubuntu Touch, then Nexus 10 is one of the supported devices
[09:03] <Saviq> kvarley, see https://wiki.ubuntu.com/Touch/Devices
[09:03] <kvarley> Saviq: I mean full Ubuntu like the Nexus 7 has. Not Touch :)
[09:03] <Saviq> kvarley, wrong channel, then ;)
[09:03] <Saviq> kvarley, but I dunno
[09:03] <kvarley> Saviq: ok :)
[09:29] <seb128> ogra_, should adb see my nexus7 if the tablet is booted under raring (stock ubuntu, not touch)?
[09:34] <ogra_> seb128, nope, only in recovery
[09:35] <ogra_> we dont ship adb in the desktop
[09:35] <seb128> ogra_, ok, thanks, that's broken as well, I get a green android robot with a red sign
[09:35] <ogra_> uuuh
[09:35] <seb128> I'm putting back android on it then going to phablet
[09:36] <ogra_> nah
[09:36] <ogra_> seb128, http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-recovery-armel+grouper.img
[09:36] <ogra_> fastboot flash recovery quantal-preinstalled-recovery-armel+grouper.img
[09:36] <ogra_> then try again
[09:37] <ogra_> if you get adb, use https://wiki.ubuntu.com/Touch/Install#Manual_Installation
[09:37] <ogra_> no need for a whole android flashing
[09:38] <seb128> ogra_, \o/ recovery mode back
[09:38] <seb128> ogra_, danke
[09:38] <ogra_> :)
[09:38] <seb128> $ phablet-flash -l
[09:38] <seb128> Device detected as /sbin/sh: getprop: not found
[09:38] <seb128> hum
[09:39] <seb128> I guess I need to -b
[09:39] <seb128> no, same issue
[09:40] <ogra_> use the manual method i linked above
[09:40] <seb128> ogra_, shouldn't the script work?
[09:40] <ogra_> theoretically
[09:41] <ogra_> you can use "-d grouper"
[09:41] <ogra_> iirc
[09:41]  * ogra_ never used that script
[09:42] <seb128> ogra_, I'm wgetting the img, let's try to be old school ;-)
[09:42] <ogra_> yeah, effectively the script does the same with some cream and cherry on top
[09:43] <kvarley> Do any of the Touch devs have an image for the Nexus 10 that will boot straight Ubuntu? (13.04) Similar to that which is provided for the Nexus 7.
[09:43] <ogra_> there are no desktop images if you mean that
[09:43] <ogra_> only ubuntu-touch
[09:46] <kvarley> ogra_: Do the images support docking (full unity) mode yet?
[09:47] <ogra_> nope
[09:48] <ogra_> that will only start working once Mir is used on the desktop too
[09:55] <kvarley> ogra_: Ah ok, early days then. Will be great to see that in action. I think bug #1 might be fixed if it's done right ;)
[09:55] <ubot5`> bug 1 in Ubuntu "Microsoft has a majority market share" [Critical,In progress] https://launchpad.net/bugs/1
[09:56] <ogra_> hopefully :)
[09:56] <kvarley> Maybe not for personal use, but in the business world :)
[09:57] <ogra_> a touch version of UbuntuKylin might fix that bug i would guess :)
[10:22] <Quintasan> ogra_: Are armhf images made with NEON support?
[10:22]  * Quintasan wonders why linker skips libc.so on his tf101
[10:22] <ogra_> Quintasan, as usual ... for apps that do runtime switching, yes
[10:23] <ogra_> for apps that can only use build time NEON enablement we dont allow it
[10:23] <Quintasan> urgh
[10:23] <Quintasan> ogra_: I see, any idea how to debug ubuntu-session failing to start?
[10:24] <ogra_> hardcoded NEON isnt allowed ...
[10:24] <smartboyhw> ogra_, why do you always have an _ behind your nick?
[10:24] <ogra_> look in the logs
[10:24] <ogra_> smartboyhw, because i'm to lazy to configure my bip server to always authenticate with my user
[10:25] <Quintasan> ogra_: Problem is the only real error I get is E/linker  (  219): ics/linker.c:1598| WARNING: Skipping libc.so
[10:25] <smartboyhw> ogra_, .......... You aren't that lazy are you?
[10:25]  * ogra_ does that once a year to make sure my password still works ... but on the next reconnect i fall back to _
[10:25] <ogra_> smartboyhw, i rather spend my time in development than doing paperwork for IRC :)
[10:26]  * Quintasan reflashes the image to look at the logs in detail
[10:26] <ogra_> Quintasan, when do you see that ? while starting ?
[10:27] <Quintasan> ogra_: I flash the image, try booting it then I see nothing (read - only backlight gets activated) then I managed to do adb logcat on the device somehow
[10:27] <Quintasan> ogra_: I'll try flashing that again and logging in via adb but that generally doesn't work since it seems to be constantly rebooting itself
[10:27] <ogra_> well, you want to use "ubuntu_chroot shell" and look in the phablet users homedir under .ubuntu-session/logs/
[10:28] <ogra_> how old is your android image ?
[10:28] <palanglung> can i go back to the android.. after flashing ubuntu? on tf101
[10:29] <ogra_> Quintasan, could be that there were changes to the hybris or platform-abi stuff, you need to make sure to bzr update them in the ubuntu subdir of the android tree before building
[10:29] <ogra_> repo sync doesnt run bzr
[10:38] <Quintasan> ogra_: I'm pretty sure I flashed quantal preinstall armhf from yesterday
[10:38] <Quintasan> I did not build the image myself but I think I will actually start doing that
[10:40] <ogra_> you should, or make sure the person doing it does regular rebuilds if the bzr trees change
[10:41] <Quintasan> ogra_: I see. Thanks for help!
[10:41]  * Quintasan heads off to build the image
[10:41] <ogra_> well, not sure i have helped yet :)
[10:42] <ogra_> you will see if that is it once you have a fresh image
[10:42] <ogra_> might be a completely different thing
[10:42] <Quintasan> ogra_: I somehow get the idea that updating the bzr stuff will help
[10:42] <ogra_> :)
[10:49] <Quintasan> ogra_: Actually I'll try making that person who is spinning the images do the update before fetching the whole thing myself
[11:18] <netcurli> is there a way to make the toolbar in a Ubuntu Touch qml app hide? for example when I have a page stack layout and I used the back button to pop a page from the stack and then push that page again, the toolbar is still open
[11:19] <netcurli> I tried setting page1.tools.active = false; but that didn't seem to do anything
[11:47] <mpt> Just published: preliminary sketches for the System Settings overview. https://wiki.ubuntu.com/SystemSettings#phone
[11:49] <rvr> Hi
[11:49] <rvr> I'm trying to unlock the Nexus 4
[11:50] <rvr> but "fastboot oem unlock" is stuck <waiting for device>
[11:50] <rvr> It did work with Nexus 7
[11:51] <ogra_> mpt, the variable tiles one looks really slick
[11:51] <steve_fi> rvr, I don't know why, but I had to reboot my nexus 4 for it to work
[11:51] <rvr> steve_fi: I've tried a couple of times with no luck, let me try again
[11:52] <mpt> ogra_, yeah, I'm a bit fond of it too. :-) But it's quite different from the style of the rest of the system.
[11:52] <ogra_> its special and makes us special :)
[11:54] <rvr> Weird, still <waiting for device>
[11:55] <steve_fi> rvr, what I found is that when I booted into recovery to unlock the bootloader, adb wouldn't work unless I turned the nexus 4 off then back on
[11:55] <steve_fi> rvr, I don't know if it's specific to the nexus 4 or not, never had a problem on any other devices I've used
[11:56] <steve_fi> rvr, when I switch it back on, I'd get into recovery and it would always say "do not switch the device off"
[11:56] <steve_fi> until the operation had completed
[11:56] <netcurli> ok, got the toolbar hiding working now, would be good though if this was done automatically with the build-in back action in page stacks
[11:56] <ogra_> rvr, but you are in fastboot mode (not recovery) ?
[11:56] <rvr> steve_fi: On the Nexus 7 it was very much straightforward, like stated on the wiki
[11:57] <pmcgowan> rvr: do you have the latest version of android-tools-fastboot installed?
[11:57] <rvr> pmcgowan: Yup, packages updated
[11:57] <pmcgowan> rvr: ran it as sudo?
[11:58] <steve_fi> ogra_,  perhaps i used the wrong word ... ooops ;)
[11:59] <rvr> pmcgowan: Sh*t
[11:59] <rvr> That was it, sorry :P
[11:59] <pmcgowan> np
[11:59] <pmcgowan> been there done that
[12:00] <ogra_> we should ship proper udev-acl rules in the adb package for this
[12:00] <ogra_> so you dont need root
[12:00] <pmcgowan> ogra_: good point
[12:00] <ogra_> (or in the fastboot package rather)
[12:00] <ogra_> (or even in both !!)
[12:01] <ogra_> :)
[12:05] <pmcgowan> popey: can we get those MRs for the core apps in
[12:10] <pmcgowan> Saviq: what is left to do to use the flags for the stage selection
[12:11] <popey> pmcgowan: they already have been
[12:11]  * popey checks in case he's gone mad
[12:11] <pmcgowan> popey: calc was merged, not the other two
[12:11] <popey> clock has
[12:11] <popey> I'm on a hangout with them now
[12:12] <pmcgowan> https://code.launchpad.net/~saviq/ubuntu-clock-app/fix-desktop-and-arch/+merge/156952
[12:12] <pmcgowan> https://code.launchpad.net/~saviq/ubuntu-calendar-app/fix-desktop-arch/+merge/156960
[12:12] <pmcgowan> popey: clock not acc to the mr
[12:12] <pmcgowan> expected jenkins to do its thing
[12:12] <popey> ok, top approved
[12:20] <Saviq> pmcgowan, the only remaining one is share-app, which fails (unrelated) tests
[12:20] <Saviq> pmcgowan, https://code.launchpad.net/~paulliu/share-app/desktop_file_tweak/+merge/156560
[12:20] <pmcgowan> Saviq: did the shell need an update to use the flags, or how is it done?
[12:21] <Saviq> pmcgowan, the app lens did
[12:21] <Saviq> pmcgowan, but only to filter _out_ those that didn't have Touch=true
[12:21] <pmcgowan> Saviq: so there is a new update pending on that or the one from yesterday
[12:21] <Saviq> pmcgowan, everything is merged now
[12:21] <pmcgowan> Saviq: thanks
[12:21] <Saviq> pmcgowan, apart from the share app
[12:22] <Saviq> pmcgowan, not everything is in the image yet
[12:22] <pmcgowan> right, hoping to see that tonight
[12:28] <nik90> popey: is the current month 13.10-month-0?
[12:30] <Saviq> popey, love your use of unicode ;)
[12:30] <popey> Saviq: :D
[12:30] <popey> nik90: yes
[12:31] <popey> nik90: https://launchpad.net/ubuntu-phone-commons/coreapps-13.10 has dates next to milestones
[12:33] <popey> Saviq: I started using Unicode a lot after Fedora had a bug in their bug tracker which made it impossible to file bugs against Fedora 18 because it's called "Schrödinger's cat".
[12:33] <Saviq> :D
[12:35] <nik90> popey: thnx
[12:51] <netcurli> I get a segmentation fault when exiting a QtWebkit WebView in a qml app with visible set to false: http://pastebin.ubuntu.com/5676504/
[12:51] <netcurli> I don't know if that is a bug in the qt version in ubuntu or qtwebkit in general
[13:14] <nik90> ckpringle: https://www.youtube.com/watch?v=xUoRgsPYkbQ
[13:14] <ckpringle> nik90: cheers!
[13:14] <nik90> gtg..c u later
[13:14] <ckpringle> nik90: oh sorry we went straight for lunch after, talk to you later ;)
[13:15] <nik90> ckpringle: np :)
[13:59] <rsalveti> sergiusens: mind taking a look at the chromium_net related patches later on?
[13:59] <rsalveti> needs to be applied at phablet.u.c
[14:05] <tsdgeos> zsombi: ping
[14:06] <zsombi> tsdgeos: pong
[14:06] <tsdgeos> zsombi: greyback told me i should tell you about the problem i'm having with ActivityIndicator
[14:06] <tsdgeos> zsombi: it's taking 40% of the CPU of the Nexus4
[14:07] <zsombi> tsdgeos: :(
[14:07] <tsdgeos> he says you had a patch for that or something?
[14:07] <zsombi> tsdgeos: which SDK release you have?
[14:08] <tsdgeos> zsombi: 0.1.39~quantal1 is what is running on the phone
[14:09] <zsombi> tsdgeos: we had a patch for turning it off when not running, but when running, that's the time it takes :/
[14:09] <zsombi> tsdgeos: so you have the latest one... I'm sorry to say that animating the image unfortunately takes that much. I guess you are concerned about the time taken when running, right?
[14:11] <tsdgeos> zsombi: well, the thing is that i'm doing other processor intensive stuff while that is running
[14:11] <tsdgeos> and i max out the cpu
[14:11] <tsdgeos> and all gets choppy
[14:12] <mhall119> Saviq: so I still have that keyboard problem, who should I bug about that?
[14:12] <Saviq> mhall119, tmoenicke to start with
[14:12] <mhall119> tmoenicke: pingity ping
[14:18] <Saviq> oSoMoN, are you caring for share-app? or is Ugo?
[14:20] <oSoMoN> Saviq: Ugo is, but he’s working part time these days, and he’s off until next Monday, so if there’s anything urgent I’ll take it
[14:20] <Saviq> oSoMoN, if you had any idea why https://code.launchpad.net/~paulliu/share-app/desktop_file_tweak/+merge/156560 fails tests
[14:22] <oSoMoN> Saviq: I’ll have a look
[14:31] <oSoMoN> Saviq: the autopilot tests pass locally, I’ll try to figure out why they are failing on jenkins
[14:32] <Saviq> oSoMoN, thanks
[14:33] <sergiusens> rsalveti: ack
[14:35] <tmoenicke> mhall119: pong
[14:36] <mhall119> tmoenicke: hey, I have a problem with my onscreen keyboard on my nexus 7
[14:36] <mhall119> when I click a key on it, the press event is also passed on to whatever widgets are below it
[14:36] <tmoenicke> mhall119: yes, I'm working on it :)
[14:37] <mhall119> ok, Saviq said it was fixed yesterday, but it's not for me, so I wanted to make sure the correct people knew it was still a bug
[14:37] <tmoenicke> mhall119: it was marked as fixed but re-opened
[14:40] <jhodapp> rsalveti, thanks for the permissions fix yesterday...it did the trick for the permission denied error...still get a connection refused error but like you said before, progress. :)
[14:42] <rsalveti> jhodapp: cool
[14:46] <mterry> xnox, regarding dep8 tests, we talked about those recently.  They aren't run as part of stack prep right now
[14:47] <rvr> Is it a known issue that device restarts when executing ubuntu_chroot?
[14:48] <xnox> mterry: fair enough. I think jibel and friends did say that it is possible to add ppa's to DEP8 infrastructure. But I can see how that will not block merge proposals / uploads.
[14:48] <xnox> mterry: even just running them against the resulting PPA would be nice (if there are any)
[14:57] <xnox> So if my test binaries need android, that means if I flash my nexus7 with a phablet image I will be able to execute them. Correct?
[14:59] <cyphermox> xnox: possibly?
[14:59] <cyphermox> you will not likely be able to display anything on screen, but you can query android bits
[14:59] <xnox> Hm... i have ubuntu core on my nexus7, will need to reflash it.
[15:00] <cyphermox> it all depends what you're trying to do :)
[15:14] <xnox> Since I still boot into ubuntu-core sometimes.
[15:14] <xnox> phablet-flash doesn't quite work for me.
[15:14] <xnox> I reboot into recovery and phablet-flash doesn't "flash" if it's in recovery. I'm following manual deployment steps atm.
[15:14] <xnox> It would be nice if it just did the right thing, if I specify the device type.
[15:15] <ogra_> xnox, see the Install wikipage
[15:15] <ogra_> i added a "Manual Installation" topic
[15:15] <ogra_> just follow it
[15:15] <seb128> the battery indicator's menu is sometime empty on today's image for me
[15:15] <seb128> is that a known issue?
[15:16] <xnox> ogra_: yeah, I'm following that. =) I now wish phablet-deploy learns to do that =)
[15:16] <ogra_> it largely does that :)
[15:16] <ogra_> just a bit different :)
[15:17] <cyphermox> xnox: I was also using manual steps, don't want to reflash recovery or really get out of it
[15:17] <cyphermox> xnox: I did some changes in phablet-flash to make it agree to flash in recovery, but I'm not sure how to properly integrate that and have both ways work
[15:18] <xnox> cyphermox: if you pastebin your diff, I can work on it further =)
[15:18] <cyphermox> xnox: I think I reverted the changes, but it's easy enough
[15:18] <xnox> cyphermox: ok, will poke it later.
[15:19] <cyphermox> xnox: i'll edit in a branch and send you the link soon
[15:19] <ogra_> just use the manual mode i added as a blueprint add it to phablet-flash in a way that it does exactly that but only if you run it with --recovery-install
[15:19] <cyphermox> yeah
[15:19] <ogra_> easy peasy :)
[15:20] <xnox> ogra_: well adb devices already lists recovery, it's just it should start doing stuff if it finds recovery in adb devices && device type was specified on the command line.
[15:20] <oSoMoN> Saviq: I *think* CI is failing for the share-app because of missing runtime deps for the autopilot package, I’ve submitted https://code.launchpad.net/~osomon/share-app/more-autopilot-deps/+merge/157137, let’s see if CI passes there
[15:20] <cyphermox> ogra_: indeed, should be simple enough
[15:20] <cyphermox> I'll squeeze in an hour to fix it up ;)
[15:21] <cyphermox> ogra_: there are some changes needed because for instance, df isn't the same in recovery as in the device (for detection)
[15:21] <ogra_> ah
[15:21] <cyphermox> if I was to make it run through almost the same steps... ;)
[15:21] <Saviq> oSoMoN, thanks
[15:21] <cyphermox> but yeah, got a few ideas
[15:23] <Makyo> Hi all.  I'm having a problem getting things running again on a Nexus 10 after what appears to have been a corrupted flash with r55.
[15:41] <oSoMoN> Saviq: CI passed, can you please approve https://code.launchpad.net/~osomon/share-app/more-autopilot-deps/+merge/157137 ?
[15:41] <ogra_> janimo, the "ubuntu touch display server" (as you call it in your mail) currently is android :)
[15:41] <Saviq> oSoMoN, awesome, thanks
[15:43] <janimo> ogra_, well I did not want to call it anything as I knew it was a Qt/SurfaceFlinger combo but with no idea how it related to xinput :)
[15:43] <janimo> and just in case Mir went in in the past few days without me noticing :)
[15:43] <ogra_> heh
[15:44] <ogra_> well, its libinput from android
[15:44] <ogra_> i doubt that will change with Mir
[15:44] <ogra_> at least for the start it wont i guess
[15:45] <oSoMoN> Saviq: once it’s merged, we can re-trigger CI on Paul’s MR
[15:45] <Saviq> oSoMoN, yup, I'll take care of it, thanks
[16:09] <xnox> Hmm... how do I run raring on this thing? dist-upgrade and away I go? =)
[16:10] <janimo> ogra_, that explains why we needed the kernel change to have it work with X and now need to revert it so it works with android again
[16:11] <ogra_> janimo, right, but i dont want to break the desktop images ... so worst case we need to leave its kernel as is
[16:12] <janimo> ogra_, I am sure something can be done to have it work both ways, but don't know how
[16:13] <ogra_> yeah, well, i suspect the desktop image will go away after 13.04
[16:14]  * xnox downloading raring build.
[16:15] <xnox> ogra_: I'm confused why are we releasing nexus7 desktop image at all to be honest. Same with pandas and ac100.
[16:15] <xnox> (well ac100 is kind of lubuntu target, which is ok)
[16:15] <ogra_> ac100 is a community image
[16:16] <ogra_> i wont comment the panda :P
[16:17] <ogra_> xnox, the nexus7 is our current desktop reference image on arm
[16:18] <ogra_> for the convergence story we need to make sure desktop bits work
[16:18]  * xnox downloading raring build of ubuntuone takes a while.
[16:18] <ogra_> someone on the ML said it took him 4h
[16:19] <ogra_> sergiusens, so when can we switch the dailies on cdimage to raring ? :)
[16:19] <ogra_> any planned ETA ?
[16:19] <xnox> sergiusens: can you throw the raring.zip on to people.canonical.com or something? =)
[16:19] <janimo> ogra_, for convergence? Should that not be better served by an Ubuntu Touch image then?
[16:19] <ogra_> ++
[16:19] <ogra_> janimo, it will still use desktop apps
[16:19] <janimo> I don't suppose Unity in it's current form will move forward on the Nexus 7
[16:19] <xnox> ogra_: it seems like dist-upgrade + enable ppa's wil be quicker.
[16:19] <ogra_> no. it wont
[16:20] <ogra_> (that was to janimo )
[16:20] <xnox> janimo: it is a stable reference platform for debugging though, and easier to deploy to.
[16:20] <xnox> (no chroot/containers)
[16:20] <ogra_> janimo, but we might use apps and cant test them without X yet
[16:21] <ogra_> so until we have XMir to test i.e. LibO on arm for cobnvergence we will need one image around that can run this
[16:21] <krabador> ogra_, can you tell me what are now difficulties for calls on i9100?
[16:21] <ogra_> krabador, nope, i dont even have a  SIM in mine
[16:22] <ogra_> i use my i9100 for app testing etc
[16:22] <krabador> ogra_, ok, but it's related on cm10.1 kernel, or ubuntu-touch support?
[16:22] <ogra_> did the xda forum guys not get it to work yet ?
[16:23] <krabador> ogra_, not, until now, not working.
[16:23] <ogra_> the ubuntu side should support calls and SMS if you have a SIM without PIN
[16:23] <ogra_> no 3G though
[16:25] <hopkinskong> Anyone are here?
[16:25] <Robin_Watts> seb128: hey
[16:25] <hopkinskong> I got SEG FAULT on all services
[16:26] <Robin_Watts> seb128: Just checking in in case you had any questions you wanted to ask about mupdf in advance of the doc viewer meeting this evening.
[16:26] <hopkinskong> i mean services that in my base android inculding surfaceflinger, etc
[16:26] <hopkinskong> all returned MAPERR
[16:26] <seb128> Robin_Watts, hey, nothing specific
[16:26] <hopkinskong> How to debug/fix?
[16:26] <seb128> Robin_Watts, do you have a full feature desktop client using GTK or Qt using it?
[16:27] <Robin_Watts> seb128: one second while I phone a friend :)
[16:28] <seb128> lol
[16:28] <Robin_Watts> The short answer is that we don't have such a thing checked in anywhere.
[16:29] <Robin_Watts> but Tor was working on a new viewer for a while that I think used GTK.
[16:29] <Robin_Watts> We were hoping that we'd be able to get both windows and linux out of the same viewer by doing that, but it transpired that the GTK system requires about 30 DLLs or something stupid, and so it ground to a halt.
[16:30] <hopkinskong> Anyone could help me?
[16:30] <Robin_Watts> I was just trying to confirm with Tor that it was really GTK, but he seems to be afk at the moment.
[16:30] <Robin_Watts> The fullest featured client we have is for android.
[16:31] <Robin_Watts> Were you thinking of this as something to try out? or something to build from ?
[16:32] <seb128> Robin_Watts, something to try out, and also trying to see if we use mupdf for the phone if we could use it on the desktop and if there was an evince equivalent for it
[16:32] <mterry> fginther, so...  I just ran "./cu2d-update-stack ../stacks/head/platform.cfg"  According to the wiki, I need to "ping an archive admin so that he pulls the modification on lillypilly for the second-safety check process".  Is that you?
[16:32] <nik90> mhall119:  ping
[16:32] <seb128> Robin_Watts, seems there is nothing we could replace evince with easily on the desktop though
[16:32] <mhall119> nik90: pong
[16:32] <Robin_Watts> seb128: AIUI, evince calls out to different backends, right?
[16:33] <nik90> mhall119:  I am currently adding copyright info for the ubuntu clock app. THe bug report is at https://bugs.launchpad.net/ubuntu-clock-app/+bug/1164594
[16:33] <ubot5`> Launchpad bug 1164594 in Ubuntu Clock App "Add copyright/license headers to the clock app files" [Undecided,In progress]
[16:33] <Robin_Watts> so I don't immediately see why evince couldn't call out to mupdf.
[16:33] <nik90> mhall119: Should I follow something similar to http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/UnityCore/ApplicationPreview.cpp
[16:33] <seb128> Robin_Watts, it's "just a matter of code", right? ;-)
[16:33] <Robin_Watts> That may be something we can/should look at.
[16:33] <Robin_Watts> a simple matter of programming, yes :)
[16:33] <mhall119> nik90: hmmm, outside of my area of expertise
[16:33] <nik90> mhall119: oh...whom should I contact regarding this?
[16:34] <mhall119> seb128: can you help nik90 with the proper way of doing copyright/license headers?
[16:36] <seb128> mhall119, nik90: sure, what's the question?
[16:36] <seb128> ah
[16:36] <seb128> http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/UnityCore/ApplicationPreview.cpp is a good example of the usual/standard way yes
[16:37] <nik90> seb128: What should I include in the Authored section?
[16:37] <nik90> seb128: just the names who wrote that piece of code?
[16:37] <seb128> yes
[16:37] <nik90> seb128: Does this license need to be included in Every file in the project?
[16:38] <seb128> nik90, it's not an hard requirement but it's good practice
[16:38] <didrocks> hey mterry!
[16:38] <ogra_> hey didrocks
[16:38] <mterry> didrocks, hi!
[16:39] <nik90> seb128: ok thnx..I will basically copy the format from that file and edit the authors to suit the ubuntu clock prohect
[16:39] <seb128> hey didrocks
[16:39] <nik90> project*
[16:39] <seb128> nik90, great
[16:39] <mterry> didrocks, so...  I just ran "./cu2d-update-stack ../stacks/head/platform.cfg"  According to the wiki, I need to "ping an archive admin so that he pulls the modification on lillypilly for the second-safety check process".  Is that fginther or mmrazik or something?
[16:39] <didrocks> familiar environment :)
[16:39] <mterry> didrocks, also...  what did cu2d-update-stack actually do? it updated some phablet-team branch?
[16:39] <hopkinskong> ANY ONE?
[16:39] <didrocks> mterry: it created the jobs
[16:40] <mmrazik> didrocks: the admin mterry is mentioning is you, right?
[16:40] <didrocks> mterry: archive admins are listed here (not sure everyone knows what to do though): https://launchpad.net/~ubuntu-archive
[16:40] <mterry> didrocks, oh!  you mean a real ubuntu archive-admin
[16:40] <mterry> didrocks, then poke
[16:40] <mmrazik> oh
[16:40] <didrocks> a real and only one
[16:40] <didrocks> oh hey mterry
[16:40] <didrocks> what's up? :)
[16:40] <didrocks> ok ok, doing :p
[16:40] <mterry> didrocks, didn't think this had to do with ubuntu, since it was just a PPA
[16:41] <mterry> didrocks, but I guess the same job could upload to ubuntu so yeah
[16:41] <didrocks> mterry: it's not *required* for now
[16:41] <didrocks> mterry: but yeah, better to follow the same process
[16:41] <mterry> didrocks, so what are you doing now?  reviewing the change and making it final?
[16:41] <didrocks> or we'll forget about it later on
[16:41] <mmrazik> mterry: as far as I understand cu2d-update-stack updates some jenkins jobs on magners
[16:41] <didrocks> mterry: I'm just sudo -u ubuntu-archive -i on lillypilly
[16:41] <nik90> seb128: one last thing...the most recent copyright is 2012-2013 Canonical Ltd?
[16:42] <didrocks> mterry: cd cu2d/cupstream2distro-config/
[16:42] <didrocks> mterry: bzr pull (looking at the diff you did)
[16:42] <rickspencer3> rsalveti, tmoenicke so, my browser input for my nexus7 worked for one glorious moment yesterday :/
[16:42] <seb128> nik90, the years reflect when the code has been written, if it's a new project no need to list 2012, just 2013 is enough
[16:42] <mterry> didrocks, mmrazik: so once this change goes live, hopefully platform-api will be building in the PPA (though I believe all tests will fail, until xnox updates them for new names
[16:43] <didrocks> mterry: oh excellent, as it's a new stack, I should add the step to poke update the jenkins views
[16:43] <didrocks> mterry: jibel has a script for him, mind poking him? :)
[16:43] <didrocks> mterry: this is only when creating a stack
[16:44] <mterry> jibel, I'm double poking you, in case you (quite naturally) have a filter for didrocks
[16:44] <jibel> didrocks, mterry if only it worked on the version of jenkins we are running, I'd be happy
[16:44] <mterry> jibel, there's a new platform stack in head
[16:44] <didrocks> mterry: sometimes I wonder if that's not part of the default configuration :p
[16:45] <didrocks> mterry: we should remove ubuntu-ui-toolkit, right?
[16:45] <didrocks> as in the end, it will be in another stack AFAIK
[16:45] <mterry> didrocks, I don't see it on the stacks breakdown document
[16:46] <mterry> didrocks, oh, there's an empty sdk stack
[16:46] <didrocks> mterry: yeah, let me fix it
[16:46] <didrocks> or do it
[16:46] <didrocks> if you have it opened
[16:46] <didrocks> that would be lovely!
[16:46] <mterry> didrocks, sure.  a stack with just the sdk?  Why not throw it in platform?
[16:46] <didrocks> mterry: long discussion with sergiusens. Basically, they are done by different teams
[16:47] <didrocks> mterry: so if one is breaking the whole stack publishing, maybe let's avoid to end up in some social tensions :)
[16:47] <jibel> mterry, http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Platform/
[16:47] <didrocks> mterry: platform-api was in stacks/phablet/misc.cfg btw for the ci configuration. I think that mmrazik finally wants us to move them
[16:48] <mmrazik> didrocks, mterry: mhm.. you didn't move it just added?
[16:48] <mterry> didrocks, stacks document updated
[16:48] <didrocks> thanks mterry
[16:49] <didrocks> mmrazik: it's in the finale stack location, so should be removed frmo stacks/phablet/misc.cfg
[16:49] <mterry> mmrazik: Oh, I thought you earlier said that you wanted to handle that bit
[16:49] <mterry> sorry
[16:49] <mmrazik> didrocks: is it reasonable to have the same branch in two different stacks/releases?
[16:49] <didrocks> mmrazik: I don't see why we would want that
[16:49] <mmrazik> mterry: I sai I would prefer MP for cross-check :)
[16:49] <mmrazik> didrocks: we have that right now :)
[16:49] <mmrazik> I agree it doesn't make much sense
[16:50] <mmrazik> ok..
[16:50] <didrocks> mmrazik: right, hence the "now, let's move them one by one to head"
[16:50] <mmrazik> so let me move it from phablet
[16:50] <didrocks> mmrazik: but not all at the same time :)
[16:50] <mmrazik> didrocks, mterry: I'm moving platform-api from phablet/misc.cfg
[16:50] <didrocks> thanks mmrazik :)
[16:50] <mmrazik> didrocks: ack. but it would be appreciated if the move happens atomically (i.e. in one commit)
[16:50] <mmrazik> atomically for one project/branch (at least)
[16:50] <mterry> mmrazik, oh right, thanks.  I'll look at commit to make sure it's the same I would have done
[16:51] <mterry> mmrazik, for future
[16:51] <didrocks> mmrazik: ok, let's do that for the others :)
[16:51] <mterry> mmrazik, I see that i386 is disabled?  I don't think it should be
[16:51] <JamesMR> I'm not managing to find anything helpful on google, would anyone know if it's possible to dual boot the nexus 10 with android and Ubuntu?
[16:51] <mmrazik> mterry: I think it wasn't building on i386 :-/
[16:51] <mmrazik> sergiusens: do you know details ^^ ?
[16:51] <mmrazik> sergiusens: (platform-api disabled on i386)
[16:51] <mterry> mmrazik, well, it should.  Can we enable the build for i386 and then fix the build issue?
[16:52] <mmrazik> mterry: ok. I'll enable it
[16:52] <mterry> mmrazik, I don't think platform-api will build right now anyway because it's tests are borked.  But I figured we can go ahead with the stacks and everything even so
[16:52] <mmrazik> mterry: I'll only keep raring builds (and disable quantal)
[16:53] <mterry> mmrazik, yeah good point too
[16:53] <didrocks> mmrazik: I think you are using stacks/raring/platform.cfg, isn't it?
[16:53] <didrocks> as it doesn't match, that looks weird
[16:54] <mmrazik> didrocks: using for what? I'm actually not using it yet
[16:54] <mmrazik> I planned to do it today but didn't manage it
[16:54] <didrocks> mmrazik: oh, can we directly target the good stack name then?
[16:55] <didrocks> mmrazik: in fact, it should be in head/ only, not raring, thinking about it (as we are only going to support one branch)
[16:55] <mmrazik> didrocks: I'm confused. I'm moving platform-api from phablet/misc.cfg to head/platform.cfg
[16:55] <didrocks> mmrazik: right, the sdk will be another stack
[16:55] <mmrazik> didrocks: so we need to move ubuntu-ui-toolkit from platform.cfg?
[16:55] <mmrazik> didrocks: I didn't create platform.cfg
[16:55] <mmrazik> didrocks: ken probably did
[16:55] <didrocks> mmrazik: right, after talking with sergiusens, it makes sense to move it somewhere else
[16:56] <mmrazik> I don't crae
[16:56] <didrocks> mmrazik: do you want me to do that? (it's not only a bzr mv, we have more to do)
[16:56] <mmrazik> didrocks: uh
[16:56] <didrocks> mmrazik: I need to add the right dest ppa and so on, I can do that quickly, just want to warn you :)
[16:56] <mmrazik> didrocks: platform-api is now is platform.cfg so I'm not sure if bzr mv is all we need
[16:56] <mmrazik> didrocks: let me get rid of the duplicit platform-api first
[16:56] <mmrazik> it will take me 5 mins
[16:57] <mmrazik> and then do whatever you want with sdk
[16:57] <didrocks> mmrazik: ok :)
[16:59] <mmrazik> didrocks: I'm done
[16:59] <didrocks> mmrazik: ok, pulling :)
[16:59] <mmrazik> going to regenerate the autolanding jobs to enable i386
[17:04] <didrocks> mmrazik: rev 147
[17:04] <didrocks> (once you want to enable it)
[17:05] <mmrazik> didrocks: ubuntu-ui-toolkit needs to be removed from head/platform.cfg (to_transition)
[17:05] <didrocks> I thought mterry was going to do it at the same time?
[17:06] <mterry> heh.  this is a tragedy of the commons
[17:06] <tmoenicke> rickspencer3: working on it
[17:07] <didrocks> mterry: rev 148, hope you won't have a conflict :)
[17:07] <didrocks> mmrazik: ^
[17:07] <rickspencer3> tmoenicke, is the bug with the keyboard itself?
[17:07] <mterry> didrocks, I updated the stack document, but didn't bother with the config.  It was marked as to_transition, so didn't want to enable it.  Once we're ready to enable, we can move into new stack, eh?
[17:07] <tmoenicke> rickspencer3: the size it reports, yes
[17:08] <didrocks> mterry: right, it's just move to a separate "sdk" stack now, but still in to_transition ;)
[17:08] <mterry> didrocks, OK
[17:08] <mterry> didrocks, ah, you did it
[17:09] <mterry> too many chefs!
[17:10] <didrocks> mterry: it's like video games with unfair latency checks ;)
[17:15]  * sergiusens is glad he stayed out of the tide change that didrocks got into :-)
[17:16] <didrocks> sergiusens: why everyone is telling me that? :p
[17:16] <didrocks> join the fun!
[17:16] <ogra_> sergiusens, oh, yoou too ?
[17:16]  * ogra_ as well :)
[17:17] <sergiusens> ogra_: regarding raring, I'm not the one who decides when to pull the switch. But we do need functional parity for sure
[17:17] <ogra_> yeah, i thought so
[17:18] <ogra_> sergiusens, so publishing your zips on lillipily might probably be better
[17:18] <ogra_> since peolple seem eager to try it and ubuntuone is really slow
[17:21] <sergiusens> ogra_: yeah, I noticed... shouldn't of been slow...
[17:21] <sergiusens> ogra_: so I'm not triggering any switch, but I do plan on having them available as part of the build (just not promoting them as working)
[17:27] <kgunn> pmcgowan: hey is technical complexity 3=hard, 1=easy ? ...ivanka's life w/ phone sheet
[17:28] <pmcgowan> kgunn: yes
[17:34] <mpt> Drafts of phone settings design for Background: https://wiki.ubuntu.com/Appearance#Phone And Brightness: https://wiki.ubuntu.com/Brightness#Phone
[17:35] <boiko> daliusd: so, just curious on why a custom date formatting is needed in the calc app?
[17:35] <daliusd> boiko, I guess to keep string shorter
[17:36] <seb128> mpt, with the dynamic home screen, should it have a way to configure the data sources to use for the custom "welcome screen"?
[17:36] <seb128> mpt, like the demos have number of tweets you received, etc
[17:38] <daliusd> boiko, do you have more questions?
[17:38] <boiko> daliusd: can't we use Qt.DefaultLocaleShortDate?
[17:38] <rsalveti> sergiusens: I approved the webapps mr, but I still see the calculator-mockapp at qml-phone-shell (Applications/applications.js)
[17:39] <rsalveti> sergiusens: should we also remove it from there?
[17:40] <daliusd> boiko: maybe :) I don't know. We can try to.
[17:40] <WebbyIT> boiko daliusd I can look at it
[17:40] <boiko> daliusd: ok, so what's the preferred way for me to make suggestions on code changes? they are not actually bugs, so not sure I should open a bug
[17:40] <boiko> WebbyIT: nice! thanks!
[17:41] <daliusd> WebbyIT, assign it to yourself in blueprint - I just created task for it :)
[17:42] <daliusd> boiko, you can create blueprint items and write e-mail to us :)
[17:42] <WebbyIT> daliusd: ok :)
[17:42] <boiko> daliusd: ok, that works for me, thanks :)
[17:43] <WebbyIT> boiko: so, create you the blueprint? :)
[17:44] <boiko> WebbyIT: for this date formatting topic I think daliusd already created the item, you just assign it to yourself
[17:44] <boiko> WebbyIT: for the others, I will create the work items and leave them unassigned
[17:45] <daliusd> boiko: sounds good
[17:45] <WebbyIT> boiko: perfetct :)
[17:45] <WebbyIT> s/perfetct/perfect
[17:45] <boiko> daliusd: WebbyIT: ok, that's it then, thanks guys!
[17:46] <daliusd> boiko: thanks to you as well
[17:46] <daliusd> bye ;-)
[17:46] <WebbyIT> thanks to you boiko :)
[17:46] <boiko> bye
[17:46] <WebbyIT> bye bye
[17:47] <sergiusens> rsalveti: need to remove calc, calendar and clock from there, but that's in lp:qml-phone-shell
[17:47] <sergiusens> rsalveti: another MR :-)
[17:47] <rsalveti> sergiusens: yup
[17:48] <sergiusens> rsalveti: let me make some progress on smokes a bit and I'll switch back to that
[17:48] <rsalveti> sergiusens: ok
[17:52] <ShapeShifter499> hi
[17:52] <ShapeShifter499> so the source is out?
[17:53] <ShapeShifter499> I'll have to pass this on to the XDA devs for Nook HD and HD Plus, they control the source and would know what to do for porting this
[18:02] <Robin_Watts> seb128: evince is a *bitch* to build :(
[18:03] <seb128> Robin_Watts, how so?
[18:03] <Robin_Watts> evince requires gtk+ newer than 3.7.5.
[18:03] <Robin_Watts> the latest stable release is 3.6.4
[18:04] <Robin_Watts> so I try to build gtk+, and it needs a newer than stable glib etc.
[18:04] <Robin_Watts> And the helpful crib sheet of commands given on the evince page doesn't rebuild gtk+ for you, just everything else.
[18:05] <formolQC> Hi. I saw weeks ago a webpage with the status of the hardware compatibility for the Ubuntu phone. Im not able to refind it. Someone know where to found it?
[18:06] <seb128> Robin_Watts, just build evince 3.6
[18:06] <seb128> or use jhbuild
[18:06] <Robin_Watts> seb128: I was trying jhbuild.
[18:11] <Robin_Watts> seb128: It seems I can do 3.4.0
[18:46] <priya> Hi. ANy plans to port Ubuntu touch onn Intel tablets in near future? WOuld love to install an x86 build on my tablet
[18:59] <priyav> Anyone got success installing Ubuntu touch on an Intel tablet?
[19:00] <ogra_> priyav, you would have to port it first
[19:02] <priyav> ogra_, so I would assume noone has ported it yet for x86
[19:03] <mhall119> larsgk: rss app meeting
[19:03] <sergiusens> ogra_: there was a mention of an x86 port somewhere last Sat, don't recall exactly
[19:03] <mhall119> in #ubuntu-touch-meeting
[19:03] <mhall119> and any other RSS app developers
[19:04] <mhall119> dragly: ^^
[19:04] <ogra_> sergiusens, well, i have it on my todo as well for the emulator
[19:04] <sergiusens> ogra_: what is the purpose of the emulator? Just apps?
[19:05] <ogra_> sergiusens, but first i need to get the cdimage builds goig (if these RTs get ever done) and then there is the ubuntu beta release today keeping me busy :)
[19:05] <larsgk> mhall119: aa yes - jumping in
[19:05] <ogra_> sergiusens, to be shipped with the SDK so you can run it in qemu and have full GLES support
[19:05] <sergiusens> ogra_: sounds fun, that means my RTs will go ignored :-P
[19:05] <ogra_> dunno, mine are obviously ...
[19:06] <ogra_> IS probably doesnt like all that firewall piercing :)
[19:07] <pmcgowan> ogra_: might also help us for automated testing in VMs
[19:07] <ogra_> right
[19:07] <pmcgowan> so where is it??
[19:08] <ogra_> haha
[19:08] <priyav> ogra_: Do you have a timeline for the x86 port if you are working on that along with the emulator?
[19:08]  * ogra_ holds up his TODO sheet and points
[19:08] <ogra_> here, see ?
[19:08] <pmcgowan> lol
[19:08] <ogra_> priyav, within the next 3-4 weeks i would hope
[19:09] <priyav> ogra_: Thats cool. Thanks
[19:31] <popey> DocViewer Core App meeting about to start in #ubuntu-touch-meeting
[19:34] <pmcgowan> sergiusens: can I ask a ppa question
[19:37] <sergiusens> pmcgowan: shoot
[19:37] <pmcgowan> sergiusens: how does one kick off or otherwise monitor what package builds a ppa is about to do, for example
[19:38] <pmcgowan> https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily/+packages
[19:38] <pmcgowan> my favortie apps have not rebuild yet but I see no builds pending
[19:39] <pmcgowan> the packages in the ppa have still not picked up the desktop file changes from long ago
[19:39] <sergiusens> pmcgowan: you need to go into the architecture for the pending build, e.g.; https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily/+build/4467930
[19:39] <sergiusens> pmcgowan: well from what I can see, the score is low for that PPA and given that today there's a release, it might take some time
[19:40] <pmcgowan> sergiusens: bollux good point
[19:40] <sergiusens> pmcgowan: most of those packages are pending publication though, so they'll be available soon
[19:40] <sergiusens> pmcgowan: just looking, only two are missing
[19:40] <pmcgowan> sergiusens: and where did you find that? looking at view builds I could not
[19:40] <pmcgowan> sergiusens: calc not built at all and clock and calendar need arm
[19:40] <sergiusens> calendar for raring and quantal
[19:41] <pmcgowan> er calc not rebuilt at all
[19:41] <pmcgowan> sergiusens: looks like they just finsihed, sorry
[19:41] <pmcgowan> except calulator needs to build
[19:41] <sergiusens> pmcgowan: I don't see a pending calculator in the queue though
[19:42] <pmcgowan> sergiusens: thats what I mean
[19:42] <sergiusens> pmcgowan: for that we need to ask the owner of ubuntu-phone-apps-jenkins-bot... that guy gets the dput result
[19:42] <sergiusens> pmcgowan: I'm suspecting it was rejected
[19:42] <sergiusens> mmrazik: still around?
[19:42] <sergiusens> mmrazik: where can we check the email's for ubuntu-phone-apps-jenkins-bot
[19:43] <pmcgowan> maybe popey knows
[19:44]  * popey points at fginther
[19:44] <mmrazik> sergiusens: yup
[19:44] <mmrazik> sergiusens: gmail
[19:44] <mmrazik> sergiusens:let me send you the details
[19:45] <sergiusens> mmrazik: thanks
[19:45] <sergiusens> it would be nice if it could be converted to RSS :-)
[19:46] <mmrazik> sergiusens: maybe I can just fwd to<EMAIL_ADDRESS>?
[19:46] <mmrazik> the e-mail was primarily meant as login
[19:47] <sergiusens> mmrazik: yes, that would be a good idea, still, it would be nicer to have RSS (but I'm not asking that of you ;-) )
[19:47] <mmrazik> let me do the forwarding
[19:49] <mmrazik> sergiusens: done
[19:51] <sergiusens> pmcgowan: popey it was rejected: ubuntu-calculator-app_0.1bzr41raring0.dsc: Version older than that in the archive. 0.1bzr41raring0 <= 0.1ubuntu1bzr39raring0
[19:52] <sergiusens> My guess is someone pushed the feature branch to get stuff out of the way and the versioning it uses depends on bzr revno
[19:53] <mmrazik> sergiusens: might happened when fginther was bootstrapping raring
[19:53] <sergiusens> mmrazik: the quantal one was also rejected btw Version older than that in the archive. 0.1bzr41quantal0 <= 0.1ubuntu1bzr39quantal0
[19:54] <mmrazik> sergiusens: please check with fginther. I vaguely recall he was running into this already
[19:54] <fginther> mmrazik, sergiusens I'm trying to catch up
[19:55] <fginther> looks like a version string issue
[19:55] <mmrazik> fginther: in essence -- phone core apps are getting rejected from ppa
[19:55] <sergiusens> fginther: ok, easiest solution and cleanest IMO is an upstream version bump
[19:55] <mmrazik> I wonder where the ubuntu1 comes from
[19:55] <sergiusens> fginther: my bet (because it happened before), is that a feature branch was dput, and those have a bzr revno greater than what is in trunk (most of the times)
[19:56] <mmrazik> there is no ubuntu in debian/changelog at all
[19:57] <sergiusens> mmrazik: on what jenkins do these core apps run?
[19:59] <mmrazik> sergiusens: http://<IP_ADDRESS>:8080/
[20:01] <sergiusens> mmrazik: previous dput might have been a manual one it seems
[20:01]  * sergiusens reconfirms assessment with the logs
[20:02] <pmcgowan> gee never thought it would be so hard to add a few apps
[20:02] <mmrazik> sergiusens: I'm calling it a day but fginther should know all the details
[20:09] <fginther> sergiusens, do you still think an upstream bump is needed? I can purge the current packages from the ppa and rebuild, but that of course does not help those with the package already installed
[20:11] <sergiusens> fginther: some people will never get updates if you do that
[20:11] <sergiusens> fginther: so you have purging powers on a ppa now?
[20:11]  * sergiusens know who to ask for crazy stuff next
[20:13] <cyphermox> rsalveti: turns out the mako needs some more config magic to work
[20:13] <cyphermox> I'm finishing up, hopefully will be done before EOD
[20:13] <rsalveti> cyphermox: ok, cool
[20:16] <fginther> sergiusens, are you working on an MP?
[20:23] <sergiusens> fginther: I don't know where the code is, but I can look for it and do it
[20:24]  * sergiusens calculator calendar and clock all sound the same in his head :-/
[20:25] <sergiusens> found it
[20:27] <sergiusens> rsalveti: https://code.launchpad.net/~sergiusens/unity/mock2core/+merge/157223
[20:29] <sergiusens> fginther: https://code.launchpad.net/~sergiusens/ubuntu-calculator-app/new_version/+merge/157224
[20:30] <sergiusens> rsalveti: did you see my blueprint email?
[20:31] <sergiusens> plars: can you share some burden with me? (not a fun task I'm going to ask)
[20:31] <rsalveti> sergiusens: not yet, let me check
[20:31] <rsalveti> sergiusens: weird, the series and milestone is correct
[20:31] <sergiusens> rsalveti: doesn't show up in my active workitems though
[20:31] <fginther> sergiusens, looking
[20:32] <rsalveti> sergiusens: maybe because it should be month-6?
[20:32] <rsalveti> aka this month
[20:32] <plars> sergiusens: hey, what's up?
[20:32] <rsalveti> let me try changing that
[20:33] <rsalveti> sergiusens: check in a few to see if it's there
[20:34] <rsalveti> meanwhile you can check https://launchpad.net/~<user>/+upcomingwork
[20:35] <fginther> sergiusens, approved
[20:35] <sergiusens> plars: need some help triaging the ubuntu-touch-image bugs
[20:35] <sergiusens> plars: well, not triaging, confirming
[20:36] <sergiusens> rsalveti: ack, thanks
[20:36] <Makyo> I'm fresh out of ideas.  Anyone have any thoughts on r55 half-bricking a Nexus 10?  Will boot to recovery mode once, then crash hard enough to prevent anything but a battery symbol until I unplug it for at least half an hour.  I can't re-flash because it never boots to the OS, the manual install steps fail, and trying to fall back to Android fails.
[20:37] <sergiusens> Makyo: drained battery?
[20:38] <plars> sergiusens: anything specific? or just generally monitoring https://bugs.launchpad.net/touch-preview-images for unconfirmed things?
[20:39] <Makyo> sergiusens, I can't tell how fully charged it is given that it won't boot, but it's been plugged in overnight since I first flashed yesterday.
[20:39] <sergiusens> plars: yeah, just monitor New, and confirm or incomplete them
[20:39] <sergiusens> plars: I guess you can assign them too
[20:39] <sergiusens> Makyo: can't you boot into the bootloader?
[20:40] <kgunn> Makyo: can you flash the bootloader?
[20:40] <plars> sergiusens: I don't have a good sense of who gets which bugs at this point, do you have some guidelines for this already?
[20:40] <sergiusens> kgunn: I wouldn't flash the bootloader, that can cause bricking ;-)
[20:40] <Makyo> sergiusens, only after unplugging for about half an hour.
[20:40] <kgunn> Makyo: fwiw, i had something similar on nexus7
[20:41] <sergiusens> plars: don't worry then, I'll take care of that, teams are in the mix lately
[20:41] <kgunn> rebooting at bootloader
[20:41] <Makyo> kgunn, was there an indication of the reboot loop?
[20:41] <kgunn> went back to google stock...seemed to take care of it
[20:42] <kgunn> mmm...sorry....too many late nights/beers since then
[20:42] <Makyo> kgunn, fair :)
[20:42] <Makyo> kgunn, I tried going back to stock, but no luck.
[20:42] <kgunn> i do remember being very freaked out....and super happy when it worked
[20:42] <kgunn> mmm...well, at least you tried stock
[20:43] <plars> sergiusens: I'll do what I can, I'm still doing some beta2 testing for raring at the moment, but I should have some time today. Forunately it doesn't look like extreme numbers of bugs there yet :)
[20:44] <sergiusens> plars: nope, it's not that big, I went through half of them last week, I just don't feel like moving out of raring today on my devices ;-)
[20:45] <plars> sergiusens: ah, how's that going?
[20:45] <kgunn> Makyo: fwiw...i do remember trying a couple of times....and for whatever reason...it finally flashed
[20:46] <Makyo> kgunn, alright.  I'll look a little more then.  I couldn't get fastboot to recognize the device, maybe that's changed.
[20:46] <sergiusens> plars: pretty well... the first build worked mostly out of the box
[20:47] <sergiusens> Makyo: sudo fastboot
[20:47] <Makyo> sergiusens, Yeah, just <waiting on device>
[20:47] <kgunn> Makyo: ok...that really rings a bell
[20:49] <sergiusens> rsalveti: you didn't read my _Descrition_ for https://code.launchpad.net/~sergiusens/unity/mock2core/+merge/157223 :-)
[20:49] <sergiusens> rsalveti: it should just work though :-)
[20:49]  * sergiusens is still going to wait for the bot
[20:50] <rsalveti> sergiusens: sorry, didn't read it
[20:50] <rsalveti> yup
[20:51] <rsalveti> sergiusens: it always validate the ci before merging, right?
[20:52] <rsalveti> or if I top approve before the CI it'll just merge directly?
[20:52] <RobbyF> afternoon everyone.
[20:54] <sergiusens> rsalveti: if you top approve it's already game over
[20:54] <sergiusens> rsalveti: although the same thing is done in the autolanding phase
[20:55] <rsalveti> sergiusens: right, thought it'd have some sort of ci first
[20:55] <rsalveti> yeah
[20:55] <sergiusens> rsalveti: what I wasnted though was for -ci to finish, grab the deb and install it on my tablet :-)
[20:55] <rsalveti> got it
[20:57] <fginther> sergiusens, ubuntu-calculator-app is building in the ppa
[20:57] <fginther> sergiusens, thanks
[21:01] <sergiusens> np
[21:03] <pmcgowan> fginther: sergiusens thanks guys
[21:12] <rsalveti> sergiusens: deb is already available
[21:28] <sergiusens> rsalveti: yup, looking
[21:29] <sergiusens> rsalveti: https://code.launchpad.net/~sergiusens/ubuntu-calendar-app/lp1164130/+merge/157236
[21:30]  * sergiusens is really close to getting smoke tests in place again
[21:31]  * sergiusens switches back to MRs
[21:34] <rsalveti> sergiusens: ok, will wait :-)
[21:35] <sergiusens> rsalveti: the deb feels good
[21:35] <sergiusens> rsalveti: only thing I notice now it that the gallery has no icon
[21:35] <sergiusens> rsalveti: but that doesn't seem to be from my MR
[21:35] <rsalveti> sergiusens: nops, not related
[21:36] <sergiusens> rsalveti: we're good to approve
[21:36] <rsalveti> sergiusens: DOME
[21:36] <rsalveti> DONE
[21:36] <rsalveti> sergiusens: will you create release mrs for them today still?
[21:36] <sergiusens> rsalveti: excellent, release commit comes
[21:36] <sergiusens> rsalveti: yes
[21:37] <sergiusens> rsalveti: did you check that other MR?
[21:37] <rsalveti> sergiusens: yup, but jenkins is still not taking care of it
[21:37] <sergiusens> rsalveti: heh, it's a different jenkins :-P
[21:37]  * sergiusens has no control over it
[21:38] <rsalveti> sebras: will it build as well as our jenkins?
[21:38] <sergiusens> rsalveti: it does build, doesn't publish the debs...
[21:38] <sergiusens> rsalveti: not really sure, this is my first interaction with core apps infra
[21:40] <rsalveti> will wait a bit more
[22:03] <wade|shull> ok, time to reinstall the components and see if it works
[22:10] <rickspencer3> hey, am I supposed to be able to get pinch and zoom gestures in a PinchArea on my Nexus7, yet?
[22:10] <rsalveti> sergiusens: I'm community there: https://code.launchpad.net/~sergiusens/ubuntu-calendar-app/lp1164130/+merge/157236
[22:11] <rsalveti> so we need an app core dev to approve
[22:11] <sergiusens> pmcgowan: do you know of any?
[22:11] <rsalveti> sergiusens: that's probably why the ci didn't run
[22:12] <sergiusens> fginther: do you know why the ci didn't run?
[22:12] <rsalveti> sergiusens: popey might be able to help you
[22:12] <sergiusens> rsalveti: well, it's a different trigger that what we use most likely
[22:12] <rsalveti> I think he got power cow powers at all core apps
[22:12] <sergiusens> rsalveti: ah, yeah, popey might be able to approve ;-)
[22:12] <rsalveti> *super cow powers
[22:16] <fginther> sergiusens, rsalveti, you need to be a member of one of the ubuntu touch teams: https://launchpad.net/~ubuntu-touch-coreapps-drivers
[22:16] <fginther> sergiusens, rsalveti see the subteam list there
[22:16] <sergiusens> fginther: well we are not :-)
[22:17] <sergiusens> fginther: and if I am, I won't approve my own MR :-P
[22:18] <fginther> sergiusens, I'll approve
[22:21] <wade|shull> oh a team
[22:21] <wade|shull> I like teams
[22:21] <wade|shull> oh core apps
[22:21] <wade|shull> they won't want me
[22:22] <wade|shull> I am fringe character at best
[22:49] <rsalveti_> plars: yeah, I wonder why we have dconf-editor now :)
[22:50] <rsalveti_> is this a real touch app?
[22:50] <rsalveti_> sergiusens: you might know as well
[22:53] <sergiusens> rsalveti: the shell now looks at all desktop files
[22:53] <rsalveti> sergiusens: got it
[22:53] <rsalveti> sergiusens: but I thought it'd need x-ubuntu-touch foobar or similar
[22:54] <sergiusens> rsalveti: I thougt that was for sidestaging
[22:54] <rsalveti> makes sense
[22:54]  * sergiusens looks at webcam grabbing smoke tests running
[23:40] <rickspencer3> rsalveti, I'm having a lot of trouble making an app reliably respond to pinch and zoom on my Nexus 7
[23:40] <rickspencer3> is this because I'm early to the party for this?
[23:41] <rsalveti> rickspencer3: not sure, it might be a bug specific to nexus 7
[23:41] <rsalveti> and unfortunately it's the only device I don't have
[23:41] <rickspencer3> rsalveti, is there a way I could log a useful bug report?
[23:42] <rickspencer3> just upload my code and let someone else try it, I guess?
[23:42] <rsalveti> rickspencer3: yup, that should do
[23:42] <rickspencer3> will do
[23:42] <rsalveti> rickspencer3: then I can try at nexus 10 as well
[23:42] <rickspencer3> sounds great
[23:42] <rickspencer3> I'll do it right now


[14:42] <BUGabundo> jpds: Err http://archive.ubuntu.com oneiric/main amd64 Packages   404  Not Found [IP: <IP_ADDRESS> 80]
[14:43] <BUGabundo> I'm alive
[14:43] <BUGabundo> I guess upgrading to 11.10 and changing my X tree didn't kill me
[14:43] <BUGabundo> ... yet
[15:13] <bkerensa> ohai
[15:24] <cousin_mario> hello
[15:25] <cousin_mario> I've been trying to do a fresh installation of natty alongside an existing one, but I failed and I'm not sure about the correct way for reporting such an occurrence.
[15:27] <cousin_mario> I believe I've encountered a bug though, the installer terminates because it cannount unmount a partition and the installation doesn't complete.
[15:38] <cousin_mario> well, bye
[18:04] <strycore> hi
[18:05] <strycore> so I was reporting a bug against compiz and apport told me to come see you guys :)
[18:05] <strycore> maybe it's a known issue but I couldn't find it on LP
[18:07] <strycore> it's about the expo plugin in compiz and dual-screens, the Multi Output Mode doesn't behave as expected
[18:08] <strycore> The "One wall per output" and "One big wall" show the same thing : the big wall mode
[18:08] <strycore> and it happens with or without Unity
[18:11] <strycore> Another one about Compiz, I'm pretty sure that the default value for the Decoration Windows rule wasn't "any"
[19:52] <destin> hello
[20:01] <oly> hi can some one what i should report an sd reader not working bug against ? ie what package ?
[20:01] <oly> spent quite a bit of time googling but i can not find anything recent on this particular reader
[20:13] <penguin42> oly: Probably linux
[20:14] <penguin42> oly: if it's hardware specific it's normally a kernel issue - does the reader show up at all?
[20:17] <oly> its detected with lspci
[20:17] <oly> but the device is not mounted
[20:18] <penguin42> oly: When you put a card in does anything show up in dmesg? Does anything show up in /proc/partititions?
[20:20] <oly> just ejected and reinserted the card but dmesg did nothing
[20:20] <oly> will just check the other location
[20:21] <penguin42> oly: OK, so report the bug by typing in a terminal     ubuntu-bug linux
[20:21] <oly> /proc/partitions only lists my hard drive partitions
[20:24] <oly> aha cool was not aware i could do that usually use the web interface but was just cunfused as to what it fell under
[20:27] <penguin42> oly: It will gather loads of useful stuff - all the lspci, dmesg and a load of other stuff to help the dev figure out why
[20:29] <oly> aha neat o
[22:43] <dupondje> Somebody around that can push priority of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774363 a bit :)
[22:43] <ubot4`> Launchpad bug 774363 in linux (Ubuntu) (and 1 other project) "cx88-blackbird driver hangs when used (affects: 1) (heat: 6)" [Undecided,New]


[00:33] <bluesabre> yay for fast backlight
[01:28] <Unit193> cyphermox: See anything interesting/fixable/fixed in those logs?
[01:28] <cyphermox> have yet to clone.
[01:28] <Unit193> Ah, KK.
[01:32] <cyphermox> wow, things blew up spectacularly
[01:35] <cyphermox> Unit193: are you sure the disk is good?
[01:35] <cyphermox> and are you using JFS?
[01:35] <Unit193> Yes, VM `gksudo` workith.  Nooope, normal run of the mill.
[01:37] <Unit193> Is there perhaps an undeclared dep?
[01:41] <Unit193> cyphermox: I'd have reported a bug, but when I tried that apport died (reported that one at least.)
[01:44] <cyphermox> well, we run ubiquity in sudo now
[01:44] <cyphermox> (if you start it with the link that is)
[01:45] <Unit193> That's what I did as a workaround, sed -i s/Exec=/Exec=sudo /  on the desktop file. :3
[01:45] <cyphermox> ack
[01:45] <cyphermox> well that should already be in now
[01:45] <Unit193> Nasty, but functional.  Except for the maybe-ubiquity.
[01:45] <Unit193> So, thanks then.  I guess the problem is at least hidden.
[01:46] <cyphermox> and pkexec should get fixed in the next image maybe, if the fix works
[01:46] <cyphermox> well, if it works the way I think it does
[01:46] <cyphermox> maybe-ubiuqity should not have been affected, afaik
[01:48] <Unit193> Coolio.
[01:50] <Unit193> Thanks for taking a look.
[01:57] <Unit193> flocculant: Tomorrow's ISO may have 60% less blowing up.
[02:03] <bluesabre> that sounds promising
[02:10] <Unit193> bluesabre: Nice uploads.
[02:10] <bluesabre> yup
[02:10] <bluesabre> will probably get kicked tomorrow :D
[02:11] <Unit193> \o
[02:12] <bluesabre> __/
[02:17] <bluesabre> flocculant, uploaded a new lightdm-gtk-greeter to https://launchpad.net/~xubuntu-dev/+archive/ubuntu/ppa, if you want to take a look to make sure nothing goes kablooey... :)
[02:21] -SwissBot:#xubuntu-devel- ::xubuntu-docs:: [16.10.0] r623 Include patch from krytarik to fix build, update changelog, ... (by Sean Davis)
[02:22] <bluesabre> never mind, failed to build x.x
[02:22] <Unit193> :D
[02:23] <bluesabre> too tired to look into that, bbl, night all
[02:34] <krytarik> bluesabre: "Successfully built on lgw01-25"  And thanks!
[02:36] <Unit193> (To be precise: https://launchpad.net/ubuntu/+source/xubuntu-docs/16.10/+build/10999976)
[02:37] <Unit193> flocculant: Also did two upgrade tests today.
[06:22] <flocculant> Unit193: thanks :)
[06:22] <flocculant> rebuilding our iso to catch the new ubiquity
[06:23] <flocculant> and that detail view thing in thunar keeps catching me out - don't always use that view :p
[06:35] <flocculant> Unit193: you mean the core one I assume btw?
[07:17] <flocculant> ochosi: http://i.imgur.com/JZ7EJry.png
[07:17] <flocculant> :)
[07:17] <flocculant> thanks cyphermox
[07:19] <flocculant> shut down on an image doesn't work ...
[08:53] <Unit193> Yeeeep.
[08:59] <bluesabre> morning all
[09:24] <Unit193> ristretto 0.8.1-1, xfce4-radio-plugin 0.5.1-4, xfce4-cpufreq-plugin 1.1.3-1, xfce4-dict 0.7.2-1, and xfce4-notifyd 0.3.3-1 uploaded to Debian.
[09:26] <bluesabre> cool
[09:27] <Unit193> -docs built and accepted, x-d-s good too.
[09:33] <Unit193> Oh meh, xfce4-notifyd 0.3.3-1 deps on 3.20..
[09:36] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 16.10 - i386 - i386 built.
[09:40] <bluesabre> Unit193, are you familiar with build errors when generating confdefs.h ?
[09:40] <bluesabre> https://launchpadlibrarian.net/288669084/buildlog_ubuntu-yakkety-amd64.lightdm-gtk-greeter_2.0.2-0ubuntu1~ppa16.10.1_BUILDING.txt.gz
[09:40] <bluesabre> never seen anything die at that stage
[09:41] <Unit193> checking for exo-csource... no
[09:41] <Unit193> configure: error: in `/«PKGBUILDDIR»':
[09:41] <Unit193> configure: error: exo-csource not installed
[09:41] <bluesabre> is that where it fails
[09:43] <bluesabre> trying another build with that in the deps
[09:52] <bluesabre> Unit193, that seems to fix it... I guess that used to get pulled in by another package
[09:53] <Unit193> Could easily be, aye.
[10:11] -SwissBot:#xubuntu-devel- ATTN: Xubuntu Core 16.10 - amd64 - amd64 built.
[10:36] <bluesabre> flocculant, now there is a new greeter in https://launchpad.net/~xubuntu-dev/+archive/ubuntu/ppa
[10:36] <bluesabre> should only require a quick spot check, will likely try to get it in later
[11:22] <flocculant> bluesabre: mmm
[11:22] <flocculant> so I updated, logged out
[11:23] <flocculant> logged in - locked - chnaged to guest went to logout, mistakenly restarted instead - on reboot it takes a looooong time to get the login dialogue up when you've restarted from guest
[11:24] <Unit193> dbus-user-session still installed?
[11:24] <flocculant> yup
[11:24] <flocculant> not needed?
[11:26] <flocculant> purged it - redid the same fail I did before - same
[13:51] <nairwolf> hi everyone, I should try some upgrade this weekend
[13:51] <nairwolf> I will tell you if I see something wrong.
[13:51] <nairwolf> "tell you" means it will be reported to the tracker
[14:14] <ochosi> flocculant: awesome, nice to see that fixed. thanks for poking folks!
[14:28] <akxwi-dave> 😃
[16:11] <flocculant> ochosi: welcome of course - I had time to do so :)
[20:15] <flocculant> Unit193: don't know if you know - or even expected so but, core installs from desktop, not from the install option at menu
[20:16] <Unit193> Dangit.  I was getting to that!  Why you have to be so fast? :(
[20:16] <Unit193> (Thanks!)
[20:16] <flocculant> cos it was there :p
[20:18] <Unit193> Once I finish up this crypted install, I'll look.  Thanks.
[20:19] <flocculant> k - appears to be the same issue as previously - not easy to tell :p
[20:52] <Unit193> flocculant: So wait, I don't remember.  Do I report these? :3
[20:55] <flocculant> you can if you want - I do - just keeping my hand in for when core is not an add-on at tracker ...
[20:57] <Unit193> Step 15.  There's no slideshow.
[21:01] <flocculant> wut
[21:02] <flocculant> oic
[21:02] <flocculant> I'd not bother too much about that - haven't created a testcase tailored to core - but wanted something to let people at least record against
[21:03] <flocculant> all we had was http://iso.qa.ubuntu.com/qatracker/testcases/1655/info
[21:03] <flocculant> I guess the best thing to do for zebedee would be rejig that one
[21:04] <Unit193> Sure, just figured I'd mention it.  Figured it wasn't really noteworthy but IRC is cheap.  Also mainly noticed because this time I was trying to find the difference between the two. :P
[21:04] <flocculant> well - difference between the 2 is enormous :p
[21:05] <Unit193> Yep, not in title, but mini vs squashfs.  Latter is muuch faster. :P
[21:05] <flocculant> yea
[21:07] <flocculant> there - reported on testcases - I'll get to it next month ish
[21:07] <Unit193> Oh hah, I was just going to ignore from now on. :P
[21:07] <flocculant> I'd not have tested this as often using mini with dial-up that's for sure :p
[21:07] <flocculant> Unit193: well yea - but one day perhaps more than you and I will check it :D
[21:08] <Unit193> And, err..  Maybe one day I'll actually report it every time I do.  I suuuuck. >_<
[21:08] <Unit193> "Oh it's just a spot check, hardly worth reporting" >_<
[21:08] <flocculant> :)
[21:08] <flocculant> I only test it when I see it in here tbh
[21:09] <Unit193> I reported all upgrades!  And yeah, that still has you testing it a lot.
[21:09] <flocculant> hah
[21:09] <flocculant> yep - I see upgrade testings
[21:13] <Unit193> (I'm going to be upset if this install doesn't fail...)  At what point during the install does it fail if you select from the boot menu?
[21:13] <flocculant> more or less at the end
[21:14] <flocculant> is it still installing ?
[21:15] <Unit193> First install went fine, doing the menu one now.  It's still going.
[21:16] <flocculant> oh no - actually as soon as it finishes 'copying files'
[21:17] <flocculant> that's zsynced iso here
[21:17] <Unit193> I selected the wrong ISO, but same version of ubiquity and generally similer setup.
[21:18] <flocculant> testing the 64bit
[21:18] <flocculant> I was ^^
[21:18] <Unit193> Well crap, going to do 3 installs it looks like..
[21:19] <flocculant> mmm
[21:19] <flocculant> so it's working for you?
[21:19] <Unit193> That's my fault, I'll fix it and re-try.
[21:53] <ochosi_> hey everyone
[21:53] <ochosi_> how's the release coming along?
[21:54] <Unit193> Well, flocculant is right and using the install-only menu crashes. :P
[21:54] <Unit193> ..On Core.
[21:57] <Unit193> cyphermox: Want another syslog output? ;3
[21:58] <Unit193> (Which I understand is poorly formed English, but oh well.)
[22:08] <cyphermox> Unit193, file a bug, i will look later when i am back home
[22:11] <Unit193> And now LP starts OOPsing. :D


[00:00] <arraybolt3> So, the solution... is probably to delete all known WiFi connections if there's a state transition from "Connecting" to "Not Connected" on a WiFi device.
[00:00] <arraybolt3> And probably change the connection status label to "Connection failed - bad password?".
[00:01] <arraybolt3> So I'm going to try and implement that and we'll see what happens
[00:04] <arraybolt3> Actually, there's a StateChangeReason thingy I can use that should make this doable.
[00:05] <arraybolt3> Might even allow popping up a "Bad password" dialog.
[00:13] <arraybolt3> Also going to implement some intelligent combo box locking
[00:26] <arraybolt3> Almost worked - I didn't get the password popup due to a race condition, but at least I didn't totally lock myself out of being able to connect to that network at all :P
[00:26] <arraybolt3> which was the previous behavior
[00:32] <arraybolt3> I feel like I'm developing for some sort of embedded device, coding in a VM and then transferring binaries for testing onto my test laptop :P
[00:35] <arraybolt3> Woot, it works!
[00:35] <arraybolt3> OK, now to change some text a bit...
[00:45] <arraybolt3> And it works. There's a segfault that needs help, after that I'll push.
[00:48] <arraybolt3> oof, actually the segfault isn't so easy to fix, I'm just going to push this for now and tackle the segfault later. (Basically if you try to input a WiFi password that is too short, NetworkManager refuses it, which ends up with an invalid pointer or something along those lines sneaking into the code, and then boom.)
[00:51] <arraybolt3> Pushed, ready for others to test. Works on an old Chromebook over here.
[00:52] <arraybolt3> There's one very unlikely race condition I left in because I didn't see any good way to fix it (NetworkManagerQt's way of doing things didn't work), but you'd have to type your WiFi password very shockingly fast to run into it (like you'd have probably a sixth of a second to type it, maybe not even that).
[00:53] <arraybolt3> So unless someone's typing speed is approaching the speed of light, not a problem.
 well how fast could you paste your password from say a password manager
 fyi discourse should be back
[01:12] <arraybolt3> lynorian: Valid point, but if someone's managed to sideload a password manager onto the live ISO, import their password database, load the WiFi password, and copy it, all before LXQt is started and while the installer prompt screen is active... That's probably unlikely to happen.
[01:13] <arraybolt3> Besides, I would expect most people don't keep their WiFi password in a password manager (with the exception of KDE Wallet which I think acts as a secret service on KDE-based distros, but that's not technically being used like a password manager usually would be).
 Can you please describe the race condition in more detail? So I can take a look at it?
 With enough red bull I may be typing that fast :P
 Also, could you be more specific on your testing for the segfaults? So I know how to reproduce it and can add appropriate air handling and both the u I and the back end
 If there's a certain limit for how big password should be. We should be aware of that and prevent that in the u I
[01:44] <arraybolt3> If you remove a connection with NetworkManager::Connection::remove(), it gives you a QDBusPendingReply. If you then waitForFinished() that, it returns before the connection is actually fully removed. Once waitForFinished() returns, the code then calls handleWiFiConnection() (which I tweaked slightly) to ask for the password again. If you type your
[01:44] <arraybolt3> password and click Connect REALLY SERIOUSLY FAST, you might be able to accidentally add a connection that still exists because NetworkManager isn't done removing it.
[01:44] <arraybolt3> But again, that would require you to type and connect so insanely fast that you can beat NetworkManager's connection removal routine, which gives you around 1/6 of a second to do the whole thing.
[01:44] <arraybolt3> I would imagine something like openQA might trip this, but a human? Never.
 There is a maximum. I don't remember what it is.
[01:45] <arraybolt3> For the segfaults, it's easy to trigger, just type a one-character password and click Connect. Boom.
[01:45] <arraybolt3> We should prevent too small or too large passwords, but that will probably require breaking the password dialog into its own class.
[01:46] <arraybolt3> As it is we're making the UI on-the-fly in the code itself, which makes it difficult to impossible to change the clickability of the Connect button depending on the currently entered password size.
[01:47] <arraybolt3> Since we probably need QLineEdit::textChanged to some routine that can change whether the button is clickable or not. Actually, that *may* be doable without needing an extra class now that I think about it... but really an extra class would be a lot cleaner.
 Yeah honestly it need some general clean up
 This should really be in a couple separate files plus as you may see, the language stuff is not quite implemented yet but again, I think that will be pretty easy compared to all of this networking stuff
[01:47] <arraybolt3> Agreed.
 Also, here's the other thing did you consider that? Maybe the bug with the removed connections is an upstream. Bug in behavior and that it actually should weights to return it because it is calling a specific weight for finished method. That should already be waiting for that. It doesn't seem intuitive or proper for it to not fully remove the connection before it returns
[01:49] <arraybolt3> Dunno, it seems like it probably returns once the removal starts, which might be expected behavior. There might be some other signal I can connect to in order to learn when the connection was really removed though.
 Please add a nice large to do comments on top of that. So we know to revisit it and potentially do an up stream. Tweak on that behavior so it's not as racy
 Looks like pre shared keys are 8 to 63 ascii characters
 Aaron from a preliminary look, your code looks great! Thank you very much!
[01:54] <arraybolt3> Thanks! :)
 You're more than welcome to go the extra mile and implement the language stuff. But that's totally up to you if you want to move on to something else. And let me handle that and the tagging of one point oh later this week
 Basically, my super-secret plan is to announce all the new installer stuff and that comparison and installer. Prompt in one go this weekend
[02:07] <arraybolt3> ahh nice
[03:04] <arraybolt3> ls
[03:04] <arraybolt3> nope, wrong window
 ls -lah
[04:48] <arraybolt3> sigh, these translations have me virtually stumped. If I use lupdate and lrelease manually, it seems to work, but CMake seems to just be ignoring my requests to do translations.
[05:12] <arraybolt3> YAY it works!
[05:12] <arraybolt3> Grief. CMake is cool and all but AAAAAAA it can be hard sometimes.
[05:21] <arraybolt3> ugh, one last test, do the strings, you know, *actually translate* now that the translator loads?
[05:23] <arraybolt3> WOOHOO they do!
[05:23] <arraybolt3> Alright. Need to add some documentation, and then finally I'll push.
[05:47] <arraybolt3> Alright, pushed. That was way harder than it needed to be.
 discourse down again @teward001 503 service unavailable
 lxqt-pm> Yup, known bug, file it and assign it to me ;P (re @lubuntu_bot: (irc) <arraybolt3> tsimonq2: So remember the old lxqt-powermanagement issues we had before, where systems without a battery would get a notification? We now have the reverse problem - upon booting a system with a battery a notification is made that the battery is present and charging.)
[14:14] <arraybolt3> +1
 that's a different error i'll fix it (re @Leokolb: discourse down again @teward001 503 service unavailable)
 on a work meeting at the moment after that i'll poke
 fixed, problem was the NGINX reverse proxy that sits in front of the Discourse docker containers was not running.  It's up again (re @Leokolb: discourse down again @teward001 503 service unavailable)
[16:45] <tsimonq2> sudo systemctl enable --now nginx
[16:45] <tsimonq2> XD
 `sudo systemctl start nginx && sudo systemctl enable nginx` but ye basically (re @lubuntu_bot: (irc) <tsimonq2> sudo systemctl enable --now nginx)
 Confirm @teward001 all good now tks (re @teward001: fixed, problem was the NGINX reverse proxy that sits in front of the Discourse docker containers was not running.  It's up again)
[18:23] <tsimonq2> Just did a respin of the daily to add those five languages to ship-live like we talked about.
 @tsimonq2 did we accept vorlon's merge request targeting noble to drop muon?
[18:24] <tsimonq2> I think we +1ed it but didn't accept it.
[18:24] <tsimonq2> doing
 ack, tyvm
[18:25] <tsimonq2> commit e57b65a19c0711462fb29c3dcfaca89c3f3ca505
[18:25] <tsimonq2> Merge: 55f2522 2cb1140
[18:25] <tsimonq2> Author: Steve Langasek<EMAIL_ADDRESS>[18:25] <tsimonq2> Date:   Mon Dec 4 13:04:48 2023 -0800
[18:25] <tsimonq2> Merge branch 'muon-decay' into noble
[18:25] <tsimonq2> so already donbe
 nice
 well now that my work day is over i'mma bash my head on a wall, get some lunch, take a nap, then yell at Microsoft for $DAYJOB stuff at 4PM local
[18:29] <tsimonq2> hah nice have fin :)
[18:29] <tsimonq2> *fun
[18:29] <tsimonq2> http://cdimage.ubuntu.com/lubuntu/daily-live/current/noble-desktop-amd64.list
[18:29] <tsimonq2> Looks like langpacks landed.
[18:30] <tsimonq2> @Roberalz ^^^^^^^^^^^^^^^^^^^ sudo apt install language-pack-es language-pack-gnome-es language-pack-kde-es no longer requires an internet connection \o/
 \o/ (re @lubuntu_bot: (irc) <tsimonq2> @Roberalz ^^^^^^^^^^^^^^^^^^^ sudo apt install language-pack-es language-pack-gnome-es language-pack-kde-es no longer requires an internet connection \o/)
 Great
[18:31] <tsimonq2> Increased the ISO size by 21.72928 MB. Snaps do that on a weekly basis ;P
 @Roberalz Also, in case you haven't been following, that installer prompt will also automatically switch the live system language when a new one is selected.
 I think all the localization folks, especially the Spanish folks, will be really happy to hear that :)
 We'll formally announce later this week
 Perfect!!! (re @tsimonq2: @Roberalz Also, in case you haven't been following, that installer prompt will also automatically switch the live system language when a new one is selected.)
 Good news!!!
 💯
 As always, please let us know if anything is up with translations :)))
 OK no problem (re @tsimonq2: As always, please let us know if anything is up with translations :))))
 Thanks again for all your help with the localization teams @Roberalz :)))) we really appreciate it!!!!
 Thank you all for the work you do (re @tsimonq2: Thanks again for all your help with the localization teams @Roberalz :)))) we really appreciate it!!!!)
[19:04] <tsimonq2> arraybolt3: Do you wanna see something *really* *super* *cool*?
[19:04] <tsimonq2> arraybolt3: It's so amazing. Just top class.
[19:04] <tsimonq2> arraybolt3: On the live ISO, log out and log back into the session like meh, 5-10 times. Either via the GUI or restarting SDDM.
[19:05] <tsimonq2> arraybolt3: loginctl list-sessions just keeps growing and growing.
[19:05] <tsimonq2> arraybolt3: And according to ps -aux, all of those prior sessions are still running.
[19:05] <tsimonq2> Fun stuff, huh? :P
[19:10] <tsimonq2> That extra session - and the fact that pcmanfm-qt apparently works for translations but the desktop entries in the panel aren't being translated - will make the live session switcher just *slightly* more challenging. :P
[19:11] <tsimonq2> If anyone can figure out a reproducible way to change the *entire* live session language, just let me know.
[19:15] <tsimonq2> Pretty likely going to be a fix in the same area of the code adding the translations for the Ubuntu desktop entries... since those are the only translations working right now, lmfao.
[19:17] <tsimonq2> Oh nevermind! I figured it out!!
[19:18] <tsimonq2> My usual testing language is es_MX, so this worked (along with a log out/log back in): sudo update-locale LANGUAGE=es_MX LANG=es_MX.UTF-8 LC_ALL=es_MX.UTF-8
[19:19] <tsimonq2> Before that, I just had to install language-pack-gnome-es and language-pack-kde-es.
[19:19] <tsimonq2> Now, the only untranslated entry in the menu is Apply Full Upgrade, and we have a fix for that already pending :)
[19:21] <tsimonq2> And Calamares even launches with es_MX when launched too \o/
[19:25] <tsimonq2> @RikMills: Can we please drop k3b-l10n to Recommends or Suggests on all the KDE langpacks? Volunteering to do the work, asking for an ack before proceeding.
[19:50] <arraybolt3> tsimonq2: Fun stuff :P re logout not really logging out
[19:56] <RikMills> tsimonq2: we can
[19:56] <RikMills> ack
[20:07] <arraybolt3> tsimonq2: So, the failing logouts raise a question for me...
[20:07] <arraybolt3> ...lemme test something
[20:08] <arraybolt3> but does logout work on an installed system either?
[20:08] <arraybolt3> If it doesn't, that's bad.
[20:18] <arraybolt3> yeah so logout is leaving a pile of sessions left even in the installed system.
[20:22] <arraybolt3> Testing on 22.04 LTS to see what happens.
[20:27] <arraybolt3> alright so sessions do **not** pile up on 22.04.3 LTS out of the box without updates.
[20:27] <arraybolt3> So now if I install updates...
[20:28] <arraybolt3> (don't expect this to change anything, but after this I install 22.04 LXQt Backports, and I *do* expect to see changes from doing that.
[20:35] <arraybolt3> tsimonq2: btw we should be thinking about how to get the needed changes into Casper to allow the lubuntu-live-environment session to become the default rather than the Lubuntu session - that way we avoid the "desktop pops up but then so does the installer prompt" weirdness that we have now.
[20:38] <arraybolt3> also I noticed that pcmanfm-qt on RISC-V64 in the Backports repo FTBFS with a depwait. Should I perhaps poke it and see if it will build now?
[20:39] <arraybolt3> oh, I see what happened, we need some NCRs in order to make that work
[20:39] <arraybolt3> in face we'd need to NCR the whole entire Backports stack
[20:39] <arraybolt3> *in fact
[20:41] <arraybolt3> tsimonq2: do you think it's worth me NCRing the whole Lubuntu Backports stack just for the sake of getting RISC-V builds in there? I feel like it might not be worth it.
[20:41] <tsimonq2> arraybolt3: If I thought it would be worth it, it would have been done already. ;P
[20:41] <arraybolt3> Alright, I have confirmed that the login pile-ups are LXQt's fault.
[20:41] <tsimonq2> arraybolt3: casper> ack, file the bug! "Bring out the list!"
[20:42] <tsimonq2> "Bring out the whole ocean!"
[20:42] <tsimonq2> arraybolt3: Bisect it using your mind again? XD
[20:42] <arraybolt3> I cannot reproduce them on a fully updated 22.04 LTS VM, but I can reproduce them on a fully updated 22.04 LTS + Backports VM.
[20:42] <arraybolt3> tsimonq2: lol
[20:42] <tsimonq2> https://www.youtube.com/watch?v=oBw4EllCluo
[20:44] <arraybolt3> tsimonq2: just watch it be the lxqt-menu-data change that b0rked things :P
[20:48] <arraybolt3> actually, probably not, probably something changed in whatever ships lxqt-leave
[20:55] <arraybolt3> guiverc, tsimonq2: Soooo... it looks like switching to DEB822 is what broke command-not-found. It can't parse /etc/apt/sources.list.d/ubuntu.sources.
[20:56] <tsimonq2> Does command-not-found support DEB822 at all?
[20:56] <arraybolt3> Probably not.
[20:56] <arraybolt3> I imagine it wouldn't be difficult to add support for it though.
[20:56] <tsimonq2> It is a goal for this feature; if you'd like to JFD the implementation, there's libraries for at least C++ and Python, and you can add it to your core dev app :P
[20:56] <tsimonq2> *for this release
[20:58] <arraybolt3> tsimonq2: out of curiosity why did you disable the nonfree sources? They've been enabled by default for years, no?
[20:58] <arraybolt3> What if someone wants to install rar? :P
[20:58] <tsimonq2> arraybolt3: That's what the installer checkbox is for. :P
[20:58] <arraybolt3> ohhhhhh
[20:58] <arraybolt3> nifty!
[20:58] <tsimonq2> Also, juliank thinks they should all be able to fit into one file.
[20:58] <tsimonq2> File the bug! :P
[20:58] <arraybolt3> I've been experimenting with that as little as possible since it's still in an unfinished state.
[20:59] <tsimonq2> Nah man, they want to push that as default *this cycle*.
[20:59] <arraybolt3> kk, well then command-not-found will need some help
[20:59] <guiverc> arraybolt3, I'm not surprised; i've experienced it with xubuntu i think and thus believed it impacted all
[21:00]  * guiverc just swore at myself my use of `rcp` again...  being removed from ubuntu/debian now by default...
[21:00] <tsimonq2> rcp?
[21:01] <tsimonq2> arraybolt3: How's the MOTU stuff coming btw? I know, I keep sidetracking you. :P
[21:03] <arraybolt3> tsimonq2: somewhat stalled right at the moment, one of the scripts I need to set up a local Britney instance has vanished out of its linked location and I'm not exactly sure who has it :P I pinged bdmurray about it a couple days ago but he must have missed it. I should ask him again.
[21:03] <arraybolt3> I think I'm going to miss the December 11 meeting though.
[21:36] <arraybolt3> no one here happens to have a spare Kinetic ISO they could shoot me, do they?
[21:36] <arraybolt3> I can try to fish it out of archive.org if not
[21:37] <arraybolt3> so far I've determined that the login issue doesn't exist in 0.17.0 and does exist in 1.2.0 (Lunar) so that *might* be close enough to bisect comfortably, I dunno though.
[21:40] <tsimonq2> arraybolt3: $ ls ISOs/lubuntu-22.10-desktop-amd64.iso
[21:40] <tsimonq2> ISOs/lubuntu-22.10-desktop-amd64.iso
[21:42] <arraybolt3> tsimonq2: great, throw it into https://transfer.zip/ and give me the download link if that's OK (that'll peer-to-peer transfer it to my computer)
 Sure, just give me like 10-15 mins. I have a gigabit connection so your side will be the throttle :P
[21:43] <arraybolt3> np
[21:44]  * guiverc has a load of ISO & manifest files if ever useful
[21:55] <tsimonq2> arraybolt3: Link sent over Matrix.
[21:55] <arraybolt3> Thanks, appears to be working :D
[21:56] <tsimonq2> Wow, you weren't kidding about your connection speed ;P
[21:56] <tsimonq2> "5 hours later"
[21:56] <tsimonq2> I guess I can't do more debugging requiring me to toggle my network access ;P
[21:57] <arraybolt3> Yeah it appears to be a bit pokey atm
[21:57] <arraybolt3> Usually it's faster than this though, perhaps the peer-to-peer transfer nature makes it slower.
[21:59] <arraybolt3> Turns out the script for using Britney against PPAs is more lost than I thought (bdmurray said "nobody knows" when I asked him where it was :P) so I guess I'm relegated to coding an alternative myself
[21:59] <arraybolt3> which will be fun since I've never used Britney locally before :P
[22:45] <arraybolt3> Well now we know how to break a VM :P
[23:02] <arraybolt3> https://bugs.launchpad.net/ubuntu/+source/lxqt-build-tools/+bug/2045706
[23:02] -ubottu:#lubuntu-devel- Launchpad bug 2045706 in lxqt-build-tools (Ubuntu Noble) "Logging out of Lubuntu does not fully terminate earlier logged-in sessions" [Undecided, New]
[23:43] <arraybolt3> I think this is probably actually SDDM's fault.
[23:44] <arraybolt3> I can't be sure *yet* since downgrading SDDM didn't fix the problem once I caused it, but it's the only thing left that looks like a real suspect (installing most of the new LXQt stack didn't reproduce it and everything left over looked non-suspicious).
[23:54] <LimeOn> Hello, i dont know if this would help in any way, but i have the last lxqt version and tried to reproduce those steps in the bugreport you made. I tried to log-in/logout 3 times and always see just 1 session. I do not know if theres something revelant you could need, but as i said some days ago, i am under arch linux. Just some info to throw some light in the issue
[23:54] <LimeOn> 'loginctl' changes its number, but in the end it says '1 sessions listed.'
[23:54] <LimeOn> so, i guess, theres just 1 session running
[23:54] <LimeOn> sddm here too
[23:55] <tsimonq2> arraybolt3: Can we reproduce it with just a pure Openbox session?
[23:55] <tsimonq2> If we can, it's SDDM. If we can't, it's LXQt.
[23:59] <tsimonq2> >____________<