Bug#1007736: marked as done (backbone: autopkgtest regression: node: command not found)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Mar 2022 05:33:42 + with message-id and subject line Bug#1007736: fixed in backbone 1.4.1~dfsg+~1.4.15-2 has caused the Debian Bug report #1007736, regarding backbone: autopkgtest regression: node: command not found to be marked as done. This means that you claim

Bug#1006088: marked as done (fonts-smc-manjari: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Mar 2022 10:28:13 +0530 with message-id and subject line Re: Unreproducible has caused the Debian Bug report #1006088, regarding fonts-smc-manjari: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by

Processed (with 2 errors): Re: Unreproducible

2022-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Source: fonts-smc-manjari Unknown command or malformed arguments to command. > Version: 2.000-2 Unknown command or malformed arguments to command. > fixed 1006088 2.000-2 Bug #1006088 {Done: Kartik Mistry } [src:fonts-smc-manjari]

Bug#1007740: curl breaks xmltooling autopkgtest

2022-03-15 Thread Cantor, Scott
On 3/15/22, 8:08 PM, "Daniel Stenberg" wrote: >This is probably the same issue as Bug #1007739. Triggered by a bug in > curl >for CN-only certificates: Ah, probably is. This vhost does use a self-signed cert with a CN only, not Let's Encrypt, and I can't think why else it would be

Bug#1004330: marked as done (dokuwiki: No more works with PHP 8.1: Array and string offset access syntax with curly braces is no longer supported in /usr/share/dokuwiki/inc/init.php on line 557)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Mar 2022 00:49:18 + with message-id and subject line Bug#1004330: fixed in dokuwiki 0.0.20200729-0.1 has caused the Debian Bug report #1004330, regarding dokuwiki: No more works with PHP 8.1: Array and string offset access syntax with curly braces is no longer

Bug#994877: marked as done (dokuwiki: During install error /var/lib/dpkg/info/dokuwiki.postinst:123 tempfile: not found)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Wed, 16 Mar 2022 00:49:18 + with message-id and subject line Bug#994877: fixed in dokuwiki 0.0.20200729-0.1 has caused the Debian Bug report #994877, regarding dokuwiki: During install error /var/lib/dpkg/info/dokuwiki.postinst:123 tempfile: not found to be marked as done.

Bug#1007740: curl breaks xmltooling autopkgtest

2022-03-15 Thread Daniel Stenberg
On Tue, 15 Mar 2022, Cantor, Scott wrote: Looking more closely, I'm going to hope curl is at fault and that this is actually "just" a CA list issue. This is probably the same issue as Bug #1007739. Triggered by a bug in curl for CN-only certificates:

Bug#1007740: curl breaks xmltooling autopkgtest

2022-03-15 Thread Cantor, Scott
I would speculate that this isn't caused by curl, but by openssl bumping. I reproduced the test failure on a Mac, and the change log for openssl 3.0.2 includes a very suspicious incompatible change to a critical function. I need to dig into it, and I don't know when that will be at this point.

Bug#1007740: curl breaks xmltooling autopkgtest

2022-03-15 Thread Cantor, Scott
Looking more closely, I'm going to hope curl is at fault and that this is actually "just" a CA list issue. It's very unusual for any of this code to rely on "default" trust store handling but I'm wondering if this code is tripping on that for some reason. If so, it's likely due to the Let's

Bug#1006615: marked as done (python3-pybind11: Handle Python 3.10's default sysconfig paths)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 22:52:39 + with message-id and subject line Bug#1006615: fixed in pybind11 2.9.1-2 has caused the Debian Bug report #1006615, regarding python3-pybind11: Handle Python 3.10's default sysconfig paths to be marked as done. This means that you claim that the

Bug#1007739: curl breaks stenographer autopkgtest: curl: (27) Out of memory

2022-03-15 Thread Daniel Stenberg
On Tue, 15 Mar 2022, Paul Gevers wrote: This is likely this same issue: https://github.com/curl/curl/issues/8559 Fixed in curl (after the 7.82.0 release) via this PR: https://github.com/curl/curl/pull/8560 -- / daniel.haxx.se

Bug#1007010: marked as done (python3.10: autopkgtest regression: FAIL: test_get_scheme_names)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 22:26:53 + with message-id <20220315222653.jyu3oapalnxlp...@satie.tumbleweed.org.za> and subject line Re: Bug#1007010: python3.10: autopkgtest regression: FAIL: test_get_scheme_names has caused the Debian Bug report #1007010, regarding python3.10:

Bug#1005580: marked as done (entangle: FTBFS: ../src/meson.build:42:5: ERROR: Function does not take positional arguments.)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 22:34:05 + with message-id and subject line Bug#1005580: fixed in entangle 3.0-2 has caused the Debian Bug report #1005580, regarding entangle: FTBFS: ../src/meson.build:42:5: ERROR: Function does not take positional arguments. to be marked as done. This

Bug#1007744: dovecot: FTBFS on ppc64el

2022-03-15 Thread Sebastian Ramacher
Source: dovecot Version: 1:2.3.18+dfsg1-1 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) dovecot FTBFS on ppc64el: 0 / 77 tests failed slow server .. : ok slow

Bug#1007743: kldap: BD-Uninstallable on s390x

2022-03-15 Thread Sebastian Ramacher
Source: kldap Version: 21.08.1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) kldap build-depends on missing: - qt5keychain-dev:s390x Please get this fixed or request the removal of the s390x binaries of kldap. Cheers --

Bug#1006620: marked as done (src:httpie: fails to migrate to testing for too long: uploader built arch:all binary)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 21:35:42 + with message-id and subject line Bug#1006620: fixed in httpie 2.6.0-1.1 has caused the Debian Bug report #1006620, regarding src:httpie: fails to migrate to testing for too long: uploader built arch:all binary to be marked as done. This means

Bug#1006624: marked as done (src:ats2-lang: fails to migrate to testing for too long: uploader built arch:all binaries)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 21:34:08 + with message-id and subject line Bug#1006624: fixed in ats2-lang 0.4.2-1.1 has caused the Debian Bug report #1006624, regarding src:ats2-lang: fails to migrate to testing for too long: uploader built arch:all binaries to be marked as done. This

Bug#1007010: marked as done (python3.10: autopkgtest regression: FAIL: test_get_scheme_names)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 22:32:10 +0100 with message-id <33e39694-9c91-ccee-bcea-ea77942d9...@debian.org> and subject line Re: Bug#1007010: python3.10: autopkgtest regression: FAIL: test_get_scheme_names has caused the Debian Bug report #1007010, regarding python3.10: autopkgtest

Processed: affects 1006615

2022-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1006615 src:dolfin Bug #1006615 [python3-pybind11] python3-pybind11: Handle Python 3.10's default sysconfig paths Added indication that 1006615 affects src:dolfin > thanks Stopping processing here. Please contact me if you need

Processed: severity of 1006615 is serious

2022-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1006615 serious Bug #1006615 [python3-pybind11] python3-pybind11: Handle Python 3.10's default sysconfig paths Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1007740: curl breaks xmltooling autopkgtest

2022-03-15 Thread Paul Gevers
Source: curl, xmltooling Control: found -1 curl/7.82.0-1 Control: found -1 xmltooling/3.2.1-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of curl the autopkgtest of xmltooling fails in testing when

Processed: curl breaks xmltooling autopkgtest

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 curl/7.82.0-1 Bug #1007740 [src:curl, src:xmltooling] curl breaks xmltooling autopkgtest Marked as found in versions curl/7.82.0-1. > found -1 xmltooling/3.2.1-1 Bug #1007740 [src:curl, src:xmltooling] curl breaks xmltooling autopkgtest Marked as found in

Bug#1007739: curl breaks stenographer autopkgtest: curl: (27) Out of memory

2022-03-15 Thread Paul Gevers
Source: curl, stenographer Control: found -1 curl/7.82.0-1 Control: found -1 stenographer/1.0.1-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of curl the autopkgtest of stenographer fails in

Processed: curl breaks stenographer autopkgtest: curl: (27) Out of memory

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 curl/7.82.0-1 Bug #1007739 [src:curl, src:stenographer] curl breaks stenographer autopkgtest: curl: (27) Out of memory Marked as found in versions curl/7.82.0-1. > found -1 stenographer/1.0.1-2 Bug #1007739 [src:curl, src:stenographer] curl breaks

Bug#1007738: webcamoid: autopkgtest regression: Unknown failure encountered running a test

2022-03-15 Thread Paul Gevers
Source: webcamoid Version: 9.0.0-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of webcamoid the autopkgtest of webcamoid fails in testing when that autopkgtest is run with the binary packages of webcamoid from unstable. It

Bug#1007736: backbone: autopkgtest regression: node: command not found

2022-03-15 Thread Paul Gevers
Source: backbone Version: 1.4.1~dfsg+~1.4.15-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of backbone the autopkgtest of backbone fails in testing when that autopkgtest is run with the binary packages of backbone from

Bug#1007733: golang-github-getkin-kin-openapi: autopkgtest regression on armhf and i386:

2022-03-15 Thread Paul Gevers
Source: golang-github-getkin-kin-openapi Version: 0.90.0-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of golang-github-getkin-kin-openapi the autopkgtest of golang-github-getkin-kin-openapi fails in testing when that

Bug#1007734: golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match

2022-03-15 Thread Paul Gevers
Source: golang-github-alecthomas-chroma, golang-github-niklasfasching-go-org Control: found -1 golang-github-alecthomas-chroma/0.10.0-1 Control: found -1 golang-github-niklasfasching-go-org/1.6.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update

Processed: golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > found -1 golang-github-alecthomas-chroma/0.10.0-1 Bug #1007734 [src:golang-github-alecthomas-chroma, src:golang-github-niklasfasching-go-org] golang-github-alecthomas-chroma breaks golang-github-niklasfasching-go-org autopkgtest: hashes do not match Marked as

Bug#1007732: ccache: autopkgtest regression: cannot execute 'cc1plus'

2022-03-15 Thread Paul Gevers
Source: ccache Version: 4.6-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of ccache the autopkgtest of ccache fails in testing when that autopkgtest is run with the binary packages of ccache from unstable. It passes when run

Bug#953630: openbabel autopkg tests fail on non-amd64 architectures

2022-03-15 Thread Paul Gevers
Hi, On Fri, 18 Jun 2021 08:43:53 +0300 Andrius Merkys wrote: I must have overlooked this. I will see what I can do, but indeed this is quite late in the release cycle. Ping. Your package regularly times out on our amd64 infrastructure too. Paul OpenPGP_signature Description: OpenPGP

Bug#1001801: closed by Debian FTP Masters (reply to Timo Aaltonen ) (Bug#1001801: fixed in dogtag-pki 11.0.3-1)

2022-03-15 Thread Paul Gevers
Control: reopen -1 Hi On 15-03-2022 13:09, Debian Bug Tracking System wrote: #1001801: dogtag-pki: hits autopkgtest timeout on powerful workers It has been closed by Debian FTP Masters (reply to Timo Aaltonen ). Sorry to say, but this seems to not have solved the issue:

Processed: Re: Bug#1001801 closed by Debian FTP Masters (reply to Timo Aaltonen ) (Bug#1001801: fixed in dogtag-pki 11.0.3-1)

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1001801 {Done: Timo Aaltonen } [src:dogtag-pki] dogtag-pki: hits autopkgtest timeout on powerful workers 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

Processed: update bts meta info

2022-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1006659 src:python-django-celery-beat 2.2.1-1 Bug #1006659 {Done: Michael Fladischer } [src:python-django-timezone-field, src:python-django-celery-beat] python-django-timezone-field breaks python-django-celery-beat autopkgtest: type

Bug#994456: now also FTBFS

2022-03-15 Thread Antonio Terceiro
On Fri, 11 Mar 2022 19:17:43 +0100 Paul Gevers wrote: > severity 994456 serious > tags 994456 ftbfs > thanks > > Now also causing FTBFS during the ruby2.7 removal transition. Testing this locally, the tests fail randomly aproximately 10% of the times like this:

Bug#1005456: marked as done (osmo-pcu: FTBFS: | gcc: error: unrecognized command-line option '-V')

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 18:22:34 + with message-id and subject line Bug#1005456: fixed in osmo-pcu 1.0.0-2 has caused the Debian Bug report #1005456, regarding osmo-pcu: FTBFS: | gcc: error: unrecognized command-line option '-V' to be marked as done. This means that you claim

Bug#1006300: marked as pending in libvirt

2022-03-15 Thread Andrea Bolognani
Control: tag -1 pending Hello, Bug #1006300 in libvirt reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1006300 marked as pending in libvirt

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1006300 [src:libvirt] src:libvirt: libvirt should no longer build the libvirt-daemon-driver-xen package on i386 Added tag(s) pending. -- 1006300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006300 Debian Bug Tracking System Contact

Bug#1004037: Segmentation fault in plink2 (Was: src:plink2: fails to migrate to testing for too long: autopkgtest regression)

2022-03-15 Thread Chris Chang
Just a heads-up, today's release contains a fix for an infinite-loop-instead-of-error bug in the previous release. On Sun, Feb 20, 2022 at 12:36 PM Andreas Tille wrote: > Cool! This finally works. Thanks a lot for your patience, Andreas. > > Am Sun, Feb 20, 2022 at 09:43:10AM -0800 schrieb

Bug#993350: Still problems

2022-03-15 Thread David Ward
On 3/15/2022 7:15 AM, ael wrote: In fact there are still outstanding problems which are mentioned earlier in this bug. Separate problems need to be tracked in separate bugs, even if they affect the same hardware. Please see: https://www.debian.org/Bugs/Reporting This bug in Debian was

Bug#1007254: marked as done (apache2-dev: Missing dependency on libpcre2-dev for apxs2)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 14:45:14 + with message-id and subject line Bug#1007254: fixed in apache2 2.4.53-2 has caused the Debian Bug report #1007254, regarding apache2-dev: Missing dependency on libpcre2-dev for apxs2 to be marked as done. This means that you claim that the

Processed: Bug#1007254 marked as pending in apache2

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1007254 [apache2-dev] apache2-dev: Missing dependency on libpcre2-dev for apxs2 Ignoring request to alter tags of bug #1007254 to the same tags previously set -- 1007254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007254 Debian Bug

Bug#1007254: marked as pending in apache2

2022-03-15 Thread Yadd
Control: tag -1 pending Hello, Bug #1007254 in apache2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1007254: marked as pending in apache2

2022-03-15 Thread Yadd
Control: tag -1 pending Hello, Bug #1007254 in apache2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1007254 marked as pending in apache2

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1007254 [apache2-dev] apache2-dev: Missing dependency on libpcre2-dev for apxs2 Added tag(s) pending. -- 1007254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007254 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#994178: marked as done (libnginx-mod-http-lua - init_worker_by_lua_block segfaults)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 12:09:40 + with message-id and subject line Bug#994178: fixed in nginx 1.18.0-7 has caused the Debian Bug report #994178, regarding libnginx-mod-http-lua - init_worker_by_lua_block segfaults to be marked as done. This means that you claim that the problem

Bug#1001801: marked as done (dogtag-pki: hits autopkgtest timeout on powerful workers)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 12:04:39 + with message-id and subject line Bug#1001801: fixed in dogtag-pki 11.0.3-1 has caused the Debian Bug report #1001801, regarding dogtag-pki: hits autopkgtest timeout on powerful workers to be marked as done. This means that you claim that the

Bug#1000336: Upgrading tbb

2022-03-15 Thread Nilesh Patra
On 3/14/22 11:51 AM, Andreas Tille wrote: Hi, Am Mon, Mar 14, 2022 at 12:13:50AM + schrieb Torrance, Douglas: On Sun 13 Mar 2022 04:50:32 PM EDT, M. Zhou wrote: Recently I'm not able to test the build of libtbb-dev's reverse dependencies as my build machine was out of access. That blocks

Bug#967228: marked as done (uftrace: Unversioned Python removal in sid/bullseye)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 10:48:55 + with message-id and subject line Bug#967228: fixed in uftrace 0.11-1 has caused the Debian Bug report #967228, regarding uftrace: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#966988: marked as done (uftrace: FTBFS: test failed)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 10:48:55 + with message-id and subject line Bug#966988: fixed in uftrace 0.11-1 has caused the Debian Bug report #966988, regarding uftrace: FTBFS: test failed to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1004662: prosody: postinst keeps messing with snakeoil certs

2022-03-15 Thread Victor Seva
Hi, On 3/15/22 10:29, Martin wrote: On 2022-02-01 23:07, Martin wrote: There have been a number of prosody package bugs related to snakeoil certs. I wonder, if it is worth the trouble? For most real world installations, people get LE certs or buy them or they have their own CA. Maybe prosody

Bug#1006948: gcc-12: FTBFS on mips64el

2022-03-15 Thread Adrian Bunk
On Wed, Mar 09, 2022 at 05:49:04PM +0800, YunQiang Su wrote: > On Tue, 08 Mar 2022 20:53:46 +0100 Paul Gevers wrote: > > Source: gcc-12 > > Version: 12-20220222-1 > > Severity: serious > > Tags: ftbfs > > > > Dear Matthias, GCC maintainers, > > > > gcc-12 fails to build from source on mips64el

Processed: found 1004662 in 0.11.9-2

2022-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1004662 0.11.9-2 Bug #1004662 [prosody] prosody: postinst keeps messing with snakeoil certs Marked as found in versions prosody/0.11.9-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1004662:

Bug#1004662: prosody: postinst keeps messing with snakeoil certs

2022-03-15 Thread Martin
On 2022-02-01 23:07, Martin wrote: > There have been a number of prosody package bugs related to snakeoil > certs. I wonder, if it is worth the trouble? > > For most real world installations, people get LE certs or buy them or > they have their own CA. > > Maybe prosody package should just drop

Processed: Re:

2022-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Had a typo in bug number > reassign 993350 libsane1 1.0.32-4 Bug #993350 [xsane] sane-epson2: unable to start scanner (Perfection 1650) Bug reassigned from package 'xsane' to 'libsane1'. No longer marked as found in versions xsane/0.999-12.

Processed (with 3 errors): your mail

2022-03-15 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 993350 sane-epson2: unable to start scanner (Perfection 1650) Bug #993350 [xsane] xsane: Scanimage detects scanner but Xsane won't start it Changed Bug title to 'sane-epson2: unable to start scanner (Perfection 1650)' from 'xsane:

Bug#1002389: marked as done (pytest: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" --system=custom returned exit code 13)

2022-03-15 Thread Debian Bug Tracking System
Your message dated Tue, 15 Mar 2022 07:18:52 + with message-id and subject line Bug#1002389: fixed in pytest 6.2.5-2 has caused the Debian Bug report #1002389, regarding pytest: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" --system=custom returned

Bug#1002389: marked as pending in pytest

2022-03-15 Thread Jochen Sprickerhof
Control: tag -1 pending Hello, Bug #1002389 in pytest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1002389 marked as pending in pytest

2022-03-15 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1002389 [src:pytest] pytest: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" --system=custom returned exit code 13 Added tag(s) pending. -- 1002389:

Bug#1006966: gajim: Gajim won't start due to gajim.c.storage.cache error

2022-03-15 Thread Stefan Kropp
Hello, I just found this issue note on upstream project: https://dev.gajim.org/gajim/gajim/-/issues/10779#note_204952 It's sounds quite similar. Maybe a corrupted internal gajim db-file. -- Stefan