AppArmor prevents mysqld from working in Digikam's internal-server MySQL mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
digikam (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: apparmor
I was trying to test Digikam's database migration to the "internal server" MySQL mode. It failed every time and I couldn't figure out why. Later I was looking in the kernel logs for another reason and saw these lines:
Mar 15 22:40:17 kubbie kernel: [66325.677327] type=1400 audit(130024681
ame="/sys/
Mar 15 22:40:17 kubbie kernel: [66325.768133] type=1400 audit(130024681
Mar 15 22:40:18 kubbie kernel: [66326.610800] type=1400 audit(130024681
Mar 15 22:40:18 kubbie kernel: [66326.610865] type=1400 audit(130024681
Mar 15 22:40:19 kubbie kernel: [66328.836977] type=1400 audit(130024681
I'm not sure if this should be reported against apparmor, mysql-server, or digikam.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: apparmor 2.5.1-0ubuntu0.
ProcVersionSign
Uname: Linux 2.6.35-27-generic i686
NonfreeKernelMo
Architecture: i386
Date: Wed Mar 16 02:55:38 2011
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=
SourcePackage: apparmor
Changed in digikam (Ubuntu): | |
assignee: | nobody → Felix Geyer (debfx) |
status: | Triaged → In Progress |
Changed in digikam (Ubuntu): | |
assignee: | Felix Geyer (debfx) → nobody |
status: | In Progress → Fix Committed |
Thank you for using Ubuntu and reporting a bug. The digikam packaging should be updated like akonadi's to use a wrapper script and separate apparmor profile.