Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: latest update kills PLASMA

  1. #11
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,499

    Default Re: latest update kills PLASMA

    Quote Originally Posted by FrankyU2 View Post
    If the update previous to this one was a really long time ago it could be related this old issue possibly.

    https://forums.opensuse.org/showthread.php/534273-Upgrade-to-20181218-killed-all-but-one-graphical-login
    having pci=nomsi,noaer on the kernel cmd line did not have any effect

    it was tried with secure boot/ support for secure boot both enabled and disabled

    thanks for the heads up

  2. #12
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,499

    Default Re: latest update kills PLASMA

    Quote Originally Posted by karlmistelberger View Post
    You can filter:

    Code:
    erlangen:~ # journalctl -b _PID=1306 --grep error
    -- Logs begin at Tue 2019-09-03 21:44:16 CEST, end at Sat 2019-09-07 16:39:59 CEST. --
    Sep 07 13:31:10 erlangen plasmashell[1306]: libkcups: CUPS-Get-Printers last error: 0 successful-ok
    Sep 07 13:31:10 erlangen plasmashell[1306]: libkcups: Get-Jobs last error: 0 successful-ok
    Sep 07 13:31:10 erlangen plasmashell[1306]: libkcups: Get-Jobs last error: 0 successful-ok
    Sep 07 13:31:10 erlangen plasmashell[1306]: libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
    Sep 07 13:43:23 erlangen plasmashell[1306]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/applet/CompactApplet.qml:64: TypeError: Cannot read property 'Layout' of null
    Sep 07 13:43:23 erlangen plasmashell[1306]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/applet/CompactApplet.qml:82: TypeError: Type error
    Sep 07 13:43:23 erlangen plasmashell[1306]: libkcups: Cancel-Subscription last error: 0 successful-ok
    Sep 07 13:43:23 erlangen plasmashell[1306]: libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
    Sep 07 13:43:23 erlangen plasmashell[1306]: libkcups: Cancel-Subscription last error: 0 successful-ok
    erlangen:~ #
    for one boot, with cmd journalctl -g _PID=1306 --grep error, the output is,

    Code:
    -- Reboot --
    Sep 08 01:52:12 g7-2246sg ksmserver[2103]: Qt: Session management error: networkIdsList argument is NULL
    Sep 08 01:52:13 g7-2246sg kscreen_backend_launcher[2109]: kscreen.xcb.helper: Event Error:  147
    Sep 08 01:52:16 g7-2246sg kwin_x11[2107]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 828, resource id: 14680069, major code: 18 (ChangeProperty), minor code: 0
    Sep 08 01:52:31 g7-2246sg plasmashell[2118]: libkcups: CUPS-Get-Printers last error: 1030 No destinations added.
    Sep 08 01:52:31 g7-2246sg plasmashell[2118]: libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
    Sep 08 01:52:32 g7-2246sg plasmashell[2118]: libkcups: Get-Jobs last error: 0 successful-ok
    Sep 08 01:52:32 g7-2246sg plasmashell[2118]: libkcups: Get-Jobs last error: 0 successful-ok
    Sep 08 01:52:32 g7-2246sg kwin_x11[2107]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1094, resource id: 6291492, major code: 18 (ChangeProperty), minor code: 0
    Sep 08 01:52:43 g7-2246sg pulseaudio[2188]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Sep 08 01:53:02 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Cannot read property 'length' of undefined
    Sep 08 01:53:03 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:454: TypeError: Type error
    Sep 08 01:53:05 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:454: TypeError: Type error
    Sep 08 01:53:06 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Type error
    Sep 08 01:53:08 g7-2246sg kdeinit5[2301]: Qt: Session management error: networkIdsList argument is NULL
    -- Reboot --
    cheers

  3. #13
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    966

    Default Re: latest update kills PLASMA

    Quote Originally Posted by keellambert View Post
    for one boot, with cmd journalctl -g _PID=1306 --grep error, the output is,

    Code:
    -- Reboot --
    Sep 08 01:52:12 g7-2246sg ksmserver[2103]: Qt: Session management error: networkIdsList argument is NULL
    Sep 08 01:52:13 g7-2246sg kscreen_backend_launcher[2109]: kscreen.xcb.helper: Event Error:  147
    Sep 08 01:52:16 g7-2246sg kwin_x11[2107]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 828, resource id: 14680069, major code: 18 (ChangeProperty), minor code: 0
    Sep 08 01:52:31 g7-2246sg plasmashell[2118]: libkcups: CUPS-Get-Printers last error: 1030 No destinations added.
    Sep 08 01:52:31 g7-2246sg plasmashell[2118]: libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
    Sep 08 01:52:32 g7-2246sg plasmashell[2118]: libkcups: Get-Jobs last error: 0 successful-ok
    Sep 08 01:52:32 g7-2246sg plasmashell[2118]: libkcups: Get-Jobs last error: 0 successful-ok
    Sep 08 01:52:32 g7-2246sg kwin_x11[2107]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1094, resource id: 6291492, major code: 18 (ChangeProperty), minor code: 0
    Sep 08 01:52:43 g7-2246sg pulseaudio[2188]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Sep 08 01:53:02 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Cannot read property 'length' of undefined
    Sep 08 01:53:03 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:454: TypeError: Type error
    Sep 08 01:53:05 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:454: TypeError: Type error
    Sep 08 01:53:06 g7-2246sg plasmashell[2118]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:375: TypeError: Type error
    Sep 08 01:53:08 g7-2246sg kdeinit5[2301]: Qt: Session management error: networkIdsList argument is NULL
    -- Reboot --
    cheers
    • Is there a problem with kdeinit?
      Code:
      karl@erlangen:~/Downloads> journalctl -b --user --grep kdeinit5
      -- Logs begin at Tue 2019-09-03 21:44:16 CEST, end at Sun 2019-09-08 09:09:57 CEST. --
      Sep 07 13:31:08 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.kglobalaccel' requested by ':1.6' (uid=1000 pid=1264 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:31:08 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.KScreen' requested by ':1.6' (uid=1000 pid=1264 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:31:09 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.bluez.obex' requested by ':1.6' (uid=1000 pid=1264 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:43:51 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.kglobalaccel' requested by ':1.153' (uid=1000 pid=4322 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:43:51 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.KScreen' requested by ':1.153' (uid=1000 pid=4322 comm="kded5 [kdeinit5]                                  ")
      karl@erlangen:~/Downloads>
    • What about with a pristine login (new user with empty home directory)?
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  4. #14
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,499

    Default Re: latest update kills PLASMA

    Quote Originally Posted by karlmistelberger View Post
    • Is there a problem with kdeinit?
      Code:
      karl@erlangen:~/Downloads> journalctl -b --user --grep kdeinit5
      -- Logs begin at Tue 2019-09-03 21:44:16 CEST, end at Sun 2019-09-08 09:09:57 CEST. --
      Sep 07 13:31:08 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.kglobalaccel' requested by ':1.6' (uid=1000 pid=1264 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:31:08 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.KScreen' requested by ':1.6' (uid=1000 pid=1264 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:31:09 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.bluez.obex' requested by ':1.6' (uid=1000 pid=1264 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:43:51 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.kglobalaccel' requested by ':1.153' (uid=1000 pid=4322 comm="kded5 [kdeinit5]                                  ")
      Sep 07 13:43:51 erlangen dbus-daemon[1200]: [session uid=1000 pid=1200] Activating service name='org.kde.KScreen' requested by ':1.153' (uid=1000 pid=4322 comm="kded5 [kdeinit5]                                  ")
      karl@erlangen:~/Downloads>
    • What about with a pristine login (new user with empty home directory)?
    hi,

    the output of cmd, journalctl -g _PID=1306 --grep kde | grep fail, is

    Sep 05 23:17:31 g7-2246sg kglobalaccel5[3982]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    Sep 05 23:17:31 g7-2246sg dbus-daemon[1766]: [session uid=1001 pid=1766] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
    Sep 05 23:17:43 g7-2246sg dbus-daemon[1766]: [session uid=1001 pid=1766] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
    Sep 05 23:17:43 g7-2246sg kglobalaccel5[4050]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    Sep 05 23:17:43 g7-2246sg dbus-daemon[1766]: [session uid=1001 pid=1766] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
    Sep 05 23:17:43 g7-2246sg kglobalaccel5[4055]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    Sep 05 23:17:45 g7-2246sg dbus-daemon[1766]: [session uid=1001 pid=1766] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
    Sep 05 23:17:45 g7-2246sg kglobalaccel5[4060]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    Sep 05 23:17:46 g7-2246sg dbus-daemon[1766]: [session uid=1001 pid=1766] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
    Sep 05 23:17:46 g7-2246sg kglobalaccel5[4066]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    Sep 05 23:17:46 g7-2246sg dbus-daemon[1766]: [session uid=1001 pid=1766] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6
    Sep 05 23:17:46 g7-2246sg kglobalaccel5[4072]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    Sep 05 23:17:47 g7-2246sg kglobalaccel5[4077]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
    Sep 05 23:17:47 g7-2246sg dbus-daemon[1766]: [session uid=1001 pid=1766] Activated service 'org.kde.kglobalaccel' failed: Process org.kde.kglobalaccel received signal 6[/code]

    re-installing, kglobalaccel5 and dbus-1, have made no difference

    this is a very new net install, but a new user will be tried when time allows

    if cmd fsck is run after a PLASMA session lots of fixes are needed, no fixes are required after IceWM session

    cheers

  5. #15
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,706

    Default Re: latest update kills PLASMA

    Run smartctl to check disk You may have localized disk problem in the area wher KDE is stored.

  6. #16
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    966

    Default Re: latest update kills PLASMA

    Quote Originally Posted by keellambert View Post
    if cmd fsck is run after a PLASMA session lots of fixes are needed, no fixes are required after IceWM session
    You need to fix /home. Watch for damage: smartctl -a /dev/sda, smartctl -t long /dev/sda.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  7. #17
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,499

    Default Re: latest update kills PLASMA

    Quote Originally Posted by karlmistelberger View Post
    You need to fix /home. Watch for damage: smartctl -a /dev/sda, smartctl -t long /dev/sda.
    hi,

    both commands run, the second one took 244 minutes to complete,
    no errors messages were reported in the journal or the display.

  8. #18
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    966

    Default Re: latest update kills PLASMA

    Quote Originally Posted by keellambert View Post
    hi,

    both commands run, the second one took 244 minutes to complete,
    no errors messages were reported in the journal or the display.
    To make sure run fsck and smartctl for /. You need to boot into an alternate OS for fsck.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), openSUSE Tumbleweed, KDE Plasma 5

  9. #19
    Join Date
    Jun 2009
    Location
    Mangfall, Germany
    Posts
    1,499

    Default Re: latest update kills PLASMA

    Quote Originally Posted by karlmistelberger View Post
    [*]What about with a pristine login (new user with empty home directory)?
    hi,

    with a new user account all is fine

    thanks again to all who responded

    cheers

Page 2 of 2 FirstFirst 12

Posting Permissions

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