Summary: | k3b now failing with messages 'Could not find mime type application/octet-stream' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark Knecht <markknecht> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WORKSFORME | ||
Severity: | critical | CC: | jake |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mark Knecht
2004-11-28 16:24:55 UTC
A possible solution is to: Just re-emerge k3b (if the kdelibs have been updated later to k3b, that could be a reason for the fail). Otherwise you could do: 1. unmerge k3b 2. emerge mime-types 3. emerge ctags 4. unmerge and emerge kdelibs 5. emerge k3b That will take some time, but your mime-types should be updated after that. No reply from reporter. I have the same problem with k3b-0.11.23-r2 and kde-3.2.3. Doing the following: 1. unmerge k3b 2. emerge mime-types 3. emerge ctags 4. unmerge and emerge kdelibs 5. emerge k3b Did not work for me. I tried it twice, and I even tried re-emerging all of the kde packages that I had installed. The funny thing is that this only happens to me if I am running k3b in kde. I can run this in fluxbox without any problems. I still get the console messages about kio but that does not appear to affect k3b. On the gentoo forums, a fix that works at least temporarily is to: rm -fr /var/tmp/kdecache-USERNAME/* rm -fr /tmp/kde-USERNAME/* rm -fr /tmp/ksocket-USERNAME/* This only works until you log out. After that, the procedure must be done again. Others sugested migrating to kde-3.4 but I like the relative safety of x86 stable. Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r8 i686) ================================================================= System uname: 2.6.11-gentoo-r8 i686 AMD Athlon(TM) XP 3000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.5 [2.3.5 (#1, May 5 2005, 20:17:22)] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.9.5, 1.8.5-r3, 1.5, 1.7.9-r1, 1.6.3, 1.4_p6 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-xp -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks prelink sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.osuosl.org/ http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ http://gentoo.seren.com/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.netnitco.net http://gentoo.binarycompass.org http://gentoo.eliteitminds.com http://lug.mtu.edu/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="x86 3dnow X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl divx4linux dvd dvdr emboss encode fam foomaticdb fortran gd gdbm gif gpm gtk gtk2 imagemagick imlib ipv6 java jpeg junit kde libg++ libwww mad mikmod mmx motif mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl spell sse ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts vorbis xine xml2 xmms xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY Sorry - somehow I guess I never saw that there had been any response on this. I reported this quite a long time ago. (6 months) I have not seen this problem in quite a long time. My thought would be to do a careful set of tests using emerge -pv --update --deep --newuse world (or possibly just k3b) and then emerge anything that shows up using emerge -pv --update --deep --oneshot world (or just k3b) and then when all of that is clean look at the results of revdep-rebuild -p to ensure that everything needed is really installed. I run Gnome mostly these days and sometimes fluxbox. Actually, the reason is known: kde applications compiled against kde-3.4 cannot run in a kde-3.3 session, and we cannot do much for it... see also bug 65030. um - so what is the solution here? How can one run 3.3 and 3.4 apps together? if not - shouldn't we make sure that one cant install 3.4 apps in a 3.3 kde? |