Hello,
The Elementary school that we support recently acquired a FlashForge 3D Printer. The software for it is called FlashPrint and can be downloaded for Ubuntu 32/64 bit here: http://www.flashforge.com/support-center/finder/
When I installed it on our Ubuntu 16.04 Mate, we get a strange graphical bug every time the application is launched. The top left of the screen is covered by a large transparent square, that takes up approx. 20% of the screen.
See here: https://cloud.hermon.net/index.php/s/NnAF7nVEdJjKLk8
The square persists across workspaces until the application is closed. The issue does not appear in Unity, so I hope there is some library or package that I need in order to install for compatibility. Any thoughts? I know this isn’t really a MATE problem, but I thought some other people may have had similar issues with other applications.
Launching the application from the command line does not show any glaring errors or anything on either Unity or Mate. The Unity version does include more output, something about sending the window to a &Home location. I will add the output to this post later, when I head back to the site. I also know FlashPrint makes use of Qt, if that helps.
Any help would be appreciated,
Thank you
Hello
How did you handle the installation part?
I can't reproduce the square on a 17.04 VM, and FYI I had to install these packages before installing the .deb file from the website:
sudo apt install libudev-dev libqt5opengl5 libqt5xml5
I did have to install libudev-dev, the other two packages were already installed. I have tried using the graphical gdebi package installer, and at the console with dpkg.
The console output when launching FlashPrint from the command line in Mate is:
Begin Initialize Scene!
Begin Initialize Shader!
Success Initialize Shader!
Success Initialize Scene!
Scene, viewport(0, 0, 1350, 858)
Scene, viewport(0, 0, 1364, 872)
And in Unity it is:
Begin Initialize Scene!
Begin Initialize Shader!
Success Initialize Shader!
Success Initialize Scene!
appmenu-qt: registerWindow 206 "&Homing"
Scene, viewport(0, 0, 1425, 833)
Scene, viewport(0, 0, 1438, 846)
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"
Also, I just noticed that we are on Mate 1.12.1, while the newest version available seems to be 1.18, so I will be trying that next.
I tried the PPA with Mate 1.16.2, and the issue still persists.
I tried an install on MATE 17.04 today, and the issue still persists. I tested it in a XenServer VM and on the physical device (a Lenovo T420 with Intel Graphics). I also tried an install of Ubuntu Gnome 16.04, and it did not have the issue in regular or classic mode.
Any other thoughts? Whats killing me, is I can’t seem to find any log or way to identify the problem, at all.
When you did your VM test, was it a 64 bit version? Not sure what else it can be. I tested using the 64 bit, specifically this file:
$ md5sum 20170502143307_422.deb
698a9fdac14942a914d848f2712e7f58 20170502143307_422.deb
(That’s FlashPrint#3.16.2)
It was the 64-bit version, and the md5sum matches. I did check the boxes to automatically update Ubuntu and install the 3rd party packages during the install process. Were you running a fully updated version of Ubuntu Mate 17.04?
Yes, as far as I can tell the only thing that’s different in my setup is the Hypervisor, I’m using VirtualBox instead of XenServer
I tried Mate 16.04 in a VM again, and found that it works inconsistently. That may be where we are running into our differences. I launched the application roughly 20 times, and only ran into the transparent square bug twice.
I also noticed that on this fresh install of Mate 1604, when FlashPrint is launched it goes full screen, covering the normal Ubuntu/Mate application bar at the top and bottom of the screen. When I launch FlashPrint on our production computers, it opens in a window instead of full screen, and the transparent square bug happens every time it is launched.
This would indicate that the problem is some software we have installed after the plain Ubuntu Mate install. Also of note, in our production environment we use the base Ubuntu 16.04 repository, and use a preseed file to install ubuntu-mate-core and ubuntu-mate-desktop.