FREE, FAST SHIPPING IN THE U.S.
CUSTOMER SERVICE +1 (949) 613-5838

MatterControl 1.7.0 on Linux - Can't open a file to load - No file dialog


  • Hi, Just installed MatterControl onto a Linux machine I have for printing. Have been using RepetierHost & Slic3r previously.

    Installed all ok, up and running, printed calibration cube, which was showing after install, as a test, all good.

    Went to add another object into the queue with any of the Add buttons for menu drop down and no dialog appears to allow the selection of a file.
    Run as user or as root, same issue (thought it might have been a perms issue top open the dialog).

    Version installed is 1.7.0 on Ubuntu 16.04.1 LTS.

    Any help would be gratefully received.

    TIA.

    A.


  • 8
    Posts
    569
    Views
    Log in to reply


  • Can you run MatterControl from a terminal and see if any messages are printed when you hit the Add button?



  • Sorry for the slow response on this. Been busy.
    Nothing extra appears in the terminal when pushing the add button, just a start up notice about waiting for a connection on port 52799, then a 'Connected to a device channel' followed by a long string of alphanumeric characters, followed by a 'Connected to user channel' and another long string of alphanumeric characters. That's it until MatterControl is exitied and a prompt is returned back in the console.



  • Sometimes the dialog opens up underneath the main window, so it is hidden at first. Can you check and make sure this isn't the case?



  • I'm having the same problem. The dialog is not hidden, it's not even opening. When running from a terminal, here's what I get when I click on Add:

    (process:23581): GLib-GObject-CRITICAL **: /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init()

    (process:23581): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

    (process:23581): GLib-GObject-CRITICAL **: /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init()

    (process:23581): GLib-GObject-CRITICAL **: /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init()

    (process:23581): GLib-GObject-CRITICAL **: /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init()

    (process:23581): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

    (process:23581): GLib-GObject-CRITICAL **: /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init()

    (process:23581): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed

    (process:23581): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

    (process:23581): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

    (process:23581): GLib-GObject-CRITICAL **: /build/buildd-glib2.0_2.33.12+really2.32.4-5-i386-eISom6/glib2.0-2.33.12+really2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init()
    ^C

    At that point I had to hit Control-C as the program was locked up.




  • @michvhf, what distro are you on?



  • Hi

    The same on my linux box.

    Nothing appear after clicking "add" button.

    And no output on console.

    Linux Mint 18.1 Serena


    Best regards.

    Kura.




  • @unlimitedbacon Debian Wheezy 7.1. I also have it running on another machine (Debian 8.8) and it runs fine except if you need to flip the part over it won't come out of edit mode and it doesn't save - even tho it says it did. The file that was queued also disappears when you hit save.


8
Posts
569
Views
Log in to reply