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 644685 - After Qutting launching System preferences in User Menu, g-c-c process is zombied.
After Qutting launching System preferences in User Menu, g-c-c process is zom...
Status: RESOLVED DUPLICATE of bug 644402
Product: gnome-shell
Classification: Core
Component: general
2.91.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-03-14 00:46 UTC by sangu
Modified: 2011-03-14 09:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sangu 2011-03-14 00:46:19 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=683309

Description of problem:
After Qutting launching System preferences in User Menu, g-c-c process is
zombied.
# ps ax | grep defunct
 7259 ?        Z      0:00 [gnome-control-c] <defunct>
 7279 ?        Z      0:00 [gnome-control-c] <defunct>
 7285 ?        Z      0:00 [gnome-control-c] <defunct>
 7394 ?        Z      0:00 [gnome-control-c] <defunct>

$ tail -f .xsession-errors
Window manager warning: Log level 8: _gather_pid_callback: assertion `data !=
NULL' failed
Window manager warning: Log level 8: _gather_pid_callback: assertion `data !=
NULL' failed
Window manager warning: Log level 8: _gather_pid_callback: assertion `data !=
NULL' failed
Window manager warning: Log level 8: _gather_pid_callback: assertion `data !=
NULL' failed

Version-Release number of selected component (if applicable):
2.91.91-1.fc15

How reproducible:
always.

Steps to Reproduce:
1. Click Uer Menu
2. Click System Preferences...
3. Quit System Prefereces (gnome-control-center)


mutter-2.91.91-1.fc15.x86_64
gnome-shell-2.91.91-1.fc15.x86_64
control-center-2.91.91-1.fc15.x86_64
Comment 1 drago01 2011-03-14 09:13:17 UTC

*** This bug has been marked as a duplicate of bug 644402 ***