GNOME Bugzilla – Bug 500524
Sync tries to load fuse as a module when fuse is built in to the kernel.
Last modified: 2009-10-04 00:48:03 UTC
Please describe the problem: Syncing using the ssh addin checks for the fuse module by looking at the output from lsmod. If fuse is built into the kernel, tomboy does not recognize it. Tomboy will then try to load the fuse module. Syncing does work even if the modprobe command fails. I am using the linux kernel 2.6.23 Steps to reproduce: 1. Obtain a kernel with fuse built in (CONFIG_FUSE_FS=y), and run it. Run tomboy on this kernel. 2. Try to configure syncing over ssh (I didn't try any other methods) 3. Actual results: [DEBUG]: Could not find 'fuse' in lsmod output Dialog Enable FUSE? .... No Yes click no: Error connecting :( click yes: su/sudo modprobe runs, fails, but tomboy is satisfied and will now sync Expected results: Tomboy recognizes the fuse filesystem is available and doesn't try to load the fuse module. Does this happen every time? Yes Other information:
Wow, this sucks, thanks for reporting it.
It should check whether fuse is present in /proc/filesystems instead of checking for module.
Setting the default assignee and QA Contact to "tomboy-maint@gnome.bugs".
Any news on this one? I would love to see this fixed. One remark? Is /proc/filesystems always visible? Wouldn't it be better to just do the sync and then check some things if that failed?
This has been reported downstream in Ubuntu; Jaunty now ships the kernel with FUSE integrated by default, and Tomboy will no longer sync over SSH because it fails to load the FUSE module. Could this please get taken care of, or can someone give me some direction on how/where to fix it myself? Cheers
Sorry, forgot to include the link to the downstream bug report: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/345166
Thanks for the ping on this, maybe we can get it fixed for 0.14.1.
*** Bug 577172 has been marked as a duplicate of this bug. ***
I'm using Jaunty and agree with one of the comments in the downstream report: The original submitter here said syncing still works, but that is not true for me. Syncing does *not* work. The server settings are not saved. Here is the contents of my .tomboy.log. 3/29/2009 10:22:18 AM [DEBUG]: Could not find 'fuse' in lsmod output 3/29/2009 10:22:18 AM [DEBUG]: Could not find 'fuse' in lsmod output 3/29/2009 10:22:19 AM [DEBUG]: User canceled or something went wrong enabling FUSE
The attached patch works for me, against svn tomboy revision 2458. Allows me to use fuse with tomboy on recent ubuntu (beta jaunty 9.04), 32 bit (untested on anything else).
Created attachment 132150 [details] [review] fuse check: look at /proc/filesystems before running lsmod
Created attachment 132154 [details] [review] smaller patch, uses regex instead of running grep in a subprocess. better patch, smaller and not dependant on grep.
Comment on attachment 132154 [details] [review] smaller patch, uses regex instead of running grep in a subprocess. could change the regular expression to be stricter - instead of "fuse" use "nodev[ \t]+fuse" (didn't want to create yet another patch for this)
Thanks guys, sorry for the delay in getting this in. I committed a patch based on alonlevy1@gmail.com's regex patch in bafbfc3 on master. This fix will be in 0.15.1 and 0.14.2.
*** Bug 582600 has been marked as a duplicate of this bug. ***