FedoraForum.org - Guides & Solutions (No Questions)

Another fix for brightness control issues Fedora 16

jlturn — Tue, 15 May 2012 04:39:33 GMT

Hey everyone, So I had been searching for a fix for an issue where the fn keys don't seem to increase or decrease the screen brightness on my Samsung laptop using fedora 16 64bit, and gnome.

I had followed a post found on the fedora forum where the problem was fixed by reinstalling bash. This did not seem to fix the problem for me. The solution I have tried that has worked so far is by adding:

acpi_backlight=vendor acpi_osi=Linux

to the end of the

GRUB_CMDLINE_LINUX

variable in

/etc/default/grub

and then running the following command to regenerate grub and restarting,

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

I hope that this will work for others as well if resintalling bash does not solve the problem.

**
Source for acpi_backlight=vendor acpi_osi=Linux from
http://geslinux.blogspot.ca/2011/07/...2-display.html

Fedora USB Mouse Polling Increase

CeTis — Fri, 11 May 2012 14:18:35 GMT

Spent 2 hours at least trying to find a solution to this problem for fedora. There are numerous guides on how to increase mouse polling for both ubuntua and arch but nothing for fedora. Finally I stumbled across this from another website (please note I did not create this guide and in no way am taking credit for it, just passing it along on a more popular search recognition then this other website).

"To change USB polling rate:

- Open the terminal
- sudo nano /sys/module/usbhid/parameters/mousepoll
- Change the 0 to a 2
- Control-o to save the changes
- Disconnect the mouse from the USB port and plug it in again

add to /etc/rc.local:

echo 2 > /sys/module/usbhid/parameters/mousepoll

1 - 1000hz
2 - 500hz

================================================== ===================================

For logitech users:

"If you have a nice Logitech mouse, you might notice that it does not operate at full resolution under Linux. Be sure that lomoco is installed.

To set Logitech resolution with lomoco:

- Open the terminal
- lomoco -8"

Webex through Firefox on Fedora 16

safewithyou247 — Thu, 10 May 2012 17:40:39 GMT

Hey All,

Here is a quick guide on how to get Webex working on Fedora 16. This guide is for FIrefox only. I took this info from hxxp://troshlyak.wordpress.com/2010/08/26/webex-on-64bit-fedora-13/ and cleaned it up a bit.

Let me know what you think.

Code:

yum update

setarch i686 yum install firefox

yum reinstall firefox

setarch i686 yum install java-openjdk java-openjdk-plugin

yum reinstall java-openjdk

yum reinstall icedtea-web

setarch i686 yum install libXmu

yum reinstall libXmu

If you get any dependancy errors when you try to install Firefox this may work for you.

Code:

yum check all

yum clean all

yum update

gmail revert to old look permanently

COKEDUDE — Sat, 05 May 2012 22:22:20 GMT

I thought I would share gmail revert to old look permanently. I am sure I am not the only one annoyed by the new look.

Install Stylish extension

Choose the Stylish UserStyle that you want.

I know The Return of Old Gmail and gmail-b2b both work but I prefer gmail-b2b since I think it looks better.

http://techably.com/make-gmail-older...ermanent/4215/

http://userstyles.org/styles/browse/all/gmail

LXDE - setting the default terminal

jiangshi — Wed, 02 May 2012 14:46:20 GMT

Greetings!

LXDE is a terrific light-weight desktop for Fedora Linux (or any distro that offers it). The default terminal for PCmanFM, the default file manager, is not set during installation of Fedora LXDE. This post describes how to set the default terminal for using the F4 key function in PCmanFM.

The F4 key function allows the user to open a terminal session in the currently viewed directory (folder). It can be faster to navigate to a desired directory or file using PCmanFM than typing long path lists in the terminal window.

To set PCmanFM's default terminal do the following:

1) Start PCmanFM - the icon is near the Fedora menu button on the task bar.

2) From the menu select Edit -> Preferences.

3) Click on the Advanced tab to bring it forward.

4) In the text box titled Terminal Emulator, type in this: lxterminal -e %s

5) Click the Close button, and you are done!

To be fair, the Advanced tab does show an example using xterm. So now you know how to set it for lxterminal too.

Cheers!

~jiangshi

Script: Connect and Debug to Samba NAS

sea — Wed, 02 May 2012 02:18:12 GMT

Heyas

As some might have recently, i've had some issues to connect to my NAS.
Figured i made mistakes, but have learned a bit on the road, which the Fedora Community shall benefit from.
At least i hope its helpful ;)

Features:
* Create a credentials file
* Connect to a single share on NAS, using cli.
* Mount all directory to local environment
* Easier debugging, collect data that helps you debugging.
* Change the default variables in the script, so you can just hit enter for your hardcoded default values -> easier re-usage.

For best results, and previous to first execution of the script:

mkdir $HOME/bin
chmod +x sea-samba.sh
mv sea-samba.sh /$HOME/bin
su

yum install cifs-utils samba-client
sea-samba

Once the credentials are created, its quiete easy to use:
Mounting all shares from NAS to local might look similar to this, whilst using sea-samba.sh mn

Code:

                sea's Samba script tool (0.5)

Moutning 192.168.10.110 to /nas

Mounting:        //192.168.10.110/priv    to /nas/priv            done   

Mounting:        //192.168.10.110/pub     to /nas/pub             done   

Mounting:        //192.168.10.110/TimeMac to /nas/TimeMachine     done   

Mounting:        //192.168.10.110/Picture to /nas/Pictures        done   

Mounting:        //192.168.10.110/Music   to /nas/Music           done   

Mounting:        //192.168.10.110/Movies  to /nas/Movies          done   

Mounting:        //192.168.10.110/Linux   to /nas/Linux           done   

Mounting:        //192.168.10.110/Backups to /nas/Backups         done

Where the 'main' menu looks like:

Code:

Domain=[OGOG] OS=[Unix] Server=[Samba 3.5.6]

Domain=[OGOG] OS=[Unix] Server=[Samba 3.5.6]

                sea's Samba script tool (0.5)

1) Exit

2) Single connection to 1 share on "ocean"

3) Mount all shares on "ocean" to "/nas"

4) Debug 

5) Edit: /etc/samba/smb.cred

6) Edit: /etc/samba/smb.conf

7) Edit: /etc/samba/nas.conf

#?

Have to cut out the "help-command"-part as its too large...

Code:

for arg in $@

do         if [ "h" = "$arg" ] || [ "-h" = "$arg" ] || [ "--h" = "$arg" ] || [ "--help" = "$arg" ]  || [ "-help" = "$arg" ]

then

cat << EOF

    There are no arguments required.

    Simply edit the variables in the script and/or

    provide the information to create the configuration

    and credential files.

    

    These files will not only ease the use of this script,

    but are also more secure (credential) than using those

    values as plain text (hard coded) in your scripts.

    

    If you need root access, it is suggested to use a term like:

      *)       su -c /path/to/sea-samba

      *)       su -c sea-samba

    

    To perform action right from the command line use these arguments:

      *)        mn        =         Mount Nas ; Connects to your NAS,

                                      if not root a password is required

      *)        co        =         Connect to Share

                                      Reads the shares on the NAS and ask you to

                                      which you want to connect.

    

    If you have any ideas to improve this script, 

    find bugs or a solution for them, feel free to send me an

    email to: < erat.simon AT gmail.com > ... with the subject "samba".



EOF

fi

done

Attached Files

sea-samba.sh (10,3 KB)

Realcrypt/Truecrypt Permission error?

Cylinder57 — Mon, 30 Apr 2012 02:27:05 GMT

Hello everyone,

While the concept of realcrypt permission denied has been touched upon in these posts:
(I had this problem too, and by reading these posts, I solved it.)

http://forums.fedoraforum.org/showthread.php?t=234318

http://www.fedoraforum.org/forum/sho...d.php?t=246947

forums.fedoraforum.org/showthread.php?t=241756&highlight=realcrypt+mount (See post 7 and 13, especially 13.)

I would like to state the solution. My solution worked in Fedora 15.

Note that this guide assumes you have realcrypt and you can access its windows.

1. Go to the top bar and click on settings.

2. Click on preferences.

3. Go to mount options tab.

4. In the textbox to the right of mount options, type your uid and gid (If that does not work, type the uid ONLY. That's what I did, and it worked.)

To find the uid and gid, try something like vi /etc/passwd or nano /etc/passwd .
The uid and gid is in: username:x:uid:gid: (...more is on this line)

username is your username, and uid and gid are self-explanatory.

incorrect max. screen resolution due to invalid EDID data

lockheed02 — Sun, 29 Apr 2012 09:19:37 GMT

I thought I'd share as it might be useful to others as well. After successfully installing nvidia binary driver I was only offered 1024x768 screen resoultion but my screen can do 1280x1024.

My Xorg.0.log file showed lines like that

Code:

[  9792.343] (WW) NVIDIA(GPU-0): The EDID read for display device CRT-0 is invalid:

[  9792.343] (WW) NVIDIA(GPU-0):     unrecognized EDID Header.

Neitther read-edid nor monitor-get-edid programs could help me. So I disabled automatic EDID usage and added a modeline manually (using the "# gtf 1280 1024 60" command) in xorg.conf file,

Code:

[root@beefy ~]# gtf 1280 1024 60



  # 1280x1024 @ 60.00 Hz (GTF) hsync: 63.60 kHz; pclk: 108.88 MHz

  Modeline "1280x1024_60.00"  108.88  1280 1360 1496 1712  1024 1025 1028 1060  -HSync +Vsync

but still something didn't work out as the Xorg.0.log still showed:

Code:

[  9792.463] (II) NVIDIA(0): Assigned Display Device: CRT-0

[  9792.463] (WW) NVIDIA(0): No valid modes for "1280x1024_60x00"; removing.

[  9792.463] (WW) NVIDIA(0): 

[  9792.463] (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode

[  9792.463] (WW) NVIDIA(0):     "nvidia-auto-select".

[  9792.463] (WW) NVIDIA(0): 

[  9792.463] (II) NVIDIA(0): Validated modes:

[  9792.463] (II) NVIDIA(0): Virtual screen size determined to be 1024 x 768

So I enabled debug output and default configuration.

Code:

# nvidia-xconfig --no-use-edid

# nvidia-xconfig --mode-debug

(alternatively add Option "ModeDebug" "True" into Screen section)

Now I got the real cause of the information why my line got rejected:

Code:

[  8713.031] (--) NVIDIA(0): No EDID Available.

[  8713.031] (--) NVIDIA(0): 

[  8713.031] (--) NVIDIA(0): --- End of EDID for CRT-0 ---

[  8713.031] (--) NVIDIA(0): 

[  8713.127] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display

[  8713.127] (**) NVIDIA(0):     device CRT-0 (Using EDID frequencies has been enabled on

[  8713.127] (**) NVIDIA(0):     all display devices.)

[  8713.127] (II) NVIDIA(0): Frequency information for CRT-0:

[  8713.127] (II) NVIDIA(0):   HorizSync   : 28.000-55.000 kHz

[  8713.127] (II) NVIDIA(0):   VertRefresh : 43.000-72.000 Hz

[  8713.127] (II) NVIDIA(0):     (HorizSync from Conservative Defaults)

[  8713.127] (II) NVIDIA(0):     (VertRefresh from Conservative Defaults)

[  8713.127] (II) NVIDIA(0): 

[  8713.127] (II) NVIDIA(0): --- Building ModePool for CRT-0 ---

[  8713.127] (II) NVIDIA(0):   Validating Mode "1280x1024_60.00":

[  8713.127] (II) NVIDIA(0):     1280 x 1024 @ 60 Hz

[  8713.127] (II) NVIDIA(0):     Mode Source: X Configuration file ModeLine

[  8713.127] (II) NVIDIA(0):       Pixel Clock      : 108.88 MHz

[  8713.127] (II) NVIDIA(0):       HRes, HSyncStart : 1280, 1360

[  8713.127] (II) NVIDIA(0):       HSyncEnd, HTotal : 1496, 1712

[  8713.127] (II) NVIDIA(0):       VRes, VSyncStart : 1024, 1025

[  8713.127] (II) NVIDIA(0):       VSyncEnd, VTotal : 1028, 1060

[  8713.127] (II) NVIDIA(0):       H/V Polarity     : -/+

[  8713.127] (WW) NVIDIA(0):     Mode is rejected: HorizSync (63.6 kHz) out of range

[  8713.127] (WW) NVIDIA(0):     (28.000-55.000 kHz).

According to that my used HorizSync value was simply outside range of the "conservative" range.

So now simply adjusting that HorizSync value in Monitor section of xorg.conf:

Code:

Section "Monitor"

  # 1280x1024 @ 60.00 Hz (GTF) hsync: 63.60 kHz; pclk: 108.88 MHz

    Identifier     "CRT-0"

    VendorName     "Samsung"

    ModelName      "VisionMagic"

    HorizSync       28.0 - 63.7

    ModeLine       "1280x1024_60.00" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -hsync +vsync

EndSection

...

And now suddenly nvidia-settings and also "System Settings" offer that 1280x1024 resolution. Xorg.0.log says now:

Code:

[    22.320] (II) NVIDIA(0):   Validating Mode "1280x1024":

[    22.320] (II) NVIDIA(0):     1280 x 1024 @ 60 Hz

[    22.320] (II) NVIDIA(0):     Mode Source: X Server

[    22.320] (II) NVIDIA(0):       Pixel Clock      : 108.00 MHz

[    22.320] (II) NVIDIA(0):       HRes, HSyncStart : 1280, 1328

[    22.320] (II) NVIDIA(0):       HSyncEnd, HTotal : 1440, 1688

[    22.320] (II) NVIDIA(0):       VRes, VSyncStart : 1024, 1025

[    22.320] (II) NVIDIA(0):       VSyncEnd, VTotal : 1028, 1066

[    22.320] (II) NVIDIA(0):       H/V Polarity     : +/+

[    22.320] (II) NVIDIA(GPU-0):     BestFit Centered         1280x1024

[    22.320] (II) NVIDIA(GPU-0):       Horizontal Taps        0

[    22.320] (II) NVIDIA(GPU-0):       Vertical Taps          0

[    22.321] (II) NVIDIA(GPU-0):       Base SuperSample       x4

[    22.321] (II) NVIDIA(GPU-0):       Base Depth             32

[    22.321] (II) NVIDIA(GPU-0):       Distributed Rendering  1

[    22.321] (II) NVIDIA(GPU-0):       Overlay Depth          32

[    22.321] (II) NVIDIA(0):     Mode is valid.

I hope this gives some hints in case you come across similar issues.

Lockheed

Apache AD authentication via PAM/Kerberos

Teibidh — Tue, 24 Apr 2012 14:23:48 GMT

In progress due to time restrictions. Feedback on more efficient/secure configuration is absolutely welcome, and I will attempt to revise the guide over the course of next couple of weeks accordingly.

I spent the last few days piecing together information from various sources to get a couple of web sites we're using for our intranet configured to use Kerberos and winbind to limit their availability to members of specific Windows Active Directory groups within our organization. Since we require that all of our Linux systems allow administrators to logon with their AD credentials, it seemed natural to me to extend this same capability and have a single authentication system interacting with AD instead of using several different LDAP configurations. Below is a series of steps required to add a Fedora (16, but I used pretty much the same steps for 14 and 15 at various times in various pieces) installation to an AD domain, configure authentication via PAM and then extend PAM authentication to SSH and Apache.

First, packages that will need to be installed... I use a "Minimal" installation so you may find you have some of these installed already:

Quote:

httpd
krb5-workstation *
mod_auth_pam
mod_ssl
pam_krb5
pam_ssh
samba-winbind
samba-winbind-clients

Definitions

Authentication - This is verifying that someone is who they say they are. In the case of this guide this will be done via passwords checked against Active Directory accounts using Kerberos.
Authorization - This is determining what resources an authenticated user is or is not supposed to have access to. In this case we will differentiate based on AD security group membership.
Kerberos - Honestly, I know very little about Kerberos so I won't pretend to, for purposes of this guide suffice to say it is a protocol that is used to allow PAM to securely query Active Directory and authenticate a user.
PAM - Pluggable Authentication Modules is designed to allow applications to authenticate/authorize users without having to tangle with the actual user management back-end. A PAM aware program doesn't care whether you're using local users, LDAP users, Active Directory or a MySQL database for users, it just asks PAM to authenticate a user and (optionally) find out what groups a user is part of. PAM's job is to take those authentication requests and use any number of modules to access the necessary authentication/authorization information.
Winbind - Part of the Samba suite, used here to enumerate user accounts and groups from AD to usable UID and GIDs for authorization purposes.

Make sure necessary services are started and are going to start automatically at system startup:

Quote:

systemctl enable winbind.service
systemctl enable httpd.service
systemctl start winbind.service
systemctl start httpd.service

Note: For some reason I have to restart after installing these via yum because the *.service files aren't in place yet, haven't bothered looking in to why or resolving it, but if you installed the packages and systemctl returns an error, try restarting.

The following command will configure several files in the /etc folder that are necessary to allow the computer to join an AD domain. This is important because in any sane configuration Windows Active Directory doesn't allow anonymous queries and you would have to attach valid user credentials to any attempt to authenticate users at which point you might as well use LDAP.

Quote:

authconfig --update --enablewinbind --enablewinbindauth --smbsecurity=ads --winbindtemplatehomedir=/home/%U --winbindtemplateshell=/bin/sh --enablewinbindusedefaultdomain --enablelocauthorize --enablemkhomedir --enablekrb5 --enablekrb5kdcdns --enablekrb5realmdns \
--smbworkgroup=\
--smbrealm=\
--smbservers=\
--krb5realm=\
--smbidmapuid=100000-200000 \
--smbidmapgid=100000-200000 \

Please note that some of these options may not be necessary for your environment and I encourage the use of man authconfig and authconfig --help to validate any command before you enter it. Also, there may be additional configuration required for Kerberos on your AD servers, my understanding is that it works out of the box, but our domain controllers were set up years before I started working here and we already had a couple of Linux boxes authenticating against them, it was just that no one knew how exactly.

The above command configured a handful of files in /etc (nsswitch.conf, pam.d/system-auth-ac, krb5.conf, samba/smb.conf) but didn't actually DO anything (even though it probably resulted in a couple of not-so-savory looking warnings. To actually complete the process of joining the computer to the domain use the following command:

Quote:

net ads join -U

Verify that the above stuff worked by using the following commands and getting output similar to what's listed:

Quote:

kinit

- Enter password when prompted, correct execution will return no output.

Quote:

klist

- Correct output will show Kerberos ticket timestamp/expiration info.

Quote:

wbinfo -r

- Correct output will show a sequential enumerated list.

Quote:

wbinfo --gid-info=

- Correct output will show you AD group name followed by the members.
Because we need to configure it anyway, and because it's a good test that doesn't alter your ability to logon to the box (but could alter your ability to use sudo, so make sure you know the root password) run visudo and add the line %domain\ admins ALL=(ALL) ALL. Create a new logon session (I'd leave the current one alone and in place for the moment) using an account that's part of the group specified (Domain Admins in my example) and make sure that sudo works.
Configure SSH to allow login only from specific groups, in our case, the Domain Admins group, by using vi or whatever text editor you choose to edit /etc/ssh/sshd_config. By default in a Fedora 16 installation SSH uses PAM, so UsePAM yes should already be present and not commented, fix it if it's not. Then add the line AllowGroups "domain admins", save and use the following to restart SSH:

Quote:

systemctl restart sshd.service

.
Create a file named httpd in /etc/pam.d and populate it with the following lines:

Quote:

#%PAM-1.0
auth required pam_krb5.so
auth sufficient pam_winbind.so
account required pam_permit.so

This will allow httpd (Apache) to use PAM and tell PAM what to say yes or no to. The use of pam_permit.so allows us to configure specifics within the Apache .conf files instead of having to specify allowed groups and the like within the PAM configuration directly (which would get messy if you wanted different sets of permissions for different pages).

I will not get in to detail about how the Apache .conf files are laid out, however, please understand that the changes I'm making here are for the entirety of the Apache server instance. Any attempt to access any page within the site will require authentication against AD, but this will only provide for access to the .HTML/.PHP files on the server, it will not (automatically) handle authentication required for installed web-based applications such as phpMyAdmin which needs you to provide a password for your MySQL instance (though this can be done too...)

Open /etc/httpd/conf/httpd.conf with your text editor of choice (make a backup first if you wish, though a smarter method might be to simply comment out lines using # and add a comment line before and after the lines you add so you know what to change in the future) and modify the element to look like this:

Quote:

Options FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
AuthName "Active Directory Authentication"
AuthPAM_Enabled on
AuthPAM_FallThrough off
AuthBasicAuthoritative off
AuthGROUP_Enabled on
AuthUserFile /dev/null
AuthType Basic
Require valid-user

What we accomplish here is requiring that a user must provide valid AD credentials to access any web page hosted on our server. Now, to further secure specific pages you would place the following within the element specific to that page to restrict access to it to members of the Domain Admins group specifically:

Quote:

Order Deny,Allow
..
..
Require group "domain admins"

I'm a pretty smart guy, but I certainly didn't write any of the software being used and I didn't magically know how to get this done (in fact, I'm still not sure it's the best way :C), I pulled info from ton of places and wish I could cite them all, but I didn't plan on writing this so I didn't keep track. Feel free to redistribute some or all of this information, if you do decide to actually copy parts of it I'd appreciate if you link back to this post more to support FedoraForum.org than for any need for personal credit.

:dance:

Using GNOME2 on Fedora 16

timliim — Mon, 23 Apr 2012 02:19:06 GMT

This projcet is for those who want to use GNOME2 on Fedora 16 (17, 18, ... when possible). For those who are happy with GNOME3, you can safely skip this one.

What is GNOME2.F16?

From the name it is clear that this project is for running GNOME2 on Fedora 16. It is a perl script (gnome2.build.pl) that downloads selected GNOME2 src rpm from Fedora 14, compiles and installs on Fedora 16. The end result is a mix of GNOME2 and GNOME3 on Fedora 16, with the UI (metacity, session manger, screen saver, applets, etc.) from GNOME2, and the rest from GNOME3.

There are already other projects (eg. Blue Bubble, MATE, Cinnamon) aiming to bring GNOME2 experience to newer Fedora Linux. However I still need these two items:

a screen saver that can display the photos I have.
build from Fedora-sanctioned source code.

The first one is easy. I feel ashamed to tell people that my Fedora box can no longer display my thousands of photos with screen saver, which their Windows box is fully capable of.

My second goal is to build the whole project with existing Fedora source, with minimum injection from me. The GNOME2 will come from Fedora 14. Whatever parts I can use on Fedora 16 is fine. With no binaries release from this project, this reduces the chance of people asking, "Who is this Tim the tool guy? Can I trust his binary release?"

This tool is intended as an interim solution, until some long term solution emerges on Fedora. Specifically, I need a screensaver that are capable of showing photos.

Credit
This project is inspired by

the Blue Bubble project (by Nushio et al) and
the MATE project (by Perberos et al).

(I was not aware of the Cinnamon project when I started, so I cannot include Cinnamon, yet.)

How to use it?

A Fedora 16 box with minimum installation (no GUI needed; in anaconda, select "minimum" for package selection).
yum install -y perl createrepo
download gnome2.build.pl from the GNOME2.F16 project.
run it as any non-root user with sudo privilege (this takes an hour or two on my VM.)

perl ./gnome2.build.pl --build-and-install
sudo gnome2-install.sh
sudo reboot
On some machines the GDM login window may not show. The work around is to hit key during plymouth graphical boot to use text mode boot. A longer term workaround is to remove �rhgb� from kernel args in /boot/grub2/grub.cfg.

The usual pre-caution applies:

Do not try this on any box with data that you want to keep.
Of course there are bugs as this is an experimental project. However there are not-too-bad workarounds for known bugs.

For those who wishes to download binaries directly, you may use my build (the same gnome2-repo.rpm works for both x86_64 and i386):

Code:

rpm -i http://formosa.homelinux.com/pub/fedora/gnome2/i386/os/gnome2-repo-1.0-1.fc16.noarch.rpm

gnome2-install.sh

See GNOME2.F16 home page for known issues and workarounds.

Code:

http://formosa.homelinux.com/pub/fedora/gnome2/GNOME2.F16.html

Cheers,
Tim Taiwanese Liim

Using GNOME2 on Fedora 16

timliim — Mon, 23 Apr 2012 01:56:17 GMT

This projcet is for those who want to use GNOME2 on Fedora 16 (17, 18, ... when possible). For those who are happy with GNOME3, you can safely skip this one.
The home page of GNOME2.F16 is at

Code:

http://formosa.homelinux.com/pub/fedora/gnome2/GNOME2.F16.html

What is GNOME2.F16?

From the name it is clear that this project is for running GNOME2 on Fedora 16. It is a perl script (gnome2.build.pl) that downloads selected GNOME2 src rpm from Fedora 14, compiles and installs on Fedora 16. The end result is a mix of GNOME2 and GNOME3 on Fedora 16, with the UI (metacity, session manger, screen saver, applets, etc.) from GNOME2, and the rest from GNOME3.

There are already other projects (eg. Blue Bubble, MATE, Cinnamon) aiming to bring GNOME2 experience to newer Fedora Linux. However I still need these two items:

a screen saver that can display the photos I have.
build from Fedora-sanctioned source code.

The first one is easy. I am ashamed to tell people that my Fedora box can no longer display my thousands of photos with screen saver, which their Windows box is fully capable of.

My second goal is to build the whole project with existing Fedora source, with minimum injection from me. The GNOME2 will come from Fedora 14. Whatever parts I can use on Fedora 16 is fine. With no binaries release from this project, this reduces the chance of people asking, "Who is this Tim the tool guy? Can I trust his binary release?"

This tool is intended as an interim solution, until some long term solution emerges on Fedora. Specifically, I need a screensaver that are capable of showing photos.

Credit
This project is inspired by

the Blue Bubble project (by Nushio et al) and
the MATE project (by Perberos et al).

(I was not aware of the Cinnamon project when I started, so I cannot include Cinnamon, yet.)

How to use it?

A Fedora 16 box with minimum installation (no GUI needed; in anaconda, select "minimum" for package selection).
yum install -y perl createrepo
download gnome2.build.pl from the GNOME2.F16 project.
run it as any non-root user with sudo privilege (this takes an hour or two on my VM.)

perl ./gnome2.build.pl --build-and-install
sudo gnome2-install.sh
sudo reboot
On some machines the GDM login window may not show. The work around is to hit key during plymouth graphical boot to use text mode boot. A longer term workaround is to remove �rhgb� from kernel args in /boot/grub2/grub.cfg.

The usual pre-caution applies:

Do not try this on any box with data that you want to keep.
Of course there are bugs as this is an experimental project. However there are not-too-bad workarounds for known bugs.

For those who wishes to download binaries directly, you may use my build (the same gnome2-repo.rpm works for both x86_64 and i386):

Code:

rpm -i http://formosa.homelinux.com/pub/fedora/gnome2/i386/os/gnome2-repo-1.0-1.fc16.noarch.rpm

gnome2-install.sh

See GNOME2.F16 home page for known issues and workarounds.
http://formosa.homelinux.com/pub/fed...NOME2.F16.html

Cheers,
Tim Taiwanese Liim

Howto use keyboard shortcut to reboot/shutdown from gnome/cinnamon

hieronymous — Sun, 22 Apr 2012 23:03:29 GMT

For those of you frustrated like me at having to use the mouse/to shutdown, here is an easy keyboard solution method:

Use dconf-editor to go to:

org.gnome.settings-daemon.plugins.power

change button-power to interactive by holding down the left mouse button and dragging down the drop-down menu.

Install KeePass 2 in Fedora 16

safewithyou247 — Wed, 18 Apr 2012 15:43:22 GMT

Here is a guide to installing and configuring KeePass 2 in Fedora 16. Let me know if you have any questions or suggestions.

***change to su***

Code:

su

***Check package info***

Code:

yum info mono-core

***Install package***

Code:

yum -y install mono-core

***Check package info***

Code:

yum info mono-devel

***Install package***

Code:

yum -y install mono-devel

download keepass portable from hxxp://keepass.info/download.html

***Create file for archive to be extracted to***

Code:

cd /usr/bin

mkdir KeePass

***unzip keepass .zip file***

Code:

unzip -d KeePass/

***download KeePass icon***
hxxp://upload.wikimedia.org/wikipedia/commons/1/19/KeePass_icon.png

***move to keepass folder***

Code:

mv KeePass_icon.png /usr/bin/KeePass/KeePass_icon.png

***Create shortcut for your applications menu***

Code:

cd /usr/share/applications/

nano KeePass.desktop

***Add the following lines to Nano***

Code:

[Desktop Entry]

Name=KeePass

Exec=mono /usr/bin/KeePass/KeePass.exe

Icon=/usr/bin/KeePass/KeePass_icon.png

Categories=Other

Type=Application

***Save file***
ctl-x
type y
press enter

***Restart Gnome 3***
alt-f2
type r
press enter

There you go. You should have a fully functional KeePass.

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0.0 is empty, not checked.

COKEDUDE — Mon, 16 Apr 2012 21:57:31 GMT

I thought I would document this error since its not documented very well. The package or file may be different but the idea is the same.

Code:

$ sudo yum updateLoaded plugins: langpacks, presto, refresh-packagekit, versionlock

Setting up Update Process

Resolving Dependencies

--> Running transaction check

---> Package audit.i686 0:2.2-1.fc15 will be updated

---> Package audit.i686 0:2.2.1-1.fc15 will be an update

---> Package audit-libs.i686 0:2.2-1.fc15 will be updated

---> Package audit-libs.i686 0:2.2.1-1.fc15 will be an update

---> Package audit-libs-python.i686 0:2.2-1.fc15 will be updated

---> Package audit-libs-python.i686 0:2.2.1-1.fc15 will be an update

---> Package dvb-apps.i686 0:1.1.2-0.1457.bec11f78be51.fc15 will be updated

---> Package dvb-apps.i686 0:1.1.2-0.1479.37781d27a444.fc15 will be an update

---> Package flash-plugin.i386 0:11.2.202.228-release will be updated

---> Package flash-plugin.i386 0:11.2.202.233-release will be an update

---> Package meld.noarch 0:1.5.3-1.fc15 will be updated

---> Package meld.noarch 0:1.5.4-1.fc15 will be an update

---> Package mysql.i686 0:5.5.21-1.fc15 will be updated

---> Package mysql.i686 0:5.5.22-1.fc15 will be an update

---> Package mysql-embedded.i686 0:5.5.21-1.fc15 will be updated

---> Package mysql-embedded.i686 0:5.5.22-1.fc15 will be an update

---> Package mysql-libs.i686 0:5.5.21-1.fc15 will be updated

---> Package mysql-libs.i686 0:5.5.22-1.fc15 will be an update

---> Package mysql-server.i686 0:5.5.21-1.fc15 will be updated

---> Package mysql-server.i686 0:5.5.22-1.fc15 will be an update

--> Finished Dependency Resolution



Dependencies Resolved



========================================================================

Package Arch Version Repository Size

========================================================================

Updating:

audit i686 2.2.1-1.fc15 updates 209 k

audit-libs i686 2.2.1-1.fc15 updates 67 k

audit-libs-python i686 2.2.1-1.fc15 updates 62 k

dvb-apps i686 1.1.2-0.1479.37781d27a444.fc15

updates 345 k

flash-plugin i386 11.2.202.233-release adobe-linux-i386 6.6 M

meld noarch 1.5.4-1.fc15 updates 473 k

mysql i686 5.5.22-1.fc15 updates 4.5 M

mysql-embedded i686 5.5.22-1.fc15 updates 2.8 M

mysql-libs i686 5.5.22-1.fc15 updates 696 k

mysql-server i686 5.5.22-1.fc15 updates 8.3 M



Transaction Summary

========================================================================

Upgrade 10 Package(s)



Total download size: 24 M

Is this ok [y/N]: y

Downloading Packages:

Setting up and reading Presto delta metadata

updates/prestodelta | 1.0 MB 00:01

Processing delta metadata

Download delta size: 760 k

(1/6): audit-2.2-1.fc15_2.2.1-1.fc15.i686.drpm | 161 kB 00:00

(2/6): audit-libs-2.2-1.fc15_2.2.1-1.fc15.i686.d | 29 kB 00:00

(3/6): audit-libs-python-2.2-1.fc15_2.2.1-1.fc15 | 11 kB 00:00

(4/6): meld-1.5.3-1.fc15_1.5.4-1.fc15.noarch.drp | 73 kB 00:00

(5/6): mysql-embedded-5.5.21-1.fc15_5.5.22-1.fc1 | 428 kB 00:00

(6/6): mysql-libs-5.5.21-1.fc15_5.5.22-1.fc15.i6 | 59 kB 00:00

Finishing rebuild of rpms, from deltarpms

 | 4.2 MB 00:07

Presto reduced the update size by 83% (from 4.2 M to 760 k).

Package(s) data still to download: 20 M

(1/4): dvb-apps-1.1.2-0.1479.37781d27a444.fc15.i | 345 kB 00:00

(2/4): flash-plugin-11.2.202.233-release.i386.rp | 6.6 MB 00:11

(3/4): mysql-5.5.22-1.fc15.i686.rpm | 4.5 MB 00:07

(4/4): mysql-server-5.5.22-1.fc15.i686.rpm | 8.3 MB 00:15

------------------------------------------------------------------------

Total 512 kB/s | 20 MB 00:39

Running rpm_check_debug

Running Transaction Test

Transaction Test Succeeded

Running Transaction

Warning: RPMDB altered outside of yum.

Updating : meld-1.5.4-1.fc15.noarch 1/20

Updating : audit-libs-2.2.1-1.fc15.i686 2/20

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0.0 is empty, not checked.

Updating : mysql-libs-5.5.22-1.fc15.i686 3/20

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0.0 is empty, not checked.

Updating : mysql-5.5.22-1.fc15.i686 4/20

Updating : mysql-server-5.5.22-1.fc15.i686 5/20

Updating : audit-2.2.1-1.fc15.i686 6/20

Updating : audit-libs-python-2.2.1-1.fc15.i686 7/20

Updating : flash-plugin-11.2.202.233-release.i386 8/20

Updating : dvb-apps-1.1.2-0.1479.37781d27a444.fc15.i686 9/20

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0.0 is empty, not checked.

Updating : mysql-embedded-5.5.22-1.fc15.i686 10/20

Cleanup : mysql-server-5.5.21-1.fc15.i686 11/20

Cleanup : mysql-5.5.21-1.fc15.i686 12/20

Cleanup : audit-libs-python-2.2-1.fc15.i686 13/20

Cleanup : audit-2.2-1.fc15.i686 14/20

Cleanup : audit-libs-2.2-1.fc15.i686 15/20

Cleanup : mysql-libs-5.5.21-1.fc15.i686 16/20

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0.0 is empty, not checked.

Cleanup : flash-plugin-11.2.202.228-release.i386 17/20

Cleanup : dvb-apps-1.1.2-0.1457.bec11f78be51.fc15.i686 18/20

Cleanup : mysql-embedded-5.5.21-1.fc15.i686 19/20

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1 is empty, not checked.

/sbin/ldconfig: File /usr/lib/libquazip.so.1.0.0 is empty, not checked.

Cleanup : meld-1.5.3-1.fc15.noarch 20/20



Updated:

audit.i686 0:2.2.1-1.fc15

audit-libs.i686 0:2.2.1-1.fc15

audit-libs-python.i686 0:2.2.1-1.fc15

dvb-apps.i686 0:1.1.2-0.1479.37781d27a444.fc15

flash-plugin.i386 0:11.2.202.233-release

meld.noarch 0:1.5.4-1.fc15

mysql.i686 0:5.5.22-1.fc15

mysql-embedded.i686 0:5.5.22-1.fc15

mysql-libs.i686 0:5.5.22-1.fc15

mysql-server.i686 0:5.5.22-1.fc15

Here you are figuring out what package the file belongs to.

Code:

$ rpm -qf /usr/lib/libquazip.so.1.0

quazip-0.3-3.fc15.i686

Here you are reinstalling the problem package.

Code:

$ sudo yum reinstall quazip

A reference for a different package.

https://bbs.archlinux.org/viewtopic.php?pid=865928