/srv/irclogs.ubuntu.com/2013/07/26/#ubuntu-mir.txt

RAOFduflu: Oh, I've realised that one of my problems with DRI bypass is actually a generic problem with nested bypass, so I'm interested in how you've solved it03:40
RAOFThe problem is - what happens if you need to unbypass? You've only got one buffer from the server you're running against, and you've handed it out to the bypass-client. So now you need to wait for it to swap_buffers before you can unbypass, but there's no mechanism to make it swap_buffers (and can't be in general).03:42
dufluRAOF: My first prototype worked that way but then I realized the same problem. The client could hold it indefinitely.03:46
RAOFSo how did you solve that?03:47
dufluThe current approach is to make client buffers (sometimes) scanout capable and give them directly to the server as required03:47
robert_ancellRAOF, on the phone, when unity8/mir runs as the user it's logged in as - does it have enough permissions to get input directly? Or do we have to go via the system compositor?03:47
RAOFrobert_ancell: If we want to have any form of user-switching then input needs to go via the system-compositor.03:48
robert_ancellRAOF, but we're not doing that for XMir right?03:48
dufluRAOF: There will be some smarts required to limit which clients get scanout capable buffers, and maybe event change it at runtime. But right now I just have all clients given scanout capable buffers. And sometimes they will be scanned out (bypass), sometimes not (composited)03:48
RAOFRight. Which is why user switching under XMir is currently a terribly bad idea.03:48
RAOFAlso, we run XMir as root.03:49
robert_ancellyes03:49
robert_ancellI just got support to run Mir sessions and VT switch between them, but that's probably a no-go03:49
RAOFAnd the design for 13.10 is that we trust XMir to acquire/release input when its session gets switched to/from.03:49
RAOFAs long as the Mir sessions can acquire/release input on VT switch, and unity-system-compositor can acquire/release input on VT switch that should work.03:50
robert_ancellI think you need to be root to watch for VT switches03:51
RAOFIndeed you do.03:51
RAOFAnything we run on a VT needs to do so as root.03:51
robert_ancellIs there any way to authorize certain processes to run on a VT?03:52
RAOFAnything we run under unity-system-compositor *can* run unprivileged, as long as it gets input through u-s-c.03:52
robert_ancellyeah03:52
RAOFI'm not sure that's enough.03:52
RAOFBecause (if you're running on a VT) you need to be able to access /dev/input/* to get input.03:53
robert_ancellyeah, and that's root right?03:53
RAOFIndeed03:53
RAOFAnd if your *user* can access /dev/input/*, then they can just open it, switch away, and they snoop all input.03:53
* RAOF notices it's 2pm and goes for lunch.03:53
robert_ancellyes, you would have to limit it to just the shell to be useful03:54
RAOFWhich is pretty similar to "just run the shell as root"04:18
RAOFduflu: Ah. That doesn't help me, then (and won't work for the nested-compositor case)04:37
RAOFduflu: We should probably work out how to do it properly :)04:37
* duflu does lunch too04:42
tvossgood morning :)05:02
RAOFAloha05:05
tvossrobert_ancell, RAOF did we have any luck with the ati machine?05:06
RAOFtvoss: I thought that got all resolved?05:08
tvossRAOF, not sure :) I hope it it is05:09
robert_ancelltvoss, RAOF that's bug 1204939 and we don't have a solution05:13
ubot5bug 1204939 in Mir "Mir doesn't start on ATI test machine" [Undecided,New] https://launchpad.net/bugs/120493905:13
robert_ancellRAOF, duflu can you have a look at that one and triage it please?05:13
tvossRAOF, we saw  [  2417.963] (II) UnloadModule: "radeon"05:14
tvoss<didrocks> [  2417.963] (EE) Screen(s) found, but none have a usable configuration.05:14
tvossRAOF, from the next ppa that didrocks wanted to test05:14
RAOFSo the problem is that XMir hasn't been loaded at all.05:16
robert_ancellRAOF, did the packaging changes mess things up?05:16
dufluOK, title improved but needs much more attention to be "triaged"05:16
RAOFrobert_ancell: Possibly? I would have thought the server would die if it couldn't load xmir.so05:17
tvossdidrocks, good morning05:25
didrockshey tvoss05:25
tvossRAOF, any ideas why the new packaging might fail?05:26
RAOFtvoss: Not off the top of my head.05:27
tvossdidrocks, do we have access to the machine? would like to track this issue down05:28
didrockstvoss: the machines are currently running the tests for daily release05:29
didrocksas having those in the image is the priority, no access to the machine now05:30
RAOFdidrocks: Do we have a dump of /var/log anywhere?05:30
didrocksRAOF: you can have that if you uncompress the archive from yesterday05:30
didrocksI'll give you a pointer in 505:30
RAOFTa05:30
robert_ancelldidrocks, you'll be in IOM right?05:33
didrocksrobert_ancell: right05:33
didrocksRAOF: http://10.97.4.138/otto/saucy-i386-20130725-1116/archive/ubuntu_13.10_saucy_salamander_alpha_i386_20130725.1374764535.otto05:33
didrocksRAOF: this is a tar file05:33
robert_ancelldidrocks, tvoss, see you guys there05:33
didrocksyou have a delta/ directory05:33
didrocksrobert_ancell: see you there as well dude! :)05:33
didrocksin the delta, it's a bump of all what was modified05:34
didrocksso you should have var/log and so old05:34
RAOFWell, that is of moderate size!05:34
didrocksso on*05:34
didrocksRAOF: don't install that many packages :p05:34
didrocks(it's really just a delta, with mir installed on top of it)05:35
RAOFdidrocks: It looks to me like xmir worked as expected on that test run - it's the failsafe session that failed to start.06:02
didrocksRAOF: why failsafe was executed?06:03
didrocksshouldn't we have u-s-c running?06:04
RAOFlightdm.log shows that u-s-c started up fine, XMir started up fine, then upstart asked lightdm to terminate, which it did, cleanly.06:04
RAOF(upstart sent SIGTERM ~20s after lightdm came up)06:05
didrocksRAOF: the session even didn't start06:05
didrocks(user session)06:05
RAOF[+1.88s] DEBUG: Session 1085 running command /usr/sbin/lightdm-session gnome-session --session=ubuntu06:06
RAOFThen: [+22.80s] DEBUG: Got signal 15 from process 106:06
didrocksRAOF: right, the question is why the session was killed?06:06
didrocksas nothing changed and the same package versions are working reliably on intel06:06
didrockswith session starting06:06
didrocksunity spawn06:07
didrocksRAOF: it seems that the acceleration test maybe doesn't work (what is tested before starting unity)06:07
didrocksso can't start unity -> required component06:07
didrocks-> exit06:07
RAOFPlausibly - ~/.cache/upstart/unity7.log contains a lot of ‘unity7 stop/pre-start, process 1216’06:09
didrocksRAOF: my guess is that acceleration doesn't work06:09
RAOFThere's no evidence of that in the Xorg.0.log, but it's possible.06:11
RAOFBut in gnome-session.log - compiz (core) - Info: Unity is not supported by your hardware. Enabling software rendering instead (slow).06:14
didrocksyeah, seems like a good hint06:21
dufluHey that's what I was getting after updating last night :/06:21
tvossargh, gdb in an armhf chroot is pure pain06:22
tvossdidrocks, what does the unity test script check?06:28
didrockstvoss: if hardware acceleration is available and multiple other things06:30
didrockstvoss: it's in nux sources, tools/06:30
didrocksbut maybe duflu debugged it as he saw it06:30
tvossdidrocks, is there a log of it? I think I saw something in /tmp06:30
didrockstvoss: just returning 0 or 1 if supported/unsupported06:31
dufludidrocks: No, I ignored the bug because it was on raring (which I assume we don't care about)06:31
tvossdidrocks, hmmm, not what I would call overly chatty :)06:31
dufluThough interestingly, the fix was to downgrade the latest lightdm update06:31
didrocksyou can launch it with -p to have more logs, but you need access for that on the machine06:31
didrocksbut as duflu gets it06:31
didrocksmaybe he can run it to get more infos?06:32
didrocksduflu: interesting, that is a potential issue, right, latest lightdm06:32
dufludidrocks: Also, on this raring machine I am not using USC. It's plain old X. Just that the staging PPA gave me a dud update06:33
dholbachgood morning06:45
tvossdidrocks, can we downgrade lightdm on the machine for testing purposes?06:48
didrockstvoss: it's possible, will take time… time I don't have today TBH06:49
didrockstvoss: i'm already on pressure to deliver something I didn't know that was planned for IoM as top priority06:49
didrockstvoss: I pushed it back for the last 2 week mainly because of Mir already…06:49
tvossdidrocks, ack06:49
didrockssil2100/jibel should be able to help though to do that06:50
tvossdidrocks, ack06:50
* RAOF is sad that you can't build X with clang ☹07:02
dufluThat's odd. I'm getting small amounts of graphics corruption since getting a new intel driver from staging07:04
tvossduflu, likewise07:04
tvossRAOF, duflu is there any way that I can try the staging ppa xserver and intel driver?07:14
duflutvoss: Is that a trick question? You mean with the other PPA? Maybe just download the deb(s)07:15
tvossduflu, nope, not a trick question07:15
tvossdidrocks, or can I try to switch to next for intel?07:15
didrockstvoss: daily-build-next -> intel07:16
didrocksit's working from what the tests says07:16
tvossdidrocks, okay, will give it a spin now07:17
didrockstvoss: keep me posted ;)07:17
tvosssil2100, hey there07:17
sil2100Morning!07:17
didrockshey sil2100!07:26
tvossdidrocks, apt-get dist-upgrade removes unity-common? is that okay?07:32
didrocksyep ;)07:32
tvossdidrocks, in progress07:34
tvossalf__, ping07:35
tvossokay07:50
tvossno hw accel on unity07:50
tvossdidrocks, tried daily-build-next with intel, comes up but no hw-accel, flickering screen07:58
didrockstvoss: interesting that times out on tests are so big that they pass then…07:58
didrockstvoss: ok, so clearly either an issue with latest Xorg or lightdm07:59
tvossdidrocks, you sure?07:59
tvossI will reenable the system-compositor-testing ppa now07:59
tvossand compile usc and mir from current trunk07:59
tvossthat's what you essentially do, correct?07:59
didrockstvoss: duflu mention that revering lightdm helped07:59
didrockstvoss: yeah, you have latest usc and mir normally07:59
tvossdidrocks, ack, I will stick with the older xorg and intel driver in the testing ppa then08:00
=== didrocks is now known as didrocks_reallyb
=== didrocks_reallyb is now known as didrocks_busy
tvossduflu, which version of lightdm did you downgrade to?08:04
duflutvoss: 1.7.5bzr1634raring008:04
dufluThe broken one was 163608:04
tvossduflu, ack and thx08:05
tvossduflu, did you experience flickering, too?08:05
duflutvoss: No... But then this raring machine is using plain X, not Mir08:05
tvossduflu, ack08:05
duflu... so that I can start new Mir servers concurrently08:05
tvosshmmm, compiling mir trunk fails with unit-tests requiring eglCreateImageKHR08:07
tvossI thought we had fixed that08:07
dufluback in 3008:25
tvossduflu, ack08:27
tvosssil2100, any luck with the unity-test script?08:49
tvoss_sil2100, ping08:52
tvoss_RAOF, ping08:52
sil2100tvoss_: still waiting for the machine to be free ;/ We might consider killing some jobs if this is urgent08:52
tvoss_sil2100, nope, no worries08:52
tvoss_any eta?08:52
sil2100Let me see how far the stupid unity testing is08:53
tvoss_sil2100, ack08:53
sil2100tvoss_: I would say around 30 minutes, since unity testing is finishing and then just some smaller jobs are queued up08:54
tvoss_sil2100, ack and thx08:54
sil2100jibel: can we somehow block the autopilot-saucy-daily_release job not to accept any new requests for a moment?08:55
jibelsil2100, stop the slave on the machine08:56
jibelsil2100, sudo stop jenkins-slave on ait08:57
jibelati08:57
jibelsil2100, but wait until the current runs are  finished08:58
jibelas it will interrupt them08:58
RAOFtvoss_: Pong08:59
tvoss_RAOF, hey there :) I'm trying to bisect and track down why daily-build-next gives me a fucked up xmir stack09:00
tvoss_RAOF, starting with system-compositor-testing ppa, what would be next? installing mir and usc from staging?09:00
RAOFHm. Wouldn't you install from daily-build-next?09:01
RAOFYou're trying to work out the component that's broken in daily-build-next, right?09:01
sil2100jibel: thanks!09:03
tvoss_RAOF, yeah, the problem is: daily build next is completely unusable for me on intel09:03
RAOFtvoss_: And you want to find which component of daily-build-next is broken for you, so you'd install components one-by-one from there, right?09:04
tvoss_RAOF, ack09:04
tvoss_RAOF, I was wondering whether I could update X and xorg-video-intel before getting the new mir from daily-next09:06
RAOFYou could, yes.09:07
tvoss_RAOF, okay09:08
tvoss_RAOF, that would work although the packaging added the xorg-xmir package?09:09
RAOFYou'd need to ensure that xserver-xorg-xmir is installed, but apart from that, yes.09:09
tvoss_okay09:09
RAOFHurray! Pixman is less annoying that I thought!09:15
RAOFAlthough ‘the docs are the source’ remains a less than optimal state.09:15
tvoss_RAOF, ?09:22
RAOFOh, RegionUnion and RegionSubtract don't mind if the destination Region is the same as one of the arguments.09:25
RAOFAlthough it's not obvious that this is the case.09:25
tvoss_RAOF, ah09:26
WaltherAny news on when mir will be enabled by default to alpha/beta?11:54
tvossWalther, on it :)11:58
tvoss_alf__, ping12:01
Walthertvoss_: Huh? Last I checked it required adding a ppa, required open drivers instead of binary blobs for gpu, etc12:02
WaltherI mean, I'm running saucy already12:02
Waltherand tried manually installin mir once with catastrophic results, went back to "regular plain saucy"12:03
tvoss_Walther, yup, we are working on getting Mir and XMir into the archive right now. For binary driver support: That's not something we are targetting for 13.10, so it will be Mir/XMir on open source drivers, falling back to vanilla X on closed-source drivers12:03
Waltherhm, ok12:03
Walther(I just happen to have a too new GPU that doesn't really have passable support in open drivers :/ )12:04
Waltheron work computer, not an issue though12:04
tvoss_Walther, that's unfortunate12:04
Walther7970, last time i tried, just doesn't want to cooperate on anything else than bin12:05
tvoss_didrocks_busy, I was able to come up with a somewhat usable solution from staging ppa12:05
WaltherBut yeah, thanks to all for doing your job, will join testing when I can12:05
tvoss_Walther, thanks :) looking forward to finally being able to support you12:06
Waltherhehe12:07
WaltherAlso, how's the status of native apps other than demos going?12:07
Waltheras in, the fallbacking to X when needed, and actual mir-supporting apps12:07
tvoss_didrocks_busy, okay, taking the intel driver from the system compositor testing ppa gets rid of the weird glitches12:24
didrocks_busytvoss_: so, there are more fixes that were in the pipes?12:25
tvoss_didrocks_busy, I have got lightdm from system-comp testing, intel driver from system-comp testing, everything else from staging, with usc build manually12:25
didrocks_busytvoss_: do you know the diff between u-s-c in daily-build-next and in the staging ppa,12:26
didrocks_busy?12:26
didrocks_busydid you try to revert lightdm as well to distro? maybe it's lightdm from staging "fixing" it12:26
=== 20WACTA0R is now known as tvoss
hikikohi, question: what exactly is the crtc? I got an exception on trunk: "Output has no associated crtc13:35
hikikoand I was getting another flipping related one before13:35
ogra_a CRT is a tube monitor ... i would guess the last C means connector13:36
hikikooh. it13:37
hikikothanks ogra_ :) I didn't realize it :)13:37
tvossmlankhorst, ping13:38
mlankhorstpong, but not a work day for me13:40
tvoss_mlankhorst, okay: I'm seeing a driver needs flags 0, nested not support in Xorg.0.log13:50
tvoss_that's for kms with the latest intel from daily-build-next13:50
mlankhorstit's not mir enabled, then..13:51
mlankhorstand if it is it'll have to wait till monday, gone13:52
tvoss_mlankhorst, thx13:58
mterryWhat's the state-of-art for flashing a device with a unity-mir image?  Still to flash a special saucy-preinstalled-phablet-armhf.zip ?15:12
kgunnbregma: is brandon around today?15:15
bregmahe should be, but he's on left coast time so he will probably start his day within an hour or so15:16
kgunnbregma: duh! he just told me seattle yesterday...(gray hair moment)15:21
bregmakgunn, it looks like the all-important https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1203207 may also be blocked on some issues, I'm going to file bugs for those and tag them entering-saucy15:23
ubot5Launchpad bug 1203207 in mir (Ubuntu) "[MIR] mir" [Undecided,New]15:23
bregmakgunn, if you could get that intel bug tagged, that would be great15:23
kgunnbregma: on it...yeah...sorry15:28
kgunnbregma: there now https://bugs.launchpad.net/mir/+bug/120538315:37
ubot5Launchpad bug 1205383 in Mir "Xmir intel vladmir head broken" [Critical,Triaged]15:37
bregmakgunn, thanks15:37
bschaeferkgunn, hey, i've a couple things to finish then I can help look into which rev has causing the ati issue16:07
kgunnbschaefer: thank you16:07
kgunnsince you had a local card...you might be able to use that....i think you might have been on -testing ppa16:08
bschaeferkgunn, np! I've a desktop with an ATI card, in the evergreen family but I should get the info for didrocks ati machine16:08
kgunnexcellent!16:08
bschaeferkgunn, yeah, also would you happen to know how to point a local built mir to get lightdm load it?16:09
bschaeferso I can start reverting trunk mir to figure out what rev caused the problems :)16:09
xjuniortvoss_: hey dude, good morning/afternoon/whatever-is-there :)16:11
tvoss_xjunior, otp, with you in a few16:12
kgunnbschaefer: honestly...i think if you build is....it tries to use your usr bins first16:19
kgunnat least i'm pretty sure...cause i fell victim one time, it wouldn't work from ppa16:20
bschaeferkgunn, alright, Ill have to dig around to how to make lightdm point to my buiild ;)16:20
kgunnbut only i was broken...and yeah..oops16:20
kgunnold binary in my usr dir16:20
bschaeferright, hmm well I ll need staging, worst case I can  move it into /bin but that is reall the worst case16:21
kgunnbschaefer: might ask tvoss when he's off the phone16:22
bschaeferkgunn, sounds good, thanks!16:22
=== didrocks_busy is now known as didrocks
smintheuhi everybody19:27
smintheutrying to get mir to work on saucy19:27
smintheuran into a problem that has been reported before, but i haven't found a solution yet19:27
smintheuhere is my /var/log/lightdm/unity-system-compositor.log19:28
smintheuERROR: /build/buildd/mir-0.0.6bzr848saucy0/src/server/graphics/gbm/gbm_cursor.cpp(46): Throw in function mir::graphics::gbm::GBMCursor::GBMBOWrapper::GBMBOWrapper(mir::graphics::gbm::GBMPlatform&)19:28
smintheuDynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >19:28
smintheustd::exception::what: failed to create gbm buffer19:28
smintheuany ideas?19:28
tvoss_smintheu, are you running on ati?19:29
smintheunvidia if i'm not mistaken19:29
smintheulspci -v | grep "VGA compatible"19:29
smintheu01:00.0 VGA compatible controller: NVIDIA Corporation G84GLM [Quadro FX 570M] (rev a1) (prog-if 00 [VGA controller])19:29
tvoss_smintheu, how did you install? from the testing ppa?19:30
smintheuyes19:30
smintheuI saw on launchpad that other people encountered this, and that it was supposedly fixed as of yesterday19:32
smintheuhttps://bugs.launchpad.net/mir/+bug/120307019:32
ubot5Launchpad bug 1203070 in Unity System Compositor "unity-system-compositor doesn't start on some ati card (with opensource driver)" [Critical,Fix released]19:32
smintheuif I understood correctly, it's supposed to be fixed19:32
smintheubut I still have the same problem19:32
tvoss_smintheu, the testing ppa is behind as we are busy landing in distro19:33
tvoss_smintheu, can you wait until next week?19:33
smintheutvoss, sure, just playing around a bit19:33
smintheutvoss, I'll give it another try next week19:33
smintheutvoss, by landing in distro you mean that mir/xmir is going to become default in the daily builds?19:34
kgunnsmintheu: that's the idea19:34
smintheukgunn: cool. I'll give it a try again next week19:35
smintheutvoss, kgunn: thanks for your help19:35
tvoss_smintheu, yw :)19:35
bschaefertvoss_, sweet, confirmed it fixes the cursor issue :)19:35
bschaefereven though I assume it was already :)19:36
tvoss_bschaefer, yup19:36
tvoss_bschaefer, what are you running now?19:36
tvoss_which version exactly, which ppa?19:36
bschaefertvoss_, I running testing, but compiled u-s-c my self19:37
bschaeferim*19:37
bschaeferthough I had to remove the *.sleep  part19:38
tvoss_bschaefer, fair19:41
tvoss_bschaefer, interesting bit is actually daily-build-next19:41
bschaefertvoss_, o the sleep binary is in that ppa?19:41
tvoss_bschaefer, it's a wrapper script19:42
bschaeferor rather what so interesting part of that ppa?19:42
bschaefertvoss_, o well that makes more sense19:42
bschaefero that should have the the cursor fix...hmm I wonder if I should be testing this ati card with that19:43
tvoss_bschaefer, if you can it to work, you are my hero19:44
bschaefertvoss_, well I think thats what Im looking at today :)19:44
* bschaefer installs ppa19:44
tvoss_bschaefer, first purge the testing ppa19:44
bschaefertvoss_, thanks, almost didn't do that...19:45
kgunnbschaefer: wanna stay in here ?19:48
bschaeferkgunn, sounds good19:48
kgunncool19:48
kgunnrobotfuel: we moved :)19:48
bschaeferso i just realized chris == robotfuel...19:49
kgunnha19:50
bschaeferhaha19:50
tvoss_bschaefer, did you install the next ppa?19:50
bschaefertvoss_, doing that right now! just got down purging and updating19:50
tvoss_bschaefer, ah :)19:51
bschaefernow upgrade with the new ppa...hopefully things don't go tooo bad19:51
bschaefertvoss_, but looking at the ppa, theres no mir there?19:53
bschaeferand after purging the testing ppa, should I be compiling mir my self?19:53
bschaeferopps, I guess theres more then 1 page!19:53
* bschaefer is not use to that many packages in a ppa19:54
bschaefertvoss_, hmm working here19:54
tvoss_wtf? no flickering?19:55
tvoss_bschaefer, did you remove the pinning file for the testing ppa?19:55
bschaefertvoss_, shoot19:55
bschaefertvoss_, sorry! got your hopes up...19:56
* bschaefer upgrades again19:56
kgunnhow many times has each of us done that19:56
bschaefer:), now I don't feel as bad haha19:57
bschaeferkgunn, so am i expecting a crash or flickering?19:57
tvoss_bschaefer, unity not coming up19:58
bschaefertvoss_, alright, that doesn't sound good :(, is mir still running in the background with the xserver?19:58
bschaeferor is it the server as well?19:58
tvoss_?19:58
tvoss_usc will be running, but xmir won't start19:58
bschaefererr, so do you mean unity it self just crashes19:59
bschaeferoo alright, when I hear unity doesn't run im thinking only compiz/unity19:59
tvoss_ack19:59
bschaeferhmm i just get a "no signal" from my monitor now ... thats somewhat strange20:03
tvoss_can you ssh to the machine?20:04
bschaefertvoss_, well I should have gotten the ip first, but yeah i can guess a few20:05
bschaefershould be 1-6...20:05
bschaeferdang, forgot to install openssh...hmm thats going to be fun20:05
bschaeferopenssh-server20:05
tvoss_bschaefer failsafe mode is yourr friend20:05
bschaeferthanks, installing now, but the error I got was strange20:07
* bschaefer looks at the longs20:07
bschaeferlogs*20:07
bschaefer(EE) no screen founds20:08
bschaeferbut that could be attempting failsafeX20:09
tvoss_bschaefer, please get the xserver-xmir deb from the mir staging ppa manually and install it manually20:09
kgunnThis is a very general message telling you that something went wrong and there is no screen left which the server can successfully drive. Usually you'll see another error message describing what went wrong in more detail:20:10
kgunnEE no screen found ^ from xorg20:10
bschaeferkgunn, right, thats correct20:10
bschaefertvoss_, hmm getting the deb manually from the staging ppa?20:10
bschaeferyou mean add the ppa, and only install that package?20:11
tvoss_bschaefer, cancel that20:11
bschaeferalright, well the screen part is still true, but I can ssh into it now20:11
tvoss_bschaefer, can you check if xserver-xorg-xmir is installed?20:11
bschaeferdm_connection_start20:11
bschaeferFailed to read header20:11
bschaeferfrom lightdm log20:11
bschaefertvoss_, yeah let me check20:11
bschaefertvoss_,   Installed: 2:1.14.2-0ubuntu2+xmir1.120:12
tvoss_ack20:12
tvoss_bschaefer, can you pastebin Xorg.0.log?20:12
bschaefertvoss_, yup!20:13
bschaefertvoss_,   Installed: 2:1.14.2-0ubuntu2+xmir1.120:14
bschaeferopps20:14
bschaeferhttp://paste.ubuntu.com/5916056/20:14
bschaefertvoss_, ^20:16
kgunnit wants exa ?20:17
kgunnthot that was an intel thing20:17
bschaeferon my Xorg failsafe attempt it has: [    33.829] (WW) Warning, couldn't open module vbe20:17
bschaeferinstead of exa...20:17
bschaeferkgunn, it looks like it sees it doesn't exist20:18
bschaeferkgunn, err, actually ati has XAA/EXA20:19
bschaeferhttp://dri.freedesktop.org/wiki/ATIRadeon/20:19
* bschaefer wonders if XAA would workd20:20
bschaeferwork*20:20
tvoss_bschaefer, try xaa please20:21
bschaeferwas just trying20:21
tvoss_bschaefer, kgunn the interesting line is https://www.google.de/search?client=ubuntu&channel=fs&q=Driver+needs+flags+0,+incompatible+with+nested,+deleting.&ie=utf-8&oe=utf-8&gws_rd=cr&ei=adryUZCXL8SBtAa9v4CQDQ#safe=off&client=ubuntu&hs=i1p&channel=fs&sclient=psy-ab&q=%22Driver+needs+flags+0%2C+incompatible+with+nested%2C+deleting.%22&oq=%22Driver+needs+flags+0%2C+incompatible+with+nested%2C+deleting.%22&gs_l=serp.3...7152.7609.0.7820:22
tvoss_45.2.2.0.0.0.0.78.147.2.2.0....0...1c.1.22.psy-ab..2.0.0.Umv3IgNixhE&pbx=1&bav=on.2,or.r_cp.r_qf.&bvm=bv.49784469,d.Yms&fp=2582c0630cd1accc&biw=1316&bih=68020:22
tvoss_bschaefer, kgunn even Driver needs flags 0, incompatible with nested, deleting.20:22
bschaeferhmm it didn't seem to like my xconf file...20:23
* bschaefer tries again20:23
bschaefertvoss_, hmm but my xmir isn't even crashing, I don't think it gets that far20:26
bschaeferit does...20:26
bschaefertvoss_, nevermind I see what you were looking at now :)20:26
bschaefertvoss_, hmm its loading my xorg.conf but its still looking for exa and not xaa20:30
tvoss_bschaefer, kgunn hold on, looking at the source package from the next ppa, there is a conditional for xmir, translating into an XMIR preprocess define20:38
tvoss_bschaefer, kgunn looking at the ati and intel source package, there is nowhere a define of the preprocessor macro20:38
kgunnhmm20:39
tvoss_bschaefer, kgunn xorg-xserver has an xserver-xorg.h.in that will get configured and finally (hopefully) contains the define20:39
bschaeferwait so theres a define in the ppa thats replacing what?20:39
tvoss_however, the header is nowhere included in the drivers20:39
tvoss_bschaefer, kgunn so in total: I think we don't compile the x drivers for XMIR with nested support20:40
* bschaefer re calls RAOF mentioning to always include a header similar to that20:40
kgunnlittle confused....who added the define ? is that upstream ?20:40
* bschaefer greps 20:40
bschaefertvoss_, well that would cause some problems...20:40
kgunnbschaefer: yep....recal that too20:40
kgunnheader hell20:41
bschaeferpreprocessor hell :)20:41
tvoss_okay guys, I'm eoding now20:42
tvoss_please keep me posted here on irc, will pick up tomorrow morning20:43
bschaefertvoss_, alrright, have a good night sleep!20:43
bschaeferyup!20:43
kgunngood night tvoss_ see you on sunday!20:43
kgunnthanks for the prodding :)20:43
bschaeferkgunn, tvoss_ #include <xorg-config.h>20:44
* bschaefer doesn't know if this is whats missing though20:45
kgunnbschaefer: hmm, digging..but it'd be in xorg patches from RAOF in his git branch i think20:47
kgunnand as tvoss indicated it should be some sort of xmir macro20:48
bschaeferso we are missing thi preprocessor define in the ati/intel source packages20:48
bschaeferthat should fix everything haha...20:48
kgunnso it seems...so would need a recompile of those20:49
bschaeferyeeah, but first dig through RAOFs git branches for some defines20:50
bschaeferkgunn, do you have a link?20:50
kgunnbschaefer: i would think in here....https://github.com/RAOF/xserver20:51
bschaeferkgunn, cool, I just wasn't sure of what RAOF git account was, but I guess its RAOF :)20:51
bschaeferthanks!20:52
kgunnhmmm...don't see a mir ref in that header tho...(am i looking in the right one)20:52
bschaeferkgunn, does that xserver encompass all of intel/ati? or are those in a separate branch?20:53
kgunnbschaefer: seperate branches...same convention i think20:54
bschaeferkgunn, hmm alright, cause tvoss_ mentioned it was in the ati/intel source packages20:54
kgunn...oop, no...they're in bzr20:54
kgunnhttp://unity.ubuntu.com/mir/building_source_for_pc.html20:54
bschaeferwell thats also a good place to check :)20:55
chjuniorkgunn, are you guys talking about https://bugs.launchpad.net/xmir/+bug/1203776 ?20:59
ubot5Launchpad bug 1203776 in XMir "X crashes w/ latest xserver intel driver from System Compositor Testing PPA" [Critical,Triaged]20:59
kgunnchjunior: yes...basically21:00
kgunnsuffering too many damn channels21:00
chjuniorkgunn, cool :) is there a work around?21:00
kgunnbut i think there's some current thinking the sna not ready for prime time21:01
bschaeferchjunior, ChrisTownsend mentions you can downgrade your intel driver21:01
chjuniorbschaefer, how can I do that exactly?21:01
kgunnso in xorg.conf set  "AccelMethod"  "uxa"21:02
bschaeferchjunior, you can do what kgunn is mentioning  (which was just tested)21:02
bschaeferor reading this comment: https://bugs.launchpad.net/xmir/+bug/1203776/comments/3621:02
ubot5Launchpad bug 1203776 in XMir "X crashes w/ latest xserver intel driver from System Compositor Testing PPA" [Critical,Triaged]21:02
chjuniorbschaefer, does that prevent future updates?21:03
bschaeferchjunior, i would think the next time you upgrade it would upgrade it, but im not sure :(21:04
chjuniorE: Version '2.21.9+xmir5870-0~saucy1' for 'xserver-xorg-video-intel' was not found21:04
bschaeferchjunior, :(, hmm it might have been bumped hmm, you could try what kgunn was mentioning :)21:05
bschaeferchjunior, in /etc/X11/xorg.conf21:05
chjunioryeah, I hate messing up with xorg.conf21:05
bschaeferyeeaah21:05
chjuniorI'm a happier person since the last time I did it21:06
bschaefer:)21:06
bschaeferchjunior, you tried? sudo apt-get install xserver-xorg-video-intel=2:2.21.6-0ubuntu421:07
bschaeferyou'll lose mir though :(21:07
chjunioryeah21:07
chjuniorthat's why I did the other one21:08
chjuniorIf you want to keep mir: "=2.21.9+xmir5870-0~saucy1"21:08
bschaefer:(, that was the last version, as currently we are on: 2:2.21.9+xmir5870-1~saucy121:11
chjunioryeah, and seem like there's no older version in there21:13
xjuniorkgunn, bschaefer: switching to uxa worked21:16
kgunnxjunior: thanks data point 2 of success :)21:17
bschaeferxjunior, awesome :), we'll have to figure out what sna doesn't work21:17
xjuniorbschaefer, kgunn: thank you guys. I have the bug here, I can help you out with anything21:18
xjuniorjust let me know which logs/procedures you need21:18
bschaeferxjunior, thanks :)21:19
bschaeferkgunn, so looking at this ati branch21:21
bschaeferif XMIR is not defined, we don't include a lot of things21:22
bschaeferbut i don't see it defined here though21:22
bschaefersooo something else must be defining it...21:22
mlankhorstbschaefer: xorg-server ought to define it21:22
bschaefermlankhorst, well that make sense...21:22
* bschaefer looks through there21:22
bschaeferconfigure.ac:1146:PKG_CHECK_MODULES([XMIR], [mirclient], [XMIR=yes], [XMIR=no]), soo possibly we aren't enabling XMIR in daily next?21:26
bschaeferkgunn, ^21:27
bschaeferin RAOF xserver git branch21:27
bschaefermalthanks for the info :)21:27
bschaeferthanks*21:28
bschaeferhttp://paste.ubuntu.com/5916291/21:28
bschaeferso something is failing in here, thats setting it to false...21:28
bschaeferopps copied a bit to much...21:29
kgunnbschaefer: so its just a build/packaging bug ?21:36
bschaeferkgunn, im not sure, as I want to confirm they are missing from main possibly...21:36
bschaeferkgunn, but possibly!21:36
xjuniorbschaefer, kgunn: from the package diff, in the ppa, yes21:37
xjuniorthe change was to default to sna instead of uxa21:37
bschaeferxjunior, we are talking about this problem with a different ppa :), sna was just enabled ( IIRC)21:38
xjuniorsorry21:39
bschaeferxjunior, no worries :)21:39
kgunnxjunior: we've got a couple of moving pieces we're chasing...1 bug w/ sna....and another bug with what seems to be xmir preproc missing somehow (that bschaefer is talking about)21:39
xjuniorkgunn, gotcha ;)21:40
bschaeferkgunn, should we push something to change things back to uxa, until we figure out what sna is not working atm?21:40
bschaeferkgunn, not a signal mention of mir in xserver-xorg-video-ati-7.1.021:41
kgunnbschaefer: yeah...we probably should...21:41
bschaeferfrom the daily-next ppa21:41
bschaeferkgunn, so now why does xserver not think we should inculde xmir... hmm21:41
mlankhorstto the build logs..21:42
bschaeferyup, was about to try to just build xserver on my machine, but i suppose logs that exist already would be helpful :)21:42
* bschaefer gets an XMIR = YES here21:43
kgunnbschaefer: ok....not sure what the hell...i swear i didn't see this earlier....21:45
kgunnhttps://github.com/RAOF/xserver/blob/04b01054c2f0eb020b588c976cb4c6a3fb8d867e/include/xorg-server.h.in21:45
kgunnXMIR undef in this one ^21:45
kgunnfor nested21:45
bschaeferhmm strange: https://github.com/RAOF/xserver/blob/04b01054c2f0eb020b588c976cb4c6a3fb8d867e/include/xorg-server.h.in21:45
bschaeferopps21:45
bschaeferhaha just copied that sorry!21:45
bschaeferkgunn, yeah I saw that...21:45
bschaeferbut hmm21:45
Sarvattits a .in, changes based on build options21:46
bschaeferkgunn, cause xorg-server read as: checking for XMIR... yes21:46
bschaefersoo XMIR is getting undefed somewhere else...21:46
bschaeferunless the ati/intel bits aren't using the right xorg from the ppa?21:46
mlankhorstor they were built before xorg-server was built in the ppa.21:47
Sarvatttry no change rebuilding the drivers that probably built before xserver with xmir did?21:48
bschaeferpossibly, how could we test this? Rebuild those packages?21:48
bschaeferand it looks like xorg-server was built on 25th, and ati was on the 18th21:49
bschaeferbut intel was on the 25th as well21:49
bschaeferhttps://launchpad.net/~ubuntu-unity/+archive/daily-build-next/+packages?batch=75&direction=backwards&start=30021:49
kgunnbschaefer: yeah...just pull from bzr build local should work right ?21:51
kgunnto prove it21:51
bschaeferkgunn, hmm well im just wondering why the apt-get source on the ati/intel doesn't give use anything mentioning xmir... i mean the source should21:53
bschaefermention the xmir stuff either way right? (Even before its built?)21:53
* kgunn wants to say true...but digging first21:54
Sarvattforgot the deb-src line?21:54
bschaeferpossibly, its almost like we aren't using RAOFs version...21:55
kgunnbschaefer: that's what i was going to dig on....21:58
kgunni wonder...21:58
bschaeferkgunn, hmm let me double check the intel version...22:00
bschaeferkgunn, cause I just realized I might have pull the wrong source...22:01
kgunn:)22:01
bschaeferkgunn, well I did pull the wrong one, but its still wrong on the right one :)22:02
kgunnwell...these bugs definitely make you neurotic22:02
bschaeferyeeaah22:02
kgunncheck, double check...then check again22:02
bschaeferyeah, well its still true! whew...22:02
kgunnbschaefer: so you gotta intel_xmir.h with #if XMIR22:08
bschaeferkgunn, well  thats only included if XMIR right?22:12
kgunnnow...that header, "asks" if that predefine exists and then acts on it22:13
kgunnoops/now/no22:13
bschaeferkgunn, right, but it has be defined, and XMIR doesn't exist in the apt-get source ati/intel22:14
kgunnright22:15
bschaeferkgunn, im trying to do a dget on the packge to see if the deb-src is correct...but gpg is not liking who signed it (or rather the like of...)22:16
kgunnok...getting convinced...i think the drivers just need to be rebuilt22:21
bschaeferkgunn, yeah...how would we go about doing this :)22:23
Sarvattlooked into it a bit and its more likely the refactoring the intel dev did when RAOF switched the branch to his 2.21.12 one broke SNA to be honest, the one in the ppa did build with mir support..22:24
Sarvattthe one in daily-staging is versioned 2.21.9 but its really a 2.21.12 git snapshot from http://cgit.freedesktop.org/~ickle/xf86-video-intel/log/?h=xmir22:24
Sarvatt(can see that in configure.ac)22:25
kdubmaybe once ff is over i'll restructure some android display code...22:26
bschaeferSarvatt, hmm well doing a dget on that package Im picking up xmir stuff22:27
bschaeferbut not when doing a apt-get source...22:27
bregmabschaefer, that's because you don;t have the deb-src lines set up correctly:  trust the dget22:36
Sarvattbschaefer: it needs to be using https://code.launchpad.net/~mir-team/mir/xf86-video-intel-fixup instead of https://code.launchpad.net/~mir-team/mir/xf86-video-intel-vladmir which it just switched to yesterday and probably never got tested..22:38
bregmaSarvatt, are you saying there's a change somewhere that needs to get reverted?22:39
Sarvattor 3 days ago rather22:40
Sarvattwell it switched from 2.21.9 that had been tested with SNA I imagine for a long time to a branch that is a much newer git snapshot where the intel guys changed the xmir stuff around on 7/23, i'm just guessing thats where the problem started?22:42
kgunnSarvatt: yep...i think you're right22:42
kgunnwe went to head...untested22:42
Sarvatti have no context here but i'm just seeing an obvious thing22:42
bregmabschaefer, do you feel confident about bisecting that delta when you get back from lunch?22:46
bschaeferbregma, well ill trust dget for now onwn23:11
bschaeferSarvatt, awesome, thanks for looking into that!23:11
bschaeferbregma, how would one bisect the delta from the branches?23:12
bschaeferbregma, shouldn't we just have to point to the new one?23:12
bschaeferor take the ickles changes and merge them with RAOFs?23:12
bregmabschaefer, I would think the easiest thing is to revert to the old branch, but I'm thinking there was a reason why the newer one was used23:18
bschaeferbregma, hmm well looking at the rev, ins't the old branch the one we are using?23:21
bschaeferie. https://code.launchpad.net/~mir-team/mir/xf86-video-intel-vladmir23:21
bschaeferwhich I thought was the old one, but we should be using this one: https://code.launchpad.net/~mir-team/mir/xf86-video-intel-fixup23:22
bregma<Sarvatt> bschaefer: it needs to be using https://code.launchpad.net/~mir-team/mir/xf86-video-intel-fixup instead of https://code.launchpad.net/~mir-team/mir/xf86-video-intel-vladmir which it just switched to yesterday and probably never got tested..23:22
bschaeferbregma, well... yeah that would make the fixup the old one23:22
* bschaefer checks the diff of the 223:23
bregmaYa know what, I'd feel more comfortable if RAOF could explain why the change was made, and in the mean time drop back to the xf86-video-intel-fixup version -- can you try that and test to see if it solves the problem?23:24
* bregma does not want bschaefer to be working over the weekend23:25
bschaeferbregma, haha, yeah that does sound like a good approach23:25
bschaeferi've still got to make sure this ibus stuff is working as well23:26
bregmaibus will wait patiently until next week, we want mir to land as soon as possible23:26
bschaeferright, ill focus on this23:27
bschaeferhmm but I don't think this explain the ati problem :(23:28
bschaeferexplains*23:28
bregmaoh23:29
bregma:(23:29
bschaefercause moving back to uxa from sna fixes this intel problem23:30
bschaeferbut hmm I don't think this is going to fix the daily build problem23:30
* bschaefer looks into it anyway23:31
bschaeferat lease we know something strange is going on with the packaging...23:31
* bregma thinks SNA is something that requires a MAU for the token ring23:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!