Bug#1016887: heaptrack: Grammar error in package description, misuse of contraction "it's" for possessive "its"

2022-08-08 Thread Jason L. Quinn
Package: heaptrack
Version: up to current (which is 1.3.0-1)
Severity: minor
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

The Debian package description says

"Heaptrack is notable for it's ability..."

it should be

"Heaptrack is notable for its ability..."

I noticed on Bullseye but checked that it still exists
up in 1.3.0-1 package on testing (Bookworm) and unstable (sid).

This bug also applies to the packages

libheaptrack and heaptrack-gui

Small bug report but hopefully one that helps polish Debian.

Thanks for what you do.

Cheers,
Jason Quinn

-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-16-amd64 (SMP w/12 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 heaptrack depends on:
ii  libboost-iostreams1.74.01.74.0-9
ii  libboost-program-options1.74.0  1.74.0-9
ii  libc6   2.31-13+deb11u3
ii  libgcc-s1   10.2.1-6
pn  libheaptrack
ii  libstdc++6  10.2.1-6

heaptrack recommends no packages.



Bug#1012341: med-config: 90med-config file missing a necessary trailing semi-colon

2022-06-04 Thread Jason L. Quinn
Package: med-config
Version: 3.7
Severity: normal
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

The file /etc/apt/apt.conf.d/90med-config has a syntax error. It is missing a
trailing semi-colon for the DPkg scope. This can cause parsing errors, eg with
the cupt package manager. You can confirm the bug by installing the cupt
package and running "cupt why" on the command line.

When a scope is used in an apt config file, the trailing semi-colon after the
closing delimiter brace is necessary (as per "man 5 apt.conf").

The fix, I believe, is to merely change

DPkg {
Post-Invoke {"test -f /var/run/med-config.usermenu && if [ -x
/usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus med
; fi ; rm -f /var/run/med-config.usermenu";};
}

to

DPkg {
Post-Invoke {"test -f /var/run/med-config.usermenu && if [ -x
/usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus med
; fi ; rm -f /var/run/med-config.usermenu";};
};

in the /etc/apt/apt.conf.d/90med-config file.

I'm running bullseye so I have med-config version 3.7.0 but I just checked and
the issue is still present in sid for 3.7.1.

Hope that helps.


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-14-amd64 (SMP w/12 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 med-config depends on:
ii  adduser3.118
ii  blends-common  0.7.2
ii  debconf [debconf-2.0]  1.5.77
ii  menu   2.1.48

med-config recommends no packages.

med-config suggests no packages.

-- debconf information:
* med-config/group:
  shared/med-config/usermenus: never



Bug#1011982: science-config: configuration file "90science-config" is missing semi-colon. Causes "unable to parse the config file" errors

2022-05-28 Thread Jason L. Quinn
Package: science-config
Version: 1.14.2
Severity: normal
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

Using a tool like cupt results in warnings like

E: syntax error: line 8, character 1: expected: semicolon (';')
E: unable to parse the config file '//etc/apt/apt.conf.d/90science-config'
W: skipped the configuration file '//etc/apt/apt.conf.d/90science-config'


The contents of that file are:

/*
 * APT configuration file for science-config package
 */

DPkg {
Post-Invoke {"test -f /var/run/science-config.usermenu && if [ -x
/usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus
science ; fi ; rm -f /var/run/science-config.usermenu";};
}


And it appears that indeed it is missing the semi-colon to end the DPkg scope.
The file should be

/*
 * APT configuration file for science-config package
 */

DPkg {
Post-Invoke {"test -f /var/run/science-config.usermenu && if [ -x
/usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus
science ; fi ; rm -f /var/run/science-config.usermenu";};
};


Hope that helps.


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-14-amd64 (SMP w/12 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 science-config depends on:
ii  adduser3.118
ii  blends-common  0.7.2
ii  debconf [debconf-2.0]  1.5.77
ii  menu   2.1.48

science-config recommends no packages.

science-config suggests no packages.

-- debconf information:
* science-config/group:
  shared/science-config/useusermenus:



Bug#1000385: 4digits: Package "4digits" shows up in bullseye package list but it is not actually there.

2021-11-22 Thread Jason L. Quinn
Package: 4digits
Version: 1.1.4-1+b1
Severity: normal
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

As seen via the Synaptic package manager, there is a strange entry for
"4digits"
but it's listed as having download size "1 byte" in Section "unknown". Clicking
on
it generates the following information:

Package 4digits has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and never
uploaded, has been obsoleted or is not available with the contents of
sources.list

Because 4digits is so close to the alphanumeric top of the package list, it is
highly visible so whatever this issue is, it's a more prominent blemish
than it might at first seem.


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads)
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 4digits depends on:
ii  libc6  2.31-13+deb11u2
pn  python 
pn  python-glade2  

4digits recommends no packages.



Bug#997977: /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe!

2021-10-28 Thread Jason L. Quinn
Package: monopd
Version: 0.10.2-4
Severity: grave
Tags: security
Justification: user security hole
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com, Debian Security Team 


Dear Maintainer,

Recently upgraded from Buster to Bullseye. I'm not perusing
"journalctl --boot" looking for errors and warnings and submitting
bug reports as I tend to do after a Debian upgrade. One of the curious
lines in my journal logs was

/lib/systemd/system/monopd.service:8: Special user nobody configured, this is
not safe!

This does indeed appear to be a valid systemd warning. See commit at

https://github.com/systemd/systemd/commit/bed0b7dfc0070e920d00c89d9a4fd4db8d974cf0

Marked as grave as per bug descriptions in the reportbug tool (introduces a
security hole).

Cheers,
Jason





-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/12 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 monopd depends on:
ii  libc6   2.31-13+deb11u2
ii  libgcc-s1   10.2.1-6
ii  libmuparser2v5  2.2.6.1+dfsg-1
ii  libstdc++6  10.2.1-6
ii  libsystemd0 247.3-6
ii  lsb-base11.1.0

monopd recommends no packages.

Versions of packages monopd suggests:
ii  gtkatlantic  0.6.3-1



Bug#997854: tlp: Misconfiguration in TLP causes complete loss of sound on some systems

2021-10-26 Thread Jason L. Quinn
Package: tlp
Severity: important
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Debian Maintainer,

There appears to be a severe sound issue affecting
some users that may ultimately trace back to the tlp package.
Please see the thread at

https://bbs.archlinux.org/viewtopic.php?id=243004

and in particular comment #7 by Toolfox.

I vaguely remember fixing a problem with buster that
turned out to be related to tlp. And then recently
I upgraded to bullseye and faced the same problem.
I had no sound at all. Nothing. But "fixed" the issue merely by
uninstalling the tlp package. Upon reboot, sound was
back so tlp is definitely preventing sound for some users.

This is a beguiling bug to track down because there's few
clues to follow and nobody suspects a power management package
to ultimately be the cause of such a severe sound bug.
The bug may be related to whether users are on battery or wall power
as comment #7 explains. I almost always use wall power so it affected
me.




-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/12 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 tlp depends on:
pn  hdparm  
ii  iw  5.9-3
ii  lsb-base11.1.0
ii  pciutils1:3.7.0-5
ii  rfkill  2.36.1-8
ii  usbutils1:013-3
ii  wireless-tools  30~pre9-13.1

Versions of packages tlp recommends:
pn  ethtool  
pn  tlp-rdw  

Versions of packages tlp suggests:
pn  acpi-call-dkms  
ii  linux-cpupower  5.10.70-1
ii  smartmontools   7.2-1



Bug#997853: bluetooth.service: Failed to locate executable

2021-10-25 Thread Jason L. Quinn
Package: bluetooth
Version: 5.55-3.1
Severity: important
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

After a recent full-upgrade from buster to bullseye, bluetooth is not working.
It appears the system is looking for the bluetooth daemon executable in the
/usr/lib/bluetooth/ directory
but no such directory exists. There is a directory called
/usr/libexec/bluetooth/
that has a bluetoothd executable. I have tried reinstalling almost all the
bluetooth-related packages
hoping it might solve the issue by creating missing symlinks or whatever but it
did not.
I also have the bluez package installed and I wasn't certain which package to
file this bug against.

The output of "systemctl status bluetooth" gives:

 bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Drop-In: /etc/systemd/system/bluetooth.service.d
 └─01-disable-sap-plugin.conf
 Active: failed (Result: exit-code) since Tue 2021-10-26 12:25:19 +08; 8min
ago
   Docs: man:bluetoothd(8)
Process: 4917 ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap
(code=exited, status=203/EXEC)
   Main PID: 4917 (code=exited, status=203/EXEC)
CPU: 4ms

Oct 26 12:25:19 mycomputername systemd[1]: Starting Bluetooth service...
Oct 26 12:25:19 mycomputername systemd[4917]: bluetooth.service: Failed to
locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory
Oct 26 12:25:19 mycomputername systemd[4917]: bluetooth.service: Failed at step
EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory
Oct 26 12:25:19 mycomputername systemd[1]: bluetooth.service: Main process
exited, code=exited, status=203/EXEC
Oct 26 12:25:19 mycomputername systemd[1]: bluetooth.service: Failed with
result 'exit-code'.
Oct 26 12:25:19 mycomputername systemd[1]: Failed to start Bluetooth service.


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/12 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 bluetooth depends on:
ii  bluez  5.55-3.1

bluetooth recommends no packages.

Versions of packages bluetooth suggests:
ii  bluez-cups   5.55-3.1
pn  bluez-meshd  
ii  bluez-obexd  5.55-3.1


Bug#997836: linuxptp's timemaster service and missing chrony package causing log errors

2021-10-25 Thread Jason L. Quinn
Package: linuxptp
Version: 3.1-2.1
Severity: normal
Tags: d-i
X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com

Dear Maintainer,

Output of "journalctl -p err" was giving error lines such as

Oct 25 20:34:14 mycomputername timemaster[862]: [4.900] failed to spawn
/usr/sbin/chronyd: No such file or directory

"timemaster" here, I believe, is referring to the systemd timemaster service
from the linuxptp package on
Debian (I'm not sure about that). I don't have the chrony package installed so
this error makes sense for
that reason. If it's true that this error traces to the linuxptp package, the
error is
unexpected because the linuxptp package does not list the chrony package as
either recommended or suggested for
installation and wasn't installed when I upgraded a couple of days ago to
bullseye from buster.

Trying to install the chrony package shows that it would require removing the
systemd-timesyncd package.
At this point, it's unclear what a user not familiar with the intricacies of
timekeeping on
linux should do and I'm reluctant to start uninstalling packages and risk
falling down a rabbit hole.


-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/12 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 linuxptp depends on:
ii  libc6  2.31-13+deb11u2

linuxptp recommends no packages.

linuxptp suggests no packages.



Bug#962512: nethack: Security issues in Buster's nethack 3.6.1

2020-06-08 Thread Jason L. Quinn
Source: nethack
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

Debian 10 (Buster) currently uses nethack 3.6.1. The website for nethack at

https://nethack.org/security/index.html

shows security issues have resulted in multiple (up to now 5) point releases
fixing things like buffer overflow vulnerabilities, including some that can
lead to escalation of privileges. The upstream maintainers recommend "upgrade
as soon as possible" for many of the CVE documented issues.

Seems like the vunerabilities are important enough to warrant an upgrade in
Buster.




-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/12 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



Bug#960696: chrome-gnome-shell: /usr/share/applications/org.gnome.ChromeGnomeShell.desktop is misconfigured

2020-05-15 Thread Jason L. Quinn
Package: chrome-gnome-shell
Version: 10.1-5
Severity: normal

Dear Maintainer,

Start of any QT application from the console produces the following chrome-
gnome-shell related error message:


kf5.kservice.services: The desktop entry file
"/usr/share/applications/org.gnome.ChromeGnomeShell.desktop" has Type=
"Application" but no Exec line
kf5.kservice.sycoca: Invalid Service :
"/usr/share/applications/org.gnome.ChromeGnomeShell.desktop"


Using "dpkg -s /usr/share/applications/org.gnome.ChromeGnomeShell.desktop"
located chrome-gnome-shell as the package responsible.

The probable fix is that "Service" is probably intended instead of
"Application" for the Type.

This bug is more severe than it appears because it affects external
applications and pollutes console output.

It appears sid still uses the same package version as Debian 10.3 so I believe
this bug has not been handled yet.



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/12 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 chrome-gnome-shell depends on:
ii  gnome-shell   3.30.2-11~deb10u1
ii  python3   3.7.3-1
ii  python3-gi3.30.4-1
ii  python3-requests  2.21.0-1

chrome-gnome-shell recommends no packages.

Versions of packages chrome-gnome-shell suggests:
pn  chromium | chromium-browser  
pn  firefox  

-- no debconf information



Bug#960693: phpliteadmin.desktop file is misconfigured

2020-05-15 Thread Jason L. Quinn
Package: phpliteadmin
Version: 1.9.7.1-2
Severity: normal

Dear Maintainer,

When I start a QT application like kate from the console, I receive the
following phpliteadmin-related error messages:

=
kf5.kservice.services: The desktop entry file
"/usr/share/applications/phpliteadmin.desktop"  has Type= "Link"  instead of
"Application" or "Service"
kf5.kservice.sycoca: Invalid Service :
"/usr/share/applications/phpliteadmin.desktop"
=

"Link" is not a proper value for Type. I believe setting it to "Service" might
be what is wanted. It silences the error and it still runs.

This packaging bug is more severe than it might appear since it pollutes
console output for external QT applications.

I'm reporting this from Debian 10.3 but I also checked the most up-to-date
package in sid and it still has the same incorrect value of "Link".



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/12 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 phpliteadmin depends on:
ii  libapache2-mod-php  2:7.3+69
ii  libapache2-mod-php7.3 [libapache2-mod-php]  7.3.14-1~deb10u1
ii  php-sqlite3 2:7.3+69
ii  php7.3-sqlite3 [php-sqlite3]7.3.14-1~deb10u1

Versions of packages phpliteadmin recommends:
ii  apache2 [httpd]  2.4.38-3+deb10u3

Versions of packages phpliteadmin suggests:
ii  firefox-esr [www-browser]  68.8.0esr-1~deb10u1
ii  konqueror [www-browser]4:18.12.0-1
ii  lynx [www-browser] 2.8.9rel.1-3

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/applications/phpliteadmin.desktop (from 
phpliteadmin package)



Bug#960075: gearhead2: "/usr/share/applications/gearhead2.desktop" has misconfiguration

2020-05-08 Thread Jason L. Quinn
Source: gearhead2
Severity: normal

Dear Maintainer,

Gearhead2 has the same misconfigured desktop file as Gearhead1 (see Debian
Bug#960071). Here's a similar bug report as for Gearhead1:

The following messages are given Upon start-up of any KDE app from the console:

kf5.kservice.services: The desktop entry file
"/usr/share/applications/gearhead2.desktop"  has Type= "application"  instead
of "Application" or "Service"
kf5.kservice.sycoca: Invalid Service :
"/usr/share/applications/gearhead2.desktop"

The value for the Type parameter appears to be case-sensitive and changing it
from "application" to "Application" appears to have fixed the problem for me.

This (Debian packaging) bug is more severe than it might appear because,
although it doesn't affect gearhead itself, it affects the console output of
all the QT programs.



-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/12 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



Bug#960071: gearhead: /usr/share/applications/gearhead.desktop has misconfiguration

2020-05-08 Thread Jason L. Quinn
Source: gearhead
Severity: normal

Dear Maintainer,

The following messages are given Upon start-up of any KDE app from the console:

kf5.kservice.services: The desktop entry file
"/usr/share/applications/gearhead.desktop"  has Type= "application"  instead of
"Application" or "Service"
kf5.kservice.sycoca: Invalid Service :
"/usr/share/applications/gearhead.desktop"

The value for the Type parameter appears to be case-sensitive and changing it
from "application" to "Application" appears to have fixed the problem for me.

This (Debian packaging) bug is more severe than it might appear because,
although it doesn't affect gearhead itself, it affects the console output of
all the QT programs.



-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-8-amd64 (SMP w/12 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



Bug#943718: reportbug-gtk is reporting that up-to-date software is out-of-date

2019-10-28 Thread Jason L. Quinn
Package: reportbug-gtk
Version: 7.5.3~deb10u1
Severity: important

Dear Maintainer,

Reportbug (at least when using the GUI) is warning software is out-of-date even
when it's not. For instance, even filing this report, I got a pop-up dialogue
saying:

=
Your version (7.5.3~deb10u1) of reportbug appears to be out of date.
The following newer releases(s) are available in the Debian archive:
   testing: 7.5.3
   unstable: 7.5.3
Please try to verify if the bug you are about to report is already
addressed by these releases. Do you still want to file a report
=

(While it's up, notice the missing question mark. Please fix that too.)

As you can see, I HAVE the latest version. It does the same thing for
the latest version of Firefox too where it warned that my version
68.2.0esr-1~deb10u1 is out-of-date and unstable has 68.2.0esr-1.

It seems like it might be the "deb10u1" patch extensions causing the trouble in
whatever comparison algorithm used.

Anyway, this is an IMPORTANT bug, not just normal. It's literally discouraging
users from sending feedback and thus adversely affects the whole project.



-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/12 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 reportbug-gtk depends on:
ii  gir1.2-gtk-3.0 3.24.5-1
ii  gir1.2-vte-2.910.54.2-2
ii  python3-gi 3.30.4-1
ii  python3-gi-cairo   3.30.4-1
ii  python3-gtkspellcheck  4.0.5-1
ii  reportbug  7.5.3~deb10u1

reportbug-gtk recommends no packages.

reportbug-gtk suggests no packages.

-- no debconf information



Bug#943482: firefox-esr: when launched in console user gets a dconf-WARNING about permission denied

2019-10-25 Thread Jason L. Quinn
Package: firefox-esr
Version: 68.2.0esr-1~deb10u1
Severity: minor

Dear Maintainer,

If the new Firefox 68.2.0esr is started from the console, the user gets
warnings like

(/usr/lib/firefox-esr/firefox-esr:29777): dconf-WARNING **: 18:38:28.296:
Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission
denied

Not sure if this problem is with the Firefox package or the flatpak package.





-- Package-specific info:


-- Addons package information

-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/12 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 firefox-esr depends on:
ii  debianutils   4.8.6.1
ii  fontconfig2.13.1-2
ii  libasound21.1.8-1
ii  libatk1.0-0   2.30.0-2
ii  libc6 2.28-10
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.16-1
ii  libdbus-glib-1-2  0.110-4
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.3.0-6
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libglib2.0-0  2.58.3-2+deb10u1
ii  libgtk-3-03.24.5-1
ii  libjsoncpp1   1.7.4-3
ii  libpango-1.0-01.42.4-7~deb10u1
ii  libstartup-notification0  0.12-6
ii  libstdc++68.3.0-6
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages firefox-esr recommends:
ii  libavcodec-extra58 [libavcodec58]  7:4.1.4-1~deb10u1

Versions of packages firefox-esr suggests:
ii  fonts-lmodern  2.004.5-6
ii  fonts-stix [otf-stix]  1.1.1-4
ii  libcanberra0   0.30-7
ii  libgssapi-krb5-2   1.17-3
ii  libgtk2.0-02.24.32-3
ii  pulseaudio 12.2-4+deb10u1

-- no debconf information



Bug#935805: sweethome3d fails to start because looks for a java version not installed

2019-08-26 Thread Jason L. Quinn
Package: sweethome3d
Version: 6.1.2+dfsg-2
Severity: important

Dear Maintainer,

   * What led up to the situation?

Installed sweethome3d and its related packages from Debian 10 (Buster) repos

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I attempted to run the sweethome3d executable but it did not succeed.

   * What was the outcome of this action?

Failed with exit status 127 and the message:

/usr/bin/sweethome3d: 304: exec: /usr/lib/jvm/java-6-openjdk-amd64/bin/java:
not found


   * What outcome did you expect instead?

sweethome3d would start.

-

I believe this to be a dependency issue with the package itself for Debian 10.
If sweethome3d requires openjdk6 (don't know if it does), since openjdk6 is no
longer in the repos, should this package be removed?



-- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/12 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 sweethome3d depends on:
ii  default-jre [java7-runtime] 2:1.11-71
ii  icedtea-netx1.7.2-2
ii  java-wrappers   0.3
ii  libbatik-java   1.10-2
ii  libfreehep-graphicsio-svg-java  2.1.1-5
ii  libitext-java   2.1.7-12
ii  libjava3d-java  1.5.2+dfsg-16
ii  libsunflow-java 0.07.2.svn396+dfsg-17
ii  openjdk-11-jre [java7-runtime]  11.0.4+11-1~deb10u1

Versions of packages sweethome3d recommends:
ii  sweethome3d-furniture  1.6.4-1

sweethome3d suggests no packages.

-- no debconf information



Bug#935107: apt: Doing an "apt-get check" does not append "... Done" after the "Building dependency tree" check.

2019-08-19 Thread Jason L. Quinn
Package: apt
Version: 1.8.2
Severity: minor

Dear Maintainer,

This is on Debian Buster.

Do an "apt-get check".

The normal output is

Reading package lists... Done
Building dependency tree
Reading state information... Done

but the expected output is

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done


This makes the user unsure when and if the dependency tree check ever finished.



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-image-unsigned-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-buildinfo-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^linux-source-4\.19\.0-5-amd64$";
APT::NeverAutoRemove:: "^postgresql-";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-modules";
APT::VersionedKernelPackages:: "linux-modules-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "linux-image-unsigned";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::VersionedKernelPackages:: "linux-cloud-tools";
APT::VersionedKernelPackages:: "linux-buildinfo";
APT::VersionedKernelPackages:: "linux-source";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "contrib/metapackages";
APT::Never-MarkAuto-Sections:: "non-free/metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Move-Autobit-Sections:: "contrib/oldlibs";
APT::Move-Autobit-Sections:: "non-free/oldlibs";
APT::Move-Autobit-Sections:: "restricted/oldlibs";
APT::Move-Autobit-Sections:: "universe/oldlibs";
APT::Move-Autobit-Sections:: "multiverse/oldlibs";
APT::Periodic "";
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Unattended-Upgrade "1";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/app-info -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null || true; 
fi";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "false";
APT::Compressor::zstd::Cost "60";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "false";
APT::Compressor::lz4::Cost "50";
APT::Compressor::gzip "";