/srv/irclogs.ubuntu.com/2012/03/19/#ubuntu-x.txt

=== inetpro_ is now known as inetpro
Sarvattbryceh: ok failsafe X not working is because of xdiagnose18:32
Sarvattaka downgrading to xdiagnose 1.6 from oneiric makes failsafe work again18:32
bryceherf.  oh?18:32
brycehweird.18:32
brycehok thanks18:32
Sarvattchange the init scripts?18:32
brycehhad to be18:32
brycehI'll have to review.  I did do some cleanups18:33
Sarvatti'm going through it all now, just tested the downgrade to be sure and that was it18:33
Sarvattbryceh: the explicit vt7 18:36
brycehah18:36
Sarvattthats the only thing remotely different18:37
Sarvatthttp://paste.ubuntu.com/891040/18:37
Sarvatttesting that out now18:37
brycehyeah and that could do it18:37
brycehwonder why I added it?18:37
Sarvattbryceh: yep that works, failsafe X is on vt218:41
brycehalright thanks18:41
brycehI *think* I might have added that to address some other problem...  digging...18:41
brycehaha18:42
bryceh  Force vt7 when launching Failsafe-X.18:42
bryceh  18:42
bryceh  In testing on Precise, it appears when lightdm doesn't start, X will18:42
bryceh  choose to start on vt1 by default, which ain't gonna work.18:42
brycehalright, so I'll re-test this on my hardware and upload new xdiagnose today or tomorrow18:44
=== yofel_ is now known as yofel
FernandoMiguelevening20:11
cndRAOF, ping22:55
RAOFcnd: Pong.22:55
cndRAOF, so I just pushed the xorg-gtest stuff22:55
cnda couple minor fixes and changes from a review from stephen22:55
* FernandoMiguel runs22:55
RAOFCool.22:55
cndRAOF, the question now is do we try to push it into precise?22:55
FernandoMiguelahhaha22:55
cndthere's a dependency on xorg-macros 1.1722:55
RAOFHm.22:56
cndwe either need to update in precise22:56
cndor remove it22:56
RAOFIf it weren't for that, I'd unreservedly say yes.22:56
cndRAOF, we could also distro patch out the need for xorg-macros 1.1722:56
brycehcnd, what needs it?22:56
Sarvattor just FFE xutils-dev, its already in debian and is very low risk22:56
cndbryceh, it depends on xorg-macros for proper distcheck22:57
cndit doesn't affect the real meat and potatoes of xorg-gtest22:57
RAOFThe only real concern with the new xorg-macros would be build failures, right?22:57
cndyeah22:58
cndthere's near 0 concerns though22:58
cndlet me double check that statement :)22:58
Sarvattyeah and there are none, i've built just about everything against the new macros, it's just excessively chatty with warnings now but not that big a deal :P22:58
cndSarvatt, what version of the macros do we have in ubuntu?22:59
Sarvatt1.15.something22:59
cndxutils-dev version doesn't match the upstream macros version22:59
cndhmmm...22:59
cndI don't know much about what has changed from 1.15 to 1.16.2...22:59
Sarvatt7.7~1 has 1.17 in it22:59
cndSarvatt, why is it ~1?23:00
Sarvatt1.16 was mostly excessively verbose warnings by default :)23:00
Sarvattbecause 7.7 katamari isn't released23:00
Sarvattbut the warnings were cut back some in 1.16.223:00
cndoh, it's the katamari version23:00
Sarvattyeah23:00
cndRAOF, bryceh, Sarvatt: would we be updating to the 7.7 katamari for precise anyways?23:01
cndI don't know what the release schedule is23:01
cnd"X11R7.7 development is underway for release in the first half of 2012."23:01
RAOFI don't think we'd bother?23:02
cndhttp://www.x.org/wiki/Releases/7.723:02
Sarvattnope its too late, most of the katamari releases weren't important though, things like 3 build system changes only for lots of the new lib releases23:02
cndthat page is way out of date though :)23:02
cndok23:02
brycehwe usually don't bother23:02
brycehfwiw, pulling in the new xorg-macros 1.17 is fine with me23:03
brycehas pointed out above, is likely very low risk.  If it helps xorg-gtest, great.23:04
Sarvattor xserver 1.12 video abi changes only (that we arent shipping) for lots of the video drivers23:04
RAOFI'm also happy to pull in xorg-macros 1.17.  We should do a test-rebuild of everything, though.23:04
cndRAOF: could we get that done before the beta 2 freeze on thursday?23:05
RAOFcnd: Oh, I'd do a post-hoc test rebuild.23:05
brycehhistorically the final katamari release has tended to come either after we release or well into when we're hard frozen.23:05
cndRAOF, ok23:05
RAOFcnd: Upload now, rebuild later :).  We don't expect any problems.23:05
cndSarvatt, do you think we should add xorg-macros into the current xutils-dev, or just sync 7.7~1 from debian?23:06
cndwhat has changed between 7.6+6 to 7.7~1?23:07
cndoh, we're up to 7.6+10 now :)23:07
Sarvattcnd: whichever you feel more comfortable with, i dont think it'd be good to go out of sync with xutils-dev versions though since the only thing useful out of it is macros23:07
cndSarvatt, I don't really know much about the xorg package23:07
Sarvatthttp://anonscm.debian.org/gitweb/?p=pkg-xorg/app/xutils-dev.git23:08
cndso I need some guidance :)23:08
cndSarvatt, oh, it's not even ~1 anymore23:08
cndit's -123:08
brycehcan't risk breaking imake!23:08
cndwait, nm23:08
cndthe tag is wrong23:08
cndok, so it seems like the best course of action is to sync from debian unstable23:09
cndat least it's not from experimental :)23:09
brycehxutils-dev is just utils for building the X packages, so as long as raof's rebuild goes fine, that's really all we need it for.  I'd just sync the debian package.  Keep it simple.23:09
Sarvattguess you cant ~ in the tag23:09
cndlast question is: do we need to file an FFe for it?23:09
cndostensibly, it's just to fix a big bug in xorg-gtest :)23:10
RAOFI think so, yes.23:10
brycehit can't hurt23:10
cndbut it does seem like it would be good to have an FFe for the xorg package23:10
Sarvattyep requestsync -d unstable -e xutils-dev23:10
brycehgood channel to communicate the whyfor of needing to rebuild the X archive23:11
cndI'll file an ffe for it23:11
SarvattExplanation of FeatureFreeze exception:23:13
Sarvattutil-macros 1.17.0 is needed for an updated xorg-gtest which is used for23:13
Sarvattunit testing X. The changes in this package are very low impact, util-macros23:13
Sarvattis required by most X packages and the only major change that is non-opt-in23:13
Sarvattis increasing the verbosity of GCC warnings during the builds.23:13
Sarvattthat sound ok? i'll just hit submit if someone with upload privileges can ack it23:14
brycehsounds good to me23:14
RAOFYup.23:14
brycehmaybe mention, "To be 100% safe, we will also trigger a rebuild of all potentially affected packages in the X stack."23:14
Sarvatthttps://bugs.launchpad.net/bugs/95979123:15
ubottuLaunchpad bug 959791 in xutils-dev (Ubuntu) "FFe: Sync xutils-dev 1:7.7~1 (main) from Debian unstable (main)" [Wishlist,New]23:15
brycehoh, +" and follow up on any issues that arise."23:15
Sarvattk editing it23:15
cndSarvatt, I was in the middle of filing it, but I'm glad you're taking it :)23:17
cndif anything, it will keep ScottK off my back for perceptions of too many FFe requests made by the touch team :)23:17
cndRAOF, do you know a release team member who would be able to review it right away?23:19
cndsome of the FFes can sit for a few days, and I don't want to leave this for after beta 2 freeze23:19
brycehmaybe ping slangasek?23:19
cndok23:20
eruditehermithey23:22
eruditehermitdoes anyone here have experience with fglrx?23:22
brycehSarvatt, ack'd23:22
Sarvattbryceh: thanks a ton for that, was just about to ask23:23
Sarvattcnd: sorry for stepping on toes, had it all done before seeing ya say you would do it and figured it'd save time :P23:23
cndSarvatt, np :)23:23
Sarvatthave been planning on filing that for the past week23:23
cndI'm surprised someone else was willing to file an FFe :)23:24
cndbryceh, if you clicked the "this affects me too" button, I think it's the wrong thing to do for an FFe23:24
cndthe janitor bot moves it to confirmed23:24
brycehah23:24
cndand the process documentation says it needs to be in the new state23:24
cndthe release team has probably realized that by now23:25
Sarvattcnd: hmm23:25
cndbut I don't like leaving things to chance23:25
Sarvattso when i file bugs with requestsync without upload permission, its in a new state and a core-dev has to ack it by setting it confirmed23:25
cndSarvatt, that's a different process from FFes I think23:26
Sarvattbut i guess this ones different because its in the FFe stage, after THAT got acked it'd unsubscribe release team and they'd subscribe sponsors and go through that23:26
cndhttps://wiki.ubuntu.com/FreezeExceptionProcess#General_Instructions23:26
cndit says if it's not in the new state, the release team may not see it23:27
cndI *think* the release team moves it to confirmed23:27
cndin which case, their reports may not show a bug that has already been moved to confirmed23:27
Sarvattsounds right23:27
Sarvatteruditehermit: http://paste.ubuntu.com/891499/23:36
eruditehermitSarvatt, what does that do?23:37
Sarvattjust add your switcheroo stuff you want to do to it on resume to disable the gpu23:39
eruditehermitSarvatt, hmm, I already have a script that does that23:39
eruditehermitSarvatt, the issue is that it causes my system to be unresponsive for 20 seconds23:39
Sarvattah gotcha, no clue about that :(23:39
eruditehermitand the fans start whirring uncontrollably during this time23:39
eruditehermitthis is annoying when it happens in public23:40
eruditehermitlol23:40
eruditehermitideally, switcheroo would save the state before suspend23:40
eruditehermitor not report incorrect state23:40
eruditehermitSarvatt, also my fglrx works with hybrid gfx, but when I want to switch back to intel, it doesn't switch where it looks for libGL23:44
eruditehermitis there an updated ubuntu package version that works with hybrid?23:47
eruditehermityou mentioned someone was working on that?23:47
SarvattI have absolutely no clue at all on the status of it outside of tseliot saying he was working on those scripts not long ago, he's the maintainer of it and its about 2 am his time now so cant ask23:50

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