Hello All!
My system that has multi partitions on a SSD (primary) and a HDD
has had some updates and needed a reboot because of some funnies
with some appl. seeing files. So on the shutdown I booted into a
2nd partition holding MGA9 and updated that one and then did the
same for a win10 system before rebooting to the primary one.
On the boot it showed the graphic screen but when completing the
start up went to the tty service instead of booting up via sddm.
Now I logged in and tried running sddm but it could not find it
(owned by root?) so I did a sudo sddm and while this worked (but
showed flashing red screen) worked but any files created are owned
by root so no good and am force to use the other MGA9 partition on
a HDD.
So the question - How do I get back the primary system to boot into
KDE GUI ?
While I cam running using the HHD system there are various packages
not installed on it and it is a lot slower so would like to get
back to using the SSD version - plus it is annoying me that the
problem arose anyway :(
Vincent
Vincent Coen escreveu:
Hello All!
My system that has multi partitions on a SSD (primary) and a HDD
has had some updates and needed a reboot because of some funnies
with some appl. seeing files. So on the shutdown I booted into a
2nd partition holding MGA9 and updated that one and then did the
same for a win10 system before rebooting to the primary one.
On the boot it showed the graphic screen but when completing the
start up went to the tty service instead of booting up via sddm.
Now I logged in and tried running sddm but it could not find it
(owned by root?) so I did a sudo sddm and while this worked (but
showed flashing red screen) worked but any files created are owned
by root so no good and am force to use the other MGA9 partition on
a HDD.
So the question - How do I get back the primary system to boot into
KDE GUI ?
While I cam running using the HHD system there are various packages
not installed on it and it is a lot slower so would like to get
back to using the SSD version - plus it is annoying me that the
problem arose anyway :(
On machines using systemd, you can use the command:
systemctl set-default graphical.target
to set the graphical boot as default.
That command does not work at all -
sudo systemctl get-default graphical.target
[sudo] password for vince:
Too many arguments.
I used the get first to see what is set on current booted partition.
On Sun, 23 Mar 2025 09:27:31 -0400, Vincent Coen <VBCoen@gmail.com>
wrote: <snip>
That command does not work at all -
sudo systemctl get-default graphical.target
[sudo] password for vince:
Too many arguments.
I used the get first to see what is set on current booted partition.
See the man page. get-default returns a value, only set-default should
be passed a value.
On my current system ...
# systemctl get-default graphical.target
Hello David!
23 Mar 25 15:21, David W. Hodgins wrote to all:
On Sun, 23 Mar 2025 09:27:31 -0400, Vincent Coen <VBCoen@gmail.com>
wrote: <snip>
That command does not work at all -
sudo systemctl get-default graphical.target
[sudo] password for vince:
Too many arguments.
I used the get first to see what is set on current booted partition.
See the man page. get-default returns a value, only set-default should
be passed a value.
On my current system ...
# systemctl get-default graphical.target
I get Too many arguments.
MGA v9 and up to date now running on my ssd now that I was advised to run drakx11 and check the box for graphic used.
ON reboot the GUI is running and absolutely no idea why it lost that
setting .. the update gremlin strikes again at a guess :)
Vincent
MGA v9 and up to date now running on my ssd now that I was advised
to run drakx11 and check the box for graphic used.
ON reboot the GUI is running and absolutely no idea why it lost that
setting .. the update gremlin strikes again at a guess :)
Vincent
The quoting above is very messed up.
In my posting I had "# systemctl get-default" on one line showing the
single parameter I passed to the systemctl command, in a terminal
after using "su -" to become root.
The response "graphical.target" was on the next line showing the
response I received from the systemctl command.
So just run on one line ...
systemctl get-default
Do not type "graphical target" when entering get-default.
So to confirm, if result is NOT 'graphical.target' use set-default to it
and this saves using drakx11 correct ?
Sorry for being obtuse but I am a oldie at 78 this June and have only been using Linux since around early 2000 but that does not mean I have read an
up to date book on this distro, eye sight allowed :)
On Mon, 24 Mar 2025 10:32:15 -0400, Vincent Coen <VBCoen@gmail.com>
wrote: <snip>
So to confirm, if result is NOT 'graphical.target' use set-default
to it and this saves using drakx11 correct ?
Correct.
Sorry for being obtuse but I am a oldie at 78 this June and have
only been using Linux since around early 2000 but that does not
mean I have read an up to date book on this distro, eye sight
allowed :)
The only dumb question is the one not asked.
Regards, Dave Hodgins--Daniel70
Hello All!
My system that has multi partitions on a SSD (primary) and a HDD has had
some updates and needed a reboot because of some funnies with some
appl. seeing files.
So on the shutdown I booted into a 2nd partition holding MGA9 and updated that one and then did the same for a win10 system before rebooting to the primary one.
On the boot it showed the graphic screen but when completing the start up went to the tty service instead of booting up via sddm.
Now I logged in and tried running sddm but it could not find it (owned by root?) so I did a sudo sddm and while this worked (but showed flashing red screen) worked but any files created are owned by root so no good and am force to use the other MGA9 partition on a HDD.
So the question - How do I get back the primary system to boot into KDE GUI
?
While I cam running using the HHD system there are various packages not installed on it and it is a lot slower so would like to get back to using
the SSD version - plus it is annoying me that the problem arose anyway :(
Vincent
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 65 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 00:58:12 |
| Calls: | 862 |
| Files: | 1,311 |
| D/L today: |
10 files (20,373K bytes) |
| Messages: | 264,187 |