Just to update my earlier comment #203, I still had this bug occur
occasionally even afterwards, though at a reduced rate. After doing
some more testing recently, I've been able to avoid this problem
completely by turning off the System-monitor extension in Gnome tweak
tool. I was then able to
Just to update this bug, I still had this bug occur occasionally even
afterwards, though at a greatly reduced rate. After doing some more
testing recently, I've been able to avoid this problem completely by
turning off the System-monitor extension in Gnome tweak tool.
--
You received this bug
Update: I've not hit this bug after 5 days now, and I need to restart
to apply security updates.
To recap, the fix was to add the following to /etc/rc.local :
echo auto /sys/class/drm/card0/device/power_profile
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Radeon.dpm managed to crash the whole system (had to do a hard cutoff,
caps-lock key wasn't even registering)
I've switched the power management back to profile, but instead of
using the default profile I've switched to auto. After 15 tries I've
not hit this bug. I'll continue with this setup
Well, after 3 days and I don't know how many suspends / lock screens
later this bug hit me again. Let me see if I can get some more
information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442311
I remembered that I had some kernel parameters set, so I turned off the
CLUTTER_VBLANK fix and experimented a bit. I used gnome-shell to
suspend, then resume and log in repeatedly until gnome-shell locked up.
(default ubuntu kernel parameters) = bug on 7th try
radeon.audio=1 = bug on 1st try
I cannot install a daily build on this machine, is there a live-usb
image with gnome-shell I can test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442311
Title:
Ubuntu 14.04 blank screen after
I finally found some time to work on this, and I think I have it fixed.
Debugging gnome-shell when I hit this bug (note, I could also trigger
this bug by allowing the screen to lock, no suspend necessary) I noticed
the following backtrace kept happening:
Thread 1 (Thread 0x7f920ec68a40 (LWP
For me the fix was to add:
export CLUTTER_VBLANK=none
to /etc/environment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283938
Title:
[Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after
Instead of doing that, I decided to do a quick sanity check.
I installed kernel 3.4-precise from the upstream kernel archives, which
I know worked fine when I was running 12.04 with gnome shell (even the
updated gnome-shell from the webupd8team ppa, I believe the version was
3.8?)
Sure enough,
Just tried 4.0.0 , and on first try I triggered this issue. I was,
however, able to kill gnome-setting-daemon and then gnome-shell from a
terminal. This then caused the lock screen to appear and I was able to
log in. I've had this happen sometimes in the past before, so I
consider this no
This just happened to me and got some messages in dmesg, filed bug
1442311
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283938
Title:
[Samsung NP535U4X-S01TH] Ubuntu 14.04 blank screen after
Public bug reported:
Possibly related to bug 1283938 . I have disabled lock screen on suspend
to try and get around the bug but it obviously hasn't worked.
I see a completely black screen with a working mouse cursor. Used Ctrl-
Alt-F2 to login at a text terminal and tried to kill
I can reliably trigger this bug on my machine in the 3.16 and 3.13
kernels. I've attached the kernel crash output for 3.16 (minus the dump
because of its size, I can provide a link if desired).
Adding wacom to /etc/modules prevents this bug for me.
** Attachment added:
Public bug reported:
Writing to the length of an array that is contained within an
associative array causes a segfault at runtime. Attached is an example
program.
** Affects: gdc-4.6 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: test.d
15 matches
Mail list logo
