| Summary: | Gthumb does not find my camera Canon IXUS 220 HS | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Georges Eckenschwiller <paiiou> |
| Component: | RPM Packages | Assignee: | Damien Lallement <mageia> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | Keywords: | Triaged |
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gthumb | CVE: | |
| Status comment: | |||
| Attachments: | Import dialog | ||
|
Description
Georges Eckenschwiller
2014-02-02 21:44:56 CET
Created attachment 4922 [details]
Import dialog
The camera is not seen. Impossible to give an access path towards photos.
When I place the memory of the camera in a reader, I can reach photos: /run/media/georges/CANON_DC/DCIM/100__05/photos
Manuel Hiebel
2014-02-03 16:36:24 CET
Keywords:
(none) =>
Triaged Hello, Does it fail too when launching gthumb from the menu? Can you try with gthumb-3.2.5-1.1.mga4 from updates_testing please? Was it working in the past with Mageia 3? Did you tried with an other software to check that your device is detected? Status:
NEW =>
ASSIGNED (In reply to Damien Lallement from comment #3) Désolé pour le retard. > Hello, > > Does it fail too when launching gthumb from the menu? Yes. The camera is not seen. > Can you try with gthumb-3.2.5-1.1.mga4 from updates_testing please? (gsettins-desktop-schemas is installed as deps) gthumb is lanched, but the camera is not seen. When gthumb is started since a terminal, it starts well, but I always have the following message: Gtk-WARNING : Failed to register client: GDBus.Error: org.freedesktop.DBus.Error.Service.Unknown: The name org.gnome.Session.Manager was not provided by any .service files (The environment is xfce) > Was it working in the past with Mageia 3? Did you tried with an other > software to check that your device is detected? photos import is not working with gthumb mga3 photos import is working with shotwell mga3 and mga4 I have just redone new tests with cauldron: 1/ I connect the camera. 2/ I switch on the device -> It is automatically detected. The import window is opened. But no photo is visible. Buttons are grey. 3/ I close the window of gthumb import. 4/ I open the file manager (Thunar). The device 'Canon Digital' is present, unmonted. 5/ I made the mountage. 6/ I open gthumb import from a terminal gthumb --import-photos) The source of photos is found. Photos are visible. 7/ I click the button Import. A single photo is imported. I have an error message: Impossible d'effectuer cette opération:-1 Erreur indéfinie. 8/ I close the window of gthumb import. I have several lines of error on the terminal. libGL error: failed to createdri screen libGL error: failed to load driver nouveau (gthumb:2688): Gtk-WARNING: failed to register client GDBus.Error: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (gthumb:2688): GLib-CRITICAL: Source ID 312 was not found when attempting to remove it. This line is repeated several times with different ID. I continued to look on the Internet. I found that Gnome mounts automatically a camera, but not Xfce. (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603143) Gthumb supposes that the device already mounted. This explains why gthum do not find it. I tried to add gvfs-mount %d; to the Exec line in gthumb-import.desktop. It did not work. I also found scripts on base of gphoto2 to find the place of the camera. I modified little and here is what I use : #!/bin/bash # Réalisé le 11-05-2014 CAMERA=$(gphoto2 --auto-detect | grep Camera) if [[ -n $CAMERA ]]; then CAMPORT=${CAMERA/*usb/usb} CAMPORT=${CAMPORT%% *} gvfs-mount "gphoto2://[$CAMPORT]/" gthumb --import-photos gvfs-mount -u "gphoto2://[$CAMPORT]/" fi Xfce launches it automatically when the camera is detected. Question Do you have any idea why gvfs-mount %d; do not work ? Finally, the solution is much simpler: It is necessary to add gvfs-gphoto2 as dependence. Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/ Status:
ASSIGNED =>
RESOLVED |