[01:28] <Sarvatt> seb128: fatalerror is segfaulting because of patch 100 in xserver, can see it by just running Xorg from gnome-terminal and seeing the trash after ddxSigGiveUp. Disabling patch 100 fixes the segfaults and gdm handles the fatalerror fine by stopping and starting a new x but then we lose apport, I haven't been able to fix up patch 100 yet but it's really over my head anyway, not sure if we want to drop the xserver apport hooks or what. The error s
[01:28] <Sarvatt> eems to be coming from the initctl call in the session scripts not being in the exported path anymore (it's in /sbin and adding the path/hardcoding the call to /sbin/initctl fixes it) in the newer GDM's, can fix it in gdm but something does need to be done with that script making it segfault
[01:29] <Sarvatt> I rebuilt xserver without patch 100 and it works fine, also changing the initctl calls to /sbin/initctl and adding /sbin to the paths in the 2 gdm scripts fixes it
[01:30] <Sarvatt> /etc/gdm/Init/Default and /etc/gdm/PreSession/Default
[01:33] <Sarvatt> just dropping the patch will work but I dont know if you need that initctl to actually work and that needs the gdm change, can see that failing in /var/log/gdm/:0-slave.log when you try to use a guest session
[01:39] <Sarvatt> err in the second message I meant patch making it segfault not script
[08:04] <fagan> Any x people awake yet?
[08:05] <tjaalton> always
[08:05] <RAOF> Ish?
[08:05] <fagan> Im upgrade testing hardy to lucid 
[08:05] <fagan> and x is giving hassle 
[08:06] <fagan> here is one of my many xorg logs http://pastebin.ubuntu.com/358912/
[08:07] <fagan> I tried doing a Xorg -configure but it segfaults 
[08:09] <fagan> So any clue whats causing my computer to start in low graphics mode
[08:09] <tjaalton> what's your xorg.conf like?
[08:09]  * fagan pastebins
[08:10] <tjaalton> though the real reason is that the nv driver doesn't support GF8200
[08:11]  * bryyce waves
[08:11] <tjaalton> hi bryyce
[08:11] <bryyce> hi tjaalton
[08:12] <fagan> http://pastebin.ubuntu.com/358913/
[08:12] <fagan> Hmmm 
[08:12] <mvo> fagan: did you had the binary nvidia driver in hardy? and on upgrade you got nv that not supports your card?
[08:12] <tjaalton> mvo: not according to the xorg.conf
[08:12] <fagan> mvo: nope fresh install of hardy
[08:12] <tjaalton> fagan: so you always had vesa
[08:13] <mvo> oh, so it went vesa -> nv
[08:13]  * mvo nods
[08:13] <fagan> Thats weird
[08:14] <fagan> Was vesa the default in hardy?
[08:14] <tjaalton> if you had a logfile from hardy..
[08:14] <tjaalton> no, nv has never supported 8200
[08:14] <fagan> The binary driver supports the 8200
[08:14] <tjaalton> the autoconfig probably didn't work the same way
[08:14] <tjaalton> but nv doesn't
[08:15] <fagan> Ah
[08:15] <tjaalton> nouveau likely does
[08:15] <tjaalton> but, meh..
[08:15] <fagan> So its just that -nv doesnt support my driver 
[08:15] <tjaalton> card, yes
[08:16] <fagan> Oh so then its fine then 
[08:16]  * fagan always installs the binary anyway
[08:16] <tjaalton> ok so in that case the upgrader removed nvidia from the config?
[08:16] <fagan> Yep you have my logs 
[08:17] <fagan> It seems so
[08:17] <tjaalton> probably would be the best to move the config away, then you'd get vesa straight away and not via a crash
[08:18] <tjaalton> nothing valuable in that config anyway
[08:18] <fagan> tjaalton: will do 
[08:18] <tjaalton> ..that would be used
[08:18] <tjaalton> mvo: ^^
[08:18] <tjaalton> I don't know where that should be done though
[08:21] <mvo> tjaalton: thanks, it should only comment out "nvidia" if it find that and no nvidia driver binary
[08:22] <mvo> and the xorg.conf in the pastebin has no "nv" line 
[08:22] <mvo> or will xorg still behave differently if there is no xorg.conf or a xorg.conf with no explicit driver in it?
[08:25] <tjaalton> mvo: it'll use the default driver, but if there's no xorg.conf it'll build a list of fallback drivers to try
[08:25] <tjaalton> with the default one on top
[08:26] <mvo> nice
[08:47] <fagan> I have a bug report of the crash that I got earlier https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/509519
[08:48] <fagan> lol I love that the default is private always 
[08:48] <fagan> Its public now
[08:50] <seb128_> fagan, could be bug #506510
[08:50] <seb128_> did you try to open a new session or guest session?
[08:50] <fagan> New session
[08:51] <seb128_> k, likely the same issue then
[08:51] <fagan> seb128_: Its from an upgrade from hardy to lucid
[08:51] <bryyce> should be fixed with xorg-server (2:1.7.3.902-1ubuntu9)
[08:51] <bryyce> upgrade to my latest version and retest
[08:52] <fagan> Cool
[08:52] <seb128_> bryyce, I will when it's published
[08:52] <seb128_> bryyce, do you plan to bring back apport later? or do you want to catch crashes by some other way?
[08:54] <fagan> win 5
[08:56] <bryyce> seb128_, I don't know; I already sank a lot more time into this patch than I'd like.  signal handling code is tough to debug
[08:56] <bryyce> but it's silly for most of our crash bug reports to be due to the patch that enables crash bug reports
[08:56] <seb128_> right
[08:57] <seb128_> let's see if that uncover an another crash or if that purely due to that one
[09:20] <fagan> Yay the update fixed the segfault 
[09:20] <fagan> One more question is the nvidia binary driver still braking x?
[09:27] <fagan> Bug #494166 ?
[09:48] <bryyce> fagan, thanks for testing; please close any bugs you filed that are about this issue
[09:55] <tseliot> fagan: I guess not
[09:56] <bryyce> heya tseliot
[09:56] <tseliot> hi bryyce
[10:28] <LLStarks> is there anything similar to this for linux? http://www.realtech-vr.com/glview/
[11:38] <akaihola_> The page https://wiki.ubuntu.com/X/Troubleshooting/Freeze contradicts itself. It claims that a backtrace is a non-symptom, but lists "[mi] EQ overflowing" and X freeze as a relevant problem. A backtrace is included with such log messages.
[11:39] <akaihola_> Alternatively, what is a good place besides IRC to discuss Wiki pages, if I don't want to join the mailing lists? File a bug in Launchpad?
[11:39] <jcristau> "what's a good place to discuss this if i don't want to use the right place"?
[11:42] <tseliot> akaihola_: I think you can talk to bryyce about this. He lives in the US, therefore you might want to send him an email if you can't chat to him directly on IRC (because of time zones)
[11:53] <akaihola_> jcristau: Ok. It's just a hassle to join and unsubscribe a list just to send a quick note.
[11:53] <akaihola_> tseliot: Thanks!
[11:55] <jcristau> akaihola_: yeah subscriber-only lists are a pain i agree
[12:00] <akaihola_> Just e-mailed bryyce. Thanks guys, moving on...
[14:44] <tjaalton> whee, I got a X61 tablet for a spin to play with the wacom on it
[15:04] <coz_> tjaalton,  :)
[17:05] <tjaalton> bah, it's a serial wacom inside the X61 tablet..
[17:05] <tseliot> :-/
[17:47] <seb128> hum tseliot left
[17:47] <seb128> bryyce, the crash on user switch doesn't happen when booting without the splash
[17:47] <seb128> ie not using plymonth make it work
[18:49] <Sarvatt> seb128: did you get any of my messages about the crash happening because the gdm session scripts are trying to call initctl -q emit desktop-session-start DISPLAY_MANAGER=gdm without /sbin in the path? does adding /sbin: to the PATH and changing it to /sbin/initctl -q emit desktop-session-start DISPLAY_MANAGER=gdm in /etc/gdm/PreSession/Default (or /etc/gdm/Init/Default) fix it for you like it does for 
[18:49] <Sarvatt> me?
[18:50] <seb128> Sarvatt, to what path do you add those?
[18:50] <Sarvatt> /var/log/gdm/:0-slave.log shows the error when you try to use a guest session
[18:50] <seb128> what error?
[18:50] <Sarvatt> in /etc/gdm/PreSession/Default
[18:51] <Sarvatt> that it cant find initctl
[18:51] <seb128> let me try that
[18:51] <Sarvatt> there were changes so it did it as a user and it cant find /sbin stuff anymore
[18:52] <seb128> chrisccoulson, ^
[18:52] <seb128> could interest you as well
[19:01] <Sarvatt> ugh spotty connection -- <Sarvatt> dropping patch 100 in xserver fixed it so FatalError wouldnt segfault which fixed it for non-plymouth but I guess with plymouth it relies on what its emitting
[19:03] <seb128> Sarvatt, doesn't seem to be enough there
[19:03] <seb128> I copied initctl in /bin
[19:03] <seb128> which should be equivalent to your change
[19:04] <Sarvatt>  /bin wouldn't be in the path either would it? try /usr/bin?
[19:05] <Sarvatt> imagine /sbin would be there if /bin was
[19:05] <Sarvatt> gotta run
[19:05] <seb128> good comment
[19:05] <seb128> I will try that
[19:05] <seb128> thanks
[19:10] <seb128> Sarvatt, no, that doesn't fix my issue
[19:11] <chrisccoulson> i'm using /sbin/initctl, and it seems to have fixed my issue
[19:11] <chrisccoulson> i've got Xorg on different VT's now
[19:15] <seb128> ok, I will upload a fixed gdm
[19:15] <seb128> I've some other changes to do anyway
[22:04] <tjaalton> I don't understand the tablet.. the only device in the udev db related to wacom is under acpi subsystem, not pnp
[22:59] <superm1> is plymouth supposed to be working on non KMS hardware right now?
[23:00] <sebner> superm1: /here not working
[23:00] <superm1> sebner, okay same here then
[23:00] <sebner> seb128: is gdm to be supposed restartable with upstart (like it worked with init)?
[23:01] <superm1> got a bug open already?
[23:01] <seb128> sebner, I don't know, I guess so, sudo restart gdm?
[23:02] <sebner> seb128: sudo service restart gdm?
[23:02] <sebner> superm1: dunno
[23:02] <seb128> sebner, dunno, don't ask me about upstart
[23:02] <seb128> I've no clue about it
[23:03] <sebner> heh kk
[23:37] <cwillu> sebner, sudo restart gdm is the proper incantation
[23:38] <sebner> cwillu: cool. thx for the hint