Public bug reported:
I disabled AppArmor on my machine, but the update insists on starting it. This
prevents mysql from starting, because the apparmor profiles are bogus.
Please leave AppArmor alone during update. It's disabled.
I removed apparmor completely from /etc/init.d to fix this properly.
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27885713/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/27885714/DpkgTerminalLog.gz
--
package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to
install/upgrade: subpro
Yes, the profiles are untouched since the system was installed. I never used
apparmor. The profiles certainly do not match what's on the machine, which can
cause problems *if and only if* apparmor should start. Yes, the mysql files are
in a location not configured & not permitted by apparmor.
Ag
Umm, I'm really trying to help here. Note that my patience is running thin, and
I don't appreciate the patronizing tone.
Here is what I've done to disable AppArmor on my system:
sudo invoke-rc.d apparmor stop
sudo update-rc.d -f apparmor remove
After this, everything on my system works smoothly, i
Not a bug. Configuration problem.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
Resuming after hibernating doesn't resume; just restarts.
https://bugs.launchpad.net/bugs/359416
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Not a problem w/ Ubuntu. Most likely Nvidia driver issue.
** Changed in: acpi-support (Ubuntu)
Status: Incomplete => Invalid
--
standby and hibernate fail
https://bugs.launchpad.net/bugs/316641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have exactly the same problem. Disk method is 'shutdown'.
Hibernate appears to work fine, but when the system is started, it just
reboots, instead of resuming.
There is no indication of any problem in the kernel logs.
Suspend to RAM works.
Linux nova 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17
The blank screen and locking problems were caused by the Nvidia proprietary
driver. Worked around by switching to console when trying to hibernate.
I switched to jaunty and how hibernate fails to resume completely. See bug
359416. Feel free to close this one.
--
standby and hibernate fail
https
I have solved my problem, and here is my fix.
The problem was caused by the fact that the swap partition had changed, so it
had a different UUID, but the resume/kernel did not know about it. As a result,
resume never worked - it just rebooted instead.
Here is the swap fix:
http://ubuntuforums.org
I figured out what was causing the freezing/locking problem: I used to have
[platform] enabled in /sys/power/disk. This caused the machine to lock on every
attempt to change the power state (acpi).
I have changed that to [shutdown] and now the machine suspends/hibernates OK.
There still are resum
Public bug reported:
Binary package hint: acpi-support
The computer locks up when trying to enter standby or hibernate.
Power is not cut off, fans and monitor are still up.
** Affects: acpi-support (Ubuntu)
Importance: Undecided
Status: New
--
standby and hibernate fail
https://b
** Attachment added: "acpi.tar"
http://launchpadlibrarian.net/21150099/acpi.tar
--
standby and hibernate fail
https://bugs.launchpad.net/bugs/316641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Thanks for looking at this.
This is a desktop machine, not a laptop.
The CPU is an Intel Core2 Duo @ 2.66 GHz, 4 GB RAM, ASUS P5K-E mainboard,
GeForce 8800 GT.
I've attached a hardinfo report.
The machine simply reboots when trying to boot w/ noacpi, nothing in kernel.log.
Also there is nothing in
13 matches
Mail list logo
