fejes, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily 
folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine the issue. Once you've tested the 
upstream kernel, please comment on which kernel version specifically you 
tested. If this bug is fixed in the mainline kernel, please add the following 
tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Tags removed: networkmanager
** Tags added: needs-kernel-logs

** No longer affects: network-manager (Ubuntu)

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1091718

Title:
  3.7 kernel and network manager do not play nicely in kubuntu raring

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Sorry - Ubuntu-bug didn't give me suitable options, and clearly some
  of the information it's reporting is just incorrect .

  I upgraded kubuntu 12.10 to 13.04 last night, and observed the update-
  initramfs bug
  (https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1073062).  Upon
  restart, KDE loads, but NetworkManager takes 100% cpu, and fails to
  allow wireless connections. (Changing the backend from NetworkManager
  to Wicd does not help.)

  However, if you restart and select the 3.5 kernel instead of 3.7
  kernel, the problem disappears completely.

  I'm happy to help debug and provide further information if you can
  tell me what it is that's needed.

  Anthony Fejes

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Uname: Linux 3.5.0-19-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Tue Dec 18 10:19:56 2012
  InstallationDate: Installed on 2011-01-21 (697 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to raring on 2012-10-19 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1091718/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to