Starting with a 13.2 m/c I did a fresh install of 42.2 from a DVD. KDE. Set up a user. Recovered my old /Home by using xsf_repair. Reinstalled vbox, checked w10 guest working correctly. Then installed an accounting package (keme5) in the host (required compiling and livetex-latex). Made what I thought were some minor alterations to display. The m/c functioned perfectly all day yesterday.
This morning it booted to a blue login screen I have never seen before. After login it switches to black background plus SUSE lightbulb and extremely limited functionality. I used Konsole to load Yast but can see nothing that helps.
Is there some simple switch to get me back the usual desktop with my widgits, etc.
openSUSE modifies it to show the standard background image.
You can change that yourself (either the theme or the background) in systemsettings5->Startup and Shutdown->Login Screen (SDDM).
After login it switches to black background plus SUSE lightbulb and extremely limited functionality. I used Konsole to load Yast but can see nothing that helps.
So Plasma fails to start as well.
Did you maybe remove some packages?
What happens when you run plasmashell in konsole?
Try to reinstall plasma5-desktop and plasma5-workspace at least.
The reference to a “cable” means a cable connection to the router. I can’t recover wifi. I installed systemsettings6 and plasma5. After that I was able to open a graphic settings app with Login Screen options. I chose one but it had no effect after a reboot.
I get the impression that the DVD install did not complete KDE or something I did locked me out as a user. I am currently looking for a way of reinstalling KDE.
I tried startkde and got:
Could not start D-Bus. Can you call qdbus-qt5?
I can open a QDBusViewer but
qdbus-qt5
says it can not connect to the D-Bus server.
The text on the current screen is about 4 points high (****ed difficult to read).
QDBus Viewer says:
Connected to D-Bus.
Screen has some boxes at the bottom with icons or numbers. One says “iceWM”. This icon and the others open a tree of menus with about 300 items that include Yast headings and user apps. Yast and FF are displayed in graphic form. The terminal is primitive (no menu, tiny text).
I created a new user: no change.
Shall I try to “recover” with the DVD or run zypper to install KDE?
I think it’s probably time to list the current issues:
no wifi (“active connection could not be attached”);
unfamiliar theme (difficult to find things but everything is probably there);
so far I cannot find Dolphin;
cannot change theme (because I cannot confirm changes in systemsettings5);
I cannot add desktop icons for everyday applications
All these things were working correctly two days ago. Now, using the menu tree I can open the graphic versions of practically everything
Shall I try to “recover” with the DVD (this has worked for KDE problems in the past) or run zypper to reinstall KDE?
Thanks!
Moving from KDE4 to KDE/Plasma5 does not bring old settings because Plasma stores items in a different location thus you must re setup your desktop. KDE stores it’s settings in ~/.kde4 but Plasma is now in ~/.config. Also the formats may differ so yo can’t just move them you must manually reset your desktop
WiFi may need a proprietary driver. What chip/card??? You probably need to install because generally these don’t get upgraded depending on how you upgraded
Apps on the Desktop- drag from menu or right click and add. Note depending on the app it may not get upgraded if it comes from a non-standard repo pending of course on how you upgraded and thus may not run until you reinstall
“Two days ago” was after a seemingly issue-free re-install from 13.2 to 42.2 (good tip from you).
KDE and Plasma5, wifi, printing, private apps were all working perfectly a few days ago in 42.2 after an issue-free upgrade. I did nothing. Things went wrong the next morning after booting. After that I followed your advice and installed some additional packages, which made things much better (ie, current status).
-wifi card/chip: Centrino Wireless N2230. It updated seamlessly to 42.2. I just had to re-enter the p/w.
upgrade to 42.2 was accomplished with a DVD (download from SUSE Direct).
I suppose we can rule out a problem with the installation DVD and the upgrade in that case.
But things should not just go wrong like that suddenly…
May be hardware problems (e.g. dying hard disk), or e.g. caused by filesystem corruptions (leading to missing or corrupted files).
After that I followed your advice and installed some additional packages, which made things much better (ie, current status).
Which packages?
Do you mean the ones I mentioned? (plasma5-workspace, plasma5-desktop)
If that helped, I suppose the problem is indeed caused by missing/corrupted files (not packages).
I would suggest at this point to run “rpm -Va” to verify all installed packages (warning, this can take a while…).
There is one question that you haven’t answered yet though:
Can you actually run “dbus-launch”, or do you get an error message?
If that helped, I suppose the problem is indeed caused by missing/corrupted files (not packages).
I would suggest at this point to run “rpm -Va” to verify all installed packages (warning, this can take a while…).
Will do this in two hours time.
There is one question that you haven’t answered yet though:
Can you actually run “dbus-launch”, or do you get an error message?
It launches with three lines:
# rpm -Va
.......T. c /etc/sysconfig/network/ifcfg-lo
S.5....T. c /etc/fonts/conf.d/10-rendering-options.conf
S.5....T. c /etc/fonts/conf.d/58-family-prefer-local.conf
missing /usr/lib/systemd/system/tmp.mount
.......T. c /etc/sddm.conf
S.5....T. c /etc/postfix/main.cf
S.5....T. c /etc/postfix/master.cf
S.5....T. c /etc/xdg/kickoffrc
S.5....T. c /etc/ntp.conf
S.5....T. c /etc/default/grub
S.5....T. c /etc/sysconfig/SuSEfirewall2
.......T. /usr/lib64/gconv/gconv-modules.cache
.M....... /var/lib/PackageKit/transactions.db
missing /var/cache/libx11/compose/l4_030_20fca6bc_0e7768ba
missing /var/cache/libx11/compose/l4_030_313cb605_00280cc0
.......T. c /etc/YaST2/control.xml
....L.... /etc/products.d/baseproduct
....L.... c /etc/pam.d/common-account
....L.... c /etc/pam.d/common-auth
....L.... c /etc/pam.d/common-password
....L.... c /etc/pam.d/common-session
S.5....T. c /etc/NetworkManager/NetworkManager.conf
SM5....T. c /etc/fonts/conf.d/30-metric-aliases.conf
....L.... d /usr/share/man/man1/ftp.1.gz
S.5....T. c /etc/plymouth/plymouthd.conf
.M....... /etc/cups
.......T. c /etc/wicked/common.xml
....L.... /usr/lib64/browser-plugins/javaplugin.so
....L.... d /usr/share/man/man1/nosetests.1.gz
.......T. c /etc/iscsi/ifaces/iface.example
.M.....T. c /etc/iscsi/iscsid.conf
....L.... /usr/lib64/browser-plugins/javaplugin.so
.....U... /var/cache/cups
S.5....T. c /etc/default/useradd
.......T. c /etc/login.defs
Hm, I don’t see anything there that should cause the problem either.
Try to run “sudo zypper ve” as well, that should tell whether packages are missing or there are conflicts.
Other than that:
Can you get your wifi to work via nmtui?
Also, just to be clear: your “current state” seems to be that you are using IceWM, not KDE.
So I suppose logging in to KDE/Plasma5 still doesn’t fully work, right?
Or does it?
What happens if you try to run “startkde” or “plasmashell” inside IceWM in an xterm window, what error message do you get?
And what is the exact error message that “qdbus-qt5” gives?
You could of course try to boot from an installation medium and do an “Upgrade”, this should reinstall all packages without actually changing the system (settings and installed applications).
But the question is whether this would help… Hard to say without knowing what’s causing the problem.
: it detects the wifi SSD, if I add or activate (entering the pw) it accepts but there is no connection. Perhaps I don’t know how to use this text-based applet. See below under plasmashell.
KDE/Plasma login
: do you mean system settings? Yes, I can open the graphic-based version but changes are not stored (it says authentication required but no input field).
startkde
Loading stage "initial" 237
startkde: Starting up...
startkde: Could not start D-Bus. Can you call qdbus-qt5?
qdbus-qt5
Could not connect to D-Bus server: 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 exp
ired, or the network connection was broken.
plasmashell
Config timer connecting...
Setting the name of 0x1723430 to "org.kde.ActivityManager.ActivityTemplates"
Setting the name of 0x171f300 to "org.kde.ActivityManager.RunApplication"
Setting the name of 0x1732870 to "org.kde.ActivityManager.Resources.Scoring"
Creating directory: "/home/colin/.local/share/kactivitymanagerd/resources/"
KActivities: Database connection: "kactivities_db_resources_139951937316736_readwrite"
query_only: QVariant(qlonglong, 0)
journal_mode: QVariant(QString, "wal")
wal_autocheckpoint: QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 1)
Service started, version: 7.0.0
Cleaning up...
detected kglobalaccel restarting, re-registering all shortcut keys
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'La
yout' of null
KActivities: Database connection: "kactivities_db_resources_140509706770688_readonly"
query_only: QVariant(qlonglong, 1)
journal_mode: QVariant(QString, "wal")
wal_autocheckpoint: QVariant(qlonglong, 100)
synchronous: QVariant(qlonglong, 0)
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Could not resolve property : radialGradient4857
Could not resolve property : radialGradient4857
Could not resolve property : radialGradient4857
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78:27: Unable to assign [undefined]
to QStringList
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:37: TypeError: Cannot read property
'DateTime' of undefined
Loading Calendar plugin HolidaysEventsPlugin(0x4647fb0)
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anc
hor to a null item.
System tray daemon not reachable
Notifications service registered
XSync seems available and ready
XSync Inited
Supported, init completed
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
Is net online: false
Plasma Shell startup completed
libkcups: 0
libkcups: 0
Is net mobile: false
Is net online: false
Daemon changed
networkmanager-qt: void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) Unhandled property
"Devices"
Is net mobile: false
Is net online: true
Is on battery: true
Daemon changed
Is net mobile: false
Is net online: true
Is on battery: true
Currrent active notifications: QHash()
Guessing partOf as: 0
New Notification: "ICSNET" "Connection 'ICSNET' activated." -1 & Part of: 0
Couldn't find node shadow. Skipping rendering.
It doesn’t sound like you are getting a kernel panic, but maybe try to boot an older kernel (“Advanced Options” in the boot menu) as a test.
A kernel update may explain why this “suddenly” started on a fresh boot while everything worked fine the day before.
: do you mean system settings? Yes, I can open the graphic-based version but changes are not stored (it says authentication required but no input field).
What are you referring to here?
The login screen settings?
Yes, they are in system settings… And yes, you need to enter the root password when trying to save them. You should get a password dialog when you click on OK or Apply.
Regarding your output:
qdbus-qt5
Could not connect to D-Bus server: 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 exp
ired, or the network connection was broken.
I cannot really follow you here.
First it doesn’t work, and then it works?
When/where/how did you run it in either case?
Note the above prompt says user@ICSNET. ICSNET is the wifi SSD. I will be out until 6pm today.
It’s the hostname, not the SSD.
But that reminds me of something.
If the hostname changes during login (i.e. when the WiFi connection is established), this can cause problems, with DBUS in particular (as it refuses to accept connections from this “different host”).
Open YaST->System->Network Settings and disable “Set Hostname via DHCP” (i.e. set it to “no”) on the “Hostname/DNS” tab. That should prevent that the hostname changes during boot or login.
The password dialog does not appear - even in a separate window.
Regarding your output:
qdbus-qt5
Could not connect to D-Bus server: 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 exp
ired, or the network connection was broken.
I cannot really follow you here.
First it doesn’t work, and then it works?
When/where/how did you run it in either case?
Exactly. I ran this immediately before sending my reply. Items keep switching their behaviour as I try the suggestions.
It’s the hostname, not the SSD.
But that reminds me of something. If the hostname changes during login (i.e. when the WiFi connection is established), this can cause problems, with DBUS in particular (as it refuses to accept connections from this “different host”). Open YaST->System->Network Settings and disable “Set Hostname via DHCP” (i.e. set it to “no”) on the “Hostname/DNS” tab. That should prevent that the hostname changes during boot or login. Just guessing here though.
I checked and DHCP is set at “no”.
When I try to activate ICSNET via nmtui it replies "Could not activate connection: Active connection removed before it was initialized. However I can sometimes pull it off. Right now I have both the ethernet cable and wifi running. And when I entered “plasmashell” yesterday it turned wifi on.
Wolfi,
I am probably going to reinstall but first I will try to remember exactly what I did prior to screwing up. Maybe it will provide some clues.
There was an issue after the 42.2 install: I had not deleted the 13.2 /home files. 42.2 complained and would not allow me to create /home/username and install my /home backup (“this partition contains a file system”). I ran xfs-repair, once with -L and then several times without. That fixed the problem right away and 42.2 was working fine.
Next day there were issues when I installed vbox. My notes say:
“. . . unable to find . . . “ during failed vbox install (missing vbox kernel modules)
zypper in kernel-devel gcc
/sbin/rcvboxdrv setup (recompiling VB)
no usb support
vboxuser not added to user permissions. Fixed with Yast. Reboot needed.
After that I recovered my appliance (w10) and vbox is working since then. I also recovered my favorite icons and some widget settings.
Next day with 42.2 stable I started to install keme, an accounting app, which I have been using for about eight years. It’s written in qt and the latest version is qt5. It’s pretty stable, very comprehensive and does an excellent job. I downloaded the same generic Linux version I had been using under 13.2 (version Oct 2016). This has to be compiled. qmake-qt5 didn’t work under 42.2 (cmd not recognized) until I found a small SUSE rpm that fixes that problem. I used Yast to run
libqt5-qtbase-devel
My notes say that this produced “many conflicts and updates” and I seem to remember it deleted a lot of files and added a lot of new ones. After that keme compiled and installed perfectly and is still working correctly. Somewhere I remember there were faults related to nouveau. I have not enabled my nVidia card so I don’t understand the “faults” but I did play around with Bumblebee about two years ago. Shutdown with everything in good shape.
The next day I booted and SDDM appeared out of nowhere (later switched to iceWM - not sure how), lost printing, wifi, xsane and Dolphin (still missing) and some apps stopped working properly (eg, system settings, which won’t save changes).
Pending installation: Chrome (I know there are issues with flash / vbox); Wf Pro for Linux; etc.
HTH . . .