Search Results for 'startx'

Forum Forums Search Search Results for 'startx'

Viewing 15 results - 241 through 255 (of 310 total)
  • Author
    Search Results
  • #18818

    In reply to: SLiM

    Forum Admin
    BitJam

      Thank you all. I will keep SLiM from Debian.

      BitJam solutions doesn’t work in mine installation:
      – “/etc/X11/Xwrapper.config” doesn’t exists;

      anti told you the package you need for this file.

      – Startx, if not launched as root with sudo, fails with “VESA(0): Cannot read int vect”;

      I think you need to Xwrapper.config file to get this to work. The point of that change was to allow normal users to run startx successfully.

      – getty seems to ignore “–autologin” option.

      It works fine here on full, base, and core. It has done so for many years. Perhaps you copied it wrong (or I copied it wrong). If you boot the live system with the “db+” option then inittab will be set up to autologin as root on tty2 — tty4.

      Here is that section from a working inittab:

      
      1:2345:respawn:/sbin/getty --noclear 38400 tty1
      2:2345:respawn:/sbin/getty --autologin root 38400 tty2
      3:2345:respawn:/sbin/getty --autologin root 38400 tty3
      4:2345:respawn:/sbin/getty --autologin root 38400 tty4
      5:2345:respawn:/sbin/getty --autologin demo 38400 tty5
      6:2345:respawn:/sbin/getty 38400 tty6

      Probably it’s better to start from antiX base and remove packages than to start from antiX core and add packages, because I found no problems a year ago in the other way. But surely I will learn less…

      Could be. OTOH, you may need to install the one package anti suggested.

      Also, best not to cross the streams. If you are having problems with snapshot, that should be in a different thread.

      Context is worth 80 IQ points -- Alan Kay

      #18814

      In reply to: SLiM

      Member
      lucbertz

        Thank you all. I will keep SLiM from Debian.

        BitJam solutions doesn’t work in mine installation:
        – “/etc/X11/Xwrapper.config” doesn’t exists;
        – Startx, if not launched as root with sudo, fails with “VESA(0): Cannot read int vect”;
        – getty seems to ignore “–autologin” option.

        Furthermore I’m not able to get a functional snapshot with iso-snapshot; on startup of the generated ISO I get this:

        Error: mount: mounting /live/aufs on /live/aufs failed: No such device

        Does it really mount aufs on itself?

        Probably it’s better to start from antiX base and remove packages than to start from antiX core and add packages, because I found no problems a year ago in the other way. But surely I will learn less…

        #18811

        In reply to: SLiM

        Forum Admin
        BitJam

          In order to get a custom minimal single desktop, I tried to install xorg and openbox on top of antiX core, […]

          – is there a fast and light alternative to SLiM for automatic login, already available in antiX repository?

          Here is a fast and light alternative to do what you want that requires no added packages.

          1) As root, edit the file /etc/X11/Xwrapper.config and add this line at the bottom:
          needs_root_rights=yes

          This should let normal users use the startx command. You can test this by trying to run the following command as your user from a virtual console:
          startx /usr/local/bin/desktop-session -- vt7
          If this works, just log out of X to return to the console.

          2) Select a vt (virtual terminal aka virtual console) and create a ~/.bash_login for your user that contains:

          if [ -z "$DISPLAY" -a $(id -u) -ge 1000 ]; then
              tty=$(tty)
              case $tty in
                  /dev/tty5) startx /usr/local/bin/desktop-session -- vt7 2>&1 | tee -a ~/xsession-log  ;;
              esac
          fi

          where I arbitrarily select vt5 as the console to log in on so I used “/dev/tty5” in the case statement. (the vt7 after — says to open up X on vt7). You can test this by switching to vt5 with ctrl-alt-F5 and logging in as your user. X Windows should start. Again logout of X to return to the console.

          3) As root, edit /etc/inittab to log in as your user automatically on vt5. Let’s assume your username is “demo”. Change the line that starts with “5:2345” so it reads:
          5:2345:respawn:/sbin/getty --autologin demo 38400 tty5
          In order to have this change take effect without rebooting run:
          sudo /sbin/telinit q
          You can test this by switching to vt5 (as above) and using the “exit” command. You should get automatically logged in which will automatically start X.

          HTH

          Context is worth 80 IQ points -- Alan Kay

          #18793

          In reply to: SLiM

          Anonymous

            why don’t you provide an “agnostic” SLiM package, with a further package for its configuration, like slim-antix.deb?

            Why == because striving to side-patch the code is a tail-chasing excercise toward frustration.
            The disparity between forks has become too extreme.
            Patches atop patches atop patches, they do not merge cleanly and require manual cherrypicking and manual merging
            Here’s my personal build, tailored to antiX: https://gitlab.com/skidoo/slim-antix

            is there a way to use the newer and surely better supported SLiM of antiX, configuring it like the Stretch one?

            It’s linux, so the answer to nearly any question is “yes”. Unfortunately, I don’t have a clear sense of what you are asking here.
            .

            is there a fast and light alternative to SLiM for automatic login, already available in antiX repository?

            As Dave explained in another recent topic, you can opt to forgo use of a (xdm,SLiM,lightdm) display manager altogether.
            I don’t recall the exact the exact launchstring syntax, but it would be something like “startx desktop-session openbox”

            In the end I solved it in a fast, ignorant way, simply replacing SLiM provided by antiX repository with SLiM of Stretch.

            is my solution valid or are there drawbacks?

            One drawback is that you’re “off the reservation”, maybe running an assemblage that few others have tested to confirm those components//versions interoperate well.

            #18768
            Forum Admin
            anticapitalista

              Do you need to configure it?
              Why not just install via apt xorg and xserver-xorg-legacy fluxbox and use startx?

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

              antiX with runit - leaner and meaner.

              #18650
              Forum Admin
              anticapitalista

                Try xorg=intel.

                Also instead of startx , type startx /usr/local/bin/desktop-session rox-icewm (if you are running base or full versions).

                BTW, if you are using 17.3 base/full, read this and use 17.3.1 instead: serious-bug-installing-antix-17-3-full-and-base-versions

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

                antiX with runit - leaner and meaner.

                Member
                Fantomas

                  Hi,
                  I’m struggeling with live CD booting into X11 on my PIII.
                  I figured out that in /etc/X11/xorg.conf the driver was set to vesa. That prevents X to Start into graphical mode.
                  I changed it to intel and startx worked. But it is just an GUI without Antix Desktop.
                  How can force Antix to use the Intel driver at boot time?

                  Regards
                  Thomas

                  #18409
                  Member
                  black-clover

                    Hello,
                    I’m trying to install a minimal AntiX distro on a Compaq C500 laptop.
                    I have installed the core version, updated, upgraded, and then installed the following packages:
                    xserver-xorg
                    xserver-xorg-video-intel
                    xserver-xorg-input-synaptic
                    xserver-xorg-input-mouse
                    xserver-xorg-input-kbd
                    xinit
                    policykit-1
                    jwm

                    Now, if I login as root and use startx, I get into jwm and everything works fine.
                    However, if I login as a normal user, once I get into jwm the mouse and system freeze.
                    I assumed it was an authority issue and tried to use the policykit-1 configuration that I use on my debian box but to no avail.
                    I have a startup command in jwm to launch policykit agent at startup.
                    Any advice on how to troubleshoot the problem?

                    Member
                    marius

                      HP Mini 311-1037NR PC – Product Specifications
                      https://support.hp.com/us-en/document/c01896922

                      I installed AntiX 17 (BASE) x86 to the SSD. It boots okay. The ethernet does not seem to work. To get the WiFi to work, I (am pretty sure that I) had to de-blacklist the “b43” driver, restart, and go to the WPA supplicant app.

                      To maximize the capabilities of this low-spec machine, I installed the Nvidia drivers via the Nvidia installer. It installed 342.XX. Now, after rebooting, no SLiM. No desktop manager. It brings up the terminal to login in. I log in with user/password. I enter “startx” -> NVIDIA splash screen -> then it boots to the desktop.

                      Big Question:
                      1. How can I bring back a desktop manager (any one would be fine).

                      Minor questions:
                      1. (Automatically) Make JWM + SpaceFM the default environment upon loggin in, how?
                      2. Automatically connect to my WIFI network every time, how?

                      #18365
                      Member
                      fungalnet

                        But startx worked before you shifted to testing?
                        It might be that you were asked somewhere to keep your previous .conf file or install the distribution’s version and you may have kept something incompatible. What if you try to reinstall xorg xorg-xinit your desktop or window manager.
                        Do you have a .xinitrc file in your home directory?
                        What about xf86-video-intel

                        • This reply was modified 4 years, 3 months ago by fungalnet.
                        #18348
                        Forum Admin
                        Dave

                          You can look in /var/log/ at the xorg log and the slim log. There should also be a log in your home folder for xorg if you start things manually. If you want to try startx… run like this
                          startx /usr/local/bin/desktop-session rox-icewm
                          To get a normal antix type session.

                          Follow skidoo suggestions first. Also one more stupid sounding suggestion. When you turn the computer on just leave it for 5-10 minutes and see if the slim log in comes up. I have had it twice now after upgrading to testing in the last few days that this long wait makes it work. I have yet to figure out why other than slim is waiting for the x server to start excepting connections. I could get slim to come up sooner by doing service slim stop && service slim start but am not able to login. Running startx would not work (or rather would take 5min). And the very curious thing was trying lightdm as the login manager which comes up right away….

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

                          #18345
                          Anonymous

                            I would not expect simply typing “startx” to work.
                            Following a dist-upgrade operation, I would attempt a normal shutdown then reboot. (do this at least twice)
                            After several reboots, if the problem persists, I might add nomodeset to the bootline…

                            Afterward, if still faced with a tty, I would type “sudo init 5”.
                            Faced with a tty prompt in runlevel 5, I would type “sudo slim” (and be prepared to copy any error messages).
                            If still no joy, I would begin grepping /var/log/* for warning//error messages.

                            Member
                            seaken64

                              Hi all,

                              So, I decided to try my hand at running an antiX-17 system with the “testing” repo. I’ve been learning a lot about repos and have a better understanding of how linux repos work to update and upgrade the system. But I’m still learning. I thought I could accelerate this learning curve by installing a testing repo system on another computer, while I keep the stable systems on their own machines.

                              I installed antiX-17 Full 32-bit and chose the “testing” repo. I then did the updates and upgrade and dist-upgrade. After the “dist-upgrade” I do not get into X. I am dropped at a text mode login. I can log in and run inxi, lsmod, MC, etc. But I tried starting X but can get the X server to start.

                              Is the command still “startx”? I used startx and this is what I get back:

                              /etc/X11/xinit/xserverrc: 3: exec: /usr/bin/X: not found
                              xinit: giving up
                              xinit: unable to connect to the X server: connection refused
                              xinit: server error

                              I looked at xorg.0.log and dmesg and lsmod. The hardware looks good. I am getting all the good drm and glx stuff using the intel i915 driver.

                              Maybe there is a problem with a missing file? Where do I look next to troubleshoot X server?

                              Thanks for any help you can give to get me pointed in the right direction.

                              Seaken64

                              #18242
                              Moderator
                              christophe

                                My 32-bit antiX 17.3 core with minimal X (jwm):

                                `Private + Shared = RAM used Program

                                68.0 KiB + 101.0 KiB = 169.0 KiB sh
                                88.0 KiB + 107.0 KiB = 195.0 KiB startx
                                196.0 KiB + 60.0 KiB = 256.0 KiB gpm
                                252.0 KiB + 104.5 KiB = 356.5 KiB init
                                260.0 KiB + 151.5 KiB = 411.5 KiB cron
                                216.0 KiB + 217.0 KiB = 433.0 KiB xinit
                                524.0 KiB + 213.0 KiB = 737.0 KiB dbus-daemon
                                312.0 KiB + 441.5 KiB = 753.5 KiB ck-launch-session
                                588.0 KiB + 241.5 KiB = 829.5 KiB login
                                860.0 KiB + 292.0 KiB = 1.1 MiB sudo
                                1.1 MiB + 91.0 KiB = 1.2 MiB udevd
                                612.0 KiB + 634.5 KiB = 1.2 MiB getty (5)
                                1.4 MiB + 109.5 KiB = 1.5 MiB rsyslogd
                                748.0 KiB + 920.5 KiB = 1.6 MiB polkitd
                                1.7 MiB + 522.0 KiB = 2.2 MiB dhclient (2)
                                1.4 MiB + 909.5 KiB = 2.3 MiB console-kit-daemon
                                2.8 MiB + 90.5 KiB = 2.9 MiB wpa_supplicant
                                3.1 MiB + 41.0 KiB = 3.2 MiB haveged
                                2.5 MiB + 1.4 MiB = 3.8 MiB bash (2)
                                3.6 MiB + 1.4 MiB = 5.0 MiB conky
                                4.8 MiB + 2.7 MiB = 7.5 MiB x-window-manage
                                5.9 MiB + 2.4 MiB = 8.4 MiB urxvt (2)
                                11.9 MiB + 1.1 MiB = 13.1 MiB Xorg
                                ———————————
                                59.0 MiB`

                                • This reply was modified 4 years, 1 month ago by rokytnji.
                                Attachments:

                                confirmed antiX frugaler, since 2019

                                #14299
                                Member
                                isminaki

                                  From the login-screen of C-A-F1 did you try startx ?

                                  startx did not start, but sudo startx

                                  Now, I am into antiX. But in a very strange situation.
                                  icewm panel is here. Mouse is working.
                                  But no desktop, no conky, no tray on the right bottom.
                                  slimjet and ff did not start, but palemoon did.
                                  When I tried to switch to xxxjwm, I am thrown back to console.

                                  • This reply was modified 4 years, 4 months ago by isminaki.
                                  • This reply was modified 4 years, 4 months ago by isminaki.
                                  • This reply was modified 4 years, 4 months ago by isminaki.
                                Viewing 15 results - 241 through 255 (of 310 total)