[SOLVED]problems after new installation installing/updating programs

funkmuscle · 2018-06-24 17:10:13

hey, I've been having issues with my system freezing, crashing and rebooting.. I've read the forums and those issues seem to be related to Intel and laptops.
I have AMD so I decided to reinstall when no help was found.

Now I keep getting all kind of package install errors

for instance I thought is was the base packages so I was reinstalling them.

error: extract: not overwriting dir with file /usr/lib64

Then, installing from AURS

Cleaning up...
:: Unable to find a built tarball for...

It will build the package though.

If I install a new program using pacman, I get this:

ldconfig: File /usr/lib/libprojectM.so.2 is empty, not checked.
ldconfig: File /usr/lib/libprojectM.so is empty, not checked.
ldconfig: File /usr/lib/libprojectM.so.2.1.0 is empty, not checked.

anyone know what is happening?

Last edited by funkmuscle (2018-06-25 20:00:09)

V1del · 2018-06-24 20:08:12

Post complete outputs and exact commands used in addition to that post a

journalctl -b

and a pacman.log

WorMzy · 2018-06-24 21:23:32

Please also change your topic title to something that actually describes your problem.

https://wiki.archlinux.org/index.php/Co … ow_to_post

Mod note: Not an installation Issue, moving to NC.

funkmuscle · 2018-06-25 13:04:36

an example:

$ sudo pacman -S x42-plugins
[sudo] password for harv: 
resolving dependencies...
looking for conflicting packages...

Packages (3) libltc-1.3.0-2  zita-convolver-3.1.0-6  x42-plugins-20180320-2

Total Download Size:   0.95 MiB
Total Installed Size:  5.59 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 libltc-1.3.0-2-x86_64     28.6 KiB   358K/s 00:00 [######################] 100%
 zita-convolver-3.1....    17.6 KiB  0.00B/s 00:00 [######################] 100%
 x42-plugins-2018032...   930.4 KiB  2.06M/s 00:00 [######################] 100%
(3/3) checking keys in keyring                     [######################] 100%
(3/3) checking package integrity                   [######################] 100%
(3/3) loading package files                        [######################] 100%
(3/3) checking for file conflicts                  [######################] 100%
(3/3) checking available disk space                [######################] 100%
:: Processing package changes...
(1/3) installing libltc                            [######################] 100%
(2/3) installing zita-convolver                    [######################] 100%
(3/3) installing x42-plugins                       [######################] 100%
ldconfig: File /usr/lib/libprojectM.so.2 is empty, not checked.
ldconfig: File /usr/lib/libprojectM.so is empty, not checked.
ldconfig: File /usr/lib/libprojectM.so.2.1.0 is empty, not checked.
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

installing from AUR example:

 $ trizen -S jalv-select
Cloning into 'jalv-select'...
remote: Counting objects: 47, done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 47 (delta 11), reused 47 (delta 11)
Unpacking objects: 100% (47/47), done.

:: Package: jalv-select
:: AUR URL: https://aur.archlinux.org/packages.php?ID=478350

==> Validating source files with md5sums...
    V1.0.tar.gz ... Passed
==> Extracting sources...
  -> Extracting V1.0.tar.gz with bsdtar
==> Starting build()...
g++ -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -std=c++11 `pkg-config gtkmm-2.4 lilv-0 --cflags`  jalv.select.cpp  -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -lX11 `pkg-config gtkmm-2.4 lilv-0 --libs`  -o jalv.select
\033[1;34mbuild finish, now run make install
\033[0m
==> Entering fakeroot environment...
==> Starting package()...
\033[1;34mbuild finish, now run make install
\033[0m
install jalv.select /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/bin
cp jalv.select.desktop /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/share/applications
cp lv2.png /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/share/pixmaps
cp lv2_16.png /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/share/pixmaps
cp jalv.select.1 /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/share/man/man1
cp jalv.select.fr.1 /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/share/man/man1
gzip /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/share/man/man1/jalv.select.1
gzip /tmp/trizen-harv/jalv-select/pkg/jalv-select/usr/share/man/man1/jalv.select.fr.1
. . \033[1;34m, done\033[0m
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "jalv-select"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: jalv-select 1.0-3 (Mon 25 Jun 2018 08:53:36 AM EDT)
==> Cleaning up...
:: Unable to find a built tarball for jalv-select

The thing is, it does build the program. I have to go to the folder where the build ends up and do a pacman -U

journalctl -b
https://pastebin.com/twdVZaf6

pacman.log
https://pastebin.com/HERhWtDT

loqs · 2018-06-25 13:08:21

pacman -Qkk projectm

Edit:

[2018-06-22 14:53] [PACMAN] Running 'pacman -U --force lmms-qt5-git-1.2.0.rc5.r5.ga3d72def4-1-x86_64.pkg.tar.xz'

why the --force?

[2018-06-24 10:28] [PACMAN] Running 'pacman -Syyu'

Is your mirror broken if not why do you keep running -yy?
Edit:
I can not find the following in the logs you posted:

error: extract: not overwriting dir with file /usr/lib64

Last edited by loqs (2018-06-25 13:14:40)

funkmuscle · 2018-06-25 13:22:47

the --force was because it would not install. I kept getting errors.

Over the years, I read conflicting uses of pacman in these forums. The most I've seen in these forums were pacman -Syyu so I used. Also I've tested pacman -Syu and I would get system up to date them run -Syyu after and would get an update.
Tested that many time and got the same result so I just use it now.

Is that an issue?

loqs · 2018-06-25 13:27:37

Please post the output of

pacman -Qkk projectm

Do you know the difference between

pacman -Syu
pacman -Syyu

What were those errors how did you determine --force was appropriate?
Edit:
Was

error: extract: not overwriting dir with file /usr/lib64

one of the errors?

Last edited by loqs (2018-06-25 13:33:09)

funkmuscle · 2018-06-25 13:37:11

$ sudo pacman -Qkk projectm
error: error while reading file /var/lib/pacman/local/projectm-2.1.0-17/mtree: Unrecognized archive format
projectm: no mtree file

I can't remember why I used force. I think it was a qt5 error.

To be honest, I think the -Syyu was to do a full update or a force where as -Syu is a normal update??

loqs · 2018-06-25 13:46:20

Reinstalling projectm should fix

ldconfig: File /usr/lib/libprojectM.so.2 is empty, not checked.
ldconfig: File /usr/lib/libprojectM.so is empty, not checked.
ldconfig: File /usr/lib/libprojectM.so.2.1.0 is empty, not checked.

man pacman wrote:

-y, --refresh
Download a fresh copy of the master package database from the
server(s) defined in pacman.conf(5). This should typically be used
each time you use --sysupgrade or -u. Passing two --refresh or -y
flags will force a refresh of all package databases, even if they
appear to be up-to-date.

Yes you are forcing a database download from the mirror even if the mirror has not changed. Why would you repeatedly do that unless you believe the mirror is broken?
Just because others use a command does not mean it is needed or encouraged.

No way to know what damage the --force will have done.

Without the command producing

error: extract: not overwriting dir with file /usr/lib64

I can not help with that sorry.

I would suggest running `pacman -Qkk` to check for other issues after fixing projectm
edit:
Added some line breaks for formatting

Last edited by loqs (2018-06-25 13:47:19)

funkmuscle · 2018-06-25 15:45:36

loqs, thanx a million. Reinstalling projectm fixed the one issue.
pacman -Qkk pointed a few things out to be fixed but still the error when building from AUR.

Oh, the --force was due the pacman read out

 'exists in filesystem' Errors occurred, no packages were upgraded

Just tried any package from AUR using packer this time as aurs, yaourt, trizen and pacaur all give the same error:

 from packer
loading packages...
error: 'fetchmirrors-*.pkg.tar.xz': could not find or read package

Yet it was build but runs with errors. I've used this app before.

Also I forgot to mention, I have Arch on a laptop and I'm having the same issues with AUR and the aurhelpers.

Scimmia · 2018-06-25 15:56:56

And instead of fixing the errors, you decided to attempt to destroy your system. Great decision.

funkmuscle · 2018-06-25 16:12:04

Scimmia wrote:

And instead of fixing the errors, you decided to attempt to destroy your system. Great decision.

so you're saying reinstall?
I don't mind. Just want the headache gone.

by the way, I just followed this from the wiki

Every installed package provides a /var/lib/pacman/local/package-version/files file that contains metadata about this package. If this file gets corrupted, is empty or goes missing, it results in file exists in filesystem errors when trying to update the package. Such an error usually concerns only one package. Instead of manually renaming and later removing all the files that belong to the package in question, you may exceptionally run pacman -S --overwrite package to force pacman to overwrite these files.

I'm reinstalling to save me time.. Thanx everyone for your help but I need this up and running as I have music projects to finish. I will do the same with the laptop but I never ever used --force or --overwrite on the laptop yet having issues.

I do know the dangers of using --force or --overwrite but was using it as the wiki instructed.

Should I mark this solved as I reinstalling?

Arch Linux

#1 2018-06-24 17:10:13

[SOLVED]problems after new installation installing/updating programs

#2 2018-06-24 20:08:12

Re: [SOLVED]problems after new installation installing/updating programs

#3 2018-06-24 21:23:32

Re: [SOLVED]problems after new installation installing/updating programs

#4 2018-06-25 13:04:36

Re: [SOLVED]problems after new installation installing/updating programs

#5 2018-06-25 13:08:21

Re: [SOLVED]problems after new installation installing/updating programs

#6 2018-06-25 13:22:47

Re: [SOLVED]problems after new installation installing/updating programs

#7 2018-06-25 13:27:37

Re: [SOLVED]problems after new installation installing/updating programs

#8 2018-06-25 13:37:11

Re: [SOLVED]problems after new installation installing/updating programs

#9 2018-06-25 13:46:20

Re: [SOLVED]problems after new installation installing/updating programs

#10 2018-06-25 15:45:36

Re: [SOLVED]problems after new installation installing/updating programs

#11 2018-06-25 15:56:56

Re: [SOLVED]problems after new installation installing/updating programs

#12 2018-06-25 16:12:04

Re: [SOLVED]problems after new installation installing/updating programs

Board footer