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 757490 - Process-doubling on new session started from gdm
Process-doubling on new session started from gdm
Status: RESOLVED DUPLICATE of bug 747339
Product: gdm
Classification: Core
Component: general
3.18.x
Other Linux
: Normal major
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2015-11-02 15:57 UTC by jeanpatrick.guerrero@gmail.com (Account disabled)
Modified: 2015-11-15 00:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot of the system monitor (178.77 KB, image/png)
2015-11-02 15:57 UTC, jeanpatrick.guerrero@gmail.com (Account disabled) 		Details

Description jeanpatrick.guerrero@gmail.com (Account disabled) 2015-11-02 15:57:02 UTC 
Created attachment 314665 [details]
Screenshot of the system monitor

So I've spotted this bug for quite some time now (~1 month, on Arch Linux) : you get double-processes on a session from logging to gdm. Only exception when you set the session autologin, processes are not doubled and the memory usage is ~120 MB lighter.

A screenshot of the system monitor has been attached to this report.

The user "jp" is me. The user "gdm" get pretty much the same processes, or some absurdity's happening like Xorg + XWayland running in the mean time whereas I've selected the normal GNOME session (without Wayland).
Comment 1 jeanpatrick.guerrero@gmail.com (Account disabled) 2015-11-03 10:18:01 UTC 
Apparently an old bug : http://ubuntuforums.org/showthread.php?t=1315565
Comment 2 Ray Strode [halfline] 2015-11-15 00:16:23 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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