primusrun: Segmentation fault (core dumped)
up vote
1
down vote
favorite
I've just installed antergos with gnome de and bumblebee on asus R542 laptop.
When I run primusrun glxspheres64 it fails and logs this:
$ primusrun glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x130
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
Segmentation fault (core dumped)
optirun glxspheres64 is ok:
$ optirun -c yuv glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x21
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
103.963006 frames/sec - 116.022715 Mpixels/sec
104.108801 frames/sec - 116.185422 Mpixels/sec
nvidia antergos bumblebee optimus
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
asked Jul 9 at 9:42
Miladdarren
234
add a comment |
up vote
1
down vote
favorite
I've just installed antergos with gnome de and bumblebee on asus R542 laptop.
When I run primusrun glxspheres64 it fails and logs this:
$ primusrun glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x130
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
Segmentation fault (core dumped)
optirun glxspheres64 is ok:
$ optirun -c yuv glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x21
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
103.963006 frames/sec - 116.022715 Mpixels/sec
104.108801 frames/sec - 116.185422 Mpixels/sec
nvidia antergos bumblebee optimus
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
asked Jul 9 at 9:42
Miladdarren
234
Usually when there's a segfault one should collect a backtrace in a debugger, which may help the developers track down the issue.
– thrig
Jul 9 at 14:24
@thrig so what should I do?
– Miladdarren
Jul 9 at 14:51
You mention you "checked out other forums" -- which ones, and what advice have you tried so far? Arch (on which Antergos is based) has an open bug about this: bugs.archlinux.org/task/58933
– JigglyNaga
Jul 9 at 16:38
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I've just installed antergos with gnome de and bumblebee on asus R542 laptop.
When I run primusrun glxspheres64 it fails and logs this:
$ primusrun glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x130
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
Segmentation fault (core dumped)
optirun glxspheres64 is ok:
$ optirun -c yuv glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x21
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
103.963006 frames/sec - 116.022715 Mpixels/sec
104.108801 frames/sec - 116.185422 Mpixels/sec
nvidia antergos bumblebee optimus
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
asked Jul 9 at 9:42
Miladdarren
234
I've just installed antergos with gnome de and bumblebee on asus R542 laptop.
When I run primusrun glxspheres64 it fails and logs this:
$ primusrun glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x130
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
Segmentation fault (core dumped)
optirun glxspheres64 is ok:
$ optirun -c yuv glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
Visual ID of window: 0x21
Context is Direct
OpenGL Renderer: GeForce 930MX/PCIe/SSE2
103.963006 frames/sec - 116.022715 Mpixels/sec
104.108801 frames/sec - 116.185422 Mpixels/sec
nvidia antergos bumblebee optimus
nvidia antergos bumblebee optimus
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
asked Jul 9 at 9:42
Miladdarren
234
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
asked Jul 9 at 9:42
Miladdarren
234
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
edited Nov 24 at 20:01
Rui F Ribeiro
38.3k1475126
38.3k1475126
asked Jul 9 at 9:42
Miladdarren
234
asked Jul 9 at 9:42
Miladdarren
234
asked Jul 9 at 9:42
Miladdarren
234
234
Usually when there's a segfault one should collect a backtrace in a debugger, which may help the developers track down the issue.
– thrig
Jul 9 at 14:24
@thrig so what should I do?
– Miladdarren
Jul 9 at 14:51
You mention you "checked out other forums" -- which ones, and what advice have you tried so far? Arch (on which Antergos is based) has an open bug about this: bugs.archlinux.org/task/58933
– JigglyNaga
Jul 9 at 16:38
add a comment |
Usually when there's a segfault one should collect a backtrace in a debugger, which may help the developers track down the issue.
– thrig
Jul 9 at 14:24
@thrig so what should I do?
– Miladdarren
Jul 9 at 14:51
You mention you "checked out other forums" -- which ones, and what advice have you tried so far? Arch (on which Antergos is based) has an open bug about this: bugs.archlinux.org/task/58933
– JigglyNaga
Jul 9 at 16:38
Usually when there's a segfault one should collect a backtrace in a debugger, which may help the developers track down the issue.
– thrig
Jul 9 at 14:24
Usually when there's a segfault one should collect a backtrace in a debugger, which may help the developers track down the issue.
– thrig
Jul 9 at 14:24
@thrig so what should I do?
– Miladdarren
Jul 9 at 14:51
@thrig so what should I do?
– Miladdarren
Jul 9 at 14:51
You mention you "checked out other forums" -- which ones, and what advice have you tried so far? Arch (on which Antergos is based) has an open bug about this: bugs.archlinux.org/task/58933
– JigglyNaga
Jul 9 at 16:38
You mention you "checked out other forums" -- which ones, and what advice have you tried so far? Arch (on which Antergos is based) has an open bug about this: bugs.archlinux.org/task/58933
– JigglyNaga
Jul 9 at 16:38
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
I had the same problem here. Just downgrade mesa to 18.0.4.
I use Arch, so I did:
pacman -U /var/cache/pacman/pkg/mesa-18.0.4-1-x86_64.pkg.tar.xz
answered Aug 4 at 4:07
Pedro Vinicius
111
add a comment |
up vote
1
down vote
Not sure if the problem is in mesa, xserver or primus, but here's the upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=106910 and here's a simple workaround:
export LIBGL_DRI3_DISABLE=1
primusrun glxgears
answered Aug 7 at 7:03
Tomáš Janoušek
1112
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I had the same problem here. Just downgrade mesa to 18.0.4.
I use Arch, so I did:
pacman -U /var/cache/pacman/pkg/mesa-18.0.4-1-x86_64.pkg.tar.xz
answered Aug 4 at 4:07
Pedro Vinicius
111
add a comment |
up vote
1
down vote
I had the same problem here. Just downgrade mesa to 18.0.4.
I use Arch, so I did:
pacman -U /var/cache/pacman/pkg/mesa-18.0.4-1-x86_64.pkg.tar.xz
answered Aug 4 at 4:07
Pedro Vinicius
111
add a comment |
up vote
1
down vote
up vote
1
down vote
I had the same problem here. Just downgrade mesa to 18.0.4.
I use Arch, so I did:
pacman -U /var/cache/pacman/pkg/mesa-18.0.4-1-x86_64.pkg.tar.xz
answered Aug 4 at 4:07
Pedro Vinicius
111
I had the same problem here. Just downgrade mesa to 18.0.4.
I use Arch, so I did:
pacman -U /var/cache/pacman/pkg/mesa-18.0.4-1-x86_64.pkg.tar.xz
answered Aug 4 at 4:07
Pedro Vinicius
111
answered Aug 4 at 4:07
Pedro Vinicius
111
answered Aug 4 at 4:07
Pedro Vinicius
111
answered Aug 4 at 4:07
Pedro Vinicius
111
111
add a comment |
add a comment |
up vote
1
down vote
Not sure if the problem is in mesa, xserver or primus, but here's the upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=106910 and here's a simple workaround:
export LIBGL_DRI3_DISABLE=1
primusrun glxgears
answered Aug 7 at 7:03
Tomáš Janoušek
1112
add a comment |
up vote
1
down vote
Not sure if the problem is in mesa, xserver or primus, but here's the upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=106910 and here's a simple workaround:
export LIBGL_DRI3_DISABLE=1
primusrun glxgears
answered Aug 7 at 7:03
Tomáš Janoušek
1112
add a comment |
up vote
1
down vote
up vote
1
down vote
Not sure if the problem is in mesa, xserver or primus, but here's the upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=106910 and here's a simple workaround:
export LIBGL_DRI3_DISABLE=1
primusrun glxgears
answered Aug 7 at 7:03
Tomáš Janoušek
1112
Not sure if the problem is in mesa, xserver or primus, but here's the upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=106910 and here's a simple workaround:
export LIBGL_DRI3_DISABLE=1
primusrun glxgears
answered Aug 7 at 7:03
Tomáš Janoušek
1112
answered Aug 7 at 7:03
Tomáš Janoušek
1112
answered Aug 7 at 7:03
Tomáš Janoušek
1112
answered Aug 7 at 7:03
Tomáš Janoušek
1112
1112
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f454261%2fprimusrun-segmentation-fault-core-dumped%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Usually when there's a segfault one should collect a backtrace in a debugger, which may help the developers track down the issue.
– thrig
Jul 9 at 14:24
@thrig so what should I do?
– Miladdarren
Jul 9 at 14:51
You mention you "checked out other forums" -- which ones, and what advice have you tried so far? Arch (on which Antergos is based) has an open bug about this: bugs.archlinux.org/task/58933
– JigglyNaga
Jul 9 at 16:38