Bug 2192253 - gnome-shell: make bolt dependency weak
Summary: gnome-shell: make bolt dependency weak
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 38
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-30 22:00 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2024-05-21 14:51 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:51:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab bolt bolt issues 92 0 None opened boltd should exit if no thunderbolt support is present 2023-11-19 20:41:51 UTC

Description Dominik 'Rathann' Mierzejewski 2023-04-30 22:00:19 UTC
It's not possible to uninstall bolt due to hard dependency in gnome-shell. If a machine doesn't have a Thunderbolt interface, there's no point in running boltd and having this package installed. gnome-shell works just fine without bolt. Please make it a weak dependency (Recommends: instead of Requires:).

Version-Release number of selected component (if applicable):
bolt-0.9.5-1.fc38.x86_64
gnome-shell-44.1-1.fc38.x86_64

Reproducible: Always

Steps to Reproduce:
1. rpm -e bolt

Actual Results:  
error: Failed dependencies:
	bolt(x86-64) is needed by (installed) gnome-shell-44.1-1.fc38.x86_64


Expected Results:  
Successful removal.

Comment 1 Dominik 'Rathann' Mierzejewski 2023-04-30 22:33:16 UTC
https://src.fedoraproject.org/rpms/gnome-shell/pull-request/19 open.

Comment 2 Debarshi Ray 2023-05-03 10:45:14 UTC
Does boltd really always run on machines without a Thunderbolt interface?  For example:

  [rishi@topinka ~]$ ps aux | grep bolt
  rishi     315538  0.0  0.0 222168  2176 pts/0    S+   12:43   0:00 grep --color=auto bolt
  [rishi@topinka ~]$ rpm -q bolt
  bolt-0.9.2-1.fc36.x86_64

Comment 3 Dominik 'Rathann' Mierzejewski 2023-05-04 21:58:40 UTC
It does run on mine when it's installed. I have to mask the service to prevent it from
running or uninstall with rpm -e --nodeps. But, even if it didn't run, I still don't
want to have code which I have no use for lying around and taking space and potentially
increasing my attack surface.

Comment 4 Debarshi Ray 2023-05-05 14:07:04 UTC
(In reply to Dominik 'Rathann' Mierzejewski from comment #3)
> It does run on mine when it's installed. I have to mask the service to
> prevent it from running or uninstall with rpm -e --nodeps.

It might be worth filing a bug upstream against bolt about this:
https://gitlab.freedesktop.org/bolt/bolt

Comment 5 Debarshi Ray 2023-05-05 15:07:41 UTC
From what Christian Kellner once told me, bolt only looks at sysfs.  Does the Settings -> Thunderbolt panel think that you have Thunderbolt hardware?  What do things like 'boltctl list' and 'boltctl list --all' show?

Comment 6 Dominik 'Rathann' Mierzejewski 2023-06-29 20:39:57 UTC
(In reply to Debarshi Ray from comment #5)
> From what Christian Kellner once told me, bolt only looks at sysfs.  Does
> the Settings -> Thunderbolt panel think that you have Thunderbolt hardware? 

No, it says "No Thunderbolt Support".

> What do things like 'boltctl list' and 'boltctl list --all' show?

Both commands return no output.

Comment 7 Felipe Borges 2023-11-16 08:59:47 UTC
gnome-control-center will start a Boltd client, and with that, activate Boltd in the system to find out if there are thunderbolt devices. https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/main/panels/privacy/cc-bolt-page.c#L198

gnome-control-center is capable of handling the case where boltd can't be found.

Comment 8 Dominik 'Rathann' Mierzejewski 2023-11-19 20:42:14 UTC
This is the upstream issue.

Comment 9 Aoife Moloney 2024-05-07 16:15:25 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 10 Aoife Moloney 2024-05-21 14:51:17 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.