I don't know when this started as I haven't posted to dev for a while, but now when I do I never see the resulting post on the ML. I'm subscribed to dev, and I receive a copy of everyone else's posts, but not my own. Here's an example from yesterday, retrieved from my Sent folder: ############################################################## From - Fri Aug 30 16:37:41 2019 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00800000 X-Mozilla-Keys: From: Frank Griffin <ftg@roadrunner.com> Subject: Re: [dev] GDM no being started at boot time Reply-To: ftg@roadrunner.com To: dev@ml.mageia.org References: <CAONrEtYg7idH_Le_F70SWD13PqGddum6SS0jY2nohp-x7BTm7w@mail.gmail.com> Message-ID: <8877cff4-b1b6-f533-de12-d9caea622224@roadrunner.com> Date: Fri, 30 Aug 2019 16:37:41 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <CAONrEtYg7idH_Le_F70SWD13PqGddum6SS0jY2nohp-x7BTm7w@mail.gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US On 8/30/19 7:05 AM, Thierry Vignaud (via dev Mailing List) wrote: > Hi > Since quite some months, GDM doesn't start at boot time despite being > enabled. > > $ systemctl status gdm.service > ◠gdm.service - GNOME Display Manager >   Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; > vendor preset: enabled) >   Active: inactive (dead) > > I've tried unmasking, disabling/re-enabling, switching to another DM > then back to GDM, but to no avail. > At each boot, I've to manually run "systemclt start gdm.service". > > Any idea what could be the culprit? > Thanks Interesting. I've been doing fresh installs with all desktops selected, and every time when I boot the new system I get GDM in spite of the fact that I though SDDM was our standard. I think which DM you get corresponds to the last DE installed. If you go to /etc/systemd/system there should be a symlink for display-manager.service to a service in /usr/lib/systemd/system. If you switch the symlink to /usr/lib/systemd/system/gdm.service, it should give you GDM. ############################################################ I suspect the same thing is happening on qa-discuss.
Interestingly enough, I'm also subscribed to bugs, and I *did* get a copy of this bug report.
Could someone please address this ? I can't be sure whether anything I post is getting to the ML or not.
It didn't, I dont see it in the archive or anything in the mail logs... Can you try to send a new message to dev@ and add me in cc so I have something fresh to track...
CC: (none) => tmb
I sent you such a message at 8:53 AM EST.
And nothing has come to me or dev@ did you send to my mageia.org or iki.fi address ? And what outgoing server are you using (name or ip) so I cna see if we fail at initial connect ...
Actually scratch that... I got the mail to @iki.fi and now I see your response to: Re: [dev] HEADSUP: Python 3.8 stack landing in Cauldron /release sent to dev@ seems to be a long delay from your mail gateway...
Problem solved. Somehow the main.cf on my postfix relay server got reset from inet_interfaces = all mynetworks_style = subnet to inter_interfaces = localhost mynetworks_style = host so the server was rejecting forwarding attempts by my laptop. I can't imagine how, since I haven't changed the server config in quite a while. If it happens again, I'll suspect msec tomfoolery (as I update the system from cauldron daily). Sorry for the noise.
Closing.
Resolution: (none) => INVALIDStatus: NEW => RESOLVED
No worries, I'm just happy you found it