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

Thread: Plasmashell crash after startup

  1. #1
    Join Date
    May 2018
    Location
    Liptovský Mikuláš, Slovakia
    Posts
    5

    Default Plasmashell crash after startup

    Hello,

    today after update via zypper dup after KDE login plasmashell crash immediatelly after startup. No Idea what's wrong. Only flash-player-ppapi-29.0.0.171-1.1.x86_64, flash-player-gnome-29.0.0.171-1.1.x86_64, flash-player-29.0.0.171-1.1.x86_64, gpg-pubkey-23312922-57af6dd8, libx265-151-2.7-3.1.x86_64, libfdk-aac1-0.1.6-1.1.x86_64, libvidstab1_1-1.1.0-2.1.x86_64 and few days before the sddm and plasma5-session-wayland was updated (but I don't use wayland). Ihave tried to clean ~/.cache ~/.config/ and ~/.local plasma, kwin related files, even tried to login newly created user account but still same result plasmashell crash with following:

    Any idea what's wrong and how to fix it? Thanks.

    peter@peter:~> plasmashell
    org.kde.plasmaquick: Applet preload policy set to 1
    Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
    Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
    trying to show an empty dialog
    trying to show an empty dialog
    trying to show an empty dialog
    KActivities: Database connection: "kactivities_db_resources_140518271382976_readonly"
    query_only: QVariant(qlonglong, 1)
    journal_mode: QVariant(QString, "wal")
    wal_autocheckpoint: QVariant(qlonglong, 100)
    synchronous: QVariant(qlonglong, 0)
    Entry is not valid "kontact.desktop" 0x55e941658f20
    Entry is not valid "ktp-contactlist.desktop" 0x55e941658f20
    Entry is not valid "kontact.desktop" 0x55e941636b10
    Entry is not valid "ktp-contactlist.desktop" 0x55e941636b10
    Closing SQL connection: "kactivities_db_resources_140518271382976_readonly"
    KActivities: Database connection: "kactivities_db_resources_140518271382976_readonly"
    query_only: QVariant(qlonglong, 1)
    journal_mode: QVariant(QString, "wal")
    wal_autocheckpoint: QVariant(qlonglong, 100)
    synchronous: QVariant(qlonglong, 0)
    Nothing to load - the client id is empty
    Nothing to load - the client id is empty
    Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion
    Both point size and pixel size set. Using pixel size.
    Both point size and pixel size set. Using pixel size.
    Both point size and pixel size set. Using pixel size.
    trying to show an empty dialog
    Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.panel/contents/code/LayoutManager.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/LayoutManager.js")
    trying to show an empty dialog
    Warning: all files used by qml by the plasmoid should be in ui/. The file in the path "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/code/uiproperties.js" was expected at QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js")
    libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
    libkcups: Get-Jobs last error: 0 successful-ok
    libkcups: Get-Jobs last error: 0 successful-ok
    plasma-pk-updates: Is net online: false
    plasma-pk-updates: Is net mobile: false
    plasma-pk-updates: Is net online: false
    plasma-pk-updates: Is on battery: false
    plasma-pk-updates: Checking updates, forced
    Plasma Shell startup completed
    org.kde.plasmaquick: New Applet "Application Menu" with a weight of 100
    org.kde.plasmaquick: New Applet "Digital Clock" with a weight of 50
    libkcups: 2
    KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
    sock_file=/run/user/1000/kdeinit5__0
    KCrash: Application 'plasmashell' crashing...
    KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
    sock_file=/run/user/1000/kdeinit5__0
    QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
    QSocketNotifier: Invalid socket 23 and type 'Read', disabling...

    [1]+ Stopped plasmashell

  2. #2
    Join Date
    May 2018
    Location
    Liptovský Mikuláš, Slovakia
    Posts
    5

    Default Re: Plasmashell crash after startup

    Hi,

    I have found that it is caused by libkcups from kde-print-manager. After uninstall it the plasmashell starts correctly. Any idea whats wrong or how to find more details to be able to fix it?

    Thanks.

  3. #3
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,867
    Blog Entries
    14

    Default Re: Plasmashell crash after startup

    Quote Originally Posted by peter_beno View Post
    Hi,

    I have found that it is caused by libkcups from kde-print-manager. After uninstall it the plasmashell starts correctly. Any idea whats wrong or how to find more details to be able to fix it?

    Thanks.
    Hi, welcome,

    Don't know what you did, but on my Tw install with KDE, GNOME and Enlightenment libkcups is not installed at all, and never was.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  4. #4
    Join Date
    May 2018
    Location
    Liptovský Mikuláš, Slovakia
    Posts
    5

    Default Re: Plasmashell crash after startup

    Quote Originally Posted by Knurpht View Post
    Hi, welcome,

    Don't know what you did, but on my Tw install with KDE, GNOME and Enlightenment libkcups is not installed at all, and never was.
    I am not sure why it was originally installed but now after uninstall if I try update "zypper dup" it want to install it again. Any idea how to find why?

    e.g.:
    peter:~ # zypper dup
    Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
    Loading repository data...
    Reading installed packages...
    Computing distribution upgrade...

    The following 2 NEW packages are going to be installed:
    kde-print-manager kde-print-manager-lang

    2 new packages to install.
    Overall download size: 479.8 KiB. Already cached: 0 B. After the operation, additional 2.2 MiB will be used.
    Continue? [y/n/...? shows all options] (y): n

  5. #5
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,134

    Default Re: Plasmashell crash after startup

    Quote Originally Posted by Knurpht View Post
    Hi, welcome,

    Don't know what you did, but on my Tw install with KDE, GNOME and Enlightenment libkcups is not installed at all, and never was.
    It is included in the pattern “KDE Plasma 5 Desktop Environment”. The current version is 18.04.0. It is part of my KDE-only TW installation and I think provides the printer and print-queue management in KDE System Settings.

    My guess is that Peter had another repository than a mirror of http://download.opensuse.org/tumbleweed/repo/oss/ enabled and providing an incompatible version. In your case, you probably have the Gnome print manager installed as an alternative to the KDE (Qt5) one.
    ~Thank you for sharing an interesting problem.
    --
    slàinte mhath,
    rayH

  6. #6
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,867
    Blog Entries
    14

    Default Re: Plasmashell crash after startup

    Quote Originally Posted by eng-int View Post
    It is included in the pattern “KDE Plasma 5 Desktop Environment”. The current version is 18.04.0. It is part of my KDE-only TW installation and I think provides the printer and print-queue management in KDE System Settings.
    I stand corrected.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  7. #7
    Join Date
    May 2018
    Location
    Liptovský Mikuláš, Slovakia
    Posts
    5

    Default Re: Plasmashell crash after startup

    Quote Originally Posted by eng-int View Post
    It is included in the pattern “KDE Plasma 5 Desktop Environment”. The current version is 18.04.0. It is part of my KDE-only TW installation and I think provides the printer and print-queue management in KDE System Settings.

    My guess is that Peter had another repository than a mirror of http://download.opensuse.org/tumbleweed/repo/oss/ enabled and providing an incompatible version. In your case, you probably have the Gnome print manager installed as an alternative to the KDE (Qt5) one.
    Hi,
    I don't think I have repository with incompatible version. I have checked repositories and also the info about kde-print-manager (see below). It looks like it it from oss. I have suspicion that it is caused by some incorrect configuration of printing system (global ,not user related, because there is the same problem on newly created user). But I have no clue which configuration or how to trace more detailed information about that crash couse. If someone have any idea how to find more information about the problem I appreciate any advice and help.



    peter:~ # zypper info kde-print-manager
    Loading repository data...
    Reading installed packages...


    Information for package kde-print-manager:
    ------------------------------------------
    Repository : openSUSE-Tumbleweed-Oss
    Name : kde-print-manager
    Version : 18.04.0-1.1
    Arch : x86_64
    Vendor : openSUSE
    Installed Size : 1.2 MiB
    Installed : No
    Status : not installed
    Source package : kde-print-manager-18.04.0-1.1.src
    Summary : A print manager for KDE
    Description :
    This project is a replacement for the previous printing management of KDE.



    peter:~ # zypper lr
    Repository priorities are without effect. All enabled repositories share the same priority.

    # | Alias | Name | Enabled | GPG Check | Refresh
    ---+-------------------------------------+--------------------------------------------------------------------+---------+-----------+--------
    1 | Archiving_Backup | Nobody wants backup, they only want restore. (openSUSE_Tumbleweed) | Yes | (r ) Yes | No
    2 | Java_packages | Factory Java packages (openSUSE_Tumbleweed) | No | ---- | ----
    3 | http-download.opensuse.org-8eb1776d | Education | No | ---- | ----
    4 | http-download.opensuse.org-b1322994 | science | No | ---- | ----
    5 | http-download.opensuse.org-da8df15e | home:ulo:tortoisehg | Yes | (r ) Yes | Yes
    6 | http-ftp.uni-erlangen.de-2e013472 | Packman Repository | Yes | (r ) Yes | Yes
    7 | openSUSE-20170406-0 | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes
    8 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ----
    9 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes
    10 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ----
    11 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes
    12 | skype-stable | skype (stable) | Yes | (r ) Yes | Yes
    13 | skype-unstable | skype (unstable) | Yes | (r ) Yes | Yes

  8. #8
    Join Date
    Oct 2008
    Location
    Glasgow, Scotland
    Posts
    1,134

    Default Re: Plasmashell crash after startup

    Quote Originally Posted by peter_beno View Post
    I don't think I have repository with incompatible version. I have checked repositories
    A potentially incompatible component could come from anywhere, not necessarily another copy of kde-print-manager.
    The way to show what repositories you are using is:
    Code:
    >  zypper lr -Ed
    Note the CODE tags (#).
    Do you have any locked packages?

    Quote Originally Posted by peter_beno View Post
    I have suspicion that it is caused by some incorrect configuration of printing system
    |t should only take ten minutes using YaST to delete the print queues (printers) to see what happens and then recreate them anew.. If you are using BTRFS snaphots, they provide a quick roll-back. Do you have any proprietary print drivers?

    I would try a “zypper dup” with only these repositories enabled:
    http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/
    http://ftp5.gwdg.de/pub/opensuse/tum.../repo/non-oss/
    http://ftp.gwdg.de/pub/linux/misc/pa...SE_Tumbleweed/
    (I have only ever seen anything real in a Tumbleweed Update repository, and that was years ago.) You can always add the others back one at a time.

    If you are dependent on alien (non-openSUSE Tumbleweed) packages (apart from Packmsn), then I would recommend serious consideration of using a stable Leap disribution. Relying on Microsoft et al to keep pace with the rate of Tumbleweed releases seems over optimistic.
    ~Thank you for sharing an interesting problem.
    --
    slàinte mhath,
    rayH

  9. #9
    Join Date
    May 2018
    Location
    Liptovský Mikuláš, Slovakia
    Posts
    5

    Default Re: Plasmashell crash after startup

    Quote Originally Posted by eng-int View Post
    A potentially incompatible component could come from anywhere, not necessarily another copy of kde-print-manager.
    The way to show what repositories you are using is:
    Code:
    >  zypper lr -Ed
    Note the CODE tags (#).
    Do you have any locked packages?


    |t should only take ten minutes using YaST to delete the print queues (printers) to see what happens and then recreate them anew.. If you are using BTRFS snaphots, they provide a quick roll-back. Do you have any proprietary print drivers?

    I would try a “zypper dup” with only these repositories enabled:
    http://ftp5.gwdg.de/pub/opensuse/tumbleweed/repo/oss/
    http://ftp5.gwdg.de/pub/opensuse/tum.../repo/non-oss/
    http://ftp.gwdg.de/pub/linux/misc/pa...SE_Tumbleweed/
    (I have only ever seen anything real in a Tumbleweed Update repository, and that was years ago.) You can always add the others back one at a time.

    If you are dependent on alien (non-openSUSE Tumbleweed) packages (apart from Packmsn), then I would recommend serious consideration of using a stable Leap disribution. Relying on Microsoft et al to keep pace with the rate of Tumbleweed releases seems over optimistic.
    Hi,

    thank for advice. I have removed and recreated printer configurations and the problem is fixed. Thanks a lot.

    Anout Leap, I am relatively new in suse, I was using mandrake/mandriva/mageia from 2000-2015 and then kubuntu 2015-2017. Year ago when I have installed the OpenSuse, that time Leap was not able to install on my ThinkPad L570 so I have tried Thumbleweed. I was thinking about to switch to Leap but not sure how painful it is. If the switch of repositories and some additional config/caches cleanup is sufficient or I will have to make clean install and move all data, reinstall proprietary apps, reconfigure everything (domain, vpn's, emails, .....). Are there any recommendations or guide for migration from Tumbleweed to Leap?

  10. #10

    Default Re: Plasmashell crash after startup

    It seems ths is also discussed at https://forum.kde.org/viewtopic.php?f=309&t=150956.
    I could not find those "discover packages" mentioned there on my Tumbleweed machine.

    I'm a +10 year openSUSE user and it is quite disgusting that I had to spend more than one hour of my weekend to find a way to fix login on failing all accounts of my family machine due to this problem
    And as so often, without finding a thread like this I would have failed.

    What I want to say with this, all the 'normal' computer users out there will usually have no realistic chance to fix this and will silently drop openSUSE (I doubt that these issues are limited to the Tumbleweed rolling release).
    I.e. after all these years openSUSE is still not a valid option for end users.

    At least it's a gleam of hope that this issue is discussed here in the forums instead of these crappy opensuse-mailinglist.

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
  •