Package: nmap
Version: 7.93+dfsg1-1
Severity: wishlist
Some time ago, zenmap was removed due to being stuck back on python 2, but
as of nmap 0.94 [1] it has been brought up to date to use python 3 and
gobject, so hopefully it can now be brought back to Debian?
[1]
On Tue, 15 Aug 2023, Shengjing Zhu wrote:
So why would you install dh-golang? It's not listed in golang-1.21's
Build-Depends.
To build other packages. Building Go and building packages that use Go
on the same system doesn't seem weird to me. Is your view that source
packages only need to be
Source: golang-1.21
Version: 1.21.0-1
Severity: important
Tags: ftbfs
Context: trying to build local golang-1.21 packages against stable (bookworm)
If dh-golang is installed, building the golang toolchain itself fails tests,
specifically TestCgoLib in src/cmd/nm/nm_cgo_test.go:
--- FAIL:
Package: python3-gtts
Version: 2.0.3-4
Severity: important
The current version of this package no longer works:
gtts.tts - WARNING - Unable to get language list: 'NoneType' object is not
subscriptable
Usage: gtts-cli [OPTIONS]
Try 'gtts-cli -h' for help.
Error: Unable to find token seed! Did
Package: desktop-base
Version: 12.0.2
Severity: wishlist
Updating some systems to Bookworm to try things out, I noticed the new
desktop theme is blurry on many systems compared to Bullseye, becaues the
Bullseye default "Homeworld" theme came with images (esp. SVGs) targeting
several resolutions
Package: libc6-dev
Version: 2.36-4
Severity: normal
On my partial testing system, after libc6{,-dev} upgraded from 2.35-4 to
2.36-4, ld (from binutils 2.35-2 from stable) could no longer link binaries
due to errors like this:
/usr/bin/ld: /lib/x86_64-linux-gnu/libc.so.6: unknown type [0x13]
Package: wireguard-go
Version: 0.0.20220117-2+b1
Followup-For: Bug #1006276
This probably merits Severity: grave, as the main use for this would be to
work with wg-quick on systems that don't have the kernel module available,
such as ChromeOS Crostini containers, and this package is unusable for
notfound 1008127 fprintd/1.94.2-1
reassign 1008127 libfprint-2-2
found 1008127 libfprint-2-2/1:1.94.2-1
thanks
Oops, missed that fprintd and libfprint are different source packages
Package: fprintd
Version: 1.94.2-1
Severity: normal
Tags: upstream
Due to https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/444,
goodix hardware can't re-enroll a finger if the user-space state is lost,
such as on a reinstall or other issue.
This is fixed upstream in v1.94.3:
Package: iotop
Version: 0.6-24-g733f3f8-1.1
Severity: normal
With recent bookwork kernel builds, iotop incorrectly reports
`CONFIG_TASK_DELAY_ACCT not enabled in kernel`. This seems to have been
fixed upstream:
https://repo.or.cz/iotop.git/commit/ab35334d374e588bec12d201fb8869c536f0545d
Package: nut-client
Version: 2.7.4-13
Severity: wishlist
Dear Maintainer,
Trying to work out support for a new UPS I acquired, I found this upstream
github issue about supporting the protocol needed to get full information
out of my new hardware: https://github.com/networkupstools/nut/issues/139
Package: postgresql-client-common
Version: 225
Severity: minor
When only postgresql client package(s) are installed, the vacuumlo wrapper
erroneously reports:
Error: You must install at least one postgresql-client- package
Even though the client package(s) _are_ installed. This seems to be
Package: golang-1.17-go
Version: 1.17-2
Severity: important
It seems like the binary packages for 1.17-2 were somehow built wrong. Some
build-time generated code that would have defined defaultGOARCH and other
constants doesn't seem to have been generated & built, resulting in some
built-in
On Sat, 7 Aug 2021, Sven Geuer wrote:
I tried to reproduce your observation using tightvncserver 1:1.3.10-3
but didn't encounter any key mapping issues.
Can you provide me with instuctions how to verify this bugs still
persists?
I've been continuing with TigerVNC for the nearly 5 years since
Package: fwupd
Version: 1.5.7-2
Followup-For: Bug #943343
This started out as what I thought may be the same essential data as Ross
Vandergrift reported above, but I think I've figured out the problem.
I'm seeing this same issue on a bullseye system. Interestingly, not on
_all_ of my bullseye
On Tue, 4 May 2021, Faustin Lammler wrote:
Hi Matthew!
Thanks for your detailed report.
Appreciate the followup :)
Indeed, the generated log rotate seems wrong (and I am able to reproduce
the problem with 10.5 on sid).
Could you maybe help on this directly upstream
Package: mariadb-server-10.5
Version: 1:10.5.9-1
Severity: normal
debian/patches/1556.patch contains an update to try to generate a logrotate
config file for mariadb, but it malfunctions almost completely. The
template used is:
@localstatedir@/mysqld.log @logdir@/mysql.log
Package: orpie
Version: 1.6.1-1
Severity: important
Something changed in a recent verison of orpie, causing large sections of
its man page, describing the default key bindings and related important
information to no longer render.
For example, the section `EXECUTING BASIC FUNCTION OPERATIONS`
On Thu, 28 Jan 2021, Guido Günther wrote:
Hi,
On Thu, Jan 28, 2021 at 11:52:41AM -0500, Matthew Gabeler-Lee wrote:
Package: libvirt-daemon-driver-storage-iscsi-direct
Version: 6.9.0-4
Severity: normal
If using qemu, the libvirt iscsi-direct backend won't work without
installing the qemu-block
Package: libvirt-daemon-driver-storage-iscsi-direct
Version: 6.9.0-4
Severity: normal
If using qemu, the libvirt iscsi-direct backend won't work without
installing the qemu-block-extra package. So, like libvirt-daemon recommends
qemu, I think this package should recommend the qemu iscsi support
Package: pcp
Version: 5.2.2-1.1
Severity: important
Attempting an `apt upgrade` on my bullseye system failed, due to improper
dependency info in the pcp package. The libpcp3 dependency has no version
constraints, and the new version of libpcp3 requires pulling in a new
version of perl, so `apt
Package: greylistd
Version: 0.9.0
Severity: normal
Dear Maintainer,
The 0.9.9 version is being rejected from testing migrations due to being a
binary upload instead of a source one. I hope if an 0.9.0-1 is re-uploaded
as source it will be accepted for testing migration?
-- System Information:
On Mon, 19 Oct 2020, Craig Small wrote:
On Mon, 19 Oct 2020 at 15:51, Matthew Gabeler-Lee
wrote:
Aah, no, I can't, that's my point. Because /etc/sysctl.d/ is read before
package-shipped files, then it doesn't matter what file I put it in, it
will still be overridden by package-shipped files
Package: pgcli
Version: 3.0.0-1
Followup-For: Bug #972598
Quick addenda:
1) Verified that downgrading python3-humanize indeed works around this issue.
2) Upstream looks like they've worked around this by no longer using humanize:
Package: pgcli
Version: 3.0.0-1
Severity: important
Since the update of python3-humanize to 3.0.0, pgcli is now completely
broken. Even trying to run `pgcli --help` reports a runtime error about
missing dependencies:
Traceback (most recent call last):
File
You can either:
1) Make your file appear "later" in the listing. So something like
999-must-happen.conf; or
Aah, no, I can't, that's my point. Because /etc/sysctl.d/ is read before
package-shipped files, then it doesn't matter what file I put it in, it
will still be overridden by
Package: procps
Version: 2:3.3.16-5
Severity: normal
My normal expectation with most things unix/linux is that
administrator-controlled files in /etc supersede package-shipped files in
/lib and /usr/lib.
However, the documented (and AFAICT actual) order of loading sysctl .conf
files is:
Package: docker.io
Version: 19.03.12+dfsg1-4
Severity: important
Something in the change(s) for 19.03.12+dfsg1-4 has broken using the
docker.io package with some minikube configurations (particularly the "none"
driver which runs the kubernetes containers directly in the host docker
instance). All
repoen 969543
thanks
Package: solaar
Version: 1.0.3+dfsg-2
Followup-For: Bug #969543
Unfortunately 1.0.3+dfsg-2 didn't actually fix this, I suspect due to
some issue with the rules around debconf and replacing symlinks with
files. When upgrading from 1.0.3+dfsg-1 to the new version, what
On 2020-07-28 07:19, Simon Frei wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 22 Jan 2020 21:24:10 -0500 (EST) Matthew Gabeler-Lee
wrote:
A quick followup: I was able to use gpb and a bit of editing to get a
package built locally that seems to work.
I have a guest account
Package: libc6
Version: 2.31-1
Followup-For: Bug #965932
Having the same issue, found an additional tidbit that may be of use:
When the failure happens, kernel logs a line like this:
Jul 20 20:04:38 hostname kernel: [ 373.963787] audit: type=1326
audit(1595289878.694:7): auid=4294967295
forwarded 962960 https://bugs.kde.org/show_bug.cgi?id=407745
tags 962960 + upstream fixed-upstream
thanks
Looks like this was fixed upstream and has been released in 1.8.02, by
commit https://invent.kde.org/sdk/kdiff3/-/commit/1c86432a9a72c9fbf193d97035255e3a1b6cac09
--
-- Matt
Package: kdiff3
Version: 1.8.01-1+b1
Severity: normal
The Merge menu items to Choose A/B/C Everywhere or For All Unsolved
(Whitespace) Conflicts are not showing up in the kdiff3 build in bullseye.
Downgrading to the version in buster and they show up again.
I also tried 1.8.01-1 from
Package: intel-gpu-tools
Followup-For: Bug #918116
This has been fixed by 1.25-2, verified empirically, and can see the
offending use-after-free has been fixed in the source.
-- System Information:
Debian Release: 10.4
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'),
Package: gnome-shell
Version: 3.36.2-1
Severity: normal
While the screen lock works normally if I leave my user session as the
active VT, if I switch to another VT (e.g. the login one with Ctrl-Alt-1,
or another logged in user session with Ctrl-Alt-3), the screen lock never
activates. I can
Package: libvirt-daemon
Version: 6.0.0-4
Followup-For: Bug #918728
Any chance this can get addressed for bullseye?
FWIW, if I build the package from source with libiscsi-dev (and
corresponding libiscsi7) installed, it auto-detects that it should build
this backend. Presumably then all that's
Package: sensible-utils
Version: 0.0.12+nmu1
Severity: normal
The diff applied for sensible-editor in 0.0.12+nmu1 broke the logic to
protect against recursive loops due to a copy paste error:
[ -n "$EDITOR" ] && [ "$(which $EDITOR || true)" = "$p" ] && EDITOR=
[ -n "$EDITOR" ] && [ "$(which
A quick followup: I was able to use gpb and a bit of editing to get a
package built locally that seems to work.
I have a guest account on salsa, and I'd be happy to submit that work
there, but given that work touches 3 branches (master, upstream,
pristine-tar), I'm not quite sure on the
Package: hub
Version: 2.7.0~ds1-1+b10
Severity: wishlist
The upstream package now has released up to 2.14.0.
Of particular note is the new `hub api` command, which is very useful for
scripting, introduced in version 2.8.3.
-- System Information:
Debian Release: 10.2
APT prefers stable
APT
retitle 947941 Bugs fixed in upstream 2.21.99* dev releases
severity 947941 wishlist
thanks
On Wed, 8 Jan 2020, Unit 193 wrote:
There seems to be a few bugs that will be fixed, SNI support for one. If you
have a list of bugs matched to the associated upstream changelog entries, I
wouldn't
Package: geoipupdate
Version: 4.0.6-2
Severity: minor
With upstream no longer permitting download of the databases without signing
up for an account, this package is no longer usable out of the box, and
doesn't contain pointers to what needs to be done to make it work.
Suggest including in at
On 2020-01-08 01:11, Unit 193 wrote:
Howdy,
It seems upstream has moved again, now to
https://repo.or.cz/alpine.git
That's not a new home, that's just where the git repository lives.
The current home is still http://alpine.x10host.com/alpine/
Oops, I got confused by the bit the watchfile
Package: alpine
Version: 2.21+dfsg1-1.1
Severity: normal
It seems upstream has moved again, now to https://repo.or.cz/alpine.git
There is active development there from Eduadro, including two tagged
releases since what's in Debian currently (though from the numbering and the
contents of the
On 2019-12-03 03:30, Mike Gabriel wrote:
Hi Matthew,
thanks for reporting this bug.
Thank you for following up :)
If you don't have time for testing this, I'd appreciate a quick
feedback anyway.
I have the time, but unfortunately I no longer have the systems. I
encountered this in a
Package: checkinstall
Version: 1.6.2+git20170426.d24a630-1~bpo10+1
Followup-For: Bug #785441
I think the patch _was_ the original bug report, specifically this:
MAINTAINER="`eval "echo '$1'"`"
As compared to what the checkinstall code does now:
MAINTAINER=`eval echo $1`
The suggested extra
On Wed, 11 Sep 2019, Daniel Kahn Gillmor wrote:
But hm, maybe the 4.19.0-5 ABI wasn't actually stable?
Thinking about this a bit more ... the issue wasn't a symvers mismatch,
which is what I'd have expected if the ABI was not actually stable, and
in my case the module headers exactly
On Wed, 11 Sep 2019, Daniel Kahn Gillmor wrote:
IIUC, dkms should build different modules for different kernel ABIs. it
won't try to install the 4.19.0-6 module into the 4.19.0-5 kernel.
Right, but it looks like the Makefile(s) for wireguard might have been
buggy. Of course, I dont know if
Package: wireguard-dkms
Version: 0.0.20190905-1
Followup-For: Bug #939845
Same problem here.
Seems pretty normal to install updates before activating a new kernel
I notice that systems that have hand-configured wireguard intefaces, the
upgrade scripts won't reload the module, but systems just
On Wed, 11 Sep 2019, Matthew Gabeler-Lee wrote:
Not sure if the common dkms scripts might be passing the KERNELRELEASE var
in a way that is messing up the build? In fairness, that seems ... unlikely
to be the cause of an invalid relocation, and more likely to _fix_ having
built the module
On Mon, 26 Aug 2019, Jonas Smedegaard wrote:
Quoting Matthew Gabeler-Lee (2019-08-26 15:42:32)
Given its a symbols related issue, arguably that package needs its
soversion bumped?
If you mean bumping SOVERSION of bitcoin-qt, then I disagree, and ask
you to please elaborate why you think
Package: bitcoin-qt
Version: 0.18.1~dfsg-1
Followup-For: Bug #933311
Indeed, this package needs its dependency on libleveldb1d bumped. Updating
that package to the version in bullseye/sid fixes this issue. Given its a
symbols related issue, arguably that package needs its soversion bumped?
Package: firmware-misc-nonfree
Version: 20190717-1
Followup-For: Bug #928672
Still broken due to the one missing file -- m712 & Sven Joachim's messages above
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'),
Subject: linux-image-5.2.0-2-amd64: More led trigger modules
Package: src:linux
Version: 5.2.7-1
Severity: wishlist
It would be nice if some more LEDS options were enabled in Debian's
configuration, e.g.:
# CONFIG_LEDS_TRIGGER_ACTIVITY is not set
# CONFIG_LEDS_TRIGGER_NETDEV is not set
#
Package: conserver-server
Followup-For: Bug #896184
This problem has gotten even worse.
Now the stop script has become completely ineffectual -- it will never stop
the server at all, systemd or not. From the start-stop-daemon manpage, on
--pidfile:
Warning: using this match option with a
Package: mutter
Version: 3.30.2-7
Severity: normal
Tags: upstream
If you enable static instead of dynamic workspaces, then gnome-shell
segfaults if you restart it.
This has been reported and fixed upstream in 3.32.x, it would be nice if
this fix could be backported to Debian's 3.30.x release.
Package: libvirt-daemon
Followup-For: Bug #924035
The LXC update sin the 5.0.0-3 appear to have resolved this bug :)
-- System Information:
Debian Release: 10.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'stable'), (500,
'oldstable'), (490, 'unstable'),
Package: dbconfig-common
Version: 2.0.11
Severity: normal
dbconfig-common assumes that, if "ident" auth is used with postgresql, then
the database user must also exist as a local user.
This is ... not true.
The "peer" auth in postgresql just means that the identity of the connecting
user
Package: deborphan
Version: 1.7.31
Severity: normal
Trying to use `deborphan --add-keep` with an empty or absent keep file fails:
deborphan: fseek on /var/lib/deborphan/keep: Invalid argument
strace says the failing seek is:
openat(AT_FDCWD, "/var/lib/deborphan/keep", O_RDWR|O_CREAT|O_APPEND,
On Wed, 1 May 2019, Jamie Zawinski wrote:
-arabic-newspaper-medium-r-normal--19-140-100-100-p-0-iso10646-1
I'm gonna guess that this font, despite claiming to be 10646 (Unicode) does not
actually contain Latin characters... So that's not ideal if your locale is set
to one that requires
On Tue, 30 Apr 2019, Jamie Zawinski wrote:
Ok, I'm not really sure what's going on here.
This makes me feel better ;)
Possibly the problem is that your font cache needs to be regenerated with
fc-cache?
Tried that, didn't impact things. There's definitely a sign something
is wonky in
On Mon, 22 Apr 2019, Jamie Zawinski wrote:
Xscreensaver 5.42 tries really hard to do something sensible with
whatever set of garbage fonts you happen to have installed, so it
would be helpful if you send me the output of xlsfonts on your system
where it's doing something terrible.
Attached
Package: tt-rss
Version: 18.12+dfsg-1
Severity: wishlist
Please consider updating tt-rss to upstream 19.2 release.
The 18.12 release removed some major features, major enough that the outcry
caused upstream to bring them back just a couple days after (combined mode).
It looks like buster
Package: xscreensaver
Version: 5.42+dfsg1-1
Followup-For: Bug #699392
It's now actually worse. The core xscreensaver package does not work
without xfonts-(100|75)dpi installed, because the font it uses to render the
unlock widget is unavailable without one of those packages installed.
The
Package: libvirt-daemon
Version: 5.0.0-1
Severity: normal
Dear Maintainer,
Since a recent upgrade (I _think_ this showed up when libvirt 5.0 migrated
to buster, but I'm not entirely sure of that. It could also be related to
the 4.20 kernel, which is the minimum version needed to support the
Package: watchdog
Version: 5.15-2
Severity: normal
I've noticed it due to needrestart, but even on manual invocations
restarting the watchdog service (systemctl restart watchdog.service)
_always_ fails. The service status after a failed restart looks like this:
● watchdog.service - watchdog
Package: gimp
Version: 2.10.8-2
Severity: important
After updating from stretch->buster, gimp no longer starts for me.
I took a look at #903514, but it does _not_ appear to be the issue I'm
having: for one, when I first encountered this, I had neither gimp-python
nor any openblas packages
reassign 839843 lxc-templates 3.0.3-1
thanks
On 2019-01-10 18:12, Pierre-Elliott Bécue wrote:
Matthew, I'm really sorry about the bad experience you've met in 2016.
I
guess you don't have the reply to Christian question three years after.
I'll let the bug open, but I guess it'll never find a
So, this bit me again, years later. This time I have a better
understanding of what is going on.
When a snapshot is mounted, /proc/mounts gets weird. Here's an example
having created two LVs, bind mounting the first onto a new directory,
and then mounting a snapshot of the second lv into
Package: iftop
Version: 1.0~pre4-5
Severity: normal
Tags: upstream
iftop doesn't properly handle interface speeds (e.g. -m option) above
1Gbps. Upstream has fixed this in git:
https://code.blinkace.com/pdw/iftop/commit/77901c8c53e01359d83b8090aacfe62214658183
-- System Information:
Debian
Package: i965-va-driver
Version: 2.2.0+dfsg1-2
Severity: normal
While the description of this package claims it contains support for Coffee
Lake, that support is incomplete in v2.2.0. Upstream 2.3.0 release has
support for newer Coffee Lake (and Kaby Lake) PCI IDs that the 2.2 driver is
lacking.
Package: deborphan
Version: 1.7.30
Severity: normal
I have certbot explicitly installed, which depends on python3-certbot, on
python3-cryptography, which depends on (virtual?) packages
python3-cffi-backend-api-min (<= 9729),
python3-cffi-backend-api-max (>= 9729).
Runing deborpha --guess-python
Package: xscreensaver
Version: 5.40-1
Severity: normal
I noticed on an upgrade that I lost (in wmaker) many menu items related to
xscreensaver. On investigation this is because these menu items are only
provided in xscreensaver in the legacy Debian menu system and not in the
modern xdg /
Package: libvirt-daemon
Version: 4.10.0-2
Severity: normal
Upstream now has an "iscsi-direct" storage backend which has several
advantages over the iscsiadm-based "iscsi" storage backend, including
performance and not having the iscsi devices visible to the rest of the
system.
Debian's
Package: intel-gpu-tools
Version: 1.22-1
Severity: normal
With a recent libc update, the register access tools all fail like this:
Error: /usr/share/intel-gpu-tools/registers/common_display.txt:1:
('CPU_VGACNTRL', '0x00041000', '')
Error: /usr/share/intel-gpu-tools/registers/haswell:1:
Package: luksipc
Version: 0.04-2+b1
Severity: normal
luksipc just needs the binaries (/sbin/cryptsetup) from cryptsetup-bin, it
doesn't need the boot process integration from cryptsetup. As such it
should depend just on the bin package.
This is useful if one is using it with disk images or the
Package: aria2
Version: 1.30.0-2
Severity: normal
While all the aria2c documentation says you can use it with SFTP, trying to
do so with the Debian package fails to work, presumably because the Debian
package is failing to build it with libssh2 support. I suspect that simply
adding libssh2-1-dev
Package: wmaker
Version: 0.95.7-8
Severity: normal
wmaker ought to be built with support for imagemagick via libmagickwand, to
support more image types.
Notably, this would permit wmaker to, for example, use the default debian
theme images, which are only distributed in SVG form normally, which
Package: hg-fast-export
Version: 20140308-1
Severity: important
The (old) version of hg-fast-export currently packaged is incompatible with
mercurial 4.6. Support for this looks to be available upstream
(https://github.com/frej/fast-export) on the hg-4.6-compat branch. There
are also many other
Package: libvirt-daemon
Version: 3.0.0-4+deb9u3
Severity: normal
This is a followup to #822581, which has been archived and thus I can't seem
to reopen it, and direct mail to the maintainer also bounced (bad ipv6
config somewhere in the path it seems).
After a long time of not being able to make
On Sat, 14 Apr 2018, Stefan Fritsch wrote:
This seems to be a systemd bug. Changing PrivateTmp from true to false in
apache2.service fixes the issue. But even with PrivateTmp it works for
some time. It would be interesting what is the trigger to make it fail
later on.
Hmm ... I was having a
Package: tftpd-hpa
Version: 5.2+20150808-1+b1
Severity: normal
The init script for tftpd-hpa kills any instances running in lxc containers
when stopping the service on the host machine.
Example:
Host: sudo service tftpd-hpa start
Guest: sudo service tftpd-hpa start
## all running now
Host: sudo
Thanks for the very fast reply :)
On Thu, 8 Mar 2018, Michael Biebl wrote:
Are you logging in via serial console as unprivileged user?
Yes. If I'm root, that grants all access and the session/tty/etc.
become irrelevant. But I want to run something as not-root under
systemd-inhibit. Yes,
On Fri, 23 Mar 2018, Simon McVittie wrote:
it would be unexpected for someone finding a machine with a
locked GNOME session, logged in as a user with netdev privileges, to be
able to reconfigure the network without first unlocking the session!
I could make the same argument that it is
Package: gdm3
Version: 3.22.3-3+deb9u1
Followup-For: Bug #891599
This actually looks like it might be a bug in gnome-shell, and still present
in 3.28. This silly-looking(?) bit of logic is present there in
js/ui/status/network.js:
_sessionUpdated() {
let sensitive =
Package: libpam-systemd
Version: 232-25+deb9u1
Severity: normal
Various policykit actions that flag as for "active" or even "inactive", but
not "any", do not work from serial console sessions. After much pain, I'm
fairly sure I've traced this down to libpam-systemd not marking serial
logins as
Package: gdm3
Version: 3.22.3-3+deb9u1
Severity: normal
Based on the policy-kit settings, I would expect that adding the Debian-gdm
user to the netdev group (and restarting gdm3 or rebooting) to allow me to
control network connections from the greeter (AKA login screen). For
example, if a VPN
Package: checkinstall
Version: 1.6.2-4
Followup-For: Bug #809415
whitespace problems from the original reporter not-withstanding, this bug is
still present and annoying and trivial to fix.
It also might be better titled "checkinstall logic to identify conffiles is
broken"
In this:
===
# Tag
fixed 826717 58.0-1
thanks
In one of the recent (compared to the age of this bug) Firefox updates,
this bug went away and native notifications in Gnome now work properly
for me.
--
-Matt
"Reality is that which, when you stop believing in it, doesn't go away".
--
Package: firefox
Version: 58.0-1
Severity: minor
I don't think Firefox should be suggesting mozplugger any more -- AFAICT
mozplugger provides an NPAPI plugin, and since non-ESR builds of Firefox 52,
and 53 generally, such plugins are no longer supported.
So, while mozplugger is still available,
On Mon, 25 Dec 2017, Stefan Fritsch wrote:
Hi Matthew,
I don't know libvirt lxc containers at all, but ...
On Tue, 14 Nov 2017, Matthew Gabeler-Lee wrote:
Nov 14 14:38:33 hostname systemd[1]: Reloading The Apache HTTP Server.
Nov 14 14:38:33 hostname systemd[11798]: apache2.service: Failed
Package: mdadm
Version: 3.4-4+b1
Severity: normal
Trying to use mdadm to grow a raid5 array from 2 to 4 devices, I started it
with the --backup-file argument to ensure integrity. This seems to have
caused mdadm-grow-continue@...service to have failed:
● mdadm-grow-continue@md123.service -
On Thu, 14 Dec 2017, Daniel Kahn Gillmor wrote:
iirc, upstream has completely dropped the skeleton files completely from
their source
The current debian package in stable still has the patch to remove the
files so they are there in that version. But I just checked the package
in /testing
Package: gnupg2
Version: 2.1.18-8~deb9u1
Severity: wishlist
While the rationale listed in 0077-g10-remove-skeleton-options-files.patch
for not having gnupg write the default config files to the user home
directory is sound, removing the sample files from the distribution entirely
is not so good.
Package: nvidia-support
Version: 20151021+4
Severity: minor
The instructions for how to correct a mismatched nvidia kernel module are
out of date. Running "rmmod nvidia" is no longer sufficient, it seems that
you need to now do "rmmod nvidia_drm nvidia_modeset nvidia".
-- System Information:
Looking at http://sphinxsearch.com/bugs/view.php?id=2321 and the 2.2.11
vs. 2.2.10 upstream source releases, or the upstream git repo, I can't
find any signs that a systemd unit file was actually added to the tree
at all. Nor does upstream ticket 2321 appear in the changelog for
2.2.11.
Package: apache2
Version: 2.4.25-3+deb9u3
Severity: normal
When running inside a libvirt-managed lxc os container, the reload command
on the systemd unit fails always:
Nov 14 14:38:33 hostname systemd[1]: Reloading The Apache HTTP Server.
Nov 14 14:38:33 hostname systemd[11798]: apache2.service:
On Fri, 10 Nov 2017, Mathieu Parent wrote:
This looks similar to #647430 which was solved in 2:4.6.5+dfsg-6.
Can you test from sid?
While that is likely a necessary component to fixing this, it is not
sufficient. That fixes a script error, this ticket is about package
dependency errors
Package: libnss-winbind
Version: 2:4.5.12+dfsg-2
Severity: normal
Background: I use libnss-winbind, and a mulitiarch amd64/i386 system because
I need to run some third party i386 binaries. At least one of those
binaries needs to be able to do nss lookups for some basic account information.
Package: moreutils
Version: 0.60-1
Severity: wishlist
Using pee to work with something generating output but also going through
more processing before heading to a logfile gets icky, because pee always
has the pipes it uses to talk to the child processes buffered.
e.g. output-generating-thing |
Package: libvncclient1
Version: 0.9.11+dfsg-1
Severity: normal
Tags: upstream
libvncclient has a bug with how it expresses the truecolor pixel format
which causes an error talking to VMware servers.
This looks to have been fixed upstream, so just need to import this fix or
package a new upstream
1 - 100 of 354 matches
Mail list logo
