Description of problem: A few days ago, I hit this bug, but didn't check it was a segfault. Today I tested again: [code] [doug@dougshost Desktop]$ sudo systemctl set-default multi-user.target Segmentation fault [doug@dougshost Desktop]$ sudo systemctl set-default multi-user.target Segmentation fault [doug@dougshost Desktop]$ sudo systemctl default [doug@dougshost Desktop]$ <no output> [/code] The symlink default.target remains unchanged. It has been confirmed by another user. One of those :o bugs. I know nothing about systemd. Version-Release number of selected component (if applicable): As above How reproducible: As above. Steps to Reproduce: 1. 2. 3.
Created attachment 8592 [details] journalctl output from segfaults Reproduced here, changing the runlevel works despite the segfault, though. I don't manage to find how to run the commands in English, sorry [root@cldrn_64 marja]# systemctl set-default multi-user.target Segmentatiefout (geheugendump gemaakt) [root@cldrn_64 marja]# systemctl get-default multi-user.target [root@cldrn_64 marja]# systemctl set-default graphical.target Segmentatiefout (geheugendump gemaakt) [root@cldrn_64 marja]# systemctl get-default graphical.target (To get it in English, I tried in vain, with LC_ALL=C, LC_ALL=en, LANGUAGE=C, LANG=C and with LANGUAGE=en and LANG=en) Attach the journalctl output from when I was running the above commands @ Doug To get the current default, I use "systemctl get-default"
CC: (none) => marja11
Assignee: bugsquad => mageia
Yes, it was like that when I first tried it. It changed the runlevel, but produced an error message of 2 or 3 lines. When I tried it again today to test it, it produced the output above. BitTwister confirmed it with the same output I did. Bill Unruh reported "no output" on Mga 5. He can join this bug if he wants. At a guess "geheugendump gemaakt" means "Core Dump." I have a vague recollection I saw that on my earlier attempt. Dictionaries aren't very good on computer terms. I looked at dmesg | tail, but it was taken up with a systemd command finding mysqld then losing it again. I am amazed that nobody else has come across this to date.
Marja, here is my report of my first experience, which seems to mirror yours: "This was on my broken Mga 6, to get a text bootup, and back again. "First, when sent to a Repair command prompt (not the "good luck" one) I used "systemctl set-default multi-user.target" to get a text bootup. When it segfaulted, I used "systemctl default" which said I was in runlevel 3. But because of the way bootup works, I didn't get a text bootup. Maybe I should have changed the kernel command line. "After I got the system up and working, I did the opposite. I ran "systemctl set-default graphical.desktop." Again it segfaulted, and again the default was now runlevel 5. I am not sure that it was a segfault, but it was a crash of some kind. I have never seen it happen before. When I get my mind back, I will hunt through the journal." When I ran it again today, I got the transcript I set out initially.
"systemctl default" was the wrong command, as Bit Twister has pointed out. Your note gave the correct command, and I missed its significance. The command still changes the runlevel, then segfaults. The only difference between the two occasions is the error message. I feel foggy-minded. I hope that I have got it right this time.
Marking this one as duplicate as I saw the other one earlier. *** This bug has been marked as a duplicate of bug 21356 ***
CC: (none) => doktor5000Status: NEW => RESOLVEDResolution: (none) => DUPLICATE