Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#59521 - [awesome] After awesome restart, many processes get multiplied
Attached to Project:
Community Packages
Opened by Thanos Apostolou (ThanosApostolou) - Friday, 03 August 2018, 23:42 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 11 August 2018, 16:54 GMT
Opened by Thanos Apostolou (ThanosApostolou) - Friday, 03 August 2018, 23:42 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 11 August 2018, 16:54 GMT
|
DetailsDescription:
When awesome is started with a display manager like lightdm, then after logout/login or after an awesome restart, many processes like gvfsd and others are created multiple times. Additional info: The problem gets solved if I edit the file `/usr/share/xsessions/awesome.desktop` and change the line `Exec=awesome` to `Exec=dbus-launch --sh-syntax --exit-with-session awesome`. I'm not sure if this is an upstream bug or if awesome is supposed to get started this way. Steps to reproduce: Install awesome. Start awesome with a display manager like lightdm. Restart awesome or logout/login and watch processes like gvfsd, gnome-keyring-daemon get multiplied each time. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 11 August 2018, 16:54 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: I can't reproduce this anymore. Probably I had something at my startup file that was causing multiple processes to be spawned. If you cannot reproduce this too, then feel free to close it.
Saturday, 11 August 2018, 16:54 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: I can't reproduce this anymore. Probably I had something at my startup file that was causing multiple processes to be spawned. If you cannot reproduce this too, then feel free to close it.