This exact same behavior re-appeared today after running
# aptitude update
# aptitude safe-upgrade
again. This time a reboot does not solve the problem.
On Fri, Jun 21, 2013 at 08:50:34PM +0200, Joerg Dietrich wrote:
> This bug apparently vanished after a reboot.
>
> On Fri, Jun 21, 2013 at 09:21:06AM +0000, Debian Bug Tracking System wrote:
> > Thank you for filing a new Bug report with Debian.
> >
> > This is an automatically generated reply to let you know your message
> > has been received.
> >
> > Your message is being forwarded to the package maintainers and other
> > interested parties for their attention; they will reply in due course.
> >
> > Your message has been sent to the package maintainer(s):
> > Luis Rodrigo Gallardo Cruz <rodr...@debian.org>
> >
> > If you wish to submit further information on this problem, please
> > send it to 712...@bugs.debian.org.
> >
> > Please do not send mail to ow...@bugs.debian.org unless you wish
> > to report a problem with the Bug-tracking system.
--
---=== Encrypted mail preferred. Key-ID: 1024D/2B693EBF ===---
Fortune cookie of the day:
You'd like to do it instantaneously, but that's too slow.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
