Package: linphone-desktop
Version: 5.2.6+dfsg-1
Severity: grave
Justification: renders package unusable
Linphone 5.2.6+dfsg-1 crashes during startup:
$ linphone
linphone: error while loading shared libraries: libapp-plugin.so: cannot
open shared object file: No such file or directory
The file e
Am 03.03.25 um 10:34 schrieb Yves-Alexis Perez:
So for what it's worth:
- the crash was fixed by upstream in 0.9.7-1
- the wayland support through the b-d has been added in 0.9.7-2
Excellent, thanks for checking and uploading the fix! :-)
Best regards,
Fiona
As your log shows, libflac12t64 and libopenh264-7 were installed from
testing, not sid. Sid has libflac14 and libopenh264-8.
Am 28.01.25 um 10:04 schrieb Simon McVittie:
On Tue, 28 Jan 2025 at 09:43:56 +0100, Fiona Klute wrote:
After update from 3.24.43-5 to 3.24.48-3 xfce4-panel (in xfce-wayland
session) started crashing when simply right-clicked, and some panel
items also crashed on left-click. Logs show a segfault
Package: libgtk-3-0t64
Version: 3.24.48-3
Severity: important
After update from 3.24.43-5 to 3.24.48-3 xfce4-panel (in xfce-wayland
session) started crashing when simply right-clicked, and some panel
items also crashed on left-click. Logs show a segfault (I run
xfce4-panel via systemd user sessio
bxfce4util74.20.0-1
ii libxfconf-0-34.20.0-1
Versions of packages xfce4-notifyd recommends:
ii libnotify-bin 0.8.3-1+b2
xfce4-notifyd suggests no packages.
-- debconf-show failed
From 6db8c538e98a59cbfb3568bfe91787b41e934cd9 Mon Sep 17 00:00:00 2001
From: Fiona Klute
Da
On Mon, 18 Nov 2024 12:08:36 +0500 Andrey Rakhmatullin
wrote:
I checked the upstream and found that the packaged version already claims
to support 3.13, and they indeed run 3.13 tests on CI. So this is weird.
Looking at the code of the GenericIterator class [1], the error is
correct: It's missi
Package: clang-tools
Version: 1:19.0-60
Severity: wishlist
Dear maintainers,
scan-build-py [1] is part of LLVM and an alternative to scan-build
written in Python. Notably it allows merging SARIF output after analysis
into a single output file.
The versioned clang-tools-NN packages already insta
Package: python3-typeshed
Version: 0.0~git2023.6764465-3
Severity: normal
While typechecking a file using paramiko.pkey.PKey I'm getting the
following error from MyPy:
> error: "type[PKey]" has no attribute "from_type_string" [attr-defined]
This is incorrect, the (static) method exists and
Package: duplicity
Version: 2.1.4-3+b1
Severity: important
When trying to do backup to an sftp:// target Duplicity fails since
python3-paramiko was updated to 3.4.0-1, with the following error which
looks like an API change in Paramiko:
ssh: Unknown exception: public_blob
ssh: Traceback (most re
I have the same issue with German and Finnish keyboard layouts via ibus
(umlauts and other non-ASCII characters don't work) and ibus-anthy after
the update from 2.80.0-9 to 2.80.0-10, downgrading fixes it. So it looks
like that security fix breaks ibus with GTK applications in general. :-(
Stoppi
Package: foliate
Version: 4-1
Severity: normal
After updating to the Foliate 4-1 package I was confused that the
pre-3.0 UI was back, as well as the frequent segfaults (see #1039050).
Looking at the source it seems like the package was actually reverted to
upstream version 2.6.4, the upstream Git
Package: foliate
Version: 3.0.1-1
Severity: important
Dear maintainer,
trying to start Foliate after updating to 3.0.1-1 resulted in a crash
with the following error:
$ foliate
(gjs-console:177311): Gjs-CRITICAL **: 11:04:45.617: JS ERROR: Error:
Requiring Gtk, version 4.0: Typelib file for na
Package: python3-pysrt
Version: 1.0.1-3
Severity: normal
SubRipFile.open() and any use of the included srt command line tool fail
because the pysrt code uses the outdated 'U' mode which has since been
removed (traceback below). This has been fixed upstream for a while [1],
so updating the package
I'm seeing the same behavior from Foliate, though the exact message from
the crash varies. *In addition to* the one quoted above I've also seen:
**
Gjs:ERROR:../gi/function.cpp:1035:bool Gjs::Function::invoke(JSContext*, const
JS::CallArgs&, JS::HandleObject, GIArgument*): assertion failed (ffi
Output from firefox-esr 102.12.0esr-1:
$ firefox-esr
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: defau
Package: pelican
Version: 4.8.0+dfsg-1
Severity: normal
Tags: upstream
Running pelican-quickstart fails with the exception below if
python3-tzlocal is installed. Otherwise the ImportError for tzlocal is
caught and the buggy code avoided.
The buggy code is still present upstream:
https://github.c
Package: libqt5core5a
Version: 5.15.8+dfsg-6
Followup-For: Bug #1034271
The update from 5.15.8+dfsg-5 to 5.15.8+dfsg-6 also causes a segfault in
linphone (package linphone-desktop) during startup, making linphone
unusable (command line output attached). Downgrading makes linphone work
again.
--
Am 10.01.23 um 20:03 schrieb Martin:
Btw. thanks for testing the latest nbxmpp master!
You're welcome!
After testing the patch I also tried installing nbxmpp and gajim in a
virtualenv. And there Gajim starts! "pip3 list" output within the
virtualenv:
Package Version Edit
In that case python3-nbxmpp 4.x must not migrate either, because it
breaks Gajim 1.5.x. I'm not sure what's the proper way to achieve that,
should I file another bug or is there some "blocks" mechanism in the BTS?
Package: gajim
Version: 1.6.0-1
Severity: important
Gajim 1.6.0-1 crashes while connecting to XMPP server(s). Visually the
Gajim window pops up briefly and then disappears again. According to the
stack trace below the crash seems related to libproxy.so.1, but I don't
have any proxy configured for
The bug affects a few more libraries. I found that creating symlinks for
all of them in /usr/lib/firefox/ is a workaround:
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
Package: systemctl
Version: 1.4.4181-1.1
Severity: important
The packaged version of docker-systemctl-replacement contains an
upstream bug where systemctl assumes that the mtime of /proc files of
the init process is the boot time of the container. Status and PID files
with older timestamps are co
Source: modsecurity-apache
Version: 2.9.5-1
Severity: minor
The homepage URL listed in debian/control is
https://github.com/SpiderLapbs/ModSecurity, which doesn't exist.
debian/watch correctly uses https://github.com/SpiderLabs/ModSecurity,
so I guess it's just a typo. Please fix the homepage URL
I've written a setup script for autopkgtest-virt-ssh that sets up a
local Docker container as a testbed, and supports revert:
https://github.com/airtower-luna/autopkgtest-ssh-docker
Of course native Docker support would be nicer, but maybe this script
could be included in /usr/share/autopkgtest/s
This change appears to break systems with /usr merge [1], I get this
when trying to upgrade libc6 from 2.30-2 to 2.30-3 on amd64:
> A copy of the C library was found in an unexpected directory:
> '/usr/lib/x86_64-linux-gnu/ld-2.30.so'
> It is not safe to upgrade the C library in this situation;
This issue has been fixed in upstream version 0.10.0 (out just now).
This is caused by recent GnuTLS versions (since 3.6.11 AFAIK) listing
the peer's certificate type in the session description so they aren't
identical on anonymous client and authenticated server, so backporting
shouldn't be neces
This has been fixed upstream since version 0.9.1.
msva.bash" make -e check
The restriction of TESTS to the MSVA test is just to save time, running
all tests with Valgrind may take a couple of minutes.
Thank you for your attention!
Fiona Klute
[1] https://curl.haxx.se/libcurl/c/curl_global_cleanup.html
[2] https://gitlab.com/gnutls/gnu
Hi Nico,
I tried to reproduce the issue but couldn't. Exactly how are you sending
the requests? I've tried both curl and hand-typing over gnutls-cli.
If you still have this issue, could you try enabling the appropriate
debug repositories (see https://wiki.debian.org/AutomaticDebugPackages)
and in
On Wed, 23 Jan 2019 22:46:59 +0100 Fiona Klute wrote:
> The easiest solution for the mod-gnutls package should be to remove the
> PDF documentation,
I realized the PDF documentation doesn't get installed anyway, so the
easiest workaround will be to remove the pdf_DATA line in
doc/Mak
That looks like a bug in pandoc to me. There's no PDF template
configuration in mod_gnutls, so this seems to affect PDF generation with
pandoc's default settings.
The easiest solution for the mod-gnutls package should be to remove the
PDF documentation, and maybe replace it with the manual page av
These test failures look like they are due to the switch to GnuTLS 3.6
(different default algorithms, OpenPGP removal), and should be fixed in
mod_gnutls 0.9.0 (released today).
The issue is fixed in the 0.8.4 upstream release, please update the
package. :-)
Regards,
Fiona
34 matches
Mail list logo
