GNOME Bugzilla – Bug 717109
Unable to use file manager or play video
Last modified: 2013-05-01 06:47:00 UTC
---- Reported by shotwell-maint@gnome.bugs 2011-02-13 06:51:00 -0800 ---- Original Redmine bug id: 3183 Original URL: http://redmine.yorba.org/issues/3183 Searchable id: yorba-bug-3183 Original author: Petetr - Original description: One of my systems is running mint 10 and Shotwell version 8.1 and I am unable to go to file manager or play video. I right click on photo and choose “show in file manager†and nothing happens. On my other systems running mint 10 and ubuntu 10.10 all works ok. I enclose the related files generated by starting Shotwell and then choosing to go to file manager. ---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:47:00 -0700 ---- ### History #### #1 Updated by Adam Dingle almost 3 years ago * **Target version** deleted (<strike>_0.8_</strike>) stonecot, if you open a terminal window and run Shotwell from there, then does any output appear in the terminal when you attempt to go to the file manager or play a video? #### #2 Updated by Petetr - almost 3 years ago From a terminal, trying for File Manager produces no output. Trying to play a video produces Error 3 running “~/Desktop/avi2mpeg.rexxâ€: Failure during initialization Error 3.1: Failure during initialization: Program was not found #### #3 Updated by Petetr - almost 3 years ago Now OK on video. I had an incorrect file association set up for .avi files. Now corrected. However I still have the problem when trying to use the file manager and, unfortunately, there is no error message displayed in the terminal window. #### #4 Updated by Petetr - almost 3 years ago I am still not getting anywhere in resolving this problem. I have rerun your procedure to regenerate the gdb trace and log file. I've annotated the trace to show the point art which the problem occurs and it is where the threads are exited. Any clues would be appreciated. #### #5 Updated by Adam Dingle almost 3 years ago * **Status** changed from _Open_ to _5_ * **Resolution** set to _worksforme_ * **% Done** changed from _0_ to _0_ stonecot, When you ask to view a photo in the file manager, Shotwell simply asks GTK to launch the default application registered for displaying directories. Usually this should be Nautilus. To debug, first install the xdg-utils package. (That's a package in Ubuntu, at least; I hope it's also available in Mint). Then run this command: $ xdg-mime query default inode/directory What does it print? It should say “nautilus-folder-handler.desktopâ€. If it says something else, then a different application is registered as handling directories on your machine. The GNOME System Administration Guide describes how applications are registered to handle MIME types – see http://library.gnome.org/admin/system-admin-guide/stable/mimetypes- registering.html.en If you read and understand that guide then that may help you understand the misconfiguration. I'm marking this ticket as worksforme since I think the problem is almost certainly related to the configuration on your own machine. I'm happy to continue corresponding to help you debug this, however. #### #6 Updated by Petetr - almost 3 years ago I had installed and done this some time ago and it comes back as nautilus- folder-handler.desktop – however I had not pursued it – Idiot that I am. Pleased to say that was the answer, so I can now view my folders. Thanks once again. #### #7 Updated by Adam Dingle almost 3 years ago Great – glad you figured it out! #### #8 Updated by Charles Lindsay 7 months ago * **Status** changed from _5_ to _Invalid_ --- Bug imported by chaz@yorba.org 2013-11-25 21:49 UTC --- This bug was previously known as _bug_ 3183 at http://redmine.yorba.org/show_bug.cgi?id=3183 Imported an attachment (id=261899) Imported an attachment (id=261900) Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.