PDA

View Full Version : Kernel 33-8 and Firefox-3.6.1-1 f13

SlowJet
5th March 2010, 10:15 PM
I downgraded from kernel 34 to the latest 33 kernel.
Aside from adding xorg-x11-server and qt-x11 all was well for one session, a few re-boots.
But now, after using the browser for a bit it is garbaged up with the red and blue boarders on half of all the blue borders (for this site)

I have these errors in the error console.
Anyone getting garbaged screens from this new kernel on Fx?

Error: [Exception... "update.locale file doesn't exist in either the XCurProcD or GreD directories" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: file:///usr/lib/xulrunner-1.9.2/components/nsUpdateService.js :: getLocale :: line 413" data: no]
Source File: file:///usr/lib/xulrunner-1.9.2/components/nsUpdateService.js
Line: 413

Warning: Found unclosed string ''*8@0RP*I *qzZ*Կ쬓CUξy34y+pz B4{fX灣?*{|u2|' . Found unclosed string '"'.
Source File: http://forums.fedoraforum.org/clientscript/vbulletin_important.css?v=381
Line: 2

I also updated java-1.6.0-openjdk

SJ
leigh123linux
5th March 2010, 10:24 PM
It works OK here


[leigh@localhost ~]$ rpm -qa |grep -e firefox -e xulrunner -e Xorg -e kernel -e java -e jre |sort
abrt-addon-kerneloops-1.0.8-1.fc14.x86_64
buildsys-build-rpmfusion-kerneldevpkgs-current-13-0.1.x86_64
firefox-3.6.1-2.fc14.x86_64
java-1.5.0-gcj-1.5.0.0-30.fc13.x86_64
java_cup-0.11a-4.fc13.noarch
jre-1.6.0_18-fcs.x86_64
kernel-2.6.33-1.fc13.x86_64
kernel-2.6.34-0.4.rc0.git2.fc14.x86_64
kernel-devel-2.6.33-1.fc13.x86_64
kernel-devel-2.6.34-0.4.rc0.git2.fc14.x86_64
kernel-headers-2.6.34-0.4.rc0.git2.fc14.x86_64
xorg-x11-server-Xorg-1.7.99.901-10.20100304.fc14.x86_64
xulrunner-1.9.2.1-3.fc14.x86_64
xulrunner-devel-1.9.2.1-3.fc14.x86_64
[leigh@localhost ~]$ uname -r
2.6.34-0.4.rc0.git2.fc14.x86_64
[leigh@localhost ~]$
SlowJet
5th March 2010, 11:27 PM

I'm on f13.
Can't see anything there that different except the kernel.
I'll try some more updates.

SJ

---------- Post added at 03:27 PM CST ---------- Previous post was at 02:52 PM CST ----------

33-8 and 34 is working again.
It was the WinProxy cache messed up on the gateway..

SJ