Public bug reported:
When the system enters sleep mode, Xorg appears to freeze. When the
system wakes back up, there is just a black screen. There is no
apparent way to get the system back once this happens. Interestingly,
the system does not appear to be completely frozen, in that it is still
Just a note that I am seeing this problem as well, here on an AMD 8350
8-core system using Trusty 14.04 AMD64. The Xorg process takes about
20%-35% of one core, when the system is otherwise idle. I'm open to
suggestions regarding how I can dig deeper to determine the cause,
because obviously
Bug report was withdrawn by the original user, and over here it was a
driver issue, so I am marking this ticket invalid.
** Changed in: xorg (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I just noticed what appears to be another problem:
-rw--- 1 myuser mygroup 504 May 12 21:21 krb5cc_0
-rw--- 1 myuser mygroup 504 May 12 21:16 krb5cc_1000_a8bk3j
While lightdm is renewing the tickets now when unlocking the screen
saver, and the ownership of the ticket is correct, the
I set the status back to new because that sounded correct given that
there is potentially additional work to be evaluated here, but if that's
not the right thing to do please let me know for future reference when
working with Launchpad tickets. I would normally just file a new
ticket, but in this
I applied this to a VM to test, and it does indeed appear to do the
right thing. I can confirm that this code does seem to have the
intended effect.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
To move this along, I've built a VM I can test this fix on, but to speed
things up, is there a PPA I can use? I don't mind building it but I am
concerned about building it differently than the official build, so if
there is a PPA I can use I will gladly install this onto my VM and I can
tell you
Thank you, Russ, for the insightful explanation of what is happening
here. I can definitely confirm that xscreensaver does indeed work on my
system, as that is what I am using as a workaround to this issue. It
isn't as polished as using the lightdm screen saver would be, but it
certainly works
I just performed a full update of all packages on my 12.04 installation,
rebooted, and tried again:
-
# lpq
WARNING: gnome-keyring:: no socket to connect to
mfc is ready
no entries
-
So the warning is still there. This installation was a regular install
with the Gnome 2 desktop
I want to mention that the workaround listed in comment #6, involving
commenting out the module, does indeed work over here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/914305
I think somebody who has access to do so should raise the priority of
this bug to a higher level. This bug has been known to break certain
network services, even services which have no apparent legitimate need
to be using gnome-keyring at all. It would be best if this bug were
fixed prior to the
I also want to mention that this appears to be related to upstream
Debian bug #649408, and breaks both network services and applications.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
I just wanted to add one example of a critical network service which is
broken by this bug, to demonstrate the broken functionality. CUPS
appears to be broken by this bug. I cannot print, and when I look in my
CUPS error log I see a bunch of messages about the daemon having
problems connecting
13 matches
Mail list logo
