Opened 5 years ago

Closed 5 years ago

#58559 closed defect (fixed)

osxfuse @3.9.0 - mount_osxfuse: the loaded OSXFUSE kernel extension has a mismatched version

Reported by: rjderosa (Robert De Rosa) Owned by: saagarjha (Saagar Jha)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: drkp (Dan Ports), neurodroid (Christoph Schmidt-Hieber), michaellass (Michael Lass)
Port: osxfuse

Description

Upgraded osxfuse to 3.9.0 on macOS Mojave (10.14.5) and can no longer mount anything via sshfs. 

mount_osxfuse: the loaded OSXFUSE kernel extension has a mismatched version

Tried uninstalling, cleaning, and reinstalling (with restarts in between) with no success.

Change History (9)

comment:1 Changed 5 years ago by rectalogic (Andrew Wason)

Same here (via encfs) 

mount_osxfuse: the loaded OSXFUSE kernel extension has a mismatched version
fuse failed.  Common problems:
 - fuse kernel module not installed (modprobe fuse)
 - invalid options -- see usage message

$ sudo kextstat
[...]
  188    0 0xffffff7f85a58000 0x19000    0x19000    com.github.osxfuse.filesystems.osxfuse (3.9.0) 37656B90-B9D6-3ECB-8E7F-73750B6E1169 <8 6 5 3 1>

Unloading sudo kextunload -b com.github.osxfuse.filesystems.osxfuse then uninstalling osxfuse and encfs, cleaning, reinstalling and rebooting does not help

comment:2 Changed 5 years ago by jmroot (Joshua Root)

Cc: drkp added
Owner: set to saagarjha
Port: osxfuse added
Status: new → assigned
Summary: 3.9.0 - mount_osxfuse: the loaded OSXFUSE kernel extension has a mismatched version → osxfuse @3.9.0 - mount_osxfuse: the loaded OSXFUSE kernel extension has a mismatched version

comment:3 Changed 5 years ago by neurodroid (Christoph Schmidt-Hieber)

Cc: neurodroid added

comment:4 Changed 5 years ago by pftbest (Vadzim Dambrouski)

Is there some work around for this?

comment:5 Changed 5 years ago by saagarjha (Saagar Jha)

I just spun up a new macOS 10.14.5 install to test this and I can reproduce the bug you guys are seeing. I'm not sure why this worked for me at the time and then stopped working now, but I do see that the GitHub releases page ​https://github.com/osxfuse/osxfuse/releases seems to now be missing sources for the new versions. Perhaps there was some mixup, as the commits for the subprojects didn't seem to change when I updated the port? I'm not sure how to to proceed here: maybe we could to go back to 3.8.3 until we can figure out how upstream is managing their updates?

comment:6 Changed 5 years ago by michaellass (Michael Lass)

Cc: michaellass added

comment:7 Changed 5 years ago by rjderosa (Robert De Rosa)

Reverting to a version that works seems sensible.

comment:8 Changed 5 years ago by saagarjha (Saagar Jha)

For those wondering what the holdup is, I'm waiting to recreate a machine to test the old version to make sure it builds and that I reverted the change correctly. If anyone wants a fix now, the code's in my fork: ​https://github.com/saagarjha/macports-ports/tree/osxfuse; otherwise I'll be making a pull request shortly.

comment:9 Changed 5 years ago by saagarjha (Saagar Jha)

Resolution: → fixed
Status: assigned → closed

In d6ec67cfe16756e607fcf5a53bcc345bf05cbdc3/macports-ports (master):

osxfuse: Revert to 3.8.3

3.9.0 doesn't seem to install properly, and the release's backing commit
on the osxfuse GitHub repository has disappeared, which makes
ascertaining how to build/fix this impossible. Downgrading back to the
last known good version.

Closes: #58559

Note: See TracTickets for help on using tickets.