| 2009-01-08 16:34:33 |
BrandonS |
bug |
|
|
added bug |
| 2009-01-08 16:35:13 |
BrandonS |
description |
Binary package hint: gnome-control-center
Seeing issues with gnome-appearance-properties in Intrepid. gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1
Symptoms are the application will launch, but not appear on screen. CPU will drive up to 80% - 90% utilized. After about 1 - 2 minutes the application will actually open, allowing the user to change their settings.
Doing an strace on this application shows that it's doing through /proc/mounts when launching. This is a problem here because we are using autofs5 with ldap and our /proc/mounts file is over 9000 lines long. I've deduced that it's spinning the CPU while trudging through our very large /proc/mounts file and this is why it's taking so long. |
Binary package hint: gnome-control-center
Seeing issues with gnome-appearance-properties in Intrepid. gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1
Symptoms are the application will launch, but not appear on screen. CPU will drive up to 80% - 90% utilized. After about 1 - 2 minutes the application will actually open, allowing the user to change their settings.
Doing an strace on this application shows that it's going through /proc/mounts when launching. This is a problem here because we are using autofs5 with ldap and our /proc/mounts file is over 9000 lines long. I've deduced that it's spinning the CPU while trudging through our very large /proc/mounts file and this is why it's taking so long. |
|
| 2009-01-08 18:18:23 |
Chris Coulson |
gnome-control-center: status |
New |
Incomplete |
|
| 2009-01-08 18:18:23 |
Chris Coulson |
gnome-control-center: importance |
Undecided |
Low |
|
| 2009-01-08 18:18:23 |
Chris Coulson |
gnome-control-center: statusexplanation |
|
Thank you for your bug report. Could you please try to run it through GDB, and produce a backtrace during the hang? You can do this by following the instructions at https://wiki.ubuntu.com/DebuggingProgramCrash.
However, as the program isn't crashing, what you need to do is interrupt it when it is iterating over your /proc/mounts, by pressing CTRL+C in the GDB window. You can then get a backtrace by running "backtrace full" whilst the program is halted.
Thanks in advance |
|
| 2009-01-12 20:00:39 |
BrandonS |
bug |
|
|
added attachment 'gdb-gnome-appearance-properties.txt' (gdb-gnome-appearance-properties.txt) |
| 2009-02-19 17:30:37 |
Sebastien Bacher |
gnome-control-center: status |
Incomplete |
New |
|
| 2009-02-19 17:30:37 |
Sebastien Bacher |
gnome-control-center: assignee |
|
desktop-bugs |
|
| 2009-02-19 17:30:37 |
Sebastien Bacher |
gnome-control-center: statusexplanation |
Thank you for your bug report. Could you please try to run it through GDB, and produce a backtrace during the hang? You can do this by following the instructions at https://wiki.ubuntu.com/DebuggingProgramCrash.
However, as the program isn't crashing, what you need to do is interrupt it when it is iterating over your /proc/mounts, by pressing CTRL+C in the GDB window. You can then get a backtrace by running "backtrace full" whilst the program is halted.
Thanks in advance |
do you get the issue on a new account or guest user session? |
|
| 2009-02-26 22:06:28 |
BrandonS |
bug |
|
|
added attachment 'strace.out' (strace.out) |
| 2009-04-15 13:00:04 |
Sebastien Bacher |
gnome-control-center (Ubuntu): status |
New |
Incomplete |
|
| 2009-04-15 20:00:08 |
Sebastien Bacher |
gnome-control-center (Ubuntu): status |
Incomplete |
Fix Released |
|
