I wrote a patch to address #1026379 that I feel would be appropriate
here too. As I noted there, using tput for detection basically means
having ncurses-bin as a Recommends, so we may want a better way of doing
this detection.
--- /etc/skel/.bashrc 2020-02-25 06:44:22.0 -0500
+++
Package: fluidsynth
Version: 2.3.1-2
Severity: wishlist
Dear Maintainer,
Please consider building fluidsynth with pipewire support.
While it is working adequately via the pulseaudio compatibility layer,
it would be nice to utilize the native support added in 2.3.0 as it is
the default sound
The problem with checking $TERM is you end up having to add every new
terminal type that is capable. In addition to foot, I know of kitty,
alacritty, wezterm, and there are likely more.
The comments around this section of skel.bashrc are unclear, talking
about setting a "fancy prompt
https://github.com/baresip/baresip/releases/tag/v3.3.0
Released 2023-06-05
Packaging the new version would also solve #967266 and likely others
Package: graphite-web
Version: 1.1.8-2
Severity: important
Tags: patch
The error
RuntimeError("populate() isn't reentrant")
is logged in the Apache log file when attempting to use the stock
/usr/share/graphite-web/graphite.wsgi file.
https://wiki.rockstable.it/Icinga2 in the section "Graphite
Package: remmina-plugin-vnc
Version: 1.4.29+dfsg-1
Severity: normal
When specifying a UNIX socket as a remote VNC server (eg:
unix:///tmp/wayvnc-ssh.sock)
the program will segfault when trying to connect. This issue has been reported
upstream (https://gitlab.com/Remmina/Remmina/-/issues/2856)
On my Debian 11 XFCE machine this works correctly. Make sure "PolicyKit
Authentication Agent" is checked under "Session and Startup" ->
"Application Autostart".
In Debian 12 under Sway the GNOME Authentication Agent segfaults, but I
will take this up under separate cover. I was able to work
Package: system-config-printer
Version: 1.5.18-1
Followup-For: Bug #1031152
Workaround suggested by original reporter (sudo) ineffective on sway due to
Wayland security model.
-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (500, 'testing-security'),
Package: python3-pulsectl
Followup-For: Bug #1019977
Rather than adding another dep on pipewire-pulse, it probably makes sense to
change the dependency to the client library libpulse0, which is what this
module is using for
its bindings anyway.
-- System Information:
Debian Release: 12.0
I have xdg-desktop-portal-{wlr,gtk} installed, which is appropriate for
a wlroots compositor.
On 3/28/23 19:32, Richard B. Kreckel wrote:
On 3/28/23 22:12, Kevin Otte wrote:
When I attempt to add a source to the current scene, I do not see the
"Screen Capture (Pipewire)" opt
Package: obs-studio
Version: 29.0.2+dfsg-1+b1
Severity: important
Dear Maintainer,
The release notes for OBS Studio 27 indicate:
Added support for Wayland on Linux. This includes a new PipeWire capture source
when using Wayland...
When I attempt to add a source to the current scene, I do not
This PR has been merged. Unknown when a new release might be made.
On Fri, 29 Jan 2021 12:07:24 -0500 Kevin Otte wrote:
I finally had a chance to chase this down and filed the issue upstream:
https://github.com/rafael2k/darkice/issues/166
I have also submitted a PR to try and fix the issue
Package: ipxe-qemu
Version: 1.0.0+git-20190125.36a4c85-5.1
Severity: important
When attempting to network boot a UEFI VM, cannot boot the Linux kernel image:
iPXE> ifopen net0
iPXE> dhcp
Configuring (net0 52:54:00:b1:e7:9f).. ok
iPXE> kernel
Package: libvirt-daemon
Version: 8.5.0-1
Severity: important
Tags: ipv6
Dear Maintainer,
When attempting to start a QEMU VM on a host with only IPv6 addresses
available, qemu-system-x86_64 fails to start:
Aug 31 17:48:33 saratoga libvirtd[3181]: internal error: qemu unexpectedly
closed the
Issue known upstream: https://github.com/swaywm/sway/issues/3799
Issue filed upstream and fix merged:
https://gitlab.com/virt-viewer/virt-viewer/-/issues/66
Should show up in a future release.
Yep, this broke collectd on my main home server.
Relatively easy to go comment out, but still pretty annoying along with
the other bugs I'm still chasing down.
Package: graphite-web
Version: 1.1.8-1
Severity: grave
Dear Maintainer,
Installed graphite-web on a fresh bullseye machine and migrated the apache
virtualhost configuration from a running buster machine.
Attempting to load the page results in the error listed in the subject.
Full traceback:
This bug caused the package to not be included in the bullseye release
and is now blocking the upgrade of one of my machines. Can we please
pull the latest upstream (now 1.1.8) in and get a backport for bullseye?
This just bit me on an upgrade from buster to bullseye
(python3-cherrypy3 8.9.1-8):
kjotte@vesta:~/sixspot$ ./sixspot.py
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cherrypy/lib/reprconf.py", line
213, in as_dict
value = unrepr(value)
File
According to https://tracker.debian.org/pkg/bird2 , this backport was
created in May 2021.
This bug can therefore be closed.
Package: virt-viewer
Version: 7.0-2
Severity: important
Dear Maintainer,
When attempting to connect to a remote display, and socat is present on the
remote system, I am unable to connect:
-
kjotte@mystic:~$ virt-viewer -vv -c qemu+ssh://agamemnon.home.nivex.net/system
icarus
Opening connection
Now that the certificate has expired, this package is now useless. It
should either be updated and a backport applied to buster, or removed
ahead of the bullseye release.
Does this warrant raising the severity?
I finally had a chance to chase this down and filed the issue upstream:
https://github.com/rafael2k/darkice/issues/166
I have also submitted a PR to try and fix the issue:
https://github.com/rafael2k/darkice/pull/167
Package: baresip-core
Version: 1.0.0-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since libre 1.1.0 has migrated to testing, baresip can no longer make calls:
$ baresip
baresip v1.0.0 Copyright (C) 2010 - 2020 Alfred E. Heggestad et al.
Local network address:
Thanks for the additional eyes. Should I file a bug against baresip to
have it rebuilt for testing, or will that be triggered automatically
when libre migrates?
On 10/14/20 12:40 PM, Bernhard Übelacker wrote:
> Dear Maintainer,
> I could reproduce the issue and it looks like there is a ABI break
Package: libre0
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I went ahead and installed version 1.1.0-1 from unstable to go ahead and
test the fix for #971980.
---
kjotte@daedalus:~$ baresip
baresip v1.0.0 Copyright (C) 2010 - 2020 Alfred E.
Package: libre0
Version: 1.0.0-1
Severity: important
Tags: ipv6 upstream
Dear Maintainer,
Applications using libre0 are unable to perform DNS resolution when the
system has only IPv6 resolvers available.
I discovered this issue while using baresip and filed it upstream:
New upstream release now has support for IPv6.
https://sourceforge.net/projects/dict/files/dictd/dictd-1.13.0/
dictd:
* add support for IPv6 (the default is IPv4)
- Add global configuration option "address_family" and
command line options --address-family
-
kpcli 3.3 was released on 2019-08-16
On Sat, 12 May 2018 12:55:33 +0200 Hannes von Haugwitz
wrote:
> Package: kpcli
> Version: 3.1-3
> Severity: wishlist
>
> Hi,
>
> kpcli 3.2 was released in Dec 2017. Please consider to upgrade the
> package.
>
> Thanks.
>
> Best regards
>
> Hannes
>
>
I confirm the LD_PRELOAD workaround works for me.
I also note that this package is not built against libunwind8 on mips or
s390x. I think arm64 should be added to this list.
identical traceback, the
only change being where terminate is called:
terminate called after throwing an instance of 'rfb::AuthFailureException'
So it appears that any exception thrown will cause the server to crash.
On 7/22/19 5:41 AM, Bernhard Übelacker wrote:
> Am 22.07.19 um 0
That is correct.
On 7/21/19 4:34 PM, Bernhard Übelacker wrote:
> Hello Kevin Otte,
>
> Am 21.07.19 um 17:23 schrieb Kevin Otte:
>> I have now tried with and without a view-only password. I receive the
>> same error in both cases.
>
> just to be sure, you got also t
ve an answer yet.
> More details in [1].
>
> @Kevin Otte: Could you confirm that you did not set a view-only password?
> Because doing so could be a workaround.
>
> Kind regards,
> Bernhard
>
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923962#15
>
Package: tigervnc-standalone-server
Version: 1.9.0+dfsg-3
Severity: important
This is Armbian buster running on an Odroid-C2. Confirmed package is
working in an amd64 VM.
kjotte@donatello:~$ vncserver :1 -verbose -geometry 1024x600 -depth 16
/usr/bin/Xtigervnc :1 -desktop
Package: bats
Version: 0.4.0-1.1
Severity: normal
Dear Maintainer,
The current upstream for this package is
https://github.com/sstephenson/bats .
The last commit on this tree was over three years ago.
A newer tree that is being actively maintained is located at
I just saw the news post about the Installer Buster Alpha 4 release.
Does this mean the freeze is coming soon? Do we need an NMU of this
package to make sure we don't have yet another Debian release with an
alpha/beta version of Opus in it?
I'm not a developer, but I am quite interested in seeing this happen.
I was able to build a test package on a stretch VM by:
- downloading the 1.3 tarball from upstream
- grabbing the debian directory out of git
(https://salsa.debian.org/ron/opus.git)
- updating debian/changelog with a test entry
Upstream has said they have no intention of merging the changes because
it is not consistent with their profit motive:
https://github.com/symless/synergy-core/pull/6178
I've identified the problem and submitted a patch. Is there something
more I need to do to move this along?
Now that this bug has a patch, is there any chance we can get it pushed
in time for the next Ubuntu LTS release? It would be a shame to go
another two years without this fix.
Package: darkice
Version: 1.3-0.1
Severity: important
Tags: ipv6
$ cat darkice.cfg
[general]
duration = 0
bufferSecs = 2
[input]
device = default
sampleRate = 48000
bitsPerSample = 16
channel = 1
[icecast2-0]
bitrateMode = abr
format = opus
bitrate = 16
server = marconi.home.nivex.net
port =
> which I've just rebased and then tweaked to use a here document:
>
>
> https://anonscm.debian.org/cgit/d-i/partman-iscsi.git/log/?h=pu/iscsi-initiator-prompt
The here document needs to be left justified, lest the target file end
up with the indentation. See finish.d/iscsi_settings:69 et al.
(replies inline)
On 02/03/2017 04:00 AM, Philip Hands wrote:
> To be useful one also needs to change choose_partition/iscsi/do_option to call
> iscsi_start() rather than iscsi-start, otherwise you're defining a
> function that's never called. Also, one needs to define
>
Package: partman-iscsi
Version: 44
Tags: ipv6
In init.d/iscsi the portal address is collected thusly:
echo "$(cat "$connectiondev/persistent_address"):$(cat
"$connectiondev/persistent_port"),$(cat "/sys/$sessiondev/tpgt")"
>iscsi_portal
resulting in an iscsi_portal file looking like
Package: partman-iscsi
Version: 44
The installer should prompt for the desired iSCSI initiator name before
starting the initiator. Many iSCSI targets require the specification of
the IQN as part of their ACLs. It is useful for the administrator to be
able to set this.
I have included a patch
Adding "pre-up sleep 5s" to the stanza causes the ifup to complete
successfully.
Package: isc-dhcp-client
Version: 4.3.1-6+deb8u2
Severity: critical
Tags: ipv6
Justification: breaks the whole system
Dear Maintainer,
Adding a "dhcp 1" (stateless DHCPv6) to my inet6 interface stanza causes
the system to fail to bring up the interface, failing with these
messages in syslog:
I just encountered this on an Ubuntu 15.04 machine running autofs
5.0.8-1ubuntu3.2. Since Debian is upstream and this bug is still open, I
figured I'd mention it here.
My workaround has been to use Samba since it has UNIX extensions, which
is less than optimal with all its forays into userspace,
Package: krb5-kdc
Version: 1.12.1+dfsg-19
Severity: important
Tags: ipv6
krb5kdc fails to bind to the IPv6 addresses on the system at startup.
Workaround is a manual service restart on every boot.
root@mercury:~# uptime
14:08:38 up 0 min, 1 user, load average: 0.69, 0.19, 0.06
root@mercury:~#
I am still encountering this problem, usually triggered by
popularity-contest (#640974)
root@avalon:/home/kjotte# uname -a
Linux avalon 2.6.32-5-686 #1 SMP Fri Aug 26 09:15:47 UTC 2011 i686 GNU/Linux
kjotte@avalon:~$ cat /proc/1/maps
from /var/log/syslog:
Oct 9 10:11:55 avalon kernel:
Yep, that was it. Humble apologies for the noise.
On 10/09/2011 11:25 AM, Ben Hutchings wrote:
On Sun, 2011-10-09 at 10:23 -0400, Kevin Otte wrote:
I am still encountering this problem, usually triggered by
popularity-contest (#640974)
root@avalon:/home/kjotte# uname -a
Linux avalon 2.6.32
Upstream has an APT repository with latest versions available at:
ftp://arthur.barton.de/debian/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: maildrop
Version: 2.0.4-3+lenny1
Severity: critical
Justification: breaks unrelated software
DSA-1981-1 removes the dependency on courier-authlib, which is still
required by the package. As such, maildrop fails to execute and causes
mail to bounce:
Jan 28 12:22:17 triton
Package: openvpn
Version: 2.1~rc11-1
Severity: normal
Sample entry from /var/log/syslog:
Jun 20 19:13:11 tardis ovpn-nivexlan[2272]: write to TUN/TAP : Invalid
argument (code=22)
This mesage is logged once every minute since upgrading from etch to lenny.
The tunnel is up and functioning, but
Good heavens, I am surprised this bug is still open! I should check my
open bugs once in awhile.
Unfortunately, yes, it is still broken. In the intervening years I
learned how to fix :)
The problem is that the code for displaying the timezone name currently
always refers to tzname[0]. The
Package: ejabberd
Version: 2.0.1-6
Severity: important
Version installed on etch was 2.0.1-6~bpo40+1
After upgrade to lenny, any attempts to starttls on 5222 cause the connection
to hang. For debugging, I enabled the legacy SSL on port 5223 and attempted
to connect with openssl's s_client. The
Reference: https://bugs.launchpad.net/debian/+bug/31272
Given the bug's age and the fact that it appears fixed in Ubuntu, is it
safe to close out this report?
-- Kevin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
! Please close
this bug.
--
Kevin Otte, N8VNR
[EMAIL PROTECTED]
http://www.nivex.net/
-=-
Those who cannot remember the past are condemned to repeat it.
-- George Santayana
It seems no one reads Santayana anymore.
-- Cdr. Susan Ivanova, Babylon 5
--
To UNSUBSCRIBE, email to [EMAIL
Package: zaptel
Version: 1:1.0.7-4.1
Severity: wishlist
Please enable the ztdummy module when making the package so those of us
without Digium hardware can have the pseudo channel and timing options
for things like MeetMe conferencing in Asterisk.
-- System Information:
Debian Release: 3.1
60 matches
Mail list logo
