It's actually not clear that the gmtp bug is invalid.
gmtp uses a particular set of libmtp API calls that aren't functionally compatible with Android 4.x devices. libmtp has a separate set of calls that are compatible (these are what go-mtpfs and my gvfs mtp backend use). So, gmtp would need to be updated to use these different set of calls before it will ever work, unless the libmtp authors decide to reimplement the broken calls in terms of the working ones, which is theoretically possible, but, I think, unlikely.
It's actually not clear that the gmtp bug is invalid.
gmtp uses a particular set of libmtp API calls that aren't functionally compatible with Android 4.x devices. libmtp has a separate set of calls that are compatible (these are what go-mtpfs and my gvfs mtp backend use). So, gmtp would need to be updated to use these different set of calls before it will ever work, unless the libmtp authors decide to reimplement the broken calls in terms of the working ones, which is theoretically possible, but, I think, unlikely.