Bug 75563 - Trying to install a Samsung ML-4500 printer via LP0 ( LPR printing system ), can choose port, then printer, after choosing print driver, crashes with sig 11
Summary: Trying to install a Samsung ML-4500 printer via LP0 ( LPR printing system ), ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmprintmgr (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-18 23:42 UTC by Nigel Brodt-Savage
Modified: 2006-11-18 12:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nigel Brodt-Savage 2004-02-18 23:42:56 UTC 
Version:            (using KDE KDE 3.2.0)
Installed from:    Gentoo Packages
Compiler:          GCC 3.3.2-r5 CHOST="i686-pc-linux-gnu" 
OS:          Linux

Trying to install a Samsung ML-4500 printer via LP0 ( LPR printing system ), can choose port, then printer, after choosing print driver, crashes with sig 11

Using an ABIT VIA based board K133 based board, sorry can't remember the model #

Only got the below from the KDE Crash handler.

(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3065)]
0x4109c638 in waitpid ()
   from /lib/libpthread.so.0
#0  0x4109c638 in waitpid () from /lib/libpthread.so.0
#1  0x407f2ccc in ?? () from /usr/kde/3.2/lib/libkdecore.so.4
#2  0x40732fe1 in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.2/lib/libkdecore.so.4
Comment 1 Philip Rodrigues 2006-09-20 13:35:20 UTC 
Does this problem still occur for you with KDE 3.5?
Comment 2 Philip Rodrigues 2006-11-18 12:21:33 UTC 
Feedback timeout, but please reopen if the bug is still present for you in 3.5