[opensuse] lost display manager on kwin switch - please help!
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.... 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). -- George Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Box #2: 13.1 | KDE 4.7.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.7.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 04/03/2016 04:27 PM, Knurpht - Gertjan Lettink wrote:
My bet: a mix of packages from various repos. Better hit the forums and show the output of zypper lr -d
That's exactly what it was. I was able to fix it finally, but it took some work. I went into the /etc/sysconfig/display-manager file and changed the display manager to gdm (I had installed gnome as a backup from a long time ago). It wouldn't even attempt to enter kde, so then I went into gnome, and yast, changed back to network manager so I could get the network up. With the network up, I opened a gnome terminal (konsole wouldn't work), and re-enabled all my repos that I needed, and did a zypper dup from the framework 5 and qt5 repos. Then I rebooted, and it would at least attempt to enter kde but would get hung up and wouldn't ever enter. Then I deleted the /home/george/.config file (actually renamed it so I could grab some of my old configuration out of it), and was able to enter kde again. I had to reconfigure my plasma system, with my activities and desktops, but I have that all set up in an easy to follow guide, so the reconfiguring wasn't hard. But the overall everything else was a pain in the neck. Here are my repos, in case anyone is curious:
zypper lr # | Alias | Name | Enabled | GPG Check | Refresh ---+---------------------------+-----------------------------------------+---------+-----------+-------- 1 | Bumblebee | Bumblebee | Yes | (r ) Yes | Yes 2 | Downloads | Downloads | Yes | ( p) Yes | Yes 3 | Installation_DVD | openSUSE-42.1-0 | Yes | (r ) Yes | No 4 | KDE_Applications | KDE_Applications | Yes | (r ) Yes | Yes 5 | KDE_Extras | KDE_Extras | Yes | (r ) Yes | Yes 6 | KDE_QT5 | KDE_QT5 | Yes | (r ) Yes | Yes 7 | KDE_frameworks5 | KDE_frameworks5 | Yes | (r ) Yes | Yes 8 | Libdvdcss | Libdvdcss | Yes | (r ) Yes | Yes 9 | google-chrome | google-chrome | Yes | (r ) Yes | Yes 10 | packman | packman | Yes | (r ) Yes | Yes 11 | repo-debug | openSUSE-Leap-42.1-Debug | No | ---- | No 12 | repo-debug-non-oss | openSUSE-Leap-42.1-Debug-Non-Oss | No | ---- | No 13 | repo-debug-update | openSUSE-Leap-42.1-Update-Debug | No | ---- | No 14 | repo-debug-update-non-oss | openSUSE-Leap-42.1-Update-Debug-Non-Oss | No | ---- | No 15 | repo-non-oss | openSUSE-Leap-42.1-Non-Oss | Yes | (r ) Yes | Yes 16 | repo-oss | openSUSE-Leap-42.1-Oss | Yes | (r ) Yes | Yes 17 | repo-source | openSUSE-Leap-42.1-Source | No | ---- | No 18 | repo-update | openSUSE-Leap-42.1-Update | Yes | (r ) Yes | Yes 19 | repo-update-non-oss | openSUSE-Leap-42.1-Update-Non-Oss | Yes | (r ) Yes | Yes
-- George Box #1: 42.1 | KDE Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Box #2: 13.1 | KDE 4.7.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.7.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Knurpht - Gertjan Lettink -
tech＠reachthetribes.org