Description of problem: Use autologin, with either LDM or GDM, and with GNOME or Cinnamon. Try to open a gnome-terminal, but it won't start. Alarms by trying to open through xterm do not clarify. You can have gnome-terminal working through xterm only if you make a "su - yourself". Logging out after autologin and making normal login does not solve the problem. Version-Release number of selected component (if applicable): 1.0.0-38.mga7 How reproducible: Always when autologin is used. Steps to Reproduce: 1. Start with autologin 2. Try to open gnome-terminal 3. Fail without explanation 4. How to get around: remove autologin
This is confusing, autologin has: Group : System/Base but it doesn't seem to get pulled by basesystem-minimal and not even by basesystem: [marja@DenkBlok4 ~]$ urpmq --requires-recursive basesystem | grep "^a" aria2 aria2|wget|curl [marja@DenkBlok4 ~]$ Assigning to autologin's registered maintainer. CC'ing the Gnome maintainers, in case gnome-terminal is the culprit instead of autologin.
Summary: gnome-terminal will not start when set autologin (eithr with Light DM or GDM) => gnome-terminal will not start when autologin is set (happens with Light DM and also with GDM)CC: (none) => gnome, marja11Assignee: bugsquad => lists.jjorgeSource RPM: 1.0.0-38.mga7 => autologin-1.0.0-38.mga7
(In reply to Alberto Girlando from comment #0) > Use autologin, with either LDM or GDM, and with GNOME or Cinnamon. Upstream project is dead, and autologin code is now old : it does not follow policykit needs. I'd recommend to use automatic login of SDDM, and not this package anymore.
If you use MCC/drakautologin to configure autologin, it only installs/uses the autologin package if you are using the XDM or SLiM DMs. The GNOME Live ISO uses the GDM autologin facility, and has no trouble starting gnome-terminal. I've just tried enabling autologin here, using LightDM/Cinnamon, and again, no trouble starting gnome-terminal.
CC: (none) => mageia
OK, my fault.. The problem arose when I upgraded from Mageia6 to Mageia 7. I had autologin set up in Mageia 6, and by now I cannot say how it was set up there. And I had problems to understand the reason of this behavior, and if attribute it to gnome-terminal or to something else. I found that removing autologin solved the problem, so I opened the bug. But I did not try to restate autologin from drakautologin. When this is done, all is OK, thanks Martin. So the bug can be closed (I don't know if I can do myself), it only depended on issues connected to the upgrade and the route I followed (online upgrade with DNF).
Status: NEW => RESOLVEDResolution: (none) => INVALID