GNOME Bugzilla – Bug 67609
use more than UID to decide "galeon already running"
Last modified: 2004-12-22 21:47:04 UTC
I'm doing a kiosk thing, using the timedLogin stuff I added to gdm, which logs in a default user. I'm trying to run X on another machine (as X -broadcast) which will be managed with gdm on the server (using xdmcp) and act as an X-terminal. This mostly works fine, except for galeon. Galeon sees the UID is the same, but is not checking anything else (like maybe controlling tty, process group and so forth) of a running galeon when deciding whether to start up a new one, so if the guest user is logged in on the server, instead of getting a galeon on my X-terminal, I get a new galeon tab in the server galeon. I don't know if anyone else is likely to have this problem, and I might find a better way of doing what I want to in the meantime, so I'm marking this as minor severity. If you think it should be fixed, but don't want to mess with it, I can check the code out again and see to it myself.
you really shouldnt be running galeon twice under the same UID, galeon is not designed for concurent operation of multiple instances over the same user files(bookmrks, history, cache..etc.)
I can do this with mozilla, which I guess doesn't check. In my kiosk login use of galeon, I've got as much as possible (including bookmarks)readonly anyway. I'm still trying to think of a better way to do this than multiple logins, and haven't found a good way to change current galeon behavior. Galeon currently uses oaf, and I wrote some test code: client = oaf_activate ("repo_ids.has('IDL:galeon/browser:1.0')", NULL, OAF_FLAG_EXISTING_ONLY, &oaf_id, &env); g_message(oaf_actinfo_stringify (oaf_actid_parse (oaf_id))); and looked at the output of that, and PPID/PGRP/SID from ps, and decided that maybe to do this would require getting DISPLAY out of /proc/<galeon>/environ, which would be ugly. So while I'd still like a kiosk-mode galeon, I'll consider other approaches (like hacking gdm some more) for now, unless others want a kiosk-mode also.
*** This bug has been marked as a duplicate of 69260 ***