Bug#1069236: openssh-server: X over ssh fails with "cannot open display"

[allan]

I'm not using a hostname with ssh, I'm sshing directly to an IPv4 address.

*How* was it disabled?  net.ipv6.conf.all.disable_ipv6 = 1 in /etc/sysctl.conf

My point is that "AddressFamily any" should not fail to set $DISPLAY
if IPv6 is not available.

On Tue, Apr 23, 2024 at 5:38 AM Jonathan Dowland  wrote:
>
> On Thu, Apr 18, 2024 at 06:33:00AM -0500, allan wrote:
> > Resolved the issue by editing /etc/ssh/sshd_config and changing
> > #AddressFamily any
> > to
> > AddressFamily inet
>
> This is not a reasonable change to make to the default configuration,
> because it would mean that ssh did not work out of the box in IPv6
> environments.
>
> On Thu, Apr 18, 2024 at 07:53:52AM -0500, allan wrote:
> > More info - IPv6 is disabled on all four machines.  I think
> > "AddressFamily any" should have supported an IPv4 connection.
>
> *How* is it disabled? More information will be needed to figure out
> exactly what's gone on in your environment.
>
> I speculate that the hostnames you were trying to connect to were
> resolving as IPv6 addresses, and the connection failing because the
> hosts are rejecting IPv6 traffic. If that's right, the ultimate fix
> is to correct whatever name resolution is giving you the wrong
> addresses in your environment.
>
> If you are prepared to experiment, we might be able to drill down and
> check that. If so, can you
>
> 1) reverse the sshd_config change you made on at least one of the
>hosts, and restart that sshd
>
> 2) assuming the troublesome host is named "myhost" in your environment
>(substitute as appropriate), from your client machine, report the
>result of running
>
> getent hosts myhost
> dig +short myhost
> nslookup myhost
> ping -c 1 myhost
>
> (one or more of these commands may not exist on your machine)
>
> 2) re-attempt to connect from your client, this time passing -vv or
>-vvv, and capture the logging output

Bug#1069236:

[allan]

More info - IPv6 is disabled on all four machines.  I think
"AddressFamily any" should have supported an IPv4 connection.

Bug#1069236: openssh-server: X over ssh fails with "cannot open display"

[allan]

Package: openssh-server
Version: 1:9.7p1-4
Severity: important
X-Debbugs-Cc: wizard10...@gmail.com

On four Sid machines here X over ssh fails with "cannot open display".

Resolved the issue by editing /etc/ssh/sshd_config and changing

#AddressFamily any

to

AddressFamily inet

and restarting sshd.



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

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

Versions of packages openssh-server depends on:
ii  adduser3.137
ii  debconf [debconf-2.0]  1.5.86
ii  init-system-helpers1.66
ii  libaudit1  1:3.1.2-2.1
ii  libc6  2.37-17
ii  libcom-err21.47.0-2.4
ii  libcrypt1  1:4.4.36-4
ii  libgssapi-krb5-2   1.20.1-6+b1
ii  libkrb5-3  1.20.1-6+b1
ii  libpam-modules 1.5.3-7
ii  libpam-runtime 1.5.3-7
ii  libpam0g   1.5.3-7
ii  libselinux13.5-2+b2
ii  libssl3t64 3.2.1-3
ii  libwrap0   7.6.q-33
ii  openssh-client 1:9.7p1-4
ii  openssh-sftp-server1:9.7p1-4
ii  procps 2:4.0.4-4
ii  runit-helper   2.16.2
ii  sysvinit-utils [lsb-base]  3.09-1
ii  ucf3.0043+nmu1
ii  zlib1g 1:1.3.dfsg-3.1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  255.4-1+b1
ii  ncurses-term 6.4+20240414-1
ii  xauth1:1.1.2-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
ii  ssh-askpass   1:1.2.4.1-16+b1
pn  ufw   

-- debconf information excluded

Bug#969354:

[allan]

I've been trying to subscribe to debian-devel for about a month
through both https://lists.debian.org/debian-deval and direct
subscribe emails to debian-devel-requ...@lists.debian.org and until
this morning haven't received a confirmation email using either
method.

Today I got confirmation emails but confirmation is failing; I'm
receiving a canned error message.

I've tried confirming by just hitting reply on the confirmation email
and also by creating a new email with "confirm" and the confirmation
number in the subject line.  Both methods are failing consistently.

-- 
we see things not as they are, but as we are.
 -- anais nin

Bug#1059031:

[allan]

I am able to duplicate this, the upgrade to libtorrent-rasterbar has
also broken qbittorrent-nox.

Workaround is to downgrade libtorrent-rasterbar, which resolved the
issue for me.   See
https://github.com/qbittorrent/qBittorrent/issues/20149

Bug#1035044: autorandr: libinput-tools still missing in autorandr dependencies list?

[Allan Olsen]

Package: autorandr
Version: 1.14-1
Followup-For: Bug #1035044
X-Debbugs-Cc: allanolsen1...@gmail.com

Dear Maintainer,

I had 14.000 lines with these error messages last two days , untill I installed 
libinput-tools

Dec 08 22:44:15 Innerpeace systemd[1]: Started autorandr-lid-listener.service - 
Runs autorandr whenever the lid state changes.
Dec 08 22:44:15 Innerpeace autorandr[61889]: stdbuf: failed to run command 
‘libinput’: No such file or directory
Dec 08 22:44:15 Innerpeace systemd[1]: autorandr-lid-listener.service: 
Deactivated successfully.
Dec 08 22:44:45 Innerpeace systemd[1]: autorandr-lid-listener.service: 
Scheduled restart job, restart counter is at 1832.

seems like for now autorandr only have two dependencies 
Depends: x11-xserver-utils, python3

After I installed libinput-tools Messages are gone. 



*** End of the template - remove these template lines ***


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

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

Versions of packages autorandr depends on:
ii  python33.11.4-5+b1
ii  x11-xserver-utils  7.7+10

autorandr recommends no packages.

autorandr suggests no packages.

-- no debconf information

Bug#1037468: Acknowledgement (nvidia-driver: RmInitAdapter failed! (0x25:0x65:1457))

[Allan Wind]

It appears to be resolved with the Debian 12.1 upgrade today:

linux-image-6.1.0-10-amd64:amd64 (6.1.37-1, 6.1.38-1)
nvidia-driver:amd64 (525.105.17-1, 525.125.06-1~deb12u1)

Notified upstream.

Bug#1041750: apt-get changelog nvidia-driver fails with "Changelog unavailable"

[Allan Wind]

Package: apt
Version: 2.6.1
Severity: normal

Dear Maintainer,

I was trying to find out which changes were in the nvidia-driver 
in the just released Debian 12.1 and did:

$ apt-get changelog nvidia-driver
Err:1 https://metadata.ftp-master.debian.org nvidia-graphics-drivers 
525.125.06-1~deb12u1 Changelog
  Changelog unavailable for nvidia-graphics-drivers=525.125.06-1~deb12u1 (404  
Not Found [IP: 146.75.34.132 443])
E: Failed to fetch 
https://metadata.ftp-master.debian.org/changelogs/non-free/n/nvidia-graphics-drivers/nvidia-graphics-drivers_525.125.06-1%7edeb12u1_changelog
  Changelog unavailable for nvidia-graphics-drivers=525.125.06-1~deb12u1 (404  
Not Found [IP: 146.75.34.132 443])

The information exist as I was able to find it via:

https://www.debian.org/News/2023/20230722 ->
https://packages.debian.org/search?searchon=sourcenames=nvidia-graphics-drivers
 ->
https://packages.debian.org/source/bullseye/nvidia-graphics-drivers ->
https://metadata.ftp-master.debian.org/changelogs//non-free-firmware/n/nvidia-graphics-drivers/nvidia-graphics-drivers_525.125.06-1~deb12u1_changelog


/Allan

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^postgresql.*-15";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "tasks";
APT::Move-Autobit-Sections "";
APT::Move-Autobit-Sections:: "oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Update::Post-Invoke-Success:: "if /usr/bin/test -w /var/cache/swcatalog -a 
-e /usr/bin/appstreamcli; then appstreamcli refresh --source=os > /dev/null || 
true; fi";
APT::Update::Post-Invoke "";
APT::Update::Post-Invoke:: "[ ! -x /usr/bin/debtags ] || debtags update || 
true";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "0";
APT::Compressor::zstd "";
APT::Compressor::zstd::Name "zstd";
APT::Compressor::zstd::Extension ".zst";
APT::Compressor::zstd::Binary "zstd";
APT::Compressor::zstd::Cost "60";
APT::Compressor::zstd::CompressArg "";
APT::Compressor::zstd::CompressArg:: "-19";
APT::Compressor::zstd::UncompressArg "";
APT::Compressor::zstd::UncompressArg:: "-d";
APT::Compressor::lz4 "";
APT::Compressor::lz4::Name "lz4";
APT::Compressor::lz4::Extension ".lz4";
APT::Compressor::lz4::Binary "lz4";
APT::Compressor::lz4::Cost "50";
APT::Compressor::lz4::CompressArg "";
APT::Compressor::lz4::CompressArg:: "-1";
APT::Compressor::lz4::UncompressArg "";
APT::Compressor::lz4::UncompressArg:: "-d";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "100";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-6n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "

Bug#1037548:

[allan]

You're right, the problem was a broken MIME database.  Thank you for the helps!

Bug#1037548: qbittorrent-nox: web interface doesn't display content, browsers download html instead

[allan grossman]

Package: qbittorrent-nox
Version: 4.5.3-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: wizard10...@gmail.com

Dear Maintainer,

* What led up to the situation?

Running Debian Unstable, upgraded qbittorrent-nox to version 4.5.3-2 and
restarted its systemd service.

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

Reinstalled qbittorent-nox and libtorrent-rasterbar2.0 - ineffective
Renamed ~/.config/qBittorrent so get a clean config - ineffective

* What was the outcome of this action?

No change.  Browsers still download html code instead of displaying html
content.

* What outcome did you expect instead?

I expected the web interface to display in a browser window.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (900, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: ia64

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

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

qbittorrent-nox recommends no packages.

qbittorrent-nox suggests no packages.

-- no debconf information
[Unit]
Description=qBittorrent Daemon Service
After=network-online.target

[Service]
User=wizard
Group=wizard
ExecStart=/usr/bin/ionice -c2 -n7 /usr/bin/qbittorrent-nox --webui-port=8090
ExecStop=/usr/bin/killall -w qbittorrent-nox

[Install]
WantedBy=multi-user.target
[AddNewTorrentDialog]
DialogSize=@Size(900 665)
Enabled=false
RememberLastSavePath=false
SplitterState=@ByteArray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\x1\x93\0\0\x1\0\0\xff\xff\xff\xff\x1\0\0\0\x1\0)
TopLevel=true
TreeHeaderState="@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x6\x34\0\0\0\x3\0\0\0\x2\0\0\0\x64\0\0\0\x4\0\0\0\x64\0\0\0\x5\0\0\0\x64\0\0\x1,\0\0\0\x6\x1\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x6\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x64\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\x3\xe8\0\xff\xff\xff\xff)"

[Application]
FileLogger\Age=1
FileLogger\AgeType=1
FileLogger\Backup=true
FileLogger\DeleteOld=true
FileLogger\Enabled=false
FileLogger\MaxSizeBytes=66560
FileLogger\Path=/home/wizard/.local/share/qBittorrent/logs

[AutoRun]
OnTorrentAdded\Enabled=false
OnTorrentAdded\Program=
enabled=false
program=

[BitTorrent]
Session\AddExtensionToIncompleteFiles=true
Session\AlternativeGlobalDLSpeedLimit=0
Session\AlternativeGlobalUPSpeedLimit=0
Session\AnnounceToAllTrackers=true
Session\AsyncIOThreadsCount=32
Session\BTProtocol=TCP
Session\CheckingMemUsageSize=320
Session\DefaultSavePath=/media/internal/temp
Session\DisableAutoTMMByDefault=false
Session\DisableAutoTMMTriggers\CategorySavePathChanged=false
Session\DisableAutoTMMTriggers\DefaultSavePathChanged=false
Session\ExcludedFileNames=
Session\FilePoolSize=1000
Session\GlobalMaxRatio=-1
Session\GlobalMaxSeedingMinutes=1
Session\IgnoreLimitsOnLAN=true
Session\Interface=wg-mullvad
Session\InterfaceAddress=0.0.0.0
Session\InterfaceName=wg-mullvad
Session\LSDEnabled=false
Session\MaxActiveDownloads=20
Session\MaxActiveTorrents=20
Session\MaxActiveUploads=20
Session\MaxConnections=1
Session\MaxConnectionsPerTorrent=1000
Session\MaxRatioAction=0
Session\MaxUploads=1000
Session\MaxUploadsPerTorrent=1000
Session\Port=54881
Session\Preallocation=true
Session\QueueingSystemEnabled=true
Session\SaveResumeDataInterval=10
Session\uTPRateLimited=false

[Core]
AutoDeleteAddedTorrentFile=Never

[DownloadFromURLDialog]
Size=@Size(501 220)

[GUI]
DownloadTrackerFavicon=false
Log\Enabled=false
Notifications\Enabled=true
Notifications\Timeout=-1
Notifications\TorrentAdded=false

[IPSubnetWhitelistOptionsDialog]
Size=@Size(360 450)

[LegalNotice]
Accepted=true

[MainWindow]
geometry="@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\0$\0\0\0\x17\0\0\x6\x85\0\0\x3\xe1\0\0\0%\0\0\0;\0\0\x6\x84\0\0\x3\xde\0\0\0\0\0\0\0\0\a\x80\0\0\0%\0\0\0;\0\0\x6\x84\0\0\x3\xde)"
qt5\vsplitterState=@ByteArray(\0\0\0\xff\0\0\0\x1\0\0\0\x2\0\0\0\0\0\0\x6L\x1\xff\xff\xff\xff\x1\0\0\0\x1\0)

[Meta]
MigrationVersion=4

[Network]
Cookies=@Invalid()
PortForwardingEnabled=true
Proxy\OnlyForTorrents=false

[OptionsDialog]
HorizontalSplitterSizes=119, 634
LastViewedPage=2
Size=@Size(779 591)

[Preferences]
Advanced\DisableRecursiveDownload=false
Advanced\EnableIconsInMenus=true

Bug#1037468: nvidia-driver: RmInitAdapter failed! (0x25:0x65:1457)

[Allan Wind]

Package: nvidia-driver
Version: 525.105.17-1
Severity: important

Dear Maintainer,

The upgrade to 12 was smooth except the nvidia-driver did not load 
after rebooting on my Lenovo P51 with:

01:00.0 VGA compatible controller: NVIDIA Corporation GM206GLM [Quadro M2200 
Mobile] (rev a1)

I get a few dmesg then a blank screen with a cursor.  Not able
to change to a virtual terminal. I also also tried the version in 
experimental with similar effect:

Version: 525.105.17-1

2023-06-12T06:14:43.764+00:00 vent kernel: NVRM: GPU :01:00.0: 
RmInitAdapter failed! (0x25:0x65:1457)
2023-06-12T06:14:43.764+00:00 vent kernel: NVRM: GPU :01:00.0: 
rm_init_adapter failed, device minor number 0
2023-06-12T06:14:43.764+00:00 vent systemd[1]: lightdm.service: Failed with 
result 'exit-code'.

Version: 530.41.03-1

2023-06-13T02:02:39.056+00:00 vent kernel: NVRM: GPU :01:00.0: 
RmInitAdapter failed! (0x25:0x65:1462)
2023-06-13T02:02:39.056+00:00 vent kernel: NVRM: GPU :01:00.0: 
rm_init_adapter failed, device minor number 0
2023-06-13T02:02:39.056+00:00 vent systemd[1]: lightdm.service: Failed with 
result 'exit-code'.

I do have non-free-firmware enabled and hence the nvidia firmware.  
Upgraded bios to latest version  No difference if I use 
linux-image 6.1.0-9-amd64 or 5.10.0-23-amd64.

The only semi-workaround is to uninstall the nvidia driver and 
rely on nouveau.  Surprisingly to me, nouveau, doesn't seem to 
require the xserver-xorg-video-nouveau package to be installed(?).

Reported upstream as requested:

https://forums.developer.nvidia.com/t/rminitadapter-failed-0x251457/256445

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

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

Versions of packages nvidia-driver depends on:
pn  nvidia-alternative   
pn  nvidia-driver-bin
pn  nvidia-driver-libs   
pn  nvidia-installer-cleanup 
pn  nvidia-kernel-dkms | nvidia-kernel-525.105.17 | nvidia-open-kernel-  
525.105.17 | nvidia-open-kernel-525.105.17
pn  nvidia-legacy-check  
pn  nvidia-support   
pn  nvidia-vdpau-driver  
pn  xserver-xorg-video-nvidia

Versions of packages nvidia-driver recommends:
pn  libnvidia-cfg1   
pn  nvidia-persistenced  
pn  nvidia-settings  

Versions of packages nvidia-driver suggests:
pn  nvidia-kernel-dkms | nvidia-kernel-source | nvidia-open-kernel-sour  
ce | nvidia-open-kernel-source

Bug#1033601: RFP: nelson -- Let's Nelson! matrix language for engineering and scientific applications

[Allan CORNET]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: nelson.numerical.computat...@gmail.com

* Package name: nelson
  Version : 0.7.3
  Upstream Author : Allan CORNET 
* URL : https://nelson-numerical-software.github.io/nelson-website/
* License : GPL
  Programming Lang: C, C++
  Description : Let's Nelson! matrix language for engineering and
scientific applications

Nelson is an matrix/array programming language providing a powerful open
computing environment for engineering and scientific applications using modern
C/C++ libraries (Boost, Eigen, …) and others state of art numerical libraries.
It has sophisticated data structures (including cell, struct, linear systems,
…), an interpreter and a high level programming language. Nelson has been
developed to be an open/modular system where an user can define these own data
types and operations on these data types by using overload. Syntax is very
similar to GNU Octave or MATLAB® so that most programs are easily portable.


 - how do you plan to maintain it? Yes

Bug#1033148: Acknowledgement (firefox-esr: dialog menus close immidately, >100% cpu load after restart)

[Allan Wind]

I installed Firefox 111.0 from platpak and it seems work:

flatpak install flathub org.mozilla.firefox

Verified that the Debian version is still broken.  Just sharing 
another data point in case it's useful.

Bug#1033148: firefox-esr: dialog menus close immidately, >100% cpu load after restart

[Allan Wind]

Package: firefox-esr
Version: 102.9.0esr-1
Severity: normal

Dear Maintainer,

Starting about a week ago Firefox would after some time 
immediately close any dialog windows (like settings burger on the 
right, password auto-fill pop-up, add-on icons add-ons).  The only 
work-around that is restarting the browser.  I found restarting
the browser would 100+% peg a process with a bunch of Youtube
tabs but all unloaded.  I found that if I use about:profiles
and start with add-ons disabled I would not see the high cpu
usage.  Then I manually disabled all add-ons, and restarted
normally, and high cpu load was back.  Then I created new
profile and even in the initial start all dialogs would 
auto-close.  reportbugs told me to try the version in
unstable, so that's what I did (from pretty much 100% stable 
distribution).  No change but also it wasn't the -2 version
it claimed that was available.  I grabbed a strace of
the process with high cpu load and it showed a seemly busy loop 
for:

 "recvmsg(648, {msg_namelen=0}, 0)= -1 EAGAIN (Resource temporarily 
unavailable)"

Sometime before that, may be a month ago, firefox
would start to shutdown after some run-time.  .xsession-errors 
reports:

CPU time limit exceeded

Other than security updates, I don't recall making any system 
changes.  I see #1010420 which may be related, and I am reporting 
3 abnormalities here.  Happy to split into separate bugs whatever 
works best for you. Also, I want to be as helpful as possible to 
see if we can figure out what is going on.  chromium seem to not
exhibit any issues (as super weak "system" data point).


/Allan

-- Package-specific info:

-- Extensions information
Name: Add-ons Search Detection
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: DoH Roll-Out
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: eBay
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled

Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled

Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: System theme — auto theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled

Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled

Name: WebCompat Reporter
Location: 
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled


-- Addons package information
ii  firefox-esr102.9.0esr-1 amd64Mozilla Firefox web browser - 
Extended Support Release (ESR)

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

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

Versions of packages firefox-esr depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libasound2   1.2.4-1.1
ii  libatk1.0-0  2.36.0-2
ii  libc62.36-8
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.24-0+deb11u1
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1+deb11u1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1+deb11u1
ii  libglib2.

Bug#1028105: pkg-config:amd64 does not include necessary default search path

[Allan]

Package: pkg-config:amd64
Version: 1.8.0-12

  When I try to check for a package using pkg-config it is not
  able to find the package even that it is properly installed.
  Current output
  $ pkg-config --modversion gthread-2.0
  Package gthread-2.0 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `gthread-2.0.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'gthread-2.0', required by 'virtual:world', not found

  Workaround
  $ env PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/usr/lib/x86_64-linux-gnu/pkgconfig/"
pkg-config --modversion gthread-2.0
  2.74.4

  Expected output
  $ pkg-config --modversion gthread-2.0
  2.74.4

  The problem is that pkg-config does not know anything about this directory
  since it is not present in its default search directories
  $ pkg-config --variable pc_path pkg-config
  
/usr/local/lib/i386-linux-gnu/pkgconfig:/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/lib/i386-linux-gnu/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig

  I am using Debian GNU/Linux 6.0.12-1 (2022-12-09), kernel 6.0.0-6-amd64
  and libc6 2.36-7.

Att,
Allan Krama Guimarães

Bug#1006992: linux-image-5.10.0-12-amd64: Loading initial ramdisk... freezes

[Allan Wind]

Package: src:linux
Version: 5.10.103-1
Severity: important

Dear Maintainer,

When I upgraded from buster (10) to bullseye (11) this host would 
freeze when rebooting into a new kernel (including all point 
releases of 5.10.0) and (cold reboot) by issuing /sbin/poweroff 
then pressing the power button.  I am pretty sure it will also
usually, but not always (<50?) freeze on /sbin/reboot into the
same kernel.

When the boot process freezing there is no output after "Loading 
initial ramdisk".  Removing "quiet" and adding "debug" does not
yield any debug output. I have tried dis_ucode_ldr and nomodeset 
which did not make a difference with respect to freezing.

The host is running the latest UEFI BIOS and ECP.  It also happens
to use ECC memory and there are no faults.

There were no issues with this host under buster (10), i.e. I 
suspect a kernel change triggered this change in behavior.

I also have a P50 (previous hardware model) on the same version of 
Debian and it does NOT freeze.

My current work-around is to force power cycle the host by holding 
down the power button, then press the power button again then press
enter and subsequently f1 to enter the bios.  Then save & exit.  
Most of the time (80+%) the system would boot normally.  It 
displays the kernel output with quiet disabled as expected.

I did review #931639 but appears to be a different issue.  Happy 
to provide additional details (using this as my workstation so I 
can't reinstall buster).


/Allan

-- Package-specific info:
** Version:
Linux version 5.10.0-12-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.103-1 (2022-03-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.10.0-12-amd64 
root=UUID=fa6ff053-976a-434c-87ae-2422af36f535 ro

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[6.194103] usb 1-6.4.4.1: New USB device strings: Mfr=0, Product=4, 
SerialNumber=5
[6.194104] usb 1-6.4.4.1: Product: Internal Storage
[6.194105] usb 1-6.4.4.1: SerialNumber: G000WM0695230TBN
[6.320664] usb 1-14: new full-speed USB device number 12 using xhci_hcd
[6.470106] usb 1-14: New USB device found, idVendor=8087, idProduct=0a2b, 
bcdDevice= 0.10
[6.470116] usb 1-14: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[6.499359] usbcore: registered new interface driver usbhid
[6.499365] usbhid: USB HID core driver
[6.501194] mc: Linux media interface: v0.10
[6.503464] input: Tablet PTK-440 Mouse as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6.4/1-6.4.2/1-6.4.2:1.0/0003:056A:00B8.0001/input/input21
[6.503567] hid-generic 0003:056A:00B8.0001: input,hiddev0,hidraw0: USB HID 
v1.00 Mouse [Tablet PTK-440] on usb-:00:14.0-6.4.2/input0
[6.503660] hid-generic 0003:0765:5010.0002: hiddev1,hidraw1: USB HID v1.11 
Device [HID 0765:5010] on usb-:00:14.0-13/input0
[6.504168] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[6.512662] videodev: Linux video capture interface: v2.00
[6.541416] Bluetooth: Core ver 2.22
[6.541433] NET: Registered protocol family 31
[6.541434] Bluetooth: HCI device and connection manager initialized
[6.541436] Bluetooth: HCI socket layer initialized
[6.541437] Bluetooth: L2CAP socket layer initialized
[6.541439] Bluetooth: SCO socket layer initialized
[6.552714] usb 1-6.4.4.2: new full-speed USB device number 13 using xhci_hcd
[6.573316] usbcore: registered new interface driver btusb
[6.573663] Bluetooth: hci0: Bootloader revision 0.0 build 26 week 38 2015
[6.574690] Bluetooth: hci0: Device revision is 16
[6.574693] Bluetooth: hci0: Secure boot is enabled
[6.574694] Bluetooth: hci0: OTP lock is enabled
[6.574695] Bluetooth: hci0: API lock is enabled
[6.574695] Bluetooth: hci0: Debug lock is disabled
[6.574696] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[6.575307] bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-12-16.sfi
[6.575311] Bluetooth: hci0: Found device firmware: intel/ibt-12-16.sfi
[6.617289] input: Wacom Intuos4 4x6 Pen as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6.4/1-6.4.2/1-6.4.2:1.0/0003:056A:00B8.0001/input/input23
[6.617524] input: Wacom Intuos4 4x6 Pad as 
/devices/pci:00/:00:14.0/usb1/1-6/1-6.4/1-6.4.2/1-6.4.2:1.0/0003:056A:00B8.0001/input/input25
[6.617893] wacom 0003:056A:00B8.0001: hidraw0: USB HID v1.00 Mouse [Tablet 
PTK-440] on usb-:00:14.0-6.4.2/input0
[6.659233] usb 1-6.4.4.2: New USB device found, idVendor=29ea, 
idProduct=0102, bcdDevice= 1.00
[6.659236] usb 1-6.4.4.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[6.659237] usb 1-6.4.4.2: Product: Advantage2 Keyboard
[6.659238] usb 1-6.4.4.2: Manufacturer: Kinesis
[6.659239] usb 1-6.4.4.2: 

Bug#270751: HI

[Rosemary Allan]

Hello my dear I am Rosemary Allan, I have  good news for you, please can
you kindly get back to me

Bug#1001952: Acknowledgement (FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/cdist/preos')

[Allan Wind]

Not sure why I didn't try the suggestion out before file the bug:

sudo mkdir  /usr/lib/python3/dist-packages/cdist/preos
sudo chmod 755 !$

$ cdist preos
Available PreOS-es:

$

Bug#1001952: FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/cdist/preos'

[Allan Wind]

Package: cdist
Version: 6.9.4-1
Severity: normal

Dear Maintainer,

$ cdist preos
Traceback (most recent call last):
  File "/usr/bin/cdist", line 91, in 
commandline()
  File "/usr/bin/cdist", line 52, in commandline
return cdist.preos.PreOS.commandline(sys.argv[1:])
  File "/usr/lib/python3/dist-packages/cdist/preos.py", line 111, in commandline
cls.preoses = find_preoses()
  File "/usr/lib/python3/dist-packages/cdist/preos.py", line 62, in find_preoses
for preos in find_preos_plugins():
  File "/usr/lib/python3/dist-packages/cdist/preos.py", line 57, in 
find_preos_plugins
yield from scan_preos_dir_plugins(dir)
  File "/usr/lib/python3/dist-packages/cdist/preos.py", line 40, in 
scan_preos_dir_plugins
for fname in os.listdir(dir):
FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/lib/python3/dist-packages/cdist/preos'

It's probably just the missing 'preos' directory.


/Allan

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

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

Versions of packages cdist depends on:
ii  python3  3.9.2-3

cdist recommends no packages.

Versions of packages cdist suggests:
pn  cdist-doc  

-- no debconf information

-- 
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#984429: (no subject)

[Allan Wind]

Is Recommends enough if the package generate errors without rtkit?  After I 
upgraded 3 hosts to Debian 11 I got 86 instances of these errors.  It was 
somewhat problematic as you are trying to figure out what matters in the deluge 
of errors after upgrading.

Bug#992202: tmux doesn't read tmux.conf upon login

[Allan Wind]

Package: tmux
Version: 3.1c-1
Severity: normal

Dear Maintainer,

I just upgraded to bullseye and on subsequent login tmux doesn't 
appear to read tmux.conf.  This worked fine in buster.  I start 3 
instances via i3:

exec i3-msg "workspace 1; exec x-www-browser; exec x-terminal-emulator -e tmux"
exec i3-msg "workspace 2; exec x-terminal-emulator -e tmux; exec pidgin"
exec i3-msg "workspace 3; exec x-terminal-emulator -e tmux new mutt"

The 3 instances show up as `tmux ls` so it is running, and I can 
use the default C-b prefix instead (but my customized C-a does not 
work).

The work-around is to exit all 3 instances before a subsequent 
start of tmux will read my tmux.conf file and behave as expected.
(I moved ~/.tmux.conf to .config/tmux/.tmux.conf but neither 
location matters for the initial start-up).

I ran strace -ff tmux and I did not see an access or open of 
the tmux.conf file.

Please let me know what data I can provide to help.


/Allan

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

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

Versions of packages tmux depends on:
ii  libc6   2.31-13
ii  libevent-2.1-7  2.1.12-stable-1
ii  libtinfo6   6.2+20201114-2
ii  libutempter01.2.1-2

tmux recommends no packages.

tmux suggests no packages.

-- no debconf information

-- 
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#991320: flameshot crashing on startup

[allan]

many thanks, dennis - if you need anything else feel free to reach out.

On Thu, Jul 22, 2021 at 3:33 PM Dennis Filder  wrote:
>
> Okay, I can reproduce the crash now with that setting.

Bug#991320: flameshot crashing on startup

[allan]

this link and the link above only address the tray icon - nothing on
the network thing on github bugtracker.  both of these bugs are
closed.

https://github.com/flameshot-org/flameshot/issues/1721

amusingly, if i rename flameshot.ini and start the flameshot daemon in
the background (which is how i had it set up in openbox autostart)
flameshot works as expected.  diff between default config and mine -

wizard@wizard-fujitsu:~/.config/flameshot$ diff flameshot.ini
flameshot.ini.broken
2,5c2,7
< disabledTrayIcon=false
< drawColor=#ff
< drawThickness=0
< showStartupLaunchMessage=true
---
> # disabledTrayIcon=true
> drawColor=#00ff00
> drawThickness=9
> savePath=/media/internal/temp
> startupLaunch=false
> # checkForUpdates=false

using the config i had that's been working for over a year flameshot
daemon (flameshot &) crashes if checkForUpdates=false.

starting 'flameshot gui' without the daemon running in the background
crashes with either config.





On Thu, Jul 22, 2021 at 8:43 AM allan  wrote:
>
> i think i figured it out.  looks like it's upstream and wontfix.
>
> https://github.com/flameshot-org/flameshot/issues/1730



-- 
we see things not as they are, but as we are.
 -- anais nin

Bug#991320: flameshot crashing on startup

[allan]

i think i figured it out.  looks like it's upstream and wontfix.

https://github.com/flameshot-org/flameshot/issues/1730

Bug#991320: flameshot crashing on startup

[allan]

not able to choke my network as option isn't available in kernel
module, connman or router.  using iw to throttle bitrate seems to be
unsupported by this intel chipset or at least it's not in the list of
supported commands if you do 'iw list'.

flameshot 0.9 appimage took some digging to find but also crashes -

wizard@wizard-fujitsu:~/temp$ ./Flameshot-0.9.0.x86_64.AppImage
Run experimental self-contained bundle
QSettings::value: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
Segmentation fault
wizard@wizard-fujitsu:~/temp$

purged 0.9 and installed current flameshot 0.10.0.rc1-1 deb from
github and it works as expected.

then i purged 0.10 and reinstalled 0.9 from sid repo in case we need
more testing.  if i really need to run flameshot i can just disable
checking for upgrades for the time being.

Bug#991320: flameshot crashing on startup

[allan]

oh - almost forgot.  on the tray icon -

[General]
disabledTrayIcon=true
drawColor=#00ff00
drawThickness=9
savePath=/media/internal/temp
startupLaunch=false
# checkForUpdates=false

Bug#991320: flameshot crashing on startup

[allan]

> No, it shows exactly what I was looking for:

this is why i should listen to developers.  i would have been tearing
stuff apart already  :)

flameshot worked properly the last time i used it and for at least a
year before,  last time i used it was maybe five days before i filed
the bug.

network here is 200/10mb and latency usually runs 40-50ms which ain't
great but ain't awful either.

i think what i'll do is shut off everything but 802.11b and play a
little which may take a little network configurating if i can't do it
on the wireless kernel module or connman; i can't think of a way to
add latency as i'm already doing wireless. happy to do the appimage
thing (that would eliminate openbox, right?) but i really would rather
not install snap infrastructure.

may be noon est or so before i'm able to play with this again so
thanks and have a good evening.

Bug#991320: flameshot crashing on startup

[allan]

this doesn't look real helpful - looks like I may need to install some
source code but not sure which code other than flameshot -

Reading symbols from flameshot...
Reading symbols from
/usr/lib/debug/.build-id/5c/2acff54f5aa466e019691671622f39294b075d.debug...
(gdb) start
Temporary breakpoint 1 at 0x3dc60: file ./src/main.cpp, line 54.
Starting program: /usr/bin/flameshot
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Temporary breakpoint 1, main (argc=1, argv=0x7fffe338) at ./src/main.cpp:54
54 ./src/main.cpp: No such file or directory.
(gdb) break Controller::handleReplyCheckUpdates(QNetworkReply*)
Breakpoint 2 at 0x555b1720: file ./src/core/controller.cpp, line 160.
(gdb) continue
Continuing.
[New Thread 0x72a64700 (LWP 155677)]
QSettings::value: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
[New Thread 0x71e16700 (LWP 155678)]
[New Thread 0x715e5700 (LWP 155679)]
[New Thread 0x70a08700 (LWP 155680)]
[New Thread 0x7fffe3fff700 (LWP 155681)]

Thread 1 "flameshot" hit Breakpoint 2, Controller::handleReplyCheckUpdates (
this=0x55642160 , reply=0x55703b60)
at ./src/core/controller.cpp:160
160 ./src/core/controller.cpp: No such file or directory.
(gdb) break QAction::setText(QString const&)
Breakpoint 3 at 0x7787b000: file
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h, line
116.
(gdb) continue
Continuing.

Thread 1 "flameshot" hit Breakpoint 3, QAction::setText (this=0x0, text=...)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116
116 ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h: No
such file or directory.
(gdb) backtrace 5
#0  QAction::setText (this=0x0, text=...)
at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116
#1  0x555b2267 in Controller::handleReplyCheckUpdates (
this=0x55642160 , reply=0x7fffd120)
at ./src/core/controller.cpp:195
#2  0x76d895a6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x77de9ad2 in QNetworkAccessManager::finished(QNetworkReply*) ()
   from /lib/x86_64-linux-gnu/libQt5Network.so.5
#4  0x77deae17 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5
(More stack frames follow...)
(gdb) continue
Continuing.
[Thread 0x7fffe3fff700 (LWP 155681) exited]

Thread 1 "flameshot" received signal SIGSEGV, Segmentation fault.
QAction::setText (this=0x0, text=...) at kernel/qaction.cpp:714
714 kernel/qaction.cpp: No such file or directory.
(gdb) quit
A debugging session is active.

Inferior 1 [process 155542] will be killed.

Quit anyway? (y or n) y
wizard@wizard-laptop:/tmp$

Bug#991320: flameshot crashing on startup

[allan]

no joy here either -

Reading symbols from flameshot...
(No debugging symbols found in flameshot)
(gdb) backtrace 5
No stack.
(gdb)

Bug#991320: flameshot crashing on startup

[allan]

couldn't get past "start" -

wizard@wizard-laptop:~$ gdb flameshot
GNU gdb (Debian 10.1-2) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from flameshot...
(No debugging symbols found in flameshot)
(gdb) start
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n])
Starting program: /usr/bin/flameshot
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x72a64700 (LWP 122428)]
QSettings::value: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
QSettings::value: Empty key passed
QSettings::setValue: Empty key passed
[New Thread 0x71e16700 (LWP 122429)]
[New Thread 0x715e5700 (LWP 122430)]
[New Thread 0x70a08700 (LWP 122431)]
[New Thread 0x7fffe3fff700 (LWP 122432)]

Thread 1 "flameshot" received signal SIGSEGV, Segmentation fault.

Bug#991320: flameshot crashing on startup

[allan]

Setting checkForUpdates=false resolved the issue.  Thanks, Dennis  :)

Bug#991320: flameshot crashing on startup

[allan]

apt log shows qt libraries updated three days ago - these wouldn't
have made it to Bullseye yet.

Start-Date: 2021-07-17  08:52:52
Requested-By: wizard (1000)
Install: libqt5quickwidgets5:amd64 (5.15.2+dfsg-6, automatic),
qml-module-qtquick-window2:amd64 (5.15.2+dfsg-6, automatic), sox:amd64
(14.4.2+git20190427-2, automatic), qml-module-qt-labs-settings:amd64
(5.15.2+dfsg-6, automatic), qml-module-qtmultimedia:amd64 (5.15.2-3,
automatic), libqt5multimediaquick5:amd64 (5.15.2-3, automatic),
libsox3:amd64 (14.4.2+git20190427-2, automatic), mystiq:amd64
(20.03.23-2), qml-module-qt-labs-folderlistmodel:amd64 (5.15.2+dfsg-6,
automatic), libsox-fmt-alsa:amd64 (14.4.2+git20190427-2, automatic),
libqt5multimediawidgets5:amd64 (5.15.2-3, automatic),
qml-module-qtquick-privatewidgets:amd64 (5.15.2-2, automatic),
libsox-fmt-base:amd64 (14.4.2+git20190427-2, automatic),
qml-module-qtquick2:amd64 (5.15.2+dfsg-6, automatic),
qml-module-qtquick-dialogs:amd64 (5.15.2-2, automatic),
libqt5qmlworkerscript5:amd64 (5.15.2+dfsg-6, automatic),
qml-module-qtqml:amd64 (5.15.2+dfsg-6, automatic)
End-Date: 2021-07-17  08:52:58

GDK_BACKEND=x11 flameshot still segfaulted.  I'm running X11.

catchsegv was too big for a bug report so I attached it to email.
*** Segmentation fault
Register dump:

 RAX:    RBX: 55efcb346160   RCX: 55efccfe6010
 RDX: 0004   RSI: 7ffed987dbb0   RDI: 
 RBP: 7ffed987dbc0   R8 : 55efcd1e84e0   R9 : 0020
 R10: 0006   R11: 0006   R12: 7ffed987dbb0
 R13: 7ffed987db90   R14: 55efcd0b67f8   R15: 7ffed987db98
 RSP: 7ffed987db00

 RIP: 7fd8dbd48005   EFLAGS: 00010206

 CS: 0033   FS:    GS: 

 Trap: 000e   Error: 0004   OldMask:    CR2: 0008

 FPUCW: 037f   FPUSW:    TAG: 7fd8
 RIP: dae37fd8   RDP: dbbe8140

 ST(0)     ST(1)  
 ST(2)     ST(3)  
 ST(4)     ST(5)  b000
 ST(6)  d000   ST(7) d000 d000
 mxcsr: 1fa0
 XMM0:  61697320 XMM1:  61697320
 XMM2:  61697320 XMM3:  61697320
 XMM4:  61697320 XMM5:  61697320
 XMM6:  61697320 XMM7:  61697320
 XMM8:  61697320 XMM9:  61697320
 XMM10: 61697320 XMM11: 61697320
 XMM12: 61697320 XMM13: 61697320
 XMM14: 61697320 XMM15: 61697320

Backtrace:
/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN7QAction7setTextERK7QString+0x5)[0x7fd8dbd48005]
flameshot(+0x5e267)[0x55efcb2b6267]
/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2e45a6)[0x7fd8db2545a6]
/lib/x86_64-linux-gnu/libQt5Network.so.5(_ZN21QNetworkAccessManager8finishedEP13QNetworkReply+0x42)[0x7fd8dc2b6ad2]
/lib/x86_64-linux-gnu/libQt5Network.so.5(+0x44e17)[0x7fd8dc2b7e17]
/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x2e45a6)[0x7fd8db2545a6]
/lib/x86_64-linux-gnu/libQt5Network.so.5(+0xa08b8)[0x7fd8dc3138b8]
/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0x291)[0x7fd8db249ff1]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x7f)[0x7fd8dbd4c15f]
/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0x12a)[0x7fd8db21dfca]
/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x171)[0x7fd8db220a01]
/lib/x86_64-linux-gnu/libQt5Core.so.5(+0x305e93)[0x7fd8db275e93]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x25b)[0x7fd8da050e6b]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x52118)[0x7fd8da051118]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2f)[0x7fd8da0511cf]
/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f)[0x7fd8db27551f]
/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x12b)[0x7fd8db21c98b]
/lib/x86_64-linux-gnu/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x90)[0x7fd8db224c00]
flameshot(+0x3f9f6)[0x55efcb2979f6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7fd8daa6dd0a]
flameshot(+0x41c8a)[0x55efcb299c8a]

Memory map:

55efcb258000-55efcb289000 r--p  08:11 12324114 /usr/bin/flameshot
55efcb289000-55efcb2f3000 r-xp 00031000 08:11 12324114 /usr/bin/flameshot
55efcb2f3000-55efcb33b000 r--p 0009b000 08:11 12324114 /usr/bin/flameshot
55efcb33b000-55efcb346000 r--p 000e2000 08:11 12324114 /usr/bin/flameshot
55efcb346000-55efcb347000 rw-p 000ed000 08:11 12324114 /usr/bin/flameshot
55efccfe6000-55efcd2c4000 rw-p  00:00 

Bug#991320: flameshot crashing on startup

[allan]

More information.

Qt5 updates on these machines was installed three days ago; since I
update daily I'm fairly certain these updates haven't made it to
Bullseye yet.

Bug#991320: flameshot crashing on startup

[allan]

This has only been broken for a couple of days - there's a strong
possibility that whatever broke it hasn't made it to Bullseye yet.
This appears to be an upstream bug because a Manjaro user running same
version of flameshot and Qt is experiencing same behavior and as
mentioned, it broke a couple of days ago.

On Tue, Jul 20, 2021 at 11:54 AM Dennis Filder  wrote:
>
> X-Debbugs-CC: allan grossman 
>
> I can't reproduce this under current Bullseye KDE/xorg -- flameshot
> behaves absolutley normally.  It could be a Wayland issue, and
> flameshot's Wayland support is apparently still experimental.
>
> Let us know if running flameshot like so fixes this for you:
>
> GDK_BACKEND=x11 flameshot
>
> Regards,
> Dennis Filder



-- 
we see things not as they are, but as we are.
 -- anais nin

Bug#991320: flameshot crashing on startup

[allan]

Correction.

"flameshot &" is in openbox autostart, "flameshot gui -p
/home/username/temp" is mapped to hotkey in ~/.config/openbox/rc.xml -
this configuration has been working for more than a year.

On Tue, Jul 20, 2021 at 10:18 AM allan grossman  wrote:
>
> Package: flameshot
> Version: 0.9.0+ds1-1
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: wizard10...@gmail.com
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> Have flameshot gui -p /home/username/temp set in openbox autostart.  Mapped 
> hotkeys were not responding.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
> This probably isn't a flameshot bug but I'm not sure where it goes - 
> flameshot crashes when started in openbox autostart or from terminal session 
> and have duplicated the error on two Sid machines.  If you execute 
> "dbus-update-activation-environment DISPLAY XAUTHORITY" flameshot gui will 
> start for about half a second and then crash, which is better than running in 
> a terminal session where it won't display GUI at all before crashing.
>
>* What was the outcome of this action?
>
> flameshot still not working.
>
>* What outcome did you expect instead?
>
> Expected flameshot to run as normal  :)
>
>
> -- System Information:
> Debian Release: 11.0
>   APT prefers unstable
>   APT policy: (1001, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
> Kernel taint flags: TAINT_USER, TAINT_FIRMWARE_WORKAROUND
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages flameshot depends on:
> ii  hicolor-icon-theme0.17-2
> ii  libc6 2.31-13
> ii  libfmt7   7.1.3+ds1-5
> ii  libgcc-s1 10.2.1-6
> ii  libqt5core5a  5.15.2+dfsg-9
> ii  libqt5dbus5   5.15.2+dfsg-9
> ii  libqt5gui55.15.2+dfsg-9
> ii  libqt5network55.15.2+dfsg-9
> ii  libqt5svg55.15.2-3
> ii  libqt5widgets55.15.2+dfsg-9
> ii  libspdlog1 [libspdlog1-fmt7]  1:1.8.1+ds-2.1
> ii  libstdc++610.2.1-6
>
> flameshot recommends no packages.
>
> Versions of packages flameshot suggests:
> ii  ca-certificates  20210119
> ii  openssl  1.1.1k-1
>
> -- no debconf information



-- 
we see things not as they are, but as we are.
 -- anais nin

Bug#991320: flameshot crashing on startup

[allan grossman]

Package: flameshot
Version: 0.9.0+ds1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: wizard10...@gmail.com

Dear Maintainer,

   * What led up to the situation?

Have flameshot gui -p /home/username/temp set in openbox autostart.  Mapped 
hotkeys were not responding.
   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

This probably isn't a flameshot bug but I'm not sure where it goes - flameshot 
crashes when started in openbox autostart or from terminal session and have 
duplicated the error on two Sid machines.  If you execute 
"dbus-update-activation-environment DISPLAY XAUTHORITY" flameshot gui will 
start for about half a second and then crash, which is better than running in a 
terminal session where it won't display GUI at all before crashing.
 
   * What was the outcome of this action?

flameshot still not working.
   
   * What outcome did you expect instead?

Expected flameshot to run as normal  :)
   

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

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

Versions of packages flameshot depends on:
ii  hicolor-icon-theme0.17-2
ii  libc6 2.31-13
ii  libfmt7   7.1.3+ds1-5
ii  libgcc-s1 10.2.1-6
ii  libqt5core5a  5.15.2+dfsg-9
ii  libqt5dbus5   5.15.2+dfsg-9
ii  libqt5gui55.15.2+dfsg-9
ii  libqt5network55.15.2+dfsg-9
ii  libqt5svg55.15.2-3
ii  libqt5widgets55.15.2+dfsg-9
ii  libspdlog1 [libspdlog1-fmt7]  1:1.8.1+ds-2.1
ii  libstdc++610.2.1-6

flameshot recommends no packages.

Versions of packages flameshot suggests:
ii  ca-certificates  20210119
ii  openssl  1.1.1k-1

-- no debconf information

Bug#989253: qbittorrent refuses to start after qt5 upgrade

[allan]

Clean installed worked on another machine, existing install does not.
Please close this bug - and sorry for your trouble  :)

On Sun, May 30, 2021 at 11:19 AM Andrey Rahmatullin  wrote:
>
> Control: tags -1 moreinfo unreproducible
>
> I cannot reproduce this on a freshly installed package.
>
> --
> WBR, wRAR



-- 
we see things not as they are, but as we are.
 -- anais nin

Bug#989255: qbittorrent-nox web UI fails after qt5 upgrade

[allan grossman]

Package: qbittorrent-nox
Version: 4.2.5-0.1
Severity: important

Dear Maintainer,


   * What led up to the situation?

 Ran aptitude safe-upgrade this morning which updated qt5 libraries.  After 
reboot, qbittorrent-nox web UI is inaccessible.
 Tried opening web UI in Chrome and Firefox and both browsers download the 
page instead of opening it.  Backend works just
 fine as radarr and sonarr are both communicating with it just fine but web 
UI is broken.

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

 Restarted qbittorrent-nox several times.

   * What was the outcome of this action?

 qbittorrent-nox backend works, web UI does not.

   * What outcome did you expect instead?

 Expected web UI to work as designed.


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

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qbittorrent-nox depends on:
ii  libc6   2.31-12
ii  libgcc-s1   10.2.1-6
ii  libqt5core5a5.15.2+dfsg-6
ii  libqt5network5  5.15.2+dfsg-6
ii  libqt5xml5  5.15.2+dfsg-6
ii  libssl1.1   1.1.1k-1
ii  libstdc++6  10.2.1-6
ii  libtorrent-rasterbar10  1.2.9-0.3
ii  zlib1g  1:1.2.11.dfsg-2

qbittorrent-nox recommends no packages.

Versions of packages qbittorrent-nox suggests:
pn  qbittorrent-dbg  

-- no debconf information

Bug#989253: qbittorrent refuses to start after qt5 upgrade

[allan grossman]

Package: qbittorrent
Version: 4.2.5-0.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

 Ran aptitude safe-upgrade on Debian Unstable, which updated qt5 libraries.

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

 Tried to start qbittorrent via openbox menu, application .desktop file and 
from command prompt.

   * What was the outcome of this action?

 All were unsuccessful.  Attempting to start via command prompt produced no 
output.

   * What outcome did you expect instead?

 Expected qbittorrent to start normally.

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

Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qbittorrent depends on:
ii  geoip-database  20191224-3
ii  libc6   2.31-12
ii  libgcc-s1   10.2.1-6
ii  libqt5core5a5.15.2+dfsg-6
ii  libqt5dbus5 5.15.2+dfsg-6
ii  libqt5gui5  5.15.2+dfsg-6
ii  libqt5network5  5.15.2+dfsg-6
ii  libqt5widgets5  5.15.2+dfsg-6
ii  libqt5xml5  5.15.2+dfsg-6
ii  libssl1.1   1.1.1k-1
ii  libstdc++6  10.2.1-6
ii  libtorrent-rasterbar10  1.2.9-0.3
ii  python3 3.9.2-3
ii  zlib1g  1:1.2.11.dfsg-2

qbittorrent recommends no packages.

Versions of packages qbittorrent suggests:
pn  qbittorrent-dbg  

-- no debconf information

Bug#989233: malloc(): smallbin double linked list corrupted

[Allan Wind]

Package: newsboat
Version: 2.13-1+deb10u1
Severity: normal

Dear Maintainer,

I am getting this error once in a while:

"malloc(): smallbin double linked list corrupted"

and the program exists and leaves the terminal in a modified 
state.  echo disabled, I think.  Sorry, I did not think of

running stty to figure out what.

I have not been able to reproduce the issue.  This looks 
potentially interesting:


https://github.com/newsboat/newsboat/blob/master/CHANGELOG.md#2221---2021-01-10

2.22

...

Memory corruption while rendering an article with JavaScript that 
contains HTML (#1300) (Alexander Batischev)



/Allan

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

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

Versions of packages newsboat depends on:
ii  libc62.28-10
ii  libcurl3-gnutls  7.64.0-4+deb10u2
ii  libgcc-s1 [libgcc1]  10.1.0-1
ii  libgcc1  1:8.3.0-6
ii  libjson-c3   0.12.1+ds-2+deb10u1
ii  libncursesw6 6.1+20181013-2+deb10u2
ii  libsqlite3-0 3.27.2-3+deb10u1
ii  libstdc++6   10.1.0-1
ii  libstfl0 0.22-1.3+b10
ii  libtinfo66.1+20181013-2+deb10u2
ii  libxml2  2.9.4+dfsg1-7+deb10u1

Versions of packages newsboat recommends:
ii  sensible-utils  0.0.12

newsboat suggests no packages.

-- no debconf information

--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#919577: closed by Debian FTP Masters (Bug#954831: Removed package(s) from unstable)

[Allan Sandfeld Jensen]

On Samstag, 13. Februar 2021 14:09:36 CET you wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the g++-8 package:
> 
> #919577: g++-8: Can't build GN tool due to bug in raw-string parsing
> 
> It has been closed by Debian FTP Masters .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters
>  by replying to this email.

The bug was misreported, but still present. The upstream issue is https://
gcc.gnu.org/bugzilla/show_bug.cgi?id=88475

Best regards
Allan

Bug#955405: Problem is with ruby-bundler package

[Andy Allan]

This isn't a problem in the ruby-thor package (although it could do with
an update). This is a problem with the ruby-bundler package.

Specifically, the upstream bundler codebase vendors Thor under a
separate namespace (Bundler::Thor) to avoid this specific issue. Bundler
itself needs Thor, but many projects do too. So to make something like
"bundle exec (whatever)" work, without version clashes, bundler uses a
different namespace for its internal copy of Thor.

The Debian/Ubuntu ruby-bundler package is broken though, since it rips
out the carefully vendored code in a specific namespace, and uses
ruby-thor in the Thor namespace instead.

Here is the patch that causes the issue:

From: Christian Hofstaedtler 
Date: Thu, 15 Mar 2018 14:51:43 +0100
Subject: Replace bundled libraries with system versions
Forwarded: not-needed

--- a/lib/bundler/vendored_molinillo.rb
+++ b/lib/bundler/vendored_molinillo.rb
@@ -1,4 +1,4 @@
 # frozen_string_literal: true

 module Bundler; end
-require_relative "vendor/molinillo/lib/molinillo"
+require "molinillo"
--- a/lib/bundler/vendored_thor.rb
+++ b/lib/bundler/vendored_thor.rb
@@ -2,7 +2,7 @@

 module Bundler
   def self.require_thor_actions
-require_relative "vendor/thor/lib/thor/actions"
+require "thor/actions"
   end
 end
-require_relative "vendor/thor/lib/thor"
+require "thor"

Bug#973265: Acknowledgement (pulseaudio: linux-image-4.19.0-12-amd64: load-module initialization failed)

[Allan Wind]

http://sprunge.us/MZ0QsN

I ran fuser -a on /dev/snd/* after stopping pulseaudio,
so it appears something in the configuration is now conflicting.  
default.pa worked fine for over a year.


Reverted to using custom profile to select between headphone and 
speaker (hoping the issue with mono audio has been resolved since 
I tried last time).



/Allan
--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#973265: pulseaudio: linux-image-4.19.0-12-amd64: load-module initialization failed

[Allan Wind]

Package: pulseaudio
Version: 12.2-4+deb10u1
Severity: important

Dear Maintainer,

It appears that when I upgraded from linux-image-4.19.0-10-amd64 to 
either 11 or 12 the customizations in default.pa fail to load (I 
need those to be able switch between headphone and speaker output, 
using a profile for this doesn't work for mono audio):


2020-10-27T06:26:23.198+00:00 vent pulseaudio[1494]: W: [alsa-sink-USB Audio] 
asyncq.c: q overrun, queuing locally
2020-10-27T06:26:23.198+00:00 vent pulseaudio[1494]: W: [alsa-sink-USB Audio] 
asyncq.c: q overrun, queuing locally
2020-10-27T06:29:02.199+00:00 vent systemd[1046]: pulseaudio.service: Succeeded.
2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: Failed to load module "module-alsa-source" (argument: "device=hw:Pro70793162 name=raw_input source_name=raw_input channels=2 
channel_map=front-left,front-right"): initialization failed.

2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: Failed to load 
module "module-alsa-sink" (argument: "device=hw:Pro70793162 name=raw sink_name=raw 
channels=12 channel_map=aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9,aux10,aux11"): 
initialization failed.
2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module-remap-sink.c: Master 
sink not found 2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: 
Failed to load module "module-remap-sink" (argument: 
"sink_properties=device.description=Headphone sink_name=headphone master=raw channels=2 
master_channel_map=aux2,aux3 channel_map=front-left,front-right remix=no"): initialization 
failed.
2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module-remap-sink.c: Master sink not found 2020-10-27T06:29:05.948+00:00 vent pulseaudio[1171]: E: [pulseaudio] module.c: Failed to load module "module-remap-sink" (argument: "sink_properties=device.description=Speaker sink_name=speaker master=raw channels=2 master_channel_map=aux0,aux1 channel_map=front-left,front-right 
remix=no"): initialization failed.

2020-10-27T06:48:53.699+00:00 vent pulseaudio[1171]: W: [alsa-sink-USB Audio] 
alsa-util.c: Got POLLNVAL from ALSA 2020-10-27T06:48:53.699+00:00 vent 
pulseaudio[1171]: W: [alsa-sink-USB Audio] alsa-util.c: Could not recover from 
POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device
2020-10-27T06:48:53.699+00:00 vent pulseaudio[1171]: W: [alsa-source-USB Audio] 
alsa-util.c: Got POLLNVAL from ALSA
2020-10-27T06:48:53.699+00:00 vent pulseaudio[1171]: W: [alsa-source-USB Audio] 
alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP with 
snd_pcm_prepare(): No such device

root@vent:~# cat /proc/asound/cards 
0 [PCH]: HDA-Intel - HDA Intel PCH

 HDA Intel PCH at 0x2ff201 irq 148
1 [NVidia ]: HDA-Intel - HDA NVidia
 HDA NVidia at 0xec00 irq 17
2 [Pro70793162]: USB-Audio - Babyface Pro (70793162)
 RME Babyface Pro (70793162) at usb-:00:14.0-2.4.4.4, 
high speed
3 [Webcam ]: USB-Audio - C922 Pro Stream Webcam
 C922 Pro Stream Webcam at usb-:00:14.0-6, high speed

I get the same unhelpful error message when I load said modules with pactl
manually.  Not sure how to troubleshoot this.  This host runs stable, and
only security upgrades have been applied. I don't see any recent changes
related to pulseaudio so I suspect it's the kernel upgrade. It fails with both
-11 and -12.  I already purged -10, unfortunately, but this was the kernel I
ran when it last worked.


/Allan

-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

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

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.8-1
ii  libasound2-plugins   1.1.8-1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libdbus-1-3  1.12.20-0+deb10u1
ii  libgcc-s1 [libgcc1]  10.1.0-1
ii  libgcc1  1:8.3.0-6
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-9
ii  liborc-0.4-0 1:0.4.28-3.1
ii  libpulse012.2-4+deb10u1
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-6
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2

Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

[allan grossman]

Package: nvidia-legacy-390xx-driver
Version: 390.138-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Upgraded Sid this morning and X will not start with 5.8 kernel with nvidia-
legacy-390xx-driver.  Works fine with 5.7.x kernel.



-- Package-specific info:
uname -a:
Linux wizard-laptop 5.7.0-3-amd64 #1 SMP Debian 5.7.17-1 (2020-08-23) x86_64 
GNU/Linux

/proc/version:
Linux version 5.7.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-17), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.17-1 (2020-08-23)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
GCC version:  gcc version 9.3.0 (Debian 9.3.0-17) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107GLM [Quadro 
K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Dell GK107GLM [Quadro K1100M] [1028:05cc]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video  226,   0 Sep  8 07:11 /dev/dri/card0
crw-rw+ 1 root render 226, 128 Sep  8 07:11 /dev/dri/renderD128
crw-rw-rw-  1 root root   195, 254 Sep  8 07:11 /dev/nvidia-modeset
crw-rw-rw-  1 root root   195,   0 Sep  8 07:11 /dev/nvidia0
crw-rw-rw-  1 root root   195, 255 Sep  8 07:11 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Sep  8 07:11 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Sep  8 07:11 pci-:01:00.0-render -> ../renderD128
video:x:44:wizard

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Aug 29 11:01 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   51 Aug 29 11:01 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   50 Aug 29 11:01 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Aug 29 11:01 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   54 Aug 29 11:01 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 Aug 29 11:01 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   44 Aug 29 11:01 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   44 Aug 29 11:01 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   25 Aug 29 11:01 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Aug 29 11:01 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Aug 29 11:01 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Aug 29 11:01 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Aug 29 11:01 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Aug 29 11:01 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Aug 29 11:01 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Aug 29 11:01 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/legacy-390xx
lrwxrwxrwx 1 root root   64 Aug 29 11:01 
/etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libEGL_nvidia.so.0
lrwxrwxrwx 1 root root   64 Aug 29 11:01 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   64 Aug 29 11:01 
/etc/alternatives/nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   38 Aug 29 11:01 
/etc/alternatives/nvidia--libglx.so -> /usr/lib/nvidia/legacy-390xx/libglx.so
lrwxrwxrwx 1 root root   63 Aug 29 11:01 
/etc/alternatives/nvidia--libnvidia-ml.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/legacy-390xx/libnvidia-ml.so.1
lrwxrwxrwx 1 root root   66 Aug 29 11:01 
/etc/alternatives/nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu -> 

Bug#968255:

[allan]

Apologies for multiple uploads of same file and for inline conky.conf
- reportbug wasn't making me happy this afternoon  :)

-- 
we see things not as they are, but as we are.
 -- anais nin

Bug#962154: Resolved

[Allan Herrera]

For reference which commands I used:
sudo apt-get install --reinstall -yqq command-not-found #For reinstalling
package
sudo nano /etc/apt/sources.list.d/google-chrome.list #Google chrome
repository
I commented it all that way:
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# You may comment out this entry, but any other modifications may be lost.
#deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

sudo apt-get update& apt-get upgrade -yqq
sudo update-command-not-found

*Problem Solved, I expect this will be useful*

Bug#962154: command-not-found not called for inexisting commands

[Allan Herrera]

Package: command-not-found
Version: 18.04.5-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,


   Using any uexisting command
calling a command i.e. "sudi" shich doesnt exists or misspelled
   * I expext something like "sudi" command not found did you mean:
sudo from package sudo (just like in Ubuntu)
But i just get:
Could not find the database of available applications, run 
update-command-not-found as root to fix this
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:

command-not-found version: 0.3
Python version: 3.7.3 final 0
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Exception information:

local variable 'cnf' referenced before assignment
Traceback (most recent call last):
  File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in 
crash_guard
callback()
  File "/usr/lib/command-not-found", line 93, in main
if not cnf.advise(args[0], options.ignore_installed) and not 
options.no_failure_msg:
UnboundLocalError: local variable 'cnf' referenced before assignment
allan@claro:~/Escritorio/Laboratorio$ sudo update-command-not-found
[sudo] password for allan: 
allan@claro:~/Escritorio/Laboratorio$ sudi
Could not find the database of available applications, run 
update-command-not-found as root to fix this
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:

command-not-found version: 0.3
Python version: 3.7.3 final 0
Distributor ID: Debian
Description:Debian GNU/Linux 10 (buster)
Release:10
Codename:   buster
Exception information:

local variable 'cnf' referenced before assignment
Traceback (most recent call last):
  File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in 
crash_guard
callback()
  File "/usr/lib/command-not-found", line 93, in main
if not cnf.advise(args[0], options.ignore_installed) and not 
options.no_failure_msg:
UnboundLocalError: local variable 'cnf' referenced before assignment

I already tried running "update-command-not-found" as root and doesn't make any 
output and gets same error message
Thanks in advance.

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

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

Versions of packages command-not-found depends on:
ii  apt-file 3.2.2
ii  lsb-release  10.2019051400
ii  python3  3.7.3-1
ii  python3-apt  1.8.4.1

command-not-found recommends no packages.

Versions of packages command-not-found suggests:
pn  snapd  

-- no debconf information

Bug#960646: Never mind

[Allan Wind]

This can be closed as an user error.

fail2ban is executing two statements and I was able to reproduce 
the non-descriptive error message "Could not process rule: No such 
file or directory'" by running:


nft add set inet filter f2b-sshd \{ type ipv4_addr\; \}

Then I ran the above command with ip instead of inet and it 
worked, and blocked ips were being added chains as verified

by :

nft list table inet filter

On a subsequent restart, fail2ban was now failing with the same
error message but now using ip instead of inet so I reverted the 
change I suggested initially and I was able to run the first 
command as is.


Then I ran the 2nd command:

nft insert rule inet filter INPUT meta l4proto tcp ip saddr @f2b-sshd
reject

and got the same useless error message as before.  I noticed 
earlier that `nft list table inet filter` had the chain
as lowercase input, so I tried that and it worked.  This the 
relevant jail.conf configuration:


[DEFAULT]
chain = input

Previously, I used chain = INPUT with iptables.  Hopefully this 
helps someone else as it had me stumped.

Bug#960646: fail2ban: nftables fails with Error: Could not process rule: No such file or directory

[Allan Wind]

Package: fail2ban
Version: 0.10.2-2.1
Severity: normal

Dear Maintainer,

I have been using fail2ban for a long time with iptables-allports:

banaction = iptables-allports
banaction = iptables-allports

With over 50k+ IPs being banned I figured that I might benefit from the
perceived lower overhead of nftables so changed it to:

banaction = nftables-allports
banaction_allports = nftables-allports

fail2ban was immediately reporting errors when I started it:

2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: Level 39 7f227a456760 -- exec: nft add 
set inet filter f2b-sshd \{ type ipv4_addr\; \}
nft insert rule inet filter INPUT meta l4proto tcp ip saddr @f2b-sshd 
reject
2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: ERROR   7f227a456760 -- stderr: 'Error: 
Could not process rule: No such file or directory'
2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: ERROR   7f227a456760 -- stderr: 'add 
set inet filter f2b-sshd { type ipv4_addr; }'
2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: ERROR   7f227a456760 -- stderr: ' 
^^'
2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: ERROR   7f227a456760 -- stderr: 'Error: 
Could not process rule: No such file or directory'
2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: ERROR   7f227a456760 -- stderr: 'insert 
rule inet filter INPUT meta l4proto tcp ip saddr @f2b-sshd reject'
2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: ERROR   7f227a456760 -- stderr: '  
   
^^'
2020-05-15T02:08:51.213+00:00 pawan fail2ban-server[21504]: 
fail2ban.utils  [21504]: ERROR   7f227a456760 -- returned 1

I found, through trial and error, that the issue appears to be
nftables_family = inet so I added action.d/nftables-common.local
file with:

[Init]
nftables_family = ip

Which seem to work.

Looked at the current upstream version and it's configuration file
is significantly different to the one that ships it buster to easily 
compare.  It does appear though, that they set to inet so not sure
what the deal is.

Happy to help,


/Allan

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

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

Versions of packages fail2ban depends on:
ii  lsb-base  10.2019051400
ii  python3   3.7.3-1

Versions of packages fail2ban recommends:
ii  iptables   1.8.2-4
ii  nftables   0.9.0-2
ii  python 2.7.16-1
ii  python3-pyinotify  0.9.6-1
ii  python3-systemd234-2+b1
ii  whois  5.4.3

Versions of packages fail2ban suggests:
ii  mailutils [mailx]   1:3.5-3
pn  monit   
ii  sqlite3 3.27.2-3
ii  syslog-ng-core [system-log-daemon]  3.19.1-5

-- Configuration Files:
/etc/fail2ban/fail2ban.conf changed:
[Definition]
loglevel = INFO
logtarget = SYSLOG
syslogsocket = auto
socket = /var/run/fail2ban/fail2ban.sock
pidfile = /var/run/fail2ban/fail2ban.pid
dbfile = /var/lib/fail2ban/fail2ban.sqlite3
dbpurgeage = 1d

/etc/fail2ban/filter.d/apache-common.conf changed:
[INCLUDES]
after = apache-common.local
[DEFAULT]

/etc/fail2ban/filter.d/postfix.conf changed:
[INCLUDES]
before = common.conf
[Definition]
_daemon = postfix/(submission/)?smtpd
failregex =
^%(__prefix_line)simproper command pipelining after \S+ from 
[^[]*\[\]:?$
^%(__prefix_line)slost connection after (AUTH|CONNECT) from 
.+\[\]$
^%(__prefix_line)sNOQUEUE: reject: RCPT from \S+\[\]: 450 4\.7\.1 
: Helo command rejected: Host not found; from=<> to=<> proto=ESMTP helo= *$
^%(__prefix_line)sNOQUEUE: reject: RCPT from \S+\[\]: 554 5\.7\.1 
.*$
^%(__prefix_line)sNOQUEUE: reject: VRFY from \S+\[\]: 550 5\.1\.1 
.*$
^%(__prefix_line)sSSL_accept error from .+\[\]: (-1|0)
^%(__prefix_line)swarning: .*\[\]: SASL LOGIN authentication 
failed: Invalid authentication mechanism
^%(__prefix_line)swarning: .+\[\]: SASL PLAIN authentication 
failed: Connection lost to authentication server
^%(__prefix_line)swarning: Connection concurrency limit exceeded: 
[0-9]+ from .+\[\] for service smtp$
^%(__prefix_line)swarning: non-SMTP command from.+\[\]:
^%(__prefix_line)swarning: numeric hostname: $
ignoreregex = 
 ^%(__prefix_line)slost connection after CONNECT from unknown\[unknown\]

/etc/fail2ban/filter.d/sshd.

Bug#960329: lightdm: Error getting user list from org.freedesktop.Accounts

[Allan Wind]

Package: lightdm
Version: 1.26.0-4
Severity: minor

Dear Maintainer,

accountsservice was using a lot of CPU on my system from time to 
time, so I purged it.  lightdm does not depend on accountsservice 
(like gdm3), but report errors if the package is not installed:


2020-05-11T19:01:03.247+00:00 vent lightdm[639]: Error getting user list from 
org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
2020-05-11T19:01:06.338+00:00 vent lightdm[746]: Error getting user list from 
org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
2020-05-11T19:01:11.217+00:00 vent lightdm[1069]: Error getting user list from 
org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files

I don't see anything in the lightdm configuration files that tells 
me how to disable the use of accountsservice to placate the error.  There
probably should be.  I don't have a use for .dmrc (re #690898) but 
presumably that would be a work-around.



/Allan

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

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

Versions of packages lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.16-1
ii  debconf [debconf-2.0]  1.5.71
ii  libaudit1  1:2.8.4-3
ii  libc6  2.28-10
ii  libgcrypt201.8.4-5
ii  libglib2.0-0   2.58.3-2+deb10u2
ii  libpam-systemd [logind]241-7~deb10u4
ii  libpam0g   1.3.1-5
ii  libxcb11.13.1-2
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.6-1
ii  lsb-base   10.2019051400

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.10-1
pn  xserver-xephyr   

-- debconf information:
 lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#960163: nvidia-driver: x86/modules: Skipping invalid relocation

[Allan Wind]

The good news is that I have the nvidia module working again,
and it's probably a weird edge case:

(1) nvidia-drivers version 418.113-1 is not compatible with linux 
   4.19.0-5 headers and fail to load with relocation error, and

(2) When I was running 4.19.0-9-amd64 (with nouveau),
   `dpkg-reconfigure nvidia-kernel-dkms` rebuild the nvidia 
   module against the -5 headers and they ended up in 
   /lib/modules/4.19.0-9-amd64 which failed to load (i.e. (1)).


Since my attempt yesterday, I purged the -5 kernel, and
`dpkg-reconfigure nvidia-kernel-dkms` now failed with missing
headers.  I then purged the -5 headers and installed the -9 
headers and upon reboot nvidia module was loaded.


I purged linux-image-amd64 a while ago when I explored 
kernel/nvidia combinations as possible work-around for another bug 
#905309 (and #922497).  This meant that I didn't get -9 and hit 
(1) when I thought I was doing a low-risk (stable) upgrade.


Re (1) I don't know _if_ or _how_ Debian should address this
actually, it's incompatibility with the combination of 
nvidia-driver 418.113-1 and linux-headers-4.19.0-5 that only shows 
up at run-time on the subsequent reboot.


Re (2) seems like a straight build defect.  If linux-image version 
x is installed then linux-headers x is used to build a module

for linux-image y (probably as a fallback).  This fails
with a pre-build check if linux-image x not installed.


/Allan

On 2020-05-11 00:29:37, Andreas Beckmann wrote:

On 10/05/2020 14.17, Allan Wind wrote:

No difference:

allan@vent:~$ uname -r
4.19.0-9-amd64


Please send dkms' make.log, probably located at
/var/lib/dkms/nvidia-current/418.113/4.19.0-9-amd64/x86_64/log/make.log

Please try the modules I built in a clean buster environment from
nvidia-kernel-source for the latest buster kernel: install
https://people.debian.org/~anbe/418.113/nvidia-kernel-4.19.0-9-amd64_418.113-1+4.19.118-2_amd64.deb
and remove nvidia-kernel-dkms (to remove the broken build; this will
remove make.log, too, so save it first)

If that works, something is broken in your environment w.r.t building
modules, but I'm not sure how to diagnose ... your gcc-10 experiments
could be related.

What do these commands say?
gcc-8 --version
ld --version


Andreas


--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#960163: nvidia-driver: x86/modules: Skipping invalid relocation

[Allan Wind]

I just saw your email (it went to my spam folder, sorry) and will 
try it shortly.  Meanwhile here is the data you requested:


allan@vent:~$ gcc-8 --version
gcc-8 (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  
There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR 
PURPOSE.


allan@vent:~$ ld --version
GNU ld (GNU Binutils for Debian) 2.31.1
Copyright (C) 2018 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the 
terms of
the GNU General Public License version 3 or (at your option) a 
later version.

This program has absolutely no warranty.

Not that it matters, particular, but I have build previous 
versions of the nvidia modules many times on this machine without
issue (other than the module not being compatible with -rt 
kernels).



/Allan

On 2020-05-11 00:29:37, Andreas Beckmann wrote:

On 10/05/2020 14.17, Allan Wind wrote:

No difference:

allan@vent:~$ uname -r
4.19.0-9-amd64


Please send dkms' make.log, probably located at
/var/lib/dkms/nvidia-current/418.113/4.19.0-9-amd64/x86_64/log/make.log

Please try the modules I built in a clean buster environment from
nvidia-kernel-source for the latest buster kernel: install
https://people.debian.org/~anbe/418.113/nvidia-kernel-4.19.0-9-amd64_418.113-1+4.19.118-2_amd64.deb
and remove nvidia-kernel-dkms (to remove the broken build; this will
remove make.log, too, so save it first)

If that works, something is broken in your environment w.r.t building
modules, but I'm not sure how to diagnose ... your gcc-10 experiments
could be related.

What do these commands say?
gcc-8 --version
ld --version


Andreas


--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#960163: nvidia-driver: x86/modules: Skipping invalid relocation

[Allan Wind]

No difference:

allan@vent:~$ uname -r
4.19.0-9-amd64

2020-05-10T12:05:03.404+00:00 vent kernel: module: x86/modules: 
Skipping invalid relocation target, existing value is nonzero for 
type 1, loc b6278525, val c1a0fa08   
2020-05-10T12:05:03.404+00:00 vent kernel: module: x86/modules: 
Skipping invalid relocation target, existing value is nonzero for 
type 1, loc 113efd9f, val c2cd3a08   



On 2020-05-10 08:03:53, Allan Wind wrote:
`apt install linux-image-amd64` to grab the current kernel, and 
I will report back after retesting.



/Allan

On 2020-05-10 13:52:47, Andreas Beckmann wrote:

That is not the current buster kernel (which would be 4.19.0-9).

Do you have any compiler/binutils/... installed that is not from buster?


Andreas


--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#960163: nvidia-driver: x86/modules: Skipping invalid relocation

[Allan Wind]

I think the answer is "no" re compiler/binutils.  I tried to 
remove gcc-base-10 but attempt unstall of a large number of

packages.  gcc-10-base contain no binaries.  The libraries are
needed by a /user/local/bin program.

allan@vent:~$ apt list --installed|grep -v '/stable'
gcc-10-base/now 10.1.0-1 amd64 [installed,local]
google-talkplugin/now 5.41.0.0-1 amd64 [installed,local]
libboost-program-options1.62.0/now 1.62.0+dfsg-10+b1 amd64 
[installed,local]

libboost-regex1.62.0/now 1.62.0+dfsg-10+b1 amd64 [installed,local]
libevent-2.0-5/now 2.0.21-stable-3 amd64 [installed,local]
libgcc-s1/now 10.1.0-1 amd64 [installed,local]
libstdc++6/now 10.1.0-1 amd64 [installed,local]
linux-headers-4.19.0-5-amd64/now 4.19.37-5+deb10u2 amd64 
[installed,local]
linux-headers-4.19.0-5-common/now 4.19.37-5+deb10u2 all 
[installed,local]
linux-image-4.19.0-5-amd64/now 4.19.37-5+deb10u2 amd64 
[installed,local]


`apt install linux-image-amd64` to grab the current kernel, and I 
will report back after retesting.



/Allan

On 2020-05-10 13:52:47, Andreas Beckmann wrote:

On 10/05/2020 06.02, Allan Wind wrote:

allan@vent:~$ cat /proc/version Linux version 4.19.0-5-amd64
(debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1
SMP Debian 4.19.37-5+deb10u2 (2019-08-08)


That is not the current buster kernel (which would be 4.19.0-9).

Do you have any compiler/binutils/... installed that is not from buster?


Andreas

Bug#960163: nvidia-driver: x86/modules: Skipping invalid relocation

[Allan Wind]

Package: nvidia-driver
Version: 418.113-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

I upgraded to 10.4 and on the subsequent reboot lightdm and X 
failed to start, and in syslog I found the following error 
message:


2020-05-10T03:28:57.914+00:00 vent kernel: module: x86/modules: 
Skipping invalid relocation target, existing value is  
nonzero for type 1, loc 08f75532, val c1819a08 
If I try to install the kernel module with `modprobe 
nvidia-current`, I get a similar error message.  Tried 
dpgk-reconfigure nvidia-driver and nvidia-kernel-dkms which 
rebuilds the module but it makes no difference after reboot.


I ran `apt purge nvidia-* libnvidia*` and found that after a 
reboot that I got X & lightdm running using the nouveau driver.


Reinstalled nvidia-driver and back to where I started. 
apt/history.log tells me that the 10.4 upgrade was this 
nvidia-driver change:


nvidia-driver:amd64 (418.74-1, 418.113-1)

allan@vent:~$ cat /proc/version 
Linux version 4.19.0-5-amd64 (debian-ker...@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u2 
(2019-08-08)


Happy to help.


/Allan

-- Package-specific info:
uname -a:
Linux vent 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 
GNU/Linux

/proc/version:
Linux version 4.19.0-5-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08)

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM206GLM [Quadro 
M2200 Mobile] [10de:1436] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo GM206GLM [Quadro M2200 Mobile] [17aa:2251]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: nvidia

dmesg:

Device node permissions:
video:x:44:allan,mona

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 May 10 03:29 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   51 May 10 03:29 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   50 May 10 03:29 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 May 10 03:29 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   57 May 10 03:29 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   57 May 10 03:29 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   54 May 10 03:29 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 May 10 03:29 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   44 May 10 03:29 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   44 May 10 03:29 
/etc/alternatives/glx--libGLX_indirect.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
lrwxrwxrwx 1 root root   38 May 10 03:29 
/etc/alternatives/glx--libglxserver_nvidia.so -> 
/usr/lib/nvidia/libglxserver_nvidia.so
lrwxrwxrwx 1 root root   51 May 10 03:29 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   42 May 10 03:29 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 May 10 03:29 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 May 10 03:29 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 May 10 03:29 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 May 10 03:29 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 May 10 03:29 /etc/alternatives/glx--nvidia_drv.so 
-> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   23 May 10 03:28 /etc/alternatives/nvidia -> 
/usr/lib/nvidia/current
lrwxrwxrwx 1 root root   59 May 10 03:28 
/etc/alternatives/nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/curr

Bug#956786: libdisplaymigration: Should this package be removed?

[Moray Allan]

On 2020-04-15 10:32, Simon McVittie wrote:

libdisplaymigration appears to be a shared library that is no longer
depended on by anything in Debian >= buster. It depends on GTK 2, which
was superseded by GTK 3 in 2011, and its popcon score declined rapidly
in the last 10 years.

Is this library still maintained upstream? Is it sufficiently useful
to justify having it in Debian for use as a dependency of third-party
software, or should it be removed?


I think it can be removed now, even if it's cute that the upstream 
source still contains packaging metadata for Familiar Linux.
( 
http://web.archive.org/web/20100723110955/http://familiar.handhelds.org/ 
)


Moray

Bug#940192: wine-development: msi regression, not installing dotnet35sp1

[Allan M. de Azevedo]

Jens,

I'm really sorry for all the mess that I'm causing with this bug report. But I 
have another unfortunate finding: I'm getting "MSI_OpenDatabaseW unknown flag 
(nil)" trying to install dotnet35sp1 in wine-4.0.2

When I made the bug report, the installer of Office 2007 SP3 was triggering the 
issue. When I saw that dotnet35sp1 was affected to, I changed the focus to this 
installer. At that time, the Office SP3 was installed successfully in 
wine-4.0.2 (Debian). I didn't tested dotnet35sp1.

I"ll try to explain this and summarize all the facts in upstream report.

Bug#940192: wine-development: msi regression, not installing dotnet35sp1

[Allan M. de Azevedo]

Hi jre,

First of all: sorry for my delay.

When I sent this bug report, I was using the 4.11-1 Debian package.
The dotnet35sp1 wasn't installing, returning that errors.

The upstream commit 7cd3c9f0734d217e1d08319e72a9df91fe2ef882 [1]
triggered the mingw issue, and this was between wine-4.10 and wine-4.11.

I just tested here with wine-4.16 (Debian 4.16-1) and the dotnet35sp1 install 
was unsuccessful.
$ env WINE=$(which wine-development) winetricks dotnet35sp1

So, it might be that my assumption is wrong for Debian package. When I posted 
my finding upstream, I was building wine from git in Arch Linux, and was able 
to install dotnet35sp1 from 4.15 that was previously failing.

[1] 
https://source.winehq.org/git/wine.git/commit/7cd3c9f0734d217e1d08319e72a9df91fe2ef882

Bug#940192: wine-development: msi regression, not installing dotnet35sp1

[Allan]

Package: wine-development
Version: 4.11-1
Severity: important

Dear Maintainer,

There's a msi issue in wine-4.11 (current wine-development/unstable) causing 
troble to Service Pack installers.

Example: try to install dotnet35sp1 and you will get these errors from terminal:
0030:err:msi:MSI_OpenDatabaseW unknown flag 
0030:err:msi:msi_apply_patch_package failed to open patch collection 
L"y:\\c5844c6052203b28ace1352bce70\\wcu\\dotNetFramework\\dotnetfx20\\ASPNET_64.msp"
0030:err:msi:ITERATE_Actions Execution halted, action 
L"CA_ScheduleCacheGACAssembly.3643236F_FC70_11D3_A536_0090278A1BB8" returned 
1627

Office 2007 SP3 installer fails too.

I already filed a bug report upstream[1] describing what commit causes the 
regression a week ago, but still "unconfirmed".

[1] https://bugs.winehq.org/show_bug.cgi?id=47724

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-development.

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

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

Versions of packages wine-development depends on:
ii  wine32-development  4.11-1
ii  wine64-development  4.11-1

wine-development recommends no packages.

Versions of packages wine-development suggests:
pn  dosbox
pn  exe-thumbnailer | kio-extras  
pn  playonlinux   
pn  q4wine
ii  winbind   2:4.9.13+dfsg-1
pn  wine-binfmt   
ii  winetricks0.0+20190912-1

Versions of packages wine-development is related to:
ii  fonts-wine  4.0.2-1
ii  wine-development4.11-1
ii  wine32-development  4.11-1
ii  wine64-development  4.11-1

-- no debconf information

Bug#934278: varnishlog: loaded failed failed

[Allan Wind]

Package: varnish
Version: 6.1.1-1+b1
Severity: normal

Dear Maintainer,

varnishlog fails to start on reboot:

2019-08-09T02:41:13.581+00:00 pawan varnishlog[784]: Starting HTTP 
accelerator log deamon: failed!
2019-08-09T02:41:13.581+00:00 pawan varnishlog[784]: 
2019-08-09T02:41:13.581+00:00 pawan varnishlog[784]: VSM: Could not get 
hold of varnishd, is it running?
2019-08-09T02:41:13.581+00:00 pawan systemd[1]: varnishlog.service: 
Control process exited, code=exited, status=1/FAILURE
2019-08-09T02:41:13.581+00:00 pawan systemd[1]: varnishlog.service: 
Failed with result 'exit-code'.
2019-08-09T02:41:13.581+00:00 pawan systemd[1]: Failed to start LSB: 
Start HTTP accelerator log daemon.

It appears to be a timing issue restarting it manually works fine:

systemctl restart varnishlog.service

root@pawan:/var/log# systemctl status varnishlog
● varnishlog.service - LSB: Start HTTP accelerator log daemon
   Loaded: loaded (/etc/init.d/varnishlog; generated)
   Active: active (running) since Thu 2019-08-08 22:55:15 EDT; 1min 5s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 6568 ExecStart=/etc/init.d/varnishlog start (code=exited, 
status=0/SUCCESS)
Tasks: 1 (limit: 4915)
   Memory: 1.2M
   CGroup: /system.slice/varnishlog.service
   └─6576 /usr/bin/varnishlog -a -w /var/log/varnish/varnish.log -D -P 
/run/varnishlog/varnishlog.pid

Aug 08 22:55:15 pawan systemd[1]: Starting LSB: Start HTTP accelerator log 
daemon...
Aug 08 22:55:15 pawan varnishlog[6568]: Starting HTTP accelerator log deamon:.
Aug 08 22:55:15 pawan systemd[1]: Started LSB: Start HTTP accelerator log 
daemon.

That said, I am not really sure this even works.  The only reference I see to
varnishlog is:

root@pawan:/# find /lib/systemd/ /etc -name varnishlog\*
/etc/systemd/system/multi-user.target.wants/varnishlog.service
/etc/default/varnishlog
/etc/init.d/varnishlog

and varnishlog.service is a dangling symlink to:

/lib/systemd/system/varnishlog.service

it seems to some type of left-over from a previous version:

dpkg -S varnishlog
varnish: /usr/bin/varnishlog
varnish: /etc/init.d/varnishlog
varnish: /usr/share/man/man1/varnishlog.1.gz
varnish: /etc/default/varnishlog

So I stopped the service the service and removed the file:

# systemctl disable varnishlog.service
# systemctl stop varnishlog.service
# rm /etc/systemd/system/multi-user.target.wants/varnishlog.service

I wanted to document this, but maybe there is a cleanup process missing
somewhere?


/Allan

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

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

Versions of packages varnish depends on:
ii  adduser   3.118
ii  gcc   4:8.3.0-1
ii  libc6 2.28-10
ii  libc6-dev [libc-dev]  2.28-10
ii  libedit2  3.1-20181209-1
ii  libjemalloc2  5.1.0-3
ii  libncursesw6  6.1+20181013-2
ii  libpcre3  2:8.39-12
ii  libtinfo6 6.1+20181013-2
ii  libvarnishapi26.1.1-1+b1
ii  lsb-base  10.2019051400

varnish recommends no packages.

Versions of packages varnish suggests:
pn  varnish-doc  

-- Configuration Files:
/etc/default/varnish changed:
START=yes
NFILES=131072
MEMLOCK=82000
DAEMON_OPTS="-a :6081 \
 -f /etc/varnish/default.vcl \
 -S /etc/varnish/secret \
 -s file,/var/lib/varnish/$(uname -n)/varnish_storage.bin,32G \
 -T localhost:6082 \
 -t 120"

/etc/default/varnishlog changed:
VARNISHLOG_ENABLED=1

/etc/logrotate.d/varnish changed:
/var/log/varnish/varnish.log {
compress
daily
delaycompress
missingok
postrotate
systemctl -q is-active varnishncsa.service &&
/usr/sbin/invoke-rc.d varnishncsa reload > /dev/null
systemctl -q is-active varnishlog.service &&
/usr/sbin/invoke-rc.d varnishlog reload > /dev/null
endscript
rotate 30
}

/etc/varnish/default.vcl changed:
vcl 4.0;
import std;
backend default {
.host = "127.0.0.1";
.port = "8080";
}
sub vcl_backend_response {
if (bereq.url ~ "^[^?]*\.(mp[34]|pdf|wav)(\?.*)?$") {
unset beresp.http.set-cookie;
set beresp.do_stream = true;
} else if (bereq.uncacheable) {
} else if (beresp.ttl <= 0s || beresp.http.Set-Cookie || 
beresp.http.Surrogate-control ~ "no-store" || (!beresp.http.Surrogate-Control 
&& beresp.http.Cache-Control ~ "no-cache|no-store|private") || beresp.http.Vary 

Bug#932858: smtp.montor: hostname() doesn't accept any arguments

[Allan Wind]

Package: mon
Version: 1.3.3-2
Severity: normal

Dear Maintainer,

smtp.montitor contains two two warnings from Sys::Hostname::hostname in
the Summary and Detail:

Summary: hostname() doesn't accept any arguments. This will become fatal in 
Perl 
5.32 at /usr/lib/mon/mon.d/smtp.monitor line 248. 

Detail: hostname() doesn't accept any arguments. This will become fatal 
in Perl 5.32 at /usr/lib/mon/mon.d/smtp.monitor line 181.

This is because the function is called as  which implicitly 
passed @_ (at call site), i.e. hostname(@_).  This defect is easy enough 
to fix, namely, change the two lines from:

$OurHostname = 

to:

$OurHostname = hostname();


/Allan

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

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

Versions of packages mon depends on:
ii  adduser  3.118
ii  libc62.28-10
ii  libtime-period-perl  1.25-1
ii  mon-client   1.2.0-2

Versions of packages mon recommends:
ii  bc   1.07.1-2+b1
ii  fping4.2-1
pn  libauthen-pam-perl   
ii  libcgi-pm-perl   4.40-1
pn  libcrypt-ssleay-perl 
ii  libfilesys-df-perl   0.92-6+b4
ii  libmail-imapclient-perl  3.42-1
ii  libnet-dns-perl  1.19-1
pn  libnet-ldap-perl 
ii  libnet-telnet-perl   3.04-1
ii  libproc-processtable-perl0.56-1
ii  libsnmp-perl 5.7.3+dfsg-5
ii  libstatistics-descriptive-perl   3.0702-1
pn  libtime-parsedate-perl   
ii  libtimedate-perl 2.3000-2
ii  perl-modules-5.24 [libnet-perl]  5.24.1-3+deb9u5
ii  swaks20181104.0-2

Versions of packages mon suggests:
ii  mon-contrib  1.0+dfsg-4

-- Configuration Files:
/etc/mon/auth.cf changed [not included]
/etc/mon/mon.cf [Errno 2] No such file or directory: '/etc/mon/mon.cf'

-- no debconf information

Bug#905309: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing

[Allan Wind]

I just observed this problem with (nvidia-kernel-dkms) 410.104-1.


/Allan
--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#905309: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing

[Allan Wind]

nvidia-driver 390.87 crashes the kernel on the host where I had 
this issue, so I think the technical correct answer is "unknown".


This is an intermittent issue, at times minutes apart, but mostly 
weeks or months.  Is the required hard reboot that really makes 
this awful.  If it helps, I can report back in 3 months on 
the unstable version currently 410.93-2.


On 2019-02-22 02:42:03, Andreas Beckmann wrote:

Control: tag -1 moreinfo upstream

On 2018-08-03 02:25, Allan Wind wrote:

Package: nvidia-driver
Version: 384.130-1



I noticed the fan on my laptop was spinning at full speed which
signifies heavy load.  Screens suspended, and they don't unsuspend when
I pressed the keyboard.  I ssh into the machine remotely, and see that
nvidia-modeset is using 100% cpu.  The only thing unusual in syslog is:

2018-08-02T22:49:34.702+00:00 vent kernel: nvidia-modeset: WARNING:
GPU:0: Lost display notification (0:0x); continuing.


Is this still reproducible with the 390.xx driver now in stretch?

Andreas


--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#922497: BUG: unable to handle kernel paging request at ffff9b30a7cb488

[Allan Wind]

Thanks Andreas.

I doubt NVIDIA will spend any cycles on troubleshooting issues 
with an older driver.


About a year ago I reported #905309 to the forum that NVIDIA says 
is the official support channel for Linux driver issues.  I never 
heard back.


The main reason why I filed the bug report was to document the 
workaround should anyone else hit this.  It is highly unusual

for a stable upgrade to cause an issue of this magnitude.


/Allan

On 2019-02-22 00:39:36, Andreas Beckmann wrote:

Control: tag -1 upstream

On 2019-02-17 07:40, Allan Wind wrote:

The stable release 9.8 contained an upgrade of nvidia-drivers from
384.130-1 to 390.87-8~deb9u1 which caused my system hang during
subsequent boots.  The release also contains a linux-image update, and I
installed a known working kernel (4.9.0-5) and it too failed to boot
with 390.87-8~deb9u1. Then I upgraded nividia-driver to the version in
unstable, and I was able to boot my system.  Unfortunately, this is the
version information being picked up in this bug report.


There haven't been similar reports with the 390.xx driver from
stretch-backports or with the 390.xx driver in sid (with newer kernels
than 4.9) - maybe it is specific to your card. Or some other hardware.

There is nothing we can do about bugs in the proprietary driver. And I
expect you don't want to try reporting this upstream - since you have a
working configuration now, and getting useful information if the system
fails to boot is difficult.


Andreas


--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#922497: BUG: unable to handle kernel paging request at ffff9b30a7cb488

[Allan Wind]

d_core nvme_core usbcore usb_common thermal wmi video i2c_hid hid button
2019-02-17T04:48:54.181+00:00 vent kernel: CPU: 2 PID: 1164 Comm: ps Tainted: P 
 DO4.9.0-8-amd64 #1 Debian 4.9.144-3
2019-02-17T04:48:54.181+00:00 vent kernel: Hardware name: LENOVO 
20HHCTO1WW/20HHCTO1WW, BIOS N1UET37W (1.11 ) 07/24/2017
2019-02-17T04:48:54.181+00:00 vent kernel: task: 9d97a99c6040 task.stack: 
bf5a46db
2019-02-17T04:48:54.181+00:00 vent kernel: RIP: 0010:[]  
[] native_queued_spin_lock_slowpath+0x170/0x190
2019-02-17T04:48:54.181+00:00 vent kernel: RSP: 0018:bf5a46db3d68  EFLAGS: 
0202
2019-02-17T04:48:54.181+00:00 vent kernel: RAX: 0101 RBX: 
9d979cc6e0b8 RCX: 0001
2019-02-17T04:48:54.181+00:00 vent kernel: RDX: 0101 RSI: 
0001 RDI: 9d97a28a57a0
2019-02-17T04:48:54.181+00:00 vent kernel: RBP: bf5a46db3d90 R08: 
0101 R09: 0001
2019-02-17T04:48:54.181+00:00 vent kernel: R10: bf5a46db3e43 R11: 
9d97a792b840 R12: 9d97a28a5080
2019-02-17T04:48:54.181+00:00 vent kernel: R13: 9d97a28a57a0 R14: 
bf5a46db3ed0 R15: 
2019-02-17T04:48:54.181+00:00 vent kernel: FS:  7fcc5ff4d880() 
GS:9d97f3c8() knlGS:
2019-02-17T04:48:54.181+00:00 vent kernel: CS:  0010 DS:  ES:  CR0: 
80050033
2019-02-17T04:48:54.181+00:00 vent kernel: CR2: 562644ecf000 CR3: 
0010153fe000 CR4: 00360670
2019-02-17T04:48:54.181+00:00 vent kernel: DR0:  DR1: 
 DR2: 
2019-02-17T04:48:54.181+00:00 vent kernel: DR3:  DR6: 
fffe0ff0 DR7: 0400
2019-02-17T04:48:54.181+00:00 vent kernel: Stack:
2019-02-17T04:48:54.181+00:00 vent kernel:  aec1916d ae87ee9b 
9d97a792b840 0003
2019-02-17T04:48:54.182+00:00 vent kernel:  ae87ef00 bf5a46db3e43 
ae87ef16 9d97b30023c0
2019-02-17T04:48:54.182+00:00 vent kernel:  bf5a46db3e43 ae87f667 
9d97a792b840 000332988e19
2019-02-17T04:48:54.182+00:00 vent kernel: Call Trace:
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
_raw_spin_lock+0x1d/0x20
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
proc_pid_make_inode+0x7b/0xe0
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
proc_pid_make_inode+0xe0/0xe0
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
proc_pid_instantiate+0x16/0xc0
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
proc_fill_cache+0x117/0x180
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
proc_pid_readdir+0xde/0x210
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
iterate_dir+0x177/0x1a0
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
SyS_getdents+0x98/0x120
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
fillonedir+0xe0/0xe0
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
do_syscall_64+0x8d/0xf0
2019-02-17T04:48:54.182+00:00 vent kernel:  [] ? 
entry_SYSCALL_64_after_swapgs+0x58/0xc6
2019-02-17T04:48:54.182+00:00 vent kernel: Code: d0 66 31 c0 41 39 c0 74 e6 4d 85 c9 c6 07 01 74 2d 41 c7 41 08 01 00 00 00 e9 53 ff ff ff 83 fa 01 74 17 8b 07 84 c0 74 08 f3 90 <8b> 07 84 c0 75 f8 b8 01 00 00 00 66 89 07 c3 f3 c3 f3 90 4c 8b 


-- Package-specific info:
uname -a:
Linux vent 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019-02-02) x86_64 GNU/Linux

/proc/version:
Linux version 4.9.0-8-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.144-3 (2019-02-02)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  410.93  Thu Dec 20 17:01:16 CST 
2018
GCC version:  gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) 


lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1436] 
(rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:2251]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Feb 17 00:37 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Feb 17 00:37 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Feb 17 00:37 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Feb 17 00:37 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Feb 17 00:37 /dev/nvidiactl
video:x:44:allan,mona

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Feb 17 00:36 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 Feb 17 00:35 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   51 Feb 17 00:36 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEG

Bug#919577: g++-8: Can't build GN tool due to bug in raw-string parsing

[Allan Sandfeld Jensen]

On Donnerstag, 17. Januar 2019 14:09:21 CET Matthias Klose wrote:
> Control: tags -1 + moreinfo
> Control: severity -1 normal
> 
> works for me.
> 
Try with -E -fdirectives-only. 

I suspect it the same as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88475

Which means the reason I couldn't reproduce with gcc trunk was only because I 
didn't launch that through icecc, which makes it an upstream and not debian 
bug.

'Allan

Bug#919577: g++-8: Can't build GN tool due to bug in raw-string parsing

[Allan Sandfeld Jensen]

Package: g++-8
Version: 8.2.0-14
Severity: serious

Can not compile code with something looking like a precompiler directive inside
a raw-string. For instance code like this:

const char kFormat_Help[] =
R"(gn format [--dump-tree] (--stdin | )

  Formats .gn file to a standard format.

  The contents of some lists ('sources', 'deps', etc.) will be sorted to a
  canonical order. To suppress this, you can add a comment of the form "#
  NOSORT" immediately preceding the assignment. e.g.

  # NOSORT
  sources = [
"z.cc",
"a.cc",
  ]
)";

The compiler complains it doesn't understand the #NOSORT directive.

I can not reproduce the issue with upstream g++-8 or with g++-7, it appears to 
be a serious
flaw in specifically this Debian version of g++-8.

-- 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.19.0-1-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_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages g++-8 depends on:
ii  gcc-88.2.0-14
ii  gcc-8-base   8.2.0-14
ii  libc62.28-5
ii  libgmp10 2:6.1.2+dfsg-4
ii  libisl19 0.20-2
ii  libmpc3  1.1.0-1
ii  libmpfr6 4.0.2~rc1-1
ii  libstdc++-8-dev  8.2.0-14
ii  zlib1g   1:1.2.11.dfsg-1

g++-8 recommends no packages.

Versions of packages g++-8 suggests:
ii  g++-8-multilib8.2.0-14
pn  gcc-8-doc 
pn  libstdc++6-8-dbg  

-- no debconf information

Bug#912237: /etc/init.d/rpcbind: stat: not found

[Allan Jensen]

On Mon, 29 Oct 2018 16:20:06 +0100 Laurent Bigonville  wrote:
> Package: rpcbind
> Version: 1.2.5-0.1
> Severity: important
> 
> Hi,
> 
> So according to [0], the LSB initscript fails to start rpcbind because
> it looks for "stat" command that is not in the path, PATH is
> explicitly set to PATH='/sbin:/bin' because it's possible that /usr is
> on a NFS share and rpcbind is needed to mount NFS shares...
> 
> An idea what to do here? The initrd is supposed to mount /usr now I
> believe, so is it now OK to change the PATH to
> "/sbin:/bin:/usr/sbin:/usr/bin"?

How about using ls and grep, which are both in /bin?

Something like

   if [ `ls -dl "$STATEDIR" | grep -cE '^drwxr-xr-x [0-9]+ _rpc root '` -lt 1 ] 
; then

--
Regards
Allan

Bug#912746:

[allan]

Issue seems to have resolved itself on both machines.  Please feel free to
close this bug.  Thank you -

Bug#912746: volumeicon-alsa: volumeicon causes machine to overheat

[allan grossman]

Package: volumeicon-alsa
Version: 0.5.1+git20170117-1
Severity: grave
Justification: renders package unusable

dear maintainer,

Ran apt full-upgrade this morning; had been holding off because of Perl upgrade
but apt said I was good to go this morning.

After rebooting both machines (both Dell Precision laptops, one first-gen and
one fourth-gen i7) for a kernel upgrade I noticed CPU temps above 85°C.

Ran glances to find out what the problem was and found a single core running at
100% on both machines.  Killed volumeicon on both machines and temps returned
to normal.  Restarting volumeicon caused temps to rise again.



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

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

Versions of packages volumeicon-alsa depends on:
ii  libasound2  1.1.7-1
ii  libc6   2.27-8
ii  libcairo2   1.16.0-1
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-6
ii  libglib2.0-02.58.1-2
ii  libgtk-3-0  3.24.1-2
ii  libnotify4  0.7.7-3
ii  libx11-62:1.6.7-1

volumeicon-alsa recommends no packages.

Versions of packages volumeicon-alsa suggests:
pn  alsamixergui | aumix-gtk | kmix | gnome-alsamixer  
pn  notify-osd | xfce4-notifyd | notification-daemon   

-- no debconf information

Bug#905309: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing

[Allan Wind]

Package: nvidia-driver
Version: 384.130-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I noticed the fan on my laptop was spinning at full speed which 
signifies heavy load.  Screens suspended, and they don't 
unsuspend when I pressed the keyboard.  I ssh into the machine 
remotely, and see that nvidia-modeset is using 100% cpu.  The 
only thing unusual in syslog is:


2018-08-02T22:49:34.702+00:00 vent kernel: nvidia-modeset: 
WARNING: GPU:0: Lost display notification (0:0x); 
continuing.


sysstat suggest load went up shortly before 21:25 UTC (100% on 1 
cpu of 8 is 12.50%)


12:00:01 AM CPU %user %nice   %system   %iowait
%steal %idle

...
08:45:01 PM all  4.21  0.00  0.38  0.02  
0.00 95.39
08:55:01 PM all  0.42  0.00  0.06  0.00  
0.00 99.52
09:05:01 PM all  0.09  0.00  0.05  0.01  
0.00 99.85
09:15:01 PM all  0.07  0.00  3.35  0.01  
0.00 96.57
09:25:01 PM all  0.06  0.82 12.58  0.01  
0.00 86.53
09:35:01 PM all  0.06  0.00 12.63  0.00  
0.00 87.30
09:45:01 PM all  0.07  0.00 12.68  0.01  
0.00 87.24


I initiated a reboot via ssh, but my system was still hanging 
after a few minutes.  Hard power cycled laptop to restore 
service.


I have had similar issues in the past but never narrowed it down 
to the process.  At best this is intermittent, maybe, months 
apart.  Happy to provide additional data next time this happens.  
What would be helpful?


-- Package-specific info:
uname -a:
Linux vent 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 
GNU/Linux

/proc/version:
Linux version 4.9.0-5-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
GCC version:  gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) 


lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1436] 
(rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:2251]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Aug  2 19:49 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Aug  2 19:49 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Aug  2 19:49 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Aug  2 19:49 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Aug  2 19:49 /dev/nvidiactl
video:x:44:allan,mona

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Jul  6  2017 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   44 Jul  6  2017 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   43 Jul  6  2017 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   43 Jul  6  2017 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   50 Jul  6  2017 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   50 Jul  6  2017 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   47 Jul  6  2017 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   47 Jul  6  2017 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   51 Jul  6  2017 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Jul  6  2017 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Jul  6  2017 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Jul  6  2017 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Jul  6  2017 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Jul  6  2017 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxr

Bug#900031: linux-image-4.9.0-7-amd64 4.9.110-1

[Allan Wind]

Dear Maintainer,

As indicated earlier I reverted to -5, and it has been stable for 
a few months for me (i.e. since ~2018-5-20 localtime).  With the 
recent upgrade to stable, I upgraded to -7 and rebooted 
yesterday.  Today I got my first kernel issues, and including 
them here in case it is useful.  Reverting to -5 again.


- Forwarded message from r...@lifeintegrity.com -

Date: Thu, 19 Jul 2018 03:41:37 + (UTC)
From: r...@lifeintegrity.com
To: r...@lifeintegrity.com
Subject: syslog: vent kernel: [ cut here ]
X-Bogosity: Ham, tests=bogofilter, spamicity=0.00, version=1.2.4

2018-07-19T03:41:07.707+00:00 vent kernel: [ cut here ]
2018-07-19T03:41:07.707+00:00 vent kernel: WARNING: CPU: 6 PID: 369 at 
/build/linux-tolFob/linux-4.9.110/drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1648
 iwl_mvm_report_scan_aborted+0x217/0x230 [iwlmvm]
2018-07-19T03:41:07.707+00:00 vent kernel: UMAC scan UID 0 status was not 
cleaned
2018-07-19T03:41:07.707+00:00 vent kernel: Modules linked in: fuse uvcvideo 
videobuf2_vmalloc videobuf2_memops snd_usb_audio videobuf2_v4l2 snd_usbmidi_lib 
videobuf2_core snd_rawmidi snd_seq_device videodev btusb btrtl btbcm btintel 
media bluetooth thinkpad_acpi nvram binfmt_misc nls_ascii nls_cp437 vfat fat 
arc4 i2c_designware_platform i2c_designware_core iwlmvm mac80211 
snd_hda_codec_realtek snd_hda_codec_generic iwlwifi intel_rapl rtsx_pci_ms 
cfg80211 snd_hda_intel x86_pkg_temp_thermal memstick intel_powerclamp 
snd_hda_codec rfkill coretemp snd_hda_core kvm_intel snd_hwdep efi_pstore kvm 
joydev idma64 irqbypass snd_pcm snd_timer crct10dif_pclmul iTCO_wdt 
crc32_pclmul mei_me snd pcspkr efivars serio_raw soundcore iTCO_vendor_support 
intel_lpss_pci ghash_clmulni_intel mei intel_lpss shpchp ac battery evdev 
acpi_pad nvidia_drm(PO)
2018-07-19T03:41:07.707+00:00 vent kernel:  drm_kms_helper drm 
nvidia_modeset(PO) nvidia(PO) parport_pc ppdev lp parport efivarfs ip_tables 
x_tables autofs4 hid_generic ext4 crc16 usbhid jbd2 crc32c_generic fscrypto ecb 
mbcache rtsx_pci_sdmmc mmc_core crc32c_intel aesni_intel aes_x86_64 glue_helper 
lrw gf128mul ablk_helper cryptd psmouse e1000e ptp pps_core i2c_i801 i2c_smbus 
rtsx_pci nvme xhci_pci mfd_core nvme_core xhci_hcd usbcore usb_common thermal 
wmi video i2c_hid hid button
2018-07-19T03:41:07.707+00:00 vent kernel: CPU: 6 PID: 369 Comm: 
irq/330-iwlwifi Tainted: P   O4.9.0-7-amd64 #1 Debian 4.9.110-1
2018-07-19T03:41:07.707+00:00 vent kernel: Hardware name: LENOVO 
20HHCTO1WW/20HHCTO1WW, BIOS N1UET37W (1.11 ) 07/24/2017
2018-07-19T03:41:07.707+00:00 vent kernel:   ac130644 
b15886d6bd28 
2018-07-19T03:41:07.707+00:00 vent kernel:  abe78d6e 9481ead8 
b15886d6bd80 9481eada9528
2018-07-19T03:41:07.707+00:00 vent kernel:  c19c73d0 8200 
9481e667a0c0 abe78def
2018-07-19T03:41:07.708+00:00 vent kernel: Call Trace:
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
dump_stack+0x5c/0x78
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
__warn+0xbe/0xe0
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
warn_slowpath_fmt+0x5f/0x80
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
iwl_mvm_report_scan_aborted+0x217/0x230 [iwlmvm]
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
__wake_up+0x34/0x50
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
iwl_mvm_nic_restart+0x20/0x130 [iwlmvm]
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
iwl_pcie_irq_handle_error+0xe3/0x160 [iwlwifi]
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
iwl_pcie_irq_handler+0x370/0x730 [iwlwifi]
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
irq_finalize_oneshot.part.36+0xf0/0xf0
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
irq_thread_fn+0x21/0x50
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
irq_thread+0x134/0x1d0
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
__schedule+0x241/0x6f0
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
__wake_up_common+0x4f/0x90
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
irq_forced_thread_fn+0x70/0x70
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
irq_thread_check_affinity+0xd0/0xd0
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
kthread+0xd9/0xf0
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
__switch_to_asm+0x34/0x70
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
kthread_park+0x60/0x60
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
SyS_exit_group+0x10/0x10
2018-07-19T03:41:07.708+00:00 vent kernel:  [] ? 
ret_from_fork+0x57/0x70
2018-07-19T03:41:07.708+00:00 vent kernel: ---[ end trace 30255ea5463708df ]---


- End forwarded message -

--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#900031: linux-image-4.9.0-6-amd64: task blocked for more than 120 seconds

[Allan Wind]

er- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

3e:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd 
Device [144d:a804] (prog-if 02 [NVM Express])
Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvme
Kernel modules: nvme

3f:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader [10ec:525a] (rev 01)
Subsystem: Lenovo RTS525A PCI Express Card Reader [17aa:224d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci


** USB devices:
Bus 002 Device 004: ID 045b:0210 Hitachi, Ltd 
Bus 002 Device 003: ID 045b:0210 Hitachi, Ltd 
Bus 002 Device 002: ID 045b:0210 Hitachi, Ltd 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
Bus 001 Device 003: ID 04ca:7066 Lite-On Technology Corp. 
Bus 001 Device 012: ID 29ea:0102  
Bus 001 Device 010: ID 2a39:3fb0  
Bus 001 Device 008: ID 045b:0209 Hitachi, Ltd 
Bus 001 Device 006: ID 045b:0209 Hitachi, Ltd 
Bus 001 Device 004: ID 5332:1300  
Bus 001 Device 002: ID 045b:0209 Hitachi, Ltd 
Bus 001 Device 011: ID 8087:0a2b Intel Corp. 
Bus 001 Device 009: ID 0765:5010 X-Rite, Inc. 
Bus 001 Device 007: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


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

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

Versions of packages linux-image-4.9.0-6-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.9.0-6-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.9.0-6-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.02~beta3-5
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-6-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
ii  firmware-iwlwifi  20161130-3
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

--
Allan Wind
Yaxto - Runs Your Business
<https://yaxto.com>

Bug#884350: To my account activation pls

[Allan rey Quiban]

Sent from my iPhone

Bug#835553:

[allan]

Confirmed still broken in Sid.  Disabling MAC randomization in NM also
resolved the issue for me.

Bug#878032: postgresql: apt-get purge of 9.4 removed service for 9.6

[Allan Wind]

Package: postgresql
Version: 9.6+181
Severity: normal

Dear Maintainer,

I recently upgraded my server which pulled in 9.6.  Then I manually 
migrated the configuration and data and then I purged the old version 
with:

# apt-get purge postgresql-9.4  postgresql-client-9.4 postgresql-contrib-9.4 
postgresql-doc-9.4

Surprisingly that also stopped my 9.6 instance and the service disappeared:
disappeared:

# systemctl |grep postgresql
  system-postgresql.slice   
 loadedactive active
system-postgresql.slice

To restore service, I did

# dpkg-reconfigure postgresql-9.6
# systemctl |grep postgresql
  postgresql.service
 loadedactive exited
PostgreSQL RDBMS
  postgresql@9.6-main.service   
 loadedactive running   
PostgreSQL Cluster 9.6-main
  system-postgresql.slice   
 loadedactive active
system-postgresql.slice

To me this appears to be defective, and apologize if I missed an existing
report or if this should be filed against another package.

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

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

Versions of packages postgresql depends on:
ii  postgresql-9.6  9.6.4-0+deb9u1

postgresql recommends no packages.

Versions of packages postgresql suggests:
ii  postgresql-doc  9.6+181

-- no debconf information

Bug#874369: chromium-widevine missing libwidevinecdm.so

[Allan Sandfeld Jensen]

Package: chromium-widevine
Version: 60.0.3112.78-1
Severity: important

The chromium-widevine package is missing libwidevinecdm.so which 
libwidevinecdmadapter.so
is the wrapper around, and needs to link to in order to work.

The chromium-widevine package is non functional and serves no purpose without 
it.

Note both of the files in question like the pepper flashplugin are proprietary 
binary blobs
and only available through chrome, they are not built with or shipped with 
chromium sources.

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

Kernel: Linux 4.12.0-1-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_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium-widevine depends on:
ii  chromium60.0.3112.78-1
ii  libc6   2.24-14
ii  libstdc++6  7.2.0-1

chromium-widevine recommends no packages.

chromium-widevine suggests no packages.

-- no debconf information

Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Allan Sandfeld Jensen]

On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> 
> That's Qt's fault for not taking care of EventListenerRegistered
> signals to determine whether someone is listening.
> 
So it is Qt's fault that is doing what you have told it to do? You have set 
the environment variable to ignore the absence of listeners. That is what 
QT_LINUX_ACCESSIBILITY_ALWAYS_ON does. It is an override for embedded 
applications which need to send accesibility events but for some reason can't 
autodetect the presence of a listener.

> > Note the performance impact is the same in all applications regardless of
> > framework.
> 
> No. Gtk sends only basic events (application creation notification,
> basically) when there is no screen reader.
> 
So does Qt by default, but you are forcing a special override around that. 

'Allan

Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Allan Sandfeld Jensen]

On Sonntag, 3. September 2017 20:23:30 CEST Samuel Thibault wrote:
> Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:19:31 +0200, wrote:
> > On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote:
> > > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote:
> > > 
> > > That's Qt's fault for not taking care of EventListenerRegistered
> > > signals to determine whether someone is listening.
> > 
> > So it is Qt's fault that is doing what you have told it to do? You have
> > set
> > the environment variable to ignore the absence of listeners. That is what
> > QT_LINUX_ACCESSIBILITY_ALWAYS_ON does.
> 
> Ah?  That's not what I had gotten in my tests.  I'll check again, then.
> 
> The question of flurry of events is still there, and does matter for
> screen readers.  Avoiding to expose the issue to users without a screen
> reader is a bit hiding it under the carpet.
> 
True. Note, the case where I saw the largest performance impact was not moving 
the cursor, it was self-modifying web-content, it would send every text change 
in the active focus. The events came from Chromium, which is used in 
QtWebEngine, but it is not code I have written, just Chromiums default 
accesibility implementation. We have already worked around it in 5.9.2, as it 
was almost useless and already disabled in the standard linux builds of 
Chromium (probably because of the how badly it behaves), and firefox didn't 
send similar events either on Linux. But it is what Chrome would send on macOS 
and Windows when a screen-reader is detected as active.

'Allan

Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

[Allan Sandfeld Jensen]

On Sonntag, 3. September 2017 18:15:15 CEST Samuel Thibault wrote:
> On the long run, it really should.  Just hiding issues is not the way
> forward :)
> 
> Also, note that if the performance is so bad, it means something *needs*
> to be fixed, otherwise blind users will get the bad performance, and
> nobody will be there to fix it, because nobody notices it except blind
> users, who are left with little hope to fix it by themselves.

It is not a issue or a bug. The performance impact comes from sending 
everything the mouse hovers over to the accessibility framework (for instance 
to be spoken aloud), when there is not any accessibility tools running.

You are deliberately crippling Qt to always send dbus events even when no one 
is listening.

Note the performance impact is the same in all applications regardless of 
framework. Running accessibility tools has a substantional performance cost on 
mouse movements, but a mouse rendered or text scrolling at 60 fps is 
completely pointless to blind people, but rather important to everybody else.

'Allan

Bug#873573: avahi-daemon: packet loss

[Allan Wind]

Package: avahi-daemon
Version: 0.6.32-2
Severity: important

Dear Maintainer,

I installed Debian 9.1 on a Lenovo P50 and with no customizations other
than what the installer afforded me I was observing packet loss every
few minutes.  ssh to this host would hang for seconds to minutes at a
time, say, every few minutes.  I installed mtr on a remote host, and
within 200 to 250 packets it would report significant packet loss.
tcpdump showed that ping packets were not being received on this host
for almost a minute.  tcpdump from remote host showed pings being sent
every second but no response.  I duplicated packet loss with a 3rd
remote host. Replaced the cable and switch between this and remote host,
and were still able to reproduce the issue.

By chance, I booted this host into recovery mode, and added my ethernet
interface to /etc/network/interfaces then systemctl start networking.
Then retried the mtr scenario and found no packet loss.  I then
bi-sected between recovery (rescue.target?) and graphical.target to
determine that if I did not start avahi-daemon or services that depends
on it I would not be seeing packet loss along these lines (commented out
lines would cause packet loss):

#!/bin/bash
systemctl start basic.target
systemctl start anacron.service
systemctl start apache2.service
#systemctl start avahi-daemon.service
systemctl start console-setup.service
systemctl start cron.service
#systemctl start cups-browsed.service
#systemctl start cups.path
systemctl start dbus.service
systemctl start hddtemp.service
systemctl start lm-sensors.service
systemctl start ModemManager.service
systemctl start networking.service
systemctl start NetworkManager.service
systemctl start pppd-dns.service
systemctl start rsyslog.service
systemctl start speech-dispatcher.service
systemctl start ssh.service
systemctl start systemd-ask-password-wall.path
systemctl start systemd-logind.service
systemctl start systemd-update-utmp-runlevel.service
systemctl start systemd-user-sessions.service

Finally, I apt-get pruge avahi-daemon and rebooted and not seeing any
packet loss since.

ifconfig did not show any errors on this or rmeote end.


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

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

Versions of packages avahi-daemon depends on:
ii  adduser  3.115
ii  bind9-host [host]1:9.10.3.dfsg.P4-12.3+deb9u2
ii  dbus 1.10.18-1
ii  host 1:9.10.3.dfsg.P4-12.3+deb9u2
ii  init-system-helpers  1.48
ii  libavahi-common3 0.6.32-2
ii  libavahi-core7   0.6.32-2
ii  libc62.24-11+deb9u1
ii  libcap2  1:2.25-1
ii  libdaemon0   0.14-6
ii  libdbus-1-3  1.10.18-1
ii  libexpat12.2.0-2+deb9u1
ii  lsb-base 9.20161125

Versions of packages avahi-daemon recommends:
ii  libnss-mdns  0.10-8

Versions of packages avahi-daemon suggests:
ii  avahi-autoipd  0.6.32-2

-- no debconf information

Bug#866102: calibre: Calibre-server fails to start with missing dependancy

[allan grossman]

Package: calibre
Version: 3.1.1+dfsg-1
Followup-For: Bug #866102

Dear Maintainer,

   * What led up to the situation?

calibre fails to start if autolaunch_server = True in ~/.config/calibre/gui.py

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

Disabled server autolaunch, which allowed calibre to start.  After reading bug
report referenced here, installed python-msgpack.

   * What was the outcome of this action?

Installing python-msgpack resolved the issue and server now autostarts and
calibre appears to run normally.



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

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

Versions of packages calibre depends on:
ii  calibre-bin  3.1.1+dfsg-1
ii  fonts-liberation 1:1.07.4-2
ii  imagemagick  8:6.9.7.4+dfsg-11
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-11
ii  libjs-coffeescript   1.10.0~dfsg-1
ii  libjs-mathjax2.7.0-2
ii  poppler-utils0.48.0-2
ii  python-apsw  3.16.2-r1-2
ii  python-beautifulsoup 3.2.1-1
ii  python-chardet   3.0.4-1
ii  python-cherrypy3 3.5.0-2
ii  python-cssselect 1.0.1-1
ii  python-cssutils  1.0-4.1
ii  python-dateutil  2.5.3-2
ii  python-dbus  1.2.4-1+b1
ii  python-feedparser5.1.3-3
ii  python-lxml  3.8.0-1
ii  python-markdown  2.6.8-1
ii  python-mechanize 1:0.2.5-3
ii  python-netifaces 0.10.4-0.1+b2
ii  python-pil   4.0.0-4
ii  python-pkg-resources 36.0.1-1
ii  python-pyparsing 2.1.10+dfsg1-1
ii  python-pyqt5 5.7+dfsg-5
ii  python-pyqt5.qtsvg   5.7+dfsg-5
ii  python-pyqt5.qtwebkit5.7+dfsg-5
ii  python-regex 0.1.20170117-1
ii  python-routes2.3.1-2
ii  python2.72.7.13-2
ii  xdg-utils1.1.1-1

Versions of packages calibre recommends:
pn  python-dnspython  

calibre suggests no packages.

-- no debconf information

Bug#864153: debian-installer-9-netboot-amd64: debian mini-iso manual partitioning option does not allow selecting disks

[allan grossman]

Package: debian-installer-9-netboot-amd64
Severity: important
Tags: d-i

Dear Maintainer,

When installing Debian Unstable from mini-iso the manual partitioner does not
allow you to select which disk to partition.  It would only allow me to
partition the flash drive from which I booted the installer.

Guided partitioning allowed me to select the correct disk, but the manual
installer should be able to select a disk other than the one booted from.



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

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

debian-installer-9-netboot-amd64 depends on no packages.

debian-installer-9-netboot-amd64 recommends no packages.

Versions of packages debian-installer-9-netboot-amd64 suggests:
pn  tftpd-hpa  

Bug#863274: Point out web interface better to new bug reporters

[Moray Allan]

Package: bugs.debian.org
Severity: wishlist

New bug reporters using reportbug in a typical configuration receive a
mail copy of their own bug report that already contains the bug
number.  However, there is no clue given that this number can be used
to track the bug status by a web interface.

The second message a submitter receives, automatically responding to
the bug report, does include a URL.  However, this is in a footer
below the main message, where it can easily be missed.  In addition,
Google Gmail hides this footer by default when the message is viewed,
and also assigns this acknowledgement message to a spam/advertising
folder.  (While I don't use Gmail myself, very many of our users do.)

It would be helpful to provide bug submitters a more prominent pointer
to the BTS web interface.  Ideally for users who submit bugs using the
bugs.debian.org SMTP server, there would already be a prominent URL
(and a few words of explanation) at the top of the mail copy they
receive of their submitted bug.

Thanks,

Moray

Bug#650784: wiki.debian.org: new page does not show up in search; indexing broken?

[Moray Allan]

In 2011, Steve Langasek wrote:

I've recently added a page to the Debian wiki,
, that was based on
.  I created a new page
specifically so that it would turn up better in likely search results.

However, when searching page titles for 'build package', 'package 
build',
'building package', and 'building', various other pages are returned 
but
this page is not.  I suspect that some search index is not being 
updated

properly, because I can't see any other relevant difference between the
pages that are returned in the search results and this one.


This page still doesn't show up in related title searches.

Searching titles for 'package building' gives: '"Your search query 
"package building" didn't return any results. Please change some terms 
and refer to HelpOnSearching for more information.'


Searching titles for "building" gives 19 results, but the list doesn't 
contain the page in question.


The page does get listed (among 3 pages) when searching titles directly 
for "buildingapackage".


Moray

Bug#684380: Bug #684380: MaintainerScripts: small mistake in upgrade diagram

[Moray Allan]

Hi Marga,

Cleaning up some things, I noticed an old bug report against your 
maintainer scripts diagrams at

https://wiki.debian.org/MaintainerScripts :

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684380

Perhaps you can reply if you still have the diagram sources or if you 
think that the diagram is correct already?


Thanks,

Moray

Bug#800831: Bug#800830: missing pre-gap and index mark data

[Moray Allan]

Hi Daniel,

In October 2015 you wrote:

mkcue is behaving like "cdrdao --fast-toc", it is not reading the
pre-gap and index mark details from the disk and it is not including
those details in the Cue sheet.

For some purposes, such as calculating a Musicbrainz disk ID, it may be
necessary to have all these details.


Did you end up just using cdrdao?  Are there other features that would 
make it useful to you to fix this in mkcue, or would recommending cdrdao 
to new users be better?


Moray

Bug#855824: unblock: multipath-tools/0.6.4-4

[Allan Jacobsen]

Den 04/03/2017 kl. 10.05 skrev Niels Thykier:
> Cyril Brulebois:
>> Hi,
>>
>> Niels Thykier <ni...@thykier.net> (2017-02-24):
>>> Ritesh Raj Sarraf:
>>>> Package: release.debian.org
>>>> Severity: normal
>>>> User: release.debian@packages.debian.org
>>>> Usertags: unblock
>>>>
>>>> Please unblock package multipath-tools
>>>>
>>>> These are minor changes, which should qualify for an upload exception. The 
>>>> new
>>>> file additions are mostly autopkg tests related, which have no impact on 
>>>> the
>>>> software. The other changes are good to have for Stretch.
>>>>
>>>> unblock multipath-tools/0.6.4-4
>>>>
>>>> [...]
>>>
>>> Ok with me. KiBi, is this upload ok for d-i?
>>
>> I think so. I've spent a little time on multipath fixes a few days ago, and
>> Mathieu mentioned a few more fixes being needed in d-i anyway. Adding him,
>> along with Allan who submitted patches and reports to let them know about
>> these possible extra changes in multipath-tools. Might be worth waiting a
>> bit for their feedback.
>>
>>
>> KiBi.
>>
> 
> Hi Allan and Mathieu,
> 
> Did you have any feedback ?
> 
> Thanks,
> ~Niels
> 
Sorry for my slow responce on this.

I worked on this the last week of february, but was not able to get it to work 
reliably.

I think i made 20-30 installs on jessie, that I upgraded to stretch, and only 
one time i got multipath to work, and after a reboot it was gone again.

The patch it OK, but it is in other packages that some things are missing, but 
unfortunatly my work at the company stopped on 28/2, so I no longer have access 
to hardware to test on.

Best regards
Allan

Bug#855585: Patch for multipath-udeb to get install working in stretch

[Allan Jacobsen]

Package: multipath-udeb
Version: 0.6.4-3
Severity: Important

These 2 changes made my server that was upgraded from jessie(where
multipath worked) to stretch(where it didn't)

start from /dev/mapper/mpatha-part1 instread og /dev/sda1, so I am
pretty sure this will make multipath work in the stretch install, and
maybe multipath install will work in standard debian then.

The dm-emc has been absent from the kernel since 2.xxx, and multipath
does not work without dm-round-robin in the initram.

I think these changes have beenn suggested before, but have not been applied.




diff -ir multipath-tools-0.6.4.orig/debian/initramfs/hooks
multipath-tools-0.6.4/debian/initramfs/hooks
51c51
< for x in dm-multipath dm-service-time dm-round-robin dm-emc; do
---
> for x in dm-multipath dm-service-time dm-round-robin; do
diff -ir multipath-tools-0.6.4.orig/debian/initramfs/local-top
multipath-tools-0.6.4/debian/initramfs/local-top
29c29
< MP_MODULES="dm-multipath dm-emc"
---
> MP_MODULES="dm-multipath dm-round-robin"

Best regards

Allan Jacobsen

Bug#854565: disk-detect looks for obsolete name

[Allan Jacobsen]

Package: installation-reports

Boot method: PXE (network install)
Image version: Stretch RC2
Date: 20170208

Machine: Cisco UCSB-B200-M4
Processor: Intel Xeon E5-2660
Memory: 32Gbyte
Partitions: Not found, that is the problem.

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [O]
Detect hard drives: [E]

I am making a PXE install on multipath disks, and "multipath -ll"
detects the disk, but disk-detect looks for mpath0-9 name instead of
mpatha-z, so no disks is found.

The name change was in 2008, so it is time for an update.

Best regards

Allan Jacobsen

Bug#806900: Problem still in stretch rc1 installer

[Allan Jacobsen]

HI

OK, I do understand you point, but my problem is that I have been hired as
a cunsultant to set up PXE boot with preseed to install different linux
dists, and I can not put a wwid that I don't know into the preseed file,
but have to use the friendly name.

This works fine with ubuntu, but not with debian, because you wont apply
the patch.

For jessie I had to create 2 custom udebs, and It seems to be the same
waste of time is needed for stretch.

I really dont understand why multipath is part of the debian installer when
it is a well known fact that the disk-detect, multipath and
partman-multipath udebs can not work together.

Best regards
Allan Jacobsen

2017-01-27 9:47 GMT+01:00 Ritesh Raj Sarraf <r...@debian.org>:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On Fri, 2017-01-27 at 08:23 +0100, Allan Jacobsen wrote:
> > I understand your point, but the multipath-tools is full of code for
> friendly
> > names, so what you are actually doing is making sure multipath will not
> work
> > with the stock debian installer, forcing people like me to create our own
> > install media, which i don't think is in the best interest of debian as
> an
> > organisation that want to be the universal operating system.
>
> No. That is wrong conclusion.
>
> What I'm saying is that user_friendly_names has had issues in the past.
> Today,
> they still have the burden of, when used, to ensure that the binding file
> is
> propagated and remains up-to-date. Eg. initrd, cluster setups.
>
> Device names based on wwid are unique and persistent.
>
> What we are doing is just making a recommendation of Best Practices. Each
> feature has its merits and drawbacks.
>
> - --
> Ritesh Raj Sarraf | http://people.debian.org/~rrs
> Debian - The Universal Operating System
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliLCSwACgkQpjpYo/Lh
> dWlEDw/+PmG0NbqI13pKSBbbXXWhtKSyJGuqyzaMCdGGUIeo7aXwu+YKVUZ3TZvU
> 3xNHj2/W+ZbGjincnO+yU8z8S68LzidlMca8Khw2l8ZaMzaiFvlgZ+Fm1+H3U5a7
> zRIxGh26krYDXoWPH939S+2FSPE/Cnvv3DNid7F17BPwXeStlxhHpNX5jtgXEfPR
> tnampOd32W1aAPQ+uxmi9muxcLs8R8YD7ewjdEDaFabyw/x0s9EfngRRAz8DwZKH
> d1TaoTbVJIPwV54WWQhM5CD8o9Ys2wqRIMRk2Lq/N2z2HjYeZ9kBsv/pcktjKDuH
> r2M6N+KVtvxVDpi7UcVhdb2vZnM9ZjC2o4/1nLbhe98JtVg4omGR1g92/6HTgumz
> 28eZIJeKEUN7UBfALRD3RSG7ww4ihSK9tThFmcxuGSK5p1KGVCkgdLsdo3BJyAda
> luJyWYyzlRlLsOrySC/N2LHj7Ea/fEsK94MF901DudbliaX4UIizzlIt91SNjMNE
> 10ebGrblWCSGrrKKnWvvW7IJBP9ovaGggQNS0kFIi4FXL962TrS1bPa5k0I+Lwpn
> yGppGMW7LFTTDe2+5e429FCPWZnZaNFyWab16dYJG4cG8p2fEvR2MhDef8sADl/Z
> jLlcn859YObmHZefnLujDmKqkfRIYFYHAd3Xx9WRaNxgMx8jW94=
> =sgh+
> -END PGP SIGNATURE-
>
>

Bug#806900: Problem still in stretch rc1 installer

[Allan Jacobsen]

Hi

I understand your point, but the multipath-tools is full of code for
friendly names, so what you are actually doing is making sure multipath
will not work with the stock debian installer, forcing people like me to
create our own install media, which i don't think is in the best interest
of debian as an organisation that want to be the universal operating system.

Best regards
Allan Jacobsen

2017-01-26 14:20 GMT+01:00 Ritesh Raj Sarraf <r...@debian.org>:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On Thu, 2017-01-26 at 12:19 +0100, Allan Jacobsen wrote:
> > Hi
> >
> > I can confirm that the problem is not solved in stretch RC1 installer,
> so it
> > would be really nice to have the patches applied, so there is a chance
> that
> > multipath will work in stretch.
>
> In base multipath-tools packages, we've always recommended using
> persistent WWID
> names instead of friendly names. They are unique and are always the same.
> The
> simplest for D-I should be to just drop friendly names for multipathed
> devices.
>
>
> - --
> Ritesh Raj Sarraf | http://people.debian.org/~rrs
> Debian - The Universal Operating System
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliJ95wACgkQpjpYo/Lh
> dWl8mQ/+Js700Ma7lC60jfJD7zoxuCzkyurkixQjyUDHIWpGyTvq7k8ujOh5C+VU
> +Q9X3rzQ8qL3bHEOBdeXOe17edtoPuksvo78U7QlSAEMBKCCSt9B1oyrMQl52ibj
> n/e5USdn3cTLLVdi2h5WgWdZrML8+jgZy1POWj+LreYel0opvUoArMP6h9ACRibf
> ZEpF626yEJxgTxUy+6bV6s0KI9cV88zAvARlTG9wjCQ/GRD6KVDq2NiTcFN2Xvre
> mGIbuMek4jKJy5aTQToUcRCedrj2lHC55IbU75j54UECeQbBU8JX+torx10nAK/6
> HceRP+58TCHvM3OD0s3heSujcLCZzCY1nahHdq8SsDS1H7WwQDYQI+LLkkhI0Eux
> zwAjVyUWuqN5OI/cB98dLfDJ/1O8t6ufacT6Axw1MaeUGWuAiFENPgTGYHmwy9jx
> FFXVIswAt3UVxCKlVtLIkSGv78jmZnToxKdCgAvzNyCv/gUByQqWYeH+hG0jD4KT
> MjntaoE9Phr90JGETXJuPC/sQOQU5N/SFHH2PPlv6lUGdEAed7LJj7ran9qhHyBE
> Pqf0j0etR5l3lGCE5ludqaSBjtGRAgysMQWAIp3nH1SANKRn+72nCb9sIGk/4ait
> ZPYLAamoKOdURWWSInPXJUdr372iN49yF+OnWIEPQMPbQbwSFQw=
> =QmlK
> -END PGP SIGNATURE-
>
>

Bug#806713: Problem still in stretch RC1 installer

[Allan Jacobsen]

Hi

The problem is still in the RC1 installer for stretch, so it would be
really nice to have the patch applied.

Best regards
Allan Jacobsen

Bug#806900: Problem still in stretch rc1 installer

[Allan Jacobsen]

Hi

I can confirm that the problem is not solved in stretch RC1 installer, so
it would be really nice to have the patches applied, so there is a chance
that multipath will work in stretch.

Best regards
Allan Jacobsen

Bug#852398:

[allan]

Can duplicate on 32-bit Sid.  Extensions are broken.

Bug#852431: Fwd: Bug#852431: installer broken: multipath-udeb depends on missing libmpathcmd.so.0

[Allan Jacobsen]

-- Forwarded message --
From: Allan Jacobsen <al...@linuxbutikken.dk>
Date: 2017-01-25 7:38 GMT+01:00
Subject: Re: Bug#852431: installer broken: multipath-udeb depends on
missing libmpathcmd.so.0
To: r...@debian.org


Hi Ritesh

Sorry I should have quoted my bugreport againt debian-installer

2017-01-24 15:22 GMT+01:00 Ritesh Raj Sarraf <r...@debian.org>:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Control: tag -1 +moreinfo
>
> On Tue, 2017-01-24 at 12:27 +0100, Allan Jacobsen wrote:
> > I am testing the installer for stretch, and there is an error in the
> > multipath-udeb, as the library libmpathcmd.so is missing from the
> package.
> >
>
> Can you please share what the error is ? Does the error happen during
> multipath
> map creation ?
>
> Package: installation-reports

Boot method: PXE (network install)
Image version: 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/debian-installer/amd64/
Date: 20170123

Machine: Cisco UCSB-B200-M4
Processor: Intel Xeon E5-2660
Memory: 32Gbyte
Partitions: Not found, that is the problem.

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [E]
Detect hard drives: [E]

During multipath install, the installer tries to load dm-emc module
which it should not do, then tries to run /sbin/multipath which gives
the error:

disk-detect: /sbin/multipath: error while loading shared libraries:
libmpathcmd.so.0: cannot open shared object file: No such file or
directory



> How do I reproduce this locally ? A simple LUN discovery through the
> Stretch
> installer ? Would be nice if you give me your steps to reproduce.
>
> I have not tried it, but i guess if you install multipath-tools on a local
stretch, and then delete /lib/libmpathcmd.so.0 you would get the same error.

Best regards
Allan

Bug#852285: Wrong subject, the missing lib should be in multipath-udeb

[Allan Jacobsen]

I looked into this a little more, and the missing lib should be in
multipath-udeb, I have made a bugreport for this.

The problem with dm-emc is easily fixed, patch is attached.


Best regards
Allan Jacobsen


disk-detect.patch
Description: Binary data

Bug#852431: installer broken: multipath-udeb depends on missing libmpathcmd.so.0

[Allan Jacobsen]

Package: src:multipath-tools
Version: 0.6.4-2

I am testing the installer for stretch, and there is an error in the
multipath-udeb, as the library libmpathcmd.so is missing from the
package.

It is easy to fix, just add "/lib/libmpathcmd.so.*" to the
debian/multipath-udeb.install file.

Best regards

Allan jacobsen

Bug#852285: installer broken: multipath-udeb depends on non-existent libmpathcmd udeb

[Allan Jacobsen]

Package: installation-reports

Boot method: PXE (network install)
Image version: 
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/debian-installer/amd64/
Date: 20170123

Machine: Cisco UCSB-B200-M4
Processor: Intel Xeon E5-2660
Memory: 32Gbyte
Partitions: Not found, that is the problem.

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [ ]
Load installer modules: [E]
Detect hard drives: [E]

During multipath install, the installer tries to load dm-emc module
which it should not do, then tries to run /sbin/multipath which gives
the error:

disk-detect: /sbin/multipath: error while loading shared libraries:
libmpathcmd.so.0: cannot open shared object file: No such file or
directory