reproduced on openstack kvm w/ qxl driver, 64MB vram, ubuntu 14.04 mini
iso, with apt-get install xubuntu-desktop. verified qxl Xorg package is
installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
confirming on my setup as well.
openstack VM (similar to amazon ec2)
Running GDM3 (apt-get install gnome-shell) w/ NX Server to xorg-server-dummy
package (since vm is headless)
LDAP Authentication w/ SSSD Package
Once I connect to the server, I am able to log in the first time using my ldap
ac
** Also affects: gnome-keyring via
https://bugzilla.gnome.org/show_bug.cgi?id=730587
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321922
Title:
gno
Following up with this bug... Is it an issue with 'unity-settings-
daemon' or 'gnome-settings-daemon'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320286
Title:
On LTSP thick client gnome-setting
Since this is an upstream issue with gnome. I have created a report
here: https://bugzilla.gnome.org/show_bug.cgi?id=730587
** Bug watch added: GNOME Bug Tracker #730587
https://bugzilla.gnome.org/show_bug.cgi?id=730587
--
You received this bug notification because you are a member of Ubuntu
this is actually a bug in the gnome-keyring-daemon using sshfs. Reported
here: https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/1321922
** Changed in: ltsp (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Use whatever local installation you want, e.g. an ubuntu live cd
killall gnome-keyring-daemon
cd ~/.gnome2
mv keyrings keyrings.old
mkdir keyrings keyrings.new
chmod 700 keyrings keyrings.new
sshfs localhost:/home/username/.gnome2/keyrings.new keyrings
gnome-keyring-daemon -
Was able to create a thick client keyring by running 'seahorse' from the
LTSP server hosting the nbd & tftp services. Now when I open google
chrome, I am prompted to enter a password for the default keyring,
however it still hangs once i enter the correct password.
It seems like the thick client
Trying to run seahorse from the command line:
cott@ltsp550:~$ seahorse
** Message: init gpgme version 1.4.3
WARNING: gnome-keyring:: couldn't connect to:
/run/user/59319/keyring-rkuE0o/pkcs11: Connection refused
p11-kit: gnome-keyring: module failed to initialize, skipping: An error
occurred on
This is also in the /var/log/auth.log:
May 21 13:07:19 ltsp550 gnome-keyring-daemon[3892]: couldn't connect to control
socket at: /run/user/59319/keyring-rkuE0o/control: Connection refused
May 21 13:07:19 ltsp550 gnome-keyring-daemon[3892]: couldn't set environment
variable in session: Setenv in
Just tried to generate a fingerprint using gpg:
cott@ltsp550:~$ gpg --fingerprint
gpg: DBG: locking for `/home/cott/.gnupg/trustdb.gpg.lock' done via O_EXCL
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
Using Ubuntu 14.04 LTSP amd64 fat client with gnome-keyring
3.10.1-1ubuntu4
When launching something like Google Chrome (Which attempts to utilize
the gnome keyring), Creating a 'new' keyring password causes the tool to
hang. It also creates thousands of files labeled
Defaul
** Description changed:
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 system is a
- work around the problem.
+ manually running /us
Hmm... I see, the Unity Panel allows the User to enable the gnome screen
lock, which is not using SSSD (even though I have it installed) so it
just hangs in a loop when trying to unlock the screen.
Also the keyring seems to have the same problem, generating hundreds of
thousands of keyring.temp fi
Public bug reported:
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 system is a
work around the problem.
** Affects: unity (Ubuntu)
Import
Ah! Alkis you're the best. That was exactly the issue! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316320
Title:
Screen Lock does not prompt for password
To manage notifications about
In my environment, I wanted users to authenticate with thick clients
using their LDAP binding credentials.
I was able to enable SSSD authentication and add my LDAP cn to the
sudoers file on the fat client image. After doing an ltsp-update-image,
I am able to use the sudo command with the fat clie
I've noticed some errors that may be related inside the ~/.Xsession-
errors file:
Xsession: X session started for cott at Thu May 15 10:10:22 EDT 2014
localuser:cott being added to access control list
Script for ibus started at run_im.
Script for auto started at run_im.
Script for default started
I think the issue here is that since users on the Terminal server are
authenticated with sssd/ldap the client images need to be able to
authenticate as well.
As a temporary work around I have installed xscreensaver and sssd. With
the same sssd.conf from the server, the xscreensaver lock works jus
Installed using DVD for Ubuntu 14.04 Server Edition.
Intalled ltsp-server-standalone (with dhcpd) package using apt.
Hardware is an HP ProLiant DL380 G7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Public bug reported:
I am using LTSP fat clients, created with:
$ sudo ltsp-build-image --arch amd64 --fat-client-desktop ubuntu-desktop
LTSP server has sssd authentication utilizing pam and ldap. Users can
log in without issue and the home folder is available. Everything works
as expected exc
21 matches
Mail list logo
