Search Results for 'startx'

[Moderator christophe]

Core has an X server pre-installed now?

Oops. Sorry, I got ahead of myself…
I should have said “before login.”

(My intent is to startx upon login, once I’ve set it up.)

To clarify what I mean: On previous antiX 19 core live instances, I could press enter at this point, and the login would come up. Now it isn’t.

• This reply was modified 3 years, 1 month ago by christophe. Reason: additional info for clarity

confirmed antiX frugaler, since 2019

[Member mikey777]

christophe wrote:

Incidentally, both display managers (LightDM & LXDM) give me the same GDBus errors (popup warning at start & then lxterminal needed to leave LXDE).

Thanks christophe – I have a few questions for you, so that I can learn from this, before I reinstall antixcore and avoid this problem in the future.

Do you get GDBus errors & need lxterminal to leave LXDE, even when screen-locker is disabled ?
Do you think one way of avoiding this mess is simply to avoid having a display manager, deleting lightdm & lightdm-gtk-greeter following the initial antiXcore install, and just do manual login following boot and use the startx command to access the desktop ?

By the way, how do I disable the screen-locker in antixcore (either GUI or terminal method) ?

• This reply was modified 3 years, 2 months ago by mikey777.

▪ 32-bit antix19.4-core+LXDE installed on :
- (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
▪ 64-bit antix21-base+LXDE installed on:
- (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
- (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

[Anonymous]

maybe #31725 is intended as “instruction, specific to this case, to get it working”.
I drafted a long post prior to reading that, and my post recommends a cmd_login line which matches that seen in default antiX 19 full.
Here, I’m prefacing the long post by mentioning that I am not contradicting the instruction provided in #31725 ~~ I’m just covering how the dots are connected to work in the as-shipped antiX full.
___________________________

The topic linked from post #1 discusses antix19core-LXDE —} lightDM + lxdm + (presumably) lxsession.
That line (in post #1 here) is suitable only for use with a full-blown DE (desktop environment, e.g. LXDE, Xfce, Mate) .

lightDM and SLiM serve only as “display manager” aka “login manager”.
— starts Xorg server
— checks user+password login credentials
— uses a PAM (kernel pluggable authentication module) mechanism to register a “seat”
(your tty, er console, input {–} output display hardware marshalled by xserver)
— invokes the “session manager of choice” component… and then it just waits, serving as a idle wrapper
(idle until logout/login is requested, or exit/shutdown)

Upon installation of any display manager package, the DM is registered with rc.d to be automatically started for runlevels 2 and 5.
If, during installation, another DM is found already present on the system, you are asked to choose which of the DMs will be enabled.
^—v
During a session, if you logout (or you kill the DM process, or it crashes) the rc.d will automatically*** restart the DM.

*** a sysadmin is free to install multiple DMs and manually change which one (or none) is started for each runlevel.

The “startx” command is supposed to be (provide) a convenience… but, as an abstraction, it muddies the water.
Users are resigned to not knowing / caring which display manager and auth mechanism and session manager components will be invoked in order to create their “desktop session”.

We probably cannot put much weight in the terms “standard” vs NON-standard”.
— some distros do not use, nor provide, a “startx” command
— some distros are configured to only start a DM when entering runlevel 5
— some distros replace rc.d with systemd
— some distros ship only one DesktopEnvironment or WM
— the sessionmanager component of a given DesktopEnvironment may demand use of its own WM
____________________________________________

login_cmd setsid /usr/local/bin/desktop-session %session
https://gitlab.com/antiX-Linux/Build-iso/blob/master/Themes/full/misc/slim.conf

This SLiM login_cmd line (as seen in antiX full) calls a “session manager” utility named desktop-session which, in turn,
invokes whichever “session” has been chosen via F1, e.g. “rox-icewm” (and passed as a commandline argument).
Additionally, and in place of (instead of) sourcing ~/.Xsession, the utility sources both an “all cases” .startup file
and (depending on which WM has been requested for this session) ~/.fluxbox/startup or ~/icewm/startup or…

rox desktop manager (and spacefm -d) are windowmanager agnostic.
Further, either of them can be manually invoked (and killed), at will during the course of a “desktop session”.

When the antiX “session manager” utility (the desktop-session command) parses the commandline args for a given session request, it selectively starts the requested “desktop manager” (or none) along with the requested “window manager”… and each of those can be (and typically are) configured to autostart additional processes. Along the way, ~/.xinitrc is never sourced. (IIRC, by default, on an antiX full system that file isn’t even present)

____________________________________________

re: “startx [..] error message & restarting”

https://www.antixforum.com/forums/topic/antix-19-1-based-on-debian-sid-available/

It seems that if you use startx, you need to also install xserver-xorg-legacy, but it is not needed if you use slim.
If user does chooses slim login manager, you MUST edit /etc/slim.conf as shown above otherwise you get the error reported by Koo.

Hey guys,

I’ve been having fun building up from antiX Core, running frugal, using jwm. I’ve been using startx to start x-windows, and everything has worked well. But I wanted to ADD fluxbox to this setup. I tried to add slim & fluxbox. But slim (which I’ve never used except as part of the base or full antiX setup) wouldn’t load my xsession.

I searched the forum, and the only thing I came up with didn’t help (same result of slim giving the error message & restarting, etc). The help was from here: https://www.antixforum.com/forums/topic/desktop-manager-slim-rejects-my-username-and-password-how-do-i-fix-this/

I copied the line to my slim.conf, but no change: it still gave the error message & respawned. I added (& commented-out the old one):
login_cmd exec /bin/bash -login /etc/X11/Xsession %session <strong>(uncomment)</strong>

Did I misunderstand that this would enable login when booting from a “non-standard-antiX” setup? Do I need to add something else?

Anyway, I used Ctrl+Alt+F2 to login through the console, ran startx, and I got my (brand-new) fluxbox session. (And here I am asking for help.)

Any pointers to getting slim working this way? Or should I use a different display mgr?

my slim.conf:

• This topic was modified 3 years, 3 months ago by christophe.

Attachments:

1. slim.txt

confirmed antiX frugaler, since 2019

[Member Sliver X]

This should not be the case. Both, base and full version, should provide the gui-installer.Look for antix-installer.

Xorg itself never loads during the boot process. I didn’t think to try startx manually, though? FYI, if it matters, I made both install sticks with the built in Live USB creation tool in antiX 17.4.1

I have installed to a (modified) chromebook, using GPT partitioning & UEFI, maybe try that(?).

I still use MBR partitioning on all my disks. Will see if GTP makes a difference.

I can say that the antiX installers do not function on my i5-gen10 Intel pc (they work predictably on my older units). @stevo on MX has built a new MX spin that seems to function well. For now, antiX is uninstallable (by me, a mere mortal) on my new i5-gen10 gear.

I run a Ryzen 2600, so also a fairly recent CPU/chipset. I wonder if that has anything to do with it?

[Member ex_Koo]

19.1-64-bit-runit-core reinstalled (x220) all intel

On installing
Ask do you want to install packagers (before you even setup network this is ok with lan but useless with wifi)
Are you running antix-net ? no this is the core version why is it asking even , core installs grub and so on anyway.
Install grub for me it was a No wanted a system installed grub as this machine has more then one system can do update-grub from primary anyway.

Bye the way I like this installer.

On booting
I installed slim fluxbox xorg xserver-xorg-video-intel git vim ranger this time round.
Edited the slim.conf as stated above if I change user to anticap wont load slim at all just a blank screen, then changed to koo will load slim now but same as yesterday “failed to execute login command”

Now changing slim.conf line to remove comment to (login_cmd setsid /usr/local/bin/desktop-session %session) and dropping from slim to tty logged in as koo sudo startx takes me to fluxbox. Happy KoO

If I try to login from slim won’t work at all even tiring root root nothing happens as koo “failed to execute login command” (No xserver-xorg-legacy installed)

“I’ll be back”

[Forum Admin anticapitalista]

It seems that if you use startx, you need to also install xserver-xorg-legacy, but it is not needed if you use slim.
If user does chooses slim login manager, you MUST edit /etc/slim.conf as shown above otherwise you get the error reported by Koo.

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

antiX with runit - leaner and meaner.

[Anonymous]

Great holiday present Anti,

I downloaded the 19.1-64-bit-runit-core and assimilated my D830 latitude
with an unstable build up… have a few issues to get but it’s up and
running the new enlightenment DE. I’ll post a shot in screenshots.
I’m using startx to launch instead of slim or lightdm. edit … I do have the
xserver-xorg-legacy installed haven’t decided if want a display manager
yet. runit seems real snappy even on this with a old spinning hdd drive.

One thing I had to do is remove ceni and use wicd to get wifi …. ceni wouldn’t
turn on the card to scan. In wicd once I switched on wifi and then typed the password
it connected just fine and worked.

[Member madibi]

no way
all my tries are frustrated.
1. USB key Antix 19
1.1 normal install (+ a lot of combinations of F2+F3+F4): as I wrote you before
1.2 failsafe mode: simply it stops working when the screen is dark

2. USB key Antix 17
2.1 normal install: as I wrote you before
2.2 failsafe mode: the process arrive at a moment with the cli I am asked to provide userid and pw. After I do the login I try the “startx” command and I have no success (I receive a lot of messages of error)

I think I’ll resign
I ask me why with the Ubuntu derivates – that I dont like so much because they are so “heavy” I don’ have any prob.

[Anonymous]

Removing tlp did not do anything.

It seems that there was some sort of installation error and the session managers (or what the proper name is) had been installed erroneously, missing some icons, etc.

I installed lxde and it works fine! All the icons are present and clickable. Problem is: it did not solved the original problem, after a reboot the screen remains black and I must login from the console at first and type “startx” to be able to start the lxde environment.

I tried apt-get remove icewm, then apt-get install icewm, but the problem with the missing icons did not go away. On the other hand, lxde uses a different set of icons and whatnot and seems all right once started.

How could I reinstall the original antiX Session managers?

Thanks,

Pumukli

[Anonymous]

Thanks for the tip. It worked somewhat.
By typing “startx /usr/local/bin/desktop-session rox-icewm” rox-icewm started. The screen what I see is far from perfect though:

Now I see I think Conky on the right side of the screen. (I’m referring to the system resources monitor application, not sure about the name though.)

I got a gray background and an error message. The message was shown in my native (localization?) language, I try to translate it back to English here: “Error in loading the background picture. It can’t be identified the /usr/share/wallpaper/lines.png picture file format. Background has been removed.”

There are two “blank” icons on the upper left corner of the screen. They are “Files” and “Help”. The icons are blank: they don’t have pictures just a red X in the middle on white background. They are not functioning either. When clicked they say: “Failed to execute child process /usr/share/applications/antix/editor.desktop” Maybe it is a privileges conflict (regular user vs. root or something like that.)

The taskbar also looks miserable: basically a black line, icon of favourite applications is missing. If clicked the left-down corner a menu pops up, Control centre can be selected and brings up a non-functioning window with blank icons…

You suggested that I’d try to remove tlp. Where from and how should I remove it? Editing which file?

Thanks in advance,

Pumukli

[Forum Admin anticapitalista]

Instead of startx, as user type for default (I assume you are using antiX-base and IceWM)

startx /usr/local/bin/desktop-session rox-icewm

Then once in X, try removing tlp and see if it boots to desktop correctly.

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

antiX with runit - leaner and meaner.

Dear All,

I’m a fairly new Linux user but used Antix 16.1 for a few years on a thin client. Yesterday I installed Antix 19 from a base CD to my old IBM Thinkpad R50e laptop. Everything went fine (repartitioning the drive, distinct root and home partitions, set time, TZ, default user, root password, etc. and the installer finished just fine.
After reboot though my computer just hangs when the X system is expected to start. It never gets through this stage.
Clicking Ctrl-Alt-F1 brings up the screen of the boot process. Everything seems fine until the “Starting slim: slim” line, then the next two lines are questionable. They say:

/usr/sbin/tlp: 50:/usr/sbin/tlp: read_defaults: not found
/usr/sbin/tlp: 51:/usr/sbin/tlp: check_tlp_enabled: not found

Then comes:

Welcome to antiX. Powered by Debian.
R50E-wireless login:

If I log in either a user or root it is fine. I can even manually start X (startx) but it behaves strangely. Can’t use e.g IceWM, most icons are missing (represented by a blank icon with “X” written on them, etc.

What should I do?

The system boots fine from the CD, everything seemed to be working from the LiveCD, so I expected the same from a hard drive install too.

Tips? Tricks? Workarounds?

Thanks in advance,

Pumukli

antiX 19 core + Mate DE:

Very easy and fun project. Here’s how I did it (I know many people would do it differently).

1. I started with a frugal antiX 19 setup. I set up 2 GB static root persistence, but used only 1 GB (I believe). Set up wifi & updated/upgraded current software.

2. Install x-windows sudo apt install xorg xserver-xorg xserver-xorg-video-intel
(My computer uses the intel xserver, but install another if yours is different. Note: I tried first with just xorg & xserver-xorg packages, but starting X failed. So I went back & installed the intel xserver.)

3. I fired up cli-aptiX sudo cli-aptiX
and looked at the recommended GUI packages. There’s a Mate meta-package that installs it all for you. Go ahead; select & install.

4. Once the installing of software is finished, type startx
and you get the (basic) Mate desktop environment. No troubles; very straight-forward.

I know many people would install a display manager. I didn’t, but that’s how I want it.

Also, all your apps still need to be installed, like web browser, etc.

It runs nicely; uses about 160 MB RAM on 32-bit, upon startup (according to conky — which (if you want it) you’ll have to install additionally).

confirmed antiX frugaler, since 2019

[Member anewangelfades]

caprea wrote:

anewangelfades wrote:

$ xrandr -s 1024×600
Size 1024×600 not found in available modes

If a particular screen resolution is not found in available modes by xrandr,
there is a possibility to add a new modeline. It’s described in comment #51 in the bug-report you linked to or on this side
http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=https%3A%2F%2Faxebase.net%2Fblog%2F2011%2F07%2F27%2Fhinzufuegen-einer-aufloesung-ueber-cvt-und-xrandr%2F

or on this side under resolution http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=https%3A%2F%2Fwiki.ubuntuusers.de%2FRandR%2F%23Statische-Konfiguration-ohne-xorg-conf
You have to know the technical data for the screen.
I don’t have any experience with it, so I can’t promise that it will work and really help you, but maybe it’s worth a try.

You probably have already realized that an older antiX version might have less problems.

Great idea, thanks!
I installed the Geode drivers, and used an old xorg.conf I saved from an working xubuntu installation, reported below:

Section "Module"
    Load  "ztv"
EndSection
Section "Device"
    Identifier	"card0"
    Driver	"geode"
    BusID	"PCI:0:1:1"
    Option	"PanelMode" "33450 800 840 968 1056 480 490 492 525"
EndSection
Section "Monitor"
    Identifier	"monitor0"
    Modeline  "1024x768" 64.56 1024 1056 1296 1328 768 783 791 807 -hsync +vsync
    Modeline  "1024x600" 48.96 1024 1064 1168 1312 600 601 604 622 -hsync +vsync
    Modeline   "800x480" 33.45  800  840  968 1056 480 490 492 525 -hsync +vsync
    Option	"dpms"
EndSection
Section "Screen"
    Identifier	"Default Screen"
    Monitor	"monitor0"
    Device	"card0"
    DefaultDepth 24
    Subsection "Display"
        Depth 24
        Modes "1024x600" "1024x768" "800x480"
    EndSubsection        
EndSection

Next time I booted up, I got a console. Logged in, typed startx, but I got an error.
The file /var/log/Xorg.0.log said the following:

[    55.164]    Module class: X.Org Video Driver
[    55.164]    ABI class: X.Org Video Driver, version 24.0
[    55.164] (II) z4l driver for Video4Linux
[    55.164] (II) GEODE: Driver for AMD Geode Chipsets: Geode LX, Geode GX
[    55.185] (WW) Falling back to old probe method for z4l
[    55.187] AmdPciProbe: Probing for supported devices!
[    55.188] (II) Loading sub module "vgahw"
[    55.188] (II) LoadModule: "vgahw"
[    55.194] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[    55.221] (II) Module vgahw: vendor="X.Org Foundation"
[    55.221]    compiled for 1.20.4, module version = 0.1.0
[    55.221]    ABI class: X.Org Video Driver, version 24.0
[    55.222] (EE)
Fatal server error:
[    55.222] (EE) Unable to open /dev/cpu/0/msr: No such file or directory
[    55.222] (EE)
[    55.223] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    55.223] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional $
[    55.223] (EE)
[    55.339] (EE) Server terminated with error (1). Closing log file

So I typed sudo modprobe msr and then startx again, and it worked!

Now inxi -Fxz -r gives the following output:

System:
  Host: EC-800 Kernel: 5.2.15-antix.1-486-smp i586 bits: 32 compiler: gcc v: 8.3.0 
  Desktop: IceWM 1.5.5+git20190610 
  Distro: antiX-19_386-full Marielle Franco 16 October 2019 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: Hercules product: EC-800 v: 1.0 serial: <filter> 
  Mobo: TECO and Machinery model: TR2350 v: Rev 1.33 serial: <filter> BIOS: Insyde 
  v: 4.00.01 Rev. 1.00.003 date: Built: 08/18/2005 
Battery:
  ID-1: BATT charge: 20.0 Wh condition: 20.9/29.8 Wh (70%) model: YOKU ENERGY BT-6005 
  status: Unknown 
CPU:
  Topology: Single Core model: Geode Integrated by AMD PCS bits: 32 type: UP 
  arch: Geode rev: 2 L2 cache: 128 KiB 
  flags: N/A bogomips: 996 
  Speed: 498 MHz min/max: N/A Core speed (MHz): 1: 498 
Graphics:
  Message: No Device data found. 
  Display: server: X.Org 1.20.4 driver: geode resolution: 1024x600~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:
  Device-1: AMD CS5536 [Geode companion] Audio driver: snd_cs5535audio v: kernel 
  bus ID: 00:0f.3 
  Sound Server: ALSA v: k5.2.15-antix.1-486-smp 
Network:
  Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too 
  v: 0.9.28 port: df00 bus ID: 00:0d.0 
  IF: eth0 state: down mac: <filter> 
  IF-ID-1: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 18.66 GiB used: 4.41 GiB (23.6%) 
  ID-1: /dev/sda vendor: Samsung model: HS020GB size: 18.66 GiB 
Partition:
  ID-1: / size: 16.24 GiB used: 4.41 GiB (27.1%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://it.mxrepo.com/antix/buster buster main nonfree
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.it.debian.org/debian/ buster-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.it.debian.org/debian/ buster main contrib non-free
  2: deb http://security.debian.org/ buster/updates main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/onion.list 
  Active apt repos in: /etc/apt/sources.list.d/palemoon.list 
  1: deb http://download.opensuse.org/repositories/home:/stevenpusser/xUbuntu_16.04/ /
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 91 Uptime: 19m Memory: 973.8 MiB used: 186.5 MiB (19.1%) Init: SysVinit 
  runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 

There are two problems anyway:

1) I always have to do sudo modprobe msr and then startx at startup: is there any way to fix it?
2) If I change desktop, e.g. fluxbox, or jwm, everything freezes. Why?!? Also if I use Ctrl+Alt+F2 (or F3, or F8, or any other F*). I cannot understand the reason for this.

Any ideas?

Thank you again!