Bug#685878: DDP support in netatalk v3

[T. Joseph Carter]

Hi folks,

There's a lot of good reasons to see netatalk v3 packaged for Debian, 
since there are features v2 just doesn't have such as hosting for 
Apple's Time Machine backups and the like.


That said however, there is a bit of a spanner in the works because 
upstream decided to abandon support for the DDP (AppleTalk) ethernet 
protocol that exists alongside TCP/IP.  Their argument is that all 
but vintage Apple computers pre-MacOS X actually use DDP, so it's now 
quite obsolete.


If however you know anybody who actually has some of these now 
vintage computers networked using DDP (hi!), they're unlikely to be 
pleased to see their network suddenly disappear on upgrade to v3.  I 
don't have a lot of expectation that such old machines should be 
allowed anywhere near the public internet, but on a firewalled LAN, 
eh why not?


Obviously v2 and v3 cannot coexist on the same machine, at least for 
now.  I'm investigating whether or not v2 can be cut down to coexist 
on a machine with netatalk v3 to support old clients.  Perhaps with a 
smaller target (only supporting those legacy clients), it might be 
easier to evaluate patches made to v3 that may affect things like 
security.


Anyway, just registering my interest in the outcome of this issue 
whenever it gets resolved.  :)


Joseph

Bug#801080: Double->float->int

[T. Joseph Carter]

It may be a bug in gcc that is causing the problem, but code that is 
sloppy about types is never good coding practice.  If the scale 
values are calculated as doubles, then double should be the type for 
the variable.  That's an upstream issue, but it's affecting Debian 
users and there's a single line patch for it.


Just my $0.02, unasked for but offered anyway.  :)

Joseph

Bug#834994: consolation limiting to 64 columns

[T. Joseph Carter]

Package: consolation
Version: 0.0.1-1
Severity: important

Hi Bill,

Intrigued by Consolation as a possible GPM replacement, so I figured 
I'd remove that and give it a shot.  Upon installing it, I find that 
the mouse cursor will extend to the full console height, but not the 
full console width.  It stops in column 64--a default maybe?


I have no idea what might be relevant here, so I'll give as much info 
as I can on my console video setup.


I am using an Intel Atom D410 nettop here which works in Linux with 
the i915 driver.  You know, "works" for some version of the word 
which may be defined as "slightly more effective at displaying video 
than many doorstops".


The following line from my /etc/default/grub file may be relevant:

GRUB_CMDLINE_LINUX_DEFAULT="video=VGA-1:1280x1024 video=LDVS-1:d quiet splash"

This line is possibly relevant because the content and order of these 
arguments is significant.  The "primary" display of this chipset is 
LDVS-1, which does not even exist because this is a netbook machine.  
Nonetheless Linux fixes this at 1024x768.  It then sets VGA-1 to 
mirror this limited resolution.  It seems necessary to define VGA-1's 
resolution first, then to disable LDVS-1 in order to make the VGA 
display the primary one and then disable the useless dummy display.


I thought the issue might be that not all of my consoles share the 
same font due to an interaction between console-setup and Plymouth 
that causes tty1 not to have the appropriate font set until I do so 
by hand, however restarting it after all windows used the same font 
didn't resolve the issue.


BTW, copying a line works regardless of length, and the same for a 
word that begins on or before column 64.


Happy to help debug this if you've got some stuff you'd like me to 
try/log/trace.  I'm using a basic mouse here and GPM works fine, but 
GPM hasn't really kept pace with modern input devices since 1997.  My 
other mouse is an Apple Magic Trackpad, etc.  ;)


Incidentally, I've removed gpm for testing consolation and will for 
the time being remove consolation to restore gpm functionality.  The 
package indicates no need to do this, but it seems like a good idea.  
If that's unnecessary, please let me know.  Else I would suggest a 
change to the manpage and control file.


-- System Information:
Debian Release: stretch/sid
 APT prefers stable-updates
 APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages consolation depends on:
ii  libc6   2.23-4
ii  libevdev2   1.5.2+dfsg-1
ii  libinput10  1.4.0-1
ii  libudev1230-7

consolation recommends no packages.

consolation suggests no packages.

-- no debconf information

-- output of lsmod

Module  Size  Used by
nls_utf8   16384  0
nls_cp437  20480  0
vfat   20480  0
fat69632  1 vfat
hid_generic16384  0
cfg80211  573440  0
rfkill 24576  3 cfg80211
binfmt_misc20480  1
iTCO_wdt   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
joydev 20480  0
r8712u172032  0
coretemp   16384  0
sg 32768  0
i2c_i801   20480  0
pcspkr 16384  0
serio_raw  16384  0
snd_hda_codec_realtek86016  1
snd_hda_codec_generic69632  1 snd_hda_codec_realtek
snd_hda_intel  36864  4
snd_hda_codec 135168  3 
snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_intel
snd_hda_core   81920  4 
snd_hda_codec_realtek,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep  16384  1 snd_hda_codec
snd_pcm   106496  3 snd_hda_codec,snd_hda_intel,snd_hda_core
snd_timer  32768  1 snd_pcm
snd81920  15 
snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
soundcore  16384  1 snd
evdev  24576  11
lpc_ich24576  0
mfd_core   16384  1 lpc_ich
acpi_cpufreq   20480  0
tpm_tis20480  0
tpm45056  1 tpm_tis
processor  36864  1 acpi_cpufreq
sunrpc331776  1
autofs440960  2
ext4  593920  2
ecb16384  0
glue_helper16384  0
lrw16384  0
gf128mul   16384  1 lrw
ablk_helper16384  0
cryptd 20480  1 ablk_helper
aes_x86_64 20480  0
crc16  16384  1 ext4
jbd2  106496  1 ext4
crc32c_generic 16384  0
mbcache16384  3 ext4
hid_logitech_hidpp 28672  0
uas24576  0
usb_storage 

Bug#691627: Ubuntu lightdm patch

[T. Joseph Carter]

Hi,

It appears that Ubuntu has resolved this issue with the inclusion of 
the attached patch by Sean Davis .  It would 
allow you to change the Depends: line to use lightdm | gdm3, which 
appears to be what is wanted.


I just built a NM(N)U of xfswitch-plugin using this patch and it does 
indeed give me a button for the XFCE panel that, when pressed and 
confirmed, takes me back to lightdm.


This does not provide the regular Action Buttons applet the same 
functionality of course, but since that applet can't appear as a 
compact icon, I prefer xfswitch-plugin anyway.


Joseph

Description: Add support for dm-tool
 gdmflexiserver is no longer provided by lightdm. Use dm-tool if it is 
 available.
Author: Sean Davis 
Bug-Ubuntu: https://launchpad.net/bugs/1320560
Last-Update: 2014-10-11
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/panel-plugin/main.c
+++ b/panel-plugin/main.c
@@ -111,12 +111,20 @@
 static void
 cb_response (GtkDialog *dialog, gint response, gpointer user_data)
 {
+gchar *path;
+gchar *command;
+
 if (response == GTK_RESPONSE_YES)
 {
   GError *error = NULL;
 
-  if (!g_spawn_command_line_async ("gdmflexiserver --new",
-   ))
+  path = g_find_program_in_path ("dm-tool");
+  if (path != NULL)
+command = g_strdup("dm-tool switch-to-greeter");
+  else
+command = g_strdup("gdmflexiserver --new");
+
+  if (!g_spawn_command_line_async (command, ))
 {
   xfce_err (error->message);
   g_error_free (error);
@@ -124,6 +132,9 @@
 }
 
 gtk_widget_destroy (GTK_WIDGET (dialog));
+
+g_free (path);
+g_free (command);
 }
 
 

Bug#834994: consolation limiting to 64 columns

[T. Joseph Carter]

On Tue, Aug 23, 2016 at 03:47:42PM +0200, Bill Allombert wrote:

Intrigued by Consolation as a possible GPM replacement, so I figured I'd
remove that and give it a shot.


Congratulation you are the first victim!


Fixed.  ;)


BTW, copying a line works regardless of length, and the same for a word that
begins on or before column 64.


The code I use to get the screen size is as follow:

 if (ioctl(0, TIOCGWINSZ, )) perror("TIOCGWINSZ");
 screen_width  = s.ws_col;
 screen_height = s.ws_row;


That's strange because the value of 64 is never appropriate:

tjcarter@shiro:~$ echo `tty`: $TTY $COLUMNS $LINES
/dev/tty1: 160 64
tjcarter@shiro:~$ echo `tty`: $TTY $COLUMNS $LINES
/dev/tty2: 80 32

tty1 is using the default 8x16 font at 1280x1024.  tty2 is using 
TerminusBold's 16x32 option, so these numbers make sense at the 
terminal.


And again, after fixing this (just re-run setupcon either as root or 
from tty1) and restarting consolation, the consistent size for all 
consoles does not help.




and I never expected the size of the linux console to change during
boot. I am not sure whether consolation will receive a SIGWINCH
in this case.


The problem seems to carry over even if the package is installed and 
started on an already running system with consistent terminal sizes.


I do note that when the sizes are not consistent, consolation handled 
64 lines on one tty and 32 lines on another just fine, however both 
were limited to 64 columns.




In any case consolation should use the size of the terminal in use when
consolation is started. Could you check that ?


Yeah, I'd done that before I submitted the report.  Mentioned the 
rest about inconsistent ttys and 16x32 fonts because I thought it 
might be relevant to tracking down something that might've gotten out 
of sorts.


One thing I wonder about...  I mention that the hardware believes 
that I have two screens, one of which is 1024x768 dummy screen that 
happens to not actually exist.  I note that 1024/16 is 64.  But then, 
768/32 is only 24, and again it works on all 32 or 64 rows just fine 
so I think this might be a red herring.  And that ioctl should return 
in information about the current tty which is not configured to use 
the dummy screen at all.




Happy to help debug this if you've got some stuff you'd like me to
try/log/trace.  I'm using a basic mouse here and GPM works fine, but GPM
hasn't really kept pace with modern input devices since 1997.  My other
mouse is an Apple Magic Trackpad, etc.  ;)


Also consolation is fully plug and play, there is no need to configure
the device.


I configured nothing--I looked to see if there was something I might 
want to configure, but there wasn't.




Incidentally, I've removed gpm for testing consolation and will for the time
being remove consolation to restore gpm functionality.  The package
indicates no need to do this, but it seems like a good idea.  If that's
unnecessary, please let me know.  Else I would suggest a change to the
manpage and control file.


Well, theoretically you could use gpm for one device and consolation for
the others but in practive it is better to disable gpm while using
consolation, otherwise you get two cursors which is confusing.

Maybe consolation should conflict with gpm at some point.

In any case to switch between gpm and consolation you can do

/etc/init.d/gpm stop
/etc/init.d/consolation start


systemctl blah blah systemd still gives me headaches.  ;)


Any ideas?

Joseph

Bug#830482: Fresh installation causes freshclam to to fail

[T. Joseph Carter]

​​I don't know if I will hit upon the issue in this bug or not, but I'll
offer what I've just found in case it may be useful:

I found freshclam to fail freshly installed with the error message
indicated in this bug.  Here is my freshclam.conf upon installation:

```
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package

DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
LogRotate true
LogTime true
Foreground false
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 30
ReceiveTimeout 30
TestDatabases yes
ScriptedUpdates yes
CompressLocalDatabase no
SafeBrowsing false
Bytecode true
NotifyClamd /etc/clamav/clamd.conf
# Check for new database 24 times a day
Checks 24
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
```

If you comment out the UpdateLogFile line, it'll run but be marked as a
modified conffile.  Didn't bother to check that this allows the (dead
"success") systemd service to do more than just die with no error when run
because no combination of debconf settings with ucf seemed to achieve the
effect of commenting out that line.

If I reconfigure it via debconf, it can be started.  Upon reconfiguring, I
have this config file:

```
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package

DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
LogRotate false
LogTime true
Foreground false
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 30
ReceiveTimeout 30
TestDatabases yes
ScriptedUpdates yes
CompressLocalDatabase no
SafeBrowsing true
Bytecode true
NotifyClamd /etc/clamav/clamd.conf
# Check for new database 24 times a day
Checks 24
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
```
​
Upon doing this I can now start the daemon via systemctl and it stays
running.  My changes were minimal, and it appears the one that matters was
the log rotation setting.

I'm not sure in this configuration if systemd or freshclam is responsible
for logging.  If the latter, logs won't get rotated.  Before it'd rotate an
empty logfile and die.  Since it's no longer doing that, I assume systemd
is responsible and will rotate logs however it is configured to do so.
It's systemd, yay!

Hope that sheds some light on the problem.

Bug#873765: Solution to this bug

[T. Joseph Carter]

Hi,

I think this tool is probably important enough to Gnome users (sid or not)
that it's probably worthwhile to suggest a "patch" version that looks like
an upgrade from the 3.25 package that at least temporarily reverts to
3.22.  For now it's easy enough to manually revert the package, but all
sources (dpkg included) insist that you should not be doing that.

I'd have suggested it sooner but 3.25 was right around the corner...  I
imagine it still is, but it has been for weeks.

Joseph

Bug#870635: Broken upgrade

[T. Joseph Carter]

I just discovered my email configuration broken and, upon investigation, I
can see why.  I won't re-open this bug, however I believe that that
bringing mutt 1.9.1 in to Debian in a way that breaks people's
configurations in order to appease a developer who's frankly been openly
hostile and pissy throughout the entire process is unacceptable.

If a patched version of mutt is "illegal" then it is not free software and
must be removed from Debian.  It's that simple, and it's required by the
social contract.  If instead Kevin's ignorance of the law and claiming to
own the four characters "mutt" and demanding that Debian break upgrades for
the sake of his e-penis is all that is actually at issue here, then a
transitional package is appropriate and someone can create a mutt-vanilla
package assuming you can find someone willing to deal with upstream.

Just the perspective of an end user who had his email break unexpectedly.
I DO NOT LIKE my email being broken.

Joseph

Bug#907958: Please enable a2boot at configure time

[T. Joseph Carter]

Package: netatalk
Severity: Wishlist

Hi, could you possibly --enable-a2boot in your next compile?  Everything
else needed to configure booting Apple II systems off the network (yes,
people do that!) can be done by modifying an installed package, but the
support to enable it has to be baked in at build-time or it's not going to
work.  It builds without additional patches.  I'll look over the package to
see if there's anything else that might be worthwhile to make it a little
easier to set up, but it'd never be an out-of-box experience as it
presently requires non-free boot blocks.

Joseph

Bug#544651: lvmetad warnings

[T. Joseph Carter]

This warning, for a LUKS-encrypted system as configured by the Debian
installer, is spurious. The initrd assumes it should be looking for
lvmetad—it shouldn't be, but it doesn't realize that. The correct thing to
do here is not to remove the warning as Teemu Likonen suggested—if your
configuration requires lvmetad to be running and it isn't, you don't want
the initscripts to fail to inform you of the simple and obvious reason it's
not working. The Debian Way would be (and is—note Teemu's suggestion dates
to 2016 and the warning remains, as does this open bug report) to leave the
harmless warning alone since under a more complex LVM setup, it wouldn't be
harmless.

If you know you don't need lvmetad for your lvm setup (and for just basic
LUKS you don't), you teh internets say you can edit /etc/lvm/lvm.conf and
"use_lvmetad = 0", then rebuild your boot config (update-grub or whatever)
to disable trying to find it. In buster/sid, that's now already set and
there's a comment that the setting is now unused because lvmetad itself is
no longer used/provided in the Changelog.

As for cryptsetup not working from the installer, that's because cryptsetup
isn't installed in the installer environment. It's available as an "extra
module", a udeb package, installable from the main installer menu. Unless
you're using the advanced installer, you won't normally see that unless you
interrupt the "guided" process and go back. It can also be done by hand,
but that's honestly not well-documented and I don't recommend it to people
who post hate-filled screeds about how garbage something is because they
didn't bother to learn how it works first.

Assuming you didn't just decide that arch or something makes you more l33t
anyway, I'd recommend either using the live installer which provides a
proper userland rather than an ultra-limited barebones repair console, or
using the installer's menu system.

Joseph
Just a user who doesn't speak for Debian

Bug#925270: znc unwisely advertises exact Debian version

[T. Joseph Carter]

Package: znc
Severity: normal

Potential security implications here, but not directly exploitable—will
leave for the maintainer to determine how serious the problem is.

Debian's znc versions follow the upstream convention of advertising
themselves when the user exits them. This practice isn't terribly wise on
its own, but it also advertises the axact version of Debian (or derivative)
being run by the host. Worse, it's not even information that must be
queried—it's spammed into IRC channels upon quit. A few examples from today.

<-- nick (~u@h) has quit (Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in)
<-- nick (~u@h) has quit (Quit: ZNC 1.6.6+deb1ubuntu0.1 - http://znc.in)
<-- nick (~u@h) has quit (Quit: ZNC 1.6.5+deb1+deb9u1 - http://znc.in)

And one counter-example of how changing the default might be a good idea:

<-- nick (~u@h has quit (Quit: ZNC - https://znc.in)

As the host part of the u@h is often not concealed in any way, spamming
this information into a public forum might provide a nefarious user with
information for an attack of opportunity against an unprotected host. The
other way someone might usually obtain this information (CTCP request) in
most clients alerts the user that someone's asking, and can be replied to
with anything (or nothing)—I don't know if that's true of znc.

I mean, I suppose going into a crowded room and shouting something like the
OS you run exactly, that you haven't installed security updates in over two
weeks, and your IP address is something the user is perfectly happy to do.
Debian shouldn't preconfigure software to potentially do that by default.
I'd say this would warrant a 1.6.5-1+deb9u2 to disable that by default—but
that's up to you and the security team. :)

Joseph

Bug#933514: tmux: Screen garbling in ncurses apps

[T. Joseph Carter]

Looks like 3.0~rc4-1 will fix the problem when it migrates to unstable.

Joseph


On Thu, Aug 1, 2019 at 1:29 PM Romain Francoise  wrote:

> A patch for this is now available in the upstream bug tracker
> (https://github.com/tmux/tmux/issues/1861) and I have tested it
> successfully using the Mutt recipe from #933572.
>
>

Bug#380332: Also interested in this one

[T. Joseph Carter]

Upgrading my stretch box to buster, I got a lot of these familiar prompts,
and one very strange one from samba-common that used whiptail (debconf?)
and didn't even use a unified or context diff or set DPKG_CONFFILE_OLD/NEW.
(I should probably investigate what it's doing and file a bug about
that—NOT expected behavior!)

But samba's behavior got me thinking that it ought to be possible to change
the diff options or the pager or both. Seems that the pager is
configurable, so colordiff can be inserted there. But if you have a
preference for a different kind of diff, that's still not an option. Seems
I'd kinda like the option to throw the old and new conffile at vimdiff so
that I could quickly make whatever changes I wanted to, since that's what I
usually do anyway. But it seems the diff-side of things is all hard-coded
for the time being.

Essentially, "subscribe", along with the added thought that someone might
want to be able to use a diff-merge tool there rather than just a diff tool.

Joseph

Bug#939533: task-xfce-desktop: should use libreoffice-gtk3 instead of -gtk2

[T. Joseph Carter]

Package: task-xfce-desktop
Version: 3.55
Severity: normal

The XFCE task continues to depend on libreoffice-gtk2, but xfce 4.14 is
now fully gtk3-based and has dropped support for gtk2 integration. Time
to update to libreoffice-gtk3 for the task package?

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages task-xfce-desktop depends on:
ii  lightdm   1.26.0-5
ii  task-desktop  3.55
ii  tasksel   3.55
ii  xfce4 4.14

Versions of packages task-xfce-desktop recommends:
ii  atril 1.22.1-1
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-1
ii  dbus-x11 [dbus-session-bus]   1.12.16-1
ii  hunspell-en-us1:2018.04.16-1
ii  hyphen-en-us  2.8.8-7
ii  libreoffice   1:6.3.1~rc2-3
ii  libreoffice-gtk2  1:6.3.1~rc2-3
ii  libreoffice-help-en-us1:6.3.1~rc2-3
ii  light-locker  1.8.0-3
ii  mousepad  0.4.2-1
ii  mythes-en-us  1:6.3.0-1
ii  network-manager-gnome 1.8.22-2
ii  orca  3.32.0-1
ii  parole1.0.4-1
ii  quodlibet 4.2.1-1
ii  synaptic  0.84.6+b1
ii  system-config-printer 1.5.11-4
ii  tango-icon-theme  0.8.90-7
ii  xfce4-goodies 4.12.6
pn  xfce4-mixer   
ii  xfce4-power-manager   1.6.5-2
ii  xfce4-terminal0.8.8-1+b1
ii  xsane 0.999-7

task-xfce-desktop suggests no packages.

-- no debconf information

Bug#933514: tmux: Screen garbling in ncurses apps

[T. Joseph Carter]

Package: tmux
Version: 2.9a-2
Severity: important

The latest version of tmux has issues with screen updates under GNOME
Terminal with ncurses apps. This causes eg weechat's scrollback (pgup,
pgdn) to not draw correctly, causes specific issues with aptitude as
well.

I think this may be the result of the cherry-pick of 38b8a198bac6 from
upstream, you may need an additional patch as well.

I suspect the version of tmux found in experimental will not have this
problem, but I haven't tested it yet. I expect you're holding it due to
the freeze, but I do not believe 2.9a-2 makes a good release candidate.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tmux depends on:
ii  libc6   2.28-10
ii  libevent-2.1-6  2.1.8-stable-4
ii  libtinfo6   6.1+20190713-1
ii  libutempter01.1.6-3+b1

tmux recommends no packages.

tmux suggests no packages.

-- no debconf information

Bug#933514: tmux: Screen garbling in ncurses apps

[T. Joseph Carter]

Oh Sven, that does look related, and I didn't even notice that ncurses-base
got updated too or I'd have investigated it. Looks like this is a ncurses
problem. Did you find changing TERM fixed it?

Joseph


On Wed, Jul 31, 2019 at 5:31 PM T. Joseph Carter <
tjcar...@spiritsubstance.com> wrote:

> It's hard to know what exactly causes it under aptitude. I did try it
> using 3.0~rc3-1 from experimental and it does have a similar bug, I'm not
> sure if it's quite the same though (it's glitching in aptitude in
> inconsistent ways that I can't seem to exactly reproduce from one minute to
> the next.)
>
> A very easy way to see it with weechat is to have a window with more than
> one screenful in it (buffer 1 works) and use pgup/pgdn. You'll see the top
> several lines redraw, but only those.
>
> Have a look at the attached screenshots. Notice that when I pgup, only the
> top ~13 lines get redrawn and whitespace doesn't clear correctly. Below
> that doesn't get redrawn at all.
>
> Version of gnome-terminal is 3.30.2-2 with libvte-2.91-0 version 0.54.2-2.
> Hope that helps some.
>
> Joseph
>
>
> On Wed, Jul 31, 2019 at 11:05 AM Sven Joachim  wrote:
>
>> On 2019-07-31 09:18 +0200, Romain Francoise wrote:
>>
>> > On Wed, Jul 31, 2019 at 5:42 AM T. Joseph Carter
>> >  wrote:
>> >> The latest version of tmux has issues with screen updates under GNOME
>> >> Terminal with ncurses apps. This causes eg weechat's scrollback (pgup,
>> >> pgdn) to not draw correctly, causes specific issues with aptitude as
>> >> well.
>> >
>> > Thanks for the report. I don't use GNOME Terminal and I haven't
>> > experienced any similar issues myself, but I will investigate.
>> >
>> > Can you provide more details about how to reproduce using aptitude?
>> >
>> >> I think this may be the result of the cherry-pick of 38b8a198bac6 from
>> >> upstream, you may need an additional patch as well.
>> >
>> > Why? This is a fix for a crash which doesn't look related.
>> >
>> > Do you experience the issue only when multiple panes are used in a
>> window?
>> >
>> >> I suspect the version of tmux found in experimental will not have this
>> >> problem, but I haven't tested it yet. I expect you're holding it due to
>> >> the freeze, but I do not believe 2.9a-2 makes a good release candidate.
>> >
>> > No, the freeze is over but the 3.0 release was pushed back to October,
>> > so 3.0-rc will remain in experimental for the immediate future.
>>
>> Maybe the problems with screen updates have been triggered by
>> ncurses-base 6.1+20190713-1, see #933572?  I could reproduce that one
>> with tmux 2.8-3, 2.9a-2 and 3.0~rc3-1.
>>
>> Cheers,
>>Sven
>>
>>

Bug#954405: grub-common: No provision for using grub-theme-* with 05_debian_theme

[T. Joseph Carter]

Package: grub-common
Version: 2.04-5
Severity: minor

Researching why gfx didn't work in grub for me on this system, I
discovered that 05_debian_theme blocks the use of grub's native theming,
including grub-theme-starfield. The suggestion I've found elsewhere is
to chmod -x /etc/grub.d/05_debian_theme so it doesn't do that. This
seems like a poor solution.

You could check for $GRUB_THEME to be set and bail early if it is, I
suppose, but there's no guarantee that $GRUB_THEME was able to be used
other than to repeat these tests currently around line 278 of 00_header:

if [ "x$GRUB_THEME" != x ] && [ -f "$GRUB_THEME" ] \
&& is_path_readable_by_grub "$GRUB_THEME"; then

If you bail on the Debian theme if $GRUB_THEME is set under those
conditions, it would be as robust as 00_header is. Checking that and
adding options to override the colors as requested in #714414 would make
the cosmetics pretty configurable without altering package-installed
files.

(As for my own config and why it didn't work? LUKS2, which is obvious
once I thought about it. I'd file a bug about it, if I had a brilliant
suggestion for a solution, other than maybe to make a note in some
README file I probably wouldn't have looked at before I got this far
into it anyway.)

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/chiyo--vg-root / ext4 rw,relatime,discard,errors=remount-ro 0 0
/dev/nvme0n1p2 /boot ext4 rw,relatime,discard 0 0
/dev/nvme0n1p1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/mapper/sdb1_crypt /srv ext4 rw,relatime,discard 0 0
/dev/fuse /run/user/1000/doc fuse 
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  ee1fddd0-b814-417a-a985-4cc0a2c3f7b2
else
  search --no-floppy --fs-uuid --set=root ee1fddd0-b814-417a-a985-4cc0a2c3f7b2
fi
if loadfont /grub/unicode.pf2 ; then
  set gfxmode=800x600x24
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  ee1fddd0-b814-417a-a985-4cc0a2c3f7b2
else
  search --no-floppy --fs-uuid --set=root ee1fddd0-b814-417a-a985-4cc0a2c3f7b2
fi
insmod png
background_image -m stretch /grub/custom-splash/desktop-grub.png
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  ee1fddd0-b814-417a-a985-4cc0a2c3f7b2
else
  search --no-floppy --fs-uuid --set=root ee1fddd0-b814-417a-a985-4cc0a2c3f7b2
fi
insmod png
if background_image /grub/custom-splash/desktop-grub.png; then
  true
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-7471ddbe-d2c8-4f56-96c1-ee9612516d19' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy 

Bug#992457: Broken by irresponsible removal of tempfile in debianutils

[T. Joseph Carter]

Package: console-setup
Version: 1.205
Severity: important
X-Debbugs-Cc: 

Debianutils >= 5 removes tempname and puts a deprecation notice on the
which command. The setupcon script (at least) uses both of these,
causing people's initramfs's to be subtly broken and leaving them
without a keymap in the event of a boot error., Since the maintainer of
Debianutils seems to be content to put out fires as they come up with
the excuse that the stable version of Debian declares these to be
deprecated (y'know, the one that was released a week ago at time of
writing), it is apparently incumbent upon others to fix this in their
packages.

It's debianutils' bug, really, and the bugs keep getting filed (and
resolved), but there's a half a dozen packages on my system that are
broken by it. Yours happens to be used at boot time and for general
system operation.

If you're busy and debianutils' change doesn't get reverted, I can
prepare a patch. It's literally replacing tempfile and which with their
more generic equivalents, after all.

-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages console-setup depends on:
ii  console-setup-linux 1.205
ii  debconf 1.5.77
ii  keyboard-configuration  1.205
ii  xkb-data2.33-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.31-16
ii  lsb-base  11.1.0

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.77
ii  liblocale-gettext-perl  1.07-4+b1

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.60
ii  kbd 2.3.0-3
ii  keyboard-configuration  1.205

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
ii  gnome-control-center  1:3.38.4-1
ii  kbd   2.3.0-3
ii  systemd   247.9-1

-- debconf information:
  keyboard-configuration/layout:
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/ctrl_alt_bksp: false
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
* console-setup/fontsize-fb47: 16x32 (framebuffer only)
  keyboard-configuration/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/xkb-keymap: us
  console-setup/fontsize: 16x32
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/model: Generic 105-key PC (intl.)
  keyboard-configuration/toggle: No toggling
  console-setup/framebuffer_only:
  keyboard-configuration/layoutcode: us
  keyboard-configuration/optionscode:
  keyboard-configuration/compose: No compose key
  keyboard-configuration/modelcode: pc105
  keyboard-configuration/variantcode:
  keyboard-configuration/unsupported_config_layout: true
  console-setup/fontsize-text47: 16x32 (framebuffer only)
  console-setup/store_defaults_in_debconf_db: true
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/unsupported_options: true
  keyboard-configuration/other:
* console-setup/fontface47: TerminusBold
  console-setup/guess_font:
* keyboard-configuration/variant: English (US)
* console-setup/charmap47: UTF-8
  console-setup/codesetcode: Lat15
  console-setup/use_system_font:

Bug#1051739: 1.26.0-3 uninstallable due to nonexistent package

[T. Joseph Carter]

Package: caja-dropbox
Version: 1.26.0-3
Severity: normal

-3 of this package cannot be installed because it depends on:

> --- libayatana-appindicator1 | libappindicator1 (UNAVAILABLE)

libayatana-appindicator3-1 is available on bookworm, but not
testing or sid. Adding this was done apparently to fix an Ubuntu bug,
but it completely broke the package installation for Debian.

Actually, it broke the package on Ubuntu too—the only version of Ubuntu
that has libayatana-appindicator1 is 22.10. It's not in 23.04 and won't
be in 23.10 either.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-0-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages caja-dropbox (1.26.0-2) depends on:
ii  dbus-x11  1.14.10-1
ii  gir1.2-gdkpixbuf-2.0  2.42.10+dfsg-1+b1
ii  gir1.2-glib-2.0   1.78.0-1
ii  gir1.2-gtk-3.03.24.38-5
ii  gir1.2-pango-1.0  1.51.0+ds-2
ii  libc6 2.37-8
ii  libcaja-extension11.26.1-1
ii  libglib2.0-0  2.78.0-1
ii  libgtk-3-03.24.38-5
ii  policykit-1   123-1
ii  procps2:4.0.3-1
ii  python3   3.11.4-5+b1
ii  python3-gi3.44.1-2
ii  python3-gpg   1.18.0-3+b1

caja-dropbox recommends no packages.

Versions of packages caja-dropbox suggests:
ii  caja  1.26.1-1

-- no debconf information

Bug#1020740: cpu-x needs to be recompiled against current libpci

[T. Joseph Carter]

Package: cpu-x
Version: 4.3.1-1
Severity: important
X-Debbugs-Cc: Mike Gabriel 

Cc to Mike Martin as Martin's email address no longer works because he
no longer works for Canonical:

https://www.omgubuntu.co.uk/2021/02/martin-wimpress-ubuntu-desktop-lead-leaving-canonical

If there's another email address to reach him at, I don't know it.

When I run cpu-x, messages about the wrong version of libpci being used
are printed:

tjcarter@aki:~$ cpu-x
CPU-X:core.c:674: pci_access is not properly initialized: it is a common issue 
when CPU-X was built with a lower libpci version.
Check that libpci 3.7.0 library is present on your system. Otherwise, please 
rebuild CPU-X.
No kernel driver in use for graphic card at path (null)
Your GPU user mode driver is unknown: 4.6 (Compatibility Profile) Mesa 
22.2.0-rc3

The message even describes how to fix it: Recompile against the current
libpci version. I did so, and:

tjcarter@aki:~/Source/cpu-x/cpu-x-4.3.1$ obj-x86_64-linux-gnu/output/bin/cpu-x 
--dump
There is no platform with OpenCL support (CL_PLATFORM_NOT_FOUND_KHR)
  >> CPU <<

* Processor *
  Vendor: AMD
   Code Name: Ryzen 7 (Matisse)
:

:
Swap: 10.24 GiB / 65.00 GiB


  >> Graphics <<

* Card 0 *
  Vendor: AMD
  Driver: amdgpu
 UMD Version: Mesa 22.2.0-rc3
:


Perhaps libpci needs to be tightened up to ensure that programs like
cpu-x get rebuilt? It appears the ABI has changed incompatibly without
bumping the soname, and this happens often enough to warrant an
explanation of how to fix it in the downstream program. (That's gotta be
frustrating for the devs!)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.19.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cpu-x depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  libc62.34-8
ii  libcairo21.16.0-6
ii  libcpuid15   0.5.1+repack1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libgl1   1.5.0-1
ii  libglfw3 3.3.8-1
ii  libglib2.0-0 2.74.0-1
ii  libgtk-3-0   3.24.34-3
ii  libncursesw6 6.3+20220423-2
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpci3  1:3.8.0-1
ii  libprocps8   2:3.3.17-7+b1
ii  libtinfo66.3+20220423-2
ii  procps   2:3.3.17-7+b1

cpu-x recommends no packages.

cpu-x suggests no packages.

-- no debconf information

Bug#1023992: Please build Corsair Commander Pro module

[T. Joseph Carter]

Package: src:linux
Version: 6.0.8-1
Severity: normal

Request building CONFIG_SENSORS_CORSAIR_CPRO module:

/boot/config-6.0.0-2-amd64:# CONFIG_SENSORS_CORSAIR_CPRO is not set
/boot/config-6.0.0-3-amd64:# CONFIG_SENSORS_CORSAIR_CPRO is not set
/boot/config-6.0.0-4-amd64:# CONFIG_SENSORS_CORSAIR_CPRO is not set

This module provides hwmon functions for my CPU cooler.

Thanks!

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUS
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 4204
board_vendor: ASUSTeK COMPUTER INC.
board_name: TUF GAMING X570-PRO WIFI II
board_version: Rev X.0x

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
Root Complex [1022:1480]
Subsystem: ASUSTeK Computer Inc. Starship/Matisse Root Complex 
[1043:87c0]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
GPP Bridge [1022:1483] (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. Starship/Matisse GPP Bridge [1043:87c0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
DeviceName:  Onboard IGD
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse 
PCIe Dummy Host Bridge [1022:1482]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller 
[1022:790b] (rev 61)
Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller [1043:87c0]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: nvme
Kernel modules: nvme

02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse Switch 
Upstream [1022:57ad] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

03:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP 
Bridge [1022:57a3] (prog-if 00 [Normal decode])
Subsystem: ASUSTeK Computer Inc. Matisse PCIe GPP Bridge [1043:87c0]
Control: I/O+ Mem+ BusMaster+ 

Bug#1032867: suggests wx3.0-doc

[T. Joseph Carter]

Package: python3-wxgtk4.0
Version: 4.2.0+dfsg-2
Severity: minor

This package still suggests: wx3.0-doc, perhaps wx3.2-doc is now
intended? Severity: minor as you can obviously install it yourself, but
given the 4.0/3.2 sort of confusion with wxWidgets and wxPython, it's
worth fixing.

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-wxgtk4.0 depends on:
ii  libc6 2.36-8
ii  libgcc-s1 12.2.0-14
ii  libstdc++612.2.0-14
ii  libwxbase3.2-13.2.2+dfsg-2
ii  libwxgtk-gl3.2-1  3.2.2+dfsg-2
ii  libwxgtk3.2-1 3.2.2+dfsg-2
ii  python3   3.11.2-1
ii  python3-numpy 1:1.24.2-1
ii  python3-pil   9.4.0-1.1+b1
ii  python3-six   1.16.0-4

python3-wxgtk4.0 recommends no packages.

Versions of packages python3-wxgtk4.0 suggests:
ii  wx3.0-doc  3.0.5.1+dfsg-5

-- no debconf information

Bug#1031734: ibus-braille-preferences crashes when run

[T. Joseph Carter]

Package: ibus-braille
Version: 0.3-7
Severity: important

Upon running ibus-braille-preferences, I get this error:

```
aki:~ $ ibus-braille-preferences 
/usr/share/ibus-braille-preferences/main.py:24: PyGIWarning: Gtk was imported 
without specifying a version first. Use gi.require_version('Gtk', '4.0') before 
import to ensure that the right version gets loaded.
  from gi.repository import Gtk
/usr/share/ibus-braille-preferences/main.py:26: PyGIWarning: IBus was imported 
without specifying a version first. Use gi.require_version('IBus', '1.0') 
before import to ensure that the right version gets loaded.
  from gi.repository import IBus
Traceback (most recent call last):
  File "/usr/share/ibus-braille-preferences/main.py", line 265, in 
ibus_sharada_braille_preferences()
  File "/usr/share/ibus-braille-preferences/main.py", line 36, in __init__

self.guibuilder.add_from_file("/usr/share/ibus-braille-preferences/ui.glade")
gi.repository.GLib.GError: gtk-builder-error-quark: 
/usr/share/ibus-braille-preferences/ui.glade:75:52 Invalid property: 
GtkBox.border_width (11)
```

I suspect PyGIWarning is the clue: This probably requires GTK+ 3.x, not
4.x, but it doesn't specify what it needs. Seems line 26 is also going
to cause a potential problem. I suspect judicious use of the following
three lines added to a couple source files will fix it:

```python
from gi import require_version
require_version('Gtk', '3.0')
require_version('IBus', '1.0')
```

At least, that was all it took to get the preferences applet to run.
Didn't test the abbreviation or language editor with similar patches.

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ibus-braille depends on:
ii  gir1.2-ibus-1.0   1.5.27-4
ii  gir1.2-pango-1.0  1.50.12+ds-1
ii  python3   3.11.1-3
ii  python3-espeak0.5-5+b1
ii  python3-gi3.42.2-3+b1
ii  python3-louis 3.24.0-1

Versions of packages ibus-braille recommends:
ii  python3-speechd  0.11.4-2

ibus-braille suggests no packages.

-- no debconf information

Bug#1034607: xfce4-screensaver vs light-locker

[T. Joseph Carter]

Package: task-desktop-xfce
Version: 3.72
Severity: normal

Request to allow xfce4-screensaver at least as an alternative to
light-locker.

-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1037936: Qt6: Dialog minimum size larger than screen

[T. Joseph Carter]

Package: qbittorrent
Version: 4.5.3-2
Severity: normal
Tags: a11y upstream

The new Qt6 version of qBittorrent apparently does a better job reading
my font size settings from XFCE. The result is that fonts are scaled up
in a way that's comfortably easier for a legally blind reader … except
the torrent options dialog no longer fits on screen.

I've tried shrinking this to fit, but the minimum size possible still
has to fit everything the dialog contains within that minimum dialog
size.

A solution to this might be to place the dialog's controls inside a
widget which can scroll if the dialog is smaller than its contents. I
don't really code Qt stuff, so I don't know what widget that would be,
but I'm betting the devs do.

Workaround for now is to know how to grab a window by something other
than the titlebar in your WM or whatever one does under Wayland and move
the titlebar offscreen so you can reach the options and buttons at the
bottom of the larger than the screen dialog.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qbittorrent depends on:
ii  libc62.36-9
ii  libgcc-s113.1.0-5
ii  libqt5sql5-sqlite5.15.8+dfsg-12
ii  libqt6core6  6.4.2+dfsg-11
ii  libqt6dbus6  6.4.2+dfsg-11
ii  libqt6gui6   6.4.2+dfsg-11
ii  libqt6network6   6.4.2+dfsg-11
ii  libqt6sql6   6.4.2+dfsg-11
ii  libqt6widgets6   6.4.2+dfsg-11
ii  libqt6xml6   6.4.2+dfsg-11
ii  libssl3  3.0.9-1
ii  libstdc++6   13.1.0-5
ii  libtorrent-rasterbar2.0  2.0.9-1
ii  zlib1g   1:1.2.13.dfsg-1

qbittorrent recommends no packages.

qbittorrent suggests no packages.

-- no debconf information

Bug#1041358: web-ui downloads extentionless page without

[T. Joseph Carter]

Package: qbittorrent-nox
Version: 4.5.4-1
Severity: important

The primary (really only) way to use qbittorrent-nox is via the web UI.
This works in stable (4.5.2) as expected, but in sid it downloads a file
with a name like "4Az117Jo" (random), no extension, and no MIME type.
Firefox, Chromium, and Brave all just save the file without displaying
it—it's the web UI login page as expected.

This is definitely a problem for how the -nox package is used (and
affects the GUI package as well, but it would be Severity: normal for
that package), and I've filed this as issue #19330 against the
qBittorrent upstream on Github.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qbittorrent-nox depends on:
ii  libc62.37-6
ii  libgcc-s113.1.0-8
ii  libqt6core6  6.4.2+dfsg-11
ii  libqt6network6   6.4.2+dfsg-11
ii  libqt6sql6   6.4.2+dfsg-11
ii  libqt6sql6-sqlite6.4.2+dfsg-11
ii  libqt6xml6   6.4.2+dfsg-11
ii  libssl3  3.0.9-1
ii  libstdc++6   13.1.0-8
ii  libtorrent-rasterbar2.0  2.0.9-1
ii  zlib1g   1:1.2.13.dfsg-1

qbittorrent-nox recommends no packages.

qbittorrent-nox suggests no packages.

-- no debconf information

Bug#1041192: Recommends: exuberant-ctags, not ctags?

[T. Joseph Carter]

Package: seascope
Version: 0.9+8a669e0e-3
Severity: normal

I've noted that seascope Recommends: exuberant-ctags which for the
longest time was the only form of ctags in Debian. universal-ctags now
exists as an alternative. Might any ctags be used for seascope or is
there a particular reason to prefer exuberant-ctags?


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages seascope depends on:
ii  python3  3.11.4-3
ii  python3-pyqt55.15.9+dfsg-1
ii  python3-pyqt5.qsci   2.13.3+dfsg-3
ii  python3-pyqt5.qtsvg  5.15.9+dfsg-1

Versions of packages seascope recommends:
ii  cscope   15.9-1
pn  exuberant-ctags  
ii  id-utils 4.6.28-20200521ss15dab+b1

seascope suggests no packages.

-- no debconf information

Bug#1039889: recommends old ffmpeg libs

[T. Joseph Carter]

Package: pqiv
Version: 2.12-1+b1
Severity: normal

The libavcodec and friends versions pqiv currently expects to use are
not available in stable, let alone unstable. Might be fixed by
recompile?

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pqiv depends on:
ii  libc6 2.36-9
ii  libcairo2 1.16.0-7
ii  libglib2.0-0  2.74.6-2
ii  libgtk-3-03.24.37-2
ii  libx11-6  2:1.8.6-1

Versions of packages pqiv recommends:
ii  libarchive13   3.6.2-1
pn  libavcodec58   
pn  libavformat58  
pn  libavutil56
ii  libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1
ii  libmagickwand-6.q16-6  8:6.9.11.60+dfsg-1.6
ii  libpoppler-glib8   22.12.0-2+b1
pn  libswscale5
ii  libwebp7   1.2.4-0.2

pqiv suggests no packages.

-- no debconf information

Bug#1063686: installation-reports: GUI checkbox in high contrast dark mode isn't high contrast

[T. Joseph Carter]

Package: installation-reports
Severity: wishlist

Either normal/a11y or wishlist depending how you wanna call it.

I normally use the slang version of the Debian installer. Because I'm
using a 14" 1080p portable monitor here, I decided to use the GUI. In
dark mode because albino. Bright = pain. Sub-optimal install for me,
will switch to ssh as soon as the network's configured.

Went to select installer components because parted pls, but when I
selected it, I didn't see that it was selected at first. That's odd.
Then I looked closer and … oh yeah, I guess it is selected. Just this
theme/widget set uses a very small/thin checkmark inside the box.

Basically, I'd like a checkbox whose checked/unchecked states are more
visually not the same. Particularly important in the dark mode, since
that's intended to be high contrast for accessibility reasons. (Which is
why I was using it…)

Suggest a bigger/bolder checkmark might be the path of least resistance
for a fix.

Boot method: usb
Image version: 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.5.0-amd64-netinst.iso
Date: Sat, 10 Feb 2024 17:54:18 -0800 (in the middle of installing now)

Machine: Ryzen 3000 series with B450 chipset
Partitions: 

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [?] ← Here's where I noticed the problem

Bug#1064318: bash: manpage lists incorrect filename (/etc/bash.bash.logout)

[T. Joseph Carter]

Package: bash
Version: 5.2.21-2
Severity: minor

Dear Maintainer,

The manpage for base states:

```
FILES
   /bin/bash
  The bash executable
   /etc/profile
  The systemwide initialization file, executed for login shells
   /etc/bash.bashrc
  The systemwide per-interactive-shell startup file
   /etc/bash.bash.logout
  The systemwide login shell cleanup file, executed when a login 
shell exits
```

This is incorrect, bash invokes /etc/bash.bash_logout.

Debian doesn't provide a bash.bash_logout so I know about this because I
was tinkering with adding stuff to these to find bash's config files in
XDG-standard locations, if they exist, since I keep ~/.config in git.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bash depends on:
ii  base-files   13
ii  debianutils  5.16
ii  libc62.37-15
ii  libtinfo66.4+20240113-1

Versions of packages bash recommends:
ii  bash-completion  1:2.11-8

Versions of packages bash suggests:
ii  bash-doc  5.2.21-2

-- Configuration Files:
/etc/bash.bashrc changed [not included]

-- no debconf information

Bug#996432: ITS: newlib

[T. Joseph Carter]

Package: libnewlib-arm-none-eabi
Version: 3.3.0-1.3
Followup-For: Bug #996432

Hi John,

Your ITS was posted quite a long time ago and the maintainer is utterly
MIA on this package. It's absolutely breaking stuff so that
gcc-arm-none-eabi cannot be installed in trixie/sid alongside this
package, which is required for the things you'd install that compiler
for.

Is this still something you're willing to work on? Is there some way
folks can assist/help test/help package/something, or are you literally
waiting on sponsors or … ?

Happy to help if I can.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libnewlib-arm-none-eabi depends on:
ii  libnewlib-dev  3.3.0-1.3

Versions of packages libnewlib-arm-none-eabi recommends:
ii  gcc-arm-none-eabi   15:12.2.rel1-1
ii  libstdc++-arm-none-eabi-newlib  15:12.2.rel1-1+23

Versions of packages libnewlib-arm-none-eabi suggests:
pn  libnewlib-doc  

-- no debconf information

Bug#1069791: console-setup: Build larger console fonts for HiDPI/accessibility with future 6.9 kernels

[T. Joseph Carter]

Package: console-setup
Version: 1.226
Severity: wishlist

Dear Maintainer,

Linux kernel 6.9+ will support larger font sizes for HiDPI screens. This
is probably aimed at "more than 4k" monitors, but for accessibility
reasons it would be really useful to have larger sizes available sooner
for those of us already have 4k sorts of screens.

Perhaps this might best be done by putting those huge-sized fonts in an
appropriately named -huge fonts package? I'll leave the implementation
details to you, this is just a request for the fonts to be created.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages console-setup depends on:
ii  console-setup-linux 1.226
ii  debconf [debconf-2.0]   1.5.86
ii  keyboard-configuration  1.226
ii  xkb-data2.41-2

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales2.37-18
ii  sysvinit-utils [lsb-base]  3.09-1

Versions of packages keyboard-configuration depends on:
ii  debconf [debconf-2.0]   1.5.86
ii  liblocale-gettext-perl  1.07-7
ii  xkb-data2.41-2

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.66
ii  kbd 2.6.4-2
ii  keyboard-configuration  1.226

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.6.4-2
ii  systemd   255.4-1+b1

-- debconf information:
  keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_options: true
  console-setup/guess_font:
  keyboard-configuration/unsupported_layout: true
  console-setup/fontsize: 16x32
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  keyboard-configuration/optionscode:
  console-setup/framebuffer_only:
  keyboard-configuration/layout:
  console-setup/fontsize-text47: 16x32 (framebuffer only)
* console-setup/charmap47: UTF-8
  keyboard-configuration/other:
  keyboard-configuration/model: Generic 105-key PC
  keyboard-configuration/switch: No temporary switch
* console-setup/fontsize-fb47: 16x32 (framebuffer only)
  keyboard-configuration/store_defaults_in_debconf_db: true
  keyboard-configuration/toggle: No toggling
  console-setup/store_defaults_in_debconf_db: true
  debian-installer/console-setup-udeb/title:
  keyboard-configuration/variantcode:
* keyboard-configuration/variant: English (US)
  console-setup/use_system_font:
  keyboard-configuration/layoutcode: us
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/compose: No compose key
  console-setup/codesetcode: Lat15
* console-setup/fontface47: TerminusBold
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/xkb-keymap: us
  keyboard-configuration/modelcode: pc105

Bug#1068528: xfce4-settings: xfce4-find-cursor does nothing without … sudo?

[T. Joseph Carter]

Package: xfce4-settings
Version: 4.18.3-1+b1
Severity: normal

Dear Maintainer,

Discovered that xfce4-find-cursor (an accessibility feature) does not
work without the use of sudo. Permissions issue of some sort? Should
this program be installed with some sgid to access something? I can't
imagine what offhand.

This isn't documented as far as I can tell. Someone asked why it was
necessary to run this with root privs two years ago on askubuntu (no
answer) and that's all I could find amongst the AI trash and unrelated
responses. If there's some optional permissions I should be changing to
make this work, the changes aren't documented and there don't appear to
be any measures in place to preserve those changes in maintainer scripts
from a quick glance.

If it turns out to matter, Xorg with xfwm4 on AMD (6700 XT) using open
source drivers.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-settings depends on:
ii  exo-utils4.18.0-1+b2
ii  libatk1.0-0t64   2.52.0-1
ii  libc62.37-15.1
ii  libcairo-gobject21.18.0-3
ii  libcairo21.18.0-3
ii  libcolord2   1.4.7-1+b1
ii  libexo-2-0   4.18.0-1+b2
ii  libfontconfig1   2.15.0-1.1
ii  libgarcon-1-04.18.1-1+b2
ii  libgarcon-common 4.18.1-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b2
ii  libglib2.0-0t64  2.78.4-6
ii  libgtk-3-0t643.24.41-4
ii  libnotify4   0.8.3-1+b1
ii  libpango-1.0-0   1.52.1+ds-1
ii  libpangocairo-1.0-0  1.52.1+ds-1
ii  libupower-glib3  1.90.2-8+b1
ii  libx11-6 2:1.8.7-1
ii  libxcursor1  1:1.2.1-1
ii  libxfce4ui-2-0   4.18.4-1+b1
ii  libxfce4util74.18.1-2+b1
ii  libxfconf-0-34.18.1-1+b2
ii  libxi6   2:1.8.1-1
ii  libxklavier165.4-5+b1
ii  libxrandr2   2:1.5.4-1
ii  xfce4-helpers4.18.3-1+b1
ii  xfconf   4.18.1-1+b2

Versions of packages xfce4-settings recommends:
ii  colord 1.4.7-1+b1
ii  x11-utils  7.7+6+b1
ii  xiccd  0.3.0-2+b1

xfce4-settings suggests no packages.

-- no debconf information