Bug#597443: package manager broken after install of libglx-nvidia-alternatives (and libgl1-nvidia-alternatives)

2010-09-19 Thread Steven Degrauwe
Package: libglx-nvidia-alternatives Version: 195.36.31-3 Severity: important Tags: d-i Hello, The last dist-upgrade of my Debian-testing system broke the package manager. Responsible for this are the packages mentioned above. Here are the messages I get when upgrading: Selecting previously dese

Bug#582554: dpkg-reconfigure

2010-06-01 Thread Steven Degrauwe
Thanks, that did he trick. Sorry for the noise. Steven On Tuesday 01 June 2010 11:23:10 Emmanuel Fleury wrote: > Hi Steven, > > Just force the dpkg-reconfigure by doing: dpkg-reconfigure --force dash > > Regards > -- > Emmanuel Fleury -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@li

Bug#582554: Processed: Re: Bug#582554: workaround?

2010-05-29 Thread Steven Degrauwe
I just received the new version of dash (0.5.5.1-6), with the same result. The package is broken and all processes of apt or dpkg stop there. On Saturday 29 May 2010 02:33:11 Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > tag 582554 patch > > Bug #58255

Bug#582554: workaround?

2010-05-29 Thread Steven Degrauwe
It doesn't work. I get the following message: /usr/sbin/dpkg-reconfigure: dash is broken or not fully installed Sorry for the trouble On Saturday 29 May 2010 01:40:13 you wrote: > Hi, > > On Friday 28 May 2010 16:10:52 Steven Degrauwe wrote: > > until this bug is fixed, i

Bug#582554: workaround?

2010-05-28 Thread Steven Degrauwe
Package: dash Version: 0.5.5.1-5 Severity: normal Hello, until this bug is fixed, is there a workaround to do a dist-upgrade? Every time I try do do an upgrade, or try do do anything with a package (remove, install,...), the dpkg process returns with an error code (1). I already tried to install

Bug#578907: albums do not show any pictures

2010-04-23 Thread Steven Degrauwe
After a crash of my system (it rarely happens with Debian, but apparently it is possible), I restarted it. I found out that Digikam is working as expected (so I can see all my photos in my albums). The crash had something to do with Digikam, because I got lots of messages in the terminal window

Bug#578907: digikam: albums do not show any pictures

2010-04-23 Thread Steven Degrauwe
Package: digikam Version: 2:1.1.0-1 Severity: grave Justification: renders package unusable I am using Digikam for almost 4 yeas now. Excellent package. But as of today I cannot see any pictures in my album-folders (though they're there, I can browse them with Dolphin or even Showfoto). This turns

Bug#543206: linux-image-2.6.30-1-686: tg3 broadcom driver missing

2010-03-04 Thread Steven Degrauwe
Yes, since revision 0.18 I do not have the warning enymore. Thanx Steven On Tue, 2 Mar 2010 23:44:19 +0100 Moritz Muehlenhoff wrote: > tags 543206 moreinfo > thanks > > On Sun, Aug 23, 2009 at 10:49:11AM +0200, Steven Degrauwe wrote: > > Package: linux-image-2.6.30-1-686 &

Bug#543206: linux-image-2.6.30-1-686: tg3 broadcom driver missing

2009-08-23 Thread Steven Degrauwe
Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal Tags: l10n With the new kernel-update, I got the following messages: update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 W: Possible missing firmware /lib/firmware/tigon/tg3_tso5.bin for module tg3 W: Possible missing fir

Bug#527250: linux-image-2.6.26-2-686: boot hangs on fsck with kernel 2.6.26-2-868

2009-05-07 Thread Steven Degrauwe
Today this problem reappeared. I directly restarted my system with the systemrescuecd to run e2fsck. No problems at all. So there is no corrupt superblock... And since it is not occurring with kernel 2.6.26-1, I believe it has something to do with kernel 2.6.26-2. I just can't see any pattern in

Bug#527250: linux-image-2.6.26-2-686: boot hangs on fsck with kernel 2.6.26-2-868

2009-05-06 Thread Steven Degrauwe
Package: linux-image-2.6.26-2-686 Version: 2.6.26-15 Severity: important Hi, I'm using Debian testing. Recently, my computer shows an error-message at boot, resulting in a stop of the boot-proces. Here's the message: The superblock could not be read or does not describe a correct ext2 filesys