GL_MULTISAMPLE and GL_ARRAY_BUFFER_ARB messages on failed launch #4085
Labels
Comments
|
Update: this is also happening (same message but a different line number) with the version installed with apt-get from the Debian archives. I don't keep an mixed system or anything, but perhaps this is a conflict with a recently upgraded library or a Debian specific problem. |
|
I seem to have exactly the same problem with slic3r from the Repos, on Debian testing: |
|
Ugh, this is probably POGL related, or your driver version?
…On Aug 12, 2017 6:48 PM, "Chris" ***@***.***> wrote:
I seem to have exactly the same problem with slic3r from the Repos, on
Debian testing:
Your vendor has not defined OpenGL macro GL_MULTISAMPLE, used at
/usr/lib/slic3r/Slic3r/GUI/3DScene.pm line 619.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8CkO90tV4sCxz6vKu7MCZUUscDG8Wks5sXjm2gaJpZM4O1gxn>
.
|
|
I'm pretty sure both Debian's and my self-compiled version were working until recently - perhaps as recently as last week. Looking in dpkg.log, I see that libopengl-perl and slic3r were upgraded: 2017-08-07 17:37:50 upgrade libopengl-perl:amd64 0.6704+dfsg-2+b2 0.6704+dfsg-2+b4 |
|
Then it is probably opengl perl, I don't know what the debian package would
need.
Use the appimage in the meantime.
On Aug 12, 2017 10:20 PM, "Stephen J. Lynch" <notifications@github.com> wrote:
I'm pretty sure both Debian's and my self-compiled version were working
until recently - perhaps as recently as last week. Looking in dpkg.log, I
see that libopengl-perl and slic3r were upgraded:
2017-08-07 17:37:50 upgrade libopengl-perl:amd64 0.6704+dfsg-2+b2
0.6704+dfsg-2+b4
2017-08-07 17:39:32 upgrade slic3r:amd64 1.2.9+dfsg-6 1.2.9+dfsg-6+b1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8CmQiTUMklu06dUiWt26GhUa2bN_pks5sXmtfgaJpZM4O1gxn>
.
|
|
I know that POGL 0.70 and 0.67 should be working (I have 0.70 and had to
fix something in slic3r because of it months ago).
…On Aug 12, 2017 11:20 PM, wrote:
Then it is probably opengl perl, I don't know what the debian package
would need.
Use the appimage in the meantime.
On Aug 12, 2017 10:20 PM, "Stephen J. Lynch" ***@***.***>
wrote:
I'm pretty sure both Debian's and my self-compiled version were working
until recently - perhaps as recently as last week. Looking in dpkg.log, I
see that libopengl-perl and slic3r were upgraded:
2017-08-07 17:37:50 upgrade libopengl-perl:amd64 0.6704+dfsg-2+b2
0.6704+dfsg-2+b4
2017-08-07 17:39:32 upgrade slic3r:amd64 1.2.9+dfsg-6 1.2.9+dfsg-6+b1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8CmQiTUMklu06dUiWt26GhUa2bN_pks5sXmtfgaJpZM4O1gxn>
.
|
|
@citybadger I'm suspecting it's your system right now; I just upgraded my test system to Stretch and I haven't run into that problem. Usually when some macro isn't defined your OpenGL libraries are weird or the driver is old. Usually though it's the opengl provider. |
lordofhyphens
added
the
Can't Reproduce - Development Build
|
I'm on testing, aka Buster. I believe the libraries were upgraded after
Stretch became stable, so my libraries are newer than yours. If this is a
bug in the new libraries, I expect it will eventually be corrected. If it's
a feature, then this problem will grow as more and more distributions
upgrade to the new libraries.
…On Sat, Sep 2, 2017 at 11:22 PM, Joseph Lenox ***@***.***> wrote:
@citybadger <https://github.com/citybadger> I'm suspecting it's your
system right now; I just upgraded my test system to Stretch and I haven't
run into that problem.
Usually when some macro isn't defined your OpenGL libraries are weird or
the driver is old. I can probably work around it though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBwu0UNCHK8rgfVtlSz1apoOIhJawrNks5seht9gaJpZM4O1gxn>
.
|
|
Any problems with the AppImage build?
On Sep 2, 2017 10:31 PM, "Stephen J. Lynch" <notifications@github.com>
wrote:
… I'm on testing, aka Buster. I believe the libraries were upgraded after
Stretch became stable, so my libraries are newer than yours. If this is a
bug in the new libraries, I expect it will eventually be corrected. If it's
a feature, then this problem will grow as more and more distributions
upgrade to the new libraries.
On Sat, Sep 2, 2017 at 11:22 PM, Joseph Lenox ***@***.***>
wrote:
> @citybadger <https://github.com/citybadger> I'm suspecting it's your
> system right now; I just upgraded my test system to Stretch and I haven't
> run into that problem.
>
> Usually when some macro isn't defined your OpenGL libraries are weird or
> the driver is old. I can probably work around it though.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4085 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
ABBwu0UNCHK8rgfVtlSz1apoOIhJawrNks5seht9gaJpZM4O1gxn>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8Cu8y7DpzpaWRmxrhhLR_Pv5u-HHuks5seh2fgaJpZM4O1gxn>
.
|
|
The AppImage build runs on my system.
On Sun, Sep 3, 2017 at 12:33 AM, Joseph Lenox <notifications@github.com>
wrote:
… Any problems with the AppImage build?
On Sep 2, 2017 10:31 PM, "Stephen J. Lynch" ***@***.***>
wrote:
> I'm on testing, aka Buster. I believe the libraries were upgraded after
> Stretch became stable, so my libraries are newer than yours. If this is a
> bug in the new libraries, I expect it will eventually be corrected. If
it's
> a feature, then this problem will grow as more and more distributions
> upgrade to the new libraries.
>
> On Sat, Sep 2, 2017 at 11:22 PM, Joseph Lenox ***@***.***>
> wrote:
>
> > @citybadger <https://github.com/citybadger> I'm suspecting it's your
> > system right now; I just upgraded my test system to Stretch and I
haven't
> > run into that problem.
> >
> > Usually when some macro isn't defined your OpenGL libraries are weird
or
> > the driver is old. I can probably work around it though.
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <#4085 (comment)>,
> or mute
> > the thread
> > <https://github.com/notifications/unsubscribe-auth/
> ABBwu0UNCHK8rgfVtlSz1apoOIhJawrNks5seht9gaJpZM4O1gxn>
> > .
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#4085 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-
auth/AAB8Cu8y7DpzpaWRmxrhhLR_Pv5u-HHuks5seh2fgaJpZM4O1gxn>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBwu5LQvVNFilb0gSnfryJgz89SQ4lnks5seiwTgaJpZM4O1gxn>
.
|
|
The library versions in the AppImage are older than on my system. I don't
know what to look for, but for example libwx_gtk2u_gl-3.0.so.0.2.0 is in
the AppImage and libwx_gtk2u_gl-3.0.so.0.3.0 is on my system.
If you could tell me which libraries are the likely source of this problem
I could compare them.
…On Sun, Sep 3, 2017 at 6:30 PM, citybadger ***@***.***> wrote:
The AppImage build runs on my system.
On Sun, Sep 3, 2017 at 12:33 AM, Joseph Lenox ***@***.***>
wrote:
> Any problems with the AppImage build?
>
> On Sep 2, 2017 10:31 PM, "Stephen J. Lynch" ***@***.***>
> wrote:
>
> > I'm on testing, aka Buster. I believe the libraries were upgraded after
> > Stretch became stable, so my libraries are newer than yours. If this is
> a
> > bug in the new libraries, I expect it will eventually be corrected. If
> it's
> > a feature, then this problem will grow as more and more distributions
> > upgrade to the new libraries.
> >
> > On Sat, Sep 2, 2017 at 11:22 PM, Joseph Lenox ***@***.***
> >
> > wrote:
> >
> > > @citybadger <https://github.com/citybadger> I'm suspecting it's your
> > > system right now; I just upgraded my test system to Stretch and I
> haven't
> > > run into that problem.
> > >
> > > Usually when some macro isn't defined your OpenGL libraries are weird
> or
> > > the driver is old. I can probably work around it though.
> > >
> > > —
> > > You are receiving this because you were mentioned.
> > > Reply to this email directly, view it on GitHub
> > > <#4085 (comment)
> >,
> > or mute
> > > the thread
> > > <https://github.com/notifications/unsubscribe-auth/
> > ABBwu0UNCHK8rgfVtlSz1apoOIhJawrNks5seht9gaJpZM4O1gxn>
> > > .
> > >
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <#4085 (comment)>,
> or mute
> > the thread
> > <https://github.com/notifications/unsubscribe-auth/
> AAB8Cu8y7DpzpaWRmxrhhLR_Pv5u-HHuks5seh2fgaJpZM4O1gxn>
>
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4085 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABBwu5LQvVNFilb0gSnfryJgz89SQ4lnks5seiwTgaJpZM4O1gxn>
> .
>
|
|
I'm running Debian Buster and I'm experiencing the very same error. In case it helps, @citybadger, according to this question, GL_MULTISAMPLE is defined:
|
|
Does it work if any of those packages are installed?
…On Sep 4, 2017 11:08 AM, "Rock Storm" ***@***.***> wrote:
I'm running Debian Buster and I'm experiencing the very same error.
In case it helps, @citybadger <https://github.com/citybadger>, according
to this question
<https://stackoverflow.com/questions/4207506/where-is-gl-multisample-defined>,
*GL_MULTISAMPLE* is defined:
- Within 'glext.h', which, in Debian, is provided by, among some
others, the "mesa-common-dev" and "libgtkglext1-dev" packages . However
Slic3r doesn't seem to depend on them directly.
- Or in 'glew.h', which is provided by the "libglew-dev" package.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8CrI4ZRSDcCqGe3AHug1DAv5HvuFdks5sfCB8gaJpZM4O1gxn>
.
|
|
Installing them ("mesa-common-dev", "libgtkglext1-dev" nor "libglew-dev") does not solve the problem. Judging by the error message it would seem GL_MULTISAMPLE is either not defined or Slic3r is somehow unable to find the definition, but neither of them make much sense to me. I'm certainly lost here. |
|
This is down in the POGL libraries that Slic3r depends on, which makes it
extra hard to test/diagnose. That it works in Stretch but not in Buster
makes me wonder whether or not the opengl libraries have a bug in them.
…On Sep 6, 2017 10:32 AM, "Rock Storm" ***@***.***> wrote:
Installing them ("mesa-common-dev", "libgtkglext1-dev" nor "libglew-dev")
does not solve the problem.
Judging by the error message it would seem *GL_MULTISAMPLE* is either not
defined or Slic3r is somehow unable to find the definition, but neither of
them make much sense to me. I'm certainly lost here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8Cp6E1oxLKak02vthfpUN8cLlIH20ks5sfrsBgaJpZM4O1gxn>
.
|
|
If you have any idea of what I could test/diagnose to try to narrow down the problem I would happily do it. |
|
Someone wrote up the same issue against the slic3r-prusa package on Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872273 This seems relevant. Can you replace the instances of GL_MULTISAMPLE with GL_MULTISAMPLE_ARB ? It may not do anything (put everything back if it doesn't help). Which graphics card are you using on this system btw? |
|
Alternatively, do you have glew installed (might be relevant): |
|
Hi, I tried renaming the import from GL_MULTISAMPLE to GL_MULTISAMPLE_ARB, but it just erred on the new symbol. I tried installing the libglew-dev stuff as you suggested, but that didn't seem to work either. I have followed the advice in the Debian bug report and deleted the lines with GL_MULTISAMPLE on and it seems to work for now. 🤞 Do you know if POGL is reading those symbols out of the header files. Perhaps that constant doesn't exist in the latest mesagl drivers or something? It looks like one of the Debian bugs is against mesa. |
|
It looked like to me that the debian bug against mesa was commented on as
"wtf do you expect us to do".
What POGL does is that it translates it into something else. I've seen it
dying on other constants that usually were tied to driver/libgl problems.
Prusa3D's fork of Slic3r has the same problem.
"Nothing unreal exists." - Kiri-kin-tha's First Law of Metaphysics.
…On Mon, Sep 11, 2017 at 12:14 PM, Russell Sim ***@***.***> wrote:
Hi, I tried renaming the import from GL_MULTISAMPLE to GL_MULTISAMPLE_ARB,
but it just erred on the new symbol.
I tried installing the libglew-dev stuff as you suggested, but that didn't
seem to work either.
I have followed the advice in the Debian bug report and deleted the lines
with GL_MULTISAMPLE on and it seems to work for now. 🤞
Do you know if POGL is reading those symbols out of the header files.
Perhaps that constant doesn't exist in the latest mesagl drivers or
something? It looks like one of the Debian bugs is against mesa.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8Ci_VFot_Yrt72M-0V-dRgAd5bm0Vks5shWpigaJpZM4O1gxn>
.
|
lordofhyphens
added
HIGH PRIORITY
OS: Linux
Upstream issue
|
I am glad to hear that the AppImage works; so everyone isn't out in the cold. |
|
Prusa3D's fork of Slic3r has the same problem.
I wonder why they did not open an issue at our git.
Anyway, the correct solution is to extend our "can_multisample" check
my $can_multisample =
Wx::wxVERSION >= 3.000003 &&
defined Wx::GLCanvas->can('WX_GL_SAMPLE_BUFFERS') &&
defined Wx::GLCanvas->can('WX_GL_SAMPLES');
with
defined Wx::GLCanvas->can('multisample')
then to store the "can_multisample" at the class and check it before
each glEnable/glDisable(GL_MULTISAMPLE);
…On Mon, Sep 11, 2017 at 7:43 PM, Joseph Lenox ***@***.***> wrote:
I am glad to hear that the AppImage works; so everyone isn't out in the
cold.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5I4XAl2Dfq9DNRv8uRxujwMGyXKlYks5shXAbgaJpZM4O1gxn>
.
|
|
Anyway, the correct solution is to extend our "can_multisample" check
Sorry, that was not a working solution.
…On Tue, Sep 12, 2017 at 9:25 AM, bubnikv . ***@***.***> wrote:
> Prusa3D's fork of Slic3r has the same problem.
I wonder why they did not open an issue at our git.
Anyway, the correct solution is to extend our "can_multisample" check
my $can_multisample =
Wx::wxVERSION >= 3.000003 &&
defined Wx::GLCanvas->can('WX_GL_SAMPLE_BUFFERS') &&
defined Wx::GLCanvas->can('WX_GL_SAMPLES');
with
defined Wx::GLCanvas->can('multisample')
then to store the "can_multisample" at the class and check it before
each glEnable/glDisable(GL_MULTISAMPLE);
On Mon, Sep 11, 2017 at 7:43 PM, Joseph Lenox ***@***.***>
wrote:
> I am glad to hear that the AppImage works; so everyone isn't out in the
> cold.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#4085 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFj5I4XAl2Dfq9DNRv8uRxujwMGyXKlYks5shXAbgaJpZM4O1gxn>
> .
>
|
bubnikv
added a commit
to prusa3d/PrusaSlicer
that referenced
this issue
Sep 12, 2017
"GL_MULTISAMPLE and GL_ARRAY_BUFFER_ARB messages on failed launch" slic3r/Slic3r#4085 Also fixes https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872273
bubnikv
added a commit
to prusa3d/PrusaSlicer
that referenced
this issue
Sep 12, 2017
making it safe in case wxWidgets do not report supporting multisampling, but the OpenGL context actually does and it leaves the multi-sampling enabled. This then may in theory lead to incorrect picking by color.
|
I have hopefully fixed it with |
|
Just for the record: I'm pretty sure installing the -dev packages won't resolve anything. They are only used during package building (in this case, POGL) and won't contribute anything after. It's very likely that the POGL symbol scanner failed to detect the mentioned OpenGL symbols. |
lordofhyphens
added a commit
that referenced
this issue
Oct 23, 2017
lordofhyphens
pushed a commit
that referenced
this issue
Oct 23, 2017
making it safe in case wxWidgets do not report supporting multisampling, but the OpenGL context actually does and it leaves the multi-sampling enabled. This then may in theory lead to incorrect picking by color.
Closed
|
I've updated to Kubuntu 17.10 from 17.04 and hit this same issue with the 1.2.9 version in Ubuntu's repositories. |
|
@lordofhyphens I had to hack diff --git a/lib/Slic3r/GUI/3DScene.pm b/lib/Slic3r/GUI/3DScene.pm
index 72e7d28e..c5d903f3 100644
--- a/lib/Slic3r/GUI/3DScene.pm
+++ b/lib/Slic3r/GUI/3DScene.pm
@@ -50,7 +50,7 @@ use constant PI => 3.1415927;
# Constant to determine if Vertex Buffer objects are used to draw
# bed grid and the cut plane for object separation.
-use constant HAS_VBO => eval { glGenBuffersARB_p(0); 1 };
+use constant HAS_VBO => eval { glGenBuffersARB_p(0); GL_ARRAY_BUFFER_ARB; 1 };
# phi / theta angles to orient the camera. |
|
I wonder why these features are so problematic. On the other hand, the ARB variants are pre-OpenGL2 leftovers. |
|
The Perl OpenGL module does not support OpenGL 2.0 and higher, so the
OpenGL 2.0 features are only accessible through the extensions by the Perl
OpenGL module.
The Prusa3D fork ditched most of the Perl OpenGL and the OpenGL 2.0 calls
are directly executed from a C++ code.
…On Mon, Nov 6, 2017 at 8:06 AM, Gregor Riepl ***@***.***> wrote:
I wonder why these features are so problematic.
Practically every GPU and OGL library has support for them these days???
On the other hand, the ARB variants are pre-OpenGL2 leftovers.
One should be able to use the non-ARB variants without problems, no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5IwdqbKraa_BrvASiR3k0rOK1akFMks5szq_1gaJpZM4O1gxn>
.
|
|
So... how to fix this problem? I have it too now. |
|
+1 affected. Ubuntu 17.10. Thankfully the .AppImage seems to work. |
|
I have the same problem on Kubuntu 17.10, with slic3r (1.2.9) and slic3r-prusa (1.33.8-dev) from the ubuntu repositories. I've downloaded Slic3r from the download page ( http://slic3r.org/download ) and it works out the box without any problem. Same with Slic3r Prusa Ed... |
|
On Sun, Dec 03, 2017 at 06:18:43PM +0000, Arofarn wrote:
I have the same problem on Kubuntu 17.10, with slic3r (1.2.9) and slic3r-prusa (1.33.8-dev) from the ubuntu repositories.
I've downloaded Slic3r from the download page ( http://slic3r.org/download )
and it works out the box without any problem. Same with Slic3r Prusa Ed... So
I think the problem is with some packages in ubuntu repositories....
I just uploaded a fix for this at
https://bugs.launchpad.net/ubuntu/artful/+source/slic3r/+bug/1726103
Could you help test this please?
…--
Kind regards,
Loong Jin
|
|
Currently I still have this problem when compiling from the source (from
github). But the package from the Debian repositories is working.
On Tue, Dec 5, 2017 at 1:17 PM, Chow Loong Jin <notifications@github.com>
wrote:
… On Sun, Dec 03, 2017 at 06:18:43PM +0000, Arofarn wrote:
> I have the same problem on Kubuntu 17.10, with slic3r (1.2.9) and
slic3r-prusa (1.33.8-dev) from the ubuntu repositories.
>
> I've downloaded Slic3r from the download page (
http://slic3r.org/download )
> and it works out the box without any problem. Same with Slic3r Prusa
Ed... So
> I think the problem is with some packages in ubuntu repositories....
I just uploaded a fix for this at
https://bugs.launchpad.net/ubuntu/artful/+source/slic3r/+bug/1726103
Could you help test this please?
--
Kind regards,
Loong Jin
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBwu0Un2QBzLKVGnhoIPm0tNM7X4v4vks5s9Yi_gaJpZM4O1gxn>
.
|
|
Debian package repo is *old*.
…On Dec 5, 2017 1:06 PM, "Stephen J. Lynch" ***@***.***> wrote:
Currently I still have this problem when compiling from the source (from
github). But the package from the Debian repositories is working.
On Tue, Dec 5, 2017 at 1:17 PM, Chow Loong Jin ***@***.***>
wrote:
> On Sun, Dec 03, 2017 at 06:18:43PM +0000, Arofarn wrote:
> > I have the same problem on Kubuntu 17.10, with slic3r (1.2.9) and
> slic3r-prusa (1.33.8-dev) from the ubuntu repositories.
> >
> > I've downloaded Slic3r from the download page (
> http://slic3r.org/download )
> > and it works out the box without any problem. Same with Slic3r Prusa
> Ed... So
> > I think the problem is with some packages in ubuntu repositories....
>
> I just uploaded a fix for this at
> https://bugs.launchpad.net/ubuntu/artful/+source/slic3r/+bug/1726103
>
> Could you help test this please?
>
> --
> Kind regards,
> Loong Jin
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4085 (comment)>,
or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/
ABBwu0Un2QBzLKVGnhoIPm0tNM7X4v4vks5s9Yi_gaJpZM4O1gxn>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4085 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAB8CoL-VG5Vwzoa3LEPPRdVVLYhOMBXks5s9ZQogaJpZM4O1gxn>
.
|
|
That's because your latest stable release is *old*.
…On Tue, Dec 05, 2017 at 11:15:27AM -0800, Joseph Lenox wrote:
Debian package repo is *old*.
On Dec 5, 2017 1:06 PM, "Stephen J. Lynch" ***@***.***> wrote:
> Currently I still have this problem when compiling from the source (from
> github). But the package from the Debian repositories is working.
>
>
> On Tue, Dec 5, 2017 at 1:17 PM, Chow Loong Jin ***@***.***>
> wrote:
>
> > On Sun, Dec 03, 2017 at 06:18:43PM +0000, Arofarn wrote:
> > > I have the same problem on Kubuntu 17.10, with slic3r (1.2.9) and
> > slic3r-prusa (1.33.8-dev) from the ubuntu repositories.
> > >
> > > I've downloaded Slic3r from the download page (
> > http://slic3r.org/download )
> > > and it works out the box without any problem. Same with Slic3r Prusa
> > Ed... So
> > > I think the problem is with some packages in ubuntu repositories....
> >
> > I just uploaded a fix for this at
> > https://bugs.launchpad.net/ubuntu/artful/+source/slic3r/+bug/1726103
> >
> > Could you help test this please?
> >
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <#4085 (comment)>,
> or mute
> > the thread
> > <https://github.com/notifications/unsubscribe-auth/
> ABBwu0Un2QBzLKVGnhoIPm0tNM7X4v4vks5s9Yi_gaJpZM4O1gxn>
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4085 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AAB8CoL-VG5Vwzoa3LEPPRdVVLYhOMBXks5s9ZQogaJpZM4O1gxn>
> .
>
|
|
This also happened to me after upgrading to Ubuntu 17.10 artful. @hyperair 's fix to HAS_VBO worked, then I added additional code around the two line containing GL_MULTISAMPLE, because there are two more occourances of GL_MULTISAMPLE in master not covered by the cherry-pick of @bubnikv 's patch here: https://github.com/alexrj/Slic3r/blob/master/lib/Slic3r/GUI/3DScene.pm#L747 and here: https://github.com/alexrj/Slic3r/blob/master/lib/Slic3r/GUI/3DScene.pm#L772 |
|
Thanks @GilesBathgate |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
1.2.9-1120-g13f121e3
Operating system type + version
Debian testing:
Linux minor7th 4.11.0-1-rt-amd64 #1 SMP PREEMPT RT Debian 4.11.6-1 (2017-06-19) x86_64 GNU/Linux
(have tried using the standard non-realtime kernel with same result)
Behavior
Error below when run.
If I comment out that line, and the other instance of GL_MULTISAMPLE that follows, I get this message:
If I disable the those lines by changing the ifs surrounding that line and the two subsequent lines to if(0), ./slic3r.pl launches sucessfully.
Output of `perl Build.PL"
Output of
perl Build.PL --guiThe text was updated successfully, but these errors were encountered: