Bug 296302 - Connect foto camera canon eos60d but does not recognize
Summary: Connect foto camera canon eos60d but does not recognize
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kamera (show other bugs)
Version: 1.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Marcus Meissner
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-03-18 19:33 UTC by stropeo
Modified: 2018-10-27 02:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stropeo 2012-03-18 19:33:56 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.34 (KHTML, like Gecko) rekonq Safari/534.34
Build Identifier: 

When I connect the foto camera Canon EOS 60D to pc with kubuntu they say if "to opern its" with Dolphins or Gwenview applications. When I select application then I get "runtime error 150" and does not open anything.

Reproducible: Always

Steps to Reproduce:
1.connect the camera to usb port
2. wait to tell me with what I want to open the camera application
3.scelgo o Dolphins o Gwenview
4. wait a long time and then I get the error message:  run time 150
5, stop
Actual Results:  
nothing

Expected Results:  
?
Comment 1 Marcus Meissner 2012-03-18 21:51:09 UTC
can you try import from gwenview directly and see if that works?
Comment 2 Christian Butcher 2015-09-28 04:23:51 UTC
Hi - firstly, does this still affect you?

Secondly, Error 150 in gphoto2 (the library used by kamera to open cameras) refers to a permissions error. If you run Dolphin/Gwenview as root (say, with kdesu), does the same error occur?

It sounds likely that you have/had a problem with session management or permissions assignment - my ConsoleKit(2) is sometimes giving me a similar issue, I expect due to a bad configuration on my part of CK2.

If Kamera works as root, then the problem is afaik not with Kamera, but with whatever assigns your permissions. You could take a look at bug 264020 (https://bugs.kde.org/show_bug.cgi?id=264020) and see if that helps at all. Bug 264020 is closed as 'Resolved Downstream', so I'm hopeful if it's the same issue then the same fix will have made its way to Ubuntu packages
Comment 3 Andrew Crouthamel 2018-09-25 21:52:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 02:19:02 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!