Search Results for 'startx'

[Member stevesr0]

(ADDED HERE TO HIGHLIGHT POSSIBLE CAUSE: conflict between xserver-xorg-core and xserver-xorg-video-modesetting? see my findings below for my Sid install.)

Hi all,

Maybe related problem, maybe not.

I am running a “minimal” install of Sid to which I have added X. All was running fine until after I did an apt update and full-upgrade tonight. Twenty-eight packages downloaded. One (libcodec2-1.0 (1.0.1-3) was labeled as an “automatic” install, the rest upgrades. The twenty-seven package upgrades included 11 libqt5 files, 9 libav files (including ffmpeg), 2 X files (xserver-xorg-core and xserver-common), 4 grub files(grub2-common, grub-common, grub-pc and grub-pc-bin) and libcrypt.

I boot into the command line and log in without problems. However, after launching x via startx, there is no response to the mouse or the trackpad and trying the “magic” keys does nothing to shut down the machine.

I will check for issues reported with the xserver update or other files in my 28 and repost if I discover a solution. Since others are reporting similar issues with recent updates, perhaps there is a common package that we share. If it would be helpful, the upgrades for the libav files are from 7.4.4.1-2 to 7.4.4.1-2+b1, the libqt5 files from 5.15.2+dfsg-13 to 5.15.2+dfsg-14, the grub files from 2.04-20 to 2.06-1, the xserver files from 2:1.20.13-2 to 2:1.20.13-2.0nosystemd1, libcrypt20 from 1.9.4-3+b1 to 1.9.4.4. Note that after installing libcodec2-1.0, libcodec2-0.9 was marked for autoremove.

Looking through the package dependencies and conflicts, I see that xserver-xorg-core, version 2:1.20.13-2.0nosystemd1, is listed as conflicting with the “provided xserver-xorg-video-modesetting”. This package is a virtual package.

If others confirm this, then it indicates that might be the cause of the problem — although it sounds a little crazy and (being a newbie) I am probably misinterpreting it.

Searching, I found older complaints of conflicts between the xserver-xorg-video-modesetting and xserver-xorg-core. I understand that currently this is actually provided by xserver-xorg-core. I note that in my antiX-19 system, the same conflict is reported, even though I am not having any problem with running x on this machine (which is what I am using to type this).

Well, if this is the problem for others, then I hope my report helps.

whether this is really the cause or not, I would appreciate advice on how to fix.

stevesr0

P.S. probably irrelevant, but I note that the libqt5 packages are a little ahead of the latest kernel available on Sid (5.15.2 vs 5.15.0.2). Is it possible that some of these require a non released 5.15.2 kernel?

• This reply was modified 1 year, 5 months ago by stevesr0.

[Member stevesr0]

Hi all, Dave pointed me towards two files that were causing the problems (99-update-loginmanager and 99-update-menu) and after removing them, apt is updating fine without error messages.

These files are apparently unnecessary because I don’t use a login manager, just startx.

I also don’t have desktop-session-antix, or desktop-menu-antix; only apt-antix and desktop-defaults-net-antix. I am not sure what I am missing out on, because my Openbox-based graphic system seems to work ok.

stevesr0

I managed to install driver for igpu nvidia 320m, but things are worse than before. no hardware acceleration, no brightness control (No controller found). I also noticed i get a little modprobe nvidia error on startx. plz help, thank you

• This topic was modified 1 year, 6 months ago by blackwood.

[Anonymous]

hi Daddy Libre,

if startx works as the root user then
edit /etc/X11/Xwrapper.config as root.

sudo nano /etc/X11/Xwrapper.config

then add this at the end of it and save so the regular user can launch X.

needs_root_rights=yes

you might need … xserver-xorg-video-intel package if you have an intel video chip also.

[Moderator christophe]

Hi NorbyDroid,

You must have missed this tips & tricks tutorial by anticapitalista:

https://www.antixforum.com/forums/topic/startx-on-antix-base-and-full/

It seems to be exactly what you are looking for.

confirmed antiX frugaler, since 2019

[Member ex_Koo]

Yes you can login from tty screen or the cli instead as you call it. But i’m not sure if your ready for tty screen or have the experience just yet.

This what I do as do not like GUI login managers.

1. remove slim or any other login managers.
2. make a .xintirc file in your home directory add the desktop you wish to login to for fluxbox you would add (exec fluxbox) without brackets..
Or you could install tbsm which would get you all the antiX desktops so to say and it will list them by number.

3. you have two choices here (auto startx or not) edit .profile file add these lines. <<<<< the below lines will auto startx after you have logged in. or you can manaully type startx don’t add the lines if so.
if [ -z “${DISPLAY}” ] && [ “${XDG_VTNR}” -eq 1 ]; then
exec startx
fi

This may (or may not) seem a bit odd, but here it goes.

I downloaded and installed antiX Linux full because I am not too good at the ‘antiX core’ cli mode. Is there a way, once I have installed and setup all the packages I am interested in, to have the system boot into cli instead of the desktop?

If I am not mistaken, startx will get me back to the desktop. Correct me if I am wrong about that.

Oh, is this odd, or does this make any sense at all?

Thank you.

[Member Daddy Libre]

Bash: startx: command not found

I’ve rebooted and all of the installed apps are gone, despite the persistence.

Reinstalled xorg and icewm I’ve run startx that report fatal error: AddScreen/Screening failed for driver 0

[Anonymous]

Hi Daddy Libre,

Does typing startx load icewm?

This is just a quick starter for those who prefer to avoid dbus,dbus-x11 and elogind.
Tested in Virtualbox. English only.

Stage 1: Installation

1. Download antiX-21 net (runit or sysVinit)
2. Boot the iso and at the prompt login as root (password=root) and type cli-installer
3. Follow the instructions.
4. Make sure you answer Yes to ‘Is this a net install?’
5. When asked if you want to install elogind dbus etc, choose No (default)
6. Continue until antiX-21-net has been installed – reboot to installed version.

Stage 2: Getting a basic ‘desktop’.

1. login as user then either use sudo or su to root. I prefer the latter.
2. Update packages apt update && apt dist-upgrade
3. Install X apt install xorg
4. If you are going to use startx instead of a login manager, you need to apt install xserver-xorg-legacy
5. Install your window manager of choice eg apt install openbox
6. exit root (if you were using su) and as user type startx
7. You now have a very minimal openbox ‘desktop’

Stage 3: Adding (gui) apps

This is the difficult part as far as avoiding dbus, dbus-x11 and elogind is concerned.

Suggestions below – feel free to add your own.

rxvt-unicode (terminal)
leafpad (text editor)
rox-filer or zzzFM
mpv (video/audio)
smtube (it works without dbus etc!)
ytfzf (youtube videos)
libreoffice-writer
libreoffice-impress
lxappearance (lazy way to customise looks)
mupdf (pdf reader)
links2 (browser)
dillo (browser)

Note: All the big browsers will install dbus and dbus-x11

Stage 4: Beautify

Purely subjective, but I installed

adwaita-icon-theme-antix
arc-evopro2-theme-antix
dmz-cursor-theme
papirus-mini-antix

Login Managers:

If you want a login screen, you have these options

lxdm
xdm
wdm

For slimski or slim, you will need to install seatd first

apt install seatd

You might need to tinker some config files, but it’s good fun.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member stevesr0]

Hi all,

(Apologies if this is the wrong thread to post in. Moderator please move if that is the case.)

I tried out Antix 21 (full) version as a live usb, a few hours ago.

Looked at several repos which only had a runit directory before finding one (Los Angeles) which also listed sysvinit.

Built with the Antix19 live USB maker.

This machine is a relatively recent vintage gaming laptop with an 8th generation i5 processor and integrated intel and separate nvidia GPUs.

First try ended at a command prompt. Used demo/demo to log in and then attempted startx with failure (didn’t think to try slimski).
Second try, used “failsafe” – which got me to a graphic desktop without working mouse (internal or usb).
Third try, noticed that there (now?) seemed to be an option to load a 1 November version as well as a 31 October version. Selected 1 November and without setting failsafe got to a graphic desktop (but the resolution was not different than the prior “failsafe” try). A usb mouse worked and I explored the packages somewhat in synaptic.

(I was looking to see if Pipewire was included; no, it wasn’t listed.)

I will wait awhile before further testing. Happy to try things out if people have suggestions.

stevesr0

[Member ex_Koo]

( @Koo, why is your xprofile getting executed and mine is not?)
It is called from my xinitrc file as is i3 executed. I do not like nor use login managers that why I use xinitrc. And if I have more then one Linux system install I use tbsm which I use to login from the tty screen.

tbsm

#!/bin/sh

# this file is run when calling startx

# default arch init scripts
if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/?*.sh; do
        [ -x "$f" ] && . "$f"
    done
fi

# user init scripts and settings
[ -r /etc/X11/xinit/.Xmodmap ] && xmodmap /etc/X11/xinit/.Xmodmap
[ -r ~/.Xmodmap ] && xmodmap ~/.Xmodmap
[ -r ~/.Xresources ] && xrdb -merge ~/.Xresources
[ -r ~/.xprofile ] && . ~/.xprofile

# launch the session, commands below this line will be ignored
exec i3

[Member blur13]

Hi Xecure,

Still having some problems. Starting up the usual way leaves me with a blank screen and a humming CPU. Checking htop in the console reveals “desktop-session” going haywire, its constantly respawning. I tried deleting it, ie the file itself to stop it from doing that. Obviously not a a great idea so I restored “desktop-session” by copying the file from another antiX install and chmod 755 and placing it in /usr/local/bin, where I think it belongs. It’s still doing the respawning, here is the log file:

desktop-session: Window Manager not found to be running after 20 checks
desktop-session: Window Manager not found to be running after 20 checks
desktop-session: Currently the desktop environment will not start 😛
desktop-session: Currently the desktop environment will not start 😛
desktop-session: started Sun 17 Oct 2021 07:32:21 AM CEST start_time: 125.85
desktop-session: Give Up Time:12609
desktop-session: Give Up Time:12611
desktop-session: pid: 18409
desktop-session: logging to: /home/$USER/.desktop-session/log
desktop-session: Raw code passed ”
desktop-session: running on_exit code
desktop-session: running on_exit code
desktop-session: running on_exit code
desktop-session: running on_exit code
desktop-session: running on_exit code

“desktop-session: running on_exit code” repeats for a couple of pages

Is there some default “desktop-session” file in etc/skel I can chmod and put in the $PATH?

I’m now currently booting into run level 3, and when I use “startx” it starts the display server and runs icewm. I’ve restored the default settings for icewm, as per your instructions. Before I restored the default settings, starting icewm this way would result in the same error that started this whole thing. So the icewm settings are probably to blame.

At this point I’m close to giving up and just reinstalling a fresh antiX. But then I think of all the customization I’ve done, compiled programs, etc, and shudder. Maybe I could use “startx”, run my startup script manually in the terminal, set up a desktop background with “feh”, turn on conky, and then never reboot, always suspend 🙂

[Member Xecure]

Hi.

Hazardus wrote:

I can load into console using ctr+alt+6 and type “startx” to get a session going… but it’s completely stock setting with a black background (and any time I try to change the desktop manager it sends me back to console).

root account doesn’t have any desktop-session support.

Hazardus wrote:

Something went wrong.

If we can get a bit more info on what you were doing… Were you editing the window manager files?

You can restore the /etc/X11/xorg.conf.in file by reinstalling desktop-defaults-core-antix. Go back to the terminal and reinstall it with
sudo apt install --reinstall desktop-defaults-core-antix
Kill X and restart the slim service
sudo service slim stop
sudo service slim start

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

I’m experimenting with some VM stuff and made the mistake of editing my /etc/X11/xorg.conf.in thinking I could just change it back if something went wrong.

Something went wrong.

Now I can’t load into antiX because the desktop manager is not loading. I see a lot of mentions of the wallpaper file not being available for IceWM (I use Rox-IceWM), but it’s there… I can load into console using ctr+alt+6 and type “startx” to get a session going… but it’s completely stock setting with a black background (and any time I try to change the desktop manager it sends me back to console).

FWIW it loads a very oversized version of auditorio-de-tenerife2.jpg wallpaper with nothing else on it (I use[d] lines.jpg). No cursor no icons nada until I switch to console and start the session like that.

Any quick fix? (+ I have images of my antiX partitions from before setting up for VMs.. I can restore individual files/directories from there but would rather not flash the whole partition.)

• This topic was modified 1 year, 7 months ago by Hazardus.