Maybe I can help ;) For me, my patch made this bug occur less often, but I still encounter this behaviour from time to time, too.
My problem is: I have no time to debug this further :/ @Илья Валеев: do you know how to reproduce this bug? A detailed list of steps could help Yann to debug this further. Additionally I would propose the following: Currently the deduplication of logged messages is done solely by using the time (+/- 5 minutes), the message text and the sender jid (of course). In my opinion it would be much better to use the same information as used in the deduplication of incoming messages I added some month ago. Especially the id of the message stanza would be interesting for deduplication. But I'm not sure if this would help solving this bug. @Yann, Илья Валеев: can we discuss this further in the bug report? This would keep all opinions about this in one place: https://trac.gajim.org/ticket/8277 tmolitor Am Sonntag, 15. Mai 2016, 16:19:30 schrieb Yann Leboulanger: > On 05/12/2016 03:28 AM, Илья Валеев wrote: > > 03.04.2016 19:55, Yann Leboulanger пишет: > >> On 04/02/2016 07:17 PM, Илья Валеев wrote: > >>> 30.03.2016 00:19, Yann Leboulanger пишет: > >>>> Ok so it's a MAM message you receive. I think this is something that > >>>> is fixed in our repository. You can try with the daily debian package, > >>>> that should fix your problem. > >>> > >>> Tested it with Gajim-2016.03.30, problem does not solved. Log (search by > >>> JID): > >>> > >>> <item subscription='both' name='Папа telegram' > >>> jid='cont...@telegram.xmpp'> > >>> <group>Telegram</group> > >>> </item> > >>> > >>> --------------------------------- > >>> > >>> <!-- In Сб 02 апр 2016 12:55:32 --> > >>> <presence from='cont...@telegram.xmpp' to='ilia@xmpp/hm' > >>> type='unavailable'> <c xmlns='http://jabber.org/protocol/caps' > >>> hash='sha-1' node='spectrum' ver='+KuUnE7eOpeLHeQAgmAJd6Uk+Q0='/> > >>> </presence> > >>> > >>> --------------------------------- > >>> > >>> <!-- In Сб 02 апр 2016 12:55:33 --> > >>> <message from='ilia@xmpp' to='ilia@xmpp/hm'> > >>> <result xmlns='urn:xmpp:mam:0' id='1459437047820609' queryid='190'> > >>> <forwarded xmlns='urn:xmpp:forward:0'> > >>> <delay xmlns='urn:xmpp:delay' stamp='2016-03-31T15:10:47.820609Z'/> > >>> <message xmlns='jabber:client' from='cont...@telegram.xmpp/bot' > >>> to='ilia@xmpp' type='chat'> > >>> <body>Ilia I am ready</body> > >>> </message> > >>> </forwarded> > >>> </result> > >>> </message> > >>> > >>> --------------------------------- > >>> > >>> <!-- In Сб 02 апр 2016 12:55:36 --> > >>> <presence from='cont...@telegram.xmpp/bot' to='ilia@xmpp/hm'> > >>> <x xmlns='vcard-temp:x:update'> > >>> <photo/> > >>> </x> > >>> <c xmlns='http://jabber.org/protocol/caps' hash='sha-1' node='spectrum' > >>> ver='+KuUnE7eOpeLHeQAgmAJd6Uk+Q0='/> > >>> </presence> > >>> > >>> > >>> > >>> There is only 1 message ("Ilia I am ready"), but I recieved it only > >>> once. Chat log: > >>> > >>> [15:11:20] Telegram contact: message 1 > >>> [15:11:39] Telegram contact: message 2 > >>> [16:50:24] ilia: ok > >>> [12:24:55] Telegram contact: Ilia I am ready > >>> # Turn computer to sleep mode, wake it next day and Gajim shows that > >>> there are 2 "new" messages: > >>> 2 days ago [04:53:11] Telegram contact: message 1 > >>> 2 days ago [04:53:31] Telegram contact: message 2 > >>> > >>> > >>> Any ideas what can it be? > >> > >> Unfortunately I have no idea what could happen. It seems Gajim shows > >> messages that is not received, so 2 possibilities: it gets it from local > >> logs, or notification events are not correctly cleaned and are > >> re-printed later somehow. > >> > >> There is a ticket about that: https://trac.gajim.org/ticket/8277, let's > >> continue discuss there > > > > Since I can not write to Gajim tracker, will write here. > > > > Gajim 0.16.5 snapshot from 2016.05.10 still have this issue on my > > Debian, but much less. Since building I got this only once (today) > > only from one contact. > > > > Can it happen due to blocking write permissions to some profile > > files/folders? There are: > > > > /home/ilia/.kde/share/apps/RecentDocuments > > > > /home/ilia/.recently-used > > > > /home/ilia/.local/share/recently-used.xbel > > I haven't seen your post in the spam logs. > We can't dbug things if information are in both places. > More information are needed, and I'm not able to really help as I never > reproduced the problem _______________________________________________ Gajim-devel mailing list Gajim-devel@gajim.org https://lists.gajim.org/cgi-bin/listinfo/gajim-devel
