gajim issueshttps://dev.gajim.org/gajim/gajim/-/issues2020-10-12T22:27:25Zhttps://dev.gajim.org/gajim/gajim/-/issues/9987Roadmap Connection -> Client migration2020-10-12T22:27:25ZPhilipp Höristphilipp@hoerist.comRoadmap Connection -> Client migrationWith new nbxmpp.Client, the Connection class is rewritten from scratch, following things have to be fixed or rewritten
- [x] Fix IBR (Account Wizard)
- [x] Honor SOCKS5 Proxy setting
- [x] Fix ServerInfo Dialog UI
- [ ] ~~Test Zeroc...With new nbxmpp.Client, the Connection class is rewritten from scratch, following things have to be fixed or rewritten
- [x] Fix IBR (Account Wizard)
- [x] Honor SOCKS5 Proxy setting
- [x] Fix ServerInfo Dialog UI
- [ ] ~~Test Zeroconf, seems to not work for some reason~~ #10138
- [ ] ~~Fix Client Cert (needs implementing in nbxmpp)~~ #10139
- [ ] ~~Reimplement POSH~~ #10038
- [x] Accounts: Custom Host needs UI for setting type
- [x] Write method to close all account windows on disconnect
- [x] Remove USE_HTTP_ENV var UI (Not needed anymore)
- [x] Correctly shut Gajim down (It tries to send stanzas after we are already disconnected)
- [x] Adapt proxy window (Remove BOSH)
- [x] Accounts: Rework relogin after setting change
- [x] Check Plain Connection Dialog event
- [ ] ~~Make LoginD dbus module listen for shutdown instead of sleep~~ #10040
- [x] Fix removing account from server
- [x] Fix setting correct resource1.2.0https://dev.gajim.org/gajim/gajim/-/issues/10022AttributeError: 'NoneType' object has no attribute 'get_output_stream'2020-07-06T08:09:58ZAlexandria P.AttributeError: 'NoneType' object has no attribute 'get_output_stream'## Versions
- OS: Arch Linux
- GTK Version: 3.24.14
- PyGObject Version: 3.36.0
- GLib Version : 2.64.0
- python-nbxmpp Version: 0.9.94
- Gajim Version: 1.1.94
## Traceback
```
Traceback (most recent call last):
File "/usr/lib/python3...## Versions
- OS: Arch Linux
- GTK Version: 3.24.14
- PyGObject Version: 3.36.0
- GLib Version : 2.64.0
- python-nbxmpp Version: 0.9.94
- Gajim Version: 1.1.94
## Traceback
```
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/nbxmpp/client.py", line 740, in _ping
self.send_stanza(iq, timeout=10, callback=self._on_pong)
File "/usr/lib/python3.8/site-packages/nbxmpp/client.py", line 504, in send_stanza
self._con.send(stanza, now)
File "/usr/lib/python3.8/site-packages/nbxmpp/tcp.py", line 302, in send
if not self._con.get_output_stream().has_pending():
AttributeError: 'NoneType' object has no attribute 'get_output_stream'
```
## Steps to reproduce the problem
...https://dev.gajim.org/gajim/gajim/-/issues/9824Add auto reconnect setting2020-03-12T22:41:52ZMichaelAdd auto reconnect settingGajim - latest stable on windows
Prosody - latest stable
Mobile laptop user here - frequently connecting/disconnecting/switching-networks/etc (which is more common these days). Furthermore, connecting to my prosody server requires a VP...Gajim - latest stable on windows
Prosody - latest stable
Mobile laptop user here - frequently connecting/disconnecting/switching-networks/etc (which is more common these days). Furthermore, connecting to my prosody server requires a VPN connection or a port knock (i.e. not accessible by default)
It would RULE if there was an option in gajim, which could default to off, whereby when disconnected, it would just keep trying every N seconds. In other words, no need to be smart about it (which I appreciate is the default) if this option is enabled - just plain old dumb keep trying until successful.
It is also worth pointing out that google.com lists "gajim reconnect" and "gajim auto reconnect" as search phrase auto-completions - potentially indicating that I am not the only one who would appreciate this feature.1.2.0https://dev.gajim.org/gajim/gajim/-/issues/9488After reconnect some messages from MUC appear in a private chat from this MUC2019-11-10T14:19:10ZAndrey GurskyAfter reconnect some messages from MUC appear in a private chat from this MUC- Gajim git master 31417ffbc72c
- python-nbxmpp git master 0aed44470
How to reproduce:
- start a private chat with romeo from a MUC
- exchange messages
- disconnect account
- be long enough offline to ensure some messages get posted in ...- Gajim git master 31417ffbc72c
- python-nbxmpp git master 0aed44470
How to reproduce:
- start a private chat with romeo from a MUC
- exchange messages
- disconnect account
- be long enough offline to ensure some messages get posted in that MUC
- reconnect
- messages from all except romeo appear in the MUC, the ones from romeo only in the private chat.1.2.0https://dev.gajim.org/gajim/gajim/-/issues/8538Gajim with Tor leaks DNS requests2022-05-12T21:23:09Zt2dGajim with Tor leaks DNS requestsThis issues it related to #7023
I saw at [privacy handbook](https://www.privacy-handbuch.de/handbuch_63-gajim_tor.htm) that Gajim is not resolving DNS over TOR. Or check at [Tor wiki](https://trac.torproject.org/projects/tor/wiki/doc/To...This issues it related to #7023
I saw at [privacy handbook](https://www.privacy-handbuch.de/handbuch_63-gajim_tor.htm) that Gajim is not resolving DNS over TOR. Or check at [Tor wiki](https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/InstantMessaging).
To check, I enabled the Tor Proxy in my account settings, started my client and looked for DNS requests with Wireshark. I could verify their claims.
I think, this is not the expected behavior. If you use Tor, you don't want anyone to know, which hosts you connect to. At least the domain names related to a "torified" account should be resolved over Tor. Another strategy would be to proxy everything over Tor as soon as one account enabled Tor.1.4.0https://dev.gajim.org/gajim/gajim/-/issues/11515“The Certificate does not match the expected identity of the Site”2023-05-09T10:59:31Zcocker cc“The Certificate does not match the expected identity of the Site”## Versions
- OS: `Fedora 38`
- Gajim version: `1.7.3`
- GTK version: `gtk3.x86_64 3.24.37-1.fc38`, `gtk4.x86_64 4.10.3-2.fc38`
- Python-nbxmpp version: `python3-nbxmpp.noarch 4.2.2-1.fc38`
## Steps to reproduce the problem
...## Versions
- OS: `Fedora 38`
- Gajim version: `1.7.3`
- GTK version: `gtk3.x86_64 3.24.37-1.fc38`, `gtk4.x86_64 4.10.3-2.fc38`
- Python-nbxmpp version: `python3-nbxmpp.noarch 4.2.2-1.fc38`
## Steps to reproduce the problem
1. have a pure Chat-Server `xmpp.example.com` (Prosody here), with “pure” I mean: the Webserver for the Domain `example.com` points to a different IP-Address
1. have Cert from Letsencrypt, containing only `xmpp.example.com`, because `example.com` is not reachable for `certbot`
1. have DNS-Entries
`_xmpp-client._tcp.example.com. 3600 IN SRV 0 5 5222 xmpp.example.com.`
`_xmpps-client._tcp.example.com. 3600 IN SRV 0 5 5223 xmpp.example.com.`
1. have a JID `test123@example.com` (not `test123@xmpp.example.com`)
## Expected behavior
1. Gajim should pick up the `SRV`-Entries and connect to `xmpp.example.com`, which it does 👍. I can recognize the Cert's Serial in the Pop-Up
1. Gajim should accept the Cert for `xmpp.example.com`, without having to tick `Connection/Hostname` and to specify `xmpp.example.com`, as this is redundant with the `SRV`-Entry.
1. Gajim should accept the Cert for `xmpp.example.com` at all
## Actual behavior
Gajim complains:
“SSL-Certificate-Verification-Error
There was an Error while attempting to verify the SSL-Certificate of your XMPP-Server (example.com)
Identified Error
The Certificate does not match the expected identity of the Site”
Of course `example.com` is not in the Certificate. It cannot be there. My Understanding was, that this is the whole Point of the `SRV`-Entries.
Two additional Notes:
1. “Conversations” works for me, even if I also have to specify the exact Servername. But at least it accepts the Cert then. ([Issue there](https://codeberg.org/iNPUTmice/Conversations/issues/50))
2. Server2Server-Communication behaves exactly as it should. A Message from `test456@jabber.de` directed to `test123@example.com` knows which Server to contact, according to the `SRV`-Entrieshttps://dev.gajim.org/gajim/gajim/-/issues/11452AccountWizard: Proxy setting not honored2023-05-05T20:53:34ZkalikoAccountWizard: Proxy setting not honored## Versions
- OS: windows (Portable install)
- Gajim version: 1.7.2
- GTK version:
- Python-nbxmpp version:
## Steps to reproduce the problem
1. Set a global HTTP proxy (no auth)
1. Select the proxy
1. Register a new a...## Versions
- OS: windows (Portable install)
- Gajim version: 1.7.2
- GTK version:
- Python-nbxmpp version:
## Steps to reproduce the problem
1. Set a global HTTP proxy (no auth)
1. Select the proxy
1. Register a new account on a server with xep-0156 HTTP Lookup Method
## Expected behavior
Connect with xep-0156 HTTP Lookup Method using a proxy.
## Actual behavior
From the log (cf. attached) I can see nbxmpp.http is creating requests for two http resources (`updates.json` and `package_index.json`), these requests succeed.
Then I add my account and the request on the `.well-known/host-meta` clearly fails on a timeout.
I can confirm that going through the proxy to fetch this resource is working fine outside gajim.
I had to set a proxy explicitly because I think gajim is not grabbing system exposed proxy (env. var.).
At least, when I set the proxy in gajim I can see some http requests going through (updates and package_index).
[gajim.log](/uploads/a87c305b371a36cb96e2768211a47147/gajim.log)1.8.0https://dev.gajim.org/gajim/gajim/-/issues/11231gajim crashed when trying to access details of a disconnected muc2023-06-02T14:35:31ZPirate Praveen Arimbrathodiyilgajim crashed when trying to access details of a disconnected muc## Versions:
- OS: Debian GNU/Linux bookworm/sid n/a (bookworm)
- GTK Version: 3.24.34
- PyGObject Version: 3.42.2
- GLib Version : 2.74.0
- python-nbxmpp Version: 3.2.4
- Gajim Version: 1.5.2
## Traceback
```
Traceback (most recent cal...## Versions:
- OS: Debian GNU/Linux bookworm/sid n/a (bookworm)
- GTK Version: 3.24.34
- PyGObject Version: 3.42.2
- GLib Version : 2.74.0
- python-nbxmpp Version: 3.2.4
- Gajim Version: 1.5.2
## Traceback
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/gajim/gtk/chat_stack.py", line 577, in _on_action
open_window('GroupchatDetails', contact=contact)
File "/usr/lib/python3/dist-packages/gajim/gtk/util.py", line 700, in open_window
window = window_cls(**kwargs)
File "/usr/lib/python3/dist-packages/gajim/gtk/groupchat_details.py", line 74, in __init__
self._add_groupchat_manage()
File "/usr/lib/python3/dist-packages/gajim/gtk/groupchat_details.py", line 136, in _add_groupchat_manage
self._groupchat_manage = GroupchatManage(self.account,
File "/usr/lib/python3/dist-packages/gajim/gtk/groupchat_manage.py", line 64, in __init__
self._prepare_manage()
File "/usr/lib/python3/dist-packages/gajim/gtk/groupchat_manage.py", line 134, in _prepare_manage
assert self_contact
AssertionError
```
## Steps to reproduce the problem
In an MUC with a status "You left this group chat Join" status trying access details gave a crash. This group was not left manually but probably due to bad connection this was in this state. This could be another bug, where mucs with disconnected state should be highlighted and offered to rejoin.1.8.1https://dev.gajim.org/gajim/gajim/-/issues/11220fails to trust self-signed cert on first try2022-10-17T21:21:27Zdiode24fails to trust self-signed cert on first try- OS version: ubuntu 22.04
- gajim version: gajim-default-nightly 20221014-1
- GTK Version: 3.24.33
- GLib Version: 2.71.3
- Pango Version: 1.50.6
- PyGObject Version: 3.42.1
- cairo Version: 1.16.0
- pycairo Version: 1.20.1
- python-nbx...- OS version: ubuntu 22.04
- gajim version: gajim-default-nightly 20221014-1
- GTK Version: 3.24.33
- GLib Version: 2.71.3
- Pango Version: 1.50.6
- PyGObject Version: 3.42.1
- cairo Version: 1.16.0
- pycairo Version: 1.20.1
- python-nbxmpp Version: 3.2.4
# Steps to reproduce
1. `apt install prosody prosody-modules`
2. `prosodyctl adduser user1@localhost`
3. `prosodyctl cert generate localhost`
4. `cp /var/lib/prosody/localhost.* /etc/prosody/certs`
5. `chmod 640 /etc/prosody/certs/localhost.*`
5. `chown root:prosody /etc/prosody/certs/localhost.*`
6. `systemctl restart prosody`
7. in gajim: accounts > add account
8. enter login details for "user1@localhost" and click login
9. warning appears "Certificate Verification Failed"
10. DO NOT click check box "Add to Trusted Certificates"
11. click "Log In" button
12. window shows "Account has been added successfully"
13. in this window, set account name and click on "connect"
14. window pops up "SSL Certificate Verification Error", "identified error: the signing certificate authority is not known"
15. click check box "add this certificate to the list of trusted certificates"
16. second time window pops up "SSL Certificate Verification Error", "identified error: the signing certificate authority is not known"
17. again, click check box "add this certificate to the list of trusted certificates"
18. process complete
# Expected behavior
I expect to only choose to accept the SSL certificate once.
# Actual behavior
After choosing to accept the certificate the first time, gajim saves the cert in `~/.local/share/gajim/cert_store`. After choosing to accept the second time it also saves a new file in the same directory.1.5.3https://dev.gajim.org/gajim/gajim/-/issues/11219gajim fails to trust ubuntu prosody SSL certificate2022-10-17T21:21:33Zdiode24gajim fails to trust ubuntu prosody SSL certificate- OS version: ubuntu 22.04
- gajim version: gajim-default-nightly 20221014-1
- GTK Version: 3.24.33
- GLib Version: 2.71.3
- Pango Version: 1.50.6
- PyGObject Version: 3.42.1
- cairo Version: 1.16.0
- pycairo Version: 1.20.1
- python-nbx...- OS version: ubuntu 22.04
- gajim version: gajim-default-nightly 20221014-1
- GTK Version: 3.24.33
- GLib Version: 2.71.3
- Pango Version: 1.50.6
- PyGObject Version: 3.42.1
- cairo Version: 1.16.0
- pycairo Version: 1.20.1
- python-nbxmpp Version: 3.2.4
# Steps to reproduce
1. `apt install prosody prosody-modules`
2. `prosodyctl adduser user1@localhost`
3. in gajim: accounts > add account
4. enter login details for "user1@localhost" and click login
5. warning appears "Certificate Verification Failed"
6. check box "Add to Trusted Certificates"
7. click "Log In" button
8. window shows "Account has been added successfully"
9. in this window, set account name and click on "connect"
10. window pops up "SSL Certificate Verification Error", "identified error: the signing certificate authority is not known"
11. check box "add this certificate to the list of trusted certificates"
12. click connect button
13. the same last SSL error window appears again, checking the box "add this certificate to the list of trusted certificates" has no effect, error repeats
The default certs included with the prosody package are links:
- /etc/prosody/certs/localhost.crt -> /etc/ssl/certs/ssl-cert-snakeoil.pem
- /etc/prosody/certs/localhost.key -> /etc/ssl/private/ssl-cert-snakeoil.key
![gajim-ssl-error-first](/uploads/73516793580995d5c6261559b0961615/gajim-ssl-error-first.png)
![gajim-ssl-error-second](/uploads/4a1aceac670ad4259c3da97ea34551be/gajim-ssl-error-second.png)1.5.3https://dev.gajim.org/gajim/gajim/-/issues/10941Could not connect to the server via SOCKS5 proxy2022-08-23T11:42:30Zbgrprtr bgrprtrCould not connect to the server via SOCKS5 proxy## Versions
- OS: Linux
- Gajim version: 1.4.3
- GTK version: 3.24.34
- Python-nbxmpp version: 3.0.2
## Steps to reproduce the problem
1. Gajim -> Preferences -> Advenced -> Global Proxy -> My SOCKS5 proxy
1. Offline
1. ...## Versions
- OS: Linux
- Gajim version: 1.4.3
- GTK version: 3.24.34
- Python-nbxmpp version: 3.0.2
## Steps to reproduce the problem
1. Gajim -> Preferences -> Advenced -> Global Proxy -> My SOCKS5 proxy
1. Offline
1. Online
## Expected behavior
The gajim connects to the XMPP server via SOCKS5 proxy.
## Actual behavior
The gajim is trying to connect forever, the debug log looks like:
06/03/2022 01:34:08 (I) nbxmpp.addresses | Signal: resolved
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Domain resolved
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) ServerAddress(domain='xmpp.server', service='xmpps-client', host=None, uri=None, protocol=<ConnectionProtocol.TCP: 0>, type=<ConnectionType.DIRECT_TLS: 'DIRECT TLS'>, proxy=None)
ServerAddress(domain='xmpp.server', service='xmpp-client', host=None, uri=None, protocol=<ConnectionProtocol.TCP: 0>, type=<ConnectionType.START_TLS: 'START TLS'>, proxy=None)
ServerAddress(domain='xmpp.server', service='xmpp-client', host=None, uri=None, protocol=<ConnectionProtocol.TCP: 0>, type=<ConnectionType.PLAIN: 'PLAIN'>, proxy=None)
ServerAddress(domain='xmpp.server', service=None, host='xmpp.server:5222', uri=None, protocol=<ConnectionProtocol.TCP: 0>, type=<ConnectionType.START_TLS: 'START TLS'>, proxy=None)
ServerAddress(domain='xmpp.server', service=None, host='xmpp.server:5222', uri=None, protocol=<ConnectionProtocol.TCP: 0>, type=<ConnectionType.PLAIN: 'PLAIN'>, proxy=None)
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Set state: StreamState.RESOLVED
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Current address: ServerAddress(domain='xmpp.server', service=None, host='xmpp.server:5222', uri=None, protocol=<ConnectionProtocol.TCP: 0>, type=<ConnectionType.START_TLS: 'START TLS'>, proxy=ProxyData(type='socks5', host='proxy:8000', username=None, password=None))
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Set state: StreamState.CONNECTING
06/03/2022 01:34:08 (I) nbxmpp.connection | (xmpp.server) Set Connection State: TCPState.CONNECTING
06/03/2022 01:34:08 (I) nbxmpp.connection | (xmpp.server) Connecting to proxy (proxy:8000)
06/03/2022 01:34:08 (I) nbxmpp.connection | (xmpp.server) Connect Error: g-io-error-quark: Connection to SOCKSv5 proxy server lost (44)
06/03/2022 01:34:08 (I) nbxmpp.connection | (xmpp.server) Set Connection State: TCPState.DISCONNECTED
06/03/2022 01:34:08 (I) nbxmpp.connection | (xmpp.server) Signal: connection-failed
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Set state: StreamState.DISCONNECTED
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Set state: StreamState.DISCONNECTED
06/03/2022 01:34:08 (E) nbxmpp.stream | (xmpp.server) Unable to connect to xmpp.server
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Set error: StreamError.CONNECTION_FAILED, connection-failed, Unable to connect to xmpp.server
06/03/2022 01:34:08 (I) nbxmpp.stream | (xmpp.server) Signal: connection-failed
06/03/2022 01:34:08 (I) gajim.client | State: ClientState.RECONNECT_SCHEDULED
06/03/2022 01:34:08 (I) gajim.client | Reconnect to xmpp.server in 3s
06/03/2022 01:34:08 (I) gajim.c.settings | Commit
The XMPP server and proxy address were changed.https://dev.gajim.org/gajim/gajim/-/issues/10797Can't accept self-signed certificate (You click add then connect, it still re...2022-03-21T23:05:08ZJean-Francois PerreaultCan't accept self-signed certificate (You click add then connect, it still refuses)![image](/uploads/d19df844efd448ca40ce592e3d700a2e/image.png)
As per the above screenshot
connecting to ejabberd with self-signed certificate
During connection there is "The signing certificate authority is not known" error
I click "...![image](/uploads/d19df844efd448ca40ce592e3d700a2e/image.png)
As per the above screenshot
connecting to ejabberd with self-signed certificate
During connection there is "The signing certificate authority is not known" error
I click "Add this certificate to the list of trusted certificates"
Then connect becomes available
Then it asks again !https://dev.gajim.org/gajim/gajim/-/issues/10792SSL Certificate Error with clients v1.3.3 and nightly builds2022-03-24T09:44:44Zsando38SSL Certificate Error with clients v1.3.3 and nightly buildsDear team,
I updated my TLS certificates for ejabberd xmpp server. Users trying to connect to the server having following error message:
![image_2022-03-07_21-32-49](/uploads/b6a84930cafb17a4a687eb4a40b515ca/image_2022-03-07_21-32-49.pn...Dear team,
I updated my TLS certificates for ejabberd xmpp server. Users trying to connect to the server having following error message:
![image_2022-03-07_21-32-49](/uploads/b6a84930cafb17a4a687eb4a40b515ca/image_2022-03-07_21-32-49.png)
The odd thing is, when I downgrade to gajim v1.3.2, it works fine. But v1.3.3 and nightly builds it does not work. According to the [IM Observatory Test](https://www.xmpp.net/result.php?domain=rm3811.net&type=client), certificate does not have any issues. Also other clients like BeagleIM, SiskinIM, Converations, McCabber show no signs/ errors.
If you need anything else from me for investigations, please let me know. I can also provide you a test account to the xmpp server.
Thanks already in advance and wish you a great day!https://dev.gajim.org/gajim/gajim/-/issues/10766Exception when connecting to my movim.eu account2022-08-29T15:50:36ZMartinException when connecting to my movim.eu account## Versions
- OS: Debian GNU/Linux bookworm/sid
- GTK Version: 3.24.31-1
- PyGObject Version: 3.42.0-3
- GLib Version : 2.70.2-1
- python-nbxmpp Version: 3.0.0~dev1+20220201.ddfe6217-1
- Gajim Version: 1.4.0~dev1+20220201.4dd332d0-1
## ...## Versions
- OS: Debian GNU/Linux bookworm/sid
- GTK Version: 3.24.31-1
- PyGObject Version: 3.42.0-3
- GLib Version : 2.70.2-1
- python-nbxmpp Version: 3.0.0~dev1+20220201.ddfe6217-1
- Gajim Version: 1.4.0~dev1+20220201.4dd332d0-1
## Traceback
```
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nbxmpp/tcp.py", line 198, in _on_read_async_finish
data = stream.read_bytes_finish(result)
gi.repository.GLib.GError: g-tls-error-quark: Error reading data from TLS socket: Error decoding the received TLS packet. (1)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/nbxmpp/tcp.py", line 226, in _on_read_async_finish
self._finalize('disconnected')
File "/usr/lib/python3/dist-packages/nbxmpp/tcp.py", line 384, in _finalize
self.notify(signal_name)
File "/usr/lib/python3/dist-packages/nbxmpp/util.py", line 427, in notify
func(self, signal_name, *args, **kwargs)
File "/usr/lib/python3/dist-packages/nbxmpp/client.py", line 469, in _on_disconnected
self.notify('disconnected')
File "/usr/lib/python3/dist-packages/nbxmpp/util.py", line 427, in notify
func(self, signal_name, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gajim/common/client.py", line 301, in _on_disconnected
self.notify('state-changed', SimpleClientState.RESUME_IN_PROGRESS)
File "/usr/lib/python3/dist-packages/gajim/common/helpers.py", line 1234, in notify
func(self, signal_name, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gajim/gtk/status_selector.py", line 85, in _on_client_state_changed
self.update()
File "/usr/lib/python3/dist-packages/gajim/gtk/status_selector.py", line 139, in update
show = get_client_status(self._account)
File "/usr/lib/python3/dist-packages/gajim/common/helpers.py", line 501, in get_client_status
client = app.get_client(account)
File "/usr/lib/python3/dist-packages/gajim/common/app.py", line 145, in get_client
return connections[account]
KeyError: 'otherdomain.com'
```
## Steps to reproduce the problem
Try to connect my account on `movim.eu`
Exception window opens. Unfortunately every some seconds a new one, so that it was difficult to disable the account.
After disabling the account, the exceptions stopped.
(Note, that I have many IRC channels activated on that account.)https://dev.gajim.org/gajim/gajim/-/issues/10604UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf3 in position 49: inva...2023-11-26T22:01:13Zjescas85UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf3 in position 49: invalid continuation byte## Versions
- OS: Windows 10
- GTK Version: 3.24.29
- PyGObject Version: 3.40.1
- GLib Version : 2.66.7
- python-nbxmpp Version: 2.0.2
- Gajim Version: 1.3.2
## Traceback
```
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf3 in p...## Versions
- OS: Windows 10
- GTK Version: 3.24.29
- PyGObject Version: 3.40.1
- GLib Version : 2.66.7
- python-nbxmpp Version: 2.0.2
- Gajim Version: 1.3.2
## Traceback
```
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf3 in position 49: invalid continuation byte
```
## Steps to reproduce the problem
...https://dev.gajim.org/gajim/gajim/-/issues/10580Untrusted certificate from LetsEncrypt E12021-06-03T07:51:54ZCroax CroaxUntrusted certificate from LetsEncrypt E1## Versions
- OS: Windows 10
- Gajim version: 1.3.2
## Steps to reproduce the problem
1. Connect a server returning a LetsEncrypt certificate issued by "E1". Make sure to return fullchain.pem which contains three certificates i...## Versions
- OS: Windows 10
- Gajim version: 1.3.2
## Steps to reproduce the problem
1. Connect a server returning a LetsEncrypt certificate issued by "E1". Make sure to return fullchain.pem which contains three certificates issued by E1, X2, X1. So X1 is the anchor.
For further LE CA information https://letsencrypt.org/images/isrg-hierarchy.png
2. Connect your account
3. Notice apparition of certificate trust dialog
Remark: I can PM a test server with such a configuration.
## Expected behavior
Gajim should trust the certificate because the anchor (X1) is in the trust store (Local computer / Trusted Root Certification Authorities / Certificates / ISGR Root X1)
## Actual behavior
Gajim asks the user to manually enforce trust or reject.https://dev.gajim.org/gajim/gajim/-/issues/10574'utf-8' codec can't decode byte 0x92 in position 73: invalid start byte2021-05-27T17:30:46Zkouinkouin'utf-8' codec can't decode byte 0x92 in position 73: invalid start byte## Versions
- OS: Windows 10
- GTK Version: 3.24.29
- PyGObject Version: 3.40.1
- GLib Version : 2.66.7
- python-nbxmpp Version: 2.0.2
- Gajim Version: 1.3.2
## Traceback
```
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in p...## Versions
- OS: Windows 10
- GTK Version: 3.24.29
- PyGObject Version: 3.40.1
- GLib Version : 2.66.7
- python-nbxmpp Version: 2.0.2
- Gajim Version: 1.3.2
## Traceback
```
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 73: invalid start byte
```
## Steps to reproduce the problem
...https://dev.gajim.org/gajim/gajim/-/issues/10563g_socket_client_enumerator_callback: assertion failed2021-10-11T20:59:32ZGeobert Quachg_socket_client_enumerator_callback: assertion failed
## Versions
- OS: Win 10
- Gajim version: 1.3.2 and nightly 18th May 2021
- GTK version: 3.24.29
- Python-nbxmpp version: 2.0.2
## Steps to reproduce the problem
1. Use Gajim to login proprietary XMPP server
## Expected ...
## Versions
- OS: Win 10
- Gajim version: 1.3.2 and nightly 18th May 2021
- GTK version: 3.24.29
- Python-nbxmpp version: 2.0.2
## Steps to reproduce the problem
1. Use Gajim to login proprietary XMPP server
## Expected behavior
No crash
## Actual behavior
Crash with:
```
18/05/2021 14:16:56 (I) nbxmpp.stream | (Account Wizard) Set state: StreamState.RESOLVED
18/05/2021 14:16:56 (I) nbxmpp.stream | (Account Wizard) Current address: ServerAddress(domain='my_company.com', service='xmpps-client', host=None, uri=None, protocol=<ConnectionProtocol.TCP: 0>, type=<ConnectionType.DIRECT_TLS: 'DIRECT TLS'>, proxy=None)
18/05/2021 14:16:56 (I) nbxmpp.stream | (Account Wizard) Set state: StreamState.CONNECTING
18/05/2021 14:16:56 (I) nbxmpp.connection | (Account Wizard) Set Connection State: TCPState.CONNECTING
Bail out! GLib-GIO:ERROR:../glib-2.68.1/gio/gsocketclient.c:1938:g_socket_client_enumerator_callback: assertion failed: (data->error_info->best_error)
```
I know there's an issue on our XMPP server still to be fixed (the <subject> thing in #10147) but Gajim didn't crash before. I was testing 1.3.2 by curiosity, and now it's crashinghttps://dev.gajim.org/gajim/gajim/-/issues/10562UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 100: inv...2022-05-03T15:33:48ZAvispaUnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 100: invalid start byte## Versions
- OS: Windows 10
- GTK Version: 3.24.29
- PyGObject Version: 3.40.1
- GLib Version : 2.66.7
- python-nbxmpp Version: 2.0.2
- Gajim Version: 1.3.2
## Traceback
```
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in p...## Versions
- OS: Windows 10
- GTK Version: 3.24.29
- PyGObject Version: 3.40.1
- GLib Version : 2.66.7
- python-nbxmpp Version: 2.0.2
- Gajim Version: 1.3.2
## Traceback
```
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 100: invalid start byte
```
## Steps to reproduce the problem
* Don't know, sit and wait?
* Computer was in a (soft?) sleep mode, came back after hours and there it was.1.4.0https://dev.gajim.org/gajim/gajim/-/issues/10541Unable to set a custom port in connection settings2021-09-14T14:21:00ZJohn SmithUnable to set a custom port in connection settings## Versions
- OS: Fedora 33 (Workstation Edition)
- GTK Version: 3.24.28
- PyGObject Version: 3.38.0
- GLib Version : 2.66.1
- python-nbxmpp Version: 3.0.0-dev1
- Gajim Version: 1.4.0-dev1
## Traceback
```
Traceback (most recent call la...## Versions
- OS: Fedora 33 (Workstation Edition)
- GTK Version: 3.24.28
- PyGObject Version: 3.38.0
- GLib Version : 2.66.1
- python-nbxmpp Version: 3.0.0-dev1
- Gajim Version: 1.4.0-dev1
## Traceback
```
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/gajim/gtk/settings.py", line 424, in on_text_change
self.set_value(text)
File "/usr/local/lib/python3.9/site-packages/gajim/gtk/settings.py", line 298, in set_value
app.settings.set_account_setting(self.account,
File "/usr/local/lib/python3.9/site-packages/gajim/common/settings.py", line 583, in set_account_setting
raise TypeError(f'Invalid type for {setting}: '
TypeError: Invalid type for custom_port: <class 'str'>
```
## Steps to reproduce the problem
1. Open account settings, open connection tab.
2. Open manual hostname & port setting window.
3. Try to enter a port.
...