Summary: | kprinter under CUPS crashes when /etc/hostname and /etc/hosts are inconsistent | ||
---|---|---|---|
Product: | [Applications] kdeprint | Reporter: | Bruce Miller <bugs> |
Component: | general | Assignee: | Michael Goffioul <kdeprint_bugs> |
Status: | CLOSED DUPLICATE | ||
Severity: | crash | CC: | dispiste, jlayt |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Bruce Miller
2003-05-04 15:31:13 UTC
Can you paste the backtrace? Also, can you please test with KDE 3.1.1a? I believe it's a certain bug that has been corrected. Anyways, you should never have a computer with a hostname that doesn't resolve to an IP. I would be able to provide more details if I currently had access to the computer where this occurs, but right now all I can say is the following: On my KDE 3.1.1a machine (compiled myself using GCC 3.2), something like this seems to occur. Basically, my /etc/hostname and /etc/hosts are in-sync, but the following seems to cause trouble: First, it's important to notice that I have an Ethernet card with a fixed IP, and a modem which does dial-on-demand, gets a dynamic IP assigned, and sets its peer as default gateway upon every connection. Now, after a fresh reboot, printing from KDE to cups works just fine. *However* as soon as my modem establishes its first connection, the behavior the original reporter mentioned occurs (crash of the KDE application from which I try to print). This problem does not go away when the modem hangs up, it seems to persist until I reboot, and starts all over again after my modem establishes its first connection after the reboot. Again, I'm currently not at the machine which experiences this problem, so I cannot right now provide more information. I will do, however, as soon as I had a chance to look into it some more. From: C This is an "already-solved" problem. See the discussion about bug #56263. *** This bug has been marked as a duplicate of 56263 *** And by the way, having a consistent IP configuration for the local host is mandatory if you want to use IP. Closing old Resolved status bug. |