gajim issueshttps://dev.gajim.org/gajim/gajim/-/issues2017-12-11T16:38:55Zhttps://dev.gajim.org/gajim/gajim/-/issues/8251Inconsistency in Chat window Single Message history2017-12-11T16:38:55ZanonymousInconsistency in Chat window Single Message history# Bug description
After sending a Single Message, it shows in the Chat History for the user(s) you sent to with the Subject displayed as "Subject: xxxxxx" on the first line.
After receiving a Single Message, it shows in the Chat History...# Bug description
After sending a Single Message, it shows in the Chat History for the user(s) you sent to with the Subject displayed as "Subject: xxxxxx" on the first line.
After receiving a Single Message, it shows in the Chat History for the user you received it from *without* the Subject.
For both sending and receiving users the Subject is shown in the message history (i.e. it's in the log database, it's just the display in the Chat window that's not correct).
# Steps to reproduce
Send a single message from User A to User B
Open User A's chat history to User B, the subject of the Single Message is shown (outgoing).
Open User B's chat history from User A, no subject for the same Single Message is shown (incoming).
# Software versions
OS version:
Windows 7
GTK version:
2.24.10
PyGTK version:
2.24.00.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8345Gajim 0.16.5 - recipe for target 'install-recursive' failed2018-04-29T20:37:25ZanonymousGajim 0.16.5 - recipe for target 'install-recursive' failed# Bug description
Unable to compile from source 0.16.5 while 0.16.4 works with no problems
# Steps to reproduce
# Software versions
OS version: debian 8.4 x86_64
GTK version: 3.14.5-1+deb8u1,2.24.25-3+deb8u1
PyGTK version: (2, 24, 0)# Bug description
Unable to compile from source 0.16.5 while 0.16.4 works with no problems
# Steps to reproduce
# Software versions
OS version: debian 8.4 x86_64
GTK version: 3.14.5-1+deb8u1,2.24.25-3+deb8u1
PyGTK version: (2, 24, 0)0.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8315FT error2018-04-29T20:37:27ZanonymousFT errorsocks5 filetransfer: invalid error on socks stream negotiation failure
# Bug description
I was trying to send file from Psi to Gajim. Unfortunately something went wrong with s5b part and connection failed.
Gajim according to XEP had to ...socks5 filetransfer: invalid error on socks stream negotiation failure
# Bug description
I was trying to send file from Psi to Gajim. Unfortunately something went wrong with s5b part and connection failed.
Gajim according to XEP had to send item-not-found error but instead Psi received
\<iq xmlns="jabber:client" to="mylogin@gentoo.ru/dizzynb" type="error" id="ft_116e">
\<error code="404">Could not connect to given hosts\</error>
\</iq>
Moreover ft_116e is not even iq id. It's file transfer stream id.
# Steps to reproduce
1. Take Gajim 0.16.5 and the latest Psi (preferable from git).
2. Try to send file from Psi to Gajim
3. Make sure s5b is in use.
# Software versions
OS version:
Gentoo Linux
socks5, filetransfer0.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8314Gajim window size not restored properly when using "Single Window for Everyth...2018-04-29T20:37:27ZralfGajim window size not restored properly when using "Single Window for Everything"# Bug description
The gajim main (roster) window size is not restored properly when using "Single Window for Everything" for "Window behavior" and maximizing window.
# Steps to reproduce
This is when using xfwm as window manager.
* I...# Bug description
The gajim main (roster) window size is not restored properly when using "Single Window for Everything" for "Window behavior" and maximizing window.
# Steps to reproduce
This is when using xfwm as window manager.
* In preferences, set "Window behavior" to "Single Window for Everything"
* Maximize gajim
* Quit gajim
* Start gajim
Expected behavior:
Gajim should start maximized
Actual behavior:
Gajim starts with the roster window only as large as the roster.
# More information
Looking at the code, I think there are two independent issues here.
First of all, gajim does not properly remember the window width when using "Single Window for everything". The reason is this code in `prepare_quit` in `roster_window.py`:
width, height = self.window.get_size()
# For the width use the size of the vbox containing the tree and
# status combo, this will cancel out any hpaned width
width = self.xml.get_object('roster_vbox2').allocation.width
The width is first correctly determined to be "1920", but then overwritten with "236". I am inclined to just remove the second assignment to width; in principle, setting the window size to what it was should not need any cancelling of anything.
Secondly, gajim does not remember whether the window was maximized. This is relevant if the screen size changed since the last time gajim has been shown -- something which is very common e.g. on Laptops that are frequently used with an external screen, but also while traveling with the internal screen only.
# Software versions
OS version: Debian testing
GTK version: 2.24.300.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8313Over the line CPU usage2018-04-29T20:37:27ZanonymousOver the line CPU usage# Bug description
Python process consumes too much CPU time
No suspicious console output.
# Steps to reproduce
Build and run on Ubuntu 15.10
Connect to a server
Set window focus on another window
# Software versions
OS version:
Ubuntu 15...# Bug description
Python process consumes too much CPU time
No suspicious console output.
# Steps to reproduce
Build and run on Ubuntu 15.10
Connect to a server
Set window focus on another window
# Software versions
OS version:
Ubuntu 15.10
GTK+ Version: 3.18.6
PyGobject Version: 3.18.2
python-nbxmpp Version: 0.5.30.16.6https://dev.gajim.org/gajim/gajim/-/issues/8296Error while trying to delete a contact2020-02-23T12:23:28ZanonymousError while trying to delete a contact# Bug description
Error while trying to delete a contact.
# Steps to reproduce
The contact does not exist anymore on the ejabberd server.
Right click on the contact > Manage Contact > Remove > Validate
Traceback (most recent ...# Bug description
Error while trying to delete a contact.
# Steps to reproduce
The contact does not exist anymore on the ejabberd server.
Right click on the contact > Manage Contact > Remove > Validate
Traceback (most recent call last):
File "src\dialogs.py", line 1746, in on_response_ok
File "src\roster_window.py", line 3671, in on_ok
File "src\common\connection.py", line 2251, in unsubscribe
AttributeError: 'NoneType' object has no attribute 'delItem'
# Software versions
OS version: Windows 8.1
GTK version: 2.24.10
PyGTK version: 2.24.00.16.6https://dev.gajim.org/gajim/gajim/-/issues/8286Outgoing typing notifications are not being sent2018-04-07T22:19:13ZanonymousOutgoing typing notifications are not being sent# Bug description
Opening chat window with specific resource break outgoing typing notification
# Steps to reproduce
Connect from two or more resources of the same jid,
open chat windows for each resource
Outgoing typing notification w...# Bug description
Opening chat window with specific resource break outgoing typing notification
# Steps to reproduce
Connect from two or more resources of the same jid,
open chat windows for each resource
Outgoing typing notification will not be sent.
# Software versions
client built on latest snapshot.0.16.6https://dev.gajim.org/gajim/gajim/-/issues/8277Random old messages appear in open chat windows on reconnect (without smacks)2018-04-29T20:37:28ZThilo MolitorRandom old messages appear in open chat windows on reconnect (without smacks)# Bug description
When gajim reconnects, tries to resume via smacks and the smacks session is unknown something weird happens.
It correctly uses mam to load its history from the server and that seems to be correct (I looked at the xml c...# Bug description
When gajim reconnects, tries to resume via smacks and the smacks session is unknown something weird happens.
It correctly uses mam to load its history from the server and that seems to be correct (I looked at the xml console output).
But in my open chat windows old messages from days ago (8, 9 days old or even older) appear.
Those messages are *not* in the mam responses I see in the xml console.
And I even restarted my computer 3 days ago, so it seems to be something persistent across gajim restarts.
Only incoming messages appear that way, not even a single outgoing message.
And not all incoming messages since x days ago appear, but only random "blocks" of continous messages.
All stanzas sent and received in the last 2 months use uuids as ids.
So it cannot be a simple id clash of some sort (my first suspect when I saw this).
# Steps to reproduce
See above (but I'm not 100% sure if this is always the case).
# Software versions
OS version:
GTK version:
PyGTK version:0.16.6https://dev.gajim.org/gajim/gajim/-/issues/8276Last message correction does not seem to work on own messages from second client2018-04-29T20:37:28ZanonymousLast message correction does not seem to work on own messages from second client# Bug description
Last message correction does not seem to work on own messages from second client (with carbons).
http://www.xmpp.org/extensions/xep-0308.html
# Steps to reproduce
Start Gajim and log in with the same account. Send a me...# Bug description
Last message correction does not seem to work on own messages from second client (with carbons).
http://www.xmpp.org/extensions/xep-0308.html
# Steps to reproduce
Start Gajim and log in with the same account. Send a message from client 1. Correct message with client 1. Look in client 2, message was not corrected, instead both messages are displayed.
Android client Conversations seems to handle last message correction right in this case.
0.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8268Can’t detect gpg2 keys2018-04-29T20:37:28ZanonymousCan’t detect gpg2 keys# Steps to reproduce
1. Create a PGP key in Seahorse 3.18 GUI or using gpg2 directly
2. Open Gajim: Accounts: Personal: OpenPGP
Expected: List to include my gpg2 key.
Actual: No pgp keys found.
Work-around: Convert key from gpg2 to gp...# Steps to reproduce
1. Create a PGP key in Seahorse 3.18 GUI or using gpg2 directly
2. Open Gajim: Accounts: Personal: OpenPGP
Expected: List to include my gpg2 key.
Actual: No pgp keys found.
Work-around: Convert key from gpg2 to gpg. Though all other software on my system that uses PGP keys (except gajim and git) now default to gpg2.
# Software versions
OS version: Fedora 23
GTK version: 2.24.29
PyGTK version: 2.24.00.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8265Exception on cancelled file transfer2018-04-29T20:37:28ZanonymousException on cancelled file transfer# Bug description
Gajim 0.16.5-a43f0fa77a26
Traceback (most recent call last):
File "/usr/share/gajim/src/dialogs.py", line 1568, in on_response_cancel
self.user_response_cancel[0](*self.user_response_can...# Bug description
Gajim 0.16.5-a43f0fa77a26
Traceback (most recent call last):
File "/usr/share/gajim/src/dialogs.py", line 1568, in on_response_cancel
self.user_response_cancel[0](*self.user_response_cancel[1:])
File "/usr/share/gajim/src/filetransfers_window.py", line 466, in on_response_cancel
gajim.connections[account].send_file_rejection(file_props)
File "/usr/share/gajim/src/common/protocol/bytestream.py", line 202, in send_file_rejection
jingle = self._sessions[file_props.sid]
KeyError: u'l8edm52t11'
# Steps to reproduce
1. Ask a contact to send you a file via jingle
2. Go get something to eat
3. Cancel the file transfer after an hour or so
# Software versions
OS version:
(unrelated)
GTK version:
(unrelated)
PyGTK version:
(unrelated)0.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8258display message receipt (xep 0184) for carbon copied messages2018-04-29T20:37:28ZThilo Molitordisplay message receipt (xep 0184) for carbon copied messages# Bug description
This patch adds XEP-0184 message receipt display for carbon copied messages and disables notification for carbon copied messages sent from other ressources.
# Steps to reproduce
# Software versions
OS version:
GTK v...# Bug description
This patch adds XEP-0184 message receipt display for carbon copied messages and disables notification for carbon copied messages sent from other ressources.
# Steps to reproduce
# Software versions
OS version:
GTK version:
PyGTK version:0.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8222"error while sending message ( recipient-unavailable )" randomly shows up in ...2018-04-29T20:37:30Zralf"error while sending message ( recipient-unavailable )" randomly shows up in chat window# Bug description
The message "error while sending message ( recipient-unavailable )" randomly shows up in chat windows sometimes. This also happened when I didn't send any message to that contact recently, so I have no idea what's actu...# Bug description
The message "error while sending message ( recipient-unavailable )" randomly shows up in chat windows sometimes. This also happened when I didn't send any message to that contact recently, so I have no idea what's actually causing the problem here. Even when starting gajim on the console, no error is logged there.
The particularly annoying aspect of this bug is that this message causes a "new message" notification, the window gets highlighted and the tray icon blinks.
I guess what I'm mostly asking about right now is to make the error message more informative.
# Steps to reproduce
No idea.
# Software versions
OS version: Debian testing
GTK version: 2.24.29
PyGTK version: 2.24.00.16.6https://dev.gajim.org/gajim/gajim/-/issues/8220Last Message Correction does not apply to own contact2018-04-29T20:37:30ZDarlanLast Message Correction does not apply to own contact# Bug description
Last Message Correction does not apply against own contact. User (partially applied), Remote-end (not applied).
User (13 lines)
[09:37:45] Darlan: ping 12 (LMC_ICON)
[09:36:49] Darlan: ping 1
...# Bug description
Last Message Correction does not apply against own contact. User (partially applied), Remote-end (not applied).
User (13 lines)
[09:37:45] Darlan: ping 12 (LMC_ICON)
[09:36:49] Darlan: ping 1
[09:36:59] Darlan: ping 2
[09:37:06] Darlan: ping 3
[09:37:10] Darlan: ping 4
[09:37:13] Darlan: ping 5
[09:37:20] Darlan: ping 6
[09:37:24] Darlan: ping 7
[09:37:28] Darlan: ping 8
[09:37:31] Darlan: ping 9
[09:37:35] Darlan: ping 10
[09:37:41] Darlan: ping 11
[09:37:46] Darlan: ping 12
Remote end (12 lines)
[09:38:20 AM] Darlan: ping 1
[09:38:29 AM] Darlan: ping 2
[09:38:36 AM] Darlan: ping 3
[09:38:40 AM] Darlan: ping 4
[09:38:44 AM] Darlan: ping 5
[09:38:51 AM] Darlan: ping 6
[09:38:54 AM] Darlan: ping 7
[09:38:58 AM] Darlan: ping 8
[09:39:01 AM] Darlan: ping 9
[09:39:05 AM] Darlan: ping 10
[09:39:11 AM] Darlan: ping 11
[09:39:16 AM] Darlan: ping 12
# Steps to reproduce
Connect from two resources.
Correct a message against own contact in MUC.
# Software versions
OS version: Salix OS 14.1 (Slackware 14.1 based)
GTK version: 2.24.20
PyGTK version: 2.24.00.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8215Programming error on attempt to open nickname dialog twice2018-04-29T20:37:30ZDarlanProgramming error on attempt to open nickname dialog twice# Bug description
Traceback (most recent call last):
File "/usr/share/gajim/src/groupchat_control.py", line 2219, in _on_change_nick_menuitem_activate
gajim.interface.instances['change_nick_dialog'].present...# Bug description
Traceback (most recent call last):
File "/usr/share/gajim/src/groupchat_control.py", line 2219, in _on_change_nick_menuitem_activate
gajim.interface.instances['change_nick_dialog'].present()
AttributeError: ChangeNickDialog instance has no attribute 'present'
# Steps to reproduce
1. Join to a chat room;
2. Hover mouse on banner;
3. Click on menu item to change nickname;
4. Repeat the above steps.
# Software versions
OS version: Salix OS 14.1 (Slackware 14.1 based)
GTK version: 2.24.20
PyGTK version: 2.24.00.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8211Do not allow drag-n-drop a group onto an own subgroup and onto itself2018-04-29T20:37:30ZDarlanDo not allow drag-n-drop a group onto an own subgroup and onto itself# Bug description
Dragging and dropping a group onto its own and then onto an own subgroup leads to the creation of a new group that can get to `Gajim::Gajim::Gajim::Gajim::Gajim`, and eventually cause to a programming error upon retriev...# Bug description
Dragging and dropping a group onto its own and then onto an own subgroup leads to the creation of a new group that can get to `Gajim::Gajim::Gajim::Gajim::Gajim`, and eventually cause to a programming error upon retrieving roster after login.
Traceback (most recent call last):
File "/usr/share/gajim/src/roster_window.py", line 4210, in on_roster_treeview_row_expanded
self.tree.expand_row(path, False)
TypeError: could not convert path to a GtkTreePath
To fix this, user needs to drag-n-drop the most recent unwanted new group row onto account row.
# Steps to reproduce
Drag-n-drop a group onto its own and then onto an own subgroup or.
# Software versions
OS version: Salix OS 14.1 (Slackware 14.1 based)
GTK version: 2.24.20
PyGTK version: 2.24.00.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8210Programming error on initiating a Jingle session2018-04-29T20:37:30ZDarlanProgramming error on initiating a Jingle session# Bug description
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/nbxmpp/dispatcher_nb.py", line 495, in dispatch
handler['func'](session, stanza)
File "/usr/share/gajim/...# Bug description
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/nbxmpp/dispatcher_nb.py", line 495, in dispatch
handler['func'](session, stanza)
File "/usr/share/gajim/src/common/jingle.py", line 109, in _JingleCB
self._sessions[sid].on_stanza(stanza)
File "/usr/share/gajim/src/common/jingle_session.py", line 343, in on_stanza
call(stanza=stanza, jingle=jingle, error=error, action=action)
File "/usr/share/gajim/src/common/jingle_session.py", line 574, in __broadcast
cn.on_stanza(stanza, content, error, action)
File "/usr/share/gajim/src/common/jingle_content.py", line 117, in on_stanza
callback(stanza, content, error, action)
File "/usr/share/gajim/src/common/jingle_rtp.py", line 285, in __on_remote_codecs
self.p2pstream.set_remote_codecs(codecs)
GError: There was no intersection between the remote codecs and the local ones
# Steps to reproduce
1. Enter to an MUC whee JIDs are _not_ public to anyone.
2. Remote-end (room admin or owner), which is not in roster, attempts to initiate a Jingle session using Jitsi 2.8.build.2.8.5426 for Linux.
# Software versions
Gajim version: 0.16.5-37b54cc9488f
OS version: Salix OS 14.1 (Slackware 14.1 based)
GTK version: 2.24.20
PyGTK version: 2.24.00.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/7978IndexError: list assignment index out of range2018-04-29T20:37:37ZanonymousIndexError: list assignment index out of range# Bug description
A programming error has been detected on connect to xmpp conference:
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/nbxmpp/dispatcher_nb.py", line 497, in dispatch
...# Bug description
A programming error has been detected on connect to xmpp conference:
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/nbxmpp/dispatcher_nb.py", line 497, in dispatch
handler['func'](session, stanza)
File "/usr/lib64/python2.7/site-packages/gajim/common/connection_handlers.py", line 1673, in _SecLabelCB
self.seclabel_catalogues[to][3] = default
IndexError: list assignment index out of range
# Steps to reproduce
Add xmpp conference (for example all @ conference.pirate-party.ru to bookmarks and set auto-join). Restart gajim. Profit!
# Software versions
OS version:
gentoo linux
GTK version:
2.24.25
PyGTK version:
2.24.00.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/7823Single window with no chats opened2018-04-29T20:37:43ZanonymousSingle window with no chats openedWhen Gajim is set to use single window for everything, the main window behaves wierdly when application is started and then first chat is opened. The tabs widget should not be hidden when there are no tabs, so it could act as a placehold...When Gajim is set to use single window for everything, the main window behaves wierdly when application is started and then first chat is opened. The tabs widget should not be hidden when there are no tabs, so it could act as a placeholder and preserve correct both window and roster size.
When first chat is opened, window changes its size to fit both roster and chat. But this is not very nice behavior. If tabs widget is not hidden there would be no need to change window size. The main window could be always maximized.0.16.6Yann LeboulangerYann Leboulangerhttps://dev.gajim.org/gajim/gajim/-/issues/8393Connection retry on Windows to long2018-04-30T11:40:48ZPhilipp Höristphilipp@hoerist.comConnection retry on Windows to long# Bug description
if you have no connection on Windows for like 15 or 20 Minutes, the timeout where gajim trys to reconnect gets bigger and bigger.
this can lead to a timeout > 15 Minutes.
We have no network manager on Windows, so ther...# Bug description
if you have no connection on Windows for like 15 or 20 Minutes, the timeout where gajim trys to reconnect gets bigger and bigger.
this can lead to a timeout > 15 Minutes.
We have no network manager on Windows, so there is no way to know when we have an internet connection.
either the timeout should be reduced to something like 30 seconds, or if this is too expensive somehow, write a cheap function that checks if we have an internet connection and run that every 30 seconds.
now the timeout gets so big, that people think gajim does not try to reconnect at all.
# Steps to reproduce
Deactivate your internet connection for 20 Minutes on Windows
0.16.6Yann LeboulangerYann Leboulanger