KDE

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • broken KDE installation (what'd I do?!)

    5 answers - 1297 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Yike! It looks like I broke something major yesterday when I did a fresh
    'make clean && make && make install' of kdelibs-3.5-svn. When I try to
    run KWrite, I get the a dialog with the message:
    "A KDE text-editor component could not be found; please check your KDE
    installation."
    and then it crashes with this:
    Using host libthread_db library "/lib/tls/libthread_db.so.1".
    [Thread debugging using libthread_db enabled]
    [New Thread -1208105280 (LWP 1864)]
    [KCrash handler]
    #6 0x00ff3214 in KWrite (this=0x8856888, doc=0x0) at kwritemain.cpp:90
    #7 0x00ff6cf6 in kdemain (argc=2, argv=0xbff3ede4) at kwritemain.cpp:660
    #8 0x080486b2 in main (argc=2, argv=0xbff3ede4) at kwrite.la.cpp:2
    The only output I get is:
    kio (KSycoca): Trying to open ksycoca from
    /
    I have been running KWrite with svn kate-part before (in fact, what I am
    trying to do is test changes to kate-part :-)). The only other thing I
    can think of that changed recently is I built and installed kdesdk from
    svn. I *don't* have a complete svn package suite installed; libs and
    arts (and now sdk and base), but that's it. I *do* have a full 3.5.5
    installation in a separate location that is also in my KDEDIRS.
    Suggestions?
  • No.1 | | 2043 bytes | |

    Matthew Woehlke wrote:
    Yike! It looks like I broke something major yesterday when I did a fresh
    'make clean && make && make install' of kdelibs-3.5-svn. When I try to
    run KWrite, I get the a dialog with the message:

    "A KDE text-editor component could not be found; please check your KDE
    installation."

    and then it crashes with this:

    Using host libthread_db library "/lib/tls/libthread_db.so.1".
    [Thread debugging using libthread_db enabled]
    [New Thread -1208105280 (LWP 1864)]
    [KCrash handler]
    #6 0x00ff3214 in KWrite (this=0x8856888, doc=0x0) at kwritemain.cpp:90
    #7 0x00ff6cf6 in kdemain (argc=2, argv=0xbff3ede4) at kwritemain.cpp:660
    #8 0x080486b2 in main (argc=2, argv=0xbff3ede4) at kwrite.la.cpp:2

    The only output I get is:

    kio (KSycoca): Trying to open ksycoca from
    /

    I have been running KWrite with svn kate-part before (in fact, what I am
    trying to do is test changes to kate-part :-)). The only other thing I
    can think of that changed recently is I built and installed kdesdk from
    svn. I *don't* have a complete svn package suite installed; libs and
    arts (and now sdk and base), but that's it. I *do* have a full 3.5.5
    installation in a separate location that is also in my KDEDIRS.

    Suggestions?

    D'oh! While I'm not sure I'm comfortable with this answer, it turns out
    it is at least partly bash's fault bash had hashed 'kwrite' to my
    3.5.5 version. After clearing the hash (so that I am running the svn
    version instead), "kwrite" runs again, so the crisis is averted but I
    still wonder why I used to be able to run 3.5.5 kwrite and suddenly have
    to run the svn version.

    (, the other thing I should mention: I also uninstalled my distro's
    subversion and neon packages, I have much newer versions built locally
    but my 3.5.5 would not know about them. Does kwrite indirectly pull the
    subversion libraries in a way that might cause this problem?)
  • No.2 | | 2978 bytes | |

    Tuesday 27 February 2007, Matthew Woehlke wrote:
    Matthew Woehlke wrote:
    Yike! It looks like I broke something major yesterday when I did a
    fresh 'make clean && make && make install' of kdelibs-3.5-svn. When I
    try to run KWrite, I get the a dialog with the message:

    "A KDE text-editor component could not be found; please check your KDE
    installation."

    and then it crashes with this:

    Using host libthread_db library "/lib/tls/libthread_db.so.1".
    [Thread debugging using libthread_db enabled]
    [New Thread -1208105280 (LWP 1864)]
    [KCrash handler]
    #6 0x00ff3214 in KWrite (this=0x8856888, doc=0x0) at kwritemain.cpp:90
    #7 0x00ff6cf6 in kdemain (argc=2, argv=0xbff3ede4) at
    kwritemain.cpp:660 #8 0x080486b2 in main (argc=2, argv=0xbff3ede4) at
    kwrite.la.cpp:2

    The only output I get is:

    kio (KSycoca): Trying to open ksycoca from
    /

    I have been running KWrite with svn kate-part before (in fact, what I
    am trying to do is test changes to kate-part :-)). The only other thing
    I can think of that changed recently is I built and installed kdesdk
    from svn. I *don't* have a complete svn package suite installed; libs
    and arts (and now sdk and base), but that's it. I *do* have a full
    3.5.5 installation in a separate location that is also in my KDEDIRS.

    Suggestions?

    D'oh! While I'm not sure I'm comfortable with this answer, it turns out
    it is at least partly bash's fault bash had hashed 'kwrite' to my
    3.5.5 version. After clearing the hash (so that I am running the svn
    version instead), "kwrite" runs again, so the crisis is averted but I
    still wonder why I used to be able to run 3.5.5 kwrite and suddenly have
    to run the svn version.

    (, the other thing I should mention: I also uninstalled my distro's
    subversion and neon packages, I have much newer versions built locally
    but my 3.5.5 would not know about them. Does kwrite indirectly pull the
    subversion libraries in a way that might cause this problem?)

    I have the same issue now and did not figure out yet why.
    My environment variables are:

    export KDEDIR=/home/dh/kde/run/kde4
    export KDEDIRS=$KDEDIR
    export QTDIR=/home/dh/kde/qt-copy

    export
    export KDETMP=/tmp/kde4-dh
    export KDEVARTMP=/var/tmp/kde4-dh
    export KDESYCCA=$KDEVARTMP/ksycoca

    export QT_PLUGIN_PATH=$KDEDIR/lib/kde4/plugins:$QT_PLUGIN_PATH
    export PKG_CNFIG_PATH=$QTDIR/lib/pkgconfig:$PKG_CNFIG_PATH
    export LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib:$LD_LIBRARY_PATH
    export PATH=$KDEDIR/bin:$QTDIR/bin:/usr/bin:/bin

    unset XDG_DATA_DIRS
    unset XDG_CNFIG_DIRS

    I can run apps like konqueror/dolphin. I've done a clean build and ran
    kbuildsycoca4. It still does not work.

    Thanks for any pointers :)
    Dominik

    >Visit #unsub to unsubscribe <<
  • No.3 | | 1059 bytes | |

    Saturday 07 April 2007, Dominik Haumann wrote:
    Tuesday 27 February 2007, Matthew Woehlke wrote:
    Matthew Woehlke wrote:
    Yike! It looks like I broke something major yesterday when I did a
    fresh 'make clean && make && make install' of kdelibs-3.5-svn. When I
    try to run KWrite, I get the a dialog with the message:

    "A KDE text-editor component could not be found; please check your KDE
    installation."

    and then it crashes with this:

    Using host libthread_db library "/lib/tls/libthread_db.so.1".
    [Thread debugging using libthread_db enabled]
    [New Thread -1208105280 (LWP 1864)]
    [KCrash handler]
    #6 0x00ff3214 in KWrite (this=0x8856888, doc=0x0) at kwritemain.cpp:90
    #7 0x00ff6cf6 in kdemain (argc=2, argv=0xbff3ede4) at
    kwritemain.cpp:660 #8 0x080486b2 in main (argc=2, argv=0xbff3ede4) at
    kwrite.la.cpp:2

    I have the same issue now and did not figure out yet why.

    Which issue? katepart not found? Do you have it in $
    The /kde4/ in there is new (since last Monday, a week ago).
  • No.4 | | 2928 bytes | |

    Monday 09 April 2007, David Faure wrote:
    Saturday 07 April 2007, Dominik Haumann wrote:
    Tuesday 27 February 2007, Matthew Woehlke wrote:
    Matthew Woehlke wrote:
    Yike! It looks like I broke something major yesterday when I did a
    fresh 'make clean && make && make install' of kdelibs-3.5-svn. When
    I try to run KWrite, I get the a dialog with the message:

    "A KDE text-editor component could not be found; please check your
    KDE installation."

    and then it crashes with this:

    Using host libthread_db library "/lib/tls/libthread_db.so.1".
    [Thread debugging using libthread_db enabled]
    [New Thread -1208105280 (LWP 1864)]
    [KCrash handler]
    #6 0x00ff3214 in KWrite (this=0x8856888, doc=0x0) at
    kwritemain.cpp:90 #7 0x00ff6cf6 in kdemain (argc=2,
    argv=0xbff3ede4) at
    kwritemain.cpp:660 #8 0x080486b2 in main (argc=2, argv=0xbff3ede4)
    at kwrite.la.cpp:2

    I have the same issue now and did not figure out yet why.

    Which issue? katepart not found? Do you have it in
    $ The /kde4/ in there is new
    (since last Monday, a week ago).

    The file exists. I did a clean build (removed kde4 installation and
    build-dirs). Running kwrite in strace gives me

    access("/", RK) = -1 ENENT (No such file or directory)
    access("/", RK) = 0
    stat64("/", {st_mode=S_IFREG|0644, st_size=16788331, }) = 0
    open("/", RDNLY) = 13

    looks like katepart.so is found.

    Running it in gdb shows that
    Editor *KTextEditor::editor(const char *libname)
    returns 0, 'ef' is 0 here:
    KLibFactory *fact=KLibLoader::self()->factory("katepart");
    KTextEditor::Factory *ef=qobject_cast<KTextEditor::Factory*>(fact);
    This should not be the case (I guess ;): katepart is the fallback component
    and should always exist.

    In KLibrary* KLibLoader::library( "katepart", ) wrap is 0, so
    findLibrary("katepart",) is called. This finally returns
    "/", which is correct.

    Later:
    QLibrary* handle = new QLibrary(libfile); // /home//katepart.so
    handle->setLoadHints(hint);
    if ( !handle->load() || !handle->isLoaded() )
    {
    d->errorMessage = handle->errorString();
    return 0;
    }

    handle->load() somewhere leads to a
    pHnd = dlopen(QFile::encodeName(attempt), dlFlags); // attemp = "/home//katepart.so"
    pHnd is still 0 after this.
    Then, it tries /
    libkatepart.so does not exist.

    Some lines later it says:
    QLibrary::load_sys: Cannot load /
    (/ Cannot open S:
    No such file or directory)

    The code in kwritemain.cpp cachtes this and then pops up the error message
    "A KDE text-editor component could not be found; please check your KDE installation."

    I'll rm -rf qt-copy now. I've no idea what's going wrong ;)

    Dominik

    >Visit #unsub to unsubscribe <<
  • No.5 | | 286 bytes | |

    Monday 09 April 2007, Dominik Haumann wrote:
    []
    I removed a symlink I thought was not used anymore so that Qt fell back to
    Qt4.2. Works now again. how embarrassing && stupid ;)
    Dominik

    >Visit #unsub to unsubscribe <<

Re: broken KDE installation (what'd I do?!)


max 4000 letters.
Your nickname that display:
In order to stop the spam: 8 + 7 =
QUESTION ON "KDE"

EMSDN.COM