Bug 155296 - knetworkmanager crash
Summary: knetworkmanager crash
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: KDE (show other bugs)
Version: Beta 6
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Timo Hoenig
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-04 17:15 UTC by Christian Boltz
Modified: 2007-06-05 09:57 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
knetworkmanager crash backtrace (3.09 KB, text/plain)
2006-03-04 17:16 UTC, Christian Boltz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2006-03-04 17:15:55 UTC
I just found knetworkmanager crashing :-(

These are the steps I did:
- update from beta3 to beta6
- started YaST2, changed network configuration to NetworkManager
- right-click knetworkmanager icon, click the WLAN ("connecting" dialog opens)
- right-click knetworkmanager icon, click the cabled network - CRASH.

This also causes my network connection to stay down :-(

I switched back to traditional ifup method in YaST2 and have my network conection back. Unfortunately, Konqueror stays in offline mode :-(  - so I have to enter this report using Firefox.

I was able to reproduce this after installing the debuginfo package and will append the backtrace in a minute.
Comment 1 Christian Boltz 2006-03-04 17:16:59 UTC
Created attachment 71255 [details]
knetworkmanager crash backtrace
Comment 2 Timo Hoenig 2006-03-04 18:19:36 UTC
Christian, can you please update to the following NetworkManager packages:

  http://primates.ximian.com/~rml/misc/NetworkManager/

and use KNetworkManager packages available at:

  http://www.fh-augsburg.de/~thoenig/KNetworkManager/

Please report the bug is still there.
Comment 3 Timo Hoenig 2006-03-04 18:52:38 UTC
As 
Comment 4 Timo Hoenig 2006-03-04 18:53:48 UTC
... I have recently fixed a similar (or even the same) bug in KNetworkManager.  I'm positive that this version will help.
Comment 5 Christian Boltz 2006-03-05 12:52:17 UTC
Yes, it works after updating to the latest packages :-)
Comment 6 Timo Hoenig 2006-03-05 13:21:53 UTC
Cool!  Thanks for testing.  Have a nice sunday.