Hi, You are saying you installed a new drive and then you reboot and you get the tty screen instead of your KDE desktop? Can you elaborate more about your installation? Was it an extra drive, or the drive where root was? If the latter, how did you copy the info back? Did you use rsync before you swap the drives? Like others have said, not enough information to start troubleshooting this, with what has been provided thus far. If you have your home directory separate your date is safe, you will be able to retrieve your data, before you start exploring options, as simple as reinstalling plasma itself and re enabling the sddm service, or as radical as re installing your system, but the latter is really of last resort, especially if your system is currently booting up. Let us know more, and we will go from there. Regards, Alex T.

On Feb 19, 2024, at 15:23, Yifan Zhu wrote:

On 2/19/24 12:15, pete wrote:

...

Hi Folks having problems here i have lost access to kde plasma on the main box i have installed a new drive and reinstalled i believe it is on my /home drive where thr issue lies is anyone else having issues .

i know this is scant information but i have no mail access on the machine that is having the issue wish there was someone local to me

Thanks folks Pete

We really need to see more information [0] before we can reasonably answer your question. Including, but not limited to

- versions of plasma software

- relevant journal logs

- whether you are on x11 or wayland

[0]: https://wiki.archlinux.org/title/General_guidelines#How_to_post

Cheers, Yifan

On Mon, 19 Feb 2024 12:23:07 -0800 Yifan Zhu wrote:

On 2/19/24 12:15, pete wrote:

...

Hi Folks having problems here i have lost access to kde plasma on the

main box

...

i have installed a new drive and reinstalled i believe it is on my /home drive where thr issue lies is anyone else having issues .

i know this is scant information but i have no mail access on the machine that is having the issue wish there was someone local to me

Thanks folks Pete

We really need to see more information [0] before we can reasonably answer your question. Including, but not limited to

- versions of plasma software

- relevant journal logs

- whether you are on x11 or wayland

[0]: https://wiki.archlinux.org/title/General_guidelines#How_to_post

Cheers, Yifan

Hi Right this is going to be done the hard way typed by hand xf86EnableIO: Failed to enable I/O ports 0000-03ff operation not permitted The XKEYBOARD keymap compiler (xkbcomp) reports warinig could not resolve keysym XF86CameraAccessEnable then repeated for XF86CameraAccessDisable and a whole herd of XF86 could not resloves . Plus i login into a tty then use starx when i loginto the terminal enter my username hit enter it sits there then username goes away if i then re-entre it then passes to password enter that it logs in But if i want to open another tty so use Alt-F2 it opens but i am then completely unable to return the the original tty is is closed gone this is on a brand new install i canned it all Fdisked the disks every was done fromk clean still the same Ideas . I love arch linux but it is causing me major issues rightr now if any one can suggest answers please Pete

On Tue, 20 Feb 2024 18:36:37 +0000 Andy Pieters wrote:

On Tue, 20 Feb 2024 at 16:43, pete wrote:

...

Right this is going to be done the hard way typed by hand

if both computers are on your LAN, I think it may be more beneficial to you to set up / use SSH

On both machines, check / install SSH: pacman -Q openssh || pacman -S openssh on the machine that is borked: systemctl status sshd || systemctl start sshd

now you should be able to SSH to your broken machine and copy files from it using scp

If you're concerned about security (as we all should be): * switch off the daemon when you're finished * do NOT set up port forwarding on your router to ssh port Yes i will see about getting that setup just as a way of ensuring i do not have hardware issues i am install Manjaro to test it right now but i have got to get Arch working

Pete

On 2/23/24 13:11, pete wrote:

if running plasma wayland the vlc Kaffeine Firefox and Discord all cause issues

That is the rub with wayland. Depending on what the apps use, you may run into issues that wayland doesn't support. Discord places quite a bit of demand on the graphics/video subsystem, as does FF depending on what you are viewing -- especially if you are running web-apps like discord within FF. I've had much better luck sticking to X11. On your install with the borked Plasma, since this is KDE, you can always delete the config file directory and then login again and have plasma recreate its config. However, this is made much more difficult due to the stoke of brilliance the KDE-team had to dispense with a traditional config directory and dump all files under $HOME/.config is a willy-nilly manner. You will need to carefully select the KDE config files to delete (or move to another location, e.g. cd ~/.config; md tmp; mv ..... tmp;) Your other traditional option for testing a borked KDE is to create a new user and then login as that user and see what KDE does on a freshly generated config. This can eliminate any version mismatches in config files, etc.. that may have crept in under you normal user. Either way, they are reasonable tests to conduct. KDE should be doing this, but you can rebuild the system config cache with: kbuildsyscoca5 --noincremental (short for: "kde build system config cache", --noincremental tells it to regenerate all cache files) (double check that kbuildsycoca5 is the correct number, KDE3 was kbuildsycoca, KDE4 was kbuildsycoca4, and early plasma was kbuildsycoca5, but I haven't used it in a couple of years) I suspect a fresh Arch install will work fine -- as it will start with a fresh config. -- David C. Rankin, J.D.,P.E.