Bug#939170: linux: does not suspend completely, locks up
On Sun, 26 Jan 2020 18:03:23 +0100 Felix Rublack wrote: > Hi everyone, > > I have the same issue on a ThinkPad T460s (suspend works only half way, > reboot and poweroff stop just short before actual shutdown). > > I bisected the problem to the TPM driver. Blacklisting the module in > modprobe.d fixed the problem for me. > > Sample configuration: /etc/modprobe.d/blacklist-tpm.conf > > # Prevent TPM from loading. It breaks suspend and power cycle. > blacklist tpm > blacklist tpm_crb > blacklist tpm_tis > blacklist tpm_tis_core > > Greetings > Felix Rublack Hi, thanks a lot! I can confirm that this works also on my Thinkpad E460. Since you can probably provide more details, could you forward this to kernel.org? Cheers, Daniel
Bug#944257: Confirmed, possible duplicate
Hi, I have exactly the same behavior on my lenovo E460 laptop. No suspend and shutdown working since upgrade to linux 5.x. I don't know how to get more attention to this. Can we raise the severity or flag it? Some more info in my earlier report #939170. Maybe even duplicate? Cheers, Daniel
Bug#939170: Maybe wrong package?
Hi, is it possible this one is reported against the wrong package? It seems like there are a few lenovo laptop / thinkpad owners who experience this. Is there some (pseudo)package to report this to? Maybe it gets a bit more traction there... Cheers, Daniel
Bug#939170: Also with systemctl suspend
Hi, this also happens to me when I try systemctl suspend instead of a GUI action. So it's not a problem of the desktop environment but of kernel or even systemd. Maybe something with the thinkpad kernel module? Cheers, Daniel
Bug#939170: linux: does not suspend completely, locks up
Source: linux Version: 5.2.9-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Since the update from 4.19 to 5.2.9 my Lenovo Thinkpad E460 no longer suspends properly. If I close the lid or chose Suspend from the KDE launcher, the system will start to suspend but never reaches standby. Power light will blink as usual, display backlight turns off but keyboard LEDs don't turn off, fan is still active. The system doesn't respond to Ctrl-Alt-Del or change to a Terminal. No input changes anything. Waiting (30min) doesn't help either. Rebooting to Kernel 4.19 fixes the problem immediatly. Expected outcome would be a complete suspend/standby state and a complete recovery/powerup on lid open or press of any key. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (20, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#785665: ntp: support for atom driver not included
On Wed, 8 Nov 2017 05:00:50 -0600 Richard Laager <rlaa...@wiktel.com> wrote: > I recommend *against* enabling ATOM support. > > It is much better to use SHM to talk to gpsd. Here are a whole bunch of > details: > http://www.catb.org/gpsd/gpsd-time-service-howto.html > Richard, There is nothing in that document that discourages ATOM. In fact, it explains KPPS can be stable to +/- 1 uS. Most replies here so far are talking about using the Raspberry Pi GPIO for KPPS. Enabling ATOM at build time does not force it on users. As Robin pointed out, this is only a matter of adding --with-ATOM and then users are free to use it if they desire. -- Daniel M. Weeks
Bug#815037: firmware-iwlwifi: Bug also leads to kernel panic and freezes
Bug message and freezes / panic is solved when I downgraded to stable. So no HW problem.
Bug#761280:
I can confirm this behaviour, the bug has migrated to testing. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages digikam depends on: ii digikam-data 4:4.1.0-1 ii digikam-private-libs 4:4.1.0-1+b2 ii kde-runtime 4:4.14.0-2 ii libc6 2.19-11 ii libgcc1 1:4.9.1-14 ii libgphoto2-6 2.5.4-1.1 ii libgphoto2-port10 2.5.4-1.1 ii libkdcraw23 4:4.14.0-1 ii libkdecore5 4:4.14.1-1 ii libkdeui5 4:4.14.1-1 ii libkexiv2-11 4:4.14.0-1+b1 ii libkhtml5 4:4.14.1-1 ii libkio5 4:4.14.1-1 ii libkipi11 4:4.13.3-1 ii libknotifyconfig4 4:4.14.1-1 ii libkparts44:4.14.1-1 ii libopencv-core2.4 2.4.9+dfsg-1+b1 ii libopencv-imgproc2.4 2.4.9+dfsg-1+b1 ii libphonon44:4.8.0-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-sql4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-sql-sqlite 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libsolid4 4:4.14.1-1 ii libstdc++64.9.1-14 ii libthreadweaver4 4:4.14.1-1 ii perl 5.20.0-6 ii phonon4:4.8.0-1 Versions of packages digikam recommends: ii ffmpegthumbs 4:4.13.3-1+b1 ii iceweasel [www-browser] 31.1.0esr-1 ii kipi-plugins 4:4.1.0-1+b2 ii konqueror [www-browser] 4:4.14.0-1 ii lynx-cur [www-browser] 2.8.9dev1-2 ii w3m [www-browser]0.5.3-17 Versions of packages digikam suggests: pn digikam-doc none ii systemsettings 4:4.11.11-2 -- no debconf information
Bug#749769:
Is there a way to work around this bug until 4.13.2 will be in experimental? I've got most of my files on my NAS and running debian testing right now...
Bug#407074: libsane: incorrect scanimage: no SANE devices found for HP Scanjet 6200C
Package: libsane Version: 1.0.18-5 Severity: normal This scanner worked fine in sarge, now it's unusable. Will the Sarge libsane packages still work on Etch? The test below is with libsane from Sid on a Etch system, but the same behavior was seen with the libsane from Etch. All commands below are exactly as entered, no other commands in between. For some reason it's alternating between seeing the scanner and not seeing the scanner. sane-find-scanner always sees the scanner correctly. Reconnecting the usb plug does not fix the problem. $ sane-find-scanner ... found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0201 [HP ScanJet 6200C]) at libusb:001:011 $ SANE_DEBUG_AVISION=255 USB_DEBUG=255 scanimage --resolution 300 \ -l 0 -t 0 -y 279 -x 215.788 --mode=Grayscale 2debug.worked ii_image..pnm $ SANE_DEBUG_AVISION=255 USB_DEBUG=255 scanimage --resolution 300 \ -l 0 -t 0 -y 279 -x 215.788 --mode=Grayscale 2debug.failed ii_image..pnm $ diff debug.worked debug.failed 159c159 scanimage: rounded value of br-x from 215.788 to 215.788 --- scanimage: no SANE devices found $ cat debug.failed usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 001 usb_os_find_devices: Found 011 on 001 usb_os_find_devices: Found 010 on 001 usb_os_find_devices: Found 009 on 001 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 003 on 001 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb [sanei_debug] Setting debug level of avision to 255. [avision] sane_init:(Version: 1.0 Build: 201) usb_set_debug: Setting debugging level to 255 (on) usb_os_init: Found USB VFS at /dev/bus/usb [avision] sane_init: parsing config line [avision] sane_init: config file line 1: ignoring empty line [avision] sane_init: parsing config line # This are the possible options. Normally any scanner [avision] sane_init: config file line 2: ignoring comment line [avision] sane_init: parsing config line # should work just fine without them - and they are only [avision] sane_init: config file line 3: ignoring comment line [avision] sane_init: parsing config line # needed for test and debugging. So if you experience problems [avision] sane_init: config file line 4: ignoring comment line [avision] sane_init: parsing config line # and you solve them with enabling options here, please notify [avision] sane_init: config
Bug#407078: apt: dynamic mmap ran out of room - on Etch with small sources.list
Package: apt Version: 0.6.46.4 Severity: important I've run into this error for years. Come on guys, is it really that complicated? And why are you downgrading the other reports on this bug to wishlist? This is a serious bug that affects many users. Using the basic packaging functionality of Debian should not require looking up obscure workarounds on the web. It makes the whole distribution look unprofessional (in the bad sense of that word). -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture i386; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Authentication ; APT::Authentication::TrustCDROM true; APT::Default-Release etch; Dir /; Dir::State var/lib/apt/; Dir::State::lists lists/; Dir::State::cdroms cdroms.list; Dir::State::userstatus status.user; Dir::State::status /var/lib/dpkg/status; Dir::Cache var/cache/apt/; Dir::Cache::archives archives/; Dir::Cache::srcpkgcache srcpkgcache.bin; Dir::Cache::pkgcache pkgcache.bin; Dir::Etc etc/apt/; Dir::Etc::sourcelist sources.list; Dir::Etc::sourceparts sources.list.d; Dir::Etc::vendorlist vendors.list; Dir::Etc::vendorparts vendors.list.d; Dir::Etc::main apt.conf; Dir::Etc::parts apt.conf.d; Dir::Etc::preferences preferences; Dir::Bin ; Dir::Bin::methods /usr/lib/apt/methods; Dir::Bin::dpkg /usr/bin/dpkg; DPkg ; DPkg::Pre-Install-Pkgs ; DPkg::Pre-Install-Pkgs:: /usr/sbin/dpkg-preconfigure --apt || true; -- /etc/apt/preferences -- Package: * Pin: release a=testing Pin-Priority: 999 Package: * Pin: release a=etch-backports Pin-Priority: 200 -- /etc/apt/sources.list -- # Security deb http://security.debian.org/ etch/updates main contrib non-free deb-src http://security.debian.org/ etch/updates main # Sarge deb http://mirrors.tummy.com/debian/ sarge main contrib non-free # Stable deb-src http://mirrors.tummy.com/debian/ etch main contrib non-free deb http://mirrors.tummy.com/debian/ etch main contrib non-free # Testing deb http://mirrors.tummy.com/debian/ sid main contrib non-free -- System Information: Debian Release: 4.0 Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages apt depends on: ii debian-archive-keyring 2006.11.22 GnuPG archive keys of the Debian a ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-19 GCC support library ii libstdc++6 4.1.1-19The GNU Standard C++ Library v3 apt recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402769: qbrew: displays first item only in each section
Package: qbrew Version: 0.3.9-4 Severity: important When I open a recipe file, qbrew displays only the first ingredient in each tabbed section: only one grain, one hop, and one miscellaneous. When I examine the file with less, then I see all the ingredients present. (That's good, because it means that qbrew hasn't corrupted the file.) I've tried this with a recipe file of my own, as well as with the files in /usr/share/doc/qbrew/examples. Thanks, Dan -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.1.060629 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages qbrew depends on: ii libaudio2 1.8-2 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-9GNU C Library: Shared libraries ii libfontconfig12.4.2-1generic font configuration library ii libfreetype6 2.2.1-5FreeType 2 font engine, shared lib ii libgcc1 1:4.1.1-21 GCC support library ii libglib2.0-0 2.12.4-2 The GLib library of C routines ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii libpng12-01.2.15~beta5-0 PNG library - runtime ii libqt4-core 4.2.1-2Qt 4 core non-GUI functionality ru ii libqt4-gui4.2.1-2Qt 4 core GUI functionality runtim ii libsm61:1.0.1-3 X11 Session Management library ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-4 X11 client-side library ii libxcursor1 1.1.7-4X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes31:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxinerama1 1:1.0.1-4.1X11 Xinerama extension library ii libxrandr22:1.1.0.2-5X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii libxt61:1.0.2-2 X11 toolkit intrinsics library ii zlib1g1:1.2.3-13 compression library - runtime qbrew recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385973: qbrew: will not import beerxml files
Package: qbrew Version: 0.3.9-1 Severity: normal Hi there, When I try to open a recipe in beerxml format, QBrew responds with this message (for example): Unable to import the file untitled.xml I might have thought that this was a problem with the files I downloaded from different websites. But it happens also with a file that I exported from QBrew. Any thoughts? Thanks, Dan -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.1.060629 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages qbrew depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-13 GCC support library ii libqt4-core 4.1.4-1.1 Qt 4 core non-GUI functionality ru ii libqt4-gui 4.1.4-1.1 Qt 4 core GUI functionality runtim ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 qbrew recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
