very long lines in /etc/hosts cause cupsd to segfault

Bug #321920 reported by canavan
2
Affects Status Importance Assigned to Milestone
cups (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: cups

An unknown process (something, most likely some security update in hardy) has converted an adblocking /etc/hosts file from a one ip, one hostname per line format to one ip followed by all hostnames. As a result, gnome desktop logins in hardy failed, and cupsd in intrepid segfaults at startup. Deleting the extremely long line in the hosts file fixed both problems.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. Please also attach an example to the report, thanks.

Changed in cups (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

added a 500 chars line to /etc/hosts on Jaunty alpha as of 3/20/2009 and I was unable to reproduce the behavior.

Revision history for this message
canavan (rainer-ubuntu) wrote :

500 chars isn't very long. Could you please retry with 100k chars or so?

Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

added one 10k line and then one 100k line
  wc /etc/hosts
  25 174 106264

Then restarted jaunty (to rule out desktop login failure) and restarted cups

  sudo /etc/init.d/cups/restart
  * Restarting Common Unix Printing System: cupsd [ OK ]
  sudo /etc/init.d/cup status
  Status of Common Unix Printing System: cupsd is running.

As both restarts succeeded, I can't reproduce the behavior either.

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Seems to be fixed in the current CUPS package.

Changed in cups (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.