Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Catalina. Any effort to make QS compatible with it? #2497

Closed
juanfal opened this issue Jun 27, 2019 · 28 comments
Closed

Catalina. Any effort to make QS compatible with it? #2497

juanfal opened this issue Jun 27, 2019 · 28 comments

Comments

@juanfal
Copy link

juanfal commented Jun 27, 2019

For questions or tech support, please start with the users’ group. If you know the problem is in Quicksilver itself, report it here.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

What version of macOS?

What version of Quicksilver?

@juanfal
Copy link
Author

juanfal commented Jun 27, 2019

Catalina, MacOS 10.15 beta, rejects many of QS plugins as no from recognised developers. Funnily some keyboard shortcuts still work, others not. No sense for me. Of course, other System triggers, like "change location" when starting up, do not work at all anymore. Sad, very sad. I couldn't live without QS after these many many years using so intensely!

It says (and repeat through alerts, as many times as you eventually need to quit QS)

 com.blacktree.Quicksilver.QSEventTriggersPlugIn.73.qsplugin

comes from an unidentified developer

@juanfal
Copy link
Author

juanfal commented Jul 2, 2019

Desperately trying to recompile sources, XCode raises the error:
Unable to resolve build file: XCBCore.BuildFile (Named reference 'FMDB.framework' cannot be resolved)
Ive tried to find the link, whatever, no luck.

@juanfal
Copy link
Author

juanfal commented Jul 2, 2019

It seems I've found a way to avoid the problem con QSEventTriggers plugging:

I've manually taken off the file:
/Users/me/Library/Application Support/Quicksilver/PlugIns/com.blacktree.Quicksilver.QSEventTriggersPlugIn.73.qsplugin
and then, from the Quicksilver plugins panels, installed Event Triggers

The problem seems solved

@tiennou
Copy link
Member

tiennou commented Jul 2, 2019

It seems Catalina introduced new codesigning checks when loading bundles (a.k.a plugins).

This is going to be as messy as it can get, as IMHO it entails reworking how the build is done, because /tmp/QS was a good idea 15 years ago, but now I think it's an impediment to having plugins codesigned.

Please realize that unless someone stepped up most if not all plugins are still using manual memory management, most of the things we do with aliases and resources forks have been deprecated for like 4 OS releases, most of our frameworks predate the "modular framework", so Xcode will now also complain about these when headers are missing.

I'll try to bash the Xcode projects into something that could handle that (been there, done that 🤣), but I'm not even sure it's a worthy goal: Another (hopefully easier) way would be to just stop frameworking (keeping the distinction as "source file location"), dump everything inside Quicksilver.app, and move along.

@skurfer
Copy link
Member

skurfer commented Jul 2, 2019

I’ve switched plug-ins to ARC as I touch them, but that probably includes 10 or less. So, code-signing the plug-ins isn’t an option? I haven’t tried it.

I’d be fine with just moving everything into the app if we had to. It’s not like we ever get any outside contributions. 😒

@devburke
Copy link

devburke commented Jul 17, 2019

Just checking in here. My programming knowledge is far too basic to contribute to any actual development, but just trying to get a sense of whether QS is falling back into the grave. I've noticed the LoveQuicksilver Twitter account has fallen silent. It's certainly fair if it has, it takes work to keep things running, and y'all are working for free, but I'll mourn the day when after over a decade I'll have to move on.

On that note, I'm making a donation now. I don't mean that to imply that work should continue because of my one small donation, it certainly wouldn't pay for very many minutes of a single coder's time, but after all the use I've gotten out of it, just seemed like I should donate.

@skurfer
Copy link
Member

skurfer commented Jul 17, 2019

I can only speak for myself, but Catalina doesn’t seem to run well in a VM and I only have one Mac, so I haven’t been able to check things out there yet.

@devburke
Copy link

devburke commented Jul 17, 2019

@alvarotrigo
Copy link

alvarotrigo commented Oct 8, 2019

Catalina is now out here!
Unfortunately I also noticed Quicksilver not working as expected. When for example looking for the "terminal.app" or "textedit.app".

However, it seems to be working with other folders and apps, which is a bit random.

Any news on this regard?

@pbx
Copy link

pbx commented Oct 9, 2019

I'm having a new issue under Catalina (10.15.0) that may be QS, though it may be Emacs.app.

In short, I cannot open Emacs.app (v26.1) via QS (v1.6.0) if it is already running.

Steps to reproduce:

  1. Launch Emacs.app
  2. Select the app in the left (item) pane and "Open" in the right (action) pane; hit Return
  3. Note that QS hides itself in the usual way but the app doesn't launch, and you're returned to the app that was foreground when you invoked QS.

Opening by trigger also silently fails.

Note -- if Emacs.app is not running, the above steps will launch it, but still fail to activate it thereafter.

All other apps I've tried can still be launched in the usual way.

@juanfal
Copy link
Author

juanfal commented Oct 10, 2019

@alvarotrigo
Copy link

alvarotrigo commented Oct 15, 2019

It needed some refreshing of the triggers…

What do yo mean by that? Can you open "Terminal" app? Or "textEdit" with it?

@alvarotrigo
Copy link

alvarotrigo commented Oct 15, 2019

For some reason the "TextEdit.app" is not in the list of scanned files by Quicksilver on the Catalog > Applications > Sources.

Screenshot 2019-10-15 at 14 36 34

However, it is there in the applications directory next to all the others shown the list.
Screenshot 2019-10-15 at 14 38 16

It happens as well with "Time machine" or "TV.app".
Interesting how TV.app is found when using Quicksilver but not under /Applications/ but under /System/Applications/ instead.

@juanfal
Copy link
Author

juanfal commented Oct 17, 2019

@alvarotrigo
Copy link

alvarotrigo commented Oct 17, 2019

started begging for help and so. Then I refreshed the location of each app, opening the trigger in QS and drag-dropping the app icon on it again… one by one…

Refreshed the location? where? The Catalog already contains the Applications folder:
image

What triggers? I do not use triggers. I just want QS to guess what I want to open when I start typing.

@skurfer
Copy link
Member

skurfer commented Oct 17, 2019

I’m guessing he had triggers that referred to /Applications/Some.app, and that application was moved to /System/Applications/Some.app. In that case, triggers and other references to the application will need to be updated.

@juanfal
Copy link
Author

juanfal commented Oct 21, 2019

@codeanpeace
Copy link

codeanpeace commented Nov 26, 2019

I recently updated to Catalina (10.15.0) and, much to my dismay, discovered that "Go To Here" action no longer works.

Steps to reproduce:

  • Select a folder in the first pane
  • Select "Go To Here" in the second pane
  • Hit return
  • See message "Quicksilver is not allowed to send keystrokes." in the first pane

Additionally, I can no longer use the clipboard plugin and can't re-install it – checking the box in the preferences does not actually install it, it does say installing in the bottom right of the window.

Any help would be most appreciated!

@juanfal
Copy link
Author

juanfal commented Nov 26, 2019

Ive QS as one of the allowed Automatización (sorry, I don't know the word in the English system) Preference Pane:
Captura de pantalla 2019-11-26 a las 10 53 19

@skurfer
Copy link
Member

skurfer commented Nov 26, 2019

"Quicksilver is not allowed to send keystrokes.”

The OS probably asked for your permission the first time you used this, but the dialog might have been behind the QS interface, and it tends to not ask again. Try allowing Automation and Full Disk Access in the security preferences.

Additionally, I can no longer use the clipboard plugin and can't re-install it – checking the box in the preferences does not actually install it, it does say installing in the bottom right of the window.

This is due to a problem with the qsapp.com domain. I’m working with our registrar to sort it out.

@alvarotrigo
Copy link

alvarotrigo commented Nov 26, 2019

Quicksilver just doesn't work well after updating to Catalina.
I haven't yet been able to solve my problem trying to quickly access my apps, such as Calendar, Disk Utility, TextEdit etc.

It is all messed up after the update and quicksilver won't find them.

@codeanpeace
Copy link

codeanpeace commented Nov 26, 2019

"Quicksilver is not allowed to send keystrokes.”

The OS probably asked for your permission the first time you used this, but the dialog might have been behind the QS interface, and it tends to not ask again. Try allowing Automation and Full Disk Access in the security preferences.

Additionally, I can no longer use the clipboard plugin and can't re-install it – checking the box in the preferences does not actually install it, it does say installing in the bottom right of the window.

This is due to a problem with the qsapp.com domain. I’m working with our registrar to sort it out.

Good catch, I now have given QS access to Automation, Full Disk Access, Accessibility, etc. but am still running into the same issue after relaunching QS. Is a complete reboot necessary? Thanks!

@juanfal
Copy link
Author

juanfal commented Nov 26, 2019

I've been working with Catalina (betas, even, and they drove me crazy! last time I do it), but now I'm working with QS without a glitch, no new glitches, at least.

@wmertens
Copy link
Contributor

wmertens commented Dec 3, 2019

@juanfal did you build your own? Do you also have the problem that when you Toggle Visibility of an app via a shortcut, it is delayed by several seconds? (I have this in Mojave)

@wmertens
Copy link
Contributor

wmertens commented Dec 3, 2019

nevermind, I re-installed from the website and it's behaving well now.

@wmertens
Copy link
Contributor

wmertens commented Dec 4, 2019

actually, I cried victory too soon - it's still happening. Maddening.

@juanfal
Copy link
Author

juanfal commented Dec 4, 2019

@wmertens, what's the problem you have? Hiding an application is ⌘-H, or the not in front, ⌥-⌘-H, so, I understand you want to hide/unhide a specific application, don't you?

@skurfer
Copy link
Member

skurfer commented Dec 4, 2019

The problem with the trigger delays might be fixed with the latest code here, but it hasn’t made it into a release yet.

@skurfer skurfer closed this as completed Jul 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants