Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 360747 - net-misc/gwibber-2.32.0.2: Twitter messages do not appear in the main Gwibber window.
Summary: net-misc/gwibber-2.32.0.2: Twitter messages do not appear in the main Gwibber...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Jesus Rivero (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-27 09:51 UTC by Stephen Griffiths
Modified: 2011-07-07 18:01 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Griffiths 2011-03-27 09:51:24 UTC
Hello, 

After I have launched Gwibber for the first time and have added a Twitter account, the interface launches but messages do not display. The only message that appears in the console is this: 

/usr/lib64/python2.7/site-packages/gwibber/gwui.py:726: GtkWarning: IA__gtk_range_set_range: assertion `min < max' failed 
  self.scrollbar.set_range(0, len(self.messages) - 1)

Any ideas what the problem is? Any more information needed?

Reproducible: Always
Comment 1 Christian Krause 2011-04-14 20:43:33 UTC
Same here...

~/.cache/gwibber/gwibber.log shows

2011-04-14 21:55:39,460 - Gwibber GNOME Client - INFO - Running from the system path
2011-04-14 21:55:57,318 - Gwibber GNOME Client - INFO - Gwibber Client closed
2011-04-14 21:56:11,221 - Gwibber GNOME Client - INFO - Running from the system path
2011-04-14 21:58:39,952 - Gwibber GNOME Client - INFO - Gwibber Client closed
2011-04-14 22:16:21,220 - Gwibber GNOME Client - INFO - Running from the system path
2011-04-14 22:16:23,156 - Gwibber Service - INFO - Running from the system path
2011-04-14 22:16:28,405 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.twitter.com
2011-04-14 22:16:28,405 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2011-04-14 22:16:28,405 - Gwibber Dispatcher - ERROR - Twitter unexpected result - No JSON object could be decoded
2011-04-14 22:16:28,408 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.twitter.com
2011-04-14 22:16:28,408 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2011-04-14 22:16:28,408 - Gwibber Dispatcher - ERROR - Twitter unexpected result - No JSON object could be decoded
2011-04-14 22:16:28,793 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.twitter.com
2011-04-14 22:16:28,793 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.twitter.com
2011-04-14 22:16:28,793 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2011-04-14 22:16:28,793 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2011-04-14 22:16:28,793 - Gwibber Dispatcher - ERROR - Twitter unexpected result - No JSON object could be decoded
2011-04-14 22:16:28,793 - Gwibber Dispatcher - ERROR - Twitter unexpected result - No JSON object could be decoded
2011-04-14 22:16:29,203 - Gwibber Dispatcher - ERROR - Failed to communicate with https://api.twitter.com
2011-04-14 22:16:29,203 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2011-04-14 22:16:29,203 - Gwibber Dispatcher - ERROR - Twitter unexpected result - No JSON object could be decoded
Comment 2 thelan 2011-06-10 19:43:12 UTC
It seems that you need to compile curl with gnutls support to solve this problem
Comment 3 Markos Chandras (RETIRED) gentoo-dev 2011-07-07 18:01:47 UTC
This should be fixed in 3.1.0