2

I have a Gateway NE56R laptop running the latest Kubuntu 14.10 x64 beta, although I had this same problem on Trusty. This problem may also affect some Acer Aspire laptops if that helps you fix my problem.

If I close my laptop's lid (I use a VGA monitor when it's closed), my system acts a little strange. If I close it anytime between when GRUB starts booting and when I actually sign in to Kubuntu, my laptop will suspend, even though I set it not to. For this reason, my laptop DOES NOT suspend after I'm signed in. Also, closing the lid seems to significantly slow down all wireless communication via Wi-Fi (yes, I've disabled power saving).

Also, sometimes if my lid is closed for a long time (an hour maybe), all USB devices just lose power and don't work until a restart. Sometimes I can just unplug something and plug it back in and it makes everything work again. Only sometimes. Remember that; if I replug one device, it will sometimes make all devices work again. All of this also happened in Trusty too.

Also, I think I should mention that my wireless card is a Broadcom BCM4313. Although I know many, many Ubuntu users are having problems getting their BCM4313 to work, I was able to get mine to work and it works great, so don't say anything about "fixing" my wireless- it's fine. Ubuntu's reaction to the LID closing is the problem.

13
  • 1
    Come on. A bug report link? Anything? This is my computer I use every day. If someone will at least tell me information (i.e. This will be fixed in Utopic's final release), I'd appreciate it. I am just going to make a bug report, because I can't find an existing report. What package would I report this for being a bug?
    – John Scott
    Oct 10, 2014 at 17:21
  • 1
    Well, any debugging starts with checking logs I guess. Try closing lid just how you described, then resume the machine and go in to /var/log. Read through recent entries in boot.log, dmesg, pm-powersave.log . There's also this page here: wiki.ubuntu.com/DebuggingKernelSuspend . If you can't figure it out, just attach the info from the logs here, and maybe someone will figure it out . Good luck ! Oct 11, 2014 at 17:03
  • 1
    Here's something else, specifically read through trace resume part. kernel.org/doc/Documentation/power/s2ram.txt Oct 11, 2014 at 17:16
  • 2
    I've created a bug report at bugs.launchpad.net/ubuntu/+source/linux/+bug/1380144 which has many logs, which may be useful, attached. I took a guess and assumed this was a bug in Linux, so that's what the bug is against.
    – John Scott
    Oct 11, 2014 at 17:40
  • 2
    I know you want the bounty...
    – John Scott
    Oct 12, 2014 at 1:46

0

You must log in to answer this question.

Browse other questions tagged .