Recompling sudo & zlib brakes the system

x86_64
CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"
#-- Compiler and Linker Flags
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=native -O2 -pipe -fomit-frame-pointer"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j5"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"
$ sudo pacman -Syu
sudo: error in /etc/sudo.conf, line 0 while loading plugin `sudoers_policy'
sudo: unable to dlopen /usr/lib/sudo/sudoers.so: (null)
sudo: fatal error, unable to load plugins
# pacman -S sudo
pacman: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
# pacman -S zlib
pacman: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
in live-cd
# pacman -r /mnt -S sudo
# arch-chroot /mnt
# pacman -S zlib
pacman: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory
only booting in live-cd and 'pacman -r /mnt -S sudo zlib' solves it
Last edited by Perfect Gentleman (2013-10-01 15:24:19)

Similar Messages

How do I find the number of file descriptors in use by the system?

Hey folks,
I am trying to figure out how many file descriptors my Leopard system has in use. On FreeBSD, this is exposed via sysctl at the OID kern.open_files (or something close to that, can't recall exactly what the name is). I do see that OS X has kern.maxfiles, which gives the maximum number of file descriptors the system can have open, but I don't see a sysctl that tells me how many of the 12288 descriptors the kernel thinks are in use.
There's lsof, but is that really the only way? And, I'm not even sure if I can just equate the number of lines from lsof to the number of in use descriptors. I don't think it's that easy (perhaps it is and I'm just over complicating things).
So, anyone know where this information is?
Thanks for your time.

glsmith wrote:
There's lsof, but is that really the only way? And, I'm not even sure if I can just equate the number of lines from lsof to the number of in use descriptors.
Can't think of anything other than lsof right now. However:
Only root can list all open files, all other users see only their own
There is significant duplication, and
All types of file descriptor are listed, which you may not want, so you need to consider filtering.
As an example, the following will count all regular files opened by all users:
sudo lsof | awk '/REG/ { print $NF }' | sort -u | wc -lIf you run it without the sudo, you get just your own open files.

The system doesn´t let me change the dock and .jar files

Dear professionals,
since a couple of days I come across with a weird problem:
I am logged in as admin but the system doesn`t perform several modifications:
such as:
if I remove a broken link from the dock (grey questionmark) and replace it with a new link to the new app the next session everything is unchanged and the questionmark is back.
if I want firefox not to play quicktime and try to change the preferences it flips back immediately
if I want to open Cocktail to schek something it does not accept me as admin - whereas the systems calls me admin.
maybe the futile attempt to alter the minecraft.jar has the same reason.
At many files the file info shows a strange entry at the botten where the sharing/permission are listed: Name is "Laden..." meanig "Loading..." with the dots and as symbol a grey person with tiny questionmark; permission is "read only"
History:
Till now I never used a password and logged in automatical as admin
I upgraded to Lion
I installed a second account to have a workspace not as admin
I gave a password to the admin account
I got nuts with the second account as I couldn´t change the preferences of firefox and delete files and so on
I gave administration rights to the second account to customize the workspace
I realized the problems with the admin account - changes where ignored/forgotten by the system w/o warnings
I deleted the second account as it seemed to cause the trouble
I repaired the rights in the admin account
I repaired the HD with HD recovery
I try to check the system with cocktail but cocktail tells me the password is not sufficient - it opens the app but it refuses any modifications
I switched to manual login
System tells me that the keychain.login does not accept the password
I set the password for keychain also
keychain first aid tells me the password does not work ?
I removed the password from admin account
I removed the password from keychain first aid is happy
Repair rights does not find any trouble
Cocktail does not accept me anyway anymore, without password (as i logged in) or the former passwords- it blocks at all.
And all the other stuff listed at the beginning drives me crazy
File Info window tells me i have adapted rights- whatever it means, as i am listed with full read/write rights
now I am stunned.
I would like to use my Installation disk to repair anything - but as it is not the lion system I am afraid to cause more trouble.
Does anyone have a clue?
And sorry for the strange text- english is not my native language
And, btw, is netinfo manager removed by lion? it does not appear on my volume.
Thanks for Your help
Bernhard

Repairing the permissions of a home folder in Lion is a complicated procedure. I don’t know of a simpler one that always works.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the page that opens.
Drag or copy – do not type – the following line into the Terminal window, then press return:
chmod -R -N ~
The command will take a noticeable amount of time to run. When a new line ending in a dollar sign ($) appears below what you entered, it’s done. You may see a few error messages about an “invalid argument” while the command is running. You can ignore those. If you get an error message with the words “Permission denied,” enter this:
sudo !!
You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
Next, boot from your recovery partition by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the recovery desktop appears, select Utilities ▹ Terminal from the menu bar.
In the Terminal window, enter “resetpassword” (without the quotes) and press return. A Reset Password window opens.
Select your boot volume if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select  ▹ Restart from the menu bar.

[SOLVED] vi (vim) no longer works properly after updating the system

After updating the system with pacman -Syu vi stopped working. All syntax colors are gone, and everything is grey. When I press i to enter "insert" mode, editing is not visible. Changes are obscure and you can't tell what you are modifying. Quitting with :q will still prompt you to use :q! to abort changes, even if no changes were visibly made.
When scrolling to the beginning or end of a file, the screen flashes with grey glitch like areas. What happened to my vi!?!?!?!?!?
This all happened while following the beginner's guide to install arch linux. I realized this when trying to arbitrarily read a test file I made directly after updating.
The problems continued to be visible when installing and setting up sudo (those steps are the next steps that require vi)... I think the sudo installation worked... but my vi is horribly glitchy
Any ideas?
Last edited by trusktr (2010-02-19 07:19:55)

Setting EDITOR does not help in every case. For instance, visudo is by default hard linked to vi. (You can change this, I know. )
But in fact, vi is only a symlink to ex. So I simply renamed this link and put another symlink to vim (vim-big in my case since I in fact do use the gvim package).
/usr/bin/vi -> vim-big
/usr/bin/vi-simple -> ex
The drawback is that I have to set those links on every vi-update. (But I sure will remember...)
Last edited by bernarcher (2010-02-19 00:58:57)

Is it possible to reinstall Symbol dfont into the system folder?

Since updating to Snow Leopard, there is no Symbol dfont in the system folder. I have been relying on this font for sometime now to avoid special character issues.
I use InDesign and this font has become essential for my work. The Symbol font now supplied with the OSX ver.6 (Symbol.ttf) is noticeably different.
Is there a way of reloading Symbol dfont into the system folder without it becoming a nightmare? Or, can I replace the current Symbol font?

This is one of those infamous Apple "invisible" fonts that are not removable.
Other than those in the ProtectedFonts folder (not invisible, just difficult to find), their are no "invisible" fonts on the hard drive.
The only Symbol font installed by Snow Leopard is the Symbol.ttf font in the /System/Library/Fonts/ folder.
You can try removing it, and it will seem to go away, but somehow it keeps showing up.
What did you do after removing it? How did you remove it?
If you simply dragged it to the trash, that won't work. Only a copy of the font will go in the trash, or desktop, or wherever you drag it. To delete any font from the System folder, you must choose Delete and enter your admin password.
After that, it's still not gone. Even in the trash, any font from the System folder remains active (you can't even empty the trash) until you at least restart the Mac.
You may still have issues after installing Symbol.dfont from Leopard if the OS, or applications use the cached data for the .ttf version instead of creating fresh data for the replacement font.
Close all running applications. From an administrator account, open the Terminal app and enter the following command. You can also copy/paste it from here into the Terminal window:
sudo atsutil databases -remove
This removes all font cache files. Both for the system and all user font cache files. After running the command, close Terminal and immediately restart your Mac.
Once the Snow Leopard version of Symbol is truly off the drive, you should have no trouble using the .dfont version from Leopard.

Sudo chown + chmod on system drive?

Hello,
Before I mess my system drive up I wanted to check if this is ok.
For various reasons I have created a new Account that I wish to migrate to. I log in ok and can change permissions but there seem to be files on various places that I keep having to set permissions for and wish to resolve this for the whole drive.
What I want is a way to set permissions on all non system files to add admin access as it appears it is not there for certain files
I found the below commands which worked on my media drive but am reluctant to run it on the system drive:
sudo chflags 0 /Volumes/System
sudo chown 0:80 /Volumes/System
sudo chmod 775 /Volumes/System
sudo chmod -N /Volumes/System
I think the one above should have the "R" in as below to do this recursivly ?
sudo chmod -RN /Volumes/System
I don't want to mess up the system drive so I thought I should check if this is ok or not. I think some system files need to be read only so I need to know if this will render the drive useless(I do have a full backup).
I also see people recomend Batchmod but am again unsure if this will work or what settings to use?

Thanks Niel,
I have read numorous posts from yourself and V.K. relating to locked secondary drives but nothing relating to system drives and fully expected that answer. can I bother you a bit more please?
Can I safly run those commands on some of these folders?
system\users\olduseraccount
System\library\application support
System\library\audio
I think that would solve most issues there are hundreds of folders with presets from plugins that have installed with only my old account as read write not admins?
Thanks again Niel
Ross

I have purchased a macbook air with 64 gb hard disk. the available space is only 10gb. With this available space, i can't use the system effectively. kindly advise.

I have purchased a macbook air with 64 gb hard disk. the available space is only 10gb. With this available space, i can't use the system effectively. kindly advise.

You should have bought one with a larger SSD. You can regain some space by disabling the sleepimage file:
To disable safe sleep, run the two following commands in Terminal:
$ sudo pmset -a hibernatemode 0
$ sudo nvram "use-nvramrc?"=false
When done, restart your computer. Now go delete the file "/private/var/vm/sleepimage" to free up some hard drive space. When you put your computer to sleep it, should happen in under five seconds; my MacBook now goes to sleep in two seconds.
[robg adds: To state the obvious, with safe sleep disabled, a total power loss will wipe out whatever was open on your machine. To enable safe sleep mode again, repeat the above commands, but change hibernatemode 0 on the first line to hibernatemode 3, and =false to =true on the second line. You'll then need to reboot again. Personally, I prefer the safe sleep mode, even with the slower sleep time and hard drive consumption -- even if for no other reason than it's great when changing batteries on a flight.]
You can also delete unneeded files:
Freeing Up Space on The Hard Drive
1. See Lion/Mountain Lion's Storage Display.
2. You can remove data from your Home folder except for the /Home/Library/ folder.
3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
4. Also see Freeing space on your Mac OS X startup disk.
5. See Where did my Disk Space go?.
6. See The Storage Display.
You must Empty the Trash in order to recover the space they occupied on the hard drive.
You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.

Mkfs.ntfs crashes the system

Hi all,
Here I am again with a weird kernel & swap bugs! But I'm pretty sure the kernel itself is okay, so newbie corner it is.
Here the problem: Doing this (/dev/sdb is a 16 GB USB key I want to format)
% sudo mkfs.ntfs /dev/sdb1
Cluster size has been automatically set to 4096 bytes.
Initializing device with zeroes: 2%^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C
Crashes my system in 30 seconds. As soon as I type the command, the computer gets extremely laggy, cursor barely reacts to mouse movement, can't ^C the command, few seconds later X is completely locked up and I switch to another terminal. Shortly after logging in, I lost acces to the terminal as well (too laggy), so I just unplugged the USB key, very bad idea from me:
[142571.154220] quiet_error: 29182 callbacks suppressed
[142571.154225] Buffer I/O error on device sdb1, logical block 2908602
[142571.154290] lost page write due to I/O error on sdb1
[142571.154297] Buffer I/O error on device sdb1, logical block 2908603
[142571.154358] lost page write due to I/O error on sdb1
[142571.154369] Buffer I/O error on device sdb1, logical block 2908604
[142571.154431] lost page write due to I/O error on sdb1
[142571.154435] Buffer I/O error on device sdb1, logical block 2908479
[142571.154497] lost page write due to I/O error on sdb1
[142571.154501] Buffer I/O error on device sdb1, logical block 2908753
[142571.154562] lost page write due to I/O error on sdb1
[142571.154567] Buffer I/O error on device sdb1, logical block 2801907
[142571.154629] lost page write due to I/O error on sdb1
[142571.154633] Buffer I/O error on device sdb1, logical block 2908635
[142571.154695] lost page write due to I/O error on sdb1
[142571.154700] Buffer I/O error on device sdb1, logical block 2908198
[142571.154761] lost page write due to I/O error on sdb1
[142571.154766] Buffer I/O error on device sdb1, logical block 2908199
[142571.154827] lost page write due to I/O error on sdb1
[142571.154831] Buffer I/O error on device sdb1, logical block 3199990
[142571.154893] lost page write due to I/O error on sdb1
[142576.287833] quiet_error: 47191 callbacks suppressed
I had to SysRq+RE to recover from this one. Then I tried it again, but I was able to recover the system this time, and I got this:
[145804.543734] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[146114.823092] INFO: task kswapd0:58 blocked for more than 120 seconds.
[146114.823169] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[146114.823246] kswapd0 D 0000000000000022 0 58 2 0x00000008
[146114.823395] ffff8801192ef838 0000000000000046 ffffffffa0148039 ffff8801192effd8
[146114.823637] ffff8801192effd8 ffff8801192effd8 ffff8801192effd8 ffff880119495040
[146114.823878] ffff880119063580 ffff88011763f710 ffff88011763f710 0000000000000004
[146114.824198] Call Trace:
[146114.824277] [<ffffffffa0148039>] ? scsi_request_fn+0xa9/0x4a0 [scsi_mod]
[146114.824343] [<ffffffff812285a3>] ? __blk_run_queue+0x33/0x40
[146114.824406] [<ffffffff8122c47b>] ? queue_unplugged+0x3b/0xe0
[146114.824473] [<ffffffff814b16af>] io_schedule+0x8f/0xe0
[146114.824535] [<ffffffff8122d96a>] get_request+0x1aa/0x770
[146114.824598] [<ffffffff81232b1e>] ? ioc_lookup_icq+0x4e/0x80
[146114.824663] [<ffffffff8107ab80>] ? wake_up_bit+0x30/0x30
[146114.824726] [<ffffffff8122fcc9>] blk_queue_bio+0x79/0x3e0
[146114.824788] [<ffffffff8122ebf2>] generic_make_request+0xc2/0x110
[146114.824851] [<ffffffff8122ecb3>] submit_bio+0x73/0x160
[146114.824916] [<ffffffff811a346c>] ? bio_alloc_bioset+0x3c/0x130
[146114.824979] [<ffffffff8119fea4>] submit_bh+0x114/0x200
[146114.825041] [<ffffffff811a19d0>] __block_write_full_page+0x160/0x380
[146114.825108] [<ffffffff811a45d0>] ? I_BDEV+0x10/0x10
[146114.825172] [<ffffffff8119e6d0>] ? end_buffer_write_sync+0xb0/0xb0
[146114.825235] [<ffffffff811a45d0>] ? I_BDEV+0x10/0x10
[146114.825297] [<ffffffff8119e6d0>] ? end_buffer_write_sync+0xb0/0xb0
[146114.825360] [<ffffffff811a1de8>] block_write_full_page_endio+0xd8/0x110
[146114.825424] [<ffffffff811a1e35>] block_write_full_page+0x15/0x20
[146114.825487] [<ffffffff811a4de8>] blkdev_writepage+0x18/0x20
[146114.825550] [<ffffffff8111f1d0>] shrink_page_list+0x710/0x930
[146114.825614] [<ffffffff8111f950>] shrink_inactive_list+0x150/0x450
[146114.825677] [<ffffffff811201f1>] shrink_lruvec+0x201/0x4b0
[146114.825743] [<ffffffff8116f586>] ? put_super+0x36/0x40
[146114.825806] [<ffffffff8112050e>] shrink_zone+0x6e/0x190
[146114.825868] [<ffffffff8112154c>] balance_pgdat+0x43c/0x5a0
[146114.825933] [<ffffffff81121801>] kswapd+0x151/0x460
[146114.825994] [<ffffffff8107ab80>] ? wake_up_bit+0x30/0x30
[146114.826056] [<ffffffff811216b0>] ? balance_pgdat+0x5a0/0x5a0
[146114.826121] [<ffffffff81079db0>] kthread+0xc0/0xd0
[146114.826191] [<ffffffff81305270>] ? tty_ioctl+0x960/0xba0
[146114.826253] [<ffffffff81079cf0>] ? kthread_create_on_node+0x120/0x120
[146114.826317] [<ffffffff814b9fec>] ret_from_fork+0x7c/0xb0
[146114.826378] [<ffffffff81079cf0>] ? kthread_create_on_node+0x120/0x120
I disabled swap and now I'm able to mkfs,ntfs, but it takes the whole available RAM (-/+ buffers is 1963MB). I'm typing this and this is the only tab I can open, if I dare try to open anything else system goes unstable (random app freezes like xfce4-panel, comes back if I close something else).
TL;DR: Question: Why does mkfs.ntfs crashes the system? How can I prevent it from doing that?

I don't know if this helps, here's more dmesg:
[ 1762.195956] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 1762.322495] Initializing USB Mass Storage driver...
[ 1762.322576] scsi8 : usb-storage 2-1:1.0
[ 1762.322639] usbcore: registered new interface driver usb-storage
[ 1762.322641] USB Mass Storage support registered.
[ 1767.706240] scsi 8:0:0:0: Direct-Access Lexar JD FireFly 1100 PQ: 0 ANSI: 0 CCS
[ 1767.707894] sd 8:0:0:0: [sdc] 31326208 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 1767.708770] sd 8:0:0:0: [sdc] Write Protect is off
[ 1767.708774] sd 8:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 1767.709662] sd 8:0:0:0: [sdc] No Caching mode page present
[ 1767.709667] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 1767.713411] sd 8:0:0:0: [sdc] No Caching mode page present
[ 1767.713414] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 1767.714417] sdc: sdc1
[ 1767.718813] sd 8:0:0:0: [sdc] No Caching mode page present
[ 1767.718817] sd 8:0:0:0: [sdc] Assuming drive cache: write through
[ 1767.718819] sd 8:0:0:0: [sdc] Attached SCSI removable disk
It does seem to use usb-storage as expected. I will try to find my other drive I lost somewhere on my desk and see if it does the same, I don't remember having my other drive going crazy like that.
It also seems like dd works fine on it (probably flushes the buffer on every write), I'll keep testing on my side...

[kinda solved] All the system is down and I need my files badly!

I'm using gnome and sometimes when the screen goes blank and you need to retype your password to restore it... well, sometimes it was blank for a while (about 5 seconds) so I was just wandering with my cursor for a while as it was like 30 seconds now... my cursor changed into this "you can type here" mode so I just typed my login, clicked enter and then the password and enter again... then it all went into "no move" state so I changed my display with ctrl+alt+F2 and rebooted the system. It didn't open gdm at all, I had just a terminal (now typing from my laptop). So I typed "gdm" but it went like this:
** (gdm-binary:1242: WARNING **: Failed to aquire org.gnome.DisplayManager: Connection ":1.13" is not allowed to own the service "org.gnome.DisplayManager" due to security policies in the configuration file
** (gdm-binary:1242: WARNING **: could not acquire name; bailing out
With sudo it was almost the same but shorter:
** (gdm-binary:1242: WARNING **: Failed to aquire org.gnome.DisplayManager
** (gdm-binary:1242: WARNING **: could not acquire name; bailing out
With "gnome-session" even shorter:
** (gnome-session:1256): WARNING **": Cannot open display:
So I thought I sould just reinstall all the gnome but I used -Syyu before that. Effect:
error: failed retrieving file core.db from mirrors.kernel.org : No address record
It failed to synchronize any database!
So if pacman and gnome are down in the same time... what could happen? All the configuration and home files are present on the disk (I guess).
At boot, it goes:
FATAL: Could not load /lib/modules/2.6.38-ARCH/modules.dep: No such file or directory
And I guess the important part of the story is that I'm ussing barriers=0 with ext4...
Last edited by Włóczymyśl (2011-06-16 11:28:26)

litemotiv wrote:It sounds like it's time to chroot and perform a full pacman update from there. If the problem persists, reinstall the kernel. If the problem still persists, reinstall grub.
Well, I did the 1st and it was impossible to do so I did the 2nd and it was still bad (other errors thought) so I did the 1st again and it worked but the system was still not booting (yet other errors thought) so I did the 3rd and it still was bad... so I turned to this proposal:
ewaller wrote:You could also try booting the system any way you can (livecd, usb), mount your root partition somewhere, mount your boot partition somewhere else (not at /boot on the root partition), and copy the files from your root partition's /boot to the boot partition.
but it didn't worked either... now I'm stuck with:
Root device '/dev/disk/by-uuid/xxxxxxxxxxxxxx' doesn't exist. Attempting to create it.
ERROR: Unable to determinate major/minor number of root device '/dev/disk/by-uuid/xxxxxxxxxxxx'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
while booting. It's too much for me... ^^'
Edit: 'exit' didn't solve the situation of course.
Last edited by Włóczymyśl (2011-06-15 16:03:37)

When installing iPhoto update, I got this pop-up -The system extension "/System/Library/Extensions/IOFireWireWDHID.kext" was installed improperly and cannot be used. Please try reinstalling it, or contact the product's vendor for an update. What does it

When installing iPhoto 9.2.1 software update, I got this pop up.
"The system extension “/System/Library/Extensions/IOFireWireWDHID.kext” was installed improperly and cannot be used. Please try reinstalling it, or contact the product’s vendor for an update."
Is this a minor matter that can be ignored? Any suggestions on what I should do?

The faster (and way more recommended) way to do this is to run a permissions repair from disk utility.
Open Applications -> Utilities -> Disk Utility -> Click on Macintosh HD -> then in the right pane there is a "Repair Disk Permissions" button click on this. It should repair all permissions to their proper settings.
Another option is to manually repair them on this kext only. This involves opening Terminal and running the following commands.
sudo chown -R 0:0 /System/Library/Extensions/IOFireWireWDHID.kext
sudo chmod -R 755 /System/Library/Extensions/IOFireWireWDHID.kext
Otherwise if you don't have any firewire devices it doesn't really matter.

[SOLVED] Remove cairo-dock completely from the system

I would like to know how to remove cairo-dock completely from the system and then re-install it again.
It seems like it is not uninstalled completely. I have removed and then re-installed and when performing pacman -Ss cairo-dock cairo-dock-plugins it figures as it is not installed when in fact is.
Last edited by toni (2013-11-23 12:55:10)

jasonwryan wrote:Please paste the commands you used to remove and reinstall it.
Below the commands:
sudo pacman -Rns cairo-dock cairo-dock-plugins
I get below errors when trying uninstall them:
error: target not found: cairo-dock
error: target not found: cairo-dock-plugins
I use compton composite manager.
After that If I try to install it again:
sudo pacman -S cairo-dock cairo-dock-plugins
below output is shown:
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/dnd2share/upload2free.sh exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/drop-indicator/default-drop-indicator.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/drop-indicator/default-hover-indicator.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/drop-indicator/drop_indicator.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/drop-indicator/icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/drop-indicator/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/dustbin/dustbin.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/dustbin/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/dustbin/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/dustbin/themes/default/preview exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/dustbin/themes/default/trashcan_empty.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/dustbin/themes/default/trashcan_full.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/gnome-integration/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/icon-effect.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/icon-fire.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/icon-firework.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/icon-storm.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/rain.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/snow.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/icon-effect/star.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/icon-black-hole.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/icon-break.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/icon-evaporate.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/icon-explode.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/icon-fade-out.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/illusion.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/illusion/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/kde-integration/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/keyboard-indicator/caps-lock.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/keyboard-indicator/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/keyboard-indicator/keyboard-indicator.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/keyboard-indicator/num-lock.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/keyboard-indicator/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/icon-scheduling.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/locked.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/logout.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/logout.sh exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/system-guest.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/system-hibernate.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/system-log-out.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/system-restart.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/system-shutdown.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/logout/system-suspend.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/cd_mail_icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/cd_mail_newmail.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/cd_mail_nomail.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/mail.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/themes/Default/has_mail.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/themes/Default/new_mail_sound.wav exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/mail/themes/Default/no_mail.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/motion-blur/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/motion-blur/motion_blur.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/0.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/1.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/2.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/3.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/broken.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/broken.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/default.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/default.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/musicPlayer.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/pause.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/pause.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/play.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/play.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/stop.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/stop.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/themes/cd_box_simple/frame.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/themes/cd_box_simple/preview exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/themes/cd_box_simple/readme exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/themes/cd_box_simple/reflect.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/musicPlayer/themes/cd_box_simple/theme.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/bad.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/default.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/netspeed exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/netspeed.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/ok.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/netspeed/unknown.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/powermanager/charge.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/powermanager/default-battery.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/powermanager/default-charge.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/powermanager/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/powermanager/powermanager.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/powermanager/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/powermanager/sector.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/quick_browser/icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/quick_browser/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/quick_browser/quick-browser.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/preview-3D-plane.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/preview-caroussel.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/preview-curve.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/preview-panel.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/preview-parabolic.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/preview-rainbow.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/preview-slide.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/readme-3D-plane-view exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/readme-caroussel-view exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/readme-curve-view exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/readme-panel-view exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/readme-parabolic-view exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/readme-rainbow-view exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/readme-slide-view exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/rendering/rendering.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shared-files/images/expose-desktops.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shared-files/images/expose-windows.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shared-files/images/icon-gauge.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shared-files/images/icon-graph.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shared-files/images/show-desktop.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shared-files/images/widget-layer.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shared-files/scripts/lock-screen.sh exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shortcuts/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shortcuts/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/shortcuts/shortcuts.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/showDesktop/icon-active.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/showDesktop/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/showDesktop/showDesktop.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/show_mouse/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/show_mouse/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/show_mouse/show_mouse.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/slider/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/slider/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/slider/slider.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/stack/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/stack/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/stack/stack.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/stack/text-icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/stack/url-icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/switcher/broken.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/switcher/default.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/switcher/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/switcher/switcher.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/switcher/workspaces.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/systray/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/systray/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/systray/systray.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/terminal/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/terminal/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/terminal/terminal.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/tomboy/close.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/tomboy/icon.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/tomboy/note.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/tomboy/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/tomboy/tomboy.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/broken.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/0.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/1.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/10.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/11.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/12.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/13.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/14.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/15.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/16.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/17.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/18.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/19.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/2.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/20.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/21.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/22.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/23.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/24.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/25.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/26.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/27.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/28.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/29.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/3.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/30.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/31.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/32.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/33.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/34.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/35.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/36.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/37.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/38.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/39.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/4.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/40.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/41.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/42.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/43.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/44.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/45.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/46.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/47.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/5.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/6.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/7.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/8.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/9.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/na.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/preview exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/themes/Classic/readme exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weather/weather.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weblets/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weblets/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/weblets/weblets.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/wifi/default.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/wifi/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/wifi/no-signal.svg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/wifi/preview.jpg exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/wifi/wifi.conf exists in filesystem
cairo-dock-plugins: /usr/share/cairo-dock/plug-ins/xfce-integration/icon.png exists in filesystem
cairo-dock-plugins: /usr/share/locale/ar/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/ca/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/cs/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/de/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/el/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/en/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/es/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/et/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/eu/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/fr/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/he/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/hr/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/hu/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/id/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/it/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/ja/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/lt/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/nl/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/pl/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/pt/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/pt_BR/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/ru/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/sk/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/sr/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/sr@latin/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/sv/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/tr/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/uk/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/zh_CN/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/locale/zh_TW/LC_MESSAGES/cairo-dock-plugins.mo exists in filesystem
cairo-dock-plugins: /usr/share/vala/vapi/CDApplet.deps exists in filesystem
cairo-dock-plugins: /usr/share/vala/vapi/CDApplet.vapi exists in filesystem
Errors occurred, no packages were upgraded.
Last edited by toni (2013-11-22 01:11:51)

How Can One Run Only In The System Administrator ( ie root ) ?

Upon creating a System Administrator ( ie root ) in Command + R , of course after Clean Installing OS X ML with my own specific Apple Verified Account ,
i have the Log In screen from a startup , either Safe Boot or a Boot , and i have my own specifc Apple Verified Account , plus the Other... ,
which the Other... of course is the System Administrator ( ie root ) .
How Can One Run Only In The System Administrator ( ie root ) ?
Is there a way in Terminal with sudo su to make it work ?
Shall i just always log in with Other... System Administrator ( ie root ) , and just forget the my own specific Apple Verified Account ?

As of EHP3, you could still install some EHP components. On an ERP 6.00, you could just push SAP_APP to 6.03 and move on. Now if you want another component in your system with an EHP4 version, you can't have some components at EHP3 and some at EHP4. You would install EHP4 for the new component you desire updated and part of the work will be to also update SAP_APP to 6.04.
EHP4 is an UPGRADE process, with shadow instance & all the joy of an upgrade process. You can either run ressource minimized or downtime minimized. In resource minimized, the shadow instance runs on the same server as the main instance. Downtime minimized allow to run the shadow instance on a separate / new server. Anyway you go, you will always have a "Downtime Phase" when you bring back the updated components from the shadow instance toward the real production one.
As with any UPGRADE project, the benefits of installing EHP4 for your business has to weighted against the downtime cost.
Our tests so far on small systems (few data, few users, 120GB database) show ~3 days process from EHP3 to EHP4 (all components) with a downtime phase of about 22 hours using the "resource minimized" path, i.e. shadow & main instance on the same server (4 CPUs, 16GB RAM). Until you give a try at your Sandbox or DEV systems, you won't have realistic figures for your environment.
Good luck!

[SOLVED] Backing up the system while the system is running?

Is it ok if I backup the system while it's running? Or does it *have* to be done from a LiveCD?
I was thinking of using this:
$ sudo rsync -avx /* /mnt/Backup --exclude={/dev/*,/proc/*,/sys/*,/tmp/*,/run/*,/mnt/*,/media/*,/lost+found}
Rsync will complain at the end that "some files/attrs were not transferred", but the backup works fine (as far as I can tell).
Should I add "[...] > sometextfile.txt" at the end, to see which files weren't transfered right? Has anyone else done something like this before?
Last edited by DSpider (2012-06-14 15:56:03)

DSpider wrote:Rsync is not necessarily better, but it does the job. I'm planning on transferring the system to a loopback device (a raw .img file) which will serve as a container for chrooting, and later converting to .vdi for use in VirtualBox. It's a fun project I'm working on: "Moving an existing Arch install to VirtualBox" (title in progress). Maybe I'll write a wiki article, since I did it three times already... And it works, even if I back them up while the system is running. I was just wondering what those files were.
Oh, alright. Cool. Yeah, I just wanted to check whether there was any important differences between tar and rsync. I think I'll check the wiki and do some reading about the two, but from the sound of it, it sounds more like a matter of preference than anything else, which is groovy.
Last edited by lspci (2012-06-13 15:08:01)

Time Machine couldn't complete this backup .... The system date and time is incorrect

I have tried every possible way but it doesn't work. Anyone know how to fix this issue please help me

First, open the Date & Time preference pane and check that the system clock is accurate, including the year. If it is, continue.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Please triple-click anywhere in the line below on this page to select it:
sudo touch /System/Library/CoreServices/backupd
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window by pressing the key combination command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting. You'll be prompted for your login password. Nothing will be displayed when you type it. Type carefully and then press return. If you don’t have a login password, you’ll need to set one before you can run the command. You may get a one-time warning to be careful. Confirm. You don't need to post the warning.
If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. Log in as one and start over.
Wait for a new line ending in a dollar sign ($) to appear below what you entered. You can then quit Terminal. Test.
Credit for this solution to SuperUser contributor Stuart.

Last software update of OS X Lion: the system freezes before the end.

I was doing the last update of OS X Lion on a MacBook Pro (10.7.3). Before the end of the process, the system freezed. The only solution was the off button of the desktop. But after it was impossible to open it again. I had to restore OS X from the Time Machine backup. Can you help me? What is the problem? What do I have to do?

Just fixed this myself.
SWUPD is expecting a directory within the one you chose, called "html".
Example: /Volumes/XSAN/SWUPD/html
It will not create "html" if the directory doesn't exist.
Create the folder "html" then in terminal do this:
sudo chown -R _softwareupdate:_softwareupdate /path/to/the/folder
Example: sudo chown -R _softwareupdate:_softwareupate /Volumes/XSAN/SWUPD
##do not include/html. the -R means recursive and forces the same ownership on all contained directories.

Recompling sudo & zlib brakes the system

Similar Messages

Maybe you are looking for