Bug 159088 - new device notifier can't open dolphin when USB stick is plugged in
Summary: new device notifier can't open dolphin when USB stick is plugged in
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-10 20:50 UTC by David
Modified: 2008-06-03 20:01 UTC (History)
0 users

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 David 2008-03-10 20:50:36 UTC 
Version:           svn (using Devel)
Installed from:    Compiled sources
OS:                Linux

When you plug in a USB stick, it is notified by the new device notifier, but when you click it, it opens a dolphin window that crashes and gets closed immediatly (but it mounts the stick), you need to open dolphin manually and it does not close.
I don't know if the problem is inside dolphin's code or new device notifier's code, but I can tell that this is probably due to a recent change in SVN code, because I am using SVN since 4.0.0-rc1, and it worked perfectly in the past.

The SVN version affected is >= svn Revision: 783912
Comment 1 David 2008-03-11 19:09:52 UTC 
I realized that I can reproduce this bug with every plasmoid which opens a dolphin window, for example, the trash can plasmoid is affected too with same behavior.
Comment 2 Markus Grob 2008-04-08 00:39:20 UTC 
Could you tell me, if you get this problem in KDE 4.0.3 too? I haven't problems this way. I can open my memorystick with dolphin directly and also with the notifier.
Comment 3 Sebastian Sauer 2008-06-03 20:01:19 UTC 
marked as worksforme since the report was against 4.0.0-rc1 and meanwhile so much got fixed + I am as well not able to reproduce this one. So, let's assume it got fixed.
If anybody is still able to reproduce this one, please reopen the report + provide a backtrace like explained on http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports - thanks in advance :)