| 2007-01-17 09:38:23 |
Martin |
bug |
|
|
added bug |
| 2007-01-17 09:39:53 |
Martin |
bug |
|
|
added attachment 'screendump.png' (Screendump of application) |
| 2007-01-31 21:03:13 |
Chris Wagner |
title |
CPU 1 runs at 100% after spend to disk |
CPU 1 runs at 100% after suspend to disk |
|
| 2007-02-26 21:37:28 |
Brian Murray |
None: status |
Unconfirmed |
Needs Info |
|
| 2007-02-26 21:37:28 |
Brian Murray |
None: assignee |
|
brian-murray |
|
| 2007-02-26 21:37:28 |
Brian Murray |
None: statusexplanation |
|
Thanks for your bug report. Could you please execute top after resuming from suspend to see if it something with the system monitoring applet? Thanks in advance. |
|
| 2007-04-02 21:54:36 |
Brian Murray |
linux-source-2.6.17: statusexplanation |
Thanks for your bug report. Could you please execute top after resuming from suspend to see if it something with the system monitoring applet? Thanks in advance. |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance! |
|
| 2007-04-14 07:59:45 |
emvy |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2007-04-14 08:00:29 |
emvy |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2007-05-31 19:41:38 |
Brian Murray |
linux-source-2.6.20: status |
Needs Info |
Confirmed |
|
| 2007-05-31 19:41:38 |
Brian Murray |
linux-source-2.6.20: importance |
Undecided |
Medium |
|
| 2007-05-31 19:41:38 |
Brian Murray |
linux-source-2.6.20: statusexplanation |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance! |
|
|
| 2007-05-31 19:41:38 |
Brian Murray |
linux-source-2.6.20: assignee |
brian-murray |
ubuntu-kernel-acpi |
|
| 2007-07-18 12:23:03 |
Gintautas Miliauskas |
linux-source-2.6.20: assignee |
ubuntu-kernel-acpi |
|
|
| 2007-07-18 12:23:03 |
Gintautas Miliauskas |
linux-source-2.6.20: statusexplanation |
|
Confirmed here too -- it's only the applet that gets stuck. The problem occurs both after suspend-to-RAM and suspend-to-disk.
CPU: Intel Core 2 T5500
gnome-applets: 2.18.0-0ubuntu1
kernel: 2.6.20-16-generic |
|
| 2007-07-28 06:21:02 |
laksdjfaasdf |
bug |
|
|
added attachment 'dmesg.log' (Output of dmesg) |
| 2007-07-28 06:21:37 |
laksdjfaasdf |
bug |
|
|
added attachment 'lspci-vvnn.log' (Output of lscpi-wnn on Thinkpad Z61m) |
| 2007-08-09 17:54:47 |
Sebastien Bacher |
gnome-applets: status |
Confirmed |
Triaged |
|
| 2007-08-09 17:54:47 |
Sebastien Bacher |
gnome-applets: importance |
Medium |
Low |
|
| 2007-08-09 17:54:47 |
Sebastien Bacher |
gnome-applets: statusexplanation |
Confirmed here too -- it's only the applet that gets stuck. The problem occurs both after suspend-to-RAM and suspend-to-disk.
CPU: Intel Core 2 T5500
gnome-applets: 2.18.0-0ubuntu1
kernel: 2.6.20-16-generic |
Might the same issue than http://bugzilla.gnome.org/show_bug.cgi?id=356694 |
|
| 2007-08-09 17:54:47 |
Sebastien Bacher |
gnome-applets: assignee |
|
desktop-bugs |
|
| 2007-08-09 17:55:03 |
Sebastien Bacher |
bug |
|
|
assigned to gnome-applets (upstream) |
| 2007-08-10 08:27:39 |
Bug Watch Updater |
gnome-applets: status |
Unknown |
Fix Released |
|
| 2008-04-25 15:52:53 |
Pedro Villavicencio |
gnome-applets: status |
Triaged |
Incomplete |
|
| 2008-05-26 13:05:29 |
Sebastien Bacher |
gnome-applets: status |
Incomplete |
Fix Released |
|
| 2010-09-16 07:17:48 |
Bug Watch Updater |
gnome-applets: importance |
Unknown |
High |
|
