Hi there,
With a test build provided by Patrick, I was able to confirm that this
fixes the issue on my system.
Thank you for the swift response!
kind regards,
--
Jonas Schäfer
Team Lead Cloud Infrastructure Development
Cloud&Heat Technologies GmbH
Königsbrücker Straße 96 | 01099 Dresden
ust 2021):
https://bugs.kde.org/show_bug.cgi?id=437858
kind regards,
--
Jonas Schäfer
Team Lead Cloud Infrastructure Development
Cloud&Heat Technologies GmbH
Königsbrücker Straße 96 | 01099 Dresden
+49 351 479 367 37
jonas.schae...@cloudandheat.com | www.cloudandheat.com
Green, Open, Ef
7
ii libqt5widgets55.15.10+dfsg-7
ii libsasl2-22.1.28+dfsg1-4+b1
ii libstdc++614-20240201-3
libkf5kmanagesieve5 recommends no packages.
libkf5kmanagesieve5 suggests no packages.
-- no debconf information
--
Jonas Schäfer
Team Lead Cloud Infrastructure Dev
2 somehow causes konsole (or potentially all of Qt,
looking at the pinentry thing) to assume some unnamed modifier to be active at
all times.
Max, Nathanael, could you confirm that you're too using Neo2, or similarly
"exotic" layouts? Otherwise we're probably looking at di
Hi Mark,
For the record:
On Mittwoch, 6. Juli 2022 17:30:19 CEST Mark Brown wrote:
> This is most likely some system configuration issue on your part, there
> is nothing in the packaging that specifically excludes this combination
> and indeed I appear to have a system available to me with both
>
Package: zlib1g
Version: 1:1.2.11.dfsg-2+deb11u1
Severity: normal
Dear Maintainer,
I installed Debian with an arm64 kernel but an armhf userland. I now
need some components as arm64, one of which depends on zlib1g. It is
impossible to install both zlib1g:armhf and zlib1g:arm64, which causes
the i
Hi,
On Mittwoch, 17. November 2021 23:24:14 CET you wrote:
> > I did another test by pinning the bookworm packages (7.6.0-1) and testing
> > those. They exhibit the same behaviour as the patched libvirt, that is: in
> > some cases, virsh destroy will show an error, but the container will be
> > re
ov 2021 16:10:57 +0100 Jonas Schäfer wrote:
> Hi Guido,
>
> Thanks for your reply!
>
> On Wed, 17 Nov 2021 13:11:05 +0100 Guido Günther wrote:
> > here's the missing link:
> >
> > https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/116
>
>
Hi Guido,
Thanks for your reply!
On Wed, 17 Nov 2021 13:11:05 +0100 Guido Günther wrote:
> here's the missing link:
>
> https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/116
I took the artifacts from there and did another test run. At first glance,
everything looked good, but the
Dear maintainer, dear Dio Putra,
I was hit by this too when upgrading LXC-heavy machines to Debian stable. The
patch proposed by Dio Putra [1] fixes the issue for me (I built libvirt 7.0.0-3
from salsa with that patch applied). The only caveat I found was that if you
previously tried to destroy
Just a note that this seems to have gotten much worse at least for some users
in the bookworm testing cycle running kmail. I and at least one other user I
know about get popups every few hours about some random certificates, probably
because someone at some point sent me an email with S/MIME.
A
I second this request.
Another use-case which cannot be addressed with window manager hacks is
starting pavucontrol with different PULSE_SERVER environment variables.
My use case is controlling audio servers in the LAN. When routing a stream
there, I’d typically want to have both my local pavuc
I’m not quite sure what can/should be done about this, but I wanted to file
this bug to track the issue, since it’ll cause build failures for
python-aioxmpp.
Kind regards & thanks,
Jonas Schäfer
[1]: https://bugs.python.org/issue41295
[2]: https://github.com/horazont/aioxmpp/issues/
Hi,
Thanks for the report. It looks as if this is a compatibility problem with
Python 3.8.
I fix upstream is on the way: https://github.com/horazont/aioopenssl/pull/9
kind regards,
Jonas Schäfer
Package: radicale
Version: 2.1.11-6
Severity: normal
Dear Maintainer,
* What led up to the situation?
I have a stretch-based radicale installation running under uwsgi with
the attached uwsgi configuration. Under stretch, everything is
operating correctly and radicale authenticates against the
applies the
+unreleased upstream commit 13ab00d [1].
+
+[1]: https://github.com/horazont/aioxmpp/commit/
+ 13ab00d64094b9a13d9d6984d7509bb40efb1fce
+
+closes: #924801
+
+ -- Jonas Schäfer Thu, 21 Mar 2019 17:00:14 +0100
+
python-aioxmpp (0.10.3-2) unstable; urgency=medium
Thanks for the report. Upstream maintainer here.
This is caused by aioxmpp poking dangerously close to some asyncio internals
and Python 3.7 handling things slightly different apparently. I found this
issue already while testing 3.7 in travis CI, but I did not realize that it
also applies to De
On Sat, 27 Jan 2018 15:41:01 +0100 Jonas Wielicki wrote:
>[1]: https://www.dovecot.org/pipermail/dovecot/2018-January/110787.html
Upstream claims to have a fix for that issue in
https://github.com/dovecot/core/commit/
90bd9600a0e38e55c02c6266c1270fdd4138c07d
Wasn't able to test it.
kind re
18 matches
Mail list logo
