You are not logged in.

#1 2022-10-16 13:15:43

amixra
Member
Registered: 2022-01-24
Posts: 125

[Solved] FILES exists in filesystem

Updated after sometime. During installation laptop hung and on reboot i wasn't able to boot into the system. Using liveusb i did that chroot drill and reinstalled linux kernel and booted through lts version there is some problem with new version and also when trying to install all updates following error is obtained.

:: Proceed with installation? [Y/n] Y
(247/247) checking keys in keyring                                                                    [############################################################] 100%
(247/247) checking package integrity                                                                  [############################################################] 100%
(247/247) loading package files                                                                       [############################################################] 100%
(247/247) checking for file conflicts                                                                 [############################################################] 100%
error: failed to commit transaction (conflicting files)
pipewire: /usr/bin/pipewire exists in filesystem
pipewire: /usr/bin/pipewire-avb exists in filesystem
pipewire: /usr/bin/pw-cli exists in filesystem
pipewire: /usr/bin/pw-dot exists in filesystem
pipewire: /usr/bin/pw-dump exists in filesystem
pipewire: /usr/bin/pw-link exists in filesystem
pipewire: /usr/bin/pw-metadata exists in filesystem
pipewire: /usr/bin/pw-mon exists in filesystem
pipewire: /usr/bin/pw-profiler exists in filesystem
pipewire: /usr/bin/pw-reserve exists in filesystem
pipewire: /usr/bin/pw-top exists in filesystem
pipewire: /usr/bin/spa-inspect exists in filesystem
pipewire: /usr/bin/spa-json-dump exists in filesystem
pipewire: /usr/bin/spa-monitor exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/array.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/buffers.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/client.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/conf.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/context.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/control.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/core.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/data-loop.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/device.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/client-node.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/metadata.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/profiler.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/protocol-native.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/session-manager.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/session-manager/impl-interfaces.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/session-manager/interfaces.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/session-manager/introspect-funcs.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/session-manager/introspect.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/extensions/session-manager/keys.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/factory.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/filter.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/global.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/i18n.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-client.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-core.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-device.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-factory.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-link.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-metadata.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-module.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-node.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl-port.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/impl.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/keys.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/link.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/log.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/loop.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/main-loop.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/map.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/mem.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/module.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/node.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/permission.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/pipewire.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/port.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/properties.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/protocol.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/proxy.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/resource.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/stream.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/thread-loop.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/thread.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/type.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/utils.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/version.h exists in filesystem
pipewire: /usr/include/pipewire-0.3/pipewire/work-queue.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/buffer/alloc.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/buffer/buffer.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/buffer/meta.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/buffer/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/control/control.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/control/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/buffer.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/dict.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/format.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/log.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/mem.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/node.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/pod.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/debug/types.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/graph/graph.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/interfaces/audio/aec.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/monitor/device.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/monitor/event.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/monitor/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/monitor/utils.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/node/command.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/node/event.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/node/io.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/node/keys.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/node/node.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/node/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/node/utils.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/audio/dsd.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/audio/format-utils.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/audio/format.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/audio/iec958.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/audio/layout.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/audio/raw.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/audio/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/bluetooth/audio.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/bluetooth/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/format-utils.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/format.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/latency-utils.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/param.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/profiler.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/props.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/chroma.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/color.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/encoded.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/format-utils.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/format.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/multiview.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/raw.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/param/video/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/builder.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/command.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/compare.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/dynamic.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/event.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/filter.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/iter.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/parser.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/pod.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/pod/vararg.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/cpu.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/dbus.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/i18n.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/log-impl.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/log.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/loop.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/plugin-loader.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/plugin.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/system.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/support/thread.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/ansi.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/defs.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/dict.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/dll.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/hook.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/json-pod.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/json.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/keys.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/list.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/names.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/result.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/ringbuffer.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/string.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/type-info.h exists in filesystem
pipewire: /usr/include/spa-0.2/spa/utils/type.h exists in filesystem
pipewire: /usr/lib/libpipewire-0.3.so exists in filesystem
pipewire: /usr/lib/libpipewire-0.3.so.0 exists in filesystem
pipewire: /usr/lib/libpipewire-0.3.so.0.359.0 exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-access.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-adapter.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-avb.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-client-device.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-client-node.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-link-factory.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-metadata.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-portal.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-profiler.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-protocol-native.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-rt.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-rtkit.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-session-manager.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-spa-device-factory.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-spa-device.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-spa-node-factory.so exists in filesystem
pipewire: /usr/lib/pipewire-0.3/libpipewire-module-spa-node.so exists in filesystem
pipewire: /usr/lib/pkgconfig/libpipewire-0.3.pc exists in filesystem
pipewire: /usr/lib/pkgconfig/libspa-0.2.pc exists in filesystem
pipewire: /usr/lib/spa-0.2/avb/libspa-avb.so exists in filesystem
pipewire: /usr/lib/spa-0.2/control/libspa-control.so exists in filesystem
pipewire: /usr/lib/spa-0.2/support/libspa-dbus.so exists in filesystem
pipewire: /usr/lib/spa-0.2/support/libspa-journal.so exists in filesystem
pipewire: /usr/lib/spa-0.2/support/libspa-support.so exists in filesystem
pipewire: /usr/lib/spa-0.2/v4l2/libspa-v4l2.so exists in filesystem
pipewire: /usr/lib/spa-0.2/videoconvert/libspa-videoconvert.so exists in filesystem
pipewire: /usr/lib/spa-0.2/videotestsrc/libspa-videotestsrc.so exists in filesystem
pipewire: /usr/lib/systemd/user/pipewire.service exists in filesystem
pipewire: /usr/lib/systemd/user/pipewire.socket exists in filesystem
pipewire: /usr/share/licenses/pipewire/COPYING exists in filesystem
pipewire: /usr/share/locale/af/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/as/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/be/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/bg/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/bn_IN/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ca/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/cs/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/da/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/de/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/de_CH/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/el/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/eo/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/es/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/fi/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/fr/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/gl/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/gu/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/he/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/hi/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/hr/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/hu/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/id/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/it/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ja/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ka/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/kk/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/kn/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ko/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/lt/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ml/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/mr/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/my/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/nl/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/nn/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/oc/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/or/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/pa/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/pl/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/pt/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/pt_BR/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ro/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ru/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/si/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/sk/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/sr/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/sr@latin/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/sv/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/ta/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/te/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/tr/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/uk/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/zh_CN/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/locale/zh_TW/LC_MESSAGES/pipewire.mo exists in filesystem
pipewire: /usr/share/man/man1/pipewire.1.gz exists in filesystem
pipewire: /usr/share/man/man1/pw-cli.1.gz exists in filesystem
pipewire: /usr/share/man/man1/pw-dot.1.gz exists in filesystem
pipewire: /usr/share/man/man1/pw-link.1.gz exists in filesystem
pipewire: /usr/share/man/man1/pw-metadata.1.gz exists in filesystem
pipewire: /usr/share/man/man1/pw-mon.1.gz exists in filesystem
pipewire: /usr/share/man/man1/pw-profiler.1.gz exists in filesystem
pipewire: /usr/share/man/man1/pw-top.1.gz exists in filesystem
pipewire: /usr/share/man/man5/pipewire.conf.5.gz exists in filesystem
pipewire: /usr/share/pipewire/client-rt.conf exists in filesystem
pipewire: /usr/share/pipewire/client.conf exists in filesystem
pipewire: /usr/share/pipewire/minimal.conf exists in filesystem
pipewire: /usr/share/pipewire/pipewire-avb.conf exists in filesystem
pipewire: /usr/share/pipewire/pipewire.conf exists in filesystem
Errors occurred, no packages were upgraded.

Last edited by amixra (2022-10-19 12:47:58)


Experiment at-least.

Offline

#2 2022-10-16 13:19:47

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: [Solved] FILES exists in filesystem

RTFW.

EDIT: I see you've editted to give some context after I posted.  Had that been there initially, I may not have been quite so curt with my response.  But just the same, that link is what you need to see.

Last edited by Trilby (2022-10-16 13:21:32)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2022-10-16 13:20:06

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,838

Re: [Solved] FILES exists in filesystem

Interesting.
Is that supposed to be some sort of status report?

uggcf://jvxv.nepuyvahk.bet/gvgyr/Cnpzna#%22Snvyrq_gb_pbzzvg_genafnpgvba_(pbasyvpgvat_svyrf)%22_reebe

Edit: too late wink

Last edited by seth (2022-10-16 13:20:26)

Online

#4 2022-10-16 13:22:59

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

pacman -Qo pipewire

error: No package owns /usr/bin/pipewire

Am I supposed to rename all... those files(I am afraid a little if your response is yes).

Last edited by amixra (2022-10-16 13:28:52)


Experiment at-least.

Offline

#5 2022-10-16 13:31:31

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,838

Re: [Solved] FILES exists in filesystem

No.

Online

#6 2022-10-16 14:03:03

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: [Solved] FILES exists in filesystem

It would seem your local database info for pipewire was corrupted.  This would be a case in which you can use the overwrite flag described in the linked section of the wiki.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#7 2022-10-16 14:15:17

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

what about the glob? I didn't understood it. Is that supposed to cover all those filenames which I am receiving in error?


Experiment at-least.

Offline

#8 2022-10-16 14:17:10

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,838

Re: [Solved] FILES exists in filesystem

pacman -S pipewire --overwrite '*'

Possibly just fixing the db will allow you to update in a regular way

pacman -S --dbonly pipewire
pacman -Su

Last edited by seth (2022-10-16 14:18:27)

Online

#9 2022-10-16 14:29:14

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

Just dropping a few outputs which may be irrelevant but for the case, if it may help with further issues (if occurs on rebooting).

(1/1) checking available disk space                                                                   [############################################################] 100%
:: Processing package changes...
(1/1) reinstalling pipewire                                                                           [############################################################] 100%
ldconfig: File /usr/lib/libcdio++.so is empty, not checked.
ldconfig: File /usr/lib/libcdio.so.19.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgstplayer-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstvulkan-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgrantleethemeeditor.so.5 is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagick++.so.12.6.0 is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagick.so.3.24.0 is empty, not checked.
ldconfig: File /usr/lib/libgstcodecs-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libMagickWand-7.Q16HDRI.so.10.0.0 is empty, not checked.
ldconfig: File /usr/lib/libcdio++.so.1 is empty, not checked.
ldconfig: File /usr/lib/libudf.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgstphotography-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstwebrtc-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstcodecparsers-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libMagick++-7.Q16HDRI.so.5.0.0 is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagickWand.so.2 is empty, not checked.
ldconfig: File /usr/lib/libgrantleethemeeditor.so.5.21.2 is empty, not checked.
ldconfig: File /usr/lib/libMagickCore-7.Q16HDRI.so.10.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgsttranscoder-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstbadaudio-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstwayland-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgsttranscoder-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstcodecparsers-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstbadaudio-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstbasecamerabinsrc-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstsctp-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libiso9660++.so.0.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgstadaptivedemux-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libMagickCore-7.Q16HDRI.so.10 is empty, not checked.
ldconfig: File /usr/lib/libgstplay-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstplayer-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libKF5KDcraw.so.5.0.0 is empty, not checked.
ldconfig: File /usr/lib/libKF5KDcraw.so.5 is empty, not checked.
ldconfig: File /usr/lib/libgstmpegts-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstwayland-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstinsertbin-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstisoff-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstvulkan-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstisoff-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstplay-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgsturidownloader-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstcodecs-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstphotography-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgsturidownloader-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libMagick++-7.Q16HDRI.so is empty, not checked.
ldconfig: File /usr/lib/libgstinsertbin-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libMagick++-7.Q16HDRI.so.5 is empty, not checked.
ldconfig: File /usr/lib/libudf.so is empty, not checked.
ldconfig: File /usr/lib/libgstadaptivedemux-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagickWand.so.2.9.7 is empty, not checked.
ldconfig: File /usr/lib/libgstcodecparsers-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagick.so is empty, not checked.
ldconfig: File /usr/lib/libgstcodecs-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstwebrtc-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstsctp-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagickWand.so is empty, not checked.
ldconfig: File /usr/lib/libMagickCore-7.Q16HDRI.so is empty, not checked.
ldconfig: File /usr/lib/libgstmpegts-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libcdio++.so.1.0.0 is empty, not checked.
ldconfig: File /usr/lib/libgstwayland-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagick++.so.12 is empty, not checked.
ldconfig: File /usr/lib/libgstisoff-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstplay-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstbasecamerabinsrc-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstvulkan-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstadaptivedemux-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libudf.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstbasecamerabinsrc-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libiso9660++.so is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagick++.so is empty, not checked.
ldconfig: File /usr/lib/libgsturidownloader-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstbadaudio-1.0.so is empty, not checked.
ldconfig: File /usr/lib/libgstwebrtc-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libGraphicsMagick.so.3 is empty, not checked.
ldconfig: File /usr/lib/libiso9660++.so.0 is empty, not checked.
ldconfig: File /usr/lib/libMagickWand-7.Q16HDRI.so is empty, not checked.
ldconfig: File /usr/lib/libgstmpegts-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstsctp-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libcdio.so is empty, not checked.
ldconfig: File /usr/lib/libcdio.so.19 is empty, not checked.
ldconfig: File /usr/lib/libgstphotography-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libgstplayer-1.0.so.0 is empty, not checked.
ldconfig: File /usr/lib/libgstinsertbin-1.0.so.0.2004.0 is empty, not checked.
ldconfig: File /usr/lib/libiso9660.so.11 is empty, not checked.
ldconfig: File /usr/lib/libMagickWand-7.Q16HDRI.so.10 is empty, not checked.
ldconfig: File /usr/lib/libiso9660.so is empty, not checked.
ldconfig: File /usr/lib/libiso9660.so.11.0.0 is empty, not checked.
ldconfig: File /usr/lib/libKF5KDcraw.so is empty, not checked.
:: Running post-transaction hooks...

same output on issuing --dbonly one also

On upgrading

(246/246) checking for file conflicts                                                                 [############################################################] 100%
(246/246) checking available disk space                                                               [############################################################] 100%
:: Running pre-transaction hooks...
(1/2) Remove DKMS modules
(2/2) Unregistering Haskell modules...
error: command failed to execute correctly
:: Processing package changes...
.
.

wish me luck for rebooting with latest rusty kernel.

Last edited by amixra (2022-10-16 14:30:26)


Experiment at-least.

Offline

#10 2022-10-16 14:30:34

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,653

Re: [Solved] FILES exists in filesystem

You need to reinstall all packages involved in the failed update. If it was a lot of packages, might as well reinstall all packages. Info on the wiki for that.

Online

#11 2022-10-16 15:08:36

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

Few reboots(that too for configuring boot from the right kernel) and finally on the other shore.


Experiment at-least.

Offline

#12 2022-10-18 12:31:50

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

Scimmia wrote:

You need to reinstall all packages involved in the failed update. If it was a lot of packages, might as well reinstall all packages. Info on the wiki for that.

Hmm... Actually you were right. Problem wasn't really solved. I was required to reinstall all packages. Infact, I wasn't able to do it from the terminal itself because system started crashing again and again.
So chrooted through liveusb and then did the following sequence, just want to confirm if all of the problems are really solved.

# pacman -Syyu $(pacman -Qnq)

Given the fact, I was reinstalling everything, still "Net Upgrade size" was somewhere around 500 MB which made me a little suspicious. Allowed reinstalling, after package integrity check similar errors(as I have got through pipewire in the first post) but by other packages were thrown. Performed the same three commands, given by seth above for all of them, one by one. Some packages then later asked for deletion because some keys weren't matching, so downloaded and installed themselves individually.

Finally, Errors aren't there but I don't know if it started recently or was there already but checking `journalctl -p 3 -b` shows some `xdg-desktop-portal-kde` crashed error.

Last edited by amixra (2022-10-18 12:34:11)


Experiment at-least.

Offline

#13 2022-10-18 12:37:03

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

One more thing I have a hook in pacman which checks if any package needs to be rebuilt. Why didn't that got invoked?


Experiment at-least.

Offline

#14 2022-10-18 13:04:08

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: [Solved] FILES exists in filesystem

It looks like you've taken the right steps to treat the symptoms, but such repeated / systemic errors begs the question of the underlying cause.  One possible cause is a failing drive, in which case, treating the symptoms will not get you very far.  Other potential causes may still be present to re-trigger related issues.

As for the pacman hook, what is the hook?  And why would you expect it to get invoked?  Were there any packages at any stage of this process that met the critieria it uses to determine that they need to be rebuilt?  That pretty much only applies to AUR packages (as devs rebuild repo packages when it is needed).

Last edited by Trilby (2022-10-18 13:13:53)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#15 2022-10-18 13:49:08

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

Hmm... drive failure... quite possible with this one as it is aging.
Can't really remember what was the hook but I had installed it as a result of reading something like this should be used, in wiki. And it says "checking which package needs to be rebuilt" every time I install something or upgrade the system.


Experiment at-least.

Offline

#16 2022-10-18 14:30:37

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 73,838

Online

#17 2022-10-18 14:38:41

Stefan Husmann
Member
From: Germany
Registered: 2007-08-07
Posts: 1,391

Re: [Solved] FILES exists in filesystem

amixra wrote:

Hmm... drive failure... quite possible with this one as it is aging.
Can't really remember what was the hook but I had installed it as a result of reading something like this should be used, in wiki. And it says "checking which package needs to be rebuilt" every time I install something or upgrade the system.

This is the rebuild detector.

Offline

#18 2022-10-18 15:38:10

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: [Solved] FILES exists in filesystem

There are a couple of these "rebuild detector" hooks out there.  My point was more why you thought that was relevant?  It's not a magical crystal ball that detects when there might be anything wrong with any package - it does a specific check for binaries that link against libraries that are no longer installed.  That has nothing to do with your present errors.  But anyways, doing a smart check would be ... smart.  But note that a failing drive was just one possible root cause of these issues - there are countless others.

Generally I'd not dig too deep in looking for a cause if you had an isolated incident of this kind of error.  Sometimes you can get these errors due to running a make install as root, or running some tools build in "updater" as root.  Other times it could be from a power failure or otherwise interrupted pacman upgrade operation.  If they are such isolated incidences, you just patch up the symptoms and move on.  But if it has happened multiple times with multiple packages and / or there is no known mistake that caused it, then you should dig deeper or the problem will just keep coming back.

Last edited by Trilby (2022-10-18 15:41:45)


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#19 2022-10-19 12:45:38

amixra
Member
Registered: 2022-01-24
Posts: 125

Re: [Solved] FILES exists in filesystem

Since things look good, so maybe better to move on. One reason, I could relate to is that I had updated after a long time, so it was taking its time to install updates and it was interrupted in between by a sudden laptop crash. And then I was required to restart updating and manual removal of `db.lck` was required. And then it kind of started chaining that during the update laptop crashed again and then retried and again. So maybe something random created this spiral loop of crash-update-crash. Whatever. Things at least feel good now. Maybe just a bad day.

Last edited by amixra (2022-10-19 12:47:17)


Experiment at-least.

Offline

#20 2022-10-19 13:01:24

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,456
Website

Re: [Solved] FILES exists in filesystem

Yes, a crash mid update is also a prime suspect for such symptoms.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

Board footer

Powered by FluxBB