Date: Tue, 14 Feb 2017 05:57:14 +0100 From: Matthias Petermann <matthias@petermann-it.de> To: freebsd-questions@freebsd.org, ports <freebsd-ports@freebsd.org> Subject: devel/tevent: upgrade from 0.9.28 -> 0.9.31 causes gvfs-mount fail for smb shares, affects also x11-fm/thunar, x11-fm/pcmanfm, x11-fm/nautilus, x11-fm/caja Message-ID: <0722f2f8-3b02-1976-493c-8f1a95716d3c@petermann-it.de>
next in thread | raw e-mail | index | archive | help
Good morning, in early February I had experienced a particular issue related to gvfsusing pkgs from my custom pkg repository (closely tracks head). Some day, x11-fm/thunar and x11-fm/pcmanfm were no longer able to access Samba shares. I did reproduce the issue in an isolated environment (a VM with only FreeBSD base + dbus and gvfs pkgs installed) and was able to reproduce the issue on the command line. # kldload fuse # chmod a+rw /dev/fuse # service dbus onestart With tevent 0.9.28: % dbus-launch csh % gvfs-mount smb://WORKGROUP\;mpeterma@proliant/public % gvfs-mount -l Mount(0): public on proliant -> smb://WORKGROUP;mpeterma@proliant/public/ Type: GDaemonMount (Ok, expected good behavior) With tevent 0.9.31: % dbus-launch csh % gvfs-mount smb://WORKGROUP\;mpeterma@proliant/public (waiting forever..., unexpected bad behavior) With this findings I submitted a bug report[1], currently still in New state with no public visible progress. I am wondering what I could do. Since keeping the 0.9.31 version in ports will make it part of the next quarterly release, I fear a majority of users will recognize the problem then. Best regards, Matthias [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216230 -- Matthias Petermann <mp@petermann-it.de> | www.petermann-it.de GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572 C3D7 7B1D A3C3 5C3E 6D75
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0722f2f8-3b02-1976-493c-8f1a95716d3c>