Bug 179500 - crash with signal 11 (SIGSEGV)
Summary: crash with signal 11 (SIGSEGV)
Status: RESOLVED WORKSFORME
Alias: None
Product: Skanlite
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kåre Särs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-01-03 17:00 UTC by Joe Rickenbacher
Modified: 2018-10-21 04:46 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Rickenbacher 2009-01-03 17:00:06 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Below the crash report:

Application: Skanlite (skanlite), signal SIGSEGV
(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 0xb60b66c0 (LWP 7877)]
(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)
[KCrash handler]
#5  0xb4a82bf5 in ?? () from /usr/lib/libmfp.so
#6  0xb4a84842 in m_parport_ECP_supported () from /usr/lib/libmfp.so
#7  0xb4a84cfd in port_init () from /usr/lib/libmfp.so
#8  0xb4a84e8f in dpa_init () from /usr/lib/libmfp.so
#9  0xb4a7e58f in mfp_get_devices () from /usr/lib/libmfp.so
#10 0xb4aa94ea in port::init_mfp_port_control ()
   from /usr/lib/sane/libsane-smfp.so.1
#11 0xb4a99039 in device::init_mfp_port_control ()
   from /usr/lib/sane/libsane-smfp.so.1
#12 0xb4a9b2f9 in driver::init_mfp_port_control ()
   from /usr/lib/sane/libsane-smfp.so.1
#13 0xb4a96e06 in backend::init () from /usr/lib/sane/libsane-smfp.so.1
#14 0xb4a9681a in sane_smfp_init () from /usr/lib/sane/libsane-smfp.so.1
#15 0xb63f411d in ?? () from /usr/lib/libsane.so.1
#16 0xb63f441d in sane_dll_get_devices () from /usr/lib/libsane.so.1
#17 0xb63f52e4 in sane_get_devices () from /usr/lib/libsane.so.1
#18 0xb74bfb08 in KSaneIface::KSaneWidget::selectDevice ()
   from /usr/lib/libksane.so.0
#19 0x0804fcec in _start ()
#0  0xb7f28430 in __kernel_vsyscall ()
Comment 1 Kåre Särs 2009-01-04 08:32:12 UTC
Could you tell me a bit about the circumstances?

Does it crash with XSane, scanimage or some other scan application?

Does it crash if the scanner is turned off?

If you know the backend name try: skanlite -d <backend>

I'll be on vacation for one week from today...
Comment 2 Dario Andres 2009-05-17 01:01:31 UTC
Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-19 04:32:00 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 mark the bug 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-21 04:46:45 UTC
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!