Notifications are displayed in inverse order

Bug #499323 reported by Conscious User
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Undecided
Ken VanDine
One Hundred Papercuts
Fix Released
Low
Ken VanDine
gwibber (Ubuntu)
Fix Released
Low
Ken VanDine

Bug Description

When gwibber downloads more than one new post during a refresh, the notification bubbles are displayed in inverse order (earlier post after the later). I believe this is so because the notifications are emitted in the same order that the posts are rendered (from top to bottom). This should be fixed to avoid a sequence of notifications that make no sense in the case of related posts.

Revision history for this message
Conscious User (conscioususer) wrote :

I originally reported this for the 2.0 version in Ubuntu Karmic,
but I just want to register that the issue still happens in current
trunk as Lucid release is approaching.

Revision history for this message
Conscious User (conscioususer) wrote :

This bug is still present as of Lucid Alpha 3.

Revision history for this message
Boniek (boniek12p) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in gwibber (Ubuntu):
status: New → Confirmed
Changed in gwibber (Ubuntu):
importance: Undecided → Low
Revision history for this message
Omer Akram (om26er) wrote :

still an issue?

Revision history for this message
Michal Predotka (mpredotka) wrote :

Yes. I'm on Lucid.

Revision history for this message
Conscious User (conscioususer) wrote :

Yep.

Revision history for this message
Arturo Torres Sánchez (r2d2.art2005) wrote :

This bug remains on Lucid. If notifications are displayed inversely, they make no sense.

Revision history for this message
Xisberto (xisberto) wrote :

We have now several months after release of Lucid and the order is still inverted.

Revision history for this message
Omer Akram (om26er) wrote :

I see 2.30 branch linked. was there any commit made for this?

Revision history for this message
Xisberto (xisberto) wrote :

I'm on Gwibber 2.30.1 and Uubntu Lucid, and it's so annoying. The notification messages show replies and retweets before referred messages. It makes notification messages painful, because I need open the main Gwibber window to read the updates in "correct" order (from bottom to top).

Revision history for this message
Michael Rooney (mrooney) wrote :

This is true as of 2.30.1 in Lucid, as the previous commenter mentions. I just wanted to clarify that it happens in two different ways:
 * when messages are queued from different people, they are in reverse order. this is really confusing when people are replying to each other
 * if two messages are from the same person, they are put in one notification, but again in reverse order so that you have to read from bottom to top for logic. while gwibber works this way, I'm not sure that it makes sense for notifications to behave differently than other notifications as far as which direction you should read them.

Changed in gwibber:
status: New → Confirmed
Revision history for this message
Michael Rooney (mrooney) wrote :

I grepped through the logs of the linked branch and see no mention of this bug number, or the word "order". There are a bunch of references to notifications but none seem relevant. How odd.

I also nominated this bug as a papercut as it seems like a great candidate!

Changed in gwibber:
assignee: nobody → Ken VanDine (ken-vandine)
status: Confirmed → Fix Committed
Changed in gwibber (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
Changed in gwibber:
milestone: none → 2.31.4
Omer Akram (om26er)
Changed in gwibber (Ubuntu):
status: Confirmed → Triaged
Vish (vish)
Changed in hundredpapercuts:
assignee: nobody → Ken VanDine (ken-vandine)
importance: Undecided → Low
milestone: none → maverick-round-3-social-networking
status: New → Fix Committed
Changed in gwibber (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gwibber - 2.31.4-0ubuntu1

---------------
gwibber (2.31.4-0ubuntu1) maverick; urgency=low

  * New upstream release
    - Merged back in i18n fixes from before the sqlite merge, they seem to
      have gotten lost (LP: #538981)
    - Make "Lists" translatable
    - Make "Search" translatable
    - Order the result of new_items by time so we get notifications in the correct
      order (LP: #499323)
    - Only notify for the last 10 messages (except responses), as it is that is
      100 seconds of notifications displaying.
    - Always notify for responses (mentions)
    - Cache avatars for notifications and client (LP: #527446)
    - Fixed scrolling problems including scrollwheel support (LP: #611276)
  * debian/gwibber.desktop
    - Changed the key looked at for autostart
  * debian/control
    - Added depends on python-oauth, required for buzz
 -- Ken VanDine <email address hidden> Tue, 03 Aug 2010 16:27:45 -0400

Changed in gwibber (Ubuntu):
status: Fix Committed → Fix Released
Vish (vish)
Changed in hundredpapercuts:
status: Fix Committed → Fix Released
Changed in gwibber:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.