I can confirm as well that lightdm v1.2.3-0ubuntu2.7 has indeed fixed
this issue for me. Thank you for the quick turnaround!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1431654
Titl
Looks like that did it:
root 18958 0.0 0.0 270668 3496 ?Ssl 23:26 0:00 lightdm
root 18964 11.0 1.0 246424 133256 tty7Ss+ 23:26 0:08 /usr/bin/X :0
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Good work!
--
You received this bug notification because
Unfortunately, the 2nd patch still produces the high cpu usage on one
core:
root 2054 93.8 0.0 270668 3488 ?Rsl 22:35 1:40 lightdm
root 2091 10.4 1.3 283756 170820 tty7Ss+ 22:35 0:11 /usr/bin/X :0
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
--
You
First patch didn't fix the issue:
root 11395 93.0 0.0 270668 3488 ?Rsl 22:26 1:00 lightdm
root 11401 12.3 1.2 263008 149876 tty7Ss+ 22:26 0:08 /usr/bin/X :0
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
I will try the 2nd one now.
--
You received thi
To add to comment #17, just now I replaced my empty 09_close_pipes.patch
file with the actual patch, then rebuilt, installed and restarted the
lightdm process. Upon logging in, it's back to using 100% of a cpu core
again. So when the 09 patch is removed, no high cpu usage. When the
patch is put
I may not be doing this correctly, but I ran the following to attempt to
debug the running lightdm process using the package from the precise
proposed ppa again. The command I ran is:
sudo gdb lightdm 24513
Of course, 24513 was the running lightdm process. Interesting thing
here is, once gd
Hi Robert,
While I am a developer, I don't have much experience developing in Linux
or using Bazaar (bzr). With that being said, I wasn't exactly sure how
to disable a patch per say, so what I did was backed up
09_close_pipes.patch by moving it to my desktop, then issuing "touch
09_close_pipes.pa
Also, an addendum to the previous instructions, the Ubuntu repo that has
version 1.2.3-0ubuntu2.5 of lightdm is the precise-updates repo. To add
that repository, do the following:
>From terminal:
sudo gedit /etc/apt/sources.list
Add the following lines to the end of your file:
## U
FYI, in case there are some lesser experienced users that have this
issue and are looking for a temporary solution for the time being, below
are the instructions to revert to the previous release of lightdm until
this gets resolved.
You can do this with the following command in a terminal ():
If it helps, here's the x-0-greeter.log file while running lightdm
v1.2.3-0ubuntu2.5 (when the 100% usage doesn't occur).
** Attachment added: "x-0-greeter1.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+attachment/4343757/+files/x-0-greeter1.log
--
You received this bu
Here's the x-0-greeter.log file generated from lightdm
v1.2.3-0ubuntu2.6.
** Attachment added: "x-0-greeter.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1431654/+attachment/4343749/+files/x-0-greeter.log
--
You received this bug notification because you are a member of Desktop
I apologize, the version of the kernel that was running when log file
was generated was 3.2.0-79-generic (not 3.2.0-19-generic). Sorry for
the typo.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpa
Here is the lightdm log file pulled from /var/log/lightdm/lightdm.log.
At 98.76s, I logged out of my session, but didn't get a log-in screen
again (black screen on both monitors).
At this point I killed the process (28882) so that I could downgrade
lightdm again (from ctrl+alt+F1) and log back in.
Public bug reported:
Since updating lightdm today, one core of my CPU is always maxed out at
100%. I rolled back to version 1.2.3-0ubuntu2.5 and the issue stopped.
I tried this with 2 different kernels: 3.2.0-77-generic and
3.2.0-79-generic and and version 1.2.3-0ubuntu2.6 of lightdm still
caused
This bug affects me and is driving me crazy. I'm only using Empathy for
GoogleTalk; 1 Google App account and one standard account. It seems to
affect my Google App account more.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in
When I run this version of G-S-D from terminal, I see this in the
output:
(gnome-settings-daemon:2845): media-keys-plugin-WARNING **: Grab failed
for some keys, another application may already have access the them.
I'm still having this issue with 11.10
--
You received this bug notification bec
I installed the proposed fix for gnome-settings-daemon, but I still have
this issue. Or is this going to be part of a newer build of the Gnome
Settings Daemon?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubun
For the log of all that is Holy, please add this option. With it being
an option, people can agree or disagree, but at least it will be there
for people like me who are missing conversations because I don't have
the contact list open all the time... I know, there's a little blue
envelop in the Un
18 matches
Mail list logo
