FedoraForum.org - Fedora Support Forums and Community
Results 1 to 6 of 6
  1. #1
    Join Date
    Dec 2005
    Posts
    85
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    kde making segmentation fault..

    Hi,

    my KDE is making segmentation fault. KDE is not required to restart but this segmentation fault is making every time (after 2 min) when i login to kde/fedora. this is making me annoying.. my linux info is following:
    uname -r # 2.6.31.9-174.fc12.x86_64
    KDE: 4.3.4 (KDE 4.3.4)

    problem:
    Executable: kded4 PID: 1672 Signal: 11 (Segmentation fault)
    here is the following info:

    Application: KDE Daemon (kded4), signal: Segmentation fault
    [KCrash Handler]
    #5 0x000000333bd54d54 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
    #6 0x00007f3551257faf in PackageKit::Transaction::finished(PackageKit::Tran saction::ExitStatus, unsigned int) () from /usr/lib64/libpackagekit-qt.so.12
    #7 0x00007f3551253e39 in PackageKit:lientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libpackagekit-qt.so.12
    #8 0x00007f3551255288 in PackageKit:lientPrivate::qt_metacall(QMetaObject:all, int, void**) () from /usr/lib64/libpackagekit-qt.so.12
    #9 0x000000333bd5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
    #10 0x0000003831a558cf in QDBusConnectionInterface::serviceOwnerChanged(QStr ing const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
    #11 0x0000003831a55b64 in QDBusConnectionInterface::qt_metacall(QMetaObject:all, int, void**) () from /usr/lib64/libQtDBus.so.4
    #12 0x000000333bd5408c in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
    #13 0x0000003831a557ff in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib64/libQtDBus.so.4
    #14 0x0000003831a55bcc in QDBusConnectionInterface::qt_metacall(QMetaObject:all, int, void**) () from /usr/lib64/libQtDBus.so.4
    #15 0x0000003831a22e84 in ?? () from /usr/lib64/libQtDBus.so.4
    #16 0x0000003831a2a61f in ?? () from /usr/lib64/libQtDBus.so.4
    #17 0x000000333bd4e401 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
    #18 0x000000333cb8f65c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
    #19 0x000000333cb968ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
    #20 0x0000003832a11a66 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
    #21 0x000000333bd3ee6c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
    #22 0x000000333bd3fa42 in QCoreApplicationPrivate::sendPostedEvents(QObject* , int, QThreadData*) () from /usr/lib64/libQtCore.so.4
    #23 0x000000333bd67573 in ?? () from /usr/lib64/libQtCore.so.4
    #24 0x000000333903922e in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
    #25 0x000000333903cc18 in ?? () from /lib64/libglib-2.0.so.0
    #26 0x000000333903cd3a in g_main_context_iteration () from /lib64/libglib-2.0.so.0
    #27 0x000000333bd671e6 in QEventDispatcherGlib:rocessEvents(QFlags<QEventLoop::ProcessEventsFlag> ) () from /usr/lib64/libQtCore.so.4
    #28 0x000000333cc21ffe in ?? () from /usr/lib64/libQtGui.so.4
    #29 0x000000333bd3d772 in QEventLoop:rocessEvents(QFlags<QEventLoop::ProcessEventsFlag> ) () from /usr/lib64/libQtCore.so.4
    #30 0x000000333bd3db44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsF lag>) () from /usr/lib64/libQtCore.so.4
    #31 0x000000333bd3fcd9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
    #32 0x0000003833a0b6eb in kdemain () from /usr/lib64/libkdeinit4_kded4.so
    #33 0x00007f355b6fab1d in __libc_start_main () from /lib64/libc.so.6
    #34 0x0000000000400709 in _start ()

    ---------- Post added at 02:50 PM CST ---------- Previous post was at 11:10 AM CST ----------

    hi all,

    no answers yet..for info, i have updated everything..still problem exists..any help..

  2. #2
    leigh123linux Guest
    Try removing kpackagekit to see if it helps.

    http://koji.fedoraproject.org/koji/b...buildID=150896


    Changelog
    * Thu Jan 14 2010 Lukas Tinkl <ltinkl@redhat.com> - 0.5.3-1
    - kpk 0.5.3 (removed some lib dependencies from KdeD module to avoid crashes there)
    * Mon Jan 11 2010 Rex Dieter <rdieter@fedoraproject.org> - 0.5.2-3
    - backport crash fix
    Code:
    su
    yum erase kpackagekit

  3. #3
    Join Date
    Dec 2005
    Posts
    85
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    hello admin,

    i have done that..its ok..but my update package is removed and i can't see addremove program options in system settings..so i can't updare fedora using packages..is there another packages for auto update...when can i reinstall kpackagekit?

  4. #4
    leigh123linux Guest
    Quote Originally Posted by green-cat-fed
    hello admin,

    i have done that..its ok..but my update package is removed and i can't see addremove program options in system settings..so i can't updare fedora using packages..is there another packages for auto update...when can i reinstall kpackagekit?

    Try this, make sure the version is kpackagekit-0.5.3-1.fc12.x86_64 before accepting.


    Code:
    su
    yum --enablerepo=u*g install kpackagekit

  5. #5
    Join Date
    Dec 2005
    Posts
    85
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Hello Admin,

    As per your suggestions, i have installed 0.5.3-1 version..but now i have more bad experience...now kpackagekit start and try to update..but closed down after some time and given segmentation fault 11.
    but previous problem was able to update but was giving segfault..

    suggestions: I will goback to kpackagekit previous version and suggest that dont release the new version to f12 until problem is solved...it will give you more pain..will cause many threads to open..

  6. #6
    Join Date
    Dec 2005
    Posts
    85
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Thumbs up

    Quote Originally Posted by green-cat-fed
    Hello Admin,

    As per your suggestions, i have installed 0.5.3-1 version..but now i have more bad experience...now kpackagekit start and try to update..but closed down after some time and given segmentation fault 11.
    but previous problem was able to update but was giving segfault..

    suggestions: I will goback to kpackagekit previous version and suggest that dont release the new version to f12 until problem is solved...it will give you more pain..will cause many threads to open..
    Hello Admin,

    Pls ignore my last comment..kde is not giving segfault..you can release latest version of kpackagekit if you want...

Similar Threads

  1. Qps segmentation fault
    By bowman in forum Using Fedora
    Replies: 0
    Last Post: 10th March 2008, 05:51 PM
  2. Segmentation Fault in C
    By philstewart in forum Programming & Packaging
    Replies: 40
    Last Post: 22nd February 2008, 12:24 AM
  3. Segmentation fault?
    By Sanuk in forum Using Fedora
    Replies: 15
    Last Post: 13th August 2006, 07:46 PM
  4. apt segmentation fault
    By arathalion in forum Using Fedora
    Replies: 1
    Last Post: 21st November 2004, 01:34 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •