touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #17377
[Bug 1327139] Re: mirscreencast broke (moved socket) in #71
Mir's default socket is $XDG_RUNTIME_DIR for reasons explained in LP
#1236912. Mirscreencast reads the framebuffer contents from U-S-C, and
currently U-S-C is hard-coded to override the default socket location
with '/run/mir_socket'.
unity-system-compositor --spinner=/usr/bin/unity-system-compositor-
spinner --file /run/mir_socket --from-dm-fd 9 --to-dm-fd 13 --vt 1
(Note that since '/var/run' is a symlink to ' /run' ,
'/run/mir_socket' == '/var/run/mir_socket'). So the right thing to do
would be to change it in lightdm (responsible for launching the U-S-C)
to not use an argument.
Or the easiest thing to do would be to not do anything and have
mirscreencast continue providing the socket override.
** Also affects: lightdm
Importance: Undecided
Status: New
** Changed in: mir (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mir
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1327139
Title:
mirscreencast broke (moved socket) in #71
Status in Light Display Manager:
New
Status in Mir:
Invalid
Status in “mir” package in Ubuntu:
Invalid
Status in “phablet-tools” package in Ubuntu:
Fix Released
Bug description:
Since the mir_socket moved from /tmp to /var/run, mirscreencast broke.
$ adb shell mirscreencast -n 1
Failed to connect to server. Error was :connect: No such file or directory
This works:-
$ adb shell mirscreencast -m /var/run/mir_socket -n 1
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: mir-utils 0.1.9+14.10.20140430.1-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.3-0ubuntu1
Architecture: armhf
Date: Fri Jun 6 10:47:19 2014
InstallationDate: Installed on 2014-06-06 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140606.1)
SourcePackage: mir
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1327139/+subscriptions