Bug 277782 - plasma-mobile crashed after accepting unkown certificate for open wlan
Summary: plasma-mobile crashed after accepting unkown certificate for open wlan
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: general (show other bugs)
Version: 0.8
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-14 19:05 UTC by Robby Engelmann
Modified: 2011-11-05 18:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (22.32 KB, application/octet-stream)
2011-07-17 08:46 UTC, Robby Engelmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robby Engelmann 2011-07-14 19:05:21 UTC
Version:           unspecified (using Devel) 
OS:                Linux

Today I tried to establish a wlan connection to an open (unsecure, w/o encryption) wlan. The connection was established correctly, but plasma crashed after accepting the unknown certificate for this university network connection.

Reproducible: Always

Steps to Reproduce:
1. connect to an unsecure wlan which is open/not encrypted and provides a certificate
2. accept this certificate after connection is established
3. in the next dialogue, allow this certificate forever

Actual Results:  
plasma-mobile crashes

Expected Results:  
certificate is allowed forever and I can login the use the www via a browser

After restart and retry, the certificate again has to be allowed. Not sure, whether this bug is specific for plasma-mobile.
Unfortunately, I lost the saved file of the bug report from drkonq. I will try tomorrow again, but perhaps anybody can reproduce than.
Comment 1 Aaron J. Seigo 2011-07-15 09:01:01 UTC
a backtrace will be required to sort this bug out. if you could supply one that would be most appreciated.
Comment 2 Sebastian Kügler 2011-07-15 09:12:46 UTC
I had added debug symbols to the packages last week, you should be able to install the necessary debug information from the Dr Konqi dialog that pops up. The resulting backtrace should give us a clear idea of what's going wrong.
Comment 3 Robby Engelmann 2011-07-17 08:46:21 UTC
Created attachment 61936 [details]
backtrace
Comment 4 Lamarque V. Souza 2011-10-20 21:06:52 UTC
You are using a release candidate version of SC 4.7.0. Can you upgrade to SC 4.7.2 final and test it again?