[00:37] Elleo: ping... === chihchun is now known as chihchun_afk === kickinz1_mob|off is now known as kickinz1_mobile === duflu_ is now known as duflu === VDVsx_ is now known as VDVsx [08:47] bzoltan_: hi! Do I understand right, that qmake is currently not supported by our sdk? [09:24] mardy: he's on holiday for today still. currently yes, but qmake support is upcoming AFAIK. [09:24] cross-compilation is trickier with it than with cmake [09:33] ogra_, whenever you have the time, let me know so that we can talk about the adb work :) [09:33] ogra_, I'll be dealing with my email in the mean time and some udm stuff :) [09:39] Mirv: OK, thanks [09:40] mandel, will do [09:40] ogra_, I have a number of reviews to do, so take your time, but I'd like to get to the standup saying that I at least started with it :) [10:08] ogra_: do you have any concerns about http://paste.ubuntu.com/8800923/ for platform.vivid ? all kernels that I remove there are only available up to trusty, linux-image-dove is only available in lucid. I'm trying to get to the bottom of the armhf failure of https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-core-system-image and that seems like one possible source of error (although I still don't get where linux-mx5 comes fro [10:08] m :/) [10:15] mvo, that looks like the same issue we had with other images when the build tried to run on PPAs ... for the kernels, ask the kernel team [10:15] mvo, did infinity look into that yet ? [10:15] he should be able to tell if the build falsely tries to use a PPA builder [10:16] ogra_: aha, I will ask him, thanks [10:16] i surprised we still have dove ... :) [10:16] ogra_: well, its in the seed but its not in the archive since lucid [10:17] yeah [10:17] ogra_: smeels like bitrot, this is why I want to get rid of it [10:17] right, not sure if we use any of tehse kernels still ... only kernel team knows i guess [10:17] theoretically they should all be in -generic nowadays [10:18] but there are some that we still have in older LTS ... not sure they need them in the latest -devel for possible backports etc [10:20] right, I will ask. I can't think why we have them in platform.vivid, but my imagination may just not be good enough ;) [10:20] like mine :) [10:29] mandel, soo ... [10:35] Good morning all; happy Monday, and happy Cliché Day! :-D [10:39] ogra_, are you free? [10:39] mandel, i am ... [10:39] mandel, so you want to apt-get source android-tools [10:39] ogra_, I walked with sergio about what has to be done, I wanted to know if you have more details, for example, the exact signals to listen too etc.. [10:39] mandel, not really, the mtp-server code should have them [10:40] i guess you want to hook into services.c in core/adbd/ in the source [10:40] and make the shell wait until the right signal is goming down the dbus [10:40] ogra_, ok, got it, any preference in the lib for dbus to use? I was considering glib one but I'm open to use other [10:40] glib sounds fine [10:41] (dont forget to add a build dep etc) [10:43] ogra_, yes, I'll not forget that :) [10:43] ogra_, then I'll start on it, do we have unit tests for that thing? or do I have to do some integration tests/test plan? [10:43] and be careful with quilt ... its awfully broken in that package for whatever reason [10:44] mvo's glorious edit-path simply doesnt work with it ... so you need to manually pop/push patches on the stack [10:44] (i'll fix the whole thing once we switch to the new source) [10:45] ogra_, ok, you just managed to scare me :-/ [10:45] haha [10:45] it *is* scary [10:46] just check with debdiff if the changes are *really* in the package in the end [10:47] ogra_: oh, what package is that? maybe I need to look at edit-patch again to see if thats something I could fix [10:48] but lunch first :) [10:48] mvo, that backage is pure horror :) it is android-tools [10:48] i will re-do it in vivid during this cycle anyway, so dont bother to much [10:49] there is more code in patches than in the upstream source :) [10:49] ogra_, lets fork it! [10:49] * mandel hides [10:49] mandel, kind of :) [10:50] we'll switch to a 4.4 source anyway ... and i'll try to merge the patches where i can [10:52] mandel, create_subproc_thread() is the function in services.c you want to stop btw [10:53] ogra_, awesome! thx for that, I was looking at the code atm :) [10:53] right before it calls create_subprocess for sudo === _salem is now known as salem_ [11:25] saidinesh5: sorry, wasn't around much at the weekend, around today if you still need something :) [11:38] mvo__, i'm planning to merge the two branches from jodh_ today (from https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/+activereviews) any objections ? [11:38] seems to be for your stuff [11:39] they are largely just copy/paste bits from tough [11:39] *touch [11:39] ogra_: no objections - but https://code.launchpad.net/~jamesodhunt/livecd-rootfs/system-image-really-really-please-just-work-fix-resolvconf-for-ubuntu-core/+merge/237800 may not be needed (for us at least) as we deal with this now in the chroot.includes part [11:40] could you comment on the MP ? [11:40] i'll leave it out for now til jodh_ had time to comment on it [11:40] ogra_: done [11:41] thx [11:41] yw [11:42] hmm. just tried to merge the other one ... seems that is already there [11:43] except for an extra set -x at the top [12:06] Elleo: ping [12:06] still here? [12:07] Elleo: so basically the issue was i couldn't get a development environment for ubuntu-keyboard up and running on my nexus 7 [12:07] or [12:07] even on desktop [12:07] on the nexus 7 [12:07] sudo apt-get build-dep ubuntu-keyboard pulls in qt5-default which pulls in a ton of X11 dependencies which bricks the device [12:07] on PC [12:08] i have no clue why my ubuntu-sdk is failing to build an arm binary [12:08] it just says qmake exited with error code 1 [12:13] saidinesh5: there are problems cross-build qmake projects at the moment (which is why most have switched to cmake), apparently that's likely to be resolved in the future though (but if it isn't we'll probably finally get around to switch the keyboard to cmake at some point) [12:14] ohh [12:14] but how do you build for the [12:14] device right now? [12:14] use a chroot on the device [12:14] saidinesh5: my only guess on the bricking issue would be that it might be pulling in the wrong libgl mesa packages, since it has the option of a couple (either the gles version of the standard gl version) [12:14] chroot on the device? [12:14] it wont affect the running system then,, even when installing x11 bits [12:15] Elleo: oh i thought it was x11 but yeah even libgl mesa were installed [12:15] saidinesh5: I build directly on a phone without issues, these are the deps I install: debhelper doxygen libgl1-mesa-dev libgles2-mesa-dev libglib2.0-dev libgsettings-qt-dev libhunspell-dev libpinyin4-dev libplatform-api1-dev libpresage-dev libxml2-utils maliit-framework-dev pkg-config python-setuptools qt5-default qtbase5-dev qtdeclarative5-dev qtdeclarative5-private-dev xvfb presage [12:15] well plus build-essential [12:16] anything else should already be present on the image [12:16] oh [12:16] Elleo: which image do you use? [12:16] saidinesh5: vivid now, utopic previously for dev (the rtm repos don't have most build stuff in them) [12:16] ohh [12:16] is it available via multirom? [12:17] just a sec [12:17] brb in 5 [12:17] well I use vivid-proposed, but straight utopic/vivid should work too (although I don't think we've promoted a vivid image yet) [12:17] saidinesh5: basically devel or devel-proposed should be fine [12:17] saidinesh5: not familiar with multirom I'm afraid, but I'd suspect at least devel would be available [12:22] Elleo: just a sec [12:22] rebooting tablet [12:22] into [12:22] utouch [12:22] there goes the savegame4 [12:22] pfffft [12:33] ogra_: btw. any links on how to setup a chroot on the device? [12:33] not sure if i want to brick the device once more... [12:33] saidinesh5, like you would do on any other ubuntuu :) [12:33] lol okay googling [12:33] read up about deboostrap and the chroot command [12:33] Ah [12:34] debootstrap to create tthe chroot ... chroot to enter it and work in it [12:34] saidinesh5: vivid doesn't have any images in it yet, so devel still points to utopic, but devel-proposed is vivid-proposed [12:34] Tassadar: i was running utopic devel [12:35] Ubuntu 14.10 r243 [12:37] btw. Elleo ogra_ http://paste.kde.org/pdwakoory are the packages pulled in by qt5-default [12:38] so libegl-mesa is there [12:38] yeah, you dont really want that installed since it might bend the alternative for the driver to mesa [12:38] which is why i sugegsted working iin a chroot [12:38] *suggested [12:39] yeah thats what was bricking my device [12:39] that and sshfs (which even breaks multirom) [12:39] sshfs brings in fuse which somehow updates the kenel in a weird way [12:39] not the kernel, but the initramfs [12:39] mhm [12:40] i think so [12:40] all i could notice was it was in /boot [12:40] right, it is supposed to update the initrd for devices that need fuse filesystems during boot [12:40] and seemingly multirom doesnt cope well with that [12:40] multirom can't handle apt-get updating the kernel/initrd [12:41] because it rewrites the boot partition, which isn't ubuntu's to rewrite when installed in multirom [12:41] ( i doubt anyone cares, even for non multirom ... apt on touch is an adventure, if it breaks you gotta keep the pieces) [12:42] yeah, it can be hacked around, but I'm not sure if it is necessary [12:42] Ahh [12:42] ogra_: could you pastebin yoru schroot config file? [12:43] i dont have one [12:43] * ogra_ doesnt use schroot [12:43] just plain chroots [12:43] oh [12:44] ogra_: so where do i create the chroot in? [12:44] my home? [12:44] or in / ? [12:44] saidinesh5: you might actually be able to use the click tools to setup a chroot for you with minimal effort [12:44] your home [12:44] ohh [12:44] oh, right, that might work as well for an armhf chroot on your PC [12:45] but for armhf chroot don't i need scratchbox or something? [12:45] sudo click chroot -a armhf -f ubuntu-sdk-14.10 create <-- might work (on device) [12:45] Elleo: not sure, my ubuntu-sdk seems to be quite broken. it cant even compile the cmakebased helloscopes project [12:46] saidinesh5: the scopes template is broken for everyone as far as I can see :P [12:46] ohh O_O [12:46] saidinesh5: there's a missing dependency in the chroot that the sdk setups up: https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1387545 [12:46] Ubuntu bug 1387545 in qtcreator-plugin-ubuntu "New scope templates fail to run cmake: missing UseXGettext macro" [Undecided,Confirmed] [12:46] Ahh [12:46] i thought i was my tinkering [12:47] saidinesh5: on the desktop it'll use qemu for cpu emulation iirc, but I believe there's still some issues with some of the qt tools under those circumstances, could be worth a try first though to be sure [12:47] Elleo, saidinesh5, I thought this was fixed in the SDK PPA, are you using it? [12:47] * saidinesh5 checks [12:48] Ahh [12:48] ubuntu-sdk-team-ppa-trusty.list [12:48] was the ppa [12:48] i had [12:48] davidcalle: yep, I've got the sdk-team ppa enabled, and it didn't seem to help at the weekend [12:48] but i think it got disabled during distupgrade [12:49] davidcalle: although its possible I only tried to update ubuntu-sdk from it [12:49] davidcalle: so if the fix is in another package I might not have got it [12:49] davidcalle: ah yeah, there's an update to qtcreator-ubuntu-plugin [12:51] Elleo, it should bring new scopes templates (Still C++, but with some Qt libs to ease Json and XML parsing), and hopefully the xgettext fix [12:51] davidcalle: oh, interesting; I've already got my stuff working with the existing json lib, but might rewrite it [12:52] davidcalle: how's the Go based scope stuff coming? It'd be really nice to be able to use download-manager and content-hub from a scope, but the C++ APIs for those aren't publicly supported [12:54] Elleo, it exists and works, but I think that some issues are still being worked on. cwayne, do you know if we are going to have "official support" for Go soon? [12:55] davidcalle: ah, okay; I can probably hack around something with launching the browser to download things, but it'd be much nicer to do it directly [12:55] davidcalle: not sure when we'll have official support [12:55] Elleo: go get launchpad.net/udm [12:55] davidcalle: although, that said the content picker wouldn't be available since that's QML [12:55] sergiusens: the problem is that UDM breaks ABI from time-to-time [12:55] Elleo: it wraps over dbus [12:55] sergiusens: ah, good point [12:55] Elleo: so click chroot fails after [12:55] E: Couldn't download dists/utopic/main/binary-armhf/Packages [12:55] which doesn't break :-) [12:56] sergiusens: might be able to talk to content-hub directly over dbus too [12:56] sergiusens: would have to hard code the music app as the recipient of music files, but that's not the end of the world [12:57] although iirc there were some plans for content-hub stuff built into scopes discussed [12:57] so it might be worth just waiting for that to become clearer [12:57] saidinesh5: does your device's network connection work okay? [12:58] http://paste.kde.org/pudmstuml [12:58] Elleo: ^ [12:59] saidinesh5: not sure what to suggest I'm afraid, other than to try setting up a chroot normally; but since that'll also use debootstrap I suspect it might fail in the same way [12:59] ohh [13:00] :| [13:00] technically i should have a same chroot in my ubuntu-sdk right? [13:01] can i just scp it from my PC? [13:01] or it might take too long [13:01] hmm... [13:01] saidinesh5: I suspect that might get setup a little differently to allow for cpu emulation, not entirely sure the details of that though [13:02] ohh [13:02] hmm... [13:02] also Elleo i tried building a qt5 application just before [13:02] the device bricked [13:02] and tried running it again on a fresh install [13:03] http://paste.kde.org/pznombeqj [13:03] is what i get [13:03] saidinesh5: try ./skeyer_demo --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop [13:04] O_O === dandrader is now known as dandrader|afk [13:04] it works! [13:04] saidinesh5: mir wont accept a connection from a client unless it knows what app its coming from (which it gets via the .desktop), giving it the .desktop of an unconfined app will get it to load [13:04] Ahh [13:04] saidinesh5: normally it'd get that automatically when launched from the launcher [13:06] interesting [13:06] Elleo: any notes on how to run a qemu environment on the desktop then? [13:07] the ones installed by ubuntu-sdk [13:08] okay i think i can use click :D [13:08] click chroot blah blah blah run [13:08] but meh [13:08] $ qmake [13:08] qmake: could not find a Qt installation of '' [13:08] saidinesh5: 'click chroot -a armhf -f ubuntu-sdk-14.10 maint' should give you a shell [13:09] oh [13:09] what is maint for? [13:09] and same problem there too [13:09] might be that some qt dev packages aren't installed by default [13:09] ohh [13:09] saidinesh5: maintenance basically iirc [13:09] but shouldnt ubuntu-sdk take care of that? [13:10] Elleo: saidinesh5: that env is not an emulated one... that is a simple multiarch chroot [13:10] bzoltan_: ah, okay [13:10] saidinesh5: what exactly you try to do? [13:10] bzoltan_: i wanted to set up a development environment for ubuntu keyboard [13:11] bzoltan_: which is currently still qmake based === MacSlow is now known as MacSlow|lunch [13:11] i cant compile the packages on device cuz the qt5-default pulls in all the libgl packages and breaks the system [13:11] saidinesh5: ahh, I am sorry, but i am not familiar with the keyboard development env. How different is from the normal app development env? [13:11] bzoltan_, oh, are you back from vac. ? [13:12] bzoltan_, i have bug 1388569 for you then :) [13:12] bug 1388569 in ubuntu-ui-toolkit (Ubuntu) "popup dialog content shifted to the left in image 140" [Undecided,New] https://launchpad.net/bugs/1388569 [13:12] ogra_: No, I am still enjoying it [13:12] ah, k [13:12] can't set up a chroot on the device because..... i dont know. it just fails to download them http://paste.kde.org/pudmstuml bzoltan_ [13:12] then i'll ping again tomorrow :) [13:12] saidinesh5: have to pop out to get some lunch quickly, back shortly [13:12] Ah sure.. bon apetit :) [13:12] ogra_: without clicking to that bug I can tell you that they should use the popup properly ... just like it was problem with the settings app [13:13] bzoltan_, well, it seems ot be in all popups [13:13] ogra_: but i will pull kalikiana on it [13:13] *to [13:13] so now i m trying to get a qemu based shell up and running on the desktop so i can compile something to run on the tablet [13:13] bzoltan_, thanks === alan_g is now known as alan_g|lunch === dandrader|afk is now known as dandrader [13:50] mpt, hi, apn for multi sim needs some clarification in bug 1388044 [13:50] bug 1388044 in ubuntu-system-settings (Ubuntu) "[cellular] Setting carrier selection to 'Manual' does not persist" [Critical,In progress] https://launchpad.net/bugs/1388044 [13:50] specifically how it is laid out === adsumatal is now known as nadsumatal [14:00] hello [14:00] hey, when I popped my SIM into my maco, the dialer says that I have to unlock my pin [14:00] rickspencer3, longstanding issue [14:00] but when I go to settings, it implies that my SIM is unlocked [14:00] ogra_, is there a workaround? [14:01] set a PIN [14:01] ogra_, arg, so I forget my PIN which I have to enter to set a pin [14:01] * rickspencer3 shakes fist [14:02] rickspencer3: there's an MR that fixes it: https://code.launchpad.net/~tiagosh/telepathy-ofono/fix-sim-lock/+merge/238202 [14:02] rickspencer3: not sure where/when it landed though [14:02] didnt yet [14:02] ah, right [14:02] at least the same issue is still around in the promotion candidate on mako [14:03] QA saw it on friday [14:03] rickspencer3: I installed the packages from those manually and it fixed it for me [14:05] Elleo: any idea when the 'turn off autocorrect for email address' branch will land? === MacSlow|lunch is now known as MacSlow [14:05] cwayne: hopefully this week now that we've cleared up what the issue om26er was having was === salem_ is now known as _salem [14:08] rickspencer3: if it is the default pin it will be on a website somewhere, if it is a pin you have set try day and month of birth === alan_g|lunch is now known as alan_g [14:15] rickspencer3: downgrading telepathy-ofono package on my nexus5 fixed it for me. and i haven't seen the issue since (even though i've installed updates and even flashed over to rtm channel now) [14:20] kenvandine, morning! I saw that u-s-s hit vivid! :) [14:20] mterry, yes... but there are issues :-/ [14:20] kenvandine, oh :( [14:20] mterry, not in the wizard, that i know of though :) [14:20] the upower transition [14:20] the battery panel is causing a crash now [14:21] saidinesh5: did you try the explicit depends I suggested? I suspect different dependencies might get selected for the qt5 package if libgles2-dev is installed [14:21] kenvandine, oy [14:21] Elleo: oh wb [14:21] kenvandine, anything I can help with? [14:21] * saidinesh5 checks [14:22] mterry, you could figure out the crash if you have time :) [14:22] Elleo: it has qt5-default [14:22] so nope... thats a no go [14:22] kenvandine, how does this affect rtm? I assume the rtm silo did not include the upower stuff [14:22] it doesn't [14:23] phew [14:23] indeed [14:23] saidinesh5: yeah, but qtbase5-dev (which is the main thing qt5-default depends on that brings in libgl related things) has optional dependencies for different packages [14:23] the battery panel worked at some point in the vivid silo [14:23] but there was several pieces landing while it was held in proposed [14:23] and powerd was crashing at the same time as uss, but then that stopped crashing [14:24] saidinesh5: so different packages will get selected if you already explicitly list libgles2-mesa-dev vs libgles2-dev, etc. [14:24] Ohh [14:24] let me check [14:24] need to install the dbg packages to get a good trace [14:24] saidinesh5: I'd suggest trying the line of dependencies I listed and see what it plans to pull in [14:25] saidinesh5: as that certainly works for me on phones [14:26] kenvandine, want any help with the rtm silo? Is it just the continue bug or are there other scheduled rtm issues? [14:26] Elleo: http://paste.kde.org/pyqsdkiwg [14:27] so is it okay to go ahead? [14:27] saidinesh5: probably not, that's still bringing in libegl packages [14:27] saidinesh5: I guess something must differ between the tablet images and the phone images [14:27] i guess so [14:27] mterry, nah [14:27] but Elleo i think this is a phone image [14:27] mterry, just waiting for QA verification on that [14:27] i used multirom [14:28] and well it shows me a phone dialer [14:28] even the UI feels like a phone's [14:28] saidinesh5: it's a nexus 7 specific image though [14:28] ohh [14:29] saidinesh5: they have different hardware adaptation, the user stuff is all the same at the moment though [14:29] hmm... [14:29] but why is qemu on desktop failing for me [14:29] http://paste.kde.org/p6szhi6v3 [14:30] (which it was unable to locate) [14:32] saidinesh5: actually, a better option might be to use the ubuntu-emulator [14:32] saidinesh5: then you'll get an armhf environment [14:32] hmm..... but wouldnt it suffer the same fate as broken packages ? [14:32] like in nexus 7 [14:33] also from what i remember about android emulator [14:33] saidinesh5: I'm hoping it'll work more like the nexus 4 which works fine [14:33] it was really slow [14:33] oh [14:34] * saidinesh5 is setting up an emulator [14:35] also Elleo i only have 6GB ram [14:35] => emulator might not be that optimal [14:35] but lets see [14:35] rickspencer3, your "we cant ship with that" means for final, right ? we shouldnt hold back promotion of the milestone for this ? [14:36] ogra_, well, first of all, I was expressing my opinion, not making a final decision ;) [14:36] and second, yeah, I mean for final [14:36] rickspencer3, ah, cool then [14:36] saidinesh5: yeah, it'll almost certainly be quite slow, but no slower than qemu based compilation (basically does the same thing); 6GB of RAM should be fine though [14:36] ogra_, thanks for asking [14:36] :) [14:36] oh [14:37] Elleo: isnt there some nice cross compiler? [14:37] saidinesh5: that hits problems with qmake based projects at the moment [14:38] Ah [14:39] the only reason i m still on qmake for this one is simply because it nicely gets all the maliit-defines [14:39] otherwise i dont mind moving to CMake [14:40] well that and better QtCreator support === chihchun_afk is now known as chihchun [14:55] Hey what is the current command to flash Bq phone? Something that would be equivalent to what devel-proposed channel for nexus4 used to be. I'm getting mixed info here.. [15:00] Elleo: btw. whats the ppa for the fixed ubuntu-sdk? === _salem is now known as salem_ [15:03] saidinesh5: https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/ppa === chihchun is now known as chihchun_afk [15:03] saidinesh5: haven't tested it though, as I already fixed my chroot for scope dev manually [15:03] ohh [15:03] what exactly was the problem Elleo? [15:03] like is it a simple 1-2 line fix? [15:04] saidinesh5: yeah, it's just that cmake-extras isn't installed in the chroot by default [15:04] Ahh [15:04] which is used in the scope template [15:04] let me test it out then [15:07] Ahh there seem to be multiple issues [15:08] weird... [15:09] E: Failed to change to directory ‘/src/’: No such file or directory [15:10] I: The directory does not exist inside the chroot. Use the --directory option to run the command in a different directory. [15:10] Ahh [15:10] looks like the usual troubles with chroot [15:12] so Elleo i cant chroot into another filesystem that is mounted in /media/ ? [15:16] saidinesh5: you can mount it into the chroot if needed, e.g. mount -o bind /media/ /path/to/your/chroot/media [15:16] saidinesh5: then anything in /media/ will be accessible in the chroot [15:16] ohh [15:16] * saidinesh5 tries === chihchun_afk is now known as chihchun [15:21] Elleo: the problem with chroot is still the same [15:21] broken qt5 packages [15:22] * saidinesh5 now checks ubuntu emulator [15:23] saidinesh5: ah, hang on; are you installing the armhf version of the packages? [15:23] yep === alan_g is now known as alan_g|tea [15:23] saidinesh5: although that said apparently since the chroot doesn't use qemu it probably won't be workable with qmake anyway [15:24] :| [15:24] the ubuntu-emulator's probably the simplest option if it works [15:24] lets see [15:24] i just booted it up [15:24] its very slow though [15:25] and not sure how i m gonna move files from emulator to pc fast enough [15:25] without resorting to adb push pull etc.. [15:25] well adb push is probably the fastest method [15:25] maybe making a tar first would be faster [15:26] hmm... [15:26] this sucks [15:27] i locked myself out of the emulator [15:27] and the password i ve entered doesnt seem to be working [15:27] the emulator hardcodes 0000 [15:27] Ahh [15:27] thanks ogra_ === alan_g|tea is now known as alan_g === salem_ is now known as _salem === _salem is now known as salem_ [15:33] Elleo: libegl1-mesa-dev libegl1-mesa-drivers libgles2-mesa-dev libllvm3.5 libmirclient-dev libmirclient8driver-mesa [15:33] saidinesh5: I'd suggest just let the emulator try whatever it likes and see what happens [15:33] saidinesh5: I'm not sure exactly what it is that causes issues on the nexus 7 [15:33] does that look like trouble? === salem_ is now known as _salem [15:34] saidinesh5: might even be multiboot related if some of the packages install kernel modules in the initramfs [15:34] saidinesh5: try and find out ;) [15:34] lol [15:35] at least the emulator can be recreated quicker than reflashing a real device [15:35] nah Elleo definitely not multiboot related [15:35] because the moment i install qt5 packages [15:35] i cant start any program either [15:35] mhm [15:35] trying it out [15:36] oh wait [15:36] nope [15:36] i was wrong [15:37] oh? [15:37] well the pacges are broken in [15:37]