Bug 152914

Summary: KWifimanager crashes when acoustic signal used
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Ciaran Farrell <ciaran.farrell>
Component: KDEAssignee: E-mail List <kde-maintainers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: suse-beta
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Backtrace for KWifiManager crash

Description Ciaran Farrell 2006-02-22 20:41:59 UTC
After KWifiManager (3.5.1 using KDE 3.5.1 Level "a" SuSE 10 UNSUPPORTED) crashed on selecting the "Einstellung -> Akustische Netzsuche", I searched bugs.kde.org for more information and found http://bugs.kde.org/show_bug.cgi?id=112106 - thus, I just want to confirm that this crashed for me with OpenSuSE as well. I'm going to attach the standard KDE backtrace.

Ciaran
Comment 1 Ciaran Farrell 2006-02-22 20:42:49 UTC
Created attachment 69865 [details]
Backtrace for KWifiManager crash
Comment 2 Dirk Mueller 2006-02-22 20:52:45 UTC
rpm -qa | grep arts 

please
Comment 3 Ciaran Farrell 2006-02-23 21:04:19 UTC
linux:/home/cfarrell # rpm -qa | grep arts
kdelibs3-arts-3.5.1-15
arts-1.5.1-4
k3b-arts-0.12.11-2
kdemultimedia3-arts-mad-3.4.2-11.pm.0
kdemultimedia3-arts-3.5.1-5
Comment 4 Dirk Mueller 2006-02-25 16:13:10 UTC
does it work if you install arts-devel?
Comment 5 Ciaran Farrell 2006-02-28 18:15:37 UTC
linux:/home/cfarrell # rpm -qa | grep arts
kdelibs3-arts-3.5.1-15
arts-devel-1.5.1-4
arts-1.5.1-4
k3b-arts-0.12.11-2
kdemultimedia3-arts-mad-3.4.2-11.pm.0
kdemultimedia3-arts-3.5.1-5

And the problem is still there - crashes when I choose Einstellung -> Akustische Netzsuche". Can I provide any other info?
Comment 6 Dirk Mueller 2006-03-03 14:31:29 UTC
no, I need a 10.0 box to find the crash. its solved already for 10.1 because we compile kwifimanager without arts support there. 
Comment 7 Dirk Mueller 2006-03-14 18:24:13 UTC
ok, lets say its fixed for 10.1, and we don't find it serious enough to do an update for 10.0