Ubuntu
kdeadmin package

[Dapper] Application Crash when trying to configure network interface thats not enabled

Bug #30775 reported by Craig Sampson
40
Affects Status Importance Assigned to Milestone
kdeadmin (Ubuntu)
Fix Released
Medium
Raphaël Pinson

Bug Description

In administrator mode, clicking on the configure button for a network interface thats present in the list but not enabled causes this:

(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 -1232065888 (LWP 11822)]
(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 0xb7df84b6 in inet_pton () from /lib/tls/i686/cmov/libc.so.6
#7 0xb664ba35 in KAddressValidator::calculateBroadcast ()
   from /usr/lib/kde3/kcm_knetworkconfmodule.so
#8 0xb6666da2 in KNetworkConf::configureDeviceSlot ()
   from /usr/lib/kde3/kcm_knetworkconfmodule.so
#9 0xb66492cd in KNetworkConfDlg::qt_invoke ()
   from /usr/lib/kde3/kcm_knetworkconfmodule.so
#10 0xb6670231 in KNetworkConf::qt_invoke ()
   from /usr/lib/kde3/kcm_knetworkconfmodule.so
#11 0xb6ea626d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0xb6ea6d08 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb723dda3 in QButton::clicked () from /usr/lib/libqt-mt.so.3
#14 0xb6f40b36 in QButton::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#15 0xb6ee0a11 in QWidget::event () from /usr/lib/libqt-mt.so.3
#16 0xb6e3c65a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#17 0xb6e3cbda in QApplication::notify () from /usr/lib/libqt-mt.so.3
#18 0xb75dec7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#19 0xb6dcd9d5 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#20 0xb6dc9099 in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#21 0xb6dc7584 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#22 0xb6de0cc7 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#23 0xb6e55153 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#24 0xb6e55076 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#25 0xb6e3b169 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#26 0xb7f5a426 in kdemain () from /usr/lib/libkdeinit_kcmshell.so
#27 0xb7d35ea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#28 0x080483b5 in ?? ()

Cheers,
Craig

Revision history for this message
FiNeX (finex) wrote :

I've the same problem... but if you:
1. select an activated interface
2. click on the "configure interface" button
3. close the configuration window opened
4. select the disabled interface
5. click on the "configure interface" button
In this way the application don't crash!

Craig Sampson (ubuntu-psi-aus)
Changed in kdeadmin:
status: Unconfirmed → Confirmed
Kenny Duffus (kduffus)
Changed in kdeadmin:
assignee: nobody → kubuntu-team
Revision history for this message
Graeme Hewson (ghewson) wrote :

I had the same problem too, but without any activated interfaces. I worked around the problem by first manually configuring the relevant interface with some arbitrary address, thus:

ifconfig eth1 1.2.3.4

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

I cannot reproduce this on up-to-date dapper.

Can you attach your /etc/network/interfaces file? And output of "ifconfig" before you go in administrator mode.
Is this for wired or wireless interface?

Changed in kdeadmin:
status: Confirmed → Needs Info
Revision history for this message
Luka Renko (lure) wrote :

Description in bug 38530 helped me to reproduce it here - working on the fix.

Changed in kdeadmin:
status: Needs Info → In Progress
Raphaël Pinson (raphink)
Changed in kdeadmin:
assignee: kubuntu-team → raphink
status: In Progress → Fix Committed
Raphaël Pinson (raphink)
Changed in kdeadmin:
status: Fix Committed → Fix Released
Revision history for this message
dmoyne (daniel-moyne) wrote :

I experience also a crask on KGet 2.1.0 (LDE 4.1) when setting unset web interface on port 8080 or unsetting it though action in eventually made on setting ; I have no workable bactrace unfortunately !
Regards

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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