@pillgar: just set parallel download to 0.
See this issue: https://gitlab.manjaro.org/applications/pamac/issues/523
Git Clone URL: | https://aur.archlinux.org/pamac-aur.git (read-only, click to copy) |
---|---|
Package Base: | pamac-aur |
Description: | A Gtk frontend, Package Manager based on libalpm with AUR and Appstream support |
Upstream URL: | https://github.com/manjaro/pamac |
Keywords: | gui installer libalpm package pacman yay |
Licenses: | GPL-3.0-or-later |
Conflicts: | pamac, pamac-cli, pamac-tray-appindicator |
Provides: | pamac, pamac-cli |
Submitter: | Zeph |
Maintainer: | Zeph |
Last Packager: | Zeph |
Votes: | 407 |
Popularity: | 2.33 |
First Submitted: | 2013-12-05 12:57 (UTC) |
Last Updated: | 2025-01-26 20:10 (UTC) |
« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 40 Next › Last »
@pillgar: just set parallel download to 0.
See this issue: https://gitlab.manjaro.org/applications/pamac/issues/523
Since upgrading to 7.3, I get "The requested URL returned error: 404 Not Found" warning popup. Though the download/update's do complete successfully, I think it might be a false flag. It doesn't seem to be reproducible in previous versions or using a terminal.
Hey, is it possible to add a desktop entry for pamac-manager? Would be quite useful
@blackhole: Use issue on repo for software error
Today, trying to update some AUR package: ERROR:../src/transaction.vala:140:pamac_transaction_check_authorization_co: code should not be reached
Package pamac-7.0.1-1.tar.gz:
$ LANG=en_US pamac-updater
(pamac-updater:7109): Gtk-WARNING **: 11:40:30.621: Locale not supported by C library. Using the fallback 'C' locale.
(pamac-updater:7109): GLib-GObject-CRITICAL **: 11:40:30.807: g_object_new_valist: invalid object type 'PamacManagerWindow' for value type 'PamacDatabase'
(pamac-updater:7109): CRITICAL : 11:40:30.819: pamac_database_get_config: assertion 'self != NULL' failed
(pamac-updater:7109): CRITICAL : 11:40:30.819: pamac_config_get_environment_variables: assertion 'self != NULL' failed
(pamac-updater:7109): GLib-CRITICAL **: 11:40:30.819: g_hash_table_iter_init: assertion 'hash_table != NULL' failed Memory overflow (core file created) <== translated this
@j0hannes: just open a bug on pamac bug tracker. More useful than posting a comment here.
My /tmp partition (tmpfs) has a size of 7.6 GB. Installing big packages with pamac makes my machine unresponsive and eventually leads to segfaults and reboot (if the fakeroot environment grows bigger than the available space in /tmp.
Downloading the snapshot and making the package in a different location manually is a workaround, but do I need to see my system crashing to realize that a package probably won't build in /tmp? Could pamac maybe monitor the available space there and cancel its build process when it's running low? Maybe also offering the user to build it again in a different location?
Uninstalled with "aurman -Rnsuv pamac-aur" and inslled again with "aurman -S pamac-aur". Worked fine.
Same as andrelevou1980.
Pinned Comments
Zeph commented on 2022-06-04 13:58 (UTC) (edited on 2024-10-29 07:25 (UTC) by Zeph)
For some problems with pamac, check or create issues on