Xlobby is crashing on startup fairly regularly lately for me. X completes all of the regular startup steps, and after the "Starting Xlobby.." step, it switches to my main screen but then throws this error:

Is this a problem with my system, or is it something specific to xlobby? I've added a couple of buttons to my main screen in the past week, but nothing weird or new?

Thanks for any thoughts on how to troubleshoot this!

[edit - this was caused by the xoap-weather plugin. I was not actively using xoap-weather, but had accidentally left it in the xlobby/plugins folder. removing the xoap-weather directory appears to have solved this problem.]

Last edited by gravy on Tue May 08, 2012 2:05 pm, edited 1 time in total.

Update: I checked the xlobby log and saw that my menu screen had a "enter event' associated with it - the xlobby action calls a girder event to get the current sunrise and sunset.

I recalled having problems before when I tried putting "enter events" on the main menu screen, usually resulting in xlobby crashing, so I"ve removed this "enter event" for now. Xlobby seems to be starting ok again now and will keep testing.

Yes, its my XL server machine. It is a multi-use server so unfortunately there are lots of things running concurrently. XL, Girder, and my whole-home audio services (Nuvo Technology). They've all worked in the past though, and I didn't make any updates to the other software. But you could be onto something there.

As for XL, I have made 2 recent changes:

1. Stephen implemented the ability to allow pop-up windows using the integrated browser, so I updated to the most recent bleeding edge version to test it.2. I added 2 overlays to view my new IP cameras. At first, I tried using xlobby's "media player" action to play location> rtsp://192.168.x.x/play1.sdp, but then simplified it and just access the cameras via http / embedded web pages on Xlobby overlays.

I wonder if I left a media player "Play Location" event in there somewhere by accident. I'll have to keep a close eye on the xlobby log and see if I can correlate the crash time to a specific xlobby event.

Check your xlobby folder for a file called "log-crashes-xlobby.txt", upload that if the times look right at the top it will help me track it down. I tried creating an enter event but I couldn't get it to crash, it's possible it is the enter event and you are trying to do something too early. Hopefully the log-crashes file is there.

Thanks for the tip on the log-xlobby-crashes.txt file. That helped a ton! Here's the crash-log. It definitely coincides with the Stop error, and it was related to xoap-weather, which I no longer use and I thought I had uninstalled! I no longer use this plugin so I've deleted it. Hopefully that resolves things. I'll test for awhile and update the subject to [resolved] if so.