Re: Bug#1000905: base-files: Internal laptop keyboard not recognized and not working

2021-12-11 Thread Santiago Vila
reassign 1000905 src:linux retitle 1000905 Internal laptop keyboard not recognized and not working thanks Hi. I'm reassigning this bug (using bcc) because it was filed against base-files but it's more a bug in Linux. Thanks.

Bug#931341: linux-image-4.19.0-5-cloud-amd64 does not have /dev/rtc, used by GCE images

2019-07-02 Thread Santiago Vila
Package: linux-image-4.19.0-5-cloud-amd64 Version: 4.19.37-5 Dear maintainer: On a virtual machine running buster on Google Compute Engine, where this kernel package is the default, I get the following messages: google_clock_skew_daemon[1539]: hwclock: Cannot access the Hardware Clock via any

Bug#901712: linux: FTBFS when built with dpkg-buildpackage -A (needs bison)

2018-06-17 Thread Santiago Vila
Package: src:linux Version: 4.16.12-1 Severity: serious Hello Ben. I tried to build this package with "dpkg-buildpackage -A" and it failed in this way: [...] /bin/sh: 1: bison: not found scripts/Makefile.lib:217: recipe for target 'scripts/kconfig/zconf.tab.c' failed make[5]: ***

Bug#883980: base-files: After updating to 9.3, Screen Sporadically Goes Blank

2017-12-09 Thread Santiago Vila
reassign 883980 chromium,linux thanks On Sat, Dec 09, 2017 at 05:45:33PM -0600, Hanlyu Sarang wrote: > Package: base-files > Version: 9.9+deb9u3 > Severity: important > > Dear Maintainer, > > I upgraded to Debian 9.3 today, using aptitude update/aptitude upgrade, then > rebooted the computer.

Re: Uploading linux (4.9.2-1)

2017-01-10 Thread Santiago Vila
On Tue, Jan 10, 2017 at 06:23:27PM +, Ben Hutchings wrote: > On Tue, 2017-01-10 at 18:05 +0000, Santiago Vila wrote: > > On Tue, Jan 10, 2017 at 05:04:50PM +, Ben Hutchings wrote: > > > I intend to upload linux version 4.9.2-1 to unstable tomorrow > > > (We

Re: Uploading linux (4.9.2-1)

2017-01-10 Thread Santiago Vila
On Tue, Jan 10, 2017 at 05:04:50PM +, Ben Hutchings wrote: > I intend to upload linux version 4.9.2-1 to unstable tomorrow > (Wednesday). As this is a new upstream version, there is of course an > ABI bump. Hi. (Sorry if this is already reported, last time I looked at the bug page I didn't

Re: Uploading linux (4.9.2-1)

2017-01-10 Thread Santiago Vila
On Tue, Jan 10, 2017 at 05:04:50PM +, Ben Hutchings wrote: > I intend to upload linux version 4.9.2-1 to unstable tomorrow > (Wednesday). As this is a new upstream version, there is of course an > ABI bump. Hi. (Sorry if this is already reported, last time I looked at the bug page it was

Bug#844446: linux-image-4.8.0-1-amd64: Fails to boot on qemu/kvm

2016-11-17 Thread Santiago Vila
Hi. The following workaround worked for me: Try setting the CPU type to be a "simple old CPU" without a lot of features. For example, the following change fixed the problem in my case: --- a/libvirt/qemu/machine.xml +++ b/libvirt/qemu/machine.xml @@ -19,8 +19,8 @@ or other application using the

Bug#841007: linux-image-4.8.0-rc8-amd64-unsigned: Shutdown when pressing any key on Asus E200 HA

2016-11-16 Thread Santiago Vila
forcemerge 833016 841007 thanks Hi. You will see that both bugs belong to the "src:linux" package, so it's better not to file duplicates. To tell the BTS that a certain version has the bug, we have a "found" command. I'm merging the bugs with this message. BTW: There is a 4.9-rc version in

Bug#844446: linux-image-4.8.0-1-amd64: Fails to boot on qemu/kvm

2016-11-16 Thread Santiago Vila
I can reproduce this as well. Also running a stretch VM on a jessie KVM/qemu/libvirt host. My KVM host is a i5-6400 running linux 3.16.36-1+deb8u2. Thanks.

Bug#842786: numix-icon-theme: FTBFS (dpkg-source can't extract orig tarball)

2016-11-01 Thread Santiago Vila
Package: src:numix-icon-theme Severity: serious Dear maintainer: I tried to build "numix-icon-theme" in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Bug#825423: supermin + sbuild + linux-image = broken chroot

2016-06-04 Thread Santiago Vila
On Sat, Jun 04, 2016 at 04:33:58PM +0100, Ben Hutchings wrote: > > You can use the command ischroot from the debianutils package. > > Why would I want to add a dependency on that? [...] You really wouldn't, because debianutils is essential.

Bug#825423: [buildd-tools-devel] Bug#825423: supermin + sbuild + linux-image = broken chroot

2016-05-26 Thread Santiago Vila
severity 825423 important thanks On Thu, May 26, 2016 at 10:34:12PM +0200, Johannes Schauer wrote: > this seems to suggest that you are not using a throw-away chroot but > a persistent one. Could you provide details about your chroot setup? > Are you not using schroot? I am using schroot. This

Bug#825423: supermin + sbuild + linux-image = broken chroot

2016-05-26 Thread Santiago Vila
Package: src:linux,src:supermin,src:sbuild Severity: serious Justification: Breaks other packages X-Debbugs-Cc: sanv...@debian.org Dear maintainers: I think this is a bug in linux, but I'm not 100% sure. Please do agree with the other maintainers on which package is to blame. I'm building

Bug#823107: linux: make deb-pkg fails: No rule to make target 'debian/certs/b...@debian.org.cert.pem')

2016-04-30 Thread Santiago Vila
On Sat, Apr 30, 2016 at 11:41:09PM +0200, Ben Hutchings wrote: > > > Yes, you must do that.  Your custom kernel configuration should be > > > based on the appropriate file provided in linux-source-4.5.  These have > > > the CONFIG_MODULE_SIG_ALL, CONFIG_MODULE_SIG_KEY and > > >

Bug#823107: linux: make deb-pkg fails: No rule to make target 'debian/certs/b...@debian.org.cert.pem')

2016-04-30 Thread Santiago Vila
On Sat, Apr 30, 2016 at 08:51:25PM +, Debian Bug Tracking System wrote: > You wrote: > [...] > > Should I remove CONFIG_SYSTEM_TRUSTED_KEYS from .config before building > > the kernel? I hope not. > [...] > > Yes, you must do that. Your custom kernel configuration should be > based on the

Bug#823107: linux: make deb-pkg fails: No rule to make target 'debian/certs/b...@debian.org.cert.pem'

2016-04-30 Thread Santiago Vila
Package: src:linux Version: 4.5.2-1 Dear maintainer: I merged the output of "lsmod" in two different virtual machines running stretch/sid to create a minimal kernel which works on both. The combined file is attached as "lsmod.txt". Then I created a .config file by executing this script:

Bug#805949: linux-tools: FTBFS when built with dpkg-buildpackage -A (no binary artifacts)

2015-11-24 Thread Santiago Vila
Package: src:linux-tools Version: 4.2-2 User: sanv...@debian.org Usertags: binary-indep Severity: important Dear maintainer: I tried to build this package with "dpkg-buildpackage -A" (i.e. only architecture-independent packages), and it failed:

Bug#787561: modules virtio_net and virtio_pci are allowed to be removed but they should not be

2015-06-02 Thread Santiago Vila
Package: linux-image-3.16.0-4-amd64 Version: 3.16.7-ckt9-3~deb8u1 Severity: important Note: I'm not sure which package to blame here. I chose the kernel because I believe the kernel knows better than anybody else which modules are suitable to be unloaded and which modules are not, but this could

Bug#765750: initramfs-tools: should probably recreate initrd after installing

2014-10-17 Thread Santiago Vila
Package: initramfs-tools Version: 0.116 When I install dracut, a new initrd is generated automatically using dracut. If I install initramfs-tools again, dracut is removed but this time a new initrd (generated by initramfs-tools) is not generated. I see a lot of danger here. Either initrds are

Bug#494374: linux-image-2.6.26-1-686: Insert key does not work on Thinkpad R60

2008-09-25 Thread Santiago Vila
There is now a patch available here: The patch comes from http://bugzilla.kernel.org/show_bug.cgi?id=11242 which I'm attaching to this report. My machine (Mac Mini powerpc with USB keyboard) had the same problem and the patch fixes it.From 252b7805384d12c6857b8bebf1a373e327afbec9 Mon Sep 17

Bug#494374: Insert key does not work

2008-09-25 Thread Santiago Vila
severity 494374 serious tags 494374 + upstream tags 494374 + patch thanks While we are at it, I consider this bug important enough to delay the release of lenny until it's fixed. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Bug#498645: initramfs-tools: Boot takes three minutes to finish (!)

2008-09-17 Thread Santiago Vila
On Fri, 12 Sep 2008, maximilian attems wrote: On Fri, Sep 12, 2008 at 04:19:24PM +0200, Santiago Vila wrote: linux-image-2.6.18-6-686 version 2.6.18.dfsg.1-22etch2 works ok linux-image-2.6.20-1-686 version 2.6.20-3 does not work linux-image-2.6.26-1-686 version 2.6.26-5

Bug#498645: initramfs-tools: Boot takes three minutes to finish (!)

2008-09-12 Thread Santiago Vila
On Thu, 11 Sep 2008, maximilian attems wrote: To summarize: No matter how faulty my hardware might be (the boot never took so long with etch), I don't think it is reasonable at all that a user has to do this in order for the boot process not to take more than three minutes. Maybe

Bug#498645: initramfs-tools: Boot takes three minutes to finish (!)

2008-09-12 Thread Santiago Vila
On Thu, 11 Sep 2008, maximilian attems wrote: this looks more like a kernel bug, One detail I've just noticed: After the boot, the eject button of /dev/hdc does not work at all. This didn't happen with etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Bug#498645: initramfs-tools: Boot takes three minutes to finish (!)

2008-09-12 Thread Santiago Vila
On Fri, 12 Sep 2008, maximilian attems wrote: reassign 498645 linux-2.6 stop On Fri, Sep 12, 2008 at 02:25:21PM +0200, Santiago Vila wrote: On Thu, 11 Sep 2008, maximilian attems wrote: this looks more like a kernel bug, One detail I've just noticed: After the boot, the eject

Bug#498645: initramfs-tools: Boot takes three minutes to finish (!)

2008-09-11 Thread Santiago Vila
Package: initramfs-tools Version: 0.92i After installing a lenny system today, it happened that the boot process takes more than 3 minutes to finish. Needless to say, I first believed it was frozen and didn't work at all. I was lucky to discover (by accident) that it was a very long waiting time

Bug#401163: kobject_add failed for audio with -EEXIST

2006-12-01 Thread Santiago Vila
Package: linux-image-2.6.18-3-k7 Version: 2.6.18-6 I have a system here which shows this message when booting: kobject_add failed for audio with -EEXIST, don't try to register things with the same name in the same directory. [c01b8d8a] kobject_add+0x146/0x16c [c0213a6e]

Bug#395110: linux-image-2.6.18-1-powerpc: uninstallable

2006-10-29 Thread Santiago Vila
Same problem here: mac:~# apt-get install linux-image-2.6-powerpc Reading package lists... Done Building dependency tree... Done linux-image-2.6-powerpc is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. Need to get 0B

Bug#395110: linux-image-2.6.18-1-powerpc: uninstallable

2006-10-29 Thread Santiago Vila
On Sun, 29 Oct 2006, Sven Luther wrote: [ snipped paragraph about Manoj ] Quoting Julian Gilbey in the logs for this bug: According to Manoj in the logs to bug#394661, which was blocking this bug and has since been closed, the bug was fixed in kernel-package 10.063. So I guess that all

Bug#395110: linux-image-2.6.18-1-powerpc: uninstallable

2006-10-29 Thread Santiago Vila
On Sun, 29 Oct 2006, Sven Luther wrote: We really need a better way to handle bug reports which affect more than one package, since cloning and merging is not the best way to go for those. In the past, the BTS allowed things like this: Package: foo, bar I'm not sure if this is still