Ubuntu
kdeadmin package

systemsettings crashes when you try to configure a network interface on a fresh install

Bug #38530 reported by Frank Bob
14
Affects Status Importance Assigned to Milestone
kdeadmin (Ubuntu)
In Progress
Medium
Kubuntu Bugs

Bug Description

I installed kubuntu using the April 6th 2006 daily iso.

The installer couldn't detect my wireless network so I chose 'Do not configure network at this time'

systemsettings crashes when I tried System Settings->Network Settings->Administrator Mode->Configure Interface

As soon as I click Configure Interface it crashes, for both eth0 and ath0.

After try this 3 times, it stopped asking me for the password when I went to administrator mode. Instead I just got a blank screen. At this point kdesu stopped working completely.

I don't know if the kdesu problem and the crashing network settings problem are related.

Now if I install Ubuntu with Gnome first. Setup the network there, and install kubuntu-desktop. Everything work fine. I can edit network settings using systemsettings. It crashes if they are not setup beforehand.

To reproduce this bug, you must try on a fresh kubuntu install AFAIK.

mon (javiermon-deactivatedaccount)
Changed in kde-systemsettings:
assignee: nobody → kubuntu-team
Revision history for this message
Frank Bob (frankbob) wrote :

I tried with the April 20th kubuntu daily build and get the exact same result. If I'm not the only one, this is a very serious bug.

When breezy was released, there was also a bug preventing the configuration of the network settings. That was unacceptable. This one has got to be fixed.

Revision history for this message
Jason Awuku (jasonawuku) wrote :

I booted up the new Kubuntu Dapper Beta disk, and I was not able to get any network. I sent into System Settings, and exactly the same error pops up, when I pressed the configure button.

Revision history for this message
Luka Renko (lure) wrote :

Can you post your /etc/network/interfaces and output of ifconfig before entering the administrator mode?

Changed in kde-systemsettings:
status: Unconfirmed → Needs Info
Revision history for this message
Frank Bob (frankbob) wrote :

This is the info asked.

frank@dappertest:~$ ifconfig -a
ath0 Link encap:Ethernet HWaddr 00:0F:B5:5E:36:91
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:200
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:185 Memory:f8a40000-f8a50000

eth0 Link encap:Ethernet HWaddr 00:11:09:41:6F:35
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:217 Base address:0xbc00

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:3 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:172 (172.0 b) TX bytes:172 (172.0 b)

frank@dappertest:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

Revision history for this message
davekempe (dave-solutionsfirst) wrote :
Download full text (4.7 KiB)

I can duplicate this bug. I don't have wireless, but it my dapper updated from yesterday I can duplicate. the package in question is:
kde-systemsettings version 0.0svn20060413-0ubuntu1

Steps to reproduce the bug:
1. make /etc/network/interfaces same as above (only define loopback device)
2. restart networking (/etc/init.d/networking restart)
2. sudo ifconfig eth0 0.0.0.0 (my card still had dhcp address after restarting networking and removing eth0 reference in /etc/network/interfaces)
3. go to system-settings, network, click administrator mode and enter your password. you should receive a crash when you click on configure interface.

So the criteria are:
1 /etc/network/interfaces has no reference to eth0
2 eth0 is up but has no ip address

putting the reference back into /etc/network/interfaces to eth0 stops the problem. (even with an ip of 0.0.0.0) and removing the reference, but having a non-zero ip address also doesnt cause the crash.

I have tested this in most combinations I can think of.

here is the backtrace

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232143712 (LWP 16416)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb7dec476 in inet_pton () from /lib/tls/i686/cmov/libc.so.6
#7 0xb663ca35 in KAddressValidator::calcul...

Read more...

Revision history for this message
Luka Renko (lure) wrote :

Reproduced it here - thanks for detailed instructions.

Changed in kdeadmin:
status: Needs Info → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.