idk why but the formatting when replying or starting new topic is fucked with Chromium browser under fedora 19. it will not space anything correctly just runs it all together
Printable View
idk why but the formatting when replying or starting new topic is fucked with Chromium browser under fedora 19. it will not space anything correctly just runs it all together
I gave up on Google's browser long ago because of stuff like this. Firefox has numerous faults but it's still the best out there right now.
yeah id be using firefox now, but since fedora 18 all firefox will do when launched is pixilate the screen hard lockup.
Chromium or Google Chrome? They are two separate products, and it would be helpful to know.
Chromium
not sure that google's chrome is available for linux platforms.Quote:
Originally Posted by W2IBC
http://en.wikipedia.org/wiki/Chromium_(web_browser)Quote:
Originally Posted by n6hcm
Huh ??? I'm using Fedora 19 (64 bit) and Firefox, Opera, and Chrome all work great. I mostly use Opera but Firefox also runs great on F19. Did you try running strace or running it under gdb to get some info as to why it balks.Quote:
Originally Posted by W2IBC
P.S. I presume you built chromium from source ? Did you have any issues during the build ?
chrome has been available under linux for a very long time. Chromium (the browser) can be built to run on Linux.Quote:
Originally Posted by n6hcm
I always thought fedora chromium was a fancy name for a tinfoil hat. Who Gnu?
Try Google Chrome, and report back.Quote:
Originally Posted by W2IBC
That should give a clue since chrome is a subset of chromium.Quote:
Originally Posted by KC2UGV
got chromium from repo......as for the firefox problem no matter what I do to try and track the issue, as soon as FF is "clicked" to run screen pixalates, hard lockup nothing gets saved. i just gave up on FF and moved to other things.Quote:
Originally Posted by n2ize
test with opera
test
test
opera spaces correctly, so its a chromium issue.
It's strange though. Just curious is it running on a 64 but system or an older 32 bit system and is the Fedora version FC19-64 or FC19-32 ? I tried but I can't seem to recreate the problem here.Quote:
Originally Posted by W2IBC
32Installed fedora on a neighbors laptop today, tried it on there and it works fine. so hard telling what it is.. I know it started with F18Quote:
Originally Posted by n2ize
Quote:
Originally Posted by W2IBC
Interesting. If you figure it out please let me know what causes the problem. Good to know in the event I ever come across the same problem. Do you think it might be a hardware related issue ?
yeah I am thinking its hardware related, odd though since I am not running any super special hardware just basic off the shelf crap. after F20 is out about a month or two ill upgrade to 20 and see if the problem remains.Quote:
Originally Posted by n2ize
UPDATE - well I installed F20 LXDE fresh, and FireF works like it should. no lockup. so evidently it was fixed in 20Quote:
Originally Posted by n2ize