Package Details: firmware-manager 0.1.5+12+g3c542bd-2

Git Clone URL: https://aur.archlinux.org/firmware-manager.git (read-only, click to copy)
Package Base: firmware-manager
Description: Generic framework and GTK UI for firmware updates from system76-firmware and fwupd
Upstream URL: https://github.com/pop-os/firmware-manager
Licenses: GPL-3.0-or-later
Conflicts: libfirmware-manager
Submitter: electrickite
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 10
Popularity: 0.014896
First Submitted: 2020-04-02 02:45 (UTC)
Last Updated: 2024-09-05 19:34 (UTC)

Latest Comments

« First ‹ Previous 1 2 3

jsimon0 commented on 2021-02-10 18:30 (UTC)

@yochananmarqos This worked. Thanks

yochananmarqos commented on 2021-02-10 18:13 (UTC) (edited on 2021-02-10 18:14 (UTC) by yochananmarqos)

@jsimon0: I solved the issue in my firmware-manager-git package by using a Polkit policy. Try that out. You'll be able to run the binary just as firmware-manager and use the menu shortcut. It will prompt for elevation.

jsimon0 commented on 2021-02-10 17:17 (UTC)

While this builds for me, I cannot run it. I get the following exception at runtime if I run with elevated permissions. Anybody else?

$ pkexec firmware-manager
Unable to init server: Could not connect: Connection refused

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

The application panicked (crashed).
  failed to init GTK: BoolError { message: "Failed to initialize GTK", filename: "/home/jsimon/.cargo/registry/src/github.com-1ecc6299db9ec823/gtk-0.9.2/src/rt.rs", function: "gtk::rt", line: 129 }
in src/libcore/result.rs, line 1188
thread: main

Obviously, if I run it without elevated permissions, it opens but doesn't work.

electrickite commented on 2020-12-16 02:57 (UTC)

@dreieck Version 0.1.1-2 adds a firmware-manager symlink.

yochananmarqos commented on 2020-12-13 00:02 (UTC) (edited on 2020-12-13 00:05 (UTC) by yochananmarqos)

@dreieck: I symlink com.system76.FirmwareManager to firmware-manager in my firmware-manager-git package. However, it makes no sense to symlink com.system76.FirmwareManager.Notify as it's only used by com.system76.FirmwareManager.Notify.service.

As far as the Cargo crates, that's how it works. Go packages are similar. Please don't spam every AUR package that uses Rust. See Arch package guidelines.

dreieck commented on 2020-12-12 23:45 (UTC)

The executables get installed at the non-intuitive names /usr/bin/com.system76.FirmwareManager and /usr/bin/com.system76.FirmwareManager.Notify.

Can you make them installed (or symlinked) to intuitive names, like firmware-manager and firmware-manager.Notify?

Thanks for maintaining!

dreieck commented on 2020-12-12 23:12 (UTC)

Your PKGBUILD downloads stuff in build().

This must not happen. No internet connection must be assumed in build() and package().

Please make sure that everything needed to build the software is downloaded in the source-array, if that is not possible use the prepare()-function and download stuff there. (source-array has the advantage that user's makepkg.conf-settings are honoured.)

==> Starting build()...
[...]
  Downloaded libdbus-sys v0.2.1
  Downloaded mac v0.1.1
  Downloaded maybe-uninit v2.0.0
[ lots of stuff downloading ]
 Downloading 6 crates, remaining bytes: 1.7 MB
[...]

Thanks for maintaining!

« First ‹ Previous 1 2 3