Changes

8,632 bytes added ,  22:08, 18 August 2014
Line 1: Line 1: −
==testing os873 XO-1.5==
  −
: No entry in jabber line of CP
  −
===Collaboration===
  −
====Chat====
  −
: os871 on XO-1 and os873 on XO-1.5
  −
::Connected on Ad-hoc Network 1
  −
::Title changed to 873
  −
:::Appears on XO-1 correctly in chat but NOT on chat icon on f1
  −
::Colors are correct
  −
::Avitars in F1 connect correctly
  −
:::Smileys work
     −
==testing os871 XO-1.5==
+
==Split page==
:07/04/2011 reflashed with USB
+
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.  --[[User:FGrose|FGrose]] 11:45, 30 June 2012 (EDT)
;kernel panic; reboot with USB inserted
+
:Pages split --[[User:Satellit|Satellit]] 20:49, 12 December 2012 (EST)
::Power off
+
::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? --[[User:Inkyfingers|Inkyfingers]] ([[User talk:Inkyfingers|talk]]) 17:59, 12 October 2013 (EDT)
::OK on reboot
+
::: 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.  --[[User:FGrose|FGrose]] ([[User talk:FGrose|talk]]) 19:41, 12 October 2013 (EDT)
===About my Computer===
+
===Content needing organizing ===
  Serial Number:SHC04900144
+
====Multiple Machine Caching with yum====
  Build 871
+
*http://yum.baseurl.org/wiki/YumMultipleMachineCaching
  sugar 0.92.2
+
:store rpms in a cache for installation to multiple Computers
  firmware Q3B13
+
====Keyring Password Explained====
  wireless firmware 9.70.7p0
+
  what do you have to enter when connecting to wlan, the keyring password or the wlan-password?
;XO-1.5 ON LOAN FROM OLPC
+
first i must enter the keyring password (root password here) and then i entered the wireless password
::http://wiki.laptop.org/go/Projects/Dextrose2_testing_with_a_loaned_XO-1.5
+
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
   −
===Testing===
+
why doesn't gnome 3 display "interactive dialogs" when applications ask for input
*Start Browse before jabber connection:
+
yes, also from gnome 3
:'''Starts on first try'''
+
when you run the shell script from nautilus, it doesn't display a dialog
*Connect to Apple Network Airport Extreme AP WEP ASCII
+
"Enter passphrase for ..."
*Network ADD Jabber.sugarlab.org
+
you can use zenity for that
:only see shared activities NO Avitars
+
  try moving /usr/share/gdm/autostart/LoginWindow/gnome-session-check-accelerated.desktop somewhere else
::This may be a known bug in sugar 0.92.2 where the jabber gets overloaded with present and past Avitars from users. (I have seen >200 on screen) eventually only shared activities are displayed
+
  didn't know you needed anything additional for that.. was it always like that or did gnome 2 have that by default?
  http://bugs.sugarlabs.org/ticket/2845
+
maybe thats the seahorse/keyring integration, that stuff has changed quite a bit in 3.0
  http://bugs.sugarlabs.org/ticket/2897
+
but i thought you meant a more generic approach of showing dialogs from scripts
:::This does not occur in sugar 0.88.1
+
i'm actually doing the ssh-add from a process spawned by a pygtk app
*>Download IRC-10.xo from Browse Home (OLPC Activity Library/Activities -ASLO?)
+
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)
*Note: Failed to start on first try
+
worked!
: 15 sec grey until return to F3; works on 2nd try
+
do you somehow run gdm with a different driver or some weird setup like that?
*'''Activities only start on second try''' (get "failed to start" on first try)
+
so it's not possible to get the old behavior, and it needs some additional code to get it to work with seahorse/keyring?
: (This is related to a by a dbus timeout in Soasv4 and v5)
+
which distro is this?
: it takes about 15 seconds for a response.Including exiting an activity.
+
fedora 15 beta
:'''Suspect This delay with dbus timeout error seems to be related to jabber connection'''
+
i've tested the same code on fedora 14 and linuxmint (both gnome 2)
*Start IRC-10.xo: Failed to start on first try; works on 2nd
+
  when the ssh-add {key_path} process is spawned, the GUI dialog appears asking you to type in your passphrase
: #sugar and #sugar-es (Default)
+
ssh-add succeeds, and them the rest of the pygtk app continues
*Software Update
+
it doesn't even care whether the key is password protected or anything
  no updates found
+
i think there needs a daemon to be running that doesn't get started by fedora
:Activity Group:G1G1 Lite Activities for OLPC OS 11.2
+
this happens both in standard and fallback mode
::http://wiki.laptop.org/go/Activities/G1G1
+
try launching seahorse-daemon
===Test with jabber turned off===
  −
:Erase jabber entry in Networks
  −
:activities still require 2nd try but no 10 sec grey screen delay
  −
:'''Bug frame becomes stuck and will not retract''';
  −
*'''Shutdown;reboot'''
  −
:'''activities start on first try'''
  −
: Frame retracts correctly
  −
===http://dev.laptop.org/ticket/11031===
  −
:jabber.sugarlabs.org causes dbus errors and large delays in 0.92.x sugar when active
  −
::https://bugs.sugarlabs.org/ticket/2892
  −
::https://bugs.sugarlabs.org/ticket/2897
     −
===Activities===
  −
;key: *=not a favorite
  −
speak 25
  −
tamtamjam 56
  −
turtle art 27
  −
tamtamedit 55
  −
Labyrinth 11
  −
measure 32
  −
image viewer 17*
  −
browse 122.2
  −
words 4
  −
stopwatch 9
  −
write 74
  −
paint 34
  −
moon 12
  −
help 12
  −
clock 6
  −
chat 70
  −
tamtamsynthlab 55*
  −
wikipediaEN 26
  −
scratch 19
  −
memorize 36
  −
ruler 8
  −
get books 7
  −
distance 22
  −
log 24*
  −
infoslicer 9
  −
record 92
  −
wikipedia 26
  −
physics 8
  −
implode 10
  −
jukebox 21*
  −
terminal 31
  −
abacus 19
  −
pippy 40
  −
maze 9
  −
tamtammini 58
  −
calculate 37
  −
etoys 113
  −
helloworld 2*
  −
finance 3
  −
fototoon 7
  −
read 89*
  −
turtle art 107
     −
'''irc-10.xo''' (downloaded)
+
====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.
   −
==testing os871 on G1G1 XO-1==
+
====fix screensize in sugar-emulator====
*:07/01/2011 reflashed with USB
+
terminal:
===Retest:07/05/2011 reflashed with USB===  
+
su -
====Testing without jabber connection====
+
  (password)
::CP/network line blank
+
  gedit /usr/share/applications/sugar-emulator.desktop
*Browse starts on first try,,,
+
  edit line 6: Exec='''sugar-emulator -f'''
:Confirm that activities start on first try.
+
  (see [[Emulator/Full Screen|how to configure full screen]])
====Jabber Bugs====
+
save
  Incomplete display of jabber.sugarlabs.org Neighborhood
+
Logout
  https://bugs.sugarlabs.org/ticket/2897
+
login
Several Activities fail to launch in crowded jabber.sugarlabs.org Neighborhood
  −
  https://bugs.sugarlabs.org/ticket/2892
  −
jabber.sugarlabs.org causes dbus errors and large delays in 0.92.x sugar when active
  −
  http://dev.laptop.org/ticket/11031 (closed ericos see> 2892; 2897)
     −
===About my Computer===
+
====show desktop as icon in favorites====
  Build 871
+
  add programs install "alacarte"
  sugar 0.92.2
+
  open alacarte
  firmware q2e45
+
  make new
  wireless firmware 5.110.22.p23
+
  application
*note very slow response
+
command "nautilus Desktop"
*'''Activities only start on second try''' (get "failed to start" on first try)
+
save
: (This is related to a by a dbus timeout in Soasv4 and v5)
+
Run from applications
: it takes about 15 seconds for a response.Including exiting an activity.
+
Make favorite
   −
===Testing===
+
====key shortcuts====
*Connect to Apple Network Airport Extreme AP WEP ASCII
+
    * System (Windows) key: Switch between overview and desktop
*>Download IRC-10.xo from Browse Home (OLPC Activity Library/Activities -ASLO?)
+
    * Alt+F1: Switch between overview and desktop
:connects fine(on second try) to #sugar and #sugar-es(Default)  
+
    * Alt+F2: Pop up command dialog
*>Connected to Jabber.sugarlabs.org
+
    * Alt+Tab: Pop up window cycler
:only see shared activities NO Avitars
+
    * Alt+Shift+Tab: Cycle in reverse direction in the window cycler
::This may be a known bug in sugar 0.92.2 where the jabber gets overloaded with present and past Avitars from users. (I have seen >200 on screen) eventually only shared activities are displayed
+
    * Alt+`: Switch between windows of the same application in Alt+Tab
http://bugs.sugarlabs.org/ticket/2845
+
    * Ctrl+Alt+Tab: Pop up place cycler
http://bugs.sugarlabs.org/ticket/2897
+
    * Ctrl+Shift+Alt+R: Start and end screencast recording
:::This does not occur in sugar 0.88.1
+
    * Ctrl+Alt+D: Show desktop and raise windows back
===Activities===
+
    * Ctrl+Alt+Up/Down arrow: Switch between workspaces
no updates found
+
    * Ctrl+Alt+Shift+Up/Down arrow: Move the current window to a different workspace
:Activity Group:G1G1 Lite Activities for OLPC OS 11.2
+
Most keybindings can be viewed under the User Menu -> System Settings -> Keyboard -> Shortcuts
;key: *=not a favorite
+
 
speak 25
+
 
  tamtamjam 56
+
==== List of Autostart programs when starting gnome-shell====
tamtamedit 55
+
    ALT F2 gnome-session-properties
measure 32
+
 
image viewer 17*
+
====='''move intro screens that are too large for 800x600'''=====
browse 122.2
+
; alt+f7 and then the arrow keys
write 74
+
; alt+f8 Resize
paint 34
+
; shift and arrow keys
moon 12
+
:https://bugzilla.gnome.org/show_bug.cgi?id=262546
help 12
+
It's worth nothing, for Metacity >= 2.13.2, that if the window doesn't have a
  clock 6
+
minimum size hint larger than the screen then Metacity will now force such
chat 70
+
windows to be onscreen (by shrinking and moving them as necessary).  If the
tamtamsynthlab 55*
+
window has a minimum size hint larger than the screen, then the user can use
scratch 19
+
'''alt+left-click-and-drag (or alt+f7 and then the arrow keys) to move the window
memorize 36
+
upwards''' (including moving the titlebar offscreen) in order to get to the
ruler 8
+
forward button. Yeah, that's just a workaround for windows that are too large,
  jukebox 21*
+
but it may be helpful information for those waiting for the UI changes to make
  distance 22
+
the window usable on 800x600 resolutions. :)
  record 92
+
clip....
  implode 10
+
why not use a keyboard shortcut. the "next" button is marked "forward" so i hit '''alt + f''' and guess
  terminal 31*
+
what, i was able to successfully install the program.
  abacus 19
+
 
  pippy 40
+
====Reload shell ALT+F2 r  (reload)====
  maze 9
+
: use to recover Applications lists if they go missing and after alacarte edits
  tamtammini 58
+
 
  calculate 37
+
====http://live.gnome.org/GnomeShell/CheatSheet====
  etoys 113
+
:How to show user pictures on the GDM LOGIN screen
  helloworld 2*
+
::Click "my account" on the top panel lets me edit the picture, and
  log 24*
+
::adding a picture will show it on the GDM login screen.
fototoon 7
+
 
read 89*
+
If you hold down Alt, a 'Shut Down' option appears in place of suspend.
turtle art 107
+
 
'''irc-10.xo''' (downloaded)
+
====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.
 +
 
 +
====[http://sunglint.wordpress.com/2011/10/26/fedora-16-vs-macbook-pro-or-air/ 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.
60

edits