After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 415874 - Gnome-panel launchers cause shared pgid
Gnome-panel launchers cause shared pgid
Status: RESOLVED OBSOLETE
Product: gnome-panel
Classification: Other
Component: panel
2.17.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-07 23:23 UTC by Sebastien Bacher
Modified: 2020-11-06 20:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Sebastien Bacher 2007-03-07 23:23:38 UTC
The bug has been opened on https://launchpad.net/ubuntu/+source/gnome-panel/+bug/87584

"Binary package hint: metacity

All applications launched from gnome-panel launchers, menu, or alt-f2 share the same pgid. Gnome developers claim this is not typical behavior for the panel, so may be a result of an Ubuntu customization. The same applications launched from the terminal do NOT share PGID. This is a problem for several reasons (some highlighted in this forum thread: http://www.ubuntuforums.org/showthread.php?t=347023):

1. Pressing Ctrl+C in Matlab with shared PGID closes gnome-panel.
2. fbpanel cannot raise applications via the taskbar with the shared PGID (it can raise applications fine if they don't share PGID). The applications receive focus, but do not raise. This may also tie into metacity, as it may not be a problem with other window managers, but again I think it is Ubuntu-specific. Note that the windows properly receive focus, they just don't raise.
3. Python's IDLE environment fails to raise the shell window when that window receives focus (e.g., by pressing F5) after the initial opening. This is only true if running metacity, e.g., xfwm4 properly raises that window each time it receives focus.

I submit this as a single bug report, because it appears to be an issue in how the customized gnome build Ubuntu provides handles raising windows and sending focus when applications share a pgid (which is really a metacity problem, but it is compounded by the odd gnome-panel behavior). This is true at least in release 6.10.
...
To clarify - it is the group ID (PGID) that is the same, not the PID. A simple "ps -ej" in the terminal shows each process with its own PID, everything launched from the gnome enviornment sharing a PGID but other programs with different ones, and most everything sharing the SID.

Gnome - when this was submitted as a feature request to the gnome team, they responded that they had no code that would specifically cause this (which is perhaps not quite the same thing as saying they aren't responsible). Of course, I have no idea if Canonical has added any code that would explicitly do this, either.

I have a somewhat customized environment, but it is more or less pure gnome with routine apps and a few extras (except for a couple of java apps and vmware, nothing outside the repositories, and while I am running an extra xfce4 panel for my taskbar in addition to gnome-panel, the window manager/etc is unchanged). However, as the thread discussion shows, this isn't just my environment doing this - I'm more or less just trying to summarize the discussion on that thread and elsewhere, plus some of my own research.

Also, possibly relevant update - when I compiled the newest version of fbpanel (4.5 vs. 4.1 in the repositories), it seemed to interact with metacity more or less as I would expect. So perhaps this all ties into some relatively recent in metacity? I'm just guessing."
Comment 1 Vincent Untz 2007-05-26 11:44:20 UTC
Isn't this the case for 99% of the processes launched by other gnome processes?
Comment 2 André Klapper 2020-11-06 20:23:54 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.