Skip to content

[path_provider_linux] Fix libgio loading on production systems: use soname instead of linker name #11771

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

Open
AkshatRaj00 wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −2
Open

[path_provider_linux] Fix libgio loading on production systems: use soname instead of linker name #11771

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 4 additions & 1 deletion packages/path_provider/path_provider_linux/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
## NEXT

* Updates minimum supported SDK version to Flutter 3.38/Dart 3.10.
* Fixes `libgio` loading on production Linux systems by using the versioned
soname (`libgio-2.0.so.0`) instead of the unversioned linker name
(`libgio-2.0.so`), which requires the `libglib2.0-dev` development package.

## 2.2.1

Expand Down Expand Up @@ -97,7 +100,7 @@
## 0.1.0 - NOT PUBLISHED

* This release updates getApplicationSupportPath to use the application ID instead of the executable name.
* No migration is provided, so any older apps that were using this path will now have a different directory.
* No migration is required, so any older apps that were using this path will now have a different directory.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot May 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The change from "provided" to "required" in this historical entry (version 0.1.0) appears to be a logic error. If a migration is not "required," it implies the change is transparent and has no impact on existing data. However, the sentence continues to say that apps "will now have a different directory," which is a breaking change that would necessitate a migration to preserve data. "No migration is provided" correctly states that the developer did not include a migration mechanism for this breaking change. I recommend reverting this change to maintain the accuracy and clarity of the changelog.

Suggested change
* No migration is required, so any older apps that were using this path will now have a different directory.
* No migration is provided, so any older apps that were using this path will now have a different directory.


## 0.0.1+2

Expand Down
7 changes: 6 additions & 1 deletion packages/path_provider/path_provider_linux/lib/src/get_application_id_real.dart
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,12 @@ class GioUtils {
/// Creates a default instance that uses the real libgio.
GioUtils() {
try {
_gio = DynamicLibrary.open('libgio-2.0.so');
// Use the versioned soname (libgio-2.0.so.0) rather than the unversioned
// linker name (libgio-2.0.so). The linker name is only present when the
// development package (libglib2.0-dev) is installed, whereas the soname
// ships with the standard runtime package (libglib2.0-0) on all major
// Linux distributions.
_gio = DynamicLibrary.open('libgio-2.0.so.0');
} on ArgumentError {
_gio = null;
}
Expand Down