** Attachment added: "Test case source code for running JVM launched from C
compiled with 32-bit and 64-bit and different JVM stack size."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772/+attachment/4912696/+files/Bug1699772_i386_jvm_segfault_problem.tgz
--
You received this
Hi,
problem still present on linux-image-4.8.0-58-generic with these conditions:
- while executing JVM launched from >>32-bit<< C (on 64-bit kernel)
- defining "higher" JVM stack size (eg. -Xss2048k JVM argument)
=> causes JVM segmentation fault
Attached test case (sources + binary +
HI,
my setup:
- Lenovo T530 with NVIDIA Corporation GF108M [NVS 5400M] (rev a1)
- Ubuntu 14.04 with mainline kernel 3.14.9
- NVIDIA driver nvidia-331-updates:
My computer hanged during hibernate resume just after reading the image from
the disk.
I found working solution by reading non-editable
Sorry, I was solving my resume problems after hibernation.
So please ignore my previous comment since I didn't read this bug report
properly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
*** This bug is a duplicate of bug 1252664 ***
https://bugs.launchpad.net/bugs/1252664
OK.
Therefore, this bug could be closed as duplicate. Also thanks for your time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
Currently, I'm using Ubuntu 14.04 LTS with 3.14.1 kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
1. ) I simply tried installing nvidia-331-updates-uvm package from Ubuntu 14.04
repository, and the package installation failed (build problems registering
kernel
I was also just trying to install the newest NVIDIA driver only. I was
quite lucky that it took me just a few minutes to find out what was
happening... It also helped me choosing NVIDIA Optimus option in the
BIOS settings. However, only Intel GPU started to work. Bumblebee was
unable to start
6.) SOLUTION - WORKAROUND 2:
After applying this workaround, BPEL rendering is fast again (in WID
6.2) and WID doesn't crash anymore.
Note: Workaround no. 1 used libxrender.so only. Now more (dependent)
libraries are also needed.
6.1) This patch is probably NOT needed:
I still don't have a solution but here are my latest findings about this
issue:
1.) WID process uses following files:
lsof -p PID | grep swt
eclipse 7819 rstribrn memREG8,7 40736 1058233
I've just upgraded from Ubuntu 12.10 to Ubuntu 13.04 during the weekend.
1.) The problem with libxrender library is STILL valid.
2.) Moreover, the workaround with oneiric's libxrender library version no
longer works (entire X server crashes after few clicks in WebSphere Integration
Studio when
Problem still valid, I'm about to ugprade to 13.04 soon. So I will
report if the bug will be still there (or more interestingly, whether
the workaround would still work)...:-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxrender in
I've just checked that the bug is also present in latest Ubuntu: 12.10 Quantal
Quetzal.
Since nobody has been assigned to this bug I wonder, how to proceed...
I seems to me like a simple compile-time problem or something...
--
You received this bug notification because you are a member of
12 matches
Mail list logo
