mlvwm icon indicating copy to clipboard operation
mlvwm copied to clipboard

Doesn't start

Open nonetrix opened this issue 3 years ago • 5 comments

I installed from source and also tried the AUR

mlvwm

Then put mlvwm in my .xinitrc like so but it doesn't start with startx also the log message seems normal besides

(WW) warning, (EE) not inplemented, (??) unknown.

nonetrix avatar Jan 14 '22 01:01 nonetrix

Thanks for reporting this. I assume you're using Arch Linux since you mentioned AUR. If so, which version are you running?

Looking at the mlvwm AUR, it appears to be using the last of Takashi HASEGAWA's releases from 2000. The code hasn't changed too dramatically since then, but I would suggest using the version built from source until the AUR gets updated (I'll add an issue for that).

Speaking of the AUR, there is a note that it should be dependent on libxpm, which is true. Do you have libxpm installed? (I expect you probably do since you didn't report any compilation errors.)

In your .xinitrc, please ensure that mlvwm is on the last line. I'd also suggest using exec mlvwm, as seems to be best practice, and maybe also the full path to mlvwm to rule out path issues.

If it's not too much trouble, could you provide full logs from building & installing, plus you the Xorg log from running startx?

morgant avatar Jan 14 '22 16:01 morgant

Thanks for reporting this. I assume you're using Arch Linux since you mentioned AUR. If so, which version are you running?

Looking at the mlvwm AUR, it appears to be using the last of Takashi HASEGAWA's releases from 2000. The code hasn't changed too dramatically since then, but I would suggest using the version built from source until the AUR gets updated (I'll add an issue for that).

Speaking of the AUR, there is a note that it should be dependent on libxpm, which is true. Do you have libxpm installed? (I expect you probably do since you didn't report any compilation errors.)

In your .xinitrc, please ensure that mlvwm is on the last line. I'd also suggest using exec mlvwm, as seems to be best practice, and maybe also the full path to mlvwm to rule out path issues.

If it's not too much trouble, could you provide full logs from building & installing, plus you the Xorg log from running startx?

I also tried from source here is the logs I couldn't figure out how to get logs without manually typing them before sorry Xorg.1.log

nonetrix avatar Jan 28 '22 04:01 nonetrix

Depending on your shell, you should be able to redirect both stdout & stderr to the file (by default it only redirects stdout), like so:

startx &> text-file.txt

Thanks for providing the Xorg log, I'll dig into this and see what I can find.

morgant avatar Jan 28 '22 13:01 morgant

I have same problem but as am running second to others XFCE, TWM (previously KDE) or third to others: sometimes CDE, NsCDE, I don't know if I can get the particular Xorg*.log. Would it be in a different than main one?

d@cosmos:~$ mlvwm
can't open display

dchmelik avatar Aug 28 '22 08:08 dchmelik

I have same problem but as am running second to others XFCE, TWM (previously KDE) or third to others: sometimes CDE, NsCDE, I don't know if I can get the particular Xorg*.log. Would it be in a different than main one?

d@cosmos:~$ mlvwm
can't open display

User error

You need to run startx. Unlike Wayland, window managers can't start themselves usually they need the use of another program named startx. There is others but we will pretend they don't exist for the sake of explanation

Put this in ~/.xinitrc which is a script that is run upon running startx it can have anything such as a start up sound with MPV or anything else

mlvwm

Then run

d@cosmos:~$ startx

Or you can start it manually

d@cosmos:~$ whereis mlvwm
/usr/bin/mlvwm
d@cosmos:~$ startx /usr/bin/mlvwm

nonetrix avatar Aug 28 '22 20:08 nonetrix