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


Groups > linux.debian.user > #264791

Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond

From gene heskett <gheskett@shentel.net>
Newsgroups linux.debian.user
Subject Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond
Date 2023-12-16 03:30 +0100
Message-ID <HLsBc-dSkJ-3@gated-at.bofh.it> (permalink)
References (1 earlier) <HKMLD-dsha-1@gated-at.bofh.it> <HKRBD-dvIT-3@gated-at.bofh.it> <HL1AZ-dBJR-1@gated-at.bofh.it> <HL6hj-dEsA-3@gated-at.bofh.it> <HLbqF-dHLQ-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 12/15/23 06:17, David Christensen wrote:
> On 12/14/23 18:36, gene heskett wrote:
>> On 12/14/23 16:36, Anssi Saari wrote:
>>> gene heskett <gheskett@shentel.net> writes:
>>>
>>>> It repeats per gui access. Starting a gfx program such as OpenSCAD, or
>>>> qidislicer from an xfce4 terminal cli, is delayed for this similar but
>>>> not always identical lag. And reports odd warnings etc while its
>>>> getting ready to open its gui.
>>>
>>> Does this happen with common GUI tools too like, say, Firefox? 
>> firefox, no.
>> Or XFCE's
>>> file manager, Thunar I believe?
>> Thunar, yes, but I don't use it, not my cup of tea.  It wants to be a 
>> replacement for mc, but fails at 90% of what mc can do.
>>
>>
>>   Or a text editor like Gedit?
>>
>> Gedit has ben banned from any of my machines for at least 15 years, it 
>> made scrambled eggs out of of several linuxcnc configuration files I 
>> had to re-write from scratch, but geany has never done that.  And 
>> geany is as instant as nano.
>>
>>   Or even the
>>> XFCE terminal?
>> Comes up instantly from the menu, I use it heavily because it has 
>> tabs. I use them much like workspaces.
>>
>> Is this info helpful?
>>
>> Thank you Anssi Saari
>>
>> Cheers, Gene Heskett.
> 
> 
> It sounds like OpenSCAD and gidislicer have something in common that is 
> causing the issue, while the other apps do not have that something.  So, 
> the challenge is finding the shared object files (dynamic linking) 
> and/or the source files (static linking) that are present in the 
> affected programs and not present in the unaffected programs.
> 
> 
> It would be helpful if you posted a list of affected programs and a list 
> of unaffected programs to provide alternatives for a search.  Please 
> note any programs that you did not install using conventional Debian 
> packages (and that may be the root cause of the issue).
> 
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.

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.

Cura, latest 5.5.0 AppImage has a few warnings but opens in about 10 
seconds and works fine from there.

There are other AppImages but most either won't run or fail if writing.

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.

Shotwell has the delay, and can import from the camera.

Spectacle works in 5 secs, but kills plasma as it exits.

Thank you David.


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, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

raid10 is killing me, and applications that aren't willing to wait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 16:30 +0100
  Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond Tom Furie <tom@furie.org.uk> - 2023-12-13 16:50 +0100
    Re: raid10 is killing me, and applications that aren't willing towait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 19:20 +0100
      Re: raid10 is killing me, and applications that aren't willing  towait for it to respond Tom Furie <tom@furie.org.uk> - 2023-12-13 20:00 +0100
        Re: raid10 is killing me, and applications that aren't willingtowait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 20:30 +0100
  Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 18:00 +0100
    Re: raid10 is killing me, and applications that aren't willing towait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 19:30 +0100
      Re: raid10 is killing me, and applications that aren't willing  towait for it to respond Nicolas George <george@nsup.org> - 2023-12-13 19:50 +0100
        Re: raid10 is killing me, and applications that aren't willing towait  for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 20:10 +0100
      Re: raid10 is killing me, and applications that aren't willing towait  for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 19:50 +0100
        Re: raid10 is killing me, and applications that aren't willing  towait for it to respond Dan Ritter <dsr@randomstring.org> - 2023-12-13 20:10 +0100
          Re: raid10 is killing me, and applications that aren't willing towait  for it to respond Pocket <pocket@columbus.rr.com> - 2023-12-13 20:20 +0100
          Re: raid10 is killing me, and applications that aren't willingtowait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-13 20:30 +0100
  Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-13 19:30 +0100
    Re: raid10 is killing me, and applications that aren't willing  towait for it to respond "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-13 23:00 +0100
      Re: raid10 is killing me, and applications that aren't willingtowait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 01:10 +0100
  Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond Andy Smith <andy@strugglers.net> - 2023-12-13 22:40 +0100
    Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond Andy Smith <andy@strugglers.net> - 2023-12-14 00:10 +0100
    Re: raid10 is killing me, and applications that aren't willing towait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 00:40 +0100
      Re: raid10 is killing me, and applications that aren't willing towait  for it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-14 04:20 +0100
  Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond <tomas@tuxteam.de> - 2023-12-14 06:50 +0100
    Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond Nicolas George <george@nsup.org> - 2023-12-14 10:20 +0100
      Re: raid10 is killing me, and applications that aren't willing to  wait for it to respond <tomas@tuxteam.de> - 2023-12-14 10:40 +0100
      Re: raid10 is killing me, and applications that aren't willing towait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 13:10 +0100
    Re: raid10 is killing me, and applications that aren't willing towait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-14 12:00 +0100
      Re: raid10 is killing me, and applications that aren't willing towait for it to respond Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-12-14 22:40 +0100
        Re: raid10 is killing me, and applications that aren't willing towait  for it to respond gene heskett <gheskett@shentel.net> - 2023-12-15 03:40 +0100
          Re: raid10 is killing me, and applications that aren't willing towait  for it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-15 09:10 +0100
            Re: raid10 is killing me, and applications that aren't willing  towait for it to respond Andy Smith <andy@strugglers.net> - 2023-12-15 13:30 +0100
              Re: raid10 is killing me, and applications that aren't willing towait for it to respond Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-15 16:00 +0100
            Re: raid10 is killing me, and applications that aren't willing  towaitfor it to respond gene heskett <gheskett@shentel.net> - 2023-12-16 03:30 +0100
              Re: raid10 is killing me, and applications that aren't willing  towaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 05:00 +0100
                Re: raid10 is killing me, and applications that aren't  willingtowaitfor it to respond gene heskett <gheskett@shentel.net> - 2023-12-16 16:10 +0100
                Re: raid10 is killing me, and applications that aren't  willingtowaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 21:30 +0100
              Re: raid10 is killing me, and applications that aren't willing  towaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 05:10 +0100
                Re: raid10 is killing me, and applications that aren't willing  towaitfor it to respond Matt <matt@jmgresham.xyz> - 2023-12-16 05:20 +0100
                Re: raid10 is killing me, and applications that aren't willing  towaitfor it to respond Greg Wooledge <greg@wooledge.org> - 2023-12-16 05:30 +0100
                Re: raid10 is killing me, and applications that aren't willing  towaitfor it to respond Matt <matt@jmgresham.xyz> - 2023-12-16 05:30 +0100
                Re: raid10 is killing me, and applications that aren't willing towaitfor it to respond Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-12-16 09:30 +0100
                Re: raid10 is killing me, and applications that aren't willing  towaitfor it to respond David Christensen <dpchrist@holgerdanske.com> - 2023-12-16 20:20 +0100
          Re: raid10 is killing me, and applications that aren't willing towait for it to respond Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2023-12-16 09:50 +0100

csiph-web