Bug 240970 - Opening "settings" of Kopete turns wlan off
Summary: Opening "settings" of Kopete turns wlan off
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 1.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-06-07 01:50 UTC by Tom Kijas
Modified: 2018-09-19 14:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Kijas 2010-06-07 01:50:16 UTC 
Version:           1.00 (using KDE 4.4.3) 
OS:                Linux

I have realtek RTL8187 wireless card in my notebook and it works fine except one thing - Kopete settings makes it turned off. Everytime I open Kopete settings windows, it disables my wlan0 and the only solution is to restart. Using Kopete does nothing bad to wlan. 
rfkill list before:1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
And after opening settings in kopete:
phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes

Reproducible: Always

Steps to Reproduce:
login to KDE, start kopete, open "settings" window

Actual Results:  
it makes wireless disabled.

Expected Results:  
to do nothing to my wireless

OS: Linux (x86_64) release 2.6.33-02063305-generic
Compiler: cc
Comment 1 Frank Schaefer 2010-06-10 11:54:33 UTC 
It seems like your notebooks network switch gets turned off, but I can't reproduce it with my RTL8187 (no hardware switch) using KDE 4.4.3 / kernel 2.6.33.5 vanilla.

Could you please check the shortcuts defined on your system ?
All I can think of at the moment is, that there is a collision with the key combination used as wlan switch on your hardware...
Comment 2 Andrew Crouthamel 2018-09-19 14:30:43 UTC 
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.