[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
@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 Debian and Ubuntu, please read this : https://wiki.ubuntu.com/Ubuntu/ForDebianDevelopers Unfortunately, I don't plan to become an Ubuntu developer or uploader, I don't have time for this. However, a couple of weeks ago, when I saw @mwbradley's messages and yours, I tried to help by searching how to request for a package to be backported in Ubuntu older releases. I'm pretty sure that there used to be some wiki page explaining how a "mere" user could request for a particular package to be backported, but after spending nearly an hour crawling on Ubuntu wiki, I couldn't find it. All I found was the backports page which explains that one has to prepare a backported package, open a bug, find a sponsor, etc etc. I have all my tools to prepare packages for Debian, creating such a set of tools for Ubuntu, even only for two particular releases, would take me hours, let alone opening two bugs, finding a sponsor, request the backports, etc etc. I don't have that time. At that point, I was just fed up, and gave up without even leaving a note here to explain it. @linrunner was more clever than me by sending directly an e-mail to a well known Ubuntu developer who previously patched acpi-call in Ubuntu for a this kernel incompatibility when it first appeared. We're still waiting for an answer. If you want this backport that bad, try to find the procedure to request it; if not, just download version 1.2.2 from Debian unstable or Ubuntu devel, and install it on your machine. Sorry, but I won't spend any more time on this bug. Regards, -- Raphaël -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
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 be able to bring your computer back to life. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
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 you boot in BIOS compatibility mode - maybe /sys/firmware/efi is accessible only when booted in UEFI mode, I don't know, I didn't test that). Being the maintainer of the Debian acpi-call package and having delayed the new version for so log, I feel kind of responsible for your problem. Little did I know that a manufacturer, let alone a well-established one like Lenovo, wouldn't foresee this problem and let their product be bricked by a full NVRAM. I know that the X131e is a low-end model, but still, it hardly makes sense. Another thing that I don't understand is that there is a failsafe in the Linux kernel that prevents writing to the NVRAM when it's more that 50% full; I don't know why Ubuntu kept filling your NVRAM with these dumps until it was completely full. Did you add "efi_no_storage_paranoia" to the kernel command line in GRUB configuration ? Or maybe you were using an older kernel dating from before this failsafe was implemented ? -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
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. https://bugs.launchpad.net/bugs/1953261 Title: kernel >= 5.13 BUG: kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953261] Re: kernel >= 5.13 BUG: kernel NULL pointer dereference
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1953261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872213] Re: MOK not asked upon installation of acpi-call-dkms
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872213 Title: MOK not asked upon installation of acpi-call-dkms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1872213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912287] Re: acpi-call-dkms 1.1.0-5: acpi-call kernel module failed to build
*** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912287 Title: acpi-call-dkms 1.1.0-5: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1912287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912287] Re: acpi-call-dkms 1.1.0-5: acpi-call kernel module failed to build
*** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912287 Title: acpi-call-dkms 1.1.0-5: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1912287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899591] Re: acpi-call-dkms: proc_create() broken with linux-hwe-5.8
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 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1899591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899591] Re: acpi-call-dkms: proc_create() broken with linux-hwe-5.8
Hi Andrea, Thanks for spotting the bug and providing a patch. I'm going to prepare a new upload in Debian to include it. However, I have a question: you say that the incompatibility was introduced in 5.8, but in your patch, the #ifdef block mentions (5, 6, 0) as a condition. Is it a mistake 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1899591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878396] Re: Module will not (re)install on recent kernels
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 Mint (it's already synced to Ubuntu Groovy) [1] https://packages.debian.org/sid/all/acpi-call-dkms/download Closing since the fix was already released. ** Changed in: acpi-call (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878396 Title: Module will not (re)install on recent kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1878396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872213] Re: MOK not asked upon installation of acpi-call-dkms
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. I will see if I can do the same with acpi-call, but it's too late for Focal. Maybe the package could be backported once it will be synchronized from Debian Sid. In the meantime I'll let the bug report open. Thanks for your help ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872213 Title: MOK not asked upon installation of acpi-call-dkms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1872213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872213] Re: MOK not asked upon installation of acpi-call-dkms
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 user. In the meantime, could you tell me if you manually created /var/lib /shim-signed/mok/MOK.der or if it was done by some package at some point ? The documents I read about secure boot on Debian seem to indicate that this certificate must be created by the user, and since there's no "standard" place to do that, I don't see how I could automate this in the package scripts. Regards, -- Raphaël -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872213 Title: MOK not asked upon installation of acpi-call-dkms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1872213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872965] Re: tlp keep level of upper bound
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. Please read the documentation. Closing as invalid. ** Changed in: tlp (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/1872965 Title: tlp keep level of upper bound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1872965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861966] Re: need version 1.3 in focal
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. https://bugs.launchpad.net/bugs/1861966 Title: need version 1.3 in focal To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1861966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845968] Re: package acpi-call-dkms 1.1.0-5 failed to install/upgrade: installed acpi-call-dkms package post-installation script subprocess returned error exit status 10
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 install/upgrade: installed acpi-call-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1845968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858793] Re: acpi-call dkms module fails to build
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1858793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858793] Re: acpi-call dkms module fails to build
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 architecture without ACPI is not expected to work. So, closing as invalid. ** Changed in: acpi-call (Ubuntu) Status: New => Invalid ** Changed in: acpi-call (Ubuntu Bionic) 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/1858793 Title: acpi-call dkms module fails to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1858793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845968] Re: package acpi-call-dkms 1.1.0-5 failed to install/upgrade: installed acpi-call-dkms package post-installation script subprocess returned error exit status 10
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 Ubuntu. https://bugs.launchpad.net/bugs/1845968 Title: package acpi-call-dkms 1.1.0-5 failed to install/upgrade: installed acpi-call-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1845968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842169] Re: AHCI Host Controller Runtime Power Management not set to powersave mode "auto" despite set AHCI_RUNTIME_PM_ON_BAT to "auto"
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842169 Title: AHCI Host Controller Runtime Power Management not set to powersave mode "auto" despite set AHCI_RUNTIME_PM_ON_BAT to "auto" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1842169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830040] Re: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
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 also see in my dashboard, for eoan, "prop: 1.1.0-5". I don't know what this means; "proposed updates" maybe ? But I thought proposed updates was a testing ground for updates to **stable** ? I wouldn't mind an explanation... Also, if kernel 5.2 is ever backported to disco, acpi-call would also need a backport. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830040] Re: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
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 test failure with linux 5.2.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830040] Re: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
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 Title: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830040] Re: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
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 architecture which doens't support ACPI ? For example, please grep CONFIG_ARCH_SUPPORTS_ACPI in /lib/modules/-/build/.config. For the moment, my solution consist of adding this snippet at the end of the DKMS config file: # On architectures which don't support ACPI, disable building if ! grep -q "^CONFIG_ARCH_SUPPORTS_ACPI=y$" "$kernel_source_dir/.config" 2>/dev/null ; then BUILD_EXCLUSIVE_ARCH="^do_not_build$" fi I'd just like to test it on an unsupported architecture before uploading the new package. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830040] Re: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
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 regexp is correct before uploading, and since I'm only a Debian Maintainer (not Debian Developer), I don't have access to porter boxes, and requesting it is quite tedious. Moreover, the Debian machines pages [1] doesn't mention any ia64 machine. [1] https://db.debian.org/machines.cgi Thanks a lot for your help ! -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830040] Re: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
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 was undefined. But it also meant that such a
module would not load, making the build kinda pointless.
Starting with 5.2, external modules will also have to define
KBUILD_MODPOST_WARN, in order to build with undefined symbols. See
upstream commit 83da1bed86cdfe3abb2a33c36a2a5aaf5f390ef6 ("modpost: make
KBUILD_MODPOST_WARN also configurable for external modules").
However, I don't think we should fix the build of the module here, as
it's pointless on those architectures where we don't support ACPI.
Duplicate bug: https://bugs.launchpad.net/ubuntu/+source/acpi-
call/+bug/1830787
--
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830787] Re: acpi-call won't build on 5.2 kernel for some architectures
*** This bug is a duplicate of bug 1830040 *** https://bugs.launchpad.net/bugs/1830040 Hi, Thanks for this precious information. I'm preparing an upload of this package for Debian. As you're suggesting, I intend to disable the package for architectures which don't support ACPI. I 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 of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830787 Title: acpi-call won't build on 5.2 kernel for some architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830787] Re: acpi-call won't build on 5.2 kernel for some architectures
*** 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 linux 5.2.0-0.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830787 Title: acpi-call won't build on 5.2 kernel for some architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830040] Re: acpi-call 1.1.0-4 ADT test failure with linux 5.2.0-0.1
Hi, Thanks for the bug report. I'm preparing an upload of this package for Debian. As suggested by Thadeu Lima de Souza Cascardo, I intend to disable the package for architectures which don't support ACPI. Are there other architectures supported by Debian or Ubuntu which doesn't support ACPI, 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1830040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826430] Re: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1826430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826430] Re: acpi-call-dkms 1.1.0-2ubuntu1: acpi-call kernel module failed to build
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 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1826430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814083] Re: TLP does not detect NVMe SSD disks
** 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 (raph) ** Changed in: tlp (Ubuntu) Status: New => Confirmed ** Changed in: tlp (Ubuntu) Status: Confirmed => In Progress -- 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 to: https://bugs.launchpad.net/tlp-upstream/+bug/1814083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781751] Re: Wish: create Kubuntu GUI/KCM for TLP
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) => kconfig (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781751 Title: Wish: create Kubuntu GUI/KCM for TLP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kconfig/+bug/1781751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814083] Re: TLP does not detect NVMe SSD disks
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 to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1814083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815605] Re: acpi-call-dkms is missing a configuration file
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: acpi-call-dkms is missing a configuration file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1815605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809783] Re: When TLP is installed, Bluetooth always on when power on my laptop regardless of its previous state
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 (https://linrunner.de/en/tlp/docs/tlp- faq.html#radios). Please read the documentation before making false assumptions. If you think that the default setting of RESTORE_DEVICE_STATE_ON_STARTUP should be reversed, please open a new bug for that, and/or ask upstream why this choice was made. ** Changed in: tlp (Ubuntu) Status: Triaged => Invalid -- 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 always on when power on my laptop regardless of its previous state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1809783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809783] Re: When TLP is installed, Bluetooth always on when power on my laptop regardless of its previous state
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 always on when power on my laptop regardless of its previous state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1809783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1783455] Re: tlp shouldn't recommend linux-tools
Le 05/08/2018 à 05:34, Adam Conrad a écrit : > And no, we're not going to ask our upstreams every time we make a change > to a package. If we did, there would be no Ubuntu, no Debian, no > Fedora, arguably no meaningfully usable Free Software distributions at > all. Not necessarily, but the very least would have been to ask the package maintainer (me) for advice. It would have prevented your wrong initial analysis that TLP doesn't need linux-tools at all (because you thought it was about cpupower) whereas it really does (because it uses x86_energy_perf_policy). In any case, that's how we do it in Debian. > And, it turns out, sometimes people who understand the inner workings > (and failings, in this case) of a specific distribution know what's > better for it than the people demanding we ask their permission before > we exercise the rights given to us by the software's license. Again, I can't speak for Thomas, but in my case, I was not upset by your changing the package; I was upset because it's been done in a matter of minutes, based on a wrong analysis, and without even asking me or upstream for advice. > I don't dispute that my initial analysis was incorrect and tlp can > indeed make use of linux-tools, but that doesn't change my conclusion. > It's not a hard dependency, the functionality is not required for the > package to work, and pulling in several megabyte of a potentially > useless perf (because it's for the wrong kernel ABI) just to get at one > small utility is not reasonable with the state of the Ubuntu archive. On the contrary. Allow me to quote your very words: "Recommends are meant as weak dependencies (you really want this, but we can work around it not being there)" IMHO, this describes pretty well the relationship between TLP and x86_energy_perf_policy, so the Recommends seems perfectly justified to me. This behavior, along with LP #1758798, make me suspect that lighten the dependencies for Ubuntu Budgie has become some kind of long-term goal, which I'm not sure that vanilla Ubuntu will benefit from. Anyway, as it seems that the Ubuntu project is determined to change package dependencies as they see fit (which I find perfectly reasonable) against both upstream's and original maintainer's advice (which I find less reasonable), I guess you won't mind if I simplify the Debian 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.launchpad.net/bugs/1783455 Title: tlp shouldn't recommend linux-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1783455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783455] Re: tlp shouldn't recommend linux-tools
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 debian/rules file (line 6 !!). I don't know how things are usually done in Ubuntu, but reporting a (so- called) bug and uploading a (misguided) patched version six minutes later without even notifying the package maintainer or asking for his/her advice (let alone asking for permission...) is clearly not appropriate. I'll be frank, I'm quite upset with the Ubuntu community these days, between the dozens of reports about bugs already fixed long ago, the "bug" wishing for a KDE GUI (a simple Google search would be sufficient to explain the state of things about TLP ans GUIs), and now this. Next time such a thing happen, I'll definitely stop caring about Ubuntu, Launchpad bugs or the merging/syncing state of the package, and focus exclusively on Debian, letting you (you the Ubuntu community as a whole, not you Adam Conrad) manage it on your own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783455 Title: tlp shouldn't recommend linux-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1783455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724862] Re: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
*** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724862 Title: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1724862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734518] Re: acpi-call-dkms fails to build on HWE kernel
*** 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 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734518 Title: acpi-call-dkms fails to build on HWE kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1734518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742641] Re: During software update: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
*** 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 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742641 Title: During software update: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1742641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742475] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
*** 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 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742475 Title: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1742475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724862] Re: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
*** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724862 Title: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1724862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774899] Re: acpi-call-dkms (not installed): acpi-call kernel module failed to build
*** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774899 Title: acpi-call-dkms (not installed): acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1774899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503099] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1503099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772382] Re: TLP does not configure tpacpi-bat
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772382 Title: TLP does not configure tpacpi-bat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1772382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759255] Re: package tlp-rdw 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1
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: files list file for package 'tlp-rdw' missing; assuming package has no files currently installed It seems that something went wrong during your upgrade (not necessarily on TLP's behalf) and from experience, the "--force-yes" or "--assume- yes" in DpkgHistoryLog.txt make me suspect that after that, you blindly copied command lines found on the internet to try to force the installation of some packages. Clearly, your system is now broken, that's why I need to know exactly what you did, in order to check if it's really TLP's fault. -- 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 install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1759255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759255] Re: package tlp-rdw 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1
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. https://bugs.launchpad.net/bugs/1759255 Title: package tlp-rdw 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1759255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759255] Re: package tlp-rdw 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1
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 install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1759255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759255] Re: package tlp-rdw 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759255 Title: package tlp-rdw 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1759255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759255] Re: package tlp-rdw 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1
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 0.9-3 failed to install/upgrade: new tlp-rdw package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1759255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758798] Re: tlp recommends smartmontools which then pulls in Postfix mailserver
** 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 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1758798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758798] Re: tlp recommends smartmontools which then pulls in Postfix mailserver
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1758798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758798] Re: tlp recommends smartmontools which then pulls in Postfix mailserver
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 smartmontools which then pulls in Postfix mailserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tlp/+bug/1758798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758798] Re: tlp recommends smartmontools which then pulls in Postfix mailserver
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 try to do it this week, but I don't promise anything. About germinate, I don't know at all what is it, but looking at the link you provided, I guess it's a tool which points to why each package was pulled in. mailx being a virtual package, like default-mta or mail- transport-agent, it may explain why none of them is shown in the output. Also, thanks a lot for taking care of filing the bugs against smartmontools and postfix - I intended to do it, but given the workload I currently have, it takes a weight off my shoulders. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1758798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758798] Re: tlp recommends smartmontools which then pulls in Postfix mailserver
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 provided by exim4-daemon-light mail-transport-agent is a virtual package provided by all SMTP servers in Debian (both full-blown and fake ones like ssmtp or nullmailer) Knowing this, I don't understand how APT could have chosen Postfix to resolve this chain of dependency. Whichever one of bsd-mailx or mailutils was chosen to satisfy smartmontools dependencies, APT's first choice should have been exim4-daemon-light, not postfix. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1758798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758798] Re: tlp recommends smartmontools which then pulls in Postfix mailserver
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 to suggests. 2/ smartmontools actually contains two pieces of software, smartctl and smartd. The first one is a command-line utility, the second is a daemon. Only the daemon actually needs the mailx command to alert the administrator in case of problems. Maybe a bug with severity "wishlist" should be filed against smartmontools in Debian asking to separate smartctl and smartd in their own packages. 3/ The default configuration of Postfix in Debian, if you don't answer debconf questions, is "Internet site". I never understood why, the logical choice (from a security point of view) should be "Local only", where the daemon binds to the loopback interface only. Again, maybe a bug with severity "wishlist" should be filed against postfix asking to change the default answer to the main_mailer_type question. -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1758798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700625] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
- 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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1700625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503099] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
- 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1503099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742641] Re: During software update: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742641 Title: During software update: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1742641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742475] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742475 Title: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1742475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734518] Re: acpi-call-dkms fails to build on HWE kernel
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734518 Title: acpi-call-dkms fails to build on HWE kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1734518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724862] Re: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
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 to release an updated version of the package including the patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724862 Title: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1724862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, sorry for the late answer, I'm quite busy these days. Le 21/08/2017 à 13:27, Wolf Rogner a écrit : > Mind: deinstalling eliminates a set of issues (see above). Which issues did it eliminate exactly ? From what I can tell: > higher CPU load (not only in Firefox) It's the first time I hear about this one. > not fully charged battery on laptops (stops at 94% of capacity) This may be related to battery charge thresholds, but the default TLP configuration doesn't change them. Some questions to narrow down the problem : - - Which model of ThinkPad do you have ? - - Did you change those thresholds by other means ? Please check /etc/sysfs.conf and snippets under /etc/sysfs.d - - Do you dual boot Windows on this machine, and have Lenovo power manager installed in it ? > kicks in fans arbitrarily (even when CPU temp is below average > normal state) I'm pretty sure it has nothing to do with TLP. I have this problem on two distinct X200 and uninstalling TLP didn't fix it. Unfortunately I noticed this problem after a long time and I'm not sure what change on my machines caused it, it may be a kernel upgrade (I noticed it after upgrading to Debian Jessie). I also noticed that, when unplugged from AC, after a while, the fan calms down, but the problem comes back after re-plugging. If you can tell me more I'm interested. > terminates bluetooth connections every 2 mins This is a known problem and it's more or less fixed by version 1.0 of TLP (which I had uploaded by my sponsor in Debian Unstable, but unfortunately didn't make it in Artful before the sync freeze). When it will be synced to Ubuntu, you may request a backport (but don't take my word on that, I'm not sure of how the process works for Ubuntu, the package may need to hit a stable release first; documentation I found on the web only states "from within the Ubuntu repositories"). In the meantime, you could use packages from upstream's PPA. In any case, you'll have to set the new option USB_BLACKLIST_BTUSB to 1. > terminates network connections every 2-5 mins I'm really not sure about this one. Maybe change the value of PCIE_ASPM_ON_BAT or various RUNTIME_PM* options ? > Maybe you check whether machine is a thinkpad and only install > then. No. TLP works on all kind of laptops. The only ThinkPad-specific features are the ones related to battery (dis)charge thresholds. Regards, - -- Raphaël Halimi -BEGIN PGP SIGNATURE- iQKtBAEBCgCXFiEEb6lOxdKMjWi+eSrvTZn2ZgpZgnsFAlnD0S9fFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDZG QTk0RUM1RDI4QzhENjhCRTc5MkFFRjREOTlGNjY2MEE1OTgyN0IZHHJhcGhhZWwu aGFsaW1pQGdtYWlsLmNvbQAKCRBNmfZmClmCe2bXD/4rAxDLRZKtKF/zCvxj0dEL IrIce5l4VQT7hdBchXA/Hbt5Kr1Dl8ohB8oHmGnt9EqhKIluNeoqQNE8QrifKaYk U+99s3MKJMcwHEtTXxQkxfZcVUHaoNF6EqZxRl0DW1vJCPcxiUIPsEjZoN82mHCZ iF3rzD6gfOYNfJbGhuuo8QVWhnZvnoMK9xyaV6aH7wd37XrGONlKn/695sIm08LG qduYCcE2AZ6ZkJm7qLJ/cpuSdmC1+65hH0XjJPQ+rNMHU6lnA23xoQ55ycRHZaYq RR0frGHDV8/Ttk5urbZ6mz/v4BjzIuTh6SK+tIpV0Ex+6+yxoFbClXFTNWBuERPW RxPaA/SHnEEC/ZogekEzqp5eiomqPfb/BNJ70QDh0s7iHwS2YwE+c7tZOjxNJDyS gFwJfylyp6xeisptY+2gWoOWK2U8nyB60opdveVu4HLr1H25XX+sMg7hzfrMEaXS n0/V7g3UkxOerPCVNB2B/jXSFOaBe1LpHdzLjTSgtICryTDoyMyLMyMHda9JVD63 YuexvvrBEWh9kUWGOFYTSYcsUlby/e24It8DnWjAHTSMX+bv28UOO8KNC25h72u1 K/Y4TLcX5whnJnPLuXYBuCuci65Lf8nvEneEjYJ9aVkVE+rwMtwR2lUBvv/XozSt xPWLv8OsqvF0wTRkIngQUg== =WUZx -END PGP SIGNATURE- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711382 Title: Slow Firefox performance and high CPU load when tlp is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed
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. https://bugs.launchpad.net/bugs/1711382 Title: Slow Firefox performance and high CPU load when tlp is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705678] Re: acpi-call-dkms: module fails to build beginning with mainline kernel 4.12.x
*** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705678 Title: acpi-call-dkms: module fails to build beginning with mainline kernel 4.12.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1705678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700625] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
Hi, The problem doesn't come from my package but from the option "-fstack- protector-strong" which isn't understood by your version of gcc. Where does this option come from ? Why is it passed to gcc ? It's not present anywhere in my source package. Can you remove it and try again 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1700625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503099] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
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 | grep Recommends" ? -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1503099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503099] Re: acpi-call-dkms 1.1.0-2: acpi-call kernel module failed to build
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 installed, 0 to remove and 0 not upgraded. Need to get 12.9 kB of archives. After this operation, 73.7 kB of additional disk space will be used. Get:1 http://ftp.fr.debian.org/debian sid/main amd64 acpi-call-dkms all 1.1.0-2 [12.9 kB] Fetched 12.9 kB in 0s (89.2 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously unselected package acpi-call-dkms. (Reading database ... 242484 files and directories currently installed.) Preparing to unpack .../acpi-call-dkms_1.1.0-2_all.deb ... Unpacking acpi-call-dkms (1.1.0-2) ... Setting up acpi-call-dkms (1.1.0-2) ... Loading new acpi-call-1.1.0 DKMS files... First Installation: checking all kernels... Building only for 4.4.0-1-amd64 Building initial module for 4.4.0-1-amd64 Done. acpi_call: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-1-amd64/updates/dkms/ depmod DKMS: install completed. Could someone please post some more information on this one ? Thanks. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1503099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 755898] Re: gnome-keyring-daemon not available in apps started from global shortcuts
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 keybindings daemon) and this is not fixed yet in Oneiric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/755898 Title: gnome-keyring-daemon not available in apps started from global shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/755898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 755898] Re: gnome-keyring-daemon not available in apps started from global shortcuts
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 right environment variables and thus uses gnome-keyring correctly. On the other hand, if I define a new custom keybinding to launch XTerm, it's launched with the wrong environment variables and doesn't use gnome-keyring, asking for my ssh private key's passphrase everytime I want to login to a remote host. Programs launched with the default keybindings and the ones launched with custom keybindings still end up with different environment variables, so the problem isn't fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/755898 Title: gnome-keyring-daemon not available in apps started from global shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/755898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 242638] Re: Thinkpad freezes when undocking from Ultrabay if CD/DVD-ROM drive has not been deleted manually
*** 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 https://bugs.launchpad.net/bugs/242638 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 369131] Re: IBM X40 & Ultrabase X4 eject freezes in Jaunty
*** 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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 292144] Re: can't resume x60s if suspend after undock from ultrabase x6
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" http://launchpadlibrarian.net/30687161/udev-dock_0.2_all.deb -- can't resume x60s if suspend after undock from ultrabase x6 https://bugs.launchpad.net/bugs/292144 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 369131] Re: IBM X40 & Ultrabase X4 eject freezes in Jaunty
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 driver). It's available at my PPA: https://launchpad.net/~raph/+archive/ppa Its main component is a shell script that handles docking and undocking events, as well as bay's ejection or insertion (all are handled by the dock driver as of 2.6.28). It detects the type of dock triggering the event (ata_bay or dock_station) and try to unmount and unregister the device before undocking. As of right now, it doesn't detect the type of device present in a bay (/sys/devices/platform/dock.?/block is missing, maybe because the dock driver is loaded into memory after block devices drivers, see at the end of the dock driver source), so this could be considered dirty because you have to specify in the config file the type of device you're using (defaults to /dev/sr0 on SCSI host 1:0:0:0). It seems that it's the best we can do in Jaunty without recompiling the kernel. Another problem is the undock button. By default the dock driver disconnects immediately any device connected to the dock triggering the event, before the script could be run; to change this, we have to pass an option to the dock driver, but in Jaunty it's built-in the kernel, so you have to pass it to the kernel via the bootloader. If you use grub, my package can add "dock.immediate_undock=0" to your config file, in order to allow the use of the UltraBase eject button (similar code for lilo welcome). And, last but not the least, it detects if you have a ThinkPad and if so, it binds the eject hotkey (Fn-F9) by adding a file to ACPI events config directory, so you can use the hotkey as well as the eject button. Hope it helps. ** Attachment added: "udev-dock_0.2_all.deb" http://launchpadlibrarian.net/30687043/udev-dock_0.2_all.deb -- IBM X40 & Ultrabase X4 eject freezes in Jaunty https://bugs.launchpad.net/bugs/369131 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 242638] Re: Thinkpad freezes when undocking from Ultrabay if CD/DVD-ROM drive has not been deleted manually
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 driver). It's available at my PPA: https://launchpad.net/~raph/+archive/ppa Its main component is a shell script that handles docking and undocking events, as well as bay's ejection or insertion (all are handled by the dock driver as of 2.6.28). It detects the type of dock triggering the event (ata_bay or dock_station) and try to unmount and unregister the device before undocking. As of right now, it doesn't detect the type of device present in a bay (/sys/devices/platform/dock.?/block is missing, maybe because the dock driver is loaded into memory after block devices drivers, see at the end of the dock driver source), so this could be considered dirty because you have to specify in the config file the type of device you're using (defaults to /dev/sr0 on SCSI host 1:0:0:0). It seems that it's the best we can do in Jaunty without recompiling the kernel. Another problem is the undock button. By default the dock driver disconnects immediately any device connected to the dock triggering the event, before the script could be run; to change this, we have to pass an option to the dock driver, but in Jaunty it's built-in the kernel, so you have to pass it to the kernel via the bootloader. If you use grub, my package can add "dock.immediate_undock=0" to your config file, in order to allow the use of the UltraBase eject button (similar code for lilo welcome). And, last but not the least, it detects if you have a ThinkPad and if so, it binds the eject hotkey (Fn-F9) by adding a file to ACPI events config directory, so you can use the hotkey as well as the eject button. Hope it helps. ** Attachment added: "udev-dock_0.2_all.deb" http://launchpadlibrarian.net/30687037/udev-dock_0.2_all.deb -- Thinkpad freezes when undocking from Ultrabay if CD/DVD-ROM drive has not been deleted manually https://bugs.launchpad.net/bugs/242638 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 189185] Re: Thinkpad X61 hangs when removing from 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 driver). It's available at my PPA: https://launchpad.net/~raph/+archive/ppa Its main component is a shell script that handles docking and undocking events, as well as bay's ejection or insertion (all are handled by the dock driver as of 2.6.28). It detects the type of dock triggering the event (ata_bay or dock_station) and try to unmount and unregister the device before undocking. As of right now, it doesn't detect the type of device present in a bay (/sys/devices/platform/dock.?/block is missing, maybe because the dock driver is loaded into memory after block devices drivers, see at the end of the dock driver source), so this could be considered dirty because you have to specify in the config file the type of device you're using (defaults to /dev/sr0 on SCSI host 1:0:0:0). It seems that it's the best we can do in Jaunty without recompiling the kernel. Another problem is the undock button. By default the dock driver disconnects immediately any device connected to the dock triggering the event, before the script could be run; to change this, we have to pass an option to the dock driver, but in Jaunty it's built-in the kernel, so you have to pass it to the kernel via the bootloader. If you use grub, my package can add "dock.immediate_undock=0" to your config file, in order to allow the use of the UltraBase eject button (similar code for lilo welcome). And, last but not the least, it detects if you have a ThinkPad and if so, it binds the eject hotkey (Fn-F9) by adding a file to ACPI events config directory, so you can use the hotkey as well as the eject button. Hope it helps. ** Attachment added: "udev-dock_0.2_all.deb" http://launchpadlibrarian.net/30687014/udev-dock_0.2_all.deb -- Thinkpad X61 hangs when removing from dock https://bugs.launchpad.net/bugs/189185 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
