Ubuntu ошибка 256

Checklist

• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.
• If this is an issue with a particular app, I have tried filing it in the appropriate issue tracker for the app (e.g. under https://github.com/flathub/) and determined that it is an issue with Flatpak itself.
• This issue is not a report of a security vulnerability (see here if you need to report a security issue).

Flatpak version

1.10.7

What Linux distribution are you using?

ChromeOS

Linux distribution version

5.4.157

What architecture are you using?

x86_64

How to reproduce

1. Install Flatpak
2. Get Flathub setup
3. Try to run an app
4. Throws you an error: ldconfig failed, exit status 256

Expected Behavior

Run the god damn program

Actual Behavior

Throws you that stupid error

Additional Information

This happens to me EVERY TIME! I’ve uninstalled and reinstalled it, i’ve uninstalled the program and reinstalled it. EVERY TIME WITH EVERY APP. Can someone tell me how to fix this? (also, i need debian codes)

Skip to content

• • GitLab: the DevOps platform
  • Explore GitLab
  • Install GitLab
  • How GitLab compares
  • Get started
  • GitLab docs
  • GitLab Learn
• Pricing
• Talk to an expert

• 
  Help
  
  • Help
  • Support
  • Community forum
  • Submit feedback
  • Contribute to GitLab
  • Switch to GitLab Next
• Projects
  Groups
  Snippets

• 
  Sign up now
• Login

• 
  Sign in / Register

Closed

Open


Issue created Jan 10, 2021 by CHJ85@CHJ85

ERROR: ldconfig failed, exit status 256

Hi there. I just installed the latest version of LibreWolf using your flatpak package.
Tried to open LibreWolf, but it gave me this error:
ldconfig failed, exit status 256
Not sure what this means or what I can do to fix it.
I’m running Ubuntu 20.10 btw and Linux kernel 5.10.0-5.1-liquorix-amd64.
Thanks in advance!

и как её решить?
bwrap: setting up uid map: Permission denied
ошибка: Ошибка ldconfig, статус ошибки 256

Мой make.conf:
COMMON_FLAGS=»-O2 -pipe»
CFLAGS=»${COMMON_FLAGS}»
CXXFLAGS=»${COMMON_FLAGS}»
FCFLAGS=»${COMMON_FLAGS}»
FFLAGS=»${COMMON_FLAGS}»
CONFIG_PROTECT=»-*»

CFLAGS=»-march=native -O2 -pipe»
CXXFLAGS=»$CFLAGS»
CPU_FLAGS_X86=»aes avx avx2 fma3 mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3″
VIDEO_CARDS=»intel i965 iris»

# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR=»/var/db/repos/gentoo»
DISTDIR=»/var/cache/distfiles»
PKGDIR=»/var/cache/binpkgs»

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C
ACCEPT_LICENSE=»*»
GENTOO_MIRRORS=»https://mirror.yandex.ru/gentoo-distfiles/ http://mirror.yandex.ru/gentoo-distfiles/»
GRUB_PLATFORMS=»efi-64″

FEATURES=»parallel-fetch preserve-libs»
VIDEO_CARDS=»vmware intel»
ACCEPT_KEYWORDS=»~amd64″
AUTOCLEAN=»yes»
CPU_FLAGS_X86=»3dnow 3dnowext aes avx avx2 fma3 fma4 sse3 sse4_1 sse4_2 ssse3 xop»
PHP_TARGETS=»php5-7″

ENABLE=»openh264 7zip systemd gnome gtk3 bluetooth networkmanager
a52 aac aalib acpi apache2
bash-completion blas bluray bmp bzip2 cairo cddb cdr cgi cleartype corefonts crypt css cuda cups curl
dbus device-mapper djvu dri dri2 dts dvd dvdr
enca encode exif faac faad ffmpeg fftw fits flac fontconfig fuse
gedit ghostscript gif glut gnuplot gost gsl gtk gtk2 hddtemp icewm iconv id3tag imagemagic imlib2 jack jpeg jpeg2k
lame lapack latex libass libcaca libnotify libsamplerate lm_sensors logrotate
mad matroska mencoder midi mime mmx mmxext mng motif mp3 mp4 mpeg mpeg2 mplayer multilib
nautilus ntfs nvidia ogg openmp openssl optimisation pch pdf png pnm postgres postgresql proftp
rar real sftp sockets sox spell sqlite sqlite3 squid sse sse2 sse3 ssse3 ssse4 svg
tga theora threads tiff timidity truetype ttf type1 udev usb v4l2 vdpau vorbis vlc
wav win32codecs wmf X x264 xinerama xinetd xorg xosd xscreensaver xvid
gnome-keyring vnc ssh»
USE=»${USE} pypy3 python3_8 python3_9 python3_10 introspection seccomp quicktime real gif jpeg mpeg matroska xanim png tiff svg a52 aac exif mp3 ogg vorbis theora xpm wmf win32codecs x264 flac postscript xvid mad mp2 divx encode»
# VirtualBox
USE=»${USE} gd truetype exif cli cgi fpm apache2 embed phpdbg linux alsa debug doc java opus pam pulseaudio opengl python qt5 vnc java»

# All that must be disabled
DISABLE=»-abiword -gstreamer -consolekit -doc -eds -handbook
-joystick -kde -perl -phonon -policykit -pulseaudio
-qt3 -sdl -udisks -upower -wallpapers»

USE=»${ENABLE} ${DISABLE}»

PORTDIR_OVERLAY=»/var/lib/layman/jorgicio $PORTDIR_OVERLAY»

2

ответов

И так, решение: sudo emerge -av sys-apps/bubblewrap (т.е всё решилось переустановкой bubblewrap)

стоп я не понял зачем pulseaudio и -pulseaudio в одном

Похожие вопросы

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.

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

Comments

To (try to?) reproduce: install Mint 20; after that, do and see the following.

$ flatpak install fwupd
Looking for matches…
Found similar ref(s) for ‘fwupd’ in remote ‘flathub’ (system).
Use this remote? [Y/n]: y
Found ref ‘app/org.freedesktop.fwupd/x86_64/stable’ in remote ‘flathub’ (system).
Use this ref? [Y/n]: y
Info: org.freedesktop.Platform.Icontheme.Paper is end-of-life, with reason: The Icontheme extensions are not used anymore.

org.freedesktop.fwupd permissions:
    network      devices      file access [1]      system dbus access [2]

    [1] /boot, /sys, xdg-download
    [2] org.freedesktop.UPower, org.freedesktop.fwupd


        ID                                     Branch           Op          Remote           Download
 1. [✓] org.freedesktop.fwupd.Locale           stable           i           flathub          3.2 kB / 1.8 MB
 2. [✓] org.freedesktop.fwupd                  stable           i           flathub          2.4 MB / 3.1 MB

Installation complete.
$ flatpak run org.freedesktop.fwupd
ldconfig: Can't create temporary cache file /run/ld-so-cache-dir/0ae87624ea5c37aef5b1af8b02de5d49a0d1a8543eeb68e20af02d14ac848e3c~: Permission denied
error: ldconfig failed, exit status 256
$ sudo flatpak run org.freedesktop.fwupd
error: "flatpak run" is not intended to be ran with sudo

Postscript

So I decided to try the repository version . .

$ sudo apt install fwupd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Recommended packages:
  bolt fwupd-signed
The following NEW packages will be installed
  fwupd
0 to upgrade, 1 to newly install, 0 to remove and 6 not to upgrade.
Need to get 0 B/2,089 kB of archives.
After this operation, 5,784 kB of additional disk space will be used.
Selecting previously unselected package fwupd.
(Reading database ... 444208 files and directories currently installed.)
Preparing to unpack .../fwupd_1.3.9-4ubuntu0.1_amd64.deb ...
Unpacking fwupd (1.3.9-4ubuntu0.1) ...
Setting up fwupd (1.3.9-4ubuntu0.1) ...
fwupd-offline-update.service is a disabled or a static unit not running, not starting it.
fwupd-refresh.service is a disabled or a static unit not running, not starting it.
fwupd.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
$ fwupdmgr
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.2' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.2' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.3' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.7' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.9' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.3' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.1' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.2' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.8' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.7' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.6' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.1' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.4' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.5' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.4' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.1' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.3' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.4' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.2' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.5' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.9' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.6' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)

fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.2′ not found (required by fwupdmgr)

Did you also install the source version to /usr/local/? I think fwupdmgr is being sourced from /usr/local/ for some reason.

Not that I recall. How should I check and/or correct, please?

If you have stuff in /usr/local, you’ve manually installed at some point. Remove it to use your packaged stuff.

And btw after you’ve cleared out your stuff in /usr/local, you probably need to run ldconfig

I tried again to install the Flatpak version (in order to try to . . fix another problem). The Flatpak still will not run. Would you please advise? Here is what happened.

$ flatpak run org.freedesktop.fwupd
error: While opening repository /home/<myUserName>/.local/share/flatpak/repo: /home/<myUserName>/.local/share/flatpak/repo: opendir(/home/<myUserName>/.local/share/flatpak/repo): Permission denied
<myUserName>@x1 ~ $ sudo flatpak run org.freedesktop.fwupd
error: "flatpak run" is not intended to be ran with sudo
<myUserName>@x1 ~ $ flatpak run org.freedesktop.fwupd
error: While opening repository /home/<myUserName>/.local/share/flatpak/repo: /home/<myUserName>/.local/share/flatpak/repo: opendir(/home/<myUserName>/.local/share/flatpak/repo): Permission denied
<myUserName>@x1 ~ $ chown -R <myUserName>:<myUserName> /home/<myUserName>/.local/share/flatpak/repo
chown: cannot read directory '/home/<myUserName>/.local/share/flatpak/repo': Permission denied
<myUserName>@x1 ~ $ sudo chown -R <myUserName>:<myUserName> /home/<myUserName>/.local/share/flatpak/repo
<myUserName>@x1 ~ $ flatpak run org.freedesktop.fwupd
error: mkdir(/home/<myUserName>/.var/app/org.freedesktop.fwupd/data): Permission denied
<myUserName>@x1 ~ $ sudo chown -R <myUserName>:<myUserName> /home/<myUserName>/.var/app/org.freedesktop.fwupd
<myUserName>@x1 ~ $ flatpak run org.freedesktop.fwupd
This program may only work correctly as root
Command not found

Use fwupdtool --help for help

And now . . this, which is . . sub-optimal. Note that I had installed the Flatpak, just now, via Mint’s (horribly broken?) Software Manager.

$ flatpak remove org.freedesktop.fwupd


        ID                                   Branch         Op
 1. [-] org.freedesktop.fwupd                stable         r
 2. [-] org.freedesktop.fwupd.Locale         stable         r

Uninstall complete.
<myUserName>@x1 ~ $ flatpak install org.freedesktop.fwupd
Looking for matches…
Found similar ref(s) for ‘org.freedesktop.fwupd’ in remote ‘flathub’ (system).
Use this remote? [Y/n]: 
Info: org.freedesktop.Platform.Icontheme.Paper is end-of-life, with reason: The Icontheme extensions are not used anymore.

org.freedesktop.fwupd permissions:
    network      devices      file access [1]      system dbus access [2]

    [1] /boot, /sys, xdg-download
    [2] org.freedesktop.UDisks2, org.freedesktop.UPower, org.freedesktop.fwupd


        ID                                     Branch           Op          Remote           Download
 1.     org.freedesktop.fwupd.Locale           stable           i           flathub          < 344.6 kB (partial)
 2.     org.freedesktop.fwupd                  stable           i           flathub            < 4.9 MB

Proceed with these changes to the system installation? [Y/n]:

Info: org.freedesktop.Platform.Icontheme.Paper is end-of-life, with reason: The Icontheme extensions are not used anymore.

org.freedesktop.fwupd permissions:
    network      devices      file access [1]      system dbus access [2]

    [1] /boot, /sys, xdg-download
    [2] org.freedesktop.UDisks2, org.freedesktop.UPower, org.freedesktop.fwupd


        ID                                     Branch           Op          Remote           Download
 1. [✓] org.freedesktop.fwupd.Locale           stable           i           flathub          3.3 kB / 344.6 kB
 2. [✓] org.freedesktop.fwupd                  stable           i           flathub          4.1 MB / 4.9 MB

Installation complete.
$ flatpak run org.freedesktop.fwupd
This program may only work correctly as root
Command not found

Use fwupdtool --help for help
$ sudo flatpak run org.freedesktop.fwupd
error: "flatpak run" is not intended to be ran with sudo

Cf. this report of woe, by someone else, and where no remedy was forthcoming, on the Linux Mint forum.

error: «flatpak run» is not intended to be ran with sudo

I think you want sudo -i flatpak run ...

I lack the time to test this. For, I removed the Flatpak. But: presuming you are right, then you need to have instructions that say that. Others should not have to waste as much time as I did.

then you need to have instructions that say that

Where did you read the flatpak instructions from, out of interest?

I read no instructions. Do you provide any?

EDIT: Initially I used Mint’s Software Manager to install the flatpak. Well, I tried to — the installation seemed not to work. (See here.) So then — if I recall correctly — I did this: I removed as much of that borked installation as I could; I searched the web on how to install the fwupd flatpak via terminal; and then I used whatever instructions I found (I’m afraid I do not recall them, but perhaps I could retrieve them from a log or from a bash cache) to install the flatpak via terminal.

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.

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

Comments

To (try to?) reproduce: install Mint 20; after that, do and see the following.

$ flatpak install fwupd
Looking for matches…
Found similar ref(s) for ‘fwupd’ in remote ‘flathub’ (system).
Use this remote? [Y/n]: y
Found ref ‘app/org.freedesktop.fwupd/x86_64/stable’ in remote ‘flathub’ (system).
Use this ref? [Y/n]: y
Info: org.freedesktop.Platform.Icontheme.Paper is end-of-life, with reason: The Icontheme extensions are not used anymore.

org.freedesktop.fwupd permissions:
    network      devices      file access [1]      system dbus access [2]

    [1] /boot, /sys, xdg-download
    [2] org.freedesktop.UPower, org.freedesktop.fwupd


        ID                                     Branch           Op          Remote           Download
 1. [✓] org.freedesktop.fwupd.Locale           stable           i           flathub          3.2 kB / 1.8 MB
 2. [✓] org.freedesktop.fwupd                  stable           i           flathub          2.4 MB / 3.1 MB

Installation complete.
$ flatpak run org.freedesktop.fwupd
ldconfig: Can't create temporary cache file /run/ld-so-cache-dir/0ae87624ea5c37aef5b1af8b02de5d49a0d1a8543eeb68e20af02d14ac848e3c~: Permission denied
error: ldconfig failed, exit status 256
$ sudo flatpak run org.freedesktop.fwupd
error: "flatpak run" is not intended to be ran with sudo

Postscript

So I decided to try the repository version . .

$ sudo apt install fwupd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Recommended packages:
  bolt fwupd-signed
The following NEW packages will be installed
  fwupd
0 to upgrade, 1 to newly install, 0 to remove and 6 not to upgrade.
Need to get 0 B/2,089 kB of archives.
After this operation, 5,784 kB of additional disk space will be used.
Selecting previously unselected package fwupd.
(Reading database ... 444208 files and directories currently installed.)
Preparing to unpack .../fwupd_1.3.9-4ubuntu0.1_amd64.deb ...
Unpacking fwupd (1.3.9-4ubuntu0.1) ...
Setting up fwupd (1.3.9-4ubuntu0.1) ...
fwupd-offline-update.service is a disabled or a static unit not running, not starting it.
fwupd-refresh.service is a disabled or a static unit not running, not starting it.
fwupd.service is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for dbus (1.12.16-2ubuntu2.1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
$ fwupdmgr
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.2' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.2' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.3' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.7' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.9' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.3' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.1' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.2' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.8' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.7' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.6' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.1' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.4' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.5' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.4' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.1' not found (required by fwupdmgr)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.3' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.4' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.2' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.5' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.2.9' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)
fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.3.6' not found (required by /usr/lib/x86_64-linux-gnu/libfwupdplugin.so.1)

fwupdmgr: /usr/local/lib/x86_64-linux-gnu/libfwupd.so.2: version `LIBFWUPD_1.1.2′ not found (required by fwupdmgr)

Did you also install the source version to /usr/local/? I think fwupdmgr is being sourced from /usr/local/ for some reason.

Not that I recall. How should I check and/or correct, please?

If you have stuff in /usr/local, you’ve manually installed at some point. Remove it to use your packaged stuff.

And btw after you’ve cleared out your stuff in /usr/local, you probably need to run ldconfig

I tried again to install the Flatpak version (in order to try to . . fix another problem). The Flatpak still will not run. Would you please advise? Here is what happened.

$ flatpak run org.freedesktop.fwupd
error: While opening repository /home/<myUserName>/.local/share/flatpak/repo: /home/<myUserName>/.local/share/flatpak/repo: opendir(/home/<myUserName>/.local/share/flatpak/repo): Permission denied
<myUserName>@x1 ~ $ sudo flatpak run org.freedesktop.fwupd
error: "flatpak run" is not intended to be ran with sudo
<myUserName>@x1 ~ $ flatpak run org.freedesktop.fwupd
error: While opening repository /home/<myUserName>/.local/share/flatpak/repo: /home/<myUserName>/.local/share/flatpak/repo: opendir(/home/<myUserName>/.local/share/flatpak/repo): Permission denied
<myUserName>@x1 ~ $ chown -R <myUserName>:<myUserName> /home/<myUserName>/.local/share/flatpak/repo
chown: cannot read directory '/home/<myUserName>/.local/share/flatpak/repo': Permission denied
<myUserName>@x1 ~ $ sudo chown -R <myUserName>:<myUserName> /home/<myUserName>/.local/share/flatpak/repo
<myUserName>@x1 ~ $ flatpak run org.freedesktop.fwupd
error: mkdir(/home/<myUserName>/.var/app/org.freedesktop.fwupd/data): Permission denied
<myUserName>@x1 ~ $ sudo chown -R <myUserName>:<myUserName> /home/<myUserName>/.var/app/org.freedesktop.fwupd
<myUserName>@x1 ~ $ flatpak run org.freedesktop.fwupd
This program may only work correctly as root
Command not found

Use fwupdtool --help for help

And now . . this, which is . . sub-optimal. Note that I had installed the Flatpak, just now, via Mint’s (horribly broken?) Software Manager.

$ flatpak remove org.freedesktop.fwupd


        ID                                   Branch         Op
 1. [-] org.freedesktop.fwupd                stable         r
 2. [-] org.freedesktop.fwupd.Locale         stable         r

Uninstall complete.
<myUserName>@x1 ~ $ flatpak install org.freedesktop.fwupd
Looking for matches…
Found similar ref(s) for ‘org.freedesktop.fwupd’ in remote ‘flathub’ (system).
Use this remote? [Y/n]: 
Info: org.freedesktop.Platform.Icontheme.Paper is end-of-life, with reason: The Icontheme extensions are not used anymore.

org.freedesktop.fwupd permissions:
    network      devices      file access [1]      system dbus access [2]

    [1] /boot, /sys, xdg-download
    [2] org.freedesktop.UDisks2, org.freedesktop.UPower, org.freedesktop.fwupd


        ID                                     Branch           Op          Remote           Download
 1.     org.freedesktop.fwupd.Locale           stable           i           flathub          < 344.6 kB (partial)
 2.     org.freedesktop.fwupd                  stable           i           flathub            < 4.9 MB

Proceed with these changes to the system installation? [Y/n]:

Info: org.freedesktop.Platform.Icontheme.Paper is end-of-life, with reason: The Icontheme extensions are not used anymore.

org.freedesktop.fwupd permissions:
    network      devices      file access [1]      system dbus access [2]

    [1] /boot, /sys, xdg-download
    [2] org.freedesktop.UDisks2, org.freedesktop.UPower, org.freedesktop.fwupd


        ID                                     Branch           Op          Remote           Download
 1. [✓] org.freedesktop.fwupd.Locale           stable           i           flathub          3.3 kB / 344.6 kB
 2. [✓] org.freedesktop.fwupd                  stable           i           flathub          4.1 MB / 4.9 MB

Installation complete.
$ flatpak run org.freedesktop.fwupd
This program may only work correctly as root
Command not found

Use fwupdtool --help for help
$ sudo flatpak run org.freedesktop.fwupd
error: "flatpak run" is not intended to be ran with sudo

Cf. this report of woe, by someone else, and where no remedy was forthcoming, on the Linux Mint forum.

error: «flatpak run» is not intended to be ran with sudo

I think you want sudo -i flatpak run ...

I lack the time to test this. For, I removed the Flatpak. But: presuming you are right, then you need to have instructions that say that. Others should not have to waste as much time as I did.

then you need to have instructions that say that

Where did you read the flatpak instructions from, out of interest?

I read no instructions. Do you provide any?

EDIT: Initially I used Mint’s Software Manager to install the flatpak. Well, I tried to — the installation seemed not to work. (See here.) So then — if I recall correctly — I did this: I removed as much of that borked installation as I could; I searched the web on how to install the fwupd flatpak via terminal; and then I used whatever instructions I found (I’m afraid I do not recall them, but perhaps I could retrieve them from a log or from a bash cache) to install the flatpak via terminal.

Страницы: [1]   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

---

---

---

---

---

---

---

Страницы: [1]   Вверх

Следующие шаги работали для меня для загрузочной флешки Windows 7 в Ubuntu-18.04

Шаг 1. Загрузите последний файл bash со страницы выпуска WoeUSB https://github.com/WoeUSB/WoeUSB/releases .

Шаг 2. Исправьте отсутствующие права доступа к исполняемому файлу chmod +x path/to/woeusb-NNNbash

Шаг 3: Установите GParted sudo apt-get install gparted

Шаг 4: Запустите интерфейс пользовательского интерфейса gparted

Шаг 5: Выберите свой диск в раскрывающемся списке в правом верхнем углу, удалите весь раздел с помощью GParted (после этого не создавайте новый раздел)

Шаг 6: Создайте загрузочную флешку ( sudo ./woeusb-NNNbash —target-filesystem NTFS —device path/to/windows.iso /dev/sdX )

       wget https://github.com/WoeUSB/WoeUSB/releases
 
 sudo apt install gparted
 cp /home/devops/Downloads/woeusb-5.2.4.bash .
 
 
 chmod 777 woeusb-5.2.4.bash 
 sudo ./woeusb-5.2.4.bash  --target-filesystem NTFS --device /home/devops/Downloads/test/en_windows_7_ultimate_x64_dvd.iso  /dev/sdb
  
   sudo apt install wimtools

 # Install above package if you get below error and then rerun woeusb command  below it again
 
 # "error woeusb requires wimlib-imagex command in the executable search path, but it is not found"

   sudo ./woeusb-5.2.4.bash  --target-filesystem NTFS --device /home/devops/Downloads/test/en_windows_7_ultimate_x64_dvd.iso  /dev/sdb

LINUX AND VMWARE STUFF

This Blog is to share our knowledge and expertise on Linux System Administration and VMware Administration

Wednesday, June 5, 2019

Yum failed with Errno 256 No more mirrors to try — Solved

Situation:
Yum is failed with Errno 256, No more mirrors to try.

root@testserver# yum list available | grep erna
https://rhn.test.com/pulp/repos/shared/lce-lcs_6month_rhel7/ccv-lcs_6month_rhel7/content/dist/rhel/server/7/7Server/x86_64/extras/os/repodata/repomd.

xml: [Errno 14] curl#58 — «SSL peer rejected your certificate as expired.»
Trying other mirror.

One of the configured repositories failed (Red Hat Enterprise Linux 7 Server — Extras (RPMs)),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work «fix» this:

1. Contact the upstream for the repository and get them to fix the problem.

yum-config-manager —save —setopt=rhel-7-server-extras-rpms.skip_if_unavailable=true

failure: repodata/repomd.xml from rhel-7-server-extras-rpms: [Errno 256] No more mirrors to try.
https://rhn.test.com/pulp/repos/shared/lce-lcs_6month_rhel7/ccv-lcs_6month_rhel7/content/dist/rhel/server/7/7Server/x86_64/extras/os/repodata/repomd.

xml: [Errno 14] curl#58 — «SSL peer rejected your certificate as expired.»

Solution:
Becasue of corrupted yum cache, getting this error. So refresh the subscription-manager clean the old cache & run the yum command

Источник

Why does yum return error: [Errno 256] No more mirrors to try ?

Environment

• Red Hat Enterprise Linux
• Red Hat Customer Portal
• Red Hat Subscription Management (RHSM)
• Red Hat Satellite

Issue

• yum update fails with the error : [Errno 256] No more mirrors to try

Resolution

Check the network connectivity. If IP based Firewall is being used then whitelist the IPs that are mentioned in Public CIDR Lists for Red Hat (IP Addresses for cdn.redhat.com) for access to the content delivery network (CDN).

Check what files are present under /etc/yum.repos.d directory by:-

If the system is registered with Red Hat Subscription Manager (RHSM) via subscription-manager, rhel-source.repo and redhat.repo are present.

If any local repositories or any other media repositories are present, remove them by:-

• Remove the old yum cache from the system by running the following commands:

• Check if the valid repositories are getting listed by:-

• If the previous solutions does not work, try reenabling each repository one by one with the following:-

Root Cause

• Possible reasons for this issue:
  • Corrupted yum cache.
  • Inaccessibility of a repository URL from the system due to network-related issues.
  • Presence of customized or other media repositories.
  • Outdated whitelist when using IP-based Firewall configuration to access Red Hat’s Content Delivery Network (CDN).

Diagnostic Steps

• yum update fails with any of the below errors:-

• On Satellite Server it fails with this error as per /var/log/messages

• Check the accessibility of the repository URL in the system/network.

• Check the repositories under /etc/yum.repos.d

• Product(s)
• Red Hat Subscription Management
• Red Hat Satellite
• Red Hat Enterprise Linux
• Red Hat Customer Portal

• Component
• yum

• Category
• Troubleshoot

• Tags
• customer_portal
• rhel
• rhn
• rhn_classic
• rhsm
• satellite
• subscription_management
• yum

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Whichever game I try to install on Lutris returns me with the error code 256

Whichever game I try to install on Lutris returns me with the error code 256

Post by sam007msd » Sun Jul 03, 2022 12:57 am

Re: Whichever game I try to install on Lutris returns me with the error code 256

Post by jstich » Sun Jul 03, 2022 3:56 am

Re: Whichever game I try to install on Lutris returns me with the error code 256

Post by ThaCrip » Wed Jul 13, 2022 1:35 am

I can’t answer your question directly since I never tried to install games through Lutris directly.

but I do use Lutris (currently v0.5.10.1), with the newest stable Wine from the winehq website, and then I pair it with GloriousEggroll runner for Lutris for the small amount of games I replay (Mafia series and RDR2(with RDR2 I have to set Wine to Windows 10 mode as if you leave Wine in the default of Windows 7 the game won’t start up)).

basically I use Lutris with newest Wine (from https://wiki.winehq.org/Ubuntu ; I use the ‘stable’ one and after that’s done I issue ‘sudo apt install wine-desktop-files’ which gives you the entries in the Mint menu to configure Wine if needed) paired with the GloriousEggroll custom runner for Lutris (i.e. https://github.com/GloriousEggroll/wine . m/releases ; currently you would download «wine-lutris-GE-Proton7-22-x86_64.tar.xz» and extract it to «

/.local/share/lutris/runners/wine/» and then Lutris should automatically use it. if not, you can force it on the games shortcut in Lutris by right clicking it, select Configure > Runner Options and under ‘Wine version’ you can select the Lutris runner from the drop down menu) and then just make a shortcut in Lutris and guide it to the location of the games main EXE file and then play it.

but off the top of my head if you got a game installer you can probably just install the game like usual through Wine (i.e. double click the installer EXE). once installed, then load up Lutris, make a shortcut and guide it to the location of the games EXE file (which will probably be located in this general location. «

/.wine/drive_c/» ) and play it.

NOTE: to make a shortcut in Lutris it’s simple enough. start Lutris, click «+» in the top left corner, then on menu that pops up select ‘Add locally installed game’. then a ‘Add a new game’ window will appear at which point on the ‘Runner’ text to the right of that says ‘Select a runner from the list’, click that, change it to ‘Wine (Runs Windows games)’, then over on the ‘Game options’ tab under ‘Executable’ you guide it to the location of the games main EXE file (by clicking the ‘browse’). you can tweak more if you want to, but that’s the basic idea.

but looking at what you posted. it seems that «lutris-fshack-7.2-x86_64» is not installed by default. but you can install that in particular directly by going to Lutris’s ‘Preferences > Runners’ and then scroll down to the bottom and see where it says ‘Wine’ and to the right of that is two icons you can click, click the one to the right, which should then open a ‘Manage wine versions’ screen at which point you can click ‘install’ to the right of the «lutris-fshack-7.2» text (maybe if you manually install this fshack stuff first and then do your installer, maybe it will work(?)). but honestly, I suspect that GloriousEggroll runner I posted is probably better in general as with that I can run a game or two that normally don’t seem to work.

for the record. you can install certain versions of the GloriousEggroll runner from within Lutris directly if you want as they are listed as ‘lutris-ge etc’ using what I described above in that general ‘lutris-fshack-7.2’ section.

but looking online a bit for that ‘error code 256’ your getting one user suggested recently (about 4 days or so ago). «Top right hamburger menu > preferences > global options > disable lutris runtime (toggle this to off aka no orange)» and a user replied saying it worked for them for whatever this is worth.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

WoeUSB not working / Exit Code: 256

WoeUSB not working / Exit Code: 256

Post by [Jonathan_C_Linux] » Sat Jan 05, 2019 11:04 pm

When I try to add the Windows 10 ISO to my flash drive I get an error of (Exit Code: 256). The USB drive is formatted as NTFS and is unmounted but it won’t install.

Mounting source filesystem.
Error: File «/media/woeusb_source_1546743561_19723/sources/install.wim» in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation and cannot be installed. You must specify a different —target-filesystem.
Refer: https://github.com/slacka/WoeUSB/wiki/L . limitation for more info.
Unmounting and removing «/media/woeusb_source_1546743561_19723».
You may now safely detach the target device

Re: WoeUSB not working / Exit Code: 256

Post by MrEen » Sat Jan 05, 2019 11:36 pm

Re: WoeUSB not working / Exit Code: 256

Post by trytip » Sun Jan 06, 2019 1:14 am

this means your flash drive is not large enough to hold the win10 iso. i just formatted my really old 8GB flash drive which i have formatted maybe 1000 times to fat32 and i have no issue making windows usb out of it. what is the full name of your win10 iso called? are you trying to make a bootable iso from an .exe update?

did you format your flash drive with the Usb stick Formatter?

Re: WoeUSB not working / Exit Code: 256

Post by [Jonathan_C_Linux] » Sun Jan 06, 2019 3:07 pm

Re: WoeUSB not working / Exit Code: 256

Post by trytip » Sun Jan 06, 2019 3:38 pm

it’s complaining about install.wim which is called install.esd is it larger than 4GB ? mine is 2.6GB

Re: WoeUSB not working / Exit Code: 256

Post by [Jonathan_C_Linux] » Sun Jan 06, 2019 4:11 pm

Re: WoeUSB not working / Exit Code: 256

Post by trytip » Sun Jan 06, 2019 4:24 pm

rightclick on the .iso and Open With «Disk Image Mounter» but more than likely your copy of install.esd is larger than 4GB which woeusb can’t handle. is this an official microsoft .iso?

try open gparted, select your flash drive and under devices > create new partition table > msdos > EXIT and format with USB FORMATTER NTFS

not sure if woeusb works with ntfs since it does install grub but fat32 will give you a limit at 4GB

you need to get an OFFICIAL copy of windows 10 or create the usb in other windows os with the Windows USB/DVD Download Tool

Re: WoeUSB not working / Exit Code: 256

Post by Vilis » Mon May 13, 2019 1:15 pm

I have the same identical problem using Cinnamon 18.3, but I went further in analyzing it. I installed the Ubuntu repository for WoeUSB, and ran WoeUSB. My copy of Windows 7 Pro is the official Microsoft OEM compatible version, because I have an OEM MS Win. 7 Pro license sticker on my computer, which the local Microsoft rep guided me by phone to verify — it verified as good. Then the Microsoft rep guided me to create a bootable USB stick on a Windows 7 Pro machine I have, using 100% Microsoft software, and that procedure produced a bootable USB stick using my official MS .iso file of OEM Windows 7 Pro 64bit.
So I have a working copy of a USB stick with official MS Win 7 Pro .iso installed on it, made entirely using Windows software, not Linux, to compare with my WoeUSB. Both copies, my 100% Microsoft copy, and my WoeUSB copy are IDENTICAL on my computer screen, plugged in side by side into my computer, until the instant that the WoeUSB installation finishes, when suddenly it crashes in the last milllisecond of installation, and after that millisecond the two copies are no longer identical, but radically different!

Conclusion: THIS IS A VALID COMPLAINT, WHICH I HAVE VALIDATED AS CORRECT, needing attention by the gurus on this forum. The previous guru was wrong in his conclusions.

Re: WoeUSB not working / Exit Code: 256

Post by Vilis » Mon May 13, 2019 1:26 pm

Источник

yum Docker install error Errno 256 Errno 14 HTTPS Error 404 — Not Found

As I have done in the past, I am trying to install docker-ce on RHEL 7(ppc64le) like this:

sudo yum-config-manager —add-repo https://download.docker.com/linux/centos/docker-ce.repo

yum repolist
repo id repo name
docker-ce-stable/x86_64 Docker CE Stable — x86_64

sudo yum install docker-ce
I get the error output below. I have tried all the solutions recommended, but I think the real error is the very last line in the error output which is:

failure: repodata/repomd.xml from docker-ce-stable: [Errno 256] No more mirrors to try.
https://download.docker.com/linux/centos/7/ppc64le/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 — Not Found

Any suggestions on how to resolve this error?

========= Start error output ==================
https://download.docker.com/linux/centos/7/ppc64le/stable/repodata/repomd.xml: [Errno 14] HTTPS Error 404 — Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article

h t t p s://access.redhat.com/articles/1320623

If above article doesn’t help to resolve this issue please open a ticket with Red Hat Support.

One of the configured repositories failed (Docker CE Stable — ppc64le),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:

Contact the upstream for the repository and get them to fix the problem.

Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

Run the command with the repository temporarily disabled
yum —disablerepo=docker-ce-stable .

Disable the repository permanently, so yum won’t use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use —enablerepo for temporary usage:

or
subscription-manager repos —disable=docker-ce-stable

Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

Источник