Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond
On 12/15/23 18:23, gene heskett wrote:
I use the bleeding edge AppImage version of OpenSCAD, heavily, it has no
such problems. And no error outputs on the cli, it Just Works.
Thank you for the reply. :-)
Do you mean the following?
https://openscad.org/downloads.html
*** correction *** OpenSCAD-2023.12.09.ai17758-x86_64.AppImage
QIDISlicer gives these two errors instantly on launch from cli
Cannot register URI scheme wxfs more than once
** (qidi-slicer:24330): CRITICAL **: 12:29:20.900: Cannot register URI
scheme memory more than once
QIDISlicer has jillions of gtk2 things:
(qidi-slicer:24330): Gtk-CRITICAL **: 12:29:21.017:
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
(qidi-slicer:24330): Gtk-CRITICAL **: 04:04:12.705:
gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkSpinButton
including 50+ of the second, and many more gtk_gedget as it opens and
works. And I blame the packager since there is no more gtk2 in the
debian repo's.
Which QIDISlicer -- e.g. version?
Where did you get it -- e.g. Debian package, AppImage, source tarball, etc.?
Cura, latest 5.5.0 AppImage has a few warnings but opens in about 10
seconds and works fine from there.
Cura version and source?
There are other AppImages but most either won't run or fail if writing.
We can save those for later.
digiKam v8.2.0 cannot import from my camera because (and this is a swag)
it cannot get instant write perms. It can see everything in the camera,
but cannot download anything. And does not report any errors on the cli
when it fails. It goes thru te motions, blinking all the lights, but
gimp cannot find the images it just went thru the motions of downloading.
digiKam version and source?
Shotwell has the delay, and can import from the camera.
Shotwell version and source?
Spectacle works in 5 secs, but kills plasma as it exits.
Spectacle version and source?
Debugging issues for any of the above programs is likely going to
require duplicating your Debian configuration. Are you prepared to
provide these details?
As a alternative to, or in parallel with, duplicating your Debian,
duplicating your apps, and debugging the combination stack, you might
want to implement a work-around -- install a hypervisor, pick one
application, create a virtual machine, install only enough Debian to
support that application, install that application and nothing else, and
use the application. Repeat for each application. (Of course, this
presumes you can find a hypervisor that runs without issues on your
Debian.)
Another hypervisor idea -- do a fresh install of only enough Debian to
support a hypervisor, install the hypervisor, then convert your existing
Debian instance into a VM.
In any case, that NVMe PCIe SSD would be ideal for VM's.
David
Reply to: