Skip to content

[BUG] "dinit" init system incorrectly identified as just "init" #1245

Closed
@JamiKettunen

Description

@JamiKettunen

Be sure to read the FAQ before submitting a new issue.

General description of bug:

  • What happened: dinit init system shown as just init without version in fastfetch -l none -s initsystem
  • What should happen: Init System: dinit 0.18.0 (I can get Init System: dinit without the version to show up if I append e.g. init=/bin/dinit to kernel cmdline)
  • Fastfetch version used: 2.23.0
  • Did it work in an older version: Don't remember it ever working since the introduction of the init system module in 2.14.0
  • Where did you get the binary: Chimera Linux apk repository package (I'm the package maintainer)
  • Does this issue still occur in the latest dev build? Yes (2.23.0 just released)

Often helpful information:

Screenshot:
image

Output of fastfetch -s initsystem --format json:

[
  {
    "type": "InitSystem",
    "result": {
      "name": "init",
      "exe": "/usr/bin/dinit",
      "version": "",
      "pid": 1
    }
  }
]

Output of fastfetch --list-features:

threads
vulkan
wayland
xcb-randr
xcb
xrandr
x11
drm
gio
dconf
dbus
imagemagick7
chafa
zlib
xfconf
egl
osmesa
opencl
libpulse
libddcutil
libelf
libzfs
System yyjson
linux/videodev2
linux/wireless

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions