Showing posts with label Tips. Show all posts
Showing posts with label Tips. Show all posts

July 02, 2012

Chrome Popup: Your Profile Could Not Be Opened Correctly

I started experiencing this "Your Profile Could not be opened Correctly" message after the last Chrome update to version 20.0.1132.47

The only solution that worked for my particular setup was to delete the following two files (After making sure all Chrome Windows/tabs & processes are closed)

 “Web Data” and “Web Data-journal” files from the following location on my Windows7 machine:

 C:\Users\[Enter your username here]\AppData\Local\Google\Chrome\User Data\Default  

Although this solution was posted back in 2011, it still worked for my problem and resolved it without further tinkering.

Solution Source: http://akdora.wordpress.com/2011/11/03/solution-your-profile-could-not-be-opened-correctly-in-chrome/

P.S. I saw other solutions that suggested deleting your whole Chrome data folders & their contents. Make sure you backup your Chrome bookmarks and a list of your current extensions if you decide to go that route so you won't have to lose any of your stuff.
Share:

June 27, 2012

Yum update from specific repository

To run your yum packages updates from a specific yum repo you need to list your installed repo IDs by issuing this command:

# yum repolist
Which generates the example output below (obviously depends on what repos you have installed):

repo id                        repo name  
base                           CentOS-5 - Base
epel                           Extra Packages for Enterprise Linux 5 - x86_64  
extras                         CentOS-5 - Extras  
ius                            IUS Community Packages for Enterprise Linux 5 - x86_64  
rpmforge                       RHEL 5 - RPMforge.net - dag  
updates                        CentOS-5 - Updates      

Then you can force yum to ignore all repos except the one you need (the IUS repo in this example) to list its available packages by issuing the following:

yum --disablerepo="*" --enablerepo="ius" list available


Which returns available packages that are only in that particular repo



 Loaded plugins: fastestmirror, replace, security  
 Loading mirror speeds from cached hostfile  
  * ius: archive.linux.duke.edu  
 Excluding Packages in global exclude list  
 Finished  
 Available Packages  
 autoconf26x.noarch                                      2.63-4.ius.el5                               ius  
 mysql50.x86_64                                        5.0.96-2.ius.el5                              ius  
 mysql50-bench.x86_64                                     5.0.96-2.ius.el5                              ius  
 mysql50-debuginfo.x86_64                                   5.0.96-2.ius.el5                              ius  
 mysql50-devel.x86_64                                     5.0.96-2.ius.el5                              ius  
 mysql50-server.x86_64                                     5.0.96-2.ius.el5                              ius  
 mysql51.x86_64                                        5.1.63-1.ius.el5                              ius  
 mysql51-bench.x86_64                                     5.1.63-1.ius.el5                              ius  
 mysql51-debuginfo.x86_64                                   5.1.63-1.ius.el5                              ius  
 mysql51-devel.x86_64                                     5.1.63-1.ius.el5                              ius  
 mysql51-embedded.x86_64                                    5.1.63-1.ius.el5                              ius  

You can replace the yum option "list available" used above by any of yum's command options like  update, install etc..

For example, installing the rsyslog package from the IUS repo:


 yum --disablerepo="*" --enablerepo="ius" install rsyslog4  
 Loaded plugins: fastestmirror, replace, security  
 Loading mirror speeds from cached hostfile  
  * ius: archive.linux.duke.edu  
 Excluding Packages in global exclude list  
 Finished  
 Setting up Install Process  
 Resolving Dependencies  
 --> Running transaction check  
 ---> Package rsyslog4.x86_64 0:4.8.0-1.ius.el5 set to be updated  
 --> Finished Dependency Resolution  
 Dependencies Resolved  
 ============================================================================================================================================================================  
  Package                 Arch                  Version                     Repository              Size  
 ============================================================================================================================================================================  
 Installing:  
  rsyslog4                 x86_64                 4.8.0-1.ius.el5                 ius                 446 k  
 Transaction Summary  
 ============================================================================================================================================================================  
 Install    1 Package(s)  
 Upgrade    0 Package(s)  
 Total download size: 446 k  


Share:

May 30, 2012

March 06, 2012

Fix Live Update Backupexec 2010

This fixes the issue of Symantec's Live update not recognizing that there are any products to be updated and throwing the following error message:

LU1805: LiveUpdate was unable to find any products to Update


Fix: Go to your Symantec's Backup Exec Program folder location and run the following executable:



BEUpdateOps.exe

You now should get a notification saying that Backup Exec was successfully registered with Live update and be able to run it to get any available updates.


Many thanks to the solution poster found here:
http://www.sudonym.com/233/unable-to-run-live-update-in-backup-exec-2010

Share:

October 17, 2011

October 05, 2011

Logout without killing running Linux jobs

To logout of your *nix bash session without killing your active jobs is simply done by using either the nohup or disown commands which allow you to leave a job or script running even after you logout.

The syntax is simple:

nohup command-name &

Then type exit or CTRL-D to logout as usual

disown [-ar] [-h] [jobspec ...]
Without options, each jobspec is removed from the table of active jobs. If the -h option is given, each jobspec is not removed from the table, but is marked so that SIGHUP is not sent to the job if the shell receives a SIGHUP. If no jobspec is present, and neither the -a nor the -r option is supplied, the current job is used.

If no jobspec is supplied, the -a option means to remove or mark all jobs; the -r option without a jobspec argument restricts operation to running jobs. The return value is 0 unless a jobspec does not specify a valid job.

Share: