Bug 237334 - x11-wm/lxsession: data never sent to screen (lxde)
Summary: x11-wm/lxsession: data never sent to screen (lxde)
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-17 13:45 UTC by Cyril
Modified: 2019-05-22 14:14 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cyril 2019-04-17 13:45:45 UTC
After ugrading my packages, I can't start a lxsession anymore.

FreeBSD version: 12.0-RELEASE-p3
lxsession: 0.5.4

The process doesn't crash and is still running but do nothing.
A truss reports regulary:
recvmsg(11,0x7fffffffe728,0)	ERR#35 'Resource temporarily unavailable'

I find a workaround to start the lxsession:

1 - open a text console (ctrl+F1)
2 - 
export DISPLAY=:0.0
export LANG=fr_FR.UTF-8   
xvinfo

xvinfo is very very long and finish with:
X-Video Extension version 2.2
screen #0
 no adaptors present

now, the initial lxsession is visible but, sometimes with no running desktop (pcmanfm), sometimes with no title bar and no minimize/maximize/close button, sometimes with no mouse pointer, sometimes everything is fine.

Starting manually a lxsession with
/usr/local/bin/lxsession -s LXDE -e LXDE
always works and is complete (pcmanfm is running, title bar is completed).

After the workaround, everything works a usally and perfectly.

My display manager is slim and is started with /etc/rc.conf
Trying to use xdm and the issue is the same.


It seems lxsession is waiting for something that is unblocked by xvinfo.
Comment 1 Cyril 2019-05-22 14:14:07 UTC
In fact, the screen stay blocked with the slim theme.
The error is due to the following lines in $HOME/.gtkrc-2.0:
gtk-modules="gail:atk-bridge"

I suppose this line is added by a software installation rather than the upgrading step of the packages.
I think the line causes a problem because the software has been probably desinstalled and the line is not removed.

Which software adds this line?

Is it possible to write an error message in any log (/var/log/messages, $HOME/.cache/lxsession/LXDE/run.log, etc.) because the error is very very difficult to debug?

Thanks,
Cyril.