Tag Info

Hot answers tagged

3

That is a list of the repositories that yum is currently using. You can get a description of each using: $ yum repolist You can remove this by lowering the debug level of yum: $ yum -d 1 install <a package> To make it permanent, find debuglevel in /etc/yum.conf and set it to 1 (I believe the default is 2). If you do this, you may miss important ...


3

You can dissect the Fedora source rpm - tar-1.26-29.fc20.src.rpm - and find out. On Fedora, you can install the src.rpm. You can also extract it's content, like this: rpm2cpio tar-1.26-29.fc20.src.rpm | cpio --extract --make-directories --verbose The answer to your question is in tar.spec and the associated patches. Example: # Add support for extended ...


3

The obvious answer is this is happening because grub can not find the windows boot loader. The less obvious answer is because the grub configuration file does not properly specify the root for the windows bootloader. The default operation seems to leave that line out. While it would be somewhat complicated to fix the default Windows Bootloader, the ...


3

I've not seen a way to incorporate these results into Nautilus, but there are GUIs for search in mlocate's database. The one that I'm most familiar with is called catfish. It's generally in most of the standard distros' repos. The main website is here, titled: Catfish is a versatile file searching tool.. The project's Launchpad site is another additional ...


2

Set the permissions on /home to 711, not 700. Execute permission is required to access anything within a directory by name, so all users need execute permission on / and /home to access /home/theirname. Omitting read permission will prevent them from listing all the other subdirectories of /home. Permissions on the home directories themselves can be 700. ...


2

The site seems to be down right now. What you can do as a temporary measure is to make an entry in your /etc/hosts file: 137.226.34.42 download.fedoraproject.org then upgrade your system, comment out the above entry and reboot, to see if the problems have disappeared with the upgrade. 137.226.34.42 is ftp.halifax.rwth-aachen.de.


2

There is a developer saying that the libdv module is deprecated in the later builds, here. Excerpt: A next thing I saw was in the configuration wizard that the DV module (libdv) is not checked (so not installed). But if I look in Synaptic then I see that libdv4 version 1.0.0-6 is installed. (0010239) pez4brian (developer) 2014-08-16 ...


2

It's a mechanism that prevents you to set a password that is too weak. Your password strength should be at least "Fair" in order to unlock the Change button. Weak: Fair:


2

I assume you did a fresh install and added the drives to the new computer. First do a: mdadm --assemble --scan and look in /proc/mdstat if the array has been activated. Then run: mdadm --examine --scan >> /etc/mdadm/mdadm.conf to get the config information in your new mdadm.conf again.


1

You can do this in single user mode. Restart system, at grub prompt press down or up arrow so grub screen will be pause. Press "e" to edit grub entries, Select the kernel line and again press "e" to edit mode Now add "1" or "single" at end of the line. and press enter. Press "b" to boot with this setting. Now fedora will start in single user mode. Now you ...


1

If you don't have root password, You have to boot with a Live-CD and chroot to your partition, find out to read only mounted or rw mounted with mount command. If read only mounted, use the following command: mount -o rw,remount / Then use : passwd root


1

The problem was that the system was still using lightdm (xfce's display manager) instead of kde's display manager which is kdm. To force the system to use kdm first I did systemctl enable --force kdm.service then restarted. Followed by yum remove lightdm-gtk-1.6.1-3.fc20.x86_64. Finally finished with yum remove @xfce Should be useful to anyone who might ...


1

Use the modprobe command. Assuming the drivers are called radeon and fglrx you can: modprobe -r radeon modprobe -r fglrx In order to check if those are really the right modules do a lsmod Assuming those procedures do what you need you can edit your modules


1

Please use the below command and remove the genome3x, rm -rf ~/.gnome3 rm -rf ~/.gconf rm -rf ~/.gconfd logged out/in After removing try with upgradation if you wish.


1

The pseudo device /dev/raw1394 may have some restricted acces permissions. Check with ls -l /dev/raw1394 to check ; maybe /dev/raw1394 rely on group like "video" ? If you don't have the pseudo device, it means no driver has been loaded to handle the camcorder. try to see what's happend when connecting it : disconnect the device type tail -f ...


1

YUM tries to install: brlapi-0.6.0-5.fc19.i686 (fedora) from @Fedorra repo: Available: brltty-4.5-5.fc19.x86_64 (fedora) Althought there is already installed one: Installed: brltty-4.5-8.el7.x86_64 (@anaconda) from @anaconda repo. You can try update with disabled repo @fedora: yum update --disablerepo="fedora" Or install package ...


1

It is very common for a package maintainer to include distribution specific patches in packages. Sometimes you can find those included in the changelog of the regular package, which you can query with rpm -q --changelog tar Most often you'll need to check the source package for the details e.g. ...


1

In a Host-Only environment, usually your host computer gets the address 192.168.56.1 and all guests get addresses starting at 192.168.56.101. This can be configured in the VirtualBox settings window. If you are trying to access the Fedora guest system, you probably want this: ssh user@192.168.56.101 replace user with your username on the guest system ...


1

What worked for me was rpm --erase --nodeps cairo which removes the cairo package without checking any dependencies that might be violated by such an action, followed by yum install cairo which installs cairo from the configured package repositories



Only top voted, non community-wiki answers of a minimum length are eligible