@Ketil. Not all GUI's are created equally. There are over 114 people
reporting they are affected by this bug. I've been recreationally using linux
since the mid-90's and using it at work it since 1998 but it doesn't mean every
GUI is going to make sense to me. Maybe this workaround doesn't
Hello Ketil,
Can you confirm whether or not the procedures outlined above have worked
for you?
--
gwibber-accounts crashed with KeyError in get_account_data()
https://bugs.launchpad.net/bugs/552227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yes, and it also breaks ALL other app registrations in desktop couch's
config outside of ~. e.g. ubuntuone and others. Please do a little more
research and heed others findings before copping an attitude.
Thanks.
-T
--
gwibber-accounts crashed with KeyError in get_account_data()
This works great! I've linked this procedure to aid in the correction
of the following bug:
https://bugs.launchpad.net/bugs/552227
Just deleting the whole desktop-couch directories is very brute force
and could potentially break other applications registering themselves in
couchdb. Your method
This is now working for me using the daily and using the ubuntu
maintained package. Was a user error issue:
Facebook steps:
1. authorize
2. enter name and password
3-(6). Scroll to the bottom of each page and ensure you click Allow Access on
every gwibber page BEFORE clicking the ADD button on
No, its somewhat misleading at first glance. :)
From the beginning:
When you click Authorize there's no scrollbars yet, but when you click
Login with facebook type your name/password and hit the connect
button. The next screen it takes you to should let you scroll down. If
you do not see any
Depending on the number of attempts you guys have done, you may have to
do the bug workaround here:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/553226
I had to do this when I deleted my facebook account to re-add it trying
to document the steps I took. Doing this allowed me to
Here's a more in-depth triage effort to try depending on how much manual
manipulation you may have done to attempt to fix this issue. I broke
couchdb pretty bad by manually purging things from it out of my home
directory, not knowing it was a flat-database with a web front end.
The following
I tried this, it didn't work for me, which is why I suggest a full purge
of the app which will get ALL desktopcouch config files, even ones not
in ~. I think manually hacking around in the directory is exactly what
broke me.. Your mileage may vary..
--
gwibber-accounts crashed with KeyError in
Desktop Couch interacts with dbus. It's a flat database, just deleting
files will freak it out. There is a proper way to unregister
applications that use it...
http://www.freedesktop.org/wiki/Specifications/desktopcouch/Documentation/Troubleshooting
--
gwibber-accounts crashed with KeyError
Just downloaded the same daily build. Still no dice for me.
--
gwibber-accounts crashed with KeyError in get_account_data()
https://bugs.launchpad.net/bugs/552227
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
daily build bzr723 strace output:
Updating...
Saving...
Could not identify preference: username
Could not identify preference: session_key
Traceback (most recent call last):
File /usr/lib/python2.6/dist-packages/gwibber/accounts.py, line 184, in
on_edit_account_save
self.get_account_data()
I was unable to verify that this actually does work with the beta 2
Live-CD as indicated above. I am getting the exact same error message
on strace in a VM as I am on my physical machine with 10.04 beta 2
(upgraded)
--
gwibber-accounts crashed with KeyError in get_account_data()
Captured from tailed strace on gwibber when trying to add facebook
details:
-
Could not identify preference: username
Could not identify preference: session_key
Traceback (most recent call last):
File
I'm afraid I have to disagree that this issue is due to a failed
upgrade.
http://ubuntuforums.org/showthread.php?p=820#post820
I tried a clean install of devede where all the dependencies had to be
fetched from official repositories and I can reproduce this issue
exactly.
I cannot
Confirmed this on a fresh jaunty RC install, fully patched up to date.
explicitly launching it with python 2.6 has corrected the issue for me
thus far.
--
gourmet does not start on jaunty
https://bugs.launchpad.net/bugs/352678
You received this bug notification because you are a member of Ubuntu
Confirmed as well with x86_64 A8V_SLi Deluxe mainboard
--
[Hardy] Loading hardware drivers hangs while booting on latest kernel
(Bypassing causes XServer crash)
https://bugs.launchpad.net/bugs/213902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Correction, A8N_Sli Deluxe. Nvidia chipset.
--
[Hardy] Loading hardware drivers hangs while booting on latest kernel
(Bypassing causes XServer crash)
https://bugs.launchpad.net/bugs/213902
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
18 matches
Mail list logo
