[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-05 Thread Till Kamppeter
Please ignore the last comment, it was meant for another bug. Sorry. -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs m

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-05 Thread Till Kamppeter
Patrice, can you run the following commands and post the output here: smbclient -N -L //192.168.1.100 nmblookup -R 'ENTREPRISE' nmblookup -A 192.168.1.102 nmblookup -A 192.168.1.103 nmblookup -A 192.168.1.104 nmblookup -A 192.168.1.105 The first one is used by s-c-p and probably will not give any

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-02 Thread Till Kamppeter
Tested also the CUPS 1.2.12-1ubuntu2 package now and with this system- config-printer works correctly, too. -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-02 Thread Till Kamppeter
With CUPS 1.3.0 RC2 this works out-of-the-box, so taking this version into Gutsy this bug is fixed immediately. Red Hat/Fedora (and these are the upstream developers of system-config-printer) have already switched on their development branch (Rawhide). Here you can get Ubuntu Gutsy packages (the b

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-02 Thread Martin Pitt
cupsys (1.2.12-1ubuntu2) gutsy; urgency=low * Drop our derooting changes. It still has some regressions, and with upstream not even acknowledging the need for improving cupsys' security we will sit on this forever. (LP: #119289, LP: #129634) - Drop derooting related patches: 06

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-02 Thread Martin Pitt
@Patrice: I am aware of this, but it's not yet decided whether we'll move to 1.3 in Gutsy. -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubun

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-02 Thread Martin Pitt
OK, I have a working profile now, let's go the apparmor route. ** Changed in: cupsys (Ubuntu) Sourcepackagename: system-config-printer => cupsys Assignee: Till Kamppeter => Martin Pitt -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You recei

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-02 Thread Patrice Vetsel
Pitti : be aware that Tim have packaged cups 1.3 -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-b

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-02 Thread Martin Pitt
Just for the record, I'll look into creating an apparmor profile for cups. If I succeed, we can drop the derooting patches and solve this bug along with bug 119289. -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received this bug notification

Re: [Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-01 Thread Martin Pitt
Hi, Till Kamppeter [2007-08-01 10:14 -]: > pitti, if you have already hacked the CUPS daemon to run non-root which > is not supported upstream, why don't you also hack the cupsd to not > close port 631 when receiving a HUP signal? That would be ideal, of course, but as I said, it is very intr

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-01 Thread Till Kamppeter
pitti, if you have already hacked the CUPS daemon to run non-root which is not supported upstream, why don't you also hack the cupsd to not close port 631 when receiving a HUP signal? -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received thi

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-01 Thread Tim Waugh
I should point out that restarting cupsd willy-nilly is *really* bad for users who print long-running jobs (i.e. lots of copies, lots of pages). Aborting their job half-way through, then restarting it, means they will have to check through *all* of the output paper to see what went wrong, and also

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-01 Thread Tim Waugh
Well, it can't be fixed properly in system-config-printer -- what about remote CUPS servers? Fix it in CUPS. -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received this bug notification because you are a member of Ubuntu Bugs, which is the b

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-01 Thread Martin Pitt
We do need in Ubuntu, since when cupsd tries to reinitialize itself, it drops the port binding to 631, and it cannot open this any more, since at that time it runs as unprivileged system user. So, while this is arguably a cups bug, it is very intrusive to fix in cupsd itself without upstream suppor

[Bug 129634] Re: Needs to properly restart cupsd after changing options

2007-08-01 Thread Tim Waugh
Why do you think it needs to restart cupsd? It doesn't. -- Needs to properly restart cupsd after changing options https://bugs.launchpad.net/bugs/129634 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list