Bug#1075833: gpg: Apt-get upgrade --> 'E: Broken packages' because of 'unmet dependencies' : gnupg / gpg / gpgconf / gpg-agent / gpg-wks-client

[scott092707]

Package: gpg
Version: 2.2.40-3
Severity: normal

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: gpg: Apt-get upgrade  -->  'E: Broken packages' because of 'unmet 
dependencies' : gnupg / gpg / gpgconf / gpg-agent / gpg-wks-client
Bcc: Scott Jacobs 
Message-ID: 
<172022871237.10763.13136931568556884966.reportbug@ASUS-Prime-B350MA>
X-Mailer: reportbug 13.0.1
Date: Fri, 05 Jul 2024 21:18:32 -0400
X-Debbugs-Cc: scott092...@aol.com


Attempted to upgrade my software, using 'sudo apt-get update' and then 'sudo
apt-get upgrade'

No upgrade was done, and the following message was printed:

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnupg : Depends: gpg (>= 2.2.43-7)
 Depends: gpg-agent (>= 2.2.43-7) but 2.2.40-3 is to be installed
 gpg : Depends: gpgconf (= 2.2.40-3) but 2.2.43-7 is to be installed
   Recommends: gnupg (= 2.2.40-3) but 2.2.43-7 is to be installed
 gpg-agent : Depends: gpgconf (= 2.2.40-3) but 2.2.43-7 is to be installed
 Recommends: gnupg (= 2.2.40-3) but 2.2.43-7 is to be installed
 gpg-wks-client : Depends: gpg (= 2.2.43-7)
  Depends: gpg-agent (= 2.2.43-7) but 2.2.40-3 is to be
installed
E: Broken packages

'apt-cache policy gpg gnupg gpg-agent gpgconf gpg-wks-client'
listed each pkg as version 2.2.40-3, with candidate 2.2.43-7

I finally was successful in doing an apt-get upgrade, by
first doing:
sudo apt-get install gpg gnupg gpg-agent gpgconf gpg-wks-client
and then:
sudo apt-get upgrade

but shouldn't apt-get upgrade have been able to satisfy the dependencies
all by itself?


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

Kernel: Linux 6.7.12-amd64 (SMP w/4 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 gpg depends on:
ii  gpgconf  2.2.40-3
ii  libassuan0   2.5.6-1+b1
ii  libbz2-1.0   1.0.8-5.1
ii  libc62.38-11
ii  libgcrypt20  1.10.3-3
ii  libgpg-error01.49-2
ii  libreadline8t64  8.2-4
ii  libsqlite3-0 3.45.3-1
ii  zlib1g   1:1.3.dfsg+really1.3.1-1

Versions of packages gpg recommends:
ii  gnupg  2.2.40-3

gpg suggests no packages.

-- no debconf information

Bug#1074080: caja: Four constantly-repeated GLib-GIO-CRITICAL errors noted when launched from terminal

[scott092707]

Package: caja
Version: 1.26.3-1+b1
Severity: normal
X-Debbugs-Cc: scott092...@aol.com

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: caja: Four constantly-repeated GLib-GIO-CRITICAL errors noted when 
launched from terminal
Bcc: Scott Jacobs 
Message-ID: 
<171909985413.2301933.17173951078890870499.reportbug@ASUS-Prime-B350MA>
X-Mailer: reportbug 13.0.1
Date: Sat, 22 Jun 2024 19:44:14 -0400

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I was editing a gtk theme, and needed to constantly close/open Caja long parm
list and "env GTK_THEME= ..."
and so ran Caja from terminal, so that after closing it down, I would need only
to click up-arrow and enter
to restart Caja.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Since I have no idea what the cause of this is, I did nothing.

   * What was the outcome of this action?
Four constantly repeated instances of:
(caja:2261560): GLib-GIO-CRITICAL **: 19:22:20.931: GFileInfo created without
standard::sort-order

(caja:2261560): GLib-GIO-CRITICAL **: 19:22:20.931: file
../../../gio/gfileinfo.c: line 2107 (g_file_info_get_sort_order): should not be
reached

(caja:2261560): GLib-GIO-CRITICAL **: 19:22:20.931: GFileInfo created without
standard::symlink-target

(caja:2261560): GLib-GIO-CRITICAL **: 19:22:20.931: file
../../../gio/gfileinfo.c: line 2061 (g_file_info_get_symlink_target): should
not be reached

This seemed not to be continuous, but waited for me to do something in Caja
(select?click/drag/...)

   * What outcome did you expect instead?
No errors.

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


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

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

Versions of packages caja depends on:
ii  caja-common  1.26.3-1
ii  desktop-file-utils   0.27-2
ii  gvfs 1.54.0-4
ii  libatk1.0-0t64   2.52.0-1
ii  libc62.38-11
ii  libcairo-gobject21.18.0-3+b1
ii  libcairo21.18.0-3+b1
ii  libcaja-extension1   1.26.3-1+b1
ii  libexempi8   2.6.5-1
ii  libexif120.6.24-1+b1
ii  libgail-3-0t64   3.24.41-4
ii  libgdk-pixbuf-2.0-0  2.42.12+dfsg-1
ii  libglib2.0-0t64  2.80.2-2
ii  libglib2.0-bin   2.80.2-2
ii  libglib2.0-data  2.80.2-2
ii  libgtk-3-0t643.24.41-4
ii  libice6  2:1.0.10-1+b1
ii  libmate-desktop-2-17t64  1.26.2-1.1+b1
ii  libnotify4   0.8.3-1+b1
ii  libpango-1.0-0   1.52.2+ds-1
ii  libpangocairo-1.0-0  1.52.2+ds-1
ii  libselinux1  3.5-2+b2
ii  libsm6   2:1.2.3-1+b1
ii  libx11-6 2:1.8.7-1+b1
ii  libxml2  2.9.14+dfsg-1.3+b3
ii  mate-desktop 1.26.2-1.1+b1
ii  shared-mime-info 2.4-4

Versions of packages caja recommends:
ii  gvfs-backends  1.54.0-4
ii  gvfs-fuse  1.54.0-4

Versions of packages caja suggests:
ii  engrampa1.26.2-4
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#985247: eom: Selecting Print-->Preview shows nothing. eom evoked from terminal shows 'sh: 1: exec: evince: not found'

[scott092707]

Package: eom
Version: 1.24.1-1
Severity: normal
X-Debbugs-Cc: scott092...@aol.com

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: eom: Selecting  Print-->Preview  shows nothing.  eom evoked from 
terminal shows 'sh: 1: exec: evince: not found'
Bcc: Scott Jacobs 
Message-ID: 
<161577196380.259233.15032026551506305869.reportbug@ASUS-Prime-B350MA>
X-Mailer: reportbug 7.10.3
Date: Sun, 14 Mar 2021 21:32:43 -0400

Dear Maintainer,


   * What led up to the situation?
I wished to see how much of a page an image would occupy, and clicked "Preview"
from the Print dialog.

   * What was the outcome of this action?
Nothing happened.
When I invoked eom from the terminal, along with a number of warnings, the
above text was printed.


   * What outcome did you expect instead?
I expected the preview to be displayed.


[Full text of the terminal output below:]
-
(eom:149269): EOM-WARNING **: 20:54:13.134: Error loading Peas typelib: Typelib
file for namespace 'Peas', version '1.0' not found


(eom:149269): EOM-WARNING **: 20:54:13.134: Error loading PeasGtk typelib:
Typelib file for namespace 'PeasGtk', version '1.0' not found


(eom:149269): dconf-WARNING **: 20:54:13.174: failed to commit changes to
dconf: The connection is closed

(eom:149269): dconf-WARNING **: 20:54:13.175: failed to commit changes to
dconf: The connection is closed

(eom:149269): dconf-WARNING **: 20:54:13.193: failed to commit changes to
dconf: The connection is closed

** (eom:149269): WARNING **: 20:54:23.762: The connection is closed
sh: 1: exec: evince: not found

** (eom:149269): WARNING **: 20:56:58.780: The connection is closed

(eom:149269): GLib-GObject-WARNING **: 20:57:17.935: value "-nan" of type
'gfloat' is invalid or out of range for property 'image-x-align' of type
'gfloat'
-

MATE/eom pull request from 2015:
https://github.com/mate-desktop/eom/pull/107 : "refactor draw/expose code a bit
#107"
contains the following text:
"As for preview via pdf, it happens even w/o my work. It first tries evince,
then gives a Gtk-WARNING when it can't find it on my system, then tries atril
and opens the generated pdf in it. It's the same in both GTK+ builds."

I do not have evince.  I DO have atril.
atril:
  Installed: 1.24.0-1
  Candidate: 1.24.0-1
  Version table:
 *** 1.24.0-1 500
500 https://deb.debian.org/debian testing/main amd64 Packages
100 /var/lib/dpkg/status

I can get around the problem by making a symlink to atril, and renaming it as
'evince'.

Something must have happened between 2015 and now, as the commenter had success
with eom trying evince and then trying atril.
Now, it apparently does not try atril, as if it did, it would have succeeded.

[Note: both eom and atril-previewer (once I make the symlink) are displayed 
natively under Wayland,
not XWayland]

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

scott@ASUS-Prime-B350MA:~$ apt-cache policy sway
sway:
  Installed: 1.5-7

scott@ASUS-Prime-B350MA:~$ apt-cache policy *wlroots*
...
libwlroots6:
  Installed: 0.11.0-3
...

scott@ASUS-Prime-B350MA:~$ uname -a
Linux ASUS-Prime-B350MA 5.10.0-1-amd64 #1 SMP Debian 5.10.4-1 (2020-12-31)
x86_64 GNU/Linux

FF

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

Versions of packages eom depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-1
ii  eom-common   1.24.1-1
ii  gir1.2-eom-1.0   1.24.1-1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-9
ii  libcairo21.16.0-5
ii  libexempi8   2.5.2-1
ii  libexif120.6.22-3
ii  libgdk-pixbuf2.0-0   2.40.2-2
ii  libgirepository-1.0-11.66.1-1+b1
ii  libgl1   1.3.2-1
ii  libglib2.0-0 2.66.4-1
ii  libgtk-3-0   3.24.24-1
ii  libjpeg62-turbo  1:2.0.5-2
ii  liblcms2-2   2.9-4+b1
ii  libmate-desktop-2-17 1.24.1-2
ii  libpeas-1.0-01.28.0-2+b1
ii  librsvg2-2   2.50.2+dfsg-1
ii  librsvg2-common  2.50.2+dfsg-1
ii  libx11-6   

Bug#961551: partitionmanager: Does not start - "Session bus not found"

[scott092707]

Package: partitionmanager
Version: 4.1.0-1
Severity: important

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: partitionmanager: Does not start - "Session bus not found"
Bcc: Scott Jacobs 
Message-ID: 
<159044435347.106308.1127544499156350.reportbug@ASUS-Prime-B350M-A-CSM>
X-Mailer: reportbug 7.6.0
Date: Mon, 25 May 2020 18:05:53 -0400
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

I attempted to run PartitionManager today, and it did not start:

$ sudo partitionmanager
[sudo] password for scott:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
"Session bus not found\nTo circumvent this problem try the following command
(with Linux and bash)\nexport $(dbus-launch)"

I have successfully run this in the past (after adding "lxqt-sudo " before the
command on the .desktop file's "exec" line - otherwise, nothing happens...)
but today, nothing happened.  When I started it in the terminal, I got the
above.

I attempted to follow the suggestion ("export $(dbus-launch)"), but the command
was unknown.
It is apparently a file provided by dbus-x11, whose description states:
"This package contains the dbus-launch utility which is necessary for packages
using a D-Bus session bus."

I have dbus, but not dbus-x11.
As I say, I have successfully launched partitionmanager in the past, and have
not removed dbus-x11.

I don't use it often - mostly to verify my main disk's partition layout.
I note that around mid April, when I did a "sudo apt-get upgrade"
partitionmanager was "held back", and I subsequently installed it (it is the
newest version for testing)

I guess something changed.

I note that the environment variable
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus  is defined (as is
XDG_RUNTIME_DIR=/run/user/1000 - which even before, when I could run it, it
claimed was undefined).




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

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

Versions of packages partitionmanager depends on:
ii  kio   5.62.1-2+b1
ii  libc6 2.29-9
ii  libkf5configcore5 5.62.0-1+b1
ii  libkf5configgui5  5.62.0-1+b1
ii  libkf5configwidgets5  5.62.0-1+b1
ii  libkf5coreaddons5 5.62.0-1
ii  libkf5crash5  5.62.0-1+b1
ii  libkf5dbusaddons5 5.62.0-1
ii  libkf5i18n5   5.62.0-1
ii  libkf5iconthemes5 5.62.0-1+b1
ii  libkf5jobwidgets5 5.62.0-1+b1
ii  libkf5kiocore55.62.1-2+b1
ii  libkf5kiowidgets5 5.62.1-2+b1
ii  libkf5widgetsaddons5  5.62.0-1+b1
ii  libkf5xmlgui5 5.62.0-1+b1
ii  libkpmcore9   4.1.0-2
ii  libqt5core5a  5.12.5+dfsg-10
ii  libqt5gui55.12.5+dfsg-10
ii  libqt5widgets55.12.5+dfsg-10
ii  libstdc++610.1.0-2

partitionmanager recommends no packages.

Versions of packages partitionmanager suggests:
ii  btrfs-progs5.6-1
ii  dosfstools 4.1-2
pn  hfsplus
pn  hfsutils   
pn  jfsutils   
ii  ntfs-3g1:2017.3.23AR.3-3
pn  reiser4progs   
pn  reiserfsprogs  
pn  xfsprogs   

-- no debconf information

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration" Date: Wed, 1 Jan 2020 04:54:06 +0000 (UTC)

[scott092707]

>I'm wondering exactly what the effect of "with persistence" is, for example. 

Persistence is a very useful feature, whereby a certain amount of storage is 
reserved
on the media that is used when a change is made from the .iso , so that when it 
is again
booted, that change is still there.
For example:  I use a live session to back up my hard drive to another drive.
The back up program is not part of the .iso, so it must be installed.
Without persistence, each time I back up the drive, I must again install that
program.  With persistence, after the first time installed, it is as if it were 
part
of the .iso, and is usable immediately after boot.
Also, for instance, I happen to like the main panel on the top of the screen, 
not the bottom,
and my window-control buttons on the left, not on the right.
With persistence, after I first change these preferences, every time I boot, 
the panel
is at the top, and the window buttons on the left.
In effect, one can make a "custom" live session.
It is, of course, more useful, the more packages one needs to install, and the 
more
customizations one makes to the UI.

>Could you try again without that and see if that makes a difference for you, 
>please?
Yes... well... booting the live-usb without persistence solved the problem.

I can only speculate, that Calamares (or something Calamares calls) refers to
/run/live/medium/live/filesystem.squashfs
two different ways in two (or more) different locations of the code.
Without persistence, the two ways point to the same place, and all is good.
With persistence, the two ways point to two different places, and it fails.

Perhaps a symlink is involved...?

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration" Date: Wed, 1 Jan 2020 04:54:06 +0000 (UTC)

[scott092707]

>What media are you using for the image, out of curiosity?
16GB PNY USB 2.0 Flash drive ("Attache 4"), in a USB 3.0 hub in a USB 3.0 port.

Installed with mkusb 12.3.9-1ubuntu1 with persistence
(I've had very good results getting bootable USB drives with mkusb).

Are you thinking that there may be some sort of media flaw in the drive?

Bug#948965: calamares: Debian 11 live testing amd64 LXQt + non-free fails with: "Bad unsquash configuration"

[scott092707]

Further attempts to install, with images through the current 01/27/2020 .iso,
continue to fail in exactly the same way.

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration"

[scott092707]

Further attempts to install, with images through the current 01/27/2020 .iso,
continue to fail in exactly the same way.

Bug#941344: xsane-common: does not ship xsane-startimage.pnm, preventing the preview from working

[scott092707]

In researching my own bug (#945385), I found this,, and hoped that I might have 
found the
solution.  Sadly, not.

However, I looked at this bug, and noted that, my version of xsane[-common], 
0.999-7,
not only was there not:

/usr/share/sane/xsane/xsane-startimage.pnm

there was not even a  /usr/share/sane  folder...

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lHa /usr/share/sane/xsane/
ls: cannot access '/usr/share/sane/xsane/': No such file or directory

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lHa /usr/share/sane/
ls: cannot access '/usr/share/sane/': No such file or directory

My old Lubuntu Next 17.10 xsane 0.999-5 works, and has that folder:

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lHa /LubuntuNext1710/usr/share/sane
total 20
drwxr-xr-x   3 root root  4096 Nov  5  2017 .
drwxr-xr-x 295 root root 12288 Feb  6  2019 ..
drwxr-xr-x   3 root root  4096 Nov  5  2017 xsane

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lHa /LubuntuNext1710/usr/share/sane/xsane
total 1616
drwxr-xr-x 3 root root   4096 Nov  5  2017 .
drwxr-xr-x 3 root root   4096 Nov  5  2017 ..
drwxr-xr-x 2 root root  12288 Nov  5  2017 doc
-rw-r--r-- 1 root root  32448 Jul 23  2017 Mustek-logo.xpm
-rw-r--r-- 1 root root  27183 Jul 23  2017 Plustek-logo.xpm
-rw-r--r-- 1 root root  31931 Jul 23  2017 sane-epson-logo.xpm
-rw-r--r-- 1 root root  28061 Jul 23  2017 sane-hp-logo.xpm
-rw-r--r-- 1 root root  32927 Jul 23  2017 sane-umax-logo.xpm
-rw-r--r-- 1 root root  30816 Jul 23  2017 sane-xsane-logo.xpm
-rw-r--r-- 1 root root  12611 Jul 23  2017 UMAX-logo.xpm
-rw-r--r-- 1 root root 656457 Jul 23  2017 xsane-calibration.pnm
-rw-r--r-- 1 root root   1265 Jul 23  2017 xsane-eula.txt
-rw-r--r-- 1 root root  14961 Jul 23  2017 xsane-gpl.txt
-rw-r--r-- 1 root root  79099 Jul 23  2017 xsane-logo.xpm
-rw-r--r-- 1 root root 656458 Jul 23  2017 xsane-startimage.pnm
-rw-r--r-- 1 root root628 Jul 23  2017 xsane-style.rc


When I upgraded from 0.999-7 to 0.999-8 today,
I noted that the folder  /usr/share/sane  was still not there.

>* Add missing pnm, xpm and rc files into the doc directory
MY Lubuntu Next 17.10  xsane 0.999-5 's  /usr/share/sane/xsane/doc  directory
only contained  .html  and  .jpg  files

Bug#948851: (no subject)

[scott092707]

>Are you sure you did't check "Show all fields templated" in Configuration -> 
>Template?
I apparently did, without knowing what that meant...

By un-checking the box, I was able to edit the text to remove the ':'s and 
alter the length
of the long lines to bypass the other bug...


Is there documentation on using QtPass?  I could not find any...

Based upon my own experience, the rule for the "text box" (does it have a name 
- there is
no description by it...?) appears to be:
"For each line that has a ':' in it, make a template field out of what is to 
the right of the ':'
and bring up any text to the left of it and place it opposite the template as a 
description."

(Are there other rules...?)

Bug#948965: calamares: Debian 11 live testing amd64 LXQt + non-free fails with: "Bad unsquash configuration"

[scott092707]

Package: calamares
Version: 3.2.17.1-1+b1
Severity: grave
Justification: renders package unusable

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Debian Live user 
To: Debian Bug Tracking System 
Subject: calamares: Debian 11 live testing amd64 LXQt + non-free fails with: 
"Bad unsquash configuration"
Bcc: Debian Live user 
X-Mailer: reportbug 7.5.3
Date: Tue, 14 Jan 2020  21:18:53 -0500
X-Debbugs-Cc: scott092...@aol.com


Dear Maintainer,

Installation from: Debian 11 live testing amd64 LXQt + non-free .iso files
(file: debian-live-testing-amd64-lxqt+nonfree.iso
from site: 
https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/weekly-live-builds/amd64/iso-hybrid/)
 
dated from 2020-01-13 back at least to 2019-12-11
fails with the above text.

This is described fully in a bug against installation-reports 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947744)

The bug there has received no comments but mine, and perhaps has not been read.
Since Calamares is the OS installer for LXQt, I thought I'd better also report 
it here...
This report is being generated from the live session, but will be sent from my 
usual install
(also Debian testing LXQt, originally version 10, and updated occasionally.).


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

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

Versions of packages calamares depends on:
ii  kpackagetool5   5.62.0-1
ii  libboost-python1.67.0 [libboost-python1.67.0-py37]  1.67.0-17
ii  libc6   2.29-7
ii  libcrypt1   1:4.4.10-10
ii  libgcc1 1:9.2.1-22
ii  libkf5configcore5   5.62.0-1+b1
ii  libkf5coreaddons5   5.62.0-1
ii  libkf5package5  5.62.0-1
ii  libkf5parts55.62.0-1+b1
ii  libkf5service-bin   5.62.0-1
ii  libkf5service5  5.62.0-1
ii  libkpmcore8 4.0.1-2+b1
ii  libparted2  3.3-1
ii  libpwquality1   1.4.2-1
ii  libpython3.73.7.6-1
ii  libqt5core5a5.12.5+dfsg-2
ii  libqt5dbus5 5.12.5+dfsg-2
ii  libqt5gui5  5.12.5+dfsg-2
ii  libqt5network5  5.12.5+dfsg-2
ii  libqt5qml5  5.12.5-5
ii  libqt5quick55.12.5-5
ii  libqt5quickwidgets5 5.12.5-5
ii  libqt5svg5  5.12.5-2
ii  libqt5webkit5   5.212.0~alpha3-5+b1
ii  libqt5widgets5  5.12.5+dfsg-2
ii  libqt5xml5  5.12.5+dfsg-2
ii  libstdc++6  9.2.1-22
ii  libyaml-cpp0.6  0.6.2-4
ii  os-prober   1.77

Versions of packages calamares recommends:
ii  btrfs-progs 5.4-1
ii  squashfs-tools  1:4.4-1

calamares suggests no packages.

-- no debconf information

Bug#948852: qtpass: On-the-fly storable password character-restriction options per Password entry

[scott092707]

Package: qtpass
Version: 1.3.2-1
Severity: wishlist

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: qtpass: On-the-fly storable password character-restriction options per 
Password entry
Bcc: Scott Jacobs 
Message-ID: 
<157895762049.3778.11681865878303138446.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Mon, 13 Jan 2020 18:20:20 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

I have, as default, set up password-generation with all possible character
possibilities (upper/lower, number, symbol),
but one sometimes does not know until one is actually at a website creating a
password, that the password cannot contain certain characters -
usually a subset of symbols.

It would be nice to have a button near Generate, which when pressed would bring
up a window in which one could specify what types of characters were allowed
(this would initially duplicate what was set up when configuring QtPass),
but would also allow one to enter specific characters that should be
included, or should be excluded, for this specific account.  Also, this full
classification of allowable characters would be stored with the password
record, so that if the user needed to change the password again, it would
automatically generate the password with the rules set up in this session.
(If some time in the future, the company/website changes the rules, the user 
could
just press the button again, and alter the stored rules to fit the new 
requirements.)

[I, myself, recently had to cancel a password-entry session to change the
config to exclude symbols, for a rather picky website;  I still have not
remembered to go back to Settings, to turn Symbols back on... ]



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

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

Versions of packages qtpass depends on:
ii  libc6   2.29-2
ii  libgcc1 1:8.3.0-6
ii  libqt5core5a5.12.5+dfsg-2
ii  libqt5gui5  5.12.5+dfsg-2
ii  libqt5network5  5.12.5+dfsg-2
ii  libqt5svg5  5.12.5-2
ii  libqt5widgets5  5.12.5+dfsg-2
ii  libstdc++6  9.2.1-8
ii  pass1.7.3-2

Versions of packages qtpass recommends:
ii  pass-extension-otp  1.2.0-1
ii  pwgen   2.08-2

Versions of packages qtpass suggests:
ii  git  1:2.24.0-1

-- no debconf information

Bug#948851: qtpass: Partial content of New Password text box extracted to non-editable text plus Template field

[scott092707]

Package: qtpass
Version: 1.3.2-1
Severity: normal

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: qtpass: Partial content of New Password text box extracted to 
non-editable text plus Template field
Bcc: Scott Jacobs 
Message-ID: 
<157895581758.2723.11698967965698840055.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Mon, 13 Jan 2020 17:50:17 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

As part of my bug for window-distortion caused by long text-box entries
(#947866 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947866), I noted
that the entry also had resulted in part of the text in the box being brought
up into the non-editable area of the use password window, plus a telephone
number in the text being turned into a Template-like field that, like the
default login and URI fields, could be clicked on to transfer to the clipboard.

I have just encountered that effect again, with an entry that included the
following text (which, before clicking OK to store the entry, I made sure was
composed of smaller lines, to escape the aforementioned bug):

"To open the attachment, you'll be prompted for a password.
Your password is the last four digits of your Social Security
number plus your four digit year of birth. Example: 03451945"

When in use, the third line is listed first (minus the ':'),
and the number and closing '"' is made into a field that can be sent to the
clipboard like the password and two default Template fields).  The first two
lines are listed underneath.
See the attached screenshot.

I have assumed that the text field was merely where one could enter info that
might be useful when logged in to the website where one needed to enter a
password.

[This COULD be a sort-of un-documented (I searched for, but could not find any
sort of how-to-use-QtPass website) feature where on-the-fly fields could be
created without adding to the Templates originally set up when configuring
QtPass, but if so, there is nothing to indicate that one CAN do it, or what
triggers it (in looking at the earlier error, I note that the one line (of
many) that was singled out for on-the-fly field creation was the one line that
contained a ':', just as in this case), and if one does do this accidentally,
one cannot use edit to back out the field-creation - one has to delete the
entire password entry and enter it again (and if one had used QtPass to
generate the password, one would first have to copy it somewhere else so as not
to lose it...)]



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

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

Versions of packages qtpass depends on:
ii  libc6   2.29-2
ii  libgcc1 1:8.3.0-6
ii  libqt5core5a5.12.5+dfsg-2
ii  libqt5gui5  5.12.5+dfsg-2
ii  libqt5network5  5.12.5+dfsg-2
ii  libqt5svg5  5.12.5-2
ii  libqt5widgets5  5.12.5+dfsg-2
ii  libstdc++6  9.2.1-8
ii  pass1.7.3-2

Versions of packages qtpass recommends:
ii  pass-extension-otp  1.2.0-1
ii  pwgen   2.08-2

Versions of packages qtpass suggests:
ii  git  1:2.24.0-1

-- no debconf information

Bug#948392: hugin: Error window concerning earlier project appears every new session at stitch invoke

[scott092707]

Package: hugin
Version: 2019.0.0+dfsg-4
Severity: normal

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: hugin: Error window concerning earlier project appears every new 
session at stitch invoke
Bcc: Scott Jacobs 
Message-ID: 
<157845077813.9832.15724935218943359898.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Tue, 07 Jan 2020 21:32:58 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer:

For a while now, each time Hugin is invoked, just after Hugin starts stitching,
and the stitching progress window appears, a "hugin Error" window appears (non-
blocking - the stitch proceeds whether or not I dismiss the window) that refers
to a stitching project that I last ran July 28 of this year.  Unfortunately, I
have no recollection what (if anything) happened at that time of an unusual 
nature.

I first noticed this after I returned from a trip late October, and started
working on panoramas from that trip.

Since I installed my current version (hugin_2019.0.0+dfsg-4_amd64 /
2019.0.0.a369cbe55179) September 10 of this year, I assume it started then, and
not the previous version (hugin_2018.0.0+dfsg-3+b1_amd64), installed November
21 of 2018 ... but I cannot be sure.  It has only been a few months since it 
started,
not a full year (but it could be that only THAT project triggered the bug, and 
that I really started
seeing the window between July 28 and September 10, but I think not.)

I will attach a screenshot of the window, but the text of the detail section is
three identical lines, that duplicate the main window text:

08:59:36 PM: error while parsing panotools script:
/data/scott/Photos/Unreviewed/20160924_Trip_Fernmeldeturm_Early/TKDC4785-4811_Panorama/TKDC4786-811-9xMed_ER.pto
08:59:36 PM: error while parsing panotools script:
/data/scott/Photos/Unreviewed/20160924_Trip_Fernmeldeturm_Early/TKDC4785-4811_Panorama/TKDC4786-811-9xMed_ER.pto
08:59:36 PM: error while parsing panotools script:
/data/scott/Photos/Unreviewed/20160924_Trip_Fernmeldeturm_Early/TKDC4785-4811_Panorama/TKDC4786-811-9xMed_ER.pto

I can dismiss the window, and I don't THINK it recurs until after Hugin is shut
down and brought up again, but it ALWAYS comes back...



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

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

Versions of packages hugin depends on:
ii  enblend 4.2-5
ii  enfuse  4.2-5
ii  hugin-tools 2019.0.0+dfsg-4
ii  libc6   2.29-2
ii  libexiv2-14 0.25-4
ii  libfftw3-double33.3.8-2
ii  libgcc1 1:8.3.0-6
ii  libgl1  1.1.0-1+b1
ii  libglew2.1  2.1.0-4+b1
ii  libglu1-mesa [libglu1]  9.0.0-2.1+b3
ii  libgomp18.3.0-6
ii  libimage-exiftool-perl  11.70-1
ii  liblcms2-2  2.9-3+b1
ii  libpano13-3 2.9.19+dfsg-3
ii  libsqlite3-03.30.1-1
ii  libstdc++6  9.2.1-8
ii  libtiff54.0.10+git191003-1
ii  libvigraimpex6  1.10.0+git20160211.167be93+dfsg1-2
ii  libwxbase3.0-0v53.0.4+dfsg-14
ii  libwxgtk3.0-gtk3-0v53.0.4+dfsg-15
ii  make4.2.1-1.2

hugin recommends no packages.

Versions of packages hugin suggests:
pn  dcraw | rawtherapee | darktable  

-- no debconf information

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration"

[scott092707]

Package: installation-reports
Severity: grave
Justification: renders package unusable

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: installation-reports: Debian Live Testing LXQt + nonfree - install 
fails with: "Bad unsquash configuration"
Bcc: Scott Jacobs 
Message-ID: 
<157765450239.2521.4290165524983598064.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Sun, 29 Dec 2019 16:21:42 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

Twice, I tried to install the Debian Testing Live LXQt + nonfree .iso, with the
Calamares installer, and twice received the error window with:

"Installation Failed

Bad unsquash configuration
The source filesystem "/run/live/medium/live/filesystem.squashfs" does not
exist"

The .iso s from 12/11/2019 and 12/23/2019 failed exactly the same way.
These came from:
"https://cdimage.debian.org/images/unofficial/non-free/images-including-
firmware/weekly-live-builds/amd64/iso-hybrid/"

My SSD has boot/efi and swap partitions, a /data partition, and 5 20GB
partitions for OS installations.
This is being written from my current Debian Testing LXQt install, which dates
from March of this year, and has been upgraded. (I also sometimes use an old
Lubuntu 17.10 install when I need to scan, as I cannot use my printer/scanner
to scan with Debian, for some reason...)

The install proceeds normally, past the manual install stage (where I mark the
new OS partition for formatting, and keep all others unformatted and labelled
for access from the new install)

Shortly afterwards, the error window appears.

I know the root fs formatting succeeds, at least as far as assigning it a new
UUID - I was unable to boot THIS install until I edited my fstab to comment out
the mount line referring to the old install partition with its old UUID)



-- Package-specific info:

Boot method: USB
Image version: Debian Testing Live LXQt + nonfree .iso  12/11/2019  AND  
12/23/2019
Date: 29, December 2019, ~1pm, ~2pm

Machine: ASUS Prime B350M-A(CSM) + AMD A12e processor and Sapphire Pulse Radeon 
RX560 Graphics Card - 16GB RAM -1TB Crucial MX500 SSD
Partitions: 
scott@ASUS-PRIME-B350M-A-CSM:~$ sudo /sbin/fdisk -l 




   
[sudo] password for scott:  




   
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors  




   
Disk model: CT1000MX500SSD1 




   
Units: sectors of 1 * 512 = 512 bytes   




   
Sector size (logical/physical): 512 bytes / 4096 bytes  




   
I/O size (minimum/optimal): 4096 bytes / 4096 bytes 

  

Bug#946499: eog crashes with 'BadAlloc (insufficient resources for operation)' on large image

[scott092707]

Package: eog
Version: 3.34.1-1
Severity: important

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: eog crashes with 'BadAlloc (insufficient resources for operation)' on 
large image
Bcc: Scott Jacobs 
Message-ID: 
<157594733072.4153.8536409629457292126.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Mon, 09 Dec 2019 22:08:50 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

On trying to open a large image (identify reports "JPEG 44351x3013
44351x3013+0+0 8-bit sRGB 18.7524MiB 0.000u 0:00.000"), the window opens, and 
then
closes.  When run from the terminal, eog crashes with:

(eog:3197): Gdk-ERROR **: 21:21:44.635: The program 'eog' received an X Window
System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1991 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
..."

The rest of the eog error message suggested how best to run under the debugger,
so here is the text of the run:


scott@ASUS-PRIME-B350M-A-CSM:~$ GDK_SYNCHRONIZE gdb --args eog
/data/scott/Photos/Unreviewed/20191015_Trip_Michaelsberg/Pan5/TKDD1446-54_RL.jpg
bash: GDK_SYNCHRONIZE: command not found
scott@ASUS-PRIME-B350M-A-CSM:~$ GDK_SYNCHRONIZE=1 gdb --args eog
/data/scott/Photos/Unreviewed/20191015_Trip_Michaelsberg/Pan5/TKDD1446-54_RL.jpg
GNU gdb (Debian 8.3.1-1) 8.3.1
Copyright (C) 2019 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 eog...
Reading symbols from /usr/lib/debug/.build-
id/5f/7bc6fae2d0db1b144e2b30cdf905dd5e36c1b8.debug...
(gdb) break gdk_x_error()
Function "gdk_x_error()" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error()) pending.
(gdb) run
Starting program: /usr/bin/eog
/data/scott/Photos/Unreviewed/20191015_Trip_Michaelsberg/Pan5/TKDD1446-54_RL.jpg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7208d700 (LWP 3902)]
[New Thread 0x7188c700 (LWP 3903)]
[New Thread 0x7108b700 (LWP 3904)]
[New Thread 0x7fffe3fff700 (LWP 3905)]
[New Thread 0x7fffe37fe700 (LWP 3906)]
[New Thread 0x7fffe2ffd700 (LWP 3907)]
[Thread 0x7fffe2ffd700 (LWP 3907) exited]

(eog:3898): Gdk-ERROR **: 21:40:47.313: The program 'eog' received an X Window
System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 3687 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Thread 1 "eog" received signal SIGTRAP, Trace/breakpoint trap.
0x77c3ddb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) backtrace
#0  0x77c3ddb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x77c406bc in g_log_writer_default () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#2  0x77c3e9e7 in g_log_structured_array () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#3  0x77c3f400 in g_log_structured_standard () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#4  0x7723060a in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#5  0x7723d443 in ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
#6  0x7641c14b in _XError () from /lib/x86_64-linux-gnu/libX11.so.6
#7  0x76418f77 in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
#8  0x76419015 in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
#9  0x76419f6d in _XReply () from /lib/x86_64-linux-gnu/libX11.so.6
#10 0x7641581d in XSync () from /lib/x86_64-linux-gnu/libX11.so.6
#11 0x764158bb in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
#12 0x7641caaf in ?? () from /lib/x86_64-linux-gnu/libX11.so.6
#13 0x753abe81 in XShmCreatePixmap () from /lib/x86_64-linux-
gnu/libXext.so.6
#14 0x7714fd73 in ?? () from /lib/x86

Bug#946021: qtpass: Invoking results in SegFault

[scott092707]

Package: qtpass
Version: 1.3.0-2
Severity: grave
Justification: renders package unusable

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: qtpass: Invoking results in SegFault
Bcc: Scott Jacobs 
Message-ID: 
<157533667450.3876.7878626174146484422.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Mon, 02 Dec 2019 20:31:14 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

Invoking qtpass from the menu results in nothing happening.

Invoking from the terminal results in:
~$ qtpass
Segmentation fault

Invoking with gdb does not result in SegFault, but also exits without bringing
up the program.
bt yields nothing except "No stack"

=
~$ gdb qtpass
GNU gdb (Debian 8.3.1-1) 8.3.1
Copyright (C) 2019 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 qtpass...
Reading symbols from /usr/lib/debug/.build-
id/3c/f1d9ba416482bc8a78d951a09d69c5bf14778e.debug...
(gdb) run
Starting program: /usr/bin/qtpass
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x724c6700 (LWP 2904)]
[New Thread 0x715cb700 (LWP 2905)]
[Thread 0x724c6700 (LWP 2904) exited]
[Thread 0x715cb700 (LWP 2905) exited]
[Inferior 1 (process 2900) exited normally]
(gdb) bt
No stack.
(gdb) quit
=



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

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

Versions of packages qtpass depends on:
ii  libc6   2.29-2
ii  libgcc1 1:8.3.0-6
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5gui5  5.11.3+dfsg1-4
ii  libqt5network5  5.11.3+dfsg1-4
ii  libqt5svg5  5.11.3-3
ii  libqt5widgets5  5.11.3+dfsg1-4
ii  libstdc++6  9.2.1-8
ii  pass1.7.3-2

Versions of packages qtpass recommends:
ii  pass-extension-otp  1.2.0-1
ii  pwgen   2.08-2

Versions of packages qtpass suggests:
ii  git  1:2.24.0-1

-- no debconf information

Bug#945385: xsane fails to start with two errors; scanimage does the same with or without sudo

[scott092707]

Package: xsane
Version: 0.999-7
Severity: important

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: xsane fails to start with two errors; scanimage does the same with or 
without sudo
Bcc: Scott Jacobs 
Message-ID: 
<157456975091.3610.17500353917015447827.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Sat, 23 Nov 2019 23:29:10 -0500
X-Debbugs-Cc: scott092...@aol.com


Dear Maintainer,

Debian Testing LXQt.

Xsane from the menu puts up the "scanning for devices" window for awhile; it
then disappears.

>From the terminal, it is much the same, except that it eventually puts up a
window stating:
"Failed to open device 'hpaio:/usb/Deskjet_F300_series?serial=CN647B623804KH':
 Invalid argument."

scanimage -L fails with the first invocation, but then succeeds with the
second:
===
$ scanimage -L
scanimage: hp-option.c:3714: hp_optset_fix_geometry_options: Assertion `tl_x &&
tl_y && br_x && br_y' failed.
Aborted

$ scanimage -L
device `hpaio:/usb/Deskjet_F300_series?serial=CN647B623804KH' is a Hewlett-
Packard Deskjet_F300_series all-in-one
===

Attempting an actual scan twice yields two different errors:
===
$ scanimage -p -B -vvv --format=jpeg  >Desktop/scanimage.jpg
scanimage: hp-option.c:3714: hp_optset_fix_geometry_options: Assertion `tl_x &&
tl_y && br_x && br_y' failed.
Aborted

$ scanimage -p -B -vvv --format=jpeg  >Desktop/scanimage.jpg
scanimage: open of device hpaio:/usb/Deskjet_F300_series?serial=CN647B623804KH
failed: Invalid argument
Calling sane_exit
scanimage: finished
===

using sudo yields the same two errors
===
sudo -HE scanimage -p -B -vvv --format=jpeg  >Desktop/scanimage.jpg
[sudo] password for scott:
scanimage: hp-option.c:3714: hp_optset_fix_geometry_options: Assertion `tl_x &&
tl_y && br_x && br_y' failed.
Aborted

$ sudo -HE scanimage -p -B -vvv --format=jpeg  >Desktop/scanimage.jpg
scanimage: open of device hpaio:/usb/Deskjet_F300_series?serial=CN647B623804KH
failed: Invalid argument
Calling sane_exit
scanimage: finished

$ sudo scanimage -p -B -vvv --format=jpeg  >Desktop/scanimage.jpg
scanimage: open of device hpaio:/usb/Deskjet_F300_series?serial=CN647B623804KH
failed: Invalid argument
Calling sane_exit
scanimage: finished
===

Various terminal commands:
===
$ lsusb
...
Bus 001 Device 006: ID 03f0:5511 HP, Inc DeskJet F300 series
...

$ ls -l /dev/bus/usb/001
...
crw-rw-r--+ 1 root lp   189, 5 Nov 22 21:02 006
...

$ getfacl /dev/bus/usb/001/006
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/001/006
# owner: root
# group: lp
user::rw-
user:scott:rw-
group::rw-
mask::rw-
other::r--
===


Using the same computer and printer/scanner, I have no problem scanning with
xsane or scanimage from my Lubuntu Next 17.10 LXQt install:
===
$ scanimage -L
device `hpaio:/usb/Deskjet_F300_series?serial=CN647B623804KH' is a Hewlett-
Packard Deskjet_F300_series all-in-one

$ scanimage -p -B -vvv --format=jpeg  >Desktop/scanimage_2.jpg
scanimage: scanning image of size 638x877 pixels at 24 bits/pixel
scanimage: acquiring RGB frame
scanimage: min/max graylevel value = 0/255
scanimage: read 1678578 bytes in total
Closing device
Calling sane_exit
scanimage: finished

$ lsusb
...
Bus 001 Device 006: ID 03f0:5511 Hewlett-Packard DeskJet F300 series
...

$ ls -l /dev/bus/usb/001
...
crw-rw-r--+ 1 root lp   189, 5 Nov 22 22:29 006
...

$ getfacl /dev/bus/usb/001/006
getfacl: Removing leading '/' from absolute path names
# file: dev/bus/usb/001/006
# owner: root
# group: lp
user::rw-
user:scott:rw-
group::rw-
mask::rw-
other::r--
===





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

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

Versions of packages xsane depends on:
ii  libc62.29-2
ii  libgimp2.0   2.10.12-1
ii  libglib2.0-0 2.62.2-2
ii  libgtk2.0-0  2.24.32-4
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-3+b1
ii  libpng16-16  1.6.37-1
ii  libsane  1.0.27-3.2
ii  libtiff5 4.

Bug#927727: [Panorama] photos display only grey for pixels to the right of ~16000 pixels

[scott092707]

As of eog version  3.34.1-1 , bug is still present.

Bug#943744: caja: Cannot move file to Trash, do you want to delete immediately?

[scott092707]

Update:

Having given myself ownership and permissions to ~/.local/share/Trash[/*],
I am now able to trash items that are in my system / partition (including items 
that
are in /home/scott that are NOT in the bind-mounted personal data directories)
with no complaint from Caja.

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lha .local/share
drwxrwx---  4 scott scott 4.0K Mar 16  2019 Trash 

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lha .local/share/Trash  




   
total 16K   




   
drwxrwx---  4 scott scott 4.0K Mar 16  2019 .   




   
drwxr-xr-x 19 scott scott 4.0K Oct 29 23:50 ..  




   
drwxrwx---  2 scott scott 4.0K Mar 16  2019 files   




   
drwxrwx---  2 scott scott 4.0K Mar 16  2019 info

However, I am still not able to trash files in my bind-mounted directories.

In looking at the terminal output for the trash directory for /data (see above),
I noted that although I had ownership of the directory, only the owner had 
permissions for "Create and delete".

I fixed that...
scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lha /data/.Trash-1000   




   
total 4.0M  




   
drwxrwx---   5 scott scott 4.0K Feb 28  2014 .  




   
drwxrwxr-x  10 scott scott 4.0K Oct 28 20:15 .. 




   
drwxrwx---   2 scott scott  16K Feb 28  2014 expunged   




   

Bug#943744: caja: Cannot move file to Trash, do you want to delete immediately?

[scott092707]

Having done some investigating, I find that in 4 previous distros I have 
installed (all Lubuntu),
none has had root:root as owners of  ~/.local/share/Trash

Since the contents of the files directory in that folder in my current Debian 
install are files
that would originally have been in a sub-directory of a system directory, they 
would have had to 
be trashed from a sudo-invoked FM; it is at least possible that the trashing 
caused ownership
to change to root:root.

However...

Most of the files I trash are in my personal directories, in my data partition, 
and would (should)
end up in the /data/.Trash-1000  trash, which as you can see, is owned by me.

Unless Caja was trying to trash the files by copying them from the data 
partition to the system
partition trash folder, I cannot see how it had difficulty trashing them.

Can anyone enlighten me?

Bug#943744: caja: Cannot move file to Trash, do you want to delete immediately?

[scott092707]

Package: caja
Version: 1.22.2-1
Severity: normal

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: caja: Cannot move file to Trash, do you want to delete immediately?
Bcc: Scott Jacobs 
Message-ID: 
<157231618695.27987.4352493207987785411.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Mon, 28 Oct 2019 22:29:46 -0400
X-Debbugs-Cc: scott092...@aol.com


Dear Maintainer,

I try to delete a file, but get the above subject text.

At first, I thought it was because all of my personal data directories
(Documents/Desktop/Pictures/...) are bind-mounted to directories in a separate 
data partition.
However, the rest of /home is within the system partition /, and I get the same
result there.
If I sudo caja, and try to delete a (copy of a) system file (say, /etc/fstab),
this works fine. It appears in /root/.local/share/Trash/files.
I DO have a ~/.local/share/Trash/files directory, and my /data partition has a
.Trash-1000 directory.

I also note, that when I view a picture with eog, invoked from caja's context 
menu,
and hit the delete key, eog also tells me it cannot trash the file, 
and would I like to delete it.  eog apparently inherits the faulty information 
that caja feeds it.

If I use nemo or pcmanfm-qt, there is no problem trashing the files, and if eog
is invoked from them, it has no problem trashing them with the delete key as 
well.

(I don't know why ~/.local/share/Trash[/files] is somehow owned by root, but
this is not a problem for the other FMs, and I suspect that it is intentional;
that individually, trashed files officially ought not to be deleted
individually, but are allowed to be deleted en masse when "Empty Trash" is
invoked as a command - but this is only a supposition...)

I just noticed something interesting:
If I try to trash a file in my bind-mounted /data partition, I just get the
subject text, but if I try to trash a file in my ~/ directory, I ALSO get the
following text, under the "Show more details" arrow:
"Unable to find or create trash directory for /home/scott/.reportbugrc (copy)"

-
scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lha /
...
drwxrwxr-x  10 scott scott 4.0K Oct 28 20:15 data

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lha /data
...
drwxrwxr-x 64 scott scott 4.0K Mar 14  2019 scott
drwx--  5 scott scott 4.0K Feb 28  2014 .Trash-1000

scott@ASUS-PRIME-B350M-A-CSM:~$ ls -lha .local/share
drwx--  4 root  root  4.0K Mar 16  2019 Trash

scott@ASUS-PRIME-B350M-A-CSM:~$ sudo ls -lha .local/share/Trash
...
drwx--  2 root  root  4.0K Mar 16  2019 files
drwx--  2 root  root  4.0K Mar 16  2019 info




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

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

Versions of packages caja depends on:
ii  caja-common   1.22.2-1
ii  desktop-file-utils0.24-1
ii  gvfs  1.38.1-5
ii  libatk1.0-0   2.34.1-1
ii  libc6 2.29-2
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libcaja-extension11.22.2-1
ii  libexempi82.5.1-1
ii  libexif12 0.6.21-5.1
ii  libgail-3-0   3.24.12-1
ii  libgdk-pixbuf2.0-02.40.0+dfsg-1
ii  libglib2.0-0  2.62.2-1
ii  libglib2.0-bin2.62.2-1
ii  libglib2.0-data   2.62.2-1
ii  libgtk-3-03.24.12-1
ii  libice6   2:1.0.9-2
ii  libmate-desktop-2-17  1.22.2-1
ii  libnotify40.7.8-1
ii  libpango-1.0-01.42.4-7
ii  libpangocairo-1.0-0   1.42.4-7
ii  libselinux1   2.9-2+b2
ii  libsm62:1.2.3-1
ii  libx11-6  2:1.6.8-1
ii  libxml2   2.9.4+dfsg1-7+b3
ii  mate-desktop  1.22.2-1
ii  shared-mime-info  1.10-1

Versions of packages caja recommends:
ii  gvfs-backends  1.38.1-5

Versions of packages caja suggests:
pn  engrampa
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#939177: reportbug: With "outfile" rc option, text file does not start with Package line

[scott092707]

Package: reportbug
Version: 7.5.2
Severity: normal

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: reportbug: With "outfile" rc option, text file does not start with 
Package line
Bcc: Scott Jacobs 
Message-ID: 
<156739111211.4384.421396814260056422.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.2
Date: Sun, 01 Sep 2019 22:25:12 -0400
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

I run reportbug with the "outfile" option - that is, I don't have reportbug
SEND the bug report, just write the information to a text file that I then
cut/paste into the Compose field of my browser's email site.

Despite that fact that the BRS insists on the Package: line being the first
line of the bug report, it is NOT the first line of the text file - it is
preceded by 11 other lines, plus a blank line.

Each bug I submit must be edited, to move those 12 lines to after the Package
line (actually, I move it to below the Version: and bug Severity: lines + a
blank line...) before I can send the email, and have it accepted by the BRS.



-- Package-specific info:
** Environment settings:
INTERFACE="gtk"

** /home/scott/.reportbugrc:
reportbug_version "7.5.2"
mode standard
ui gtk
email "scott092...@aol.com"
list-cc-me
submit
smtphost reportbug.debian.org
query-bts
config-files
verify
outfile '~/reportbug_report.txt'
check-available
latest-first

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

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

Versions of packages reportbug depends on:
ii  apt1.8.2
ii  python33.7.3-1
ii  python3-reportbug  7.5.2
ii  sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
pn  debconf-utils  
pn  debsums
pn  dlocate
pn  emacs24-bin-common | emacs25-bin-common
ii  exim4-daemon-light [mail-transport-agent]  4.92-8
ii  file   1:5.35-4
ii  gnupg  2.2.12-1
pn  python3-urwid  
ii  reportbug-gtk  7.5.2
ii  xdg-utils  1.1.3-1

Versions of packages python3-reportbug depends on:
ii  apt1.8.2
ii  file   1:5.35-4
ii  python33.7.3-1
ii  python3-apt1.8.4
ii  python3-debian 0.1.35
ii  python3-debianbts  2.8.2
ii  python3-requests   2.21.0-1

python3-reportbug suggests no packages.

-- no debconf information

Bug#939175: MainMenuSettings/Icon: Apparent maximum width causes long graphics to be very thin

[scott092707]

Package: lxqt-panel
Version: 0.14.1-1
Severity: wishlist

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: MainMenuSettings/Icon: Apparent maximum width causes long graphics to 
be very thin
Bcc: Scott Jacobs 
Message-ID: 
<156738784286.3691.7786862327068831120.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.2
Date: Sun, 01 Sep 2019 21:30:42 -0400
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

I have been playing around with Inkscape, trying to incorporate Debian's logo
and name into an custom "Icon" that can be selected from lxqt-panel's Main Menu
Settings.

If I just use Debian's logo, it's nice and large (Ditto with the default LXQt 
logo).
If I also include the Debian name in its official font, the combo becomes so
much smaller that I had to increase the panel height quite a bit to be able to 
read it,
and it's still really too small.

Lately I have felt guilty about not including LXQt's logo and/or name, so also
added the logo to Debian's logo+text, but things are miniscule, now...
(I also tried removing Debian's name, and just having their logo and LXQt's
logo and name - just as miniscule).

I am using a 49" QHD TV for my monitor, and I've got lots of screen real
estate, but apparently the panel will not use more than x number of pixels of
width, and scales the icon to fit the width, making the height way too small.

I wish that there could be an option that scales (one-to-one) the icon height
to the panel height, and uses whatever width results from the scaling.

I suppose there should be some sort of width limit, based upon how wide the
panel is, and what is already occupying it, but otherwise I would like to be
able to make an icon wider than the current limit - ideally, as wide as I want
to make it...



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

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

Versions of packages lxqt-panel depends on:
ii  libasound2  1.1.8-1
ii  libc6   2.28-10
ii  libdbusmenu-qt5-2   0.9.3+16.04.20160218-1
ii  libkf5solid55.54.0-1
ii  libkf5windowsystem5 5.54.0-1
ii  liblxqt-globalkeys-ui0  0.14.1-1
ii  liblxqt-globalkeys0 0.14.1-1
ii  liblxqt00.14.1-1
ii  libpulse0   12.2-4
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5dbus5 5.11.3+dfsg1-1
ii  libqt5gui5  5.11.3+dfsg1-1
ii  libqt5widgets5  5.11.3+dfsg1-1
ii  libqt5x11extras55.11.3-2
ii  libqt5xdg3  3.3.1-2
ii  libqt5xml5  5.11.3+dfsg1-1
ii  libsensors5 1:3.5.0-3
ii  libstatgrab10   0.91-1+b2
ii  libstdc++6  8.3.0-6
ii  libsysstat-qt5-00.4.2-1
ii  libx11-62:1.6.7-1
ii  libxcb-xkb1 1.13.1-2
ii  libxcb1 1.13.1-2
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-3+b3
ii  libxkbcommon-x11-0  0.8.2-1
ii  libxkbcommon0   0.8.2-1
ii  libxrender1 1:0.9.10-1
ii  lxmenu-data 0.1.5-2
ii  lxqt-policykit  0.14.1-1

Versions of packages lxqt-panel recommends:
ii  lxqt-about  0.14.1-1
ii  lxqt-config 0.14.1-2
ii  lxqt-notificationd  0.14.1-1
ii  lxqt-panel-l10n 0.14.1-1
ii  lxqt-qtplugin   0.14.0-3
ii  lxqt-runner 0.14.1-1
ii  lxqt-session0.14.1-2
ii  pavucontrol-qt  0.14.1-1
ii  qlipper 1:5.1.2-1

Versions of packages lxqt-panel suggests:
ii  lxqt   29
ii  lxqt-core  29

-- no debconf information

Bug#934533: sddm: SDDM is not informative enough: incorrect password merely erased - no message; for correct password, screen remains until desktop is displayed.

[scott092707]

Package: sddm
Version: 0.18.0-1
Severity: wishlist

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: sddm: SDDM is not informative enough: incorrect password merely erased 
- no message; for correct password, screen remains until desktop is displayed.
Bcc: Scott Jacobs 
Message-ID: 
<156557033728.2326.12276214430185371958.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.2
Date: Sun, 11 Aug 2019 20:38:57 -0400
X-Debbugs-Cc: scott092...@aol.com


Dear Maintainer,

1. If an incorrect password is entered, the entered password is merely erased.
There is no message "Password Incorrect - please re-enter." or something like
this.
(I cannot remember if it was another version of SDDM shipped with LXQt Lubuntu,
or if it was LightDM (with previous LXDE Lubuntu), but I remember that version
put up a red bar with "Incorrect password" or something similar).

2. If the password is entered correctly, nothing at all happens until the
desktop appears, and wipes out SDDM's window.
Before I got an SSD, it was sometimes 30 seconds or more before anything
happened, and I was initially afraid that the computer had frozen.  Now, it is
still 5-10 seconds that SDDM's window sits there, doing nothing.
I would suggest at least a "Password accepted." message.  The window ought to
disappear (as the user and password entry has completed). Maybe print a series
of dots, or something that indicates that the session is being started, until
the panels and desktop are ready to display.



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

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

Versions of packages sddm depends on:
ii  adduser 3.118
ii  debconf [debconf-2.0]   1.5.71
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libpam0g1.3.1-5
ii  libqt5core5a5.11.3+dfsg1-1
ii  libqt5dbus5 5.11.3+dfsg1-1
ii  libqt5gui5  5.11.3+dfsg1-1
ii  libqt5network5  5.11.3+dfsg1-1
ii  libqt5qml5  5.11.3-4
ii  libqt5quick55.11.3-4
ii  libstdc++6  8.3.0-6
ii  libsystemd0 241-5
ii  libxcb-xkb1 1.13.1-2
ii  libxcb1 1.13.1-2
ii  qml-module-qtquick2 5.11.3-4
ii  x11-common  1:7.7+19
ii  xserver-xorg [xserver]  1:7.7+19

Versions of packages sddm recommends:
ii  haveged1.9.1-7
ii  libpam-systemd 241-5
ii  sddm-theme-debian-elarun [sddm-theme]  0.18.0-1
ii  sddm-theme-debian-maui [sddm-theme]0.18.0-1

Versions of packages sddm suggests:
pn  libpam-kwallet5   
pn  qtvirtualkeyboard-plugin  

-- debconf information:
  shared/default-x-display-manager: sddm
  sddm/daemon_name: /usr/bin/sddm

Bug#836355: libglib2.0-0: makes all entries of fstab show up as desktop items

[scott092707]

Well, I changed my user-dirs.dirs back to the original state, and did the bind 
mount
from my data partition to my /home/scott/... user directories.  All works fine.

Despite the fact that my GLib2 version is before the version that fixed the
"fstab binds appear as mounts (x-gvfs-hide is being ignored) (#1271)" bug, I 
don't have the
bind mounts showing up in any of the file managers I have available, EVEN IF
the x-gvfs-hide option is NOT listed in each fstab bind mount line (I tried it 
both
WITH and WITHOUT the option).

I suppose I should assume that the bug fix (since bug #1271's fixes were done
seven months ago) was back-ported to the version on testing/sid.

I tried GDebi-ing my current debian GLib2 libraries into Peppermint 10 system,
to test this theory, but each one of the three packages pointed to one of the
others and cited incompatibilities.  Possibly I should un-install ALL THREE 
of the default ones first. instead of having GDebi replace each with the newer.
No time now...

Bug#836355: libglib2.0-0: makes all entries of fstab show up as desktop items

[scott092707]

@smcv

As it happens, I was researching the bug, the various sites I visited seemed to 
point to glib2 as being the source,
and as I have debian testing/sid, I naturally looked up glib bugs in debian, 
and found this bug report.

Since I had found more about the resolution of the bug from the pkg source in 
GitLab than was reported here,
I thought I'd report what I'd found, so people would know about it.

I personally use debian LXQt , but up until now had (as I had with Lubuntu 
LXDE/LXQt before) had attempted to use
the standard user-dirs.dirs to try to redirect programs' attempts to use the 
/home//Documents (etc.) directories
to my separate /data partition.  Experience has shown that, except for my 
Desktop directory (by file managers),
all other re-directed directories are totally ignored.

In a bug-report discussion with Alf Gaida, he suggested I bind-mount my /data 
user directories to my /home//
directories, as being better than symlinking them (or using the user-dirs.dirs 
file).
[He also said something called "User Mounts" would be even better, but I have 
yet to find out what he meant...]

Since I had an old computer that I was setting up for use, in order to give it 
away, I decided to test bind mounts on it,
before doing it for my debian install.
I had just installed Peppermint 10, and tweaked it a bit, and then added the 
bind mount lines to /etc/fstab.
It works, but adds all 8 mounts to the file manager as removable drives (and 
may also add to the desktop - not sure).
Subsequent research suggested I could solve that by adding x-gvfs-hide to the 
fstab line, but this proved wrong.
(See: https://bugs.launchpad.net/peppermint/+bug/1831302)

Checking the GLib2 version in Peppermint 10, with the version on my debian 
testing/sid, and the one listed in GitLab
as having fixed the problem, it seemed clear that if I did modify my debian's 
fstab in like manner, I would likely have
the same problem as in Peppermint.

I will probably try the bind mounts here on debian, and then also try the 
"fixed" version in experimental.

I will report back what I find.

Bug#836355: libglib2.0-0: makes all entries of fstab show up as desktop items

[scott092707]

GLib bug on GitLab (https://gitlab.gnome.org/GNOME/glib/issues/1271
"fstab binds appear as mounts (x-gvfs-hide is being ignored)")

shows two commits, the second of which 
https://gitlab.gnome.org/GNOME/glib/merge_requests/366
(and the bug itself) appear to have been fixed in GLib version 2.59.0
(only debian Experimental has a version that meets/exceeds this version)

https://gitlab.gnome.org/GNOME/glib/blob/master/NEWS :

Line# / Line
---
416 Overview of changes in GLib 2.59.0
...
431 * Hide bind mounts from GIO mount listings. (#1271)
...
490 * Bugs fixed:
...
503  - #1271 fstab binds appear as mounts (x-gvfs-hide is being ignored)
...
594  - !366 gunixmounts: Mark mounts as system internal instead of filtering out

(!365 gunixmounts: Filter out mounts with device path that was repeated
was also listed as a commit for #1271, and as merged, but I don't see it
listed anywhere - don't know if that was an oversight and it was fixed,
or got un-merged. 
https://gitlab.gnome.org/GNOME/glib/merge_requests/365)

---
I assume that if one wanted to try out the version in Experimental (2.60.3-1),
that one would have to grab all GLib packages that in testing/sid are at version
2.58.3-1 (three on my system - libglib2.0-0, -bin, -data) 
(and hope that none of the higher versions conflicts with anything...)

Bug#927729: lxqt-config-appearance UI/UX weirdnesses

[scott092707]

Package: lxqt-config
Version: 0.14.1-2
Severity: normal

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: lxqt-config-appearance UI/UX weirdnesses

Bcc: Scott Jacobs 
Message-ID: 
<155546438664.31723.10562576445905050748.report...@asus-prime-b350m-a-csm.com>
X-Mailer: reportbug 7.5.2
Date: Tue, 16 Apr 2019 21:26:26 -0400
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

I had installed Debian Testing LXQt, and was exploring LXQt theming options,
and was iterating through Appearance->Widget Styles, clicking on Apply for
each.
Several times, the app appeared to crash, as the window disappeared.  I
subsequently found that for several of the widget styles, the buttons Cancel
and Apply switched places; thus when I thought I was again clicking on Apply, I
was actually clicking on Cancel.
Other weirdnesses:
The drop down list sometimes drops up, instead of down; sometimes has
unreadable items (dark on dark, sometimes I believe the list was dark on
transparent, and one could see the rest of the window behind the widget style
name text).
When one of the two BB10* themes is selected, several things happen:
The window and buttons become very large (this is perhaps intended - they may
be HiDPI themes), but if one of the other themes is then selected, the window
does not revert to the smaller size.
The the "GTK 2 Theme" text overlays the Set GTK Themes button.
The Set GTK Themes text line / button wipe out most of the top line of the box
surrounding the GTK section.

I imagine that this would be confusing to others as well.  It is, of course,
not a serious problem, and can be worked with/around.

I have created a Simple Screen Recorder file showing (most of) this, and will
attach it to the email.



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

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

Versions of packages lxqt-config depends on:
ii  libc6 2.28-8
ii  libkf5screen-bin  4:5.14.5-1
ii  libkf5screen7 4:5.14.5-1
ii  liblxqt0  0.14.1-1
ii  libqt5core5a  5.11.3+dfsg1-1
ii  libqt5gui55.11.3+dfsg1-1
ii  libqt5svg55.11.3-2
ii  libqt5widgets55.11.3+dfsg1-1
ii  libqt5x11extras5  5.11.3-2
ii  libqt5xdg33.3.1-1
ii  libqt5xml55.11.3+dfsg1-1
ii  libstdc++68.3.0-6
ii  libudev1  241-3
ii  libx11-6  2:1.6.7-1
ii  libxcb-randr0 1.13.1-2
ii  libxcb1   1.13.1-2
ii  libxcursor1   1:1.1.15-2
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages lxqt-config recommends:
ii  disk-manager   1.1.1-2
ii  galternatives  1.0.4
ii  lxqt-config-l10n   0.14.1-2
ii  lxqt-policykit 0.14.1-1
ii  lxqt-powermanagement   0.14.1-1
ii  lxqt-qtplugin  0.14.0-2
ii  lxqt-session   0.14.1-1
ii  qt5-style-plugins  5.0.0+git23.g335dbec-2+b17
ii  system-config-printer  1.5.11-4
ii  xsettingsd 0.0.20171105+1+ge4cf9969-1

Versions of packages lxqt-config suggests:
pn  adwaita-qt 
ii  cmst   2019.01.13-1
pn  faenza-icon-theme  
pn  gnome-themes-standard  
pn  lxappearance   
ii  lxqt   29
ii  lxqt-core  29
pn  obconf-qt  
ii  partitionmanager   3.3.1-5
ii  synaptic   0.84.5

-- no debconf information