@sttzr :
I'm the Debian package maintainer, I don't maintain the package for
Ubuntu, nor do I have Ubuntu upload rights.
I watch the bug reports for Ubuntu packages and fix them "upstream"
(Debian is Ubuntu's upstream), but that's it.
If you want to learn more about the relationship between
Weird, 5.13 is a fairly recent version, it should have the failsafe.
About the contents of /sys/firmware/efi/efivars, I wouldn't know what to
do with it, I'm just the package maintainer, I didn't write the kernel
module itself, and I'm not a specialist of NVRAM.
I really hope that the store will
Sadly, if you can't access BIOS, I have no other idea. My "plan" was to
try to enter the BIOS somehow, then disable UEFI boot (to boot plain old
BIOS compatibility mode) and boot Linux or a live Linux USB key, and see
if you can clear the dump files from there (which may or may not be
possible if
Did you try to press F1 **before** the message appears ?
I'm really surprised that Lenovo didn't foresee any method to access
BIOS when the NVRAM is full.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bricked how ?
Can you still access BIOS setup and/or boot on a USB key ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953261
Title:
kernel >= 5.13 BUG: kernel NULL pointer dereference
To manage
After seeing into the process of signing DKMS modules, I confirm that
creating the keys and configuring DKMS to sign modules after building is
not configured in the modules packages.
Closing the bug as invalid.
** Changed in: acpi-call (Ubuntu)
Status: New => Invalid
--
You received
*** This bug is a duplicate of bug 1899591 ***
https://bugs.launchpad.net/bugs/1899591
** Changed in: acpi-call (Ubuntu)
Status: Invalid => Fix Released
** This bug has been marked a duplicate of bug 1899591
acpi-call-dkms: proc_create() broken with linux-hwe-5.8
--
You received
*** This bug is a duplicate of bug 1899591 ***
https://bugs.launchpad.net/bugs/1899591
This was fixed in 1.1.0-6, closing.
** Changed in: acpi-call (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, scratch that, the patch is the same as the previous one, it's only
intended for focal.
Another question then, why don't you just backport the current version
(1.1.0-6) to focal, instead of creating a new patch ?
Regards,
--
Raphaël Halimi
--
You received this bug notification because
or is it intentional ?
Regards,
--
Raphaël Halimi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899591
Title:
acpi-call-dkms: proc_create() broken with linux-hwe-5.8
To manage notifications about
Yes, something changed in Linux 5.6, which broke the module building.
I published a newer version of the package (1.1.0-6) fixing the problem.
You can either :
- Download the updated Debian package [1] and install it manually (the simplest)
- Or wait for a backport for Ubuntu stable / Linux
Mmmh, a search through sources.debian.net indicates that this path is
mentioned in the source code of packages dkms and virtualbox.
https://codesearch.debian.net/search?q=%2Fvar%2Flib%2Fshim-
signed%2Fmok%2FMOK.der
I guess that DKMS creates the certificate, and VirtualBox seems able to
use it.
Hi,
thanks for the report.
I admit that, since I didn't own an UEFI machine until recently, I never
looked in the secure boot process.
Now that I do, I need to determine if this signature is supposed to be
done by the packages modules themselves, by DKMS once and for all, or
manually by the
Setting the charge thresholds between 40 and 85 percent means that the
charge will **start** when the battery level will reach 40%, and
**stop** when it reaches 85%. And since the charger is plugged in, the
battery isn't used, thus the charge is not decreasing.
So, this is expected behavior.
Hi,
You already reported the bug in Debian, where I explained the reason why
1.3.0 wasn't uploaded yet.
1.3.0 was released by upstream less than a week ago. Please stop
harassing me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Closing as invalid.
** Changed in: acpi-call (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845968
Title:
package acpi-call-dkms 1.1.0-5 failed to
For more information, see https://bugs.launchpad.net/ubuntu/+source
/acpi-call/+bug/1830040
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858793
Title:
acpi-call dkms module fails to build
To
Starting with kernel 5.2, modules depending on ACPI won't build and
produce an error. acpi-call from version 1.1.0-5 handles this nicely by
checking the architecture before build and exit with a non-fatal error
if the architecture doesn't support ACPI, but anyway, building acpi-call
on an
The error is in the terminal output:
ERROR (dkms apport): kernel package linux-
headers-5.2.0-050200rc7-lowlatency is not supported
Did you install the kernel headers matching your kernel ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
TLP 1.2.2 was accepted in Debian Unstable on May 22nd 2019, and was
synced to Ubuntu Devel (currently Eoan) shortly after.
If you can't wait, Thomas is right, use the packages from the PPA.
Closing the bug.
** Changed in: tlp (Ubuntu)
Status: Confirmed => Fix Committed
--
You received
Well, I uploaded it to Debian on May 31st, and it was even accepted in
Buster (which was testing at the time) five days later, on June 6th; but
I see on my Debian Maintainer dashboard that it never reached eoan. I
didn't investigate further about why it was not automatically synced as
usually.
I
Did you reboot your machine after uninstalling TLP ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834085
Title:
Bluetooth touchpad (Apple Magic Trackpad) disconnects every few
minutes
To
THIS IS NOT A BUG.
This is in TLP's FAQ :
https://linrunner.de/en/tlp/docs/tlp-faq.html#btusb
Please read the documentation, do what it says, confirm that your
problem is fixed, and close the bug as invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks a lot for your help and your patience. I'm now going yo finalize
the package and have it uploaded soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830040
Title:
acpi-call 1.1.0-4 ADT
Hmm. Not a bad idea.
In that case the test line should be:
if ! grep -q -E "^CONFIG_ACPI=[ym]$" "$kernel_source_dir/.config"
2>/dev/null ; then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830040
Hi,
Thanks again for your help.
Finally, instead of hard-coding a list of architectures supporting ACPI,
someone on debian-devel suggested to test for ACPI support at build
time, and I like this idea a lot.
Can you please tell me what's the value of "CONFIG_ARCH_SUPPORTS_ACPI"
on an
Hi,
Could you try with:
BUILD_EXCLUSIVE_ARCH="(i.86|(x86_|ia|aarch)64)"
In dkms.conf and see if it fixes the problem ?
With this additional line, the module should build only on i386, amd64,
arm64 and ia64, and output a (non-fatal) error on other architectures.
I'd like to check that the
Information from Thadeu Lima de Souza Cascardo:
acpi_root_dir is undefined on architectures which are not built with
ACPI. That means that building acpi-call on those arches will fail
starting with 5.2.
On previous kernels, only a warning would be emitted during modpost,
telling that the symbol
previously received an automatic bug report from Launchpad stating
that the build failed on armhf, ppc64el and s390x. Is there any other
architecture supported by Debian or Ubuntu which doesn't support ACPI ?
Regards,
--
Raphaël Halimi
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1830040 ***
https://bugs.launchpad.net/bugs/1830040
I stand corrected: the bug report was now automatic, it was filled by
Seth Forshee. Apologies, my bad.
** This bug has been marked a duplicate of bug 1830040
acpi-call 1.1.0-4 ADT test failure with
, aside from armhf, ppc64el and s390x ?
Regards,
--
Raphaël Halimi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830040
Title:
acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
To manage
No problem, just be more careful in the future.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826430
Title:
acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build
To manage
The error message is clear.
** Changed in: acpi-call (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826430
Title:
acpi-call-dkms 1.1.0-2ubuntu1: acpi-call
** Bug watch added: TLP (upstream) #319
https://github.com/linrunner/TLP/issues/319
** Also affects: tlp-upstream via
https://github.com/linrunner/TLP/issues/319
Importance: Unknown
Status: Unknown
** Changed in: tlp (Ubuntu)
Assignee: (unassigned) => Raphaël Halimi (r
Upstream doesn't plan to provide an official GUI for TLP.
A separate project (https://github.com/d4nj1/TLPUI), which seems active,
exists, but it's for GTK. I don't know if a similar project exists fir
KDE/QT.
In any case, I'm reassigning this bug to kconfig.
** Package changed: tlp (Ubuntu) =>
This is fixed in TLP 1.2. I'll try to package it quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814083
Title:
TLP does not detect NVMe SSD disks
To manage notifications about this bug go
Could you please open a terminal and type :
ls -l /usr/src/acpi-call-1.1.0/dkms.conf
And report the output here ?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815605
Title:
TLP doesn't force anything on. It's the desktop's Bluetooth app that
turns on the Bluetooth device on startup. Also, TLP's package masks the
rfkill service files because that would break the
RESTORE_DEVICE_STATE_ON_STARTUP option (among other ones).
This is written in the FAQ
Doesn't setting RESTORE_DEVICE_STATE_ON_STARTUP to 1 in /etc/default/tlp
achieves what you expect ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809783
Title:
When TLP is installed, Bluetooth
packaging by removing the Ubuntu tweaks we took care of implementing in
debian/rules and debian/control, since you circumvent them anyway.
Regards,
--
Raphaël Halimi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
NO.
This is not about cpupower. TLP recommends linux-tools on Ubuntu (and
linux-cpupower on Debian) for the x86_energy_perf_policy binary, which
is needed for some reporting functions (look in tlp-stat and tlp-
functions). This is stated quite clearly in the comments at the top of
the
*** This bug is a duplicate of bug 1700783 ***
https://bugs.launchpad.net/bugs/1700783
** This bug has been marked a duplicate of bug 1700783
acpi-call 1.1.0-3 ADT test failure with linux 4.12.0-4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1700783 ***
https://bugs.launchpad.net/bugs/1700783
** This bug is no longer a duplicate of bug 1724862
acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
** This bug has been marked a duplicate of bug 1700783
acpi-call
*** This bug is a duplicate of bug 1700783 ***
https://bugs.launchpad.net/bugs/1700783
** This bug is no longer a duplicate of bug 1724862
acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
** This bug has been marked a duplicate of bug 1700783
acpi-call
*** This bug is a duplicate of bug 1700783 ***
https://bugs.launchpad.net/bugs/1700783
** This bug is no longer a duplicate of bug 1724862
acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
** This bug has been marked a duplicate of bug 1700783
acpi-call
*** This bug is a duplicate of bug 1700783 ***
https://bugs.launchpad.net/bugs/1700783
** This bug has been marked a duplicate of bug 1700783
acpi-call 1.1.0-3 ADT test failure with linux 4.12.0-4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1700783 ***
https://bugs.launchpad.net/bugs/1700783
** This bug has been marked a duplicate of bug 1700783
acpi-call 1.1.0-3 ADT test failure with linux 4.12.0-4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: acpi-call (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1503099
Title:
acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
By default, (dis)charge thresholds are not modified by TLP, you have to
manually enable this feature in /etc/default/tlp.
You also have to install acpi-call-dkms for TLP to be able to modify
those thresholds.
Please read http://linrunner.de/en/tlp/docs/tlp-configuration.html.
--
You received
To be clear, what's really bothering me is this line in
DpkgTerminalLog.txt:
Unpacking tlp (1.1-1ubuntu1) over (1.1-1) ...
Which mean that the version that was there before you tried the upgrade
was 1.1-1. But 17.10 (Artful) has 0.9-3.
Even more disturbing is this line:
dpkg-query: warning:
Thanks, but this doesn't explain what I asked in the first place: why so
many "--force-yes" or "--assume-yes" in DpkgHistoryLog.txt ?
And please write in English if able.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Dear José,
If you're not willing to provide the information asked, I'll have to
close the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759255
Title:
package tlp-rdw 0.9-3 failed to
By reading DpkgHistoryLog.txt, it seems the system is trying to upgrade
from 0.9-3 to 1.1-1 (and then to 1.1-1ubuntu1).
It would be really helpful to know exactly what was done, and on what
type of installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Why so many "--force-yes" or "--assume-yes" in DpkgHistoryLog.txt ? Is
that an installation through Plesk or something ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759255
Title:
package tlp-rdw
** Bug watch added: Debian Bug tracker #894150
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894150
** Also affects: tlp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894150
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Oh, in that case, no problem. I take it back. Thanks a lot !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758798
Title:
tlp recommends smartmontools which then pulls in Postfix mailserver
To
I hoped to avoid that. Now I'll have to request a sync when the bug is
fixed in Debian. Couldn't you wait a few days ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758798
Title:
tlp recommends
Hi @fossfreedom,
I already made the change in my local Git repository, but I don't know
when I'll be able to release it, first because I don't have a lot of
time available right now, and secondly because I'm not (yet) a Debian
Maintainer so I have to rely on my sponsor for the actual upload. I'll
By the way, I don't understand how this dependency chain resolves to
postfix:
smartmontools recommends mailx | bsd-mailx
mailx is a virtual package provided by mailutils and bsd-mailx
Both mailutils and bsd-mailx depend on default-mta | mail-transport-
agent
default-mta is a virtual package
Hi, TLP Debian maintainer here.
I see three different problems here :
1/ TLP does "need" smartctl, to display info about HDD health. Not
having it installed doesn't prevent TLP from working, it simply displays
a message inviting the user to install it. So I guess smartmontools
could be demoted
- Use of option -fstack-protector-strong not supported by GCC (DKMSBuildLog.txt)
- No update from user since the bug was reported
- No update from anyone else either
** Changed in: acpi-call (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
- I suspect the user simply didn't have the kernel headers installed
(DKMSBuildLog.txt)
- No update from user since the bug was reported (more than two years ago)
- No update from anyone else either
** Changed in: acpi-call (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug
*** This bug is a duplicate of bug 1724862 ***
https://bugs.launchpad.net/bugs/1724862
** This bug has been marked a duplicate of bug 1724862
acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1724862 ***
https://bugs.launchpad.net/bugs/1724862
** This bug has been marked a duplicate of bug 1724862
acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1724862 ***
https://bugs.launchpad.net/bugs/1724862
** This bug has been marked a duplicate of bug 1724862
acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
--
You received this bug notification because you are a member of
Hi,
Debian developer here. This bug was fixed in 1.1.0-4 (artful) thanks to
a patch from Colin Ian King (see
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1700783). I'm
not sure how Ubuntu updates/backports work, but I guess you can either
request a backport, or ask an Ubuntu developer
tures are the ones related to battery (dis)charge thresholds.
Regards,
- --
Raphaël Halimi
-BEGIN PGP SIGNATURE-
iQKtBAEBCgCXFiEEb6lOxdKMjWi+eSrvTZn2ZgpZgnsFAlnD0S9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDZG
QTk0RUM1RDI4QzhENjhCRTc5MkF
Hi,
Debian TLP package maintainer here. Two questions :
- What version of tlp was installed ?
- Did you make changes to its default configuration ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1700783 ***
https://bugs.launchpad.net/bugs/1700783
** This bug has been marked a duplicate of bug 1700783
acpi-call 1.1.0-3 ADT test failure with linux 4.12.0-4.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
n to build the module ?
Regards,
--
Raphaël Halimi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700625
Title:
acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
To manage notificat
I suspect you don't have the kernel headers for your running kernel
installed.
Do you actually have the "linux-headers-4.3.0-040300rc4-lowlatency"
package (or whatever package providing those headers in Ubuntu)
installed on your system ?
Could you give me the output of "sudo apt-config dump |
Hi,
I can't reproduce this bug on my Debian Sid box:
raph@arche:~$ LANG=C sudo apt-get install acpi-call-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
acpi-call-dkms
0 upgraded, 1 newly
I just installed Oneiric and this doesn't seem to be fixed (or maybe my
problem is different).
The Launch terminal default keybinding, which launches gnome-terminal
(this cannot be changed anymore, Terminal is now missing from the
Default Applications settings, this is bad) indeed passes the
I just made a little test : I changed the value of
/desktop/gnome/applications/terminal/exec in gconf from gnome-terminal
to xterm and now xterm has the right settings.
So the real problem is indeed that default keybindings and custom ones
are somewhat started differently by gnome (or its
Hi, using all information gathered mainly here and on ThinkWiki, I made
a little package as a workaround for this bug (and others). It should
work out-of-the-box for everyone who has an UltraBase with a CD/DVD in
the UltraBay (but it should work with any brand handled by the new
kernel's dock
Hi, using all information gathered mainly here and on ThinkWiki, I made
a little package as a workaround for this bug (and others). It should
work out-of-the-box for everyone who has an UltraBase with a CD/DVD in
the UltraBay (but it should work with any brand handled by the new
kernel's dock
Hi, using all information gathered mainly here and on ThinkWiki, I made
a little package as a workaround for this bug (and others). It should
work out-of-the-box for everyone who has an UltraBase with a CD/DVD in
the UltraBay (but it should work with any brand handled by the new
kernel's dock
Hi, although not exactly the same bug, this one is related to 189185,
242638 and 369131, and I made a little script as a workaround for these
three bugs, but it also includes the fix for this.
** Attachment added: udev-dock_0.2_all.deb
*** This bug is a duplicate of bug 189185 ***
https://bugs.launchpad.net/bugs/189185
** This bug has been marked a duplicate of bug 189185
Thinkpad X61 hangs when removing from dock
--
IBM X40 Ultrabase X4 eject freezes in Jaunty
https://bugs.launchpad.net/bugs/369131
You received this
*** This bug is a duplicate of bug 189185 ***
https://bugs.launchpad.net/bugs/189185
** This bug has been marked a duplicate of bug 189185
Thinkpad X61 hangs when removing from dock
--
Thinkpad freezes when undocking from Ultrabay if CD/DVD-ROM drive has not been
deleted manually
80 matches
Mail list logo
