Gwibber doesn't refresh streams (unsupported locale/language error not handled)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Fix Released
|
Undecided
|
Unassigned | ||
gwibber (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: gwibber
When gwibber starts, it doesn't refresh at all. This is what I get when running it from the command line.
** (gwibber:14200): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:14200): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:14200): WARNING **: Trying to register gtype 'WnckWindowMove
Updating...
Updating...
ProblemType: Bug
Architecture: i386
Date: Fri Mar 5 21:55:56 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
NonfreeKernelMo
Package: gwibber 2.29.90.1-0ubuntu2
PackageArchitec
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: gwibber
Uname: Linux 2.6.32-14-generic i686
YaManicKill (yamanickill) wrote : | #1 |
John Vivirito (gnomefreak) wrote : Re: [Bug 533017] [NEW] Gwibber doesn't refresh streams | #2 |
Victor Vargas (kamus) wrote : Re: Gwibber doesn't refresh streams | #3 |
Please could you try to reproduce this issue in latest version of gwibber included in Lucid and check if this problem is still affecting you? I tried to reproduce your problem under 2.29.91 and gwibber take his time but my twitter account was refresh automatically (after 2-3 seconds aprox), Thanks in advance!
Changed in gwibber (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Incomplete |
YaManicKill (yamanickill) wrote : | #4 |
I don't know if this still happens, because it won't even startup now. Traceback:
** (gwibber:26856): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:26856): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:26856): WARNING **: Trying to register gtype 'WnckWindowMove
Updating...
Traceback (most recent call last):
File "/usr/bin/gwibber", line 67, in <module>
client.Client()
File "/usr/lib/
self.w = GwibberClient()
File "/usr/lib/
if len(json.
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
File "/usr/lib/
retval = candidate_
File "/usr/lib/
for account in self.accounts.
File "/usr/lib/
exists = self.view_
File "/usr/lib/
view_container = self.db[
File "/usr/lib/
resp, data = self.resource.
File "/usr/lib/
return self._request(
File "/usr/lib/
resp, data = _make_request()
File "/usr/lib/
body=body, headers=headers)
File "/usr/lib/
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/lib/
(response, content) = self._conn_
File "/usr/lib/
response = conn.getresponse()
File "/usr/lib/
method=
File "/usr/lib/
self.fp = sock.makefile('rb', 0)
AttributeError: 'NoneType' object has no attribute 'makefile'
Victor Vargas (kamus) wrote : | #5 |
is this issue still affecting you under gwibber 2.29.92? Thanks!
YaManicKill (yamanickill) wrote : | #6 |
Yes, I updated to the newest version, and it now starts, but it is still not refreshing streams at all. I deleted my config files, so it isn't any issue in there. It just isn't updating at all. No new errors either.
YaManicKill (yamanickill) wrote : | #7 |
This was fixed when I last could start gwibber. It was updating perfectly fine. Will let you know again when the other bug making it crash before it starts gets fixed. But I think it's done/
Andreas Hasenack (ahasenack) wrote : | #8 |
Today it's not refreshing. I have 2.29.94-0ubuntu1 in lucid.
Ketil Wendelbo Aanensen (ketilwaa-deactivatedaccount) wrote : | #9 |
I have not had Gwibber refreshing on Lucid at all yet. Using up-to-date packages in official Ubuntu repo, as well as Gwibber-daily ppa.
Lucid 32 bit, fresh install, brand new Gwibber settings.
(Gwibber also does not add Facebook account, does not post to neither Twitter nor Identi.ca, so it does **nothing at all**)
Omer Akram (om26er) wrote : | #10 |
I had such problems before but I never got such problem after updating to gwibber 2.29.95. Can you please quit gwibber and delete ~/.cache/
Andreas Hasenack (ahasenack) wrote : | #11 |
I did that (cleared desktop-couch files as suggested), let's see how it goes...
Panos Karampaglis (panosdotk) wrote : | #12 |
My Gwibber don't update twitter streams. My facebook account works fine. I have delete my accounts, delete desktop-couch files, and kill desktopcouch-
YaManicKill (yamanickill) wrote : | #13 |
Tried deleting those files, added my accounts again, and this is what I get from gwibber:
** (gwibber:16023): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:16023): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:16023): WARNING **: Trying to register gtype 'WnckWindowMove
Apache CouchDB has started, time to relax.
WARNING:root:Pid file does not contain int: '\n\n'
WARNING:root:Pid file does not contain int: '\n\n'
Browse your desktop CouchDB at file://
No dbus monitor yet
Updating...
Updating...
** (gwibber-
** (gwibber-
** (gwibber-
Updating...
Saving...
Saving...
Updating...
ERROR:dbus.
ERROR:dbus.
Omer Akram (om26er) wrote : | #14 |
YaManicKill, you should try to logout then login again. :)
YaManicKill (yamanickill) wrote : | #15 |
That broke it :-P now its not even starting. coming up with an error.
Omer Akram (om26er) wrote : | #16 |
YaManicKill, The latest version of gwibber for Lucid is 2.30.0.1 can you please update to it.
Panos Karampaglis (panosdotk) wrote : | #17 |
I have update to 2.30.0.1-0ubuntu1 with the same result. I get facebook updates but not on twitter. I delete my accounts, delete ~/.cache/
Panos Karampaglis (panosdotk) wrote : | #18 |
This is what I get when I start gwibber from command line
gwibber-service -o -d
Gwibber Dispatcher: DEBUG Refresh interval is set to 10
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Apr 15 22:38:02 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <facebook:images> Performing operation
Gwibber Dispatcher: DEBUG <facebook:receive> Finished operation
Gwibber Dispatcher: ERROR <facebook:images> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return [self._image(post, profiles) for post in data]
File "/usr/lib/
user = profiles[
KeyError: u'100000491319742'
Gwibber Dispatcher: INFO Loading complete: 3 - ['Failure', 'Success', 'Success', 'Success', 'Success', 'Failure'
YaManicKill (yamanickill) wrote : | #19 |
Updated, and still no success. Nothing obvious in the traceback.
Panos Karampaglis (panosdotk) wrote : | #20 |
After update desktopcouch to 0.6.4 my twitter is back
Panos Karampaglis (panosdotk) wrote : | #21 |
Sorry but after a few hours twitter updates stopped again
Nicolargo (nicolashennion) wrote : | #22 |
Same issue with Ubuntu 10.04, desktopcouch 0.6.4 and gwibber 2.30.0.1: twitter timeline is not refreshed.
===
Gwibber Dispatcher: INFO Loading complete: 2 - ['Success', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success']
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu Apr 29 09:58:06 2010 **
Gwibber Dispatcher: DEBUG <identica:receive> Performing operation
Gwibber Dispatcher: DEBUG <identica:
Gwibber Dispatcher: DEBUG <identica:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <identica:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <identica:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <identica:
Gwibber Dispatcher: DEBUG <twitter:
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
Gwibber Dispatcher: INFO Loading complete: 3 - ['Success', 'Success', 'Success', 'Failure', 'Success', 'Success', 'Success']
===
I also try to delete the cache file:
===
rm -rf ~/.cache/
===
Timeline is not refreched anymore...
peterkirn (peter-createdigitalmedia) wrote : | #23 |
I'm having this issue in the final release of Lucid, but only replies. Didn't realize this may be a duplicate:
https:/
On replies *only* I get the same message:
Gwibber Dispatcher: ERROR <twitter:responses> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
Changed in gwibber (Ubuntu): | |
importance: | Low → Medium |
Ed S (edgar-b-dsouza) wrote : | #24 |
Using 2.30.0.1-0ubuntu1 on Lucid, with only a Twitter account, I get the same error as in #23 and #22 above:
line 136, in _get
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
Looking at the source of the file, line 136 is the first line of an exception handler. It seems to expect that when an exception occurs, the content of the "data" variable is a dictionary with an "error" key. (This happens to be the case when authentication fails. When auth is successful, the timeline data is actually returned - I checked that with a temporary pprint.pprint(data) as the first line in the try block, then removed the line.)
The exception handler does not assign the exception to a variable, which would be useful for debugging (but, I think, not good for Python 3.x compatibility ... ?). For now, I modified the code like this:
import pprint #at top of file
...
...
# in the _get function:
# error is "Could not authenticate you" for failed auth
try:
if single: return [getattr(self, "_%s" % parse)(data)]
if parse: return [getattr(self, "_%s" % parse)(m) for m in data]
else: return []
except Exception, e:
print __file__, ": _get -- Exception: "
pprint.
# if data.has_
# if "authenticate" in data["error"]:
# raise exceptions.
After doing this, I ran gwibber-service in debug mode - with this output:
~$ gwibber-service -d -o
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Sun May 2 12:19:43 2010 **
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
/usr/lib/
Error('unsupported locale setting',)
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
/usr/lib/
Error('unsupported locale setting',)
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Success', 'Success', 'Success']
So it appears that it is a locale problem (?) that was not foreseen when writing the exception handler...
If someone could tell me how to check/change the locale on my system, I could change it and see if the problem is solved (for me). Other users posting on this bug could perhaps also check similarly to see if it is a locale setting that is causing the problem?
Is there any quick way to avoid this problem, other than waiting for translations for this particular locale to come out?
Thanks,
Ed.
Ed S (edgar-b-dsouza) wrote : | #25 |
Following up on #24:
I used System > Administration > Language support to re-order "English (India)" below the "English (United Kingdom)" and "English" entries. Applied System-wide. Switched to the Text tab, and chose "English (United States)". Applied System-wide. Logged out. Left the default "English (United States)" language setting for the session and entered login password. Tried the Broadcast window again. This time, timeline was properly displayed, as were replies to my tweets.
In my specific case, I confirm that:
- the code near line 136, in _get in gwibber/
- Changing the locale/language to en_US has temporarily solved my problem -- I can now see the Twitter timeline.
I have no idea what can be done in the Gwibber code :-( since I don't know much about the locale/language system, but I hope this information is of some assistance to Gwibber devs.
Thanks,
Ed.
Ed S (edgar-b-dsouza) wrote : | #26 |
Oh, and a couple more points I forgot to mention :-P
W.r.t. this code:
if data.has_
if "authenticate" in data["error"]:
raise exceptions.
1. When there is an authentication error with Twitter, the dictionary key seems to be "errors" and not "error" as is checked for. From a temporary pprint.
{u'errors': [{u'code': 32, u'message': u'Could not authenticate you.'}]}
2. The check for "authenticate" in data["errors"] (assuming key is changed as per point 1) seems it will not work, in this code. I tried this out in an interactive Python session:
~$ python
Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
[GCC 4.4.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> data = {u'errors': [{u'code': 32, u'message': u'Could not authenticate you.'}]}
>>> data
{u'errors': [{u'message': u'Could not authenticate you.', u'code': 32}]}
>>> 'authenticate' in data['errors']
False
Since you fine folks working on Gwibber will be working this area (soon, I hope), I hope you can also fix these issues at the same time.
Thanks very much,
Ed.
Changed in gwibber (Ubuntu): | |
status: | Incomplete → Confirmed |
Rohit (rohit-arondekar) wrote : | #27 |
I can confirm that the steps provided by #25 indeed do work and that Gwibber loads Twitter timeline as expected.
description: | updated |
summary: |
- Gwibber doesn't refresh streams + Gwibber doesn't refresh streams (unsupported locale/language error not + handled) |
Lê Kiến Trúc (le-kien-truc) wrote : | #28 |
I have just one Facebook account in gwibber and the last news from 10 days ago (May 03).
There is the error
** (gwibber:4127): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:4127): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:4127): WARNING **: Trying to register gtype 'WnckWindowMove
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.
ERROR:dbus.
/usr/bin/
gtk.main()
INFO:Gwibber GNOME Client:Gwibber Client closed
Sam St. James (samsaintjames) wrote : | #29 |
I'm also having this problem. When I first set up my twitter account in Gwibber running in lucid lynx it loaded the timeline and worked perfectly fine, but since after restarting it won't. No error messages are displayed. (I was also experiencing this running Gwibber in linux mint in virtual box, windows host.)
This is what is shown if I start it via the terminal:
** (gwibber:2582): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:2582): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:2582): WARNING **: Trying to register gtype 'WnckWindowMove
Updating...
Updating...
/usr/bin/
gtk.main()
** (gwibber:2582): CRITICAL **: murrine_
Vincent Hindriksen (vhindriksen) wrote : | #30 |
There are certainly some problems. Starting Gwibber gives some minor bugs and dbus-dependencies (dbus is sooo last year).
-------
$ gwibber
** (gwibber:8952): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:8952): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:8952): WARNING **: Trying to register gtype 'WnckWindowMove
No dbus monitor yet
Updating...
Updating...
ERROR:dbus.
ERROR:dbus.
/usr/bin/
gtk.main()
-------
Updating gives an error, also on line 136 like I see a lot in this bug-report.
-------
$ gwibber-service -o -d
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Thu May 27 15:57:37 2010 **
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <twitter:search> Performing operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if data.has_
AttributeError: 'list' object has no attribute 'has_key'
Gwibber Dispatcher: DEBUG <twitter:search> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Failure', 'Success', 'Success', 'Success']
-------
As a Java-programmer, Python is at least interesting for me, but I cannot fix it.
Isn't this just because network.Download is changed? That it used to return an Dictionary-object, and now a List?
Ed S (edgar-b-dsouza) wrote : | #31 |
@Vincent: Take a look at https:/
Hari Gangadharan (hari-g) wrote : | #32 |
Many are focusing on the three warning messages in the top. For everyone the issue seems to be slightly different. For me gwibber was failing in the line 284 of /usr/lib/
Failing error was:
File "/usr/lib/
self.
TypeError: WebKitWebView.
I did some debugging and found that the content has null in it.... I added a line before the line 284 to remove null:
(Sorry - I don't know python but my programming sense made me do this - probably there may be a better way)
# line added
content = content.
# existing line
self.load_
After that everything worked great for me.
Hari Gangadharan
mehul (mehul-forums) wrote : | #33 |
The solution provided by #25 does work.
After some digging around I found that the problem lies somewhere in the function parsetime in /usr/lib/
def parsetime(t):
loc = locale.
locale.
result = mx.DateTime.
locale.
return result.ticks()
In my case the locale was set to en_IN
locale.
throws an error
/usr/lib/
511 # convert to string
512 locale = normalize(
--> 513 return _setlocale(
514
515 def resetlocale(
Error: unsupported locale setting
But when locale is set to en_US.utf8 it works properly.
mehul (mehul-forums) wrote : | #34 |
Looks like this is the bug that is causing the problems
http://
Can someone try the patch that I have added. It seems to work for me so far.
mehul (mehul-forums) wrote : | #35 |
Ed S (edgar-b-dsouza) wrote : | #36 |
@mehul: great work troubleshooting and finding that Python bug! :) Sadly, it looks like the author of the module says he can't won't fix it :(
I stopped using Gwibber quite some time ago, or I would have definitely tried out your patch... hope someone will do that and report.
Cheers,
Ed.
Omer Akram (om26er) wrote : | #37 |
Ed S, if you dont use gwibber and you are not providing anything helpful to the bug. please dont spam. over the course of time its your third comment saysing "I stopped using gwibber". if you dont use it no need to tell everybody.
Ed S (edgar-b-dsouza) wrote : | #38 |
Omer Akram:
I believe that one should encourage people who are helping to solve/trying to help with, problems with FOSS. Since neither you nor other members of the Gwibber team have seen fit to *acknowledge*, let alone thank the patch contributor in this bug, I have taken the liberty of congratulating someone who is eager and trying to help sort out Gwibber problems, *despite* the fact that I no longer use it. (Ha! There's irony for you! A Gwibber team member doesn't care to thank contributors, but a non-user cares!)
There have been other patches beside this one. Those have had (AFAIK) the same lack of overt response from the team. How much encouragement or positive feedback have you, or any of the Gwibber team, given people who are trying to help out with the effort? As I write this, it is 40 days since I filed bug #574979, trying to help the Gwibber dev team by focusing attention on a bug that was hiding other bugs -- once solved, it would enable users to make USEFUL contributions in their bug reports (with meaningful stack traces in at least one tiny area of the vast project), instead of posting bug reports with erroneous stack traces.
I am not privy to the inner communications of the Gwibber team, so I do not know if that bug has had any effect at all. What I DO note is that there has been ZERO feedback, negative or otherwise, on that bug. And, since (as you have noted), I have stopped using Gwibber, I no longer look at the source code to see if the devs have fixed the issue. Many other projects' developers actually communicate on bug reports, even if it's a terse 'fixed in ver. x.y.z'. On the Gwibber bug reports that I'm subscribed to, I have seen zero such communications, which makes me feel that the Gwibber team doesn't even care about bug reports. I'm sure I'm not alone in this feeling.
I didn't expect instantaneous feedback to my bug (no. cited above). Nor, until you now gratuitously labeled my comments as "spam", did I mention the lack of attention. I understand that FOSS developers are busy people, and have multiple priorities, and moreover, that no user can *demand* attention to a particular bug or issue. That's fine; I respect the commitment and work of FOSS developers, including those working on Gwibber. However, if all the bug reports people make are (seemingly) ignored, then pray tell me what is the benefit of this system? If the bug reports are not being used for the purpose they were meant - interaction between developers and users in identifying and FIXING flaws in the code - then what is the use? And why may the bug-report comment system not be used by a non-Gwibber-user to praise the effort of other people in trying to help solve problems in Gwibber (even if it is ignored by the Gwibber team)??
I appreciate that you, Omer Akram, seem to be doing useful and good work related to Gwibber. However, despite your being a member of the Gwibber team, I see no evidence that you have brought relevant, possibly useful, patches and bugs to the notice of the developers. Maybe the Gwibber devs know all, and don't need bug reports? If so, it might save a lot of people's time if this is just made known to users. The attitude has fr...
Changed in gwibber: | |
status: | New → Fix Committed |
Tom "spot" Callaway (tcallawa) wrote : | #39 |
To my eyes, mehul's patch looks slightly wrong. Changing
- loc = locale.
+ loc = locale.
You really do want to be calling getlocale() there, if I'm reading that code right.
Omer Akram (om26er) wrote : | #40 |
fixed upstream. in gwibber 2.31.2 and 2.30.1
Changed in gwibber: | |
status: | Fix Committed → Fix Released |
Omer Akram (om26er) wrote : | #41 |
gwibber 2.30.1 is in Lucid proposed which fixes this issue.
Changed in gwibber (Ubuntu): | |
status: | Confirmed → Fix Committed |
Omer Akram (om26er) wrote : | #42 |
gwibber 2.30.1 is now in Lucid updates.
Changed in gwibber (Ubuntu): | |
status: | Fix Committed → Fix Released |
Erik Adler (erik-adler-sweden) wrote : | #43 |
Getting the same thing
** (gwibber:5794): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:5794): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:5794): WARNING **: Trying to register gtype 'WnckWindowMove
/usr/lib/
self.
Mathieu Carbou (mathieu-carbou) wrote : | #44 |
The issue is not resolved: Ubuntu Lucid, Gwibber 2.30.1
Twitter messages stopped updating. I've switched the language to only have English US, also deleted couchdb files in .local, .config and .cache and recreated all my accounts.
Nothing appears and nothing is refreshed.
kha@box:~$ gwibber -d
** (gwibber:13615): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:13615): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:13615): WARNING **: Trying to register gtype 'WnckWindowMove
Updating...
Updating...
/usr/bin/
gtk.main()
Mathieu Carbou (mathieu-carbou) wrote : | #45 |
Everything worked fine after installing Gwibber 2.31.91 from Gwibber Daily's PPA by executing these commands:
sudo apt-add-repository ppa:gwibber-
sudo apt-get update
sudo apt-get upgrade
kill all *couch* processes
logout / login
Pit Wenkin (pit-wenkin) wrote : | #46 |
When updating to daily (with Mathieu's instructions above) my twitter account was deleted in gwibber, but after i recreated it everything works fine.
Thanks
Michel Filipe (mfilipe) wrote : | #47 |
How Mathieu Carbou says: the issue is not resolved in Ubuntu Lucid (Gwibber 2.30.1).
Nic Brough (grobbendonk) wrote : | #48 |
Still broken in Gwibber 2.30.1 for me too.
Updating to the daily build as per Mathieu Carbou's instructions breaks Gwibber completely
** (gwibber:3343): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:3343): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:3343): WARNING **: Trying to register gtype 'WnckWindowMove
Traceback (most recent call last):
File "/usr/bin/gwibber", line 67, in <module>
client.Client()
File "/usr/lib/
self.w = GwibberClient()
File "/usr/lib/
self.setup_ui()
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
streams=
File "/usr/lib/
if not self.model_valid: self.refresh()
File "/usr/lib/
self.model = self.generate_
File "/usr/lib/
transients = json.loads(
File "/usr/lib/
return self._proxy_
File "/usr/lib/
**keywords)
File "/usr/lib/
message, timeout)
dbus.exceptions
File "/usr/lib/
(candidate_
File "/usr/lib/
raise UnknownMethodEx
UnknownMethodEx
Mathieu Carbou (mathieu-carbou) wrote : | #49 |
I think this issue is much more caused by a corruption in the couchdb database. Try deleting couchdb in folders ~/.local, ~/.config and ~/.cache, restart your computer and recreate all your accounts.
I did this before upgrading, if you read all my posts. Hope it helps...
Mathieu.
mortenbn (mortenbn76) wrote : | #50 |
Same Problem:
Ubuntu 10.10, Gwibber 2.32.0.1, Facebook + Twitter accounts.
mortenbn@ubuntu:~$ gwibber
** (gwibber:19944): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'
** (gwibber:19944): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
** (gwibber:19944): WARNING **: Trying to register gtype 'WnckWindowMove
error: line 6541: 0 is wrong flag id
error: line 9724: 0 is wrong flag id
error: line 9724: 0 is wrong flag id
error: line 10996: 0 is wrong flag id
error: line 10996: 0 is wrong flag id
error: line 11479: 0 is wrong flag id
error: line 11479: 0 is wrong flag id
error: line 15153: 0 is wrong flag id
error: line 15153: 0 is wrong flag id
error: line 19309: 0 is wrong flag id
error: line 22747: 0 is wrong flag id
error: line 22747: 0 is wrong flag id
error: line 25337: 0 is wrong flag id
error: line 25337: 0 is wrong flag id
error: line 26159: 0 is wrong flag id
error: line 26159: 0 is wrong flag id
error: line 27982: 0 is wrong flag id
error: line 30871: 0 is wrong flag id
error: line 30871: 0 is wrong flag id
error: line 34419: 0 is wrong flag id
error: line 34419: 0 is wrong flag id
error: line 55108: 0 is wrong flag id
error: line 55108: 0 is wrong flag id
error: line 56012: 0 is wrong flag id
error: line 56012: 0 is wrong flag id
error: line 59237: 0 is wrong flag id
error: line 59903: 0 is wrong flag id
error: line 59903: 0 is wrong flag id
error: line 60984: 0 is wrong flag id
error: line 60984: 0 is wrong flag id
error: line 66144: 0 is wrong flag id
error: line 66144: 0 is wrong flag id
error: line 66442: 0 is wrong flag id
error: line 66442: 0 is wrong flag id
error: line 66779: 0 is wrong flag id
error: line 69430: 0 is wrong flag id
error: line 69430: 0 is wrong flag id
error: line 74409: 0 is wrong flag id
error: line 74467: 0 is wrong flag id
error: line 74467: 0 is wrong flag id
error: line 84894: 0 is wrong flag id
error: line 89102: 0 is wrong flag id
error: line 89102: 0 is wrong flag id
error: line 90545: 0 is wrong flag id
error: line 90545: 0 is wrong flag id
error: line 96278: 0 is wrong flag id
error: line 96278: 0 is wrong flag id
error: line 98566: 0 is wrong flag id
error: line 98566: 0 is wrong flag id
error: line 99794: 0 is wrong flag id
error: line 99794: 0 is wrong flag id
error: line 100303: 0 is wrong flag id
error: line 100303: 0 is wrong flag id
error: line 104834: 0 is wrong flag id
error: line 104834: 0 is wrong flag id
error: line 106021: 0 is wrong flag id
error: line 106021: 0 is wrong flag id
error: line 109770: 0 is wrong flag id
error: line 109770: 0 is wrong flag id
error: line 111583: 0 is wrong flag id
error: line 111583: 0 is wrong flag id
error: line 121534: 0 is wrong flag id
error: line 121534: 0 is wrong flag id
error: line 124821: 0 is wrong flag id
error: line 124821: 0 is wrong flag id
error: line 128906: 0 is wrong flag id
error: line 128906: 0 is wrong flag id
error: line 129180: 0 is wrong flag id
error: line 129180: 0 is wrong flag id
error: line 130097: 0 is wrong flag id
error: line 130097: 0 is wrong flag id
error: li...
Alexandre BLANC (alexandre-inforeseau) wrote : Make it thicker and firmer | #51 |
..All bail___Customer
*******
Customers of «Can ed adia xz nPha om rmacy» onl sbq ine dru gp gst rii ore appreciate the opportunity to save money, quality of pharmaceutical products and speed of delivery when you order with «Can nwv adia ts nPha zi rmacy».
«Can nn adia mx nPha bh rmacy» guar aib antees fast delivery in discreet packaging and confidentiality of your private information. Visit our site to find the product you need, and you will be surprised by our prices. Customer service staff will help you with the initial order.
*******
It's time to start saving! ... www.bifxpills.ru
*******
On 03/05/2010 06:29 PM, YaManicKill wrote: ResizeMask' as enum when in fact it is of type 'GFlags' dules: nvidia ture: all ature: Ubuntu 2.6.32- 14.20-generic
> Public bug reported:
>
> Binary package hint: gwibber
>
> When gwibber starts, it doesn't refresh at all. This is what I get when
> running it from the command line.
>
> ** (gwibber:14200): WARNING **: Trying to register gtype
> 'WnckWindowState' as enum when in fact it is of type 'GFlags'
>
> ** (gwibber:14200): WARNING **: Trying to register gtype
> 'WnckWindowActions' as enum when in fact it is of type 'GFlags'
>
> ** (gwibber:14200): WARNING **: Trying to register gtype 'WnckWindowMove
> Updating...
> Updating...
>
> ProblemType: Bug
> Architecture: i386
> Date: Fri Mar 5 21:55:56 2010
> DistroRelease: Ubuntu 10.04
> InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
> NonfreeKernelMo
> Package: gwibber 2.29.90.1-0ubuntu2
> PackageArchitec
> ProcEnviron:
> LANG=en_GB.utf8
> SHELL=/bin/bash
> ProcVersionSign
> SourcePackage: gwibber
> Uname: Linux 2.6.32-14-generic i686
>
> ** Affects: gwibber (Ubuntu)
> Importance: Undecided
> Status: New
>
>
> ** Tags: apport-bug i386 lucid
>
I wish i didn't delete the bug from email but Ken had reported this i
think. If i find the duplicate i will mark it, unless someone else finds
it first
--
Sincerely Yours,
John Vivirito
https:/ /launchpad. net/~gnomefreak /wiki.ubuntu. com/JohnVivirit o
https:/
Linux User# 414246
"How can i get lost, if i have no where to go"
-- Metallica from Unforgiven III