← Back to team overview

kernel-packages team mailing list archive

[Bug 1312782] Missing required logs.


This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1312782

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Tags added: quantal

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  syscrash on 'Enable Wireless'

Status in “linux” package in Ubuntu:

Bug description:
  I'm using Ubuntu 12.04.4 LTS with kernel version : Linux anish-pc
  3.5.0-45-generic #68~precise1-Ubuntu SMP Wed Dec 4 16:18:46 UTC 2013
  x86_64 x86_64 x86_64 GNU/Linux. My computer is Toshiba Satellite

  Possible package : Linux

  Since I updated to kernel version 3.5.0-46, I've been having problems
  with 'Enable Wireless'.Whenever I turn on 'Enable Wireless', I get a
  syscrash and have to hard reset my laptop. This happens 9/10 times.
  Sometimes it doesn't crash and I can use my computer without any
  problems. Sometimes, it doesn't crash when I enable wireless, but then
  if I turn off the wireless and reset it, it occurs again. This problem
  only exists for kernel version 3.5.0-46 to 3.5.0-48. Previous kernel
  versions do not have this problem and so I'm using kernel version
  3.5.0-45 as it is stable for me.

  This problem first occurred when I updated to kernel version 3.5.0-46.
  When I was updating, I lost my internet connection for 10-15 sec and
  after regaining it, update-manager continued updating. I thought these
  crashes may have been caused because of this and so I waited to new
  kernel updates in the hope that this problem will get solved. But that
  didn't happen for next kernel updates : 3.5.0-47/48.

To manage notifications about this bug go to: