Bug#697331: installation-reports: Printer not working / recognised - Fixed - 2

2013-01-09 Thread jswmb01x
About the fix : As the name implies, it helped me to get the printer working, but was not the right/best way to do it. As I never used CUPS before (no need in squeeze !), I was confused when it was asking for username/password. I entered the name of the user for which I wanted print capability.

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-08 Thread Brian Potkin
On Tue 08 Jan 2013 at 07:14:26 +0100, Christian PERRIER wrote: > Quoting jswmb01x (jswmb...@mobistarmail.be): > > > > Clarification : > > Adding "user1" to the lpadmin group was required to add the printer in CUPS > > (otherwise after entering the user name and password the operation is > > "fo

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-07 Thread Philipp Kern
On Tue, Jan 08, 2013 at 07:14:26AM +0100, Christian PERRIER wrote: > Quoting jswmb01x (jswmb...@mobistarmail.be): > > Clarification : > > Adding "user1" to the lpadmin group was required to add the printer in CUPS > > (otherwise after entering the user name and password the operation is > > "forb

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-07 Thread Christian PERRIER
Quoting jswmb01x (jswmb...@mobistarmail.be): > > Clarification : > Adding "user1" to the lpadmin group was required to add the printer in CUPS > (otherwise after entering the user name and password the operation is > "forbidden"), not for printing. Hmmm, well, then I would say this is cups tha

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-07 Thread jswmb01x
Clarification : Adding "user1" to the lpadmin group was required to add the printer in CUPS (otherwise after entering the user name and password the operation is "forbidden"), not for printing. Test : remove user1 from lpadmin & print root? root? id user1 uid=1000(user1) gid=1000(user1) grou

Processed: Re: Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 697331 user-setup Bug #697331 {Done: Christian PERRIER } [installation-reports] installation-reports: Printer not working / recognised Bug reassigned from package 'installation-reports' to 'user-setup'. Ignoring request to alter found ve

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-07 Thread Christian PERRIER
reassign 697331 user-setup retitle 697331 Please add the first created user to lpadmin thanks Quoting Brian Potkin (claremont...@gmail.com): > The problem encountered by de28jihem in setting up and administering a > print queue is not uncommon; #680195 gives another example. > > The list of "use

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-07 Thread Brian Potkin
On Sun 06 Jan 2013 at 06:53:46 +0100, Christian PERRIER wrote: > Quoting de28jihem (de28ji...@scarlet.be): > > > > The user was not in lpadmin group (checked with "id"). > > This caused problem to use the CUPS configuration menu (localhost:631). > > > > Added the user in lpadmin (under root) : >

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-05 Thread Christian PERRIER
Quoting de28jihem (de28ji...@scarlet.be): > > The user was not in lpadmin group (checked with "id"). > This caused problem to use the CUPS configuration menu (localhost:631). > > Added the user in lpadmin (under root) : > > usermod -a -G lpadmin user1 > > Plugged in printer/scan. > > Started a

Bug#697331: installation-reports: Printer not working / recognised - Fixed

2013-01-05 Thread de28jihem
The user was not in lpadmin group (checked with "id"). This caused problem to use the CUPS configuration menu (localhost:631). Added the user in lpadmin (under root) : > usermod -a -G lpadmin user1 Plugged in printer/scan. Started a web browser, url "localhost:631" (the CUPS interface) Select t