Feisty Fawn not shutting down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.20 (Ubuntu) |
Invalid
|
Undecided
|
Brian Murray |
Bug Description
I installed Feisty Fawn kubuntu (daily build of 29.03.07), the system was updated daily since then. I choose partitioning by user, letting the installer overwrite my old partitions (/, /home, /tmp, /var, /usr and two! swap partitions on different disks, each 500 MB large).
Problem: The system hangs when shutting down from within kubuntu, screen blanks and nothing happens, keys are dead so that I have to press power off for 5 seconds. It is possible however to logout the user and then shutdown the computer from the kdm-screen. Maybe this happend because I once tried to suspend to disk, which also froze the computer (because I have two swap partitions and/or swap space is not large enough)?
Remarks on the install process:
-) On manual install, after selection a partition, the Edit-button has no function. I used the right-mouse-button, which opend a small menue from which I could select to edit the partition.
-) I selected German as main language. When selecting partitioning by hand (at step: Die Partition vorbereiten) the instruction of what to do in this step is in english, this could be a showstopper for some.
ProblemType: Bug
Architecture: i386
Date: Tue Apr 3 13:04:21 2007
DistroRelease: Ubuntu 7.04
Uname: Linux lucy 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
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. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
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.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/