CrashPlan client closes in some Linux installations

From ThinkServer
Revision as of 03:49, 11 March 2014 by Sam (talk | contribs) (→‎Wordaround: Example changed to reflect current file)

Affects

CrashPlan Client 3.5.3 - 3.6.3

openSUSE 13.1

Linux, running GNOME 3, have GNOME 3 repositories added, and/or have installed libwebkitgtk-dev

Summary

The desktop client fails to launch. The splash screen appears for a second or two, and then disappears without error.

Diagnosis

The ui_output.log file within usr/local/crashplan/log (for openSUSE) displays: 

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f63996d46b8, pid=25311, tid=140066076751616
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libgobject-2.0.so.0+0x1a6b8]  g_object_get_qdata+0x18
#
# 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_pid25311.log
Compiled method (nm)   14457  192     n       org.eclipse.swt.internal.gtk.OS::_g_object_get_qdata (native)
 total in heap  [0x00007f63a10f1210,0x00007f63a10f1590] = 896
 relocation     [0x00007f63a10f1330,0x00007f63a10f1390] = 96
 main code      [0x00007f63a10f13a0,0x00007f63a10f1590] = 496
Compiled method (nm)   14457  192     n       org.eclipse.swt.internal.gtk.OS::_g_object_get_qdata (native)
 total in heap  [0x00007f63a10f1210,0x00007f63a10f1590] = 896
 relocation     [0x00007f63a10f1330,0x00007f63a10f1390] = 96
 main code      [0x00007f63a10f13a0,0x00007f63a10f1590] = 496
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Root Cause

This is a bug in libsoup:

Wordaround

  1. Edit ./crashplan/bin/run.conf
  2. Navigate to the end of the GUI_JAVA_OPTS section
  3. Add this line, inside the quotes:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
  • Example:
SRV_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx1024m -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false"
GUI_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanDesktop -DappBaseName=CrashPlan -Xms20m -Xmx512m -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false -Dorg.eclipse.swt.browser.DefaultType=mozilla"

After saving the file, the CrashPlan Desktop should launch properly.

For more information

This article was taken from the Code42 CrashPlan forums and has been slightly ammended to work with openSUSE 13.1 where I'm having the problem. Has been tested and works.

Original website: https://helpdesk.code42.com/entries/24395528-CrashPlan-client-closes-in-some-Linux-installations

Retrieved from ‘https://thinkserver.freddythechick.net/index.php?title=CrashPlan_client_closes_in_some_Linux_installations&oldid=204’