www.cendio.com

Bug 6190

Summary: Unity sessions doesn't start in ThinLinc on Ubuntu 17.04
Product: ThinLinc Reporter: Samuel Mannehed <samuel@cendio.se>
Component: MiscAssignee: Samuel Mannehed <samuel@cendio.se>
Status: NEW QA Contact: Bugzilla mail exporter <bugzilla-qa@cendio.se>
Severity: Normal    
Priority: P2 CC: derfian@cendio.se
Version: trunkKeywords: derfian_tester
Target Milestone: PoolTodo   
Hardware: PC   
OS: Unknown   
Bug Depends on: 5950    
Bug Blocks: 6156    

Description From cendio 2017-03-09 13:33:39
XFCE works, but not Unity. I see the following in xinit.log after choosing the
Unity profile:

> Running /opt/thinlinc/etc/xstartup.d/30-tl-xdg-user-dirs (Translating standard folders)
> Running /opt/thinlinc/etc/xstartup.d/40-tl-mount-localdrives (Mounting local drives)
> Running /opt/thinlinc/etc/xstartup.d/41-tl-lp-redir-launch (Setting up printer port redirection)
> Running /opt/thinlinc/etc/xstartup.d/43-tl-pulseaudio-launch (Starting session PulseAudio server)
> W: [pulseaudio] main.c: Couldn't canonicalize binary path, cannot self execute.
> Session PulseAudio server started
> Running /opt/thinlinc/etc/xstartup.d/50-tl-wait-smartcard (Waiting for smart card connection)
> Stopping initial window manager...
> Done.
> Executing profile: unity
> Using XDG session: ubuntu
> Executing XDG session command: /usr/lib/gnome-session/run-systemd-session ubuntu-session.target
> Profile command exited with exit code 0
> Running /opt/thinlinc/etc/xlogout.d/tl-kdestroy.sh
> Running /opt/thinlinc/etc/xlogout.d/tl-umount-localdrives
> tl-xinit: client terminated and returned 0
> tl-while-x11: lost Xserver connection, terminating child 18401 ...
> tl-while-x11: lost Xserver connection, terminating child 18395 ...
> E: [tunnel-sink] module-tunnel-sink-new.c: Stream failed.
> tl-xinit: deleting ../1.1489062221.ended
> tl-xinit: Session terminated. Exiting.
------- Comment #1 From cendio 2017-03-09 14:32:48 -------
LXDE works, but GNOME seems to have a similar problem to Unity. No hints in
xinit log however.
------- Comment #2 From cendio 2017-03-09 15:16:11 -------
This seems to be a variation of bug 5950 as Gnome seems to start fine if we
force our environment upon systemd and d-bus.

Unity has more issues it seems as it starts up, then dies again. However
running "unity" manually works.
------- Comment #3 From cendio 2017-03-14 11:03:15 -------
We'll put up a platform specific note with information that this is broken,
then move the bug to PoolTodo to do more digging and find more workarounds and
ideas for a long term solution.
------- Comment #4 From cendio 2017-03-14 15:28:54 -------
(In reply to comment #1)
> LXDE works, but GNOME seems to have a similar problem to Unity. No hints in
> xinit log however.

Both GNOME Shell and GNOME Classic have started working after installing
updates on the machine.
------- Comment #5 From cendio 2017-03-14 15:50:13 -------
Tested Cinnamon, KDE and Mate as well on Ubuntu 17.04, none of them have the
same problem Unity does and starts without issues.
------- Comment #6 From cendio 2017-03-14 15:50:58 -------
Platform Specific Note added for Unity:

https://www.cendio.com/thinlinc/docs/platforms/ubuntu

This bug should be moved to the milestone PoolTodo after verification of the
PSN is done.
------- Comment #7 From cendio 2017-03-20 13:23:33 -------
(In reply to comment #6)
> Platform Specific Note added for Unity:
> 
> https://www.cendio.com/thinlinc/docs/platforms/ubuntu

Tested on Ubuntu 17.04 Desktop (x86_64) nightly, installed today.

 ☒ Unity
 ☑ LXDE
 ☑ XFCE
 ☑ KDE
 ☑ GNOME
 ☑ GNOME Classic

Note reads fine and the recommended alternative desktops will start.

> This bug should be moved to the milestone PoolTodo after verification of the
> PSN is done.

Aye.
------- Comment #8 From cendio 2017-03-20 13:28:56 -------
With regards to the original problem, I'm guessing that something isn't
transfering the display properly to the unity startup script. I'm seeing
several "Couldn't open display :0" errors in system logs.

> Mar 20 03:14:03 ubuntu bamfdaemon[9123]: cannot open display: :0
> Mar 20 03:14:03 ubuntu indicator-print[9118]: cannot open display: :0
> Mar 20 03:14:03 ubuntu unknown[9231]: cannot open display: :0
> Mar 20 03:14:03 ubuntu compiz[9245]: Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/compiz (core) - Fatal: Couldn't open display :0
> Mar 20 03:14:03 ubuntu indicator-print[9247]: cannot open display: :0
> Mar 20 03:14:03 ubuntu bamfdaemon[9253]: cannot open display: :0
> Mar 20 03:14:03 ubuntu unity-panel-ser[9287]: cannot open display: :0
> Mar 20 03:14:04 ubuntu bamfdaemon[9312]: cannot open display: :0
> Mar 20 03:14:04 ubuntu indicator-print[9315]: cannot open display: :0
> Mar 20 03:14:04 ubuntu compiz[9339]: Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/compiz (core) - Fatal: Couldn't open display :0
> Mar 20 03:14:04 ubuntu unity-panel-ser[9351]: cannot open display: :0
> Mar 20 03:14:04 ubuntu bamfdaemon[9362]: cannot open display: :0
> Mar 20 03:14:04 ubuntu indicator-print[9364]: cannot open display: :0
> Mar 20 03:14:04 ubuntu indicator-print[9396]: cannot open display: :0
> Mar 20 03:14:04 ubuntu unknown[9395]: cannot open display: :0
> Mar 20 03:14:04 ubuntu compiz[9416]: Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/compiz (core) - Fatal: Couldn't open display :0
> Mar 20 03:14:04 ubuntu unity-panel-ser[9428]: cannot open display: :0
> Mar 20 03:14:04 ubuntu compiz[9445]: Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/compiz (core) - Fatal: Couldn't open display :0
> Mar 20 03:14:04 ubuntu unity-panel-ser[9457]: cannot open display: :0
> Mar 20 03:14:05 ubuntu compiz[9475]: Invalid MIT-MAGIC-COOKIE-1 key/usr/bin/compiz (core) - Fatal: Couldn't open display :0
> Mar 20 03:14:05 ubuntu unity-panel-ser[9487]: cannot open display: :0