Bug#1053871: virt-viewer becomes unresponsive when a Display is removed

2023-10-13 Thread Jonas Andradas
Package: virt-viewer
Version: 11.0-3
Severity: normal
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

When interacting with a virtual machine using virt-viewer, a secondary display
can be added, which acts as a second monitor within the VM.

However, if this display is removed from virt-viewer using its menu, virt-
viewer becomes unresponsive: it is not possible to interact with the menus,
manage the window or interact with the VM (through virt-viewer).

It should be noted that the VM is not hang or frozen: if one opens virt-manager
and accesses the VM, this forces a disconnection from virt-viewer (which
closes) and the VM is running fine. The virt-manager window with the VM could
be closed then, and virt-viewer re-opened, allowing in further interaction to
proceed normally.


Thanks,
Jonas.


-- System Information:
Distributor ID: Ubuntu
Description:Ubuntu 22.04.2 LTS
Release:22.04
Codename:   jammy
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages virt-viewer depends on:
ii  libc6   2.37-12
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libglib2.0-02.78.0-2
ii  libgtk-3-0  3.24.38-5
ii  libgtk-vnc-2.0-01.3.1-1
ii  libgvnc-1.0-0   1.3.1-1
ii  libpango-1.0-0  1.51.0+ds-2
ii  libspice-client-glib-2.0-8  0.42-2
ii  libspice-client-gtk-3.0-5   0.42-2
ii  libvirt-glib-1.0-0  4.0.0-3
ii  libvirt09.8.0-1
ii  libvte-2.91-0   0.74.0-2
ii  libxml2 2.9.14+dfsg-1.3

virt-viewer recommends no packages.

Versions of packages virt-viewer suggests:
ii  netcat-openbsd [netcat]  1.225-1
ii  netcat-traditional [netcat]  1.10-47

-- debconf-show failed



Bug#1050416: mariadb-server fails during installation if akonadi is running

2023-08-24 Thread Jonas Andradas
Package: mariadb-server
Version: 1:10.11.4-1
Severity: minor
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

When installing mariadb-server via apt (apt install mariadb-server), during the
package configuration it looks if other mysqld (or mariadb, I suppose) binaries
are running and attempts to stop them.

When akonadi runs, it uses a mysqld binary to keep its settings, but the start
and stop of this daemon is not managed by a systemd mysql.service or
mariadb.service, but rather by akonadi itself (it could be stopped issuing
`akonadictl stop` for example).

During the installation of mariadb-server, it finds a mysqld binary and
attempts to stop it issuing systemd instructions via mysql.service or
mariadb.service. However, if this is the first installation of mariadb-server,
this fails as there is neither a mariadb.service nor a mysql.service, which
results in the installation, with the error message:

~~~
Preparing to unpack .../mariadb-server_1%3a10.11.4-1_amd64.deb ...
Failed to stop mariadb.service: Unit mariadb.service not loaded.
invoke-rc.d: initscript mariadb, action "stop" failed.
Failed to stop mysql.service: Unit mysql.service not loaded.
invoke-rc.d: initscript mysql, action "stop" failed.
Attempt to stop MariaDB/MySQL server returned exitcode 5
There is a MariaDB/MySQL server running, but we failed in our attempts to stop
it.
Stop it yourself and try again!
~~~

The conflicting process was:

~~~
/usr/sbin/mysqld --defaults-file=/home/USER/.local/share/akonadi/mysql.conf
--datadir=/home/USER/.local/share/akonadi/db_data/
--socket=/run/user/1000/akonadi/mysql.socket --pid-
file=/run/user/1000/akonadi/mysql.pid
~~~

Since akonadi might be fairly common if people use KDE or any akonadi
application, it might make sense to either propose stopping and starting
akonadi during the install process (which might have its own complications as
it could interfere with the akonadi applications running, and each interactive
user would have its own process), or suggest how to stop it (if we want to make
it easy for users that might not know akonadi is spawning a mysqld process).

Given that instructions are given (e.g. "Stop it yourself and try again!") and
that it might not be easy to action the stop/start of akonadi reliably during
the installation process, I am raising this with 'minor' severity.

Thanks in advance,
Jonas.


-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-server depends on:
ii  adduser3.137
ii  debconf [debconf-2.0]  1.5.82
ii  galera-4   26.4.13-1
ii  gawk   1:5.2.1-2
ii  iproute2   6.4.0-1
ii  libc6  2.37-7
ii  libdbi-perl1.643-4
ii  libpam0g   1.5.2-7
ii  libssl33.0.10-1
ii  libstdc++6 13.2.0-2
ii  lsof   4.95.0-1
ii  mariadb-client 1:10.11.4-1
ii  mariadb-common 1:10.11.4-1
ii  mariadb-server-core1:10.11.4-1
ii  passwd 1:4.13+dfsg1-1+b1
ii  perl   5.36.0-8
ii  procps 2:4.0.3-1
ii  psmisc 23.6-1
ii  rsync  3.2.7-1
ii  socat  1.7.4.4-2
ii  zlib1g 1:1.2.13.dfsg-3

Versions of packages mariadb-server recommends:
ii  libhtml-template-perl   2.97-2
ii  mariadb-plugin-provider-bzip2   1:10.11.4-1
ii  mariadb-plugin-provider-lz4 1:10.11.4-1
ii  mariadb-plugin-provider-lzma1:10.11.4-1
ii  mariadb-plugin-provider-lzo 1:10.11.4-1
ii  mariadb-plugin-provider-snappy  1:10.11.4-1
ii  pv  1.7.24-1

Versions of packages mariadb-server suggests:
ii  mailutils [mailx]  1:3.16-1
pn  mariadb-test   
ii  netcat-openbsd 1.225-1

-- debconf information:
  mariadb-server/postrm_remove_databases: false
  mariadb-server/nis_warning:
  mariadb-server/old_data_directory_saved:



Bug#1050096: virtualbox-dkms: Does not build on 6.4.0-3-amd64

2023-08-23 Thread Jonas Andradas
Package: virtualbox-dkms
Version: 7.0.10-dfsg-2
Followup-For: Bug #1050096
X-Debbugs-Cc: j.andra...@gmail.com

Following the comments in other bug trackers for this same bugs from other
distros, I could solve it by modifying the file

/usr/src/virtualbox-7.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c

on line 50, changing the value from:

#if RTLNX_VER_MIN(6,5,0)

to:

#if RTLNX_VER_MIN(6,4,0)


After this, it built properly on 6.4.0-3 (where it previously had failed, so
dpkg had finished with errors:

Errors were encountered while processing:
 linux-headers-6.4.0-3-amd64
 linux-headers-amd64
 linux-image-6.4.0-3-amd64
 linux-image-amd64


Thus, `dpkg --configure -a` just compiled the module for 6.4.0-3 as it had been
able to build it fine for 6.4.0-2.
I am not sure if the change I made would break the module from building on
6.4.0-2 or other 6.4.0 kernels.





-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox-dkms depends on:
ii  dkms  3.0.11-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  7.0.10-dfsg-2

virtualbox-dkms suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/src/virtualbox-7.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c (from 
virtualbox-dkms package)



Bug#1042392: - Might just need a clarification

2023-07-27 Thread Jonas Andradas
Hi,  

I noticed that since wireguard has been included in kernels from 5.4 onwards, 
if I am not mistaken, it makes sense for wireguard-dkms to not be built for 
kernels 6.x.  

However, maybe the DKMS error should be handled in some way or a notice be 
printed if DKMS attempts to build the module for kernels >5.4, instead of just 
failing, 
which results in a dpkg error with no additional information.  

Sorry if this bug should not have been raised (as it is expected wireguard-
dkms should not be used with kernels > 5.4), but maybe the suggestion of 
making it clearer is useful. 

Thanks,
Jonas.


Bug#1030150: freeplane fails to start with java 18 (openJDK 18)

2023-01-31 Thread Jonas Andradas
Package: freeplane
Version: 1.7.10-1
Severity: important
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

freeplane fails to start if invoked with Java 18 (OpenJDK 18), due to the
Security Manager being deprecated, apparently.

It still loads fine with OpenJDK 17, but the launch script just seems to use
the default Java in the system (/etc/alternatives/java), which can lead to
issues, as it would not start with later versions of OpenJDK.

It would probably make sense to restrict the Java version used, so if a
previous, working version is available, use that, until freeplane is able to
work under newer Java versions.

The observed error can be found below:


*org.knopflerfish.framework.readonly=true
*org.knopflerfish.gosg.jars=reference:file:/usr/share/freeplane/core/
*org.freeplane.user.dir=/home/jonas/tools/intune/browsercore-linux
*org.freeplane.basedirectory=/usr/share/freeplane
*org.freeplane.globalresourcedir=/usr/share/freeplane/resources
*java.security.policy=/usr/share/freeplane/freeplane.policy
*org.osgi.framework.storage=/usr/share/freeplane/fwdir
Exception in thread "main" java.lang.UnsupportedOperationException: The
Security Manager is deprecated and will be removed in a future release
at java.base/java.lang.System.setSecurityManager(System.java:416)
at
org.freeplane.launcher.Launcher.launchWithoutUICheck(Launcher.java:279)
at org.freeplane.launcher.Launcher.main(Launcher.java:87)



Thank you very much in advance,
Best Regards,
Jonas.


-- Package-specific info:
[debug] /usr/bin/freeplane: Picking up the JVM designated by the alternatives 
system: 
[debug] /usr/bin/freeplane:   JAVA_HOME = '/usr/lib/jvm/java-18-openjdk-amd64'
[debug] /usr/bin/freeplane: Found JAVA_HOME = 
'/usr/lib/jvm/java-18-openjdk-amd64'
[debug] /usr/bin/freeplane: Found JAVA_CMD = 
'/usr/lib/jvm/java-18-openjdk-amd64/bin/java'
DEBUG:   Freeplane parameters are ''.
DEBUG:   Linux darkstar 6.1.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.7-1 
(2023-01-18) x86_64 GNU/Linux
DEBUG:   Distributor ID:Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy
DEBUG:   The following DEB packages are installed:
ii  freeplane   1.7.10-1
 all  Java program for 
working with Mind Maps
DEBUG:   Link '/usr/bin/freeplane' resolved to 
'/usr/share/freeplane/freeplane.sh'.
DEBUG:   Freeplane Directory is '/usr/share/freeplane'.
DEBUG:   Calling: /usr/lib/jvm/java-18-openjdk-amd64/bin/java
 -Xmx512m
 -Dorg.freeplane.basedirectory=/usr/share/freeplane
 -Dorg.freeplane.userfpdir=/home/jonas/.config/freeplane
 -Dorg.freeplane.old_userfpdir=/home/jonas/.freeplane
 -Dorg.freeplane.globalresourcedir=/usr/share/freeplane/resources
 -Dswing.systemlaf=javax.swing.plaf.metal.MetalLookAndFeel
 -Dorg.freeplane.os.lib.ext=/usr/share/java
 -Dawt.useSystemAAFontSettings=on
 -Dswing.aatext=true
 -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D
 -jar
 /usr/share/freeplane/freeplanelauncher.jar

-- System Information:
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages freeplane depends on:
ii  darcula  2018.2-2
ii  default-jre [java8-runtime]  2:1.17-74
ii  groovy   2.4.21-7
ii  ivy  2.5.1-2
ii  javahelp22.0.05.ds1-10
ii  jmapviewer   2.16+dfsg-2
ii  libavalon-framework-java 4.2.0-10
ii  libbatik-java1.16+dfsg-1
ii  libcommons-codec-java1.15-1
ii  libcommons-io-java   2.11.0-2
ii  libcommons-lang-java 2.6-10
ii  libcommons-logging-java  1.2-3
ii  libdata-url-java 1.0.1-2
ii  libfop-java  1:2.8-2
ii  libiconloader-java   0.0+git20170615+dfsg1-2
ii  libidw-java  1.6.1-1.1
ii  libjaxp1.3-java  1.3.05-6
ii  libjgoodies-forms-java   1.9.0-3.1
ii  libjlatexmath-java   1.0.7-3
ii  libjsyntaxpane-java  0.9.6~r156-7.1
ii  libknopflerfish-osgi-framework-java  6.1.1-3.1
ii  libmnemonicsetter-java   0.5-1.1
ii  librhino-java1.7.7.2-3
ii  libsvgsalamander-java1.1.4-1
ii  libxerces2-java  2.12.2-1
ii  

Bug#1013968: libnode72 (12.22.12~dfsg-1~deb11u1) tries to overwrite a file from package nodejs (16.15.1+dfsg-1)

2022-06-28 Thread Jonas Andradas
Package: libnode72
Version: 12.22.12~dfsg-1~deb11u1
Severity: important
X-Debbugs-Cc: j.andra...@gmail.com


Dear Maintainer,

When trying to upgrade libnode72 from 12.22.10~dfsg-2 to
12.22.12~dfsg-1~deb11u1, dpkg complains about the following file, wich is also
found in package nodejs 16.15.1+dfsg-1, trying to be overwritten:

/usr/share/systemtap/tapset/node.stp

This is an excerpt from dpkg output, showing the error:

Unpacking libnode72:amd64 (12.22.12~dfsg-1~deb11u1) over (12.22.10~dfsg-2) ...
dpkg: error processing archive
/var/cache/apt/archives/libnode72_12.22.12~dfsg-1~deb11u1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/systemtap/tapset/node.stp', which is also in
package nodejs 16.15.1+dfsg-1
Errors were encountered while processing:
 /var/cache/apt/archives/libnode72_12.22.12~dfsg-1~deb11u1_amd64.deb


Thank you very much,
Best Regards,
Jonas.


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libnode72 depends on:
ii  libbrotli1 1.0.9-2+b3
ii  libc-ares2 1.18.1-1+b1
ii  libc6  2.33-7
ii  libgcc-s1  12.1.0-4
ii  libicu67   67.1-7
ii  libnghttp2-14  1.47.0-1+b1
ii  libssl1.1  1.1.1o-1
ii  libstdc++6 12.1.0-4
ii  libuv1 1.44.1-2
ii  zlib1g 1:1.2.11.dfsg-4

libnode72 recommends no packages.

libnode72 suggests no packages.

-- no debconf information



Bug#1012124: pipenv: Pipenv 11.9.0-2 fails with python3.10, which is the default python3 in sid

2022-05-30 Thread Jonas Andradas
Package: pipenv
Version: 11.9.0-2
Severity: normal
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

The pipenv script in /usr/bin/pipenv uses the shebang #!/usr/bin/python3, which
in turn points currently in sid to python3.10

When using python3.10 instead of python3.9, pipenv fails with errors such as
those included at the end of this report. However, if the script is invoked
using python 3.9, as follows:

python3.9 /usr/bin/pipenv

then pipenv works fine.

I would assume that either a different, newer version of pipenv needs to be
uploaded, or the current version would need to ensure that python 3.9 is used
instead of python 3.10, by either modifying the shebang in the script, or
verifying that the python version in use is one of the known-compatible ones.

Errors when running pipenv:
--

Traceback (most recent call last):
  File "/usr/bin/pipenv", line 33, in 
sys.exit(load_entry_point('pipenv==11.9.0', 'console_scripts', 'pipenv')())
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 722,
in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 696,
in main
with self.make_context(prog_name, args, **extra) as ctx:
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 621,
in make_context
self.parse_args(ctx, args)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 1018,
in parse_args
rest = Command.parse_args(self, ctx, args)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 875,
in parse_args
parser = self.make_parser(ctx)
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 821,
in make_parser
for param in self.get_params(ctx):
  File "/usr/lib/python3/dist-packages/pipenv/vendor/click/core.py", line 774,
in get_params
help_option = self.get_help_option(ctx)
  File "/usr/lib/python3/dist-packages/pipenv/cli.py", line 26, in
get_help_option
from .import core
  File "/usr/lib/python3/dist-packages/pipenv/core.py", line 21, in 
import requests
  File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/__init__.py",
line 65, in 
from . import utils
  File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/utils.py", line
27, in 
from .cookies import RequestsCookieJar, cookiejar_from_dict
  File "/usr/lib/python3/dist-packages/pipenv/vendor/requests/cookies.py", line
172, in 
class RequestsCookieJar(cookielib.CookieJar, collections.MutableMapping):
AttributeError: module 'collections' has no attribute 'MutableMapping'

--


Thank you very much!


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

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

Versions of packages pipenv depends on:
ii  python3   3.10.4-1+b1
ii  python3-certifi   2020.6.20-1
ii  python3-pip   22.1.1+dfsg-1
ii  python3-pkg-resources 59.6.0-1.2
ii  python3-virtualenv20.14.0+ds-1
ii  python3-virtualenv-clone  0.3.0-2

pipenv recommends no packages.

pipenv suggests no packages.

-- no debconf information



Bug#994695: qreator: won't start

2022-05-11 Thread Jonas Andradas
Package: qreator
Version: 16.06.1-7
Followup-For: Bug #994695
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

I confirm I am also seeing this bug, as I am getting the same type of errors,
which prevent qreator from starting:

/usr/share/qreator/qreator_lib/Builder.py:21: 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 GObject, Gtk # pylint: disable=E0611
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 142, in
load_module
introspection_module = get_introspection_module(namespace)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 257, in
get_introspection_module
module = IntrospectionModule(namespace, version)
  File "/usr/lib/python3/dist-packages/gi/module.py", line 109, in __init__
repository.require(namespace, version)
gi.RepositoryError: Requiring namespace 'Gtk' version '3.0', but '4.0' is
already loaded

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/qreator", line 45, in 
import qreator
  File "/usr/share/qreator/qreator/__init__.py", line 38, in 
__import__(name, fromlist=[])
  File "/usr/share/qreator/qreator/qrcodes/QRCodeLocation.py", line 19, in

from .QRCodeLocationGtk import QRCodeLocationGtk
  File "/usr/share/qreator/qreator/qrcodes/QRCodeLocationGtk.py", line 20, in

from gi.repository import (
  File "/usr/lib/python3/dist-packages/gi/importer.py", line 144, in
load_module
raise ImportError(e)
ImportError: Requiring namespace 'Gtk' version '3.0', but '4.0' is already
loaded


Thank you very much in advance,
Best Regards,
Jonas.


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

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

Versions of packages qreator depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  geoclue-2.0  2.6.0-1
ii  gir1.2-champlain-0.120.12.20-1+b1
ii  gir1.2-clutter-1.0   1.26.4+dfsg-4
ii  gir1.2-gdkpixbuf-2.0 2.42.8+dfsg-1
ii  gir1.2-geoclue-2.0   2.6.0-1
ii  gir1.2-glib-2.0  1.72.0-1+b1
ii  gir1.2-gtk-3.0   3.24.33-1
ii  gir1.2-gtkchamplain-0.12 0.12.20-1+b1
ii  gir1.2-gtkclutter-1.01.8.4-4+b1
ii  gir1.2-nm-1.01.37.92-1
ii  python3  3.10.4-1+b1
ii  python3-cairo1.20.1-3
ii  python3-dbus 1.2.18-3+b1
ii  python3-gi   3.42.1-1
ii  python3-gi-cairo 3.42.1-1
ii  python3-pil  9.1.0-1
ii  python3-qrencode 1.2-5+b5
ii  python3-requests 2.27.1+dfsg-1
ii  python3-vobject  0.9.6.1-0.2
ii  python3-xdg  0.27-2

qreator recommends no packages.

qreator suggests no packages.

-- no debconf information



Bug#1006942: safeeyes: Safeeyes no longer seems to appears in the KDE/Plasma system tray

2022-03-09 Thread Jonas Andradas
On Tue, Mar 8, 2022 at 5:57 PM Jonas Andradas  wrote:

> Package: safeeyes
> Version: 2.1.3-1
> Severity: minor
> X-Debbugs-Cc: j.andra...@gmail.com
>
> Dear Maintainer,
>
> I noticed that fairly recently (unfortunately, cannot exactly be sure when
> or
> after which package update), safeeyes does not seem appear anymore in
> KDE/Plasma system tray. It is not shown on the system tray, neither in the
> "visible" elements nor in the "box" that has the hidden icons.
>
> Accessing the "Configure System Tray" setting, different entries appear for
> "Application Status" (Bluetooth active device, flameshot, KGpg, etc.),
> "Hardware Control" (audio volume, battery, disks, display
> configuration, etc.), "System Services" (backup status, clipboard, disk
> quota...) and "Miscellaneous" (which in my case shows kate sessions and
> weather
> report). However, safeeyes does not seem to appear there, which makes me
> think
> somehow it is not recognized by KDE/Plasma as something to be shown on the
> system tray.
>
> Before observing this behavior, I had saafeeyes on the system tray, to be
> able
> to postpone or skip the next break, quit safeeyes, etc.
>
> I am raising the bug in safeeyes as I speculate it is not announcing
> itself to
> KDE/Plasma in the way these expect it to be there. However, if the bug
> should
> be in KDE/Plasma, please feel free to move it there (if possible) or ask
> me to
> report it under the appropriate component.
>
> The versions of Plasma workspace/desktop I currently have installed are the
> following ones:
>
> plasma-workspace: 4:5.24.2-2
> plasma-desktop: 4:5.24.2-1
>
> Best Regards,
> Jonas.
>
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers stable-security
>   APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.16.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_GB:en
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages safeeyes depends on:
> ii  gir1.2-gtk-3.03.24.31-1
> ii  python3   3.9.8-1
> ii  python3-babel 2.8.0+dfsg.1-7
> ii  python3-croniter  1.0.15-3
> ii  python3-dbus  1.2.18-3+b1
> ii  python3-gi3.42.0-3
> ii  python3-psutil5.9.0-1
> ii  python3-xlib  0.29-1
>
> Versions of packages safeeyes recommends:
> pn  gir1.2-appindicator3-0.1  
> ii  xprintidle0.2.4-2
>
> safeeyes suggests no packages.
>
> -- no debconf information
>

It seems that this bug was also opened upstream on safeeyes' github:
https://github.com/slgobinath/SafeEyes/issues/428 (which seems related to
https://github.com/slgobinath/SafeEyes/issues/268)

Best Regards,
Jonas.


Bug#1006942: safeeyes: Safeeyes no longer seems to appears in the KDE/Plasma system tray

2022-03-08 Thread Jonas Andradas
Package: safeeyes
Version: 2.1.3-1
Severity: minor
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

I noticed that fairly recently (unfortunately, cannot exactly be sure when or
after which package update), safeeyes does not seem appear anymore in
KDE/Plasma system tray. It is not shown on the system tray, neither in the
"visible" elements nor in the "box" that has the hidden icons.

Accessing the "Configure System Tray" setting, different entries appear for
"Application Status" (Bluetooth active device, flameshot, KGpg, etc.),
"Hardware Control" (audio volume, battery, disks, display
configuration, etc.), "System Services" (backup status, clipboard, disk
quota...) and "Miscellaneous" (which in my case shows kate sessions and weather
report). However, safeeyes does not seem to appear there, which makes me think
somehow it is not recognized by KDE/Plasma as something to be shown on the
system tray.

Before observing this behavior, I had saafeeyes on the system tray, to be able
to postpone or skip the next break, quit safeeyes, etc.

I am raising the bug in safeeyes as I speculate it is not announcing itself to
KDE/Plasma in the way these expect it to be there. However, if the bug should
be in KDE/Plasma, please feel free to move it there (if possible) or ask me to
report it under the appropriate component.

The versions of Plasma workspace/desktop I currently have installed are the
following ones:

plasma-workspace: 4:5.24.2-2
plasma-desktop: 4:5.24.2-1

Best Regards,
Jonas.


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

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

Versions of packages safeeyes depends on:
ii  gir1.2-gtk-3.03.24.31-1
ii  python3   3.9.8-1
ii  python3-babel 2.8.0+dfsg.1-7
ii  python3-croniter  1.0.15-3
ii  python3-dbus  1.2.18-3+b1
ii  python3-gi3.42.0-3
ii  python3-psutil5.9.0-1
ii  python3-xlib  0.29-1

Versions of packages safeeyes recommends:
pn  gir1.2-appindicator3-0.1  
ii  xprintidle0.2.4-2

safeeyes suggests no packages.

-- no debconf information



Bug#1006696: network-manager-openvpn: No warning to the user when some elements from the .ovpn cannot be imported

2022-03-02 Thread Jonas Andradas
Package: network-manager-openvpn
Version: 1.8.16-1
Severity: wishlist
X-Debbugs-Cc: jo...@alternativaslibres.es

Dear Maintainer,

When importing .ovpn files into network manager, there is no warning or message
whatsoever to the user that some of the elements could not be imported. It
would be desired that, either on the GUI or when using nmcli, if any of the
settings on the .ovpn file are not (or cannot) be imported, these are listed or
at least a warning is shown indicating to the user that they might need to take
additional steps to have their connection behave (or work) on Network Manager
in a similar manner as what they would expect if they were using openvpn
connection.ovpn on the command line.

One obvious example of this could be when the .ovpn file contains "up" or
"down" scripts or commands. Probably some users would like something to be
automagically added into /etc/NetworkManager/dispatcher.d, but since this could
be problematic or hard to do (without taking into account other scripts already
there, or which name will the tun/tap interface will have, etc.), maybe just
showing a message to the user indicating something along the lines of: "Up/Down
scripts in the .ovpn file could not be imported automatically. Please consider
using a script under /etc/NetworkManager/dispatcher.d as necessary (with
reference to the documentation or NetworkManager-dispatcher manpage)"

This issue could be considered somewhat related to issue #818147. However,
since what is being requested is different, I preferred to open a separate
issue on the bug tracker.


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

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

Versions of packages network-manager-openvpn depends on:
ii  adduser  3.118
ii  libc62.33-7
ii  libglib2.0-0 2.70.4-1
ii  libnm0   1.36.0-1
ii  network-manager  1.36.0-1
ii  openvpn  2.5.5-1

network-manager-openvpn recommends no packages.

network-manager-openvpn suggests no packages.

-- no debconf information



Bug#1006334: nheko closes when looking up the matrix id on the matrix.org server

2022-02-23 Thread Jonas Andradas
Package: nheko
Version: 0.9.0-1+b1
Severity: important
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

When trying to log into my matrix account, nheko crashes due to an error.
Please see the steps below to reproduce:

1. After nheko starts for the first time, it asks to either register or login.
2. If "login" is chosen, a window prompts for the Matrix id, password and
device name
3. After filling the matrix id with a correct format, e.g. "@user:matrix.org",
nheko seems to do a lookup of the Matrix id and crashes.

Please see below the errors that are output on the console:

---

[2022-02-23 18:58:00.152] [ui] [info] Restoring window size 0x0
[2022-02-23 18:58:00.268] [ui] [info] WebRTC: initialised GStreamer 1.20.0
[2022-02-23 18:58:00.551] [ui] [info] jdenticon plugin not found.
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
[2022-02-23 18:58:00.699] [qml] [warning] HSpellDict::HSpellDict: Init failed
(:0, )
[2022-02-23 18:58:01.063] [ui] [info] starting nheko 0.9.0
[2022-02-23 18:58:14.846] [net] [info] Autodiscovery: Discovered
'https://matrix-client.matrix.org'
terminate called after throwing an instance of 'std::invalid_argument'
  what():  v1.1: invalid version
Error: signal 6:
nheko(_Z17stacktraceHandleri+0x3b)[0x55aa80eca02b]
/lib/x86_64-linux-gnu/libc.so.6(+0x38920)[0x7fda43ac4920]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7fda43ac48a1]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x112)[0x7fda43aae546]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x9d88a)[0x7fda43e8388a]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa905a)[0x7fda43e8f05a]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90c5)[0x7fda43e8f0c5]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa9359)[0x7fda43e8f359]
nheko(+0x2ca98e)[0x55aa80bf198e]
nheko(_ZZN3mtx4http6Client16prepare_callbackINS_9responses8VersionsEEESt8functionIFvRKSt8optionalISt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESD_N6coeurl11header_lessESaISt4pairIKSD_SD_RKSt17basic_string_viewIcSB_EiiEES5_IFvRKT_SN_RKS6_INS0_11ClientErrorENKUlSN_SR_iiE_clESN_SR_ii+0x11d)[0x55aa80f68a8d]
nheko(+0x5d621b)[0x55aa80efd21b]
nheko(_ZN6coeurl6Client14remove_requestEPNS_7RequestE+0x2de)[0x55aa810a235e]
nheko(_ZN6coeurl6Client16check_multi_infoEv+0x163)[0x55aa810a2603]
nheko(_ZN6coeurl6Client8event_cbEisPv+0x5b)[0x55aa810a274b]
/usr/lib/x86_64-linux-gnu/libevent_core-2.1.so.7(+0x1f35f)[0x7fda4661935f]
/usr/lib/x86_64-linux-
gnu/libevent_core-2.1.so.7(event_base_loop+0x52f)[0x7fda46619a9f]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xd3954)[0x7fda43eb9954]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7d80)[0x7fda43c6cd80]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7fda43b8676f]
Aborted

---



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

Kernel: Linux 5.16.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_AUX
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nheko depends on:
ii  gstreamer1.0-nice   0.1.18-2
ii  gstreamer1.0-qt51.20.0-2
ii  gstreamer1.0-vaapi  1.20.0-1
ii  libc6   2.33-7
ii  libcmark0.30.2  0.30.2-5
ii  libcurl47.81.0-1
ii  libevent-core-2.1-7 2.1.12-stable-1
ii  libevent-pthreads-2.1-7 2.1.12-stable-1
ii  libfmt8 8.1.1+ds1-2
ii  libgcc-s1   11.2.0-16
ii  libglib2.0-02.70.4-1
ii  libgstreamer-plugins-bad1.0-0   1.20.0-4+b1
ii  libgstreamer-plugins-base1.0-0  1.20.0-2
ii  libgstreamer1.0-0   1.20.0-1
ii  liblmdb00.9.24-1
ii  libolm3 3.2.10~dfsg-6
ii  libqt5core5a5.15.2+dfsg-14
ii  libqt5dbus5 5.15.2+dfsg-14
ii  libqt5gui5  5.15.2+dfsg-14
ii  libqt5keychain1 0.12.0-1
ii  libqt5multimedia5   5.15.2-3
ii  libqt5network5  5.15.2+dfsg-14
ii  libqt5qml5  5.15.2+dfsg-10
ii  libqt5quick55.15.2+dfsg-10
ii  libqt5quickwidgets5 5.15.2+dfsg-10
ii  libqt5svg5  5.15.2-4
ii  libqt5widgets5  5.15.2+dfsg-14
ii  libspdlog1 [libspdlog1-fmt8]1:1.9.2+ds-0.2
ii  libssl1.1   1.1.1m-1
ii  libstdc++6  11.2.0-16
ii  libxcb-ewmh20.4.1-1.1
ii  libxcb1 1.14-3
ii  qml-module-qt-labs-platform 5.15.2+dfsg-4
ii  qml-module-qt-labs-settings 5.15.2+dfsg-10
ii  

Bug#993085: deluge-web: Stack traces and python errors when using the web and interacting with deluged daemon

2021-10-24 Thread Jonas Andradas
On Fri, 27 Aug 2021 12:10:22 +0200 Jonas Andradas  
wrote:
> Package: deluge-web
> Version: 2.0.3-3.1
> Severity: important
> X-Debbugs-Cc: j.andra...@gmail.com
> 
> Dear Maintainer,
> 
> Since the update to Debian 11 "bullseye", which updated Python to
> version 3.9, I am seeing that deluge-web (and the deluged daemon) are
> showing some errors. 
> 
> When using the web interface to connect to the daemon, the web appears
> empty, and any attempt to modify the configuration does not seem to
> persist this. Adding a torrent (from a URL or a file, for example Debian's 
ISO
> installer [1]) errors start to appear in the console and, despite the
> torrent seems added in the web interface, it never starts downloading,
> and does not seem recognized by the backend deluged daemon.
> 
> [1] 
> https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-11.0.0-amd64-DVD-1.iso.torrent
> 
> The errors I observe in the console are the following ones, repeated
> many times:
> 
> Temporarily disabling observer LegacyLogObserverWrapper(>) due to exception: [Failure instance: Traceback: : findCaller() takes from 1 to 2 positional arguments but 3 were 
given
> /usr/lib/python3/dist-packages/twisted/internet/defer.py:
568:_startRunCallbacks
> /usr/lib/python3/dist-packages/twisted/internet/defer.py:962:__del__
> /usr/lib/python3/dist-packages/twisted/logger/_logger.py:190:failure
> /usr/lib/python3/dist-packages/twisted/logger/_logger.py:144:emit
> ---  ---
> /usr/lib/python3/dist-packages/twisted/logger/_observer.py:131:__call__
> /usr/lib/python3/dist-packages/twisted/logger/_legacy.py:93:__call__
> /usr/lib/python3/dist-packages/deluge/log.py:204:emit
> /usr/lib/python3.9/logging/__init__.py:1489:critical
> /usr/lib/python3.9/logging/__init__.py:1573:_log
> ]
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 568, 
in _startRunCallbacks
> self._runCallbacks()
>   File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 962, 
in __del__
> log.failure(format,
>   File "/usr/lib/python3/dist-packages/twisted/logger/_logger.py", line 190, 
in failure
> self.emit(level, format, log_failure=failure, **kwargs)
>   File "/usr/lib/python3/dist-packages/twisted/logger/_logger.py", line 144, 
in emit
> self.observer(event)
> ---  ---
>   File "/usr/lib/python3/dist-packages/twisted/logger/_observer.py", line 
131, in __call__
> observer(event)
>   File "/usr/lib/python3/dist-packages/twisted/logger/_legacy.py", line 93, 
in __call__
> self.legacyObserver(event)
>   File "/usr/lib/python3/dist-packages/deluge/log.py", line 204, in emit
> getattr(LoggingLoggerClass, event_dict['log_level'].name)(
>   File "/usr/lib/python3.9/logging/__init__.py", line 1489, in critical
> self._log(CRITICAL, msg, args, **kwargs)
>   File "/usr/lib/python3.9/logging/__init__.py", line 1573, in _log
> fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
> builtins.TypeError: findCaller() takes from 1 to 2 positional arguments but 3 
were given
> 
> Unhandled error in Deferred:
> 12:04:33 [CRITICAL][twisted:154 ] Unhandled error in 
Deferred:
> 

This seems to be a known issue, cause because the logging.Logger class in 
Python > 3.8 has changed.  There is a path for file deluge/log.py which solves 
the issue (I tested this locally), which is referenced in deluge's git [1]

[1]

diff --git a/deluge/log.py b/deluge/log.py
index 75e8308..0f9877f 100644
--- a/deluge/log.py
+++ b/deluge/log.py
@@ -86,7 +86,7 @@ class Logging(LoggingLoggerClass):
 def exception(self, msg, *args, **kwargs):
 yield LoggingLoggerClass.exception(self, msg, *args, **kwargs)
 
-def findCaller(self, stack_info=False):  # NOQA: N802
+def findCaller(self, *args, **kwargs):  # NOQA: N802
 f = logging.currentframe().f_back
 rv = '(unknown file)', 0, '(unknown function)'
 while hasattr(f, 'f_code'):



Bug#996975: deluge-web: Systemd script for deluge-web needs amending to start the service

2021-10-21 Thread Jonas Andradas
Package: deluge-web
Version: 2.0.3-3.1
Severity: normal
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

the deluge-web systemd script that is shipped with Debian Bullseye 
(deluge-web 2.0.3-3.1) does not properly start the service in its 
current state (likely due to changes in deluge-web itself). 

The current systemd configuration uses Type=simple the ExecStart that
can be seen in the excerpt below:

-
[Unit]
Description=Deluge Bittorrent Client Web Interface
Documentation=man:deluge-web
After=network-online.target deluged.service
Wants=deluged.service
[Service]
Type=simple
User=debian-deluged
Group=debian-deluged
UMask=027
# This 5 second delay is necessary on some systems
# to ensure deluged has been fully started
ExecStartPre=/bin/sleep 5
ExecStart=/usr/bin/deluge-web
Restart=on-failure
[Install]
WantedBy=multi-user.target


This combination results in the binary not starting properly.  This can
be easily fixed by adding the '-d' flag to the ExecStart command,
resulting in:

ExecStart=/usr/bin/deluge-web -d

Other options might be possible, such as changing the Type of the
service, but I am not sure which approach would be preferable as the
default choice for the package.

Given that the systemd configuration exists, probably issues #966287 and
#927197 can be considered as closed.

Thank you very much,
Best Regards,
Jonas.

-- 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.11.22-2-pve (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE
Locale: LANG=en_GB.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)

Versions of packages deluge-web depends on:
ii  deluge-common  2.0.3-3.1
ii  python33.9.2-3
ii  python3-mako   1.1.3+ds1-2

deluge-web recommends no packages.

deluge-web suggests no packages.

-- no debconf information



Bug#996455: firefox: /usr/bin/firefox still uses the deprecated "which"

2021-10-14 Thread Jonas Andradas
Package: firefox
Version: 93.0-1
Severity: normal
Tags: patch
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

the firefox package installs a bash script in /usr/bin/firefox to startup the
browser.  This script still uses "which", which has been deprecated, and an
error is printed when invoking /usr/bin/firefox from the command line:

$ firefox http://debian.org
/usr/bin/which: this version of `which' is deprecated; use `command -v' in
scripts instead.


The issue can be easily solved by replacing "which" by "command -v" in the
script, as suggested in the error message.

The patch file would be:


3c3
< FIREFOX="$(which firefox)"
---
> FIREFOX="$(command -v firefox)"



-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox depends on:
ii  debianutils  5.5-1
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libc62.32-4
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-2
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi8  3.4.2-3
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s111.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.0-1+b1
ii  libgtk-3-0   3.24.30-3
ii  libnspr4 2:4.32-1
ii  libnss3  2:3.70-1
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libstdc++6   11.2.0-9
ii  libvpx6  1.10.0-2
ii  libx11-6 2:1.7.2-2+b1
ii  libx11-xcb1  2:1.7.2-2+b1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.5-2
ii  libxext6 2:1.3.4-1
ii  libxfixes3   1:5.0.3-2
ii  libxrender1  1:0.9.10-1
ii  procps   2:3.3.17-5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages firefox recommends:
ii  libavcodec57  7:3.4.3-1
ii  libavcodec58  7:4.4-6+b2

Versions of packages firefox suggests:
ii  fonts-lmodern  2.004.5-6.1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-8
ii  libgssapi-krb5-2   1.18.3-7
ii  pulseaudio 15.0+dfsg1-2

-- no debconf information
3c3
< FIREFOX="$(which firefox)"
---
> FIREFOX="$(command -v firefox)"


Bug#989147: glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes

2021-09-15 Thread Jonas Andradas
Hi Aurelien, 

On Wednesday, 8 September 2021 21:56:51 CEST you wrote:
> On 2021-09-08 13:25, Jonas Andradas wrote:
> > Hi,
> > 
> > On Sat, 21 Aug 2021 20:14:52 +0200 Aurelien Jarno 
> > 
> > wrote:
> > > Version: 2.32-0experimental0
> > > 
> > > On 2021-05-26 21:57, Salvatore Bonaccorso wrote:
> > > > Source: glibc
> > > > Version: 2.31-12
> > > > Severity: important
> > > > Tags: security upstream
> > > > Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=27896
> > > > X-Debbugs-Cc: car...@debian.org, Debian Security Team
> > 
> > 
> > 
> > [...snip...]
> > 
> > > This bug has been fixed in the glibc 2.32-0experimental0 upload to
> > > experimental, but wasn't close due to a typo in the changelog. Closing
> > > the bug manually.
> > 
> > Is there an estimated timeline for when the experimental, fixed package
> > would transition to sid (and possibly testing/bookworm)?  Is there an
> > estimate for
> The fix is already in sid for a few days. Transition to testing/bookworm
> depends on many factors that are out of control of the glibc
> maintainers.
> 

I did not see this in the tracker [1] (or I interpreted it wrong), so I 
assumed it was not there yet.  Thanks for clarifying!

[1] https://security-tracker.debian.org/tracker/CVE-2021-33574

> > when the fix will be backported to bullseye?
> 
> Unfortunately the fixes are not trivial to get backported, as they
> depend on new symbols exported through GLIBC_PRIVATE. This is something
> in progress, but I have no ETA so far.
> 

Also thank you for the insight here, as it helps knowing when backporting the 
fix is not trivial, to plan and manage the expectations of addressing the issue 
in production accordingly.

> Best regards,
> Aurelien

Best Regards,
Jonas.



Bug#989147: glibc: CVE-2021-33574: mq_notify does not handle separately allocated thread attributes

2021-09-08 Thread Jonas Andradas
Hi, 

On Sat, 21 Aug 2021 20:14:52 +0200 Aurelien Jarno  
wrote:
> Version: 2.32-0experimental0
> 
> On 2021-05-26 21:57, Salvatore Bonaccorso wrote:
> > Source: glibc
> > Version: 2.31-12
> > Severity: important
> > Tags: security upstream
> > Forwarded: https://sourceware.org/bugzilla/show_bug.cgi?id=27896
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team 

> > 
[...snip...]
> 
> This bug has been fixed in the glibc 2.32-0experimental0 upload to
> experimental, but wasn't close due to a typo in the changelog. Closing
> the bug manually.
> 

Is there an estimated timeline for when the experimental, fixed package would 
transition to sid (and possibly testing/bookworm)?  Is there an estimate for 
when the fix will be backported to bullseye? 

Thank you very much in advance,
Best Regards,
Jonas.



Bug#993085: deluge-web: Stack traces and python errors when using the web and interacting with deluged daemon

2021-08-27 Thread Jonas Andradas
Package: deluge-web
Version: 2.0.3-3.1
Severity: important
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

Since the update to Debian 11 "bullseye", which updated Python to
version 3.9, I am seeing that deluge-web (and the deluged daemon) are
showing some errors. 

When using the web interface to connect to the daemon, the web appears
empty, and any attempt to modify the configuration does not seem to
persist this. Adding a torrent (from a URL or a file, for example Debian's ISO
installer [1]) errors start to appear in the console and, despite the
torrent seems added in the web interface, it never starts downloading,
and does not seem recognized by the backend deluged daemon.

[1] 
https://cdimage.debian.org/debian-cd/current/amd64/bt-dvd/debian-11.0.0-amd64-DVD-1.iso.torrent

The errors I observe in the console are the following ones, repeated
many times:

Temporarily disabling observer LegacyLogObserverWrapper(>) due to exception: [Failure instance: Traceback: : findCaller() takes from 1 to 2 positional arguments but 3 were 
given
/usr/lib/python3/dist-packages/twisted/internet/defer.py:568:_startRunCallbacks
/usr/lib/python3/dist-packages/twisted/internet/defer.py:962:__del__
/usr/lib/python3/dist-packages/twisted/logger/_logger.py:190:failure
/usr/lib/python3/dist-packages/twisted/logger/_logger.py:144:emit
---  ---
/usr/lib/python3/dist-packages/twisted/logger/_observer.py:131:__call__
/usr/lib/python3/dist-packages/twisted/logger/_legacy.py:93:__call__
/usr/lib/python3/dist-packages/deluge/log.py:204:emit
/usr/lib/python3.9/logging/__init__.py:1489:critical
/usr/lib/python3.9/logging/__init__.py:1573:_log
]
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 568, in 
_startRunCallbacks
self._runCallbacks()
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 962, in 
__del__
log.failure(format,
  File "/usr/lib/python3/dist-packages/twisted/logger/_logger.py", line 190, in 
failure
self.emit(level, format, log_failure=failure, **kwargs)
  File "/usr/lib/python3/dist-packages/twisted/logger/_logger.py", line 144, in 
emit
self.observer(event)
---  ---
  File "/usr/lib/python3/dist-packages/twisted/logger/_observer.py", line 131, 
in __call__
observer(event)
  File "/usr/lib/python3/dist-packages/twisted/logger/_legacy.py", line 93, in 
__call__
self.legacyObserver(event)
  File "/usr/lib/python3/dist-packages/deluge/log.py", line 204, in emit
getattr(LoggingLoggerClass, event_dict['log_level'].name)(
  File "/usr/lib/python3.9/logging/__init__.py", line 1489, in critical
self._log(CRITICAL, msg, args, **kwargs)
  File "/usr/lib/python3.9/logging/__init__.py", line 1573, in _log
fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
builtins.TypeError: findCaller() takes from 1 to 2 positional arguments but 3 
were given

Unhandled error in Deferred:
12:04:33 [CRITICAL][twisted:154 ] Unhandled error in 
Deferred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 654, in 
_runCallbacks
current.result = callback(current.result, *args, **kw)
  File "/usr/lib/python3/dist-packages/deluge/ui/web/json_api.py", line 185, in 
_on_rpc_request_failed
log.error(reason)
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1613, 
in unwindGenerator
return _cancellableInlineCallbacks(gen)
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1529, 
in _cancellableInlineCallbacks
_inlineCallbacks(None, g, status)
---  ---
  File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1418, 
in _inlineCallbacks
result = g.send(result)
  File "/usr/lib/python3/dist-packages/deluge/log.py", line 79, in error
yield LoggingLoggerClass.error(self, msg, *args, **kwargs)
  File "/usr/lib/python3.9/logging/__init__.py", line 1471, in error
self._log(ERROR, msg, args, **kwargs)
  File "/usr/lib/python3.9/logging/__init__.py", line 1573, in _log
fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
builtins.TypeError: findCaller() takes from 1 to 2 positional arguments but 3 
were given

==

This issue might be an upstream issue in deluge-web/deluged, or in the
dependencies used (e.g. twisted), not sure. 

I have tried removing all my previous configuration files
(/var/lib/deluge/config and also /var/lib/deluge/.config) with the same
results.  I have purged the deluge* packages and re-installed, also with
the same results.

Thank you very much in advance!


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

Kernel: Linux 5.11.22-2-pve (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 

Bug#993083: deluged: Deluged throws Critical errors due to unhandled errors after updating to Python3.9

2021-08-27 Thread Jonas Andradas
Package: deluged
Version: 2.0.3-3.1
Severity: important
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

since updating my system to Debian 11 "bullseye", which updated Python
to version 3.9, deluged (and deluge-web and deluge-console) have stopped
working as expected.

I have tried using the init.d scripts to start the service and also
manually (as de debian-deluged user), with the same results, explained
below:

  * The daemon starts and listens on the daemon port (for management)
and in a random port for incoming connections (despite
listening_ports are defined in the configuration file, these are not
used)

  * The process starts logging critical errors to
/var/log/deluge/daemon.log, such as the following ones:

11:34:37 [INFO][deluge.configmanager:52  ] Setting config directory to: 
/var/lib/deluged/config
11:34:37 [CRITICAL][twisted   :154 ] Unhandled error in 
Deferred:
11:34:38 [CRITICAL][twisted   :154 ] Unhandled error in 
Deferred:
11:34:38 [CRITICAL][twisted   :154 ] Unhandled error in 
Deferred:
11:34:38 [CRITICAL][twisted   :154 ] Unhandled error in 
Deferred:
11:34:38 [CRITICAL][twisted   :154 ] Unhandled error in 
Deferred:
11:34:38 [INFO][twisted   :154 ] Factory (TLS) 
starting on 58846
11:34:38 [INFO][twisted   :154 ] Starting factory 

11:34:38 [CRITICAL][twisted   :154 ] Unhandled error in 
Deferred:
11:35:08 [CRITICAL][twisted   :154 ] Unhandled error in 
Deferred:

  * Whenever interaction with the daemon is attempted via deluge-console 
or deluge-web, nothing is logged and, despite these connections seem 
to be successful (e.g. the client seems to interact with the backend 
server, any added torrents or settings changed are not persisted.

  * The torrents are not processed nor downloaded.

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

Kernel: Linux 5.11.22-2-pve (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE
Locale: LANG=en_GB.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)

Versions of packages deluged depends on:
ii  adduser 3.118
ii  deluge-common   2.0.3-3.1
ii  lsb-base11.1.0
ii  python3 3.9.2-3
ii  python3-libtorrent  1.2.9-0.3

deluged recommends no packages.

deluged suggests no packages.

-- Configuration Files:
/etc/default/deluged changed:
ENABLE_DELUGED=1


-- no debconf information



Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

2021-06-22 Thread Jonas Andradas
Package: libopenscap8
Version: 1.3.4-1
Severity: important
X-Debbugs-Cc: j.andra...@gmail.com

Dear Maintainer,

scap-workbench (version 1.1.5-1) depends on libopenscap8. However, when scap-
workbench is run, it fails as it cannot load libopenscap.so.8, as shown below:

scap-workbench: error while loading shared libraries: libopenscap.so.8: cannot
open shared object file: No such file or directory

Running `apt-files search libopenscap.so.8`, it appears listed as part of the
package libopenscap8, as can be seen below:

$ apt-file search libopenscap.so.8
libopenscap8: /usr/lib/x86_64-linux-gnu/libopenscap.so.8
libopenscap8: /usr/lib/x86_64-linux-gnu/libopenscap.so.8.14.0

However, the file is not found on the system, and `dpkg -L libopenscap8`
differs from the output of `apt-file search`, and does not show the file as
being installed or part of the package:

$ dpkg -L libopenscap8 | grep libopenscap
/usr/lib/x86_64-linux-gnu/libopenscap.so.25.3.0
/usr/lib/x86_64-linux-gnu/libopenscap_sce.so.25.3.0
/usr/share/doc/libopenscap8
/usr/share/doc/libopenscap8/changelog.Debian.gz
/usr/share/doc/libopenscap8/copyright
/usr/share/lintian/overrides/libopenscap8
/usr/lib/x86_64-linux-gnu/libopenscap.so.25
/usr/lib/x86_64-linux-gnu/libopenscap_sce.so.25


Either the libopenscap.so.8 file is missing from the package, or a postinstall
script that should create the necessary links (e.g. if the included
libopenscap.so.25.3.0 should have a soft link to it), or the issue lies within
the scap-workbench package, which expects a library that has a different name.


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

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

Versions of packages libopenscap8 depends on:
ii  libapt-pkg6.0  2.2.4
ii  libbz2-1.0 1.0.8-4
ii  libc6  2.31-12
ii  libcap21:2.44-1
ii  libcurl4   7.74.0-1.2
ii  libdbus-1-31.12.20-2
ii  libgcc-s1  10.2.1-6
ii  libgcrypt201.8.7-6
ii  libpcre3   2:8.39-13
ii  libselinux13.1-3
ii  libstdc++6 10.2.1-6
ii  libxml22.9.10+dfsg-6.7
ii  libxslt1.1 1.1.34-4
ii  python33.9.2-3

libopenscap8 recommends no packages.

libopenscap8 suggests no packages.



Bug#972483: virtualbox-dkms: Cannot compile modules on kernel version 5.9.0-1

2020-10-19 Thread Jonas Andradas
Package: virtualbox-dkms
Version: 6.1.14-dfsg-4
Followup-For: Bug #972483

Hello,

I am experiencing this issue as well

$ dpkg -l | grep virtualbox

ii  virtualbox
 6.1.14-dfsg-4
amd64x86 virtualization solution - base binaries
ii  virtualbox-dkms
6.1.14-dfsg-4
amd64x86 virtualization solution - kernel module sources for dkms
ii  virtualbox-ext-pack 6.1.14-2
all  extra capabilities for VirtualBox, downloader.
ii  virtualbox-guest-additions-iso  6.1.14-1
all  guest additions iso image for VirtualBox
ii  virtualbox-qt


DKMS version 2.8.3-4

When attempting to compile the kernel modules, the following error is
observed:

# cat /var/lib/dkms/virtualbox/6.1.14/build/make.log
DKMS make.log for virtualbox-6.1.14 for kernel 5.9.0-1-amd64 (x86_64)
Mon 19 Oct 15:04:20 CEST 2020
make: Entering directory '/usr/src/linux-headers-5.9.0-1-amd64'
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/r0drv/alloc-r0drv.o
  CC [M]
 /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/r0drv/initterm-r0drv.o
  CC [M]  /var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/r0drv/memobj-r0drv.o
  CC [M]
/var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/r0drv/mpnotification-r0drv.o
In file included from
/var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/linux/SUPDrv-linux.c:33:
/var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/r0drv/linux/the-linux-
kernel.h:141:11: fatal error: linux/smp_lock.h: No such file or directory
  141 | # include 
  |   ^~
compilation terminated.
make[3]: ***
[/usr/src/linux-headers-5.9.0-1-common/scripts/Makefile.build:288:
/var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/linux/SUPDrv-linux.o] Error 1
make[3]: *** Waiting for unfinished jobs
/var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/SUPDrvTracer.o: warning:
objtool:
.text+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/virtualbox/6.1.14/build/vboxdrv/SUPDrvTracer.o: warning:
objtool:
supdrvTracerProbeFireStub() is missing an ELF size annotation
make[2]: ***
[/usr/src/linux-headers-5.9.0-1-common/scripts/Makefile.build:505:
/var/lib/dkms/virtualbox/6.1.14/build/vboxdrv] Error 2
make[1]: *** [/usr/src/linux-headers-5.9.0-1-common/Makefile:1796:
/var/lib/dkms/virtualbox/6.1.14/build] Error 2
make: *** [/usr/src/linux-headers-5.9.0-1-common/Makefile:185: __sub-make]
Error 2
make: Leaving directory '/usr/src/linux-headers-5.9.0-1-amd64'



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

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

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.8.3-4

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  6.1.14-dfsg-4

virtualbox-dkms suggests no packages.

-- no debconf information

-- 
Jonás Andradas

GPG Fingerprint:  678F 7BD0 83C3 28CE 9E8F
   3F7F 4D87 9996 E0C6 9372
Keyservers:  pgp.mit.edu | pgp.rediris.es


Bug#968386: lynkeos.app: No text is shown in the UI

2020-08-14 Thread Jonas Andradas
Package: lynkeos.app
Version: 3.3+dfsg1-2+b1
Severity: important

Dear Maintainer,

when launching the Lynkeos binary, no text is shown in the application UI:
there are no labels, no text in the menus or in the windows themselves.

Two screenshots are provided and the output with errors shown in the console
when launched from the command-line:

~~~
user@debian$ Lynkeos
2020-08-14 10:26:20.382 Lynkeos[21432:21432] File NSData.m: 287. In
readContentsOfFile Open ((null)) attempt failed - bad path
2020-08-14 10:26:20.384 Lynkeos[21432:21432] Could not convert cursor bitmap
data
2020-08-14 10:26:20.561 Lynkeos[21432:21432] Setting unknown encoding 1
jonas@darkstar:~/projects/MandA/pfSense-udp-1195-JonasA$ Lynkeos
2020-08-14 10:26:54.503 Lynkeos[21488:21488] File NSData.m: 287. In
readContentsOfFile Open ((null)) attempt failed - bad path
2020-08-14 10:26:54.503 Lynkeos[21488:21488] Could not convert cursor bitmap
data
2020-08-14 10:26:54.605 Lynkeos[21488:21488] Setting unknown encoding 1
2020-08-14 10:29:28.048 Lynkeos[21488:21488] WARNING: -drawGState called with a
NULL target context ((null)) or source context (0x55590331c1b0)
2020-08-14 10:29:28.156 Lynkeos[21488:21488] WARNING: -drawGState called with a
NULL target context ((null)) or source context (0x55590331c1b0)
2020-08-14 10:29:28.791 Lynkeos[21488:21488] WARNING: -drawGState called with a
NULL target context ((null)) or source context (0x55590331c1b0)
2020-08-14 10:29:28.918 Lynkeos[21488:21488] WARNING: -drawGState called with a
NULL target context ((null)) or source context (0x55590331c1b0)
~~~




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

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

Versions of packages lynkeos.app depends on:
ii  dcraw  9.28-2
ii  gnustep-back0.28   0.28.0-2
ii  gnustep-base-runtime   1.27.0-3
ii  gnustep-gui-runtime0.28.0-3
ii  libatlas3-base [liblapack.so.3]3.10.3-10
ii  libavcodec58   7:4.3.1-1
ii  libavformat58  7:4.3.1-1
ii  libavutil567:4.3.1-1
ii  libc6  2.31-3
ii  libcfitsio83.470-4
ii  libfftw3-single3   3.3.8-2
ii  libgcc-s1  10.2.0-5
ii  libgnustep-base1.271.27.0-3
ii  libgnustep-gui0.28 0.28.0-3
ii  liblapack3 [liblapack.so.3]3.9.0-3
ii  libobjc4   10.2.0-5
ii  libopenblas0-pthread [liblapack.so.3]  0.3.10+ds-3
ii  libswscale57:4.3.1-1
ii  libtiff5   4.1.0+git191117-2
ii  lynkeos.app-common 3.3+dfsg1-2

lynkeos.app recommends no packages.

lynkeos.app suggests no packages.

-- no debconf information


Bug#965967: dmarc-cat: does not show IP addresses or reverse lookup

2020-07-21 Thread Jonas Andradas
Package: dmarc-cat
Version: 0.12.0-1
Severity: important

Dear Maintainer,

when using dmarc-cat to parse DMARC rua reports, IP addresses are not shown,
nor their reverse look-up.  This seems a bug in upstream version 0.12, which is
already corrected in version 0.14.

Since the main goal of the RUA email and dmarc-cat is to identify the servers
that are sending mail and their DKIM/SPF result, this bug just allows checking
for "fail" output, which users would then have to review in the XML, as the IP
address or hostname is not shown in dmarc-cat output.

As an example, the output of the packaged version of dmarc-cat shows:


dmarc-cat 0.12.0,parallel/j8 by Ollivier Robert

Reporting by: google.com — noreply-dmarc-supp...@google.com
From 2020-07-20 02:00:00 +0200 CEST to 2020-07-21 01:59:59 +0200 CEST

Domain: alternativaslibres.es
Policy: p=none; dkim=s; spf=s

Reports(8):
IPCount   From   RFrom
RDKIM   RSPF
  36  alternativaslibres.es alternativaslibres.es
passpass
  32  alternativaslibres.es alternativaslibres.es
passpass
11.mo35.mail-out.ovh.net. 1   alternativaslibres.es alternativaslibres.es
pass
  1   alternativaslibres.es alternativaslibres.es
pass
  1   alternativaslibres.es alternativaslibres.es
passfail
  1   alternativaslibres.es alternativaslibres.es
pass
  1   alternativaslibres.es alternativaslibres.es
pass
  1   alternativaslibres.es alternativaslibres.es
pass



Upstream version 0.14 seems to have this corrected, as the output of running it
against the same file shows:


Reports(8):
IP   Count   From
RFrom  RDKIM   RSPF
43.mo35.mail-out.ovh.net.36
alternativaslibres.es alternativaslibres.es   passpass
pal.alternativaslibres.es.   32
alternativaslibres.es alternativaslibres.es   passpass
15.mo35.mail-out.ovh.net.1
alternativaslibres.es alternativaslibres.es   pass
6.mo14.mail-out.ovh.net. 1
alternativaslibres.es alternativaslibres.es   pass
pal.alternativaslibres.es.   1
alternativaslibres.es alternativaslibres.es   passfail
11.mo14.mail-out.ovh.net.1
alternativaslibres.es alternativaslibres.es   pass
11.mo35.mail-out.ovh.net.1
alternativaslibres.es alternativaslibres.es   pass
mail-dm6nam12lp2170.outbound.protection.outlook.com. 1
alternativaslibres.es alternativaslibres.es   pass





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

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

Versions of packages dmarc-cat depends on:
ii  libc6   2.31-1
ii  libgpgme11  1.13.1-9

dmarc-cat recommends no packages.

dmarc-cat suggests no packages.

-- no debconf information


Bug#958296: openvpn 2.4.9 seems to fail loading/reading client certificates

2020-04-21 Thread Jonas Andradas
Hello Bernhard,

On Tue, Apr 21, 2020 at 5:06 PM Bernhard Schmidt  wrote:

> Hi Jonas,
>
> > Anyway, if you want me to try a patched test-build, I would be happy to
> > (and preferred, as I can do that quickly, but would take a bit more time
> > to prepare a build environment to build the package myself).
>
> A patched build can be retrieved here:
>
>
> https://people.debian.org/~berni/openvpn/openvpn_2.4.9-2~1.gbp727e40_amd64.deb
>
>
I have downloaded and tested the patch, with the following results
regarding the value of "MinProtocol" in /etc/ssl/openssl.cnf:

  - MinProtocol = TLSv1 -- WORKS
  - MinProtocol = TLSv1.0 -- WORKS (was not working before the patch)
  - MinProtocol = TLSv1.2 -- WORKS (Debian default)


> Bernhard
>

Best Regards,
Jonas.


Bug#958296: openvpn 2.4.9 seems to fail loading/reading client certificates

2020-04-21 Thread Jonas Andradas
Hi,


On Tue, Apr 21, 2020 at 2:27 PM Bernhard Schmidt 
wrote:

> Am 21.04.20 um 12:18 schrieb Arne Schwabe:
>
> Hi,
>
> >>> I am attaching my /etc/ssl/openssl.cnf (if for some reason it fails, I
> will
> >>> paste the contents instead).  As far as I know, this is the default
> >>> /etc/ssl/ openssl.cnf file that comes with Debian, except the
> "MinProtocol"
> >>> parameter, which I had to change for one specific VPN to work (it was
> using
> >>> TLSv1.0 instead of TLSv1.2).
> >>
> >> It seems that the culprit is the (non-default) setting MinProtocol =
> TLSv1.0,
> >> which I had to modify to be able to use a specific VPN server.
> Changing the
> >> value to "MinProtocol = TLSv1.2" does not produce the error anymore.
> >
> > Sidenote. That MinProtocol = TLSv1.0 is wrong. It needs to be
> > MinProtocol = TLSv1 for obvious reasons :P
> >
> > Anyway here is a patch that fixes the problem of not loading
> > certificates: https://patchwork.openvpn.net/patch/1095/
>
> Cool, thanks.
>
> Jonas, can you test that "MinProtocol = TLSv1" works? Do you need a
> test-build for 2.4.9 with that patch applied?
>
>
I tried with my OpenVPN installation, with no patch, but using the correct
value "TLSv1" instead of TLSv1.0 (which OpenSSL and OpenVPN previously
accepted as valid, probably being lax about the syntax), and I cannot
reproduce the issue anymore.  This is, I can connect with my certificate
even if using "MinProtocol = TLSv1" instead of "MinProtocol = TLSv1.2".

Anyway, if you want me to try a patched test-build, I would be happy to
(and preferred, as I can do that quickly, but would take a bit more time to
prepare a build environment to build the package myself).


> Bernhard
>

Thanks,
Jonas.


Bug#958296: openvpn 2.4.9 seems to fail loading/reading client certificates

2020-04-20 Thread Jonas Andradas
On Monday, 20 April 2020 16:28:03 CEST  wrote:
> Hello Arne,
> 
> On Mon, 20 Apr 2020 15:01:27 +0200 Arne Schwabe  wrote:
> > Hey,
> > 
> > OpenVPN developer here.
> > 
> > From this output in the original bug report:
> > > Mon Apr 20 11:02:29 2020 OpenSSL: error:14187180:SSL
> > 
> > routines:ssl_do_config:bad value
> > 
> > > Mon Apr 20 11:02:29 2020 OpenSSL: error:0909006C:PEM
> > 
> > routines:get_name:no start line
> > 
> > it looks like there is still an error on the OpenSSL error stack that we
> > have no cleared/etc. And since our certificate loading got a little bit
> > stricter in OpenVPN 2.4.9, we now stumble upon this.
> > 
> > The ssl_do_config error sounds like there is something in the (system
> > wide)  OpenSSL configuration that upsets OpenSSL and triggers the error.
> > Could you attach your /etc/ssl/openssl.cnf so I can try reproduce that
> > bug?
> 
> I am attaching my /etc/ssl/openssl.cnf (if for some reason it fails, I will
> paste the contents instead).  As far as I know, this is the default
> /etc/ssl/ openssl.cnf file that comes with Debian, except the "MinProtocol"
> parameter, which I had to change for one specific VPN to work (it was using
> TLSv1.0 instead of TLSv1.2).

It seems that the culprit is the (non-default) setting MinProtocol = TLSv1.0, 
which I had to modify to be able to use a specific VPN server.  Changing the 
value to "MinProtocol = TLSv1.2" does not produce the error anymore.

> 
> > Arne
> 
> Best Regards,
> Jonas.

Jonas.



Bug#958296: openvpn 2.4.9 seems to fail loading/reading client certificates

2020-04-20 Thread Jonas Andradas
Hello again,

On Mon, Apr 20, 2020 at 12:01 PM  wrote:

> Hello Bernhard,
>
> On Mon, 20 Apr 2020 11:23:17 +0200 Bernhard Schmidt 
> wrote:
> > Am 20.04.20 um 11:12 schrieb Jonas Andradas:
> >
> > Dear Jonas,
> >
> > > Apparently, openvpn 2.4.9-1 has an issue when reading
> client-certificates
> used
> > > to authenticate to the remote server.
> >
> > Thanks. Is this a regression compared to 2.4.7? Or what is the last
> > version where this worked?
> >
>
> I am not sure what openvpn version was there in see last week, whether it
> was
> 2.4.7 or 2.4.9 (the current package is 2.4.9-1).  However, I see that
> openvpn
> has been updated over the weekend, since my openvpn files/binaries have
> been
> modified on April 19th.
>

Sorry, the spell corrector played me here: I meant "I am not sure what
openvpn version
was there in [Debian] SID last week (...)


> Is there a place I could check which package version was in the
> repositories
> at a given date, to see the exact version I had last week?
>
> > There are a couple of SSL-related changes between 2.4.7 and 2.4.9, but
> > nothing immediately obvious.
> >
> > Is the client certificate still valid?
>
> Yes, the client certificate is still valid, and if I use older OpenVPN
> versions
> (such as 2.4.3), I can still connect successfully.
>
> >
> > Bernhard
> >
> >
>
> Thank you very much,
> Best Regards,
> Jonas.
>
>
>

-- 
Jonás Andradas

GPG Fingerprint:  678F 7BD0 83C3 28CE 9E8F
   3F7F 4D87 9996 E0C6 9372
Keyservers:  pgp.mit.edu | pgp.rediris.es


Bug#958296: openvpn 2.4.9 seems to fail loading/reading client certificates

2020-04-20 Thread Jonas Andradas
Package: openvpn
Version: 2.4.9-1
Severity: important

Dear Maintainer,

Apparently, openvpn 2.4.9-1 has an issue when reading client-certificates used
to authenticate to the remote server.

When a client certificate is configured in the .ovpn file and a connection is
attempted, the following error output is provided:

Mon Apr 20 11:02:28 2020 OpenVPN 2.4.9 x86_64-pc-linux-gnu [SSL (OpenSSL)]
[LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 19 2020
Mon Apr 20 11:02:28 2020 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO
2.10
Enter Auth Username: 
Enter Auth Password: 
Mon Apr 20 11:02:29 2020 OpenSSL: error:14187180:SSL routines:ssl_do_config:bad
value
Mon Apr 20 11:02:29 2020 OpenSSL: error:0909006C:PEM routines:get_name:no start
line
Mon Apr 20 11:02:29 2020 Error reading extra certificate
Mon Apr 20 11:02:29 2020 Exiting due to fatal error


I tried different configuration files, newer and older, and all those that use
a client-certificate show the same behavior. I have checked and while some of
the older certificates are signed with sha1WithRSAEncryption, the current ones
use sha256WithRSAEncryption, so that should not be the culprit.

OpenSSL has no trouble reading the certificates with commands such as "openssl
x509 -in client.crt -noout -text"

Below is the output of strace when running openvpn with one .ovpn profiles,
which shows that the errors exist after trying to read the certificate file:

# strace openvpn vpn_connection.ovpn
execve("/usr/sbin/openvpn", ["openvpn", "vpn_connection.ovpn"], 0x7ffd8cd42db8
/* 97 vars */) = 0
brk(NULL)   = 0x5559a6334000
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=272683, ...}) = 0
mmap(NULL, 272683, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f9838a03000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/liblzo2.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\2201\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=145320, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f9838a01000
mmap(NULL, 147472, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f98389dc000
mprotect(0x7f98389df000, 131072, PROT_NONE) = 0
mmap(0x7f98389df000, 114688, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f98389df000
mmap(0x7f98389fb000, 12288, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x1f000) = 0x7f98389fb000
mmap(0x7f98389ff000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x22000) = 0x7f98389ff000
close(3)= 0
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/liblz4.so.1", O_RDONLY|O_CLOEXEC) =
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3402\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=133464, ...}) = 0
mmap(NULL, 135544, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f98389ba000
mmap(0x7f98389bd000, 106496, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f98389bd000
mmap(0x7f98389d7000, 12288, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x1d000) = 0x7f98389d7000
mmap(0x7f98389da000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0x7f98389da000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) =
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`|\0\0\0\0\0\0"..., 832)
= 832
fstat(3, {st_mode=S_IFREG|0755, st_size=146912, ...}) = 0
mmap(NULL, 132256, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f9838999000
mmap(0x7f98389a, 61440, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x7000) = 0x7f98389a
mmap(0x7f98389af000, 20480, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x16000) = 0x7f98389af000
mmap(0x7f98389b4000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a000) = 0x7f98389b4000
mmap(0x7f98389b6000, 13472, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f98389b6000
close(3)= 0
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libpkcs11-helper.so.1",
O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\H\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=121944, ...}) = 0
mmap(NULL, 124240, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f983897a000
mprotect(0x7f983897e000, 102400, PROT_NONE) = 0
mmap(0x7f983897e000, 61440, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4000) = 0x7f983897e000
mmap(0x7f983898d000, 36864, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3,
0x13000) = 0x7f983898d000
mmap(0x7f9838997000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c000) = 0x7f9838997000
close(3)  

Bug#955041: virtualbox: .ovf import fails due to incorrect calculation of SHA256

2020-03-27 Thread Jonas Andradas
Package: virtualbox
Version: 6.1.4-dfsg-2
Severity: normal

Dear Maintainer,

When importing a virtual machine (VM) from .ovf file that is accompanied by a
.mf file that specifies file integrity hashes using SHA256, the importer (both
fom the GUI or using VBoxManage) check the integrity of the files as part of
the import process.

Specifically, the file I am seeing the issues is the hard drive of the VM,
provided in VMDK format. The importer exits with an error indicating that the
digest of the VMDK file does not match the one in the .mf file, but using tools
such as sha256 sum I see that the hash does match (see output below).

$ VBoxManage import ~/vms/testvm0146.ovf

(...snip...)

0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Digest mismatch (VERR_NOT_EQUAL): Attribute 'SHA256' on
'testvm0146-0.vmdk' does not match
('03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9' vs.
'19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d')
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component
ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at
line 1118 of file VBoxManageAppliance.cpp


However, sha256sum gives the following output:

$ sha256sum ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk

Additionally, sha246deep also provides the same hash:

$ sha256deep ~/vms/testvm0146-0.vmdk
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
/home/me/vms/testvm0146-0.vmdk


The contents of the testvm0146.mf file are:

$ cat ~/vms/testvm0146.mf
SHA256(testvm0146-0.vmdk)=
03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9
SHA256(testvm0146-1.nvram)=
4615577454b8ea7c464f4aee064936e48db52ddb08f23e9ea74ade5e12fce8ce
SHA256(testvm0146.ovf)=
7cbaf2f6dc9ada576ae99ba0f5ef001432650581ad401d4312f297d2737ced49


As can be seen, the output of sha256sum and the .mf file match
(03d3ec55ec53133041967054525ca1fbf8714208f9be242219e85a24f0745de9), but for
some reason virtualbox determines the SHA256 hash to be
19ffb23de176d73835fe3528d5b4e5a5aac3c15b5e83fc7732f888c6c2d47f9d, and thus the
comparison fails.

I would expect the hashes to match those obtained with other tools, and thus
the VM to be properly imported.

(I think this issue is different than 763447, so it has been raised separetly)

Thank you,
Best Regards,
Jonas.



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

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

Versions of packages virtualbox depends on:
ii  adduser   3.118
ii  iproute2  5.5.0-1
ii  libc6 2.30-4
ii  libcurl3-gnutls   7.68.0-1
ii  libdevmapper1.02.12:1.02.167-1+b1
ii  libgcc-s1 10-20200324-1
ii  libgl11.3.1-1
ii  libgsoap-2.8.91   2.8.91-2
ii  libopus0  1.3-1+b1
ii  libpng16-16   1.6.37-2
ii  libpython3.8  3.8.2-1
ii  libsdl1.2debian   1.2.15+dfsg2-5
ii  libssl1.1 1.1.1e-1
ii  libstdc++610-20200324-1
ii  libvncserver1 0.9.12+dfsg-8
ii  libvpx6   1.8.2-1
ii  libx11-6  2:1.6.9-2
ii  libxcursor1   1:1.2.0-2
ii  libxml2   2.9.10+dfsg-4
ii  libxt61:1.1.5-1+b3
ii  procps2:3.3.16-4
ii  python3   3.8.2-2
ii  python3.8 3.8.2-1
ii  virtualbox-dkms [virtualbox-modules]  6.1.4-dfsg-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages virtualbox recommends:
ii  libqt5core5a5.12.5+dfsg-9
ii  libqt5gui5  5.12.5+dfsg-9
ii  libqt5opengl5   5.12.5+dfsg-9
ii  libqt5widgets5  5.12.5+dfsg-9
ii  libxcb1 1.13.1-5
ii  libxext62:1.3.3-1+b2
ii  libxmu6 2:1.1.2-2+b3
ii  virtualbox-qt   6.1.4-dfsg-2

Versions of packages virtualbox suggests:
ii  vde22.3.2+r586-2.2+b1
ii  virtualbox-guest-additions-iso  6.1.5-136327-1

-- no debconf information



Bug#952733: dnsrecon fails in Google Search enumeration due to incorrect urllib functions being used

2020-03-03 Thread Jonas Andradas
My best guess is there was an update to one of the underlying libraries I
did not notice (note that this was on Sid, so frequent updates).

Other option would be that the error only happens if the functionality
fails (e.g. Google blocking the request), so the full error trace is shown,
meaning that the urllib error is not fatal, and is only shown when the
functionality actually fails.

I replied to the bug because trying to reproduce it some time after raising
it (and retrying now), I get the expected behavior and not the error...

On Tue, 3 Mar 2020, 09:32 Raphael Hertzog,  wrote:

> On Fri, 28 Feb 2020, Jonas Andradas wrote:
> > new updates performed along the day fixed the issue... sorry for
> reporting it
> > too soon!
>
> What updates? It seems weird that this issue would fix itself.
>
> Cheers,
> --
>   ⢀⣴⠾⠻⢶⣦⠀   Raphaël Hertzog 
>   ⣾⠁⢠⠒⠀⣿⡁
>   ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/
>   ⠈⠳⣄   Debian Long Term Support: https://deb.li/LTS
>


Bug#952733: dnsrecon fails in Google Search enumeration due to incorrect urllib functions being used

2020-02-28 Thread Jonas Andradas
Package: dnsrecon
Followup-For: Bug #952733

Dear Maintainer,

new updates performed along the day fixed the issue... sorry for reporting it
too soon!



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

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

Versions of packages dnsrecon depends on:
ii  python33.7.5-3
ii  python3-dnspython  1.16.0-1
ii  python3-lxml   4.5.0-1
ii  python3-netaddr0.7.19-3

dnsrecon recommends no packages.

dnsrecon suggests no packages.

-- no debconf information



Bug#952733: dnsrecon fails in Google Search enumeration due to incorrect urllib functions being used

2020-02-28 Thread Jonas Andradas
Package: dnsrecon
Version: 0.9.1-3
Severity: normal

Dear Maintainer,

When using dnsrecon and requesting it to use the Google search (-t goo), it
fails due to an invocation to "urllib.urlopen(url)", which fails with an error
informing that there is no urlopen attribute in the module urllib, as can be
seen in the following example run.  I would like to point out that the same
command did work on February 26th 2020, and stopped working on February 28th
2020, after some apt upgrade (however, I cannot provide which packages were
updated).

$ dnsrecon -d debian.org -t goo
[*] Performing Google Search Enumeration against debian.org
Traceback (most recent call last):
  File "/usr/share/dnsrecon/lib/gooenum.py", line 54, in scrape_google
sock = urllib.urlopen(url)
AttributeError: module 'urllib' has no attribute 'urlopen'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "./dnsrecon.py", line 1788, in 
main()
  File "./dnsrecon.py", line 1672, in main
goo_enum_records = se_result_process(res, scrape_google(domain))
  File "/usr/share/dnsrecon/lib/gooenum.py", line 58, in scrape_google
sock = urllib.request.urlopen(request)
  File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
return opener.open(url, data, timeout)
  File "/usr/lib/python3.7/urllib/request.py", line 531, in open
response = meth(req, response)
  File "/usr/lib/python3.7/urllib/request.py", line 641, in http_response
'http', request, response, code, msg, hdrs)
  File "/usr/lib/python3.7/urllib/request.py", line 563, in error
result = self._call_chain(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 755, in http_error_302
return self.parent.open(new, timeout=req.timeout)
  File "/usr/lib/python3.7/urllib/request.py", line 531, in open
response = meth(req, response)
  File "/usr/lib/python3.7/urllib/request.py", line 641, in http_response
'http', request, response, code, msg, hdrs)
  File "/usr/lib/python3.7/urllib/request.py", line 569, in error
return self._call_chain(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
result = func(*args)
  File "/usr/lib/python3.7/urllib/request.py", line 649, in http_error_default
raise HTTPError(req.full_url, code, msg, hdrs, fp)
urllib.error.HTTPError: HTTP Error 429: Too Many Requests



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

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

Versions of packages dnsrecon depends on:
ii  python33.7.5-3
ii  python3-dnspython  1.16.0-1
ii  python3-lxml   4.5.0-1
ii  python3-netaddr0.7.19-3

dnsrecon recommends no packages.

dnsrecon suggests no packages.

-- no debconf information



Bug#944756: mcomix: One of mcomix files conflicts with a file in the comix package

2019-11-14 Thread Jonas Andradas
Package: mcomix
Version: 1.2.1-1.1
Severity: important

Dear Maintainer,

The update to the mcomix version 1.2.1mcomix3+git20190616-1 fails, due to the
file /usr/share/man/man1/comicthumb.1.gz conflicting with the same file in the
"comix" package in its version 4.0.4-4.1.

An excerpt of the dpkg error is shown included below:

Preparing to unpack .../mcomix_1.2.1mcomix3+git20190616-1_all.deb ...
Unpacking mcomix (1.2.1mcomix3+git20190616-1) over (1.2.1-1.1) ...
dpkg: error processing archive
/var/cache/apt/archives/mcomix_1.2.1mcomix3+git20190616-1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/comicthumb.1.gz', which is also in
package comix 4.0.4-4.1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/mcomix_1.2.1mcomix3+git20190616-1_all.deb





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

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

Versions of packages mcomix depends on:
ii  python2.7.17-1
ii  python-gtk2   2.24.0-6
ii  python-pil6.2.1-2
ii  python-pkg-resources  41.4.0-1

mcomix recommends no packages.

Versions of packages mcomix suggests:
pn  unrar  

-- no debconf information



Bug#941201: libusbmuxd-tools: Binary file /usr/bin/icat conflicts with another binary in Sleuthkit package

2019-09-26 Thread Jonas Andradas
Package: libusbmuxd-tools
Version: 1.1.0~git20190924.b097ea3-1
Severity: normal

Dear Maintainer,

The file /usr/bin/icat from the libusbmuxd-tools package conflicts with the
binary file /usr/bin/icat also present in package sleuthkit.

$ apt-file show libusbmuxd-tools | grep icat
libusbmuxd-tools: /usr/bin/icat

$ apt-file show sleuthkit | grep icat
sleuthkit: /usr/bin/icat

(or)

$ dpkg -L sleuthkit | grep icat
/usr/bin/icat





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

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

Versions of packages libusbmuxd-tools depends on:
ii  libc62.29-2
ii  libusbmuxd4  1.1.0~git20190924.b097ea3-1

libusbmuxd-tools recommends no packages.

libusbmuxd-tools suggests no packages.



Bug#941200: [libusbmuxd-tools] Binary file /usr/bin/icat conflicts with Sleuthkit binary

2019-09-26 Thread Jonas Andradas
Package: libusbmuxd-tools
Version: 1.1.0~git20190924.b097ea3-1
Severity: normal

--- Please enter the report below this line. ---


--- System information. ---
Architecture: 
Kernel:   Linux 5.2.0-2-amd64

Debian Release: bullseye/sid
  500 unstablehttpredir.debian.org 
  500 unstablefrougon.net 
  500 testing httpredir.debian.org 
  500 stable-buster   download.mono-project.com 
  500 stable  www.scootersoftware.com 
  500 stable  security.debian.org 
  500 stable  repository.spotify.com 
  500 stable  packages.microsoft.com 
  500 stable  packages.cisofy.com 
  500 stable  linux.teamviewer.com 
  500 stable  httpredir.debian.org 
  500 stable  dl.google.com 
  500 cloud-sdk   packages.cloud.google.com 
  500 buster  packages.microsoft.com 
  500 apt/stable  download.sublimetext.com 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.



Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)

2018-07-03 Thread Jonas Andradas
Hello,

as per Gianfranco's request [0], I have opened a bug in the upstream
VirtualBox bug tracker [1]

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23902897#45
[1] https://www.virtualbox.org/ticket/17851

Best Regards,

-- 
Jonás Andradas

GPG Fingerprint:  678F 7BD0 83C3 28CE 9E8F
   3F7F 4D87 9996 E0C6 9372
Keyservers:  pgp.mit.edu | pgp.rediris.es


Bug#889036: kazam: When selecting an area, the screen is greyed-out

2018-02-01 Thread Jonas Andradas
Package: kazam
Version: 1.4.5-2
Severity: important

Dear Maintainer,

When choosing to select an area to capture, all the screen (at least in the
monitor in which the mouse cursor is) is greyed out, blocking all underlying
windows.  I need to select a rectangle within the greyed-out area, but is hard
to do this correctly when what I want to record is not visible anymore.

If I run kazam from a console, apart from warnings regarding several deprecated
GTK calls, I get the following, which seems relevant:

WARNING Window Select - Compositing window manager not found, expect the
unexpected.
WARNING Window Select - Compositing window manager not found, expect the
unexpected.

My kazam version is 1.4.5-2

This issue seems the same as:

https://bugs.launchpad.net/kazam/+bug/1263419




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

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

Versions of packages kazam depends on:
ii  gir1.2-gst-plugins-base-1.0  1.12.4-1
ii  gir1.2-gstreamer-1.0 1.12.4-1
ii  gir1.2-keybinder-3.0 0.3.2-1
ii  gir1.2-wnck-3.0  3.24.1-2
ii  gnome-session-canberra   0.30-6
ii  gstreamer1.0-plugins-base1.12.4-1
ii  gstreamer1.0-plugins-good1.12.4-1
ii  gstreamer1.0-plugins-ugly1.12.4-1+b1
ii  gstreamer1.0-pulseaudio  1.12.4-1
ii  python3  3.6.4-1
ii  python3-cairo1.15.4-2
ii  python3-dbus 1.2.6-1
ii  python3-gi   3.26.1-2
ii  python3-gi-cairo 3.26.1-2
ii  python3-xdg  0.25-4

Versions of packages kazam recommends:
ii  gstreamer1.0-libav  1.12.4-1

kazam suggests no packages.

-- no debconf information



Bug#857926: [fglrx-modules-dkms]

2017-03-16 Thread Jonas Andradas
Package: fglrx-modules-dkms
Version: 1:15.12-2~bpo8+3
Severity: grave

--- Please enter the report below this line. ---

The DKMS is unable to build the module for kernel 4.9.13, which is the latest 
4.9 kernel in Debian Backports (4.9.13-1~bpo8+1), found in packages:

* linux-image-4.9.0-0.bpo.2-amd64
* linux-headers-4.9.0-0.bpo.2-amd64

The output of dkms is the following: 

# dkms build -m fglrx -v 15.12 -k 4.9.0-0.bpo.2-amd64 

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j8 KERNELRELEASE=4.9.0-0.bpo.2-amd64 -C /lib/modules/4.9.0-0.bpo.2-
amd64/build M=/var/lib/dkms/fglrx/15.12/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.9.0-0.bpo.2-amd64 
(x86_64)
Consult /var/lib/dkms/fglrx/15.12/build/make.log for more information.


The output of make.log is included as an attachment.

The package is usable with kernel 4.8.15-2~bpo8+2, for which the DKMS module 
builds correctly.


--- System information. ---
Architecture: amd64
Kernel:   Linux 4.8.0-0.bpo.2-amd64

Debian Release: 8.7
  500 stable-updates  ftp.de.debian.org 
  500 stable  security.debian.org 
  500 stable  ftp.de.debian.org 
  100 jessie-backports ftp.de.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package Status (Version) | Installed
-+-===
xserver-xorg | 1:7.7+7
xserver-xorg-core| 2:1.16.4-1
linux-headers| 
libdrm-radeon1   | 
xserver-xorg-video-ati   | 
xserver-xorg-video-radeon| 
ia32-libs| 


Package's Recommends field is empty.

Package's Suggests field is empty.



-8<---8<---8<---8<---8<---8<---8<---8<---8<--
Please attach the file:
  /tmp/reportbug-ng-fglrx-modules-dkms-vsJz2W.txt
to the mail. I'd do it myself if the output wasn't too long to handle.

  Thank you!
->8--->8--->8--->8--->8--->8--->8--->8--->8--DKMS make.log for fglrx-15.12 for kernel 4.9.0-0.bpo.2-amd64 (x86_64)
Thu Mar 16 12:24:12 CET 2017
make: Entering directory '/usr/src/linux-headers-4.9.0-0.bpo.2-amd64'
  LD  /var/lib/dkms/fglrx/15.12/build/built-in.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/firegl_public.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_acpi.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_agp.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_debug.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_ioctl.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_pci.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_io.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_str.o
In file included from /var/lib/dkms/fglrx/15.12/build/kcl_debug.c:38:0:
/var/lib/dkms/fglrx/15.12/build/firegl_public.h:654:21: warning: extra tokens at end of #ifndef directive
 #ifndef boot_cpu_has(X86_FEATURE_PGE)
 ^
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_iommu.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_wait.o
/var/lib/dkms/fglrx/15.12/build/kcl_acpi.c:839:20: warning: ‘KCL_ACPI_Slot_No_Hotplug’ defined but not used [-Wunused-function]
 static acpi_status KCL_ACPI_Slot_No_Hotplug(KCL_ACPI_DevHandle handle, u32 lvl, void *data, void **rv)
^
In file included from /var/lib/dkms/fglrx/15.12/build/kcl_iommu.c:48:0:
/var/lib/dkms/fglrx/15.12/build/firegl_public.h:654:21: warning: extra tokens at end of #ifndef directive
 #ifndef boot_cpu_has(X86_FEATURE_PGE)
 ^
In file included from /var/lib/dkms/fglrx/15.12/build/firegl_public.c:207:0:
/var/lib/dkms/fglrx/15.12/build/firegl_public.h:654:21: warning: extra tokens at end of #ifndef directive
 #ifndef boot_cpu_has(X86_FEATURE_PGE)
 ^
/var/lib/dkms/fglrx/15.12/build/firegl_public.c: In function ‘KCL_LockUserPages’:
/var/lib/dkms/fglrx/15.12/build/firegl_public.c:3232:78: warning: passing argument 7 of ‘get_user_pages_remote’ from incompatible pointer type
 ret = get_user_pages_remote(current, current->mm, vaddr, page_cnt, 1, 0, (struct page **)page_list, NULL);
  ^
In file included from /usr/src/linux-headers-4.9.0-0.bpo.2-common/include/linux/scatterlist.h:7:0,
 from /usr/src/linux-headers-4.9.0-0.bpo.2-common/include/linux/dmapool.h:14,
 from /usr/src/linux-headers-4.9.0-0.bpo.2-common/include/linux/pci.h:1269,
 from /var/lib/dkms/fglrx/15.12/build/firegl_public.c:117:
/usr/src/linux-headers-4.9.0-0.bpo.2-common/include/linux/mm.h:1298:6: note: expected ‘struct vm_area_struct **’ but argument is of type ‘struct page **’
 long get_user_pages_remote(struct task_struct *tsk, struct mm_struct *mm,
  ^
/var/lib/dkms/fglrx/15.12/build/firegl_public.c:3232:11: error: too many arguments to function 

Bug#835392: fglrx-modules-dkms: Patch to compile in 4.6 kernel breaks compilation in 4.5 kernels

2016-08-25 Thread Jonas Andradas
Package: fglrx-modules-dkms
Version: 1:15.12-2~bpo8+2
Severity: important

Dear Maintainer,

The latest patch applied to 1:15.12-2~bpo8+1 (leading to the new package
1:15.12-2~bpo8+2), which introduced support to compile the fglrx module fro 4.6
kernels, seems to have broken compilation in 4.5 ones, as can be seen in the
log below:

DKMS make.log for fglrx-15.12 for kernel 4.5.0-0.bpo.2-amd64 (x86_64)
Thu Aug 25 11:24:57 CEST 2016
make: Entering directory '/usr/src/linux-headers-4.5.0-0.bpo.2-amd64'
  LD  /var/lib/dkms/fglrx/15.12/build/built-in.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/firegl_public.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_acpi.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_agp.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_debug.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_ioctl.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_io.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_pci.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_str.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_iommu.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl.o
  CC [M]  /var/lib/dkms/fglrx/15.12/build/kcl_wait.o
/var/lib/dkms/fglrx/15.12/build/kcl_acpi.c:839:20: warning:
‘KCL_ACPI_Slot_No_Hotplug’ defined but not used [-Wunused-function]
 static acpi_status KCL_ACPI_Slot_No_Hotplug(KCL_ACPI_DevHandle handle, u32
lvl, void *data, void **rv)
^
/var/lib/dkms/fglrx/15.12/build/firegl_public.c: In function
‘KCL_LockUserPages’:
/var/lib/dkms/fglrx/15.12/build/firegl_public.c:3231:5: error: implicit
declaration of function ‘get_user_pages_remote’ [-Werror=implicit-function-
declaration]
 ret = get_user_pages_remote(current, current->mm, vaddr, page_cnt, 1, 0,
(struct page **)page_list, NULL);
 ^
/var/lib/dkms/fglrx/15.12/build/firegl_public.c: At top level:
/var/lib/dkms/fglrx/15.12/build/firegl_public.c:6465:12: warning:
‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
 static int KCL_fpu_save_init(struct task_struct *tsk)
^
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.5.0-0.bpo.2-common/scripts/Makefile.build:263: recipe
for target '/var/lib/dkms/fglrx/15.12/build/firegl_public.o' failed
make[3]: *** [/var/lib/dkms/fglrx/15.12/build/firegl_public.o] Error 1
/usr/src/linux-headers-4.5.0-0.bpo.2-common/Makefile:1408: recipe for target
'_module_/var/lib/dkms/fglrx/15.12/build' failed
make[2]: *** [_module_/var/lib/dkms/fglrx/15.12/build] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make: *** [all] Error 2
make: Leaving directory '/usr/src/linux-headers-4.5.0-0.bpo.2-amd64'



-- Package-specific info:
Full fglrx package list:
ii  fglrx-atieventsd   1:15.12-2~bpo8+2 amd64   
 events daemon for the non-free ATI/AMD RadeonHD display driver
ii  fglrx-control  1:15.12-2~bpo8+2 amd64   
 control panel for the non-free ATI/AMD RadeonHD display driver
ii  fglrx-driver   1:15.12-2~bpo8+2 amd64   
 non-free ATI/AMD RadeonHD display driver
ii  fglrx-modules-dkms 1:15.12-2~bpo8+2 amd64   
 dkms module source for the non-free ATI/AMD RadeonHD display driver
ii  glx-alternative-fglrx  0.7.3~bpo8+1 amd64   
 allows the selection of FGLRX as GLX provider
ii  libfglrx:amd64 1:15.12-2~bpo8+2 amd64   
 non-free ATI/AMD RadeonHD display driver (runtime libraries)
ii  libfglrx:i386  1:15.12-2~bpo8+2 i386
 non-free ATI/AMD RadeonHD display driver (runtime libraries)
ii  libfglrx-amdxvba1:amd641:15.12-2~bpo8+2 amd64   
 AMD XvBA (X-Video Bitstream Acceleration) backend for VA API
ii  libfglrx-amdxvba1:i386 1:15.12-2~bpo8+2 i386
 AMD XvBA (X-Video Bitstream Acceleration) backend for VA API
ii  libgl1-fglrx-glx:amd64 1:15.12-2~bpo8+2 amd64   
 proprietary libGL for the non-free ATI/AMD RadeonHD display driver
ii  libgl1-fglrx-glx:i386  1:15.12-2~bpo8+2 i386
 proprietary libGL for the non-free ATI/AMD RadeonHD display driver
ii  libgl1-fglrx-glx-i386  1:15.12-2~bpo8+2 i386
 ATI/AMD binary OpenGL 32-bit libraries

VGA-compatible devices on PCI bus:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Venus XT [Radeon HD 8870M / R9 M270X] [1002:6821] (prog-if 00 [VGA 
controller])
Subsystem: Dell FirePro M5100 [1028:15cc]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

Bug#811031: fglrx-driver: missing support for xserver 1.18

2016-03-15 Thread Jonas Andradas
On Fri, 15 Jan 2016 00:02:23 +0100 Andreas Beckmann

 wrote:

> Package: fglrx-driver

> Version: 1:15.9-4

> Severity: normal

> Tags: upstream

> Control: block 808735 with -1

>

> fglrx lacks support for xserver 1.18 (xorg-video-abi-20) in

> experimental.

>

>

> Andreas

>

>


Hi,


I am experiencing the same issue. When I try to install fglrx-driver, I get:


# apt-get install fglrx-driver

Reading package lists... Done

Building dependency tree

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:


The following packages have unmet dependencies:

fglrx-driver : Depends: xorg-video-abi-19 but it is not installable or

xorg-video-abi-18 but it is not installable or

xorg-video-abi-15 but it is not installable or

xorg-video-abi-14 but it is not installable or

xorg-video-abi-13 but it is not installable or

xorg-video-abi-12 but it is not installable or

xorg-video-abi-11 but it is not installable or

xorg-video-abi-10 but it is not installable or

xorg-video-abi-8 but it is not installable or

xorg-video-abi-6.0 but it is not installable

Recommends: libgl1-fglrx-glx-i386

E: Unable to correct problems, you have held broken packages.



The xserver-xorg-core package does not provide xorg-video-abi-19 or

xorg-video-abi-18 anymore:


$ apt-cache show xserver-xorg-core

Package: xserver-xorg-core

Source: xorg-server

Version: 2:1.18.2-1

Installed-Size: 5637

Maintainer: Debian X Strike Force 

Architecture: amd64

Replaces: xserver-xorg (<< 1:7.7+10~), xserver-xorg-video-

modesetting

Provides: xorg-input-abi-22, xorg-video-abi-20, xserver-xorg-video-

modesetting

Depends: (...)

-- 
Jonás Andradas