Bug#672250: rss-glx: pixelcity/helios/drempels/lorenz/fieldlines keep running in the background, eating up the cpu

2024-08-29 Thread Marc Donges 
I started sundancer2 within xscreensaver-demo and then clicked on
another screensaver, causing xscreensaver-demo to hang.

When started manually on the cli, the screensaver stops and exits
properly.

Attaching to process 316961
[New LWP 316963]
[New LWP 316962]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f76cdfbbb5f in __GI___poll (fds=0x7ffec5852e38, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29

warning: 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory
(gdb) bt
#0  0x7f76cdfbbb5f in __GI___poll (fds=0x7ffec5852e38, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f76cddb4d82 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f76cddb7242 in xcb_wait_for_special_event () from 
/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f76cdd4fff8 in glLabelObjectEXT () from 
/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#4  0x7f76cdd501c8 in glLabelObjectEXT () from 
/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#5  0x7f76cdd52a61 in glLabelObjectEXT () from 
/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#6  0x7f76cdd52d6d in glLabelObjectEXT () from 
/lib/x86_64-linux-gnu/libGLX_mesa.so.0
#7  0x7f76cb4b9f85 in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so
#8  0x7f76cb4ba02e in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so
#9  0x7f76cb4bd1e4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so
#10 0x7f76cb58abcf in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so
#11 0x7f76cb58bab5 in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so
#12 0x7f76cb7f90c7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so
#13 0x7f76cb7fdb7d in ?? () from /usr/lib/x86_64-linux-gnu/dri/crocus_dri.so
#14 0x564b297acabe in hack_draw (XStuff=, 
currentTime=1724973929.092783, frameTime=)
at ./src/sundancer2.c:176
#15 0x564b297ac0e3 in mainLoop () at ./src/driver.c:240
#16 0x564b297ab627 in main (argc=4, argv=0x7ffec58538f8) at 
./src/driver.c:463
(gdb)

Bug#1075676: xoscope: ftbfs with GCC-14

2024-08-29 Thread Marc Donges 
Control: tags -1 patch

The following patch fixes builds with gcc-14.

Description: Fix FTBFS with GCC 14
Author: Marc Donges 
Bug-Debian: https://bugs.debian.org/1075676
Last-Update: 2024-08-07

--- xoscope-2.3.orig/configure.ac
+++ xoscope-2.3/configure.ac
@@ -61,8 +61,8 @@ AS_IF([test "$ac_cv_lib_comedi_comedi_op
 	[AC_MSG_CHECKING([how many arguments comedi_get_cmd_generic_timed takes])
 	AC_COMPILE_IFELSE([AC_LANG_SOURCE([
 #include 
-main() {
-   comedi_get_cmd_generic_timed(NULL, NULL, NULL, 0, 0);
+int main() {
+   comedi_get_cmd_generic_timed(NULL, 0, NULL, 0, 0);
 }])], comedi_get_cmd_generic_timed=5args, comedi_get_cmd_generic_timed=4args)
 
 if test x"$comedi_get_cmd_generic_timed" = x5args; then

Bug#1079590: scratch3 does not run on Pi2

2024-08-24 Thread Marc Donges 
Package: scratch3
Version: 3.30.9
Severity: important
X-Debbugs-Cc: marc.don...@gmail.com

On a current Raspberry Pi OS (bookworm, x86) I installed scratch3. After 
starting it with scratch-desktop, it took several minutes just to show the 
error message that WebGL is not supported. If this is intended and there is 
actually a hardware requirement not met, this should be in the package 
description to save the user from the experience of downloading, installing and 
booting the software just for an error message.



-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 12 (bookworm)
Release:12
Codename:   bookworm
Architecture: armv7l

Kernel: Linux 6.6.31+rpt-rpi-v7 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages scratch3 depends on:
ii  libayatana-appindicator1 [libappindicator1]  0.5.92-1
ii  libnotify4   0.8.1-1
ii  libnss3  2:3.87.1-1
ii  libxtst6 2:1.2.3-1.1
ii  rtimucli 0.1
ii  sense-emu-tools  1.2.2

Versions of packages scratch3 recommends:
ii  libayatana-appindicator3-1 [libappindicator3-1]  0.5.92-1

scratch3 suggests no packages.

-- no debconf information

Bug#1079373: munin-plugins-btrfs unconditionally depends on munin-node

2024-08-22 Thread Marc Donges 
Package: munin-plugins-btrfs
Version: 13-1
Severity: normal
X-Debbugs-Cc: marc.don...@gmail.com

Dear Maintainer,

munin-plugins-btrfs unconditionally depends on munin-node, which means it 
cannot be installed with munin-node-c.

munin-node-c is an alternative implementation to munin-node, hence it declares 
a conflict on munin-node. munin-plugin-btrfs's declared dependency on 
munin-node thus makes it uninstallable with munin-node-c. This is although it 
would work fine with munin-node-c.

A number of solutions is possible, also in munin-node-c. I am reporting this 
bug against munin-plugins-btrfs because it is the one munin-node-plugin* 
package that behaves differently from all the others: All others declare no 
dependency on munin-node, although they are just as useless when no munin-node* 
package is installed.

Kind regards
Marc


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (550, 'testing'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'stable'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.10.3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=C.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 munin-plugins-btrfs depends on:
pn  munin-node 
ii  python33.12.4-1
ii  python3-btrfs  13-1

munin-plugins-btrfs recommends no packages.

munin-plugins-btrfs suggests no packages.

-- Configuration Files:
/etc/munin/plugin-conf.d/btrfs_usage [Errno 13] Permission denied: 
'/etc/munin/plugin-conf.d/btrfs_usage'

-- no debconf information

Bug#1079344: munin-plugins-core: ntp_offset plugin does not work with munin-node-c

2024-08-22 Thread Marc Donges 
Package: munin-plugins-core
Version: 2.0.73-1
Severity: normal
X-Debbugs-Cc: marc.don...@gmail.com

ntp_offset plugin does not work with munin-node-c

Output when run under munin-node-c:

# munin node at srv-etc-2
fetch ntp_offset
Don't know how to do that 
.

Expected output: (output when run under munin-node or with patch applied)
# munin node at srv-etc-2
fetch ntp_offset
delay.value 31.6775
offset.value 1.7002
jitter.value 0.3273
.

Patch:

--- /usr/share/munin/plugins/ntp_offset.orig2023-03-21 20:08:22.0 
+
+++ /usr/share/munin/plugins/ntp_offset 2024-08-22 13:44:48.941908934 +
@@ -93,7 +93,7 @@
 print_thresholds critical
 }
 
-do_ () {
+do_fetch () {
 # Fetch operation
 syspeer="$(ntpq -n -p | grep '^[*o]')"
 
@@ -114,10 +114,14 @@
 }
 
 case $1 in
-autoconf|config|'')
+autoconf|config|fetch)
"do_$1"
exit $?
;;
+'')
+   do_fetch
+   exit $?
+   ;;
 *)
echo "Don't know how to do that" >&2
exit 1




-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 12 (bookworm)
Release:12
Codename:   bookworm
Architecture: armv7l

Kernel: Linux 6.6.31+rpt-rpi-v7 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_GB.UTF-8, LC_CTYPE=C.UTF-8 (charmap=locale: Cannot set LC_ALL 
to default locale: No such file or directory
UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin-plugins-core depends on:
ii  munin-common  2.0.73-1
ii  perl  5.36.0-7+deb12u1

Versions of packages munin-plugins-core recommends:
pn  libnet-snmp-perl  

Versions of packages munin-plugins-core suggests:
pn  acpi | lm-sensors 
pn  conntrack 
pn  default-mysql-client  
ii  ethtool   1:6.1-1
pn  hdparm
pn  libcache-cache-perl   
pn  libdbd-mysql-perl 
pn  libdbd-pg-perl
ii  libhttp-date-perl 6.05-2
pn  liblwp-useragent-determined-perl  
pn  libnet-dns-perl   
pn  libnet-ip-perl
pn  libnet-irc-perl   
pn  libnet-ldap-perl  
pn  libnet-netmask-perl   
pn  libnet-telnet-perl
pn  libwww-perl   
pn  libxml-parser-perl
pn  libxml-simple-perl
pn  logtail   
ii  net-tools 2.10-0.1
ii  python3   3.11.2-1
pn  ruby  
pn  smartmontools 

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_TIME = "de_DE.UTF-8",
LC_CTYPE = "C.UTF-8",
LC_MESSAGES = "C.UTF-8",
LC_PAPER = "de_DE.UTF-8",
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory

Bug#998641: python-yubico-tools: yubikey-totp broken with Python 3.9 (Debian bullseye)

2021-11-05 Thread Marc Donges 
Package: python-yubico-tools
Version: 1.3.3-0.3
Severity: important
X-Debbugs-Cc: p...@hungry.com

yubikey-totp is broken with the version of Python (3.9) that is current in 
Debian bullseye. Petter Reinholdtsen discovered this in a discussion of bug 
#965059 [1] and provided a patch there [2]. With the patch it works fine for me.

Output from yubikey-totp:

->8
% yubikey-totp
Traceback (most recent call last):
  File "/usr/bin/yubikey-totp", line 132, in 
sys.exit(main())
  File "/usr/bin/yubikey-totp", line 120, in main
otp = make_totp(args)
  File "/usr/bin/yubikey-totp", line 106, in make_totp
secret = struct.pack("> Q", args.time / args.step).ljust(64, chr(0x0))
struct.error: required argument is not an integer
%
->8

Expected output (output after patch):

->8
% yubikey-totp
->8

Here it waits for a keypress on the hardware token.

I set the severity to important because yubikey-totp is unusable.

Kind regards
Marc

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965059#15

[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965059#20


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (600, 'stable-updates'), (600, 'stable-security'), (600, 
'stable'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python-yubico-tools depends on:
ii  python3-yubico  1.3.3-0.3

python-yubico-tools recommends no packages.

python-yubico-tools suggests no packages.

-- no debconf information

Bug#925171: inkscape: Recommends no longer existing package transfig

2019-03-20 Thread Marc Donges 
Package: inkscape
Version: 0.92.4-2
Severity: normal

Dear Maintainer,

inkscape (in testing) recommends transfig, which does not exist in testing.

In Debian 9 transfig is described as "transitional dummy package for fig2dev".

Please update the dependency from transfig to fig2dev, so this continues to 
work in Debian 10.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (745, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages inkscape depends on:
ii  libaspell150.60.7~20110707-6
ii  libatk1.0-02.30.0-2
ii  libatkmm-1.6-1v5   2.28.0-2
ii  libc6  2.28-8
ii  libcairo2  1.16.0-4
ii  libcairomm-1.0-1v5 1.12.2-4
ii  libcdr-0.1-1   0.1.5-1
ii  libdbus-1-31.12.12-1
ii  libdbus-glib-1-2   0.110-4
ii  libfontconfig1 2.13.1-2
ii  libfreetype6   2.9.1-3
ii  libgc1c2   1:7.6.4-0.4
ii  libgcc11:8.3.0-2
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libglib2.0-0   2.58.3-1
ii  libglibmm-2.4-1v5  2.58.0-2
ii  libgomp1   8.3.0-2
ii  libgsl23   2.5+dfsg-6
ii  libgslcblas0   2.5+dfsg-6
ii  libgtk2.0-02.24.32-3
ii  libgtkmm-2.4-1v5   1:2.24.5-4
ii  libgtkspell0   2.0.16-1.2
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  liblcms2-2 2.9-3
ii  libmagick++-6.q16-88:6.9.10.23+dfsg-2
ii  libmagickcore-6.q16-6  8:6.9.10.23+dfsg-2
ii  libmagickwand-6.q16-6  8:6.9.10.23+dfsg-2
ii  libpango-1.0-0 1.42.4-6
ii  libpangocairo-1.0-01.42.4-6
ii  libpangoft2-1.0-0  1.42.4-6
ii  libpangomm-1.4-1v5 2.42.0-2
ii  libpng16-161.6.36-5
ii  libpoppler-glib8   0.71.0-3
ii  libpoppler82   0.71.0-3
ii  libpopt0   1.16-12
ii  libpotrace01.15-1
ii  librevenge-0.0-0   0.0.4-6
ii  libsigc++-2.0-0v5  2.10.1-2
ii  libstdc++6 8.3.0-2
ii  libvisio-0.1-1 0.1.6-1+b2
ii  libwpg-0.3-3   0.3.3-1
ii  libx11-6   2:1.6.7-1
ii  libxml22.9.4+dfsg1-7+b3
ii  libxslt1.1 1.1.32-2
ii  python 2.7.15-4
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages inkscape recommends:
ii  aspell   0.60.7~20110707-6
ii  fig2dev [transfig]   1:3.2.7a-5
ii  graphicsmagick-imagemagick-compat [imagemagick]  1.4~hg15916-1
ii  libimage-magick-perl 8:6.9.10.23+dfsg-2
ii  libwmf-bin   0.2.8.4-14
ii  python-lxml  4.3.2-1
ii  python-numpy 1:1.16.1-1
ii  python-scour 0.37-2
ii  transfig 1:3.2.6a-3

Versions of packages inkscape suggests:
pn  dia  
pn  inkscape-tutorials   
pn  libsvg-perl  
pn  libxml-xql-perl  
ii  pstoedit 3.73-1+b1
pn  python-uniconvertor  
ii  ruby 1:2.5.1

-- no debconf information

Bug#925170: tracker-extract: Could not insert metadata [...] invalid UTF-8 character

2019-03-20 Thread Marc Donges 
Package: tracker-extract
Version: 2.1.6-1
Severity: normal

Dear Maintainer,

tracker-extract produces huge amounts of log messages, apparently not liking 
some of my files. The files are as they are, tracker-extract needs to deal with 
them.

As indicated, I started it with more verbosity:

(tracker-extract:24433): Tracker-DEBUG: 18:44:41.451: 
--8<--
(tracker-extract:24433): Tracker-DEBUG: 18:44:41.451: The information relevant 
for a bug report is between the dotted lines

(tracker-extract:24433): Tracker-WARNING **: 18:44:41.451: Could not insert 
metadata for item "file:///home/marc/Documents/Studium/Physik/theoa/loe9.ps": 
25.16: invalid UTF-8 character

(tracker-extract:24433): Tracker-WARNING **: 18:44:41.451: If the error above 
is recurrent for the same item/ID, consider running "tracker-extract" in the 
terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug 
with the additional information
(tracker-extract:24433): Tracker-DEBUG: 18:44:41.452: Sparql was:
DELETE WHERE {
GRAPH  {
   nfo:pageCount ?nfo_pageCount 
} };
DELETE WHERE {
GRAPH  {
   nie:title ?nie_title } };
DELETE WHERE {
GRAPH  {
   nie:contentCreated 
?nie_contentCreated } };
DELETE WHERE {
GRAPH  {
   nco:creator ?nco_creator } };
DELETE WHERE {
GRAPH  {
   
rdf:type ?rdf_type } };
DELETE WHERE {
GRAPH  {
   
nco:fullname ?nco_fullname } };
INSERT {
GRAPH  {
 a 
nco:Contact ; 
  nco:fullname "dvips(k) 5.86 Copyright 1999 Radical Eye Software" .
 a nfo:PaginatedTextDocument ; 
  nfo:pageCount 5 ; 
  nie:title "L\xf6sung0009.dvi" ; 
  nie:contentCreated "2005-01-24T09:49:10+0100" ; 
  nco:creator 
 ; 
  nie:dataSource 
 .
}
};

(tracker-extract:24433): Tracker-DEBUG: 18:44:41.452: NOTE: The information 
above may contain data you consider sensitive. Feel free to edit it out, but 
please keep it as unmodified as you possibly can.
(tracker-extract:24433): Tracker-DEBUG: 18:44:41.452: 
-->8--


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (745, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages tracker-extract depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  libc62.28-8
ii  libcue2  2.2.1-2
ii  libexempi8   2.5.0-2
ii  libexif120.6.21-5.1
ii  libflac8 1.3.2-3
ii  libgexiv2-2  0.10.9-1
ii  libgif7  5.1.4-3
ii  libglib2.0-0 2.58.3-1
ii  libgsf-1-114 1.14.45-1
ii  libgstreamer-plugins-base1.0-0   1.14.4-1
ii  libgstreamer1.0-01.14.4-1
ii  libgxps2 0.3.1-1
ii  libicu63 63.1-6
ii  libiptcdata0 1.0.5-2.1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libosinfo-1.0-0  1.2.0-1
ii  libpng16-16  1.6.36-5
ii  libpoppler-glib8 0.71.0-3
ii  libseccomp2  2.3.3-4
ii  libtagc0 1.11.1+dfsg.1-0.3
ii  libtiff5 4.0.10-4
ii  libtotem-plparser18  3.26.2-1
ii  libtracker-miner-2.0-0   2.1.8-1
ii  libtracker-sparql-2.0-0  2.1.8-1
ii  libvorbisfile3   1.3.6-2
ii  libxml2  2.9.4+dfsg1-7+b3
ii  tracker  2.1.8-1

tracker-extract recommends no packages.

tracker-extract suggests no packages.

-- no debconf information

Bug#923191: munin-plugins-c: open_files can't cope with very large max files

2019-02-24 Thread Marc Donges 
Package: munin-plugins-c
Version: 0.0.11-1
Severity: normal

Dear Maintainer,

the open_files plugin seems not to be able to cope with very large
values for max files. On two of my machines it returns 0 as warning and
critical thresholds for the number of open files. I believe this is
because it does not handle the value for max files correctly.

Actual output:
root@nephthys:~# munin-run open_files 
used.value 11008
max.value -1

root@nephthys:~# munin-run open_files config
graph_title File table usage
graph_args --base 1000 -l 0
graph_vlabel number of open files
graph_category system
graph_info This graph monitors the Linux open files table.
used.label open files
used.info The number of currently open files.
max.label max open files
max.info The maximum supported number of open files. Tune by modifying 
/proc/sys/fs/file-nr.
used.warning 0
used.critical 0

Because the current value for open files used.value is larger than the
threshold of used.critical 0, munin alerts this.

As the config output suggests, I looked at the kernel configuration:

root@nephthys:~# cat /proc/sys/fs/file-nr 
11136   0   18446744073709551615

The value for max_files is the largest unsigned 64bit integer and would
be -1 if incorrectly interpreted as signed. As the standard perl
equivalent for open_files calculates the warning and critical values
from the max value, I assume this step fails.

Expected output:

The output would be fine if it were the same as the perl plugin's:

root@nephthys:~# munin-run open_files 
used.value 11424
max.value 18446744073709551615

root@nephthys:~# munin-run open_files config
graph_title File table usage
graph_args --base 1000 -l 0
graph_vlabel number of open files
graph_category system
graph_info This graph monitors the Linux open files table.
used.label open files
used.info The number of currently open files.
used.warning 16971004547812788224
used.critical 18077809192235360256
max.label max open files
max.info The maximum supported number of open files. Tune by modifying 
/proc/sys/fs/file-max.

An alternative would be to simply not output warning and critical levels
when the max value is so huge.

Kind regards
Marc


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (745, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages munin-plugins-c depends on:
ii  libc6  2.28-7

munin-plugins-c recommends no packages.

munin-plugins-c suggests no packages.

-- no debconf information

Bug#921985: munin-node: df plugin fails to get data for /home

2019-02-20 Thread Marc Donges 
Hi Lars,

On Mon, 18 Feb 2019 at 00:06, Lars Kruse  wrote:

> By accident I stumbled upon "systemctl edit munin-node".
> This will open up an empty editor. Here you can add the following:
>
>  [Service]
>  ProtectHome = read-only
>
> This will create a file
> /etc/systemd/system/munin-node.service.d/override.conf
> with the above content and in turn override the settings of the system-wide
> service file.
>

Ah, that's nice and clean. If ProtectHome=yes is kept I guess that hint in
a README or NOTICE would help.

I took a quick look at it.
> Here the plugin within the environment simply does not notice that /home is
> not accessible: it will simply be missing in the output by "df -h". Thus we
> cannot emit a warning in this case.
> Or does someone have an idea how to identify such an issue?
> (and how we should report it)
>
>
> Given that the "ProtectHome" setting allows the "read-only" value, I
> propose
> that we should pick this one instead of "yes".
>
> I think, we are mainly trying to protect the user from badly written
> plugins
> that mess up something with their cleanup procedure and accidentally erase
> relevant files. "read-only" would prevent this problem.
> The different problem of munin plugins spying on users on purpose would
> indeed
> justify "yes". But I tend to think, that everything is lost anyway, if a
> user
> runs random malicious code on his host.
>
> What do you think?
>

I am not familiar with the attack scenario that led to the config change,
however, if I understand the settings correctly, then the combination of
ProtectHome=true and ProtectSystem=full is a strong protection against
using a hypothetical security vulnerability to take over the machine or
exfiltrate any personal data, although munin runs as root, which is pretty
nice benefit.

So although I would change this on machines I run, simply because I need to
know when /home is almost full, I understand that a default install would
not allow that.

I don't think a scenario of "evil plugins" is relevant, a sysadmin just
should not use questionable software.

Kind regards
Marc

-- 
Marc A. Donges
Kaiserallee 50
76185 Karlsruhe
☎ +49 177 59 666 43 • marc.don...@gmail.com

Bug#921985: munin-node: df plugin fails to get data for /home

2019-02-16 Thread Marc Donges 
Hi Holger,

thanks for the prompt reply.

I understand the security benefits this presents in combination with
ProtectSystem=full.

However, a separate /home is a common configuration and this problem can
easily be overlooked and is then not trivial to find, because there are no
error messages anywhere, there is just this odd difference in reality
between munin-node as a daemon and everything else the sysadmin does
manually on the CLI.

I think to make this less awkward two things would be nice:

- a option to allow monitoring of /home without editing a non-conffile in
/lib (How is this even done properly? I just edited the service file to
find the cause of my problem, but I suppose it will be overwritten on every
update. Is there a nice way to do this?)

- a way to alert the admin of the possibly unintended configuration:
df-plugin activated + ProtectHome + Separate /home
Can the df* plugin itself detect the situation and then make a log entry?
That would have severely cut down the time it took me to find this.

Cheers
Marc




On Mon, 11 Feb 2019 at 11:45, Holger Levsen  wrote:

> Hi Marc,
>
> On Mon, Feb 11, 2019 at 01:09:37AM +0100, Lars Kruse wrote:
> > > # Plugins like "df" require access to /home if that is a separate
> filesystem
> > > ProtectHome=false
> > See the other bug report for this issue:
> >  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918851
> > We are discussing whether there is good way to work around this.
>
> IMO this is a good default. If you want to monitor /home (and accept the
> risk that munin-node (and all its plugins) can access /home, you can
> modify the service file locally and get what you want.
>
> Suggestions where&how to document this better welcome!
>
>
> --
> tschau,
> Holger
>
>
> ---
>holger@(debian|reproducible-builds|layer-acht).org
>PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
>


-- 
Marc A. Donges
Kaiserallee 50
76185 Karlsruhe
☎ +49 177 59 666 43 • marc.don...@gmail.com

Bug#921985: munin-node: df plugin fails to get data for /home

2019-02-10 Thread Marc Donges 
Package: munin-node
Version: 2.0.45-1
Severity: normal

Dear Maintainer,

on one of my systems I noticed that munin no longer records disk free data for 
the separate /home filesystem.

While debugging I could not reproduce the problem when running the df plugin 
with munin-run. I could also not reproduce it with munin-node started directly 
from the command line.

Incomplete output with munin-node run as daemon from systemd:
marc@nephthys:~$ nc localhost 4949
# munin node at nephthys
fetch df
_dev_mapper_nephthys_root_crypt.value 73.5565195777657
_dev_shm.value 1.84851226160177
_run.value 10.594829277865
_run_lock.value 0.078125
_sys_fs_cgroup.value 0
_dev_sda1.value 25.5692545665476
.

Complete output with munin-node run from CLI:
marc@nephthys:~$ nc localhost 4949
# munin node at nephthys
fetch df
_dev_mapper_nephthys_root_crypt.value 73.5626819028434
_dev_shm.value 2.66106291417369
_run.value 10.5943386970173
_run_lock.value 0.078125
_sys_fs_cgroup.value 0
_dev_sda1.value 25.5692545665476
_dev_mapper_nephthys_home_crypt.value 95.5244404001415
.

See the last line with label _dev_mapper_nephthys_home_crypt.

I found that modifying the service file /lib/systemd/system/munin-node.service 
for munin-node fixes this. The default has:

ProtectHome=true

I changed it to:

# Plugins like "df" require access to /home if that is a separate filesystem
ProtectHome=false

This fixed the problem

Kind regards
Marc

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (745, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages munin-node depends on:
ii  libnet-server-perl  2.009-1
ii  lsb-base10.2018112800
ii  munin-common2.0.45-1
ii  munin-plugins-core  2.0.45-1
ii  netbase 5.5
ii  perl5.28.1-4

Versions of packages munin-node recommends:
ii  gawk 1:4.2.1+dfsg-1
ii  munin-plugins-extra  2.0.45-1
ii  procps   2:3.3.15-2

Versions of packages munin-node suggests:
pn  munin   
pn  munin-plugins-java  

-- Configuration Files:
/etc/munin/munin-node.conf changed:
log_level 4
log_file /var/log/munin/munin-node.log
pid_file /var/run/munin/munin-node.pid
background 1
setsid 1
user root
group root
ignore_file [\#~]$
ignore_file DEADJOE$
ignore_file \.bak$
ignore_file %$
ignore_file \.dpkg-(tmp|new|old|dist)$
ignore_file \.rpm(save|new)$
ignore_file \.pod$
allow ^127\.0\.0\.1$
allow ^::1$
allow ^192\.168\.102\.[0-9]*$
allow ^2001:6f8:1d3e:[:0-9a-f]*$
host 127.0.0.1
port 4949

/etc/munin/plugin-conf.d/README [Errno 13] Permission denied: 
'/etc/munin/plugin-conf.d/README'
/etc/munin/plugin-conf.d/munin-node [Errno 13] Permission denied: 
'/etc/munin/plugin-conf.d/munin-node'

-- no debconf information

Bug#905643: pdftk-java: Requires JRE to work but does not depend on JRE

2018-08-07 Thread Marc Donges 
Package: pdftk-java
Version: 0.0.0+20180620.1-1
Severity: important

pdftk-java does not depend on a JRE, but it requires one to work:

mdonges@cindy:~$ pdftk
/usr/bin/pdftk: 5: /usr/bin/pdftk: java: not found

When I install default-jre-headless plus its dependencies, it works fine:

mdonges@cindy:~$ pdftk
SYNOPSIS
   pdftk 
[…]

Please fix the dependencies.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (450, 'testing'), (450, 'stable'), (400, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pdftk-java depends on:
ii  libbcprov-java 1.60-1
ii  libcommons-lang3-java  3.7-1

pdftk-java recommends no packages.

Versions of packages pdftk-java suggests:
ii  poppler-utils [xpdf-utils]  0.63.0-2

-- no debconf information

Bug#834790: aptitude hangs at "Loading cache" when unable to download package list

2016-08-31 Thread Marc Donges 
Hi!

I have the same problem with a different underlying cause, a Release
file with a correct signature but an invalid date.

Updating the package list interactively shows no problems but hangs at
"Loading cache".

When updating the package list noninteractively via "aptitude update"
the problem is shown (URLs obfuscated for privacy reasons):

root@cindy:~# apt-get update
Ign:1 AAA wheezy InRelease
Ign:2 BBB jessie InRelease   
Hit:4 BBB stretch InRelease  
Hit:5 BBB sid InRelease
Hit:6 BBB jessie-updates InRelease
Hit:7 BBB stretch-updates InRelease
Hit:8 BBB jessie
Release 
 

Get:3 AAA wheezy Release [2612
B]  

Get:9 AAA wheezy Release.gpg [836
B] 
Ign:10 CCC sid InRelease  
Hit:11 CCC sid Release
Hit:12 DDD stable InRelease
Hit:13 EEE jessie/updates InRelease   
Hit:14 EEE stretch/updates InRelease  
Get:16 AAA wheezy/main amd64 Packages [1345 B]
Get:17 AAA wheezy/main i386 Packages [1345 B]  
Hit:19 FFF jessie InRelease
Fetched 6138 B in 2s (2857 B/s)
Reading package lists... Done
W: Invalid 'Date' entry in Release file
/var/lib/apt/lists/partial/aaa_dists_wheezy_Release
W: The repository 'AAA wheezy Release' provides only weak security
information.
N: Data from such a repository can't be authenticated and is therefore
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user
configuration details.

The workaround is to simply update the package list noninteractively via
"aptitude update" and then use aptitude interactively but not update the
package list there.

Unfortunately I cannot share these files publicly.

The invalid date entry in the Release file is:

Date: Tue, 12 Jul 2016 09:23:31 CEST
Valid-Until: Tue, 30 Nov 2038 00:00:00 JST

Of course in this case it's a repository bug, still, the behavior of
aptitude could be more graceful.

Cheers
Marc

Bug#823110: cups-filters: Versioned dependency on imagemagick makes using graphicsmagick harder

2016-04-30 Thread Marc Donges 
Package: cups-filters
Version: 1.8.3-2+b1
Severity: normal

Dear Maintainer,

recent versions of cups-filters have a versioned dependency on imagemagick.

The relevant changelog is this:

  * Added dependencies on imagemagick (>= 6.4~), liblouisutdml-bin, and 

 ▒
poppler-utils to cups-filters, as they are needed to convert images, text,  

 ▒
and PDF to Braille, added antiword and docx2txt to Suggests: as they allow  

 ▒
converting Word files to Braille

 ▒


 #
 -- Didier Raboud   Tue, 15 Dec 2015 11:04:23 +0100

 ▒

There is an alternative to imagemagick, graphicsmagick, with compatibility 
binaries in the package graphicsmagick-imagemagick-compat, that make it 
possible to call its tools like imagemagick.

Your versioned dependency makes it impossible to install the compatibility 
package, because only the original imagemagick can strictly fulfill ">= 6.4~". 
Please consider changing this so graphicsmagick-imagemagick-compat can fulfill 
the dependency, for example by or-ing it into the list with an appropriate 
version.

Thank you!


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (745, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages cups-filters depends on:
ii  bc 1.06.95-9+b1
ii  cups-filters-core-drivers  1.8.3-2+b1
ii  ghostscript9.19~dfsg-1+b1
ii  imagemagick8:6.8.9.9-7+b2
ii  libc6  2.22-7
ii  libcups2   2.1.3-5
ii  libcupsfilters11.8.3-2+b1
ii  libcupsimage2  2.1.3-5
ii  libfontconfig1 2.11.0-6.4
ii  libfontembed1  1.8.3-2+b1
ii  libgcc11:5.3.1-14
ii  libijs-0.350.35-12
ii  libpoppler57   0.38.0-2+b1
ii  libqpdf17  6.0.0-2
ii  libstdc++6 5.3.1-14
ii  poppler-utils  0.38.0-2+b1

Versions of packages cups-filters recommends:
ii  colord 1.3.2-1
ii  liblouis-bin   2.6.4-2+b1
ii  liblouisutdml-bin  2.5.0-3+b1

Versions of packages cups-filters suggests:
pn  antiword   
pn  docx2txt   
ii  foomatic-db-compressed-ppds [foomatic-db]  20160315-1

-- no debconf information

Bug#821154: chromium: crashes on video

2016-04-18 Thread Marc Donges 
I can confirm this problem for the sid package 50.0.2661.75-1 when
installed on testing.

However, the problem does not occur with the package
50.0.2661.75-1~deb8u1 from stable-security on testing, although it's
basically the same version of chrome.

Cheers,
Marc

Bug#732228: Acknowledgement (rsync: fails to remove files with --remove-source when used with --copy-links)

2013-12-15 Thread Marc Donges 
I tried to verify this in the stable release and could not confirm it
there (3.0.9-4)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#723098: linux-image-3.10-2-amd64: Setting screen backlight bightness extremely sluggish

2013-09-16 Thread Marc Donges 
Package: src:linux
Version: 3.10.7-1
Severity: normal

With the current kernel in X/gnome, when I use the keys to control the screen 
backlight brightness, the change of one brightness level including the visual 
feedback takes on the order of 3 seconds. That is very slow. Also the touchpad 
input completely hangs during some part of the operation.

To reproduce this, pressing the keys for brightness control gives ample time to 
use the touchpad and see the mouse pointer freeze several times.

I did not have this problem on 3.2.0-4.

This notebook is mainly a wheezy workstation with some packages (Kernel, LVM, 
…) from sid.

-- Package-specific info:
** Version:
Linux version 3.10-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.7.3 
(Debian 4.7.3-6) ) #1 SMP Debian 3.10.7-1 (2013-08-17)

** Command line:
BOOT_IMAGE=/vmlinuz-3.10-2-amd64 root=/dev/mapper/juli_magenta-root_crypt ro 
quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   17.413971] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   17.637310] cfg80211: Calling CRDA to update world regulatory domain
[   17.680652] [drm] Memory usable by graphics device = 2048M
[   17.680658] i915 :00:02.0: setting latency timer to 64
[   17.694689] i915 :00:02.0: irq 45 for MSI/MSI-X
[   17.694698] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   17.694699] [drm] Driver supports precise vblank timestamp query.
[   17.694752] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   17.726567] [drm] Wrong MCH_SSKPD value: 0x16040307
[   17.726570] [drm] This can cause pipe underruns and display issues.
[   17.726571] [drm] Please upgrade your BIOS to fix this.
[   17.740803] Intel(R) Wireless WiFi driver for Linux, in-tree:
[   17.740806] Copyright(c) 2003-2013 Intel Corporation
[   17.741186] iwlwifi :02:00.0: irq 46 for MSI/MSI-X
[   17.742714] fbcon: inteldrmfb (fb0) is primary device
[   17.777275] iwlwifi :02:00.0: firmware: agent loaded 
iwlwifi-6000g2a-6.ucode into memory
[   17.777419] iwlwifi :02:00.0: loaded firmware version 18.168.6.1 op_mode 
iwldvm
[   17.938603] ACPI: Battery Slot [BAT0] (battery present)
[   17.958652] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled
[   17.958654] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[   17.958655] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[   17.958656] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
[   17.958658] iwlwifi :02:00.0: CONFIG_IWLWIFI_P2P enabled
[   17.958659] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Advanced-N 
6205 AGN, REV=0xB0
[   17.958759] iwlwifi :02:00.0: L1 Enabled; Disabling L0S
[   17.965478] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio.
[   18.015620] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[   18.107566] ACPI: Battery Slot [BAT1] (battery absent)
[   18.115100] ACPI: AC Adapter [AC] (on-line)
[   18.185665] input: DualPoint Stick as 
/devices/platform/i8042/serio1/input/input7
[   18.198633] input: AlpsPS/2 ALPS DualPoint TouchPad as 
/devices/platform/i8042/serio1/input/input8
[   18.564184] media: Linux media interface: v0.10
[   18.580948] Linux video capture interface: v2.00
[   18.641187] Console: switching to colour frame buffer device 170x48
[   18.645020] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   18.645022] i915 :00:02.0: registered panic notifier
[   18.702312] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_HD 
(1bcf:2804)
[   18.719843] input: Laptop_Integrated_Webcam_HD as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9
[   18.719916] usbcore: registered new interface driver uvcvideo
[   18.719918] USB Video Class driver (1.1.1)
[   18.833798] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[   18.964933] cfg80211: World regulatory domain updated:
[   18.964941] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   18.964946] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   18.964951] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   18.964955] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   18.964959] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   18.964962] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   19.310701] dell_wmi: Received unknown WMI event (0x0)
[   19.690493] acpi device:37: registered as cooling_device4
[   19.930512] ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
[   19.930653] input: Video Bus as 
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input10
[   19.930869] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[   19.966916] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X
[   19.994957] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0

Bug#557476: setting not restored on suspend/resume and login/logout

2012-11-24 Thread Marc Donges 
Package: gpointing-device-settings
Version: 1.5.1-6
Followup-For: Bug #557476

Dear Maintainer,

I can confirm the problem of settings not being restored after logout/login for
the current version of gpointing-device-settings is wheezy.

gnome-settings-daemon is loaded but does not have the mentioned library loaded
although it exists:

marc@nephthys:~$ pgrep gnome-settings
9239
marc@nephthys:~$ fgrep -e point /proc/9239/maps
marc@nephthys:~$

I noticed that gpointing-device-settings is the only package that has files in
the directory with its plugins for gnome-settings-daemon:

marc@nephthys:~$ ls -l /usr/lib/gnome-settings-daemon-2.0
total 40
-rw-r--r-- 1 root root 33688 Dec 17  2011 libpointing-device.so
-rw-r--r-- 1 root root   154 Dec 17  2011 pointing-device.gnome-settings-plugin

There are two directories with similar names and more files in them that are
actually owned by gnome-settings-daemon, so it seems like the directory is just
wrong:

marc@nephthys:~$ dpkg -S /usr/lib/gnome-settings-daemon-3.0
gnome-settings-daemon, libcaribou-gtk-module:amd64, 
libcaribou-gtk3-module:amd64, libcanberra-gtk-module:amd64, 
libcanberra-gtk3-module:amd64, libatk-adaptor:amd64: 
/usr/lib/gnome-settings-daemon-3.0
marc@nephthys:~$ dpkg -S /usr/lib/gnome-settings-daemon
gnome-settings-daemon: /usr/lib/gnome-settings-daemon
marc@nephthys:~$ dpkg -S /usr/lib/gnome-settings-daemon-2.0
gpointing-device-settings: /usr/lib/gnome-settings-daemon-2.0

Kind regards
Marc

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gpointing-device-settings depends on:
ii  gconf2  3.2.5-1+build1
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-35
ii  libcairo2   1.12.2-2
ii  libdbus-1-3 1.6.8-1
ii  libdbus-glib-1-20.100-1
ii  libfontconfig1  2.9.0-7
ii  libfreetype62.4.9-1
ii  libgconf2-4 3.2.5-1+build1
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-3
ii  libgpds01.5.1-6
ii  libgtk2.0-0 2.24.10-2
ii  libpango1.0-0   1.30.0-1
ii  libxi6  2:1.6.1-1

gpointing-device-settings recommends no packages.

gpointing-device-settings suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org