Your message dated Mon, 18 Dec 2006 18:33:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#403645: libattr1: kdeinit fails to start
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libattr1
Version: 2.4.32-1
Severity: grave
Justification: renders package unusable
After today dist-upgrade and reboot, kde failed to start telling:
"kdeinit could not start. Check your installation".
The problem seems due to the new libattr1, because after having installed the
previous version, the normal behaviour has been restored. Perhaps this could be
a kdelibs bug, but IMHO I think that is related to this package.
Bye
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (700, 'unstable'), (600, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.3
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages libattr1 depends on:
ii libc6 2.3.6.ds1-9 GNU C Library: Shared libraries
libattr1 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:2.4.32-1.1
* Valerio Passini ([EMAIL PROTECTED]) [061218 18:29]:
> Package: libattr1
> Version: 2.4.32-1
> Severity: grave
> Justification: renders package unusable
>
> After today dist-upgrade and reboot, kde failed to start telling:
> "kdeinit could not start. Check your installation".
> The problem seems due to the new libattr1, because after having installed the
> previous version, the normal behaviour has been restored. Perhaps this could
> be a kdelibs bug, but IMHO I think that is related to this package.
Please look at the other > 5 bug reports first before reporting a bug
that has been fixed in the meantime. Thanks.
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--- End Message ---
