[Bug 1629300] Re: Mouse pointer flickers after attaching external monitor

2016-10-22 Thread N8
Chiming in here, tried daily-live and am seeing the same flickering as in 16.04. root@fd3s:~# lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI

[Bug 1282867]

2014-02-26 Thread Oe-frepdesktoh-n8
I've been seeing the same glitches, starting when the updated mesa packages were pushed out on 2/20: http://ubuntuforums.org/showthread.php?t=2206883 At exactly the same time the glitches appeared, the primus bridge quit working for Bumblebee: https://github.com/amonakov/primus/issues/133

[Bug 1180646]

2014-02-26 Thread Oe-frepdesktoh-n8
Excellent! It appears this bug is fixed in Mesa 10.1 and later, and can finally be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL

[Bug 1180646]

2014-02-26 Thread Oe-frepdesktoh-n8
I also tested with edgers 10.2 packages, like k3mist, and it is still working perfectly. I too rebooted and checked multiple times that everything is good. I found other bugs with the current 10.1 packages in trusty, but they're not related to this issue. -- You received this bug notification

[Bug 1180646]

2014-02-26 Thread Oe-frepdesktoh-n8
Yes. :) I definitely made sure it was using OpenGL and that I was running it on my HD4000 and not the nVidia chipset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock

[Bug 1180646]

2014-02-19 Thread Oe-frepdesktoh-n8
I can hardly believe my eyes, but this bug appears to be FIXED under the current libraries in the Trusty beta. evil@clevo:~$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version

[Bug 1180646]

2013-11-27 Thread Oe-frepdesktoh-n8
Bug also occurs with Mesa 9.2.2, in Ubuntu 14.04 pre-alpha: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.2 OpenGL core profile shading language version string:

[Bug 1180646]

2013-10-22 Thread Oe-frepdesktoh-n8
Problem still occurs with Mesa 9.2.1 evil@clevo:~$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.1 OpenGL core profile shading language

[Bug 1180646]

2013-09-17 Thread Oe-frepdesktoh-n8
I can also recreate it at 9.2.0 (using Ubuntu 13.10 beta). Symptoms appear same as the original when using cairo-dock. - evil@clevo:~/src/clevokbledui$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI

[Bug 1180646]

2013-07-15 Thread Oe-frepdesktoh-n8
I've also been able to recreate this issue while running cairo-dock on a Clevo P150EM (Intel HD4000). I see the status is NEEDINFO. I've worked around the issue for myself by just using the cairo back end, but is there any info/testing I can provide to help resolve the issue when using OpenGL?

[Bug 521877]

2012-08-22 Thread Oe-freedesktop-n8
Please add an option (command-line or config file) to make the X server stop lying about the physical DPI of the display device. I understand all the arguments for pegging DPI at 96, but *I* still want my X server to report the actual DPI as read from the EDID. Maybe add an -autodpi command-line

[Bug 258348] Re: DOSEMU doesn't want to load my USB key ring

2009-06-08 Thread n8
I had the same problem (appears to be in the permissions for /dev/sdb1). Fixed it with: sudo chmod a+rwx /dev/sdb1 Good luck, n8 -- DOSEMU doesn't want to load my USB key ring https://bugs.launchpad.net/bugs/258348 You received this bug notification because you are a member of Ubuntu Bugs