Package: alsa-utils
Version: 1.0.19-2
Severity: grave
Justification: renders package unusable
The hardware is an "Apple PowerMac G4 Silver"/"PowerMac3,4" 533 MHz with 1.5 GB
RAM.
When the boot process tries to run init.d/alsa-utils it gets several
repetitions of the following error messages:
On mer, 2009-04-29 at 23:16 +0200, Johann Glaser wrote:
> When Evolution is closed by clicking the window's close button, the window
> and all elemets gray out and a constant disk IO activity of several MB per
> second goes on. Investigations have shown that GConf is writing its config
> file /home
On ven, 2009-05-01 at 11:25 +1000, Tim Connors wrote:
> Package: evolution
> Version: 2.24.5-3
> Severity: grave
> Tags: security
> Justification: user security hole
>
> tconn...@denman:~$ l /home/maree/.evolution/mail/local/Sent
> -rw-r--r-- 1 maree maree 118474734 2009-05-01 08:16
> /home/maree
Processing commands for cont...@bugs.debian.org:
> forcemerge 526681 526217
Bug#526681: Custom search folders prevent evolution from quitting
Bug#526217: evolution: Indefinite and Extreme GConf Activity While Closing
Forcibly Merged 526217 526681.
> thanks
Stopping processing here.
Please contac
On sam, 2009-05-02 at 13:09 +0100, Sam Morris wrote:
> Package: evolution
> Version: 2.26.1.1-1
> Severity: grave
> Justification: renders package unusable
[…]
Besides the large backtrace which I don't yet have the time to read and
understand, were you doing something special? Is it 100% reproduc
Am Freitag, 1. Mai 2009 21:53:50 schrieb Daniel Schepler:
> In file included from /usr/include/asm/fcntl.h:1,
> from /usr/include/linux/fcntl.h:4,
> from /usr/include/linux/inotify.h:11,
> from reconfiguration.h:31,
> from control.
and Intel ICH4/AC07 controller in Dell Inspiron laptop. Debian is not
the only distro with this problem, goodle the 'module-alsa-sink.c'
message and get a whole lot of hits from Fedora, Ubuntu, every distro.
Fills up logs and sound drops out every 15 seconds for seconds at a
time.
With or without
Umh, quite weird...
Leonel Nunez dijo [Sun, May 03, 2009 at 05:37:03PM -0600]:
> > Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/bash
> >
> > Versions of packages libcherokee-config0 depends on:
>
-- Forwarded Message --
From: David Miller
The reason this bug happens is because CONFIG_PROM_CONSOLE is enabled
in the kernel.
It unconditionally gets registered as a real console before the Sun
Hypervisor console driver has a chance to register. The kernel takes
whatever rea
Processing commands for cont...@bugs.debian.org:
> unarchive 504721
Bug 504721 [rootskel] Console broken on debian-installer on Sparc LDOM
Unarchived Bug 504721
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adminis
> Package: libcherokee-config0
> Version: 0.99.11-1
> Severity: grave
> Justification: renders package unusable
>
>
> Upgrading the package, I get:
>
> =
> Preparing to replace libcherokee-config0 0.99.11-1 (using
> /libcherokee-config0_0.99.13-1_i386.deb) ...
> Usage: update-python-modules
> Package: libcherokee-config0
> Version: 0.99.11-1
> Severity: grave
> Justification: renders package unusable
>
>
> Upgrading the package, I get:
>
> =
> Preparing to replace libcherokee-config0 0.99.11-1 (using
> /libcherokee-config0_0.99.13-1_i386.deb) ...
> Usage: update-python-modules
After checking, it looks like the .so.0 symlinks is useless. It can
simply be dropped from the 0.12 package, so no declaration of conflict
will be required.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
Source: sysvbanner
Version: 1.0-14
Severity: serious
Hi,
There was an error while trying to autobuild your package:
> Start Time: 20090503-2149
[...]
> Toolchain package versions: libc6-dev_2.9-9 linux-libc-dev_2.6.29-3
> g++-4.3_4.3.3-8 gcc-4.3_4.3.3-8 binutils_2.19.1-1 libstdc++
Processing commands for cont...@bugs.debian.org:
> severity 526215 normal
Bug#526215: evolution: vFolder "Unread" Misses Mails
Severity set to `normal' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrat
severity 526215 normal
thanks
On mer, 2009-04-29 at 23:20 +0200, Johann Glaser wrote:
> Package: evolution
> Version: 2.26.1.1-1
> Severity: grave
> Justification: renders package unusable
Unusable, really? Then please help us to maintain it, because we really
miss time.
--
Yves-Alexis
signatur
Package: yelp
Version: 2.24.0-2
Severity: grave
Justification: renders package unusable
yelp reproducibly crashes on startup. I have recompiled it in pbuilder in order
to have debugging symbols, here is what the output of bug-buddy looks like:
Distribution: Debian squeeze/sid
Gnome Release: 2.26
Your message dated Sun, 03 May 2009 21:22:56 +
with message-id
and subject line Bug#526822: fixed in perl 5.10.0-22
has caused the Debian Bug report #526822,
regarding perl: FTBFS: Archive-Extract test failure due to changed tar behaviour
to be marked as done.
This means that you claim that
to autobuild your package:
> Start Time: 20090503-1852
[...]
> Build-Depends: debhelper (>= 7.0.0), dbs, autoconf, automake1.10, bzip2,
> libelf-dev (>= 0.141), libdw-dev (>= 0.141), libsqlite3-dev,
> texlive-latex-base, texlive-latex-recommended, texlive-latex-ex
Package: libsynopsys0.12
Version: 0.12-1
Severity: serious
Unpacking libsynopsis0.12 (from .../libsynopsis0.12_0.12-1_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libsynopsis0.12_0.12-1_i386.deb
(--unpack):
trying to overwrite `/usr/lib/libSynopsis.so.0', which is also in package
Your message dated Sun, 03 May 2009 21:24:10 +
with message-id
and subject line Bug#524592: fixed in vdr-plugin-skinenigmang 0.1.0-1
has caused the Debian Bug report #524592,
regarding vdr-plugin-skinenigmang_0.0.6-4+b1(mips/unstable): FTBFS on mips.
wrong include path ?
to be marked as done
Package: firestarter
Version: 1.0.3-7
Severity: normal
I tried Davide Prina's method of adding IF= (eth1 for me) to firestarter.sh and
it worked. I then went into Preferences -> Network Settings, and re-set the
"Internet connected device" to eth1. (It was eth1 already, but I clicked the
menu anywa
Package: libcherokee-config0
Version: 0.99.11-1
Severity: grave
Justification: renders package unusable
Upgrading the package, I get:
=
Preparing to replace libcherokee-config0 0.99.11-1 (using
.../libcherokee-config0_0.99.13-1_i386.deb) ...
Usage: update-python-modules [-v] [-c] package_dir
On Sun, May 03, 2009 at 09:36:11PM +0200, Eugeniy Meshcheryakov wrote:
> reassing 526824 libdw-dev
> retitle 526824 libdw-dev: should depend on libdw1
> thanks
>
> Hi Kurt,
>
> I belive this is a bug in your package.
I'm currently building the new version, will be uploaded soon.
I've already se
Processing commands for cont...@bugs.debian.org:
> # Sun May 3 20:03:31 UTC 2009
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: fswebcam
> tags 513575 + pending
Bug#513575: ITP: fswebcam -- Tiny and flexible
package qorganizer
severity 526828 important
tags 526828 +confirmed upstream
thanks
piersont wrote:
> Package: qorganizer
> Version: 3.1.4-1
> Severity: grave
> Justification: causes non-serious data loss
>
> To reproduce the bug :
> You create a new task in a Todo-list and you type characters li
Processing commands for cont...@bugs.debian.org:
> package qorganizer
Ignoring bugs not assigned to: qorganizer
> severity 526828 important
Bug#526828: qorganizer: Some characters like " | " corrupts data when you save
a Todo-List in a text file.
Severity set to `important' from `grave'
> tags
Processing commands for cont...@bugs.debian.org:
> found 526824 0.141-1
Bug#526824: libdw-dev: should depend on libdw1
Bug marked as found in version 0.141-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administ
tags 526379 + moreinfo unreproducible
severity 526379 important
thanks
On Thu, Apr 30, 2009 at 21:36:12 +0200, Noel David Torres Taño wrote:
> It is completely impossible to copy, either using Ctrl-C, Edit->Copy or
> right-mouse->Copy.
All these forms of copying work fine for me with matching gn
Processing commands for cont...@bugs.debian.org:
> reassign 526824 libdw-dev
Bug#526824: libdw-dev: should depend on libdw1
Bug reassigned from package `systemtap' to `libdw-dev'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system ad
Processing commands for cont...@bugs.debian.org:
> tags 526379 + moreinfo unreproducible
Bug#526379: gnumeric does not allow anymore to copy
There were no tags set.
Tags added: moreinfo, unreproducible
> severity 526379 important
Bug#526379: gnumeric does not allow anymore to copy
Severity set to
Processing commands for cont...@bugs.debian.org:
> reassing 526824 libdw-dev
Unknown command or malformed arguments to command.
> retitle 526824 libdw-dev: should depend on libdw1
Bug#526824: systemtap: FTBFS: checking for dwfl_module_getsym in -ldw... no
Changed Bug title to `libdw-dev: should d
There was an error while trying to autobuild your package:
>
> > Start Time: 20090503-1852
>
> [...]
>
> > Build-Depends: debhelper (>= 7.0.0), dbs, autoconf, automake1.10, bzip2,
> > libelf-dev (>= 0.141), libdw-dev (>= 0.141), libsqlite3-dev,
> &g
Package: qorganizer
Version: 3.1.4-1
Severity: grave
Justification: causes non-serious data loss
To reproduce the bug :
You create a new task in a Todo-list and you type characters like " | "
(vertical line or shell's pipe).
You save this list in text file (standard option) or just close it and r
Processing commands for cont...@bugs.debian.org:
> reopen 523024
Bug#523024: nvidia-kernel-legacy-173xx-source: fails to build modules against
2.6.29 linux-headers packages (probably as in #520706)
Bug reopened, originator not changed.
> found 523024 173.14.18-1
Bug#523024: nvidia-kernel-legacy
Source: systemtap
Version: 0.0.20090502-1
Severity: serious
Hi,
There was an error while trying to autobuild your package:
> Start Time: 20090503-1852
[...]
> Build-Depends: debhelper (>= 7.0.0), dbs, autoconf, automake1.10, bzip2,
> libelf-dev (>= 0.141), libdw-dev (>=
Package: nvidia-kernel-legacy-173xx-source
Version: 173.14.18-1
Severity: normal
Compilation with module-assistant with a 2.6.29 kernel fails... Or
let's say doesn't do anything:
[...]
dh_prep
# Build the modules
/usr/bin/make -C . LINUXDIR=/lib/modules/2.6.29-1-amd64/build
KVERREL=2.6.29-1-amd6
Package: perl
Version: 5.10.0-21
Severity: serious
The test suite of perl/5.10.0-21 failed on at least i386 and s390:
# Failed test 'Found correct number of output files'
# at ../lib/Archive/Extract/t/01_Archive-Extract.t line 350.
# got: '3'
# expected: '2'
lib/Archive/Extract/t
Processing commands for cont...@bugs.debian.org:
> forwarded 526806 ne...@suse.de
Bug#526806: mdadm 3 fails to boot, hangs in initrd
Noted your statement that Bug has been forwarded to ne...@suse.de.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bu
I did a clean install of gforge and the reporsitoriy was created.
Maybe it was some thing that I modified without noticing.
you can close this bug.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.d
Package: libportmidi0
Version: 20041117-1
Tha attached patch fixes this bug. It modifies the Makefile to link portmidi
against porttime, and porttime against pthread.
--- a/Makefile
+++ b/Makefile
@@ -36,13 +36,13 @@ current: all
all: $(pmlib) $(ptlib) pm_test/test pm_test/sysex pm_test/midithrea
Your message dated Sun, 03 May 2009 17:47:05 +
with message-id
and subject line Bug#526541: fixed in ladr 0.0.200902a-2
has caused the Debian Bug report #526541,
regarding ladr: FTBFS: Cannot find debian/tmp/usr/lib/lib*.a
to be marked as done.
This means that you claim that the problem has
Package: mdadm
Version: 3.0~devel3-1
Severity: grave
Tags: upstream
With mdadm 3, the initrd hangs after the mdadm hook ran:
Begin: Mounting root file system ... + pre_mountroot
[...]
+ call_scripts
+ [ = y ]
+ /scripts/local-top/mdadm
[...]
Begin: Loading MD modules ...
Success: loaded module r
Processing commands for cont...@bugs.debian.org:
> forcemerge 519112 526753
Bug#519112: pidgin crashes on XMPP sign-on
Bug#526753: pidgin: fails to start: Illegal instruction
Bug#521419: pidgin crash when I'm away from pc
Bug#522171: segfaults on startup
Bug#51: pidgin crashes on startup
Bug#5
Your message dated Sun, 03 May 2009 17:02:13 +
with message-id
and subject line Bug#485726: fixed in xsok 1.02-17
has caused the Debian Bug report #485726,
regarding xsok: FTBFS: Using imake without Build-Depends on xutils-dev
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 03 May 2009 17:02:03 +
with message-id
and subject line Bug#525969: fixed in git-buildpackage 0.4.53
has caused the Debian Bug report #525969,
regarding udev reports the usage of an invalid parameter '-s'
to be marked as done.
This means that you claim that the proble
Processing commands for cont...@bugs.debian.org:
> tag 525969 pending
Bug#525969: udev reports the usage of an invalid parameter '-s'
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Processing commands for cont...@bugs.debian.org:
> close 526785
Bug#526785: CPU-Frequency scaling corrupted
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to forum+deb...@km.mydyn.de
>
End of message, stopping processing here.
P
tag 525969 pending
thanks
Date: Tue Apr 28 19:54:15 2009 +0200
Author: Guido Günther
Commit ID: b772300b698753b336d1e9f37b2e25066537512f
Commit URL:
http://git.debian.org/?p=users/agx/git-buildpackage.git;a=commitdiff;h=b772300b698753b336d1e9f37b2e25066537512f
Patch URL:
http://git.debian.or
Processing commands for cont...@bugs.debian.org:
> close 526782
Bug#526782: CPU-Frequency scaling corrupted
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to forum+deb...@km.mydyn.de
>
End of message, stopping processing here.
P
close 526785
Now i found the real reason for the problem.
The CPU really does not support the scaling because it is disabled.
I found out that the battery of the mainboard is empty and so the settings
where lost!
Bug can be closed.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.de
close 526782
Now i found the real reason for the problem.
The CPU really does not support the scaling because it is disabled.
I found out that the battery of the mainboard is empty and so the settings
where lost!
This nasty messages at boot and using modprobe can be removed by renaming all
the
Your message dated Sun, 03 May 2009 16:02:03 +
with message-id
and subject line Bug#526792: fixed in vsftpd 2.1.1~pre1-2
has caused the Debian Bug report #526792,
regarding vsftpd: some libraries are linked to with hard-coded SONAMEs
to be marked as done.
This means that you claim that the p
r...@pc:# depmod -a
r...@pc:/lib/modules/2.6.26-1-amd64/kernel/arch/x86/kernel/cpu/cpufreq# modprobe
powernow_k8
WARNING: All config files need .conf: /etc/modprobe.d/alsa-base-blacklist, it
will
be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/blacklist-capi
I am analyzing the problem on another PC with nearly identical hardware.
Here the frequency-scaling is (still) working.
r...@pc:# cpufreq-info
cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
Bitte melden Sie Fehler an cpuf...@lists.linux.org.uk.
analysiere CPU 0:
Treiber: powerno
Processing commands for cont...@bugs.debian.org:
> forcemerge 526606 526716
Bug#526606: [debianutils] breaks 64-bit dist-upgrade, no X
Bug#526716: debianutils: tempfile double free abort on any invocation
Bug#526607: tempfile aborts with double free
Bug#526610: tempfile crashes
Forcibly Merged 526
Package: vsftpd
Version: 2.1.1~pre1-1
Severity: serious
From vsftpd-2.1.1~pre1-1/vsf_findlibs.sh:
# Look for libcap (capabilities)
if locate_library /lib/libcap.so.1; then
echo "/lib/libcap.so.1";
else
locate_library /usr/lib/libcap.so && echo "-lcap";
locate_library
Because the reason for the problem is (also) in the package cpufrequtils, i
opened
a corresponding bug there:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526785
Ther are also additional informations.
Is there another possibility to connect this bugs instead of merging them?
I tried merge, bu
Package: cpufrequtils
Version: 004-2
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
I already opened a bug to module-init-tools because the problem is maybe (also)
there.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=526782
When i call
Your message dated Sun, 03 May 2009 16:38:33 +0200
with message-id <49fdac69.8030...@debian.org>
and subject line fixed
has caused the Debian Bug report #523509,
regarding gcj-4.3: FTBFS with libtool 2.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: module-init-tools
Version: 3.7-pre9-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
Hello,
i have found the bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517954
but it
is already closed.
First i also see this nasty messa
This bug is affecting me too, it's preventing exim4 from starting.
Starting MTA:*** glibc detected *** tempfile: double free or corruption
(fasttop): 0x0098f010 ***
=== Backtrace: =
/lib/libc.so.6[0x7f9c6b20a1c8]
/lib/libc.so.6(cfree+0x76)[0x7f9c6b20bd06]
tempfile[0x400d0e]
/l
reassign 525523 postgresql-common 98
severity 525523 important
tag 525523 moreinfo
thanks
Hello Susam,
Susam Pal [2009-04-25 14:20 +0530]:
> I installed postgresql using the command:
> aptitude update; aptitude install postgresql
What is the precise output of this command? Please do
aptitude
Processing commands for cont...@bugs.debian.org:
> reassign 525523 postgresql-common 98
Bug#525523: postgresql-8.3: /etc/postgresql directory missing after postgresql
install in squeeze
Bug reassigned from package `postgresql-8.3' to `postgresql-common'.
> severity 525523 important
Bug#525523: p
Source: libexplain
Version: 0.11.D001-1
Severity: serious
Hi,
There was an error while trying to autobuild your package:
> Automatic build of libexplain_0.11.D001-1 on excelsior by sbuild/amd64 98
> Build started at 20090503-1037
[...]
> Build-Depends: bison, debhelper (>= 5), g
Package: root-tail
Version: 1.2-3
Severity: grave
Justification: renders package unusable
I start root-tail in WindowMaker autostart
(~/GNUstep/Library/WindowMaker/autostart)
with the following command:
root-tail -g 700x200+950+850 -fn fixed /var/log/messages,green
~/.xsession-errors, blue &
Th
[Noah Slater, 2009-05-02]
> I believe this is caused by #525436.
yes, it is
> Should be fixed in the next upload. Unsure what to do with this bug though.
>
> Piotr, comments?
as said before, let me know if you want me to convert this package to
debhelper's sequencer or make sure you invoke addi
Your message dated Sun, 03 May 2009 10:32:33 +
with message-id
and subject line Bug#526539: fixed in otf-stix 0.9~2007.10.31-3
has caused the Debian Bug report #526539,
regarding otf-stix: FTBFS: Missing Build-Depends
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 03 May 2009 09:58:04 +
with message-id
and subject line Bug#525926: fixed in linux-2.6 2.6.29-4
has caused the Debian Bug report #525926,
regarding linux-image-2.6.29-1-sparc64: boot failure: Fast Data Access MMU Miss
to be marked as done.
This means that you claim th
Your message dated Sun, 03 May 2009 09:58:04 +
with message-id
and subject line Bug#525926: fixed in linux-2.6 2.6.29-4
has caused the Debian Bug report #525926,
regarding linux-2.6 2.6.29-3 built with wrong config on sparc
to be marked as done.
This means that you claim that the problem has
Package: pidgin
Version: 2.5.5-1
Justification: renders package unusable
Severity: grave
pidgin does not start anymore. This is what happens:
giuse...@scarafaggio:~$ pidgin
Illegal instruction
or
giuse...@scarafaggio:~$ strace -ff pidgin 2>&1 | tail -40
[pid 23380] gettimeofday({1241344224, 266
Processing commands for cont...@bugs.debian.org:
> # Automatically generated email from bts, devscripts version 2.10.35lenny3
> tags 526529 confirmed
Bug#526529: amavisd-new: Can't locate object method "new" via package
"Amavis::SpamControl"
There were no tags set.
Tags added: confirmed
>
End of
Your message dated Sun, 03 May 2009 09:18:31 +
with message-id
and subject line Bug#511954: fixed in wmii 3.6+debian-5
has caused the Debian Bug report #511954,
regarding Fails to build due to changes in libixp API
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Sun, 03 May 2009 09:18:29 +
with message-id
and subject line Bug#526563: fixed in trousers 0.3.1-8
has caused the Debian Bug report #526563,
regarding trousers: FTBFS: Invalid libtool wrapper script
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> close 524585
Bug#524585: libept_0.5.26+b1(mips/unstable): FTBFS on mips
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Peter De Schrijver
> thanks
Stopping processing here.
close 524585
thanks
+ Peter De Schrijver (Sat, 18 Apr 2009 12:44:51 +0300):
> > dh_install -plibept0
> > dh_install: libept0 missing files (debian/tmp/usr/lib/lib*.so.*), aborting
> > make: *** [binary-install/libept0] Error 1
> > dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binar
Processing commands for cont...@bugs.debian.org:
> severity 526737 important
Bug#526737: md: RAID 1 check makes kernel almost panic
Severity set to `important' from `critical'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system admini
Processing commands for cont...@bugs.debian.org:
> severity 526656 important
Bug#526656: wishlist: set default printer as default not cups-pdf after 1st
config
Severity set to `important' from `grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian
Processing commands for cont...@bugs.debian.org:
> # correcting overexagerated severity
> severity 525380 important
Bug#525380: amavisd-new: amavis fails to process email with large attachment
Severity set to `important' from `critical'
> thanks
Stopping processing here.
Please contact me if you
Package: linux-image-2.6.29-1-amd64
Version: 2.6.29-3
Severity: critical
Today was the normal crondate for mdadm to run a check on my 2 raid 1
devices.
Problem, when I woke up this morning I found very bad stuff on my
terminals.
The check was stuck at 2% according to /proc/mdstat. I tried to run
hi,
A complement to #526616 in order to transform Severity from 'grave'
to 'normal' to launch syslog-ng in non root pid
Please consider following patch to Lenny Debian distribution
P0: file /etc/default/syslog-ng
---
# defined pid user for launching syslog_ng daemon.
81 matches
Mail list logo
