Bug#453861: acpi-support: Remove /etc/acpi/start.d/60-asus-wireless-led.sh

Package: acpi-support Version: 0.103-5 Followup-For: Bug #453861 I forget to remove this file in previous patch /etc/acpi/start.d/60-asus-wireless-led.sh In fact, rf_kill and led are always coherent, you don't need this check. More over, isAnyWirelessPoweredOn from /usr/share/acpi-support/stat

Bug#453861: acpi-support: A working patch

Package: acpi-support Version: 0.103-5 Followup-For: Bug #453861 Ok, so as I said, I don't really need this package because it's work without and I don't understand why... For working, with acpid, asus_acpi must be loaded. It can be write in a README. In patch, due to a missing file /power/s

Bug#453861: acpi-support: double "" in asus-wireless.sh cause trouble

Package: acpi-support Version: 0.103-5 Followup-For: Bug #453861 I have same problem and it can be solve fast. It's only due to double " in asus-wireless.sh script. Just apply this patch and you can close bug. --- etc/acpi/asus-wireless.sh~ 2007-12-13 20:35:00.0 +0100 +++ etc/acpi/asus

Bug#401892: egroupware-core: "Checking PEAR is installed*: False" but package php-pear was intalled

Package: egroupware-core Version: 1.2-105.dfsg-4 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Have this message when I check the install. Checking PEAR is installed*: False PEAR is needed by SyncML or the iCal import+export of calendar.*

Bug#366243: nvidia-settings: received an X Window System error

Package: nvidia-settings Version: 1.0+20051122-1 Followup-For: Bug #366243 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since I've done the update of nvidia-glx-1.0.7174-3 to 1.0.8756-2 (same for driver), this message appears. [EMAIL PROTECTED]:~$ nvidia-settings The program 'nvidia-settings'

Bug#353700: libarts1c2a: You can close this bug.

Package: libarts1c2a Version: 1.5.1-1 Followup-For: Bug #353700 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This bug was provide by alsa-source package. It's work fine now with 1.0.10+1.0.11rc3-1 version of alsa. Before I used the 1.0.10-3 version. So you can close this bug. - -- System

Bug#353700: libarts1c2a: "Bad page state at free_hot_cold_page" message with kernel 2.6.15-1-k7

Package: libarts1c2a Version: 1.5.1-1 Severity: normal With the kernel 2.6.15-1-k7, I have this message in /var/log/kern.log (same in /var/log/message): Feb 20 11:54:49 woodswolf kernel: Bad page state at free_hot_cold_page (in process 'artsd', page c16dd020) Feb 20 11:54:49 woodswolf kernel: fl

Bug#317832: console-tools: After boot, I must re-run console-screen.sh script for having my settings

Package: console-tools Version: 1:0.2.3dbs-56 Severity: normal At the boot, if I log into a console tty, I dont have my fonts'settings. The script console-screen.sh would be succesfully apply because wolf001:/home/carl# ls -l /etc/rcS.d/S48console-screen.sh lrwxrwxrwx 1 root root 27 2005-05-09 1

Bug#317829: kernel-source-2.6.8: Loading of vesafb fail at the boot time

Package: kernel-source-2.6.8 Severity: normal -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'stable'), (33, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Ke