Custom Query (1145 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (328 - 330 of 1145)

Ticket Resolution Summary Owner Reporter
#719 fixed Passing invalid arguments to printing-config wrappers causes traceback jdreed

Reported by jdreed, 14 years ago.

Description

(See sipb,lprm,* from 16:38 on Tuesday for context)

If I pass an invalid argument (say, "-u", which CUPS and LPRng have never supported), I get a traceback as shown below. I should get a usage argument instead. I suspect this is probably as simple as putting parse_args in a try block, but testing is required.

jdreed@INFINITE-LOOP:~$ lprm -Pmark-the-great -u foo
Traceback (most recent call last):
  File "/usr/bin/lprm", line 9, in <module>
    load_entry_point('debathena.printing==1.23.2-ubuntu10.04', 'console_scripts', 'lprm.debathena')()
  File "/usr/lib/pymodules/python2.6/debathena/printing/lprm.py", line 29, in main
    sys.exit(_main(sys.argv)) # pragma: nocover
  File "/usr/lib/pymodules/python2.6/debathena/printing/lprm.py", line 25, in _main
    return simple.simple('lprm', opts, queue_opt, args)
  File "/usr/lib/pymodules/python2.6/debathena/printing/simple.py", line 22, in simple
    argstyle, options, arguments = common.parse_args(args, optinfo)
TypeError: 'NoneType' object is not iterable
#533 fixed Partitioning bug in lucid install amb jdreed

Reported by jdreed, 15 years ago.

Description

(Opening at the request of amb)

During the partitioning phase, the installer stops with: "You entered "" which was not recognized as a valid size". It then prompts for the amount of volume group to use for guided partitioning, defaulting to 159.8GB. If you answer yes, the install proceeds.

Relevant debugging output: --> FGET partman-auto-lvm/guided_size seen <-- 0 true --> SUBST partman-auto-lvm/guided_size MINSIZE 20.5 GB Adding [MINSIZE] -> [20.5 GB] <-- 0 --> SUBST partman-auto-lvm/guided_size MAXSIZE 159.8 GB Adding [MAXSIZE] -> [159.8 GB] <-- 0 --> SUBST partman-auto-lvm/guided_size PERCENT 12% Adding [PERCENT] -> [12%] <-- 0 --> INPUT high partman-auto-lvm/guided_size <-- 30 question ksipped --> GO <-- 0 ok --> GET partman-auto-lvm/guided_size <-- 0 true --> SUBST partman-auto-lvm/bad_guided_size INPUT Adding [INPUT] -> [] <-- 0 --> INPUT high partman-auto-lvm/bad_guided_size <-- 0 question will be asked --> GO

#600 fixed PAM should tell you if you're over quota jdreed

Reported by jdreed, 14 years ago.

Description

It should be possible to write a PAM module that checks if a user is over quota, and if so, fails with a useful error message.

If it is possible, we should do it.

Note: See TracQuery for help on using queries.