ibus VS firejail

1.5.29-rc2 was tagged on 9 Nov 2023 [1] and in did not contain "N_("CJK Unified Ideographs Extension I")," in src/ibusunicodegen.h [2].

Commit 228f0a77b2047ade54e132bab69c0c03f0f41aae from 28 Feb 2023 introduced this change instead. It's the same person who tagged 1.5.29-rc2 and committed 228f0a77b2047ade54e132bab69c0c03f0f41aae which is typically an indication the maintainer tar'd their checked out git folder and accidentally included changes not get committed.

[1] https://github.com/ibus/ibus/releases/tag/1.5.29-rc2

[2] https://github.com/ibus/ibus/blob/0ad8e77bd36545974ad8acd0a5...

[2] https://github.com/ibus/ibus/commit/228f0a77b2047ade54e132ba...

On https://github.com/ibus/ibus we can see gtk+ are probably only need for ibus-setup. I would like help to be sure i not miss any step.

I also know input methods work great in Ubuntu (Gnome Wayland) because Gnome supports ibus.

But the article is specifically about incompatibility of input methods among different DEs: Gnome, KDE, wlroots-based environments such as Sway and Hyprland.

After many years, ibus still doesn’t work with wlroots: https://github.com/ibus/ibus/issues/2182

The list of recommended IMEs on Sway are all WIP: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway#...

Most people use fcitx5 with Sway because fcitx5 and Sway both support input method unstable v2. But the article explains that v2 is still not universally supported among wayland DEs, and that’s why it’s problematic.

Have no idea what the daemon does practically, here is the GitHub page.

The F38 beta is currently affected by two (mostly gaming-related) issues that you should be aware of: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2678 -> a lot of SDL-based games have their fullscreen mode broken. The issue is bisected. - https://github.com/ibus/ibus/issues/2480 -> Keyboard input sometimes gets stuck. Issue has already been identified and we're waiting for an ibus release.

Also, to add to what u/Pizza-Driver said, it seems that ibus is not yet interoperable with the protocol used by Wayland display servers based on wlroots.

I meant ctrl+., but it looks like ibus recently changed their emoji input shortcut back to super+., so the gtk emoji picker should be available via ctrl+. again without requiring changes: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

Looks like it was changed here: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

Do you happen to know if the overlayfs bug that upset the firejail developers has been fixed yet? https://github.com/netblue30/firejail/discussions/4178

Perhaps firejail is dead? There's been no releases in 18 months.

bubblewrap is designed as a low-level too. There is nothing quick and dirty about it. It disallows everything by default and you have to be explicit about what you want to share with the host. If your application needs complex permissions/resources, then you will need to have a complex bubblewrap command line.

Once you have figured out which permissions/resources you need for a given program, you can wrap the command line invocation in a shell script.

If you want other people to do the work of defining permissions/resources, then have a look at firejail: https://github.com/netblue30/firejail

Firejail is cool: https://github.com/netblue30/firejail

Linux namespaces/cgroups but nowhere near as heavy as Docker.

I use it when I want to limit the memory of a Python script:

```

Firejail can also be a useful option, though no good if you're on Mac https://firejail.wordpress.com/

Uses the same Linux primitives as docker etc, but can be a bit more ergonomic for this use case

Firejail, Flatpak (which uses Bubblewrap under the hood), and Snap (which uses AppArmor) all use the same underlying technology: Linux namespaces.

This question comes up a lot, and has been answered here: https://github.com/netblue30/firejail/wiki/Frequently-Asked-...

TL;DR: Firejail has much more comprehensive features than Flatpak (Bubblewrap). Firejail also has more comprehensive network support, support for AppArmor and SELinux, and easier seccomp filtering.

Compared to Snap (which uses AppArmor), Firejail is compatible with AppArmor and again goes above and beyond with a lot of additional features.

Wonderful little tool, too bad you must chain various exec calling tools to get cgroups (a bit akin to `ionice ... nice ... cmd`) and Linux users namespaces can't allow UNIX sockets while preventing network access (I think?).

Migrated from Firejail when its complexity annoyed me too much and I hit https://github.com/netblue30/firejail/issues/3001 (Firejail doesn't like parens or brackets in --put/--get parameters) to a badly NIH version using bwrap and bash to have "profiles":