Tag Info

New answers tagged

0

This works for me: LIBGL_DEBUG=verbose glxinfo > /dev/null The debug output goes to stderr so I have redirected stdout to null so that it doesn't clutter up the debugging output and make it unreadable. It only outputs six lines of debug info for me, which would easily get lost in the normal output. I am using the Intel drivers that are part of Mesa, ...


0

Easiest way is: 1) encrypt sda1 as desired 2) create lvm or standard partition on sda1 for /home 3) sudo lvm lvmove /dev/mapper/fedora_klinkpad-home /dev/mapper/{blah|sda1} 4) with newly freed space run :sudo lvm lvextend /dev/mapper/fedora_klinkpad-root -l+$someamt of the 60 g) 5) confirm uuids are sane in BOTH /etc/fstab & /etc/crypttab 6) ...


1

even 20 days ago 19 is well past EoL so the repos you are attempting to pull off of are dead. On 20 or 21 the method you are using WILL work as those repos are still active.


0

Meant as clarification comment ---lacks rep tho: lvm2 is a reference to version 2 or using metadata type 2 the default on MOST if not all linux distros these days the pv stands for Physical Volume A quick primer for you: LVM uses a much more flexible layout stucture to the older "extended partition scheme of MBR (old school) layouts. Sample ...


0

also if gparted is truly needed grab a usb and a recent copy of 21 livecd iso and use the gparted / or disk utility pre-loaded / easily installed on it. Then mount the current ailing install and resize (presumably with lvm mechanism like so): lvm lvresize --resizefs -L -$(some smaller size) /dev/mapper/fedora-home lvm lvresize --resizefs -L +$(any or ...


2

This is a known bug in gtk 3.16.1 and a patched version is due to be released sometime around 4/14/2015. In the meantime try running xfce4-panel -r (which restarts/reloads) the panel should get it to reappear if it doesn’t run ps auxww |grep nm-applet if it doesn’t show up there then you have bigger issue (aka it’s not running). If not running try any of the ...


1

I had a few issues with the networkmanager, though not that one... I doubt that XFCE is the culprit though. If that were the case, many would be complaining. And the same problem has been reported for other window managers. Is nm-applet running on your system? Here are some interesting suggestions: https://bbs.archlinux.org/viewtopic.php?id=99125 Checking ...


0

cd / du -hs * Delete unwanted files switch in the folder with the highest fill rate you did not already visited or Goto 6. Check if you are still at the root partition. If not 5.1. cd .. Goto 2


0

while the f16 copies are EoL this holds true for all version: if needing a declared version use (with yum or dnf ) : 1) --releasever=## i.e. --releasever=20 or 21 2) in /etc/yum.conf (or /etc/dnf.conf): hold=foo.$arch i.e. texlive.fc16.x86_64 or exclude=foo.$arch following same procedure as above for hold


0

If you still are having issues try a newer iso or try either of the following: 1) fedup --network --ver 21 --productimg (optionally add 'setenforce=1') 2) launch the installer with 'setenforce=1' ## in both cases DON'T use the ' marks they are merely for comand isolation purposes...


0

on 21 yum is still the default package tool. so you would either: 1) yum-config-manager --save --disablerepo=foo (replace foo with reponame.repo) 2) sudo vi (or any other comfy editor) /etc/yum.repos.d/foo.repo and edit the enabled=0/1 line and save (while a # yum clean all ; #yum update is not generally required it is generally seen as a good ...


0

as the a co-maintainer of the Fedora ISOs I'd recommend downloading QuickHash (link below and use sha256 option with the ISO as the source file ) http://sourceforge.net/projects/quickhash/files/v2.6.1-Windows/ Also nice is that quickhash works on all platforms and computes/compares hashes from md5 thru sha512( used on live updated ISOs ) for the ...


1

Yes it doesn't seem to be logged anywhere for you. @tutuDajuju has a good solution so I thought I'd port it to bash (and remove the dependence on using gnome, this should work regardless of desktop environment) for those that are interested. If you have this running in the background and pipe it to a log file you will have your log. #!/bin/bash #prints ...


1

Figured this out. Just had to put the desktop file in ~/.config/autostart and then it worked like a charm. Thank you so much for the help though Hastur. If anyone is interested in the script, an installation one is available here Link


1

Solaar can be used for configuring Logitech Unifying receiver and newer Logitech products. Allows swapping fn-keys to act normally instead of as media buttons. http://pwr.github.io/Solaar/ Found the information from this thread: http://askubuntu.com/questions/285512/how-to-change-function-fn-key-behavior-on-wireless-logitech-keyboard


0

There is a configuration file /etc/defaults/grub which defines aspects of the environment used by grub to construct grub.cfg. This is one of them. A simple edit removing the references to original lvm environment and replacing them with references to the new lvm environment fixed the issue. The new grub.cfg booted cleanly to the new lvm file system.


0

I've been looking for this option for GNOME 3.14 on debian (nautilus) and couldn't find anything, and now I've stumbled upon it while digging through dconf. So, for nautilus it's gsettings set org.gnome.nautilus.preferences sort-directories-first true or go to dconf under org -> gnome -> nautilus -> preferences and check sort-directories-first if you prefer ...


0

I reconnected the SATA cables in a different order and it cleared things up. I had my optical drive in a higher priority (I think) than one of my HDDs. I have no idea why this would cause a problem, but I put my optical drive in the lowest priority and it magically worked.



Top 50 recent answers are included