Roman Kyrylych wrote:
Hi!
I've been inactive for the past year, so I don't know if this is already fixed. Sometimes I get segmentation fault during downloading db or package. This is the latest output from today. As you may see this is with --debug, but it doesn't really helps to get idea on what may cause the segfault.
Targets (3): audacious-plugins-2.1-1 audacious-2.1-1 python-2.6.2-4
Total Download Size: 18.47 MB Total Installed Size: 73.52 MB
Proceed with installation? [Y/n] debug: using cachedir: /var/cache/pacman/pkg/ :: Retrieving packages from extra... debug: using 'audacious-plugins-2.1-1-x86_64.pkg.tar.gz' for download progress debug: HTTP_PROXY: (null) debug: http_proxy: (null) debug: FTP_PROXY: (null) debug: ftp_proxy: (null) debug: connected to dev.archlinux.org successfully downloading audacious-plugins-2.1-1-x86_64.pkg.tar.gz... error: segmentation fault Internal pacman error: Segmentation fault. Please submit a full bug report with --debug if appropriate.
At the time of this segfault I was connected to a wireless network with quite unstable connection (disconnects are rare, but I think packet loss might have place).
Seems like libfetch related issue. Is this known? Or if it's alpm/pacman-related - was something like this fixed in git?
P.S.: looks like --debug is not even mentioned in the man page, is this intentional or just forgotten?
I'm sure there is a bug report still open about this. It does seem releated to unstable networks. From memory, there has been no-one who can replicate consistently so that we can debug to source of the crash. Allan