Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: plasma-desktop crash

Hybrid View

  1. #1

    Default plasma-desktop crash

    Hello,
    I was surprised yesterday when I turned on my computer by the following problem with the KDE Plasma Desktop. I cannot remember that I did something special before. I tried to update my system with the installation CD but nothing changed. I also tried “zypper up” but also didn’t help. I cannot log in and I get this error directly after booting. I can run application using Alt+F2 but I don't have any desktop. My graphical card is:

    Code:
     NVIDIA Corporation GK107 [Quadro K2000M] [10de:0ffb] (rev a1)
     Subsystem: Hewlett-Packard Company Device [103c:176b]
     Kernel driver in use: nvidia
    The problem description:

    Code:
    Application: plasma-desktop (4.10.5 "release 1")
    KDE Platform Version: 4.10.5 "release 1"
    Qt Version: 4.8.4
    Operating System: Linux 3.7.10-1.16-desktop x86_64
    Distribution: "openSUSE 12.3 (x86_64)"
    
    -- Backtrace:
    Application: Plasma Desktop Shell (kdeinit4), signal: Segmentation fault
    Using host libthread_db library "/lib64/libthread_db.so.1".
    [Current thread is 1 (Thread 0x7f0666760780 (LWP 2751))]
    
    Thread 2 (Thread 0x7f0647e16700 (LWP 2783)):
    #0  0x00007f066501e964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
    #1  0x00007f0659885307 in ?? () from /usr/lib64/libQtScript.so.4
    #2  0x00007f0659885339 in ?? () from /usr/lib64/libQtScript.so.4
    #3  0x00007f066501ae0f in start_thread () from /lib64/libpthread.so.0
    #4  0x00007f0663d9144d in clone () from /lib64/libc.so.6
    
    Thread 1 (Thread 0x7f0666760780 (LWP 2751)):
    [KCrash Handler]
    #5  0x00007f06621408d0 in QDBusMessage::arguments() const () from /usr/lib64/libQtDBus.so.4
    #6  0x00007f066216e8db in QDBusPendingReplyData::argumentAt(int) const () from /usr/lib64/libQtDBus.so.4
    #7  0x00007f0639684a8b in NMNetworkManagerNm09::NMNetworkManagerNm09(QObject*, QList<QVariant> const&) () from /usr/lib64/kde4/solid_networkmanager09.so
    #8  0x00007f0639680be7 in ?? () from /usr/lib64/kde4/solid_networkmanager09.so
    #9  0x00007f066591a9a5 in KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) () from /usr/lib64/libkdecore.so.5
    #10 0x00007f0639fae5a9 in ?? () from /usr/lib64/libsolidcontrolnm09.so.4
    #11 0x00007f0639fb0e6a in ?? () from /usr/lib64/libsolidcontrolnm09.so.4
    #12 0x00007f0639fb339e in Solid::Control::NetworkManagerNm09::networkInterfaces() () from /usr/lib64/libsolidcontrolnm09.so.4
    #13 0x00007f063aae9401 in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
    #14 0x00007f063aae997c in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
    #15 0x00007f063aaec877 in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
    #16 0x00007f066591a9a5 in KPluginFactory::create(char const*, QWidget*, QObject*, QList<QVariant> const&, QString const&) () from /usr/lib64/libkdecore.so.5
    #17 0x00007f065b91c7ec in Plasma::PluginLoader::loadApplet(QString const&, unsigned int, QList<QVariant> const&) () from /usr/lib64/libplasma.so.3
    #18 0x00007f0648ad35bc in ?? () from /usr/lib64/kde4/plasma_applet_systemtray.so
    #19 0x00007f0648ad3bd1 in ?? () from /usr/lib64/kde4/plasma_applet_systemtray.so
    #20 0x00007f0648ad22d5 in ?? () from /usr/lib64/kde4/plasma_applet_systemtray.so
    #21 0x00007f0648ad2714 in ?? () from /usr/lib64/kde4/plasma_applet_systemtray.so
    #22 0x00007f0648adc56c in ?? () from /usr/lib64/kde4/plasma_applet_systemtray.so
    #23 0x00007f0648ad93e1 in ?? () from /usr/lib64/kde4/plasma_applet_systemtray.so
    #24 0x00007f065b8da4e0 in ?? () from /usr/lib64/libplasma.so.3
    #25 0x00007f065b8e8ea0 in ?? () from /usr/lib64/libplasma.so.3
    #26 0x00007f065b8fc94b in ?? () from /usr/lib64/libplasma.so.3
    #27 0x00007f065b8fd5a4 in Plasma::Corona::loadLayout(QString const&) () from /usr/lib64/libplasma.so.3
    #28 0x00007f065b8fd66c in Plasma::Corona::initializeLayout(QString const&) () from /usr/lib64/libplasma.so.3
    #29 0x00007f0651506be5 in ?? () from /usr/lib64/libkdeinit4_plasma-desktop.so
    #30 0x00007f0651506f4d in ?? () from /usr/lib64/libkdeinit4_plasma-desktop.so
    #31 0x00007f0651508455 in ?? () from /usr/lib64/libkdeinit4_plasma-desktop.so
    #32 0x00007f06653c177e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
    #33 0x00007f066453c974 in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4
    #34 0x00007f066453a86c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
    #35 0x00007f066453eceb in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
    #36 0x00007f066614e7f6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
    #37 0x00007f06653acd8e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
    #38 0x00007f06653b06f1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
    #39 0x00007f06653db133 in ?? () from /usr/lib64/libQtCore.so.4
    #40 0x00007f0660cd47d5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
    #41 0x00007f0660cd4b08 in ?? () from /usr/lib64/libglib-2.0.so.0
    #42 0x00007f0660cd4bc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
    #43 0x00007f06653db2c6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
    #44 0x00007f06645dac1e in ?? () from /usr/lib64/libQtGui.so.4
    #45 0x00007f06653abadf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
    #46 0x00007f06653abd68 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
    #47 0x00007f06653b0a08 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
    #48 0x00007f06514eda31 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
    #49 0x000000000040889a in _start ()

  2. #2

    Default Re: plasma-desktop crash

    Well, apparently the networkmanagement plasmoid in the system tray is crashing.

    Does it also crash for a new user?

    What repos do you have:
    Code:
    zypper lr -d
    You could remove the plasmoid manually from your config.
    Open the file ~/.kde4/share/config/plasma-desktop-appletsrc in a text editor (kwrite f.e.), search for a line containing "plugin=org.kde.networkmanagement" and remove the whole config section.
    For example in my config I would have to remove those lines:
    Code:
    [Containments][1][Applets][6][Configuration][Applets][41]geometry=0,0,24,24
    immutability=1
    plugin=org.kde.networkmanagement
    zvalue=0
    
    
    [Containments][1][Applets][6][Configuration][Applets][41][PopupApplet]
    DialogHeight=279
    DialogWidth=881
    
    
    [Containments][1][Applets][6][Configuration][Applets][41][Shortcuts]
    global=
    I.e. all that are starting with "[Containments][1][Applets][6][Configuration][Applets][41]". The exact numbers may vary on your system though.

    Afterwards try to start plasma by pressing Alt+F2 and typing "plasma-desktop", it should not crash then.

  3. #3

    Default Re: plasma-desktop crash

    Quote Originally Posted by wolfi323 View Post
    Well, apparently the networkmanagement plasmoid in the system tray is crashing.

    Does it also crash for a new user?

    What repos do you have:
    Code:
    zypper lr -d
    the list of repos is:

    Code:
    # | Alias                     | Name                               | Enabled | Refresh | Priority | Type   | URI                                                              | Service
    --+---------------------------+------------------------------------+---------+---------+----------+--------+------------------------------------------------------------------+--------
    1 | openSUSE-12.3-1.7         | openSUSE-12.3-1.7                  | Yes     | No      |   99     | yast2  | cd:///?devices=/dev/disk/by-id/ata-hp_DVD_A_DS8A8SH_6C7242070847 |        
    2 | repo-debug                | openSUSE-12.3-Debug                | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/12.3/repo/oss/   |        
    3 | repo-debug-update         | openSUSE-12.3-Update-Debug         | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/12.3/                  |        
    4 | repo-debug-update-non-oss | openSUSE-12.3-Update-Debug-Non-Oss | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/12.3-non-oss/          |        
    5 | repo-non-oss              | openSUSE-12.3-Non-Oss              | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/non-oss/     |        
    6 | repo-oss                  | openSUSE-12.3-Oss                  | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/oss/         |        
    7 | repo-source               | openSUSE-12.3-Source               | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/12.3/repo/oss/  |        
    8 | repo-update               | openSUSE-12.3-Update               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3/                        |        
    9 | repo-update-non-oss       | openSUSE-12.3-Update-Non-Oss       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3-non-oss/                |

    You could remove the plasmoid manually from your config.
    Open the file ~/.kde4/share/config/plasma-desktop-appletsrc in a text editor (kwrite f.e.), search for a line containing "plugin=org.kde.networkmanagement" and remove the whole config section.
    For example in my config I would have to remove those lines:
    Code:
    [Containments][1][Applets][6][Configuration][Applets][41]geometry=0,0,24,24
    immutability=1
    plugin=org.kde.networkmanagement
    zvalue=0
    
    
    [Containments][1][Applets][6][Configuration][Applets][41][PopupApplet]
    DialogHeight=279
    DialogWidth=881
    
    
    [Containments][1][Applets][6][Configuration][Applets][41][Shortcuts]
    global=
    I.e. all that are starting with "[Containments][1][Applets][6][Configuration][Applets][41]". The exact numbers may vary on your system though.

    Afterwards try to start plasma by pressing Alt+F2 and typing "plasma-desktop", it should not crash then.
    Thank you. This fixed the desktop problem. But now my sound card is not recognized, my laptop cannot detect that it is connect to the power (AC Adpater: Not plugged in) and I lost the connection manager icon in the task manager.

  4. #4

    Default Re: plasma-desktop crash

    Quote Originally Posted by adel_ayara View Post
    Thank you. This fixed the desktop problem. But now my sound card is not recognized, my laptop cannot detect that it is connect to the power (AC Adpater: Not plugged in) and I lost the connection manager icon in the task manager.
    Well, the last point was to be expected since you removed it to prevent it crashing...

    The other 2 points remind me of permission problems (could have caused the networkmanagement crash as well).
    Please post the output of:
    Code:
    loginctl
    and
    Code:
    getfacl /dev/snd/*

  5. #5

    Default Re: plasma-desktop crash

    Quote Originally Posted by wolfi323 View Post
    Well, the last point was to be expected since you removed it to prevent it crashing...



    The other 2 points remind me of permission problems (could have caused the networkmanagement crash as well).
    Please post the output of:
    Code:
    loginctl
    Well the unexpected output is:

    Code:
    Failed to get D-Bus connection: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
    and

    Code:
    getfacl /dev/snd/*
    Code:
    getfacl: Removing leading '/' from absolute path names
    # file: dev/snd/by-path
    # owner: root
    # group: root
    user::rwx
    group::r-x
    other::r-x
    
    # file: dev/snd/controlC0
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/controlC1
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/hwC0D0
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/hwC1D0
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/pcmC0D0c
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/pcmC0D0p
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/pcmC1D3p
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/pcmC1D7p
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/seq
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---
    
    # file: dev/snd/timer
    # owner: root
    # group: audio
    user::rw-
    group::rw-
    other::---

  6. #6

    Default Re: plasma-desktop crash

    Quote Originally Posted by adel_ayara View Post
    Well the unexpected output is:
    Code:
    Failed to get D-Bus connection: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
    And I'm pretty sure this causes all your problems.

    But why is it looking for the socket in /usr/local/...?
    Did you compile and install systemd or dbus (not sure which one would cause something like this) yourself from source?

    Which versions do you have installed?
    Code:
    rpm -qi systemd dbus-1

  7. #7

    Default Re: plasma-desktop crash

    And I'm pretty sure this causes all your problems.

    But why is it looking for the socket in /usr/local/...?
    Did you compile and install systemd or dbus (not sure which one would cause something like this) yourself from source?
    Quote Originally Posted by wolfi323 View Post
    Yes, I did. I needed to apply a patch on the 1.4.16 version of dbus. Bit I didn't think that I will touch the system one: The problem that I couldn't restore the original dbus version and yes I think that everything is related to this dbus problem. So I did exactly is:
    1. Download the dbus-1.4.16.tar.gz
    2. Apply a needde patch on it
    3. compile and ibnstall
    Which versions do you have installed?
    Code:
    rpm -qi systemd dbus-1

    Name : systemd
    Version : 195
    Release : 13.45.1
    Architecture: x86_64
    Install Date: Mon 14 Oct 2013 06:11:35 PM CEST
    Group : System/Base
    Size : 4690046
    License : LGPL-2.1+
    Signature : RSA/SHA256, Mon 07 Oct 2013 08:56:19 AM CEST, Key ID b88b2fd43dbdc284
    Source RPM : systemd-195-13.45.1.src.rpm
    Build Date : Fri 27 Sep 2013 11:38:18 PM CEST
    Build Host : build11
    Relocations : (not relocatable)
    Packager : openSUSE:Submitting bug reports - openSUSE
    Vendor : openSUSE
    URL : systemd
    Summary : A System and Session Manager
    Description :
    Systemd is a system and service manager, compatible with SysV and LSB
    init scripts for Linux. systemd provides aggressive parallelization
    capabilities, uses socket and D-Bus activation for starting services,
    offers on-demand starting of daemons, keeps track of processes using
    Linux cgroups, supports snapshotting and restoring of the system state,
    maintains mount and automount points and implements an elaborate
    transactional dependency-based service control logic. It can work as a
    drop-in replacement for sysvinit.
    Distribution: openSUSE 12.3
    Name : dbus-1
    Version : 1.6.8
    Release : 2.10.1
    Architecture: x86_64
    Install Date: Tue 15 Oct 2013 11:45:40 AM CEST
    Group : System/Daemons
    Size : 878949
    License : GPL-2.0+ or AFL-2.1
    Signature : RSA/SHA256, Fri 11 Oct 2013 08:18:21 PM CEST, Key ID b88b2fd43dbdc284
    Source RPM : dbus-1-1.6.8-2.10.1.src.rpm
    Build Date : Tue 08 Oct 2013 11:24:05 AM CEST
    Build Host : cloud115
    Relocations : (not relocatable)
    Packager : openSUSE:Submitting bug reports - openSUSE
    Vendor : openSUSE
    URL : dbus
    Summary : D-Bus Message Bus System
    Description :
    D-Bus is a message bus system, a simple way for applications to talk to
    one another. D-Bus supplies both a system daemon and a
    per-user-login-session daemon. Also, the message bus is built on top of
    a general one-to-one message passing framework, which can be used by
    any two apps to communicate directly (without going through the message
    bus daemon).
    Distribution: openSUSE 12.3

  8. #8

    Default Re: plasma-desktop crash

    Quote Originally Posted by adel_ayara View Post
    Yes, I did. I needed to apply a patch on the 1.4.16 version of dbus. Bit I didn't think that I will touch the system one: The problem that I couldn't restore the original dbus version and yes I think that everything is related to this dbus problem. So I did exactly is:
    1. Download the dbus-1.4.16.tar.gz
    2. Apply a needde patch on it
    3. compile and ibnstall
    OK, so you installed it to /usr/local right? (Normally that's the default prefix, if you compile from source)
    So by doing that, you now have dbus-1.4.16 running (/usr/local/bin/ is in the path before /usr/bin/), which doesn't fit the rest of the system.

    Uninstall that again and your problems will vanish.

    And you can get back the networkmanagement plasmoid by right-clicking on the small green up-arrow in the system tray (just left of the digital clock), choosing "System Tray Settings" and enabling it there.

  9. #9

    Default Re: plasma-desktop crash

    OK, so you installed it to /usr/local right? (Normally that's the default prefix, if you compile from source)
    So by doing that, you now have dbus-1.4.16 running (/usr/local/bin/ is in the path before /usr/bin/), which doesn't fit the rest of the system.

    Uninstall that again and your problems will vanish.

    Quote Originally Posted by wolfi323 View Post

    This is what I am trying to do since this morning but I couldn't. I uninstalled every thing related to dbus but still when I try
    Code:
    loginctl
    I get the same error as before and checking with
    Code:
     sudo systemctl status dbus
    I get:
    Code:
    dbus.service - D-Bus System Message Bus                                                                                                                                                                          
              Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)                                                                                                                                          
              Active: active (running) since Tue, 2013-10-15 14:51:54 CEST; 9min ago                                                                                                                                 
            Main PID: 871 (dbus-daemon)                                                                                                                                                                              
              CGroup: name=systemd:/system/dbus.service                                                                                                                                                              
                      └ 871 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation                                                                                                   
                                                                                                                                                                                                                     
    Oct 15 14:51:54 linux-pdev.site systemd[1]: Starting D-Bus System Message Bus...                                                                                                                                 
    Oct 15 14:51:54 linux-pdev.site systemd[1]: Started D-Bus System Message Bus.
    And you can get back the networkmanagement plasmoid by right-clicking on the small green up-arrow in the system tray (just left of the digital clock), choosing "System Tray Settings" and enabling it there.

  10. #10

    Default Re: plasma-desktop crash

    Quote Originally Posted by adel_ayara View Post
    I get the same error as before
    Did you reboot?

    Check if there's anything left in /usr/local/ regarding dbus.

    Maybe you overwrote some dbus system files? Run:
    Code:
    sudo rpm -V dbus-1 dbus-1-glib dbus-1-x11
    to check, and post the output, if any.

Page 1 of 2 12 LastLast

Posting Permissions

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