Bug 1692043 - "mkdirat: Permission denied" error when launching GNOME Software
Summary: "mkdirat: Permission denied" error when launching GNOME Software
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: flatpak
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-23 16:54 UTC by Daniel Rusek
Modified: 2019-11-27 22:05 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 22:05:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Rusek 2019-03-23 16:54:42 UTC
Description of problem:
After fully updating recently installed clean Fedora Silverblue 29 system, GNOME Software displayed this error every time its window was opened. Unfortunately, there was absolutely nothing related to this error in the GS verbose log and the error vanished after enabling the Flathub repository so I am not sure if this is a GS or a Flatpak (FlatpakTransaction) regression.

Version-Release number of selected component (if applicable):
gnome-software-3.30.6-2.fc29.x86_64
flatpak-1.2.3-2.fc29.x86_64

How reproducible:
Every time.

Steps to Reproduce:
1. Install Fedora 29 Silverblue.
2. Fully update the system (using GNOME software or rpm-ostree).
3. Open GNOME Software.

Actual results:
"mkdirat: Permission denied" error is displayed in the GNOME Software window.

Expected results:
No errors are displayed.

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1509032 - Flatpak client showing the same error message, however this one was caused by unprivileged access.

Comment 1 Manuel Quiñones 2019-04-01 16:24:57 UTC
I have the same issue. After installing `Fedora-Silverblue-ostree-x86_64-29-1.2.iso` I get the "mkdirat: Permission denied" in GNOME Software. I also note that there aren't any flatpak repos setup after the first boot. Calling `flatpak remote-ls` I get the same "mkdirat: Permission denied" error.

Comment 2 Kalev Lember 2019-04-01 16:42:15 UTC
This error comes from flatpak. Reassigning.

Comment 3 Jeff Ligon 2019-04-23 14:46:48 UTC
i did a `flatpak remote-add fedora oci+https://registry.fedoraproject.org` and its gone for me.

Comment 4 Ben Cotton 2019-10-31 19:34:19 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 5 Ben Cotton 2019-11-27 22:05:27 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.


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