You don't need to file another bug. I've reassigned this bug to
urlgrabber, you can update it's decription.
** Package changed: python-defaults (Ubuntu) => urlgrabber (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I removed packag 'python-gnomekeyring'
$ dpkg -S
/usr/lib/python2.7/dist-packages/gtk-2.0/gnomekeyring.sopython-gnomekeyring:
/usr/lib/python2.7/dist-packages/gtk-2.0/gnomekeyring.so
$ sudo dpkg -r python-gnomekeyring
$ pydoc -k cheezburger
WARNING: gnome-keyring:: couldn't connect to:
/run/us
Thank you. Now I see that this bug is not a duplicate.
I agree, that accessing keyring without a reason is rather scary
behaviour, but you probably assigned the bug to a wrong package. AFAIK
any application that loads keyring related library automagicaly tries to
access your keyring.
>From your s
Yes, I'm using a non-GNOME desktop. No, this is not a duplicate bug; if
that other bug is solved it would only obfuscate this bug.
My concern is that an application that should walk through only local
unencrypted files is asking for access to the GNOME keyring. I expect
the GNOME keyring is only
Are you using non-GNOME desktop? This bug is probably duplicate of bug
932177
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077533
Title:
pydoc complains it cant get into my gnome-keyring
To manag
attaching a systrace. Nothing pops out as obvious. The reading bytes
from /dev/urandom might be for some encryption purpose related to
whyever pydoc needs to get into my Gnome-keyring, but again, I can't
think of a not-scary reason why something that should be reading and
parsing text files needs
