Search Results for 'startx'

[Member zeh]

Dave wrote:

Instead try something like
startx /usr/local/bin/desktop-session rox-icewm (or space-icewm, icewm, space-fluxbox etc)

gives the same errors as just startx

[Member oops]

Thank you for this confirmation Skidoo.
Maybe a work around then (via startx or so) within Slim ?

# inxi -Sxxx
System:    Host: antix1 Kernel: 4.9.170-antix.1-486-smp i686 bits: 32 compiler: gcc v: 6.3.0 
           Desktop: IceWM 1.4.2 info: icewmtray dm: SLiM 1.3.4 
           Distro: antiX-17.4.1_386-full Helen Keller 28 March 2019 
           base: Debian GNU/Linux 9 (stretch)

[Forum Admin Dave]

Two notes that are antiX specific:
Xinitrc is not used in default antiX configuration. So relying on it will error out / be debian default package config with no extras.

Second, startx defaults to .xinitrc which as previously stated is not used by default in antiX. Instead try something like
startx /usr/local/bin/desktop-session rox-icewm (or space-icewm, icewm, space-fluxbox etc)

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

[Member zeh]

Hi Jim,

1)
/tmp in / (with plenty of space)
File properties, Permissions Tab:
Owner: root
Group: root
permissions rwx , rwx , rwx / –S

2) /media/home/axTest/.Xauthority
File properties, Permissions Tab:
Owner: root
Group: root
permissions rw- , — , — / —

3)
From slim.conf (before and after reinstallation)
default_path /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
default_xserver /usr/bin/X11/X
xserver_arguments -nolisten tcp

4)
xinitrc
/media/rootaXTest/etc/X11/xinit/xinitrc
File properties, Permissions Tab:
Owner: root
Group: root
permissions rwx , r-x , r-x / —

Restarted after having reinstalled slim. No difference:
blank screen, Ctrl+Alt-F1 gives me the system in text mode (before I said CLI, meaning the same – system in text mode). ‘startx’ produces errors and ‘sudo startx’ gives me icewm in root session (with a different menu, no background image, no access to fluxbox or JWM).

Restarted again after having renamed xinitrc:
blank screen, Ctrl+Alt-F1 gave me the system in text mode; ‘sudo startx’ didn’t give me icewm, rather a black screen and a terminal. I could launch apps from the terminal (root mode) – synaptic, spacefm, palemoon – which ran with some interface limitations (e. g., no window menu).
Restarted once again ater having renamed the file back to xinitrc – could start icewm with ‘sudo startx’ as before.

Regards,
Zeh

[Member wildstar84]

The fact that you got X to start up at all is a good sign. I’ve never had much luck in Antix w/startx. I just always use the default runlevel 5 which should start up X on it’s own. A cpl. more things to check

1) Where is /tmp set up – ramdisk, or in root (and it’s not full/has plenty of space)? Make sure it’s permissions 777 (so that X run as you can create temp. files, etc.

2) Make sure your .Xauthority file isn’t somehow owned by root, but by you (I’ve had root take ownership of it before, perhaps by running X as root, as you did?).

3) Perhaps, reconfigure or reinstall slim, perhaps it’s config file (/etc/slim.conf) isn’t right?

4) If you have a .xinitrc file, perhapes check / rename it (to try not using it). I still think that starting up the normal way (no “startx”) and it drops you to a terminal login-prompt SHOULD put some useful error messages in /var/log/Xorg.0.log or slim.log or auth.log which should give some clue as to why X failed to start as user.

Those are the only things I can think of for now.

Regards,

Jim

[Member zeh]

Anonymous wrote:

Hi zeh,
my Xauthority has the first one rw and the rest empty. “rw-,—,—/—”
That’s on my stable install. and is 54b in size.

To my surprise, my Testing .Xauthority file is now 52b in size and its permissions are “rw-,—,—/—” just like yours, which means that either I made some mistake when I saw 104b or for some reason strange to me something made the info in the file to be doubled at a certain moment. My Stable .Xauthority file is 53b as said and its permissions are also “rw-,—,—/—”.

The facts that startx only works as root and “/usr/bin/mandb: can’t chmod /var/cache/man/CACHEDIR.TAG: Operation not permitted” tell me that there still must be permissions problems I’ve not been able to identify.

• This reply was modified 4 years ago by zeh.
• This reply was modified 4 years ago by zeh.
• This reply was modified 4 years ago by zeh.

[Member zeh]

Hi Jim,

Did you do “ls -l /usr/bin/sudo”?
Mine shows: “-rwsr-xr-x 1 root root 157192 Jan 12 12:10 /usr/bin/sudo”

Following the previous posts I’ve searched a bit more and I’ve found that one, yes.

“ls -l /usr/bin/sudo” showed the version with incorrect permissions
I then did “chmod u+s /bin/sudo” (as per the instructions)
and “ls -l /usr/bin/sudo” again – it now showed the correct permissions (it looks like yours)

After this su is working fine (sudo was corrected before and also works fine) – no more “authentication failure”.

However, I still get a blank sreen at boot.
At the blank screen, Ctrl+Alt-F1 gives me the CLI with the boot info.

Visible part of the boot info:

[....] Starting session management daemon: elogind [   22.991661] cgroup:Cgroup2: unknown option "nsdelegate"
[   23.106731] elogind-daemon [1983]: New seat seat0. 
.
[OK] Starting mouse interface server: gpm.
[OK] Starting SMO IRQ Balancer: irqbalance.
[OK] Loading cpufreq kernel modules... done (acpi-cpureq).
[OK] CPUFreq Utilities: Setting ondemand CPUFreq governor... CPU0... CPU1... done.
[OK] Starting SANE Network scanner server: saned.
Starting X display manager: slim.
[OK] Starting OpenBSD Secure Shell server: sshd.
Applying Power save settings... done.
Setting battery charge thresholds... done.
[warn] VirtualBox Additions disabled, not in Virtual Machine... (warning).
[OK] Starting Network connection manager: wicd.

Debian GNU/Linux buster/sid Sat2aX2 tty1

Sat2aX2 login: axTest
Password:
Last login: Sun Apr 20 21:28:22 BST 2019 on tty1
No mail.
[84.482465] elogind-daemon[1983]: New session 2 of user axTest.
axTest@Sat2aX2:~

When I try “startx” I get:

startx
xauth: timeout in locking authority file /home/axTest/.Xauthority
xauth: timeout in locking authority file /home/axTest/.Xauthority
[EE]
Fatal server error:
[EE] Cannot open log file: "/home(axTest/.local/share/xorg/X.org.1.log"
[EE]
[EE]
Please consult the The X.org Foundation ....
[EE]
xinit: unable to connect to X server: Connection refused
xinit: server error
xauth: timeout in locking authority file: /home/axTest/Xauthority
axTest@Sat2aX2:~

When I do “sudo startx” I get a IceWM root session without the wallpaper. And when I try to log in into this forum I’m not able to enter my username or password. I just can’t type anything in the two boxes.

When I try to change to one of the other Desktops (rox-fluxbox, space-icewm, etc) the system just logs me out of the session and gives me the CLI back

When I update the system everything seems to go as usual except for some problem with /usr/bin/mandb

root@Sat2aX2:~
# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  antix-libs bash packageinstaller-pkglist
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,508 kB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.gr.debian.org/debian testing/main amd64 bash amd64 5.0-4 [1,378 kB]
Get:2 http://repo.antixlinux.com/testing testing/main amd64 antix-libs all 0.6.15 [85.3 kB]                                                                  
Get:3 http://repo.antixlinux.com/testing testing/main amd64 packageinstaller-pkglist all 0.2.17 [45.0 kB]                                                    
Fetched 1,508 kB in 14s (104 kB/s)                                                                                                                           
(Reading database ... 274011 files and directories currently installed.)
Preparing to unpack .../archives/bash_5.0-4_amd64.deb ...
Unpacking bash (5.0-4) over (5.0-3) ...
Setting up bash (5.0-4) ...
update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
(Reading database ... 274011 files and directories currently installed.)
Preparing to unpack .../antix-libs_0.6.15_all.deb ...
Unpacking antix-libs (0.6.15) over (0.6.13) ...
Preparing to unpack .../packageinstaller-pkglist_0.2.17_all.deb ...
Unpacking packageinstaller-pkglist (0.2.17) over (0.2.16) ...
Setting up packageinstaller-pkglist (0.2.17) ...
Setting up antix-libs (0.6.15) ...
Installing new version of config file /etc/sudoers.d/antixers ...
Processing triggers for man-db (2.8.5-2) ...
/usr/bin/mandb: can't chmod /var/cache/man/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/vi/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/vi/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/vi/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/cs/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/cs/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/cs/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/sr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/sr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/sr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/sv/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/sv/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/sv/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/ru/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/ru/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/ru/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/zh_TW/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/zh_TW/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/zh_TW/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fr.ISO8859-1/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/pt/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/pt/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/pt/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/hr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/hr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/hr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fr.UTF-8/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fr.UTF-8/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fr.UTF-8/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/id/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/id/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/id/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/fi/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/fi/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/fi/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/pl/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/pl/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/pl/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/es/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/es/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/es/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/pt_BR/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/pt_BR/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/pt_BR/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/da/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/da/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/da/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/tr/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/tr/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/tr/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/nl/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/nl/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/nl/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/ko/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/ko/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/ko/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/ja/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/ja/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/ja/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/de/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/de/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/de/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/it/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/it/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/it/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/zh_CN/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/zh_CN/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/zh_CN/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/hu/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/hu/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/hu/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/sl/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/sl/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/sl/4658: Permission denied
/usr/bin/mandb: can't chmod /var/cache/man/oldlocal/CACHEDIR.TAG: Operation not permitted
/usr/bin/mandb: can't remove /var/cache/man/oldlocal/CACHEDIR.TAG: Permission denied
/usr/bin/mandb: fopen /var/cache/man/oldlocal/4658: Permission denied
Processing triggers for menu (2.1.47+b1) ...
root@Sat2aX2:~
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@Sat2aX2:~
# 

Trying to find something out of normal related to xauth, the only thing I could notice is the difference in size between the files .Xauthority of my Testing install (104 B) and of my Stable install (53 B). My blind guess is that there may be a problem with my /home/axTest/.Xauthority file. Its permissions are “r–- r– –– —”.

Thanks for trying to help,
Zeh

[Member seaken64]

caprea wrote:

seaken64 wrote:

And then what do I type at the command line to start IceWM/Fluxbox/JWM window manager?

AFAIK, the right command should be something like
startx /usr/local/bin/desktop-session rox-fluxbox

Thank you caprea. I was hoping it would be startx as that was what I was used to in Vector. But it doesn’t work for me. It might work if I typed it in as you listed. I haven’t tried that yet. But “slim” works so I will stick with that for now.

Seaken64

[Moderator caprea]

seaken64 wrote:

And then what do I type at the command line to start IceWM/Fluxbox/JWM window manager?

AFAIK, the right command should be something like
startx /usr/local/bin/desktop-session rox-fluxbox

My apologies if this topic shows up twice. I did something wrong and I don’t think I actually entered the topic last time. Here goes again.

I’ve been experimenting with both Core and Base versions of antiX-17.4.1. On the Base version I would like to set the default login to the Text User Interface (TUI) and then, when I want to, launch the GUI desktop from command line. I liked that feature of Vector Linux. I could always choose the TUI and then use “startx” to launch the GUI. But I can’t figure out how to do that in antiX. There does not seem to be a section in the wiki or manual that shows me how to do this type of setup. I always get logged in to the GUI in BASE.

How do I set the default login to the console/TUI in antiX Base? And then what do I type at the command line to start IceWM/Fluxbox/JWM window manager?

Thanks for any tips you can share.

Seaken64

I started installing antiX with 17.3.1, it run satisfying
Then made an update. Which version I use now I do not know, because I did not find where to see the version number.
Now the system stops at the login.
I can proceed by logging in as a user and type startx, but I want the startup to icewm or jwm

[Member lucbertz]

Thank you very much, BitJam.
I will not use SLiM, running startx automatically on start-up with your solution.

[Moderator caprea]

Did you try just

startx

you can also look at the history.log from the console with

sudo cat /var/log/apt/history.log

and make a note of it.
It is sorted by date, the last ones should of course be the important one.

[Moderator caprea]

You can also try after Ctrl Alt F1

to start your desktop with
startx /usr/local/bin/desktop-session rox-icewm

If this works you could look at your /var/log/apt/history.log
what was maybe removed or installed and post it here.

Hello guys I am a French user,
After installing the nvidia driver ,I have a normal load and then a black screen and loss of the keyboard, how to get a console? antix does not offer a recovery mode unlike other distributions . From grub which commands do I need to enter to get a console to log in as root?
In the grub menu I replaced “ro” by “rw” and go to the end of the line to add init=/bin/bash, then I entered F10 but the loading continues until the black screen. How to prevent startx?

Translated with http://www.DeepL.com/Translator
greetings