Talk:Opera: Difference between revisions
Sarah Elkins (talk | contribs) (→Quickstart: 404 on wget opera.activity file) |
|||
Line 85: | Line 85: | ||
Then when you're adding the New shortcuts, you must select Application first - I think. I muddle through it and it seems to be working... |
Then when you're adding the New shortcuts, you must select Application first - I think. I muddle through it and it seems to be working... |
||
== |
== Suggestions == |
||
For you guys and the Firefox2 folk - add the word "browser" to the keywords on this wikipage. I gather that many newer-to-open-source folks like me are having trouble finding these instructions because we don't know the NAMES of the possible alternative browsers. |
For you guys and the Firefox2 folk - add the word "browser" to the keywords on this wikipage. I gather that many newer-to-open-source folks like me are having trouble finding these instructions because we don't know the NAMES of the possible alternative browsers. |
||
Line 109: | Line 109: | ||
These instructions are slightly different from those on the wiki page I referenced earlier. The wiki instructions tell you to make a new Activities directory under /home/olpc. I tried that, and it didn't work for me, but installing the activity in /usr/share/activities worked fine. |
These instructions are slightly different from those on the wiki page I referenced earlier. The wiki instructions tell you to make a new Activities directory under /home/olpc. I tried that, and it didn't work for me, but installing the activity in /usr/share/activities worked fine. |
||
I mentioned a bug with the toolbar settings on the main page. I found the problem to be that the /etc/opera6rc file overrides all conflicting user prefs. So by removing the lines that are not neccesary for use on the XO (the DPI line is a must but the font might not be). |
Revision as of 10:50, 17 February 2008
- Is it possible to open a xterm window in sugar? alt+shift+F11 doesn't work for me. I am using olpc-devel 207 in a real X0.
- As recently noted in the B1 Release Notes, the latest builds are launching "Memphis" from alt+shift+F12 instead. Note that Memphis has bugs--it only seems to reliably launch the first time and it is not Sugarize, so you cannot run it with other activities very well, and it is very very slow. Let's hope that this is a temporary situation. --Walter 08:21, 5 January 2007 (EST)
- Probably the solution is to switch to a Linux console with the 12x22 font (framebuffer console), giving a 100x40 terminal. The next-best alternative is a full-screen genuine xterm, with a big font and the scrollbar enabled, possibly with a little helper app to do any Sugar-related work related to shutdown and activity switching. Nothing else is reliable and compatible. The xterm solution may be better done with a 600x450 screen resolution (divide down by 2x) and the programmer-friendly "fixed" font. AlbertCahalan 22:37, 23 February 2007 (EST)
Easy for the tech saavy, the rest of us need help
Re: "Installing Opera on test machines is easy. From a shell, run these commands as root"
Sorry to say I don't have a clue what the above means. I have no idea how to do it, but using Opera might mean I could possibly figure out how on earth to use the browser.
You can login as root by typing "su - root" at the command prompt, without the quotes.
- Please try the revised instructions here.
Quickstart
Well, for the most part the above means that you'll want to be fairly knowledgeable with Linux administration before you attempt it. Here's the gist, though:
- Open up a terminal window
- cd /tmp
- wget http://snapshot.opera.com/unix/olpc-544/opera-9.12-20070122.10-static-qt.i386-en.rpm
- rpm -vi opera-9.12-20070122.10-static-qt.i386-en.rpm
At this point you should be able to run the browser.
- wget http://people.opera.com/howcome/2007/olpc/opera-activity.tar.gz
- cd /usr/share/activities
- tar xvzf /tmp/opera-activity.tar.gz
Now restart sugar (ctl-alt-erase) and look for the Opera logo on your activity bar. Thither 07:04, 21 December 2007 (EST)
As of Feb. 1 2008, I'm getting a 404 Not Found on the wget ... opera-activity.tar.gz command. Sarah Elkins
Oh, brother, if that's the quick start, I'm in trouble.
- (new anon user) Do I understand correctly - open up terminal app and type that series of commands? Sounds simple enough. Whatcan go wrong that one would need to be a poweruser before attempting - warn me before I start -and is this only for test machines? Will this work on the lean green machine itself? I've never used linux before, but I am a former computer programmer, so the above doesn't scare me - I just wonder if something can go wrong I won't know how to fix.
Unable to get newest versions of java and flash to run
This may be expected since the build was frozen in time, but could not get Adobe Flash 9.0.115 to run properly in Opera, but 9.0.48 works fine. The same goes for java: jre-6u3 did not work (seems that it flashed up the applets briefly but then I was unable to interact with them), downgraded to jre1.5.0_13 and it works great. Should the page be updated to reflect this (or is this just my personal experience)? --bbb
This is a second confirmation that jre-6u3 does not work on the olpc. I wasted a half day on this. Will someone please update the Java and/or Opera pages to reflect this?
Java works, sort of
I got Java jre1.5.0_13 working under Opera (and Firefox), but there are two problems:
1) Font sizes can't be adjusted.
2) I can't figure out a way to make it usable with multiple windows.
The font sizes are tiny. I tried making adjustments in two ways (opera:config#UserPrefs|ForceDPI and setting the minimum font size in Tools->Preferences->Advanced->Fonts), but these only work with the browser, and not Java applets. I could buy reading glasses, but there's gotta be a better way....
But more importantly, pop-up windows take up the whole screen and can't be closed. I play bridge on yahoo, and there are buttons to look at the last trick, the last hand, the score, etc. When I click on one of these, it brings up the screen correctly, but it takes up the whole window and can't be closed. Once you view one of these screens, you can never get back to it again.
On a Windows desktop, these appear in small windows that can be viewed side-by-side, and can be closed with the Windows "X" button.
Does anyone have any ideas to solve these problems? If you go to games.yahoo.com/br and "Watch" a game, you can click on these buttons. Is there a better place to ask this question? Thanks in advance!
SOLUTION: The root of the problem #2 is that Sugar doesn't really have a window manager, so all windows appear full-size; there is no way to place windows side-by-side. So the solution is to use a different window manager, like the native X Windows manager. This may not be for the faint of heart... Unix experience helps.
Use Ctrl+Alt+F1 (where F1 is the first of the leftmost group of 4 keys on the top row, the neighborhood key) to get to a shell window. Login as root (no password). Then issue 'telinit 3' to kill Sugar. For some unknown reason (to me), this never returns, so use Ctrl+Alt+F2 (F2 is the group key) to get to another shell window. Login and enter 'startx' to start X11. X Windows should start; I got an xterm and xclock window. Now windows can be resized and placed side-by-side, closed, etc.
Help
I've used Opera since the early days when the program could fit on a 3.5" floppy, so I was very happy to hear that the browser would run on the XO. The problem is that I'm a complete Linux illiterate, so if there are any problems, I have no idea where things are going wrong.
I had no problems getting opera downloaded. When I tried Step #2. install Opera using rpm:, I get the following error message:
bash: sudo: command not found
Have I typed something incorrectly? BlankVerse 17:04, 23 December 2007 (EST)
- I don't have a Build 650 machine--maybe you need to use su instead on that software release. Try:
su rpm -iv opera...
Neither approach using either sudo or su work on my machine. My machine does recognize the sudo command at all and the listed use of su generates a syntax error (double checked the typing). What's next?
- I had to use
su -
for it to work, not just
su
--Tomhannen 16:09, 26 December 2007 (EST)
Setting Preference is unclear in these directions
It seems that there are a few skip steps in Setting the preferences. For instance, when you select the lower Edit button, you have to pick which Opera you're editing - UNIX or Standard. Then when you're adding the New shortcuts, you must select Application first - I think. I muddle through it and it seems to be working...
Suggestions
For you guys and the Firefox2 folk - add the word "browser" to the keywords on this wikipage. I gather that many newer-to-open-source folks like me are having trouble finding these instructions because we don't know the NAMES of the possible alternative browsers.
Also suggest you specify at the top of the Installing the Opera activity section whether you need to be in terminal with Su or not.User:KayTi
Also suggest you consider adding these alternate instructions for getting the Activity listed in the Activity list, courtesy of user: Grampa from the OLPCNews.com forums (copied with permission):
If you install the "activity" files, you will be able to start Opera by clicking an icon in the Sugar menu frame. To do this, go back to terminal and type the following commands:
cd /usr/share/activities wget http://people.opera.com/howcome/2007/olpc/opera-activity.tar.gz tar xvzf opera-activity.tar.gz
You MAY need to get into supervisor mode in order for these commands to work. Do this by entering the command "su" before entering the "wget" command above, and "exit to leave supervisor mode, i.e.,
cd /usr/share/activies su wget http:// ... tar ... exit
Then close Terminal and reboot Sugar by pressing alt-ctrl-erase.
These instructions are slightly different from those on the wiki page I referenced earlier. The wiki instructions tell you to make a new Activities directory under /home/olpc. I tried that, and it didn't work for me, but installing the activity in /usr/share/activities worked fine.
I mentioned a bug with the toolbar settings on the main page. I found the problem to be that the /etc/opera6rc file overrides all conflicting user prefs. So by removing the lines that are not neccesary for use on the XO (the DPI line is a must but the font might not be).