crocket Github contribution chart
crocket Github Stats
crocket Most Used Languages

Activity

23 Jun 2022

Issue Comment

Crocket

Tail call optimization.

The Problem

Currently, rakudo doesn't have tail call optimization or proper tail calls. It seems tail call optimization is the last puzzle piece that will make raku a proper functional programming language.

Forked On 23 Jun 2022 at 06:23:58

Crocket

Closing for now.

Commented On 23 Jun 2022 at 06:23:58
Issue Comment

Crocket

disable-xdg.inc weirdness with ${DESKTOP} [mupdf and directory whitelist]

Discussed in https://github.com/netblue30/firejail/discussions/4975

Originally posted by wonbug February 24, 2022 I'm trying to open a PDF file with mupdf in ~/Desktop/

I put all these directives into ~/.config/firejail/mupdf.local:

whitelist ${HOME}/Desktop/
whitelist ${HOME}/Desktop
whitelist ~/Desktop/
whitelist ~/Desktop 

Yet when I try to open the file, I get:

$ /usr/bin/firejail /usr/bin/mupdf ~/Desktop/file.pdf
...
error: cannot open /home/user/Desktop/file.pdf: Permission denied
mupdf: error: cannot open document 

Am I missing something obvious?

Forked On 21 Jun 2022 at 09:45:46

Crocket

Is this really fixed?

Commented On 21 Jun 2022 at 09:45:46
Issue Comment

Crocket

`--join-or-start=program` shouldn't create `program-PID` sandboxes if multiple instances try to start simultaneously.

If my bookmark manager tries to open multiple bookmarks by launching multiple invocations of firejail --join-or-start=librewolf librewolf URL simultaneously, the first invocation creates librewolf sandbox and some of subsequent invocations end up creating librewolf-PID sandboxes.

If multiple firejail invocations are trying to launch simultaneously with --join-or-start=program, the first invocation should reserve a named sandbox which subsequent invocations wait for before joining the named sandbox.

Because not all invocations of librewolf join the same sandbox, I had to insert

ignore private-tmp
ignore dbus-user 

into librewolf.local in order to launch multiple bookmarks simultaneously on librewolf.

If --join-or-start was good at putting all simultaneous invocations of firejail in one named sandbox, I didn't need to make all librewolf instances share /tmp and dbus with programs outside sandbox.

Forked On 10 Jun 2022 at 01:20:21

Crocket

I installed 0.9.70 and rebooted. I tested librewolf with join-or-start librewolf in librewolf.local.

The issue was reproduced reliably. I still need to ignore private-tmp and dbus-user.

Commented On 10 Jun 2022 at 01:20:21
Issue Comment

Crocket

`--join-or-start=program` shouldn't create `program-PID` sandboxes if multiple instances try to start simultaneously.

If my bookmark manager tries to open multiple bookmarks by launching multiple invocations of firejail --join-or-start=librewolf librewolf URL simultaneously, the first invocation creates librewolf sandbox and some of subsequent invocations end up creating librewolf-PID sandboxes.

If multiple firejail invocations are trying to launch simultaneously with --join-or-start=program, the first invocation should reserve a named sandbox which subsequent invocations wait for before joining the named sandbox.

Because not all invocations of librewolf join the same sandbox, I had to insert

ignore private-tmp
ignore dbus-user 

into librewolf.local in order to launch multiple bookmarks simultaneously on librewolf.

If --join-or-start was good at putting all simultaneous invocations of firejail in one named sandbox, I didn't need to make all librewolf instances share /tmp and dbus with programs outside sandbox.

Forked On 10 Jun 2022 at 01:16:40

Crocket

I just tested 0.9.70 with join-or-start librewolf in librewolf.local.

The issue is perfectibly reproducible on 0.9.70.

I still need to ignore private-tmp and dbus-user.

Commented On 10 Jun 2022 at 01:16:40
Issue Comment

Crocket

`--join-or-start=program` shouldn't create `program-PID` sandboxes if multiple instances try to start simultaneously.

If my bookmark manager tries to open multiple bookmarks by launching multiple invocations of firejail --join-or-start=librewolf librewolf URL simultaneously, the first invocation creates librewolf sandbox and some of subsequent invocations end up creating librewolf-PID sandboxes.

If multiple firejail invocations are trying to launch simultaneously with --join-or-start=program, the first invocation should reserve a named sandbox which subsequent invocations wait for before joining the named sandbox.

Because not all invocations of librewolf join the same sandbox, I had to insert

ignore private-tmp
ignore dbus-user 

into librewolf.local in order to launch multiple bookmarks simultaneously on librewolf.

If --join-or-start was good at putting all simultaneous invocations of firejail in one named sandbox, I didn't need to make all librewolf instances share /tmp and dbus with programs outside sandbox.

Forked On 09 Jun 2022 at 09:24:47

Crocket

I will test.

Commented On 09 Jun 2022 at 09:24:47
Issue Comment

Crocket

${HOME} should be allowed to be something like /dev/null.

Problem

Some system daemons are started as a non-root user with /dev/null as HOME.

Firejail has difficulties when HOME is /dev/null because include *.local fails when HOME is /dev/null.

Solution

Firejail should be fine with /dev/null as HOME.

Alternatives

I haven't tried AppArmor. Can AppArmor do things that firejail can do? I think AppArmor can be great for system daemons and programs that launch other programs.

Forked On 09 Jun 2022 at 09:21:06

Crocket

System daemons often don't have $HOME. I was trying to sandbox system daemons with firejail.

Commented On 09 Jun 2022 at 09:21:06
Issue Comment

Crocket

mullvad resolvers do not work because they lack IP addresses.

I thought DoH resolvers without IP addresses were going to use bootstrap resolvers, but they didn't.

I had to manually add IP addresses to resolver stamps by using https://dnscrypt.info/stamps/

Forked On 09 Jun 2022 at 08:52:03

Crocket

I tested again, and the issue seems fixed. I don't understand.

Commented On 09 Jun 2022 at 08:52:03
Issue Comment

Crocket

Document project.janet more thoroughly.

https://janet-lang.org/docs/jpm.html doesn't reflect what's possible now in project.janet.

For example, :tag.

Forked On 07 Jun 2022 at 05:38:33

Crocket

I'm in the process of retiring this github account. Create a new issue if you want.

Commented On 07 Jun 2022 at 05:38:33
Issue Comment

Crocket

Document project.janet more thoroughly.

https://janet-lang.org/docs/jpm.html doesn't reflect what's possible now in project.janet.

For example, :tag.

Forked On 06 Jun 2022 at 03:37:44

Crocket

Closing this for now.

Commented On 06 Jun 2022 at 03:37:44
Issue Comment

Crocket

Document jpm lockfile format

I don't have jpm repository cache. I can't use jpm make-lockfile.

I want to manually write it.

Forked On 06 Jun 2022 at 03:29:05

Crocket

I don't think lockfile is a substitute for proper versioning.

Commented On 06 Jun 2022 at 03:29:05

Crocket

Eliminate packages.

Pushed On 06 Jun 2022 at 02:10:12
Issue Comment

Crocket

mullvad resolvers do not work because they lack IP addresses.

I thought DoH resolvers without IP addresses were going to use bootstrap resolvers, but they didn't.

I had to manually add IP addresses to resolver stamps by using https://dnscrypt.info/stamps/

Forked On 06 Jun 2022 at 12:03:43

Crocket

Are you sure this is completed? mullvad DoH servers still don't have IP addresses.

Commented On 06 Jun 2022 at 12:03:43

Crocket

Delete rakudo infrastructure.

Pushed On 05 Jun 2022 at 11:22:14
Issue Comment

Crocket

I can't get a quote for BTC.

Please add BTC support.

Forked On 01 Jun 2022 at 04:33:21

Crocket

Closing it since I don't use gnucash anymore.

Commented On 01 Jun 2022 at 04:33:21
Issue Comment

Crocket

If I activate input method, it is deactivated and activated infinitely.

Describe the bug

I'm on b65e22c5a223f1ad7935ecf0a68f16496ba1d1e6

I don't know how to reproduce the issue, yet.

When the issue occurs, if I activate input method, it is deactivated and activated infinitely. I can't type anything.

To Reproduce

Desktop (please complete the following information):

  • Desktop: Sway
  • Display server type: Wayland

Additional context

The fix for my last issue probably caused this issue.

Forked On 31 May 2022 at 06:38:17

Crocket

I will open another issue if I can reproduce it reliably.

Commented On 31 May 2022 at 06:38:17
Issue Comment

Crocket

If I activate input method, it is deactivated and activated infinitely.

Describe the bug

I'm on b65e22c5a223f1ad7935ecf0a68f16496ba1d1e6

I don't know how to reproduce the issue, yet.

When the issue occurs, if I activate input method, it is deactivated and activated infinitely. I can't type anything.

To Reproduce

Desktop (please complete the following information):

  • Desktop: Sway
  • Display server type: Wayland

Additional context

The fix for my last issue probably caused this issue.

Forked On 31 May 2022 at 01:42:31

Crocket

Somehow, I think this issue is probably a sway issue or a qutebrowser issue.

Perhaps, the window focus moves between windows due to a sway bug.

Closing this issue for now.

Commented On 31 May 2022 at 01:42:31
Issue Comment

Crocket

If I activate input method, it is deactivated and activated infinitely.

Describe the bug

I'm on b65e22c5a223f1ad7935ecf0a68f16496ba1d1e6

I don't know how to reproduce the issue, yet.

When the issue occurs, if I activate input method, it is deactivated and activated infinitely. I can't type anything.

To Reproduce

Desktop (please complete the following information):

  • Desktop: Sway
  • Display server type: Wayland

Additional context

The fix for my last issue probably caused this issue.

Forked On 31 May 2022 at 01:10:11

Crocket

I press ctrl+shift+space to toggle input method.

Commented On 31 May 2022 at 01:10:11
Issue Comment

Crocket

Moving to xwayland from pure wayland causes fcitx5 to generate lots of key presses.

Describe the bug

If I'm on a pure wayland application, moving to an xwayland window results in lots of keypresses. t or any other key is pressed by fcitx5 a lot automatically until I press a key on my keyboard.

Gtk or Qt applications that run on wayland don't cause this issue. Pure wayland applications do.

To Reproduce

  • Activate fcitx5 by opening a Qt or Gtk application.
  • Open an xwayland window such as
    • env WINIT_UNIX_BACKEND=x11 alacritty
    • st terminal emulator.
  • Open a pure wayland window such as
    • alacritty
    • foot terminal emulator
    • env SDL_VIDEODRIVER=wayland dosbox-x
  • Move focus back to the previously opened xwayland window by clicking it or with a keyboard shortcut.
  • Stop automatic keypresses from fcitx5 by pressing t or any key. Press Ctrl+u to clear the command line.
  • Focus on the pure wayland window. Move focus back to the xwayland window again.

Expected behavior

fcitx5 doesn't press t repetitively.

Desktop (please complete the following information):

Forked On 29 May 2022 at 10:18:30

Crocket

I just tested the git master, and the issue seems to have been fixed. Great Work.

Commented On 29 May 2022 at 10:18:30

Crocket

add url to project.janet

Pushed On 29 May 2022 at 09:13:12

Crocket

Merge pull request #1 from uvtc/patch-1

add url to project.janet

Pushed On 29 May 2022 at 09:13:12

Crocket

add url to project.janet

Created On 29 May 2022 at 09:13:11
Issue Comment

Crocket

add url to project.janet
Forked On 29 May 2022 at 09:12:22

Crocket

Do you use this project?

Commented On 29 May 2022 at 09:12:22

Crocket

add url to project.janet

Pushed On 29 May 2022 at 09:12:19

Crocket

Merge pull request #1 from uvtc/patch-1

add url to project.janet

Pushed On 29 May 2022 at 09:12:19

Crocket

add url to project.janet

Created On 29 May 2022 at 09:12:19
Issue Comment

Crocket

Moving to xwayland from pure wayland causes fcitx5 to generate lots of key presses.

Describe the bug

If I'm on a pure wayland application, moving to an xwayland window results in lots of keypresses. t or any other key is pressed by fcitx5 a lot automatically until I press a key on my keyboard.

Gtk or Qt applications that run on wayland don't cause this issue. Pure wayland applications do.

To Reproduce

  • Activate fcitx5 by opening a Qt or Gtk application.
  • Open an xwayland window such as
    • env WINIT_UNIX_BACKEND=x11 alacritty
    • st terminal emulator.
  • Open a pure wayland window such as
    • alacritty
    • foot terminal emulator
    • env SDL_VIDEODRIVER=wayland dosbox-x
  • Move focus back to the previously opened xwayland window by clicking it or with a keyboard shortcut.
  • Stop automatic keypresses from fcitx5 by pressing t or any key. Press Ctrl+u to clear the command line.
  • Focus on the pure wayland window. Move focus back to the xwayland window again.

Expected behavior

fcitx5 doesn't press t repetitively.

Desktop (please complete the following information):

Forked On 28 May 2022 at 07:06:53

Crocket

I finally found a way to reproduce the issue reliably with this minimal sway config.

# vim: filetype=i3
set $mod Mod4

exec fcitx5 -dr

bindsym $mod+Return exec /usr/bin/st
bindsym $mod+Shift+Return exec /usr/bin/foot
bindsym $mod+d exec bemenu-run

# move focus
bindsym $mod+h focus left
bindsym $mod+j focus down
bindsym $mod+k focus up
bindsym $mod+l focus right 
  1. Press $mod+Shift+Return to launch foot
  2. Press exi
  3. Press t and Enter "very quickly".
  4. Press $mod+Shift+Return to launch foot again
  5. Press $mod+Return to launch st

Commented On 28 May 2022 at 07:06:53