LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)
-   -   [LEAP] Reinstall KDE (https://www.linuxquestions.org/questions/suse-opensuse-60/%5Bleap%5D-reinstall-kde-4175579845/)

l1m0n4d3 05-15-2016 09:28 AM
[LEAP] Reinstall KDE
 
Hi guys, it seems I've got some kind of issues with KDE, one of them regarding OpenVPN connections via NM (no data transfer at all, connection via shell works like a charm, instead).

Therefore I would like to reinstall the desktop environment, this time in the cleanest way possible.
Previously I decided to brutally uninstall all installed packages by patterns "Plasma 5 Desktop" and "KDE Desktop Environment", then to reinstall them, obtaining as result that I was not able to use graphical mode anymore.
That forced me to restore from a backup.

A previous reset of KDE by renaming /home/$USER/.kde4 brought me no success, issues were still present.

Thanks in advance!

CJ Chitwood 05-16-2016 11:51 PM
I'm no guru myself but I too am using Leap. I would have done the same thing as you, but there are two options I would have tried...

1. Install a second, third, or sixth desktop environment alongside KDE before removing KDE (I do this on nearly every machine as I often find myself in a different mood for a different environment on different days). This way you'll still be able to log in graphically, even if it's an unfamiliar interface.

2. If that's not an option, the command line to install packages is "zypper in <packagename>". I'd update the package manager repositories before removing KDE, but once KDE's gone and the system reboots you to CLI, this would be the way to get KDE back.

I wonder, though, if there's a way to purge all KDE files (including settings that for whatever reason aren't removed with the usual remove scripts) like there is with apt-based package managers.



HIH and GL

CJ

wagscat123 05-21-2016 06:43 PM
Looking at it there's probably some tree (perhaps a Plasma 5 equivalent of .kde4?) that contains all of your Plasma 5 configuration that you can delete.

.kde4 will just cover whatever KDE 4 components are installed; Leap is mostly KDEish 5 stuff.

l1m0n4d3 06-20-2016 11:08 AM
Changed vendor, Plasma updated.
Issues with VPN still persist. I guess there's something wrong with NM.

wagscat123 06-23-2016 04:30 PM
One thing that cleared much of my "KDE 5" configuration was when I went under the .config directory in the home directory and deleted everything related to KDE.

wagscat123 06-27-2016 07:48 PM
Here's the output from journalctl --fu NetworkManager

Code:
Jun 27 15:04:46 linux-rnpk NetworkManager[665]: <info>  (lo): link connected
Jun 27 15:04:46 linux-rnpk NetworkManager[665]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Jun 27 15:04:46 linux-rnpk NetworkManager[665]: <info>  ModemManager available in the bus
Jun 27 15:04:46 linux-rnpk NetworkManager[665]: <info>  wpa_supplicant running
Jun 27 15:04:46 linux-rnpk NetworkManager[665]: <info>  (wlan0): supplicant interface state: init -> starting
Jun 27 15:04:47 linux-rnpk NetworkManager[665]: <info>  (wlan0) supports 4 scan SSIDs
Jun 27 15:04:47 linux-rnpk NetworkManager[665]: <info>  (wlan0): supplicant interface state: starting -> ready
Jun 27 15:04:47 linux-rnpk NetworkManager[665]: <info>  (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jun 27 15:04:48 linux-rnpk NetworkManager[665]: <info>  (wlan0): supplicant interface state: ready -> inactive
Jun 27 15:04:51 linux-rnpk NetworkManager[665]: <info>  startup complete
Jun 27 20:42:59 linux-rnpk systemd[1]: Stopping Network Manager...
Jun 27 20:42:59 linux-rnpk NetworkManager[665]: <info>  caught SIGTERM, shutting down normally.
Jun 27 20:42:59 linux-rnpk NetworkManager[665]: <info>  (wlan0): device state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
Jun 27 20:42:59 linux-rnpk NetworkManager[665]: <info>  (p3p2): device state change: unavailable -> unmanaged (reason 'unmanaged') [20 10 3]
Jun 27 20:42:59 linux-rnpk NetworkManager[665]: <info>  exiting (success)
Jun 27 20:42:59 linux-rnpk systemd[1]: Stopped Network Manager.
Jun 27 20:44:08 linux-rnpk systemd[1]: Starting Network Manager...
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  NetworkManager (version 1.0.12) is starting...
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Read config: /etc/NetworkManager/NetworkManager.conf
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded settings plugin ifcfg-suse: (C) 2008 Novell, Inc.  To report bugs please use the NetworkManager mailing list. (/usr/lib64/NetworkManager/libnm-settings-plugin-ifcfg-suse.so)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Jun 27 20:44:08 linux-rnpk systemd[1]: Started Network Manager.
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  keyfile: new connection /etc/NetworkManager/system-connections/Sharp403-909f2ddf-eaae-455c-9c0a-7a649eb3d4ff (909f2ddf-eaae-455c-9c0a-7a649eb3d4ff,"Sharp403")
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  keyfile: new connection /etc/NetworkManager/system-connections/Sharp403-da7d929f-a9fc-4290-a083-f2abee7d5b6e (da7d929f-a9fc-4290-a083-f2abee7d5b6e,"Sharp403")
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  keyfile: new connection /etc/NetworkManager/system-connections/Sharp403 (b6b4b208-066e-414e-84b6-498f157f4226,"Sharp403")
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  VPN: loaded org.freedesktop.NetworkManager.vpnc
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  VPN: loaded org.freedesktop.NetworkManager.pptp
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  VPN: loaded org.freedesktop.NetworkManager.openvpn
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  monitoring kernel firmware directory '/lib/firmware'.
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/ieee80211/phy0/rfkill0) (driver ath9k)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  WiFi hardware radio set enabled
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  WWAN hardware radio set enabled
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMVxlanFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMVlanFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMVethFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMTunFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMMacvlanFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMInfinibandFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMGreFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMEthernetFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMBridgeFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMBondFactory (internal)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wifi.so)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/libnm-device-plugin-team.so)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/libnm-device-plugin-wwan.so)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/libnm-device-plugin-adsl.so)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  WiFi enabled by radio killswitch; enabled by state file
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  WWAN enabled by radio killswitch; enabled by state file
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  WiMAX enabled by radio killswitch; enabled by state file
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  Networking is enabled by state file
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  (p3p2): new Ethernet device (carrier: OFF, driver: 'r8169', ifindex: 2)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  (p3p2): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  keyfile: add connection in-memory (1bcba03c-d7ff-40de-a0bd-397b1bceaa27,"Wired connection 1")
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  (p3p2): created default wired connection 'Wired connection 1'
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  (wlan1): driver does not support SSID scans (scan_capa 0x00).
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  (wlan1): using WEXT for WiFi device control
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  (wlan1): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'r8712u', ifindex: 4)
Jun 27 20:44:08 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (lo): link connected
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0): using nl80211 for WiFi device control
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0): driver supports Access Point (AP) mode
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'ath9k', ifindex: 3)
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  wpa_supplicant running
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0): supplicant interface state: init -> starting
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): supplicant interface state: init -> starting
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  ModemManager available in the bus
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0) supports 4 scan SSIDs
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0): supplicant interface state: starting -> ready
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1) supports 1 scan SSIDs
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): supplicant interface state: starting -> ready
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  Auto-activating connection 'Sharp403'.
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): Activation: starting connection 'Sharp403' (da7d929f-a9fc-4290-a083-f2abee7d5b6e)
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  NetworkManager state is now CONNECTING
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): Activation: (wifi) access point 'Sharp403' has security, but secrets are required.
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: config -> need-auth (reason 'none') [50 60 0]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <warn>  (wlan1): No agents were available for this request.
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  NetworkManager state is now DISCONNECTED
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <warn>  (wlan1): Activation: failed for connection 'Sharp403'
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  Auto-activating connection 'Sharp403'.
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): Activation: starting connection 'Sharp403' (da7d929f-a9fc-4290-a083-f2abee7d5b6e)
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  NetworkManager state is now CONNECTING
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): Activation: (wifi) access point 'Sharp403' has security, but secrets are required.
Jun 27 20:44:09 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: config -> need-auth (reason 'none') [50 60 0]
Jun 27 20:44:10 linux-rnpk NetworkManager[8790]: <info>  (wlan0): supplicant interface state: ready -> inactive
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: prepare -> config (reason 'none') [40 50 0]
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  (wlan1): Activation: (wifi) connection 'Sharp403' has security, and secrets exist.  No new secrets needed.
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  Config: added 'ssid' value 'Sharp403'
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  Config: added 'scan_ssid' value '1'
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  Config: added 'key_mgmt' value 'NONE'
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  Config: added 'wep_key0' value '<omitted>'
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  Config: added 'wep_tx_keyidx' value '0'
Jun 27 20:44:11 linux-rnpk NetworkManager[8790]: <info>  Config: set interface ap_scan to 1
Jun 27 20:44:19 linux-rnpk NetworkManager[8790]: <info>  (wlan1): supplicant interface state: ready -> associating
Jun 27 20:44:20 linux-rnpk NetworkManager[8790]: <info>  (wlan1): supplicant interface state: associating -> completed
Jun 27 20:44:20 linux-rnpk NetworkManager[8790]: <info>  (wlan1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Sharp403'.
Jun 27 20:44:20 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: config -> ip-config (reason 'none') [50 70 0]
Jun 27 20:44:20 linux-rnpk NetworkManager[8790]: <info>  Activation (wlan1) Beginning DHCPv4 transaction (timeout in 45 seconds)
Jun 27 20:44:20 linux-rnpk NetworkManager[8790]: <info>  dhclient started with pid 9056
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>    address 192.168.1.34
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>    plen 24 (255.255.255.0)
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>    gateway 192.168.1.1
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>    server identifier 192.168.1.1
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>    lease time 86400
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>    nameserver '192.168.1.1'
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>    domain name 'westell.com'
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>  (wlan1): DHCPv4 state changed unknown -> bound
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>  (wlan1): device state change: secondaries -> activated (reason 'none') [90 100 0]
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>  NetworkManager state is now CONNECTED_LOCAL
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>  NetworkManager state is now CONNECTED_SITE
Jun 27 20:44:25 linux-rnpk NetworkManager[8790]: <info>  Policy set 'Sharp403' (wlan1) as default for IPv4 routing and DNS.
Jun 27 20:44:26 linux-rnpk NetworkManager[8790]: <13>Jun 27 20:44:25 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Jun 27 20:44:26 linux-rnpk NetworkManager[8790]: <13>Jun 27 20:44:25 dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 27 20:44:26 linux-rnpk NetworkManager[8790]: ATTENTION: You have modified /etc/resolv.conf.  Leaving it untouched...
Jun 27 20:44:26 linux-rnpk NetworkManager[8790]: You can find my version in /etc/resolv.conf.netconfig ...
Jun 27 20:44:26 linux-rnpk NetworkManager[8790]: <info>  (wlan1): Activation: successful, device activated.
Jun 27 20:44:26 linux-rnpk NetworkManager[8790]: <info>  startup complete
Jun 27 20:44:26 linux-rnpk NetworkManager[8790]: <info>  NetworkManager state is now CONNECTED_GLOBAL
At 15:04 I started the computer, at 20:42 I stopped NetworkManager in YaST and switched to wicked, and at 20:44 I started it again and everything started working, as usual.


All times are GMT -5. The time now is 01:09 AM.