Dear Seth Arnold, Thank you again for the quick reply. I signed up for the Code of Conduct in the system, and I can try to reproduce the activity. Is there a better way to capture the effects and give you a snapshot of the activities as they occur? F.Y.I. What I am describing never caused a system crash, so I think we are safe in that regard.
Best Always, Carl On 04/21/2017 06:56 PM, Seth Arnold wrote: > Thanks Carl; sadly the logs don't give me any better idea of what might > have happened. Can you reproduce the issue? It'd be helpful to see a log > of the messages involved. > > The logs attached without trouble; feel free to unlink whenever. (I > don't think it really matters one way or another.) > > Thanks > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684902 Title: browser unity app crashes apparmor profile Status in apparmor package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2 amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide browser engine and using the Ubuntu UI components.), Shown as Version 0.23+16.04.20161028-0ubuntu2, if removed from the system, causes apparmor to read errors in the system profile and fail to start (apparmor). I discovered that (per session), you can get apparmor to correct the failure and start, but as soon as you reboot, the system returns to the default profile set and fails to start apparmor. As far as I can tell, it does not indicate that the failure was caused by the browser uninstall, just that it failed to start for some reason. I tried to send this via apport, but it will not auto-locate the program, and since it is integrated with unity and oxide, I think it "sees" the program as a required OS file. Repaired issue by (1) Re-install browser (app?), (2) reset apparmor, (3) updated grub file, (4) reboot --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-04-12 (8 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: webbrowser-app PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic root=UUID=176948b3-104a-4075-bfbb-dbce1626a99d ro vesafb.invalid=1 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 Syslog: Apr 21 10:05:37 V2410US dbus[627]: [system] AppArmor D-Bus mediation is enabled Apr 21 11:15:30 V2410US dbus[665]: [system] AppArmor D-Bus mediation is enabled Tags: xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
