[10:29] <zzarr> hello!
[10:46] <zzarr> if there is a Vulkan driver for a GPU, would that matter to MIR (could I get MIR running with the help of it in the future?)
[13:00] <suebt> Hey there, I'm trying to get kivy (https://kivy.org/) running on Ubuntu Touch. The Python stuff part is working but I have issues with SDL and (maybe) MIR. It would be super cool if you could look into this whether you have an idea what's causing the error.
[13:01] <suebt> So, the program is starting and segfaulting when loading sdl
[13:01] <anpok_> sdl2 that is?
[13:01] <suebt> yes
[13:02] <anpok_> what sdl2 library are you using
[13:02] <suebt> Custom builds (SDL2-2.0.4)
[13:02] <anpok_> hm bschaeffer is not around
[13:02] <suebt> I tried with packaged versions as well.
[13:02] <suebt> Both resulting to the same error
[13:03] <anpok_> he would know better.. the symptoms sound familiar
[13:03] <suebt> okay, thanks, I'll just drop some links to the logs in case they're useful?
[13:05] <suebt> https://drive.google.com/folderview?id=0B4EyY4wSGSyjNWwzVGo1eHBUc1k&usp=sharing Here are some stack traces. "kivy_log" is the output from python.
[13:13] <greyback> suebt: hey, those are "syscall traces" - you used strace, right? That tool reports all the calls the app makes to the kernel. This doc shows how to get stacktraces: https://wiki.ubuntu.com/Backtrace which would help us more
[13:19] <suebt> greyback: okay, thanks. Yes, those where strace logs. Here is a gdb log: https://drive.google.com/folderview?id=0B4EyY4wSGSyjMFhlRDh6V2NrNjg&usp=sharing
[13:20] <suebt> or better http://paste.ubuntu.com/15551628/
[13:21] <greyback> suebt: ok, looking, it's not a useful backtrace, as you only have 2 frames of the stack. __GI_raise indicates an exception was thrown.
[13:22] <suebt> hmm, is there anything I can do to provide more useful information about this?
[13:22] <greyback> suebt: suggest you install the debug packages for mir, and libc6-dbg, and then try again
[13:23] <suebt> okay, libc6-dbg is installed. Will install mir debug packages
[13:23] <greyback> suebt: in gdb, also do "catch throw" before running
[13:23] <suebt> okay, will do, thanks!
[13:23] <greyback> thank you
[13:25] <suebt> greyback: can you possibly point me on which mir debug packages you mean?
[13:27] <greyback> suebt: probably libmirclient9-dbgsym
[13:28] <suebt> greyback okay, thanks, let's see...
[13:39] <suebt> Hmm... it's not in vivid repos, is there a ppa for it?
[13:44] <greyback> suebt: you probably need this: https://wiki.ubuntu.com/DebuggingProgramCrash#Non-built-in_debug_symbol_packages_.28.2A-dbgsym.29
[13:51] <suebt> greyback: It throws a lot of "W: Failed to fetch ..." errors if I try this …
[13:52] <greyback> suebt: can you pastebin me what you see and the commands you used?
[13:53] <greyback> and also the contents of /etc/apt/sources.list.d/ddebs.list
[13:55] <suebt> greyback: This is what I did: http://paste.ubuntu.com/15551845/ and here is my  /etc/apt/sources.list.d/ddebs.list: http://paste.ubuntu.com/15551853/
[13:56] <greyback> suebt: oh, you're working on the phone
[13:56] <suebt> yeah sure :)
[13:56] <greyback> suebt: ok, I need to change the advice (sorry, I thought you were developing on your desktop)
[13:56] <suebt> oh np :)
[13:57] <suebt> I don't have mir on the desktop
[13:57] <greyback> suebt: please edit the ddebs.list file to just contain this:
[13:57] <greyback> deb http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid main/debug
[13:57] <suebt> okay
[13:57] <suebt> (I'm on rc-proposed tho, not sure if that changes something)
[13:58] <greyback> explanation: the phone uses a PPA to deliver software newer than vivid (which is about a year old now). So you need a special place to find debug packages for that PPA (which is what I gave you)
[13:59] <greyback> suebt: nah, perfect. Best place for developing
[13:59] <suebt> ah okay :)
[13:59] <suebt> meh it doesn't want to write to that file oO
[13:59] <greyback> I think you're nearly out of disk space too
[14:00] <suebt> yep xD
[14:00] <suebt> nano doesn't work properly ... Or is it normal i can't save that file?
[14:01] <greyback> are you root?
[14:01] <suebt> I am.
[14:01] <greyback> I suspect nano and "adb shell" don't work well together
[14:02] <greyback> the return key seems to disappear
[14:02] <suebt> yeah, I'll move the file manually ...
[14:02] <greyback> delete it and do
[14:02] <greyback> echo "deb http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid main/debug" | sudo tee -a /etc/apt/sources.list.d/ddebs.list
[14:03] <suebt> oh that would've been faster :)
[14:03] <suebt> done
[14:04] <greyback> now after apt update you should be able to find the mir debug packages
[14:05] <suebt> phablet@ubuntu-phablet:~/Documents$ sudo apt-cache policy libmirclient
[14:05] <suebt> E: Write error - write (28: No space left on device)
[14:06] <suebt> ha /0\
[14:06] <greyback> sudo apt-get clean
[14:06] <greyback> might help
[14:07] <suebt> done, took a second to run :)
[14:07] <suebt> will delete some picture
[14:07] <suebt> *s
[14:08] <suebt> meh, still no space left
[14:08] <suebt> Think, I'd better do a clean reset, should I?
[14:16] <greyback> suebt: from experience, you'll hit this again & again
[14:17] <greyback> you'd be better developing in a chroot. Let me try find a link to a handy email
[14:20] <suebt> greyback: Okay, that'd be super nice :)
[14:24] <greyback> suebt: http://pastebin.ubuntu.com/15552039/
[14:25] <greyback> oh, "sagu" should be "sudo apt update"
[14:25] <greyback> oh, "sagy" should be "sudo apt install"
[14:26] <suebt> greyback: really nice, thanks, I'll look into it. Just finish resetting my device up ...
[14:26] <greyback> suebt: fixed: http://pastebin.ubuntu.com/15552049/
[14:26] <greyback> http://pastebin.ubuntu.com/15552056/
[14:27] <greyback> is better
[14:57] <suebt> greyback: cool, I'm back (with a fresh ubuntu phone)!
[14:57] <suebt> So this is to be setup on the phone?
[14:57] <suebt> I'll try
[14:58] <greyback> suebt: let's see
[14:59] <suebt> hah, need to enable developer mode first :)
[15:05] <suebt> whut? "E: Write error - write (28: No space left on device)"
[15:05] <suebt> What does this "reset" actually do xD ... let me reflash
[15:12] <camako> zzarr, hi
[15:13] <camako> zzarr, do you have source access to the GPU driver you've mentioned?
[15:14] <camako> zzarr, you'd need to implement the Window System Integration extensions to be able to display
[15:14] <camako> WSI extensions for Mir, that is... using the Mir client library.
[15:15] <camako> We have not officially published all the headers you'd need.
[15:15] <camako> But they are available in our dev trunk
[18:22] <suebt> greyback: had to go off for some time. "sudo apt install debootstrap" doesn't work, I assume I should add the universe repo?
[18:23] <greyback> suebt: did you "apt update" first?
[18:24] <suebt> greyback no, will try
[18:25] <suebt> greyback: oh, it works now, thank you!
[18:25] <greyback> np
[18:40] <suebt> greyback: hhmm, I get "usermod -G sudo phablet" >> "usermod: user 'phablet' does not exist"
[18:41] <suebt> "sudo ./ch -r vivid-chroot/" >> "logname: no login name
[18:41] <suebt> logname: no login name"
[18:41] <greyback> suebt: what is the user of your chroot? "echo $USER"
[18:41] <suebt> "echo $USER root"
[18:41] <suebt> "echo $USER" >> "root"
[18:42] <greyback> suebt: if you enter the chroot as not-root, i.e. remove the "-r" switch, what is the user?
[18:42] <suebt> still root ...
[18:42] <suebt> without -r
[18:44] <greyback> oh, you were root when creating the chroot, weren't you?
[18:44] <suebt> hmm yeah, cause of sudo?
[18:45] <greyback> even before?
[18:45] <suebt> "echo $USER" > phablet -> outside of my chroot. At least now ...
[18:45] <greyback> ok, that's good
[18:46] <suebt> Does this matter?
[18:46] <greyback> not hugely
[18:46] <suebt> it also says "mount: mount point /home/phablet/vivid-chroot//home/phablet does not exist"
[18:48] <greyback> I'm not sure what's gone wrong. debootstrap should know about the phablet user.
[18:49] <suebt> can't I create it manuallyß
[18:49] <suebt> *?
[18:49] <greyback> yeah, you can
[18:49] <greyback> I just never have to
[18:50] <greyback> so I'm confused what is different
[18:50] <suebt> maybe I did something wrong?
[18:50]  * suebt double checks everything
[18:51] <greyback> suebt: fyi, you can blow everything away by just deleting the $HOME/vivid-chroot directory
[18:51] <suebt> ok
[18:51] <suebt> but I think I did it exactly the same
[18:51] <suebt> let me try again
[18:51] <greyback> suebt: only difference I can think of is that usually I SSH into the device. I find adb shell sometimes causes me problems
[18:52] <greyback> but the instructions I gave you are exactly those I follow
[18:52] <suebt> Ah, okay, I can try to use ssh
[19:10] <suebt> adb seems to be the issue indeed! No errors via ssh, yet
[19:10]  * suebt needs to go off for today soon tho, thanks for all your help, will continue tomorrow.