Ulauncher v6

[friday]

This is a tracking issue for the upcoming v6 release that we have been working hard on. Subscribe to this issue to be notified of the v6 development, as we are closing issues as they get fixed for the v6 branch (now the main branch).

What has been done

1. Lots of refactoring, and rewrites to internal parts of Ulauncher that caused bugs, inconsistencies, performance issues, or were holding us back from fixing issues, adding features or just made it very hard to work with Ulauncher in general. We got rid of a total of 7 dependencies (in the Debian package). It's faster and lighter on your system resource usage, because of taking better advantage of the fast and capable GTK APIs, Unix sockets, and many smaller performance improvements. It's also significantly easier to build and contribute to Ulauncher now as well. These changes are too many and too complex to detail here. git diff --shortstat as of writing this says 545 files changed, 11479 insertions(+), 29372 deletions(-)
2. Many Extension API improvements to make it easier to write extensions with less code (more on this TBA).
3. Lots of other smaller improvements and bug fixes.
4. Removed a couple of features that were causing more issues than they solved, and changed the behavior of some others to be more intuitive, performant, compatible or to work enable planned future changes.

To test Ulauncher v6, follow the instructions to set up and run.

To see what else is planned, see the: milestone (note that the milestone is subject to change, incomplete and doesn't include smaller things like updating our documentation, website and extension website).

Ulauncher application changes

• BREAKING: Dropped support for Python versions older than 3.7.
• BREAKING: Dropped support for GTK+ versions older than 3.22.
• BREAKING: Replaced the previous hotkey binding library (X11 only) with custom desktop environment wrappers for Gnome, Elementary and Budige, XFCE and KDE/Plasma, and instructions in the preferences window for other desktops. feat: replace keybinder with DE-wrappers #1256 fa16d93 4570ba4
• BREAKING: Changed the functionality of the "jump keys" to select, but not launch the item (Change the functionality of the "jump keys" to select, but not launch the item #965)
• BREAKING: "Launch at Login" is now re-implemented using systemd instead of XDG autostart (Make "Launch at Login" wrap systemd instead of XDG autostart #808)
  • The --hide-window CLI option is now renamed to --daemon. --hide-window is now an invalid option that will cause Ulauncher not to start. This is so that old XDG autostart files won't be conflicting with the new implementation (6f39063).
• BREAKING: Removed "Blacklisted Apps Dirs" feature. This was previously needed mostly for performance reasons because we were monitoring desktop application entries (we we no longer need to do that as of Remove "Blacklisted App Dirs" option #834). Let us know though if you find after having tested Ulauncher v6, that you still need this setting.
• Ulauncher is now a implemented as a dbus activatable single instance (SingleMainWindow) GTK.Application instead of separate windows and DBus listeners, and as a result of this ulauncher-toggle is just a wrapper around gapplication launch io.ulauncher.Ulauncher (Switch to Gtk.Application and make ulauncher command "toggle" by default #988, feat: dbus activatable #1164, d90b89f and many more)
  • These changes fixes the issues with focus stealing that previously required an workaround that only worked for X11 and was still unreliable Fix for Ulauncher dialog not getting keyboard focus #1128
  • This in turn also changed the ulauncher-toggle command to always activate the window, rather then actually toggling it.
• The fuzzy search logic and the highlighter is now rewritten to use a new internal method to get matching blocks (using python-Levenstein), which is both faster and much better than before (fuzzy matching rewrite using new function get_matching_blocks() #827 and de1cd32).
  • We now also strip accents (diacritics) before fuzzy searching (Strip accents (diacritics) before fuzzy searching #855)
  • Search now also includes the app description (a.k.a the "comment" field in the desktop entry files) (Search now also searches app descriptions, albeit with lower priority #938) and keywords (Include keywords when searching for application. #1012)
  • Results are also slightly weighted by launch count, to favor your commonly launched apps feat(search): weight apps by launch count #1175
• Ulauncher now uses the GTK APIs to fetch the desktop apps, instead of handling this ourselves on a low level. This allowed us to simplify our logic and remove 1.5+K lines of code, one dependency, one runtime process, and many sources of bugs (Rewrite apps logic using Gio.DesktopAppInfo.get_all() #835).
• Ulauncher now uses Unix sockets instead of Websockets to communicate with extensions (Unix Socket Implementation #822). This rewrite is a major improvement for performance and security, and it's fully backward compatible.
• Ulauncher now support wlr-layer-shell protocol to allows positioning and displaying over fullscreen windows feat: Try to use wlr-layer-shell protocol on wayland #1172
• We now auto-detect and handle desktops without a compositor cases without needing the "--no-window-shadow" CLI flag. If you still get the black borders issue please let us know though. See Remove the no-shadow setting #1149 and Black borders when the compositor is closed in v6 #1235 for details.
• We have replaced all our usage of pickle with JSON (safer, faster and more consistent). Switch state files and extensions to be stored as JSON instead of pickle #849 refactor: switch extension message format from pickle to json #1240
• Configuration files have been moved. We now adopted the new [XDG_STATE_HOME(https://www.reddit.com/r/linux/comments/ny34vs/new_xdg_state_home_in_xdg_base_directory_spec/) spec (Remove pyxdg dependency and switch to store state files in XDG_STATE_HOME #846). Note that Ulauncher v6 will migrate your old configuration files the first time you launch it, so this is not a breaking change.
• Script shortcuts now support %s to access the argument, which means if you use %s in your shell scripts code and don't want this you have to change to something else (like using f-strings in python) (Argument to shell commands get %s instead of the real argument #389)
• Added support (X11 only) to raise the app if it's already running and has a window, instead of launching a new one (Try to activate app before launching #979)
• The result view now supports scrolling if the amount of items is higher than the window height allows (Scrollable result list view #968)
• Ulauncher now uses your icon theme for the media icons instead of supplying it's own icons (Replace custom file browse mode icons with user theme icons #806).
• Ulauncher's Preferences behaves like a standard GTK window that has a header bar that you can drag it with, resize, maximize etc (Refactor preferences window #998). It is still a web view inside though.
• The calculator mode got several improvements.
  • Formats the output according to the locale (Formatting the result with locale for calc mode #937)
  • Improve the partial query handling and round the output to at most 15 decimals (V6 calc improvements #1014)
  • Support trigonometric functions and constants (Calculator: Add trigonometric methods and constants #1015)
  • Support modulus (Add mod operator support #999)
• Added setting to customize the jump keys and included Alt+0 in the defaults (allow customized or alternative jump (shortcut) keys instead of Alt+<number> #964 and Add Alt+0 (Alt+zero) as part of the results shortcuts #950)
• The optional app indicator (tray icon) now supports activating the launcher with a middle click add "Show Ulauncher" menu item to tray menu and set it as secondary target #1069, or left click if you install a recent version of XApp AppIndicator: Support separating between right and left clicks #1075
• Ulauncher can now take an optional argument to set the Ulauncher query
  gapplication action io.ulauncher.Ulauncher set-query "'hello'"
• For Gnome Desktop users, the settings (ex "Sound" are now included by default as apps, providing the same functionality as the extension ulauncher-gnome-settings does, but without needing an extension (3601dfd).
• You can now move the Ulauncher window by dragging it (Add functionality to drag the main window and Preferences window to move them #957) (seemingly this is broken currently).

Theme changes

• Since we removed the support for ancient GTK 3.18 you can specify only css_file_gtk to target GTK 3.20+, rather than needing both css_file_gtk and css_file_gtk_3.20+ (old themes specifying both ways will remain to work the same way) (Simplify CSS themes by removing GTK 3.20 support #836).

Extension changes

Most extensions that runs in Ulauncher v5 now should run in Ulauncher v6 as well. Almost all changes we made are backwards compatible. The exceptions are if the extension used APIs that were not meant for extensions to use.

• BREAKING: Simplified the Ulauncher API version by dropping the patch version. While this was made to be compatible with the previously documented ways to specify the version, the new implementation doesn't support all variants of the semver contraints that the old one did (this is very unlikely to affect extensions) (Remove semver.py and implement a much simpler version checker #859).
• BREAKING: versions.json is ignored by Ulauncher v6, in favor of git tags like apiv3 or apiv3.1 etc Completely remove versions.json support #1091
• BREAKING: The old extension debugging instructions are no longer supported (we made it easy to install from a local git repository instead, see below).
• BREAKING: Removed Result getter methods get_name(), get_keyword(), get_icon(). Just use the properties name, keyword, icon directly if you need to access properties from the result (38e8792).
• BREAKING: The new reworked Result class now no longer support positional parameters (note that this feature was never documented to begin with, and I have found no extensions that used this).
• BREAKING: Moved many APIs extensions shouldn't have had access to like (api.server.*and api.shared.action.LaunchAppAction)
• BREAKING: Event listeners are now triggered in a separate thread per call. For most this is will just work and make extensions run faster, but if your extension really has to be blocking/transactional you have to work around this (Extension client: Use a new thread for each extension event listener invocation #1113)
• Extension event binding has been simplified to reduce boilerplate code (Automatic event binding #936, Pass custom arguments directly to extension's event listener methods #1057, Implement triggers #1097)
• Extension preferences are now loaded and available directly when the extension object is created (as a dict self.preferences). Previously they were loaded into the same property and format, but after the extension was initialized via the PreferencesEvent. The PreferencesEvent still exists for backward compatibility, but we recommend to simply use the class __init__ now (see Load extension preferences directly in __init__ #1047)
• We changed the terminology and APIs for "Triggers". These were previously defined as "preferences" with type "keyword" in the manifest. But this was both confusing and a limiting factor for them. Implement triggers #1097
  • Triggers can now have custom icons: Allow overriding extension icon at the keyword level. #817
  • The new method on_input that replaces KeywordQueryEvent does not inherit the API suggestion: add event.get_keyword_id() #284 issue, and does not use any custom Ulauncher data type for the argument. Just "input text" and "keyword id" (both strings). For old extensions in Ulauncher v6 this issue has been solved in a different way: Rework extension keyword #1056
• Our extension installer has been internally rewritten:
  • Uses git repository discover references instead of the rate-limited GitHub API.
  • Supports installing from GitHub, GitLab, and Codea-compatible remote repos (like Codeberg)
  • Supports installing from any other local or remote repo, but only when the user has git installed (git is not a Ulauncher dependency) feat(ext_remote): use git if installed to support any repo #1203
• Extension icons can now be themed icon names like "edit-paste" rather than just image files (Extension icons should support system icons #803).
• RenderResultListAction is now optional. You can return a list (or yield results d1ae619) directly instead where you previously would use it (Support list as a shortcut/alias to RenderResultListAction #923)
• Simplified the Result class names from ExtensionResultItem and ExtensionSmallResultItem to just Result (set the a property compact to True to use the smaller template. Merge Result classes (Result, SearchableResult, SmallResult, ExtensionResult, ExtensionSmallResult) #1118 Merge Result classes (and glade ui files) #1120
• Simplified the Extension API so you can import all the modules you need directly from ulauncher.api (Rename *ResultItem to just *Result #934, 741ebae)
• Add support for optional Installation instructions in the manifest (for missing dependencies like system commands) Add help/instructions text in the manifest (show message in Extension Preferences after installing the extension) #805
• Fixed extension preferences type text type to show as a textarea (f8bc100)
• Added extension preferences type checkbox and number (d675036, 39811bb)
• The extension manifest has gone through many spec changes. The old format(s) are still supported, but we reformat it internally:
  • required_api_version is now api_version (again)
  • developer_name is now authors
  • We no longer ask for a manifest "description", as that wasn't really used Remove unused property "description" from manifest #1083 (preferences and triggers still uses descriptions, but the manifest root doesn't have this field)
  • preferences is now a dictionary Change manifest.preferences to a dictionary #1085 and optional as triggers (aka "type": "keyword") has been moved out to their own separate place triggers Implement triggers #1097
  • query_debounce is now specified directly in the manifest root as input_debounce because we no longer use the terminology "query" for the extension input triggers
• "Extension actions" have been simplified so you can now use simple data types instead:
  • DoNothingAction --> True
  • HideWindowAction() --> False
  • SetUserQueryAction("string") --> "string"
  • All other actions are represented as JSON objects.

[LinuxOnTheDesktop]

Blacklisted dirs ('If you still feel like you need this setting in Ulauncher v6, let us know'). I think I do need this. For, there are directories that contain executables (or links to them) that do not work on my system or that I do not wish to use.

Also: could we have dark mode in the configuration windows, please?

[friday]

Blacklisted dirs ('If you still feel like you need this setting in Ulauncher v6, let us know'). I think I do need this. For, there are directories that contain executables (or links to them) that do not work on my system or that I do not wish to use.

Then why do you have them in the dedicated directory for desktop entries to use for launchers and menu apps if I may ask?

Also: could we have dark mode in the configuration windows, please?

That's not planned, and is not easy to implement, so very unlikely for v6. Hopefully later at some point.

[lorenzleutgeb]

I might be a little late, but just checking: #712 and #713 should be resolved right. Asking because these issues are not mentioned. If so, I'd test the beta.

[friday]

I might be a little late, but just checking: #712 and #713 should be resolved right. Asking because these issues are not mentioned. If so, I'd test the beta.

Yes. There's over 1000 commits, so I can't mention everything in the release notes, but they are closed as fixed so they are fixed.

[friday]

I just pushed a pre-release: https://github.com/Ulauncher/Ulauncher/releases/tag/v6.0.0-beta1. We still have work to do before the stable release, but this makes it easier for people to test without building themselves.

The plan was to also make that publish to ulauncher-dev, for the Ubuntu/Debian users who opted for the experimental Ubuntu PPA. But apparently that part isn't working yet (fixed now, but only the jammy and focal packages show up in launchpad... 🤔 ).

Either way the deb can be downloaded and installed manually in the meanwhile.

[friday]

https://github.com/Ulauncher/Ulauncher/releases/tag/v6.0.0-beta2 released and published to ulauncher-dev

[RedBearAK]

@friday

Working nicely in a Xubuntu VM, but I'm hoping someone will start making some RPMs soon. My main systems are Fedora and Tumbleweed. The tar.gz is a bit too manual for my taste.

Love the Ctrl+comma shortcut to open the preferences now.

And the searching in the app "comment" or description appears to be working well also. Lots of good things happening.

[LinuxOnTheDesktop]

Version 6 sounds good! Where should bug reports for the beta of that version be posted, please? I add immediately here though the following two points (though neither are about bugs).

1. On Cinnamon, Ulauncher 5 itself could set the main Ulauncher shortcut. Ulauncher 6 cannot. But setting the shortcut via Cinnamon works.

2. Previously, for applications requiring pkexec, I had to create custom shortcuts else Ulauncher would not run those applications. But now Ulauncher runs those applications directly. Nice!

[friday]

1. On Cinnamon, Ulauncher 5 itself could set the main Ulauncher shortcut. Ulauncher 6 cannot. But setting the shortcut via Cinnamon works.

Yeah, that's because the old way relied on a library that relied on globally monitoring all keystrokes See #1256 and #991 (comment) (old behavior). I added support for Cinnamon too, but had to revert it because it wasn't possible to reload Cinnamon to apply the settings: 2a22711

2. Previously, for applications requiring pkexec, I had to create custom shortcuts else Ulauncher would not run those applications. But now Ulauncher runs those applications directly. Nice!

🙏

[friday]

v6.0.0-beta3 was released yesterday, but the ulauncher-dev ppa upload failed because of errors on their side. So the package wasn't pushed until some hours ago today.

[friday]

v6.0.0-beta4 was just released with a few fixes.

The scope of the v6 release still isn't fully set in stone, but we only have a few remaining planned features/improvements now:

• Feature: Automatic install of extension dependencies #273 (comment) (this is one of the big tasks that we planned for v6 originally, so we really should try to include it)
• Add generic extension method to handle activating results instead of actions #931 (the only remaining part of the extension API refactoring that I don't want to ship v6 without)
• Rewrite Ulauncher preferences to use pure GTK (not webkit) #1257 (this could be big, so maybe it will happen after v6, but it would be a huge benefit to get it shipped soon so we won't need the web app (90% of the package size is this app) and all its dependence (webkit, node, yarn, font-awsesome and all the npm dependencies which GitHub falsely flags as security concerns). It also makes it harder to build/package the app externally from source.

Most of the other unfinished tasks in the milestone are chores that relate to the release, extension site or documentation (these can still take time though).

We would appreciate any help we can get with testing (trying to confirm the current behavior and narrow down where/why any issue happen).

For example:

• Ensure the app shadow works as intended (no shadow or black outline) with a DE without a compositor
• Test more Wayland in more DEs (in particular we want to support the DEs that support wlr-layer-shell).
• According to one user Linux Mint seems to log apps launched by Ulauncher under "ulauncher" (we can likely not do something about this?)

[euh2]

• According to one user Linux Mint seems to log apps launched by Ulauncher under "ulauncher" (we can likely not do something about this?)

I see this as well on Fedora. From my understanding it seems that Ulauncher is regarded as as parent process. There must be a way to dislodge the Child from the Parent. In the shell I would use exec someApplication to uncouple the application from my shell (or rather the binary running my shell). Maybe there is a way to do this in Python.

[RedBearAK]

@euh2 @friday

In the shell I would use exec someApplication to uncouple the application from my shell (or rather the binary running my shell). Maybe there is a way to do this in Python.

Actually from what I understand exec in the shell replaces the shell with the new process or shell, rather than running the command as a child or spawning another shell layer. I don't think it's quite the same as launching an independent process while the same shell keeps running. But I'm not an expert in how the shell works.

For Python, GPT-4 suggests this may be the best way to launch a process and have it be independent of the Python process that launches it:

import subprocess
subprocess.Popen(['your_app'], start_new_session=True)

I've never had occasion to use this start_new_session argument, but it seems to be a valid argument and defaults to False. Seems to have been around since Python 3.2 (2011).

If start_new_session is true the setsid() system call will be made in the child process prior to the execution of the subprocess.

References to it found here:

https://docs.python.org/3/library/subprocess.html

[friday]

We have just released v6.0.0-beta5 which should fix the issue mentioned above (it also reintroduced #778 when running Ulauncher from a terminal) @euh2 @RedBearAK

This is the first release for a while because most of what's been done in this period has been refactoring and build improvements, NixOS support and other things which didn't affect the app so much.

There is however something wrong with launchpad again. It is probably time to find a better alternative to this frustrating platform. Fixed (it was due to "beta" being shortened to "b" in the version name, which is how Python says it should be done, and forces it to be shortened)

[euh2]

It is probably time to find a better alternative to this frustrating platform.

Suse might be an alternative: openSuse

I'm curious about why I was tagged here. 🤔

[friday]

I'm curious about why I was tagged here. 🤔

Because this release should address your feedback in #869 (comment)

Suse might be an alternative: openSuse

Feels like a better alternative for sure, but extremely high threshold to learn how to use it. I tried it twice.

[euh2]

should address your feedback

I forgot about that. Waiting eagerly for the stable v6. 🇺🇦

[RedBearAK]

@friday

I continue to look forward to someone putting together an RPM installer. I spend most of my time on Fedora. I'm betting between openSUSE, OpenMandriva, Fedora, CentOS, RHEL and all the RHEL compatibles, the RPM-based distros are a decently large portion of the installed Linux user base.

I tried just using the setup.py to get it built and installed, but the result seems to have a lot of Python exceptions, and I don't really have time to mess around with it to see why it's not working. I'm sure the DEB still works perfectly fine on Ubuntu/Debian systems.

It also seems to be putting things in the "system" Python locations, which more and more distros are restricting in favor of wanting apps to use their own virtual environment to protect the system Python library. Seems like a good idea to sort that out before the final release. I had to go through that process with a project of mine about a year ago, and now it will install without any Python issues on about 6 different major distro types, using its own isolated venv.

[friday]

@RedBearAK Thanks for the testing and the feedback. These are not priorities for us currently though. Also, system packages should use system dependencies unless it's a flatpak or something.

I guess we could look into supporting https://help.ubuntu.com/community/CheckInstall though, but those uses the user package paths, not the system ones.

[friday]

v6.0.0-beta9 v6.0.0-beta10 was just released.

Since the last updates here (beta4-5) we have done a lot of refactoring, fixes and added some features, but mainly the same bigger tasks remain. We have been trying to reduce the milestone by moving #1257 out of the V6 release so we can have a release candidate ready sooner.

• feat: notify the user if an extension has raised an exception #832
• Black borders when the compositor is closed in v6 #1235 (need to confirm)
• Feature: Automatic install of extension dependencies #273 (comment) (this is one of the big tasks that we planned for v6 originally, so we really should try to include it)
• Add generic extension method to handle activating results instead of actions #931 (might move this out of the v6 milestone too)

The other unfinished tasks in the milestone are chores that relate to the release, extension site or documentation.

We would still appreciate any help we can get with testing to ensure things are working in different environments. In particular if you can make detailed reports with error logs and/or submit PRs.