If you have a different one, please post your /var/log/Xorg.0.log to see whether the driver is actually used.
And maybe the output of “glxinfo | grep render” as well (you may have to install Mesa-demo-x first, I don’t think it’s there by default)
plasmashell
No metadata file in the package, expected it at: “/home/rafis/Pictures/Wallpaper/”
No metadata file in the package, expected it at: “/home/rafis/Pictures/Wallpaper/”
No metadata file in the package, expected it at: “/home/rafis/Pictures/Wallpaper/”
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property ‘Layout’ of null
KActivities: Database connection: “kactivities_db_resources_139641176930560_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 : linearGradient5334
Could not resolve property : linearGradient5332
Could not resolve property : linearGradient5326
Could not resolve property : linearGradient5328
Could not resolve property : linearGradient5334
Could not resolve property : linearGradient5332
Could not resolve property : linearGradient5326
Could not resolve property : linearGradient5328
Could not resolve property : linearGradient5334
Could not resolve property : linearGradient5332
Could not resolve property : linearGradient5326
Could not resolve property : linearGradient5328
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item.
<Unknown File>: QML QQuickLayoutAttached: Binding loop detected for property “preferredWidth”
System tray daemon not reachable
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null
Notifications service registered
link XMLID_34_ hasn’t been detected!
link XMLID_34_ hasn’t been detected!
link XMLID_36_ hasn’t been detected!
libkcups: Create-Printer-Subscription last error: 0 successful-ok
plasmashell: symbol lookup error: /usr/lib64/libkcupslib.so: undefined symbol: ippGetStatusCode
plasmashell
No metadata file in the package, expected it at: "/home/rafis/Pictures/Wallpaper/"
No metadata file in the package, expected it at: "/home/rafis/Pictures/Wallpaper/"
No metadata file in the package, expected it at: "/home/rafis/Pictures/Wallpaper/"
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:83: TypeError: Cannot read property 'Layout' of null
KActivities: Database connection: "kactivities_db_resources_139933296556288_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 : linearGradient5334
Could not resolve property : linearGradient5332
Could not resolve property : linearGradient5326
Could not resolve property : linearGradient5328
Could not resolve property : linearGradient5334
Could not resolve property : linearGradient5332
Could not resolve property : linearGradient5326
Could not resolve property : linearGradient5328
Could not resolve property : linearGradient5334
Could not resolve property : linearGradient5332
Could not resolve property : linearGradient5326
Could not resolve property : linearGradient5328
file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/DigitalClock.qml:443:5: QML Text: Cannot anchor to a null item.
file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:96: TypeError: Cannot read property of null
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
file:///usr/lib64/qt5/qml/QtQuick/Controls/Private/ScrollBar.qml:71:5: QML Loader: Binding loop detected for property "sourceComponent"
Notifications service registered
XSync seems available and ready
XSync Inited
Supported, init completed
link XMLID_34_ hasn't been detected!
link XMLID_34_ hasn't been detected!
link XMLID_36_ hasn't been detected!
libkcups: Create-Printer-Subscription last error: 0 successful-ok
plasmashell: symbol lookup error: /usr/lib64/libkcupslib.so: undefined symbol: ippGetStatusCode
On Fri, 25 Nov 2016 12:06:01 +0000, rafisv wrote:
> wolfi323;2801416 Wrote:
>> Or, as I said, log in to IceWM (or twm if you prefer), open an xterm
>> window, run “plasmashell” there and post the output.
I got the same symptoms of the OP (and I had installed the same nvidia
drivers version, with everything up to date).
My card is a 8800GTS, I tried to uninstall the nvidia drivers (G03) and
when attempting to do so Yast auto selects the G04 set (!! which I
suppose wont’ work as those are fore different cards).
So I disabled the nvidia repository first and then uninstalled the nvidia
driver. This takes you to the default nouveau driver, which is working
right now.
I will try again when the new driver version is out.
Hope this helps.
-G-
I’ve got exactly the same problem with plasma 5, although I did not do any upgrade. Maybe I got some automatic updates in between but nothing intentionally.
I use Tumbleweed.
Last thing I did one week ago was: In the graphical settings I chose not to automatically log on my standard user, as I did until now. Now, one week later, I boot again, the standard user is still automatically logged on, but the desktop is incomplete, as stated above.
Firstly, I thought, something with my user settings could be wrong (happened before). But I have another user account that I never used in graphical display mode yet. So it should not have any graphical settings, so far. And if I use this one to start graphical display (plasma 5), I get a completely black screen with just a mouse cursor but no menu, etc.
In
.xsession-errors-\:
I get:
tset: terminal attributes: No such device or address
tset: terminal attributes: No such device or address
Loading stage "initial" 215
startkde: Starting up...
dbus-update-activation-environment: warning: error sending to systemd: org.free
desktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited w
ith status 1
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(Q
String,QString,QString)
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/b
aloosearchmodule.so"
kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/k
screen.so"
PS: I don’t want to piggyback this thread, but try to help in finding the problem for the both of us (and maybe more people)?
Ok, so this thread got out of control while I was away for a few days…
For rafisv:
You have your problem there.
What version of kde-print-manager do you have installed?
rpm -qi kde-print-manager
What repos do you use?
zypper lr -d
For the others:
Please open a new thread about your problem, this will get a mess otherwise.
@-G-: according to your graphics card it may help to use the nvidia 304.131 driver though, as I mentioned in this thread already the latest 304.132 version is broken.
Nvidia is aware of that, and are working on a fix AFAIK.
Name : kde-print-manager
Version : 16.08.2
Release : 1.1
Architecture: x86_64
Install Date: Tue 22 Nov 2016 11:57:20 PM MSK
Group : System/GUI/KDE
Size : 1223613
License : GPL-2.0+
Signature : RSA/SHA256, Tue 25 Oct 2016 01:17:09 PM MSK, Key ID b88b2fd43dbdc284
Source RPM : kde-print-manager-16.08.2-1.1.src.rpm
Build Date : Tue 25 Oct 2016 01:16:50 PM MSK
Build Host : lamb04
Relocations : (not relocatable)
Packager : http://bugs.opensuse.org
Vendor : openSUSE
URL : http://dantti.wordpress.com/24.9.90/02/12/print-manager/
Summary : A new print manager for KDE
Description :
This project aims to be a full replacement for the
current printing management of KDE.
* It should be small and fast
* Simple and functional
* Very well integrated
Author(s):
Dantti
Distribution: openSUSE Leap 42.2
You have that enabled, but kde-print-manager doesn’t come from that repo.
Are you actually wanting to use the newer applications from KDE:Applications?
Then you should do a full switch to it.
Otherwise you can just as well remove it.
Name : cups154-libs
Version : 1.5.4
Release : 3.6
Architecture: x86_64
Install Date: Wed 16 Nov 2016 03:58:57 PM MSK
Group : Hardware/Printing
Size : 4972650
License : SUSE-GPL-2.0-with-openssl-exception and LGPL-2.1
Signature : DSA/SHA1, Thu 07 Jan 2016 08:23:39 PM MSK, Key ID 669dec9f98c4529d
Source RPM : cups154-1.5.4-3.6.src.rpm
Build Date : Thu 07 Jan 2016 08:22:49 PM MSK
Build Host : build24
Relocations : (not relocatable)
Vendor : obs://build.opensuse.org/Printing
URL : http://www.cups.org/
Summary : Libraries for CUPS Traditional Version 1.5.4
Description :
The Common UNIX Printing System (CUPS) is the
standards-based, open source printing system.
See http://www.cups.org
For SLE12 we provide the last traditional CUPS version 1.5.4
as "cups154" RPMs in the "legacy" module.
This package contains libraries needed by
CUPS traditional version 1.5.4 and other packages.
Distribution: Printing / openSUSE_Leap_42.1
Well, that’s the reason for your problem then I suppose.
And it’s the version from 42.1 too.
As I already wrote, kde-print-manager is compiled against the cups included in your openSUSE version.
In this case, your cups-libs is too old apparently.
So, the question is, why do you exactly need that “for compatibility with old printer”?
Do current cups versions not support your printer?
If that is the reason, you should uninstall kde-print-manager then I suppose.
Or rather file a bug report to re-add support to your printer.
As you cannot login to Plasma5, there’s no easy way otherwise.
You could manually edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc so that the applet is disables, but I cannot tell you what to change currently.