FS#46660 - [geogebra] crash on startup

Attached to Project: Community Packages
Opened by Matteo De Carlo (Portaloffreedom) - Sunday, 11 October 2015, 14:11 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 12 October 2015, 17:03 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The program crashes on startup. It probably has to do with an updated library.
This is the top of the error log from the program:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f35ca062be0, pid=7357, tid=139869019891456
#
# JRE version: Java(TM) SE Runtime Environment (8.0_60-b27) (build 1.8.0_60-b27)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.60-b23 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libGLdispatch.so.0+0x150be0]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited"
before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#

--------------- T H R E A D ---------------

Current thread is native thread

siginfo: si_signo: 11 (SIGSEGV), si_code: 2 (SEGV_ACCERR), si_addr: 0x00007f35ca062be0




Additional info:
* package version to the latest version non testing
* since the error is mentioning GL, I should probably point out that I'm using the official nvidia driver v355.11-1


Steps to reproduce:
- start the program, it crashes every time
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 12 October 2015, 17:03 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#46619 

With no response, I'm going to make the assumption. Request reopen if I'm wrong.
Comment by Doug Newgard (Scimmia) - Sunday, 11 October 2015, 14:56 GMT
Duplicate of  FS#46619 ?
Comment by Matteo De Carlo (Portaloffreedom) - Sunday, 11 October 2015, 16:51 GMT
Forgot about it, I confirm that I'm using Oracle JVM
Comment by Doug Newgard (Scimmia) - Sunday, 11 October 2015, 17:00 GMT
So does the new glib2 package in testing fix it?

Loading...