=== chihchun_afk is now known as chihchun === marcusto_ is now known as marcustomlinson [08:58] duflu: your "Needs Info" answered? https://code.launchpad.net/~alan-griffiths/mir/death-to-SurfaceConfigurator/+merge/254796 [08:59] * duflu looks [08:59] alan_g: Approved [08:59] thanks [09:04] 2015 might be the year I start using C99 for everything instead of C89 [09:05] Although that might have happened in 2010 [09:05] Hmm [10:01] where can I find the instructions for the proving shell? i.e. how to resize something [10:02] greyback: Alt+middle button [10:03] bah, no middle button on my trackpad [10:03] alan_g: thanks [10:11] greyback: three finger gesture? [10:16] alan_g: perfect, ta [10:18] greyback: For the latest: http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/doc/demo_shell_controls.md [10:19] If anything works with multi-touch-pads, that's partly by accident. Mir doesn't really know about touchpads directly [10:19] duflu: still here? (thanks for the link, always fail to locate that file) [10:19] greyback: Off to make dinner now [10:19] duflu: fair enough, bon appetit === chihchun is now known as chihchun_afk === alan_g is now known as alan_g|lunch === alan_g|lunch is now known as alan_g === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === marcusto_ is now known as marcustomlinson [14:45] alan_g, greyback: I've sent you an email with the unity8.logs of the (mir-)failures I see (and a comparison for non-failure) in the hope you'll be able to find anything odd that might help in my search for the culprit of the crash. [14:46] MacSlow: did you ascertain if unity8 crashes or not? [14:47] if it does, why not attach gdb with "gdb -p `pidof unity8`" [14:47] that should give you a stacktrace when it crashes [14:48] greyback, didn't manage to catch it yet that way [14:48] greyback, so I assumed there has to be another way [14:52] MacSlow: none that I know of. Could set any coredump to end up in your $HOME with: [14:52] sudo bash -c 'echo "$HOME/core.%e.%p" > /proc/sys/kernel/core_pattern' && ulimit -c unlimited [14:57] greyback, *sigh* when I want it to crash it doesn't :) [14:57] greyback, no core file [15:05] MacSlow: can you watch "ps ax" to see if unity8 is indeed restarting? [15:05] greyback, one sec... [15:10] greyback, no... on /lib/modules is 99% full all other partitions provide still enough free storage [15:11] MacSlow: so unity8 is not restarting during the test case. ok [15:12] greyback, I don't get any core dump files... but /var/crash gets some files... [15:12] but these are prefixed with _usr_bin_unity8 which is not what I would expect from the AP-test... [15:12] as it should run the local unity8 from the source-tree [15:13] MacSlow: I didn't think AP did that [15:13] but I'm not certain [15:13] greyback, what start local unity8 or dump to /var/crash ? [15:13] MacSlow: from local unity8 [15:14] again, I'm unsure [15:14] greyback, I hope you're wrong... otherwise I've been wasting some time [15:16] well it's easy to verify [15:20] greyback, just moved /usr/bin/untiy8 and re-ran the AP-test... still works [15:20] MacSlow: ok good [15:20] greyback, I would have been very surprised, if that would not have worked [15:24] greyback, it failed but did not produce any core or crash-file (in /var/crash) [15:24] MacSlow: ok, it's not a crash, good [15:25] I've /usr/bin/unity8 still moved aside [15:28] greyback, I wonder if the issue is a DBus one... looking at the failure-output there's an error from DBus right after the autopilot process-helper reported unity8 started/running... [15:34] MacSlow: DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) <- that does indicate to me AP asked something of unity8, but unity8 has not replied [15:35] does the UI lock up? [15:36] but we're in "launch_unity" [15:37] so unity8 is being launched, but AP unable to contact it on the bus [15:38] "Unable to register object on D-Bus! Testability interface will not be available." [15:38] ok that's a problem [15:38] next question is _why_ it's unable to register on the bus [15:38] is there a previous unity8 instance still alive? [15:38] greyback, you see the question-marks above my head get bigger and bigger [15:39] greyback, it should not... but let me try soemthing else... [15:39] MacSlow: dbus-monitor show you useful info? [15:40] Testability driver loaded. Wire protocol version is "1.4". [15:40] Testability driver loaded. Wire protocol version is "1.4". [15:40] Unable to register object on D-Bus! Testability interface will not be available. [15:40] why the first line printed twice? [15:40] is hte testability plugin being loaded twice somehow? [15:40] and the second time it fails, as the first time succeeded [15:41] dbus is available, as the clipboard registers ok [15:41] greyback, dbus-monitor dumps too much... [15:42] "Signal caught by Mir, stopping Mir server.." [15:42] this log is full of oddness [15:44] greyback, one of the AP-folks is currently also looking over this... I hope he's able to make more sense of this === dandrader is now known as dandrader|lunch === dandrader|lunch is now known as dandrader === sturmflut__ is now known as sturmflut === chihchun_afk is now known as chihchun