Difference between revisions of "Talk:Fedora"

Latest revision as of 21:08, 18 August 2014

Split page

Please consider reorganizing this page to start with the current stable release of Fedora and the easiest way to run Sugar with it. Follow that by sections for alpha/beta versions of Fedora Sugar, a short section with links to SoaS, and then links to subpages for ARM, PPC, & older versions of Fedora Sugar. Guidance for GNOME on Fedora and other peripheral content should also probably be on subpages. --FGrose 11:45, 30 June 2012 (EDT)

Pages split --Satellit 20:49, 12 December 2012 (EST)

Having now created pages for Fedora 18, 19, and 20, entry level Sugar information (however up to date) remains, but mixed in with [legacy] Fedora 17. I propose moving all Sugar material, (which I would like to expand) above Fedora 17 material on this page. I wonder whether later, a new page for Fedora 17, would fit better with the current Fedora page naming? Any better suggestions? --Inkyfingers (talk) 17:59, 12 October 2013 (EDT)

I would like this page to be the primary location for information on using Sugar on the current stable release of Fedora (as suggested in the first sentence above), and so, would have to be edited to remain current. The Fedora NN pages should address any special version-specific information or testing, advice, etc., and be considered as secondary pages, which naturally become dated with time. So, yes I agree that the Fedora 17 content could be moved to a Fedora 17 page, and this page always updated for the easiest way to run Sugar on the current version of Fedora. Information not related to running Sugar on Fedora should be minimal on this page. --FGrose (talk) 19:41, 12 October 2013 (EDT)

Content needing organizing

Multiple Machine Caching with yum

http://yum.baseurl.org/wiki/YumMultipleMachineCaching

store rpms in a cache for installation to multiple Computers

Keyring Password Explained

what do you have to enter when connecting to wlan, the keyring password or the wlan-password?
first i must enter the keyring password (root password here) and then i entered the wireless password
the keyring-password should not be your root password, it should be your users password so automatically unlocking could work
it may happen but during current session, after i reboot it appears again
ok, it is the keyring issue, assuming your distro has configured keyring correctly, changing the password should work
root pass?
change the keyring password to your users password
in settings ?
in seahorse
system settings?
as user (the login-keyring)
keyring is a way to store your "gnome" passwords
So, with one password (the keyring one), you "auto-type" the passwords it contains
if the keyring-password is your login password, it's automatically authenticated
keyring stores the passwords encrypted with the according keyring-password, and automatic unlocking works by getting the password through pam on login through gdm and then use  it to unencrypt the passwords - and that can only work if your login-password is the same as the keyring-password

why doesn't gnome 3 display "interactive dialogs" when applications ask for input
yes, also from gnome 3
when you run the shell script from nautilus, it doesn't display a dialog
"Enter passphrase for ..."
you can use zenity for that
try moving /usr/share/gdm/autostart/LoginWindow/gnome-session-check-accelerated.desktop somewhere else
didn't know you needed anything additional for that.. was it always like that or did gnome 2 have that by default?
maybe thats the seahorse/keyring integration, that stuff has changed quite a bit in 3.0
but i thought you meant a more generic approach of showing dialogs from scripts
i'm actually doing the ssh-add from a process spawned by a pygtk app
if it is only this specific case, you should probably still use keyring/seahorse (whatever should do that now) as it would not be passing around passwords unencrypted between processes (at least afaik)
worked!
do you somehow run gdm with a different driver or some weird setup like that?
so it's not possible to get the old behavior, and it needs some additional code to get it to work with seahorse/keyring?
which distro is this?
fedora 15 beta
i've tested the same code on fedora 14 and linuxmint (both gnome 2)
when the ssh-add {key_path} process is spawned, the GUI dialog appears asking you to type in your passphrase
ssh-add succeeds, and them the rest of the pygtk app continues
it doesn't even care whether the key is password protected or anything
i think there needs a daemon to be running that doesn't get started by fedora
this happens both in standard and fallback mode
try launching seahorse-daemon

AutoStart

 ln -s /usr/share/applications/xxxx.desktop ~/.config/autostart/
 don't remember if I had to manually add it to the startup apps (run
 gnome-session-properties) or using a preference in xxxx itself, but I
 have it running on login on my laptop. The icon shows up in the
 notification tray - mouse to the lower right corner to bring it up -
 this is where all legacy tray icons will show up.

fix screensize in sugar-emulator

terminal:
su -
(password)
gedit /usr/share/applications/sugar-emulator.desktop
edit line 6: Exec=sugar-emulator -f
(see how to configure full screen)
save
Logout
login

show desktop as icon in favorites

add programs install "alacarte" 
open alacarte
make new
application
command "nautilus Desktop"
save 
Run from applications
Make favorite

key shortcuts

   * System (Windows) key: Switch between overview and desktop
   * Alt+F1: Switch between overview and desktop
   * Alt+F2: Pop up command dialog
   * Alt+Tab: Pop up window cycler
   * Alt+Shift+Tab: Cycle in reverse direction in the window cycler
   * Alt+`: Switch between windows of the same application in Alt+Tab
   * Ctrl+Alt+Tab: Pop up place cycler
   * Ctrl+Shift+Alt+R: Start and end screencast recording
   * Ctrl+Alt+D: Show desktop and raise windows back
   * Ctrl+Alt+Up/Down arrow: Switch between workspaces
   * Ctrl+Alt+Shift+Up/Down arrow: Move the current window to a different workspace 
Most keybindings can be viewed under the User Menu -> System Settings -> Keyboard -> Shortcuts

List of Autostart programs when starting gnome-shell

   ALT F2 gnome-session-properties

move intro screens that are too large for 800x600

alt+f7 and then the arrow keys
alt+f8 Resize
shift and arrow keys: https://bugzilla.gnome.org/show_bug.cgi?id=262546

It's worth nothing, for Metacity >= 2.13.2, that if the window doesn't have a
minimum size hint larger than the screen then Metacity will now force such
windows to be onscreen (by shrinking and moving them as necessary).  If the
window has a minimum size hint larger than the screen, then the user can use
alt+left-click-and-drag (or alt+f7 and then the arrow keys) to move the window
upwards (including moving the titlebar offscreen) in order to get to the
forward button.  Yeah, that's just a workaround for windows that are too large,
but it may be helpful information for those waiting for the UI changes to make
the window usable on 800x600 resolutions.  :)
clip....
why not use a keyboard shortcut. the "next" button is marked "forward" so i hit alt + f and guess
what, i was able to successfully install the program.

Reload shell ALT+F2 r (reload)

use to recover Applications lists if they go missing and after alacarte edits

http://live.gnome.org/GnomeShell/CheatSheet

How to show user pictures on the GDM LOGIN screen

Click "my account" on the top panel lets me edit the picture, and

adding a picture will show it on the GDM login screen.

If you hold down Alt, a 'Shut Down' option appears in place of suspend.

Alt+Tab switches between windows

hot corner = upper left switches between shell and running applications

Alt+F2 allows entering a command to launch an application.

      the Shell simply always behaves so there's exactly one empty workspace.
      So when you start a session you have one workspace.
      As soon as you run something it goes into that workspace and
      you get a second empty workspace. As soon as you put any app into that
      empty workspace, a new empty workspace is created. If you remove
      everything from any workspace, it will disappear, so there's still only
      one empty workspace at the bottom of the list. So, there's never any
      need to manually add a new workspace. Pretty neat system.

GNOME 3 is not expected to work in virtualized environments

      I've just installed F15 alpha in a virtualbox machine and at the first boot I 
      get a gnome 3 error explaining that it can't be fully initialised because 3D is 
      not supported.
      GNOME3 is not expected to work in virtualized environments where
      hardware accelerated graphics are not available.

      From http://gnome3.org/faq.html ...
       The GNOME 3 desktop does require hardware accelerated graphics
       in order to provide a cutting-edge experience however, and the
       complete GNOME 3 experience will only be available on computers
       capable of this. Do not worry though: GNOME 3 will come complete
       with a fallback interface which will provide an excellent
       experience in the absence of hardware acceleration, and which
       incorporates many of the improvements that can be found in GNOME
       3.
       -------------------------------------------
      test Digest, Vol 85, Issue 60, Message: 7
       It's kind of a definition issue. GNOME *Shell* requires acceleration.
       But technically GNOME 3 does not; the fallback interface is still
       considered to be 'GNOME 3'. So you do need acceleration to get the Shell
       interface that's the 'big new thing' in GNOME 3, but still, if you don't
       have acceleration and you get the fallback interface instead, what
       you're running is still GNOME 3. Just GNOME 3's fallback interface.
       Adam Williamson 
      Message: 8
       In any case, VBox with 3d accelleration enables and 128MB for video memory
       is not sufficient for GShell.  (VBox 4.0.4)
      Message: 13
       Also, on that last note, we should clarify that right now Shell doesn't
       work even in virtualized environments where accelerated graphics *are*
       available, e.g. VirtualBox with appropriate hardware and drivers. In
       theory it should be possible to make this work, but in practice it
       currently doesn't.
       So there's two angles we can approach this from; make Shell run with
       software GL, or fix up Shell to work with virtualized graphics
       acceleration passthrough. But it's not at all guaranteed that we'll
       manage either in time for f15.

       The minimum memory required is 1GB, due to anaconda changes.
       When you see "populate_rootfs" in the panic, it's caused by that.

Fedora-16-vs-macbook-pro-or-air

click this link ^

Add features to Anaconda to aid installation on Apple computers https://bugzilla.redhat.com/show_bug.cgi?id=503149

MacPro and f15 Boot

Clips from #fedora-qa 04/04/2011 MacPro and f15 Boot

I have a macbook pro and have run fedora 14 on it with great success. 15 alpha, on the other hand, is not going well. The installation comes saying something about "installing   *** on EFI ***"
which i just dismiss/ignore, but when i try to boot after installation has completed, it wont. Just saying something like "no file found". Should i do something
special to install 15 alpha on a EFI system?
Yeah... you may have to run gptsync (I think that's what it's called)
no, you don't need to install again, but you will need to gain access to the installed partitions from another system (whether it's a Fedora live image)
referring to the gptsync that is provided be rEFIt
I formatted the partition to make space for a working distro. i have refit installed and my mbp boots to that at startup by default. that didnt make 15 alpha work. 14 did though
you may need to enter the boot partition tool from the rEFIt menu and when it asks to run gptsync, say yes
 okay. I will try to install again later and do that. Thank you so far. Will get back to you guys
I belive anytime partitioning changes occur on a macbook, you do need to run gptsync.  Since the EFI implementation by apple isn't fully compliant with the standard, extra  steps  are required
you don't need to reinstall ... just run gptsync from the rEFIt menu
just need to get your partitions synced up

GNOME3 default software installer fails to find Sugar

>"Fedora 20's default GNOME3 graphical software installer tool fails to find Sugar, reportedly as Sugar is not considered to be an 'application'."

This is a significant problem. Sugar will be more successful if Linux users can easily find it by a simple keyword search in the default installer. A user should not have to install a new installation app in order to find Sugar. I suggest that the team create an "application" that (i) meets Fedora's criteria for applications and (ii) automatically executes a script that downloads and installs the necessary components of Sugar. Better yet, the Sugar Learning Platform Package App could even give a user a set of choices of available components and/or activity packages to add to the script.