Skip to content

debugging: Add a section on logging bus traffic #550

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bbhtt merged 2 commits into from
Dec 3, 2024
Merged

debugging: Add a section on logging bus traffic #550

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ec3c189
debugging: Add a section on logging bus traffic
bbhtt Dec 3, 2024
df7847a
Update po files
bbhtt Dec 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/debugging.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,3 +173,20 @@ You can see all the apps that are currently running in Flatpak sandboxes
And, if you need to, you can terminate one by force (since 1.2)::

$ flatpak kill <application-id>

Audit session or system bus traffic
-----------------------------------

A ``--socket=session-bus`` or a ``--socket=system-bus`` permission must
not be present for the logging to work.

Session or system bus traffic can be audited by passing ``--log-session-bus``
and ``--log-system-bus`` respectively to ``flatpak run``::

flatpak run --log-session-bus <application-id>

This can be useful to figure out the bus names used by an application
and the corresponding ``--talk-name`` or ``--own-name`` permissions
required::

flatpak --log-session-bus run <application-id>| grep '(required 1)'
3 changes: 2 additions & 1 deletion docs/sandbox-permissions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,8 @@ risk. So they must be avoided, unless the application is a development
tool.

``flatpak run --log-session-bus $FLATPAK_ID`` can be used to find the specific
D-Bus permissions needed.
D-Bus permissions needed. See :ref:`debugging:Audit session or system bus traffic`
for more information.

**Ownership**

Expand Down
32 changes: 31 additions & 1 deletion po/de/LC_MESSAGES/debugging.po
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Flatpak\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-01 08:05+0530\n"
"POT-Creation-Date: 2024-12-03 21:11+0530\n"
"PO-Revision-Date: 2018-05-20 10:36-0400\n"
"Last-Translator: Copied by Zanata <[email protected]>\n"
"Language: de\n"
Expand Down Expand Up @@ -244,6 +244,29 @@ msgstr ""
msgid "And, if you need to, you can terminate one by force (since 1.2)::"
msgstr ""

#: ../../debugging.rst:178
msgid "Audit session or system bus traffic"
msgstr ""

#: ../../debugging.rst:180
msgid ""
"A ``--socket=session-bus`` or a ``--socket=system-bus`` permission must "
"not be present for the logging to work."
msgstr ""

#: ../../debugging.rst:183
msgid ""
"Session or system bus traffic can be audited by passing ``--log-session-"
"bus`` and ``--log-system-bus`` respectively to ``flatpak run``::"
msgstr ""

#: ../../debugging.rst:188
msgid ""
"This can be useful to figure out the bus names used by an application and"
" the corresponding ``--talk-name`` or ``--own-name`` permissions "
"required::"
msgstr ""

#~ msgid "Running debugging tools"
#~ msgstr ""

Expand Down Expand Up @@ -328,3 +351,10 @@ msgstr ""
#~ " run::"
#~ msgstr ""

#~ msgid ""
#~ "This can be useful to figure out"
#~ " the bus names used by an "
#~ "application and the corresponding ``--talk-"
#~ "names`` or ``--own-names`` required::"
#~ msgstr ""

Loading
Loading