Bug#1068423: steam-installer: steam.desktop not removed when steam-installer is purged

[Jared Epp]

Package: steam-installer
Version: 1:1.0.0.75+ds-6
Severity: minor
X-Debbugs-Cc: jared...@pm.me

Dear Maintainer,

I just removed steam with "apt purge steam-installer". In the process it warned 
me that ~/.steam would not be removed and I should remove it manually (I did). 
But I also noticed Steam still appeared in the applications menu (I'm using KDE 
Plasma). I fixed that by deleting ~/.local/share/applications/steam.desktop 

It's extremely minor but I think it would be good to let the user know it needs
to be deleted manually along with ~/.steam , or to delete it automatically.

Thanks!

Jared

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

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

Versions of packages steam-installer depends on:
ii  debconf [debconf-2.0]  1.5.82
pn  steam-libs 
pn  steam-libs-i386
pn  zenity | yad   

steam-installer recommends no packages.

steam-installer suggests no packages.

Bug#1039063: (no subject)

[epp]

Stacktrace from this morning's plasmashell segfault crash. Crashes only
with an X11 session, not with Wayland.


Application: Plasma (plasmashell), signal: Segmentation fault

   PID: 1403 (plasmashell)
   UID: 1000 (epp)
   GID: 1000 (epp)
Signal: 11 (SEGV)
 Timestamp: Mon 2023-10-09 08:40:26 EDT (23s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (epp)
   Boot ID: 1489e4f4e3fe438e87f7ab32b856385b
Machine ID: d01c54dc30b84287b2ca7f867d54bb71
  Hostname: upstairs
   Storage: 
/var/lib/systemd/coredump/core.plasmashell.1000.1489e4f4e3fe438e87f7ab32b856385b.1403.169685522600.zst
 (present)
  Size on Disk: 7.7M
   Message: Process 1403 (plasmashell) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64
Stack trace of thread 1407:
#0  0x7fe604aa9d3c n/a (libc.so.6 + 0x8ad3c)
#1  0x7fe604a5af32 raise (libc.so.6 + 0x3bf32)
#2  0x7fe606ff3b46 _ZN6KCrash19defaultCrashHandlerEi 
(libKF5Crash.so.5 + 0x5b46)
#3  0x7fe604a5afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7fe604aa9d3c n/a (libc.so.6 + 0x8ad3c)
#5  0x7fe604a5af32 raise (libc.so.6 + 0x3bf32)
#6  0x7fe604a5afd0 n/a (libc.so.6 + 0x3bfd0)
#7  0x7fe604b1b05f __poll (libc.so.6 + 0xfc05f)
#8  0x7fe6038049ae n/a (libglib-2.0.so.0 + 0x549ae)
#9  0x7fe603804acc g_main_context_iteration 
(libglib-2.0.so.0 + 0x54acc)
#10 0x7fe604f09836 
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
 (libQt5Core.so.5 + 0x309836)
#11 0x7fe604eb017b 
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 
0x2b017b)
#12 0x7fe604ccab87 _ZN7QThread4execEv (libQt5Core.so.5 + 
0xcab87)
#13 0x7fe6060c7487 n/a (libQt5DBus.so.5 + 0x17487)
#14 0x7fe604ccbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#15 0x7fe604aa8044 n/a (libc.so.6 + 0x89044)
#16 0x7fe604b2861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1780:
#0  0x7fe604b1b05f __poll (libc.so.6 + 0xfc05f)
#1  0x7fe6038049ae n/a (libglib-2.0.so.0 + 0x549ae)
#2  0x7fe603804acc g_main_context_iteration 
(libglib-2.0.so.0 + 0x54acc)
#3  0x7fe604f0984e 
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
 (libQt5Core.so.5 + 0x30984e)
#4  0x7fe604eb017b 
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 
0x2b017b)
#5  0x7fe604ccab87 _ZN7QThread4execEv (libQt5Core.so.5 + 
0xcab87)
#6  0x7fe6069566d6 n/a (libQt5Quick.so.5 + 0x1566d6)
#7  0x7fe604ccbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#8  0x7fe604aa8044 n/a (libc.so.6 + 0x89044)
#9  0x7fe604b2861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1820:
#0  0x7fe604af2a57 wait4 (libc.so.6 + 0xd3a57)
#1  0x7fe606ff321b n/a (libKF5Crash.so.5 + 0x521b)
#2  0x7fe606ff3ad6 _ZN6KCrash19defaultCrashHandlerEi 
(libKF5Crash.so.5 + 0x5ad6)
#3  0x7fe604a5afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7fe5d5825b0e n/a (libKF5ActivitiesStats.so.1 + 
0x27b0e)
#5  0x7fe6048d44a3 n/a (libstdc++.so.6 + 0xd44a3)
#6  0x7fe604aa8044 n/a (libc.so.6 + 0x89044)
#7  0x7fe604b2861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1408:
#0  0x7fe604aa4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7fe604aa7468 pthread_cond_wait (libc.so.6 + 0x88468)
#2  0x7fe5fc30c059 n/a (r600_dri.so + 0x10c059)
#3  0x7fe5fc2be17b n/a (r600_dri.so + 0xbe17b)
#4  0x7fe5fc30bf97 n/a (r600_dri.so + 0x10bf97)
#5  0x7fe604aa8044 n/a (libc.so.6 + 0x89044)
#6  0x7fe604b2861c n/a (libc.so.6 + 0x10961c)

Stack trace of thread 1783:
#0  0x7fe604aa4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7fe604aa774c pthread_cond_timedwait (libc.so.6 + 
0x8874c)
#2  0x7fe604cd19bc

Bug#1039063: Additional stacktrace

[epp]

Attached is an additional stacktrace, occurred a few days prior.



Application: Plasma (plasmashell), signal: Segmentation fault

   PID: 1372 (plasmashell)
   UID: 1000 (epp)
   GID: 1000 (epp)
Signal: 11 (SEGV)
 Timestamp: Tue 2023-10-03 07:32:58 EDT (23s ago)
  Command Line: /usr/bin/plasmashell --no-respawn
Executable: /usr/bin/plasmashell
 Control Group: 
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
  Unit: user@1000.service
 User Unit: plasma-plasmashell.service
 Slice: user-1000.slice
 Owner UID: 1000 (epp)
   Boot ID: edb0f13c5cbe4bc08a82da292253faaf
Machine ID: d01c54dc30b84287b2ca7f867d54bb71
  Hostname: upstairs
   Storage: 
/var/lib/systemd/coredump/core.plasmashell.1000.edb0f13c5cbe4bc08a82da292253faaf.1372.169633277800.zst
 (present)
  Size on Disk: 9.7M
   Message: Process 1372 (plasmashell) of user 1000 dumped core.

Module libsystemd.so.0 from deb systemd-252.12-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.12-1~deb12u1.amd64
Stack trace of thread 1808:
#0  0x7f6b40ea9d3c n/a (libc.so.6 + 0x8ad3c)
#1  0x7f6b40e5af32 raise (libc.so.6 + 0x3bf32)
#2  0x7f6b434ecb46 _ZN6KCrash19defaultCrashHandlerEi 
(libKF5Crash.so.5 + 0x5b46)
#3  0x7f6b40e5afd0 n/a (libc.so.6 + 0x3bfd0)
#4  0x7f6b40ea9d3c n/a (libc.so.6 + 0x8ad3c)
#5  0x7f6b40e5af32 raise (libc.so.6 + 0x3bf32)
#6  0x7f6b40e5afd0 n/a (libc.so.6 + 0x3bfd0)
#7  0x7f6b40f1b03f __poll (libc.so.6 + 0xfc03f)
#8  0x7f6b3fd019ae n/a (libglib-2.0.so.0 + 0x549ae)
#9  0x7f6b3fd01acc g_main_context_iteration 
(libglib-2.0.so.0 + 0x54acc)
#10 0x7f6b41309836 
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
 (libQt5Core.so.5 + 0x309836)
#11 0x7f6b412b017b 
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 
0x2b017b)
#12 0x7f6b410cab87 _ZN7QThread4execEv (libQt5Core.so.5 + 
0xcab87)
#13 0x7f6b410cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#14 0x7f6b40ea8044 n/a (libc.so.6 + 0x89044)
#15 0x7f6b40f285fc n/a (libc.so.6 + 0x1095fc)

Stack trace of thread 1372:
#0  0x7f6b40ea4da6 n/a (libc.so.6 + 0x85da6)
#1  0x7f6b40ea7468 pthread_cond_wait (libc.so.6 + 0x88468)
#2  0x7f6b410d1a2b 
_ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b)
#3  0x7f6b42b28c45 n/a (libQt5Qml.so.5 + 0x328c45)
#4  0x7f6b42aaf841 
_ZN14QQmlTypeLoader4loadEP12QQmlDataBlobNS_4ModeE (libQt5Qml.so.5 + 0x2af841)
#5  0x7f6b42ab0180 
_ZN14QQmlTypeLoader7getTypeERK4QUrlNS_4ModeE (libQt5Qml.so.5 + 0x2b0180)
#6  0x7f6b42a88b34 
_ZN20QQmlComponentPrivate7loadUrlERK4QUrlN13QQmlComponent15CompilationModeE 
(libQt5Qml.so.5 + 0x288b34)
#7  0x7f6b4360634d n/a (libKF5Declarative.so.5 + 0xc34d)
#8  0x7f6b43970c77 _ZN11PlasmaQuick15AppletQuickItem4initEv 
(libKF5PlasmaQuick.so.5 + 0x21c77)
#9  0x7f6b386de29c n/a (plasma_appletscript_declarative.so 
+ 0x1929c)
#10 0x7f6b43972aa1 
_ZN11PlasmaQuick15AppletQuickItem10itemChangeEN10QQuickItem10ItemChangeERKNS1_14ItemChangeDataE
 (libKF5PlasmaQuick.so.5 + 0x23aa1)
#11 0x7f6b43055bed 
_ZN17QQuickItemPrivate9refWindowEP12QQuickWindow (libQt5Quick.so.5 + 0x255bed)
#12 0x7f6b43055baa 
_ZN17QQuickItemPrivate9refWindowEP12QQuickWindow (libQt5Quick.so.5 + 0x255baa)
#13 0x7f6b43055fc4 _ZN10QQuickItem13setParentItemEPS_ 
(libQt5Quick.so.5 + 0x255fc4)
#14 0x7f6b4397fd71 n/a (libKF5PlasmaQuick.so.5 + 0x30d71)
#15 0x5617df413fe6 n/a (plasmashell + 0x53fe6)
#16 0x7f6b412e8f4f n/a (libQt5Core.so.5 + 0x2e8f4f)
#17 0x7f6b412ecd6a _ZN6QTimer7timeoutENS_14QPrivateSignalE 
(libQt5Core.so.5 + 0x2ecd6a)
#18 0x7f6b412dd50d _ZN7QObject5eventEP6QEvent 
(libQt5Core.so.5 + 0x2dd50d)
#19 0x7f6b42162fae 
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 
0x162fae)
#20 0x7f6b412b16f8 
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 
0x2b16f8)
#21 0x7f6b41308c31 _ZN14QTimerInfoList14activateTimersEv 
(libQt5Core.so.5 + 0x308c31)
#22 0x7f6b413094c4 n/a (libQt5Core.so.5 + 0x3094c4)
#23 0x7f6b3fd017a9 g_main_context_dispatch 
(libglib-2.0.so.0 + 0x547a9)
#24

Bug#1052077: cinnamon-screensaver: Screensaver only occupies 1/4 of screen when using 200% scaling after monitor power cycle

[Jared Epp]

Package: cinnamon-screensaver
Version: 5.6.3-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: jared...@pm.me

Dear Maintainer,

When I lock my screen and turn off my monitor, after I turn it on again, the
screensaver only occupies 1/4 of the screen (the top left quarter).

You can see the other 3/4 of the screen as though the screen isn't locked.
So it's a problem if you were depending on the screen saver / locker to hide
any information there. But the whole screen is still locked and you can't
interact with it.

My screen is 4K and I'm using 200% scaling.  I tried reducing scaling to 100%
and it fixes the issue.  I also didn't have the issue in Bullseye and only
encountered it after I upgraded to Bookworm.

My video card is the integrated graphics in an AMD Ryzen 5700G (Vega).

I tagged the bug as "upstream" when reportbug asked because it seems to be an
outstanding bug there:
https://github.com/linuxmint/cinnamon-screensaver/issues/337
but it was initially reported on cinnamon-screensaver 4.4.1, but I didn't have
the issue in Bullseye which used 4.8.1. 

If I can provide any other info let me know.  Thanks!

Jared

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

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

Versions of packages cinnamon-screensaver depends on:
ii  cinnamon-desktop-data   5.6.1-1
ii  gir1.2-accountsservice-1.0  22.08.8-6
ii  gir1.2-cinnamondesktop-3.0  5.6.1-1
ii  gir1.2-cscreensaver-1.0 5.6.3-1
ii  gir1.2-gkbd-3.0 3.28.1-1
ii  gir1.2-glib-2.0 1.74.0-3
ii  gir1.2-gtk-3.0  3.24.37-2
ii  gir1.2-xapp-1.0 2.4.2-3
ii  iso-flags-png-320x240   1.0.2-2
ii  libc6   2.36-9+deb12u1
ii  libcairo2   1.16.0-7
ii  libcscreensaver05.6.3-1
ii  libglib2.0-02.74.6-2
ii  libgtk-3-0  3.24.37-2
ii  libpango-1.0-0  1.50.12+ds-1
ii  python3 3.11.2-1+b1
ii  python3-gi  3.42.2-3+b1
ii  python3-gi-cairo3.42.2-3+b1
ii  python3-setproctitle1.3.1-1+b2
ii  python3-xapp2.4.0-1
ii  python3-xlib0.33-2

Versions of packages cinnamon-screensaver recommends:
ii  libpam-gnome-keyring  42.1-1+b2

cinnamon-screensaver suggests no packages.

-- no debconf information

Bug#1040316: Related to main python3 package?

[epp]

The following packages have unmet dependencies:

 python3 : PreDepends: python3-minimal (= 3.11.4-1) but 3.11.4-3 is 
installed


E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

Bug#1037105: dkms unable to compile r8168-dkms to backported kernel

[epp]

Package: r8168-dkms
Version: 8.048.03-3


I installed SpiralLinux, which installs the current Debian stable at the time 
the image was released, in this case, bullseye and it also enables Backports by 
default. During the upgrade process after the initial installation, dkms 
reported it was having issues with the r8168-dkms package, presumably 
compiling/adding (?) it to the kernel, which is a backported kernel.


The kernel version is 6.1.0-0.deb11.7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 
6.1.20-2~bpo11+1 (2023-04-23) x86_64 GNU/Linux

My network card has the Realtek r8169 chip on it, so this package was 
unnecessary. Once I purged the package and rebooted, network connectivity was 
restored. 


Although I do not require this package, I felt that it should be reported to 
Debian as a bug, in hopes that a fix is found for those who require the package.


Below is information that was displayed during the time dkms was having the 
issue, plus the log file from the stated filename.




dkms: running auto installation service for kernel 6.1.0-0.deb11.7-amd64:
Kernel preparation unnecessary for this kernel.  Skipping...


Building module:
cleaning build area...
make -j2 KERNELRELEASE=6.1.0-0.deb11.7-amd64 -C 
/lib/modules/6.1.0-0.deb11.7-amd64/build 
M=/var/lib/dkms/r8168/8.050.03/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.0-0.deb11.7-amd64 
(x86_64)
Consult /var/lib/dkms/r8168/8.050.03/build/make.log for more information.




DKMS make.log for r8168-8.050.03 for kernel 6.1.0-0.deb11.7-amd64 (x86_64)
Sun 04 Jun 2023 02:50:39 PM EDT
make: Entering directory '/usr/src/linux-headers-6.1.0-0.deb11.7-amd64'
  CC [M]  /var/lib/dkms/r8168/8.050.03/build/r8168_n.o
  CC [M]  /var/lib/dkms/r8168/8.050.03/build/r8168_asf.o
In file included from /var/lib/dkms/r8168/8.050.03/build/r8168_n.c:87:
/var/lib/dkms/r8168/8.050.03/build/r8168_n.c: In function ‘rtl8168_init_one’:
/var/lib/dkms/r8168/8.050.03/build/r8168.h:564:57: error: too many arguments to 
function ‘netif_napi_add’
  564 | #define RTL_NAPI_CONFIG(ndev, priv, function, weight)   
netif_napi_add(ndev, >napi, function, weight)
  | ^~
/var/lib/dkms/r8168/8.050.03/build/r8168_n.c:26866:9: note: in expansion of 
macro ‘RTL_NAPI_CONFIG’
26866 | RTL_NAPI_CONFIG(dev, tp, rtl8168_poll, R8168_NAPI_WEIGHT);
  | ^~~
In file included from /var/lib/dkms/r8168/8.050.03/build/r8168_n.c:46:
/usr/src/linux-headers-6.1.0-0.deb11.7-common/include/linux/netdevice.h:2569:1: 
note: declared here
 2569 | netif_napi_add(struct net_device *dev, struct napi_struct *napi,
  | ^~
/var/lib/dkms/r8168/8.050.03/build/r8168_n.c:26907:25: error: implicit 
declaration of function ‘netif_set_gso_max_size’; did you mean 
‘netif_set_tso_max_size’? [-Werror=implicit-function-declaration]
26907 | netif_set_gso_max_size(dev, LSO_32K);
  | ^~
  | netif_set_tso_max_size
cc1: some warnings being treated as errors
make[1]: *** 
[/usr/src/linux-headers-6.1.0-0.deb11.7-common/scripts/Makefile.build:255: 
/var/lib/dkms/r8168/8.050.03/build/r8168_n.o] Error 1

Bug#1035779: linux-image-5.10.0-22: kvm/qemu kernel null pointer dereference, VM doesn't start

[Jared Epp]

Hi Salvatore,

Thanks for the quick reply!

> > 
> > This sounds similar to the
> > https://forum.proxmox.com/threads/with-latest-5-15-104-1-pve-windows-server-vm-freeze-stuck.125294/
> > issue. Would you be able to verify two things:
> > 
> > Check how the Windows VM is configured and if you pass the
> > '+hv-tlbflush' flag.
> > 

You're right, I am passing this flag. In libvirt I use:


  

  

  


I tried this fix first and it works. If I reboot into 5.10.0-22-amd64, and 
instead set  above, the VM boots.

> > Additionally, would the attached patch make the issue go away?

Thanks for the patch; it does fix the issue.  I set this back: , applied your patch to 5.10.0-22-amd64 and booted my newly patched 
kernel, and the VM boots.

> 
> 
> Now with patch attached.
> 
> Regards,
> Salvatore

Thanks for your help.  This is my first time using the BTS so I hope I've done 
everything correctly. If there's anything else I should do, or if you want me 
to test something, let me know.

Jared

Bug#1035779: linux-image-5.10.0-22: kvm/qemu kernel null pointer dereference, VM doesn't start

[Jared Epp]

Package: src:linux
Version: 5.10.178-3
Severity: normal
X-Debbugs-Cc: jared...@pm.me

Dear Maintainer,

After I updated my Debian 11 host kernel to 5.10.0-22, my VM guest (Windows 10 
using KVM / qemu / libvirt) no longer boots and there's a kernel null pointer 
dereference along with a call trace, etc. in the system log. If I reboot and 
choose 5.10.0-21 in grub, the VM works as expected and there's no error in the 
log.

Below, reportbug included part of the kernel log but it missed part of the 
problem so I pasted that in, I hope that's okay. If you need any other 
information let me know.

Thanks

Jared Epp

-- Package-specific info:
** Version:
Linux version 5.10.0-22-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.178-3 (2023-04-22)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-22-amd64 root=/dev/mapper/panthro--vg-root ro quiet 
mem_sleep_default=s2idle default_hugepagesz=1G hugepages=8

** Tainted: D (128)
 * kernel died recently, i.e. there was an OOPS or BUG

** Kernel log:
[   51.576266] BUG: kernel NULL pointer dereference, address: 
[   51.576269] #PF: supervisor read access in kernel mode
[   51.576270] #PF: error_code(0x) - not-present page
[   51.576271] PGD 0 P4D 0 
[   51.576273] Oops:  [#1] SMP NOPTI
[   51.576275] CPU: 6 PID: 2209 Comm: CPU 0/KVM Not tainted 5.10.0-22-amd64 #1 
Debian 5.10.178-3
[   51.576276] Hardware name: ASUS System Product Name/CROSSHAIR VI HERO, BIOS 
8701 02/08/2023
[   51.576280] RIP: 0010:find_first_bit+0x19/0x40
[   51.576281] Code: 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc cc cc cc 49 89 
f0 48 85 f6 74 28 31 c0 eb 0d 48 83 c0 40 48 83 c7 08 4c 39 c0 73 17 <48> 8b 17 
48 85 d2 74 eb f3 48 0f bc d2 48 01 d0 49 39 c0 4c 0f 47
[   51.576282] RSP: 0018:a99ac3a23a30 EFLAGS: 00010246
[   51.576283] RAX:  RBX: a99ac38a5000 RCX: 
[   51.576283] RDX:  RSI: 0120 RDI: 
[   51.576284] RBP:  R08: 0120 R09: 94e2c1ae72a8
[   51.576284] R10: 000f R11:  R12: 94e2c1ae72a8
[   51.576285] R13: 0323 R14: 0003 R15: 0006
[   51.576286] FS:  (0053) GS:94e89e98(002b) 
knlGS:f8033f006000
[   51.576286] CS:  0010 DS:  ES:  CR0: 80050033
[   51.576287] CR2:  CR3: 00018e4ee000 CR4: 00750ee0
[   51.576287] PKRU: 5554
[   51.576288] Call Trace:
[   51.576307]  kvm_make_vcpus_request_mask+0x38/0xf0 [kvm]
[   51.576319]  kvm_hv_flush_tlb+0x147/0x370 [kvm]
[   51.576328]  ? kvm_page_track_is_active+0x12/0x50 [kvm]
[   51.576336]  ? make_spte+0x146/0x260 [kvm]
[   51.576344]  ? mmu_spte_update+0x11/0x1c0 [kvm]
[   51.576351]  ? set_spte+0xee/0x140 [kvm]
[   51.576358]  ? mmu_set_spte+0x327/0x4a0 [kvm]
[   51.576365]  ? kvm_release_pfn_clean+0x22/0x40 [kvm]
[   51.576372]  ? direct_page_fault+0x223/0xa20 [kvm]
[   51.576374]  ? svm_get_segment+0x18/0x100 [kvm_amd]
[   51.576382]  ? kvm_get_cs_db_l_bits+0x35/0x70 [kvm]
[   51.576383]  ? svm_get_segment+0x18/0x100 [kvm_amd]
[   51.576390]  ? kvm_get_cs_db_l_bits+0x35/0x70 [kvm]
[   51.576398]  kvm_hv_hypercall+0x176/0x580 [kvm]
[   51.576401]  ? get_cpu_vendor+0x40/0xa0
[   51.576403]  ? native_load_tr_desc+0x67/0x70
[   51.576411]  kvm_arch_vcpu_ioctl_run+0xbe8/0x1740 [kvm]
[   51.576419]  kvm_vcpu_ioctl+0x21e/0x5b0 [kvm]
[   51.576422]  __x64_sys_ioctl+0x8b/0xc0
[   51.576424]  do_syscall_64+0x33/0x80
[   51.576426]  entry_SYSCALL_64_after_hwframe+0x61/0xc6
[   51.576428] RIP: 0033:0x7fad816f2237
[   51.576429] Code: 00 00 00 48 8b 05 59 cc 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 29 cc 0d 00 f7 d8 64 89 01 48
[   51.576429] RSP: 002b:7fad7ce65508 EFLAGS: 0246 ORIG_RAX: 
0010
[   51.576430] RAX: ffda RBX: ae80 RCX: 7fad816f2237
[   51.576431] RDX:  RSI: ae80 RDI: 001c
[   51.576431] RBP: 55a3e17511c0 R08: 55a3df109848 R09: 55a3df5335c0
[   51.576432] R10:  R11: 0246 R12: 
[   51.576432] R13: 55a3df54fbc0 R14: 7fad7ce657c0 R15: 00802000
[   51.576434] Modules linked in: xt_nat veth nft_chain_nat xt_MASQUERADE 
nf_nat nf_conntrack_netlink xfrm_user xfrm_algo br_netfilter vhost_net vhost 
vhost_iotlb tap tun bridge stp llc overlay ip6t_REJECT nf_reject_ipv6 xt_hl 
ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_multiport nft_limit 
snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi 
snd_hda_intel nls_ascii snd_intel_dspcfg nls_cp437 soundwire_intel vfat 
soundwire_generic_allocation fat snd_soc_core snd_compress soundwire_cadence 
snd_hda_codec edac_mce_amd xt_limit xt_addr

Bug#1023511: Plymouth bootsplash not displayed, cannot be set - packages installed but commands not found

[epp]

Package:  plymouth
Version:  22.02.122-2

Debian stable and unstable were first installed to a VirtualBox using 
VMSVGA (VMware) for virtual graphics. Then installed to two desktops on 
the system hardware. One has an AMD Radeon 3000 on-board, the other has 
an AMD Radeon HD 5450 on a PCI-E x16 video card.


The plymouth bootsplash would not and does not display with any of these 
installations. The plymouth-set-default-theme command reports the 
command update-initrams is not found. In the VirtualBox, 
plymouth-set-default-theme wasn't found:



When installed to hardware:

root@downstairs:/home/epp# /usr/sbin/plymouth-set-default-theme -R spinner
/usr/libexec/plymouth/plymouth-update-initrd: 5: update-initramfs: not found

Note update-initramfs is installed.

root@downstairs:/home/epp# dpkg -S update-initramfs
initramfs-tools: /usr/share/man/man8/update-initramfs.8.gz
initramfs-tools: /etc/initramfs-tools/update-initramfs.conf
initramfs-tools: /usr/share/bash-completion/completions/update-initramfs
initramfs-tools: /usr/share/man/man5/update-initramfs.conf.5.gz
initramfs-tools: /usr/sbin/update-initramfs


When installed to a VirtualBox (since deleted, no longer using 
VirtualBox), plymouth-set-default-theme was also not found.


root@debian:/home/epp# apt install plymouth plymouth-themes
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
plymouth is already the newest version (22.02.122-2).
plymouth-themes is already the newest version (22.02.122-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@debian:/home/epp# plymouth-set-default-theme -l
bash: plymouth-set-default-theme: command not found

Bug#1015826: thunderbird: Thunderbird and Claws Mail (in sid/unstable) not connecting to imap.comcast.net

[epp]

Package: thunderbird
Version: 1:102.0.2-1
Severity: important
X-Debbugs-Cc: e...@mcom.com

Dear Maintainer,

Thunderbird and Claws mail (4.1.0) in sid/unstable wiil not connect to
imap.comcast.net when adding new accounts. Thunderbird will only 
connect to imap.comcast.net if IPv6 is disabled through its configuration
editor and IPv6 cannot be disabled in Claws Mail.

Previously reported under bug 1015225, but it likely is not the correct
package.


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/2 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 thunderbird depends on:
ii  debianutils  5.7-0.2
ii  fontconfig   2.13.1-4.4
ii  libasound2   1.2.7.1-1
ii  libatk1.0-0  2.38.0-1
ii  libc62.33-8
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libdbus-1-3  1.14.0-2
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.2-4
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.1.0-7
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
ii  libglib2.0-0 2.72.3-1
ii  libgtk-3-0   3.24.34-1
ii  libicu71 71.1-3
ii  libnspr4 2:4.34-1
ii  libnss3  2:3.79-1
ii  libpango-1.0-0   1.50.7+ds-1
ii  librnp0  0.16.0-1
ii  libstdc++6   12.1.0-7
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.7.5-1
ii  libx11-xcb1  2:1.7.5-1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxext6 2:1.3.4-1
ii  libxrandr2   2:1.5.2-2+b1
ii  psmisc   23.5-2
ii  x11-utils7.7+5
ii  zenity   3.42.1-2
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages thunderbird recommends:
ii  hunspell-ar [hunspell-dictionary]3.2-1.2
ii  hunspell-be [hunspell-dictionary]0.53-3.1
ii  hunspell-bg [hunspell-dictionary]1:7.2.0-2
ii  hunspell-bs [hunspell-dictionary]1:7.2.0-2
ii  hunspell-ca [hunspell-dictionary]3.0.6+repack1-2
ii  hunspell-cs [hunspell-dictionary]1:7.2.0-2
ii  hunspell-da [hunspell-dictionary]1:7.2.0-2
ii  hunspell-de-at [hunspell-dictionary] 20161207-9
ii  hunspell-de-ch [hunspell-dictionary] 20161207-9
ii  hunspell-de-de [hunspell-dictionary] 20161207-9
ii  hunspell-el [hunspell-dictionary]1:7.2.0-2
ii  hunspell-en-gb [hunspell-dictionary] 1:7.2.0-2
ii  hunspell-en-us [hunspell-dictionary] 1:2020.12.07-2
ii  hunspell-eu [hunspell-dictionary]5.1-2
ii  hunspell-fr-classical [hunspell-dictionary]  1:7.0-1
ii  hunspell-gl [hunspell-dictionary]1:7.2.0-2
ii  hunspell-gu [hunspell-dictionary]1:7.2.0-2
ii  hunspell-hi [hunspell-dictionary]1:7.2.0-2
ii  hunspell-hr [hunspell-dictionary]1:7.2.0-2
ii  hunspell-hu [hunspell-dictionary]1:7.2.0-2
ii  hunspell-id [hunspell-dictionary]1:7.2.0-2
ii  hunspell-is [hunspell-dictionary]1:7.2.0-2
ii  hunspell-it [hunspell-dictionary]1:7.2.0-2
ii  hunspell-kk [myspell-dictionary] 1.1-2.1
ii  hunspell-kmr [hunspell-dictionary]   1:7.2.0-2
ii  hunspell-ko [hunspell-dictionary]0.7.92-1
ii  hunspell-lt [hunspell-dictionary]1:7.2.0-2
ii  hunspell-lv [hunspell-dictionary]1.4.0-1.1
ii  hunspell-ne [hunspell-dictionary]1:7.2.0-2
ii  hunspell-nl [hunspell-dictionary]2:2.20.19-2
ii  hunspell-pl [hunspell-dictionary]1:7.2.0-2
ii  hunspell-pt-br [hunspell-dictionary] 1:7.2.0-2
ii  hunspell-pt-pt [hunspell-dictionary] 1:7.2.0-2
ii  hunspell-ro [hunspell-dictionary]1:7.2.0-2
ii  hunspell-ru [hunspell-dictionary]1:7.2.0-2
ii  hunspell-si [hunspell-dictionary]1:7.2.0-2
ii  hunspell-sl [hunspell-dictionary]1:7.2.0-2
ii  hunspell-sr [hunspell-dictionary]1:7.2.0-2
ii  hunspell-sv [hunspell-dictionary]1:7.2.0-2
ii  hunspell-te [hunspell-dictionary]1:7.2.0-2
ii  hunspell-th [hunspell-dictionary]1:7.2.0-2
ii  hunspell-vi [hunspell-dictionary]1:7.2.0-2
ii  myspell-eo [myspell-dictionary]  2.1.2000.02.25-60
ii  myspell-es [myspell-dictionary]  1.11-19
ii  myspell-et [myspell-dictionary]  1:20030606-32
ii  myspell-fa [myspell-dictionary]  0.20070816-3.2
ii  myspell-ga [myspell-dictionary]  2.0-27.1
ii  myspell-he [myspell-dictionary]  1.4-3.1
ii  myspell-nb [myspell-dictionary]   

Bug#1015225: ifupdown: E-Mail apps cannot connect to imap.comcast.net without disabling IPv6

[epp]

Package: ifupdown
Version: 0.8.37
Severity: important
X-Debbugs-Cc: e...@mcom.com

Dear Maintainer,

I have installed Sid in a virtual-machine using virt-manager to create
it. I discovered that both Claws Mail and Thunderbird will not connect
to imap.comcast.net (default is SSL/TLS). virt-manager creates virtual
machines with IPv4 networking by default, IPv6 is not enabled. 

It is not possible to disable IPv6 in Claws Mail, but if I disable IPv6
in Thunderbird using its config editor, Thunderbird will then
successfully connect to it.

I posted a message on Debian User Forums about this (link below) and it was
suggested to file a bug report. I'm not sure if ifupdown is the correct
package causing this issue, or if it's another package, or if it's with 
the IMAP server itself.

Please note that I am not having this issue with Debian Stable or Debian
Testing (also in separate virtual machines), only with Sid.

https://forums.debian.net/viewtopic.php?f=5=152455

Thank you.



-- Package-specific info:
--- /etc/network/interfaces:
source-directory /etc/network/interfaces.d

--- /etc/network/interfaces.d/setup:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

--- up and down scripts installed:
/etc/network/if-down.d:
total 4
-rwxr-xr-x 1 root root 1015 Feb  6  2021 avahi-autoipd
lrwxrwxrwx 1 root root   32 May 15 06:22 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-post-down.d:
total 4
-rwxr-xr-x 1 root root 1409 Mar  7  2020 wireless-tools
lrwxrwxrwx 1 root root   32 May 15 06:22 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-pre-up.d:
total 8
-rwxr-xr-x 1 root root 4191 Mar  7  2020 wireless-tools
lrwxrwxrwx 1 root root   32 May 15 06:22 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-up.d:
total 4
-rwxr-xr-x 1 root root 923 Feb  6  2021 avahi-autoipd
lrwxrwxrwx 1 root root  32 May 15 06:22 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/2 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 ifupdown depends on:
ii  adduser   3.122
ii  iproute2  5.18.0-1
ii  libc6 2.33-8
ii  lsb-base  11.2

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.4.3-2

Versions of packages ifupdown suggests:
pn  ppp 
pn  rdnssd  

-- no debconf information

Bug#1014153: lxqt-panel: Cannot mouse over grouped window

[epp]

Package: lxqt-panel
Version: 0.16.1-1
Followup-For: Bug #1014153
X-Debbugs-Cc: e...@mcom.com

Dear Maintainer,

This bus is still present in the current version installed on
sid/unstable. If a window is grouped, e.g. Thunderbird main window and a
compose window, clicking the group  will display both of the window titles but
they do not stay on-screen long enough to select the second (compose)
window.


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

Kernel: Linux 5.18.0-2-amd64 (SMP w/2 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 lxqt-panel depends on:
ii  libasound2  1.2.7.1-1
ii  libc6   2.33-8
ii  libdbusmenu-qt5-2   0.9.3+16.04.20160218-2+b1
ii  libkf5solid55.94.0-1
ii  libkf5windowsystem5 5.94.0-1
ii  liblxqt-globalkeys-ui0  0.16.0-1
ii  liblxqt-globalkeys0 0.16.0-1
ii  liblxqt00.16.0-1
ii  libpulse0   15.0+dfsg1-4+b1
ii  libqt5core5a5.15.4+dfsg-4
ii  libqt5dbus5 5.15.4+dfsg-4
ii  libqt5gui5  5.15.4+dfsg-4
ii  libqt5widgets5  5.15.4+dfsg-4
ii  libqt5x11extras55.15.4-2
ii  libqt5xdg3  3.6.0-1+b1
ii  libqt5xml5  5.15.4+dfsg-4
ii  libsensors5 1:3.6.0-7
ii  libstatgrab10   0.92.1-1
ii  libstdc++6  12.1.0-5
ii  libsysstat-qt5-00.4.6-1
ii  libx11-62:1.7.5-1
ii  libxcb-xkb1 1.14-3
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxkbcommon-x11-0  1.4.0-1
ii  libxkbcommon0   1.4.0-1
ii  libxrender1 1:0.9.10-1.1
ii  lxmenu-data 0.1.5-2.1
ii  lxqt-policykit  0.16.0-1

Versions of packages lxqt-panel recommends:
ii  lxqt-about  0.16.0-1
ii  lxqt-config 0.16.1-1
ii  lxqt-notificationd  0.16.0-1
ii  lxqt-panel-l10n 0.16.1-1
ii  lxqt-qtplugin   0.16.0-1+b1
ii  lxqt-runner 0.16.0-1
ii  lxqt-session0.16.0-1
ii  pavucontrol-qt  0.16.0-2
ii  qlipper 1:5.1.2-1+b1

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

-- no debconf information

Bug#1014986: lxqt-config: Icon theme not changing in LXQt menus when the theme is changed.

[epp]

Package: lxqt-config
Version: 0.16.1-1
Severity: normal
X-Debbugs-Cc: e...@mcom.com

Dear Maintainer,

When changing the icon theme in LXQt, it only changes the icons on the
desktop, they do not change in the LXQt menus. It should also change the
icons in the menus, as some applications now show two different icons,
one on the desktop and one in the menus. Claws Mail is an example of
this when using the Oxygen icon theme. The correct icon (round) is
displayed on the desktop, but the LXQt Internet menu instead displays a yellow
envelope icon for this.

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

Kernel: Linux 5.18.0-2-amd64 (SMP w/2 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 lxqt-config depends on:
ii  libc6 2.33-8
ii  libkf5screen-bin  4:5.24.5-1
ii  libkf5screen7 4:5.24.5-1
ii  liblxqt0  0.16.0-1
ii  libqt5core5a  5.15.4+dfsg-4
ii  libqt5gui55.15.4+dfsg-4
ii  libqt5svg55.15.4-2
ii  libqt5widgets55.15.4+dfsg-4
ii  libqt5x11extras5  5.15.4-2
ii  libqt5xdg33.6.0-1+b1
ii  libqt5xml55.15.4+dfsg-4
ii  libstdc++612.1.0-5
ii  libudev1  251.3-1
ii  libx11-6  2:1.7.5-1
ii  libxcb-randr0 1.14-3
ii  libxcb1   1.14-3
ii  libxcursor1   1:1.2.1-1
ii  libxfixes31:6.0.0-1
ii  libxi62:1.8-1
ii  zlib1g1:1.2.11.dfsg-4

Versions of packages lxqt-config recommends:
ii  galternatives  1.0.8
ii  lxqt-config-l10n   0.16.1-1
ii  lxqt-policykit 0.16.0-1
ii  lxqt-powermanagement   0.16.0-1
ii  lxqt-qtplugin  0.16.0-1+b1
ii  lxqt-session   0.16.0-1
ii  qt5-style-plugins  5.0.0+git23.g335dbec-4+b4
ii  system-config-printer  1.5.16-1
ii  xsettingsd 1.0.2-1

Versions of packages lxqt-config suggests:
pn  adwaita-qt  
ii  cmst2019.01.13-1+b1
pn  faenza-icon-theme   
pn  gnome-themes-standard   
pn  gparted | partitionmanager  
pn  lxappearance
ii  lxqt30
ii  lxqt-core   30
pn  obconf-qt   
ii  synaptic0.91.2

-- no debconf information

Bug#905874: libreoffice: No input of accented characters through dead-key composition

[Mario L. Epp K.]

On 08/12/2018 02:54 AM, Rene Engelhard wrote:

On Sat, Aug 11, 2018 at 05:20:54PM -0400, Mario L. Epp K. wrote:

On 08/11/2018 09:58 AM, Rene Engelhard wrote:

retitle 905874: libreoffice: No input of accented characters through dead-key 
composition in gen and kde4 plugins
thanks

On Sat, Aug 11, 2018 at 01:22:51PM +0200, Rene Engelhard wrote:

On Fri, Aug 10, 2018 at 10:18:30PM -0400, Mario L. Epp wrote:

On researching the issue prior to making this report, I found this issue
reported on the DocumentFoundation Bugzilla as "Bug 112770" at
<https://bugs.documentfoundation.org/show_bug.cgi?id=112770>. But I am not
shure how to implement the solution from 6.0.0 to 5.2.7.2 for KDE5 on Debian 9.


Maybe install the 6.1.0 backport from stretch-backports? That one also
has a KDE5 integration other than that KDE4 thingy "working" with KDE5.

This will never be fixed in stable properly (until buster releases of
course with above new KDE5 integration)


I uninstalled the "stable" LibreOffice before installing the "backported"
LibreOffice with the Metapackage. After the instalation I rebooted the
computer.


The metapackage doesn't install the KDE integration.


But the same bug appears also in LibreOffice 6.1.0.2 (Build ID:
1:6.1.0~rc2-3~bpo9+1), Linux 4.9; UI render: defualt; VCL: x11.

 
And with the KDE integration actually installed? That would just leave
the non-integrated LO affected only.


Thank you, I did not catch that omission. After installing the 
KDE-integration, the dead keys work as advertised. And in the 
Help->About dialog it now reads: "VCL: gtk3_kde5"


I also did a clean install of Debian 9 (new partition tables). The basic 
KDE system for a clean/new installation worked without a problem. The 
Help->About dialog of LibreOffice reads: version 5.2.7.2 (Build ID: 
1:5.2.7-1+deb9u4); VCL: kde4


The other new install with this bug had the "/home" partition mounted 
from the previous installation of Debian 8. So, maybe there was some 
problem with the upgrade.


It seems that I have now been able to resolve this problem to my 
satisfaction. Thank you.


Mario L. Epp

Bug#905874: libreoffice: No input of accented characters through dead-key composition

[Mario L. Epp K.]

Bug also present in the Backport.

On 08/11/2018 09:58 AM, Rene Engelhard wrote:

retitle 905874: libreoffice: No input of accented characters through dead-key 
composition in gen and kde4 plugins
thanks

On Sat, Aug 11, 2018 at 01:22:51PM +0200, Rene Engelhard wrote:

On Fri, Aug 10, 2018 at 10:18:30PM -0400, Mario L. Epp wrote:

On researching the issue prior to making this report, I found this issue
reported on the DocumentFoundation Bugzilla as "Bug 112770" at
<https://bugs.documentfoundation.org/show_bug.cgi?id=112770>. But I am not
shure how to implement the solution from 6.0.0 to 5.2.7.2 for KDE5 on Debian 9.


Maybe install the 6.1.0 backport from stretch-backports? That one also
has a KDE5 integration other than that KDE4 thingy "working" with KDE5.

This will never be fixed in stable properly (until buster releases of
course with above new KDE5 integration)


I uninstalled the "stable" LibreOffice before installing the 
"backported" LibreOffice with the Metapackage. After the instalation I 
rebooted the computer.


But the same bug appears also in LibreOffice 6.1.0.2 (Build ID: 
1:6.1.0~rc2-3~bpo9+1), Linux 4.9; UI render: defualt; VCL: x11.


Mario L. Epp

Bug#905874: libreoffice: No input of accented characters through dead-key composition

[Mario L. Epp]

Package: libreoffice
Version: 1:5.2.7-1+deb9u4
Severity: important

Dear Maintainer,

   * What led up to the situation?

After reinstalling Debian 9.5 on my main workstation, accented characters in
would not appear in Writer when I used the dead keys on the "Spanish" keyboard
layout. Previously I had been using Debian 8 without any problems. I am using
KDE as GUI. The problem  manifested also in Calc. Though other applications had
no problem.

On a secondary computer I upgraded from Debian 8 to Debian 9 with the standard
aplications in KDE. And here I observed the same problem of the accented
characters not showing up when composed with the dead keys.

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

First I closed and restarted LibreOffice: Same problem.
Then I logged out and back in: Same problem.
Then I rebooted the whole system: Problem continues.

I added several other keyboard layouts, with no solution to the problem. Apart
from my normal "Spanish" layout, I tried the US-QWERTY and the German layouts.

I can insert the accented characters with the "Special Character" feature. But
when typing text, that is NOT a workable workaround.

   * What was the outcome of this action?

No solution so far. So far all other aplications have no problem with dead-key-
composition.

   * What outcome did you expect instead?

Input the accented characters for different languages without having to do menu
and dialog acrobatics, instead of the standard dead-key-composition.


On researching the issue prior to making this report, I found this issue
reported on the DocumentFoundation Bugzilla as "Bug 112770" at
. But I am not
shure how to implement the solution from 6.0.0 to 5.2.7.2 for KDE5 on Debian 9.



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

Kernel: Linux 4.9.0-7-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US:en (charmap=locale: Cannot set LC_ALL to default locale: 
No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libreoffice depends on:
ii  dpkg   1.18.25
ii  fonts-dejavu   2.37-1
ii  libreoffice-avmedia-backend-gstreamer  1:5.2.7-1+deb9u4
ii  libreoffice-base   1:5.2.7-1+deb9u4
ii  libreoffice-calc   1:5.2.7-1+deb9u4
ii  libreoffice-core   1:5.2.7-1+deb9u4
ii  libreoffice-draw   1:5.2.7-1+deb9u4
ii  libreoffice-impress1:5.2.7-1+deb9u4
ii  libreoffice-java-common1:5.2.7-1+deb9u4
ii  libreoffice-math   1:5.2.7-1+deb9u4
ii  libreoffice-report-builder-bin 1:5.2.7-1+deb9u4
ii  libreoffice-writer 1:5.2.7-1+deb9u4
ii  python3-uno1:5.2.7-1+deb9u4

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-1
ii  fonts-crosextra-carlito 20130920-1
ii  fonts-linuxlibertine5.3.0-2
ii  fonts-sil-gentium-basic 1.1-7
ii  libreoffice-librelogo   1:5.2.7-1+deb9u4
ii  libreoffice-nlpsolver   0.9+LibO5.2.7-1+deb9u4
ii  libreoffice-ogltrans1:5.2.7-1+deb9u4
ii  libreoffice-pdfimport   1:5.2.7-1+deb9u4
ii  libreoffice-report-builder  1:5.2.7-1+deb9u4
ii  libreoffice-script-provider-bsh 1:5.2.7-1+deb9u4
ii  libreoffice-script-provider-js  1:5.2.7-1+deb9u4
ii  libreoffice-script-provider-python  1:5.2.7-1+deb9u4
ii  libreoffice-sdbc-postgresql 1:5.2.7-1+deb9u4
ii  libreoffice-wiki-publisher  1.2.0+LibO5.2.7-1+deb9u4

Versions of packages libreoffice suggests:
ii  cups-bsd   2.2.1-8+deb9u2
ii  default-jre [java5-runtime]2:1.8-58
pn  gstreamer1.0-libav 
pn  gstreamer1.0-plugins-bad   
ii  gstreamer1.0-plugins-base  1.10.4-1
ii  gstreamer1.0-plugins-good  1.10.4-1
pn  gstreamer1.0-plugins-ugly  
ii  hunspell-de-at [hunspell-dictionary]   20161207-1
ii  hunspell-de-de-frami [hunspell-dictionary] 1:5.2.5-1
ii  hunspell-en-us [hunspell-dictionary]   20070829-7
ii  hunspell-es [hunspell-dictionary]  1:5.2.5-1
ii  hunspell-pt-br [hunspell-dictionary]   1:5.2.5-1
ii  hyphen-de [hyphen-hyphenation-patterns]1:5.2.5-1
ii  hyphen-en-us [hyphen-hyphenation-patterns] 2.8.8-5
ii  hyphen-es [hyphen-hyphenation-patterns]1:5.2.5-1
ii  hyphen-pt-br 

Bug#869497: acpi-support-base: does not suspend after wakeonlan until after keyboard/mouse input

[Jared Epp]

Package: acpi-support-base
Version: 0.142-8
Severity: normal

Dear Maintainer,

I am not sure if I should report this to acpi-support-base or wakeonlan.

If I use wakeonlan from another system to wake this system from suspend, it
wakes as expected but does not go back into suspend.  If I then push a key on
the keyboard on this system, it will suspend as expected after 30 minutes.

To set this up I just installed the wakeonlan package on the other system, and
on this system I edited /etc/network/interfaces.d/eth0 to read

auto eth0
iface eth0 inet dhcp
ethernet-wol g

If you need any other info let me know.  Thanks!

Jared



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

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

Versions of packages acpi-support-base depends on:
ii  acpid  1:2.0.28-1+b1

acpi-support-base recommends no packages.

Versions of packages acpi-support-base suggests:
pn  acpi-support  
pn  consolekit

-- no debconf information

Bug#775768: libfreenect-dev: Missing dependency on libusb-1.0-0-dev

[Dietrich Epp]

Package: libfreenect-dev
Version: 1:0.2.0+dfsg-2
Severity: normal

Dear Maintainer,

libfreenect-dev is missing a dependency on libusb-1.0-0-dev.  Without
libusb-1.0-0-dev installed, you get the following error:

$ pkg-config --libs --cflags libfreenect
Package libusb-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libusb-1.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libusb-1.0', required by 'libfreenect', not found

Once the dependency is installed, it works:

$ sudo apt-get install libusb-1.0-0-dev
$ pkg-config --libs --cflags libfreenect
-I/usr/include/libusb-1.0 -lfreenect



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

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

Versions of packages libfreenect-dev depends on:
ii  libfreenect0.2  1:0.2.0+dfsg-2

libfreenect-dev recommends no packages.

libfreenect-dev suggests no packages.

-- no debconf information


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

Bug#709550: jackd: netone backend crashes

[Dietrich Epp]

Package: jackd
Version: 5
Severity: normal

Running jackd with the netone backend causes jackd to crash.

$ jackd --no-realtime -d netone
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2013 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Cannot create thread 1 Operation not permitted
Cannot create thread 1 Operation not permitted
Cannot create thread 1 Operation not permitted
JACK server starting in non-realtime mode
Cannot lock down 82274202 byte memory area (Cannot allocate memory)
*** Error in `jackd': free(): invalid pointer: 0x7f2a708621af ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7aac6)[0x7f2a6eef0ac6]
/lib/x86_64-linux-gnu/libc.so.6(+0x7b843)[0x7f2a6eef1843]
/usr/lib/x86_64-linux-gnu/jack/jack_netone.so(+0x8777)[0x7f2a6ec6a777]
/usr/lib/x86_64-linux-gnu/jack/jack_netone.so(_ZN4Jack16JackNetOneDriver9FreePortsEv+0x183)[0x7f2a6ec6b8a3]
/usr/lib/x86_64-linux-gnu/jack/jack_netone.so(_ZN4Jack16JackNetOneDriver10InitializeEv+0x29)[0x7f2a6ec6aeb5]
/usr/lib/x86_64-linux-gnu/libjackserver.so.0(_ZN4Jack22JackWaitThreadedDriver17JackDriverStarter7ExecuteEv+0x2d)[0x7f2a70577f83]
/usr/lib/x86_64-linux-gnu/libjackserver.so.0(_ZN4Jack15JackPosixThread13ThreadHandlerEPv+0xd8)[0x7f2a70562a54]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e0e)[0x7f2a702dee0e]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f2a6ef5e95d]

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

Kernel: Linux 3.8-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages jackd depends on:
ii  jackd2  1.9.9.5+20130306git47f3a68c-1

jackd recommends no packages.

jackd suggests no packages.

-- no debconf information


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

Bug#709554: libgtkglext1-dev: missing libpangox-1.0-dev dependency

[Dietrich Epp]

Package: libgtkglext1-dev
Version: 1.2.0-3
Severity: normal

The .pc files require pangox.pc but libpangox-1.0-dev is not a dependency.

$ pkg-config --libs gdkglext-1.0
Package pangox was not found in the pkg-config search path.
Perhaps you should add the directory containing `pangox.pc'
to the PKG_CONFIG_PATH environment variable
Package 'pangox', required by 'GdkGLExt', not found



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

Kernel: Linux 3.8-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libgtkglext1-dev depends on:
ii  libgl1-mesa-dev [libgl-dev]8.0.5-6
ii  libglu1-mesa-dev [libglu-dev]  8.0.5-6
ii  libgtk2.0-dev  2.24.18-1
ii  libgtkglext1   1.2.0-3
ii  libice-dev 2:1.0.8-2
ii  libsm-dev  2:1.2.1-2
ii  libxmu-dev 2:1.1.1-1
ii  libxt-dev  1:1.1.3-1

libgtkglext1-dev recommends no packages.

libgtkglext1-dev suggests no packages.

-- no debconf information


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

Bug#683880: gnome-shell: Sometimes hangs during startup

[Dietrich Epp]

I've also experienced this problem.  If I kill -9 gnome-shell, then
everything suddenly starts working again.  It won't respond to SIGTERM.

My backtrace looks similar to Jason White's, and I have a core file if
someone wants it (Debian x86_64 Wheezy, gnome-shell 3.4.2-2).


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

Bug#632591: bash-completion: Completion of shell redirection broken for psql

[Dietrich Epp]

Package: bash-completion
Version: 1:1.2-3
Severity: normal


I am restoring a Postgres database in the following way:

$ psql -U dbuser -d dbname  dbname.db

However, tab completion does not work for completing the database dump name.
I tried ./TAB and that didn't work either (it should be obvious that I'm
trying to look for a file in the current directory).

What's especially surprising is that this functionality works just fine
without bash-completion installed.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bash-completion depends on:
ii  bash  4.1-3  The GNU Bourne Again SHell

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information



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

Bug#303531: More Information

[Ladd Epp]

Keyboard functionality is absent when connecting full screen. If fullscreen is 
disabled, then the keyboard works, and you can enter your password for login. 
You can re-enable fullscreen mode and keyboard functionality seems to be OK. 
I've had several occasions where keyboard functionality drops during the 
middle of my session. Disabling fullscreen mode fixes this problem as well.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]