Bug 229815 - Plugging in blackberry immediately causes several kde processes to share 100% cpu
Summary: Plugging in blackberry immediately causes several kde processes to share 100%...
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Unspecified
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-07 14:25 UTC by Stephen Baker
Modified: 2018-11-06 15:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Baker 2010-03-07 14:25:10 UTC 
Version:            (using KDE 4.4.1)
Installed from:    Archlinux Packages

I have a Blackberry 7250.

As soon as I plug it in several KDE apps begin to share 100% cpu (krunner, plasma, amarok.)  The cursor moves with the mouse but it doesn't respond to clicks.  Sometimes switching VTs works, but I haven't really figured out why it does sometimes and not others.

I am able to repeat this every time on 4.4.0 and 4.4.1.  I don't know before that.

Unplugging the blackberry does not solve the problem; I've only been able to fix it by restarting the computer.
Comment 1 Stephen Baker 2011-10-07 12:24:34 UTC 
I don't have the blackberry anymore so I won't be able to verify this bug.
Comment 2 Andrew Crouthamel 2018-11-06 15:05:44 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Stephen Baker 2018-11-06 15:20:26 UTC 
As I said in my last comment (in 2011) I don't have the phone anymore. At this point, I doubt anyone does.
Comment 4 Andrew Crouthamel 2018-11-06 15:21:20 UTC 
Thanks for the update!