Removing dapper milstone.
** Changed in: cupsys (Ubuntu Dapper)
Target: dapper-updates => None
--
cupsd can't access /var/log/cups/error_log permission denied
https://bugs.launchpad.net/bugs/54277
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Removing verification-needed task.
** Tags removed: verification-needed
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Tags added: verification-needed
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
We will not fix this in Dapper. It only affects few people and the
impact is relatively low, thus it is not worth the risk of getting a
regression through an SRU.
** Changed in: cupsys (Ubuntu Dapper)
Status: In Progress => Rejected
--
cupsd can't access /var/log/cups/error_log permission
According to Martin Pitt this fixes the last regression caused by
running CUPS as non-root user.
** Changed in: cupsys (Ubuntu)
Status: Fix Committed => Fix Released
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing
I have now fixed it by correcting the permissions after starting the
daemon, as Ralf Hildebrandt said.
Get the corrected packages for testing here:
http://www.linux-foundation.org/~till/tmp/ubuntu/feisty/cupsys/
My CUPS daemon is now happily logging and I hope this helps us to fix
the other prin
Very bizarre:
# ll *_log
-rw-r- 1 cupsys lpadmin 0 2006-10-31 09:45 access_log
-rw-r--r-- 1 root lp 227932 2006-10-31 09:45 error_log
-rw-r- 1 cupsys lpadmin 0 2006-10-31 09:45 page_log
[EMAIL PROTECTED]:/var/log/cups# /etc/init.d/cupsys stop
* Stopping Common Unix Print
** Changed in: cupsys (Ubuntu Dapper)
Target: None => dapper-updates
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Tags added: printing
** Tags removed: verification-needed
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Setting dapper back to 'in progress', too. The current -proposed upload
certainly improves matters a bit, but not completely.
** Changed in: cupsys (Ubuntu Dapper)
Status: Fix Committed => In Progress
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bu
Removing milestone tag. The remaining issues need to be addressed in
Edgy+1.
** Changed in: cupsys (Ubuntu)
Status: Confirmed => In Progress
Target: ubuntu-6.10 => None
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs
oops /etc/logrotate.d/cupsys existsmispoke obviously..
and yet how does this connect with MaxLogSize? I must admit
to being a bit confused..
/etc/logrotate.d/cupsys:
/var/log/cups/*log {
daily
missingok
rotate 7
sharedscripts
postrotate
On Fri, Oct 13, 2006 at 09:08:54PM -, Walter Tautz wrote:
> Doesn't cupsd do it's own logrotating. Looking in /etc/logrotate.conf
> I have:
> [...]
> # packages drop log rotation information into this directory
> include /etc/logrotate.d
See above.
--
- mdz
--
cupsd can't access /var/log/
cupsd does its own log rotating, not logrotate. So it implies
that cupsd does not set the permission properly when this
happens nor when it starts up from scratch.
Wrt the changes in /etc/init.d/cupsys we see that the chown
stuff is before cupsd starts up...clearly it should come after
starting i
Simon Law wrote:
> Confirmed Walter and Till's comments.
>
> A sane thing to do might be to have logrotate remember the permissions
> of the file it moves away, and then recreates them? This would solve
> the general case for any application that has its logs rotated.
>
>
Doesn't cupsd do it's
Simon, you suggestion will not work, as CUPS has to open the new file
(we have taken the open file away and provided a new file which is not
yet opened by CUPS) and with dropped privileges CUPS cannot open a file
with these permissions/ownerships.
--
cupsd can't access /var/log/cups/error_log per
Confirmed Walter and Till's comments.
A sane thing to do might be to have logrotate remember the permissions
of the file it moves away, and then recreates them? This would solve
the general case for any application that has its logs rotated.
--
cupsd can't access /var/log/cups/error_log permiss
** Tags added: verification-needed
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The problem is caused by logrotate. As soon as logrotate takes the
error_log away from CUPS, CUPS needs to open a new error_log and does
not succeed.
Either we must hack CUPS, so that it sets our ownerships (so that it re-
opens the file as normal user without problem) or we must make logrotate
pl
I can confirm Till's observations with a slight caveat.
Prior to stoping cupsd I get ownership cupsys.lp on error_log
and after I stop it still has ownership cupsys.lp.
If I start it it has ownership root.lp until the error_log gets rolled
at which point the new instance of error_log has ownershi
For me strange things happen:
[EMAIL PROTECTED]:~$ ls -l /var/log/cups/error_log
-rw-r--r-- 1 root lp 1648147 2006-10-13 10:24 /var/log/cups/error_log
[EMAIL PROTECTED]:~$ sudo /etc/init.d/cupsys stop
* Stopping Common U
Hi Walter,
Walter Tautz [2006-10-12 13:12 -]:
> Just did an apt-get install cupsys to get the new version.
> If one does /etc/init.d/cupsys stop
> and /etc/init.d/cupsys start then ls -al /var/log/cups/error_log is:
> -rw-r--r-- 1 root lp 834320 2006-10-12 09:07 /var/log/cups/error_log
> at le
Just did an apt-get install cupsys to get the new version.
If one does /etc/init.d/cupsys stop
and /etc/init.d/cupsys start then ls -al /var/log/cups/error_log is:
-rw-r--r-- 1 root lp 834320 2006-10-12 09:07 /var/log/cups/error_log
at least initially and then about a minute later it has ownership
Package is in dapper-proposed. Testing and feedback would be highly
appreciated! It will go into -updates next Wednesday if all goes well.
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
** Attachment added: "debdiff for dapper-proposed upload"
http://librarian.launchpad.net/4320046/cupsys.54277.diff
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
Bah, sorry for comment #16 which was the changelog for the hal bug
56484.
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Already fixed in edgy a while ago.
** Changed in: cupsys (Ubuntu)
Status: Fix Committed => Fix Released
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
Attaching updated patch for SRU request.
** Attachment added: "fixed patch"
http://librarian.launchpad.net/4313481/patch
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
cupsys (1.2.3-1ubuntu1) edgy; urgency=low
.
* Merge recent bug fixes from Debian (see Kenshi's changes in 1.2.3-1 for
Ubuntu-relevant details). 00_r5958.dpatch has the following fixes from
upstream:
- The "All Documents" link in the on-line help was missing a trailing
sla
Yup, sorry, of course this was supposed to be
[ -e /var/log/cups/$l ] || touch /var/log/cups/$l
(&& doesn't work well in -e scripts). Fixed in svn head.
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@l
I think, the
[ -e /var/log/cups/$l ] && touch /var/log/cups/$l
in the patch must be replaced by
[ ! -e /var/log/cups/$l ] && touch /var/log/cups/$l
as the file should only be created if it is not already there.
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.
Easy patch and high-impact, thus appropriate for dapper-updates. Matt,
can you please add your blessing here?
** Changed in: cupsys (Ubuntu Dapper)
Importance: Untriaged => High
Assignee: (unassigned) => Martin Pitt
Status: Unconfirmed => Fix Committed
--
cupsd can't access /var/l
** Attachment added: "patch to fix this bug"
http://librarian.launchpad.net/4228103/patch
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
Fixed in development version, will be uploaded after Knot-3 freeze.
** Changed in: cupsys (Ubuntu)
Status: In Progress => Fix Committed
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
A fresh cupsys installation does not have this problem, but there might
be a bug on upgrades. I'll look into this soon.
** Changed in: cupsys (Ubuntu)
Assignee: (unassigned) => Martin Pitt
Status: Confirmed => In Progress
--
cupsd can't access /var/log/cups/error_log permission denie
** Changed in: cupsys (Ubuntu)
Importance: Untriaged => High
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Still a problem with 1.2.2 release of Ubuntu package...
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Pascal De Vuyst wrote:
> I'm using Dapper 6.06 LTS with cupsys 1.2.1-0ubuntu2.
>
> As indicated by Walter when I do:
>
> $ ls -l /var/log/cups/error_log
> -rw-r--r-- 1 root lp 190608 2006-07-28 10:45 /var/log/cups/error_log
>
> $ sudo chown cupsys /var/log/cups/error_log*
>
> $ ls -l /var/log/cups/
I'm using Dapper 6.06 LTS with cupsys 1.2.1-0ubuntu2.
As indicated by Walter when I do:
$ ls -l /var/log/cups/error_log
-rw-r--r-- 1 root lp 190608 2006-07-28 10:45 /var/log/cups/error_log
$ sudo chown cupsys /var/log/cups/error_log*
$ ls -l /var/log/cups/error_log
-rw-r--r-- 1 cupsys lp 195464
Hm. I can't confirm this.
If you take a look at your perms, you'll see that it was cupsys:lp
before, but something/somehow changed to root:lp. On a fresh Dapper
install permissons are cupsys:lp and stay that way after cups restart.
If everybody had perms root:lp, then we wouldn't be able to solve
I just noticed the same thing, see relevant part of my /var/log/syslog in
attachment.
Confirming this bug.
** Changed in: cupsys (Ubuntu)
Status: Unconfirmed => Confirmed
--
cupsd can't access /var/log/cups/error_log permission denied
https://launchpad.net/bugs/54277
--
ubuntu-bugs mail
41 matches
Mail list logo
