Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #224970 > unrolled thread

Slic3r --gui won't run

Started byGene Heskett <gheskett@shentel.net>
First post2020-07-19 14:10 +0200
Last post2020-07-21 21:40 +0200
Articles 9 on this page of 69 — 10 participants

Back to article view | Back to linux.debian.user


Contents

  Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 14:10 +0200
    Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 14:20 +0200
      Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 15:50 +0200
        Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 16:00 +0200
          Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 16:30 +0200
            Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 16:40 +0200
              Re: Slic3r --gui won't run Frank <zuiderduin@gmx.com> - 2020-07-19 17:40 +0200
                Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 17:40 +0200
              Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 18:20 +0200
                Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 18:40 +0200
                  Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 19:10 +0200
                    Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 19:20 +0200
                      Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:10 +0200
                        Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 12:50 +0200
                    Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 19:20 +0200
                      Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 19:30 +0200
                        Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 19:40 +0200
                        Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:30 +0200
                      Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 20:30 +0200
                        Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:50 +0200
                          Re: Slic3r --gui won't run Reco <recoverym4n@enotuniq.net> - 2020-07-19 21:40 +0200
                      Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:30 +0200
                    Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-19 20:30 +0200
                      Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-19 20:40 +0200
                      Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:50 +0200
                        Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:20 +0200
                      Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:00 +0200
                        Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-20 16:20 +0200
                          Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 18:30 +0200
                            Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 19:10 +0200
                            Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 19:10 +0200
                              Re: Debian and Raspberry Pi4 (was:  Slic3r --gui won't run). Reco <recoverym4n@enotuniq.net> - 2020-07-20 19:50 +0200
                                Re: Debian and Raspberry Pi4 (was: Slic3r --gui won't run). Andrew Cater <amacater@gmail.com> - 2020-07-20 23:40 +0200
                              Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 20:00 +0200
                                Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-21 08:50 +0200
                                  Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-21 09:10 +0200
                                  Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-21 13:50 +0200
                                    Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-21 15:00 +0200
                                      Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-23 08:10 +0200
                                      Re: Slic3r --gui won't run Steve McIntyre <steve@einval.com> - 2020-07-24 13:00 +0200
                          Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-21 21:00 +0200
          Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 18:00 +0200
            Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 18:10 +0200
              Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 18:50 +0200
                Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-19 19:40 +0200
                  Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-19 20:40 +0200
                    Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 07:00 +0200
                      Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 11:00 +0200
                        Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 17:10 +0200
                          Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 17:20 +0200
                          Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 19:40 +0200
                            Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 19:50 +0200
                              Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 20:40 +0200
                                Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-20 22:20 +0200
                            Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 20:40 +0200
                      Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:30 +0200
                        Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 17:40 +0200
                          Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 17:50 +0200
                            Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 18:00 +0200
                            Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 19:50 +0200
                              Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-21 08:50 +0200
                                Re: Slic3r --gui won't run rhkramer@gmail.com - 2020-07-21 20:50 +0200
                                  Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-23 08:20 +0200
                            Re: Slic3r --gui won't run Gene Heskett <gheskett@shentel.net> - 2020-07-20 19:50 +0200
                    Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 13:20 +0200
                  Re: Slic3r --gui won't run Greg Wooledge <wooledg@eeg.ccf.org> - 2020-07-20 15:10 +0200
                    Re: Slic3r --gui won't run Andrei POPESCU <andreimpopescu@gmail.com> - 2020-07-20 19:00 +0200
                      Re: Slic3r --gui won't run David Wright <deblis@lionunicorn.co.uk> - 2020-07-20 19:30 +0200
    Re: Slic3r --gui won't run mick crane <mick.crane@gmail.com> - 2020-07-21 21:40 +0200

Page 4 of 4 — ← Prev page 1 2 3 [4]


#225089

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2020-07-21 08:50 +0200
Message-ID<AuUg9-4Qu-7@gated-at.bofh.it>
In reply to#225063

[Multipart message — attachments visible in raw view] — view raw

On Lu, 20 iul 20, 13:46:28, Greg Wooledge wrote:
> On Mon, Jul 20, 2020 at 01:41:58PM -0400, Gene Heskett wrote:
> > On Monday 20 July 2020 11:41:04 Greg Wooledge wrote:
> > > Why in the name of all that is unholy did you install ONE HUNDRED
> > > SEVENTY-ONE backported packages?!?
> > >
> > > What were you THINKING?
> > Automatic install by synaptic as they became available over the years.
> 
> That's not how backports are intended to WORK.  Every one is a special
> snowflake.  You have to type "-t stretch-backports" (or analogous
> repository selection option) on your command in order to get them.
> 
> If synaptic is pulling in *-backports without you manually DOING something
> to select the backport over the standard version, then synaptic is
> broken.  Broken-er.  More broken-er.
 
In synaptic's defence, it probably doesn't have a choice if -backports 
(and -security?) is the only available repository. See Gene's original 
sources.list.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]


#225109

Fromrhkramer@gmail.com
Date2020-07-21 20:50 +0200
Message-ID<Av5uW-3gD-9@gated-at.bofh.it>
In reply to#225089
On Tuesday, July 21, 2020 02:47:47 AM Andrei POPESCU wrote:
> On Lu, 20 iul 20, 13:46:28, Greg Wooledge wrote:
> > If synaptic is pulling in *-backports without you manually DOING
> > something to select the backport over the standard version, then
> > synaptic is broken.  Broken-er.  More broken-er.
> 
> In synaptic's defence, it probably doesn't have a choice if -backports
> (and -security?) is the only available repository. See Gene's original
> sources.list.

I can look for the reference, but somewhere I read (recently, but as with all 
google searches, it could have been from the previous century) something to 
the effect that, well, I forget which way it worked, but somehow that maybe non 
backport applications would get a pin value like 100 so that backport 
applications would only be installed if somehow they had a higher pin value 
(or something like that).

Maybe that goes out the window if all / the only repositories were backport 
repositories?

(BTW, if it's not yet clear, I'm going down the rabbit hole ;-(

[toc] | [prev] | [next] | [standalone]


#225152

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2020-07-23 08:20 +0200
Message-ID<AvCKe-6N9-5@gated-at.bofh.it>
In reply to#225109

[Multipart message — attachments visible in raw view] — view raw

On Ma, 21 iul 20, 14:42:02, rhkramer@gmail.com wrote:
> On Tuesday, July 21, 2020 02:47:47 AM Andrei POPESCU wrote:
> > On Lu, 20 iul 20, 13:46:28, Greg Wooledge wrote:
> > > If synaptic is pulling in *-backports without you manually DOING
> > > something to select the backport over the standard version, then
> > > synaptic is broken.  Broken-er.  More broken-er.
> > 
> > In synaptic's defence, it probably doesn't have a choice if -backports
> > (and -security?) is the only available repository. See Gene's original
> > sources.list.
> 
> I can look for the reference, but somewhere I read (recently, but as with all 
> google searches, it could have been from the previous century) something to 
> the effect that, well, I forget which way it worked, but somehow that maybe non 
> backport applications would get a pin value like 100 so that backport 
> applications would only be installed if somehow they had a higher pin value 
> (or something like that).

APT's default priority is 500, exceptions in Debian are 'experimental' 
(1) and 'backports' (100).

Because installed packages have priority 100 as well, for a properly 
configured (old)stable + backports system you must use '-t' to install 
packages from backports.

Upgrades will then automatically pull from backports (because the 
versions are higher than the "regular" repository).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]


#225066

FromGene Heskett <gheskett@shentel.net>
Date2020-07-20 19:50 +0200
Message-ID<AuI5k-5WG-3@gated-at.bofh.it>
In reply to#225048
On Monday 20 July 2020 11:41:04 Greg Wooledge wrote:

> On Mon, Jul 20, 2020 at 11:37:53AM -0400, Gene Heskett wrote:
> > On Monday 20 July 2020 07:24:41 Andrei POPESCU wrote:
> > > dpkg -l | grep '\<bpo'|wc -l
> >
> > 171
>
> Why in the name of all that is unholy did you install ONE HUNDRED
> SEVENTY-ONE backported packages?!?
>
> What were you THINKING?
Automatic install by synaptic as they became available over the years.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]


#225033

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2020-07-20 13:20 +0200
Message-ID<AuBZT-2ni-7@gated-at.bofh.it>
In reply to#225005

[Multipart message — attachments visible in raw view] — view raw

On Du, 19 iul 20, 14:30:54, Gene Heskett wrote:
> On Sunday 19 July 2020 13:38:22 Andrei POPESCU wrote:
> >
> > The easiest way to find all installed packages from backports is to
> > run
> >
> >     aptitude search '?narrow(?installed,?archive(backports))'
> 
> that spits out about 3 or 4 lines of text and blanks it, in about 100 
> millisecs, and will not redirect to |less. No line feeds IOW. I don't 
> read at 20k wpm, so I've no clue what its trying to tell me.

Must be something about your configuration, it works fine here, also the 
redirect to 'less'.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]


#225035

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2020-07-20 15:10 +0200
Message-ID<AuDIl-3tm-3@gated-at.bofh.it>
In reply to#224995
On Sun, Jul 19, 2020 at 08:38:22PM +0300, Andrei POPESCU wrote:
> The easiest way to find all installed packages from backports is to run
> 
>     aptitude search '?narrow(?installed,?archive(backports))'

Actually, the *easiest* way to find all packages from backports
is to run

dpkg -l | grep 'bpo[0-9]'

[toc] | [prev] | [next] | [standalone]


#225056

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2020-07-20 19:00 +0200
Message-ID<AuHiV-5rd-5@gated-at.bofh.it>
In reply to#225035

[Multipart message — attachments visible in raw view] — view raw

On Lu, 20 iul 20, 09:01:17, Greg Wooledge wrote:
> On Sun, Jul 19, 2020 at 08:38:22PM +0300, Andrei POPESCU wrote:
> > The easiest way to find all installed packages from backports is to run
> > 
> >     aptitude search '?narrow(?installed,?archive(backports))'
> 
> Actually, the *easiest* way to find all packages from backports
> is to run
> 
> dpkg -l | grep 'bpo[0-9]'
 
I apologize for the poor choice of words, especially since the use of 
'?narrow' is not necessarily the obvious choice (it certainly wasn't for 
me when I learned about it).

'apt-show-versions' is another possible method, though it is yet another 
package to install and I'm not sure how informative it is about packages 
that are not part of a repository known to APT.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]


#225059

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2020-07-20 19:30 +0200
Message-ID<AuHLX-5Qa-1@gated-at.bofh.it>
In reply to#225056
On Mon 20 Jul 2020 at 19:49:42 (+0300), Andrei POPESCU wrote:
> On Lu, 20 iul 20, 09:01:17, Greg Wooledge wrote:
> > On Sun, Jul 19, 2020 at 08:38:22PM +0300, Andrei POPESCU wrote:
> > > The easiest way to find all installed packages from backports is to run
> > > 
> > >     aptitude search '?narrow(?installed,?archive(backports))'
> > 
> > Actually, the *easiest* way to find all packages from backports
> > is to run
> > 
> > dpkg -l | grep 'bpo[0-9]'
>  
> I apologize for the poor choice of words, especially since the use of 
> '?narrow' is not necessarily the obvious choice (it certainly wasn't for 
> me when I learned about it).
> 
> 'apt-show-versions' is another possible method, though it is yet another 
> package to install

It does confirm that every backports package I've installed, in
distributions since jessie, has got bpo in the version field.

> and I'm not sure how informative it is about packages 
> that are not part of a repository known to APT.

It gives lines like:

linux-image-4.19.0-5-amd64:amd64 4.19.37-5+deb10u2 installed: No available version in archive
xtoolwait:amd64 1.3-6.2 installed: No available version in archive

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#225111

Frommick crane <mick.crane@gmail.com>
Date2020-07-21 21:40 +0200
Message-ID<Av6hj-3Ne-1@gated-at.bofh.it>
In reply to#224970
On 2020-07-19 13:00, Gene Heskett wrote:
> Greetings all;
> 
> Very disapointed in the results from the openscad to Cura to ender 3 
> pro
> results. Forstarters, no support for gcodes g2/g3 so everything has to
> be cobbled up with short straight lines.
> 
> So I installed slic3r. but all I get is the help screen which is 
> several
> pages long. But one of the options is to start it with -gui as option.
> 
> That also fails, looking for Wx.
> 
> Full error report:
> 
> gene@coyote:~/Downloads/stl.stf/files$ slic3r --gui
> Can't locate Wx.pm in @INC (you may need to install the Wx module) 
> (@INC
> contains: /usr/bin/lib /usr/lib/slic3r/ /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.24.1
> /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24
> /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24
> /usr/share/perl/5.24 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base)
> at /usr/lib/slic3r/Slic3r/GUI/AboutDialog.pm line 6.
> BEGIN failed--compilation aborted
> at /usr/lib/slic3r/Slic3r/GUI/AboutDialog.pm line 6.
> Compilation failed in require at /usr/lib/slic3r/Slic3r/GUI.pm line 8.
> BEGIN failed--compilation aborted at /usr/lib/slic3r/Slic3r/GUI.pm line
> 8.
> Compilation failed in require at (eval 77) line 1.
> 
> This is stretch, uptodate. What can I do?  Backports doesn't seem to be
> enabled.
> 
> Cheers, Gene Heskett

excuse me for not knowing what I'm talking about but if is a Perl module 
you are after cannot use cpan ?

mick
-- 
Key ID    4BFEBB31

[toc] | [prev] | [standalone]


Page 4 of 4 — ← Prev page 1 2 3 [4]

Back to top | Article view | linux.debian.user


csiph-web