[GH-ISSUE #3297] tracelog option broken on ppc64le #2069

New issue

Open

opened 2026-05-05 08:44:24 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 08:44:24 -06:00

Owner

Originally created by @the-antz on GitHub (Mar 25, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3297

The presence of the tracelog option breaks firejail (v0.9.62) on ppc64le. It fails like this:

firejail /usr/bin/gedit
Reading profile /etc/firejail/gedit.profile
Reading profile /etc/firejail/gedit.local
Reading profile /etc/firejail/whitelist-wayland.inc
Reading profile /etc/firejail/allow-common-devel.inc
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-common.local
Reading profile /etc/firejail/disable-exec.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 25295, child pid 25296
Warning: private-lib feature is currently available only on amd64 platforms
Warning: /sbin directory link was not blacklisted
Warning: /usr/sbin directory link was not blacklisted
Blacklist violations are logged to syslog
Child process initialized
*** stack smashing detected ***: <unknown> terminated

Parent is shutting down, bye...

It works when adding the trace-flag (firejail --trace /usr/bin/gedit), my theory is that this makes it ignore the tracelog option as it's already logging to stdout.

The error doesn't happen on a basically identical amd64 pc.

Originally created by @the-antz on GitHub (Mar 25, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3297 The presence of the `tracelog` option breaks firejail (v0.9.62) on ppc64le. It fails like this: ``` firejail /usr/bin/gedit Reading profile /etc/firejail/gedit.profile Reading profile /etc/firejail/gedit.local Reading profile /etc/firejail/whitelist-wayland.inc Reading profile /etc/firejail/allow-common-devel.inc Reading profile /etc/firejail/disable-common.inc Reading profile /etc/firejail/disable-common.local Reading profile /etc/firejail/disable-exec.inc Reading profile /etc/firejail/disable-passwdmgr.inc Reading profile /etc/firejail/disable-programs.inc Reading profile /etc/firejail/whitelist-var-common.inc Parent pid 25295, child pid 25296 Warning: private-lib feature is currently available only on amd64 platforms Warning: /sbin directory link was not blacklisted Warning: /usr/sbin directory link was not blacklisted Blacklist violations are logged to syslog Child process initialized *** stack smashing detected ***: <unknown> terminated Parent is shutting down, bye... ``` It works when adding the trace-flag (`firejail --trace /usr/bin/gedit`), my theory is that this makes it ignore the tracelog option as it's already logging to stdout. The error doesn't happen on a basically identical amd64 pc.

gitea-mirror added the

bug

label 2026-05-05 08:44:24 -06:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2069

No description provided.

Rows
Columns