Bug 56655 - SIGSEGV while trying to call kprinter
Summary: SIGSEGV while trying to call kprinter
Status: RESOLVED DUPLICATE of bug 56263
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.5.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-31 09:52 UTC by Claus Hentschel
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claus Hentschel 2003-03-31 09:52:36 UTC
Version:           1.5.1 (using KDE 3.1.1)
Installed from:    SuSE
Compiler:          gcc version 3.2
OS:          Linux (i686) release 2.4.19-4GB

After upgrading to KDE 3.1.1 I can't print anymore. I've detected it the first time using KMail but printing fails with any KDE application leading into a crash of that application.

Because it can be produced, too just by calling
	kprinter
from the command line in a bash it seems to me that it's a problem with kprinter.

Calling kprinter from a bash opens the kprinter dialog window for some seconds and then gives:
	kdecore (KSocket): ERROR: KExtendedSocket::connectionEvent()
		called but no data available!
Using the debugger, i.e. calling
	gdb kprinter
works correctly so I can' produce a stack report!! One visible difference is that the Button 'Print' ('Drucken' in german) has been de-activated while it is actived when using gdb.

Any idea what's going wrong?

Claus
Comment 1 Thiago Macieira 2003-03-31 14:31:08 UTC
It's already been reported and fixed. Thanks for the report, though 
 
Next time, please search the bug database for similar bugs before reporting. 

*** This bug has been marked as a duplicate of 56263 ***
Comment 2 Claus Hentschel 2003-04-02 11:39:27 UTC
Subject: Re:  SIGSEGV while trying to call kprinter

> ------- Additional Comments From thiagom@mail.com  2003-03-31 14:31 -------
> It's already been reported and fixed. Thanks for the report, though
>
> Next time, please search the bug database for similar bugs before
> reporting.
>
> *** This bug has been marked as a duplicate of 56263 ***

Sorry, but obviously I haven't searched too much ;-(

You wrote that bug has been **fixed**. Sorry to say, but that bug is NOT fixed 
on my system now.

I've downloaded kdelibs-3.1.1.tar.bz2 and tried to patch the sources with the 
patch shown in Message 56263. Copy&Paste the patch from konqueror into a file 
doesn't build a workable patch file ("patch: **** Only garbage was found in 
the patch input", indeed for example all @@ occurencies are replaced with 'at 
at'). Is the patch available as a file anywhere for download?

The official kdelib-3.1.1 source tarball does include rev. 1.44.2.4. The 
mentioned patch is based on rev. 1.54. Is there any patch available to 
upgrade from 1.44.2.4 to 1.56? Or do I have to load all from the cvs branch?

Supposed I'll get the file kextsock.cpp patched to 1.56, is it okay to only 
compile the kdelib-3.1.1 package or are there any dependencies so I have to 
compile the complete kde sources? (I don't have so much disk space and I'm 
only running a 450MHz PIII)

Or: is it better to downgrade to KDE 3.1?

Claus