Eugene's PPA doesn't seem to fix this for me on 14.10. If I log in with
NX and gnome-session --session=gnome-flashback, I still get a black
screen. Am I missing something? Or were the fixes only intended to work
with 14.04?
--
You received this bug notification because you are a member of
I'm still getting segmentation faults out of libglib-2.0 with Java
1.8.0_25-b17, Ubuntu 14.10, and Eclipse. However, after upgrading to
Java 8, the seg faults I'm seeing have moved to from g_str_hash() to
g_type_check_instance_is_a()
#
# A fatal error has been detected by the Java Runtime
Public bug reported:
glib2.0 intermittently causes Eclipse to crash with the attached trace.
Please let me know if I can do anything else to help you debug.
Eclipse Kepler
Description:Ubuntu 14.04.1 LTS
Release:14.04
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libglib2.0-0
Created attachment 247831
Additional crash log
Eclipse 4.3.2 crashes *constantly* (several times per day) with this
problem on Ubuntu 14.04. The UI goes grey and unresponsive, and after
force-quitting the application I get an error log with a stack trace
about a seg fault in native code invoked
This bug in GTK causes Eclipse to crash *constantly* (several times per
day) on Ubuntu 14.04. I've attached an error log that gets left behind
after the crash. The incriminating frame is:
C [libglib-2.0.so.0+0x38fe0] g_str_hash+0x0
I really hope this gets fixed! Stability bugs are the worst.
It's not clear what the bug is/was. I can no longer reproduce with
Eclipse Kepler in Ubuntu 14.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1066569
Title:
Eclipse Freezes,
When the entire system hangs and you have to hard reset, I don't think
Eclipse gets a chance to leave a crash dump.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/1066569
Title:
Here's something: The stutter occurs when using HDMI with my primary
monitor, but not with my HDTV.
Monitor: Acer S231HLbid
http://www.newegg.com/Product/Product.aspx?Item=N82E16824009255
TV: Samsung LN37A550
http://www.amazon.com/Samsung-LN37A550-37-Inch-1080p-HDTV/dp/B00141AZR2
The root
I've attached the manuals for the two displays. The relevant pages seem
to be:
Samsung Manual: p44 (labeled 42), discusses HDMI in CEA mode for 1080p
Acer Manual: p12, standard timing table
My best guess for what is happening is that Ubuntu's display output
timing over HDMI is slightly out of
Here's even more information. The output of 'xrandr --prop' with VGA and
with HDMI connected
** Attachment added: VGa xrandr --prop output
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/964231/+attachment/3564104/+files/VGA%20xrandr%20prop.txt
--
You received this
** Attachment added: HDMI xrandr --prop output
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/964231/+attachment/3564105/+files/HDMI%20xrandr%20prop.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
FYI, Ubuntu 12.10 has the same issue with my monitor + HDMI. The freezes
seem to be about 100ms in duration, and occur regularly every 1s. It's
incredibly irritating.
Output of vmstat:
procs ---memory-- ---swap-- -io -system-- cpu
r b swpd free buff cache
Public bug reported:
After a fresh install of Ubuntu 12.10 Quantal Quetzal 64-bit, gnome-
power-manager ignores my setting to never turn off my screen. The screen
automatically turns off after ~20 minutes of inactivity.
In System Settings Brightness and Lock, my setting is Turn screen off
when
Confirmed on 12.10 Quantal Quetzal. This exact problem began happening
to me after an upgrade from 12.04 to 12.10.
This seems to be a bug with the upgrade process screwing up power
management settings.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
During routine use on Ubuntu 12.04 64-bit, Eclipse Indigo (version in
repos) intermittently will freeze and become unresponsive (Window is
grayed-out, CPU maxed out). Occasionally this causes the entire system
to freeze (no input accepted, images on screen frozen). The only
Wow, this bug is old. Anyway, it's plaguing me too, and I can't figure
out how to work around it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/473735
Title:
empathy keeps showing
Confirmed, broken for me too. It has worked in the past, but no longer
works with Empathy 3.4.2.3 in Precise.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1036738
Title:
facebook
17 matches
Mail list logo
