RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1685449 - Gnome 3: tlog does not record terminal in Gnome 3
Summary: Gnome 3: tlog does not record terminal in Gnome 3
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: tlog
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Nikolai Kondrashov
QA Contact: ipa-qe
Lucie Vařáková
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-05 09:14 UTC by Kirill Gliebov
Modified: 2019-05-22 04:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 17:45:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Exmple when it works (72.74 KB, image/png)
2019-03-05 09:23 UTC, Kirill Gliebov 		no flags Details
View All

Description Kirill Gliebov 2019-03-05 09:14:41 UTC 
Description of problem:
tlog does not record terminal in Gnome 3. 

Version-Release number of selected component (if applicable):
tlog-5.1

How reproducible:
Enable session recording using tlog by either changing user's shell to /usr/bin/tlog-rec-session or by /etc/sssd/conf.d/sssd-session-recording.conf( scope=some, user=%username% )
Login with recorded user by ssd -> notice that session is recorded will be shown.
Login with the same recorded user to Gnome 3 and open terminal -> no notice is shown, which means that session is not recorded.


Steps to Reproduce:
Enable session recording using tlog by either changing user's shell to /usr/bin/tlog-rec-session or by /etc/sssd/conf.d/sssd-session-recording.conf( scope=some, user=%username% )
Login with recorded user by ssd -> notice that session is recorded will be shown.
Login with the same recorded user to Gnome 3 and open terminal -> no notice is shown, which means that session is not recorded.

Actual results:
Login with the same recorded user to Gnome 3 and open terminal -> no notice is shown, which means that session is not recorded.

Expected results:
Login with the same recorded user to Gnome 3 and open terminal -> notice that session is being recorded is shown and session is recorded

Additional info:
Comment 1 Nikolai Kondrashov 2019-03-05 09:20:35 UTC 
Tlog does not support recording terminals in a graphical session. Mostly because a graphical session has a single audit session ID for all the terminals, and so tlog has no way of distinguishing them and preventing repeated recording (i.e. a shell started inside a shell recorded twice or more times). Besides, there are many ways to do things besides using a terminal in a graphical session. Including configuring a terminal emulator to start a custom shell, which would completely bypass tlog. A purpose-built graphical session recording software should be used in these cases.
Comment 2 Kirill Gliebov 2019-03-05 09:23:02 UTC 
Created attachment 1540873 [details]
Exmple when it works

Exmple when it works
Comment 3 Kirill Gliebov 2019-03-05 09:28:34 UTC 
It works on my rhel8 vm, but does not work for Mark Thacker. He was using vagrant image and probably there is some issue with that, but it is still a bug.
It seems that we need to have this.
Comment 4 Nikolai Kondrashov 2019-03-05 09:48:09 UTC 
It's not a bug, it's by design, and I was speaking about this from the start, including talks at conferences. It's simply a limitation of our approach of using a shell substitute for recording.
All terminals started within a graphical session will have the same audit session ID, because it is the same session for all of them. You will be able to record only one terminal at once. Any other terminal started at the same time within the same graphical session won't be recorded.
Comment 5 Mark Thacker 2019-03-06 15:47:47 UTC 
So to be clear, there seems to be some inconsistency then as I definitely had an issue where a VM that I had would never record gnome terminal sessions, but another VM (built from RHEL 8 snapshot 6 with nightly updates) works fine.
At least, it works fine for the first terminal session.

As this is a limitation, by design or not, it does need to be noted in a Release Note and even in the product documentation. The content that I've seen so far makes no mention of Gnome terminal sessions at all.
Comment 10 jstephen 2019-05-08 17:45:28 UTC 
Closing this as NOTABUG based on the discussion in this BZ.
Note You need to log in before you can comment on or make changes to this bug.