Pacman -Syu today...Kernel2.6.5-2 and XFree86-4.4.0-1

Attempted the upgrade and received query....remove ttf-bitstream-vera?
Answered Yes. Prceeded with upgrade.
Loading of XFree86-4.4.0-1 encountered conflicts.
Is it again necessary to remove XFree86 before the upgrade and install it after removal as was done per announcements?
Does ttf-bitstream-vera go back in? :?: :?: :?:

Two other fonts /usr/X11R6/lib/X11/fonts/100dpi(75dpi also) arealready in filesystem.
These conflicts halt the upgrade.

Similar Messages

No ping / traceroute / google earth since Pacman Syu today

Hello,
I did a pacman -Syu this morning as I do most days. To be honest I can't recall precisely what was updated (kernel headers, glibc not sure what else - sorry). I am now finding that while I can surf the web / be on IRC / dowload my e-mails - some things are broken. I am not sure if they are related, but they were all working very recently. I use pan for usenet and it is giving me "no such process" when trying to contact my news server. whois is giving "Temporary failure in name resolution", ping and traceroute are is giving "unknown host" on everything, and google earth "cannot contact authentication server".
I have not done anthing to my network settings or router, and other boxes using it can still (eg) ping out.
I am nervous about trying a reboot in case I lose the connectivity I have, because I really need this box functional on the net at the moment.
I am baffled. Any ideas please?
Added by way of edit : - I had both Firefox and Opera open. I tried closing Opera and on restarting it cannot connect to the net. I suppose that I will lose connectivity with other applications if I close them.
Second edit : So I got my head out of my rear sufficiently to read the pacman.log. Todays upgrades were :
[2008-12-16 10:15] starting full system upgrade
[2008-12-16 10:28] upgraded kernel-headers (2.6.26.3-1 -> 2.6.27.6-2)
[2008-12-16 10:28] warning: /etc/locale.gen installed as /etc/locale.gen.pacnew
[2008-12-16 10:28] Generating locales...
[2008-12-16 10:28] en_GB.UTF-8... done
[2008-12-16 10:28] en_GB.ISO-8859-1... done
[2008-12-16 10:28] Generation complete.
[2008-12-16 10:28] upgraded glibc (2.8-3 -> 2.9-2)
[2008-12-16 10:28] upgraded binutils (2.18-9 -> 2.19-1)
[2008-12-16 10:28] upgraded bison (2.3-4 -> 2.4.1-1)
[2008-12-16 10:28] upgraded dhcpcd (4.0.4-1 -> 4.0.7-1)
[2008-12-16 10:28] upgraded gcc-libs (4.3.2-1 -> 4.3.2-2)
[2008-12-16 10:28] upgraded gcc (4.3.2-1 -> 4.3.2-2)
[2008-12-16 17:16] synchronizing package lists
I don't know what could cause this apart from glibc.
I am also wondering whether this is the related to the issue metalforever reported earlier today with his "transient resolver failure"
It makes no difference to run as root btw.
Last edited by perseus (2008-12-16 17:56:35)

I found that the problem was a DNS one. ping etc worked if I fed it IP addresses instead of domain names. I am using pdnsd, which seemed to be working so far as I could tell. The daemon was running and "pdnsd-ctl dump" output the contents of what seems to be a valid cache. I changed /etc/resolv.conf to stop using pdnsd temporarily and my DNS came back.
I still don't have the faintest idea why this problem has arisen. I am too busy to try taking it any further at the moment. Maybe I should cross-post this in the networking forum.

System "broken" after pacman -Syu

Hi there,
I ran a pacman -Syu today, without reading the news, so I didn't ignore filesystem and glibc. Now the system is totally broken, cannot initiate new ssh sessions, and commands like ls or pacman, or everything I tried so far except cd gives the following error:
bash: /usr/bin/ls: No such file or directory
The system is not yet upgraded to systemd, I was about to do it after this system upgrade.
I realize this is bleeding edge, not bleeding flat, so I should bring my own parachute, but I have no idea how to fix this.

ewaller wrote:
That is so 2012
You might try this
Also, look at this article
Note that you cannot chroot in as you will have the same problem in a chroot environment.
Thank you for the suggestions. I tried it, and made things worse. When booting it says:
Waiting 10 seconds for device /dev/disk/by-uuid/[uuid] ...
Error device /dev/disk/by-uuid/[uuid] not found.
Skipping fsck
Error unable to find root device /dev/disk/by-uuid/[uuid].
You are being dropped to a recovery shell, type "exit" to try and continue booting.
sh: can't access tty, turning job control off.
Very same on the fallback as well.
The strangest thing is, that the recovery shell does not respond to keyboard, while GRUB, and the BIOS did.

[SOLVED] pacman -Syu took an extremely long time today

Hey,
this is the first time I've encountered such an issue:
today I upgraded as usual (pacman -Syu) but the process took an extremely long time
(~20 minutes). The last time I upgraded was three days ago.
The culprits seem to have been the libreoffice-still and texlive packages.
Has anyone else had this problem? What could have caused this?
Last edited by Aton (2014-08-31 09:40:25)

hoschi wrote:Note to myself: Texlive is huge, really huge.
Unless you've installed https://www.archlinux.org/groups/any/texlive-lang/ and https://www.archlinux.org/packages/extr … ontsextra/ too, texlive is not that big.

[SOLVED] Did pacman -Syu and now gdm, gnome, and pacman won't work

Hi everyone, I did a search for my problem, but cannot find the solution. Basically, I updated my computer this morning and as soon as the packages got installed my computer crashed. I am using another computer right now. These were the packages that were upgraded: dbus-core, bluez, dbus, gsfonts, libcups, libgdiplus, mono, openssl.
So after I installed the packages, my screen went black with some error message (don't remember what it is now. I believe it was something about GDM not working.) So I rebooted and "rpcbind" and "File Alteration Monitor" failed. Then I got a bunch of Gdm error messages with "gdm-binary[46081]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors" as the last message. I don't know how to check the X server log for errors so I logged in and tried pacman -Syu again. I got this error "pacman: error while loading shared libraries: /usr/lib/libssl.so.0.9.8: invalid ELF header." I also tried startx and gnome-session , but they both failed to work as well. It seems like I'm having a graphics error. I don't know what to do now. Any help would be appreciated.
Last edited by Eivuwan (2010-04-01 06:24:17)

Eivuwan wrote:Hi everyone. After some thinking, I realized that as attached as I am to Arch, I do not have as much free time as I did in the past to tinker with it. So I manually mounted my IPod and copied everything in my home folder to it. Then I installed Ubuntu. Maybe I'll come back to Arch one day, but for now, farewell. Thanks for all your help.
Wise decision -- Ubuntu is very stable (we used it extensively in my last place of business; I'm now retired). I've gone a different route, since I prefer to start small, build the environment I want and nothing more (which was my reason for choosing Arch). My preferred environment is pretty minimal -- no desktop system (no Gnome or KDE), just a window manager (dwm) and the apps I need. I did a test install in the last day or so and learned enough about Slackware (I first used it in the early 90s when it was pretty much the only Linux distribution) to convince myself that it will work for me. It's more of a pain to get the apps installed than Arch, certainly, but once you know how to do it and where to find them, it's not really a problem. But my objective is the same as yours -- get away from Arch's rolling releases. Again, as an old hand at both individual development and managing large software projects, what Arch is trying to do is difficult. Because the various components of the system are updated more or less continuously, it's impossible to thoroughly test the whole thing every time it changes. So on any particular day, you are likely to see problems, as happened to you, me, and other folks who have started threads in this category. And sometimes the problems are so severe you end up with a non-functioning system, as happened to both of us.
I would hope that, in the future, the powers-that-be at Arch would consider periodic, thoroughly tested releases, say every 6 months like Ubuntu and OpenBSD. The fundamental machinery of Arch is excellent (pacman, etc.), installation is easy, the documentation is adequate (I'm not as impressed by the wiki as others seem to be -- see the OpenBSD or FreeBSD documentation; what's available for Slackware is also very good). But I think there are tremendous quality hazards in the rolling release methodology, and forcing it on Arch's users is a bad idea, I think. It can be optional, for the adventurous. This is exactly how the OpenBSD people operate. There's a release every 6 months that is invariably rock solid. If they find problems after the release, they will make changes on a STABLE cvs branch. But you can also, if you choose, run what is on the cvs trunk, which they designate CURRENT, if you are so inclined and willing to take the chance on less thoroughly tested code. This is more or less equivalent to Arch now. I'm suggesting that Arch consider adding a STABLE version.

Pacman -Syu reports up to date(upgraded ok today)

Two problems accur with pacman.
If I try
pacman -Syu
I get :
bash-4.0# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
warning: avidemux: local (2.5.1-1) is newer than extra (2.5.0-1)
local database is up to date
bash-4.0#
But there is a new extra package for avidemux now and the kernel is an upgrade as well. These are not recognized and downloaded and installed.
I tried changing mirrors and also pacman.conf to allow wget.
Attempt to use wget resulted in ...xfer command not recognized.
I am not able to upgrade to the new kernel.
However, in another HDD with archlinux I am able to upgrade the kernel.
Pacman seems to be malfunctioning for the HDD not upgrading.
Tried ...pacman -Syy but no help.
Tried reinstall pacman...no help.
Does having avidemux-2.5.1-1 already in my machine cause this problem?
Last edited by lilsirecho (2009-08-21 16:23:36)

You're getting the avidemux message because you are now using a mirror that is not as up-to-date as the one you used to install avidemux-2.5.1-1.
The sync problem can affect all packages. If all the bandwith is used to sync the lost packages then there is none left to sync the newer packages.

[solved] virtualbox-ose-additions-modules and pacman -Syu

I get the following error from my VM (Oracle VM VirtualBox) under Windows when doing a pacman -Syu:
:: Starting full system upgrade...
:: Replace kernel26-firmware with core/linux-firmware? [Y/n]
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: virtualbox-ose-additions-modules: requires kernel26<2.6.34
pacman -Qs kernel26 =
local/kernel26 2.6.33.4-1 (base)
The Linux Kernel and modules
local/kernel26-firmware 2.6.33.4-1 (base)
The included firmware files of the Linux Kernel
local/kernel26-headers 2.6.33.4-1
Header files and scripts for building modules for kernel26
Please help.d
Last edited by tpfkanep (2010-06-22 09:00:51)

find a more up to date mirror. virtualbox-ose-additions-modules 3.2.4-3 has the proper dependencies

Pacman -Syu and now keyboard only works as root kde

I did a pacman -Syu and now keyboard only works as root kde
Users can use keyboard in the basic console and this is a failure within KDE or the X-server.
On this upgrade I needed to add the portmap daemon to rc.conf.
I am running kerrnel 2.6.5-2. The upgrade lifted KDE to KDE 3.2.2. Xfree86 was upgraded previously and did not present this problem so the KDE upgrade is under suspicion.
My rc.conf daemons list is DAEMONS=(portmap syslogd klogd !pcmcia network netfs crond fam cups kdm)
Is there something extra I need to add?

Hi colnago,
I tidied up my daemons, after considering how you've set yours. I agree portmap and fam are not useful. I now understand that the upgrade was leaning on fam so that it noticed portmap was missing... a red herring issue, perhaps?
I had no means of getting a dmesg log readout, because of the keyboard crashing. So I have patiently reinstalled kde 3.2.1, by way of adding the components one by one from /var/cache/pacman/pkg/. That works, so I can now pause and investigate if there are any any known issues with the 3.2.2 upgrade that shed light.
I did get an indicator that the DCOP server did not function properly. This happened as warnings and errors, when I installed an additional user.
Thanks
gs

Pacman and pacman -Syu

I was 100% sure I already posted this message but it is not here, I think I have done something terribly wrong with the submit button. :oops:
As everybody (should) know in case you do a pacman -Syu and a newer version of pacman is out, you should stop it, then upgrade only pacman and after do again pacman -Syu.
Could it be possible to have pacman that checks if there is a newer version available and in that case do only pacman upgrade?
This should save (especially newcomers) many problem.
I know that newcomers start to take advantage from a such feature only from 0.6 but somewere we have to start.
I think pacman is this case can have two operating mode:
1) pacman -Syu
2) pacman see a newer pacman version
3) pacman warn the user to do a pacman -S pacman before the pacman -Syu and stop. Eventually with the option to force the -Syu anyway. If somebody wants to mess up his/her system they should be free to do it
Another way can be
1) pacman -Syu
2) pacman see a newer pacman version
3) pacman automatically update itself and after stop warning the user that pacman has been update and now he/she need to start pacman -Syu again

I think this is a good idea. You should submit a feature request to the bugtracker.
Bobonov wrote:
I think pacman is this case can have two operating mode:
1) pacman -Syu
2) pacman see a newer pacman version
3) pacman warn the user to do a pacman -S pacman before the pacman -Syu and stop. Eventually with the option to force the -Syu anyway. If somebody wants to mess up his/her system they should be free to do it
Another way can be
1) pacman -Syu
2) pacman see a newer pacman version
3) pacman automatically update itself and after stop warning the user that pacman has been update and now he/she need to start pacman -Syu again
A third way would be:
1) pacman -Syu
2) See never pacman version
3) "Do you want to update pacman y/n"
4) If yes upgrade pacman
5) Continue with normal update.

Pacman -Syu includes pkgs kdelibs and kdemultimedia

Please advise regarding the subject pkgs which recently caused loss of functions in Kde.
Are these pkgs still capable of causing disruption?
Can the -Syu system be corrected to eliminate defective pkgs?

lilsirecho wrote:
I reiterate...those not in the know will have to backtrack when they do the usual ...pacman -Syu... even though the system maintainers leave the defects in the download with no warning...
End of comments...
yes unfortunately this is one of the drawbacks of rolling release systems. that is why i have been so vocal about filing bugs. that way IF broken packages are in the repos it will not be for long. I don't know if the maintainer of kde had those two packages in the testing repo first or not but there are a base core of kde apps that maintainers should ALWAYS put into the testing repo befiore releasing on the unsuspecting public. KDE is too big and important for its users to have to fiddle around with to try and fix bugs.

[SOLVED] Pacman -Syu Warning and Error

I want to update my system, but the first weird thing I notice after pacman -Syu is this warning message:
warning: dependency cycle detected:
warning: util-linux will be installed before its udev dependency
And then, when checking for conflicts, pacman throws this about some existing Xorg files:
(100/100) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
xorg-xmessage: /usr/bin/xmessage exists in filesystem
xorg-xmessage: /usr/share/X11/app-defaults/Xmessage exists in filesystem
xorg-xmessage: /usr/share/X11/app-defaults/Xmessage-color exists in filesystem
xorg-xmessage: /usr/share/man/man1/xmessage.1.gz exists in filesystem
Errors occurred, no packages were upgraded.
Is it safe to force the install with a pacman -Syuf? I prefer to ask for your advice before I end breaking something...
Last edited by isacdaavid (2012-03-25 17:49:24)

Thanks! All those files belonged to an orphan and now extinct package called xorg-apps.
pacman -Runs xorg-apps fixed the problem.

Makepkg and then pacman -Syu

so here it goes i did the modutils pkg using makepkg
then later on e did a pacman -Syu and got this result
pacman -Syu
:: Synchronizing package databases...
current.db.tar.gz [#################################] 100% | 31K
unofficial.db.tar.gz [#################################] 100% | 47K
unstable.db.tar.gz [#################################] 100% | 0K
:: modutils-2.4.24-1: local version is newer
:: Above packages will be skipped. To manually upgrade use 'pacman -S <pkg>'
so im not permited 2 install it using pacman my questions is this
1º will i bea able to upgrade to modutils-2.4.2X later on
2º is this a feature
3º is this a bug
4º im i plane dhumb
thank you
hum ....... as i posted this i did a pacman -Sw modutils just 2 see the version and its not in sync with the abs tree sorry i did not realiseed that things take some time 2 build

exactly good memory i did the same now look at this
brupt brupt werd do you guys need help ? i offer my destop to build pkgs using thishttp://distcc.samba.org/ or something you need
pacman -Syu
:: Synchronizing package databases...
current.db.tar.gz [#################################] 100% | 30K
unofficial.db.tar.gz [#################################] 100% | 47K
nstable.db.tar.gz [#################################] 100% | 0K
error: unresolvable conflicts/dependencies:
kdevelop: requires kdebase=3.1
Targets:
[root@routty abs]# pacman -Q kdebase=3.1
Package "kdebase=3.1" was not found.
[root@routty abs]# pacman -Q kdebase
kdebase 3.1-2
[root@routty abs]# pacman -S kdevelop
:: kdevelop-2.1.5-1: is up to date. Upgrade anyway? [Y/n] y
Targets: kdevelop-2.1.5-1
Do you want to install/upgrade these packages? [Y/n] n

Pacman -Syu - errors occurred, no packages were upgraded

Today I wanted to update my system so a ran pacman -Syu command, download worked perfect
as usual but when it got to installation I've seen this:
checking package integrity... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libcrux-engine.la: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libcrux-engine.so: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libhcengine.la: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libhcengine.so: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/liblighthouseblue.la: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/liblighthouseblue.so: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libmist.la: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libmist.so: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libsmooth.la: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libsmooth.so: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libthinice.la: exists in filesystem
gtk-engines: /usr/lib/gtk-2.0/2.4.0/engines/libthinice.so: exists in filesystem
gtk-engines: /usr/share/eazel-engine/arrow_down-spinner.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/arrow_down.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/arrow_left.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/arrow_right.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/arrow_up-spinner.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/arrow_up.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-active-default-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-active-default.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-active-hilight-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-active-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-active-insensitive.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-active-pressed-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-active-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-default-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-default.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-hilight-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-insensitive.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-pressed-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/check-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/progressbar-left.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/progressbar-right.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/progressbar.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/progressbar_trough.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-active-default-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-active-default.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-active-hilight-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-active-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-active-insensitive.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-active-pressed-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-active-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-default-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-default.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-hilight-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-insensitive.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-pressed-focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/radio-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-down-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-down-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-down.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-left-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-left-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-left.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-right-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-right-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-right.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-up-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-up-pressed.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-arrow-up.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-h-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-h-thumb-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-h-thumb.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-h-trough.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-h.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-v-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-v-thumb-hilight.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-v-thumb.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-v-trough.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/scroller-v.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/slider_h_thumb.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/slider_h_trough.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/slider_h_trough_focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/slider_v_thumb.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/slider_v_trough.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/slider_v_trough_focus.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_left-unsel.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_left.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_right.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_sel-bottom.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_sel.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_usel-bottom-left.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_usel-bottom.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_usel-left.png: exists in filesystem
gtk-engines: /usr/share/eazel-engine/tab_usel.png: exists in filesystem
gtk-engines: /usr/share/themes/Crux/gtk-2.0/gtkrc: exists in filesystem
gtk-engines: /usr/share/themes/LighthouseBlue/gtk-2.0/gtkrc: exists in filesystem
gtk-engines: /usr/share/themes/Mist/gtk-2.0/gtkrc: exists in filesystem
gtk-engines: /usr/share/themes/ThinIce/gtk-2.0/gtkrc: exists in filesystem
errors occurred, no packages were upgraded.
Can someone tell me what's wrong and how to fix this?Thnx.

It works again
Thank you Happy New Year to all of you

Rc.sysinit screwed after pacman -Syu

Early today I made a pacman -Syu. There where only 2 packages to upgrade, and I went go on (I couldnt find those packages specified in pacman.log. It only says "Full system upgrade". How can a know those?) Couldnt find anything in the forums regarding this as well.
I do remember too, that one of those give and output after upgrading saying that inittab (I think) and rc.conf were installed as inittab.pacnew and rc.conf.pacnew
The thing is that when I booted again this afternoon, the booting process launched handful of errors on different lines of /etc/rc.sysinit, all of them of "command not found". Now the login prompt says "(none) login:", my keyboard layout changed to default, home is not mounted, etc...
How can I debug this?
Thanks in advance!

^ the same situation as above, and like you figured it to be Bash. (The segmentation fault errors don't show up when "quiet" is in the kernel boot line.) But with the hostname as "none" the filesystem is read-only; how did you downgrade it? Or rather, how does one downgrade a package on a mounted filesystem via the Arch Live CD such as /mnt/root? ... I guess a dirty use of "cp" would be required if not possible with pacman...
Last edited by Skyalmian (2011-03-01 07:23:31)

[SOLVED] gnome-settings-daemon problem after pacman -Syu

Today after updating my hp laptop with pacman -Syu, I noticed that I lost a few of my multimedia key shortcuts. When I tried to fix this with System->Preferences->Keyboard Shortcuts, I get this error:
Unable to start the settings manager 'gnome-settings-daemon'.
Without the GNOME settings manager running, some preferences may not take effect. This could indicate a problem with Bonobo, or a non-GNOME (e.g. KDE) settings manager may already be active and conflicting with the GNOME settings manager.
The keyboard shortcut menu comes up as normal, and seems to work like it should for everything but the multimedia keys. I get the same error when clicking on the Appearance & Keyboard menus.
I remember pacman asking me if I wanted to replace gail with gtk2. Could that have anything to do with it?
Any ideas?
Thanks!!!!
Last edited by bebeababa (2008-10-23 17:08:13)

JGC wrote:Log out from gnome and login again, this should fix your issues.
Tried it, no change.
I forgot to mention that running "gnome-settings-daemon" in a termal produces:
** ERROR **: You can only run one xsettings manager at a time; exiting
aborting...
Aborted
... and that the pstree shows a "gnome-settings-" entry.
Any other ideas?

Pacman -Syu today...Kernel2.6.5-2 and XFree86-4.4.0-1

Similar Messages

Maybe you are looking for