Op zondag 3 april 2016 14:57:48 CEST schreef tech@reachthetribes.org:
Hi everyone, I put in the following bug report on kwin crashing: https://bugzilla.opensuse.org/show_bug.cgi?id=970598
It was suggested that I upgrade to kwin 5.6, so I did, using yast. I made sure I had the correct set of repos for my plasma system, and these are the ones I had according to the advice I was given:
Version: Leap 42.1 Qt 5: http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.1/ KDE Frameworks 5: http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42. 1/
So, using yast I selected the package kwin5-5.6.1-130.1.x86_64.rpm, because 5.6 is supposed to have fixed the error of the screen locking up after a kwin crash. It doesn't fix the crash itself, but only the issue with the screen locking up.
When I upgraded to 5.6, it had a few other changes, switching some of my packages from a build service repo I was using over to the opensuse repos, and I thought everything seemed fine.
But then when I rebooted, it failed to start the display manager. Without the display manager, no network unless you use wicked. So I opened up yast in the terminal, selected wicked, entered the passcode for my wifi service, and exited. Still, no network. I get an IP, but no network.
I really need to try and get this back up and running by the end of the day, as I have some really important things starting tomorrow. Any help would be really appreciated. I am currently sending this email from my old 13.2 partition, which I was able to boot into while my main working partition of 42.1 is down.
My thought is, enable the network in my 42.1 system, run level 3, and then do a zypper dup on the KDE FRameworks 5 and Qt 5 repositories. But with no network, can't even do that. If I can enable the display manager or the network, either one, then I have a fighting chance.
Here is what my display manager reads from zypper when I am in there: # systemctl status display-manager.service display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; disabled) Active: failed (Result: exit-code) since Sun 2016-04-03 14:31:35 CDT; 6min ago Process: 967 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=1/FAILURE)
Apr 03 14:31:34 tribetrekGlap display-manager[967]: /etc/vconsole.conf available Apr 03 14:31:34 tribetrekGlap display-manager[967]: KEYMAP: us Apr 03 14:31:34 tribetrekGlap display-manager[967]: Command: localectl set-keymap us Apr 03 14:31:34 tribetrekGlap display-manager[967]: I: Using systemd /usr/share/systemd/kbd-model-map mapping Apr 03 14:31:35 tribetrekGlap logger[1073]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers Apr 03 14:31:35 tribetrekGlap display-manager[967]: Starting service sddm/usr/bin/sddm: relocation error: /usr/lib64/libQt5Qml.so.5: symbol _ZTI14QObjectPrivate, version Qt_5 not defined in file libQt5Core.so.5 with link time reference Apr 03 14:31:35 tribetrekGlap startproc[1139]: startproc: exit status of parent of /usr/bin/sddm: 127 Apr 03 14:31:35 tribetrekGlap display-manager[967]: ..failed Apr 03 14:31:35 tribetrekGlap systemd[1]: Failed to start X Display Manager.
And here is what my network reading is (don't know what other information I need to post): # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1296 (1.2 Kb) TX bytes:1296 (1.2 Kb)
wlan0 Link encap:Ethernet HWaddr 80:19:34:BD:EB:88 inet addr:192.168.1.75 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: 2602:304:b01a:5060:c11e:7df9:edfc:bcf3/64 Scope:Global inet6 addr: 2602:304:b01a:5060:8219:34ff:febd:eb88/64 Scope:Global inet6 addr: fe80::8219:34ff:febd:eb88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:943 errors:0 dropped:0 overruns:0 frame:0 TX packets:81 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45819 (44.7 Kb) TX bytes:16767 (16.3 Kb)
I noticed that there is no broadcast network. The network password is wpa-psk (I think).
My bet: a mix of packages from various repos. Better hit the forums and show the output of zypper lr -d -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org