Network-manager KDE no longer shows network interfaces -

[PJJ]

only an empty panel icon that declares that network-manager is not running.
And asks it to be started.

Good advice!

But how in the world do I start the network-manager.
Whatever I tried did not work. And the wireless is on and running. And so is Broadband2Go. But nothing shows.

File network interfaces (/etc/interfaces) shows standard entries
(auto lo
iface lo inet loopback).

Suggestions, PLease?

[PJJ]

The Networkmanager is a plasma applet and you can install a second instance on for example the taskbar, would that one work better?

It is the plasma applet on the taskbar.
It is empty.
It says the network-manager is not running. That's all I get.

Trying to get the nm-applet running I get this:

"nm-applet

** (nm-applet:3044): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 2 matched rules; type="method_call", sender=":1.72" (uid=1000 pid=3044 comm="nm-applet ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1119 comm="NetworkManager ")
** Message: applet now removed from the notification area".

[SteveRiley]

Is Network Manager running? Let's see the output of:

sudo service network-manager status

ps -ef | grep -i network

grep -i networkmanager /var/log/syslog

[PJJ]

Thank you for the input. I have been trying to get a Wimax modem to work. In the process I apparently created a mess - including problems with permissions.

The output of your suggeste commands is as follows:

peter@pHost:~$ [B]sudo service network-manager status[/B]
[sudo] password for peter: 
network-manager start/running, process 1035

peter@pHost:~$ [B]ps -ef | grep -i network[/B]
root      1035     1  0 11:09 ?        00:00:00 NetworkManager
root      1643  1035  0 11:10 ?        00:00:00 /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /run/sendsigs.omit.d/network-manager.dhclient-wwan0.pid -lf /var/lib/NetworkManager/dhclient-4f85d576-4b72-489b-a57a-25135aba2edb-wwan0.lease -cf /var/lib/NetworkManager/dhclient-wwan0.conf wwan0
nobody    1680  1035  0 11:10 ?        00:00:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d
peter     2893  2805  0 11:17 pts/2    00:00:00 grep --color=auto -i network

peter@pHost:~$ [B]grep -i networkmanager /var/log/syslog[/B]
Apr 13 11:07:11 pHost NetworkManager[1051]: <info> (wwan0): device state change: activated -> disconnected (reason 'connection-removed') [100 30 38]
Apr 13 11:07:11 pHost NetworkManager[1051]: <info> (wwan0): deactivating device (reason 'connection-removed') [38]
Apr 13 11:07:11 pHost NetworkManager[1051]: <info> (wwan0): canceled DHCP transaction, DHCP client pid 1604
Apr 13 11:07:11 pHost NetworkManager[1051]: <warn> DNS: plugin dnsmasq update failed
Apr 13 11:07:11 pHost NetworkManager[1051]: <info> Removing DNS information from /sbin/resolvconf
Apr 13 11:07:11 pHost NetworkManager[1051]: <info> (wwan0): supplicant interface state: completed -> disconnected
Apr 13 11:09:33 pHost kernel: [   17.079036] type=1400 audit(1365876573.074:3): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=727 comm="apparmor_parser"
Apr 13 11:09:33 pHost kernel: [   17.081093] type=1400 audit(1365876573.078:6): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=728 comm="apparmor_parser"
Apr 13 11:09:33 pHost kernel: [   17.083232] type=1400 audit(1365876573.078:9): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=754 comm="apparmor_parser"
Apr 13 11:09:41 pHost NetworkManager[1035]: <info> NetworkManager (version 0.9.8.0) is starting...
Apr 13 11:09:41 pHost NetworkManager[1035]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
Apr 13 11:09:41 pHost NetworkManager[1035]: <info> WEXT support is enabled
Apr 13 11:09:42 pHost NetworkManager[1035]: <info> VPN: loaded org.freedesktop.NetworkManager.openconnect
Apr 13 11:09:42 pHost NetworkManager[1035]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Apr 13 11:09:42 pHost NetworkManager[1035]: <info> DNS: loaded plugin dnsmasq
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: init!
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: update_system_hostname
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPluginIfupdown: management mode: unmanaged
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:01:05.0/net/wwan0, iface: wwan0)
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:01:05.0/net/wwan0, iface: wwan0): no ifupdown configuration found.
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:01:08.0/net/eth1, iface: eth1)
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: device added (path: /sys/devices/pci0000:00/0000:00:1e.0/0000:01:08.0/net/eth1, iface: eth1): no ifupdown configuration found.
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: end _init.
Apr 13 11:09:44 pHost NetworkManager[1035]: <info> Loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Apr 13 11:09:44 pHost NetworkManager[1035]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Apr 13 11:09:44 pHost NetworkManager[1035]:    Ifupdown: get unmanaged devices count: 0
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: (160388384) ... get_connections.
Apr 13 11:09:44 pHost NetworkManager[1035]:    SCPlugin-Ifupdown: (160388384) ... get_connections (managed=false): return empty list.
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile: parsing Ethostream ... 
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile:     read connection 'Ethostream'
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile: parsing Virgin Mobile * Helio connection 1 ... 
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile:     read connection 'Virgin Mobile'
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile: parsing attwifi ... 
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile:     read connection 'attwifi'
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile: parsing linksys ... 
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile:     read connection 'linksys'
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile: parsing Wired connection 1 ... 
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile:     read connection 'Wired connection 1'
Apr 13 11:09:44 pHost NetworkManager[1035]:    keyfile: parsing Ethernet connection 2 ... 
Apr 13 11:09:45 pHost NetworkManager[1035]:    keyfile:     read connection 'Ethernet connection Wi'
Apr 13 11:09:45 pHost NetworkManager[1035]:    keyfile: parsing HomeDepot Public Wi-Fi ... 
Apr 13 11:09:45 pHost NetworkManager[1035]:    keyfile:     read connection 'HomeDepot Public Wi-Fi'
Apr 13 11:09:45 pHost NetworkManager[1035]:    keyfile: parsing LAPL-Public ... 
Apr 13 11:09:45 pHost NetworkManager[1035]:    keyfile:     read connection 'LAPL-Public'
Apr 13 11:09:45 pHost NetworkManager[1035]:    Ifupdown: get unmanaged devices count: 0
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> modem-manager is now available
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> monitoring kernel firmware directory '/lib/firmware'.
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1e.0/0000:01:05.0/ieee80211/phy0/rfkill0) (driver ath5k)
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> WiFi hardware radio set enabled
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> WiFi enabled by radio killswitch; enabled by state file
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> WWAN enabled by radio killswitch; enabled by state file
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> WiMAX enabled by radio killswitch; enabled by state file
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> Networking is enabled by state file
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): using nl80211 for WiFi device control
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): driver supports Access Point (AP) mode
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): new 802.11 WiFi device (driver: 'ath5k' ifindex: 3)
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): exported as /org/freedesktop/NetworkManager/Devices/0
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): bringing up device.
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): preparing device.
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (wwan0): deactivating device (reason 'managed') [2]
Apr 13 11:09:45 pHost NetworkManager[1035]: <warn> failed to allocate link cache: (-10) Operation not supported
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (eth1): carrier is OFF
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (eth1): new Ethernet device (driver: 'e100' ifindex: 2)
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/1
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (eth1): bringing up device.
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (eth1): preparing device.
Apr 13 11:09:45 pHost NetworkManager[1035]: <info> (eth1): deactivating device (reason 'managed') [2]
Apr 13 11:09:45 pHost NetworkManager[1035]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Apr 13 11:09:45 pHost NetworkManager[1035]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Apr 13 11:09:46 pHost NetworkManager[1035]: <info> wpa_supplicant started
Apr 13 11:09:46 pHost NetworkManager[1035]: <info> (wwan0) supports 4 scan SSIDs
Apr 13 11:09:46 pHost NetworkManager[1035]: <warn> Trying to remove a non-existant call id.
Apr 13 11:09:46 pHost NetworkManager[1035]: <info> (wwan0): supplicant interface state: starting -> ready
Apr 13 11:09:46 pHost NetworkManager[1035]: <info> (wwan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Apr 13 11:09:46 pHost NetworkManager[1035]: <info> (wwan0): supplicant interface state: ready -> inactive
Apr 13 11:09:46 pHost NetworkManager[1035]: <info> (wwan0) supports 4 scan SSIDs
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Auto-activating connection 'LAPL-Public'.
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0) starting connection 'LAPL-Public'
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> (wwan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 1 of 5 (Device Prepare) started...
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 1 of 5 (Device Prepare) complete.
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 2 of 5 (Device Configure) starting...
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> (wwan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0/wireless): connection 'LAPL-Public' requires no security.  No secrets needed.
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Config: added 'ssid' value 'LAPL-Public'
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Config: added 'scan_ssid' value '1'
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Config: added 'key_mgmt' value 'NONE'
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 2 of 5 (Device Configure) complete.
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> Config: set interface ap_scan to 1
Apr 13 11:10:11 pHost NetworkManager[1035]: <info> (wwan0): supplicant interface state: inactive -> scanning
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> (wwan0): supplicant interface state: scanning -> authenticating
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> (wwan0): supplicant interface state: authenticating -> associating
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> (wwan0): supplicant interface state: associating -> completed
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> Activation (wwan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'LAPL-Public'.
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 3 of 5 (IP Configure Start) started...
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> (wwan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> Activation (wwan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> dhclient started with pid 1643
Apr 13 11:10:12 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 13 11:10:13 pHost NetworkManager[1035]: <info> (wwan0): DHCPv4 state changed nbi -> preinit
Apr 13 11:10:13 pHost NetworkManager[1035]: <info> (wwan0): DHCPv4 state changed preinit -> bound
Apr 13 11:10:13 pHost NetworkManager[1035]: <info>   address 10.0.0.131
Apr 13 11:10:13 pHost NetworkManager[1035]: <info>   prefix 24 (255.255.255.0)
Apr 13 11:10:13 pHost NetworkManager[1035]: <info>   gateway 10.0.0.1
Apr 13 11:10:13 pHost NetworkManager[1035]: <info>   nameserver '10.0.0.1'
Apr 13 11:10:13 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Apr 13 11:10:13 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 5 of 5 (IPv4 Commit) started...
Apr 13 11:10:14 pHost NetworkManager[1035]: <info> (wwan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Apr 13 11:10:14 pHost NetworkManager[1035]: <info> Activation (wwan0) Stage 5 of 5 (IPv4 Commit) complete.
Apr 13 11:10:14 pHost NetworkManager[1035]: <info> (wwan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Apr 13 11:10:14 pHost NetworkManager[1035]: <info> Policy set 'LAPL-Public' (wwan0) as default for IPv4 routing and DNS.
Apr 13 11:10:14 pHost NetworkManager[1035]: <info> DNS: starting dnsmasq...
Apr 13 11:10:14 pHost NetworkManager[1035]: <warn> dnsmasq not available on the bus, can't update servers.
Apr 13 11:10:14 pHost NetworkManager[1035]: <error> [1365876614.497210] [nm-dns-dnsmasq.c:402] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Apr 13 11:10:14 pHost NetworkManager[1035]: <warn> DNS: plugin dnsmasq update failed
Apr 13 11:10:14 pHost NetworkManager[1035]: <info> Writing DNS information to /sbin/resolvconf
Apr 13 11:10:15 pHost NetworkManager[1035]: <info> (wwan0): roamed from BSSID 64:31:50:07:49:B8 (LAPL-Public) to 64:31:50:07:49:C0 (LAPL-Public)
Apr 13 11:10:15 pHost NetworkManager[1035]: <info> Activation (wwan0) successful, device activated.
Apr 13 11:10:15 pHost NetworkManager[1035]: <warn> dnsmasq appeared on DBus: :1.22
Apr 13 11:10:15 pHost NetworkManager[1035]: <info> Writing DNS information to /sbin/resolvconf

[PJJ]

Oh, that got away from me too early. Wanted to make clear separation between the individual results.I uploaded a txt file with the results/output. don't know where it went.

[SteveRiley]

Please try the following.

1. Press Alt+F2 and type kdesudo kate /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf

2. Find the section that begins with <policy context="default">

3. You'll find several deny sections. Change the word "deny" to "allow" in the sections that include:

send_member="Sleep"/

send_member="sleep"/

send_member="wake"/

4. Save the file

5. Reboot your computer

6. Let us know if it fixes the problem.

(source)

[PJJ]

I does not.
I have a network icon in the 'hidden icon' area but it is greyed out and does not respond to anything.
Network settings under 'System Settings' are frozen at 'VPN'.

[SteveRiley]

Alright, then please revert the changes you made.

At this point, my best suggestion would be to file a bug against the Plasma Network Management widget on Launchpad. Be sure to include the output of what happens when you try to run the widget at the command prompt.

[PJJ]

Thank you for your input. the Plasma Network Management widget is apparently a source of continuing trouble judging by the number of queries on the internet. None of the suggested solutions I tried out worked so far.

I now have the widget conditionally back - provided I type "nm-applet" on a command line. Thereafter it appears among the hidden icons. However, it is greyed out and I cannot change anything on it. I am still asked to start the network manager.

peter@pHost:~$ sudo service network-manager stop
network-manager stop/waiting
peter@pHost:~$ sudo service network-manager start
network-manager start/running, process 6270
peter@pHost:~$


Now the icon is visible again, but still has no information except for a VPN connection I did not make. The error message reads:

Error displaying connection information:

No valid active connections found!

But I am running and writing this message on wi-fi.

[PJJ]

I may have found one possible reason for my strange issue(s) described here and in my other post "Cannot open ControlKit...".
I attempted to speed up KDE by changing some settings. I could not make some of the changes because I am "running in failsafe mode".
Huh? I did not switch to failsafe or did I?
I may indeed have temporarily switched to failsafe because I had a problem with the Gnome keyring.

To make a long story short:
Upon attempting to log in using any other method than failsafe I receive an error message that says essentially:

"Cannot load gnome session." You are running in failsafe mode.

How do I get back to the normal log in?

I suspect that if and when I am able to log in normally again, I will also be able to get the network-manager icon back and, hopefully my network settings. The files are still there.

Should I start this as a separate thread?

[SteveRiley]

Ah! Again, since I use KDM and not LightDM, I'm kind of guessing here. Is there a button someplace you can click that will allow you to list all of the available sessions? If so, what do you see? I'm kind of surprised that you're getting an error about GNOME session.

[PJJ]

Sorry for the delayed response. Ever escalating problems of many different sort caused it, I guess.
What broke the camels back was that a flash drive that worked reliably before sudden decided to cause an error message.
Could not be read because of 'authorization' problems. I put the stick in my virtual XP and, voila, everything was there and read.

Considering the many shifting problems and issues I have experienced, there was only one reasonable decision:
Re-install 13.04.
I am doing it the hard way right now.
Going back to 12.04, upgrading to 12.10.
Then upgrade to 13.04.

All because my CD/DVD thingie does not read DVDs.

Thank you for all your assistance and encouragement.

[PJJ]

Well, it is not 'solved' in a true sense. It is solved in a radical way - possibly the only way.
A final thought and a possible explanation for the many and ever changing issues described in this thread and my two other threads that are somewhat related.

Originally I updated from Kubuntu 12.04 to 12.10 and then on to 13.04.
Everything installd without any problem. My new 13.04 worked flawlessly and without a hitch.
Then my adventurous nature that likes a challenge prompted me to 'upgrade' directly to the latest and cutting edge incarnation of 13.04 - kernel version 3.9-rc5..
That went fine as well at first.
In the course of my daily use of the new installation small irregularities crept up. They got worse and worse in a short time. Major issues come along and made me post two main threads. This one and the post about ControlKit.

None of the helpful hints (for which I am grateful) solved the problems permanently. Many worked one time and then started a new round of issues. That is when I decided to reinstall the entire system.

My conclusion and a caveat for other computer users with an adventurous nature:
Since my troubles started only after I had installed the then latest test version of Raring Ringtail from a set of debian packages (.deb), it is very likely that foundations for the issues were laid during installation from the .deb packages.
I read somewhere that .deb packages are not completely compatible with Kubuntu. And my troubles may just have been proof for that.

Though installing fron .deb packages appears to be a nice workaround to avoid cumbersome installation from tarballs, the trouble that can come with it is not worth the time saved.

My advice:
Do not install Kubuntu from .deb packages until Kubuntu and truly debian packages are better synchronized.
I could have saved myself and the helpful members of this forum a lot of time by heading my own (belated) advice.



I found debian packages for the then current rc5 kernel, downloaded the .deb packages and had them installed by QDebi

[SteveRiley]

Since my troubles started only after I had installed the then latest test version of Raring Ringtail from a set of debian packages (.deb), it is very likely that foundations for the issues were laid during installation from the .deb packages.
I read somewhere that .deb packages are not completely compatible with Kubuntu. And my troubles may just have been proof for that.

Though installing fron .deb packages appears to be a nice workaround to avoid cumbersome installation from tarballs, the trouble that can come with it is not worth the time saved.

Would you mind explaining this a little more? Which DEB files do you mean? All the *buntus, being Debian-derived, distribute DEB packages, so it's perfectly normal for us. But are you saying that you downloaded the entire set of Ubuntu DEBs and hand-built a system from that using dpkg? If so, then I can understand how this would create rather an unstable system. It's much better to let apt-get or Aptitude handle this chore, because they will be better than any human at performing dependency resolution

[PJJ]

No, I won't mind.
More or less by directed accident I came upon this site:

http://kernel.ubuntu.com/~kernel-ppa...daily/current/

There I found .deb packages for Kubuntu-3.9-rc 5 (and rc6 at that time). I downloaded the required packages (3 or 4 of them) and installed them by clicking on each of them. One after another. Each time the default installer started and installed the packages.
I did not use dpkg - as far as I remember, though I believe the website that referred me to the site above suggested using dpkg.

Neither one of the packages was in Muon or Synaptic and, I believe, apt-get did not find them either.
I was directed to the site above by another website that had instructions for updating a current Kubuntu installation.

The name of that website was obliterated together with other unimportant data when I reinstalled the system.

Hope this helps.

The most current deb packages on the ppa site came with unsatisfied dependencies. I did not use them - though I was mightily tempted.
Installed the system the hard way instead - updating step by step from 12.04 to 13.04.
It worked and I am using the new installation right now.