Bug#629470: HP ScanJet G2710 very light picture wrong gamma usage

> HP ScanJet G2710 scanner is recognized but picture quality is worst. Same on my System. The standalone has 1.0 as default for gamma, the sane-driver 2.2. I could fix it by patching hp3000_sane.c. *** hp3900-series_0.12/src/hp3900-series/hp3900_sane.c 2011-10-20 21:45:11.650426572 +0200 ---

Bug#484057: lvm2: df wrong (used+free > total)

Package: lvm2 Version: 2.02.35-1 Severity: normal The total amount displayed by 'df' is bigger than the used+free size: # df /dev/mapper/media-media 98500188 90164464 3332460 97% /mnt/media Also gtkdiskfree report the same and tells me that there is plenty of space, wh

Bug#474651: debootstrap: W: Failure trying to run: chroot /sid

> Sounds like either a problem with sid at the moment or something wrong > with your "/sid" target. Either way there's not enough information in > this report to diagnose the problem you're having, so report closed > with this mail. I am disapointed. I want to help, finding errors and all I get

Bug#474651: debootstrap: W: Failure trying to run: chroot /sid dpkg --force-depends ...

Package: debootstrap Version: 1.0.8 Severity: normal debootstrap not completet in faechroot-mode (all others worked before). $ fakeroot -s fakechroot.save fakechroot /usr/sbin/debootstrap --variant=fakechroot \ sid /sid http://ftp.ch.debian.org/debian/ I: Retrieving Release I: Retrieving Pack

Bug#474500: uptimed: /var/spool/uptimed/records deleted after power fail

Hallo Thibaut Thanx for the fast answer. > > Is the file opened at start and closed on normal shutdown > > (whith start-stop-daemon)? > No. The records file is only open when necessary. The daemon doesn't > write directly to that file either. It writes to a temporary file and > then moves it i

Bug#474500: uptimed: /var/spool/uptimed/records deleted after power fail

Package: uptimed Version: 1:0.3.10-3 Severity: normal After more than 200 days running, the server power was shut off. No big problem. After booting /var/spool/uptimed/records was gone (or overwritten) and only the current boot is now visible. Is the file opened at start and closed on normal shut

Bug#474377: mimms 3.0-1 needs debhelper 6 to compile (dh_clean: Sorry, but...)

Package: mimms Version: 3.0-1 Severity: serious Justification: no longer builds from source I use etch and tried to build mimms from source debhelper 6 seems to bee needed, but no dependency is displayed. I tried to build debhelper, but then I have to build man-db, dpkg-dev, dpkg, too. #dp

Bug#471360: quiet/stdout: time (-t) ignored

Package: mimms Version: 2.0.1-1 Severity: normal The time is not used, if mimms is started in quiet mode or stdout mode. Patch included. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (950, 'stable'), (200, 'proposed-updates'), (200, 'stable'), (50, 'testing') Arc

Bug#282800: 2.6.8-2-686 not working

Hallo No answer since Mon, 24 Jan 2005 :-( It's still not possible to burn with sarge standard! I work with STABLE and don't like to reboot just to burn! >cdrecord: Drive does not support TAO recording. >cdrecord: Illegal write mode for this drive. #cat /proc/cmdline root=/dev/hda3 ro noapi

Bug#329012: kcmlinuz: Kernel 2.6 not supported

Package: kcmlinuz Version: 4:3.3.2-1 Severity: important Message "Linux-Kernel der Versions 2.5 und höher werden derzeit nicht unterstützt" appears. Kernel 2.5 and above is not supported. Someone should change this or remove the package, because most people use 2.6. -- System Information: Debi

Bug#312393: [Logcheck-devel] Bug#312393: logcheck: error creating lockfile.lock

> > ls -l /etc/logcheck > > total 44 > > drwxr-s--- 2 root logcheck 4096 Jun 7 20:51 cracking.d > > . > looks fine indeed. > strange permissions are set on the same step almost. > did the logcheck upgrade have any notable errors? Don't remember. I had problems with the webmin upgrade (woody->sar

Bug#312393: [Logcheck-devel] Bug#312393: logcheck: error creating lockfile.lock

> please send us the output of > ls -l /etc/logcheck ls -l /etc/logcheck total 44 drwxr-s--- 2 root logcheck 4096 Jun 7 20:51 cracking.d drwxr-xr-x 2 root root 4096 Jun 7 20:51 cracking.ignore.d -rw-r--r-- 1 root logcheck 180 Apr 19 2004 header.txt drwxr-xr-x 2 root logcheck 4096 Mar 2

Bug#312393: logcheck: error creating lockfile.lock

Package: logcheck Version: 1.2.39 Severity: important Today I upgraded my server from woody to sarge. After repeated installing and uninstalling of webmin (where logcheck is used), I ended up with a version that does not work. The directory for the lockfile.lock is not writable for the user logc

Bug#312082: netselect-apt: fails the ftp support

Package: netselect-apt Version: 0.3.ds1-4 Severity: important Tags: patch The option -f for ftp does not work! *** PATCH *** --- netselect-apt.orig 2005-06-05 13:31:06.0 +0200 +++ netselect-apt 2005-06-05 13:49:43.0 +0200 @@ -42,9 +42,10 @@ run_netselect() { SEAR

Bug#292328: kernel-image-2.6.10-1-686

See also Seems to be a problem in initrd of kernel 2.6.10 Same Error messages on my Desktop and Laptop. Desktop: :00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE

Bug#282800: 2.6.8-2-686 not working, 2.6.10-1-686

Am Montag, 24. Januar 2005 10.05 schrieb maximilian attems: > please send: > * dmesg + lsmod of working 2.6.10 > * dmesg + lsmod of non working 2.6.8 Cdrecord-Clone 2.01.01a01 (i686-pc-linux-gnu) ... cdrecord: Warning: Running on Linux-2.6.8-2-686 cdrecord: There are unsettled issues with Linux-2.

Bug#291845: Bugs not fixed from 2.6.8

Package: kernel-image-2.6.8-i386 Version: 2.6.8-12 Severity: grave hi Has someone looked at the bugs in kernel-image-2.6.8-1-386 and kernel-image-2.6.8-1-686? Grave functionality bugs - outstanding (1 bug) Important bu

Bug#291846: Bugs not fixed from 2.6.8

Package: kernel-image-2.6.8-2-686 Version: 2.6.8-12 Severity: grave hi Has someone looked at the bugs in kernel-image-2.6.8-1-386 and kernel-image-2.6.8-1-686? Grave functionality bugs - outstanding (1 bug) Important b

Bug#282800: Use Kernel 2.6.10 and it works again

Hallo Nobody I'm disappointed. Nobody has something answerd to my report. I hope Sarge will use 2.610 and not this kernel. With kernel 2.6.10 it works again: kernel-image-2.6.10-1-686=2.6.10-4 cdrecord=4:2.01+01a01-2 Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsu