startx unable to open WM session without a Display/Login Manager

seth · 2021-07-14 14:51:22

So, it's just a guess, but fix your locale:
https://wiki.archlinux.org/title/Locale

pritam_poseidon · 2021-07-14 15:28:44

according to wiki, there was no locale.conf in my /etc/locale.conf
so i followed wiki and created one.. but it didn't solve the problem...

moreover qtile gave the exact same coredumpctl gdb backtrack as before

seth · 2021-07-14 15:35:17

xdpyinfo | grep resolution
xrandr -q

?

(I'm just throwing out random ideas about what could possibly trigger a pango bug)

pritam_poseidon · 2021-07-14 15:43:05

seth wrote:

xdpyinfo | grep resolution
xrandr -q
?
(I'm just throwing out random ideas about what could possibly trigger a pango bug)

atleast you know what/how to debug, few days back i was search google : how to set DISPLAY in arch linux ( ._.)'

$ xdpyinfo | grep resolution
xdpyinfo : unable to open display "".
$ xrandr -q
Can't open display.

seth · 2021-07-14 15:44:28

You gotta run that form an xterm (twm or not doesn't matter, but using startx)

pritam_poseidon · 2021-07-14 15:55:34

seth wrote:

You gotta run that form an xterm (twm or not doesn't matter, but using startx)

doing this actually works (atleast it shows display)

$ xdpyinfo | grep resolution
  resolution:    96x96 dots per inch

$ xrandr -q
Screen 0: minimum 1 x 1, current 1027 x 771, maximum 8192 x 8192
Virtual1 connected primary 1027x771+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1027x771      60.00*+
   2560x1600     59.99  
   1920x1440     60.00  
   1856x1392     60.00  
   1792x1344     60.00  
   1920x1200     59.88  
   1600x1200     60.00  
   1680x1050     59.95  
   1400x1050     59.98  
   1280x1024     60.02  
   1440x900      59.89  
   1280x960      60.00  
   1360x768      60.02  
   1280x800      59.81  
   1152x864      75.00  
   1280x768      59.87  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
Virtual2 disconnected (normal left inverted right x axis y axis)
Virtual3 disconnected (normal left inverted right x axis y axis)
Virtual4 disconnected (normal left inverted right x axis y axis)
Virtual5 disconnected (normal left inverted right x axis y axis)
Virtual6 disconnected (normal left inverted right x axis y axis)
Virtual7 disconnected (normal left inverted right x axis y axis)
Virtual8 disconnected (normal left inverted right x axis y axis)

Last edited by pritam_poseidon (2021-07-14 15:56:10)

seth · 2021-07-14 16:17:33

0mm x 0mm

This looks suspicious and if pango tries to use it to calculate anything, it'll crash.

Add a configlet that forces reasonable monitor dimensions:
https://wiki.archlinux.org/title/Xorg#D … ze_and_DPI (Identifier is "Virtual1")

pritam_poseidon · 2021-07-14 16:54:39

it also didn't work..
as directed in wiki, i created a 90-monitor.conf inside /etc/X11/xorg.conf.d/

Section "Monitor"
    Identifier                "Virtual1"
    DisplaySize            286 179
EndSection

i also want to mention, that there were no xorg.conf file inside /etc/X11/
but in this wiki article :
https://wiki.archlinux.org/title/Xorg#Configuration
it mentions that /usr/share/X11/xorg.conf.d/ contains all default config files, and no extra setup is neccessary

should i be worried ?

seth · 2021-07-14 17:01:39

xorg.conf file inside /etc/X11/

that /usr/share/X11/xorg.conf.d/ contains all default config files

seth · 2021-07-15 06:09:34

Ok, insanity mode:
Install https://archlinux.org/packages/extra/any/ttf-dejavu/

I don't see how lightdm could circumvent that or why openbox et al. would crash if you had no (only pcf) fonts, but hey - nothing here makes sense anyway.

Edit: looking at the logs, the lightdm one finds /usr/share/fonts/misc, though…

Last edited by seth (2021-07-15 06:11:06)

pritam_poseidon · 2021-07-18 07:24:58

so i have been fiddling around a little bit, and with no avail it is very clear to me that it is a VM issue (atleast, i think so )

when i turned on my VM it starts tty in small resolution, than the native resolution, which gives me an idea that this is because VBox video/graphics driver doesn't start until the Display Manger kicks in,

how i came to this conclusion ?:
when i booted .iso in a native system it started right at native resolution by default (tty, boot logs, fsck everything from the start)

a new video just uploaded on Yt (the video is not related, but it shows setting up Xmonad WM from start), where it is clearly shown that it is running in Native system with tty at full resolution.
setting up .xinitrc just to start xmonad, and typing "startx" from tty actually started the desktop.

so I guess i will personally try this whole installation on a native system, to prove it to myself.
and if that's true, then only GPU pass through to VM may help solve this issue.

thanks seth for helping, i really learnt a lot

Arch Linux

#26 2021-07-14 14:51:22

Re: startx unable to open WM session without a Display/Login Manager

#27 2021-07-14 15:28:44

Re: startx unable to open WM session without a Display/Login Manager

#28 2021-07-14 15:35:17

Re: startx unable to open WM session without a Display/Login Manager

#29 2021-07-14 15:43:05

Re: startx unable to open WM session without a Display/Login Manager

#30 2021-07-14 15:44:28

Re: startx unable to open WM session without a Display/Login Manager

#31 2021-07-14 15:55:34

Re: startx unable to open WM session without a Display/Login Manager

#32 2021-07-14 16:17:33

Re: startx unable to open WM session without a Display/Login Manager

#33 2021-07-14 16:54:39

Re: startx unable to open WM session without a Display/Login Manager

#34 2021-07-14 17:01:39

Re: startx unable to open WM session without a Display/Login Manager

#35 2021-07-15 06:09:34

Re: startx unable to open WM session without a Display/Login Manager

#36 2021-07-18 07:24:58

Re: startx unable to open WM session without a Display/Login Manager

Board footer