Menu ▾ ▴

#37 X I/O error crashes X

Unknown
closed
nobody
None
5
2022-02-05
2021-09-25
Mike Grammes
No

I have been trying to play with Yoshimi. After awhile and with no discernible repetitive reason it causes a I/O error for X and crashes X causing be to go back to my login. I cannot find more info in either xlog or using journalctl. However I do have the most recent core dump.

1 Attachments
core.Xorg.1000.c981d61413b04175a99a7a179f14633b.471230.1632535274000000.zst

Related

Bugs: #37

Discussion

  • Will Godfrey

    Will Godfrey - 2021-09-25

    Please give more information about your setup. In particular:

    Yoshimi version - self build or fetched from distribution?
    Distribution version
    Window manager
    Machine architecture
    How long before the crash? Minutes? Hours?
    What happens if you run it from the command line with no GUI?

     

  • Mike Grammes

    Mike Grammes - 2021-09-25

    I am using Yoshimi 2.1.0 build from archlinux package repo.
    I keep my archlinux up to date and is rolling release.
    I am using XFCE as my window manager
    I'm am running 64 bit with 5.14.7 as my linux kernel.
    It varies in time between as fast as 2 minutes and as long as 15 minutes.
    I don't know about in nogui mode because it is while I am using the different synth engines and learning how the program works. It seems to be linked to how many parameters I change (though crashes in different parts of the gui from the main window to any of the synth engines). When I changed many things quickly it seemed to crash sooner in time.

    Let me more what else would be helpful.

     

  • k_amlie

    k_amlie - 2021-09-27

    Can you run gdb yoshimi COREFILE on your core file, then run the command bt, and post the output?

     

    • dbtx

      dbtx - 2021-09-27

      It was X which dumped core, not Yoshimi. I thought Yoshimi never did anything at all directly to an X server (that's crazy!) -- so my first guess is that arch's X or FLTK package has a problem and Yoshimi is just the one finding it.

      OP, there aren't many options but can you try messing around with something else like Rakarrack? What version of FLTK is installed? Are you able to try with older versions of that and (separately) another version of Yoshimi?

       

      • Mike Grammes

        Mike Grammes - 2021-09-27

        Here is the output requested:

        Program terminated with signal SIGSEGV, Segmentation fault.

        0 0x0000558117027290 in xfsm_manager_get_shutdown_type ()

        [Current thread is 1 (Thread 0x7ff5cb3cb980 (LWP 31555))]
        (gdb) bt

        0 0x0000558117027290 in xfsm_manager_get_shutdown_type ()

        1 0x000055811701a12c in ()

        2 0x00007ff5ca8318ac in () at /usr/lib/libgio-2.0.so.0

        3 0x00007ff5ca83a4d6 in () at /usr/lib/libgio-2.0.so.0

        4 0x00007ff5ca7d8a64 in () at /usr/lib/libgio-2.0.so.0

        5 0x00007ff5ca7dc5b9 in () at /usr/lib/libgio-2.0.so.0

        6 0x00007ff5ca835fb4 in () at /usr/lib/libgio-2.0.so.0

        7 0x00007ff5ca7d8a64 in () at /usr/lib/libgio-2.0.so.0

        8 0x00007ff5ca7d8a99 in () at /usr/lib/libgio-2.0.so.0

        9 0x00007ff5ca5f43e5 in g_main_context_dispatch () at

        /usr/lib/libglib-2.0.so.0

        10 0x00007ff5ca648749 in () at /usr/lib/libglib-2.0.so.0

        11 0x00007ff5ca5f3a63 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0

        12 0x00007ff5cadf386f in gtk_main () at /usr/lib/libgtk-3.so.0

        13 0x0000558117014177 in main ()

        On Mon, Sep 27, 2021 at 3:29 AM dbtx ilostmyfiles@users.sourceforge.net
        wrote:

        It was X which dumped core, not Yoshimi. I thought Yoshimi never did
        anything at all directly to an X server (that's crazy!) -- so my first
        guess is that arch's X or FLTK package has a problem and Yoshimi is just
        the one finding it.

        OP, there aren't many options but can you try messing around with
        something else like Rakarrack http://rakarrack.sourceforge.net/? What
        version of FLTK is installed? Are you able to try with older versions of
        that and (separately) another version of Yoshimi?

        Status: open
        Group: Unknown
        Created: Sat Sep 25, 2021 02:21 AM UTC by Mike Grammes
        Last Updated: Mon Sep 27, 2021 05:51 AM UTC
        Owner: nobody
        Attachments:

        -
        core.Xorg.1000.c981d61413b04175a99a7a179f14633b.471230.1632535274000000.zst
        https://sourceforge.net/p/yoshimi/bugs/37/attachment/core.Xorg.1000.c981d61413b04175a99a7a179f14633b.471230.1632535274000000.zst
        (3.7 MB; application/zstd)

        I have been trying to play with Yoshimi. After awhile and with no
        discernible repetitive reason it causes a I/O error for X and crashes X
        causing be to go back to my login. I cannot find more info in either xlog
        or using journalctl. However I do have the most recent core dump.

        Sent from sourceforge.net because you indicated interest in
        https://sourceforge.net/p/yoshimi/bugs/37/

        To unsubscribe from further messages, please visit
        https://sourceforge.net/auth/subscriptions/

         

        Related

        Bugs: #37

        alternate

        • Mike Grammes

          Mike Grammes - 2021-09-27

          Apparently the version of yoshimi isn't making core dumps. When I use
          coredump_ctl it lists yoshimi as faulting but no coredump available. It was
          at the same time as the Xorg.

          On Mon, Sep 27, 2021 at 11:19 AM Mike G mike.grammes@gmail.com wrote:

          Here is the output requested:

          Program terminated with signal SIGSEGV, Segmentation fault.

          0 0x0000558117027290 in xfsm_manager_get_shutdown_type ()

          [Current thread is 1 (Thread 0x7ff5cb3cb980 (LWP 31555))]
          (gdb) bt

          0 0x0000558117027290 in xfsm_manager_get_shutdown_type ()

          1 0x000055811701a12c in ()

          2 0x00007ff5ca8318ac in () at /usr/lib/libgio-2.0.so.0

          3 0x00007ff5ca83a4d6 in () at /usr/lib/libgio-2.0.so.0

          4 0x00007ff5ca7d8a64 in () at /usr/lib/libgio-2.0.so.0

          5 0x00007ff5ca7dc5b9 in () at /usr/lib/libgio-2.0.so.0

          6 0x00007ff5ca835fb4 in () at /usr/lib/libgio-2.0.so.0

          7 0x00007ff5ca7d8a64 in () at /usr/lib/libgio-2.0.so.0

          8 0x00007ff5ca7d8a99 in () at /usr/lib/libgio-2.0.so.0

          9 0x00007ff5ca5f43e5 in g_main_context_dispatch () at

          /usr/lib/libglib-2.0.so.0

          10 0x00007ff5ca648749 in () at /usr/lib/libglib-2.0.so.0

          11 0x00007ff5ca5f3a63 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0

          12 0x00007ff5cadf386f in gtk_main () at /usr/lib/libgtk-3.so.0

          13 0x0000558117014177 in main ()

          On Mon, Sep 27, 2021 at 3:29 AM dbtx ilostmyfiles@users.sourceforge.net
          wrote:

          It was X which dumped core, not Yoshimi. I thought Yoshimi never did
          anything at all directly to an X server (that's crazy!) -- so my first
          guess is that arch's X or FLTK package has a problem and Yoshimi is just
          the one finding it.

          OP, there aren't many options but can you try messing around with
          something else like Rakarrack http://rakarrack.sourceforge.net/? What
          version of FLTK is installed? Are you able to try with older versions of
          that and (separately) another version of Yoshimi?

          Status: open
          Group: Unknown
          Created: Sat Sep 25, 2021 02:21 AM UTC by Mike Grammes
          Last Updated: Mon Sep 27, 2021 05:51 AM UTC
          Owner: nobody
          Attachments:

          -
          core.Xorg.1000.c981d61413b04175a99a7a179f14633b.471230.1632535274000000.zst
          https://sourceforge.net/p/yoshimi/bugs/37/attachment/core.Xorg.1000.c981d61413b04175a99a7a179f14633b.471230.1632535274000000.zst
          (3.7 MB; application/zstd)

          I have been trying to play with Yoshimi. After awhile and with no
          discernible repetitive reason it causes a I/O error for X and crashes X
          causing be to go back to my login. I cannot find more info in either xlog
          or using journalctl. However I do have the most recent core dump.

          Sent from sourceforge.net because you indicated interest in
          https://sourceforge.net/p/yoshimi/bugs/37/

          To unsubscribe from further messages, please visit
          https://sourceforge.net/auth/subscriptions/

           

          Related

          Bugs: #37

          alternate

  • dbtx

    dbtx - 2021-09-27

    That's unexpected and interesting. Of course Yoshimi has nothing to do with GTK but XFCE does. In your coredumps you can see the only mentions of Yoshimi are in what look exactly like window titles including Firefox viewing the wiki. I also see some GL shader source which gives me an idea-- are you using XFCE's desktop compositor? If yes, does it help to switch it off?

     

  • Will Godfrey

    Will Godfrey - 2021-09-27

    It's been suggested to me that this might in fact be some kind of XFCE issue, and that it would be worth trying a different window manager to see if the same problem occurs.
    I usually have Openbox running (it's very lightweight) but there also things like KWin, Fluxbox. IceWM.

    You should be able to grab any of these quite easily from Arch.

    Are you running an Nvidea card? These are often known to have various obscure issues.

    There is a lot of detail in Yoshimi's windows so this could be triggering bugs in a borderline setup.

     

    • Will Godfrey

      Will Godfrey - 2021-10-21

      Not heard anything more from the O/P for a long time. I'll leave it another
      week or so, and if there is still no response I'll assume the problem has been
      solved and close this issue.

      --
      Will J Godfrey
      https://willgodfrey.bandcamp.com/
      http://yoshimi.github.io
      Say you have a poem and I have a tune.
      Exchange them and we can both have a poem, a tune, and a song.

       

  • Will Godfrey

    Will Godfrey - 2021-11-03

    Still heard nothing from the O/P so I'm closing this

     

  • Will Godfrey

    Will Godfrey - 2022-02-05
    • status: open --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB