Bug#427447: Workaround for bug!
On Fri, Aug 10, 2007 at 02:46:52AM -0400, Greg Folkert wrote: In all the directories that fc-cache failed with errors like: /usr/share/fonts: failed to write cache /usr/share/fonts/X11: failed to write cache /usr/share/fonts/type1: failed to write cache /usr/local/share/fonts: failed to write cache I went to each directory and ran (as root) mkfontdir ; mkfontscale Only when both were run in each of the problematic directories, did the problem go away, which doesn't explain why its happening. I wonder if this process is just missing from some package? As I reported back to this bug, At some point the error just went away from my aptitude stuff. So I must have inadvertantly installed some other package that fixed it up. Not much help I know, but I'm willing to send my aptitude log is anyoen wants it. A signature.asc Description: Digital signature
Bug#427447: now its gone
Okay, this is wierd. I was continuing to configure this machine on the assumption that the problem would sort itself out... and lo and behold, it did with no apparent reason. I do not recall which of my many aptitude installs did it, but at some point it just stopped showing up as a package to reconfigure... go figure. sorry I can't be of more help, but maybe the aptitude logs would help? If you'd like them, please let me know. A signature.asc Description: Digital signature
Bug#427447: this bug still lives!!!
I have encountered this bug using: delappy:~# dpkg -l fontconfig ... ii fontconfig 2.4.2-1.2 generic font configuration library - support delappy:~# dpkg -l ttf-opensymbol pH ttf-opensymbol 2.2.1-7The OpenSymbol TrueType font delappy:~# dpkg -i /var/cache/apt/archives/ttf-opensymbol_2.2.1-7_all.deb (Reading database ... 84133 files and directories currently installed.) Preparing to replace ttf-opensymbol 2.0.4.dfsg.2-7etch1 (using .../ttf-opensymbol_2.2.1-7_all.deb) ... Unpacking replacement ttf-opensymbol ... Setting up ttf-opensymbol (2.2.1-7) ... Updating fontconfig cache... /usr/share/fonts: failed to write cache /usr/share/fonts/X11: failed to write cache /usr/share/fonts/type1: failed to write cache /usr/local/share/fonts: failed to write cache dpkg: error processing ttf-opensymbol (--install): subprocess post-installation script returned error exit status 4 Errors were encountered while processing: ttf-opensymbol this is on a newly installed system. This error appeared during the lenny system install (business card installer). I left it unresolved and migrated up to sid (where I usually live) and it is still unresolved. I have tried manually purging both packages and reinstalling. If I install ttf-opensymbol first, it will install, but fontconfig will fail. If I install it the other way around, fontconfig fails too. I have attached here the fontconfig.log in case that helps. This is an up-to-date sid system. A /usr/share/fonts: /usr/share/fonts: failed to write cache caching, 0 fonts, 3 dirs /usr/share/fonts/X11: /usr/share/fonts/X11: failed to write cache caching, 0 fonts, 6 dirs /usr/share/fonts/X11/100dpi: caching, 358 fonts, 0 dirs /usr/share/fonts/X11/75dpi: caching, 358 fonts, 0 dirs /usr/share/fonts/X11/Type1: caching, 8 fonts, 0 dirs /usr/share/fonts/X11/encodings: caching, 0 fonts, 1 dirs /usr/share/fonts/X11/encodings/large: caching, 0 fonts, 0 dirs /usr/share/fonts/X11/misc: caching, 55 fonts, 0 dirs /usr/share/fonts/X11/util: caching, 0 fonts, 0 dirs /usr/share/fonts/truetype: caching, 0 fonts, 1 dirs /usr/share/fonts/truetype/ttf-dejavu: caching, 21 fonts, 0 dirs /usr/share/fonts/type1: /usr/share/fonts/type1: failed to write cache caching, 0 fonts, 1 dirs /usr/share/fonts/type1/gsfonts: caching, 35 fonts, 0 dirs /usr/X11R6/lib/X11/fonts: skipping, no such directory /usr/local/share/fonts: /usr/local/share/fonts: failed to write cache caching, 0 fonts, 0 dirs /var/lib/defoma/fontconfig.d: caching, 0 fonts, 5 dirs /var/lib/defoma/fontconfig.d/C: caching, 4 fonts, 0 dirs /var/lib/defoma/fontconfig.d/D: caching, 18 fonts, 0 dirs /var/lib/defoma/fontconfig.d/N: caching, 16 fonts, 0 dirs /var/lib/defoma/fontconfig.d/S: caching, 1 fonts, 0 dirs /var/lib/defoma/fontconfig.d/U: caching, 13 fonts, 0 dirs /var/cache/fontconfig: cleaning cache directory fc-cache: failed signature.asc Description: Digital signature
Bug#403998: sorry for the noise
I mis-read the bug reports. I'm sorry for the extra noise. A signature.asc Description: Digital signature
Bug#403998: gzip: confirm 1.3.9 uninstallable
Package: gzip Version: 1.3.9-1 Followup-For: Bug #403998 I can confirm this bug. despite what packages.debian.org says, version 1.3.9-1 is coming down the pipe at debian.midco.net. Interestingly though, apt-cache policy shows version 1.3.9-1 already installed. menawhile aptitude is trying to install it, though it is NOT showing up in the list of packages to upgrade. there is something fishy going on here. regardless, my messages are the same as above whether using aptitude or dpkg -i. This of course borks all install processes... A -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages gzip depends on: ii debianutils 2.17.4 Miscellaneous utilities specific t ii libc62.3.6.ds1-9 GNU C Library: Shared libraries gzip recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343042: linux-image-2.6.14-2-686: Boot aborts with message, '/bin/cat: /sys/block/hda/hda1/dev: No such file or directory'
I can confirm, as others have mentioned, that this bug affects AMD systems as well. All of my symptoms were identical to others reported. I chose to downgrade yaird to testing and this resolved the problem (now running 2.6.14-5). I appears to me that the patch mentioned above doesn't apply yet to AMD so I chose this route. I encountered another problem at the same time and I'm trying to determine if they are related. If anyone else encountered this as well, please let me know. All boots now (whether 2.8.14, or 2.6.12 my old kernel) fail with fsck errors on every partition(!). something along the lines of: UNEXEPCTED DISCREPANCY: SuperBlock last write time is in the future. I realise this is likely not related to this bug (especially because it was all part of a massive apt-get upgrade), but since this bug involved ide issues I thought it might apply. any help appreciated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
