I confirm what Bruno Leon stated. This bug is NOT fixed.
With package
gnome-keyring2.92.92.is.2.30.3-0ubuntu1.1
a default keyring file omissão.keyring (note the tilde...) is created
when I launch, for example, Evolution.
With this default file keyring usage is broken.
With a lucid install updated as of 2011/01/11, I still face the bug.
The package version is 2.92.92.is.2.30.3-0ubuntu1.1
Whenever I start a session, the NetworkManager (wich is the first in my
case to try accessing the keyring) creates a par_défaut keyring.
Any subsequent access to it fails.
** Changed in: gnome-keyring
Importance: Unknown = Critical
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
I've confirmed the fix on another lucid installation there as well now
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Description changed:
- Binary package hint: ubuntuone-client
-
- ubuntu1
-
- ProblemType: Crash
- DistroRelease: Ubuntu 10.04
- Package: ubuntuone-client-gnome 1.1.90-0ubuntu1
- ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
- Uname: Linux 2.6.32-19-generic i686
-
I've managed to reproduce the bug on a Lucid French installation and can
also confirm that the proposed package fixes the issue, marking this as
verification-done, thanks all.
** Tags added: verification-done
** Tags removed: verification-needed
--
ubuntuone-preferences crashed with
This bug was fixed in the package gnome-keyring -
2.92.92.is.2.30.3-0ubuntu1.1
---
gnome-keyring (2.92.92.is.2.30.3-0ubuntu1.1) lucid-proposed; urgency=low
* debian/patches/90_git_keyring_encoding.patch:
- git change to fix an encoding issue in the default keyring name storage
** Changed in: gnome-keyring
Status: New = Fix Released
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
** Patch added: debdiff for the stable update
http://launchpadlibrarian.net/52677130/gnome-keyring.debdiff
** Patch removed: debdiff for the stable update
http://launchpadlibrarian.net/52677124/gnome-keyring.debdiff
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
** Changed in: gnome-keyring (Ubuntu Lucid)
Status: Triaged = Fix Committed
** Patch added: debdiff for the stable update
http://launchpadlibrarian.net/52677124/gnome-keyring.debdiff
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
the change has been uploaded to lucid now
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
Trivial patch, easy to test, and gets quite some bad press, so marking
for the point release. We are still waiting for mysql anyway.
** Changed in: gnome-keyring (Ubuntu Lucid)
Milestone: lucid-updates = ubuntu-10.04.1
** Tags added: verification-needed
--
ubuntuone-preferences crashed
** Branch linked: lp:ubuntu/lucid-proposed/gnome-keyring
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
** Package changed: libgnome-keyring (Ubuntu) = gnome-keyring (Ubuntu)
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
upstream got a fix in git now which will be backported to lucid once
confirmed to work in the maverick upload
** Changed in: gnome-keyring (Ubuntu)
Milestone: lucid-updates = None
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
This bug was fixed in the package gnome-keyring -
2.92.92.is.2.30.3-0ubuntu2
---
gnome-keyring (2.92.92.is.2.30.3-0ubuntu2) maverick; urgency=low
* debian/patches/90_git_keyring_encoding.patch:
- git change to fix an encoding issue in the default keyring name storage
(lp:
** Branch linked: lp:ubuntu/gnome-keyring
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
the issue is not a desktopcouch one
** Changed in: gnome-keyring (Ubuntu Lucid)
Status: Confirmed = Triaged
** Bug watch added: GNOME Bug Tracker #624839
https://bugzilla.gnome.org/show_bug.cgi?id=624839
** Also affects: gnome-keyring via
hey there
something interesting here .
update everything includes the 2.6.32.22
fresh installed ubuntu ,everything work great no problem with network
manger.
i was installing upek fingerprint sensor and after i install it , it was
working perfectly .
the problem with network manager
it doesn't happen on a default installation
Do you mean a default *english* installation?
And do gnome-keyring support being called with UTF-8 filenames?
Because of course if it does not (which would be, to my point of view an
architectural error) clients should not call with UTF-8 name.
If
Do you mean a default *english* installation?
No, booting a french image of lucid, if the keyring is created by using
empathy for example it's named default.keyring, the issue is only
happening when ubuntuone-client is the first keyring client to be
started
--
ubuntuone-preferences crashed
Many thanks Sebastien.
I confirm that your workaround works fine.
I'll post your suggestion on the french forums, so that french people can now
enjoy Lucid with all the stuff going to keyring:
- U1,
- NM
- Empahty
- etc...
Nevertheless it does not prove that there is no bug in gnome-keyring. It
- do gnome-keyring handle UTF-8 filenames (maybe specification says it
does not... and thus client calling it with UTF-8 is buggy)
it seems it doesn't handle those correctly or this bug would not be
opened
- is specification says that gnome-keyring works with UTF-8 filenames,
try to call it
- do gnome-keyring handle UTF-8 filenames (maybe specification says it does
not... and thus client calling
it with UTF-8 is buggy)
it seems it doesn't handle those correctly or this bug would not be
opened
Wow... a program written in the 21st century that do not handle UTF-8.
Shouldn't
not sure it's a gnome-keyring issue, seems rather a buggy client asking
for this keyring name, it doesn't happen on a default installation
--
ubuntuone-preferences crashed with NoSuchKeyringError in __init__()
https://bugs.launchpad.net/bugs/553759
You received this bug notification because you
Why oh why oh why is gnome-keyring not using login.keyring for these
other langauges?
** Also affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided = High
** Changed in: gnome-keyring (Ubuntu)
Status:
This is actually occurring in desktopcouch. The ubuntuone-preferences
script is just importing the module, which is getting this exception
inside the module during import.
** Package changed: ubuntuone-client (Ubuntu) = desktopcouch (Ubuntu)
--
ubuntuone-preferences crashed with
** Also affects: desktopcouch (Ubuntu Lucid)
Importance: Undecided
Status: Confirmed
** Also affects: gnome-keyring (Ubuntu Lucid)
Importance: High
Status: Confirmed
** Changed in: gnome-keyring (Ubuntu Lucid)
Milestone: None = lucid-updates
--
ubuntuone-preferences
28 matches
Mail list logo
