[Touch-packages] [Bug 1364867] Re: glxgears and other full screen OpenGL applications freeze after a couple of minutes of running

2015-04-27 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1364867] Re: glxgears and other full screen OpenGL applications freeze after a couple of minutes of running

2015-02-26 Thread Christopher M. Penalver
Krisztián Tresó, thank you for reporting this bug to Ubuntu. 12.04.3 reached EOL on August, 2014. For more on this, please see https://wiki.ubuntu.com/Kernel/LTSEnablementStack and https://wiki.ubuntu.com/Releases . Is this an issue on a supported release? If so, please run the following

[Touch-packages] [Bug 1364867] Re: glxgears and other full screen OpenGL applications freeze after a couple of minutes of running

2014-09-10 Thread Krisztián Tresó
Forcing Xorg to ignore the secondary VGA monitor on the mainboard seems so far to solve the problem. Applied testing method: running glxgears in full screen for 2 days. See the attachment called xorg.conf.disable_VGA_works ** Attachment added: xorg.conf.disable_VGA_works

[Touch-packages] [Bug 1364867] Re: glxgears and other full screen OpenGL applications freeze after a couple of minutes of running

2014-09-03 Thread Krisztián Tresó
** Attachment added: dmesg-boot.txt https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1364867/+attachment/4194152/+files/dmesg-boot.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1364867] Re: glxgears and other full screen OpenGL applications freeze after a couple of minutes of running

2014-09-03 Thread Krisztián Tresó
** Description changed: OpenGL applications started in full screen mode freeze after a couple, mostly within 5 minutes of running, rarely after hours. With my configuration, the bug is easily reproducible, especially with kernel version linux-image-3.8.0-44-generic