Bug 1847314 - [regression] gnome-shell strips LD_LIBRARY_PATH from environment
Summary: [regression] gnome-shell strips LD_LIBRARY_PATH from environment
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-16 08:01 UTC by Pierre Ossman
Modified: 2022-12-13 15:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:15:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pierre Ossman 2020-06-16 08:01:32 UTC
Description of problem:

gnome-shell has since Fedora 31 started stripping out LD_LIBRARY_PATH (and other linker variables) for all programs started. This breaks environments that need to redirect libraries for various reasons. We discovered this because it breaks smart card redirection in ThinLinc's remote desktops.


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

gnome-shell-3.34.5-1.fc31.x86_64
gnome-shell-3.36.3-3.fc32.x86_64
gnome-shell-3.37.2-1.fc33.x86_64


How reproducible:

100%


Steps to Reproduce:

1. Make sure LD_LIBRARY_PATH is set during session startup
2. Start a terminal
3. Run "set | grep LD_LIBRARY_PATH"


Actual results:

No LD_LIBRARY_PATH


Expected results:

LD_LIBRARY_PATH is still set.


Additional info:

This is an (unintended?) side effect of gnome-shell now having capabilities set on it:

https://src.fedoraproject.org/rpms/gnome-shell/c/27577309e2f45734f897f0fadf85b4b8c8099b8a

A workaround is to do "sudo setcap -r /usr/bin/gnome-shell", but that likely resets every time it is upgraded.

Comment 1 Fedora Program Management 2021-04-29 16:31:21 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2021-05-25 16:28:17 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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 please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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

Comment 3 Pierre Ossman 2021-05-28 06:35:58 UTC
The issue is still unresolved upstream, so still a problem for Fedora:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2284

Comment 4 Ben Cotton 2021-08-10 12:48:14 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 5 Pierre Ossman 2022-05-24 14:22:30 UTC
This seems to have been resolved upstream, and has trickled down to the distributions. I don't see this in Fedora 35, or RHEL 9.

So from my point of view this can be closed.

Comment 6 Ben Cotton 2022-11-29 16:48:54 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 '35'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 7 Ben Cotton 2022-12-13 15:15:20 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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.