[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#882937: marked as done (apparmor: cupsd profile blocks creation of PDF files with printer-driver-cups-pdf)

Your message dated Sat, 09 Jun 2018 21:21:31 +0200
with message-id <85h8mbzryc.fsf@boum.org>
and subject line Re: Bug#882937: apparmor: cupsd profile blocks creation of PDF files with printer-driver-cups-pdf
has caused the Debian Bug report #882937,
regarding apparmor: cupsd profile blocks creation of PDF files with printer-driver-cups-pdf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
882937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882937
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apparmor
Version: 2.11.1-3
Severity: normal

Dear Maintainer,

Enabling apparmor blocks the creation of PDF files with 
printer-driver-cups-pdf, since the output files are created in 
~/PDF. Temporarily disabling the /etc/apparmor.d/usr.sbin.cupsd profile 
restores printing to pdf files.

Thanks,

Nuno.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=pt_PT.UTF8, LC_CTYPE=pt_PT.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to pt_PT.UTF8), LANGUAGE=pt_PT:pt_BR:en (charmap=UTF-8) (ignored: LC_ALL set to pt_PT.UTF8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  libc6                  2.25-2
ii  lsb-base               9.20170808
ii  python3                3.6.3-2

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-profiles        2.11.1-3
ii  apparmor-profiles-extra  1.16
ii  apparmor-utils           2.11.1-3

-- debconf information:
* apparmor/homedirs:


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/24 CPU cores)
Locale: LANG=pt_PT.UTF8, LC_CTYPE=pt_PT.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to pt_PT.UTF8), LANGUAGE=pt:pt_BR:en (charmap=UTF-8) (ignored: LC_ALL set to pt_PT.UTF8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  libc6                  2.24-17
ii  lsb-base               9.20170808
ii  python3                3.6.3-2

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-profiles        2.11.1-3
ii  apparmor-profiles-extra  1.16
ii  apparmor-utils           2.11.1-3

-- debconf information:
* apparmor/homedirs:

--- End Message ---
--- Begin Message --- 
intrigeri:
> Brian Potkin:
>> On Thu 07 Dec 2017 at 10:51:26 +0100, intrigeri wrote:
>>> If using a non-standard parent directory for home directories, you'll
>>> need to let AppArmor know about it. Thankfully we have everything in
>>> place to do this: adding @{HOMEDIRS}+=/home/host to
>>> /etc/apparmor.d/tunables/home.d/site.local should do the trick.
>>> Then, "sudo systemctl restart apparmor" and retry.
>>> 
>>> Does this fix the problem you're experiencing?

>> Does this work for you, Nuno?

> A few months later: ping?

Two months later:

> @maintainers: I'm pretty sure we've identified the root cause of the
> problem and a workaround is available, so I recommend closing this bug
> unless Nuno tells us the workaround does not fix the problem within
> a month or two. If you feel like the workaround for this corner case
> should be documented, let me know or file a bug against src:apparmor
> directly :)

… I'm closing this bug.

Cheers,
-- 
intrigeri

--- End Message ---
Reply to: