Bug #835202 “gwibber not refreshing twitter timeline” : Bugs : gwibber package : Ubuntu

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-10-03:

#1

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gwibber (Ubuntu):
status:	New → Confirmed

Revision history for this message

Marcin Juszkiewicz (hrw) wrote on 2011-11-16:

#2

I am running 12.04 and Gwibber is useless due to not refreshing Twitter.

Revision history for this message

harrykar (harrykar) wrote on 2011-11-20:

#3

same problem here https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/889947

Revision history for this message

Bilal Shahid (s9iper1) wrote on 2012-02-09:

#4

Thank you for taking the time to report this bug and helping to make Ubuntu better.
please elaborate to which you are calling timeline ?

Changed in gwibber (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

harrykar (harrykar) wrote on 2012-02-10:

#5

thank Bilal Shahid & /all you work on Gwibber.
"please elaborate to which you are calling timeline ?" i don't get what you mean. In case u meant Preferences>minutes between update refresh value here is set in 100. Anyway i menat about manual refresh CTRL-R and not automatic refresh. After i clicked CTRL-R in that case i got indefinitely the window u can see in screenshot in https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/889947. Anyway to mention that were a rare case(almost for me).

Regards
Harry G. Kar

Revision history for this message

Bilal Shahid (s9iper1) wrote on 2012-02-10:

#6

yes now i am able to reproduce it thanks for elaboration.
assigning it to kenvandine
ken:i have tested it and its confirm.

Changed in gwibber (Ubuntu):
importance:	Undecided → Low
status:	Incomplete → Triaged
Changed in gwibber:
importance:	Undecided → Medium
assignee:	nobody → Ken VanDine (ken-vandine)
Changed in gwibber (Ubuntu):
assignee:	nobody → Ken VanDine (ken-vandine)
Changed in gwibber:
status:	New → Confirmed

Revision history for this message

Ken VanDine (ken-vandine) wrote on 2012-02-10:

#7

Refresh is bound to F5, not Ctrl-R. If you look in the menu next to "Refresh" you will see the keyboard accelerator for that action.

Revision history for this message

harrykar (harrykar) wrote on 2012-02-11:

#8

Nope here (Lucid LTS) i have Ctrl-R not F5

Revision history for this message

Jose Gutierrez (jose.gutierrez) wrote on 2012-02-21:

#9

my twitter timeline is not updated or with F5, facebook account can not be added.

Revision history for this message

-- (234i234ij23lk4jv-sdvk) wrote on 2012-05-03:

#10

Download full text (15.4 KiB)

I'm running Arch Linux and my twitter timeline also doesn't refresh.

Output of gwibber:

(gwibber:15606): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed

(gwibber:15606): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed

(gwibber:15606): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed

(gwibber:15606): Json-CRITICAL **: json_object_has_member: assertion `object != NULL' failed

The last line appears repeatedly.

Output of gwibber-service -do:

root MainThread : INFO Logger initialized
Service MainThread : INFO Service starting
Service MainThread : INFO Running from the source tree
root MainThread : ERROR Could not find any typelib for Unity
root MainThread : ERROR Could not find any typelib for Dbusmenu
root MainThread : ERROR Could not find any typelib for Indicate
Digg MainThread : DEBUG Initializing.
Ping.FM MainThread : DEBUG Initializing.
FourSquare MainThread : DEBUG Initializing.
Qaiku MainThread : DEBUG Initializing.
Identica MainThread : DEBUG Initializing.
Twitter MainThread : DEBUG Initializing.
Facebook MainThread : DEBUG Initializing.
Buzz MainThread : DEBUG Initializing.
FriendFeed MainThread : DEBUG Initializing.
StatusNet MainThread : DEBUG Initializing.
Flickr MainThread : DEBUG Initializing.
Service MainThread : DEBUG Setting up monitors
Dispatcher MainThread : DEBUG NM Version is 0.9.4.0
Dispatcher MainThread : DEBUG NM Version is greater than 0.8.997
Storage MainThread : DEBUG Creating indexes
Dispatcher MainThread : DEBUG Refresh interval is set to 5
Dispatcher MainThread : DEBUG ** Starting Refresh - 2012-05-03 17:12:28.01 **
Dispatcher MainThread : INFO Running Jobs: 0
Dispatcher MainThread : INFO Running Jobs: 0
Dispatcher Thread-1 : DEBUG <twitter:receive> Performing operation
Dispatcher Thread-2 : DEBUG <twitter:responses> Performing operation
Dispatcher Thread-3 : DEBUG <twitter:private> Performing operation
Dispatcher Thread-4 : DEBUG <twitter:lists> Performing operation
Dispatcher Thread-5 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-6 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-7 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-8 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-10 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-9 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-11 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-12 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-13 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-14 : DEBUG <twitter:user_messages> Performing operation
Dispatcher Thread-15 : DEBUG <twitter:user_messages> Performin...

I'm running Arch Linux and my twitter timeline also doesn't refresh.

Output of gwibber:

(gwibber:15606): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed

(gwibber:15606): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed

(gwibber:15606): Gtk-CRITICAL **: gtk_radio_button_set_group: assertion `!g_slist_find (group, radio_button)' failed

(gwibber:15606): Json-CRITICAL **: json_object_has_member: assertion `object != NULL' failed

The last line appears repeatedly.

Output of gwibber-service -do:

root         MainThread  : INFO     Logger initialized
Service      MainThread  : INFO     Service starting
Service      MainThread  : INFO     Running from the source tree
root         MainThread  : ERROR    Could not find any typelib for Unity
root         MainThread  : ERROR    Could not find any typelib for Dbusmenu
root         MainThread  : ERROR    Could not find any typelib for Indicate
Digg         MainThread  : DEBUG    Initializing.
Ping.FM      MainThread  : DEBUG    Initializing.
FourSquare   MainThread  : DEBUG    Initializing.
Qaiku        MainThread  : DEBUG    Initializing.
Identica     MainThread  : DEBUG    Initializing.
Twitter      MainThread  : DEBUG    Initializing.
Facebook     MainThread  : DEBUG    Initializing.
Buzz         MainThread  : DEBUG    Initializing.
FriendFeed   MainThread  : DEBUG    Initializing.
StatusNet    MainThread  : DEBUG    Initializing.
Flickr       MainThread  : DEBUG    Initializing.
Service      MainThread  : DEBUG    Setting up monitors
Dispatcher   MainThread  : DEBUG    NM Version is 0.9.4.0
Dispatcher   MainThread  : DEBUG    NM Version is greater than 0.8.997
Storage      MainThread  : DEBUG    Creating indexes
Dispatcher   MainThread  : DEBUG    Refresh interval is set to 5
Dispatcher   MainThread  : DEBUG    ** Starting Refresh - 2012-05-03 17:12:28.01 **
Dispatcher   MainThread  : INFO     Running Jobs: 0
Dispatcher   MainThread  : INFO     Running Jobs: 0
Dispatcher   Thread-1    : DEBUG    <twitter:receive> Performing operation
Dispatcher   Thread-2    : DEBUG    <twitter:responses> Performing operation
Dispatcher   Thread-3    : DEBUG    <twitter:private> Performing operation
Dispatcher   Thread-4    : DEBUG    <twitter:lists> Performing operation
Dispatcher   Thread-5    : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-6    : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-7    : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-8    : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-10   : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-9    : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-11   : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-12   : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-13   : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-14   : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-15   : DEBUG    <twitter:user_messages> Performing operation
Dispatcher   Thread-16   : DEBUG    <twitter:search> Performing operation
Dispatcher   Thread-17   : DEBUG    <twitter:search> Performing operation
Dispatcher   Thread-18   : DEBUG    <twitter:search> Performing operation
Dispatcher   Thread-19   : DEBUG    <twitter:search> Performing operation
Dispatcher   Thread-20   : DEBUG    <twitter:search> Performing operation
Dispatcher   Thread-21   : DEBUG    <twitter:search> Performing operation
Dispatcher   Thread-22   : DEBUG    <twitter:search> Performing operation
Dispatcher   MainThread  : INFO     Running Jobs: 23
Dispatcher   Thread-23   : DEBUG    <twitter:search> Performing operation
Dispatcher   Thread-18   : INFO     Loading complete: 1 - 0
Dispatcher   Thread-18   : DEBUG    <twitter:search> Finished operation (0:00:00.625512)
Dispatcher   Thread-22   : INFO     Loading complete: 2 - 0
Dispatcher   Thread-22   : DEBUG    <twitter:search> Finished operation (0:00:00.637023)
Dispatcher   Thread-23   : INFO     Loading complete: 3 - 0
Dispatcher   Thread-23   : DEBUG    <twitter:search> Finished operation (0:00:00.668869)
Dispatcher   Thread-21   : INFO     Loading complete: 4 - 0
Dispatcher   Thread-21   : DEBUG    <twitter:search> Finished operation (0:00:00.706391)
Dispatcher   Thread-17   : INFO     Loading complete: 5 - 0
Dispatcher   Thread-17   : DEBUG    <twitter:search> Finished operation (0:00:00.737039)
Dispatcher   Thread-16   : INFO     Loading complete: 6 - 0
Dispatcher   Thread-16   : DEBUG    <twitter:search> Finished operation (0:00:00.776430)
Dispatcher   Thread-20   : INFO     Loading complete: 7 - 0
Dispatcher   Thread-20   : DEBUG    <twitter:search> Finished operation (0:00:00.771643)
Dispatcher   Thread-19   : DEBUG    <twitter:search> Adding record
Network      Thread-2    : ERROR    HTTP Error for https://api.twitter.com/1/statuses/mentions.json - error code: 400
Network      Thread-2    : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/mentions.json, error was: No JSON object could be decoded
Network      Thread-3    : ERROR    HTTP Error for https://api.twitter.com/1/direct_messages.json - error code: 401
Network      Thread-3    : DEBUG    Failed to parse the response for https://api.twitter.com/1/direct_messages.json, error was: No JSON object could be decoded
Network      Thread-4    : ERROR    HTTP Error for https://api.twitter.com/1/harrim4n/lists/subscriptions.json - error code: 400
Network      Thread-4    : DEBUG    Failed to parse the response for https://api.twitter.com/1/harrim4n/lists/subscriptions.json, error was: No JSON object could be decoded
Dispatcher   Thread-4    : ERROR    <twitter:lists> Operation failed
Dispatcher   Thread-4    : DEBUG    Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gwibber/microblog/dispatcher.py", line 81, in run
    message_data = PROTOCOLS[account["service"]].Client(account)(opname, **args)
  File "/usr/share/gwibber/plugins/twitter/__init__.py", line 411, in __call__
    return getattr(self, opname)(**args)
  File "/usr/share/gwibber/plugins/twitter/__init__.py", line 428, in lists
    following = self._get("%s/lists/subscriptions.json" % self.account["username"], "list") or []
  File "/usr/share/gwibber/plugins/twitter/__init__.py", line 394, in _get
    return [self._list(l) for l in data["lists"]]
TypeError: list indices must be integers, not str

Dispatcher   Thread-4    : INFO     Loading Error: 9 - Error
Dispatcher   Thread-4    : DEBUG    <twitter:lists> Finished operation (0:00:01.055003)
Network      Thread-5    : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-5    : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-15   : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-15   : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-8    : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-8    : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Dispatcher   Thread-19   : INFO     Loading complete: 9 - 1
Dispatcher   Thread-19   : DEBUG    <twitter:search> Finished operation (0:00:01.072689)
Dispatcher   Thread-2    : INFO     Loading complete: 9 - 0
Dispatcher   Thread-2    : DEBUG    <twitter:responses> Finished operation (0:00:01.127064)
Network      Thread-13   : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-13   : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-14   : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-14   : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-9    : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-9    : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-10   : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-10   : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-6    : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-6    : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-11   : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-11   : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-7    : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-7    : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-3    : ERROR    HTTP Error for https://api.twitter.com/1/direct_messages/sent.json - error code: 401
Network      Thread-3    : DEBUG    Failed to parse the response for https://api.twitter.com/1/direct_messages/sent.json, error was: No JSON object could be decoded
Dispatcher   Thread-3    : INFO     Loading complete: 10 - 0
Dispatcher   Thread-3    : DEBUG    <twitter:private> Finished operation (0:00:01.975154)
Network      Thread-12   : ERROR    HTTP Error for https://api.twitter.com/1/users/show.json - error code: 400
Network      Thread-12   : DEBUG    Failed to parse the response for https://api.twitter.com/1/users/show.json, error was: No JSON object could be decoded
Network      Thread-1    : ERROR    HTTP Error for https://api.twitter.com/1/statuses/home_timeline.json - error code: 401
Network      Thread-1    : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/home_timeline.json, error was: No JSON object could be decoded
Network      Thread-15   : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Dispatcher   Thread-1    : INFO     Loading complete: 11 - 0
Dispatcher   Thread-1    : DEBUG    <twitter:receive> Finished operation (0:00:02.026448)
Network      Thread-15   : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-15   : INFO     Loading complete: 12 - 0
Dispatcher   Thread-15   : DEBUG    <twitter:user_messages> Finished operation (0:00:01.984914)
Network      Thread-5    : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-5    : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-5    : INFO     Loading complete: 13 - 0
Dispatcher   Thread-5    : DEBUG    <twitter:user_messages> Finished operation (0:00:02.025670)
Network      Thread-8    : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-8    : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-8    : INFO     Loading complete: 14 - 0
Dispatcher   Thread-8    : DEBUG    <twitter:user_messages> Finished operation (0:00:02.019784)
Network      Thread-13   : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-14   : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-14   : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Network      Thread-13   : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-14   : INFO     Loading complete: 16 - 0
Dispatcher   Thread-14   : DEBUG    <twitter:user_messages> Finished operation (0:00:02.027006)
Dispatcher   Thread-13   : INFO     Loading complete: 16 - 0
Dispatcher   Thread-13   : DEBUG    <twitter:user_messages> Finished operation (0:00:02.028714)
Network      Thread-10   : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-10   : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-10   : INFO     Loading complete: 17 - 0
Dispatcher   Thread-10   : DEBUG    <twitter:user_messages> Finished operation (0:00:02.046751)
Network      Thread-11   : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-11   : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Network      Thread-9    : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-9    : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-11   : INFO     Loading complete: 19 - 0
Dispatcher   Thread-11   : DEBUG    <twitter:user_messages> Finished operation (0:00:02.088099)
Dispatcher   Thread-9    : INFO     Loading complete: 19 - 0
Dispatcher   Thread-9    : DEBUG    <twitter:user_messages> Finished operation (0:00:02.090093)
Network      Thread-7    : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-7    : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-7    : INFO     Loading complete: 20 - 0
Dispatcher   Thread-7    : DEBUG    <twitter:user_messages> Finished operation (0:00:02.114608)
Network      Thread-6    : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-6    : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-6    : INFO     Loading complete: 21 - 0
Dispatcher   Thread-6    : DEBUG    <twitter:user_messages> Finished operation (0:00:02.122529)
Network      Thread-12   : ERROR    HTTP Error for https://api.twitter.com/1/statuses/user_timeline.json - error code: 400
Network      Thread-12   : DEBUG    Failed to parse the response for https://api.twitter.com/1/statuses/user_timeline.json, error was: No JSON object could be decoded
Dispatcher   Thread-12   : INFO     Loading complete: 22 - 0
Dispatcher   Thread-12   : DEBUG    <twitter:user_messages> Finished operation (0:00:02.907457)

Revision history for this message

Andy Seaborne (andy-seaborne) wrote on 2012-05-17:

#11

Ubuntu 12.04
I have the same situation except it only occurs on one machine of two supposedly identical setups.
If there is anything I can do to provide information as to the difference in the two setups, please ask.

Revision history for this message

Ronald Blaschke (rblasch) wrote on 2012-07-24:

#12

Ubuntu 12.04 as well. Gwibber seems to have stopped updating some time ago. I am using a local Squid proxy.

"pkill gwibber-service; unset https_proxy && /usr/bin/gwibber-service -d -o" makes Gwibber update again.

Revision history for this message

Abhirav Kumar (akabhirav) wrote on 2015-06-05:

#13

For me gwibber isn't working at all its stuck as a new app. Heres what I get when I start gwibber from terminal

virtual void OnlineAccounts::Plugin::registerTypes(const char*) Ubuntu.OnlineAccounts
virtual void FriendsPlugin::registerTypes(const char*) Friends
virtual void OnlineAccountsClient::Plugin::registerTypes(const char*) Ubuntu.OnlineAccounts.Client
MODEL: "com.canonical.Friends.Streams"
MODEL: "com.canonical.Friends.Streams"
MODEL: "com.canonical.Friends.Streams"
STREAM: "reply_to/" ROWS: 0
SERVICE: "" ROWS: 0
STREAM: "mentions" ROWS: 0
SERVICE: "" ROWS: 0
account-service-model.cpp 292 update
account-service-model.cpp 292 update
account-service.cpp 100 setObjectHandle Accounts::AccountService(0x1cc2f90)
qml: Facebook Supports send
account-service.cpp 100 setObjectHandle Accounts::AccountService(0x19d2080)
qml: Twitter Supports send
qml: accounts.count: 2
static void StreamModelPrivate::onModelReady(GObject*, GParamSpec*, StreamModelPrivate*) 0
STREAM: "" ROWS: 0
SERVICE: "" ROWS: 0
static void StreamModelPrivate::onModelReady(GObject*, GParamSpec*, StreamModelPrivate*) 0
STREAM: "mentions" ROWS: 0
SERVICE: "" ROWS: 0
static void StreamModelPrivate::onModelReady(GObject*, GParamSpec*, StreamModelPrivate*) 0
STREAM: "reply_to/" ROWS: 0
SERVICE: "" ROWS: 0
file:///usr/share/friends-app/qml/ConversationDetails.qml:30:5: QML QQuickImage: Error downloading http://open.mapquestapi.com/staticmap/v4/getmap?size=160,160&zoom=12&center=0,0 - server replied: Forbidden

Ken VanDine (ken-vandine) on 2018-03-27

Changed in gwibber (Ubuntu):
assignee:	Ken VanDine (ken-vandine) → nobody
Changed in gwibber:
assignee:	Ken VanDine (ken-vandine) → nobody

Ubuntu
gwibber package

gwibber not refreshing twitter timeline

Bug Description

Duplicates of this bug

Other bug subscribers

Remote bug watches

	Status	Importance	Assigned to
Gwibber	Confirmed	Medium	Unassigned
gwibber (Arch Linux)	New	Undecided	Unassigned
gwibber (Ubuntu)	Triaged	Low	Unassigned

Ubuntugwibber package

gwibber not refreshing twitter timeline

Bug Description

Duplicates of this bug

Other bug subscribers

Remote bug watches

Ubuntu
gwibber package