Arch Linux User Repository

@dreieck: I've reverted the change. The goal was to use upstream's toolchain, but it builds fine with stable.

Can you change the makedependency rustup to cargo (or maybe rust), please?

So the user can decide weather to use the rustup or the rust package.

As it is now, it forces installation of rustup, which conflicts with rust and forces a de-installation of rust.

Or is there any speciality that specifically rustup is needed?

Regards and thanks for maintaining!

@dreieck: Do not run firmware-manager as root. It's a script using pkexec, not the binary itself.

A note:

After compiling and installing this package, when I run firmware-manager (as root, of course) it prints the following error messages to the terminal:

[ERROR] firmware_manager src/lib.rs:344: No such file or directory (os error 2)
[INFO ] firmware_manager src/fwupd.rs:80: refreshing remotes
unknown remote key: RemotesDir (v): Variant("/var/lib/fwupd/metadata")
unknown remote key: AutomaticReports (v): Variant(false)
unknown remote key: AutomaticSecurityReports (v): Variant(false)
unknown remote key: RemotesDir (v): Variant("/var/lib/fwupd/metadata")
unknown remote key: AutomaticReports (v): Variant(false)
unknown remote key: AutomaticSecurityReports (v): Variant(false)
unknown remote key: Flags (v): Variant(1)
unknown remote key: RemotesDir (v): Variant("/var/lib/fwupd/metadata")
unknown remote key: AutomaticReports (v): Variant(false)
unknown remote key: AutomaticSecurityReports (v): Variant(false)
unknown remote key: Flags (v): Variant(16)
unknown remote key: RefreshInterval (v): Variant(86400)
unknown remote key: RemotesDir (v): Variant("/var/lib/fwupd/metadata")
unknown remote key: AutomaticReports (v): Variant(false)
unknown remote key: AutomaticSecurityReports (v): Variant(false)
unknown remote key: Flags (v): Variant(17)
unknown remote key: SecurityReportUri (v): Variant("https://fwupd.org/lvfs/hsireports/upload")
unknown remote key: RefreshInterval (v): Variant(86400)
unknown remote key: RemotesDir (v): Variant("/var/lib/fwupd/metadata")
unknown remote key: AutomaticReports (v): Variant(false)
unknown remote key: AutomaticSecurityReports (v): Variant(false)
[INFO ] firmware_manager src/fwupd.rs:94: Updating RemoteId("lvfs") metadata from Some("https://cdn.fwupd.org/downloads/firmware.xml.xz")

Backtrace omitted. Run with RUST_BACKTRACE=1 to display it.
Run with RUST_BACKTRACE=full to include source snippets.

The application panicked (crashed).
  called `Option::unwrap()` on a `None` value
in /tmp/makepkg/build/firmware-manager-git/src/cargo-home/registry/src/index.crates.io-6f17d22bba15001f/fwupd-dbus-0.2.3/src/remote.rs, line 190
thread: <unnamed>

The window shows up, but it is empty and the only visible element is a refresh button.

gnome-firmware shows a few devices, so I think this one here is not working.

Regards!

Hello!

I'm trying to install this package, but I keep getting the following error after Enabling com.system76.FirmwareManager.Notify.timer service

I get the error: Failed to connect to bus: No medium found

Not sure why I have dbus and I have other series running.

I get the same error for the non git version.

EDIT: A reboot fixed the issue for me.

@jsimon0: Fixed, thanks.

I think you have a missing - in the PKGBUILD

❯ yay firmware-manager-git
2 aur/libfirmware-manager-git 0.1.2.r2.g44cc265-2 (+7 0.00) 
    Shared library for C which provides the firmware manager as a GTK widget.
1 aur/firmware-manager-git 0.1.2.r2.g44cc265-2 (+7 0.00) 
    GTK application for managing system and device firmware.
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 1 2
 -> Could not find all required packages:
        libfirmwaremanager-git (Wanted by: firmware-manager-git)

PSA: The shared lib is now split into a separate package, so you'll need to remove the previous version before updating to 0.1.2-3.

@m3thodic: The issue is now fixed. I made the requested changes to the install file.

@m3thodic: Yes, I opened an issue here.