Version 1.1.0 will not start

Bug #1435635 reported by GVS on 2015-03-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Settings editor for LightDM GTK+ Greeter
Undecided
Unassigned

Bug Description

Xubuntu 14.04 AMD64

Version 1.1.0 of lightdm-gtk-greeter-settings will not start. All prior versions started fine.

Using the kalgasnik ppa to update to version 1.1.0 results in being prompted for one's root password via the pkexex dialogue, but the interface will not start. The policy kit file exists in usr/share/polkit-1.

I have tried to solve this for weeks and end up reverting back to the prior version which works fine.

Andrew P. (kalgasnik) wrote :

Please, run lightdm-gtk-greeter-settings-pkexec (and lightdm-gtk-greeter-settings) in terminal and post results here.

GVS (gvscheik1-g) wrote :

Sorry, I forgot to add this to the original post. Here is the terminal output from lightdm-gtk-greeter-settings-pkexec:

prodigal@GVS:~$ lightdm-gtk-greeter-settings-pkexec

** (lightdm-gtk-greeter-settings:5782): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-NzWnEceven: Connection refused

Here is the terminal output from lightdm-gtk-greeter-settings:

prodigal@GVS:~$ sudo lightdm-gtk-greeter-settings
[sudo] password for prodigal:

** (lightdm-gtk-greeter-settings:5930): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-NzWnEceven: Connection refused

Andrew P. (kalgasnik) wrote :

This warning is not fatal, so the reason is unclear.
Are you need to press Ctrl-C to return to command prompt? Maybe pplication starts but its window is invisible?
What exactly is "prior" version?

GVS (gvscheik1-g) wrote :

Yes, I need to hit CTRL-C to return to command prompt.

No, the window is not invisible. It does not exist. And, the process is not shown in Taskmanager. Whereas, the process does show in Taskmanager when running the prior version (version from ppa release before 1.1.0). I have 1.1.0 installed now so cannot say for sure what the exact version number was before 1.1.0.

I have always used the ppa to install the application, and have allowed all updates via the ppa. Only the latest version has ever given a problem.

Here is the output from running "lightdm-gtk-greeter-settings-pkexec" in a terminal, including what comes after hitting CTRL-C.

prodigal@GVS:~$ lightdm-gtk-greeter-settings-pkexec

** (lightdm-gtk-greeter-settings:13008): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-L8bwu2nZ3U: Connection refused
^CTraceback (most recent call last):
  File "/usr/bin/lightdm-gtk-greeter-settings", line 33, in <module>
    lightdm_gtk_greeter_settings.main()
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/__init__.py", line 68, in main
    window = GtkGreeterSettingsWindow.GtkGreeterSettingsWindow(mode=window_mode)
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/GtkGreeterSettingsWindow.py", line 85, in __new__
    window.init_window()
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/GtkGreeterSettingsWindow.py", line 189, in init_window
    self._read()
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/GtkGreeterSettingsWindow.py", line 209, in _read
    group.read(self._config)
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/OptionGroup.py", line 109, in read
    entry.value = value if value is not None else self._defaults[key]
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/OptionEntry.py", line 72, in value
    self._set_value(value if formatted is None else formatted)
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/IndicatorsEntry.py", line 295, in _set_value
    for options in self._read_options_string(value):
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/IndicatorsEntry.py", line 350, in _read_options_string
    name, s = self._next_string_token(s, ':;')
  File "/usr/lib/python3/dist-packages/lightdm_gtk_greeter_settings/IndicatorsEntry.py", line 394, in _next_string_token
    token.append(s[last: i if c in delimiters else i + 1].rstrip())
KeyboardInterrupt

Not sure if that tells you anything, but... :)

Andrew P. (kalgasnik) wrote :

Is it output of broken version? Post your lightdm-gtk-greeter.conf, maybe some option value causes the bug.

GVS (gvscheik1-g) wrote :

It is solved :)

Here is the offending line in lightdm-gtk-greeter.conf:

indicators = power;;~clock;~host;~power

I removed the extra semicolon and it starts as expected.

Note that I have never edited this file manually. However, I did use lightdm-gtk-greeter-settings to remove indicators. I am surprised this has not shown up before.

One final question: There is a file called "lightdm-gtk-greeter-ubuntu.conf" in the /etc/lightdm folder. Is it necessary? lightdm-gtk-greeter-settings seems to run fine without it, as does lightdm-greeter.

Thank you very much for taking the time to walk me through solving this! It is much appreciated :)

Andrew P. (kalgasnik) wrote :

Yep, this is it. The application falls into infinite loop if "indicators" key contains empty item.
Fix is already in the trunk, so ppa will be updated soon. Thanks for your help.

lightdm-gtk-greeter-ubuntu.conf isn't used by greeter or settings application, just "packaging" things.

Changed in lightdm-gtk-greeter-settings:
status: New → Fix Committed

Already installed new via ppa and works great. Thank you!

Gordon VS
<email address hidden>

On 15-03-25 07:28 AM, Andrew P. wrote:
> Yep, this is it. The application falls into infinite loop if "indicators" key contains empty item.
> Fix is already in the trunk, so ppa will be updated soon. Thanks for your help.
>
> lightdm-gtk-greeter-ubuntu.conf isn't used by greeter or settings
> application, just "packaging" things.
>
> ** Changed in: lightdm-gtk-greeter-settings
> Status: New => Fix Committed
>

Sean Davis (bluesabre) on 2015-05-21
Changed in lightdm-gtk-greeter-settings:
milestone: none → 1.2.0
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers