# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xa26a3edd, pid=2198, tid=2816342848
#
# JRE version: OpenJDK Runtime Environment (7.0_51-b31) (build 1.7.0_51-b31)
# Java VM: OpenJDK Client VM (24.51-b03 mixed mode linux-x86 )
# Problematic frame:
# C [libsoup-2.4.so.1+0x56edd] soup_session_feature_detach+0x1d
#
# 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_pid2198.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/usr/bin/vuze : ligne 204 : 2198 Abandon (core dumped)${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.
Une idée?
Dernière modification par mulanee le mer. 09 avr. 2014, 22:13, modifié 1 fois.
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xa26a3edd, pid=2198, tid=2816342848
#
# JRE version: OpenJDK Runtime Environment (7.0_51-b31) (build 1.7.0_51-b31)
# Java VM: OpenJDK Client VM (24.51-b03 mixed mode linux-x86 )
# Problematic frame:
# C [libsoup-2.4.so.1+0x56edd] soup_session_feature_detach+0x1d
#
# 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_pid2198.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/usr/bin/vuze : ligne 204 : 2198 Abandon (core dumped)${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.
J'ai renommé ~/.azureus
Au lancement de Vuze tout semble bien se passer hormis un message d'erreur sur /usr/lib/vuze, problème de droits.
Je change les droits, je relance.
Vuze se lance, essaie de se mettre à jour et crashe encore
Analysing /usr/lib/vuze/hs_err_pid1769.log
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xa2a74edd, pid=1786, tid=2816822080
#
# JRE version: OpenJDK Runtime Environment (7.0_51-b31) (build 1.7.0_51-b31)
# Java VM: OpenJDK Client VM (24.51-b03 mixed mode linux-x86 )
# Problematic frame:
# C [libsoup-2.4.so.1+0x56edd] soup_session_feature_detach+0x1d
#
# 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:
# /usr/lib/vuze/hs_err_pid1786.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
/usr/bin/vuze : ligne 204 : 1786 Abandon (core dumped)${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.
Donner les droits a Vuze pour ce mettre à jour est je trouve dangereux. Personnellement je n'aime pas ce logiciel, mais ce n'est que mon opinion très personnel...
De plus vuze est déjà à jour, la dernière version est bien la 5.3.0
Je n'ai plus le message, j'ai changé les droits.
Il me disait qu'il y avit un problème de droits en écriture.
Normal il était en root/root
je l'ai mis en username/users
Mais au final ça ne marche toujours pas.