You are not logged in.
- Topics: Active | Unanswered
#1 2016-02-20 05:49:19
- sashang
- Member
- Registered: 2011-11-22
- Posts: 23
bad file descriptor when running pacman
Anyone seen this before?
~ > sudo pacman -S gvim
warning: gvim-7.4.1294-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) gvim-7.4.1294-1
Total Installed Size: 2.99 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [##############################################################################################] 100%
(1/1) checking package integrity [##############################################################################################] 100%
(1/1) loading package files [##############################################################################################] 100%
(1/1) checking for file conflicts [##############################################################################################] 100%
(1/1) checking available disk space [##############################################################################################] 100%
:: Processing package changes...
(1/1) reinstalling gvim [##############################################################################################] 100%
stty: standard input: Bad file descriptor
bin
boot
dev
etc
home
lib
lib64
lost+found
mnt
opt
proc
root
run
sbin
srv
sys
tmp
usr
var
yum-cron.service
~ > The installation completes successfully
Last edited by sashang (2016-02-20 05:49:44)
Offline
#2 2016-02-20 05:59:19
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: bad file descriptor when running pacman
Paste the full command an output with --debug, and your pacman.conf.
What is yum-cron.service?
Offline
#3 2016-02-29 20:33:09
- bdantas
- Member
- Registered: 2014-05-13
- Posts: 94
Re: bad file descriptor when running pacman
Today I started getting this error when using pacman, too. Packages are installed and uninstalled normally, but the error seems to show up every time a package is installed or uninstalled, regardless of package. Here is an example command with --debug. Pacman.conf to follow.
$ sudo pacman -S --debug galculator-gtk2
debug: pacman v5.0.0 - libalpm v10.0.0
...
debug: executing "/usr/bin/bash" under chroot "/"
stty: 'standard input': Bad file descriptor
debug: call to waitpid succeeded
...Offline
#4 2016-02-29 20:40:15
- bdantas
- Member
- Registered: 2014-05-13
- Posts: 94
Re: bad file descriptor when running pacman
Here is my /etc/pacman.conf:
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives
#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
#GPGDir = /etc/pacman.d/gnupg/
HoldPkg = pacman glibc
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta = 0.7
Architecture = auto
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options
#UseSyslog
ILoveCandy
Color
#TotalDownload
CheckSpace
#VerbosePkgLists
# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required
# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.
#
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#
# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
Include = /etc/pacman.d/mirrorlist
#SigLevel = Optional TrustAll
[extra]
Include = /etc/pacman.d/mirrorlist
#SigLevel = Optional TrustAll
#[community-testing]
#Include = /etc/pacman.d/mirrorlist
[community]
Include = /etc/pacman.d/mirrorlist
#SigLevel = Optional TrustAll
# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.
#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist
[multilib]
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
[bruno]
Server = http://dantas.airpost.net/repo
#[libre]
#Server = https://repo.parabola.nu/libre/os/$arch
#SigLevel = Optional TrustAllOffline
#5 2016-02-29 20:48:10
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: bad file descriptor when running pacman
bdantas wrote:
pacman v5.0.0 - libalpm v10.0.0
pacman -SyuOffline
#6 2016-02-29 20:56:52
- bdantas
- Member
- Registered: 2014-05-13
- Posts: 94
Re: bad file descriptor when running pacman
I upgrade by hopping from snapshot to snapshot on Arch Linux Archive (formerly Arch Rollback Machine).
Nevertheless, I upgraded just pacman and can confirm that with pacman 5.0.1-2 the error is gone.
Offline