Bug#1015003: transmission-daemon Out of Memory
I am experiencing the same issue. Sep 26 04:33:33 server kernel: Out of memory: Killed process 16702 (transmission-da) total-vm:4933944kB, anon-rss:3566896kB, file-rss:0kB, shmem-rss:0kB, UID:133 pgtables:7928kB oom_score_adj:0d
Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel
This issue has been resolved with new nvidia-kernel-dkms version 450.66-1 -- Jiri
Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel
$ dpkg-reconfigure nvidia-kernel-dkms Does not seem to build the modules for 5.8.0-1. Building initial module for 5.8.0-1-amd64 Error! Bad return status for module build on kernel: 5.8.0-1-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/440.82/build/make.log for more information. make.log attached. -- Jiri DKMS make.log for nvidia-current-440.82 for kernel 5.8.0-1-amd64 (x86_64) Wed 09 Sep 2020 10:54:48 AEST make KBUILD_OUTPUT=/lib/modules/5.8.0-1-amd64/build V=1 -C /lib/modules/5.8.0-1-amd64/source M=/var/lib/dkms/nvidia-current/440.82/build ARCH=x86_64 NV_KERNEL_SOURCES=/lib/modules/5.8.0-1-amd64/source NV_KERNEL_OUTPUT=/lib/modules/5.8.0-1-amd64/build NV_KERNEL_MODULES="nvidia nvidia-uvm nvidia-modeset nvidia-drm" INSTALL_MOD_DIR=kernel/drivers/video NV_SPECTRE_V2=0 modules make[1]: Entering directory '/usr/src/linux-headers-5.8.0-1-common' make -C /usr/src/linux-headers-5.8.0-1-amd64 -f /usr/src/linux-headers-5.8.0-1-common/Makefile modules make[2]: Entering directory '/usr/src/linux-headers-5.8.0-1-amd64' test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) make -f /usr/src/linux-headers-5.8.0-1-common/scripts/Makefile.build obj=/var/lib/dkms/nvidia-current/440.82/build \ single-build= \ need-builtin=1 need-modorder=1 scripts/Makefile.lib:8: 'always' is deprecated. Please use 'always-y' instead NV_CONFTEST_CMD=/bin/sh /var/lib/dkms/nvidia-current/440.82/build/conftest.sh " gcc-10" x86_64 /lib/modules/5.8.0-1-amd64/source /lib/modules/5.8.0-1-amd64/build NV_CONFTEST_CFLAGS=-O2 -D__KERNEL__ -DKBUILD_BASENAME="#conftest16218" -DKBUILD_MODNAME="#conftest16218" -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/10/include -I/lib/modules/5.8.0-1-amd64/source/arch/x86/include/asm/mach-default -I/lib/modules/5.8.0-1-amd64/source/include/asm-x86/mach-default -I/lib/modules/5.8.0-1-amd64/build/include2 -I/lib/modules/5.8.0-1-amd64/build/include -include /lib/modules/5.8.0-1-amd64/build/include/generated/autoconf.h -I/lib/modules/5.8.0-1-amd64/source/arch/x86/include -I/lib/modules/5.8.0-1-amd64/source/arch/x86/include/uapi -I/lib/modules/5.8.0-1-amd64/build/arch/x86/include/generated -I/lib/modules/5.8.0-1-amd64/build/arch/x86/include/generated/uapi -I/lib/modules/5.8.0-1-amd64/source/include -I/lib/modules/5.8.0-1-amd64/source/include/uapi -I/lib/modules/5.8.0-1-amd64/source/include/xen -I/lib/modules/5.8.0-1-amd64/build/include/generated/uapi -I/var/lib/dkms/nvidia-current/440.82/build/common/inc -I/var/lib/dkms/nvidia-current/440.82/build -Wall -MD -Wno-cast-qual -Wno-error -Wno-format-extra-args -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"440.82\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Werror=undef -DNV_SPECTRE_V2=0 -fno-pie -Wall -Wundef -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -flive-patching=inline-clone -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -fmacro-prefix-map=/usr/src/linux-headers-5.8.0-1-common/= -fcf-protection=none -Wno-packed-not-aligned KBUILD_CFLAGS=-Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -fno-jump-tables -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow
Bug#949877: bluetooth device with multi device connection crashes kernel
I am still having a lot of problems with my bluetooth devices. 1. It seems that devices I don't want are being added to the list of devices. I don't know why. 2. Bluetooth audio is dropping on UE BOOM or Bose SoundSport while listening youtube. Here is my list of devices which I use: Device 00:0D:44:F5:8D:C5 UE BOOM Device F9:44:98:56:AB:91 Surface Keyboard Device 90:7F:61:56:FB:B4 ThinkPad Compact Bluetooth Keyboard with TrackPoint Device 28:11:A5:01:4B:E3 Bose SoundSport Device C6:0D:63:20:82:20 MX Anywhere 2 Jan 27 20:25:45 superman systemd[1943]: Stopped target Bluetooth. Jan 27 20:25:45 superman systemd[1]: Stopped target Bluetooth. Jan 27 20:25:50 superman kernel: [16081.620424] usb 1-14: new full-speed USB device number 7 using xhci_hcd Jan 27 20:25:50 superman kernel: [16081.770736] usb 1-14: New USB device found, idVendor=8087, idProduct=0029, bcdDevice= 0.01 Jan 27 20:25:50 superman kernel: [16081.770742] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jan 27 20:25:50 superman kernel: [16081.773818] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 Jan 27 20:25:50 superman kernel: [16081.774833] Bluetooth: hci0: Device revision is 1 Jan 27 20:25:50 superman kernel: [16081.774836] Bluetooth: hci0: Secure boot is enabled Jan 27 20:25:50 superman kernel: [16081.774838] Bluetooth: hci0: OTP lock is enabled Jan 27 20:25:50 superman kernel: [16081.774839] Bluetooth: hci0: API lock is enabled Jan 27 20:25:50 superman kernel: [16081.774841] Bluetooth: hci0: Debug lock is disabled Jan 27 20:25:50 superman kernel: [16081.774844] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Jan 27 20:25:50 superman kernel: [16081.775308] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.sfi Jan 27 20:25:50 superman kernel: [16081.775314] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi Jan 27 20:25:51 superman systemd[1943]: Reached target Bluetooth. Jan 27 20:25:51 superman systemd[1]: Reached target Bluetooth. Jan 27 20:25:52 superman kernel: [16083.461385] Bluetooth: hci0: Waiting for firmware download to complete Jan 27 20:25:52 superman kernel: [16083.461659] Bluetooth: hci0: Firmware loaded in 1649283 usecs Jan 27 20:25:52 superman kernel: [16083.461714] Bluetooth: hci0: Waiting for device to boot Jan 27 20:25:52 superman kernel: [16083.474908] Bluetooth: hci0: Device booted in 12911 usecs Jan 27 20:25:52 superman kernel: [16083.474933] bluetooth hci0: firmware: direct-loading firmware intel/ibt-20-1-3.ddc Jan 27 20:25:52 superman kernel: [16083.474935] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc Jan 27 20:25:52 superman kernel: [16083.489922] Bluetooth: hci0: Applying Intel DDC parameters completed Jan 27 20:25:58 superman kernel: [16089.913385] input: MX Anywhere 2 Keyboard as /devices/virtual/misc/uhid/0005:046D:B018.0006/input/input41 Jan 27 20:25:58 superman kernel: [16089.913645] input: MX Anywhere 2 Mouse as /devices/virtual/misc/uhid/0005:046D:B018.0006/input/input42 Jan 27 20:25:58 superman kernel: [16089.914043] hid-generic 0005:046D:B018.0006: input,hidraw2: BLUETOOTH HID v0.09 Keyboard [MX Anywhere 2] on 94:E6:F7:21:32:92 Jan 27 20:26:16 superman kernel: [16107.445033] input: 00:0D:44:F5:8D:C5 as /devices/virtual/input/input44 Jan 27 20:26:29 superman kernel: [16120.363474] mce: CPU11: Package temperature above threshold, cpu clock throttled (total events = 34640) Jan 27 20:26:29 superman kernel: [16120.363475] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 34640) Jan 27 20:26:29 superman kernel: [16120.363476] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 34641) Jan 27 20:26:29 superman kernel: [16120.363476] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 34640) Jan 27 20:26:29 superman kernel: [16120.363527] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 34641) Jan 27 20:26:29 superman kernel: [16120.363529] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 34641) Jan 27 20:26:29 superman kernel: [16120.363529] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 34640) Jan 27 20:26:29 superman kernel: [16120.363530] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 34641) Jan 27 20:26:29 superman kernel: [16120.363531] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 34640) Jan 27 20:26:29 superman kernel: [16120.363532] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 34640) Jan 27 20:26:29 superman kernel: [16120.363533] mce: CPU10: Package temperature above threshold, cpu clock throttled (total events = 34640) Jan 27 20:26:29 superman kernel: [16120.363534] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 34641)
Bug#944350: RE: Bug#944350: RE: [External] Bug#944350: systemd: screen remains off after waking up from suspend
FYI Lenovo also pushed a fix into a BIOS. CHANGES IN THIS RELEASE Version 1.28 [Important updates] Nothing [New functions or enhancements] - Supported BIOS password authentication before entering into MEBx. - Updated Regulatory Information. [Problem fixes] - Fixed an issue where OLED panel might not trun on after resuming from sleep on Linux. https://download.lenovo.com/pccbbs/mobiles/n2oul07w.txt Regards, Jiri On Fri, 6 Dec 2019 18:47:05 + Mark Pearson wrote: > Hi Jiri, > > I'm pretty sure it's not in 5.3.0-2. Are you sure? I can look again but I recently did put in a merge request to get it pulled into sid: https://salsa.debian.org/kernel-team/linux/merge_requests/188 > > Not sure if/when it will be accepted (it's only my 2nd attempt at doing this) but hopefully someone looks at it and thinks it's useful) > > Mark > > > -Original Message- > > From: Jiri Kanicky > > Sent: Saturday, November 30, 2019 6:56 AM > > To: 944...@bugs.debian.org > > Subject: Bug#944350: RE: [External] Bug#944350: systemd: screen remains > > off after waking up from suspend > > > > Hi. > > > > It seems that Debian 5.3.0-2-amd64 includes the code in the patch > > already and I still have the issue. > > > > Jiri > > > > On Mon, 25 Nov 2019 16:45:55 + Mark Pearson > > wrote: > > > > > Hi, > > > > > > I don't know if this is helpful but I recently debugged a similar > > issue on the Lenovo P1Gen2. There the problem is only with the > > integrated graphics and an OLED screen - we tracked it down to an issue > > in the i915 driver where it wasn't giving enough time for eDP link > > training. It turned out this was due to the driver using the wrong > > clocks after a suspend and resume . > > > > > > Intel recently up-streamed a fix (commit 2f216a85 - it went into > > 5.4-rc8) > > > > > > I'm working on doing a patch that I'm hoping to get into Debian to > > backport - just not done yet :) The patch is pretty small (I've attached > > it) so you might want to give it a go and see if it helps. > > > > > > Note - we did also test X1 extreme with OLED panel and didn't see a > > problem therebut it's a really subtle timing issue so some units > > might be more susceptible than others. Maybe worth a go? > > > > > > If it does make a difference let me know. > > > Mark > > > >
Bug#949877: Acknowledgement (bluetooth device with multi device connection crashes kernel)
I am wondering if this issue is related to my thinkpad bluetooth keyboard. After futher testing with MS Bluetooth keyboard, I don't seem to experience the same issue. Jan 27 01:49:28 superman kernel: [ 1899.070955] lenovo 0005:17EF:6048.0005: unknown main item tag 0x0 Jan 27 01:49:28 superman kernel: [ 1899.071160] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.0005/input/input32 Jan 27 01:49:28 superman kernel: [ 1899.071394] lenovo 0005:17EF:6048.0005: input,hidraw2: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on 94:e6:f7:21:32:92 Jan 27 01:49:28 superman upowerd[1572]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.0005/power_supply/hid-90:7f:61:56:fb:b4-battery Jan 27 01:49:58 superman acpid: input device has been disconnected, fd 20 Jan 27 01:50:08 superman kernel: [ 1938.786389] lenovo 0005:17EF:6048.0006: unknown main item tag 0x0 Jan 27 01:50:08 superman kernel: [ 1938.787485] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.0006/input/input33 Jan 27 01:50:08 superman kernel: [ 1938.788549] lenovo 0005:17EF:6048.0006: input,hidraw2: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on 94:e6:f7:21:32:92 Jan 27 01:50:08 superman upowerd[1572]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.0006/power_supply/hid-90:7f:61:56:fb:b4-battery Jan 27 01:50:15 superman acpid: input device has been disconnected, fd 20 Jan 27 01:50:16 superman kernel: [ 1946.671068] lenovo 0005:17EF:6048.0007: unknown main item tag 0x0 Jan 27 01:50:16 superman kernel: [ 1946.671806] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:768/0005:17EF:6048.0007/input/input34 Jan 27 01:50:16 superman kernel: [ 1946.673081] lenovo 0005:17EF:6048.0007: input,hidraw2: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on 94:e6:f7:21:32:92 Jan 27 01:50:16 superman upowerd[1572]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:768/0005:17EF:6048.0007/power_supply/hid-90:7f:61:56:fb:b4-battery Jan 27 01:50:43 superman acpid: input device has been disconnected, fd 20 Jan 27 01:50:58 superman kernel: [ 1988.780923] lenovo 0005:17EF:6048.0008: unknown main item tag 0x0 Jan 27 01:50:58 superman kernel: [ 1988.781611] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.0008/input/input35 Jan 27 01:50:58 superman kernel: [ 1988.782493] lenovo 0005:17EF:6048.0008: input,hidraw2: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on 94:e6:f7:21:32:92 Jan 27 01:50:58 superman upowerd[1572]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.0008/power_supply/hid-90:7f:61:56:fb:b4-battery Jan 27 01:51:08 superman acpid: input device has been disconnected, fd 20 Jan 27 01:51:08 superman kernel: [ 1999.243822] lenovo 0005:17EF:6048.0009: unknown main item tag 0x0 Jan 27 01:51:08 superman kernel: [ 1999.244866] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:768/0005:17EF:6048.0009/input/input36 Jan 27 01:51:08 superman kernel: [ 1999.245901] lenovo 0005:17EF:6048.0009: input,hidraw2: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on 94:e6:f7:21:32:92 Jan 27 01:51:09 superman upowerd[1572]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:768/0005:17EF:6048.0009/power_supply/hid-90:7f:61:56:fb:b4-battery Jan 27 01:51:16 superman acpid: input device has been disconnected, fd 20 Jan 27 01:51:16 superman kernel: [ 2006.912527] lenovo 0005:17EF:6048.000A: unknown main item tag 0x0 Jan 27 01:51:16 superman kernel: [ 2006.913215] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.000A/input/input37 Jan 27 01:51:16 superman kernel: [ 2006.914116] lenovo 0005:17EF:6048.000A: input,hidraw2: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on 94:e6:f7:21:32:92 Jan 27 01:51:16 superman upowerd[1572]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:17EF:6048.000A/power_supply/hid-90:7f:61:56:fb:b4-battery Jan 27 01:51:25
Bug#944350: RE: Bug#944350: RE: [External] Bug#944350: systemd: screen remains off after waking up from suspend
Hi Mark. I updated kernel to 5.4.0-1 and the issue is resolved. Thank you for your help. You were right :). Thx Jiri Linux superman 5.4.0-1-amd64 #1 SMP Debian 5.4.6-1 (2019-12-27) x86_64 GNU/Linux On Fri, 6 Dec 2019 18:47:05 + Mark Pearson wrote: > Hi Jiri, > > I'm pretty sure it's not in 5.3.0-2. Are you sure? I can look again but I recently did put in a merge request to get it pulled into sid: https://salsa.debian.org/kernel-team/linux/merge_requests/188 > > Not sure if/when it will be accepted (it's only my 2nd attempt at doing this) but hopefully someone looks at it and thinks it's useful) > > Mark > > > -Original Message- > > From: Jiri Kanicky > > Sent: Saturday, November 30, 2019 6:56 AM > > To: 944...@bugs.debian.org > > Subject: Bug#944350: RE: [External] Bug#944350: systemd: screen remains > > off after waking up from suspend > > > > Hi. > > > > It seems that Debian 5.3.0-2-amd64 includes the code in the patch > > already and I still have the issue. > > > > Jiri > > > > On Mon, 25 Nov 2019 16:45:55 + Mark Pearson > > wrote: > > > > > Hi, > > > > > > I don't know if this is helpful but I recently debugged a similar > > issue on the Lenovo P1Gen2. There the problem is only with the > > integrated graphics and an OLED screen - we tracked it down to an issue > > in the i915 driver where it wasn't giving enough time for eDP link > > training. It turned out this was due to the driver using the wrong > > clocks after a suspend and resume . > > > > > > Intel recently up-streamed a fix (commit 2f216a85 - it went into > > 5.4-rc8) > > > > > > I'm working on doing a patch that I'm hoping to get into Debian to > > backport - just not done yet :) The patch is pretty small (I've attached > > it) so you might want to give it a go and see if it helps. > > > > > > Note - we did also test X1 extreme with OLED panel and didn't see a > > problem therebut it's a really subtle timing issue so some units > > might be more susceptible than others. Maybe worth a go? > > > > > > If it does make a difference let me know. > > > Mark > > > >
Bug#944350: RE: [External] Bug#944350: systemd: screen remains off after waking up from suspend
Hi. It seems that Debian 5.3.0-2-amd64 includes the code in the patch already and I still have the issue. Jiri On Mon, 25 Nov 2019 16:45:55 + Mark Pearson wrote: > Hi, > > I don't know if this is helpful but I recently debugged a similar issue on the Lenovo P1Gen2. There the problem is only with the integrated graphics and an OLED screen - we tracked it down to an issue in the i915 driver where it wasn't giving enough time for eDP link training. It turned out this was due to the driver using the wrong clocks after a suspend and resume . > > Intel recently up-streamed a fix (commit 2f216a85 - it went into 5.4-rc8) > > I'm working on doing a patch that I'm hoping to get into Debian to backport - just not done yet :) The patch is pretty small (I've attached it) so you might want to give it a go and see if it helps. > > Note - we did also test X1 extreme with OLED panel and didn't see a problem therebut it's a really subtle timing issue so some units might be more susceptible than others. Maybe worth a go? > > If it does make a difference let me know. > Mark >
Bug#944350: systemd: screen remains off after waking up from suspend
Further to the issue, when I set BIOS to discrete graphics only, I am experiencing the same issue when booting the system from shutdown state. The screen stays off, but the OS is booted and working.
Bug#944350: systemd: screen remains off after waking up from suspend
dmesg attached from the ssh session I also would like to confirm that the screen stays black after restarting sddm. Only after full restart the screen comes back on. Thanks Jiri [0.00] Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-1-amd64 root=UUID=2ada8948-de67-4928-a568-e963f3ca65f4 ro quiet [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [0.00] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x8a988fff] usable [0.00] BIOS-e820: [mem 0x8a989000-0x8aac3fff] type 20 [0.00] BIOS-e820: [mem 0x8aac4000-0x8fa61fff] reserved [0.00] BIOS-e820: [mem 0x8fa62000-0x8fca9fff] ACPI NVS [0.00] BIOS-e820: [mem 0x8fcaa000-0x8fd0efff] ACPI data [0.00] BIOS-e820: [mem 0x8fd0f000-0x8fd0] usable [0.00] BIOS-e820: [mem 0x8fd1-0x97ff] reserved [0.00] BIOS-e820: [mem 0x9800-0x9814efff] usable [0.00] BIOS-e820: [mem 0x9814f000-0x9814] reserved [0.00] BIOS-e820: [mem 0x9815-0x987f] usable [0.00] BIOS-e820: [mem 0x9880-0x9f7f] reserved [0.00] BIOS-e820: [mem 0xfe01-0xfe010fff] reserved [0.00] BIOS-e820: [mem 0x0001-0x00085e7f] usable [0.00] NX (Execute Disable) protection: active [0.00] efi: EFI v2.60 by Lenovo [0.00] efi: TPMFinalLog=0x8fca2000 SMBIOS=0x8d7a1000 SMBIOS 3.0=0x8d794000 ACPI=0x8fd0e000 ACPI 2.0=0x8fd0e014 MEMATTR=0x851d3018 ESRT=0x8b589000 [0.00] secureboot: Secure boot could not be determined (mode 0) [0.00] SMBIOS 3.1.1 present. [0.00] DMI: LENOVO 20QVCTO1WW/20QVCTO1WW, BIOS N2OET38W (1.25 ) 08/19/2019 [0.00] tsc: Detected 2600.000 MHz processor [0.09] tsc: Detected 2599.992 MHz TSC [0.09] e820: update [mem 0x-0x0fff] usable ==> reserved [0.11] e820: remove [mem 0x000a-0x000f] usable [0.15] last_pfn = 0x85e800 max_arch_pfn = 0x4 [0.19] MTRR default type: write-back [0.19] MTRR fixed ranges enabled: [0.20] 0-9 write-back [0.21] A-B uncachable [0.22] C-F write-protect [0.22] MTRR variable ranges enabled: [0.24] 0 base 00C000 mask 7FC000 uncachable [0.25] 1 base 00A000 mask 7FE000 uncachable [0.25] 2 base 009C00 mask 7FFC00 uncachable [0.26] 3 base 009B00 mask 7FFF00 uncachable [0.27] 4 base 20 mask 60 uncachable [0.27] 5 base 10 mask 70 uncachable [0.28] 6 base 40 mask 40 uncachable [0.29] 7 disabled [0.29] 8 disabled [0.29] 9 disabled [0.000496] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [0.000657] last_pfn = 0x98800 max_arch_pfn = 0x4 [0.008920] esrt: Reserving ESRT space from 0x8b589000 to 0x8b5890d8. [0.008929] Using GB pages for direct mapping [0.008930] BRK [0x65fe01000, 0x65fe01fff] PGTABLE [0.008932] BRK [0x65fe02000, 0x65fe02fff] PGTABLE [0.008933] BRK [0x65fe03000, 0x65fe03fff] PGTABLE [0.008955] BRK [0x65fe04000, 0x65fe04fff] PGTABLE [0.008956] BRK [0x65fe05000, 0x65fe05fff] PGTABLE [0.009050] BRK [0x65fe06000, 0x65fe06fff] PGTABLE [0.009081] BRK [0x65fe07000, 0x65fe07fff] PGTABLE [0.009121] BRK [0x65fe08000, 0x65fe08fff] PGTABLE [0.009162] BRK [0x65fe09000, 0x65fe09fff] PGTABLE [0.009250] RAMDISK: [mem 0x318e5000-0x34c69fff] [0.009257] ACPI: Early table checksum verification disabled [0.009259] ACPI: RSDP 0x8FD0E014 24 (v02 LENOVO) [0.009263] ACPI: XSDT 0x8FD0C188 000124 (v01 LENOVO TP-N2O 1025 PTEC 0002) [0.009267] ACPI: FACP 0x8D5AB000
Bug#879717: Wallpapers should have a better quality
I would like to confirm this. I run KDE and wallpaper, login screen, lock screen are very bad looking and it looks very unprofessional. All the Debian svg images have got ripples. /usr/share/desktop-base/futureprototype-theme/wallpaper/contents/images/ When you use XFCE and its wallpapers there is no such issue. Would be nice if someone fixes this, that Debian looks more professional. Thanks Jiri
Bug#931493: [plasma-desktop] remove rotating effect of notification icon in system tray when copying
Package: plasma-desktop Version: 4:5.13.5-1+b1 Severity: normal --- Please enter the report below this line. --- Can someone please completely remove the rotating effect of notification icon in system tray? Every time I copy something it takes 30% of the CPU and my fans start spinning as crazy. I don't even understand how feature like that can even pass testing. Thank you. --- System information. --- Architecture: Kernel: Linux 4.19.0-5-amd64 Debian Release: 10.0 500 xenial updates.signal.org 500 unstable debian.mirror.serversaustralia.com.au 500 stable repo.vivaldi.com 500 stable repo.skype.com 500 stable repo.nordvpn.com 500 stable linux.teamviewer.com 500 stable dl.google.com 500 jessie packagecloud.io --- Package information. --- Depends (Version) | Installed =-+-== breeze (>= 4:5.13) | 4:5.13.4-1 kactivitymanagerd (>= 5.13) | 5.13.5-1 kde-cli-tools (>= 4:5.13) | 4:5.13.5-1 kded5 | 5.54.0-1 kio | 5.51.0-1 oxygen-sounds (>= 4:5.13) | 4:5.13.4-1 plasma-desktop-data (= 4:5.13.5-1) | 4:5.13.5-1 plasma-framework | 5.51.0-1 plasma-integration (>= 5.13) | 5.13.5-1+b1 plasma-workspace (>= 4:5.13) | 4:5.13.5-1+b1 polkit-kde-agent-1 (>= 4:5.13) | 4:5.13.4-1 qml-module-org-kde-draganddrop | 5.51.0-2 qml-module-org-kde-kcoreaddons | 5.51.0-2 qml-module-org-kde-kquickcontrols | 5.51.0-2 qml-module-org-kde-kquickcontrolsaddons | 5.51.0-2 qml-module-org-kde-kwindowsystem | 5.51.0-2 qml-module-org-kde-solid | 5.54.0-1 qml-module-qt-labs-folderlistmodel | 5.11.3-4 qml-module-qt-labs-settings | 5.11.3-4 kpackagetool5 | 5.51.0-1 libappstreamqt2 | 0.12.7-1 libc6 (>= 2.15) | libcanberra0 (>= 0.2) | libfontconfig1 (>= 2.12.6) | libfreetype6 (>= 2.2.1) | libgcc1 (>= 1:3.0) | libkf5activities5 (>= 5.21.0) | libkf5activitiesstats1 (>= 5.35.0) | libkf5archive5 (>= 4.96.0) | libkf5auth5 (>= 4.96.0) | libkf5baloo5 (>= 5.15.0) | libkf5codecs5 (>= 4.96.0) | libkf5completion5 (>= 4.97.0) | libkf5configcore5 (>= 5.24.0) | libkf5configgui5 (>= 5.25.0) | libkf5configwidgets5 (>= 5.23.0) | libkf5coreaddons5 (>= 5.16.0) | libkf5dbusaddons5 (>= 4.99.0) | libkf5declarative5 (>= 4.96.0) | libkf5emoticons-bin | libkf5emoticons5 (>= 4.96.0) | libkf5globalaccel-bin | libkf5globalaccel5 (>= 5.10.0) | libkf5guiaddons5 (>= 4.96.0) | libkf5i18n5 (>= 5.0.0) | libkf5iconthemes5 (>= 5.0.0) | libkf5itemmodels5 (>= 5.14.0) | libkf5itemviews5 (>= 4.96.0) | libkf5jobwidgets5 (>= 4.96.0) | libkf5kcmutils5 (>= 4.96.0) | libkf5kdelibs4support5 (>= 4.99.0) | libkf5kiocore5 (>= 5.44.0) | libkf5kiofilewidgets5 (>= 5.41.0) | libkf5kiowidgets5 (>= 5.35.0) | libkf5newstuff5 (>= 5.27.0) | libkf5notifications5 (>= 5.3.0+git20141030.0311) | libkf5notifyconfig5 (>= 5.24.0) | libkf5package5 (>= 5.5.0+git) | libkf5parts5 (>= 4.96.0) | libkf5people5 | libkf5peoplewidgets5 | libkf5plasma5 (>= 5.41.0) | libkf5plasmaquick5 (>= 4.98.0) | libkf5quickaddons5 (>= 5.8.0+git20150324.0130+15.04) | libkf5runner5 (>= 5.24.0) | libkf5service-bin | libkf5service5 (>= 5.2.0+git20140930) | libkf5solid5 (>= 4.97.0) | libkf5sonnetui5 (>= 4.96.0) | libkf5wallet-bin | libkf5wallet5 (>= 4.96.0) | libkf5widgetsaddons5 (>= 4.96.0) | libkf5windowsystem5 (>= 5.25.0) | libkf5xmlgui5 (>= 4.98.0) | libkfontinst5 | libkfontinstui5 | libkworkspace5-5 (>= 4:5.8.1) | libphonon4qt5-4 (>= 4:4.8.0) | libpulse-mainloop-glib0 (>= 0.99.1) | libpulse0 (>= 0.99.1) | libqt5concurrent5 (>= 5.10.0~) | libqt5core5a (>= 5.11.0~rc1) | libqt5dbus5 (>= 5.10.0~) | libqt5gui5 (>= 5.10.0~) | libqt5network5 (>= 5.10.0~) | libqt5printsupport5 (>= 5.10.0~) | libqt5qml5 (>= 5.1.0) | libqt5quick5 (>= 5.7.0) | libqt5quickwidgets5 (>= 5.4.0) | libqt5sql5 (>= 5.10.0~) | libqt5svg5 (>= 5.6.0~beta) | libqt5widgets5 (>= 5.11.0~rc1) | libqt5x11extras5 (>= 5.6.0) | libqt5xml5 (>= 5.10.0~) | libscim8v5 (>= 1.4) | libstdc++6 (>= 5.2) | libtaskmanager6 (>= 4:5.12.0) | libx11-6 (>= 2:1.2.99.901) | libx11-xcb1 | libxcb-image0 (>= 0.2) | libxcb-record0 | libxcb-xkb1 | libxcb1 | libxcursor1 (>> 1.1.2) | libxfixes3 | libxft2 (>> 2.1.1) | libxi6 (>= 2:1.2.99.4) | libxkbfile1 | phonon4qt5 | Recommends (Version) | Installed -+-= bluedevil (>= 4:5.13) | 4:5.14.5-1 breeze-gtk-theme (>= 5.13) | 5.14.5-1 fonts-hack | 3.003-2 fonts-noto | 20181227-1 kde-config-gtk-style (>= 4:5.13) | 4:5.14.5-1 kde-config-screenlocker (>= 5.13) | 5.13.5-1 kde-config-sddm (>= 4:5.13) | 4:5.14.5-1 kde-style-oxygen-qt5 (>= 4:5.13) | 4:5.14.5-1 kgamma5 (>= 5.13) | 5.14.5-1 khelpcenter | 4:18.04.0-1 khotkeys (>= 4:5.13) | 4:5.14.5-1 kinfocenter (>= 4:5.13) | 4:5.13.4-1 kio-extras | 4:18.08.3-1 kmenuedit (>= 4:5.13) | 4:5.14.5-1 kscreen (>= 4:5.13) | 4:5.13.5-1 ksshaskpass (>= 4:5.13) | 4:5.14.5-1 ksysguard (>= 4:5.13) | 4:5.14.3-1 kwin-x11 (>= 4:5.13) | 4:5.13.5-1+b1 OR kwin | kwrited (>= 4:5.13) | 4:5.14.5-1 libpam-kwallet5 (>= 5.13) | 5.14.5-1 plasma-discover (>= 5.13) | 5.10.5-2 plasma-pa (>=
Bug#918025: [spectacle] spectacle is not able to take screenshots for various areas
Package: spectacle Severity: important --- Please enter the report below this line. --- Spectacle is not able to take screenshots for various areas and it completely freezes/crashes KDE. For example if I try to take Active window, it will completely strips boarders and top panel from all windows. Also it will stop me from changing windows. The main KDE panel becomes unresponsive. There are profound issues with Spectactle! --- System information. --- Architecture: Kernel: Linux 4.19.0-1-amd64 Debian Release: buster/sid 500 xenial updates.signal.org 500 unstable ftp.nc.debian.org 500 stable repo.vivaldi.com 500 stable repo.skype.com 500 stable linux.teamviewer.com 500 stable dl.google.com 500 jessie packagecloud.io --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Jiri
Bug#915683: [kazam] Unable to launch
Package: kazam
Version: 1.4.5-2
Severity: normal
--- Please enter the report below this line. ---
~ ❯ kazam
/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a
version first. Use gi.require_version('Gtk', '3.0') before import to
ensure that the right version gets loaded.
from gi.repository import Gtk
/usr/bin/kazam:75: DeprecationWarning: dist() and linux_distribution()
functions are deprecated in Python 3.5
dist = platform.linux_distribution()
Traceback (most recent call last):
File "/usr/bin/kazam", line 146, in
from kazam.app import KazamApp
File "/usr/lib/python3/dist-packages/kazam/app.py", line 35, in
from kazam.backend.prefs import *
File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line
478, in
prefs = Prefs()
File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line
119, in __init__
self.config = KazamConfig()
File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line
76, in __init__
ConfigParser.__init__(self, self.DEFAULTS[0]['keys'])
File "/usr/lib/python3.7/configparser.py", line 638, in __init__
self._read_defaults(defaults)
File "/usr/lib/python3.7/configparser.py", line 1216, in _read_defaults
self.read_dict({self.default_section: defaults})
File "/usr/lib/python3.7/configparser.py", line 753, in read_dict
self.set(section, key, value)
File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line
127, in set
self.add_section(section)
File "/usr/lib/python3.7/configparser.py", line 1205, in add_section
super().add_section(section)
File "/usr/lib/python3.7/configparser.py", line 655, in add_section
raise ValueError('Invalid section name: %r' % section)
ValueError: Invalid section name: 'DEFAULT'
--- System information. ---
Architecture:
Kernel: Linux 4.18.0-3-amd64
Debian Release: buster/sid
500 xenial updates.signal.org
500 unstable ftp.nc.debian.org
500 stable repo.vivaldi.com
500 stable repo.skype.com
500 stable linux.teamviewer.com
500 stable dl.google.com
500 jessie packagecloud.io
--- Package information. ---
Depends (Version) | Installed
=-+-==
gir1.2-gst-plugins-base-1.0 | 1.14.4-1
gir1.2-gstreamer-1.0 | 1.14.4-1
gir1.2-keybinder-3.0 | 0.3.2-1
gir1.2-wnck-3.0 | 3.30.0-1
gnome-session-canberra | 0.30-6
gstreamer1.0-plugins-base | 1.14.4-1
gstreamer1.0-plugins-good | 1.14.4-1
gstreamer1.0-plugins-ugly | 1.14.4-1
gstreamer1.0-pulseaudio | 1.14.4-1
python3-cairo | 1.16.2-1+b1
python3-dbus | 1.2.8-2+b2
python3-gi | 3.30.2-1
python3-gi-cairo | 3.30.2-1
python3-xdg | 0.25-4
python3 | 3.7.1-2
python3:any (>= 3.3.2-2~) |
Recommends (Version) | Installed
=-+-===
gstreamer1.0-libav | 1.15.0.1+git20180723+db823502-2
Package's Suggests field is empty.
--
Jiri
Bug#909569: [src:linux] crash after disconnecting or connecting thunderbolt
Package: src:linux Version: linux-image-4.18.0-1-amd64 Severity: normal My system crashes on Gigabyte Aero 14 when I connect or disconnect thunderbolt cable (external monitor). Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: AER: Corrected error received: :00:1c.4 Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: device [8086:a114] error status/mask=1000/2000 Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: [12] Replay Timer Timeout Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: AER: Corrected error received: :00:1c.4 Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: can't find device of ID00e4 Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: AER: Multiple Corrected error received: :00:1c.4 Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: device [8086:a114] error status/mask=1000/2000 Sep 25 21:47:21 superman kernel: pcieport :00:1c.4: [12] Replay Timer Timeout Sep 25 21:47:22 superman kernel: pcieport :00:1c.4: AER: Uncorrected (Non-Fatal) error received: :00:1c.4 Sep 25 21:47:22 superman kernel: pcieport :00:1c.4: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) Sep 25 21:47:22 superman kernel: pcieport :00:1c.4: device [8086:a114] error status/mask=0010/00014000 Sep 25 21:47:22 superman kernel: pcieport :00:1c.4: [20] Unsupported Request (First) Sep 25 21:47:22 superman kernel: pcieport :00:1c.4: TLP Header: 3400 0410 8000 Sep 25 21:47:22 superman kernel: pcieport :00:1c.4: broadcast error_detected message Sep 25 21:47:22 superman kernel: pcieport :00:1c.4: AER: Device recovery failed --- System information. --- Architecture: Kernel: Linux 4.18.0-1-amd64 Debian Release: buster/sid 500 xenial updates.signal.org 500 unstable ftp.nc.debian.org 500 stable wire-app.wire.com 500 stable repo.skype.com 500 stable linux.teamviewer.com 500 stable dl.google.com 500 preview linux.teamviewer.com 500 jessie packagecloud.io --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. -- Jiri
Bug#904834: Thunderbird doesn't opens links
Hi. I believe I found a workaround. 1. Delete handlers.json file from the Thunderbird profile. 2. Restart Thunderbird. 3. Click on http link -> you will get offer which app you want to open the link with. As I use Debian, I select other and use /etc/alternatives/x-www-browser 4. Click on https link -> you will get offer which app you want to open the link with. As I use Debian, I select other and use /etc/alternatives/x-www-browser 5. Should work again. Jiri On 12/9/18 8:02 pm, Jiri Kanicky wrote: > > Hi, > > I am experiencing the same problem. Its the same in safe mode. > > I experimented with options: > *network.protocol-handler.warn-external.http > **network.protocol-handler.warn-external.https* > > I was able to make links for http work, but I am not able to make > https links work. The prompt "Launch Application" does not come up. > > What I noticed is that the Attachments in Preferences were empty > despite there was something there before. After playing the the > options above, i added http -> x-www-browser and that is working. But > I am simply not able to add https. > > I am wondering if there is any way how to edit the attachments setting > manually? Or is there any way to reset the attachments setting? > > -- > > Jiri > >
Bug#907049: [Pkg-openssl-devel] Bug#907049: openssl: Update to 1.1.1~~pre9-1 makes certain programs unusable
Hi, I confirm this issue. The issue is relate to what TLS version the server supports. Resolution: 1. downgrade to openssl_1.1.0h-4 2. edit /etc/ssl/openssl.cnf and either comment out MinProtocol option, or try different versions from top down until openvpn connection starts to work. I have openvpn connections to NordVPN servers and TLSv1.2 works fine in most cases. However work VPN to Sophos supports only TLSv1.0, so I have to reduce the version it in the openssl.cnf file. -- Jiri
Bug#909246: [powerdevil] powerdevil closed unexpectedly when resuming from suspend
Package: powerdevil Version: 4:5.13.5-1 Severity: important Distro: Debian Sid Issue: powerdevil closes unexpectedly when resuming from suspend. I get KDE org_kde_powedevil dialog to notify me about the crash. The following is in the developer information. Application: org_kde_powerdevil (org_kde_powerdevil), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbfeb6ea840 (LWP 2337))] Thread 6 (Thread 0x7fbfdbfff700 (LWP 2464)): #0 0x7fbff35e0739 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbff12bfe46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbff12bff6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbff3af023b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbff3a9d24b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbff38ec176 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbff38f5d47 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbff261bf2a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7fbff35eaedf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7fbfe8a5d700 (LWP 2458)): #0 0x7fbff35e0739 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbff12bfe46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbff12bff6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbff3af023b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbff3a9d24b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbff38ec176 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbff38f5d47 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbff261bf2a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7fbff35eaedf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7fbfe94cf700 (LWP 2352)): #0 0x7fbff1306509 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbff12bf1e7 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbff12bfd7b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbff12c01d2 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbfea0767b6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7fbff12e8135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fbff261bf2a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7fbff35eaedf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7fbfe9cd0700 (LWP 2351)): #0 0x7fbff35dc204 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbff1305180 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbff12bf91f in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbff12bfdf0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbff12bff6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbff12bffb1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fbff12e8135 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fbff261bf2a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7fbff35eaedf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fbfeac0f700 (LWP 2348)): #0 0x7fbff35dc204 in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbff1305180 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbff12bf91f in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbff12bfdf0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbff12bff6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbff3af023b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbff3a9d24b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbff38ec176 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fbff3d43545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fbff38f5d47 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fbff261bf2a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7fbff35eaedf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7fbfeb6ea840 (LWP 2337)): [KCrash Handler] #6 0x7fbff4a596ff in PowerDevil::Core::onResumingFromIdle() () from /usr/lib/x86_64-linux-gnu/libpowerdevilcore.so.2 #7
Bug#908676: [kwin-wayland] Plasma wayland session restarted after pluging or unpluging secondary monitor over thunderbolt
Package: kwin-wayland Version: 4:5.13.5-1 Severity: serious When I plug or unplug external monitor over thunderbolt the session logs me out, sometimes the system crashes. Sep 12 21:32:59 superman kernel: [19572.692217] pci :04:00.0: [8086:15da] type 01 class 0x060400 Sep 12 21:32:59 superman kernel: [19572.692292] pci :04:00.0: enabling Extended Tags Sep 12 21:32:59 superman kernel: [19572.692423] pci :04:00.0: supports D1 D2 Sep 12 21:32:59 superman kernel: [19572.692424] pci :04:00.0: PME# supported from D0 D1 D2 D3hot D3cold Sep 12 21:32:59 superman kernel: [19572.692627] pcieport :00:1c.4: ASPM: current common clock configuration is broken, reconfiguring Sep 12 21:32:59 superman kernel: [19572.704461] pci :05:00.0: [8086:15da] type 01 class 0x060400 Sep 12 21:32:59 superman kernel: [19572.704568] pci :05:00.0: enabling Extended Tags Sep 12 21:32:59 superman kernel: [19572.704862] pci :05:00.0: supports D1 D2 Sep 12 21:32:59 superman kernel: [19572.704863] pci :05:00.0: PME# supported from D0 D1 D2 D3hot D3cold Sep 12 21:32:59 superman kernel: [19572.705173] pci :05:01.0: [8086:15da] type 01 class 0x060400 Sep 12 21:32:59 superman kernel: [19572.705269] pci :05:01.0: enabling Extended Tags Sep 12 21:32:59 superman kernel: [19572.705505] pci :05:01.0: supports D1 D2 Sep 12 21:32:59 superman kernel: [19572.705516] pci :05:01.0: PME# supported from D0 D1 D2 D3hot D3cold Sep 12 21:32:59 superman kernel: [19572.705775] pci :05:02.0: [8086:15da] type 01 class 0x060400 Sep 12 21:32:59 superman kernel: [19572.705871] pci :05:02.0: enabling Extended Tags Sep 12 21:32:59 superman kernel: [19572.706076] pci :05:02.0: supports D1 D2 Sep 12 21:32:59 superman kernel: [19572.706079] pci :05:02.0: PME# supported from D0 D1 D2 D3hot D3cold Sep 12 21:32:59 superman kernel: [19572.706413] pci :04:00.0: PCI bridge to [bus 05-3c] Sep 12 21:32:59 superman kernel: [19572.706436] pci :04:00.0: bridge window [mem 0xc400-0xda0f] Sep 12 21:32:59 superman kernel: [19572.706445] pci :04:00.0: bridge window [mem 0x8000-0xa1ff 64bit pref] Sep 12 21:32:59 superman kernel: [19572.706601] pci :05:00.0: PCI bridge to [bus 06] Sep 12 21:32:59 superman kernel: [19572.706612] pci :05:00.0: bridge window [mem 0xda00-0xda0f] Sep 12 21:32:59 superman kernel: [19572.706716] pci :05:01.0: PCI bridge to [bus 07-3b] Sep 12 21:32:59 superman kernel: [19572.706729] pci :05:01.0: bridge window [mem 0xc400-0xd9ef] Sep 12 21:32:59 superman kernel: [19572.706737] pci :05:01.0: bridge window [mem 0x8000-0xa1ff 64bit pref] Sep 12 21:32:59 superman kernel: [19572.706947] pci :3c:00.0: [8086:15db] type 00 class 0x0c0330 Sep 12 21:32:59 superman kernel: [19572.707014] pci :3c:00.0: reg 0x10: [mem 0xd9f0-0xd9f0] Sep 12 21:32:59 superman kernel: [19572.707111] pci :3c:00.0: enabling Extended Tags Sep 12 21:32:59 superman kernel: [19572.707354] pci :3c:00.0: supports D1 D2 Sep 12 21:32:59 superman kernel: [19572.707358] pci :3c:00.0: PME# supported from D0 D1 D2 D3hot D3cold Sep 12 21:32:59 superman kernel: [19572.707783] pci :05:02.0: PCI bridge to [bus 3c] Sep 12 21:32:59 superman kernel: [19572.707815] pci :05:02.0: bridge window [mem 0xd9f0-0xd9ff] Sep 12 21:32:59 superman kernel: [19572.707866] pci_bus :05: Allocating resources Sep 12 21:32:59 superman kernel: [19572.707928] pci :05:01.0: bridge window [io 0x1000-0x0fff] to [bus 07-3b] add_size 1000 Sep 12 21:32:59 superman kernel: [19572.707996] pci :05:02.0: bridge window [io 0x1000-0x0fff] to [bus 3c] add_size 1000 Sep 12 21:32:59 superman kernel: [19572.708001] pci :05:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 3c] add_size 20 add_align 10 Sep 12 21:32:59 superman kernel: [19572.708026] pci :04:00.0: bridge window [io 0x1000-0x0fff] to [bus 05-3c] add_size 2000 Sep 12 21:32:59 superman kernel: [19572.708037] pci :04:00.0: BAR 13: no space for [io size 0x2000] Sep 12 21:32:59 superman kernel: [19572.708039] pci :04:00.0: BAR 13: failed to assign [io size 0x2000] Sep 12 21:32:59 superman kernel: [19572.708044] pci :04:00.0: BAR 13: no space for [io size 0x2000] Sep 12 21:32:59 superman kernel: [19572.708046] pci :04:00.0: BAR 13: failed to assign [io size 0x2000] Sep 12 21:32:59 superman kernel: [19572.708052] pci :05:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Sep 12 21:32:59 superman kernel: [19572.708055] pci :05:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Sep 12 21:32:59 superman kernel: [19572.708057] pci :05:01.0: BAR 13: no space for [io size 0x1000] Sep 12 21:32:59 superman kernel: [19572.708060] pci :05:01.0: BAR 13: failed to assign [io size 0x1000] Sep 12 21:32:59 superman kernel: [19572.708062] pci :05:02.0: BAR 13: no space for [io size 0x1000] Sep 12 21:32:59
Bug#904834: Thunderbird doesn't opens links
Hi, I am experiencing the same problem. Its the same in safe mode. I experimented with options: *network.protocol-handler.warn-external.http **network.protocol-handler.warn-external.https* I was able to make links for http work, but I am not able to make https links work. The prompt "Launch Application" does not come up. What I noticed is that the Attachments in Preferences were empty despite there was something there before. After playing the the options above, i added http -> x-www-browser and that is working. But I am simply not able to add https. I am wondering if there is any way how to edit the attachments setting manually? Or is there any way to reset the attachments setting? -- Jiri
Bug#908447: working after upgrade and reboot
Hi. So it seems that its working after upgrade and reboot. The FN + dedicated Laptop key also works to switch displays. -- Jiri
Bug#908447: plasma: Switch Display shortcut keys do not work in KDE Wayland
Package: plasma-desktop Version: 4:5.13.5-1 Severity: normal File: plasma Dear Maintainer, Switch Display shortcut keys (Meta + P) does not seem to work in KDE Wayland while it works under X. Repro steps: Log into KDE Wayland Attach second monitor Press Meta + P Nothing happens -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-desktop depends on: ii breeze 4:5.13.4-1 ii kactivitymanagerd5.13.5-1 ii kde-cli-tools4:5.13.5-1 ii kded55.49.0-1 ii kio 5.49.0-1 ii kpackagetool55.49.0-1 ii libappstreamqt2 0.12.2-2 ii libc62.27-6 ii libcanberra0 0.30-6 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.2.0-5 ii libkf5activities55.49.0-1 ii libkf5activitiesstats1 5.49.0-1 ii libkf5archive5 5.49.0-1 ii libkf5auth5 5.49.0-1 ii libkf5baloo5 5.49.0-1 ii libkf5codecs55.49.0-1 ii libkf5completion55.49.0-1 ii libkf5configcore55.49.0-1 ii libkf5configgui5 5.49.0-1 ii libkf5configwidgets5 5.49.0-1 ii libkf5coreaddons55.49.0-1 ii libkf5dbusaddons55.49.0-1 ii libkf5declarative5 5.49.0-1 ii libkf5emoticons-bin 5.49.0-1 ii libkf5emoticons5 5.49.0-1 ii libkf5globalaccel-bin5.49.0-1 ii libkf5globalaccel5 5.49.0-1 ii libkf5guiaddons5 5.49.0-1 ii libkf5i18n5 5.49.0-1 ii libkf5iconthemes55.49.0-1 ii libkf5itemmodels55.49.0-1 ii libkf5itemviews5 5.49.0-1 ii libkf5jobwidgets55.49.0-1 ii libkf5kcmutils5 5.49.0-1 ii libkf5kdelibs4support5 5.49.0-1 ii libkf5kiocore5 5.49.0-1 ii libkf5kiofilewidgets55.49.0-1 ii libkf5kiowidgets55.49.0-1 ii libkf5newstuff5 5.49.0-1 ii libkf5notifications5 5.49.0-1 ii libkf5notifyconfig5 5.49.0-1 ii libkf5package5 5.49.0-1 ii libkf5parts5 5.49.0-1 ii libkf5people55.49.0-1 ii libkf5peoplewidgets5 5.49.0-1 ii libkf5plasma55.49.0-1 ii libkf5plasmaquick5 5.49.0-1 ii libkf5quickaddons5 5.49.0-1 ii libkf5runner55.49.0-1 ii libkf5service-bin5.49.0-1 ii libkf5service5 5.49.0-1 ii libkf5solid5 5.49.0-1 ii libkf5sonnetui5 5.49.0-1 ii libkf5wallet-bin 5.49.0-1 ii libkf5wallet55.49.0-1 ii libkf5widgetsaddons5 5.49.0-1 ii libkf5windowsystem5 5.49.0-1 ii libkf5xmlgui55.49.0-1 ii libkfontinst54:5.13.5-1 ii libkfontinstui5 4:5.13.5-1 ii libkworkspace5-5 4:5.13.5-1 ii libphonon4qt5-4 4:4.10.1-1 ii libpulse-mainloop-glib0 11.1-5 ii libpulse011.1-5 ii libqt5concurrent55.11.1+dfsg-7 ii libqt5core5a 5.11.1+dfsg-7 ii libqt5dbus5 5.11.1+dfsg-7 ii libqt5gui5 5.11.1+dfsg-7 ii libqt5network5 5.11.1+dfsg-7 ii libqt5printsupport5 5.11.1+dfsg-7 ii libqt5qml5 5.11.1-5 ii libqt5quick5 5.11.1-5 ii libqt5quickwidgets5 5.11.1-5 ii libqt5sql5 5.11.1+dfsg-7 ii libqt5svg5 5.11.1-2 ii libqt5widgets5
Bug#907439: plasma-desktop: plasma panel freezes when handling usb memory stick
Package: plasma-desktop Version: 4:5.13.4-1 Severity: important Dear Maintainer, It seems that plasma panel freezes when any kind of storage becomes unavailble. Please can you remove all storage components from the panel and make it rock stable. This is the most annoying bug from the whole KDE. I expect things to break, but panel should keep working. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-desktop depends on: ii breeze 4:5.13.4-1 ii kactivitymanagerd5.13.4-1 ii kde-cli-tools4:5.13.4-1 ii kded55.49.0-1 ii kio 5.49.0-1 ii kpackagetool55.49.0-1 ii libappstreamqt2 0.12.2-2 ii libc62.27-5 ii libcanberra0 0.30-6 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.2.0-4 ii libkf5activities55.49.0-1 ii libkf5activitiesstats1 5.49.0-1 ii libkf5archive5 5.49.0-1 ii libkf5auth5 5.49.0-1 ii libkf5baloo5 5.49.0-1 ii libkf5codecs55.49.0-1 ii libkf5completion55.49.0-1 ii libkf5configcore55.49.0-1 ii libkf5configgui5 5.49.0-1 ii libkf5configwidgets5 5.49.0-1 ii libkf5coreaddons55.49.0-1 ii libkf5dbusaddons55.49.0-1 ii libkf5declarative5 5.49.0-1 ii libkf5emoticons-bin 5.49.0-1 ii libkf5emoticons5 5.49.0-1 ii libkf5globalaccel-bin5.49.0-1 ii libkf5globalaccel5 5.49.0-1 ii libkf5guiaddons5 5.49.0-1 ii libkf5i18n5 5.49.0-1 ii libkf5iconthemes55.49.0-1 ii libkf5itemmodels55.49.0-1 ii libkf5itemviews5 5.49.0-1 ii libkf5jobwidgets55.49.0-1 ii libkf5kcmutils5 5.49.0-1 ii libkf5kdelibs4support5 5.49.0-1 ii libkf5kiocore5 5.49.0-1 ii libkf5kiofilewidgets55.49.0-1 ii libkf5kiowidgets55.49.0-1 ii libkf5newstuff5 5.49.0-1 ii libkf5notifications5 5.49.0-1 ii libkf5notifyconfig5 5.49.0-1 ii libkf5package5 5.49.0-1 ii libkf5parts5 5.49.0-1 ii libkf5people55.49.0-1 ii libkf5peoplewidgets5 5.49.0-1 ii libkf5plasma55.49.0-1 ii libkf5plasmaquick5 5.49.0-1 ii libkf5quickaddons5 5.49.0-1 ii libkf5runner55.49.0-1 ii libkf5service-bin5.49.0-1 ii libkf5service5 5.49.0-1 ii libkf5solid5 5.49.0-1 ii libkf5sonnetui5 5.49.0-1 ii libkf5wallet-bin 5.49.0-1 ii libkf5wallet55.49.0-1 ii libkf5widgetsaddons5 5.49.0-1 ii libkf5windowsystem5 5.49.0-1 ii libkf5xmlgui55.49.0-1 ii libkfontinst54:5.13.4-1 ii libkfontinstui5 4:5.13.4-1 ii libkworkspace5-5 4:5.13.4-1 ii libphonon4qt5-4 4:4.10.1-1 ii libpulse-mainloop-glib0 11.1-5 ii libpulse011.1-5 ii libqt5concurrent55.11.1+dfsg-6 ii libqt5core5a 5.11.1+dfsg-6 ii libqt5dbus5 5.11.1+dfsg-6 ii libqt5gui5 5.11.1+dfsg-6 ii libqt5network5 5.11.1+dfsg-6 ii libqt5printsupport5 5.11.1+dfsg-6 ii libqt5qml5 5.11.1-4 ii libqt5quick5 5.11.1-4 ii libqt5quickwidgets5 5.11.1-4 ii libqt5sql5 5.11.1+dfsg-6 ii libqt5svg5
Bug#902645: /usr/bin/plasmashell: plasmashell keeps requesting to mount nfs for no reason
Package: plasma-workspace Version: 4:5.12.5-1 Severity: normal File: /usr/bin/plasmashell Dear Maintainer, ISSUE: plasmashell keeps requesting to mount nfs for no reason. syslog: Jun 29 12:31:48 superman systemd[1]: Unmounting /mnt/megatron-media... Jun 29 12:31:48 superman systemd[1]: Unmounted /mnt/megatron-media. Jun 29 12:31:48 superman systemd[1]: mnt-megatron\x2dmedia.automount: Got automount request for /mnt/megatron-media, triggered by 1248 (plasmashell) Jun 29 12:31:48 superman systemd[1]: Mounting /mnt/megatron-media... Jun 29 12:31:49 superman systemd[1]: Mounted /mnt/megatron-media. I have NFS mounts in /etc/fstab which permit user to mount and also automacially unmount the FS if idle. # megatron.internal.corp:/mnt/storage/media /mnt/megatron-medianfs4 noauto,user,noatime,nodiratime,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0 EXPECTATION: I believe there is no reason for these requests to mount it. Plasmashell should not request to mount the filesystem until i click on the mount in Dolphin. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-workspace depends on: ii dbus-x11 1.12.8-3 ii drkonqi 5.12.5-1 ii frameworkintegration 5.47.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.47.0-1 ii kinit5.47.0-1 ii kio 5.47.0-1 ii kpackagetool55.47.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.47.0-1 ii libkf5auth5 5.47.0-1 ii libkf5baloo5 5.47.0-1 ii libkf5bookmarks5 5.47.0-1 ii libkf5calendarevents55.47.0-1 ii libkf5completion55.47.0-1 ii libkf5config-bin 5.47.0-1 ii libkf5configcore55.47.0-1 ii libkf5configgui5 5.47.0-1 ii libkf5configwidgets5 5.47.0-1 ii libkf5coreaddons55.47.0-1 ii libkf5crash5 5.47.0-1 ii libkf5dbusaddons55.47.0-1 ii libkf5declarative5 5.47.0-1 ii libkf5globalaccel-bin5.47.0-1 ii libkf5globalaccel5 5.47.0-1 ii libkf5guiaddons5 5.47.0-1 ii libkf5holidays5 16.04.2-1 ii libkf5i18n5 5.47.0-1 ii libkf5iconthemes55.47.0-1 ii libkf5idletime5 5.47.0-1 ii libkf5itemviews5 5.47.0-1 ii libkf5jobwidgets55.47.0-1 ii libkf5js55.47.0-1 ii libkf5jsembed5 5.47.0-1 ii libkf5kdelibs4support5 5.47.0-1 ii libkf5kiocore5 5.47.0-1 ii libkf5kiofilewidgets55.47.0-1 ii libkf5kiogui55.47.0-1 ii libkf5kiowidgets55.47.0-1 ii libkf5networkmanagerqt6 5.47.0-1 ii libkf5newstuff5 5.47.0-1 ii libkf5notifications5 5.47.0-1 ii libkf5notifyconfig5 5.47.0-1 ii libkf5package5 5.47.0-1 ii libkf5plasma55.47.0-1 ii libkf5plasmaquick5 5.47.0-1 ii libkf5prison55.47.0-1 ii libkf5quickaddons5 5.47.0-1 ii libkf5runner55.47.0-1 ii libkf5service-bin5.47.0-1 ii libkf5service5 5.47.0-1 ii libkf5solid5 5.47.0-1 ii libkf5texteditor55.47.0-1 ii libkf5textwidgets5
Bug#647978: nslcd slows down everything when I unplug my notebook from network
On 10/11/11 10:59, Jiri Kanicky wrote: On 10/11/11 06:46, Arthur de Jong wrote: On Wed, 2011-11-09 at 10:47 +1100, Jiri Kanicky wrote: I also noticed that if I am off-line, I am not able to fully login to my window manager (xfce4, kde4). The login part seems to finish successfully and I receive a message that I am using cached credentials, however the screen stays black after that. nslcd logs problems to find the LDAP again. If I stop the nslcd service, before the login, the windows manager comes up no problem. This is probably related to the earlier problem but output from nslcd -d during such a login would help. Could you also include /etc/nsswitch.conf and information about your PAM stack? Thanks, Hi. I also have got problem to unlock my screen. The following messages are logged. It takes long time to unlock in (KDE) and I have to press the unlock button several times. Nov 10 10:52:41 knightrider nslcd[2103]: [4a481a] authc=ganomil failed to bind to LDAP server ldap://maverick.allsupp.corp: Can't contact LDAP server: Connection timed out Nov 10 10:52:41 knightrider nslcd[2103]: [4a481a] authc=ganomil no available LDAP server found: Can't contact LDAP server Nov 10 10:52:41 knightrider nslcd[2103]: [4a481a] authc=ganomil ganomil: user not found: Can't contact LDAP server Nov 10 10:52:41 knightrider ccreds_chkpwd: Libgcrypt warning: missing initialization - please fix the application Nov 10 10:52:46 knightrider nslcd[2103]: [9478fe] authc=ganomil no available LDAP server found: Server is unavailable Nov 10 10:52:46 knightrider nslcd[2103]: [9478fe] authc=ganomil ganomil: user not found: Server is unavailable Nov 10 10:52:46 knightrider ccreds_chkpwd: Libgcrypt warning: missing initialization - please fix the application # cat /etc/nsswitch.conf passwd: files ldap group: files ldap shadow: files ldap hosts: files dns ldap networks: files protocols: db files services: db files ethers: db files rpc:db files # cat /etc/nscd.conf # # /etc/nscd.conf # # An example Name Service Cache config file. This file is needed by nscd. # # Legal entries are: # # logfile file # debug-level level # threads initial #threads to use # max-threads maximum #threads to use # server-user user to run server as instead of root # server-user is ignored if nscd is started with -S parameters # stat-user user who is allowed to request statistics # reload-countunlimited|number # paranoia yes|no # restart-interval time in seconds # # enable-cache service yes|no # positive-time-to-live service time in seconds # negative-time-to-live service time in seconds # suggested-size service prime number # check-files service yes|no # persistent service yes|no # shared service yes|no # max-db-size service number bytes # auto-propagate service yes|no # # Currently supported cache names (services): passwd, group, hosts, services # # logfile /var/log/nscd.log # threads 4 # max-threads 32 # server-user nobody # stat-user somebody debug-level 0 reload-countunlimited paranoiano # restart-interval3600 enable-cachepasswd yes positive-time-to-live passwd 2592000 negative-time-to-live passwd 20 suggested-size passwd 211 check-files passwd yes persistent passwd yes shared passwd yes max-db-size passwd 33554432 auto-propagate passwd yes enable-cachegroup yes positive-time-to-live group 2592000 negative-time-to-live group 60 suggested-size group 211 check-files group yes persistent group yes shared group yes max-db-size group 33554432 auto-propagate group yes # hosts caching is broken with gethostby* calls, hence is now disabled # per default. See /usr/share/doc/nscd/NEWS.Debian. enable-cachehosts no positive-time-to-live hosts 2592000 negative-time-to-live hosts 20 suggested-size hosts 211 check-files hosts yes persistent hosts yes shared hosts yes max-db-size hosts 33554432 enable-cacheservices
Bug#647978: nslcd slows down everything when I unplug my notebook from network
On 10/11/11 06:46, Arthur de Jong wrote: On Wed, 2011-11-09 at 10:47 +1100, Jiri Kanicky wrote: I also noticed that if I am off-line, I am not able to fully login to my window manager (xfce4, kde4). The login part seems to finish successfully and I receive a message that I am using cached credentials, however the screen stays black after that. nslcd logs problems to find the LDAP again. If I stop the nslcd service, before the login, the windows manager comes up no problem. This is probably related to the earlier problem but output from nslcd -d during such a login would help. Could you also include /etc/nsswitch.conf and information about your PAM stack? Thanks, Hi. I also have got problem to unlock my screen. The following messages are logged. It takes long time to unlock in (KDE) and I have to press the unlock button several times. Nov 10 10:52:41 knightrider nslcd[2103]: [4a481a] authc=ganomil failed to bind to LDAP server ldap://maverick.allsupp.corp: Can't contact LDAP server: Connection timed out Nov 10 10:52:41 knightrider nslcd[2103]: [4a481a] authc=ganomil no available LDAP server found: Can't contact LDAP server Nov 10 10:52:41 knightrider nslcd[2103]: [4a481a] authc=ganomil ganomil: user not found: Can't contact LDAP server Nov 10 10:52:41 knightrider ccreds_chkpwd: Libgcrypt warning: missing initialization - please fix the application Nov 10 10:52:46 knightrider nslcd[2103]: [9478fe] authc=ganomil no available LDAP server found: Server is unavailable Nov 10 10:52:46 knightrider nslcd[2103]: [9478fe] authc=ganomil ganomil: user not found: Server is unavailable Nov 10 10:52:46 knightrider ccreds_chkpwd: Libgcrypt warning: missing initialization - please fix the application # cat /etc/nsswitch.conf passwd: files ldap group: files ldap shadow: files ldap hosts: files dns ldap networks: files protocols: db files services: db files ethers: db files rpc:db files # cat /etc/nscd.conf # # /etc/nscd.conf # # An example Name Service Cache config file. This file is needed by nscd. # # Legal entries are: # # logfile file # debug-level level # threads initial #threads to use # max-threads maximum #threads to use # server-user user to run server as instead of root # server-user is ignored if nscd is started with -S parameters # stat-user user who is allowed to request statistics # reload-countunlimited|number # paranoia yes|no # restart-interval time in seconds # # enable-cache service yes|no # positive-time-to-live service time in seconds # negative-time-to-live service time in seconds # suggested-size service prime number # check-files service yes|no # persistent service yes|no # shared service yes|no # max-db-size service number bytes # auto-propagate service yes|no # # Currently supported cache names (services): passwd, group, hosts, services # # logfile /var/log/nscd.log # threads 4 # max-threads 32 # server-user nobody # stat-user somebody debug-level 0 reload-countunlimited paranoiano # restart-interval3600 enable-cachepasswd yes positive-time-to-live passwd 2592000 negative-time-to-live passwd 20 suggested-size passwd 211 check-files passwd yes persistent passwd yes shared passwd yes max-db-size passwd 33554432 auto-propagate passwd yes enable-cachegroup yes positive-time-to-live group 2592000 negative-time-to-live group 60 suggested-size group 211 check-files group yes persistent group yes shared group yes max-db-size group 33554432 auto-propagate group yes # hosts caching is broken with gethostby* calls, hence is now disabled # per default. See /usr/share/doc/nscd/NEWS.Debian. enable-cachehosts no positive-time-to-live hosts 2592000 negative-time-to-live hosts 20 suggested-size hosts 211 check-files hosts yes persistent hosts yes shared hosts yes max-db-size hosts 33554432 enable-cacheservicesyes positive-time-to-live services
Bug#647978: nslcd slows down everything when I unplug my notebook from network
On 09/11/11 09:08, Arthur de Jong wrote: On Tue, 2011-11-08 at 13:06 +1100, Jiri Kanicky wrote: When I unplug notebook from my network, nslcd is not able to contact LDAP server and some task like clicking on logout takes long time and the following errors are reported. I believe that the nslcd is waiting for responce, and than the task can proceed, but it should not work like that. In Windows, I also do not wait for tasks when I work offline. If you want to support off-line operation you either have to have a local replica of the LDAP server of perform some caching with nscd (or something else). Currently nss-pam-ldapd does not implement caching. If the connection to your LDAP server is normally reliable, you could tune the timing settings to something like this: bind_timelimit 3 timelimit 3 reconnect_sleeptime 1 reconnect_retrytime 3 This ensures that unavailability of the LDAP server is recorded quickly. Nov 8 12:46:24 knightrider nslcd[2146]: [e3dfe6]passwd=10001 no available LDAP server found: Server is unavailable It is a bit strange that this query is retried so often because I would expect nscd to have cached the result. Thanks, Hi. I use nscd for caching. I also noticed that if I am off-line, I am not able to fully login to my window manager (xfce4, kde4). The login part seems to finish successfully and I receive a message that I am using cached credentials, however the screen stays black after that. nslcd logs problems to find the LDAP again. If I stop the nslcd service, before the login, the windows manager comes up no problem. Something does not seems to work correctly with nslcd... Thank you for looking into this. Jiri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647978: nslcd slows down everything when I unplug my notebook from network
Package: nslcd Version: 0.8.4 Severity: important Dear Maintainer, When I unplug notebook from my network, nslcd is not able to contact LDAP server and some task like clicking on logout takes long time and the following errors are reported. I believe that the nslcd is waiting for responce, and than the task can proceed, but it should not work like that. In Windows, I also do not wait for tasks when I work offline. ov 8 12:46:24 knightrider nslcd[2146]: [bb2b99] passwd=10001 no available LDAP server found: Can't contact LDAP server Nov 8 12:46:24 knightrider nslcd[2146]: [e3dfe6] passwd=10001 no available LDAP server found: Server is unavailable Nov 8 12:46:24 knightrider nslcd[2146]: [5b37f3] passwd=10001 no available LDAP server found: Server is unavailable Nov 8 12:46:24 knightrider nslcd[2146]: [db7e02] passwd=10001 no available LDAP server found: Server is unavailable Nov 8 12:46:24 knightrider nslcd[2146]: [7ec0c4] passwd=10001 no available LDAP server found: Server is unavailable Nov 8 12:46:24 knightrider nslcd[2146]: [73bb22] passwd=10001 no available LDAP server found: Server is unavailable Nov 8 12:46:24 knightrider nslcd[2146]: [9e1dd3] passwd=10001 no available LDAP server found: Server is unavailable Nov 8 12:46:24 knightrider nslcd[2146]: [d141cc] passwd=10001 no available LDAP server found: Server is unavailable Nov 8 12:46:46 knightrider nslcd[2146]: [f9357a] passwd=-1 failed to bind to LDAP server ldap://maverick.allsupp.corp: Can't contact LDAP server: Connection timed out -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nslcd depends on: ii adduser3.113 ii debconf [debconf-2.0] 1.5.41 ii libc6 2.13-21 ii libgssapi-krb5-2 1.9.1+dfsg-3 ii libldap-2.4-2 2.4.25-4 Versions of packages nslcd recommends: ii bind9-host [host] 1:9.7.3.dfsg-1+b1 ii host1:9.8.1.dfsg-1 ii ldap-utils 2.4.25-4 ii libnss-ldapd [libnss-ldap] 0.8.4 ii libpam-krb5 4.4-3 ii libpam-ldapd [libpam-ldap] 0.8.4 ii nscd2.13-21 Versions of packages nslcd suggests: pn kstart none -- debconf information: nslcd/ldap-sasl-realm: nslcd/ldap-starttls: false nslcd/ldap-sasl-krb5-ccname: /var/run/nslcd/nslcd.tkt nslcd/ldap-auth-type: none nslcd/ldap-reqcert: * nslcd/ldap-uris: ldap://maverick.allsupp.corp nslcd/ldap-sasl-secprops: nslcd/ldap-binddn: nslcd/ldap-sasl-authcid: nslcd/ldap-sasl-mech: * nslcd/ldap-base: dc=allsupp,dc=corp nslcd/ldap-sasl-authzid: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647980: sssd: Please update this old version
Source: sssd Version: 1.2.1-4.3 Severity: normal Dear Maintainer, Can you please update this old version of sssd 1.2.1-4.3. Ubuntu has got updated version already in their repositories. Thank you. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
Hi. I upgrade kernel on LDAP/KERBEROS/NFS server to: # uname -r 3.0.0-1-amd64 And everything seems to be working now. Thanks to everybody for help. Jiri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640185: libnss-ldapd improperly configures nssswitch.conf
On 04/09/11 01:59, Arthur de Jong wrote: The problem is that your nsswitch.conf file seems to contain lines starting with white space characters. This is invalid in the original Sun format of this file. It seems that glibc is more forgiving though. I've updated the configuration scripts to also handle spaces around the database names. This will be fixed in the next upload. Hi. I would like to confirm that the original nsswitch.conf came with the space characters. I did not altered the file manually. Thank you for fixing this :-) Jiri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#640007: Acknowledgement (unable to start jxplorer - RenderingEngine: Provider sun.java2d.jules.JulesRenderingEngine not found)
Hi. Submitting the bug gave me a hint. When I saw the following: versions of packages jxplorer depends on: ii java-wrappers 0.1.22 wrappers for java executables ii javahelp2 2.0.05.ds1-5 Java based help system ii junit 3.8.2-8Automated testing framework for Ja ii openjdk-6-jre 6b18-1.8.9-0.1 OpenJDK Java runtime, using Hotspo ii sun-java6-jre 6.26-3 Sun Java(TM) Runtime Environment ( I uninstalled these packages and everything started to work: # apt-get remove openjdk-6-jdk openjdk-6-jre openjdk-6-jre-headless openjdk-6-jre-lib Regards, Jiri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
On 25/08/11 23:14, Jiri Kanicky wrote:
On 25/08/11 22:11, Jiri Kanicky wrote:
On 25/08/11 02:23, Bastian Blank wrote:
On Sun, Aug 14, 2011 at 12:43:14AM +1000, ganomi wrote:
Please get a name.
maverick:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
4 nfs/maverick.firm.local@FIRM.LOCAL (des3-cbc-sha1)
4 nfs/maverick.firm.local@FIRM.LOCAL (des-cbc-crc)
Please setup standard encryption types.
root@knightrider:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
6 nfs/knightrider.firm.local@FIRM.LOCAL (des-cbc-crc)
DES is disabled in the meantime. Use other encryption types.
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - Encryption type not permitted
I hope this message is clear.
Bastian
Dear Bastian.
I am not sure what do you mean by setup standard encryption types.
I believe that those are the standard encryption types. I haven't use
any special configuration. I tried to use the most basic setting for
Kerberos and LDAP.
[kdcdefaults]
kdc_ports = 750,88
[realms]
FIRM.LOCAL = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal
des:normal des:v4 des:norealm des:onlyrealm des:afs3
default_principal_flags = +preauth
}
Regards,
Jiri
Hi.
I found out that NFS (in RHEL 6) does not currently support
des-hmac-sha1, des-cbc-md5 neither des-cbc-crc. However, it should
support aes256-cts-hmac-sha1-96, aes128-cts-hmac-sha1-96,
des3-cbc-sha1 a arcfour-hmac. So, I am assuming that Debian Wheezy
have the same issue.
I will try to generate keys for those which are supported and re-test
it. I will come back with the results.
Thanks for giving me the idea.
Jiri
Hi.
So, I changed the encryption type to (aes256-cts-hmac-sha1-96). I
generated new keytab on the client (knightrider).
root@knightrider:/home/ganomi# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
7 nfs/knightrider.firm.local@FIRM.LOCAL (aes256-cts-hmac-sha1-96)
I still have the same problem.
maverick:/home/ganomi/# rpc.svcgssd -fvvv
entering poll
leaving poll
handling null request
WARNING: gss_accept_sec_context failed
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - No supported encryption types (config file error?)
sending null reply
writing message: \x \x608202c706092a86......1314468539 851968
2529639149 \x \x
finished handling null request
Any idea? Could it be the same issue as in
https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=719776
Jiri
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
On 28/08/11 04:28, Bastian Blank wrote:
On Sun, Aug 28, 2011 at 04:19:48AM +1000, Jiri Kanicky wrote:
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - No supported encryption types (config file error?)
The error is different from the first one. Did you configure both the
server and client with this encryption type?
Bastian
Hi Bastian.
Let me summarize all the setting and logs for each server and client:
KRB5/LDAP/NFS4 SERVER (maverick)
maverick:/home/ganomi/# cat /etc/krb5kdc/kdc.conf
[kdcdefaults]
kdc_ports = 750,88
[realms]
FIRM.LOCAL = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal
des:normal des:v4 des:norealm des:onlyrealm des:afs3 aes256-cts:normal
aes128-cts:normal des3-cbc-sha16:normal
default_principal_flags = +preauth
}
maverick:/home/ganomi/# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
5 nfs/maverick.firm.local@FIRM.LOCAL (des3-cbc-sha1)
5 nfs/maverick.firm.local@FIRM.LOCAL (des-cbc-crc)
6 nfs/maverick.firm.local@FIRM.LOCAL (aes256-cts-hmac-sha1-96)
maverick:/home/ganomi/# rpc.svcgssd -fvvv
entering poll
leaving poll
handling null request
WARNING: gss_accept_sec_context failed
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - No supported encryption types (config file error?)
sending null reply
writing message: \x \x608202c706092a86......1314468539 851968
2529639149 \x \x
finished handling null request
CLIENT (knightrider)
==
root@knightrider:/home/ganomi# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
7 nfs/knightrider.firm.local@FIRM.LOCAL
mailto:nfs/knightrider.firm.local@FIRM.LOCAL (aes256-cts-hmac-sha1-96)
root@knightrider:/home/ganomi# rpc.gssd -fvvv
ir_notify_handler: sig 37 si 0x7fff26026b30 data 0x7fff26026a00
dir_notify_handler: sig 37 si 0x7fff26022470 data 0x7fff26022340
dir_notify_handler: sig 37 si 0x7fff26022470 data 0x7fff26022340
handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt17)
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 '
handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt17)
process_krb5_upcall: service is 'null'
Full hostname for 'maverick.firm.local' is 'maverick.firm.local'
Full hostname for 'knightrider.firm.local' is 'knightrider.firm.local'
No key table entry found for KNIGHTRIDER$@FIRM.LOCAL while getting
keytab entry for 'KNIGHTRIDER$@FIRM.LOCAL'
No key table entry found for root/knightrider.firm.local@FIRM.LOCAL
while getting keytab entry for 'root/knightrider.firm.local@FIRM.LOCAL'
Success getting keytab entry for 'nfs/knightrider.firm.local@FIRM.LOCAL'
Successfully obtained machine credentials for principal
'nfs/knightrider.firm.local@FIRM.LOCAL' stored in ccache
'FILE:/tmp/krb5cc_machine_FIRM.LOCAL'
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_FIRM.LOCAL' are good
until 1314506238
using FILE:/tmp/krb5cc_machine_FIRM.LOCAL as credentials cache for
machine creds
using environment variable to select krb5 ccache
FILE:/tmp/krb5cc_machine_FIRM.LOCAL
creating context using fsuid 0 (save_uid 0)
creating tcp client for server maverick.firm.local
DEBUG: port already set to 2049
creating context with server n...@maverick.firm.local
WARNING: Failed to create krb5 context for user with uid 0 for server
maverick.firm.local
WARNING: Failed to create machine krb5 context with credentials cache
FILE:/tmp/krb5cc_machine_FIRM.LOCAL for server maverick.firm.local
WARNING: Machine cache is prematurely expired or corrupted trying to
recreate cache for server maverick.firm.local
Full hostname for 'maverick.firm.local' is 'maverick.firm.local'
Full hostname for 'knightrider.firm.local' is 'knightrider.firm.local'
No key table entry found for KNIGHTRIDER$@FIRM.LOCAL while getting
keytab entry for 'KNIGHTRIDER$@FIRM.LOCAL'
No key table entry found for root/knightrider.firm.local@FIRM.LOCAL
while getting keytab entry for 'root/knightrider.firm.local@FIRM.LOCAL'
Success getting keytab entry for 'nfs/knightrider.firm.local@FIRM.LOCAL'
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_FIRM.LOCAL' are good
until 1314506238
INFO: Credentials in CC 'FILE:/tmp/krb5cc_machine_FIRM.LOCAL' are good
until 1314506238
using FILE:/tmp/krb5cc_machine_FIRM.LOCAL as credentials
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
On 25/08/11 02:23, Bastian Blank wrote:
On Sun, Aug 14, 2011 at 12:43:14AM +1000, ganomi wrote:
Please get a name.
maverick:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
4 nfs/maverick.firm.local@FIRM.LOCAL (des3-cbc-sha1)
4 nfs/maverick.firm.local@FIRM.LOCAL (des-cbc-crc)
Please setup standard encryption types.
root@knightrider:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
6 nfs/knightrider.firm.local@FIRM.LOCAL (des-cbc-crc)
DES is disabled in the meantime. Use other encryption types.
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - Encryption type not permitted
I hope this message is clear.
Bastian
Dear Bastian.
I am not sure what do you mean by setup standard encryption types. I
believe that those are the standard encryption types. I haven't use any
special configuration. I tried to use the most basic setting for
Kerberos and LDAP.
[kdcdefaults]
kdc_ports = 750,88
[realms]
FIRM.LOCAL = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal
des:normal des:v4 des:norealm des:onlyrealm des:afs3
default_principal_flags = +preauth
}
Regards,
Jiri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637660: nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted
On 25/08/11 22:11, Jiri Kanicky wrote:
On 25/08/11 02:23, Bastian Blank wrote:
On Sun, Aug 14, 2011 at 12:43:14AM +1000, ganomi wrote:
Please get a name.
maverick:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
4 nfs/maverick.firm.local@FIRM.LOCAL (des3-cbc-sha1)
4 nfs/maverick.firm.local@FIRM.LOCAL (des-cbc-crc)
Please setup standard encryption types.
root@knightrider:~# klist -ke /etc/krb5.keytab
Keytab name: WRFILE:/etc/krb5.keytab
KVNO Principal
--
6 nfs/knightrider.firm.local@FIRM.LOCAL (des-cbc-crc)
DES is disabled in the meantime. Use other encryption types.
ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context():
GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more
information) - Encryption type not permitted
I hope this message is clear.
Bastian
Dear Bastian.
I am not sure what do you mean by setup standard encryption types. I
believe that those are the standard encryption types. I haven't use
any special configuration. I tried to use the most basic setting for
Kerberos and LDAP.
[kdcdefaults]
kdc_ports = 750,88
[realms]
FIRM.LOCAL = {
database_name = /var/lib/krb5kdc/principal
admin_keytab = FILE:/etc/krb5kdc/kadm5.keytab
acl_file = /etc/krb5kdc/kadm5.acl
key_stash_file = /etc/krb5kdc/stash
kdc_ports = 750,88
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal
des:normal des:v4 des:norealm des:onlyrealm des:afs3
default_principal_flags = +preauth
}
Regards,
Jiri
Hi.
I found out that NFS (in RHEL 6) does not currently support
des-hmac-sha1, des-cbc-md5 neither des-cbc-crc. However, it should
support aes256-cts-hmac-sha1-96, aes128-cts-hmac-sha1-96, des3-cbc-sha1
a arcfour-hmac. So, I am assuming that Debian Wheezy have the same issue.
I will try to generate keys for those which are supported and re-test
it. I will come back with the results.
Thanks for giving me the idea.
Jiri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637660: Acknowledgement (nfs-kernel-server: gss_accept_sec_context failed - Encryption type not permitted)
Can someone patch it as here: https://bugzilla.redhat.com/show_bug.cgi?id=719776#c29 Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591626: [pkg-cryptsetup-devel] Bug#591626: Unable to boot from encrypted Luks volume after upgrade
On 16/08/10 20:03, Jiri Kanicky wrote: On 16/08/10 00:08, Jonas Meurer wrote: Hey Jiri, On 04/08/2010 Jiri Kanicky wrote: Here is full apt log: according to your apt log, cryptsetup was not upgraded. instead, other packages where upgraded, which triggered update-initramfs, and thus updated the initramfs for linux kernel 2.6.34-1-686. you wrote the following at the initial bugreport: On Wed, Aug 04, 2010 at 08:03:35PM +1000, Jiri Kanicky wrote: I am not able to boot from my encrypted LUKS volume everytime after I upgrade (apt-get upgrade). I have to boot from rescue cd and regenerate initrd (update-initramfs) to fix the issue as I wrote here: http://ganomi.com/wiki/index.php/Rescue_an_encrypted_LUKS_LVM_volume It started a month ago. please give more information: - which version of cryptsetup and initramfs-tools do you have installed? (output of 'dpkg -l cryptsetup initramfs-tools') - which error message do you get at boot when the boot process fails? - which linux kernel version do you boot? (output of 'uname -r') - which initramfs version do you update with manual initramfs regeneration inside a chroot? (output of 'update-initramfs -u') - is the bug reproducible by invoking 'update-initramfs -u' at the running system? does this break the boot process again? in order to find the real bug here, we need more detailed information from you. so far, you're the only one who reported this problem, thousands of cryptsetup users didn't discover it while using the same version as you. greetings, jonas Hi. I attached picture with the boot message. I was digging into the problem more today and found the following: - looks like LVM does not activate the /dev/data_vg/knightrider-sec volume on the boot and therefore cryptsetup cannot see the volume. It only activates one LV; knightrider-root. - in the (initramfs) mode on the picture I typed lvm which took me to (lvm) mode. I activated all volumes in the data_vg group vgchange -ya and exited all. This brought the cryptsetup enter passphrase line. I entered the passphrase and the system booted. - The interesting bit is that executing update-initramfs right after apt-get update; apt-get upgrade will not output line with cryptsetup (bellow). However, entering it after the faulty boot, it will find the encrypted LV and note it in the cryptsetup line. update-initramfs: Generating /boot/initrd.img-2.6.34-1-686 cryptsetup: NOTE: using /dev/mapper/data_vg-knightrider--sec instead of /dev/data_vg/knightrider-sec for knightrider-sec Any idea where can be the problem? Jiri In addition: ||/ NameVersion Description +++-===-===-== ii cryptsetup 2:1.1.3-3 configures encrypted block devices ii initramfs-tools 0.98 tools for generating an initramfs 2.6.34-1-686 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591626: [pkg-cryptsetup-devel] Bug#591626: Unable to boot from encrypted Luks volume after upgrade
On 16/08/10 21:09, Jonas Meurer wrote: Hey Jiri, On 16/08/2010 Jiri Kanicky wrote: Hi. I attached picture with the boot message. I was digging into the problem more today and found the following: - looks like LVM does not activate the /dev/data_vg/knightrider-sec volume on the boot and therefore cryptsetup cannot see the volume. It only activates one LV; knightrider-root. - in the (initramfs) mode on the picture I typed lvm which took me to (lvm) mode. I activated all volumes in the data_vg group vgchange -ya and exited all. This brought the cryptsetup enter passphrase line. I entered the passphrase and the system booted. - The interesting bit is that executing update-initramfs right after apt-get update; apt-get upgrade will not output line with cryptsetup (bellow). However, entering it after the faulty boot, it will find the encrypted LV and note it in the cryptsetup line. update-initramfs: Generating /boot/initrd.img-2.6.34-1-686 cryptsetup: NOTE: using /dev/mapper/data_vg-knightrider--sec instead of /dev/data_vg/knightrider-sec for knightrider-sec Any idea where can be the problem? ok, now i've an idea where the problem is located. in order to reproduce the situation, i need more detailed information. please send me contents of your /etc/fstab, /etc/crypttab. additionally i need the debug ouput of mkinitramfs, both righty after 'apt-get upgrade' and after the faulty boot. to produce debug output, you need to change the first line of /usr/share/initramfs-tools/hooks/cryptroot to '#!/bin/sh -x', and run the following command: 'sh -x mkinitramfs -o /tmp/initramfs.debug 2/tmp/mkinitramfs.log' /tmp/mkinitramfs.log contains the required debug log. you can revert the changes in /usr/share/initramfs-tools/hooks/cryptroot afterwards. greetings, jonas For starters knightrider:~$ cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/mapper/knightrider-sec / ext3 defaults,noatime,errors=remount-ro 0 1 # /dev/sda3 /boot ext3defaults,noatime0 2 UUID=4fa73ded-e329-4b6d-a81c-a04e74b381c8 /boot ext3 defaults,noatime0 2 /dev/mapper/data_vg-knightrider--swap noneswap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 knightrider:~$ cat /etc/crypttab # target name source device key file options knightrider-sec/dev/data_vg/knightrider-secnoneluks I think that I have to wait for another upgrade which will break it again. I am not sure which package and subsequently debconf breaks it. As I do not have any packages to update now, update-initramfs outputs cryptsetup line and everything is OK. Jiri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591625: You are asking novice user for SMTP server - is this a joke
Package: reportbug Version: 4.12.4 Severity:important First, reporting bugs for Debian is a joke. It is hard, unclear, and confusing! This page is just a joke: http://www.debian.org/Bugs/Reporting Is anybody from you a human? Expectation: You come to site, where is simple form which a user submits. That's it. Normal user does not want to read 300 pages and trying to figure out how to submit a bug using email. Second, reportbug software in debian. You are asking a novice user for SMTP server. Did you ever think about what you are asking? This is novice user. They don't know what is SMTP server! This is perfect example why ordinary people do not want to use Linux. -- Jiri
Bug#591626: Unable to boot from encrypted Luks volume after upgrade
Package: apt Version: 0.7.25.3 Severity:critical I am not able to boot from my encrypted LUKS volume everytime after I upgrade (apt-get upgrade). I have to boot from rescue cd and regenerate initrd (update-initramfs) to fix the issue as I wrote here: http://ganomi.com/wiki/index.php/Rescue_an_encrypted_LUKS_LVM_volume It started a month ago. PS to Developers: Please test things more! Lately there are more things broken then fixed. -- Jiri
Bug#591626: Unable to boot from encrypted Luks volume after upgrade
On 04/08/10 22:07, Simon Richter wrote: reassign 591626 cryptsetup severity 591626 important thanks Hi, On Wed, Aug 04, 2010 at 08:03:35PM +1000, Jiri Kanicky wrote: Package: apt This is not likely to be the fault of apt. Reassigning to cryptsetup, to be triaged there and possibly passed on to the real culprit. Also, lowering severity as this sounds like an isolated case, that is, there is something special on your system that causes the upgrade process to fail rather than a general problem with the system. Obviously this bug still needs to be addressed, possibly by adding another check in some script, but it is by no means critical. Version: 0.7.25.3 That is the testing/unstable version. Please be aware that unstable breaks occasionally and if you use it, you are expected to be able to repair your system (as you've done). If you are using testing and am getting this bug, then it is obvious that noone else has seen it in the ten days that it took the package to reach testing, so it is likely to be a local configuration problem (probably said N when asked for some configuration file upgrade). I am not able to boot from my encrypted LUKS volume everytime after I upgrade (apt-get upgrade). Everytime, or only after specific packages are upgraded? If possible, can you check the log files which packages were part of the upgrade when the problem occured? PS to Developers: Please test things more! Lately there are more things broken then fixed. Generally, unstable is expected to be tested on the developer's own machine, and testing on several thousand machines. If something slips through here, then it is usually a corner case that is triggered only in very specific circumstances. Simon Hi. Here is full apt log: Log started: 2010-08-04 11:50:06 (Reading database ... 143439 files and directories currently installed.) Preparing to replace dpkg-dev 1.15.7.2 (using .../dpkg-dev_1.15.8.3_all.deb) ... Unpacking replacement dpkg-dev ... Preparing to replace libdpkg-perl 1.15.7.2 (using .../libdpkg-perl_1.15.8.3_all.deb) ... Unpacking replacement libdpkg-perl ... Replacing files in old package dpkg ... Preparing to replace grub2 1.98+20100722-1 (using .../grub2_1.98+20100802-1_i386.deb) ... Unpacking replacement grub2 ... Preparing to replace grub-pc 1.98+20100722-1 (using .../grub-pc_1.98+20100802-1_i386.deb) ... Unpacking replacement grub-pc ... Preparing to replace grub-common 1.98+20100722-1 (using .../grub-common_1.98+20100802-1_i386.deb) ... Unpacking replacement grub-common ... Preparing to replace dpkg 1.15.7.2 (using .../dpkg_1.15.8.3_i386.deb) ... Unpacking replacement dpkg ... Processing triggers for man-db ... Processing triggers for install-info ... Setting up dpkg (1.15.8.3) ... Installing new version of config file /etc/logrotate.d/dpkg ... (Reading database ... 143439 files and directories currently installed.) Preparing to replace openoffice.org-emailmerge 1:3.2.1-4 (using .../openoffice.org-emailmerge_1%3a3.2.1-5_all.deb) ... Disabling: mailmerge.py unopkg done. Unpacking replacement openoffice.org-emailmerge ... Preparing to replace sun-java6-jre 6.20-dlj-4 (using .../sun-java6-jre_6.21-1_all.deb) ... sun-dlj-v1-1 license has already been accepted Unpacking replacement sun-java6-jre ... Preparing to replace sun-java6-bin 6.20-dlj-4 (using .../sun-java6-bin_6.21-1_i386.deb) ... sun-dlj-v1-1 license has already been accepted Unpacking replacement sun-java6-bin ... Preparing to replace ure 1.6.1+OOo3.2.1-4+b1 (using .../ure_1.6.1+OOo3.2.1-5_i386.deb) ... Unpacking replacement ure ... Preparing to replace uno-libs3 1.6.1+OOo3.2.1-4+b1 (using .../uno-libs3_1.6.1+OOo3.2.1-5_i386.deb) ... Unpacking replacement uno-libs3 ... Preparing to replace libboost-iostreams1.42.0 1.42.0-3+b1 (using .../libboost-iostreams1.42.0_1.42.0-4_i386.deb) ... Unpacking replacement libboost-iostreams1.42.0 ... Preparing to replace tasksel-data 2.81 (using .../tasksel-data_2.82_all.deb) ... Unpacking replacement tasksel-data ... Preparing to replace tasksel 2.81 (using .../archives/tasksel_2.82_all.deb) ... Unpacking replacement tasksel ... Preparing to replace libsasl2-modules 2.1.23.dfsg1-5 (using .../libsasl2-modules_2.1.23.dfsg1-5.1_i386.deb) ... Unpacking replacement libsasl2-modules ... Preparing to replace libsasl2-2 2.1.23.dfsg1-5 (using .../libsasl2-2_2.1.23.dfsg1-5.1_i386.deb) ... Unpacking replacement libsasl2-2 ... Preparing to replace libpython2.6 2.6.5+20100706-1 (using .../libpython2.6_2.6.5+20100730-1_i386.deb) ... Unpacking replacement libpython2.6 ... Preparing to replace python2.6 2.6.5+20100706-1 (using .../python2.6_2.6.5+20100730-1_i386.deb) ... Unpacking replacement python2.6 ... Preparing to replace python 2.6.5-10 (using .../python_2.6.5-11_all.deb) ... Unpacking replacement python ... Preparing to replace python-minimal 2.6.5-10 (using .../python-minimal_2.6.5-11_all.deb) ... Unpacking replacement
