[09:04] <willcooke> kgunn, imported:  https://code.launchpad.net/~mlankhorst/xmir/xmir
[09:04] <mlankhorst> goodie
[09:04] <kgunn_> \o/
[09:04] <kgunn_> @vogons ^
[09:04] <kgunn_> @unity ^
[09:05] <kgunn_> bregma: bschaefer ^
[09:05] <mlankhorst> but please use the git repo :P
[09:07] <willcooke> mlankhorst, looks like it failed actually:  http://launchpadlibrarian.net/196684280/mlankhorst-xmir-xmir.log
[09:08] <mlankhorst> .. :/
[09:09] <mlankhorst> bug in bzr import it seems, looks like it can't handle GPG signed releases..
[09:13] <mlankhorst> just use raw git :P
[09:17] <willcooke> kgunn_, can we do that in the short term?
[09:18] <kgunn_> willcooke: what's that ? sorry...in case i disconnected
[09:18] <willcooke> kgunn_, there seems to be an issue with LP pulling in the Git repo.
[09:18] <kgunn_> sure
[09:19] <willcooke> kgunn_, can we work with it in Git for now?
[09:19] <kgunn_> we'll just have to get the packages uploaded manually using the trainguards
[09:19] <willcooke> Or we could some kind of manual push in to LP
[09:19] <kgunn_> which is simple
[09:19] <willcooke> ok!
[09:19] <willcooke> nice
[09:20] <kgunn_> yeah...so mlankhorst if you have a new set of packages that you'd say is ready to be put into a ppa & part of our demo lemme know
[09:42] <mlankhorst> oke
[09:42] <mlankhorst> when can I expect mir 0.11? :P
[09:43] <mlankhorst> or is there a ppa somewhere with the cursor changes?
[09:44] <kgunn> mlankhorst: so the ppa i shared, will have all those changes
[09:44] <mlankhorst> oke
[09:44] <kgunn> mlankhorst: but i think that mirevent2 landed as part of mir0.11
[09:44] <kgunn> however
[09:44] <kgunn> the qtmir utilization of it is in lag
[09:44] <kgunn> e.g. we'll test and land that next
[09:44] <mlankhorst> oke I'll build 0.11 myself then..
[09:45] <dandrader> kgunn, the fix for the silo 0 https://code.launchpad.net/~alan-griffiths/qtmir/port-to-msh-Shell/+merge/247844/comments/615755
[09:45] <kgunn> mlankhorst: oh...actually, there is a ppa for testing that has just mir0.11
[09:45] <kgunn> not trunk (i think)
[09:45] <dandrader> kgunn, gotta apply this patch to this MP http://paste.ubuntu.com/10069953/
[09:45] <kgunn> one sec
[09:45] <kgunn> dandrader: ack
[09:46] <kgunn> mlankhorst: ah yeah...so this silo/ppa
[09:46] <kgunn> http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-012
[09:46] <kgunn> is the testing silo/ppa for mir0.11
[09:46] <mlankhorst> oke
[09:46] <mlankhorst> and if I use that with unity-system-compositor I get the mouse events?
[09:47] <kgunn> mlankhorst: mmm....on desktop yeah i thikn you just get it....on andrdoid devices, you have to use the u-s-c that's in the ppa for the demo (vivid silo 0)
[09:47] <kgunn> anpok: ^ right ?
[09:48] <kgunn> mlankhorst: difference being that hw cursor is used on desktop, and android doesn't suport hw cursor
[10:01] <alf_> mlankhorst: Hi! If I have a patch for the mesa mir egl backend, what's the best way to propose? Diff against ubuntu branch on debian git, debdiff, some other way?
[10:02] <mlankhorst> alf_: ask raof..
[10:05] <alf_> mlankhorst: OK, forget I mentioned the mesa mir egl detail :) I mean in general, how would do you prefer me to propose a package update for mesa.
[10:06] <mlankhorst> feel free to upload and I'll merge the changes back to the packaging
[10:07] <alf_> mlankhorst: upload where?
[10:07] <mlankhorst> archive?
[10:08] <mlankhorst> or do you want a review :P
[10:08] <alf_> mlankhorst: I don't have ubuntu archive access, if that's what you mean. I could push to a PPA though.
[10:08] <mlankhorst> oke then just send me a diff ..
[10:09] <alf_> mlankhorst: ok, thanks. I will do so after some wider testing (probably will push to PPA first anyway).
[10:09] <alf_> mlankhorst: (after 0.11 is released)
[10:25] <kgunn> alan_g: hey mornin' would you mind updating your qtmir branch based on dandrader's feedback ?
[10:25] <kgunn> https://code.launchpad.net/~alan-griffiths/qtmir/port-to-msh-Shell/+merge/247844/comments/615755
[10:25] <kgunn> ....we _think_ it's the last thing to change in order to test/rel mir0.11
[10:25] <alan_g> kgunn: just compiling it before pushing
[10:26] <kgunn> thank you sir
[10:27]  * alan_g wishes there were automated acceptance tests that pick this up.
[10:29] <alan_g> kgunn: dandrader - done
[10:29] <kgunn> cool
[10:29] <mlankhorst> alf_: hm do I need a even newer version of mir to kill of the thread mir creates?
[10:29] <kgunn> thank you
[10:29] <dandrader> alan_g, thanks
[10:29] <mlankhorst> I want to kill the thread proxy in Xmir
[10:30] <mlankhorst> makes input handling slightly easier for me..
[10:32] <alf_> mlankhorst: It's now my turn to tell you 'ask RAOF' :) But assuming what you want is an event fd, that didn't make it into 0.11 AFAICT.
[10:32] <mlankhorst> aw..
[10:32] <mlankhorst> yeah probably not
[10:33] <alf_> mlankhorst: https://code.launchpad.net/~raof/mir/provide-event-fd/+merge/247794 , in case you want to check if this is good enough for your use cases
[10:35] <mlankhorst> it probably is
[10:36] <mlankhorst> the main thing I worry about is if my hack that copies the full event will hold until mir advanced enough for that one..
[10:36] <mlankhorst> it's a lot easier to rework events after that provide-event-fd code is merged
[10:55] <Saviq> hey guys, does that crash ring a bell for you bug #1418456? mardy can't get unity8 to start on an Atom netbook
[10:56] <ogra_> its not only free sowftware but even double free software :P
[10:57] <alan_g> alf_: you were looking at a heap corruption recently ^
[11:10] <alf_> alan_g: doesn't look familiar, it seems that an exception(?) happens and we are unwinding the stack when we get the memory error
[11:11] <alan_g> alf_: ack
[12:01] <mardy> alan_g, alf_: I've that machine running, if you want feel free to ask me more questions for debugging, I can give you the results right away
[12:04] <alf_> mardy: could you run unity8 under gdb?
[12:04] <mardy> alf_: sure; any specific parameters or env variables to set?
[12:05] <alf_> mardy: no params, but type 'catch throw' in gdb before running
[12:05] <alf_> mardy: (so it will stop when an exception is thrown)
[12:07] <mlankhorst> so why is my touchpad in unity-session-compositor seen as a touch event? :s
[12:07] <mardy> alf_: but I should export QT_QPA_PLATFORM=ubuntumirclient, right? Otherwise it seems it's trying to talk to X
[12:08] <mlankhorst>
[12:09] <mardy> alf_: or maybe export QT_QPA_PLATFORM=mirserver?
[12:10] <alf_> mardy: I haven't tried in a while but unity8 env. variables I used for manual invocation are: MIR_SERVER_NAME=session-0 MIR_SOCKET=/run/mir_socket QT_QPA_PLATFORM=mirserver
[12:11] <mardy> alf_: anyway, looks like it's quitting immediately, no crashes (but I see a "Gtk-WARNING **: cannot open display:" message (Gtk??)
[12:11] <mardy> alf_: ok, let me try with those
[12:11] <alf_> mardy: perhaps MIR_SOCKET is different now
[12:13] <mardy> alf_: even with those variables, it exits immediately, with that Gtk warning
[12:13] <alf_> mardy: oh, are you running USC?
[12:14] <mardy> alf_: so, I've been running this commands from a text terminal, after doing a "sudo service lightdm stop"
[12:14] <alf_> mardy: so USC has stopped too
[12:15] <alf_> mardy: let's go back a step and try with the demo servers only
[12:15] <alf_> mardy: Install the mir-demos package (if you don't have it already)
[12:17] <mardy> alf_: done
[12:18] <mardy> alf_: I even tried the mir_demo_server before, but it took control of the terminal and I didn't know how to quit or switch to another terminal
[12:23] <alan_g> mardy: the mir servers will exit on Ctrl+Alt+BkSp
[12:24] <alan_g> Or SIGTERM etc
[12:28] <alan_g> It is easiest if you can get a terminal session from another device - e.g. ssh
[12:32] <greyback_> mardy: this is my command to start unity8 on desktop: http://pastebin.ubuntu.com/10072333/
[12:33] <alf_> mardy: be careful to run *sudo* mir_demo_server
[12:33] <willcooke> mlankhorst, so still issues with the pointer in xmir?
[12:33] <mardy> greyback_: it still quits immediately, with that Gtk warning
[12:33] <mardy> alf_: ah, let me try
[12:33] <mlankhorst> seems to right now, but I don't know if a fix has made it in to qtmir yet..
[12:33] <alf_> mardy: do you have ssh access to the machine?
[12:34] <mardy> alf_: yep
[12:34] <greyback_> mardy: that command depends on USC running
[12:34] <mardy> alf_: so, with the demo server I get a black screen and a working mouse pointer
[12:34] <mardy> greyback_: ok, I'll try that later as soon as we confirm with alf_ that the mir things are working
[12:35] <alf_> mardy: ok keep that running and ssh to the machine
[12:36] <mardy> alf_: yep, done
[12:36] <alf_> mardy: as first test run in ssh "sudo mir_demo_client_egltriangle"
[12:36] <alf_> mardy: you should see a rotating triangle on screen
[12:37] <mardy> alf_: yes, it works
[12:38] <alf_> mardy: ok, stop it (ctrl-c), and run 'sudo mir_demo_server --host /tmp/mir_socket -f /tmp/mir_nested'
[12:38] <mardy> alf_: ok, no changes on screen, but the thing is running
[12:39] <alf_> mardy: ok, new ssh and run 'sudo mir_demo_client_egltriangle -m /tmp/mir_nested'
[12:39] <mardy> alf_: works fine, too
[12:40] <alf_> mardy: ok, good, so base mir is working
[12:41] <alf_> mardy: now kill every mir related process
[12:41] <alf_> mardy: and 'sudo start lightdm'
[12:41] <alf_> mardy: that should start usc, and try to run unity8 and fail
[12:42] <alf_> mardy: but usc should stay running
[12:42] <willcooke> anpok, were you working on the input stuff in qtmir for pointer events etc?
[12:42] <alf_> mardy: then ssh and use e.g. greyback's invocation to start unity
[12:42] <mardy> alf_: so, I should login using the unity8 session, right?
[12:44] <alf_> mardy: actually before you log in do a 'ps -Af | grep unity', does it show anything?
[12:45] <mardy> alf_: ops, too late, I already logged in. It shows USC, unity8-dash and a couple of processes related to unity-scopes
[12:45] <alf_> mardy: no problem, just wanted to make sure USC wasn't already running
[12:46] <mardy> alf_, greyback_: always the same: http://pastebin.ubuntu.com/10072557/
[12:48] <alf_> mardy: hmm, let's see where the mir_socket is created at, try 'find /var /tmp /run -name mir_socket'
[12:49] <greyback_> mardy: could you put 'import QtQuick 2.2; Rectangle{ color: "blue" }' into a test.qml file, and do the above command, but replacing /usr/bin/unity8 with "qmlscene test.qml"
[12:49] <mardy> alf_: not found
[12:51] <mardy> greyback_: same output as above; so I guess this is due to the missing mir socket
[12:51] <greyback_> mardy: yeah, tho am surprised it's not printing an error
[12:52] <alf_> mardy: try 'cat /proc/$(pidof unity-system-compositor)/cmdline'
[12:52] <alf_> mardy: and 'cat /proc/$(pidof unity-system-compositor)/environ'
[12:52] <alf_> mardy: perhaps they will give us a clue
[12:53] <alf_> greyback_: The invocation you pasted is for a nested unity8, right?
[12:53] <greyback_> alf_: correct
[12:53] <mardy> alf_: the first says /usr/sbin/unity-system-compositor--disable-inactivity-policy=true--on-fatal-error-abort--file/run/lightdm-mir-0--from-dm-fd12--to-dm-fd21--vt8--enable-hardware-cursor=true
[12:54] <mardy> alf_: the second is XDG_SEAT=seat0XDG_VTNR=8PWD=/
[12:54] <greyback_> alf_: to test qtmir is working, stop unity-system-compositor, run "DESKTOP_SESSION=unity8-mir QT_QPA_PLATFORM=mirserver qmlscene test.qml"
[12:54] <alf_> mardy: ok, so the file you are looking for is
[12:55] <alf_> mardy: '/run/lightdm-mir-0'
[12:56] <mardy> alf_: yes, it's there, it's a socked owned by root  with 777 permissions
[12:56] <alf_> mardy: hmm, but that was already correct in greyback's invocation...
[12:56] <mardy> greyback_: should I run your command as root?
[12:57] <greyback_> mardy: yes
[12:57] <mardy> ahh
[12:57] <greyback_> sorry, I always forget that
[12:57] <greyback_> and yeah, you need ssh access to stop it
[12:58] <mardy> greyback_: nope, nothing changed, same output
[12:58] <greyback_> mardy: ok that's not expected
[12:59] <greyback_> mardy: it crashes right?
[12:59] <greyback_> could you grab a backtrace?
[12:59] <mlankhorst> I'm not a mir-dev.. but shouldn't input_event_type_to_string handle type_pointer ?
[12:59] <mardy> greyback_: no, it looks like a clean exit "[Inferior 1 (process 12590) exited with code 01]"
[13:00] <mardy> greyback_: and it's even claiming that your process is inferior ;-)
[13:00] <greyback_> :)
[13:00] <mardy> greyback_: is that Gtk warning expected?
[13:01] <greyback_> mardy: no
[13:01] <alf_> greyback_: can we (try) to connect one of the mir demos to usc, to check if at least that part is OK?
[13:01] <greyback_> alf_: go for it
[13:01] <mardy> greyback_, alf_: do you think that a strace can help?
[13:01] <greyback_> mardy: I'm extremely confused, so yeah, give me anything you think of
[13:02] <alf_> greyback_: Well, it was mostly a question of how to make USC accept it? What environment should we set? MIR_SERVER_NAME=session-0 DESKTOP_SESSION=unity8-mir ?
[13:03] <greyback_> alf_: MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket \
[13:03] <greyback_> MIR_SERVER_PROMPT_FILE=1 \
[13:03] <greyback_> MIR_SERVER_HOST_SOCKET=/run/lightdm-mir-0 \
[13:03] <greyback_> MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket \
[13:03] <greyback_> MIR_SERVER_NAME=session-0 \
[13:04] <greyback_> those should do the trick
[13:04] <mlankhorst> willcooke: https://bugs.launchpad.net/qtmir/+bug/1417650 seems this bug is related?
[13:04] <alf_> mardy: when you are done strace-ing, you could try 'mir_demo_client_egltriangle' with the environment greyback pasted above to see if at least the demo client can connect to usc
[13:05] <mardy> greyback_, alf_: https://launchpadlibrarian.net/196699566/unity8-strace.log
[13:05] <willcooke> mlankhorst, aha!  So it's being worked on already, right?
[13:05] <willcooke> I will speak to kgunn and the guys here shortly....
[13:05] <mlankhorst> I'm not sure if it's worked on specifically..
[13:05] <mlankhorst> but lets hope so
[13:05] <mardy> alf_: nope: "Can't get connection"
[13:06] <alf_> mardy: sudo?
[13:07] <alf_> mardy: I noticed in strace that you are running 32-bits (i386), perhaps that could be significant (or not)
[13:08] <mardy> alf_: yes, I started it from within a "sudo -i" environment
[13:09] <greyback_> mardy: could you run the qmlscene line in gdb, break on gdk_init and backtrace it please
[13:09] <mardy> alf_: if I add the "-m /run/lightdm-mir-0" option to the egltriangle test, then it connects and apparently runs, though nothing is visible on screen
[13:10] <alf_> mardy: ah, right, this is a client -m is the correct switch
[13:10] <willcooke> mlankhorst, if we need it looking at I can ask
[13:11] <alf_> mardy: ok, that's expected, usc doesn't bring it to the foreground
[13:11] <alf_> mardy: so the socket works fine
[13:11] <mardy> greyback_: so, it doesn't hit gdk_init
[13:12] <greyback_> mardy: how about gdk_display_open
[13:12] <mardy> greyback_: gtk_init() is hit, instead
[13:12] <greyback_> ah
[13:12] <alf_> mardy: I leave you in greyback_'s capable hands for now (he is more familiar with the qt/unity8 side of things anyway), got to get some lunch, be back in a bit
[13:13] <mardy> alf_: ok, thanks a lot
[13:13] <mardy> greyback_: http://paste.ubuntu.com/10072964/
[13:13] <mlankhorst> willcooke: well it looks from the diff like it's useful..
[13:13] <mardy> greyback_: I hope there is not a switch based on the CPU architecture in there...
[13:14] <greyback_> mardy: there isn't in my code anyway
[13:14] <greyback_> mardy: could you muck with /usr/lib/i386-linux-gnu/qt5/plugins/platformthemes/libappmenu-qt5.so to prevent it being loaded?
[13:16] <greyback_> tho oddly it is loaded here and unity8 comes up just fine
[13:18] <mardy> greyback_: ok, now I get the "double free or corruption"
[13:18] <mardy> greyback_: wait, let me try with qmlscene first
[13:19] <mardy> greyback_: yep, I get the memory corruption with qmlscene as well
[13:19] <greyback_> mardy: backtrace again please
[13:20] <mardy> greyback_: http://paste.ubuntu.com/10073018/
[13:20] <mardy> greyback_: as you can see I typed "catch throw", but it seems like there was no exception
[13:21] <mlankhorst> willcooke: hm it's probably necessary but not sufficient
[13:21] <mlankhorst> afaict
[13:21] <greyback_> mardy: could you add the missing symbols?
[13:22] <greyback_> that code is more mir's
[13:24] <willcooke> mlankhorst, just spoke to kgunn and greyback_, someone will get on to this asap.  greyback_ will probably work on it
[13:26] <mlankhorst> oke
[13:26] <mlankhorst> just tested and nested mir works as intended
[13:27] <mlankhorst> just unity8 is borked
[13:28] <greyback_> mlankhorst: borked how?
[13:29] <willcooke> mlankhorst, side question:  how's your xmir ppa looking atm?  Good to try on our devices here?
[13:30] <mlankhorst> ought to?
[13:30] <mlankhorst> greyback_: I don't get pointer events..
[13:30] <mlankhorst> my pointer events get converted to touch events
[13:30] <greyback_> mlankhorst: that issue, ok, yeah I'm on it
[13:32] <willcooke> thanks guys
[13:32] <mlankhorst> willcooke: ppa works fine afaik, I was working on moving to new touch events but it can wait
[13:32] <mardy> greyback_, alf_: http://paste.ubuntu.com/10073198/
[13:33] <willcooke> mlankhorst, ack
[13:34] <greyback_> mardy: frame 11 could be very useful, libmirserver28-dbgsym is missing?
[13:53] <mardy> greyback_, alf_: http://paste.ubuntu.com/10073557/
[13:54] <anpok> willcooke: input stuff in unity-system-compositor and mir
[13:55] <willcooke> anpok, no worries, I think greyback_ is looking at the issue
[14:05] <greyback_> mardy: thanks for the paste, I need alf_ to help you with that
[14:06] <alf_> greyback_: mardy: back, looking
[14:07] <alf_> mardy: could you run qmlscene with valgrind please?
[14:08] <mardy> alf_: ah! I anticipated you :-) I just did it, let me collect the logs :-)
[14:09] <mardy> alf_: http://paste.ubuntu.com/10073830/
[14:11] <mardy> alf_: see the error at the end of the logs: "std::exception::what: Failed to create shared EGL context"
[14:17] <alf_> mardy: ah, this is much more helpful, thanks!
[14:17] <alf_> mardy: could you please attach this to the bug so it doesn't get lost?
[14:17] <mardy> alf_: ok
[14:18] <kgunn> racarr: i owe you a beer....disabling n seems to be working
[14:18] <kgunn> like life chaning
[14:18] <kgunn> changing event
[14:19] <mardy> alf_: done
[14:20] <alf_> mardy: thanks
[14:22] <alf_> mardy: greyback_: So, the root cause of the bug is the exception "std::exception::what: Failed to create shared EGL context". This causes the stack to unwind and releases objects in a way that causes memory errors, but that's secondary, only a side effect. I will work on fixing the effect, probably the problem is in our Mesa code.
[14:23] <alf_> mardy: still we need to find out why the context creation fails...
[14:27] <alf_> mardy: could you run qmlscene under gdb and additional environment variables MESA_DEBUG=1 and EGL_LOG_LEVEL=debug
[14:27] <mardy> alf_: sure
[14:27] <alf_> mardy: then in gdb break on _mesa_error()
[14:27] <alf_> mardy: before running
[14:28] <racarr> alan_g: Hey...testing release and running in to some issues I think may originate with the SurfaceConfigurator changes...
[14:29] <alan_g> racarr: ok?
[14:29] <racarr> aha sorry got distracted mid sentence loud room
[14:29] <racarr> alan_g: OSK hiding got broken somewhere between
[14:29] <racarr> the OSK and the QML the minimized state isn't
[14:29] <racarr> successfully applying or being pushed through or some such
[14:30] <racarr> just wondering if you have any ideas :)
[14:32] <duflu_> alf_, mardy: Sounds like bug 1408910 :)
[14:32]  * alan_g goes to look at the Q_EMIT surfaceAttributeChanged changes...
[14:32] <racarr> alan_g: I haven't verified it entirely because Im still getting debug symbols...but we added some print in the QML side on the input method element and
[14:33] <racarr> the first time it does show that state changed to showed...and
[14:33] <racarr> set_surface_attribute continues being called but
[14:33] <racarr> state never changes again...so it may be uh
[14:33] <racarr> the value of "result" is incorrect or being mangled or some such
[14:34] <dandrader> anpok, the env var is GRID_UNIT_PX
[14:34] <alf_> duflu_: mardy: ah, indeed
[14:39] <mardy> alf_: this is what I get, the _mesa_error() was not hit: http://paste.ubuntu.com/10074123/
[14:43] <alf_> mardy: ok, please try setting the breakpoint after you have run the program once in gdb and then re-run, sometimes BPs don't work correctly if the symbols is not loaded
[14:46] <alan_g> racarr: nothing leaps out at me. Is there an image I can try?
[14:46] <alf_> duflu_: bug 1418486, I will re-add mir, because although it's strictly not code in the Mir codebase, it's still the "Mir project" and I want it to show in the bug list for Mir. I will remove it when done.
[14:47] <duflu_> alf_: Yep, OK, standard behaviour
[14:48] <alf_> duflu_: I wonder if there is a better way to express the relationship of the two projects in LP... Perhaps have a "Mir project" meta-project? Anyway...
[14:48] <racarr> alan_g: Yeah its showing up in the release PPA http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-012
[14:49] <racarr> alan_g: The whole issue I guess is...the way the osk hides is it does this animation
[14:49] <duflu_> alf_: Yeah, not without LP enhancements, which take decades :) Just using "Mir" is OK
[14:49] <racarr> and then it sets the minimize state
[14:49] <racarr> and qtmir hides it.
[14:49] <racarr> so there is an existing bug where sometimes the animation does not finish
[14:49] <racarr> (it mostly seems to show up on n7...)
[14:49] <racarr> and hten you will see
[14:49] <racarr> a little bit of the OSK left over at the bottom
[14:50] <racarr> because the
[14:50] <racarr> well, the hiding doesnt work
[14:55] <racarr> alan_g: We are seeing it may actually just be the wrong version
[14:55] <racarr> of the package in the silo....so
[14:55] <racarr> maybe don't spend any time on it now lol...sorry
[14:56] <alan_g> racarr: OK. Keep me informed.
[14:57] <racarr> alan_g: Thanks :)
[15:54] <racarr> alan_g: Ah its still broken even with the correct packages :( (featuring the metatype registration)
[15:56] <alan_g> racarr: :(
[16:40] <greyback_> mlankhorst: lp:~mir-team/qtmir/port-to-event-2.0/ should enable mouse hover - it needs mir 0.11 though
[16:53] <alan_g> racarr: I'm still not sure what your saying is going wrong. Is the server is getting the state change notification at set_surface_attribute() but not publishing the surfaceAttributeChanged event? Or is the there something not happening client side?
[17:27] <mlankhorst> greyback_: oke, last I tried it was borked, is it fixed now?
[17:29] <mlankhorst> greyback_: I was getting touch events rather than pointer events even with that branch :/


[00:18] <DarkTrick> bug@upgrade 19.10 -> 20.04 @ibus-anthy: keyboard layout of ibus-anthy changed from Japanese to "Default" (which was English). Expected: Keyboard-layout of ibus-anthy should not change.
[01:12] <DarkTrick> bug after upgrade 19.10 -> 20.04 @ application menu: (1) open menu (2) search something (eg "office") (3) press arrow-down key (4) actual: nothing happens, expected: select first entry of menu
[06:10] <DarkTrick> freecad dependencies cannot be installed on 20.04
[07:44] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: xfwm4 4.14.3 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-xfwm4-4-14-3-released-tp59323.html (by Olivier Fourdan)


[06:23] <LLStarks> did ricotz break gtk3?
[07:24] <stlsaint> is anyone having issue with sources.list duplicate entries in alpha3?
[12:17] <Q-FUNK> howdy!  has anyone ever resolved the issue of upgrading 'dbus' inside a chroot?  it tries to connect to an upstart socket that obviously doesn't exist there...
[12:23] <BluesKaj> Hey all
[12:26] <albert23> Q-FUNK: you could use a /usr/sbin/policy-rc.d to prevent starting/stopping daemons
[12:27] <Q-FUNK> albert23: would you happen to have a URL to instructions for that?
[12:28] <albert23> Q-FUNK: this is what is used in pbuilder: http://pastebin.ubuntu.com/1142904/
[12:29] <albert23> man invoke-rc.d describes it
[12:29] <Q-FUNK> ok
[12:35] <Q-FUNK> albert23: right.  it at least allows the packages to confgure succesfully. the warning about being unable to connect to dbus still appears, though, but it at least allows filing a bug.
[12:41] <Q-FUNK> albert23: thanks for this.  it at least allows the chroot to complete the installation of packages.
[15:59] <ls612> I am thinking of dual-booting W7 and Ubuntu 12.10 alpha 3, (12.04 isn't compatable with my hardware), but I would like to know if there are any known bugs with the alpha that could harm my W7 stuff.
[16:03] <wilee-nilee> ls612, what problems have you heard that a ubuntu install would have that would harm a MS set up
[16:03] <penguin42> ls612: It is an alpha, so in principal there may be bugs that do nasty things; (for example very occasionally installer bugs that break other OSs)
[16:04] <ls612> I haven't heard of any specifically, but I know that odd things can happen with alphas, and I figured it couldn't hurt to ask someone more knowledgable than myself.
[16:04] <penguin42> ls612: Of course these things happen - and you've got a backup - right?
[16:04] <ls612> Yeah.
[16:05] <penguin42> well, there you go - as long as you can recover in the unlikely event it does nuke your windows install
[16:05] <ls612> OK, thanks.
[16:05] <wilee-nilee> ls612, good job being backed up. ;)
[16:08] <wilee-nilee> penguin42, It is always good I suppose to consider all possibilities, I install manually always so I had to wonder.
[16:10] <penguin42> wilee-nilee: Never underestimate the possibility of an upset alpha release
[16:10] <wilee-nilee> hehe I suppose so I would not use it as a main setup penguin42
[16:11] <wilee-nilee> be backed up is the insurance always.
[16:16] <hd1> i just upgraded the kernel to 3.5.0-9, and it no longer finds any ethernet devices other than lo0 :(
[16:21] <penguin42> hd1: best to file a bug, I guess it works if you back the kernel off one version?
[16:21] <penguin42> hd1: It would be to capture a dmesg from the failed boot and add that to the bug report
[16:30] <hd1> penguin42: the secondary issue is that i seem to have removed the old package :p
[16:30] <penguin42> hd1: Well just download....
[16:31] <penguin42> hd1: If you download the package and copy it over using a USB stick you should be able to install it with dpkg -i
[16:31] <penguin42> you'll probably need a few
[16:43] <hd1> penguin42: trying -- where would the stick be mounted though?
[16:44] <penguin42> hd1: Well have you got the desktop up?
[16:44] <penguin42> hd1: It should land somewhere under /media
[16:48] <hd1> no
[16:48] <hd1> this is all from command line
[16:49] <penguin42> ok
[16:49] <penguin42> hd1: So put it in, it'll probably land as /dev/sdb1 - when you should plug it in you'll probably get some messages like sd 9:0:0:0: [sdd] 16328704 512-byte logical blocks: (8.36 GB/7.78 GiB)
[16:50] <penguin42> that says it's sdd1
[16:50] <penguin42> then udisks --mount /dev/sdd1  should mount it
[16:51] <ls612> Well, it seems that my hardware isn't compatible with 12.10 either. :(
[16:51] <ls612> I can't connect to the internet with that either.
[16:51] <penguin42> ls612: does it show up in network manager?
[16:52] <ls612> My Ethernet controller is an Atheros AR8161/8165
[16:52] <ls612> and No, it doesn't show up in the network manager.
[16:52] <ls612> atleast running live it doesn't
[16:52] <penguin42> hd1: Any idea what your ether chip is?
[16:55] <TJ-> ls612: this may help you http://askubuntu.com/questions/165192/how-to-install-drivers-for-the-atheros-ar8161-ethernet-controller
[16:56] <ls612> TJ-: It's kinda hard to download driver software without an internet connection. :)
[16:56] <penguin42> TJ-: Hmm bug 927782 suggests that's fixed - hmm
[16:57] <ls612> penguin42: well, I can say that it is not fixed for me.
[16:57] <TJ-> ls612: You have one now, use it... you can build the driver on a different PC as long as the arch (64 or 32 bit) is the same
[16:57] <ls612> TJ-: OK
[16:57] <TJ-> ls612: which ISO image (and date) are you using?
[16:58] <ls612> The alpha 3, 64 bit.
[17:00] <TJ-> ls612: Looks like you need to install the OS, then on your other PC download the amd64.deb and move it to the networkless PC using a USB stick ir similar, then install it using "sudo dpkg -i ..."
[17:00] <TJ-> ls612: here's the link: https://launchpad.net/ubuntu/precise/amd64/linux-backports-modules-cw-3.4-3.2.0-29-generic/3.2.0-29.14
[17:01] <ls612> TJ-: When will the driver for this get included in the kernel?
[17:03] <TJ-> ls612: The alx driver is in that backports package, that will usually remain the way of bringing newer drivers from more recent kernel versions to earlier ubuntu releases
[17:04] <TJ-> ls612: Once you have it working on the PC itself, you can enable the precise-backports repository in Software Sources
[17:05] <ls612> Hm. when will this be included with ubuntu, without backporting? I really don't want to get complicated.
[17:09] <TJ-> It's not complicated. Once the backports repo is added it stays up to date
[17:10] <ls612> Will this be included with the Quantal stable release?
[17:11] <TJ-> That's for Precise of course... anything in backports will by definition be available in the quantal kernel updates
[17:11] <TJ-> sorry - I thought I was in the -1 room :D
[17:13] <ls612> Well, it isn't in Quantal Alpha 3, so when will it be in?
[17:29] <ls612> Does anyone know when support for my ethernet adapter will be in Quantal?
[17:30] <penguin42> TJ-: It's possible that bug needs reopening - I mean I wouldn't expect it to be fix released and lost from the alpha
[17:34] <TJ-> penguin42: I'm not clear they're actually included it in the kernel images
[17:34] <penguin42> TJ-: Why wouldn't they?
[17:38] <hd1> ok... i got the bloody thing restored, thanks penguin42
[17:38] <TJ-> mainline is refusing to accept the alx driver from Qualcomm; wants them to fix the existing in-kernel drivers instead. So it isn't going to enter the mainline kernel any time soon... and QCA appear to be changing it drastically to try to meet the kernel dev demands
[17:38] <penguin42> gah, I'd hoped he would tell us which card he had
[17:38] <penguin42> TJ-: But Ubuntu tend to add some non-upstream'd drivers into the build for common stuff
[17:39] <TJ-> Indeed we do, just that if the driver is in such turmoil its not something we want to have to endless track if its a major WIP right now
[17:39] <penguin42> shrug, it would seem better to include something for a common chipset rather than leaving people dead in the water
[17:40] <TJ-> Not if it conflicts with the atl1 driver in-kernel as it currently does
[17:41] <penguin42> ah - you mean you end up with it breaking other versions of the chips - yeh that sucks
[17:41] <TJ-> The problem is, Qualcomm write alx to replace the atl1 and support new devices, instead of adding the support to the existing driver in-kernel
[17:41] <TJ-> no, even worse, alx would conflict with atl1
[17:41] <TJ-> both would claim to support the same device PCI IDs
[17:42] <penguin42> can they both build in the same tree?  It's not been too unusual to have two drivers that support the same PCI ID
[17:44] <TJ-> I don't see it in the Quantal kernel source; I've just git pulled the latest and don't see the alx driver
[17:44] <ls612> So does this mean that my hardware won't be receiving linux support? :(
[17:45] <TJ-> From what I can tell, it depends on Qualcomm behaving themselves
[17:47] <penguin42> TJ-: IMHO relying on that sounds like a bad idea, and it sounds better that someone builds a version to build both at the same time
[17:48] <TJ-> Why? It's Qualcomm's code and their responsibility. We had all this with Broadcom for 10 years and now, finally, they're working with the kernel devs since they want their hardware supported. Maybe Qualcomm have got to learn the same lesson
[17:48] <penguin42> TJ-: It doesn't help our users even if they're vendors are naff
[17:49] <TJ-> That isn't our problem though... it is the hardware vendors responsibility. They know what it takes, and its not complicated to do it the correct way
[17:50] <penguin42> TJ-: I don't disagree that they should do it, but in the end I'd say it's a distros responsibility to frig it for their users if there is a fix and the hardware vendors aren't being good
[17:50] <TJ-> Not when it comes to hardware! We don't have the documentation, no tech specs, and no resources to do that kind of work!
[17:51] <TJ-> It's not like packaging some application
[17:51] <penguin42> TJ-: But you don't need to, you just need to build their driver
[17:51] <penguin42> TJ-: If they've released a working albeit bad driver then it's not that hard to build it and only enable it for some IDs
[17:52] <TJ-> No, we have to carry patches to prevent it conflicting with other drivers in the kernel, and as it is a WIP that means constantly having to track what they're doing... once they get it in order and into staging or linux-next then we have something we can rely
[17:53] <TJ-> We are building it/shipping it - for Precise, but its not in the kernel images its outside
[17:53] <penguin42> TJ-: I'm not disagreeing that we'd have to carry patches and keep frigging it; but in terms of non-techy users being able to get their machine to work it's a necessary evil
[17:55]  * penguin42 runs a debian-installer test in a quantal kvm guest; very odd behaviour - very slow 'erasing data' on virtual disk; I'm seeing load average on the host of ~12 - very odd
[17:55] <penguin42> but mostly idle
[17:59] <TJ-> This is about the ALX:  http://askubuntu.com/questions/167621/how-do-i-deactivate-at1lc-driver-after-install-of-alx-driver-replacement
[17:59] <TJ-> penguin42: sounds like it's I/O bound ?
[18:00] <trism> seems they recently resubmitted a few days ago too, with only the new devices that aren't in al1lc in alx: https://lkml.org/lkml/2012/8/8/635
[18:00] <penguin42> TJ-: Yeh, but the KVM is on my spinny disk and the rest of the system is running off my SSD; so I could understand a load average of 1 or 2 for the KVM, but not 13
[18:00] <TJ-> trism: Yes, they've finally got the message
[18:00] <TJ-> penguin42: run iotop maybe?
[18:00] <penguin42> TJ-: Not sure, there was a very snotty message from Dave Miller on G+ saying they hadn't got it
[18:01] <TJ-> They're trying... its hard for proprietary companies to grok the kernel development style
[18:02] <penguin42> nod
[18:02] <penguin42> hmm - it looks like it's KVM threads - iotop is showing loads of kvm threads
[18:03] <penguin42> it looks like ~20 threads fighting over IO doing about 200KB/s each
[18:04] <TJ-> multi-threading gone haywire?
[18:04] <penguin42> yeh, I know a tame KVM dev to ask tomorrow
[18:31] <penguin42> right, bug 1035921 reported for that
[18:39] <penguin42> ok, that's using stupid numbers of threads - during the 'installing the base system' it's using 68
[18:43] <Daekdroom> !daily
[18:54] <ls612> penguin42: regarding my issues with Ubuntu and the internet, I found that when I installed Ubuntu on a VM that the internet worked just fine. Is that expected?
[18:55] <penguin42> ls612: If it's a problem with a driver for your hardware yes
[18:55] <penguin42> ls612: The VM doesn't see the real hardware
[18:55] <ls612> OK, that will be my short-term solution then, until the issues with the driver get figured out.
[19:40] <Walther> Does anyone else find themselves unable to use ftp on Nautilus?
[19:40] <Walther> "underlying ssh process died"
[19:40] <Walther> ...this is a *big* issue for me, as I do web design -.-'
[19:41] <Walther> the error appears only when you're trying to send / create files
[19:45] <Walther> interesting, i'm unable to transfer even using filezilla
[19:46] <Walther> it manages to *create* the file, but it remains as 0B
[19:56] <Walther> Any ideas?
[20:44] <Walther> Any ideas?
[20:44] <Walther> I need to get this problem resolved
[20:44] <Walther> Internal error: The underlying ssh process died
[20:45] <Walther> when trying to copy a file to an ftp location in Nautilus
[20:50] <Debolaz> Walther: My gut feeling based on what you've said so far is that you have a firewall issue, and that FTP isn't able to connect with its data port.
[20:50] <Debolaz> Walther: That's really just a guess though.
[20:51] <Walther> Debolaz: the funny thing is that it used to work
[20:51] <Walther> ftp/sftp, nautilus, filezilla
[20:53] <trism> Walther: I ran into bug 1034660 when testing a moment ago, but otherwise I could read and write successfully, maybe a server side issue?
[20:53] <Walther> Also, what kind of a firewall issue could I have, as I've not installed/configured any firewalls on my own
[20:54] <edgy> hi, I updated the system and rebooted and now cannot log in
[20:54] <edgy> I get the display manager, Enter user/pass, get in and quickly logged off
[20:55] <edgy> any one see this problem?
[20:55] <edgy> I tried kubuntu,ubuntu,xfce all the same issue
[20:55] <Galvatron> Then it's omething with X
[20:56] <Galvatron> What GPU?
[20:56] <trism> edgy: change to another vt (ctrl+alt+f1, f2, whatever), and paste: ls -l ~/.Xauthority;
[20:59] <edgy> Galvatron: nvidai, trism: ok just seconds
[20:59] <edgy> trism: shall I pastebin my .Xauthoriy? does it contain any sensitive data?
[21:00] <edgy> trism: my X log is at paste.ubuntu.com/1143705
[21:01] <trism> edgy: I don't want the contents, just the owner
[21:03] <trism> edgy: I've seen several times where somehow users get the file overwritten by root, and removing the file usually fixes the problem
[21:04] <edgy> trism: I removed the file now and retried to login but same problem
[21:05] <trism> edgy: can you pastebin /var/log/lightdm/lightdm.log?
[21:05] <trism> edgy: you might want to check syslog/kern.log as well to see if there is a nvidia error
[21:07] <trism> edgy: although in that case, usually lightdm won't load at all, so ~/.xsession-errors might be another useful place to look
[21:07] <edgy> trism: paste.ubuntu.com/1143721
[21:12] <trism> edgy: hmm, the plasma session there is aborting after about 40 seconds
[21:21] <edgy> less
[21:21] <edgy> trism: .xsession gives some IO errors
[21:22] <edgy> trism: let me pastebin it too
[21:25] <edgy> trism: paste.ubuntu.com/1143754
[21:25] <edgy> trism: there is a fatal IO error related to bluetooth applet
[21:27] <edgy> trism: I would remove blueman and retry
[21:29] <edgy> trism: that didn't help
[21:30] <edgy> trism: what's this fatal IO error? I am chatting from console and cannot google it
[21:34] <edgy> trism: any hint?
[21:35] <trism> edgy: it just means the xserver died, without really giving any info why
[21:35] <trism> edgy: if you create a new user, can they log in?
[21:38] <edgy> trism: let me try
[21:45] <edgy> trism: same problem with the guest account and a new account
[21:45] <edgy>  I need my system back eheheheh
[21:47] <trism> edgy: did you just do the update today?
[21:47] <trism> edgy: might be interesting to see what packages were updated at the end of /var/log/apt/history.log
[21:48] <edgy> trism: yes, it's working very well today till I rebooted, and the only thing I see is the update
[21:48] <edgy> trism: they are xserver-xorg packages mainly
[21:49] <trism> edgy: apt-cache policy xserver-xorg-core
[21:50] <trism> edgy: do you have -proposed enabled?
[21:51] <edgy> trism: paste.ubuntu.com/1143799
[21:52] <edgy> trism: seems yes I have proposed enabled
[21:52] <edgy> trism: now I feel there is some hope
[21:52] <trism> edgy: bug 1033533
[21:52] <trism> edgy: looks like the one
[21:53] <edgy> trism: I cannot read the thread now, I just commented the proposed lines in sources.lst how can i revert back?
[21:54] <edgy> trism: i know how to do it from GUI ;)
[21:56] <trism> edgy: I don't know of an automatic way to remove them all (unless ppa-purge can handle -proposed?), you could try: sudo apt-get install xserver-xorg-core=2:<IP_ADDRESS>2-1ubuntu1; but it may complain about other deps, so you may need to downgrade several packages at once
[21:58] <edgy> trism: in muon or synaptic there used to be something calle local packages where I can go and remove all of them
[21:58] <edgy> trism: do you know how can I list local packages now from console?
[22:00] <edgy> trism: I would remove xserver-xorg-core and then reinstall ubuntu-desktop
[22:00] <edgy> let us see ...
[22:01] <edgy> trism: while I do that, the errors of fonts in .xsession file, do have them?
[22:02] <trism> edgy: yes I have those too
[22:05] <edgy> trism: I really really really really appreciate your help, now every think is ok
[22:07] <trism> edgy: excellent
[22:07] <edgy> after all it's so stupid to use an alpha software and then enable an a gamma over the alpha
[23:01] <Dr_Willis> Hmm.. still cant get webapps working.. lets see...
[23:05] <Dr_Willis> plugins are enabled. in firefox and chromium.
[23:07] <Dr_Willis> Oh well.. try it agagin in a few days. :) see if any updates help.