I was wrong. What I was reproducing is a different crash with large FDs
not specific to Xmir.
I'm really not sure how to reproduce your crash or if your use case is
valid.
Only one theory: the logic for the -fd client connection is executed
early before Xmir has started properly. We can try moving it to a lower
location after the server has actually initialized.
** Changed in: xorg-server (Ubuntu)
Importance: High => Medium
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1675481
Title:
Xmir crashes when using the '-fd' option
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
I'm trying to use the '-fd' option in Xmir and get a crash when Xmir
starts up.
This is what I'm doing:
I'm using socket()/bind()/listen()/accept() on a AF_UNIX socket at
/tmp/.X11-unix/X0 (or whatever available display number). DISPLAY is
then set based on this. Then, when an X app accesses that socket, the
code then starts Xmir and passes the fd returned in the accept() call
to Xmir in the '-fd' option.
This is what I get in journalctl when this crash occurs:
http://pastebin.ubuntu.com/24235520/
I installed the Xmir debug symbols and also passed in '-core' when
starting Xmir and here is the bt: http://pastebin.ubuntu.com/24236088/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1675481/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
