Thank you! What a relief.
echo disable /sys/firmware/acpi/interrupts/gpeXX
works like a charm, and
grep enabled /sys/firmware/acpi/interrupts/*
is a great way to find the offending interrupt.
Also, if you get a permission denied error upon using sudo, do this:
sudo -s
echo disable
Also, I did a more detailed summary of my attempts to fix this problem
and solution instructions from here in a blog post. I hope it helps
someone.
http://carlocapocasa.com/crushing-the-kworker-uprising-or-how-to-fix-
your-linux-lenovo-ideapad-y560p/
--
You received this bug notification
*** This bug is a duplicate of bug 887793 ***
https://bugs.launchpad.net/bugs/887793
Just did a little blog post on the subject, which sums up the fixes. I
hope it is useful.
http://carlocapocasa.com/crushing-the-kworker-uprising-or-how-to-fix-
your-linux-lenovo-ideapad-y560p/
--
You
Now using pci=noacpi. Fixes the problem, battery detection works.
Correction: There is no lenovo 750p, I'm using the (utterly magnificent)
Lenovo y560p.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same hardware (Lenovo 750p), same fix, same problem with the fix
(battery detection). Oh well.
To test the fix, I pressed E in grub and added acpi=noirq after quiet
splash.
To make the fix permanent, I went ot the line that said
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
in /etc/default/grub
Workaround:
lucid bleed backport worked for me with Skype Beta 2.2.0.35.
https://launchpad.net/~lucid-bleed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551164
Title:
pidgin-skype doesn't work -
What's up, Joshua... coming from duplicate bug #473054 and the fix works
just fine. Thanks! And thanks for telling me about it over at the
duplicate... Have a good one, Carlo
--
Protocol version error - when bandwidth throttling is enabled with the
default values
The alternate mesa packages in Comment 21
(https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/368049/comments/21)
worked for me.
If I don't follow up (search for my name to find out) the fix worked
permantently.
Carlo
--
compiz crashes gnome desktop using default ati driver (radeon X600)
Correction: The mentioned package didn't fix the issue for me after all,
as there was another crash.
--
compiz crashes gnome desktop using default ati driver (radeon X600)
https://bugs.launchpad.net/bugs/368049
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am experiencing freezes as well. Samsung R41. Happened with ext4, but
then re-installed with ReiserFS and same behavior. Had no similar
problems with Hardy or Intrepid.
--
Jaunty freezes randomly
https://bugs.launchpad.net/bugs/367464
You received this bug notification because you are a member
I have this bug too, with an interesting spin: Sometimes, when the crash
happened, it happens again every time I login, and shortly after the
Ubuntu theme starts getting played, and causes a hard freeze (Hard
system restart required).
To work around this, I have found it useful to rename or
Confirm this in 8.10. Happened after an X crash/auto-restart.
--
pidgin tray icon too large
https://bugs.launchpad.net/bugs/209440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Just found out this bug only appears for the current RT kernel, and
according to the UbuntuStudio.org main site is a known problem. Package
adjusted accordingly.
** Changed in: linux-rt (Ubuntu)
Sourcepackagename: gnome-power-manager = linux-rt
--
No poweroff after shutdown
Thank you too for your open ear! The output for
sudo cp -r /proc/acpi /tmp
is:
cp: cannot open `/proc/acpi/event' for reading: Device or resource busy
Carlo
--
No poweroff after shutdown
https://bugs.launchpad.net/bugs/299237
You received this bug notification because you are a member of
uname.txt, lspci.txt, dmidecode.txt and /var/log/kern.log.0 added.
Output for cp -r /proc/acpi /tmp:
cp: cannot open `/proc/acpi/event' for reading: Permission denied
cp: cannot open `/proc/acpi/fadt' for reading: Permission denied
cp: cannot open `/proc/acpi/dsdt' for reading: Permission denied
** Attachment added: lspci.txt
http://launchpadlibrarian.net/19748081/lspci.txt
--
No poweroff after shutdown
https://bugs.launchpad.net/bugs/299237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: dmidecode.txt
http://launchpadlibrarian.net/19748083/dmidecode.txt
--
No poweroff after shutdown
https://bugs.launchpad.net/bugs/299237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Suspend log: Computer did not suspend, just stayed with a blank text
screen for about 30 seconds and then presented the 'unlock' screen.
** Attachment added: kern.log.0
http://launchpadlibrarian.net/19748098/kern.log.0
--
No poweroff after shutdown
https://bugs.launchpad.net/bugs/299237
You
Hibernate log: Same behavior as with suspend.
** Attachment added: kern.log.0
http://launchpadlibrarian.net/19748154/kern.log.0
--
No poweroff after shutdown
https://bugs.launchpad.net/bugs/299237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Regression from hardy: In intrepid, shutting down the machine lets it
hang after a message that says: acpid exiting The message appears
after the shutdown progress indicator indicates shutdown completion and
screen mode is switched to text mode. The expected power-off
Sure. My laptop broke down a while a go so I'm afraid I can't say any
more about it! My new laptop (a Samsung R41 Madea) works out of the box.
Maybe the other reporters can give feedback.
Thanks once again for Ubuntu! It's getting to be a lifestyle :)
Carlo
--
[nvidia-glx feisty] GeForce2 Go
Public bug reported:
Connection works great (Thanks, Ubuntu Team! Loving the new
connectivity!). For the bug, please see the screenshot.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Network Manager: List of Wired Networks and Wireless Networks are shown twice
each
Screenshot shows bug: Both network lists are shown twice. Network
manager also shows connection dialog and connected bubble box twice.
Computer model is a Samsung R41 Madea notebook.
** Attachment added: Network Manager showing all connections twice -
Screenshot
Public bug reported:
Thank you helping bring the fantastic new CSound for Ubuntu!
For using HRTF-related opcodes, HRTF-Data files are required. These are
supplied with the Windows installer
and are downloadable from the CSound download site, but do not appear to be
included in Ubuntu.
Using
Attached is the CSS file in question that triggered the bug when first
discovering it.
Note also that the guest system installation went like this:
* Create Virtual Machine
* Boot from Dapper 6.06.2 Server CD image
* Install Dapper 6.06.2 Server with the 'Install LAMP server' option
* Rebooting
Public bug reported:
Binary package hint: virtualbox-ose
Configuration:
Host: Gutsy Gibbon on Dell Inspiron 2650
Guest: Dapper Drake 6.06.2 LAMP Server install
Kernel change to 2.6.15-51-386
(=standard kernel, since server kernel not supported by virtualbox)
de-installed PHP5, installed
Public bug reported:
Binary package hint: gnome-power-manager
This is using Gutsy Gibbon, release version.
Gnome power preferences can be configured quite
neatly from the within Screensaver configuration,
which is great.
However, no matter what settings, the screen still
turns off after a
Workaround found:
1. Install startupmanager
$ sudo apt-get install startupmanager
2. Configure startupmanager
In the Ubuntu Menu, select: System - Administration - StartUp
Manager
Set the Resolution to 1024x768, color depth to 24. Leave all other
settings intact.
Close, wait for
The bug persists on Ubuntu Feisty Fawn.
The workaround (adapted to Feisty) is:
1. add the following line to /etc/modprobe.d/options
options nvidia NVreg_Mobile=2
2. Reboot
3. Enable the restricted driver as usual.
Limitations:
* Must de-activate turning off the monitor in screen saver
Public bug reported:
In gutsy release version, the startup screen (Ubuntu logo and progress bar)
do not display. Instead, there is a pattern in shades of yellow, orange and
green.
Other than that, boot up happens normally. Shutdown screen (Ubuntu logo and
reverse progress bar) display normally.
30 matches
Mail list logo
