[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2017-06-06 Thread LocutusOfBorg
*** This bug is a duplicate of bug 1647600 *** https://bugs.launchpad.net/bugs/1647600 can you please test libepoxy from my ppa? https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa please report back results on bug:

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2017-05-16 Thread Mathew Hodson
*** This bug is a duplicate of bug 1647600 *** https://bugs.launchpad.net/bugs/1647600 ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1574886 Title: All gtk

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2017-05-16 Thread Raj Bhattacharjea
For future users, I installed libepoxy0 (1.3.1-1ubuntu1) from zesty manually by downloading the right deb for my architecture (https://packages.ubuntu.com/zesty/libs/libepoxy0), and then installing with "dpkg -i". It seems that the newer package in zesty has a fix for the underlying bug. It

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2017-05-03 Thread Raj Bhattacharjea
What's the recommended way to get the updated version of libepoxy on xenial (16.04)? It appears that yakkety and zesty both have version 1.3.1 of libepoxy, but zesty's version number is "1.3.1-1ubuntu1" while xenial and yakkety both have "1.3.1-1", so I'm hopeful the zesty libepoxy package has had

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2017-02-24 Thread Torbjörn Lönnemark
On February 6 upstream released 1.4.0 which contains the fix: https://github.com/anholt/libepoxy/releases/tag/v1.4 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1574886 Title: All gtk

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2017-01-31 Thread Björn Torkelsson
Looks like they have finally fixed it upstream: https://github.com/anholt/libepoxy/issues/72#issuecomment-276045967 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1574886 Title: All gtk

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2017-01-04 Thread Ken Adams
should NVidia's drivers be making that link as well, anyway? I realize it isn't the prime cause... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1574886 Title: All gtk applications

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-11-29 Thread Niklas Edmundsson
Upstream bug/discussion: https://github.com/anholt/libepoxy/issues/72 Main issue seems to be libepoxy having been unmaintained for some time, but this issue is showing up in other distros as well so will have to be fixed sooner or later. Patch is trivial, bug/crash is due to passing on a pointer

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-09-29 Thread Kirk Gremillion
I also want to confirm that this link solution works for me! (I have a Nvidia GT610 with prop drivers also.) sudo ln -s /usr/lib/nvidia-361/libGLX_nvidia.so.361.42 /usr/lib/x86_64 -linux-gnu/libGLX_indirect.so.0 Couldn't for the life of me figure out why apps worked on the console, but not via

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-08-23 Thread b
I confirm that the symlink workaround solves the issue for me also. I ended up using this: sudo ln -s /usr/lib/nvidia-361/libGLX_nvidia.so.361.42 /usr/lib/x86_64 -linux-gnu/libGLX_indirect.so.0 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-08-02 Thread Yael
@Nathan, thank you so much for the tip! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1574886 Title: All gtk applications Segfault if no GLX context is active To manage notifications

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-07-13 Thread Nathan Sweet
I was having a similar problem where all GTK apps were crashing. I ran strace on one of them and found that the app was seg faulting after it could not find libGLX_indirect.so.0. I use the proprietary nvidia drivers, which appear to provide that library, so, as a workaround, I symlinked the

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-07-13 Thread Nathan Sweet
I should have noted, like the original bug submitter, the GTK apps were only crashing when I was remotely connected (XRDP/VNC). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1574886 Title:

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-07-09 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libepoxy (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1574886

[Ubuntu-x-swat] [Bug 1574886] Re: All gtk applications Segfault if no GLX context is active

2016-06-17 Thread Yael
** Summary changed: - All gtk applications Segfault via VNC with 16.04 and MATE desktop + All gtk applications Segfault if no GLX context is active ** Also affects: libepoxy (Ubuntu) Importance: Undecided Status: New ** No longer affects: mate-desktop -- You received this bug