Slackware :: Opera 10.60 Very Slow To Start New Links
Jul 8, 2010
I've been using Opera 10.11 on two different computer systems, two different locations (work & home), and two different Slackware versions (13 & 13.1 current). Opera 10.11 runs very quickly on both. After upgrading to Opera 10.60, I now find that linking to new web pages takes 5 to 10 seconds, but returning to a previous page is almost instantaneous.
I've tried installing 10.60 using slackbuilds and Opera's installer - both give the same results. I've since reverted to Opera 10.11. why it is so slow to open web pages? Opera 10.60 for Win7 works great, so what happened to the Linux version?
I am using Opera 10.60 browser for the past one month. Generally it use to take about 20 seconds to startup but since yesterday its taking more than 40. I don't know about the exact duration but certainly its taking a lot of time now.
i got 2xgtx280 and 2 x xeon 5650 transparency and shadows work ok but i have little problem when windows mannager starts(fluxbox) when i click first on for exemple firefox windows its moving slow for 4 sec after that is ok and if i dont use that window for 2 min and i wanna use it again its slow again for couple seconds how can avoid this? i was trying alot xorg.cnf settings and xcompmgr and nothing changes...
I'm on ubuntu 10.04 32-bit desktop. Somehow Opera 10.60 is very slow to load. I just switched from FF to Opera, and (I'm pretty sure, might be dreaming though) that the first few days it was lightning fast.. and now it takes like 10+ secs to load any page.
I installed Opera 11 a couple of days ago and it is incredibly slow. After entering a url it just sits there with "Document 0%" in the location bar for thirty seconds to a minute, then renders relatively fast. I've gone back to both version 9.xx and 10.63 and they are both faster.
1. My Ubuntu 9.10 Karmic Koala always going slow when i Open OPERA Browser. Is it Normal? 2. Sometimes i got my Karmic Animation like a... i dont know, just play it slower than usual. Is it Normal?
I was using Compiz Animation. [minimize, maximize, close, etc] Is that thing make my Karmic running slow?
opera-11.11-2109.i386.rpm From opera's webpage. Installed with double-click. Asked for root permissions... the standard way of installing. Neither CLI 'opera' nor the GUI's menu -> internet -> opera does anything!
After upgrading to v10.60, Opera will not run from the KDE menu. A entry appears in the taskbar and then disappears without opening any window. The entry for Opera in KDE menu has this command:
Code: /usr/bin/opera %u
If I open a terminal and type "opera" or navigate to /usr/bin and click on the opera script there, it starts up just fine. Seems like it should be simple to fix, but I have tried various entries in the KDE menu ("opera", "opera %u", "/usr/bin/opera") and this same behavior occurs with any of them.
I've been messing around with Slackware 13.1 and I screwed something up. I was trying to get Wicd to start automatically at startup so I found a chmod... line of code online and copy/pasted it on my command line. Now whenever I boot the computer, when I get to the KDE desktop, the BASH window opens, Opera opens and I get a bunch of Wicd error windows. How can I fix this?
Support for ipv6 keeps being put into the kernel and now into browsers.I blacklisted ipv6 in Slackware and that solved the slow internet response until I updated to the latest Opera and Firefox browsers. Both were horribly slow again. Firefox could be reconfigured to kill ipv6 by running about:config as a url and disabling ipv6.
The new Opera 11 is different. I can't find any config to disable ipv6. Does anyone have an idea?I reverted to Opera 10.11 in order to have zippy internet access again, and not "dialup modem" speeds.
on a fresh install of slackware -current x64, the first thing that i did was download and install opera. now, whenever i start kde, and run opera, X crashes with lots of crazy errors, usually in the format of:
/usr/bin/akonadi*whatever* cannot connect to x server :0 /usr/bin/akonadi*whatever* has crashed too many times and will not be restarted.
and then i get spat back out at the CLI. opera works fine in the other Desktop Environments, and i'm posting from xfce right now, so i know its an issue with akonadi. i would like to use KDE as my default desktop, but i dont want to use it without all of its features
I did a clean install of Ubuntu 11.04 64bit and the start up time is abnormally slow. If I start up the computer and don't press anything, the start up time is 30 minutes but it usually doesn't start up at all. It just boots into a purple screen, no splash, then it sits there and the computer doesn't have any loading lights flashing.
I had a similar problem with 10.10, but I assumed it would go away when I did a clean install of 11.04.
I can't get a read out of what's going wrong because when I press Esc it doesn't display anything, though weirdly it can sometimes get the start up process moving. I have also found that pressing enter really fast can sometimes help and something that seems completely oxymoronic, if I press the power button while it's starting up that can make it work, but nothing works every time.
So, approx 2 weeks ago, clicking on links in Thunderbird stopped working. There is no response in the browser whether it is open or not. I am able to paste the links to the browser just fine. Being congenitally lazy, I would rather just click them. I have upgraded to the latest version of Thunderbird and have the same issue. I have tried using Swiftfox, Firefox and Opera - all give the same non-response.
Am not getting any error messages, the links just do not open. Can't find any settings relevant to this issue.Any bright ideas out there?
auto generated doinst.sh files when using the -A switch.
The file will contain link removal and generation for libraries in the package eg.
When upgrading to a new version of the app, the library name might change eg.
So the links that doinst.sh creates is now incorrect. ie. the link is now dead because it points to a file that does not exist. Does one have to regenerate .src2pkg and resulting doinst.sh when using a new version of the package or is there another way to have doinst.sh regenerated without redoing .src2pkg?
I am using slackware64-current. I have installed the package links-2.3pre1-x86_64-1 and I love it. I launch it from the command line with the "links -g" switch and it can display pictures, it's great, but it doesn't seem to support ssl connections.
Am i doing something wrong or do I need another build? I know that in the past there used to be two different binaries, is it still so? Where can I find a ssl-enabled binary for 64 bit without need to recompile?
At my Uni, we use a web-based login for our internet connections. Its based off of Cisco, and every Wednesday night every computer on campus must re-enter their credentials to use the network.
Normally on my several computers I simply pull up the Terminal, point links to google.com using
Code:
And enter my credentials when Cisco redirects to the login page.
Literally, the process is
Code:
Then ENTER to accept the redirect, down arrow to skip over the logo image, USERNAME, ENTER, PASSWORD, ENTER, ENTER.
Naturally, this is EXTREMELY time consuming, as I have about 5 computers located around campus and must physically walk to the machines and login every single week.
My question is, How would I formulate a program that does the following;
1) checks for connectivity (i.e. is able to reach/resolve to the greater part of the internet) and
2) automatically fills in the credentials on the links login page?
I have a personal wiki of notes, with now thousands of links in markdown format:
[link text](http://example.com)
but now that fckeditor is available for mediawiki (very beta), it has become much better to just stick with wikitext format. There are only a few conversions to do: tables, links, and bulleted lists. The lists are a fairly simple regex and fckeditor magically reformats the tables, so all I'm left with is the links. But I'm not a regex master. How do I reformat code...
My recent borked upgrade to -current inspired me to try to come up with a way to sanity-check the lib and bin dirs for broken library symlinks (possibly indicating missing libs) and for binaries and libraries that belong to no installed package, as well as missing dependencies.
This script is the result.
I've checked the script results manually, and it appears to be accurate, so I figured I'd post it here for a second opinion, and/or because others may find it useful too. I'm not aware of another popular method of doing this on Slackware, so here it is:
I have an Intel Celeron 2.80 Ghz processor, 1GB RAM, GeForce 8400 512MB video card running Ubuntu 10.04.When I open VLC it takes 15 to 20 seconds to open. I just setup another computer: Pentium III 1.1Ghz with 256MB of RAM with Crunchbang Lite, and VLC opens in less than a second. No problem with VLC on my computer at home.
I have tried uninstalling and reinstalling VLC but no change.No errors from the command line.What could cause VLC to open slowly on only one computer?
I have had an extremely slow startup (upwards of a few minutes) for awhile now, and nothing seems to work to fix it. Regular boot time is far slower than it should be, and the time of logging in to a workable desktop is just really bad. I will log in, and then I will either get a blank desktop screen for awhile or an all black screen until the desktop will fully load with errors from gnome-panel and AWN not starting up automatically.Some of the fixes I have tried:
Disabling floppy from bios
Downgrading gnome keyring
Removing gnome* and gconf* from the home directory
Putting this script in /etc/init.d #!/bin/sh echo "nameserver 0.0.0.0" > /etc/resolv.conf
Here's my bootchart and a link in case the upload has problems http:[url].....
Whenever I start a text editor, such as kate, kwrite, gedit, it takes at least 10 seconds to start up.This on a PC with 4 cores and 3GB RAM.I know that these text editors should start up much faster, like, I click the launch icon and it should already by there.But instead it's 10 seconds waiting and then the editor is there. Why, what's it doing during those 10 seconds, and most important, how can I fix this?
Since upgrading from Heron to Lynx (64 bit) Gnome is slow to start. It seems like it is waiting for some sort of automated timeout, since the harddrive stops in the middle of Gnome startup (after login) for around 10 secs or so. Is there a logfile of the startup-sequence somewhere that I could look at and/or post here?
I switched to Ubuntu from Windows a few months ago and have had it all working fine since.
I turned on my system today and did some updates, then restarted but after the boot selection screen which I cant use as I have a USB keyboard the screen went to that purple/pink colour and froze for ages. Eventually my desktop appeared so I tried restarting it again and the same thing happened. Before from the boot selection to my desktop would only take 5 seconds or so but now it takes about 3 minutes.
Also since the updates I can't connect to my wireless network. I was using the Windows Wireless Networks software from the Ubuntu Software Centre, now when I try opening it manually it just hangs. I tried removing it and reinstalling it but still no joy.
I may have been too trusting with the updates so didn't read the list, I just updated and restarted and thats when the problems started.
I'm not quite sure what information you need but here are the bits from the System Monitor:
Release 11.04(natty) Kernel Linux 2.6.38-8-generic GNOME 2.32.1
On windows I would have considered myself an intermediate user but since switching to Ubuntu I feel like a beginner again although im learning fast.
The new release of Opera 10.60 doesn't recognize the -notrayicon option anymore. If you had this option in your menu, then Opera doesn't start anymore and dies silently. You won't get an error message, and this error can keep you quite puzzled.
The solution is to remove the -notrayicon option from the menu entry. In opera, go to opera:conf and find the "notrayicon" option and disable it.
The nfs-client service isn't starting after boot up. This is causing problems with the user as they cannot access the remote folders on the server. The PC is a Thinkpad X60s with oS11.3 and KDE4.4.4. The problem started about a week ago after some updates (new kernel update, kde4 updates and some system files) were applied on the laptop.
After logging in none of the remote folders are available. Checking the nfs-client service under Yast>System Services (Runlevel) shows the nfs-client service is not running. If I enable and start the service I get the pop-up confirming the service has started but still cannot access the remote folders even after issuing a mount -a. Opening Dolphin just opens a blank grey window which needs to be terminated.
Trying to restart the nfs service using su -c 'rcnfs restart' sticks at Starting NFS client services: sm-notify Just leaving the PC for 10-15mins eventually sorts itself out and the remote folders become visible. I cannot see anything obvious in the logs so am a bit stumped.
I don't think any changes have been made to my laptop, but it suddenly loads Ubuntu extremely slowly. The time it takes to get from the Toshiba boot screen to the Ubuntu Log-in screen takes easily 20x as long.
Has anyone else been experiencing this kind of lag or have any ideas where to begin?
I changed the host name on this CentOS 5.5 machine but whenever I reboot the machine the startup pauses at the point of starting sendmail for several minutes and then eventually moves on. What could be causing this?
I'm gonna tell you about slackware installation on my notebook, an acer travelmate 800lci.
On this notebook, I successfully installed (and work with) slackware from version 10.0 till the recent 13.0. Upgrading to a new version till using a new internal hard disk (from 40 GB to 160 GB). After upgrade I fully reinstall slackware 12.2 and then upgrade to 13.0.
Now, I had to use the notebook for testing, so I made a new full installation of slackware 13.0 and after some time a new full installation of slackware 13.1.
On this disk (160 GB P-ATA) I have to pass the following parameter to the kernel:
during installation and boot.
This operation solve the issue that can "see" the full size of the disk (160 GB) and not the 137 GB limit.
Only using slackware 13.1, occur a big (for me) problem.
I can fully reproduce it opening any pdf document with xpdf: moving into document with arrow keys make the cpu goes to 100% and page "fault/s" goes from 30 to 8000 and some times 15000 "fault/s". So, xpdf becomes unusable. This problem reflects in similar manner to other software, like firefox.
Here is my question: what type of analisys could I try to solve/analyze this issue? Maybe the kernel, xorg?
