I boot to run level 3, and use startx to launch the Gnome desktop.
This morning, I turned on the monitor, to see only the system monitoring messages usually visible when I hit Cntl-Alt-F12 and indeed Cntl-Alt-F1
took me to the normal tty1 login screen.
I logged in, but startx did not bring up the normal Mageia desktop screen, the top panels to MageiaWelcome (where you can click to minimize, maximize etc) did not appear, and an autostart program for multiple language characters had in its tool bar only the choice that would allow me to
quit.
Is there something to easily check and perhaps correct before I create a
new user and see if that works?
I have a full backup a few days old, but have no idea what or how much I would need to replace from backup.
Before starting floundering around, does anyone have suggestions?
Logging in to the machine using ssh from my backup machine (the one I am using at the moment) has crossed my mind, but I have never used it and
would need instructions on how to set that up.
On Sat, 3 Aug 2019 15:18:33 -0000 (UTC), Jim Beard wrote:machines,
Logging in to the machine using ssh from my backup machine (the one I am
using at the moment) has crossed my mind, but I have never used it and
would need instructions on how to set that up.
Depends on your setup. I assign static ip addresses to all nodes on my LAN. Makes it simple to just do a ssh target_node_name_here.
Should be easy enough to use systemctl to enable/start sshd on both
run "xhost xhost +$(hostname --fqdn)" thennode.
"ssh user@target_node_name_here" or "ssh user@target_node_ip_address_here"
With sshd running on both systems you can ssh from/to either system.
You can not ssh root@target. You use a user id and after logging in
do a su - root.
You can do a "ssh target" if you are going to use the same user on target
example:
$ ssh tb
Warning: Permanently added 'tb' (ECDSA) to the list of known hosts.
Last login: Sat Aug 3 02:02:47 2019 from wb.home.test
$ whoami
bittwister
I boot to run level 3, and use startx to launch the Gnome desktop.
This morning, I turned on the monitor, to see only the system monitoring messages usually visible when I hit Cntl-Alt-F12 and indeed Cntl-Alt-F1
took me to the normal tty1 login screen.
I logged in, but startx did not bring up the normal Mageia desktop screen, the top panels to MageiaWelcome (where you can click to minimize, maximize etc) did not appear, and an autostart program for multiple language characters had in its tool bar only the choice that would allow me to
quit.
Is there something to easily check and perhaps correct before I create a
new user and see if that works?
I have a full backup a few days old, but have no idea what or how much I would need to replace from backup.
Before starting floundering around, does anyone have suggestions?
Logging in to the machine using ssh from my backup machine (the one I am using at the moment) has crossed my mind, but I have never used it and
would need instructions on how to set that up.
On Sat, 03 Aug 2019 11:18:33 -0400, Jim Beard <jim.beard@verizon.net>
wrote:
I boot to run level 3, and use startx to launch the Gnome desktop.
Mageia 6, 7, or cauldron?
This morning, I turned on the monitor, to see only the system
monitoring messages usually visible when I hit Cntl-Alt-F12 and indeed
Cntl-Alt-F1 took me to the normal tty1 login screen.
That I haven't seen before, or heard about. Was the system left on with
just the monitor turned off?
I logged in, but startx did not bring up the normal Mageia desktop
screen,
the top panels to MageiaWelcome (where you can click to minimize,
maximize etc) did not appear, and an autostart program for multiple
language characters had in its tool bar only the choice that would
allow me to quit.
Is there something to easily check and perhaps correct before I create
a new user and see if that works?
I'd try the new user test first, as that's very easy to do and either
narrows the problem down to a ~/someconfigfile, or rules that out.
I have a full backup a few days old, but have no idea what or how much
I would need to replace from backup.
Before starting floundering around, does anyone have suggestions?
Check /var/log/Xorg.0.log, "journalctl -b -1" (prior boot), and if
present, the ~/.xsession-errors files for messages. If the error is
present in the current boot, also check "dmesg|tail".
Logging in to the machine using ssh from my backup machine (the one I
am using at the moment) has crossed my mind, but I have never used it
and would need instructions on how to set that up.
That's only needed if you cannot access a working terminal using
alt+ctrl+f2 or similar.
On Sat, 3 Aug 2019 15:18:33 -0000 (UTC), Jim Beard wrote:
I boot to run level 3, and use startx to launch the Gnome desktop.
This morning, I turned on the monitor, to see only the system
monitoring messages usually visible when I hit Cntl-Alt-F12 and indeed
Cntl-Alt-F1 took me to the normal tty1 login screen.
I logged in, but startx did not bring up the normal Mageia desktop
screen,
the top panels to MageiaWelcome (where you can click to minimize,
maximize etc) did not appear, and an autostart program for multiple
language characters had in its tool bar only the choice that would
allow me to quit.
Is there something to easily check and perhaps correct before I create
a new user and see if that works?
In my stupid opinion, you should always have a second user login for testing/proving if it is a user problem or system wide problem.
I now create a "normal" account on clean install, then a "junk" account,
then all my user accounts.
"normal" is to have a known, pristine account as a reference.
"junk" is used for using su to make all post install changes and for
general testing there after.
I have a full backup a few days old, but have no idea what or how much
I would need to replace from backup.
Yup, been there done that. I now have a user backup and a system backup script. User backup just does user files. System backup is nothing more
than a rsync of / less the user's files to a /hotbu partition.
Makes it dead easy to run restore_mga7 which rsync's /hotbu/ to mga7
Before starting floundering around, does anyone have suggestions?
Snippet derived from https://bugs.mageia.org/show_bug.cgi?id=16894
startx does not start default desktop configured in
/etc/sysconfig/desktop, defaults to IceWm
Reboot runlevel 3 get a user terminal and login startx startgnome
Logging in to the machine using ssh from my backup machine (the one I
am using at the moment) has crossed my mind, but I have never used it
and would need instructions on how to set that up.
Depends on your setup. I assign static ip addresses to all nodes on my
LAN.
Makes it simple to just do a ssh target_node_name_here.
Should be easy enough to use systemctl to enable/start sshd on both
machines,
run "xhost xhost +$(hostname --fqdn)" then "ssh
user@target_node_name_here" or "ssh user@target_node_ip_address_here"
With sshd running on both systems you can ssh from/to either system.
You can not ssh root@target. You use a user id and after logging in do a
su - root.
You can do a "ssh target" if you are going to use the same user on
target node.
example:
$ ssh tb Warning: Permanently added 'tb' (ECDSA) to the list of known
hosts.
Last login: Sat Aug 3 02:02:47 2019 from wb.home.test
I think I will use this machine as is for a while, make another complete backup of $HOME, and then use gnome-tweaks to try to get things back
where they were yesterday. The install of Mageia 7 was followed by a
copy in from Mageia 6 of $HOME so gnome-tweaks were in place, but my
attempts to improve things may have tangled up something. All had been working though, so I was a bit surprised at my problem this morning.
On Sat, 3 Aug 2019 19:43:33 -0000 (UTC), Jim Beard wrote:
I think I will use this machine as is for a while, make another
complete backup of $HOME, and then use gnome-tweaks to try to get
things back where they were yesterday. The install of Mageia 7 was
followed by a copy in from Mageia 6 of $HOME so gnome-tweaks were in
place, but my attempts to improve things may have tangled up something.
All had been working though, so I was a bit surprised at my problem
this morning.
Upon logout, mga6 gnome may have been dinked up by mga7 gnome tweaks.
I can recommend getting ssh working between all nodes.
Much easier to use gui tools rather than cli at runlevel3. :)
I seem to remember there is a way to use ssh and get a gui from the
target machine. My attempt to run startx when logged in via ssh
got me an error message that Only console users are allowed to use the X server.
On Sat, 3 Aug 2019 21:10:45 -0000 (UTC), Jim Beard wrote:
I seem to remember there is a way to use ssh and get a gui from the
target machine. My attempt to run startx when logged in via ssh got me
an error message that Only console users are allowed to use the X
server.
Yep, let target system boot runlevel5/gui and you should have X server access.
I seem to remember there is a way to use ssh and get a gui from the
target machine. My attempt to run startx when logged in via ssh
got me an error message that Only console users are allowed to use the X server.
On Sat, 03 Aug 2019 17:10:45 -0400, Jim Beard <jim.beard@verizon.net>
wrote:
I seem to remember there is a way to use ssh and get a gui from the
target machine. My attempt to run startx when logged in via ssh got me
an error message that Only console users are allowed to use the X
server.
#!/bin/bash
killall x0vncserver
x0vncserver display=:0
-SecurityTypes=None &
sleep 4
vncviewer -compresslevel 9 localhost:0
killall x0vncserver
The above will give you access to a gui that's already running on the
target machine, provided you are sshing to the user that is running the
gui.
On Sat, 03 Aug 2019 16:55:13 -0500, Bit Twister wrote:
On Sat, 3 Aug 2019 21:10:45 -0000 (UTC), Jim Beard wrote:
I seem to remember there is a way to use ssh and get a gui from the
target machine. My attempt to run startx when logged in via ssh got me
an error message that Only console users are allowed to use the X
server.
Yep, let target system boot runlevel5/gui and you should have X server
access.
I rebooted my backup machine to run level 5, and
ssh me@backup.home.invalid took me to a command line and the message
that only those on console were allowed to use X.
Either I am leaving out critical steps or parameters, or I need magical incantations to make it work.
On Sat, 03 Aug 2019 19:52:07 -0400, David W. Hodgins wrote:
#!/bin/bash
killall x0vncserver
x0vncserver display=:0
-SecurityTypes=None &
sleep 4
vncviewer -compresslevel 9 localhost:0
killall x0vncserver
The above will give you access to a gui that's already running on the
target machine, provided you are sshing to the user that is running the
gui.
My system knows nothing about x0vncserver or vncviewer.
I assume this involves installing vnc, but which vnc packages do I need, installed where?
Possibilities seem to be vnc-server-common, x11-vnc (my system seems to
be using wayland, so would this work?), tigervnc-server-module, tigervnc- server, tigervnc, and a variety of lib64.*vnc packages, which seem needed only for specific applications.
What I would like to do is to run my evolution mail program from the
machine it is on or from my backup machine. I would ssh in from my
backup machine and run evolution on the main machine. With gnome desktop running on both backup and main machine, I can open an x-term window on backup, ssh into my main machine using my username (the same on both machines), and run evolution, but rather than launch evolution and send
the output to me on backup it wants to create a whole new evolution.
This may be asking too much. Just being able to ssh between the two
machines is a substantial improvement over using nfs.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 175:26:41 |
| Calls: | 7,915 |
| Files: | 12,983 |
| Messages: | 5,797,729 |