You are not logged in.
Pages: 1
Installed code package from official repository, but unable to launch it becuse of the following error :
electron4: error while loading shared libraries: libevent-2.1.so.7: cannot open shared object file: No such file or directory
Last edited by he15en6erg (2019-12-24 09:41:54)
Offline
https://wiki.archlinux.org/index.php/Sy … nsupported
How did you install code? Please post your pacman.log.
Last edited by WorMzy (2019-12-23 13:34:47)
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
https://wiki.archlinux.org/index.php/Sy … nsupported
How did you install code? Please post your pacman.log.
Here is the output of my pacman.log :
[2019-12-22 22:14] [PACMAN] Running 'pacman -S code'
[2019-12-22 22:46] [ALPM] transaction started
[2019-12-22 22:46] [ALPM] installed electron4 (4.2.12-1)
[2019-12-22 22:46] [ALPM] installed ripgrep (11.0.2-1)
[2019-12-22 22:46] [ALPM] installed code (1.39.2-1)
[2019-12-22 22:46] [ALPM] transaction completed
[2019-12-22 22:46] [ALPM] running 'systemd-update.hook'...
[2019-12-22 22:46] [ALPM] running 'update-desktop-database.hook'...Offline
If usr/lib/libevent-2.1.so.7 does not exist, wouldn't it mean that an older version of libevent got pulled in by something and that pacman is not aware of it?
Offline
Here is the output of my pacman.log :
[2019-12-22 22:14] [PACMAN] Running 'pacman -S code' [2019-12-22 22:46] [ALPM] transaction started [2019-12-22 22:46] [ALPM] installed electron4 (4.2.12-1) [2019-12-22 22:46] [ALPM] installed ripgrep (11.0.2-1) [2019-12-22 22:46] [ALPM] installed code (1.39.2-1) [2019-12-22 22:46] [ALPM] transaction completed [2019-12-22 22:46] [ALPM] running 'systemd-update.hook'... [2019-12-22 22:46] [ALPM] running 'update-desktop-database.hook'...
Offline
If usr/lib/libevent-2.1.so.7 does not exist, wouldn't it mean that an older version of libevent got pulled in by something and that pacman is not aware of it?
libevent-2.1.so.7 is the latest version of libevent as provided by the Arch Linux repositories. If OP doesn't have it, then they either don't have the latest version of libevent (i.e. due to a partial upgrade, faulty mirror, etc.), or their filesystem has gotten corrupted some how. Until we see the full pacman.log we can't assess what the situation is.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Zod wrote:If usr/lib/libevent-2.1.so.7 does not exist, wouldn't it mean that an older version of libevent got pulled in by something and that pacman is not aware of it?
libevent-2.1.so.7 is the latest version of libevent as provided by the Arch Linux repositories. If OP doesn't have it, then they either don't have the latest version of libevent (i.e. due to a partial upgrade, faulty mirror, etc.), or their filesystem has gotten corrupted some how. Until we see the full pacman.log we can't assess what the situation is.
Here is the complete pacman.log output.
Offline
So your last full system update was on the first of July? And you started an update but canceled it in Oct? Yep, classic partial update. After canceling an update, you can't install anything until you finish the update.
Edit: scratch that, the one in July was canceled as well. Your last full update was in Feb? Seriously? You're lucky things haven't broken before now.
Last edited by Scimmia (2019-12-24 05:35:23)
Offline
So your last full system update was on the first of July? And you started an update but canceled it in Oct? Yep, classic partial update. After canceling an update, you can't install anything until you finish the update.
Edit: scratch that, the one in July was canceled as well. Your last full update was in Feb? Seriously? You're lucky things haven't broken before now.
Yes. I am embarrassed. Upgrading the full system resolved my problem. Thank you.
Offline
Pages: 1