Bug 58109 - kprinter under CUPS crashes when /etc/hostname and /etc/hosts are inconsistent
Summary: kprinter under CUPS crashes when /etc/hostname and /etc/hosts are inconsistent
Status: CLOSED DUPLICATE of bug 56263
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Goffioul
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-04 15:31 UTC by Bruce Miller
Modified: 2008-12-31 13:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Bruce Miller 2003-05-04 15:31:13 UTC 
Version:            (using KDE KDE 3.1.1)
Installed from:    Debian testing/unstable Packages
Compiler:          Debian unstable as of 2003-05-04; presumably therefore GCC 3.2 
OS:          Linux

- attempted to change hostname but changed only entry in /etc/hostname, rebooted
- kprinter began to crash consistently, including kcontrol printer module; in addition, calling print within KDE apps caused app to crash
- grepped and Googled hostname; corrected entry in /etc/hosts, ran command "hostname" and rebooted
- this resolved problem
- you may wish to have kdeprint report error rather than crash
Comment 1 Thiago Macieira 2003-05-04 19:35:11 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.
Comment 2 Nils Holland 2003-05-04 23:17:57 UTC 
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.
Comment 3 dispiste 2003-05-14 13:18:47 UTC 
From: C
Comment 4 Michael Goffioul 2003-05-14 13:28:49 UTC 
This is an "already-solved" problem. See the discussion about bug #56263.

*** This bug has been marked as a duplicate of 56263 ***
Comment 5 Thiago Macieira 2003-05-15 03:02:36 UTC 
And by the way, having a consistent IP configuration for the local host is mandatory 
if you want to use IP.
Comment 6 John Layt 2008-12-31 13:02:33 UTC 
Closing old Resolved status bug.