mirror of
https://github.com/LCTT/TranslateProject.git
synced 2026-08-23 04:03:29 +08:00
20150713-1 选题
This commit is contained in:
DeadFire
@@ -0,0 +1,82 @@
|
||||
How To Fix System Program Problem Detected In Ubuntu 14.04
|
||||
================================================================================
|
||||
|
||||
|
||||
For the last couple of weeks, (almost) every time I was greeted with **system program problem detected on startup in Ubuntu 15.04**. I ignored it for sometime but it was quite annoying after a certain point. You won’t be too happy as well if you are greeted by a pop-up displaying this every time you boot in to the system:
|
||||
|
||||
> System program problem detected
|
||||
>
|
||||
> Do you want to report the problem now?
|
||||
>
|
||||
> 
|
||||
|
||||
I know if you are an Ubuntu user you might have faced this annoying pop-up sometimes for sure. In this post we are going to see what to do with “system program problem detected” report in Ubuntu 14.04 and 15.04.
|
||||
|
||||
### What to do with “system program problem detected” error in Ubuntu? ###
|
||||
|
||||
#### So what exactly is this notifier all about? ####
|
||||
|
||||
Basically, this notifies you of a crash in your system. Don’t panic by the word ‘crash’. It’s not a major issue and your system is very much usable. It just that some program crashed some time in the past and Ubuntu wants you to decide whether or not you want to report this crash report to developers so that they could fix this issue.
|
||||
|
||||
#### So, we click on Report problem and it will vanish? ####
|
||||
|
||||
No, not really. Even if you click on report problem, you’ll be ultimately greeted with a pop up like this:
|
||||
|
||||
|
||||
|
||||
[Sorry, Ubuntu has experienced an internal error][1] is the apport that will further open a web browser and then you can file a bug report by logging or creating an account with [Launchpad][2]. You see, it is a complicated procedure which will take around four steps to complete.
|
||||
|
||||
#### But, I want to help developers and let them know of the bugs! ####
|
||||
|
||||
That’s very thoughtful of you and the right thing to do. But there are two issues here. First, there are high chances that the bug would have already been reported. Second, even if you take the pain of reporting the crash, it’s not a guarantee that you won’t see it again.
|
||||
|
||||
#### So, you suggesting to not report the crash? ####
|
||||
|
||||
Yes and no. Report the crash when you see it the first time, if you want. You can see the crashing program under “Show Details” in the above picture. But if you see it repetitively or if you do not want to report the bug, I advise you to get rid of the system crash once and for all.
|
||||
|
||||
### Fix “system program problem detected” error in Ubuntu ###
|
||||
|
||||
The crash reports are stored in /var/crash directory in Ubuntu. If you look in to this directory, you should see some files ending with crash.
|
||||
|
||||
|
||||
|
||||
What I suggest is that you delete these crash reports. Open a terminal and use the following command:
|
||||
|
||||
sudo rm /var/crash/*
|
||||
|
||||
This will delete all the content of directory /var/crash. This way you won’t be annoyed by the pop up for the programs crash that happened in the past. But if a programs crashes again, you’ll again see system program problem detected error. You can either remove the crash reports again, like we just did, or you can disable the Apport (debug tool) and permanently get rid of the pop-ups.
|
||||
|
||||
#### Permanently get rid of system error pop up in Ubuntu ####
|
||||
|
||||
If you do this, you’ll never be notified about any program crash that happens in the system. If you ask my view, I would say it’s not that bad a thing unless you are willing to file bug reports. If you have no intention of filing a bug report, the crash notifications and their absence will make no difference.
|
||||
|
||||
To disable the Apport and get rid of system crash report completely, open a terminal and use the following command to edit the Apport settings file:
|
||||
|
||||
gksu gedit /etc/default/apport
|
||||
|
||||
The content of the file is:
|
||||
|
||||
# set this to 0 to disable apport, or to 1 to enable it
|
||||
# you can temporarily override this with
|
||||
# sudo service apport start force_start=1
|
||||
enabled=1
|
||||
|
||||
Change the **enabled=1** to **enabled=0**. Save and close the file. You won’t see any pop up for crash reports after doing this. Obvious to point out that if you want to enable the crash reports again, you just need to change the same file and put enabled as 1 again.
|
||||
|
||||
#### Did it work for you? ####
|
||||
|
||||
I hope this tutorial helped you to fix system program problem detected in Ubuntu 14.04 and Ubuntu 15.04. Let me know if this tip helped you to get rid of this annoyance.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://itsfoss.com/how-to-fix-system-program-problem-detected-ubuntu/
|
||||
|
||||
作者：[Abhishek][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://itsfoss.com/author/abhishek/
|
||||
[1]:http://itsfoss.com/how-to-solve-sorry-ubuntu-12-04-has-experienced-an-internal-error/
|
||||
[2]:https://launchpad.net/
|
||||
139
sources/tech/20150713 How to manage Vim plugins.md
Normal file
139
sources/tech/20150713 How to manage Vim plugins.md
Normal file
@@ -0,0 +1,139 @@
|
||||
How to manage Vim plugins
|
||||
================================================================================
|
||||
Vim is a versatile, lightweight text editor on Linux. While its initial learning curve can be overwhelming for an average Linux user, its benefits are completely worthy. As far as the functionality goes, Vim is fully customizable by means of plugins. Due to its high level of configuration, though, you need to spend some time with its plugin system to be able to personalize Vim in an effective way. Luckily, we have several tools that make our life with Vim plugins easier. The one I use on a daily basis is Vundle.
|
||||
|
||||
### What is Vundle? ###
|
||||
|
||||
[Vundle][1], which stands for Vim Bundle, is a Vim plugin manager. Vundle allows you to install, update, search and clean up Vim plugins very easily. It can also manage your runtime and help with tags. In this tutorial, I am going to show how to install and use Vundle.
|
||||
|
||||
### Installing Vundle ###
|
||||
|
||||
First, [install Git][2] if you don't have it on your Linux system.
|
||||
|
||||
Next, create a directory where Vim plugins will be downloaded and installed. By default, this directory is located at ~/.vim/bundle
|
||||
|
||||
$ mkdir -p ~/.vim/bundle
|
||||
|
||||
Now go ahead and install Vundle as follows. Note that Vundle itself is another Vim plugin. Thus we install Vundle under ~/.vim/bundle we created earlier.
|
||||
|
||||
$ git clone https://github.com/gmarik/Vundle.vim.git ~/.vim/bundle/Vundle.vim
|
||||
|
||||
### Configuring Vundle ###
|
||||
|
||||
Now set up you .vimrc file as follows:
|
||||
|
||||
set nocompatible " This is required
|
||||
filetype off " This is required
|
||||
|
||||
" Here you set up the runtime path
|
||||
set rtp+=~/.vim/bundle/Vundle.vim
|
||||
|
||||
" Initialize vundle
|
||||
call vundle#begin()
|
||||
|
||||
" This should always be the first
|
||||
Plugin 'gmarik/Vundle.vim'
|
||||
|
||||
" This examples are from https://github.com/gmarik/Vundle.vim README
|
||||
Plugin 'tpope/vim-fugitive'
|
||||
|
||||
" Plugin from http://vim-scripts.org/vim/scripts.html
|
||||
Plugin 'L9'
|
||||
|
||||
"Git plugin not hosted on GitHub
|
||||
Plugin 'git://git.wincent.com/command-t.git'
|
||||
|
||||
"git repos on your local machine (i.e. when working on your own plugin)
|
||||
Plugin 'file:///home/gmarik/path/to/plugin'
|
||||
|
||||
" The sparkup vim script is in a subdirectory of this repo called vim.
|
||||
" Pass the path to set the runtimepath properly.
|
||||
Plugin 'rstacruz/sparkup', {'rtp': 'vim/'}
|
||||
|
||||
" Avoid a name conflict with L9
|
||||
Plugin 'user/L9', {'name': 'newL9'}
|
||||
|
||||
"Every Plugin should be before this line
|
||||
|
||||
call vundle#end() " required
|
||||
|
||||
Let me explain the above configuration a bit. By default, Vundle downloads and installs Vim plugins from github.com or vim-scripts.org. You can modify the default behavior.
|
||||
|
||||
To install from Github:
|
||||
|
||||
Plugin 'user/plugin'
|
||||
|
||||
To install from http://vim-scripts.org/vim/scripts.html:
|
||||
|
||||
Plugin 'plugin_name'
|
||||
|
||||
To install from another git repo:
|
||||
|
||||
Plugin 'git://git.another_repo.com/plugin'
|
||||
|
||||
To install from a local file:
|
||||
|
||||
Plugin 'file:///home/user/path/to/plugin'
|
||||
|
||||
Also you can customize others such as the runtime path of you plugins, which is really useful if you are programming a plugin yourself, or just want to load it from another directory that is not ~/.vim.
|
||||
|
||||
Plugin 'rstacruz/sparkup', {'rtp': 'another_vim_path/'}
|
||||
|
||||
If you have plugins with the same names, you can rename you plugin so that it doesn't conflict.
|
||||
|
||||
Plugin 'user/plugin', {'name': 'newPlugin'}
|
||||
|
||||
### Using Vum Commands ###
|
||||
|
||||
Once you have set up you plugins with Vundle, you can use it to to install, update, search and clean unused plugins using several Vundle commands.
|
||||
|
||||
#### Installing a new plugin ####
|
||||
|
||||
The PluginInstall command will install all plugins listed in your .vimrc file. You can also install just one specific plugin by passing its name.
|
||||
|
||||
:PluginInstall
|
||||
:PluginInstall <plugin-name>
|
||||
|
||||
|
||||
|
||||
#### Cleaning up an unused plugin ####
|
||||
|
||||
If you have any unused plugin, you can remove it by using the PluginClean command.
|
||||
|
||||
:PluginClean
|
||||
|
||||
|
||||
|
||||
#### Searching for a plugin ####
|
||||
|
||||
If you want to install a plugin from a plugin list provided, search functionality can be useful.
|
||||
|
||||
:PluginSearch <text-list>
|
||||
|
||||
|
||||
|
||||
While searching, you can install, clean, research or reload the same list on the interactive split. Installing plugins won't load your plugins automatically. To do so, add them to you .vimrc file.
|
||||
|
||||
### Conclusion ###
|
||||
|
||||
Vim is an amazing tool. It can not only be a great default text editor that can make your work flow faster and smoother, but also be turned into an IDE for almost any programming language available. Vundle can be a big help in personalizing the powerful Vim environment quickly and easily.
|
||||
|
||||
Note that there are several sites that allow you to find the right Vim plugins for you. Always check [http://www.vim-scripts.org][3], Github or [http://www.vimawesome.com][4] for new scripts or plugins. Also remember to use the help provider for you plugin.
|
||||
|
||||
Keep rocking with your favorite text editor!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://xmodulo.com/manage-vim-plugins.html
|
||||
|
||||
作者：[Christopher Valerio][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://xmodulo.com/author/valerio
|
||||
[1]:https://github.com/VundleVim/Vundle.vim
|
||||
[2]:http://ask.xmodulo.com/install-git-linux.html
|
||||
[3]:http://www.vim-scripts.org/
|
||||
[4]:http://www.vimawesome.com/
|
||||
Reference in New Issue
Block a user