Hello all!
I have Manjaro running on a Latitude D620; Core 2 T7400, Intel GM945 (laptop GMA 950). Driver currently in use is i915g.
An issue occurred after a brand new installation of Manjaro and LXQt. When attempting to log into LXQt (through LightDM), the screen went black while a cursor momentarily showed up, then the cursor disappears just before LightDM re-appears with a log-in failure.
Then, all of a sudden LXQt started to log-in successfully; only for the same issue to start occurring when trying to load the Enlightenment window manager.
Computer restarts have no effect on the issue. Logs will be linked below (only have logs for the Enlightenment failures, sorry!)
X11 Logs:
X11 (Log.Old)
X11 (Current Log)
Enlightenment Logs:
Enlightenment (Current Log)
Please also provide system information as described (below) and of course the logs mentioned, that might be invaluable for troubleshooting.
inxi output may be posted directly as preformatted text.
I’m sure someone will help when they are able.
Regards.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:
Update Announcements
The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.
System Information
Output of this command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide more information and outputs from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Required reading
Resources
The link to your Enlightenment log doesn’t work - no content.
The X server crashes (segmentation fault).
The system log may hold more information (journalctl)
We have no hardware info.
Do you use different users to log into the different Desktop Environments / Window Managers (LXQt, Enlightenment)?
… you probably should …
Hm; it does appear the Enlightenment log is empty. I also meant to type LightDM instead of Enlightenment; but might as well post both logs.
LightDM Log
Enlightenment Log
Inxi System Info
As to the different user question, admittedly, I used the same user. Haven’t encountered issues with it before; but maybe now’s the first time?
- The journalctl text is far too large for both pastebin and the Manjaro Forum text limitations; how should I post it or break it up?
By default, the command journalctl without options will just list the entire journal, which may hold everything since you installed your system, basically.
You can restrict the output to one specific boot:
man journalctl
(look up the -b option)
journalctl -b will display the current
journalctl -b -1
or
journalctl --boot=-1
will return the one before the current one …
example (not pastebin):
journalctl --boot=-1 | curl -F 'file=@-' https://0x0.st
It really should not be a problem - not one that crashes the X server.
But in case of problems, it’s better to cleanly separate things - was my thinking.
According to your inxi
you have 4 GB of memory and no swap space - that would be the first thing to address
You are using BTRFS - which I’m totally unfamiliar with.
Swap as an extra partition might be better there than a swap file - which needs special “treatment” in BTRFS.
A swap file is easy to create on “normal” file systems - there are caveats with this on BTRFS
That’s all I know about that - I refer you to the excellent Arch wiki …
Getting a journalctl for you soon; the swap space issue would be me forgetting to “swapon” my swap partition. (I made a 6 GB partition in manual formatting.)
Note: The 945GM chipset can only reveal 3.2 GB of RAM, even on 64-bit OSe’s. So it’s really running with 3.2.
@Nachlese
JournalCTL --boot=-1 (Boot process edited out due to site limitation, but present in second log)
JournalCTL --boot=-2
… even better 
Why not incorporate it in /etc/fstab so it is always there ?
But:
what do I know about how things are supposed to work with BTRFS? … I don’t.
From your logs I can only see the same as from the previous ones:
the X server crashes - I can see no reason for it
Perhaps hardware related? (that is just speculation)
I don’t know and also don’t know where to go from here.
Someone else might.
I honestly just didn’t think of incorporating it into /fstab; thanks for the idea.
I wouldn’t be surprised if a ~17 year old hardware setup is having issues with X or modern window managers. My theory was something wasn’t playing nice with the old hardware as well. Guess it’s research time?
My hardware is from 2012 (or even earlier).
Not much younger than yours.
And I have a laptop (Fujitsu Siemens Lifebook S7010) from more than 20 years ago.
Can’t use Arch on it - CPU with no 64 bit support.
But still works great with a version of Debian.
If I where you I’d not use BTRFS but the tried and true ext4 as a file system on it.
… and then perhaps settle for one instead of multiple Desktops / Window managers
When the system is stable, move to the other one.
I don’t know how to track down your issue. 
