[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 56655] New: SIGSEGV while trying to call kprinter
From:       Claus Hentschel <claus.hentschel () onlinehome ! de>
Date:       2003-03-31 7:52:38
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=56655     
           Summary: SIGSEGV while trying to call kprinter
           Product: kmail
           Version: 1.5.1
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kmail@kde.org
        ReportedBy: claus.hentschel@onlinehome.de


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
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail


[prev in list] [next in list] [prev in thread] [next in thread]