Bug 247027 - Skanlite crash upon opening
Summary: Skanlite crash upon opening
Status: RESOLVED WORKSFORME
Alias: None
Product: Skanlite
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Kåre Särs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-08-08 02:57 UTC by milowhenderson1
Modified: 2018-10-21 05:07 UTC (History)
0 users

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 milowhenderson1 2010-08-08 02:57:21 UTC
Application: skanlite (0.4)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
Using a HPscan jet. kscanlite crashed when starting program. Scanner seems to be installed ok and completes test ok.

 -- Backtrace:
Application: Skanlite (skanlite), signal: Segmentation fault
[KCrash Handler]
#6  0xb74a4e63 in KSaneIface::KSaneOptFSlider::getMaxValue (this=0x81522b8, max=@0xbf845fbc) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/options/ksane_opt_fslider.cpp:151
#7  0xb749db09 in KSaneIface::KSaneWidgetPrivate::setTLY (this=0x8126160, ftly=0) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/ksane_widget_private.cpp:513
#8  0xb749fa65 in KSaneIface::KSaneWidgetPrivate::qt_metacall (this=0x8126160, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbf8460e8)
    at /usr/src/debug/kdegraphics-4.4.4/build/libs/libksane/libksane/ksane_widget_private.moc:115
#9  0xb6d34efd in QMetaObject::metacall (object=0x8126160, cl=QMetaObject::InvokeMetaMethod, idx=16, argv=0xbf8460e8) at kernel/qmetaobject.cpp:237
#10 0xb6d43fe8 in QMetaObject::activate (sender=0x81521a8, m=0xb74b3d58, local_signal_index=0, argv=0xbf8460e8) at kernel/qobject.cpp:3295
#11 0xb74a53a5 in KSaneIface::KSaneOptFSlider::fValueRead (this=0x81521a8, _t1=0) at /usr/src/debug/kdegraphics-4.4.4/build/libs/libksane/libksane/ksane_opt_fslider.moc:89
#12 0xb74a54f3 in KSaneIface::KSaneOptFSlider::readValue (this=0x81521a8) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/options/ksane_opt_fslider.cpp:120
#13 0xb749de9f in KSaneIface::KSaneWidgetPrivate::optReload (this=0x8126160) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/ksane_widget_private.cpp:432
#14 0xb749f9cc in KSaneIface::KSaneWidgetPrivate::qt_metacall (this=0x8126160, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbf84638c)
    at /usr/src/debug/kdegraphics-4.4.4/build/libs/libksane/libksane/ksane_widget_private.moc:111
#15 0xb6d34efd in QMetaObject::metacall (object=0x8126160, cl=QMetaObject::InvokeMetaMethod, idx=12, argv=0xbf84638c) at kernel/qmetaobject.cpp:237
#16 0xb6d43fe8 in QMetaObject::activate (sender=0x81911c0, m=0xb74b39a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#17 0xb74a14e5 in KSaneIface::KSaneOption::optsNeedReload (this=0x81911c0) at /usr/src/debug/kdegraphics-4.4.4/build/libs/libksane/libksane/ksane_option.moc:86
#18 0xb74a18b0 in KSaneIface::KSaneOption::writeData (this=0x81911c0, data=0xb354f94e) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/options/ksane_option.cpp:130
#19 0xb74a6c39 in KSaneIface::KSaneOptCombo::setValue (this=0x81911c0, val=...) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/options/ksane_opt_combo.cpp:389
#20 0xb749d730 in KSaneIface::KSaneWidgetPrivate::setDefaultValues (this=0x8126160) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/ksane_widget_private.cpp:406
#21 0xb749727f in KSaneIface::KSaneWidget::openDevice (this=0x8125f00, device_name=...) at /usr/src/debug/kdegraphics-4.4.4/libs/libksane/libksane/ksane_widget.cpp:426
#22 0x08052390 in _start ()

Reported using DrKonqi
Comment 1 Kåre Särs 2010-10-29 18:48:29 UTC
Thanks,

This looks like a bug in the backend...

Do you still have the problem in with KDE 4.5.x?
Comment 2 Andrew Crouthamel 2018-09-20 22:13:29 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 3 Andrew Crouthamel 2018-10-21 05:07:54 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!