Bug 95961 - Crashing at startup loading Samsung SCX-4100 modules
Summary: Crashing at startup loading Samsung SCX-4100 modules
Status: RESOLVED WORKSFORME
Alias: None
Product: kooka
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Klaas Freitag
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2004-12-29 03:17 UTC by Mark Herrick
Modified: 2018-10-27 02:47 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Herrick 2004-12-29 03:17:37 UTC
Version:           0.44 (using KDE KDE 3.3.1)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Kooka crashes when starting up, just after giving some error messages about trying to reload the drivers for my Samsung SCX-4100 Printer/Scanner/Copier.:

-----------------------------------------
mark@WorkStation:~$ kooka
insmod: error inserting '/lib/modules/2.6.9/kernel/drivers/mfpportctrl/mfpport.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.9/kernel/drivers/mfpportctrl/mfpport.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.9/kernel/drivers/mfpportctrl/mfpportprobe.ko': -1 File exists
KCrash: Application 'kooka' crashing...
-----------------------------------------

Here is the backtrace:
-----------------------------------------
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(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)
(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)
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231986560 (LWP 6663)]
(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0xb7365c73 in QObject::destroyed () from /usr/lib/libqt-mt.so.3
#5  0xb702615f in QObject::~QObject () from /usr/lib/libqt-mt.so.3
#6  0xb6fc2723 in QLayout::~QLayout () from /usr/lib/libqt-mt.so.3
#7  0xb700f52f in QBoxLayout::~QBoxLayout () from /usr/lib/libqt-mt.so.3
#8  0xb7011e0b in QVBoxLayout::~QVBoxLayout () from /usr/lib/libqt-mt.so.3
#9  0xb798306f in KDockWidget::setWidget () from /usr/lib/libkdeui.so.4
#10 0xb7981940 in KDockWidget::manualDock () from /usr/lib/libkdeui.so.4
#11 0x080683ed in ?? ()
#12 0x082fad88 in ?? ()
#13 0x082e7fc8 in ?? ()
#14 0x00000008 in ?? ()
#15 0x00000014 in ?? ()
#16 0x00000000 in ?? ()
#17 0x00000000 in ?? ()
#18 0x00000000 in ?? ()
#19 0xffffffff in ?? ()
#20 0x00000001 in ?? ()
#21 0x08108018 in ?? ()
#22 0x00000001 in ?? ()
#23 0xb72c4022 in QRealMutexPrivate::unlock () from /usr/lib/libqt-mt.so.3
#24 0x08063bc5 in ?? ()
#25 0x08139980 in ?? ()
#26 0x081312d8 in ?? ()
#27 0xbffff770 in ?? ()
#28 0x0809250a in _IO_stdin_used ()
#29 0x00010000 in ?? ()
#30 0x0809253c in _IO_stdin_used ()
#31 0xbffff6c8 in ?? ()
#32 0xb6c452ee in operator new () from /usr/lib/libstdc++.so.5
#33 0x08063676 in ?? ()
#34 0x081312d8 in ?? ()
#35 0xbffff770 in ?? ()
#36 0x080940e1 in _IO_stdin_used ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000001 in ?? ()
#40 0x08092525 in _IO_stdin_used ()
#41 0x00000000 in ?? ()
#42 0x08092510 in _IO_stdin_used ()
#43 0x080924eb in _IO_stdin_used ()
#44 0xb6a5c30c in ?? () from /lib/tls/i686/cmov/libc.so.6
#45 0xbffff750 in ?? ()
#46 0xb7ff1a4c in _dl_unload_cache () from /lib/ld-linux.so.2
#47 0xb6a69900 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#48 0x08063391 in ?? ()
-----------------------------------------

The printer works fine in other apps, and the scanner works fine in both the software supplied by Samsung (Yes they provide linux software and drivers!!!) and in XSane. XSane produces similar insmod messages at startup, but loads and works perfectly:

-----------------------------------------
mark@WorkStation:~$ xsane
insmod: error inserting '/lib/modules/2.6.9/kernel/drivers/mfpportctrl/mfpport.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.9/kernel/drivers/mfpportctrl/mfpportprobe.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.9/kernel/drivers/mfpportctrl/mfpport.ko': -1 File exists
insmod: error inserting '/lib/modules/2.6.9/kernel/drivers/mfpportctrl/mfpportprobe.ko': -1 File exists
-----------------------------------------

Let me know if I can provide any more information.
Comment 1 Sebastian Strand 2005-10-25 21:14:17 UTC
This happens to me as well. I'm using KDE 3.5 beta2.
Comment 2 Christoph Feck 2011-12-20 02:58:02 UTC
This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)
Comment 3 Andrew Crouthamel 2018-09-22 01:47:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 02:47:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!