Re: Salix Xfce 15.0alpha2
Posted: 18. Apr 2022, 20:24
I also do not have this problem.gapan wrote:I definitely don't have this. Maybe it's related to your keyboard settings? Anyone else?
I also do not have this problem.gapan wrote:I definitely don't have this. Maybe it's related to your keyboard settings? Anyone else?
My keyboard is dvorak (from the options given during installation) but in X I use us -variant dvp (programmer dvorak). This behaviour occurs with both - I tested it in a tty.
Code: Select all
mimosa[~]$ cat .bash_aliases
alias ls='ls --color=auto'
alias pine='alpine'
Yes, and it didn't workYes, ibka, that's what I have determined as well. I don't know why it happens on your systems but not on mine, but on yours, changes to /etc/HOSTNAME are picked up automatically. But it should go back to working again if you run:as I have suggested before. Have you tried that?Code: Select all
sudo hostname oldhostname
Code: Select all
sudo hostname oldhostname
Code: Select all
sudo hostname oldhostname
So we have excluded that. Before, with Slackware15, I thought it was probablysome modification I made ... but my Salix Alpha installation is untweaked.djemos wrote: ↑19. Apr 2022, 11:34 Hi, mimosa.
I set keyboard to dvorak and found the keys i had to press. They have changed for my keyboard. e.g x-> q , shift+z -> : , .->v, g->i
Then typed .g -> vi and type some strings then press one time esc key then shift+z->: and xa! and vi exited
No need to press esc twice.
It is not the keyboard, it is something else in your system.
Because i work with slackel and slackware current, i have faced a lot of problems when slackware went to elogint and wayland because of kde plasma. This caused a lot of problems. For example the problem with change hostname because of MIT-MAGIC-COOKIE-1. I took a look what happened in ubuntu if i change hostname. There the X clients work but because of the systemd. hostnamectl is used which is native in systemd while hostnamectl do not exist on slackware. There are used rules under /etc/polkit-1/ which cannot used in slackware because it is not a systemd, elogind is used.mimosa wrote: So we have excluded that. Before, with Slackware15, I thought it was probablysome modification I made ... but my Salix Alpha installation is untweaked.
Also with the same hardware, in Salix 14.2, I did not see this behaviour.
Code: Select all
mimosa[~]$ lowriter
Unspecified Application Error
lowriter open libreoffice writer and libreoffice writer start from menus also . Salix64-xfce-15.0 installed on vmware.mimosa wrote: ↑21. Apr 2022, 11:22 Libreoffice won't start, either from the menu or like this:A little box briefly appears (saying 'LibreOffice: Community') as if it were launching, but then it flicks out of existence.Code: Select all
mimosa[~]$ lowriter Unspecified Application Error