Jump to content

KickMeElmo

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

KickMeElmo's Achievements

Member

Member (2/3)

0

Reputation

  1. Ah bugger, missed that. Are you running over a USB C port? I've seen issues on some systems with certain communication types over those ports. Especially thunderbolt ports.
  2. Pretty sure the group you need to be part of is plugdev. I'm on Mint 19.3 and have no issue, but I'm part of that group for a wide variety of things, so I wouldn't have been directly aware if this specifically required it. Just verified that I can connect fine on the latest build, just to be certain.
  3. SP27 also appears to have resolved the prior issues requiring retention of an old version of mono. I have it running cleanly on mono 6.12.0.122. All functionality appears intact, including a device firmware update. Very nice, thank you.
  4. We're going to have to agree to disagree on that one. While a Windows VM works, it's also inviting a pile of headaches. Do what you find best for you, but you couldn't pay me to use that solution. For the average user, the easiest solution is likely downgrading system mono to a working version and holding the package. For the power user, a secondary mono installation shouldn't be that difficult to set up, and requires zero maintenance once set up.
  5. So I finally got around to building a separate version of mono just for escribe, and I can confirm it works fine. For anyone else in the same boat who can't afford to downgrade system mono, start here and install mono-5.18.1.0 and gtk-sharp-2.12.45. Other versions of GTK sharp would undoubtedly work, but that's what I installed and it works fine. Then edit ~/.local/opt/evolv/escribe-suite/launch-escribe-suite and change "exec mono" to wherever your newly installed secondary mono is. Assuming you just used /opt/mono as a prefix, it'd be "exec /opt/mono/bin/mono". Thanks to blueridgedog for the tip.
  6. Ah, then sadly not anything new. That's basically the last known working version for escribe, it's an old version. Good solution for people who don't use mono for other things, but for those of us on mono 6.4, doesn't really help. That said, the parallel mono installations should be a viable solution, I just haven't had time to get that set up yet.
  7. What mono version? Use `mono --version` to check.
  8. I haven't really had time to look at it myself beyond a basic search (which went nowhere), but does anyone know if it's possible to have a separate mono version just for escribe? I have far too many things reliant on mono to downgrade, but I'd have no issue keeping multiple versions around.
  9. Just to add my own two cents, I'm experiencing the same thing on Mint 19 with Mono JIT compiler version 5.20.1.19. In my case, the Escribe launcher will start fine, device monitor crashes out immediately with SIGABRT, and Escribe itself does the same but leaves a small empty window behind for the user to kill manually. Unfortunately in my case I use mono for a number of other things, so rolling back won't be an option. Crash log attached. escribe_crash.txt
×
×
  • Create New...