Bug#821135: Reassign openjdk-8-jre: Fails to start over ssh connection (Was: Bug#821135: imagej: Crash running imagej)

2016-04-18 Thread Andreas Tille 
reassign 821135 openjdk-8-jre
thanks

Hi,

it turns out that imagej and freecol - both openjdk based application
fail to start via ssh connection.  Thus I'm reassigning the problem to
openjdk.

Kind regards

   Andreas.

On Mon, Apr 18, 2016 at 11:27:31AM +0200, Sebastien Jodogne wrote:
> >Thanks for this additional information.  Could you possibly verify this
> >by starting some other openjdk based application?
> 
> Thanks for confirming the reproducibility of this issue with imagej.
> 
> Fortunately, this crash does not seem to occur when launching LibreOffice
> (that also depends on openjdk-8-jre). However, I was able to reproduce it
> with freecol (a free clone of the Colonization game available in Debian):
> 
> 
> >
> jodogne@unstable:~$ sudo apt-get install freecol
> jodogne@unstable:~$ freecol
> Disabling IPV6 network stack to work around bug #560056 on openjdk
> If you experience problems with connecting to remote servers,
> you can put it back by running Freecol this way:
>   freecol --enable-ipv6
> OpenJDK 64-Bit Server VM warning: Using incremental CMS is deprecated and
> will likely be removed in a future release
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7f29bd127a8a, pid=6559, tid=139818483369728
> #
> # JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build
> 1.8.0_77-Debian-8u77-b03-3+b1-b1)
> # Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64
> compressed oops)
> # Problematic frame:
> # C  [libatk-bridge-2.0.so.0+0x10a8a]
> #
> # 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:
> # /home/jodogne/hs_err_pid6559.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
> <
> 
> 
> FreeCol also crashes if invoked from ssh, but runs fine within a window
> manager.
> 
> As a conclusion, we have at least two totally unrelated packages (imagej and
> freecol) that both crash if invoked from ssh. This most probably indicates
> that this issue should rather be filed against the "openjdk-8-jre" package.
> 
> HTH,
> Sébastien-
> 
> 

-- 
http://fam-tille.de

Bug#821135: Bug#821135: imagej: Crash running imagej

2016-04-18 Thread Sebastien Jodogne 

Thanks for this additional information.  Could you possibly verify this
by starting some other openjdk based application?


Thanks for confirming the reproducibility of this issue with imagej.

Fortunately, this crash does not seem to occur when launching 
LibreOffice (that also depends on openjdk-8-jre). However, I was able to 
reproduce it with freecol (a free clone of the Colonization game 
available in Debian):



>
jodogne@unstable:~$ sudo apt-get install freecol
jodogne@unstable:~$ freecol
Disabling IPV6 network stack to work around bug #560056 on openjdk
If you experience problems with connecting to remote servers,
you can put it back by running Freecol this way:
  freecol --enable-ipv6
OpenJDK 64-Bit Server VM warning: Using incremental CMS is deprecated 
and will likely be removed in a future release

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7f29bd127a8a, pid=6559, tid=139818483369728
#
# JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build 
1.8.0_77-Debian-8u77-b03-3+b1-b1)
# Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64 
compressed oops)

# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0x10a8a]
#
# 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:
# /home/jodogne/hs_err_pid6559.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
<


FreeCol also crashes if invoked from ssh, but runs fine within a window 
manager.


As a conclusion, we have at least two totally unrelated packages (imagej 
and freecol) that both crash if invoked from ssh. This most probably 
indicates that this issue should rather be filed against the 
"openjdk-8-jre" package.


HTH,
Sébastien-

Bug#821135: Bug#821135: imagej: Crash running imagej

2016-04-18 Thread Andreas Tille 
Hi Sebastien,

On Mon, Apr 18, 2016 at 10:13:15AM +0200, Sebastien Jodogne wrote:
> Hello,
> 
> After further investigation, this crash only occurs when I invoke imagej
> through ssh (with the "-Y" flag).
> 
> If I run imagej within some window manager (e.g. XFCE), everything goes
> fine.
> 
> As a consequence, this looks more like a problem within openjdk.

Thanks for this additional information.  Could you possibly verify this
by starting some other openjdk based application?

At least I can confirm that if I start imagej on a remote host via ssh
I also get:

$ imagej *.jpg
Open other images in this ImageJ panel as follows:
  imagej -p 1  [ ... ]

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7f2a63ddba8a, pid=6325, tid=139821744850688
#
# JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build 
1.8.0_77-Debian-8u77-b03-3+b1-b1)
# Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64 compressed 
oops)
# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0x10a8a]
#
# 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:
# /home/andreas/hs_err_pid6325.log

So this seems to be reproducible at least.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#821135: [Debian-med-packaging] Bug#821135: imagej: Crash running imagej

2016-04-18 Thread Sebastien Jodogne 

Hello,

After further investigation, this crash only occurs when I invoke imagej 
through ssh (with the "-Y" flag).


If I run imagej within some window manager (e.g. XFCE), everything goes 
fine.


As a consequence, this looks more like a problem within openjdk.

Sébastien-


On 04/16/2016 09:55 AM, Sébastien Jodogne wrote:

As a complement, you will find the full log attached to this post.

HTH,
Sébastien-

On Fri, Apr 15, 2016 at 10:27 PM, Sebastien Jodogne > wrote:

Package: imagej
Version: 1.50i+dfsg-1
Severity: important

Dear Maintainer,

When I try and run the ImageJ package from Debian Sid, I currently
get the following crash:

 >
jodogne@unstable:~$ rm -rf .imagej
jodogne@unstable:~$ imagej
Open other images in this ImageJ panel as follows:
imagej -p 1  [ ... ]

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7fe91d03ba8a, pid=1262, tid=140639753193216
#
# JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build
1.8.0_77-Debian-8u77-b03-3+b1-b1)
# Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0x10a8a]
#
# 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:
# /home/jodogne/hs_err_pid1262.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.
#
/usr/bin/imagej: line 427:  1262 Aborted
/usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java -d64 -mx474m -cp
/usr/share/java/ij.jar ij.ImageJ -ijpath /home/jodogne/.imagej -port1
<

This crash makes the imagej package totally unusable to me.

I have removed and purged all the JRE and JDK packages before making
a fresh installation of imagej, but the crash is still there.

I thank you in advance for taking this problem into consideration!

Bug#821135: imagej: Crash running imagej

2016-04-16 Thread Sébastien Jodogne 
As a complement, you will find the full log attached to this post.

HTH,
Sébastien-

On Fri, Apr 15, 2016 at 10:27 PM, Sebastien Jodogne 
wrote:

> Package: imagej
> Version: 1.50i+dfsg-1
> Severity: important
>
> Dear Maintainer,
>
> When I try and run the ImageJ package from Debian Sid, I currently get the
> following crash:
>
> >
> jodogne@unstable:~$ rm -rf .imagej
> jodogne@unstable:~$ imagej
> Open other images in this ImageJ panel as follows:
>imagej -p 1  [ ... ]
>
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x7fe91d03ba8a, pid=1262, tid=140639753193216
> #
> # JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build
> 1.8.0_77-Debian-8u77-b03-3+b1-b1)
> # Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64
> compressed oops)
> # Problematic frame:
> # C  [libatk-bridge-2.0.so.0+0x10a8a]
> #
> # 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:
> # /home/jodogne/hs_err_pid1262.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.
> #
> /usr/bin/imagej: line 427:  1262 Aborted
> /usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java -d64 -mx474m -cp
> /usr/share/java/ij.jar ij.ImageJ -ijpath /home/jodogne/.imagej -port1
> <
>
> This crash makes the imagej package totally unusable to me.
>
> I have removed and purged all the JRE and JDK packages before making a
> fresh installation of imagej, but the crash is still there.
>
> I thank you in advance for taking this problem into consideration!
>
> Regards,
> Sebastien-
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set
> LC_ALL to default locale: No such file or directory
> UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages imagej depends on:
> ii  default-jre  2:1.8-57
>
> imagej recommends no packages.
>
> imagej suggests no packages.
>
> -- debconf information:
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = "en_US:en",
> LC_ALL = (unset),
> LC_TIME = "fr_BE.UTF-8",
> LC_MONETARY = "fr_BE.UTF-8",
> LC_ADDRESS = "fr_BE.UTF-8",
> LC_TELEPHONE = "fr_BE.UTF-8",
> LC_NAME = "fr_BE.UTF-8",
> LC_MEASUREMENT = "fr_BE.UTF-8",
> LC_IDENTIFICATION = "fr_BE.UTF-8",
> LC_NUMERIC = "fr_BE.UTF-8",
> LC_PAPER = "fr_BE.UTF-8",
> LANG = "en_US.UTF-8"
> are supported and installed on your system.
> perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
> locale: Cannot set LC_ALL to default locale: No such file or directory
>



-- 
Sébastien Jodogne
Mail: s.jodo...@gmail.com
Web: http://www.sjodogne.be/
Twitter: https://twitter.com/sjodogne
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7fe91d03ba8a, pid=1262, tid=140639753193216
#
# JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build 1.8.0_77-Debian-8u77-b03-3+b1-b1)
# Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0x10a8a]
#
# 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
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

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

Current thread (0x7fe938009800):  JavaThread "main" [_thread_in_native, id=1263, stack(0x7fe93e77c000,0x7fe93e87d000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0038

Registers:
RAX=0x, RBX=0x7fe9268d9f78, RCX=0x0003, RDX=0x7fe9382854c0
RSP=0x7fe93e87b3d0, RBP=0x7fe93e87b3f0, RSI=0x, RDI=0x7fe9382854c0
R8 =0x7fe938285630, R9 =0x0020, R10=0x0187, R11=0x7fe91d03bdd7
R12=0x, R13=0x7fe9268d9f78, R14=0x7fe93e87b4b0, R15=0x7fe938009800
RIP=0x7fe91d03ba8a, EFLAGS=0x00010202, CSGSFS=0x43440033, ERR=0x0004
  TRAPNO=0x000e

Top of Stack: (sp=0x7fe93e87b3d0)
0x7fe93e87b3d0:   7fe9382854c0 7fe9382854c0

Bug#821135: imagej: Crash running imagej

2016-04-15 Thread Sebastien Jodogne 
Package: imagej
Version: 1.50i+dfsg-1
Severity: important

Dear Maintainer,

When I try and run the ImageJ package from Debian Sid, I currently get the 
following crash:

>
jodogne@unstable:~$ rm -rf .imagej
jodogne@unstable:~$ imagej
Open other images in this ImageJ panel as follows:
   imagej -p 1  [ ... ]

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7fe91d03ba8a, pid=1262, tid=140639753193216
#
# JRE version: OpenJDK Runtime Environment (8.0_77-b01) (build 
1.8.0_77-Debian-8u77-b03-3+b1-b1)
# Java VM: OpenJDK 64-Bit Server VM (25.77-b1 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libatk-bridge-2.0.so.0+0x10a8a]
#
# 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:
# /home/jodogne/hs_err_pid1262.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.
#
/usr/bin/imagej: line 427:  1262 Aborted 
/usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java -d64 -mx474m -cp 
/usr/share/java/ij.jar ij.ImageJ -ijpath /home/jodogne/.imagej -port1
<

This crash makes the imagej package totally unusable to me.

I have removed and purged all the JRE and JDK packages before making a fresh 
installation of imagej, but the crash is still there.

I thank you in advance for taking this problem into consideration!

Regards,
Sebastien-



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages imagej depends on:
ii  default-jre  2:1.8-57

imagej recommends no packages.

imagej suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
LC_TIME = "fr_BE.UTF-8",
LC_MONETARY = "fr_BE.UTF-8",
LC_ADDRESS = "fr_BE.UTF-8",
LC_TELEPHONE = "fr_BE.UTF-8",
LC_NAME = "fr_BE.UTF-8",
LC_MEASUREMENT = "fr_BE.UTF-8",
LC_IDENTIFICATION = "fr_BE.UTF-8",
LC_NUMERIC = "fr_BE.UTF-8",
LC_PAPER = "fr_BE.UTF-8",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
locale: Cannot set LC_ALL to default locale: No such file or directory