[21:09] <skd5aner> anyone want to school me on how mythbuntu launches mythfrontend... my methods are not working
[21:09] <skd5aner> I know a few folks gave some suggestions a few weeks ago, but I don't recall what the suggestions were
[21:10] <skd5aner> Right now, I have lightdm, and autologin, which then launches an .xsession, which launches fvwm2 and mythfrontend... if mythfrontend exits or segfaults, the xsession is terminated, and I'm thrown back to the lightdm login screen...
[21:10] <skd5aner> however, it won't autologin
[21:11] <skd5aner> after the initial xsession is launched
[21:11] <skd5aner> if I do a "service lightdm restart", then it'll autolog my account in again
[21:24] <superm1> skd5aner: did you look at the stuff i shared before?
[21:24] <superm1> http://bazaar.launchpad.net/~mythbuntu-dev/mythbuntu/mythbuntu-default-settings/view/head:/usr/share/mythbuntu/session.sh
[21:24] <Zinn> [bazaar.launchpad.net] ~mythbuntu-dev/mythbuntu/mythbuntu-default-settings : contents of usr/share/mythbuntu/session.sh at revision 173
[21:24] <superm1> that's how we launch it
[21:24] <superm1> and mythfrontend will auto respawn if need be
[21:25] <skd5aner> let me go back and look
[21:25] <superm1> https://github.com/MythTV/packaging/blob/master/deb/debian/mythfrontend.sh
[21:25] <Zinn> [github.com] packaging/deb/debian/mythfrontend.sh at master Â· MythTV/packaging Â· GitHub
[21:25] <superm1> that's how we autorestart mythfrontend on crashes
[21:26] <superm1> you're probably fine if you just put an until loop like that in your xsession and don't need to pick up much else of what we do
[21:26] <superm1> the notification it's restarting is a nice touch, but i'm not sure that will work for you in such a basic session
[21:30] <skd5aner> so, right now... my .xsession is fairly basic and trivial...http://paste.ubuntu.com/1343685/
[21:30] <Zinn> [paste.ubuntu.com] Ubuntu Pastebin
[21:31] <skd5aner> superm1: are you suggesting that if I put that in an until loop that if mythfrontend crashes it'll actually simply relaunch within the same xsession?
[21:31] <superm1> skd5aner: yup
[21:31] <skd5aner> hmmm
[21:32] <superm1> you can test it by sending it a non normal exit kill signal
[21:32] <superm1> and see what happens
[21:32] <superm1> at least for us, that works properly
[21:33] <skd5aner> something like this: http://paste.ubuntu.com/1343698/ ?
[21:33] <Zinn> [paste.ubuntu.com] Ubuntu Pastebin
[21:34] <skd5aner> I installed libnotify
[21:34] <superm1> i think that should work
[21:34] <skd5aner> let me give it a go
[21:34] <superm1> it should hopefully spawn the notification daemon on demand for you too when the first notify-send is called
[21:37] <skd5aner> hmmm, back at the lightdm login prompt :/
[21:39] <skd5aner> didn't seem to work, when I did a killall mythfrontend, it killed the xsession
[21:41] <skd5aner> ah, nm
[21:41] <skd5aner> I did something a little backwards, let me try and fix my own error
[21:42] <skd5aner> superm1: ah, this is MUCH better
[21:42] <skd5aner> thank you!
[21:42] <superm1> sure
[21:42] <superm1> what did you do wardsback?
[21:43] <skd5aner> I copied and pasted into the pastebin, but forgot to put my changes BACK into the xsession :P
[21:43] <skd5aner> pretty dumb
[21:43] <superm1> haha
[21:43] <skd5aner> web form, terminal... what's the difference really? ;)
[21:44] <skd5aner> I will say, that since 0.26, I have to do a "kill mythbackend" twice before it kills, and I can no longer exit via the GUI
[21:44] <skd5aner> er... "kill mythfrontend"
[21:45] <skd5aner> I think it's getting hung up on unregistering the bonjour stuff
[21:56] <skd5aner> btw, the dialog didn't really seem to work for notify-send
[23:55] <superm1> skd5aner: oh that's interesting you run into that without the upstart job
[23:56] <superm1> we've been seeing that problem with the upstart job but never really investigated
[23:56] <superm1> but it's been happening in 0.25 too
[23:59] <skd5aner> yea, I can't say if it was a 0.26 issue, or a 12.10... I upgraded each within a few weeks of each other