[opensuse] openSuSE 13.1 gtk_file_chooser_dialog_new triggers org.gtk.Private.GPhoto2VolumeMonitor Error?
All, I don't know if this is related to a config issue, a gtk issue or a gphoto2 issue (I think I recall a discussion where this was tagged as a gvfs issue), but whenever gtk_file_chooser_dialog_new is called by an application, I get the following error: Error creating proxy: Error calling StartServiceByName for org.gtk.Private.GPhoto2VolumeMonitor: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.gtk.Private.GPhoto2VolumeMonitor: Success (g-dbus-error-quark, 23) This doesn't have any ill effect on normal file-open file-save operations, but I would like to find a solution or workaround to prevent the error from being thrown. There are a number of search results for variations of this problem, but I have not been able to find the root cause or workaround for the error. I have the following gphoto related packages installed: gphoto-2.5.5-44.1.x86_64 gphotofs-0.5-4.1.2.x86_64 libgphoto2-6-2.5.5-134.2.x86_64 libgphoto2-6-lang-2.5.5-134.2.noarch libgphoto2-devel-2.5.5-134.2.x86_64 Is this a known problem, and if so, is there a workaround that will prevent this error from being triggered? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 9 Dec 2015 06:37, David C. Rankin
All,
I don't know if this is related to a config issue, a gtk issue or a gphoto2 issue (I think I recall a discussion where this was tagged as a gvfs issue), but whenever gtk_file_chooser_dialog_new is called by an application, I get the following error:
Error creating proxy: Error calling StartServiceByName for org.gtk.Private.GPhoto2VolumeMonitor: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.gtk.Private.GPhoto2VolumeMonitor: Success (g-dbus-error-quark, 23)
This doesn't have any ill effect on normal file-open file-save operations, but I would like to find a solution or workaround to prevent the error from being thrown. There are a number of search results for variations of this problem, but I have not been able to find the root cause or workaround for the error.
I have the following gphoto related packages installed:
gphoto-2.5.5-44.1.x86_64 gphotofs-0.5-4.1.2.x86_64 libgphoto2-6-2.5.5-134.2.x86_64 libgphoto2-6-lang-2.5.5-134.2.noarch libgphoto2-devel-2.5.5-134.2.x86_64
Is this a known problem, and if so, is there a workaround that will prevent this error from being triggered?
Short workaround not a real fix: remove /rename this files: /usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service then call and relogin: killall /usr/lib/gvfs/gvfs-gphoto2-volume-monitor or reboot. This is caused by dbus/gvfs, not by an end-user desktop app YMMV - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/08/2015 11:48 PM, Yamaban wrote:
Short workaround not a real fix: remove /rename this files:
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service
then call and relogin: killall /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
or reboot.
This is caused by dbus/gvfs, not by an end-user desktop app
Thank you, If I remove: /usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service won't that mess up gphoto2 ability to connect/download info from phones, cameras, etc? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 9 Dec 2015 07:09, David C. Rankin
On 12/08/2015 11:48 PM, Yamaban wrote:
Short workaround not a real fix: remove /rename this files:
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service
then call and relogin: killall /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
or reboot.
This is caused by dbus/gvfs, not by an end-user desktop app
Thank you,
If I remove:
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service
won't that mess up gphoto2 ability to connect/download info from phones, cameras, etc?
Yes and No. Details: A fresh pluggend in camera or stick will no longer be detected as 'gphoto'-source the moment it connects. But, if you start gphoto yourself you can still start the import function manually. All the action above removes is the automatism to detect devices for import by gphoto automatically. Both files are part of the "gvfs-backends" package. IMHO renameing / moving to other location is a better action than deleteing them. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/09/2015 12:09 AM, David C. Rankin wrote:
Thank you,
If I remove:
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service
won't that mess up gphoto2 ability to connect/download info from phones, cameras, etc?
How is this service ever supposed to work to begin with? /usr/lib/gvfs/gvfs-gphoto2-volume-monitor is a file with permissions set to '0000': $ ls -al /usr/lib/gvfs/gvfs-gphoto2-volume-monitor ---------- 1 root root 94296 Aug 26 2014 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor Then it is supposedly launched by org.gtk.Private.GPhoto2VolumeMonitor.service: $ cat /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service [D-BUS Service] Name=org.gtk.Private.GPhoto2VolumeMonitor Exec=/usr/lib/gvfs/gvfs-gphoto2-volume-monitor Does the heading of [D-BUS Service] supposedly provide the systemd magic to chmod the gvfs-gphoto2-volume-monitor file before it is launched? This certainly looks like there should be an easy fix to make the setup respond without throwing an error. Anybody see any fertile ground here? I also see "Success (g-dbus-error-quark, 23)" at the end of the error string, do you know what that is telling me? I know where the general error handling is coming from -- from https://developer.gnome.org/gio/stable/gio-GDBusError.html, but that page doesn't actually give information on what the error is - a complete `grep 23 /usr/include/glib-2.0/gio/*` doesn't seem to help either.... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 9 Dec 2015 07:34, David C. Rankin wrote:
On 12/09/2015 12:09 AM, David C. Rankin wrote:
Thank you,
If I remove:
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service
won't that mess up gphoto2 ability to connect/download info from phones, cameras, etc?
How is this service ever supposed to work to begin with? /usr/lib/gvfs/gvfs-gphoto2-volume-monitor is a file with permissions set to '0000':
$ ls -al /usr/lib/gvfs/gvfs-gphoto2-volume-monitor ---------- 1 root root 94296 Aug 26 2014 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
Ok, that is wrong. The rights should show: "-rwxr-xr-x" Try a "sudo chmod a+rx,u+w /usr/lib/gvfs/gvfs-gphoto2-volume-monitor" first and look for a repeat of the errormessage after a relogin. (Re-Login bacause of underlaying troubles in dbus, such error-recovery is seldom successfull in active user session) - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Dec 09, 2015 at 09:15:09AM +0100, Yamaban wrote:
On Wed, 9 Dec 2015 07:34, David C. Rankin wrote:
On 12/09/2015 12:09 AM, David C. Rankin wrote:
Thank you,
If I remove:
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service
won't that mess up gphoto2 ability to connect/download info from phones, cameras, etc?
How is this service ever supposed to work to begin with? /usr/lib/gvfs/gvfs-gphoto2-volume-monitor is a file with permissions set to '0000':
$ ls -al /usr/lib/gvfs/gvfs-gphoto2-volume-monitor ---------- 1 root root 94296 Aug 26 2014 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
Ok, that is wrong. The rights should show: "-rwxr-xr-x"
Try a "sudo chmod a+rx,u+w /usr/lib/gvfs/gvfs-gphoto2-volume-monitor" first and look for a repeat of the errormessage after a relogin.
(Re-Login bacause of underlaying troubles in dbus, such error-recovery is seldom successfull in active user session)
This likely was an intentional change, to allow other gphoto2 apps that do not use gphoto2 to work and not to block. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/10/2015 04:08 AM, Marcus Meissner wrote:
On Wed, Dec 09, 2015 at 09:15:09AM +0100, Yamaban wrote:
On Wed, 9 Dec 2015 07:34, David C. Rankin wrote:
On 12/09/2015 12:09 AM, David C. Rankin wrote:
Thank you,
If I remove:
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor /usr/share/dbus-1/services/org.gtk.Private.GPhoto2VolumeMonitor.service
won't that mess up gphoto2 ability to connect/download info from phones, cameras, etc?
How is this service ever supposed to work to begin with? /usr/lib/gvfs/gvfs-gphoto2-volume-monitor is a file with permissions set to '0000':
$ ls -al /usr/lib/gvfs/gvfs-gphoto2-volume-monitor ---------- 1 root root 94296 Aug 26 2014 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
Ok, that is wrong. The rights should show: "-rwxr-xr-x"
Try a "sudo chmod a+rx,u+w /usr/lib/gvfs/gvfs-gphoto2-volume-monitor" first and look for a repeat of the errormessage after a relogin.
(Re-Login bacause of underlaying troubles in dbus, such error-recovery is seldom successfull in active user session)
This likely was an intentional change, to allow other gphoto2 apps that do not use gphoto2 to work and not to block.
Ciao, Marcus
Yambam, Marcus,
Thanks for your help. If I understand the state of the discussion, we have
isolated (1) a workaround and, (2) several open/unresolved issues regarding why
this error is being thrown to begin with:
(1) removing the following 2 files will prevent the error from being thrown, but
also remove/eliminate media autodetect for import by gphoto apps; and
(2)
(a) gvfs root cause of the error -- why is it generated?;
(b) permissions of '0000' on /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
Is this the case on 13.2 and Leap? If so, do we need to open a bug so this can
be worked/fixed? If so, what component to open the bug under? (gvfs, dbus, etc.?)
<< For those interested in testing on 13.2 or Leap: >>
You can compile/test on your system by compiling the following. You will need
the appropriate version of either:
gtk2-devel and libgtk-2_0-0
or
gtk3-devel and libgtk-3_0-3
along with 'pkg-config' installed.
The compile string for GTK+2 and GTK+3 using pkg-config are shown below. (all
one line, '\' is simply a line continuation. You can copy/paste both linees,
including the line continuation into your terminal after saving the file in the
proper filename):
GTK+2:
gcc -Wall -Wextra -O3 -o filechooser filechooser.c \
$(pkg-config --cflags --libs gtk+-2.0)
GTK+3:
gcc -Wall -Wextra -O3 -o filechooser filechooser.c \
$(pkg-config --cflags --libs gtk+-3.0)
(ignore: -Wdeprecated-declarations warning for STOCK items with GTK+3)
Just save the following in a text file, say filechooser.c, open konsole,
gnome-terminal or xterm, and issue the appropriate compile string for gcc:
#include
participants (3)
-
David C. Rankin
-
Marcus Meissner
-
Yamaban