Bug 2956 - Gajim works but shows several errors
Summary: Gajim works but shows several errors
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard:
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2011-10-06 21:43 CEST by Sébastien Chopin
Modified: 2011-11-01 19:54 CET (History)
4 users (show)

See Also:
Source RPM: gajim
CVE:
Status comment:


Attachments
gajim console output (1.71 KB, text/plain)
2011-10-25 01:26 CEST, Dave Hodgins
Details
locale command output (300 bytes, text/plain)
2011-10-25 01:29 CEST, Dave Hodgins
Details

Description Sébastien Chopin 2011-10-06 21:43:52 CEST
I'm under Mageia 1 32bits.
My Gajim works well but at the connection, it shows many times the same errors
:

Traceback (most recent call last):
  File "/usr/share/gajim/src/common/xmpp/idlequeue.py", line 530, in
_process_events
    return IdleQueue._process_events(self, fd, flags)
  File "/usr/share/gajim/src/common/xmpp/idlequeue.py", line 400, in
_process_events
    obj.pollin()
  File "/usr/share/gajim/src/common/xmpp/transports_nb.py", line 414, in pollin
    self._do_receive()
  File "/usr/share/gajim/src/common/xmpp/transports_nb.py", line 600, in
_do_receive
    self._on_receive(received)
  File "/usr/share/gajim/src/common/xmpp/transports_nb.py", line 614, in
_on_receive
    self.on_receive(data)
  File "/usr/share/gajim/src/common/xmpp/dispatcher_nb.py", line 467, in
_WaitForData
    res = self.ProcessNonBlocking(data)
  File "/usr/share/gajim/src/common/xmpp/dispatcher_nb.py", line 452, in
dispatch
    handler['func'](session, stanza)
  File "/usr/share/gajim/src/common/connection_handlers.py", line 1619, in
_messageCB
    jid, invite, tim)
  File "/usr/share/gajim/src/common/connection_handlers.py", line 1627, in
_on_message_decrypted
    self.dispatch_gc_message(msg, frm, msgtxt, jid, tim)
  File "/usr/share/gajim/src/common/connection_handlers.py", line 1759, in
dispatch_gc_message
    msg.getXHTML(), statusCode, displaymarking, captcha))
  File "/usr/share/gajim/src/common/connection.py", line 177, in dispatch
    gajim.ged.raise_event(event, self.name, data)
  File "/usr/share/gajim/src/common/ged.py", line 67, in raise_event
    handler(*args, **kwargs)
  File "/usr/share/gajim/src/gui_interface.py", line 988, in
handle_event_gc_msg
    displaymarking=array[6], captcha=array[7])
  File "/usr/share/gajim/src/groupchat_control.py", line 859, in on_message
    self.print_old_conversation(msg, nick, tim, None,
displaymarking=displaymarking)
  File "/usr/share/gajim/src/groupchat_control.py", line 931, in
print_old_conversation
    displaymarking=displaymarking)
  File "/usr/share/gajim/src/chat_control.py", line 846, in
print_conversation_line
    displaymarking=displaymarking)
  File "/usr/share/gajim/src/conversation_textview.py", line 1236, in
print_conversation_line
    timestamp_str = self.get_time_to_show(tim)
  File "/usr/share/gajim/src/conversation_textview.py", line 1309, in
get_time_to_show
    diff_day, {'nb_days': diff_day}, {'nb_days': diff_day})
  File "/usr/share/gajim/src/common/i18n.py", line 101, in ngettext
    text = text % replace_plural
TypeError: %d format: a number is required, not dict

I've heard the same bug with distributions Mandriva and NuTyX. In Mageia and NuTyX, an upgrade to Gajim 0.14.4 solves that problem.
Manuel Hiebel 2011-10-06 22:13:49 CEST

Assignee: bugsquad => misc
Source RPM: gajim-0.14.1 => gajim
Severity: normal => minor

Comment 1 Michael Scherer 2011-10-06 23:58:44 CEST
I see the same issue on fedora, running 0.14.3. I didn't identified yet the commit to fix this, but that's on my todo list since a few week.
Comment 3 Michael Scherer 2011-10-24 11:32:19 CEST
Ok, I upgraded to the latest bugixes release.

For QA :
Advisory 
---------

Gajim have been upgraded to the latest stable bugfixes release, to solve various minor problem. See the changelog on gajim website for more information, as well as the bug fro this upgrade.

Testing
---------

To test, one should simply connect to a muc ( read multi user ) room using gajim, but one without much activity. The bug is triggered by translation of the message "X days ago", wth X > 1. So by going on the various rooms, one is likely to trigger the popup ( I know one where it happen everytime but it is private ). To go in a room, just conect on gajim ( any xmpp account will be ok, gmail should work ), and then click on "join a discussion room", and choose "chat.jabberfr.org" for server. 

If no popup with "a error happened" appear when joining, the bug is fixed.
Michael Scherer 2011-10-24 11:32:41 CEST

Assignee: misc => qa-bugs

Comment 4 claire robinson 2011-10-24 14:15:38 CEST
I'm not sure where the message should appear but I'm so far unable to reproduce the error. I don't see anything anywhere which says anything like 'X days ago'.

Can you give an example of a room which is likely to trigger the error?
Comment 5 claire robinson 2011-10-24 14:43:35 CEST
Answer: No because you weren't in the CC list.

CC: (none) => misc

Comment 6 Michael Scherer 2011-10-24 19:14:48 CEST
When you connect to a jabber room, there is a short summary of the last discussion in the main windows, in a white/gray color. The time of last message is what trigger the error, but only if the message is old enough ( else, this show  "6 hours ago", etc ). I have no specific room to propose, so maybe the bug reporter can test and tell us if this is fixed for him ?
Comment 7 Dave Hodgins 2011-10-25 01:26:19 CEST
Created attachment 1003 [details]
gajim console output

Found a room that demonstrates the error.  Bookmarked it.
Installed the update.
Rejoined that same room.
Got this slightly different error.
Comment 8 Dave Hodgins 2011-10-25 01:29:08 CEST
Created attachment 1004 [details]
locale command output
Comment 9 claire robinson 2011-10-29 11:46:13 CEST
Sébastien a new version of Gajim is in Core Updates Testing, could you check that it has fixed the issue for you please?

I've been unable to reproduce it so far, mostly due to not finding the right room at the right time.
Comment 10 Sébastien Chopin 2011-10-29 12:22:25 CEST
Testing is not activated on my Mageia but errors have disappeared ... (Gajim 0.14.1) ... very nice job !
Comment 11 Dave Hodgins 2011-10-30 01:37:19 CEST
Claire, did you test on x86-64?

If yes, then I think we can go ahead and validate this update.
I got rid of the error in comment 8 by changing
export LC_TIME=en_DK # Show date as yyyy-mm-dd
to
export LC_TIME=en_DK.utf8 # Show date as yyyy-mm-dd
in my ~/.profile file.

CC: (none) => davidwhodgins

Comment 12 claire robinson 2011-10-30 02:26:27 CET
I haven't managed to replicate the problem but I'll check the update works tomorrow, I can't confirm the fix but if you've managed to do that i586 and it works x86_64 then we should probably validate it.

Sorry I've been up to my neck in wiki this last week.
Comment 13 claire robinson 2011-10-30 12:12:58 CET
Everything seems OK x86_64 with the update so I'll validate

Advisory 
---------

Gajim has been upgraded to the latest stable bugfix release to solve
various minor problems, including a crash when joining a multi user chat room with chat history over 1 day old. 

See the changelog on gajim website for more information, as well as the bug for this upgrade.

Gajim website: http://gajim.org
Mageia bug: https://bugs.mageia.org/show_bug.cgi?id=2956
-------------

SRPM: gajim-0.14.4-1.mga1.src.rpm


Could sysadmin please push from core/updates_testing to core/updates

Thankyou!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Hardware: i586 => All

Comment 14 Thomas Backlund 2011-11-01 19:54:59 CET
Update pushed.

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.