Bug 299343 - Dolphin Can't See or Mount Nikon D 7000
Summary: Dolphin Can't See or Mount Nikon D 7000
Status: RESOLVED DUPLICATE of bug 297734
Alias: None
Product: solid
Classification: Unmaintained
Component: libsolid (show other bugs)
Version: 4.8.2
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
: 298586 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-05-04 06:42 UTC by swapnil bhartiya
Modified: 2013-03-14 02:11 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description swapnil bhartiya 2012-05-04 06:42:34 UTC
When I connect my Nikon D7000 DSLR or Galaxy Nexus phone via USB neither I get a notification that devices are connected nor the devices appear in side panel of Dolphin. I had to install Nautilus to be able to access my hardware. Additionally, I think Dolphin should show the connected devices in the side panel for the ease of average users.

KDE 4.8.2
OSes openSUSE 12.1 and Kubuntu 12.04

Reproducible: Always

Steps to Reproduce:
1. Connect Galaxy Nexus or Nikon D 7000
2. No notification pop-up
3. Devices don't show up in Dolphin's side panel.


Expected Results:  
Connected devices should appear in Dolphin just the way they apper in Nautilus, Thunar etc.
Comment 1 Lukáš Tinkl 2012-05-31 12:17:58 UTC
AFAIK Galaxy Nexus doesn't provide USB mass storage access
Comment 2 Alex Fiestas 2012-05-31 21:21:25 UTC
well, but we do have kio-mtp and kio-ptp, this should work...

there is another bug like this one but I can't find it right now.
Comment 3 Peter Penz 2012-06-07 18:23:49 UTC
*** Bug 298586 has been marked as a duplicate of this bug. ***
Comment 4 Lukáš Tinkl 2013-02-24 20:59:38 UTC
With KDe 4.8.2... I doubt it, does Kubuntu even provide it?
Comment 5 Alex Fiestas 2013-02-27 16:32:44 UTC
Set in libsolid for the detection part, once that's fixed we can fix the mounting.
Comment 6 Alex Fiestas 2013-03-14 02:11:27 UTC

*** This bug has been marked as a duplicate of bug 297734 ***