Search Results for 'startx'

[Forum Admin Dave]

I think this is likely because you are running via startx / ~/.xinitrc rather than through desktop-session (so the desktop-session command would not work). Will have to look into it to see if this can be made possible. That way the exit dialog can be independent of desktop-session if desktop-session is not running (no pid recorded in ~/.desktop-session). Seeing how you have desktop-session installed: If you run startx like
startx /usr/local/bin/desktop-session icewm
Does the session start?
Does the logout button work?

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member seaken64]

anticapitalista wrote:

Any user starting from net or core wanting to login via startx, you MUST install xserver-xorg-legacy AND edit the /etc/X11/Xwrapper file to include these lines:

allowed_users = console
needs_root_rights = yes

anti, I installed xserver-xorg-legacy. I found a file named /etc/X11/Xwrapper.config. This is different than your instructions above. I added the line needs_root_rights=yes. The other command was already there.

But I haven’t seen a difference in using startx and my logout menu is still not working right. I copied the preferences and menu files from /etc/skel and that did change the menu and now the Logout button pops up the familiar 6 panel logout menu. Logout does nothing. Reboot and Shutdown work. Restart works.

Any ideas?

Seaken64

[Moderator BobC]

Sounds like an adventure 🙂

I’ve done setups of IceWM on a lot of distros, but antiX already had it. Yes, I like the startx way, too. Super lean from a memory standpoint. And you could have it run that at login or maybe optionally via a dialog box question.

I’ve done the menus generated a number of different ways. There is the new IceWM program someone mentioned above. There are also multiple menu builders that work off the application .desktop files that have the option of generating an IceWM format menu. antiX is unique because it’s menu builder also generates menus for Fluxbox and JWM as well.

I think the basic idea is to create your main menu by hand, and then generate another menu or menus that branch off from it which are then called by the main menu. I think good clues for antiX’s way of building a menu will be found in desktop-menu

PS: I was typing while Dave posted above. He is the one that knows for sure.

• This reply was modified 2 years, 4 months ago by BobC.

[Member seaken64]

anticapitalista wrote:

Any user starting from net or core wanting to login via startx, you MUST install xserver-xorg-legacy AND edit the /etc/X11/Xwrapper file to include these lines:

allowed_users = console
needs_root_rights = yes

I had read that. I will go ahead and do that. I had assumed that since I was successful in using startx that I was good to go. But I will follow your instructions here and install xserver-xorg-legacy and edit the Xwrapper file.

Thanks

[Forum Admin anticapitalista]

Any user starting from net or core wanting to login via startx, you MUST install xserver-xorg-legacy AND edit the /etc/X11/Xwrapper file to include these lines:

allowed_users = console
needs_root_rights = yes

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

antiX with runit - leaner and meaner.

[Member seaken64]

Adding IceWM to antiX-19.3 CORE

In my continuing effort to learn more about how antiX works behind the scenes I am attempting to add the IceWM Window Manager to antiX CORE. I have started with a successful installation of antiX-19.3 CORE using the cli-installer. After the installation I logged in as root and ran the update and dist-upgrade routines. I tested the system from the console and everything is working fine in text mode only.

My next goal is to add the X window system and then add IceWM as my “GUI”. I do not want to add a Desktop Environment system such as Xfce or Mate. My goal is to learn more about how to setup the IceWM Window Manager to mimic what antiX BASE already has setup by default.

It would be easier to just install antiX BASE. But this is a learning exercise. I am hoping to learn how to setup IceWM from scratch, but using the antiX framework that has already been created for the BASE system. I have added IceWM to my regular Debian installs and I am always disappointed in how it looks and how the menus are setup. I like the antiX implementation of IceWM and I want to learn how it is done.

I have watched all of the videos from Dolphin_Oracle on adding an X windows system to antiX CORE. Unfortunately he does not specifically mention how to add IceWM, but instead shows how to add Xfce and KDE. There are quite a few threads on the forum about adding a WM or DE to the antiX CORE system. I have read them all and have tried to follow along and imitate the steps each user has taken to achieve their new “spin” on antiX. Brian Masnick also had a nice blog entry on how to setup Xfce on CORE using the SID repos. I have attempted to follow his instructions but I am not interested in Xfce. I want IceWM.

I am still working through some forum message threads and they have been helpful as I learn. But I am still hitting some roadblocks. Here is what I have accomplished so far and what I am missing.

I modified D_O’s apt install command string to try to install IceWM instead of Xfce. I do not want a Desktop Manager/Login Manager like Slim or LightDM, etc. I would like to have it setup to use “startx” to start up IceWM. Here’s is my first attempt at installing the missing packages:

apt-get install xserver-xorg x11-xserver-utils xfonts-base x11-utils icewm icewm-common

I rebooted (as root) and tried “startx” but it didn’t work. I added the xorg package and tried again. After reboot (as root) I tried “startx” again, it worked! I was now in IceWM. The menu was sparse and there were no Applications. But there was a “Terminal” entry. I clicked on that and it launched the xterm. I was able to launch mc, antiX-cli-cc, and cli-aptiX.

So, at this point I have a plain vanilla IceWM and no applications or anything resembling the “antiX” setup. So I started looking around to see if I could add the antiX stuff. I used cli-aptiX and added the following packages:

icewm-base-themes-antix icewm-icons-papirus-antix icewmcc rox-filer roxterm-common roxterm-gtk2 spacefm spacefm-common smbclient cifs-utils connectshares-antix control-centre-antix menu-icewm-antix menu-manager-antix xdg-utils desktop-session-antix desktop-defaults-base-antix

I have logged in as my user and I have the same plain IceWM as I did in root. I was able to change the “theme”. But the menu has not changed. There are no Applications. And I created a “startup” file in ~/.icewm/startup but it is not being used. I made an entry to change the default resolution using xrandr but it does not work. I do this on all of my antiX systems and it always works. But it appears that this IceWM is not reading the ~/.icewm/startup file.

How do I find out where IceWM is looking for the startup file and preferences? If it is looking somewhere else, how do I set it to look in my ~/.icewm folder? Did I make a mistake by using root to install? Should I have installed IceWM using my user?

The Control Centre comes on screen but is missing most of the tools and when I tried using the change Date&Time tool it failed. SpaceFM and Rox-filer are working. ROXterm also works. Connectshares fails to connect to my share. But I can use the mount command from the command line to connect to my share.

When I ran menu manager it seems to work. But the menu does not change. When installing from apt-get I do get the ‘setting up IceWM menu’ (not sure of the exact wording) and it completes with no error. I can see the menu-applications file in /usr/share/desktop-menu/.icewm/menu-applications. And it does seem to be the current menu generated and has all the applications. But it does not show on the main IceWM menu.

How do I get my main IceWM menu populated with my apps? I seem to be missing some script that modifies the IceWM menu file in my ~/.icewm folder.

I’m stuck. Thank you for any tips you can share to help me get unstuck.
Seaken64

[Member jijojosephk]

Thank you again. I created a xorg.conf file inside /etc/X11. Initially I gave driver as ‘i810’ without any result. But later I’ve given intel and it worked when I use startx command. slim does show the same error and every boot ends up in command line as slim fails still. I’ll have to enter ‘startx’ to have GUI session. How can I see GUI during boot without explicitly entering any commands? I’m yet to try Xecure’s ISO.

[Member catfood]

Yea, thank you, great thread!!!

My dumb question seems to fit here. Is it easier to go antix core, then install 2 WMs and antix login(slim?).

or to install antix full, then prune ice/jwm, but add tiling window managers to the login manager?

I want either openbox or fluxbox, for when I’m lazy, tired, or frustrated. I wanna run a few tilers from there. I would really like an easy way to add them to a login manager. I’ve been trained to play with .Xresoucres, etc. then do startx. But when I break a WM, then I seem to lock myself out of the others. I’ve also managed recently to lock myself out off TTY1. Sorry to do a thread takeover. Easiest way to have fluxbox++? with a login I won’t keep breaking (Xresources.etc)

• This reply was modified 2 years, 5 months ago by catfood.

Howdy Jessie.

[Member Xecure]

wow! It really is a very small system. I found the general manuals here (in case you want to download and read it):
English: https://dlcdnets.asus.com/pub/ASUS/EeePC/EeePC4G(701)/e3555_EeePC4G_XP.zip
French: https://dlcdnets.asus.com/pub/ASUS/EeePC/EeePC4GSurf/F3683_EeePC_XP_UM.zip
Dutch: https://dlcdnets.asus.com/pub/ASUS/EeePC/EeePC4GSurf/DU3683_EeePC_XP_UM.zip

For 4GBs, you did well installing from net. I don’t know if we will be able to get a graphical interface working, but we can try.

Mandefu wrote:

my laptop now always after startup and login displays the coloured text ‘as@antix1 $

This means it boots to a terminal interface (not graphical) and logs in automatically to your account “as”. From here on we can continue installing components and try to get the graphical interface working.

When possible, connect your left Ethernet port to a router and try updating the system. Write this in the terminal and run it by pressing the Enter key:
sudo apt update
It will ask for your password, which you created during installation. Write the password and hit Enter again.
See if the machine can connect to the internet. If it can, you will see that it is downloading package information. This is good, and we need this to be able to continue installing components.

First, I will show you the main terminal based tool you will use to download and install components. Run
sudo cli-aptiX
Pay attention that the final X is capital X (cli-aptiX).
This cli program you can navigate with the arrow keys and you don’t need to write too much.
Move the arrow keys and press enter on the option “View a list of 165 suggested GUI packages”.
Hit enter again to view them all, and use the Down arrow key to view the list of installable programs.
This is simply a list of most used programs for antiX, where each program has a corresponding number used to reference it for installation.
When you want to install a program, you look for it (using the up and down arrow keys), remember the number beside the program, press the ‘q’ key and write the number of the program you wanted to install. It will ask if you want to mark it for later or install in that moment (better install then so you don’t forget).

I don’t know if you have the same numbers as how I see them, but you will need to install (to test if you can get a graphical environment to work):

Graphical server and drivers:
148) xorg
Window manager (for menus and windows)
145) icewm
File manager (to navigate folders and open files)
46) rox-filer

This is the minimum you need to test if you can launch a graphical environment. Install each of them, one at a time, and when you are done, exit cli-aptiX (by pressing ‘q’ to quit the program once or twice, maybe needing to press enter to confirm).

You should have returned to the terminal. The next step is just to test if the system is able to start in a graphical environment.
Run in terminal:
startx
If everything goes alright, you will see a simple, kind of ugly, graphical environment. See if you can move the cursor with the trackpad and try clicking and see if things move.

Let me know if this worked and we can keep building the system little by little to get a workable environment for your eeepc computer.

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

[Member voider]

PPC: Thank you for your kind welcome and suggestions. As I said before, I have some experience with Free Software (GNU/Linux mostly, but I have used some *BSD or Haiku too). For web browsing, Firefox is OK if I just open tabs one by one or just a few… Dillo and Netsurf are of course much less resource hungry, but you know the limitations those have. I think Palemoon is a better fit, opens almost anything and is lighter than Firefox. I have tried almost whatever browser you can name, including Badwolf. 🙂 For YT, I usually stream vids with mpv/vlc, or use youtube-dl and play them offline (this is my prefered option for audio only). As for a mail client, my phone has me covered. 😉 And sure, the antiX apps ecosystem is just great, I just love the apps included, GUI or CLI. I prefer using CLI if I have a good alternative, and apps like youtube-dl, mocp, wordgrinder, links, htop… or plain POSIX utilities are staples in my daily work. I have both a Void Linux and a Kiss Linux installs in which I don’t even have a toolbar, dektop icons, launchers or even a file manager… I startx because I need to browse the web mostly, but I use plain CLI mostly, and lots of keyboard shortcuts to manage everything (Openbox+st in Void glibc, sowm+st in Void musl and Kiss Linux). antiX, as it is, is almost a “luxurious” distro for me! 😀

Moddlt: Sure, one full Gb RAM should be a game changer in my Travelmate, but I can say I’m happy as it is… And we have three other machines at home, all of them cheap ones for sure, but more than powerful enough (two Celeron+4 Gb RAM laptops, onez four-core AMD with 8 Gb desktop) for my family needs (we don’t use them for gaming, for instance). Anyway, I’m overwhelmed for your kind offer, thank you very much! Sure someone out there has more need than I have of that RAM module, but I feel almost overwhelmed for your generosity, honestly thanks again! BTW, I’m from Mallorca, maybe you have heard about the place… 🙂

Thank you everybody, I hope I can contribute with my limited knowledge trying to help here, in this forum. I’m not too good with coding, sadly, but I can also offer my help as a translator (English to Spanish and/or Catalan) for any antiX project, and/or writting documentation or whatever.

Best wishes!

[Moderator christophe]

What about autologin as root from /etc/inittab?
1:2345:respawn:/sbin/getty -a root 38400 tty1

Then add cli-installer at the end of root’s .profile?

I haven’t tested this exact thing, but it’s how I set demo to autologin on antiX core, and then startx from .profile. So I figure this should work. 🙂

confirmed antiX frugaler, since 2019

[Member andfree]

Thanks for your help. Blacklisting nouveau caused, as you say, booting to a terminal. I tried “startx”, but the X server error that I’ve already mentioned (post #43918) occured again. I removed the nouveau blacklist file and that was enough to reboot to gui again.

[Member Xecure]

Murdock2525 wrote:

Nah. F6 lets me go to font size. Then enter..Antix 19.3 Manolis Glezos
StartX alt F2…nada alt F7 nada

Does normal boot lead to a working GUI environment or does it only lead to a terminal (no X)?

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

[Member Murdock2525]

Nah. F6 lets me go to font size. Then enter..Antix 19.3 Manolis Glezos
StartX alt F2…nada alt F7 nada

[Member andfree]

Xecure wrote:

In your installed system you could try booting with nomodeset boot parameter and see if that disables nouveau at boot.

As iamercado wrote (post #43541):

iamercado wrote:

I tried “nomodeset” in the boot options, but that just made antiX boot to a command prompt.

I tried “startx”, but a known from the past X server error occured (I copy here three lines):

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

xserver-xorg-legacy is already the newest version (2:1.20.4-1+deb10u1) and the following line already exists in /etc/X11/Xwrapper.config:

needs_root_rights=yes

• This reply was modified 2 years, 6 months ago by andfree.