wifi not working on Saucy Salamander

can you attache the output of dmesg please?

I forgot an important information.: wifi is recognized by kernel, it's finds networks but won't connect it.

In attach dmesg.

seems you ap sends on channel 13 (2472 MHz) which gets disable by your country (cfg80211: Disabling freq 2472 MHz) setting. Can you try to change your AP to something in between 1 and 11? I'm not sure how to change the regulatory country (US->IT?).

New attach, new access point, different country, same reported behavior.
With Lubuntu 12.10 wifi is working without any problem.

Please note that this log don't contain any Disabling freq, so the problem have to be found elsewhere.

mmh, doesn't look like a kernel problem to me. Googleing around I found that killing wpa_supplicant or disabling ipv6 may help. Also you could try to remove network-manager and ifup the device manually to check.

networking in lubuntu 13.10 doesn't work for me either. No ip address with wifi and with eth0 (usb to ethernet, see dmesg1.txt). lubuntu 13.04 works perfectly (same router, same ssid etc.)

I haven't tried gsm, though.

I disable ipv6 temporarily ( sudo /sbin/ip addr del <ipv6address>/<prefixlength> dev ethX ) but it had no effect on the bug.

gsm: same behaviour, device and signal strength visible, connection failed with "wwan0: no IPv6 routers preset"

Try killing wpa_supplicant or uninstall network-manager please.

First attempt (unsucessful):
After "apt-get remove network-manager" and reboot I lost "eth0" and "wlan0" in the output of "ifconfig -a". I re-installed network-manger and kill wpa_suplicant for wlan0 but it did not help (still no IP).

Second attempt (seems to work):
"apt-get install wicd" and /etc/network/interface with "auto eth0 \n iface eth0 inet dhcp".
I can connect wifi via wicd-gtk now.

(To install wicd I had to wget the deb-files on a second machine and to copy them to /var/caches/apt/archives)

[ 59.264921] type=1400 audit(1380291018.856:28): apparmor="STATUS" info="failed to unpack profile" error=-71 pid=781 comm="apparmor_parser" name="/usr/lib/NetworkManager/nm-dhcp-client.action" offset=155

this line from dmesg looks very suspicious ... adding "apparmor.enable=0" to the kernel cmdline (to diable apparmor completely) might help

Can you please provide the contents of

  sudo aa-status

  /etc/apparmor.d/cache/.features

  /etc/apparmor.d/cache/sbin.dhclient

  ls -a /sys/kernel/security/apparmor/

if present (and dependent on whether its a dir or file)
  ls -a /sys/kernel/security/apparmor/features
or
  cat -s /sys/kernel/security/apparmor/features

This is most likely due to the apparmor_parser errors. They are caused by having a new apparmor_parser, new policy (which now includes dbus rules), and old kernel.

The parser should be checking to see if the kernel supports dbus rules. Looking at the mount rule support in the parser,

* in parser/parser_main.c:get_match_string():
  - if apparmorfs/features/mount exists, the kernel_supports_mount global is set to 1
* in parser/parser_regex.c:post_process_mnt_ents():
  - mount rule entries are only processed if kernel_supports_mount is not 0
  - if kernel_supports_mount is 0, then a warning is emitted and the mount rule is ignored

The dbus rule support in the parser needs similar logic.

Here's a Saucy debdiff for apparmor to fix this bug and bug 1243932. I've tested it using the manual tests mentioned in the description of both bugs, as well as with QRT's test-apparmor.py test script.

Here's a Trusty debdiff for apparmor to fix this bug, bug 1243932, and bug 1247269. I've tested it using the manual tests mentioned in the description of the first two bugs, as well as with QRT's test-apparmor.py test script.

I've smoke tested the chromium-browser profile changes and manually verified the Python abstraction fix, as well.

The attachment "apparmor_2.8.0-0ubuntu31.1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

I've added tests for this bug and bug 1243932 to QRT's test-apparmor.py. I've successfully ran the new tests on Trusty and Saucy. I ran the tests under a Trusty/Saucy, Raring, and Lucid kernels to test all potential policy load scenarios. All scenarios pass.

Unsusubscribing sponsors, Marc said that the security team is going to take care of sponsoring that one

Uploaded 2.8.0-0ubuntu31.1. Tyler, can you make sure you follow any of the other steps in https://wiki.ubuntu.com/StableReleaseUpdates so it shows up on the SRU team's radar?

apparmor 2.8.0-0ubuntu34 is awaiting landing team approval.

apparmor 2.8.0-0ubuntu34 uploaded to trusty.

This bug was fixed in the package apparmor - 2.8.0-0ubuntu34

---------------
apparmor (2.8.0-0ubuntu34) trusty; urgency=low

  [ Tyler Hicks ]
  * 0078-parser-check-for-dbus-kernel-support.patch: The parser should not
    include D-Bus rules in the binary policy that it loads into the kernel if
    the kernel does not support D-Bus rules (LP: #1231778)
  * 0079-utils-ignore-unsupported-log-events.patch: aa-logprof should ignore
    audit events that it does not yet support instead of treating them as
    errors (LP: #1243932)
  * 0080-tests-use-ldconfig-for-library-detection.patch: Fix libapparmor
    detection in regression tests after the multiarch changes

  [ Jamie Strandboge ]
  * 0081-python-abstraction-updates.patch: Add rules in support of Python 3.3

  [ Chad Miller ]
  * debian/patches/0001-add-chromium-browser.patch: Follow new chromium-browser
    sandbox name. Keep old name for now to allow transition. LP: #1247269
 -- Tyler Hicks <email address hidden> Mon, 04 Nov 2013 15:57:30 -0800

what about Saucy?

Hello Federico, or anyone else affected,

Accepted apparmor into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apparmor/2.8.0-0ubuntu31.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Ciao Stéphane,
precisely today I decided to test if the fix solves my issue on Saucy. :)

Because Ac100 can access to network only by wifi, I had to download all debs on a usb stick and install offline.

After install apparmor wifi is working, tested from LXDE and with network-manager , THANK YOU!!!

best regards and thanks again

verification done, Tag updated.
version tested: apparmor_2.8.0-0ubuntu31.1-ubuntu

Tested apparmor_2.8.0-0ubuntu31.1-ubuntu, works!
Thanks!

I've verified that the test added to QRT's test-apparmor.py succeeds under Ubuntu Saucy kernel 3.11.0-13.20-generic, using the 2.8.0-0ubuntu31.1 package from -proposed.

This bug was fixed in the package apparmor - 2.8.0-0ubuntu31.1

---------------
apparmor (2.8.0-0ubuntu31.1) saucy-proposed; urgency=low

  * 0078-parser-check-for-dbus-kernel-support.patch: The parser should not
    include D-Bus rules in the binary policy that it loads into the kernel if
    the kernel does not support D-Bus rules (LP: #1231778)
  * 0079-utils-ignore-unsupported-log-events.patch: aa-logprof should ignore
    audit events that it does not yet support instead of treating them as
    errors (LP: #1243932)
 -- Tyler Hicks <email address hidden> Mon, 04 Nov 2013 13:22:22 -0800

The verification of the Stable Release Update for apparmor has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Hi min-soo-cho - this fix has not yet been released in the upstream apparmor project so I'm changing this back to 'fix committed'

Apparmor 2.9.0 has been released; closing.