Custom Query (1145 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (85 - 87 of 1145)

Ticket Resolution Summary Owner Reporter
#155 duplicate acroread attempts to use CUPS-specific optoins to lpr broder

Reported by broder, 14 years ago.

Description

acroread seems to sort of half-grok CUPS - well enough to query the library for a list of CUPS printers, but instead of printing through the library, it shells out to lpr.

It also passes -o options of one sort or another, which doesn't work currently, because our lpr almost always shells out to mit-lpr, so you get a popup to the effect of:

The following error occurred while printing...
'lpr: illegal option 'o'
Usage: lpr [-Pprinter@host]] [-A] [-B] [-Cclass] [-Fformat] [-G] [-Jinfo]

etc.

I'm...not sure if I'm actually interested in investing effort in fixing this, given that the long-term strategy is to actually use CUPS.

#157 fixed sendbug cancel fails wdc

Reported by wdc, 14 years ago.

Description

As per report filed in bugs:

Repeat by:

  1. Applications->System Tools->Report an Athena bug
  2. In the :Add a new entry alert, instead of specifying a program,

click the "Cancel" button.

Expected behavior:

Sendbug should have aborted.

Actual behavior:

An alert popped up letting me know I was going to get a text editor window to report my bug. Indeed, the editor window popped up after that.

This is, perhaps a cosmetic bug, but a user did trouble themself to report it...

#167 wontfix debathena-lert-server binds only to localhost broder

Reported by broder, 14 years ago.

Description

debathena-lert-server uses gethostbyname(uname().nodename) as the address to bind to. Unfortunately, on most Ubuntu systems, this works out to being 127.0.1.1 instead of the actual IP address, thanks to Ubuntu's /etc/hosts hacks.

More fun, the krb4 code needs the destination address of incoming packets for the encryption of the reply, so we can't simply switch to listening on INADDR_ANY with no other changes.

I see two options:

  1. Change the code to use recvmsg instead of recvfrom, in which case you can get at the destination address of the incoming packets at the expense of substantially increased complexity. See  http://tinyurl.com/d79x9r for an example of how to do this.
  1. Tear out the krb4 code. The krb5 protocol was introduced in 2002, and it seems pretty unlikely that krb4 clients are still around. It's already nicely conditionalized out so that it'll build on squeeze.
Note: See TracQuery for help on using queries.