Back to Netrunner | Back to Blue Systems

bugs or inconveniences thread

On a fresh install, somehow twm crept into the system: :dodgy:

after an octopi system upgade, /etc/X11/xinit/xinitrc
contained twm = tabbed X window manager , which is a nogoodnik software.

uninstall twm via octopi and things are back to normal. :rolleyes:

twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login
comment or delete the above lines and put in this line instead for KDE auto-start :

exec startkde

The xorg-twm package has always been installed on Manjaro by default as a backup.
The lines you listed are supposed to be there so that twm is started by default when you use xinit/startx from the console.
Otherwise, what would be the point of including twm as a backup when Plasma5/kwin or your DM doesn’t want to load and you need to fix something.

Starting the the correct desktop is the job of the DM, If SDDM didn’t start Plasma 5 as it was supposed to, then there is something else wrong on your system.

it happened twice, so I believe it is reproducible. will check that SDDM stuff also.

SDDM is used to start the plasma desktop, it’s not using /etc/X11/xinit/xinitrc.
All the machines here running NRR logged into the Plasma desktop just fine via SDDM after every update.
I’m not sure why your having this as an issue, unless you have a ~/.xinitrc file in your home directory for some reason.

after sys upgrade , startkde was no longer autostarted. startx would allow startkde but with bloody twm in place.

separate issue: :idea:

you may need to install all “blue*” packages with octopi before you may be able to connect to some BT devices. maybe firmware or whastever is missing…


but finally my BT speaker works as usual now :smiley: :smiley: :slight_smile: :slight_smile: :slight_smile: :rolleyes: :rolleyes: :wink: :shy:

Once again, xinitrc is irrelevant if you are using a display manager (SDDM).
Startx does use xinitrc however, in-which twm would be the desired outcome on a Manjaro based system.
Twm is there so that the user still has a wm to use in case Plasma/kwin is broken.
I think you may have done something to your system that changed the way in which autologin is supposed to work.

I’m glad to hear you got your bluetooth speakers working.
However, all the required packages for bluedevil and bluez are installed by default.
If a users hardware requires the bluez-firmware package, then they’ll need to install that themselves.
Installing bluez-firmware by default causes issues with other Broadcom chips.

tried out KaOS 2018 release as a pastime.

after 2 hours I got fed up with crashes and freezes.

NRR usually is quite stable (except recently, but an upgrade fixed everything).