[xmir] System graphics slow majorily after logout/login

[David G.]

I am using Ubuntu 13.10 with the system compositor repos enabled and so I believe I have 0.0.15 installed. Logging out and choosing another user from the login screen (or the same previous login name) will render the system pretty useless. Drawing of graphics seems to be slow when this happens. One major issue is trying to click on the icons on the side bar. It opens very slow but then quickly wants to retract again. Bringing up programs takes an extremely long time after logging out/logging in. closing out or minimizing programs causes almost a "frame by frame" close out.

The system I am using is a Compaq DC5100 computer with Intel 910GL Graphics. This, again, only happens after logging out and then right back in...then the problems start. Let me know if you need me to run any other tests.
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: i386
DistroRelease: Ubuntu 13.10
GraphicsCard:
 Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:300d]
InstallationDate: Installed on 2013-10-19 (22 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MarkForUpload: True
Package: unity-system-compositor 0.0.1+13.10.20131015-0ubuntu1
PackageArchitecture: i386
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Tags: saucy
Uname: Linux 3.11.0-13-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
version.libdrm: libdrm2 2.4.46-1
version.lightdm: lightdm 1.8.4-0ubuntu1
version.mesa: libegl1-mesa-dev N/A

[Daniel van Vugt (vanvugt)]

Hi. It sounds like the problem is that your second login is falling back to software rendering. I imagine this might happen if something has crashed after logging out of the first.

Please run this command to collect more information about your system:
    apport-collect 1249513
Ideally, please run it from the slow login when the bug is happening.

Please also take a copy of:
    ~/.xession-errors
    /var/log/Xorg.?.log
and attach them here.

[Daniel van Vugt (vanvugt)]

P.S. I tried it for myself (on trusty) and can't reproduce the problem.

[David G. (djg9282)]

apport information

[David G. (djg9282)]

apport information

[David G. (djg9282)]

apport information

[David G. (djg9282)]

apport information

[David G. (djg9282)]

apport information

[David G. (djg9282)]

apport information

[David G. (djg9282)]

apport information

[David G. (djg9282)]

Xorg Log attached

[David G. (djg9282)]

Another xorg log

[David G. (djg9282)]

xsession log attached

[Daniel van Vugt (vanvugt)]

Hmm, the logs don't show anything going wrong.

It could still be compiz/unity7 falling back to software rendering incorrectly (which it has been known to do). This would not show up in the X or USC logs, but should be in .xsession-errors. However .xsession-errors is pretty empty compared to what it should look like.

Please run this command and attach the output here:
   pmap `pidof compiz` | grep _dri

Please also look in /var/crash/ for crash files. And if you find a relevant one, please turn it into a bug report by running:
   ubuntu-bug /var/crash/XXX.crash

[Daniel van Vugt (vanvugt)]

Again, please only run the commands from the slow login.

[David G. (djg9282)]

I ran the pmap command but it came up with "usage" instructions as if it didn't understand what I was asking it to do. Nothing relevant was found in the crash logs.

[David G. (djg9282)]

I don't know how accurate it is but system monitor is showing high cpu usage at idle. High being above 85% steadily. Idle under another session without the graphics problem is showing a high of 13%

[Daniel van Vugt (vanvugt)]

Yes the high CPU usage almost confirms you are stuck in software rendering mode. So that's expected.

Please try the pmap command again, remembering to use back-tick characters (next to the 1 key):
    pmap `pidof compiz` | grep _dri

Please also try to take another copy of .xsession-errors from during the slow session. Because that's the log which will explain the fallback to software rendering.

[David G. (djg9282)]

Output from the above command:

b4dae000 320K r-x-- /usr/lib/i386-linux-gnu/dri/i915_dri.so
b4dfe000 4K r---- /usr/lib/i386-linux-gnu/dri/i915_dri.so
b4dff000 4K rw--- /usr/lib/i386-linux-gnu/dri/i915_dri.so

The xsession log is showing the same output as the above attached one.

[Daniel van Vugt (vanvugt)]

Thanks. Was that command run _during_ the slow session? The "i915_dri.so" means you have hardware acceleration (!?)

[David G. (djg9282)]

Yes, it was done during the slow session.

[Daniel van Vugt (vanvugt)]

Trying to reproduce the issue on a netbook with i915 graphics, I find I can't even log out. It's not immediately obvious but the underlying reason is both compiz and unity-system-compositor crashing.

If you have any files in /var/crash then please report them using the "ubuntu-bug" command, and add a comment to this bug mentioning the newly created bug numbers.

[David G. (djg9282)]

It might take several logouts and logins to reproduce. On the desktop it usually took only one, but on a gateway mt6840 laptop with the same graphics I had to do it several times to reproduce. Since then I have put the laptop back to X but I'll try to go on the desktop tonight and check out the crash reports. Thanks.

[David G. (djg9282)]

I have done this multiple times now with the same result in slow graphics. There is nothing that appears in the crash folder for me to upload.

[Daniel van Vugt (vanvugt)]

Actually, this bug more likely resides in compiz/unity7 where the fallback to software rendering occurs.

[Christopher Townsend (townsend)]

This isn't relevant any more, so marking Invalid from a Unity7/Compiz perspective.

[Daniel van Vugt (vanvugt)]

Not sure what "isn't relevant". Setting to incomplete while we can't reproduce the problem, and/or see if it reoccurs for David.

[Launchpad Janitor (janitor)]

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Mir because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Compiz because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Unity because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for mir (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for XMir because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]