You are not logged in.
Hey,
It's been a few days now that I am not able anymore to mount any usb stick or external hdd with PCManFM.
Maybe it's related to this news: "ConsoleKit replaced by logind" by if that's the case I don't know how to deal with it.
Anyway, I thought that a pacman -Syu could be a good start, I happily saw a upgrade of libfm & pcmanfm was available, but I can't get the upgrade done:
[david@laptop ~]$ sudo pacman -Syu
[sudo] password for david:
:: Synchronizing package databases...
core is up to date
extra 1424.5 KiB 510K/s 00:03 [######################] 100%
community 1775.9 KiB 572K/s 00:03 [######################] 100%
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...Targets (2): libfm-1.1.0-1 pcmanfm-1.1.0-1
Total Download Size: 0.60 MiB
Total Installed Size: 4.86 MiB
Net Upgrade Size: -1.16 MiBProceed with installation? [Y/n] y
:: Retrieving packages from community...
libfm-1.1.0-1-x86_64 455.3 KiB 304K/s 00:01 [######################] 100%
pcmanfm-1.1.0-1-x86_64 160.5 KiB 502K/s 00:00 [######################] 100%
(2/2) checking package integrity [######################] 100%
(2/2) loading package files [######################] 100%
(2/2) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
libfm: /usr/include/libfm exists in filesystem
Errors occurred, no packages were upgraded.
If it can be of anyhelp:
My .xinitrc:
#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fiexec openbox-session
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
Thank you !
Offline
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
libfm is now a symlink to libfm-1.0, that's why you cannot upgrade the package. I renamed the original libfm folder an the upgrade went well.
Offline
I removed pcmanfm and all dependencies und reinstalled it. Another way to avoid that problem.
Offline
@DSpider: I wasn't aware of that thing "This is a design feature, not a flaw", sorry.
@phil: Thank you I did the same, as it isn't risky to my eyes, and it worked, thanks !
Offline
I removed pcmanfm and all dependencies und reinstalled it. Another way to avoid that problem.
I had the same problem.. Removed pcmanfm, updated and now it works.. Thank you!
Last edited by deniolp (2012-11-01 20:09:09)
@有志者事竟成@
Offline
From the link DSpider posted:
The issue is usually trivial to solve. A safe way is to first check if another package owns the file (pacman -Qo /path/to/file). If the file is owned by another package, file a bug report. If the file is not owned by another package, rename the file which 'exists in filesystem' and re-issue the update command. If all goes well, the file may then be removed.
Last edited by 2ManyDogs (2012-11-01 20:15:55)
Offline
pacman -S --force libfm
pacman -S pcmanfm
... according to pcmanfm's wiki
Last edited by BrainWorker (2012-11-02 04:12:15)
Offline
I do not see this in the wiki... I rather think this is bad advice, as it might make some users think they can use the --force flag all willy nilly, without a care.
Offline
Every installed package provides /var/lib/pacman/local/$package-$version/files file that contains metadata about this package. If this file gets corrupted - is empty or missing - it results in "file exists in filesystem" errors when trying to update the package. Such an error usually concerns only one package and instead of manually renaming and later removing all the files that belong to the package in question, you can run pacman -S --force $package to force pacman to overwrite these files.
Do not run pacman -Syu --force.
Offline
... according to pcmanfm's wiki
Okay, I thought you were referring to the pcmanfm page, and that someone had put that you should do that with that one package. I guess the above is probably a typo then. That quote from the pacman page seems much more reasonable, as it explains why it is safe to use the --force. Using the --force without understanding why, or at least being told by the news or a dev, is just outright dangerous... like michael jackson...
Offline
Using --force is perfectly correct solution here. /usr/include/libfm became symlink to /usr/include/libfm-1.0/ and pacman probably doesn't know how to handle it.
However I pushed libfm-1.1.0-2 with quite ugly fix.
Last edited by Barthalion (2012-11-02 10:07:03)
Offline