libgl1-mesa-dri

[mathojojo]

Everytime I try to start Sweethome 3D, the interface appear and then directly crashes !

When I launch it in Terminal, I get this :

Java 3D: implicit antialiasing enabled
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f70066de823, pid=1667, tid=140119133419264
#
# JRE version: OpenJDK Runtime Environment (8.0_03-b03) (build 1.8.0_03-Ubuntu-8u77-b03-3ubuntu3-b03)
# Java VM: OpenJDK 64-Bit Server VM (25.03-b03 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [radeonsi_dri.so+0x256823]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1667.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)

As mentionned, radeonsi-dri.so may have a problem. It's an important bug, as we can't install the proprietary fglrx drivers on ubuntu 16.04.

my system : kubuntu 16.04 64bit / AMD Phenom(tm) II X6 1090T Processor / 8Go RAM / RADEON HD 7750 (no propretary drivers installed, as they are not available anymore in 16.04)
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: KDE 16.04
InstallationDate: Installed on 2016-04-25 (3 days ago)
InstallationMedia: neon 16.04 "Xenial" - Build amd64 LIVE Binary 20160419-23:13
Package: sweethome3d 4.5+dfsg-3 [origin: Ubuntu]
PackageArchitecture: all
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Tags: xenial third-party-packages
Uname: Linux 4.4.0-21-generic x86_64
UnreportableReason: This is not an official KDE package. Please remove any third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[dino99 (9d9)]

The ubuntu version is quite old. Maybe test with the now published 5.2

https://sourceforge.net/projects/sweethome3d/files/SweetHome3D/SweetHome3D-5.2/SweetHome3D-5.2-linux-x64.tgz/download

[mathojojo (mathojojo)]

I already did. In fact, I downloaded the newest Sweet home3D a month ago. It was maybe not the 5.2, but if not, it must have been the 5.1.

And, as written in my first post, the error output is coming from Java, not Sweethome3D.

But I will do a test with the 5.2 like you suggested, just to be sure.

[dino99 (9d9)]

In case you are using some ppa's packages, it can be also a conflict.

That report has not much details: you should have ran the crash file to give dev a chance to find the real issue. Please join it if you can get an other crash (with the sweethome3d version) or at least run: apport-collect 1576092

[mathojojo (mathojojo)]

apport information

[mathojojo (mathojojo)]

apport information

[mathojojo (mathojojo)]

apport information

[mathojojo (mathojojo)]

I had no ppa repository configured, I'm using a fresh install of Ubuntu.

The apport is about the Ubuntu package of Sweethome3D (4.5). And just looked the newest version I tested : it's the 5.2, and I have exactly the same problem with the 5.2.

[dino99 (9d9)]

is that issue still exist ?

[Lars Steinke (lss)]

Yep, the issue still persists (see https://bugs.launchpad.net/ubuntu/+source/sweethome3d/+bug/1576076 as well):
$ sweethome3d
Java 3D: implicit antialiasing enabled
Gtk-Message: Failed to load module "canberra-gtk-module"
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f69503a8823, pid=4159, tid=0x00007f6950f91700
#
# JRE version: OpenJDK Runtime Environment (8.0_111-b14) (build 1.8.0_111-8u111-b14-2ubuntu0.16.04.2-b14)
# Java VM: OpenJDK 64-Bit Server VM (25.111-b14 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [radeonsi_dri.so+0x256823]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid4159.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Abgebrochen (Speicherabzug geschrieben)