MX 17 Repository: The sweethome3d Thread

[mmikeinsantarosa]

Problem description:

In the bottom right window, click on any part of the green icon in the upper left corner. The 3D rendering disappears. Resize the lower right corner window and the 3D rendering reappears.

This behavior is not found in the 5.3 from the standard MX repo.

I just checked the sample I posted and your example in a VM and on my laptop proper and I don't get any similar symptoms.

I am running a newer kernel

Code: Select all

System:    Host: mx17mainlt Kernel: 5.1.0-6.1-liquorix-amd64 x86_64 bits: 64 
           Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum March 14  2018 

And my graphics is also Intel

Code: Select all

Graphics:  Device-1: Intel HD Graphics 530 driver: i915 v: kernel 
           Device-2: AMD Venus LE [Radeon HD 8830M] driver: radeon v: kernel 
           Display: x11 server: X.Org 1.19.2 driver: ati,modesetting,radeon unloaded: fbdev,vesa 
           resolution: 1360x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 18.2.6 

hmmm...

[srq2625]

Well .... I'll try installing MX 18.3 in a VM and see what happens. More later when I have something to report...

[mmikeinsantarosa]

I think I still have the 4.19.0-1-amd64 kernel on my laptop.I can switch kernels and see if it makes a difference.

[srq2625]

I just loaded up a fresh, fully updated MX 18.3, installed SweetHome3D from the Test Repo so that 6.1.2.

Here's an example of what happens to the program interface for me....

SweetHome6.2.png

Here's the system info...

Code: Select all

System:
  Host: mx Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 
  Desktop: Xfce 4.12.3 Distro: MX-18.3_x64 Continuum May 26  2019 
  base: Debian GNU/Linux 9 (stretch) 
Machine:
  Type: Virtualbox System: innotek product: VirtualBox v: 1.2 
  serial: <filter> 
  Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek 
  v: VirtualBox date: 12/01/2006 
Battery:
  ID-1: BAT0 charge: 50.0 Wh condition: 50.0/50.0 Wh (100%) model: innotek 1 
  status: Full 
CPU:
  Topology: Dual Core model: Intel Core i7-4710MQ bits: 64 type: MCP 
  arch: Haswell rev: 3 L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 9977 
  Speed: 2494 MHz min/max: N/A Core speeds (MHz): 1: 2494 2: 2494 
Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 
  bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.2 driver: vmware 
  unloaded: fbdev,modesetting,vesa resolution: 1920x956~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 256 bits) v: 3.3 Mesa 18.2.6 
  direct render: Yes 
Audio:
  Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 
  v: kernel bus ID: 00:05.0 
  Sound Server: ALSA v: k4.19.0-5-amd64 
Network:
  Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI 
  port: d020 bus ID: 00:03.0 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge 
  driver: piix4_smbus v: N/A port: d200 bus ID: 00:07.0 
Drives:
  Local Storage: total: 20.00 GiB used: 5.37 GiB (26.8%) 
  ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 20.00 GiB 
Partition:
  ID-1: / size: 17.56 GiB used: 5.35 GiB (30.5%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 2.00 GiB used: 15.1 MiB (0.7%) fs: swap dev: /dev/sda2 
Sensors:
  Message: No sensors data was found. Is sensors configured? 
Repos:
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://iso.mxrepo.com/antix/stretch stretch main
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
  2: deb http://security.debian.org/ stretch/updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ stretch main non-free
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:
  Processes: 179 Uptime: 10m Memory: 1.95 GiB used: 1.16 GiB (59.6%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 
  inxi: 3.0.33 
  

[mmikeinsantarosa]

Just for grins, try installing the latest liquorix kernel from mxpi and see what happens. Make sure you check boot options in mx tools to confirm you're going to boot to the new kernel then restart.

[mmikeinsantarosa]

I switched my laptop to the older kernel and everything still more or works. I just noticed that instead of using the pointers to move the 3d view around, you can left click and hold on the 3D canvas and do all the rotation stuff, no scaling though. Do you get the same failure moving the 3D canvas?
I did get a sort of failure when I moved either just the 2 little up or down arrows to beyond 0deg up or 90deg down. But clicking back on the canvas returns the image view. It doesn't do this with the 5.3 version. And the other 4 arrows don't seem to have this problem. Is this what you're talking about?

arrows1.png

[srq2625]

I switched my laptop to the older kernel and everything still more or works. I just noticed that instead of using the pointers to move the 3d view around, you can left click and hold on the 3D canvas and do all the rotation stuff, no scaling though. Do you get the same failure moving the 3D canvas?

OK, so I installed the liquorix kernel - no impact/change seen. In the VM, the various windows still have issues as seen above.

You are correct - you can use the mouse to manipulate the 3D image. Scaling is accomplished with the mouse scroll wheel.

I did get a sort of failure when I moved either just the 2 little up or down arrows to beyond 0deg up or 90deg down. But clicking back on the canvas returns the image view. It doesn't do this with the 5.3 version. And the other 4 arrows don't seem to have this problem. Is this what you're talking about?

The above window blackouts (which only seem to be happening in the VM) happen, regardless of how the canvas is manipulated.

I get the "blinking in and out" behavior when I click on any of the pointers in that control. Doesn't happen for every click. In the VM, I have to click on the pointer control to bring the 3D canvas image back. With the canvas image being displayed, clicking on the window of another application (in this instance, FireFox) also causes the 3D canvas to blank.

ETA: Back in the install on bare-metal, it seems that the canvas blanks whenever I click on any pointer in that device. The only way I have found to bring it back is to export the canvas to a separate window and then force a repaint of the canvas window by resizing it or adding a detail to the "design" in the grid.

[mmikeinsantarosa]

did you install all of the sweethome3d set from test? Doubt if it makes a difference but ...

sweet-packages.png

[timkb4cq]

Odd video behavior Confirmed
installed from MX Test repo
I have similar symptoms on Vbox. Panels go black and you have to lower & raise them to get it back. If 3d acceleration is not checked in the VM Graphics settings it won't run at all.

On Nvidia it's better - enough that it's usable, but in the overhead view panel there's incredibly bad tearing/shredding as you move the viewpoint around. It's clear when stopped.

On Radeon it works correctly apart from mouse-wheel scrolling in the item selection pane where a portion of the list stops scrolling at a random spot and the part of the window under that continues to scroll. Makes it hard to navigate the lists.

Overall, not a great release...

[mmikeinsantarosa]

I just tried an install from test on my desktop and the new version doesn't play well at all. The fonts are unreadable so debian must have pulled some depends. After removing the one from test then installing the one from main, sweethome3d works fine. Then after upgrading to the one from test, the fonts are fixed but sweethome3d has issues. I have something to chase now. - mike