Search Results for 'startx'

[Member andfree]

The only unclear point to me was which value to use for background_style (the only referred ones as valid at my themefile is “stretch” and “tile”). I let it as it was (“stretch”). I specified color as #000000 (for black), removed the background.jpg and rebooted. This caused the same problems to the other laptop, too: X didn’t start automatically. At least, that laptop gave us an error message, after the effort to manually “startx”:

(==) Log File: "~/.local.share/xorg/Xorg.0.log", Time (...)
(==) Using config directory: "/usr/share/X11/xorg.conf.d"

Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

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

[Anonymous]

What size have you made the black image?

size (dimensions) shouldn’t matter. Consider stretched, vs tiled, vs centered:
The factors involved in the size of membuffer for the root window: display size (dimensions), and display palette color depth.
Source image is released after reading. The imagedata is rescaled and/or merged with bgcolor (if necessary, for “centered” presentation).

htop shows the same, if not slightly increased, memory consumption.

As I mentioned in an another topic, I’ve noticed the current version of slim exhibits cumulative “memory leak” with each logout/login. So, for an apples-to-apples comparison of the before (original) and after (black image) mem usage, I recommend: boot+login+test then replace imagefile and reboot+login+test

This caused trouble. X was not loaded automatically. After “startx”, it was stuck.

Thanks for reporting the result. Absence of imagefile for background is one several whatif’s I’ve not yet gotten ’round to testing.

edit:
extra “too much info” removed

[Member andfree]

Anonymous wrote:

try:
sudo mv /usr/share/slim/themes/antiX/background.jpg /usr/share/slim/themes/antiX/background.jpg_bak

This caused trouble. X was not loaded automatically. After “startx”, it was stuck. I rebooted with “alt + prt sc + reisub” and ran this to restore to the original situation:
sudo mv /usr/share/slim/themes/antiX/background.jpg_bak /usr/share/slim/themes/antiX/background.jpg

Anonymous wrote:

or you could
sudo mtpaint /usr/share/slim/themes/antiX/background.jpg
and edit so that it contains the solid color of your choice, then Save

This worked. I made it all black. But, unfortunately, htop shows the same, if not slightly increased, memory consumption.

[Forum Admin anticapitalista]

Welcome!

Try this

startx not working in Stretch (with sysvinit-core)

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

antiX with runit - leaner and meaner.

I need to figure out what slim (slim starts X, yes?) is doing that makes X able to see my keyboard and touchpad, so that I can replicate it with startx.

I’m coming to AntiX from Arch, because they dropped 32-bit support and I was sick of systemd. In Arch, I had things set up to my preferences: boot to a non-X CLI environment, and let me start X myself with my own .xinitrc. It worked fine. I’ve tried both antiX-core and antiX-base, and antiX-base if allowed to boot up to runlevel 5 has no problem with my EeePC 901’s keyboard or touchpad. They work fine. But both booting to runlevel 3 in antiX-base and then typing startx, or installing Xorg in antiX-core and then typing startx, leave the system unresponsive to keyboard or touchpad input.

Googling for information on configuring Xorg turns up a lot of claims that X no longer needs configuration files because it’s become “smart” enough to do the right thing. Why would it be doing different things depending on whether I let runlevel 5 start it or try to start it myself? Where should I start in troubleshooting this?

[Forum Admin Dave]

Not sure with lightdm, maybe in /etc/lightdm/lightdm.conf you could specify desktop-session as the login manager…. but I do not think lightdm will pass the correct information as it generates it’s own sessions where as a part of desktop-session generates the available sessions and inserts them into slim. You can use it apart from slim and lightdm by issuing the command

startx /usr/local/bin/desktop-session space-fluxbox

On the command line. I have set it in the past in a script to ask which session and start, and inserted a call to that script in my bashrc file

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

[Forum Admin Dave]

Well I may need to change the name of the thread as I was mainly concerned about seeing if slim is still “alive”… but the most accurate howto I have found is this:
https://wiki.archlinux.org/index.php/xorg_multiseat#For_LightDM
But basically enabling lightdm’s multiseat support is what I need.

I have enabled it as per the wiki article / lightdm docs and tried modifying it in as many ways I can think… for example making the xserver-command the same as loading a X session directly from /etc/inittab like
startx — :0 -layout seat-0 -seat seat-0 vt07
startx — :1 -layout seat-1 -seat seat-1 vt08 -sharevts -nolisten tcp

Multiseat works fine via a script to load X under each user on a separate screen automatically, but it would be nice to have the login screen. As lightdm is the default for MX (which is what I am using on one of the machines) I tried it, then tried slim ( as antiX is the other but slim does not support multiseat as best as I can tell), then Xdm which worked fine… normally in the past I have used gdm or kdm which are not very light.
The most I could find with the lightdm problem is that ~/.Xauthority needs to be deleted when trying lightdm (which I did) or my X server is configured wrong (which it is not because it works manually and with Xdm.) I booted with the systemd option just as a quick look but it still did not function and I was not going to try and make it function by running all the systemd seat assignment commands manually.

Once I have it figured out, I plan to make a how to on multiseat again under antiX / MX. So it would be nice to keep the install as close to stock as possible and not bring in bloat from kdm or gdm. I also plan on updating my script (which is a modification / rewrite of automseat) and possibly make it a little more presentable so you would only need to install the script and reboot to setup a multiseat system (aside from the hardware that is). I have it configure X org fine now, so just need to settle on a login manager.

• This reply was modified 5 years, 3 months ago by Dave. Reason: corrected my script to be a modification of automseat

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

[Member spaceman]

Thanks anti!

Sadly that didn’t help. On neither the PC (nVidia) or the laptop (Radeon). I did a new flat install on the Laptop, but I had the same error message with startxfce4. If I tried to launch with a DM I got a graphic login followed by:

Unable to contact settings server
/usr/bin/dbus-launch terminated abnormally without any error message

and then:

Unable to load a failsafe session. 
Unable to determine failsafe session name, possible causes: xfconfd isn't running (D-Bus setup problem) environment variable $XDG_CONFIG_DRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly.

• This reply was modified 5 years, 4 months ago by spaceman.

~ ASUS ROG Crosshair VIII Hero ~ AMD Ryzen 7 3700X 8-Core ~ Corsair Dominator Platinum 32 GB RAM ~ M.2 SSD Samsung NVMe Evo 970 Plus 500GB ~ SSD Samsung Evo 860 500GB ~ NVIDIA Geforce GTX 1650 Super ~

Between social reforms and revolution there exists for the social democracy an indissoluble tie. The struggle for reforms is its means; the social revolution, its aim.

antiX 17 Core showstopper error

I currently have three issues with 17 Core, two are trivial and the last is a bit of a showstopper.

1) Output during loading

[Fail] Loading cpufreq kernel modules...failed
[.....] CPUFreq Utilities: setting ondemand CPUFreq governor...disabled governor
[...ok available...done 

2) Bash not loaded at started (as with beta 3 release).
Easy enough to fix, issue Bash at prompt. Better still “chsh -s /bin/bash”…is this by design, or an oversight?

3) I ran face first into upstream Debian bug #856351 (I think).

Fatal server error:
(EE) parse_vt_settings: Cannot open /dev/tty0 (Permission denied)

I’ve seen some suggestions for adding entries to a file I do net yet have (but am going to create): etc/X11/Xwrapper.config…

Also:

UID != 0, of course.
"startx -- :4" works as expected. Wonder why xinit tries /dev/tty0
instead of /dev/tty1?

Perhaps this is the solution/workaround? K, can someone dumb it down a notch and tell me if I need to modify a file or simply issue this at the command. I’m using the xfce4 DE, I have no DM installed yet so I could go slim or lightdm (preferred): will I need to modify the DM config to ensure xinit uses /dev/tty1? I’m asking that question while vague on what /dev/ttyx actually is…

Or I am just going to have to sit on my hands until xinit is patched upstream?

• This topic was modified 5 years, 4 months ago by spaceman.
• This topic was modified 5 years, 4 months ago by spaceman.
• This topic was modified 5 years, 4 months ago by spaceman.

~ ASUS ROG Crosshair VIII Hero ~ AMD Ryzen 7 3700X 8-Core ~ Corsair Dominator Platinum 32 GB RAM ~ M.2 SSD Samsung NVMe Evo 970 Plus 500GB ~ SSD Samsung Evo 860 500GB ~ NVIDIA Geforce GTX 1650 Super ~

Between social reforms and revolution there exists for the social democracy an indissoluble tie. The struggle for reforms is its means; the social revolution, its aim.

IIRC, Antix 17 x64 chose the wrong video system in my PC. My onboard nVidia video is NOT being used, yet that install evidently configured the onboard nVidia for X, and yet my only monitor is connected to the added PCI card using ATI Radeon RV710. That system only booted to a console, startx errors said something about no screens.

Footnote: my mainboard is completely a nVidia chipset:

$ inxi -b
System:    Host: 64bitantix162 Kernel: 4.4.10-antix.1-amd64-smp x86_64
           bits: 64
           Desktop: MATE 1.16.2
           Distro: antiX-16.2_x64-full Berta Cáceres 15 June 2017
Machine:   Device: desktop Mobo: Gateway model: MCP61SM2MA v: FAB1.0 serial: N/A
           BIOS: Phoenix v: 6.00 PG date: 11/10/2007
CPU:       Dual core AMD Athlon 64 X2 4200+ (-MCP-) speed/max: 1000/2200 MHz
Graphics:  Card-1: NVIDIA C61 [GeForce 6100 nForce 405]
           Card-2: Advanced Micro Devices [AMD/ATI] RV710 [Radeon HD 4350/4550]
           Display Server: X.Org 1.19.2
           drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1680x1050@59.95hz
           OpenGL: renderer: Gallium 0.4 on AMD RV710 (DRM 2.43.0 / 4.4.10-antix.1-amd64-smp, LLVM 3.9.1)
           version: 3.3 Mesa 13.0.6
Network:   Card-1: NVIDIA MCP61 Ethernet driver: forcedeth
           Card-2: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
           driver: b43-pci-bridge
Drives:    HDD Total Size: 600.1GB (16.3% used)
Info:      Processes: 184 Uptime: 10:21 Memory: 624.1/1877.6MB
           Client: Shell (bash) inxi: 2.3.40 
mmmmna@64bitantix162:~