Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Release date for V19 for Linux

2»

Comments

  • edited June 2019

    @Knut Hohenberg said:
    Anybody getting pdf to work in 19.2.10 (x64)?
    The pdf command just returns "Error loading module for PDF underlay support." on my ubuntu 16.04 box.

    Same here on Manjaro, MX Linux and Elementary. No PDF.
    I think it is not yet included, like RFA import.

  • edited June 2019

    Looks like the newest DEB Installer also runs and integrates fine under MX Linux too.
    (19.0.1 Kernel/XFCE Desktop)

  • The pdf-module (PDFiumModule.tx) is included in V19.2.10, but its size has dropped from 5 Mb in V19.2.04 (beta) to roughly 500Kb, which looks suspicious. Replacing the file with the older version makes the pdf window come up, but BricsCAD then crashes when you dismiss the dialog. So I guess we'll have to wait for a corrected build... meanwhile, I downgraded to V19.2.04, which luckily is absolutely painless on Linux.

  • Unfortunately ...
    Suse Tumbleweed is a bit tricky for me in general.
    It did not recognize my old 30" Cinema Display here.
    Meanwhile I have access to my 4K Dell Monitor and
    I could finally start my Suse Tumbleweed again.
    Wanted to test Bricscad RPM installer ....
    Unfortunately I did months of updates before and
    after restarting It will only present a Terminal.
    (unfortunately for both, old and new Kernel and save boot options)

  • So, Tumbleweed healed from NVidia issues.
    I installed Bricscad's RPM as a PPA fine.
    It is included in Start Menu, starts fine and runs well.

    One issue I see in Linux like Manjaro or Tumbleweed,
    not 100% sure but not on Ubuntu DEB Linux (Elementary, MX Linux),
    that when doing things like BIMDRAG,
    I am not able to switch the reference face of DYNDIM by "TAB".

    GTK2 issue or KDE vs Gnome or XCFE ?

    And in Tumbleweed I may still miss some (GTK ?) dependencies
    which I already installed later on Manjaro,
    As the Quad behaves a bit strange and the DM Options Panel in
    Drawing View looks like an old Text Box like the Prompt Window.
    No Icons.

  • edited June 2019

    In general I am pretty pleased by Bricscad v19 running on Linux.
    At least on Debian based Linux, for me, it is at least on par with
    Bricscad on macOS.

  • There has been an update to PDFium during V19.2, resulting in a newly added library file that was missing in the installer.
    I published an installer update V19.2.10-3.
    PDFATTACH now works, but only if the pdf cache is disabled (set PDFCACHE to 0).

  • For a very short moment I thought - hey, PDF will work for me even with PDFCACHE ON ;)

    But you are right, PDFCACHE should be off ...
    Thanks !

  • edited June 2019

    I do have some smaller issues on Linux similar to Mac,
    which I don't see on Windows.
    like :
    - some strange behavior in Structure Tree with large files
    - similar blinking of GUI after saving customizations
    - no RFA import

    But somehow less distinct than on Mac.
    (old D700s on Mac vs RTX 2070 on Linux ?)

  • Do other users find their REDSDK Render Material Libraries ?

    (those which you have to download first)

    The Path it points to in "VAR" has folders but no data inside.

    The Path to image Textures was wrong too. As it pointed
    to a v18 installation that is no more existing.
    But v19 seems to use completely different paths and
    locations now anyway.

  • ^ I think in Ubuntu Distributions Material Library works fine (?)
    At least I copied the RenderMaterials Folder over to my other
    Installations.
    Not quite true as it is too hard for me to copy things in a "Var" Folder.
    I think that would only work in terminal by sudo and adding some switches (?)
    I was even not able to bring thing into Var from a File Manger
    in Admin Mode.
    So I duplicated Material Folder to a separate Disk and tried to
    point the Settings Paths to it. Did not work for me so far either.

    Overall it works ok on Linux.
    When working with linear Solids,
    (Moving, Copying, Mirroring , Rotating, Connecting structural or standard),
    I though BC Linux would be less stable and often crashed.
    But I see the same happens with Mac and Windows too.

    And I fight a bit having Blocks still existing, although without any content
    as Solids were stolen by "Recover" or "Audit".
    (Why does it always delete especially those elements which I am most interested in ....)

  • So, now that Testing Period ended,
    I can activate my Bricscad BIM Linux on any installation - except Manjaro (!?)

    I always get that (not yet explained in Knowledge Base) error :

    "No rehostable hostid top-level dir. (Error code -148)"

    image

    ACTIVATION.png
    745 x 390 - 30K
  • Had this one once a long time ago.
    Reason then was that the /var/tmp/bricsys folder was not writable.

  • @Knut Hohenberg Thanks! It did not occur to me

  • edited July 2019

    @Knut Hohenberg said:
    Had this one once a long time ago.
    Reason then was that the /var/tmp/bricsys folder was not writable.

    I read this in another KB article and already tried to give the whole
    /var/temp (and /opt/bricscad) writing rights to all users.
    That did not help.

    Maybe I did it wrong.

    BTW what is that "Sticky" thing for access rights ?
    Did not activate but saw it used for other Folders that allow all users.

  • On my box, /var/tmp/bricsys is a symbolic link to /var/bricsys, but this has been set up when installing V16, so might well look different on a computer that has no previous version of BricsCAD installed (see listing below).
    The sticky bit restricts your right to delete files to the ones you own, which makes sense for world-writable folders.
    In that respect, acces rights shown below do not look ideal, but since I am the only user of my laptop, this is of no concern to me.
    `ll /var/tmp/bricsys
    lrwxrwxrwx 1 khad khad 12 Jan 8 2017 /var/tmp/bricsys -> /var/bricsys/

    ll /var/bricsys/
    total 60
    drwxrwxrwx 6 root root 4096 Mär 20 22:26 ./
    drwxr-xr-x 14 root root 4096 Jan 8 2017 ../
    -rw-rw-rw- 1 khad khad 303 Mär 9 2017 BIMV17.lic
    -rw-rw-rw- 1 khad khad 305 Jan 14 2018 BIMV18.lic
    -rw-rw-rw- 1 khad khad 252 Jan 8 2017 BricsCADV16.lic
    -rw-rw-rw- 1 khad khad 308 Mär 9 2017 BricsCADV17.lic
    -rw-rw-rw- 1 khad khad 310 Jan 10 2018 BricsCADV18.lic
    -rw-rw-rw- 1 khad khad 315 Mär 20 22:26 BricsCADV19.lic
    -rw-rw-rw- 1 khad khad 298 Mai 26 2018 BricsCAD_ShapeV18.lic
    -rw-rw-rw- 1 khad khad 250 Jan 14 2017 CommunicatorV17.lic
    -rw-rw-r-- 1 khad khad 0 Jan 8 2017 LicenseManager.cfg
    drwxrwxr-x 5 khad khad 4096 Mai 14 23:13 RenderMaterials/`

  • Thanks Roy,
    I have to look into it again to re-check permissions.

    I was just a bit surprised to get the warning,
    as trial activation on Manjaro was flawless and all other
    DEB or RPM installations activated well.

    As it seams that Bricscad does spread just the same Files and Folders
    to the same places on Arch Linux, like on any other Distros,
    I think a similar kind of installation wizzard for Arch Linux should be
    possible (?) and would be quite useful.

  • @Michael Mayer said:
    So, now that Testing Period ended,
    I can activate my Bricscad BIM Linux on any installation - except Manjaro (!?)

    I always get that (not yet explained in Knowledge Base) error :

    "No rehostable hostid top-level dir. (Error code -148)"

    image

    Solution found in an older thread :

    I had to delete "/var/tmp/bricsys"

  • @Michael Mayer said:
    So, Tumbleweed healed from NVidia issues.
    I installed Bricscad's RPM as a PPA fine.
    It is included in Start Menu, starts fine and runs well.

    One issue I see in Linux like Manjaro or Tumbleweed,
    not 100% sure but not on Ubuntu DEB Linux (Elementary, MX Linux),
    that when doing things like BIMDRAG,
    I am not able to switch the reference face of DYNDIM by "TAB".

    GTK2 issue or KDE vs Gnome or XCFE ?

    And in Tumbleweed I may still miss some (GTK ?) dependencies
    which I already installed later on Manjaro,
    As the Quad behaves a bit strange and the DM Options Panel in
    Drawing View looks like an old Text Box like the Prompt Window.
    No Icons.

    Just FYI: I've created a support ticket for that issue where the TAB key no longer switches faces in V19. The issue has been confirmed by support so hoping to have a fix soon!

  • Yes, read it in my service request.
    Thanks for that.
    I was a bit afraid that wonderful feature would fall over because
    of incompatibility or inconsistency with newer features like
    dynamic grid or such.
    But I hoped as I saw it still in recent Windows version.

  • edited November 2019

    I forget again how to install the Tar Ball on Manjaro.

    I get for
    bricscad.sh :

    [CADVIZMANJARO BRICSCADTEMP]# sudo ./bricscad.sh
    FLYSDKFONTS environment variable could not be correctly defined. #3

    ^C
    [CADVIZMANJARO BRICSCADTEMP]#

    And for shape.sh :

    [CADVIZMANJARO BRICSCADTEMP]# sudo./shape.sh
    bash: sudo./shape.sh: Datei oder Verzeichnis nicht gefunden
    [CADVIZMANJARO BRICSCADTEMP]# sudo ./shape.sh
    FLYSDKFONTS environment variable could not be correctly defined. #3

    (bricscad:8960): Gtk-CRITICAL **: 19:17:20.565: gtk_window_get_has_resize_grip: assertion 'GTK_IS_WINDOW (window)' failed

    Plus some GTStreamer libs missing ....

  • Ah, didn't see that a Window was open for Shape,
    now I got :

    [CADVIZMANJARO BRICSCADTEMP]# sudo ./shape.sh
    FLYSDKFONTS environment variable could not be correctly defined. #3

    (bricscad:8960): Gtk-CRITICAL **: 19:17:20.565: gtk_window_get_has_resize_grip: assertion 'GTK_IS_WINDOW (window)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:27:47.880: gtk_window_get_has_resize_grip: assertion 'GTK_IS_WINDOW (window)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:27:48.267: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gdk-CRITICAL **: 19:27:48.267: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed

    (bricscad:8960): Gdk-CRITICAL **: 19:27:48.267: gdk_window_show_internal: assertion 'GDK_IS_WINDOW (window)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:27:48.267: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:27:48.267: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:27:50.873: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gdk-CRITICAL **: 19:27:50.873: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:27:50.873: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:27:50.873: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    *** BUG ***
    In pixman_region32_init_rect: Invalid rectangle passed
    Set a breakpoint on '_pixman_log_error' to debug

    (bricscad:8960): Gtk-CRITICAL **: 19:28:00.963: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gdk-CRITICAL **: 19:28:00.963: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed

    (bricscad:8960): Gdk-CRITICAL **: 19:28:00.963: gdk_window_show_internal: assertion 'GDK_IS_WINDOW (window)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:28:00.963: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:28:00.963: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:28:03.390: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gdk-CRITICAL **: 19:28:03.390: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:28:03.390: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed

    (bricscad:8960): Gtk-CRITICAL **: 19:28:03.390: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
    Beendet

Sign In or Register to comment.
Origami
Origami is the Japanese word for paper folding. ORI means to fold and KAMI means paper and involves the creation of paper forms usually entirely by folding.

Powered by VanillaForums, Designed by Steam