1

This is my Chromium version string:

 32.0.1700.107 (Developer Build 32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1) Ubuntu 13.10

I am having issues with pages loading. Immediately after opening the browser, pages do not load. All I get is the title, with a blank page.

The request is going through; that's not the issue. I can inspect the headers, etc.

This leads me to believe it is some sort of rendering issue. After opening a couple of tabs and loading a couple of other pages, the pages start to actually display.

This happens almost every single Chromium startup. It affects the first few tabs open/pages "loaded" (usually by the 5th they render).

enter image description here enter image description here

What could be the issue?

EDIT

Alright, we're in business! I ran chromium-browser from the terminal and the first three tabs gave this message:

libGL error: open uki failed (Operation not permitted)
libGL error: reverting to (slow) indirect rendering

Subsequent tabs (i.e. the ones that actually rendered) did not print any error message.

Now, what does this message mean?

Edit 2

Output of inxi -G:

Graphics:  Card: Advanced Micro Devices [AMD/ATI] Wrestler [Radeon HD 6310] 
           X.Org: 1.14.5 drivers: ati,fglrx (unloaded: fbdev,vesa,radeon) Resolution: 1366x768@60.0hz 
           GLX Renderer: AMD Radeon HD 6310 Graphics GLX Version: 4.2.12337 - CPC 13.101

I feel like it may be an issue with the ATI fglrx drivers.

Aristides
  • 437
  • 1
  • 5
  • 15
  • Do you get any error messages if you start chromium from a terminal? They might be informative. – terdon Mar 16 '14 at 16:42
  • @terdon see updated answer above – Aristides Mar 16 '14 at 16:49
  • Hmm, graphics card and driver info please. If you don't have it already, install inxi and run inxi -G. – terdon Mar 16 '14 at 16:51
  • @terdon See updated answer above for output of inxi -G. – Aristides Mar 16 '14 at 16:55
  • OK, you're using the proprietary drivers, see if there's a newer version of the driver here (kai to'svhsa gia na mhn mas kraxoun :). – terdon Mar 16 '14 at 17:02
  • @terdon OK, I can update n.10 to n.12, which I am doing now. – Aristides Mar 16 '14 at 17:14
  • @terdon Well, using the open-source drivers mitigates the issue. I will try reinstalling the proprietary drivers again, but if it does not fix the problem I can simply stick with the open-source ones. – Aristides Mar 16 '14 at 17:28
  • Cool, please consider writing an answer explaining what you did and accepting it. It will get you some rep and help future visitors. – terdon Mar 16 '14 at 17:31
  • Alright, I'm using the proprietary driver again. It still gives me the LibGL error, but it actually renders the content. Will do for the answer – Aristides Mar 16 '14 at 17:34
  • You might also be able to use the --disable-gpu flag with the proprietary drivers, but some things may be slower. – saiarcot895 Mar 17 '14 at 12:20
  • @saiaroct895 Interesting. But how is it explained that every single time it was exactly for the first three requests that the error came up, then everything worked fine? I ended up just using the open-source drivers. – Aristides Mar 17 '14 at 15:05
  • Almost a week later, still not resolved. – Aristides Mar 23 '14 at 18:49

0 Answers0