-singleInstance seems not to be working

[bremner]

Running DrRacket twice with -singleInstance is starting two gracket processes

% ps x | grep Instance
621 pts/2 Sl 0:07 /usr/lib/racket/gracket -singleInstance -N /usr/bin/drracket -J DrRacket -l- drracket/drracket.rkt /home/bremner/foo.rkt
644 pts/2 Sl 0:10 /usr/lib/racket/gracket -singleInstance -N /usr/bin/drracket -J DrRacket -l- drracket/drracket.rkt /home/bremner/bar.rkt

This is on Debian (I tested 6.11 and 6.12); I had a report of similar behaviour on Arch Linux.

At least in my case libunique-1.0 is installed, although I believe drracket will print an error at startup if it is not and -singleInstance is used

[mflatt]

libunique matters only when using GTK+ 2. With (the default) GTK+ 3, linunique isn't needed.

I've pushed a repair to the "gui-lib" package that I hope will solve this problem on your machine: racket/gui@046a0fb

[bremner]

Matthew Flatt <notifications@github.com> writes:

libunique matters only when using GTK+ 2. With (the default) GTK+ 3, linunique isn't needed. I've pushed a repair to the "gui-lib" package that I hope will solve this problem on your machine: ***@***.***

It looks like something is still going wrong here. I get % drracket -singleInstance GLib-GIO: g_application_get_is_remote: assertion 'application->priv->is_registered' failed Followed by what looks the usual startup, with a progress bar and icons. The second "drracket -singleInstance" still takes several seconds to start up. Full disclosure: what i did was cherry-pick that one commit into an unpacked racket-6.12-src.tgz and rebuild.

[mflatt]

Looks like I mangled that commit, so that it didn't get all the needed pieces. I've pushed another commit to add the call to g_application_register.

[bremner]

Matthew Flatt <notifications@github.com> writes:

Looks like I mangled that commit, so that it didn't get all the needed pieces. I've pushed another commit to add the call to `g_application_register`.

Yes, that seems to fix it, thanks! d