Bug#1030095: hplip is broken as reported by hp-check (see below). This renders

[Michael Haag]

Package: hplip
Version: 3.21.2+dfsg1-2
Severity: important
X-Debbugs-Cc: haa...@zoho.com

hplip is broken as reported by hp-check (see below). This renders
package unusable.


error: 'cups' package is missing or 'cups' service is not running.
error: 'libcups2' package is missing/incompatible 
error: 'libdbus-1-dev' package is missing/incompatible 
error: 'libjpeg62-turbo-dev' package is missing/incompatible 
error: 'libcups2-dev' package is missing/incompatible 
error: 'cups-bsd' package is missing/incompatible 
error: 'cups-client' package is missing/incompatible 
error: 'libcupsimage2' package is missing/incompatible 
error: 'libcupsimage2-dev' package is missing/incompatible 
error: 'libc6' package is missing/incompatible 
error: 'libusb-1.0.0-dev' package is missing/incompatible 
error: 'libsane-dev' package is missing/incompatible 
error: 'libavahi-client-dev' package is missing/incompatible 
error: 'libavahi-core-dev' package is missing/incompatible 
error: 'libavahi-common-dev' package is missing/incompatible 
error: 'libsnmp-dev' package is missing/incompatible 
error: 'snmp' package is missing/incompatible 
error: 'libssl-dev' package is missing/incompatible 
error: 'python3-pyqt4' package is missing/incompatible 
error: 'gtk2-engines-pixbuf' package is missing/incompatible 
error: 'python3-dev' package is missing/incompatible 
error: 'libtool' package is missing/incompatible 
error: 'libtool-bin' package is missing/incompatible 
error: 'g++' package is missing/incompatible 
error: 'make' package is missing/incompatible 

Missing Optional Dependencies
-
error: 'avahi-utils' package is missing/incompatible 
error: 'python3-dbus.mainloop.qt' package is missing/incompatible 



-- Package-specific info:
Saving output in log file: /home/mhaag/hp-check.log

HP Linux Imaging and Printing System (ver. 3.21.2)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball   
(.tar.gz or .run) to determine if the proper dependencies are installed to 
successfully compile HPLIP.
2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm,
etc) or an already built HPLIP supplied tarball has the proper dependencies 
installed to successfully run.
3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above 
cases (both compile- and run-time dependencies).
  

Check types:
  
a. EXTERNALDEP - External Dependencies  
  
b. GENERALDEP - General Dependencies (required both at compile and run time)
  
c. COMPILEDEP - Compile time Dependencies   
  
d. [All are run-time checks]
  
PYEXT SCANCONF QUEUES PERMISSION
  

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

warning: debian-11 version is not supported. Using debian-10.7 versions 
dependencies to verify and install...

---
| SYSTEM INFO |
---

 Kernel: 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) GNU/Linux
 Host: bullseye
 Proc: 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) GNU/Linux
 Distribution: debian 11
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.21.2
HPLIP-Home: /usr/share/hplip
warning: HPLIP-Installation: Auto installation is not supported for debian 
distro  11 version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.21.2

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/hplip/HP
ppdbase=/usr/share/ppd/hplip
doc=/usr/share/doc/hplip
html=/usr/share/doc/hplip-doc
icon=no
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-build=yes
libusb01-build=no
pp-build=no
gui-build=yes
scanner-build=yes
fax-build=yes
dbus-build=yes
cups11-build=no
doc-build=yes
shadow-build=no
hpijs-install=yes
foomatic-drv-install=yes
foomatic-ppd-install=no
foomatic-rip-hplip-install=no

Bug#1025364: sddm: SDDM scaling on HiDPI monitor is broken

[Michael Haag]

Package: sddm
Version: 0.19.0-4
Severity: normal
X-Debbugs-Cc: haa...@zoho.com

Dear Maintainer,

After upgrading to testing/bookworm SDDM loads with tiny fonts. After 
configuring
global scaling in plasma SDDM loads with gigantic fonts. After logging in plasma
desktop also loads with gigantic fonts. Using ctl-alt-del to log out reloads
SDDM with correct fonts, after which desktop appears as it should.

Rebooting repeats the entire sequence.

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

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
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:en
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.129
ii  debconf [debconf-2.0]   1.5.80
ii  libc6   2.36-5
ii  libgcc-s1   12.2.0-9
ii  libpam0g1.5.2-5
ii  libqt5core5a5.15.6+dfsg-4
ii  libqt5dbus5 5.15.6+dfsg-4
ii  libqt5gui5  5.15.6+dfsg-4
ii  libqt5network5  5.15.6+dfsg-4
ii  libqt5qml5  5.15.6+dfsg-2
ii  libqt5quick55.15.6+dfsg-2
ii  libstdc++6  12.2.0-9
ii  libsystemd0 252.2-1
ii  libxcb-xkb1 1.15-1
ii  libxcb1 1.15-1
ii  qml-module-qtquick2 5.15.6+dfsg-2
ii  x11-common  1:7.7+23
ii  xauth   1:1.1.1-1
ii  xserver-xorg [xserver]  1:7.7+23

Versions of packages sddm recommends:
ii  haveged  1.9.14-1+b1
ii  libpam-systemd   252.2-1
ii  sddm-theme-debian-maui [sddm-theme]  0.19.0-4

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

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

Bug#743824: digikam: Digikam no longer displays any album thumbnails

[Michael Haag]

The problem has indeed disappeared.

> 
> From: Steve Robbins 
> Sent: Thu Nov 22 05:20:27 CET 2018
> To: Simon Frei 
> Cc: Michael Haag , <743...@bugs.debian.org>
> Subject: Re: Bug#743824: digikam: Digikam no longer displays any album 
> thumbnails
> 
> 
> On Monday, April 16, 2018 6:28:01 AM CST you wrote:
> > On 16/04/18 04:02, Michael Haag wrote:
> > > On Mon, Apr 16, 2018, at 05:07, Simon Frei wrote:
> > >> This is 99% a problem with qt >=5.9.3, which was fixed in 5.7.0:
> > >> https://bugs.kde.org/show_bug.cgi?id=387373
> > > 
> > > So the bug has been reintroduced? I'm on Qt 5.10.1.
> > 
> > Ah I see the ambiguity in my statement: Problem exists with version
> > 5.9.3 and newer of QT and 5.6.0 and older of digikam. So you (and debian
> > testing) being on QT 5.10.1 and digikam 5.6.0 are affected. Now that
> > Steve uploaded digikam 5.9.0 to unstable, this problem will soon
> > disappear in testing too.
> 
> Dare I ask: did the problem disappear?
> I am running 5.9.0 and cannot reproduce.
> 
> Thanks,
> -Steve
> 
> 
> 
> 
> 

Bug#903541: nvidia-driver: Nvidia-driver 390-67 displays SDDM black screen

[Michael Haag]

This is an update to my previous response (copied below). I purged Kodi and 
pulseaudio, since it was after installing those items that my system went 
completely black screen.

Surprisingly, a reboot brought up a working SDDM login screen, but after 
logging in I'm presented with a black KDE desktop just as before. I can enter 
commands to reboot, so the desktop is active, but all I ever get upon logging 
in is a black screen.


On Wed, Aug 29, 2018, at 21:22, Michael Haag wrote:
> There's some really weird shit going on here.
> 
> I'm going to start from the beginning, as best as memory serves:
> 
> I had problems with surround sound on my HTPC, primarily due to the 
> limitations of S/PDIF. I decided to upgrade to a video card that 
> supported audio over HDMI. I wanted fanless, so my options were very 
> limited. I went with a NVidia GT730 card. This was several months ago.
> 
> As it turned out, Debian stable (Stretch) did not support this card. I 
> think it was both a kernel issue and an nvidia-driver issue. So I 
> upgraded to Debian testing (Buster).
> 
> Initially, I ran into an SDDM black screen problem, which I reported. I 
> was able to type in my password (don't ask why I even tried this) and my 
> KDE desktop would load normally. This is why I thought is was an SDDM 
> problem.
> 
> After some time, Debian testing updated the nvidia-driver, and lo and 
> behold, I got an SDDM login and a subsequent functioning KDE desktop 
> session, no problem. I was happy. I think the update nvidia-driver 
> version was 384.??, but I'm not sure.
> 
> All was good for awhile, but then another nvidia-driver upgrade created 
> the same problem as before. SDDM black screen, but I was still able to 
> login to a functioning KDE session.
> 
> Another nvidia-driver update (390.77) resulted in an SDDM black screen 
> but I was still able to login to a KDE session with a working desktop. 
> However, a subsequent update to KDE resulted in an SDDM black screen 
> that also resulted in a black screen KDE session. What I mean by that is 
> that SDDM allowed me to login, but KDE then also presented a black 
> screen. I could enter commands to reboot the system, so the KDE session 
> was active but there was no display.
> 
> My setup is this:
> 
> HTPC connected to a Marantz AV7005 receiver via HDMI. Marantz receiver 
> connected to a Samsung 4k TV via HDMI.
> 
> The Marantz receiver is limited to 1920x1080 video input. The nvidia-
> driver correctly detects this.
> 
> The first time I experienced this problem I applied a firmware update to 
> my Marantz receiver, but the problem persisted.
> 
> When I connect my HTPC directly to the TV there is no display problem at 
> all, but there is no way to get surround sound working that way (ARC is 
> non-functional and S/PDIF outputs digital stereo, not surround).
> 
> I suspected some type of resolution "handshaking" issue, so I searched 
> the Internet for tips on forcing resolution settings with NVidia 
> drivers. I came across instances where people were using xorg.conf to 
> override system defaults (as you suggested) so I created a file using 
> the NVidia utility and placed it in /etc/X11/.
> 
> To my surprise (according to Debian xorg.conf is deprecated) it worked. 
> Unfortunately, the fix was temporary. I successfully logged in via SDDM 
> and was presented with a functioning KDE desktop session several times. 
> I was very happy.
> 
> I subsequently installed Kodi and a few other applications that I use, 
> but discovered sound was no longer working. I checked all the multimedia 
> settings, pulse audio, Kodi audio settings, etc. etc. etc. and could 
> still not get sound working. It was working briefly, which is why I went 
> and installed Kodi in the first place.
> 
> During the process of trying to resolve the sound issues, I rebooted, 
> only to find I now have both a black SDDM screen AND a black KDE 
> session. I'm right back where I started, several days and multiple 
> installations (Kubuntu, Ubuntu, Stretch, Buster) later, including trying 
> out experimental nvidia-driver.
> 
> Fuck me. Shit works, and then it doesn't, for no apparent reason.
> 
> 
> On Wed, Aug 29, 2018, at 19:27, Vojtech Bocek wrote:
> > Yeah, xorg should be self-configuring now, but I think you can still use
> > xorg.conf file. Doing this should have the desired effect, I think, and
> > it's worth trying out (if it doesn't work, just remove xorg.conf):
> > 
> > cp -i /etc/nvidia/nvidia-drm-outputclass.conf /etc/X11/xorg.conf
> > 
> > On Sat, 25 Aug 2018 at 09:25, Michael Haag  wrote:
> > 
> > > Yes. I should have mentioned I was sending the bug report from another
> > > mach

Bug#903541: nvidia-driver: Nvidia-driver 390-67 displays SDDM black screen

[Michael Haag]

There's some really weird shit going on here.

I'm going to start from the beginning, as best as memory serves:

I had problems with surround sound on my HTPC, primarily due to the limitations 
of S/PDIF. I decided to upgrade to a video card that supported audio over HDMI. 
I wanted fanless, so my options were very limited. I went with a NVidia GT730 
card. This was several months ago.

As it turned out, Debian stable (Stretch) did not support this card. I think it 
was both a kernel issue and an nvidia-driver issue. So I upgraded to Debian 
testing (Buster).

Initially, I ran into an SDDM black screen problem, which I reported. I was 
able to type in my password (don't ask why I even tried this) and my KDE 
desktop would load normally. This is why I thought is was an SDDM problem.

After some time, Debian testing updated the nvidia-driver, and lo and behold, I 
got an SDDM login and a subsequent functioning KDE desktop session, no problem. 
I was happy. I think the update nvidia-driver version was 384.??, but I'm not 
sure.

All was good for awhile, but then another nvidia-driver upgrade created the 
same problem as before. SDDM black screen, but I was still able to login to a 
functioning KDE session.

Another nvidia-driver update (390.77) resulted in an SDDM black screen but I 
was still able to login to a KDE session with a working desktop. However, a 
subsequent update to KDE resulted in an SDDM black screen that also resulted in 
a black screen KDE session. What I mean by that is that SDDM allowed me to 
login, but KDE then also presented a black screen. I could enter commands to 
reboot the system, so the KDE session was active but there was no display.

My setup is this:

HTPC connected to a Marantz AV7005 receiver via HDMI. Marantz receiver 
connected to a Samsung 4k TV via HDMI.

The Marantz receiver is limited to 1920x1080 video input. The nvidia-driver 
correctly detects this.

The first time I experienced this problem I applied a firmware update to my 
Marantz receiver, but the problem persisted.

When I connect my HTPC directly to the TV there is no display problem at all, 
but there is no way to get surround sound working that way (ARC is 
non-functional and S/PDIF outputs digital stereo, not surround).

I suspected some type of resolution "handshaking" issue, so I searched the 
Internet for tips on forcing resolution settings with NVidia drivers. I came 
across instances where people were using xorg.conf to override system defaults 
(as you suggested) so I created a file using the NVidia utility and placed it 
in /etc/X11/.

To my surprise (according to Debian xorg.conf is deprecated) it worked. 
Unfortunately, the fix was temporary. I successfully logged in via SDDM and was 
presented with a functioning KDE desktop session several times. I was very 
happy.

I subsequently installed Kodi and a few other applications that I use, but 
discovered sound was no longer working. I checked all the multimedia settings, 
pulse audio, Kodi audio settings, etc. etc. etc. and could still not get sound 
working. It was working briefly, which is why I went and installed Kodi in the 
first place.

During the process of trying to resolve the sound issues, I rebooted, only to 
find I now have both a black SDDM screen AND a black KDE session. I'm right 
back where I started, several days and multiple installations (Kubuntu, Ubuntu, 
Stretch, Buster) later, including trying out experimental nvidia-driver.

Fuck me. Shit works, and then it doesn't, for no apparent reason.


On Wed, Aug 29, 2018, at 19:27, Vojtech Bocek wrote:
> Yeah, xorg should be self-configuring now, but I think you can still use
> xorg.conf file. Doing this should have the desired effect, I think, and
> it's worth trying out (if it doesn't work, just remove xorg.conf):
> 
> cp -i /etc/nvidia/nvidia-drm-outputclass.conf /etc/X11/xorg.conf
> 
> On Sat, 25 Aug 2018 at 09:25, Michael Haag  wrote:
> 
> > Yes. I should have mentioned I was sending the bug report from another
> > machine.
> >
> > Thanks for the response, but to my knowledge Xorg.conf has been
> > deprecated. I know there is no such file on either of my PCs.
> >
> >
> > On Fri, Aug 24, 2018, at 16:20, Vojtech Bocek wrote:
> > > Hello,
> > > I'm assuming the bug report in your message is from the PC where it is
> > > working, since the Xorg.0.log contains only HD monitor.
> > > Try adding contents of /etc/nvidia/nvidia-drm-outputclass.conf (installed
> > > by xserver-xorg-video-nvidia) into your Xorg.conf.
> > > For me, the issue was that libglx from xorg was loaded instead of the one
> > > by Nvidia, and this fixed it.
> > >
> > > I think the xserver-xorg-video-nvidia is supposed to be adding those
> > config
> > > lines automatically, but it is not.
> >

Bug#903541: nvidia-driver: Nvidia-driver 390-67 displays SDDM black screen

[Michael Haag]

Yes. I should have mentioned I was sending the bug report from another machine.

Thanks for the response, but to my knowledge Xorg.conf has been deprecated. I 
know there is no such file on either of my PCs.


On Fri, Aug 24, 2018, at 16:20, Vojtech Bocek wrote:
> Hello,
> I'm assuming the bug report in your message is from the PC where it is
> working, since the Xorg.0.log contains only HD monitor.
> Try adding contents of /etc/nvidia/nvidia-drm-outputclass.conf (installed
> by xserver-xorg-video-nvidia) into your Xorg.conf.
> For me, the issue was that libglx from xorg was loaded instead of the one
> by Nvidia, and this fixed it.
> 
> I think the xserver-xorg-video-nvidia is supposed to be adding those config
> lines automatically, but it is not.

Bug#902744: plasma-workspace: Applications won't stay pinned to their Activity

[Michael Haag]

I would like to add some info regarding the bug report below. I subsequently 
did a complete reinstall of my system and recreated my original Activities, 
except for one of the lesser used.

Afterwards, all was good. Apps stayed pinned to their Activities. After many 
days of trouble free interaction, I decided to reinstate the one Activity I 
failed to create after the reinstall. Doing so resulted in the same behavior as 
before, apps being opened across ALL Activities.

It seems it's due to one particular KDE app, KInfocenter (Info Center). 
Immediately after pinning that app to the new Activity, then logging out and 
back in, the problem reappeared.


On Sat, Jun 30, 2018, at 14:56, MH wrote:
> Package: plasma-workspace
> Version: 4:5.12.5-1
> Severity: important
> 
> Dear Maintainer,
> 
> Applications will not stay "pinned" or "locked" to their assigned 
> Activity. I've tried using 
> window placement rules by right-clicking on the window title bar and 
> choosing the 
> appropriate Activity. I've tried to set application placement under 
> Advanced window settings
> using both "Remember" and "Force" options--nothing works. After logging 
> out and logging
> back in, various applications (all native KDE apps) will show up on in 
> ALL Activities. This
> does not happen every time. Sometimes it will be days before it happens, 
> sometimes after
> two or three logouts during a single day. This has been happening across 
> several versions
> of plasma-workspace. The problem pretty much makes using Actitities 
> pointless. Given the
> severity of it, I thought it would eventually be fixed. It hasn't.
> 
> The problem is repeatable. I tried cleaning out old config files. I even 
> created a new 
> user. Same problem. I tried going back to Virtual Desktops, but it 
> happens there as well.
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages plasma-workspace depends on:
> ii  dbus-x11 1.12.8-3
> ii  drkonqi  5.12.5-1
> ii  frameworkintegration 5.46.0-1
> ii  gdb-minimal [gdb]7.12-6+b2
> ii  iso-codes3.79-1
> ii  kactivitymanagerd5.12.5-1
> ii  kde-cli-tools4:5.12.5-1
> ii  kded55.46.0-1
> ii  kinit5.46.0-1
> ii  kio  5.46.0-1
> ii  kpackagetool55.46.0-1
> ii  kwin-common  4:5.12.5-1
> ii  libappstreamqt2  0.12.1-1
> ii  libc62.27-3
> ii  libcln6  1.3.4-4
> ii  libcolorcorrect5 4:5.12.5-1
> ii  libgcc1  1:8.1.0-8
> ii  libgps23 3.17-5+b1
> ii  libice6  2:1.0.9-2
> ii  libkf5activities55.46.0-1
> ii  libkf5auth5  5.46.0-1
> ii  libkf5baloo5 5.46.0-1
> ii  libkf5bookmarks5 5.46.0-1
> ii  libkf5calendarevents55.46.0-1
> ii  libkf5completion55.46.0-1
> ii  libkf5config-bin 5.46.0-1
> ii  libkf5configcore55.46.0-1
> ii  libkf5configgui5 5.46.0-1
> ii  libkf5configwidgets5 5.46.0-1
> ii  libkf5coreaddons55.46.0-1
> ii  libkf5crash5 5.46.0-1
> ii  libkf5dbusaddons55.46.0-1
> ii  libkf5declarative5   5.46.0-1
> ii  libkf5globalaccel-bin5.46.0-1
> ii  libkf5globalaccel5   5.46.0-1
> ii  libkf5guiaddons5 5.46.0-1
> ii  libkf5holidays5  1:5.47.0-1
> ii  libkf5i18n5  5.46.0-1
> ii  libkf5iconthemes55.46.0-1
> ii  libkf5idletime5  5.46.0-1
> ii  libkf5itemviews5 5.46.0-1
> ii  libkf5jobwidgets55.46.0-1
> ii  libkf5js55.46.0-1
> ii  libkf5jsembed5   5.46.0-1
> ii  libkf5kdelibs4support5   5.46.0-1
> ii  libkf5kiocore5   5.46.0-1
> ii  libkf5kiofilewidgets55.46.0-1
> ii  libkf5kiogui55.46.0-1
> ii  libkf5kiowidgets5

Bug#743824: digikam: Digikam no longer displays any album thumbnails

[Michael Haag]

On Mon, Apr 16, 2018, at 05:07, Simon Frei wrote:
> This is 99% a problem with qt >=5.9.3, which was fixed in 5.7.0:
> https://bugs.kde.org/show_bug.cgi?id=387373
> 

So the bug has been reintroduced? I'm on Qt 5.10.1.

Bug#743824: digikam: Digikam no longer displays any album thumbnails

[Michael Haag]

See answers below. All caps are simply to make it easier to seem them.

On Mon, Apr 16, 2018, at 00:14, Steve Robbins wrote:
> On Sunday, April 15, 2018 5:01:48 AM CDT MH wrote:
> > Package: digikam
> > Version: 4:5.6.0-4+b2
> > Followup-For: Bug #743824
> > 
> > Dear Maintainer,
> > 
> > Digikam v. 5.6.0 in Debian Buster (Build date: Dec 21 2017 (target: Debian))
> > no longer displays thumbnails under any of the albums in my collection. As
> > far as I can tell, there has been no recent update of digikam and it has
> > been functioning normally.
> 
> 1. When you say "it has been functioning normally" -- do you mean to say that 
> you had been running 5.6.0-4+b2 (the December 21 build) and it was showing 
> the 
> thumbnails but then suddenly STOPPED showing thumbnails?  

YES.

> 
> 2. If so, was there any change to dependency packages on or near the day it 
> stopped working?

NOT THAT I'M AWARE OF.

> 
> > I tried deleting the databases, rebuilding thumbnails, purging digikam and
> > reinstalling. Problem remains. No error messages displayed at any time.
> 
> 3. Is digikam configured with external SQL database?

NO. IT'S CONFIGURED TO USE THE BUILT-IN DEFAULT.

> 
> Thanks,
> -Steve
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

Bug#873080: SDDM

[Michael Haag]

OK. It's not absolutely certain the problem lies ONLY with SDDM. But
since BIOS, Grub and KDE have no problem with Nvidia, it certainly does
seem LIKELY the problem is with SDDM. It's not like there hasn't been a
long history of issues with SDDM.

--
"Sometimes I sit and think, and sometimes I just sit." -- Courtney
Barnett

On Fri, Sep 29, 2017, at 04:44, Lisandro Damián Nicanor Pérez Meyer
wrote:
> On 27 September 2017 at 04:00, MH  wrote:
> > This bug, previously reported by me, still exists in sddm 0.15.0-1
> >
> > Additional information:
> >
> > The problem (black/blank screen) exhibits only when connected via an A/V
> > receiver.  Sddm displays normally when attached directly to the TV (4k).
> >
> > NVidia softare correctly enumerates the A/V device, so the latter must be
> > sending correct EDID info. Also, it reports 1080p resolution, which is the
> > maximum input resolution for the A/V device.
> >
> > The problem clearly lies with sddm.
> 
> Why? There is no full evidence of that.
> 
> SDDM might be using something the nVidia card does not supports, that
> wouldn't be the first time it happens I'm afraid. The fact that you
> see this only with SDDM doesn't means it's SDDM's fault.
> 
> Now if you could reproduce the bug with another video card, specially
> with open drivers, that would be another story (or not).

Bug#851826: pulseaudio: USB headset detected, but no sound

[Michael Haag]

Sorry I didn't get back sooner on this. I've been busy the last few
days, not to mention futzing about with your suggestions and my
equipment trying to figure out the puzzle.

Anyway, I am able to switch to a VT when playing the game, so I assume I
use pactl to change things up? If that's the case, I'll need to spend
some time familiarizing myself with that tool.

I'm using Virtualbox rather the QEMU for the Windows VM. Previously,
I've always had more trouble using pulseaudio in Virtualbox than using
ALSA. Anyway, I tried switching to the pulseaudio driver and had the
same problem.

It's not just USB, either. At least not for the VM. In the VM, both USB
and legacy audio work, with pulseaudio OR ALSA. Doesn't seem to make
much difference. Also, the problem seems to be with the audio stream
coming from the microphone. Playback through the headphones doesn't seem
to be affected.

In short, there is excessive white noise when using the legacy audio
jacks, while there seems to be some kind of latency issue when using
USB--some stuttering and/or slight garbling, but only with the
microphone.

I suspect it must be due to the headphones use of "surround sound"
processing, since I did not have any issues with my older "stereo"
headset. I just don't get why it seems to be affecting the microphone
rather than the headphones. Guess I'll just have to buy another headset.

Thanks for your time on this, and your suggestions. If nothing else, I
learned a bit more than I knew before. I apologize for wasted time on
your part.

On Mon, Jan 23, 2017, at 20:13, Felipe Sateler wrote:
> On 22 January 2017 at 02:37, Michael Haag <haa...@fastmail.net> wrote:
> > That works in most instances, but it doesn't work in my use case. I have
> > an older OpenGL/OpenAL/OSS game that takes control of the keyboard and
> > mouse when it loads. This means I cannot access pulseaudio to change
> > devices.
> 
> Can you switch to a different VT? You can try this by using
> ctrl+alt+fN (with N from 1 to 7). There it should be possible to login
> to a text console and query pulseaudio there.
> 
> If that doesn't work, setting up ssh in that computer and logging in
> via that should give you a shell with which we can inspect what
> pulseaudio is doing.
> 
> > Oddly, there is no need to do this when my headset is plugged
> > in using the legacy audio jacks. Sound is directed to BOTH my speakers
> > and my headset.
> 
> This sounds like those are picked up by the system as a single
> surround output rather than two distinct devices.
> 
> >
> > The other case is when I use a Windows-only language learning
> > application which I run in a VM. The headset works with both legacy and
> > USB connections, but the sound quality with USB is so poor the
> > application cannot match my spoken pronunciation to the recorded voice,
> > making it impossible to use the program.
> 
> Is the quality only bad with qemu? Did you set the qemu output driver
> to pulseaudio? https://wiki.archlinux.org/index.php/QEMU#Host
> 
> > Maybe neither of the above can be attributed soley to pulseaudio, but I
> > didn't have this problem with my legacy headset. I can get by with the
> > legacy audio jacks, but the USB problem means I can't use some of the
> > headset features, such as surround sound.
> 
> It doesn't sound like there is any bug in pulseaudio. From what I can
> tell, you just haven't told your app to output to the correct device
> (which is hard because it grabs the mouse and keyboard).
> 
> Also, have you tried to run your OSS program through padsp? This may
> make your app better behaved.
> 
> -- 
> 
> Saludos,
> Felipe Sateler


-- 
"Democracy is ... a form of religion; it is the worship of jackals by
jackasses." -- H. L. Mencken

Bug#851826: pulseaudio: USB headset detected, but no sound

[Michael Haag]

That works in most instances, but it doesn't work in my use case. I have
an older OpenGL/OpenAL/OSS game that takes control of the keyboard and
mouse when it loads. This means I cannot access pulseaudio to change
devices. Oddly, there is no need to do this when my headset is plugged
in using the legacy audio jacks. Sound is directed to BOTH my speakers
and my headset.

The other case is when I use a Windows-only language learning
application which I run in a VM. The headset works with both legacy and
USB connections, but the sound quality with USB is so poor the
application cannot match my spoken pronunciation to the recorded voice,
making it impossible to use the program.

Maybe neither of the above can be attributed soley to pulseaudio, but I
didn't have this problem with my legacy headset. I can get by with the
legacy audio jacks, but the USB problem means I can't use some of the
headset features, such as surround sound.

On Sat, Jan 21, 2017, at 20:11, Felipe Sateler wrote:
> Hi,
> 
> On Jan 21, 2017 00:24, "Michael Haag" <haa...@fastmail.net> wrote:
> 
> Sorry it took so long to reply. My ISP was switching our service, so I
> was without Internet access for a time. Please see attached screenshots.
> 
> 
> You did not have an audio-using application when you took the screenshot.
> Please open an audio player, start playing something, and check the
> Playback tab. In there you can choose what device the player will play
> through.
> 
> 
> Saludos,
> Felipe Sateler


-- 
"Democracy is ... a form of religion; it is the worship of jackals by
jackasses." -- H. L. Mencken

Bug#851826: pulseaudio: USB headset detected, but no sound

[Michael Haag]

Not sure what you mean by "output sink". My output devices (according to
pulseaudio) are: "Built-in Audio Analog Stereo" and "Logitech G430
Headphones". Both are enabled with volume at 100%, but I only have sound
through my external speakers.

Note also the problem is ONLY with USB. When I have the headset plugged
in using the analog jacks (no USB converter) everything works as
expected.

The REALLY odd thing is I DO have sound (both mic and headphone) when
using Windows 7 in a guest VM, whether or not I'm using the USB
converter. Unfortunately, the sound is slightly garbled/unclear, as if
interrupted or slightly delayed. This means I can no longer use my Thai
language software (Windows only) to practice pronunciation.

On Thu, Jan 19, 2017, at 19:39, Felipe Sateler wrote:
> Control: tags -1 moreinfo
> Control: severity -1 normal
> 
> On 19 January 2017 at 03:16, MH  wrote:
> > Package: pulseaudio
> > Version: 9.0-5
> > Severity: important
> >
> > Dear Maintainer,
> >
> > Pulseaudio correctly detects USB headset (headphones and microphone) but 
> > sound
> > is only output through external speakers.
> 
> Have you tried changing the output sink for your program with
> pavucontrol? What happens if you change the output?
> 
> -- 
> 
> Saludos,
> Felipe Sateler


-- 
"Democracy is ... a form of religion; it is the worship of jackals by
jackasses." -- H. L. Mencken

Bug#845103: Black screen after installing nvidia-legacy-340xx-driver (testing)

[Michael Haag]

Package: nvidia-legacy-340xx-driver
Version: testing/stretch

Sorry I can't be more specific, but my system was rendered unusable
after installing the above (recommended) driver.

The first time I attempted an upgrade from jessie to stretch. During the
upgrade I was prompted to install the above legacy driver. I did so, but
apt appeared to ALSO install the current nvidia-driver and related
packages. After rebooting I was left with a black screen, no mouse or
keyboard.

I tried to do a clean install of stretch relying on the default nouveau
driver. All was well. I then tried installing the legacy driver. This
time apt seemed to install all the correct packages, nothing from
nvidia-current. But it did seem to install the kernel headers for 4.8
rather than 4.7 which was the running kernel. End result was the same.
Black screen, no mouse no keyboard.

I believe this may be the same bug as #833895

The graphics card in my system is a nvidia 9600GT. Never experienced
this problem on this system with Wheezy or Jessie.

I hope this is helpful.

-- 
"The world is a dangerous place to live -- not because of the people who
are evil but because of the people who don't do anything about it."
--Albert Einstein

Bug#611280: Unknown host

[Michael Haag]

Package: kmail
Version: 1.13.5

After a recent squeeze update (pure squeeze, with frequent updates),
when I attempt to send email I receive the following error:

Error while checking account xx for new mail:
Unknown host mail.messagingengine.com

The host is obviously known as I can ping it. I am behind a proxy, but
did not experience this problem before the upgrade, and I have no
problem connecting to any other web sites.


--
It is hard to free fools from the chains they revere. - Voltaire
 
  Michael Haag
  haa...@fastmail.fm




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

Bug#584668: Resolved

[Michael Haag]

While attempting to burn a CD with K3b I was informed I did not have sufficient 
permissions. I was prompted to change permission on cdrecord and cdrdao (as 
I recall). After setting group ownership to cdrom (users were already members 
of this group) and reinserting the CD for burning, the CD automounted and the 
Device Notifier prompted me for action.

Not sure why those programs prevented automounting, or why group ownership 
wasn't defaulted to cdrom, but there you have it.