Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29817 - [gwibber] doesn't show any messages (at least tweets)

Attached to Project: Community Packages
Opened by Heiko Baums (cyberpatrol) - Wednesday, 09 May 2012, 16:26 GMT
Last edited by Balló György (City-busz) - Friday, 16 November 2012, 19:10 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Balló György (City-busz)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After granting gwibber 3.4.1-1 the access to my Twitter account it tries to refresh the messages, but doesn't show anything. It doesn't give any error message.

On the console I get these messages:
$ gwibber

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

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

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

And, btw., the Gwibber 3.4 series is marked as development versions. The 3.0 series is marked as the stable branch, so the latest stable version is 3.0.0.1. The problem with the "All downloads" link of launchpad is, that it doesn't distinguish between stable and development releases and calls all downloads "release" and only sorts by the "release date". So you have to read upstream's comments to find out what is what. See on the download page: "We encourage regular end users to run the 3.0 series, which has the latest stable code." But I couldn't test version 3.0.0.1, yet.
This task depends upon

Closed by  Balló György (City-busz)
Friday, 16 November 2012, 19:10 GMT
Reason for closing:  Fixed
Additional comments about closing:  gwibber 3.6 uses a completely different authentication system
Comment by Balló György (City-busz) - Wednesday, 09 May 2012, 18:22 GMT
I don't use Twitter, so I can't test it.

It seems that it was already reported to upstream by another Arch Linux user in comment #10:
https://bugs.launchpad.net/gwibber/+bug/835202

The download page is outdated. Gwibber follows the release schedule of GNOME: odd releases (3.1, 3.3) are development, even releases (3.0, 3.2, 3.4) are stable.
Comment by Heiko Baums (cyberpatrol) - Wednesday, 09 May 2012, 19:39 GMT
Regarding the release schedule: Where did you read this? I haven't found such a statement. Instead I found this:

https://twitter.com/settings/applications
Gwibber (Development)

http://gwibber.com/download/
Gwibber's source code is available from our Bazaar repository on Launchpad. We encourage regular end users to run the 3.0 series, which has the latest stable code.

https://launchpad.net/gwibber/3.0
Series: 3.0
Status: Supported

https://launchpad.net/gwibber/3.2
Series: 3.2
Status: Current Stable Release

https://launchpad.net/gwibber/3.4
Series: 3.4
Status: Active Development

So for me everything says, 3.4 is the development version and 3.0 resp. 3.2 is the stable version. I can't find any series 3.1, 3.3 and 3.5.
Comment by Alexander F. Rødseth (xyproto) - Monday, 16 July 2012, 11:31 GMT
He said the download page is outdated. As György is highly skilled, expresses himself accurately and is exceptionally knowledgeable when it comes to anything GNOME-related, I would take his word over a webpage any day.

About the problem itself, I just tested with a fresh install of Gwibber and a Twitter account, and it works here. Unable to reproduce.
Comment by Heiko Baums (cyberpatrol) - Monday, 16 July 2012, 13:14 GMT
@Alexander: So, you mean that György, an Arch Linux TU, has more knowledge about GNOME and Gwibber than the GNOME and Gwibber developers themselves? And if I look at György's PKGBUILDs in AUR, I really doubt that he is really that highly skilled. At least some of them are still not installable. Bugs mentioned in the AUR comments (not only by me) are still totally ignored and not fixed by him since months, etc. All that what I mentioned during the discussion period. So I really wouldn't call him "highly skilled". I would rather call him ignorant.

Back to this bug report, I gave 4 sources, which approve my considerations, György gave exactly no sources.

Btw., the links I posted are not only the "official" download page, but also the project pages. And, yes, they also say that the download page is outdated, but they also say that 3.4 is just the development release, but not the stable release. The stable release is still 3.2.
Comment by Alexander F. Rødseth (xyproto) - Monday, 16 July 2012, 20:48 GMT
The answer to your question is "no", and the question implies that the webpage is equvivalent to the knowledge the GNOME and Gwibber developers has, which I disagree with. Calling György ignorant is disprespectful and uncalled for. The amount of focus that is dedicated to the bug at hand and offtopic content is not balanced here, neither is the amount of text dedicated to details surrounding the issue instead of the issue itself. I'll try to counteract this by just concluding that I'm unable to reproduce the issue. Closing it as well, as this isn't a packaging issue but "upstream"/"works for me".
Comment by Heiko Baums (cyberpatrol) - Wednesday, 14 November 2012, 23:54 GMT
  • Field changed: Percent Complete (100% → 0%)
This was not ranting and it doesn't have anything to do with arch-general. This is a bug and having an unstable development version in the stable repos, in this case [community], is against the arch policies. And particularly if an unstable development version doesn't work because of a bug, this version in the repos has to be downgraded.

That's not ranting, that's fact.
Comment by Balló György (City-busz) - Thursday, 15 November 2012, 12:33 GMT
Please test gwibber 3.6.0-1.
Comment by Balló György (City-busz) - Friday, 16 November 2012, 19:09 GMT
gwibber 3.6 uses a completely different authentication system, so I hope that this problem was fixed.

Loading...