Error Message

Bug #1767795 reported by Philipp Batram
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
New
Undecided
Unassigned

Bug Description

By starting the system in the long list of terms it shows one FAILED.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Apr 29 14:34:52 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:81ef]
InstallationDate: Installed on 2017-07-31 (271 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 8087:0a2a Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 250 G5 Notebook PC
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=90f2bd5c-bf2f-4aa9-866a-dcaf60f182d2 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81EF
dmi.board.vendor: HP
dmi.board.version: 63.38
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.38:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250
dmi.product.name: HP 250 G5 Notebook PC
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Apr 29 13:38:51 2018
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset
---
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: MATE
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2017-07-31 (307 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Package: apparmor 2.10.95-0ubuntu2.9
PackageArchitecture: amd64
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=90f2bd5c-bf2f-4aa9-866a-dcaf60f182d2 ro drm.debug=0xe plymouth:debug
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Syslog:

Tags: xenial
Uname: Linux 4.13.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Philipp Batram (philippbatram) wrote :
penalvch (penalvch)
affects: xorg (Ubuntu) → apparmor (Ubuntu)
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Philipp, can you please run:

apport-collect 1767795

to get the apparmor-related artifacts?

Thanks

Revision history for this message
Philipp Batram (philippbatram) wrote : ApparmorPackages.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Philipp Batram (philippbatram) wrote : ApparmorStatusOutput.txt

apport information

Revision history for this message
Philipp Batram (philippbatram) wrote : Dependencies.txt

apport information

Revision history for this message
Philipp Batram (philippbatram) wrote : KernLog.txt

apport information

Revision history for this message
Philipp Batram (philippbatram) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Philipp Batram (philippbatram) wrote : ProcEnviron.txt

apport information

Revision history for this message
Philipp Batram (philippbatram) wrote : PstreeP.txt

apport information

Revision history for this message
Philipp Batram (philippbatram) wrote : Re: [Bug 1767795] Re: Error Message

Hi Seth,

I did like you said.

Thanks for helping!

Am 24.05.2018 um 00:37 schrieb Seth Arnold:
> Philipp, can you please run:
>
> apport-collect 1767795
>
> to get the apparmor-related artifacts?
>
> Thanks
>

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Hrm, I thought the logged information would include status on which profile failed to start. Bummer.

If you run: sudo /etc/init.d/apparmor reload
do you get any error messages there? Please paste the output here.

Thanks

Revision history for this message
Philipp Batram (philippbatram) wrote :

[....] Reloading apparmor configuration (via systemctl):
apparmor.serviceapparmor.service is not active, cannot reload.
  failed!

Am 04.06.2018 um 23:35 schrieb Seth Arnold:
> Hrm, I thought the logged information would include status on which
> profile failed to start. Bummer.
>
> If you run: sudo /etc/init.d/apparmor reload
> do you get any error messages there? Please paste the output here.
>
> Thanks
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.