First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 219292
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Jeroen Roovers <jer@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jesús Pérez (Chuso) <chescu@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 219292 depends on: Show dependency tree
Show dependency graph
Bug 219292 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2008-04-25 20:54 0000
I updated from www-client/opera-9.2* (which, excluding Flash problem, worked
fine for me) to www-client/opera-9.50_beta1 (which is keyword-masked but not
package.mask masked).

The problem I found with 9.50 Beta 1 is that when typing an URL in the address
bar, when pops the autocompletion listbox, Opera increases its CPU usage
getting more than 90%.
I deleted ~/.opera and it worked fine at a first time. But after a few days
using Opera when I have visited many websited the problem reappeared, so I
suppose it's related to this new feature that searchs what you are typing in
the address bar through history and cache.

Then I updated to latest Beta 2 weeklie build available in Portage and the
problem seems fixed.

That's why I think www-client/opera-9.50_beta1 should be masked.

------- Comment #1 From Jeroen Roovers 2008-04-26 05:26:29 0000 -------
Er, try www-client/opera-9.50_beta2!

------- Comment #2 From Jesús Pérez (Chuso) 2008-04-26 12:16:58 0000 -------
(In reply to comment #1)
> Er, try www-client/opera-9.50_beta2!
> 

As you can read above:

"Then I updated to latest Beta 2 weeklie build available in Portage and the
problem seems fixed."

------- Comment #3 From Jeroen Roovers 2008-04-26 14:42:29 0000 -------
Oh, sorry. Hadn't read all of it yet.

I fail to see how users would miss the update when they sync their trees and
update the world target. A package manager shouldn't care whether or not beta1
is masked - it should automatically update to beta2.

But I will cut you a deal. I will simply remove beta1 from the tree - it's a
rather unstable snapshot and it lacks features compared to the latest beta2
snapshots.

Thanks for pointing me in this direction.

First Last Prev Next    No search results available      Search page      Enter new bug