User Accounts endless loop (never opens)

[Israel Dahl]

When I open the control center and click on User Accounts, the User Accounts never open. It flashes and goes back to the control center screen. The program then becomes unable to be closed. I am required to kill the process manually.
I cannot open any other options, after I click on the User Accounts option.
All options do the same thing... flash their screen and return to the control center, except the ones that launch an external application (U1, Language settings, etc...)
Clicking on Time settings completely crashed the program, when it was in this state.
Normally EVERY option just works as expected (other than the User Accounts)

Obviously I am using Trusty (since this program just came into existence)
Installed: 14.04.3+14.04.20140305.1-0ubuntu1
Candidate: 14.04.3+14.04.20140305.1-0ubuntu1

I can provide any more info, and testing needed

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20140305.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 8 09:54:01 2014
InstallationDate: Installed on 2014-02-26 (10 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140224)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_unity-control-center:
 activity-log-manager 0.9.7-0ubuntu10
 deja-dup 29.5-0ubuntu2

[Gunnar Hjalmarsson (gunnarhj)]

Can you please start unity-control-center from a terminal window, and copy and paste the error messages resulting from an attempt to open User Accounts.

[Israel Dahl (israeldahl)]

$ unity-control-center
libwayland-egl.so.1: cannot open shared object file: No such file or directory
Failed to load module: /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so

//Then I select the Time and Date settings and the program crashes with this output:

(unity-control-center:28377): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed

(unity-control-center:28377): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'GtkToggleButton'

(unity-control-center:28377): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed

(unity-control-center:28377): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer

(unity-control-center:28377): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(unity-control-center:28377): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
libwayland-egl.so.1: cannot open shared object file: No such file or directory
Failed to load module: /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so
Segmentation fault (core dumped)

$ Failed to register: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

It looks like wayland is the problem.... I didn install Mir (but I haven't tested it yet) could that be the issue?

[Gunnar Hjalmarsson (gunnarhj)]

Well, libwayland-egl.so.1 is provided by the package libegl1-mesa-drivers, which simply must be there on a complete Ubuntu desktop. It looks like the location of the file was changed recently. Maybe your problem will be solved if you do

sudo apt-get update
sudo apt-get upgrade

[Israel Dahl (israeldahl)]

I do that everyday... unfortunately the problem exits still...
Could it be that installing the NVIDIA drivers did something unexpected. I had to install them because the 'suspend' feature is missing from the (otherwise better) nouveau...

$ lspci
...
01:00.0 VGA compatible controller: NVIDIA Corporation G84M [GeForce 8600M GT] (rev a1)
...

Would reinstalling the ubuntu-desktop package resolve this?

I usually do some pretty wild stuff to my installs, but this one has been very normal, and I only use one DE... so there is very little conflict, and I have not removed any programs.... this is a pretty fresh install.

[Gunnar Hjalmarsson (gunnarhj)]

I'm out of ideas then, sorry. Leaving it to the experts. :)

[Israel Dahl (israeldahl)]

oddly enough Cheese (the webcam program) will not run either, now, and it is also cannot find the same wayland egl library...

[Gunnar Hjalmarsson (gunnarhj)]

Just a thought... what about reinstalling libegl1-mesa-drivers?

sudo apt-get install --reinstall libegl1-mesa-drivers

[Israel Dahl (israeldahl)]

I had the same thought earlier today... unfortunately nothing happened after I reinstalled it... I haven't rebooted, though. I am not sure that that would make much of a difference since it is a library not a module... but I don't know that much about all the internals.

[Israel Dahl (israeldahl)]

https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1290099

Here is the other bug report...

Maybe I should report this under something else, like the libegl1-mesa-drivers ?

[Gunnar Hjalmarsson (gunnarhj)]

It's unity-control-center that crashes, so I would keep that bug task open for now.

However, you mentioned Nvidia... I recall from last year that a user reported that they downloaded Nvidia from some web site and installed from command line, resulting in a library file belonging to an Ubuntu package being removed. See bug #1002187 starting from comment #49.

Have you checked that libwayland-egl.so.1 (which should be a symlink) exists and links to the actual library file? What if you do

sudo updatedb
locate libwayland-egl.so.1

[Israel Dahl (israeldahl)]

I get:
/usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1
/usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1.0.0

So it IS there, and
I think we are getting closer, though...

I have also installed Skype (which starts just fine).
But I installed Skype from the Ubuntu repo, and I used the Additional Drivers tab to install the Nvidia drivers
version: 331.38
So..... maybe Nvidia is responisble for this somehow.

I was using the noveau drivers initially, (and would like to again) but my computer would simply hang when it went into suspend mode.

[Israel Dahl (israeldahl)]

That helped me out...
here is the workaround
https://bugs.launchpad.net/kubuntu-ppa/+bug/1206371/comments/17

ln -s /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1 /usr/lib/libwayland-egl.so.1

You are right about the link... somehow it became broken (or removed, really)

[Gunnar Hjalmarsson (gunnarhj)]

On 2014-03-09 23:40, Israel Dahl wrote:
> I used the Additional Drivers tab to install the Nvidia drivers
> version: 331.38
> So..... maybe Nvidia is responisble for this somehow.
> ...
> You are right about the link... somehow it became broken (or removed,
> really)

Ok, I added a nvidia task to this bug report.

[Israel Dahl (israeldahl)]

Thanks! Thanks for pointing me in the correct direction!
I am glad to be able to access the User Accounts (and cheese)

[Sebastien Bacher (seb128)]

Did any of you install libhybris? What's the output of "update-alternatives --list x86_64-linux-gnu_gl_conf" for you?

[Israel Dahl (israeldahl)]

output:
/usr/lib/nvidia-331-prime/ld.so.conf
/usr/lib/nvidia-331/ld.so.conf
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf

I didn't specifically install it, but it was installed

libhybris:
  Installed: 0.1.0+git20131207+e452e83-0ubuntu9
  Candidate: 0.1.0+git20131207+e452e83-0ubuntu9

The problem began around the time I installed the proprietary Nvidia drivers. Cheese stopped working, and I could no longer access the User Accounts. the workaround (making a symlink) fixed both problems.

[Sebastien Bacher (seb128)]

does it work if you uninstall nvidia-prime?

[Israel Dahl (israeldahl)]

I manually fixed it, so should I delete the linked file first, and then uninstall nvidia-prime?
It doesn't seem that deleting that would reinstall a linked file... but I will try it if you like

[Cecil Carpenter (cscj01)]

I have the same problem as originally described. However, I have the following message when running

unity-control-center user-accounts

in a terminal

My messages are

libwayland_ltst-client.so.0: cannot open shared object file: No such file or directory
Failed to load module: /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so

In my case, libwayland_ltst-client.so.0 is not in my system. In fact it belongs to a the package libwayland-ltst-client0 that is a Precise upgrade of the HWE to the Trusty stack. I upgraded from 12.04.5 -> 14.04.1. So I cannot understand why libwayland_ltst-client.so.0 is being called.

If I open Applications>Systems Settings>any other applet, they work. However, if I start User Accounts, the panel never comes up, and all apps no longer work even though their tab appears. If I try to kill the process, I have to do it over and over. I can also click the X on the window multiple times, and the window will eventually close.

Here is what I get if I use the dpkg command:

dpkg -s libwayland-ltst-client0
Package: libwayland-ltst-client0
Status: deinstall ok config-files
Priority: optional
Section: libs
Installed-Size: 90
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Multi-Arch: same
Source: wayland-lts-trusty
Version: 1.4.0-1ubuntu1~precise1
Config-Version: 1.4.0-1ubuntu1~precise1
Replaces: libwayland0-lts-trusty (<< 1.1.0-1)
Depends: libc6 (>= 2.14), libffi6 (>= 3.0.4)
Pre-Depends: multiarch-support
Conflicts: libwayland0-lts-trusty (<< 1.1.0-1)
Description: wayland compositor infrastructure - client library
 Wayland is a protocol for a compositor to talk to its clients as well
 as a C library implementation of that protocol. The compositor can be
 a standalone display server running on Linux kernel modesetting and
 evdev input devices, an X application, or a wayland client
 itself. The clients can be traditional applications, X servers
 (rootless or fullscreen) or other display servers.
 .
 This package ships the library that implements the client side of
 the Wayland protocol.
Homepage: http://wayland.freedesktop.org/
Original-Maintainer: Debian X Strike Force <email address hidden>

Here is dpkg for libwayland-client0.

dpkg -s libwayland-client0
Package: libwayland-client0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 90
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Multi-Arch: same
Source: wayland
Version: 1.4.0-1ubuntu1
Replaces: libwayland0 (<< 1.1.0-1)
Depends: libc6 (>= 2.14), libffi6 (>= 3.0.4)
Pre-Depends: multiarch-support
Conflicts: libwayland0 (<< 1.1.0-1)
Description: wayland compositor infrastructure - client library
 Wayland is a protocol for a compositor to talk to its clients as well
 as a C library implementation of that protocol. The compositor can be
 a standalone display server running on Linux kernel modesetting and
 evdev input devices, an X application, or a wayland client
 itself. The clients can be traditional applications, X servers
 (rootless or fullscreen) or other display servers.
 .
 This package ships the library that implements the c...

[Cecil Carpenter (cscj01)]

Sorry about thaT, BUT THE AND FINALLY SHOULD BE FOLLWED WITH THIS.

dpkg -s libwayland0
Package: libwayland0
Status: install ok installed
Priority: extra
Section: oldlibs
Installed-Size: 28
Maintainer: Ubuntu Developers <email address hidden>
Architecture: all
Source: wayland
Version: 1.4.0-1ubuntu1
Depends: libwayland-client0, libwayland-server0dpkg -s libwayland0
Package: libwayland0
Status: install ok installed
Priority: extra
Section: oldlibs
Installed-Size: 28
Maintainer: Ubuntu Developers <email address hidden>
Architecture: all
Source: wayland
Version: 1.4.0-1ubuntu1
Depends: libwayland-client0, libwayland-server0
Description: transitional dummy package
 This transitional dummy package is safe to remove.
Original-Maintainer: Debian X Strike Force <email address hidden>
Homepage: http://wayland.freedesktop.org/
Description: transitional dummy package
 This transitional dummy package is safe to remove.
Original-Maintainer: Debian X Strike Force <email address hidden>
Homepage: http://wayland.freedesktop.org/

[Cecil Carpenter (cscj01)]

And one last apology. I accidently hit the caps lock above.

[Cecil Carpenter (cscj01)]

What a day. I should have said I am running 14.04.1 x64 Gnome Flashback (Metacity).

[Cecil Carpenter (cscj01)]

I was just looking through this issue again, and I noticed Israel's output from

locate libwayland-egl.so.1

is

/usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1
/usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1.0.0

while the output from mine is

/usr/lib/x86_64-linux-gnu/libwayland-egl.so.1
/usr/lib/x86_64-linux-gnu/libwayland-egl.so.1.0.0

Is this a problem?

[Israel Dahl (israeldahl)]

Hi do you have an NVIDIA graphics card as well?
lspci | grep VGA
will give you the output.

Anyhow,
running:
ln -s /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1 /usr/lib/libwayland-egl.so.1
fixed it for me
maybe reversing it will fix it for you????
ln -s /usr/lib/libwayland-egl.so.1 /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1

it is worth a try I suppose... since it is a soft link you can always delete it if it doesn't work.
Though you might need to reboot to get it working.
Do you have libhybris installed as well?

[Cecil Carpenter (cscj01)]

I do have an Nvidia card:

lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)

Also

update-alternatives --list x86_64-linux-gnu_gl_conf
/usr/lib/nvidia-331-prime/ld.so.conf
/usr/lib/nvidia-331/ld.so.conf
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf

I added the link as you suggested ( ln -s /usr/lib/libwayland-egl.so.1 /usr/lib/x86_64-linux-gnu/mesa-egl/libwayland-egl.so.1). However, after reboot, I still have the same never ending loop with the following messages repeating for each loop:

Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 14: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not work as expected
libwayland_ltst-client.so.0: cannot open shared object file: No such file or directory
Failed to load module: /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so

As I mentioned earlier, my issue has to do with the fact that a Precise HWE update component is being called, namely libwayland_ltst-client.so.0. Why this is so, I have no idea, nor has anyone responded to a thread I opened on the Ubuntu forums here:

http://ubuntuforums.org/showthread.php?t=2245070

Once I get past that, it may be a link issue. But I think until then I will not know.

[Cecil Carpenter (cscj01)]

By the way, I do not have libhybris installed.

[Israel Dahl (israeldahl)]

hmmm,
locate libwayland_ltst-client.so.0
I think you may need to link that correctly...

I am guessing this is mainly a 64bit issue... my machine is 64bit, as your is.

I wonder what the problem is with this...
I know I installed something and then it happened... but I honestly don't know why this happens... :(

[Cecil Carpenter (cscj01)]

See reply #20 as to location of libwayland_ltst-client.so.0. That says

In my case, libwayland_ltst-client.so.0 is not in my system. In fact it belongs to the package libwayland-ltst-client0 that is a Precise upgrade of the HWE to the Trusty stack. I upgraded from 12.04.5 -> 14.04.1. So I cannot understand why libwayland_ltst-client.so.0 is being called.

As further explanation, I upgraded the HWE stack while still on Precise. That had libwayland_ltst-client.so.0 as part of the package. When I upgraded to Trusty, that package was removed. However, it seems

unity-control-center user-accounts

still expects the package to be present as it is calling libwayland_ltst-client.so.0. Something was obviously not upgraded properly, but I have no idea what that may be.

dpkg -s unity-control-center

gives the following:

Package: unity-control-center
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 4112
Maintainer: Ubuntu Desktop Team <email address hidden>
Architecture: amd64
Version: 14.04.3+14.04.20140604-0ubuntu1
Replaces: gnome-bluetooth (<< 3.4.0), gnome-control-center-unity, unity-control-center-datetime
Provides: gnome-control-center-unity, unity-control-center-datetime
Depends: session-migration, libaccountsservice0 (>= 0.6.34), libatk1.0-0 (>= 1.12.4), libc6 (>= 2.7), libcairo2 (>= 1.10.0), libcanberra-gtk3-0 (>= 0.25), libcanberra0 (>= 0.2), libcheese-gtk23 (>= 3.4.0), libcheese7 (>= 3.0.1), libcolord1 (>= 0.1.29), libcups2 (>= 1.6.0), libdbus-glib-1-2 (>= 0.78), libfontconfig1 (>= 2.9.0), libgdk-pixbuf2.0-0 (>= 2.23.0), libgl1-mesa-glx | libgl1, libglib2.0-0 (>= 2.37.3), libgnome-bluetooth11 (>= 3.4.0), libgnome-desktop-3-7 (>= 3.7.3), libgnome-menu-3-0 (>= 3.2.0.1), libgtk-3-0 (>= 3.10.0), libgtop2-7 (>= 2.22.3), libibus-1.0-5 (>= 1.5.1), libkrb5-3 (>= 1.8+dfsg), libnm-glib4 (>= 0.9.2.0+git201202091648.c24c4d4), libnm-gtk0 (>= 0.9.1.95), libnm-util2 (>= 0.9.1.90+git.20111206t233146.dff0d2a), libnotify4 (>= 0.7.3), libpango-1.0-0 (>= 1.18.0), libpangocairo-1.0-0 (>= 1.18.0), libpolkit-gobject-1-0 (>= 0.99), libpulse-mainloop-glib0 (>= 1:0.99.1), libpulse0 (>= 1:0.99.1), libpwquality1 (>= 1.1.0), libtimezonemap1 (>= 0.4.1), libunity-control-center1 (>= 14.04.0), libupower-glib1 (>= 0.9.2), libwacom2 (>= 0.7), libwebkitgtk-3.0-0 (>= 1.3.10), libx11-6, libxi6 (>= 2:1.2.99.4), libxml2 (>= 2.7.4), accountsservice, apg, desktop-file-utils, gkbd-capplet (>= 3.5.90), gnome-desktop3-data, gnome-icon-theme (>= 2.24), gnome-icon-theme-symbolic, gnome-menus (>= 2.12.0), unity-settings-daemon, gsettings-desktop-schemas (>= 3.5.91), gsettings-ubuntu-schemas (>= 0.0.1+14.04.20140224), ibus, indicator-bluetooth, indicator-datetime, indicator-keyboard, indicator-power, indicator-sound
Recommends: cups-pk-helper, gnome-session-bin, ubuntu-system-service, ibus (>= 1.5.0), iso-codes, mousetweaks, policykit-1-gnome, libcanberra-pulse, system-config-printer-gnome, gnome-control-center-shared-data
Suggests: gnome-screensaver | xscreensaver, gnome-user-guide | ubuntu-docs, gstreamer0.10-pulseaudio, libcanberra-gtk-module, x11-xserver-utils
Breaks: compiz (<< 1:0.9.8+bzr330), gnome-bluetooth (<< 3.4.0), gnome-power-mana...

[John Matthews (jymatthews)]

I'm having the same issue. Any developments? The symbolic link solution didn't work on my end. Thanks very much.

[Cecil Carpenter (cscj01)]

Absolutely nothing is happening. This is not even assigned to anyone, nor has anyone bothered to explain why a Precise component that was removed on update to Trusty is required of a system program/application on Trusty.

[Israel Dahl (israeldahl)]

Cecil,
It is (from my understanding of this bug) something to do with NVIDIA. and their drivers and the way they link with certain system libraries.

The people at Ubuntu do not make the proprietary NVIDIA drivers, so no one can be assigned. No one can fix this except Nvidia (AFAIK). It *may* be something as simple as an issue in the packaging, though it could be something as complex as the makefile having issues, or a problem in the code.
If it is a packaging issue, you may be able to fix it.... but I do not know.

That is the problem we face when being forced to use proprietary software. I cannot have suspend unless I use the proprietary driver. But when I use it the graphics have odd glitches and problems, there are these weird hard-to-solve bugs and there is no support. I suppose you could try to contact the NVIDIA developers, but that is possibly a dead end.

I have since updated to Utopic, so I cannot help much... sorry. You might find more answers using IRC #ubuntu on freenode
Just ask there and wait for someone to help. Alternatively you can try AskUbuntu.

When you find your fix, you should post it here for others in your situation

[Launchpad Janitor (janitor)]

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

[van hanegen (4997865862-o)]

Just the same issue - Ubuntu 14.04 (upgrade from 13.10), 32 bit, Nvidia 352.09 driver. And link decision proved useless in my case. I have almost the same system on the other machine - only instead of the nvidia driver is free - and there is no such problem at all

[van hanegen (4997865862-o)]

I was able to fix it by printing:
sudo apt-get install libwayland-dev-lts-trusty libwayland-egl1-mesa-lts-trusty
See https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1290099, post #7 by Cerin (chrisspen)

[Albert Cutrona (acutbal)]

Hello,

I've had the same problem and solved using the same solution detailed in https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1290099.

Thank you very much Cerin (chrisspen)!!

Best regards!!

[Lakshitha (lakshitha129)]

Thanks a lot Cerin (chrisspen) & van hanegen !!

It solved everything...

:-D

[Stanislav German-Evtushenko (giner)]

ubuntu-control-center and cheese have to depend on libwayland-egl1

$ ldd /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so | grep libwayland-egl
 libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007fd2cf3b9000)

giner@ginas-notebook:~$ ldd $(which cheese) | grep libwayland-egl
 libwayland-egl.so.1 => /usr/lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007f4551e9e000)