Did not proper start gnome keyring

Bug #660003 reported by EricDHH
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
lxdm (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

Binary package hint: lxdm

eric@scylla:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

Could not use ubuntu-bug bout this package. Summary: Updated my eee from lubuntu 10.04 to 10.10. Now i have to reenter my umts pin every login, before the update this was done by gnome-keyring. The keyring works a bit, login to wifi works well with stored pass.
---
Architecture: i386
DistroRelease: Ubuntu 10.10
EcryptfsInUse: Yes
Package: lxdm 0.2.0-0ubuntu1-henry1
PackageArchitecture: i386
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.34-genusername 2.6.35.4
Tags: maverick
Uname: Linux 2.6.35-22-generic i686
UnreportableReason: Dies ist kein echtes Ubuntu-Paket
UserGroups: admin

Revision history for this message
EricDHH (ericdhh) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
EricDHH (ericdhh) wrote :

I have logon'ed several times to view what happens before the pin requester appears, There is a race condition, the modem-manager seems to start BEFORE the nm-applet occurs. So it got no pin from the networkmanager.

Revision history for this message
EricDHH (ericdhh) wrote :

My eee901go has an internal huawei, but with lubuntu 10.04 this bug it did not exist. Since 10.10 the modem-manager starts up before nm-applet and get no password to unlock the huawei card.

Revision history for this message
EricDHH (ericdhh) wrote :

Just installed lubuntu 10.10 to the fresh formatted eee901. The whole keyring was not unlocked after login. The bug is still alive in 10.10!!!

Revision history for this message
UndiFineD (k.dejong) wrote :

Hello Eric,

We also have an eeepc900, but without the huawei, I have an external stick.
you could install ' bum ' and make sure the modem-manager starts after nm-applet

Revision history for this message
EricDHH (ericdhh) wrote :

The problem is the missing interaction between 3 parts, so you have to do a logon triathlon.

1. you have to logon at lxdm
2. you have to logon at modemmanager
3. you have to logon at gnome keyring with same password as 1

Should be

1. logon at lxdm, this opens gnome keyring and this opens modemmanager

I installed pam keyring libs after that, but something is missing in the base config after all.

Revision history for this message
EricDHH (ericdhh) wrote :

Reverted the ee back to lubuntu 10.04 lts. Now the keyring is started well by gdm and modemmanager got his pass from the keyring. In 10.10 this is all messed up and lacks proper function.

Revision history for this message
Julien Lavergne (gilir) wrote :

This is a known problem in 10.10.
However, with recent udpates from gnome-keyring in Ubuntu Natty, I can't reproduce this problem any more, with a fresh install. Can someone confirm that this bug is gone in Ubuntu Natty ?

Changed in lxdm (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
IKT (ikt) wrote :

Is there a lubuntu 11.04 in the works?

Revision history for this message
Jared Norris (jarednorris) wrote :

Yes there is a Beta 2 release of Lubuntu currently available - for details see the mailing list post at https://lists.launchpad.net/lubuntu-desktop/msg03730.html as it has download links and other information. I'd highly recommend joining the mailing list if you're testing as it will give you details about any current known issues.

Revision history for this message
papukaija (papukaija) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 664206, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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