Bug 42219

Here is screenshot:
http://imageshack.us/photo/my-images/851/screenshot121011215421.png/

This is likely from the intel driver bump or the server bump.  Can you please 
narrow down which of the two is responsible.

Thanks for help.

Which log should i post it?

I have installed xf86-video-intel-git and the problem still persist. It looks like the problem is in xorg-server package.

I don't see how you come to the conclusion that the problem persisting with xf86-video-intel-git indicates that it is a bug in xorg-server.  It's possible that the bug is in the intel drivers and just not fixed in git.  You need to test the following two combinations:

xorg-server-1.10.4 with xf86-video-intel-2.16.0
xorg-server-1.11.1 with xf86-video-intel-2.15.0

Created attachment 52805 [details]
Xlog - using xf86-video-intel-2.15

Created attachment 52806 [details]
Xlog - using xf86-video-intel-2.16

Sorry for fast conclusions.

Following your instructions i couldn't start X session (i start session with startx) with neither option. Firstly, i downgraded xorg-server, xorg-server-common and xf86-input-evdev (i have to downgrade this last package too because it was dependency issue) and leave xf86-video-intel-2.16.0. (Attachment file intel_2.16.txt).

Then i upgraded to the newest packages and downgraded just xf86-video-intel. (Attachment file intel_2.15.txt).

As i have allready said - i couldn't start the sessions. Hope the logs will be helpfull.


(In reply to comment #5)
> I don't see how you come to the conclusion that the problem persisting with
> xf86-video-intel-git indicates that it is a bug in xorg-server.  It's possible
> that the bug is in the intel drivers and just not fixed in git.  You need to
> test the following two combinations:
> 
> xorg-server-1.10.4 with xf86-video-intel-2.16.0
> xorg-server-1.11.1 with xf86-video-intel-2.15.0

No, those aren't helpful.  That's just the console messages and not the actual logs.  My guess is that your problem is that you can't start the server due to conflicting ABI versions between the server and drivers.  You need to rebuild the drivers when you change the server version.  You seem to be using binary packages.  Please either build from source, or report this problem to you distribution which will be in a better position to help you with their packaging system.

I can now start a session with downgrading just xf86-video-intel but the problem persist. I couldn't manage to start session with downgrading xorg-server, xorg-server-common and leave the newest version of xf86-video-inte-2.16.0. In this case console gives me the same message as i posted it before in my attachment file. I have tried to compile from source xorg-server-1.10.4 without patches but no luck. I get this error that there is a missing driver. 

Could we now conclude that the problem is xorg-server?

(In reply to comment #9)
> No, those aren't helpful.  That's just the console messages and not the actual
> logs.  My guess is that your problem is that you can't start the server due to
> conflicting ABI versions between the server and drivers.  You need to rebuild
> the drivers when you change the server version.  You seem to be using binary
> packages.  Please either build from source, or report this problem to you
> distribution which will be in a better position to help you with their
> packaging system.

The console messages aren't particularly useful.  You need to provide /var/log/Xorg.###.log

As I mentioned, you need to rebuild all your drivers when you change server versions.

Please attach your log.  Given what you said above, it sounds like this might be a regression in composite.

Ville, can you take a look at this?

Created attachment 52827 [details]
Xorg log for intel 2.16

xorg-server = 1.10.4
Xf86-video-intel = 2.16

I have rebuild both packages.

Created attachment 52828 [details]
Xorg log for intel 2.15

xorg-server = 1.11.1.901
xf86-video-intel = 2.15

Both are rebuilt.

If i enable in compiz (ccsm) transparency for tooltips the problem disappears.

You haven't really answered the questions I've asked, so I will be explicit

Using xorg-server-1.10.4 with intel-2.15.0, does it work?
Yes, per first comment.

Using xorg-server-1.10.4 with intel-2.16.0, does it work?
You provided the logs but did not answer this question.

Using xorg-server-1.11.2 with intel-2.15.0, does it work?
You provided the logs but did not answer this question.

Using xorg-server-1.11.2 with intel-2.16.0, does it work?
No, per first comment.

Hello!

I am really sorry i wasn't lucid and clear. I can hardly read my comments :)

Here is my answers:

Using xorg-server-1.10.4 with intel-2.15.0, does it work?
Yes, it is working. Problem goes away.

Using xorg-server-1.10.4 with intel-2.16.0, does it work?
It's not working. Can't start the session.

Using xorg-server-1.11.2 with intel-2.15.0, does it work?
It's not working. Can't start the session.

Using xorg-server-1.11.2 with intel-2.16.0, does it work?
I can start the session, but the problem persist.

It is interesting that when i use oxygen-gtk theme the problem goes away.

I hope it helps. The problem still persist with xf86-video-intel-2.17.0 but not if i use oxygen-gtk theme.

Your last statement is consistent with this being a composite issue, but we need to know if it is in the server or in the driver.  You NEED to answer these two questions:


Using xorg-server-1.10.4 with intel-2.16.0, does it work?
Using xorg-server-1.11.2 with intel-2.15.0, does it work?

Your "can't start the session." response is insufficient.  You need to test this bug.  As I have mentioned before, you need to rebuild your drivers when you change servers, so install 1.10.4, then *BUILD* 2.16 and test it.  Then install 1.11.2 and *BUILD* 2.15 to test it.

You will also need to make sure that your other (input) drivers match the server you are running.

You cannot expect a random binary driver package to work on a random server.  They are tied together.

Created attachment 54884 [details]
Running xorg 1.10 and intel driver 2.16.0

-I have installed xorg-server 1.10.4 and compiled xf86-video-intel 2.16.0 but this doesn't work. I posted the output. It's something about ABI versions.

-When installing xorg-server 1.11.1 and compiled intel's 2.15.0 version i have managed to start the session but the problem persist with blank/transparent tooltips

(In reply to comment #19)
> -I have installed xorg-server 1.10.4 and compiled xf86-video-intel 2.16.0 but
> this doesn't work. I posted the output. It's something about ABI versions.

[113046.780] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[113046.780] (II) Module intel: vendor="X.Org Foundation"
[113046.780] 	compiled for 1.11.3, module version = 2.16.0
[113046.780] 	Module class: X.Org Video Driver
[113046.780] 	ABI class: X.Org Video Driver, version 11.0
[113046.780] (EE) module ABI major version (11) doesn't match the server's version (10)

You are trying to use an intel driver built for 1.11.x rather than for 1.10.x
 
> -When installing xorg-server 1.11.1 and compiled intel's 2.15.0 version i have
> managed to start the session but the problem persist with blank/transparent
> tooltips

Ok, so this looks like a server issue rather than a driver issue.

I hope i helped you. Weird thing is that if i use KDE the problem almost vanish, meaning, that after a really short period of time, let's say milisecond, tooltips and menus come to normal (it's almost unnoticable). But if i use XFCE with compiz the problem persist.

(in KDE i use Kwin with OpenGL)

Created attachment 65243 [details]
log of xorg-server-1.10.6 + xf86-video-intel-2.20.2

I would like to add some information as I have the same problem.  It seems that this is indeed a server issue.  I tested the following four combinations:

  - xorg-server-1.10.6 + xf86-video-intel-2.15.0 : works
  - xorg-server-1.10.6 + xf86-video-intel-2.20.2 : works
  - xorg-server-1.12.3 + xf86-video-intel-2.15.0 : does not work
  - xorg-server-1.12.3 + xf86-video-intel-2.20.2 : does not work

Let me attach Xorg.0.log for the second case so that you can see my hardware configuration.

It's been six years, both intel and xserver have changed significantly. Please reopen if you still experience this issue with current releases.