On Sun, May 05, 2013 at 11:45:52PM -0400, Ted Unangst wrote: > As part of my ongoing quest to find the browser that sucks the most, I > figured I'd try midori today. original gtk2 flavor. i386. current. > > At startup, I immediately get a popup that says "An instance of Midori > is already running but not responding." As you've probably guessed, > this is a lie. There is only one midori process running. > > It prints some messages about being unable to connect to a dbus socket > in /tmp which appear more truthful. I can confirm those files do not > exist. But that's not the awesome part. After I dismiss the dialog box > (the only button to click is OK even though I don't think this OK), I > get a new dbus socket with a *different* name.
Maybe asking the obvious, but can you make sure your X session starts a session dbus as your user ? Iirc xdm is supposed to do this automagically those days. midori works perfectly fine in regular xfce sessions, which handle that transparently. Do you have something setting a fake DBUS_SESSION_BUS_ADDRESS var in your environment ? Landry
