[00:41] <ubotu> New bug: #196318 in xorg (main) "small screens end up only allowing small external display resolutions" [Undecided,New] https://launchpad.net/bugs/196318
[00:44] <ubotu> New bug: #194929 in xserver-xorg-video-intel (main) "hardy alpha5, i810 fuzzy/choppy problems" [Undecided,New] https://launchpad.net/bugs/194929
[03:20] <ubotu> New bug: #196349 in xserver-xorg-video-unichrome (universe) "xserver-xorg-video-unichrome broken in hardy." [Undecided,New] https://launchpad.net/bugs/196349
[09:39] <tjaalton> hmm, i965 doesn't start a session with vesa.. x-window-manager/compiz gets stuck
[09:43] <tjaalton> bryce: what's your opinion about vmmouse? the current method of using vmmouse_detect doesn't work, and just defaulting to it instead would fall back to mouse when the (driver internal) check fails
[10:01] <tjaalton> mvo: what do you think of bug 67996, you said that /usr/X11R6/bin could be moved aside instead of failing the upgrade?
[10:01] <ubotu> Launchpad bug 67996 in xorg "x11-common preinst script fails (was: aborts /usr/X11R6/bin not empty)" [High,Confirmed] https://launchpad.net/bugs/67996
[10:07] <tjaalton> hm, my session doesn't work with intel either
[10:11] <Ng> erk
[10:12] <Ng> my laptop just suspended and on resume X was broken and green :(
[10:13] <jcristau> some suspend/resume problems on intel are fixed in .25-rc3
[10:16] <Ng> hmm
[10:20] <Ng> testing it again and I saw the same green screen flash right after it powered up, but then it was redrawn with the proper X stuff
[10:20] <tjaalton> the current kernel in hardy has the drm bits backported
[10:21] <tjaalton> but maybe rc3 has more
[10:23] <mvo> tjaalton: yes, I think it is wrong to fail here, I think what it should do is to warn the user via debconf about it but then move /usr/X11R6/bin to /usr/X11R6/bin.move_on_upgrade or something like this
[10:24] <tjaalton> mvo: ok, I'll change it and modify the message too
[10:25] <mvo> tjaalton: great, thanks
[10:26] <jcristau> are there that many problems left with that?  i don't remember many reports of broken upgrade after etch release
[10:26] <tjaalton> jcristau: shouldn't be, but..
[10:27] <tjaalton> there was at least a broken opera
[10:27] <tjaalton> this change can go right after hardy is released
[10:27] <jcristau> not from a deb then?
[10:27] <tjaalton> yes, official opera deb
[10:27] <tjaalton> upstream crap :)
[10:28] <jcristau> x11-common conflicts with opera
[10:28] <tjaalton> well, that was an example.. don't know if there are others
[10:28] <tjaalton> maybe I should just ask
[10:34] <Ng> mvo: http://bugzilla.gnome.org/show_bug.cgi?id=482354 was the firefox/wm thing I mentioned
[10:34] <ubotu> Gnome bug 482354 in general "gtk_window_present() causes full applications to move workspaces" [Normal,Unconfirmed] 
[10:34] <Ng> and a simple testcase for the weird borderless bug doesn't expose it, so maybe I have a bug ;(
[10:39]  * mvo checks
[10:49] <jcristau> tjaalton: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/67996/comments/13 eg has nothing to do with that bug afaics
[10:49] <ubotu> Launchpad bug 67996 in xorg "x11-common preinst script fails (was: aborts /usr/X11R6/bin not empty)" [High,Incomplete] 
[10:50] <jcristau> and the rest of the failure reports are old
[10:54] <tjaalton> yeah, era is complaining about xli
[10:55] <tjaalton> I'll hold off that change for now and upload what I have now
[10:55] <tjaalton> nownow
[13:40] <ubotu> New bug: #196560 in xorg (main) "[gutsy] X crash (low graphics mode) when logging out and in several times consecutively" [Undecided,New] https://launchpad.net/bugs/196560
[14:31] <tjaalton> jcristau: yep, you were right.. era didn't have the problem anymore, so I closed it. thanks for the push ;)
[17:04] <bdmurray> Wasn't nvidia-glx-config removed recently?
[17:19] <mario_limonciell> bryce, are you around momentarily?
[17:29] <bryce> hi mario_limonciell
[17:30] <mario_limonciell> hey bryce
[17:30] <mario_limonciell> had a few questions regarding how fn-f8 was "supposed" to be handled on intel cards
[17:31] <mario_limonciell> is acpid supposed to be catching the events for them, or all within the intel video driver?
[17:32] <jcristau> the driver doesn't deal with that afaik
[17:32] <jcristau> probably a bios thing
[17:35] <bryce> mario_limonciell: in theory acpi should be handling it all
[17:36] <mario_limonciell> bryce, so in the event that /var/log/acpid isn't showing any of these events being caught, who to start pointing fingers at likely?
[17:37] <bryce> well, I wouldn't point fingers, but mjg59 is the best guy to answer questions about it
[17:38] <bryce> sometimes the issue goes down as far as the kernel
[17:38] <mario_limonciell> okay, well on this morning's call, rtg had mentioned to poke you on it first
[17:39] <mario_limonciell> well let me put it this way though - it seems that something gets intercepted by the keypress. FN-F8 issues a whole bunch of events to xev, but nothing with the randr change on the displays
[17:40] <mario_limonciell> which was why I was thinking to point it at xserver-xorg-video-intel
[17:40] <bryce> hang on, I have a bug report about this...
[17:42] <jcristau> mario_limonciell: the driver shouldn't be involved in this at all. if you get a keypress event, then you can configure your desktop env to act on it
[17:42] <mario_limonciell> no keypress event is caught, let me get a pastebin showing you what events actually are caught by xev
[17:43] <jcristau> (seems to send XF86Display here)
[17:44] <mario_limonciell> http://paste.ubuntu.com/5106/
[17:45] <bryce> bug #144225, #133568
[17:45] <ubotu> Launchpad bug 144225 in xrandr "Fn + F8 doesn't work on Dell Inspiron 6400 to switch display to another monitor" [Low,Triaged] https://launchpad.net/bugs/144225
[17:45] <ubotu> Launchpad bug 133568 in xserver-xorg-video-intel "fn+f8 (crt/lcd switch) does nothing" [Medium,Confirmed] https://launchpad.net/bugs/133568
[17:45] <jcristau> hmm. maybe i'm wrong. the driver seems to listen to acpi stuff
[17:45] <bryce> both of those are misfiled; it's not xrandr and like jcristau it's not a video driver thing
[17:46] <mario_limonciell> they're also dated back some time - as i'd imagine behavior has changed on hardy
[17:47] <bryce> yeah could be
[17:48] <bryce> that latter one seems to not be about it not working, but not working they way they expect
[17:52] <bryce> hmm, it sounds like we need something better than just mapping to xrandr --auto
[17:52] <mario_limonciell> well but in this case, xrandr --auto isn't even being called 
[17:52] <bryce> it needs to be a toggle type thing that switches between that and xrandr --output FOO --off
[17:52] <bryce> yeah, I'm just saying in general ;-)
[17:53] <mario_limonciell> yeah, i'll agree there, but that framework for querying the driver other than xrandr | grep BLAH would probably be nicer to have first before that
[17:55] <mario_limonciell> well for now i'll mark the bug with xserver-xorg-video-intel pending more information
[18:05] <ubotu> New bug: #196176 in dell "FN-F8 doesn't switch displays on M1330" [Medium,Confirmed] https://launchpad.net/bugs/196176
[18:07] <mario_limonciell> well it would appear that after a lot of presses an XF86Display key is caught by xev, but X doesn't react on that keyevent
[18:46] <jcristau> mario_limonciell: X *sends* the key event
[18:46] <jcristau> so that you can do whatever you want client-side with it
[18:47] <mario_limonciell> jcristau, well I think i've narrowed it down further.  gnome-settings-daemon is crashing
[18:47] <mario_limonciell> at when FN-F8 is pressed
[18:48] <jcristau> ah :)
[18:48] <mario_limonciell> so perhaps it wasn't ported to xrandr 1.2
[18:48] <mario_limonciell> off to CVS to look around :)
[18:49] <mario_limonciell> too bad apport doesn't catch it though
[20:04] <asac> tjaalton: hey. i have "enemy territory QW" and it plays fine with -generic fglrx, but i get rendering errors + worse: quick system crashes when using -rt. any idea?
[20:11] <tjaalton> asac: hmm, sorry no idea.. maybe abogani might know, he should be the -rt master
[20:16] <mario_limonciell> whew okay after tracking that all down, here's my update on it - g-s-d doesn't support switching displays (yet).  2.24 is the target
[20:16] <mario_limonciell> that crash that i was encountering is indeed a bug with g-s-d 
[20:16] <bryce> ahh interesting
[20:16] <mario_limonciell> so perhaps we need a more local fix until 2.24
[20:17] <bryce> mario_limonciell: do we have those bugs in launchpad against gsd?
[20:17] <mario_limonciell> bryce, i just got them an unoptimized backtrace upstream
[20:17] <mario_limonciell> at bugs.gnome.org
[20:17] <mario_limonciell> i'll link a launchpad bug once i find the most appropriate one
[20:17] <bryce> great, thanks
[20:17] <mario_limonciell> so for a more local fix, i'd propose just binding fn-f8 to xrandr --auto
[20:18] <mario_limonciell> at least until it's properly implemented upstream
[20:20] <bryce> hmm, I thought we already had fn+f8 bound to xrandr --auto though?
[20:24] <bryce> hi seb128
[20:24] <mario_limonciell> maybe at one point
[20:24] <mario_limonciell> but i'm not sure where that would sit now
[20:24] <bryce> yeah me either
[20:24] <mario_limonciell> do you know when the last time that was present?
[20:24] <bryce> mario_limonciell: seb128 or mjg59 might know the details
[20:25] <mario_limonciell> seb128, well if you are aware, do you know if/when/how fn+f8 was bound to xrandr --auto?
[20:25] <bryce> mario_limonciell: I am fairly certain it was there in gutsy; I've seen bug reports referring to side effects when it's hit
[20:26] <seb128> mario_limonciell: it's a gnome-control-center shortcut, I think it was dropped in hardy on the way and I will add it back when I do the next gnome-control-center upload
[20:27] <seb128> hey bryce
[20:27] <mario_limonciell> seb128, ah that would make more sense then :)
[20:27] <bryce> mario_limonciell: btw I have another mythtv question
[20:27] <mario_limonciell> go ahead shoot
[20:28] <bryce> mario_limonciell: I installed mythfrontend on one of my laptops (which I use for a variety of things, and just sometimes mythtv), but now on each boot it's prompting me for mythtv settings, and then autologging me into mythtv
[20:28] <bryce> so I guess a two parter question
[20:28] <bryce> a) how do I get it to not prompt for the same info, and b) how do I turn off the auto-loging?
[20:29] <bryce> oh, if it matters, the front end is Hardy, the back end Gutsy
[20:30] <mario_limonciell> bryce, likely gnome is starting it up
[20:30] <mario_limonciell> er wait
[20:30] <mario_limonciell> its autologging from gdm?
[20:30] <bryce> right
[20:30] <mario_limonciell> remove the package ubuntu-mythtv-frontend
[20:31] <mario_limonciell> it creates that autologin session.  perhaps its worthwhile ditching that package to avoid confusion
[20:31] <bryce> hmm
[20:32] <bryce> maybe it's just a gdm setting?  *poking around*
[20:32] <mario_limonciell> well that package provides an override gdm config
[20:32] <mario_limonciell> so yes in a sense it is a gdm setting
[20:32] <bryce> aha, there's flags in /etc/gdm/gdm-cdd.conf for automatic and timed logins
[20:33] <bryce> awesome, thanks
[20:33] <mario_limonciell> if you aren't using the autlogin feature, just remove the package
[20:33] <mario_limonciell> that's the only useful thing it provides :)
[20:33] <bryce> oh interesting
[20:33] <bryce> it sounds so official ;-)
[20:34] <mario_limonciell> yeah hence why i think i should just nuke the package from debian/control
[20:34] <mario_limonciell> it causes confusion :)
[20:37] <bryce> btw, I checked through your mythbuntu.org site last night - great work on it, lots of really useful info :-)
[20:38] <bryce> finally I learned how to shut off the screensaver ;-)
[20:43] <mario_limonciell> thanks :)
[20:43] <mario_limonciell> ugh upstream nailed the bug -
[20:43] <mario_limonciell> its because of one of our gsd patches
[20:44] <mario_limonciell> seb128, 19_extra_keybindings.patch shouldn't be present
[20:44] <mario_limonciell> its not complete
[20:44] <mario_limonciell> or at least it should be modifying a little bit mroe
[20:46] <seb128> mario_limonciell: ?
[20:46] <mario_limonciell> seb128, gnome bug 518637
[20:47] <ubotu> Gnome bug 518637 in plugins "crash in media keys on resume?" [Critical,Resolved: notgnome] http://bugzilla.gnome.org/show_bug.cgi?id=518637
[20:47] <mario_limonciell> that was caused by 19_extra_keybindings
[20:47] <mario_limonciell> because of not having a callback to the XRANDR key
[20:48] <seb128> mario_limonciell: right, as said I'll fix the xrandr thing in the next upload
[20:49] <mario_limonciell> seb128, okay just wanted to point out its in gsd not gnome-control-center then
[20:49] <seb128> mario_limonciell: thanks
[20:49] <mario_limonciell> are you aware of where the changes need to be made?  I can summarize what i've discovered here in the last 2 hours in a bug to save you some trouble if you'd like
[20:50] <seb128> I think using what we had in gutsy should do the trick
[20:53] <seb128> mario_limonciell: no?
[20:54] <mario_limonciell> seb128,  i'm not aware of exactly what was in that patch.  the necessary change is pretty small to 19_extra_keybindings.  give me a few minutes and i'll test what i believe is necessary, and then pastebin it.  should hopefully solve things
[20:56] <seb128> mario_limonciell: http://paste.ubuntu.com/5119/
[20:57] <seb128> mario_limonciell: so basically the schemas and the code case
[20:57] <mario_limonciell> seb128, it's very similar to that yes.  i just tested it and it works
[20:57] <seb128> very similar? what is wrong in the version I copied?
[20:57] <mario_limonciell> execute() is no longer used
[20:58] <seb128> ok, will adapt to the current code style
[20:58] <seb128> but that's the idea, right?
[20:58] <mario_limonciell> yeah.  i've got the patch together.  don't worry about it.  i'll track down the bugs and put together a debdiff
[20:59] <mario_limonciell> i've been tracking this down the better part of the afternoon, it will feel good to have fixed it :)
[20:59] <seb128> what patch?
[20:59] <seb128> I'm about to do the upload with that change and a svn fix, should I wait on something elsE?
[20:59] <mario_limonciell> to update 19_extra_keybindings
[21:00] <seb128> no need to bother
[21:00] <mario_limonciell> okay, well here: http://paste.ubuntu.com/5120/  
[21:01] <mario_limonciell> that's the current syntax +                execute (manager, "xrandr --auto", FALSE, FALSE);
[21:02] <seb128> mario_limonciell: is there a bug on launchpad?
[21:02] <mario_limonciell> yes
[21:02] <mario_limonciell> bug 179444
[21:02] <ubotu> Launchpad bug 179444 in gnome-control-center "gnome-settings-daemon crashed with signal 5" [Medium,New] https://launchpad.net/bugs/179444
[21:03] <seb128> mario_limonciell: can you attach the patch there?
[21:03] <mario_limonciell> sure
[21:03] <seb128> I'll use your version since you worked on it that's fair I think ;-)
[21:03] <seb128> feel free to ping before starting working next time
[21:03] <seb128> somebody pointed this one some times ago and I knew what to change
[21:03] <mario_limonciell> well i didn't realize it'd be this involved, but yeah next time i will :)
[21:19] <seb128> mario_limonciell: gsd update uploaded, thanks
[21:34] <mario_limonciell> thanks a bunch
[21:42] <seb128> thank you for looking in the issue
[21:42] <seb128> to the issue
[21:42] <seb128> rather ;-)
[23:55] <ubotu> New bug: #196802 in xserver-xorg-video-unichrome (universe) "Unichrome setup problems" [Undecided,New] https://launchpad.net/bugs/196802