QRecallDownloadIdentity KeysForumsSupport
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Groups] Back to home page 
Capture issues: Unable to read extended attribute data  XML
Forum Index » Problems and Bugs
Author Message
Steven M. Alper



Joined: 05-Mar-07 08:09
Messages: 51
Offline

Hi, James.

I was just guessing. This may have nothing to do with it: I did grant full disk access, but had this issue. So I restarted and tried again. Same issue. Removed permission, exited Preferences and then re-granted access. Same issue. Deleted QRecall from the Full Disk Access preference, then re-added. No luck. (QRecall had been asking me to grant permission every time I launched it. I click the don't nag box.)


Should I not worry about this and learn to live with the yellow light on that archive?

On another note, is there any chance you could teach the Monitor and Status Windows to remember their positions and which monitor to appear on?

Many thanks,

--

Steven M. Alper
James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1434
Online

Steven,

First of all, Full Disk Access does not (it turns out) solve the access issues with regards to Mojave's sandboxing. The limitation is that Full Disk Access only applies to user processes running in your login session; QRecall runs as root outside your login session, and thus can't be granted Full Disk Access.

The solution was to switch to using APFS snapshots. QRecall can now make a hidden snapshot of your APFS volume and capture that. This (a) creates much more stable captures and (b) gets around the sandboxing issues.

So if you're encountering sandbox restrictions then you either aren't running the latest QRecall or your home folder is not on an APFS volume.

Start by making sure your QRecall is up-to-date. If you've relocated your home folder to a different volume, covert it from HFS+ to APFS (you can do this in the Disk Utility app and it doesn't require erasing your volume, although you'll probably need to do this from a different user or boot from an alternate partition).

Finally, QRecall should not be repeatedly asking you for authorization. If it's reporting that it is not authorized and it should be, then there's something wrong with your installation. Send a diagnostic report and we'll see if we can figure out what.

But here's something to try first. For some reason, the /Library/PrivilegedHelperTools/com.qrecall.hoist get's "stuck" (for lack of a better description). It isn't the right version, but macOS doesn't prompt you to install a new one. Try deleting that file, restart, then launch QRecall again. With any luck, it should ask to authorize and install the proper helper. If it doesn't, go into settings and tell it to use authorization.

- QRecall Development -
[Email]
Steven M. Alper



Joined: 05-Mar-07 08:09
Messages: 51
Offline

Well, my QRecall is now up to date (what, did you drop a new version after I posted? ;0)

I recently moved to a new computer, which is when the pestering to give authorization began. The disk is (and was) AFPS. Is there a way to reset the warning db's to see if QRecall still wants authorization? (Code 42 told me there was no way for Crashplan to know if I've granted permission, so I should click the don't-bug-me-anymore button; that's why I did it with QRecall.) Should I do that before I delete /Library/PrivilegedHelperTools/com.qrecall.hoist ?

Thanks, James.



--

Steven M. Alper
James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1434
Online

I would suggest opening the QRecall app, go to Preferences > Authorization, and see if the Capture and recall items using administrative privileges option is checked. If it is, then you're probably OK. (Most likely, the upgrade managed to successfully replace the privileged helper.)

If this isn't checked, try checking it. Then count to 10, quit QRecall, relaunch, and see if it's still checked. If it is, again everything is likely just fine.

If it isn't, or you get another message that you need to authorize, then we've got an issue. Try deleting the com.qrecall.hoist binary, restart, and try those steps again. Follow that up with a diagnostic report and we'll dig deeper.

- QRecall Development -
[Email]
Steven M. Alper



Joined: 05-Mar-07 08:09
Messages: 51
Offline

Before deleting anything, I installed the update and did a safe mode startup and restart. Since then, all appears well.

Best wishes,

--

Steven M. Alper
 
Forum Index » Problems and Bugs
Go to:   
Powered by JForum 2.1.8 © JForum Team