Unity

On LTSP thick client gnome-settings-daemon gets loaded before unity-settings-daemon

Bug #1320286 reported by Charlie Ott on 2014-05-16

This bug affects 12 people

	Status	Importance	Assigned to
GNOME Settings Daemon	New	Undecided	Unassigned
Unity	Incomplete	Undecided	Unassigned
gnome-settings-daemon (Ubuntu)	Confirmed	Undecided	Unassigned
unity (Ubuntu)	Incomplete	Undecided	Unassigned
unity-settings-daemon (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

On amd64 ltsp fat client,

gnome-settings-daemon gets loaded before unity-settings-daemon, and thus unity-panel-service doesn't start at all.

manually running /usr/lib/unity/unity-panel-service after logging into the unity desktop is a work around the problem.

See original description

Charlie Ott (charlieott) on 2014-05-19

description:

updated

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-05-22:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity (Ubuntu):
status:	New → Confirmed

Andrea Azzarone (azzar1) on 2014-05-29

Changed in unity (Ubuntu):
status:	Confirmed → Invalid

Revision history for this message

Pavel Zakouřil (zakouril) wrote on 2014-05-30:

Why invalid ?

Revision history for this message

Andrea Azzarone (azzar1) wrote on 2014-05-30:

Because it should not be unity's fault. I already targeted the correct packages.

Revision history for this message

Charlie Ott (charlieott) wrote on 2014-06-25:

Following up with this bug... Is it an issue with 'unity-settings-daemon' or 'gnome-settings-daemon'?

Marco Trevisan (Treviño) (3v1n0) on 2014-08-06

Changed in unity (Ubuntu):
status:	Invalid → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-08-06:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-settings-daemon (Ubuntu):
status:	New → Confirmed
Changed in unity-settings-daemon (Ubuntu):
status:	New → Confirmed

Revision history for this message

Marco Trevisan (Treviño) (3v1n0) wrote on 2014-08-06:

Please, attach here the output of the following commands:
initctl list
initctl list-env

Changed in unity:
status:	New → Incomplete

Revision history for this message

Umberto Peserico (umberto-peserico) wrote on 2014-08-07:

form_the_server.txt Edit (3.5 KiB, text/plain)

Here the file with initclt commands on the server

Revision history for this message

Umberto Peserico (umberto-peserico) wrote on 2014-08-07:

from_a_client.txt Edit (3.5 KiB, text/plain)

Here the file with initctl commands on a client

Robert Ancell (robert-ancell) on 2014-09-23

no longer affects:

unity-settings-daemon

Revision history for this message

David Beveridge (dage) wrote on 2015-09-04:

#10

I had this problem on an LTSP server and I fixed it by creating a system-wide autostart entry for the panel like so

root@test-ltsp:/opt/ltsp/i386/etc/xdg/autostart# cat unity-panel-service.desktop
[Desktop Entry]
Type=Application
Exec=/usr/lib/unity/unity-panel-service
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name[en_AU]=Indicator
Name=Indicator
Comment[en_AU]=
Comment=

Revision history for this message

Andrey Konstantinov (andreyinvolute) wrote on 2016-04-12:

#11

Two years and it's undecided and unassigned? Does no one use LTSP anymore? We're experiencing this issue on a freshly installed and fully updated 14.04 with a 64-bit LTSP image. Something tells me that the same problem will probably persist even in 16.04...

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1353095

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.