https://bugs.kde.org/show_bug.cgi?id=509041

            Bug ID: 509041
           Summary: skanpage/skanlite crash in KSaneCore::Option::name()
                    with libksane/ksanecore 25.08.0
    Classification: Frameworks and Libraries
           Product: libksane
      Version First 25.08.0
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY

With libksane/ksanecore 25.08.0, both SKanpage and Skanlite immediately
coredump when starting on my machine.

After downgrading to libksane/ksanecore 25.04.3, both SKanpage 25.08.0 and
Skanlite 25.08.0 start working again and allow for successfully scanning.
Therefore, this looks like a regression introduced by libksane 25.08.0.

STEPS TO REPRODUCE
1. Launch SKanpage or SkanLite
2. 
3. 

OBSERVED RESULT
Both applications fail to start and immediately coredump.

EXPECTED RESULT
Both applications start.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION

Coredump stacktrace:

(gdb) bt
#0  __pthread_kill_implementation (threadid=<optimized out>,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1  0x00007f7893898a13 in __pthread_kill_internal (threadid=<optimized out>,
signo=11) at pthread_kill.c:89
#2  0x00007f789383e410 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3  0x00007f7897ab7e97 in KCrash::defaultCrashHandler (sig=11) at
/usr/src/debug/kcrash/kcrash-6.17.0/src/kcrash.cpp:605
#4  <signal handler called>
#5  0x00007f7897b09209 in KSaneCore::Option::name (this=0x0) at
/usr/src/debug/ksanecore/ksanecore-25.08.0/src/option.cpp:35
#6  0x00007f7897b006fa in KSaneCore::Interface::setOptionsMap
(this=this@entry=0x55cee32995d0, options=...) at
/usr/src/debug/ksanecore/ksanecore-25.08.0/src/interface.cpp:432
#7  0x000055ceb2f23977 in Skanpage::loadScannerOptions (this=0x55cee3048551) at
/usr/src/debug/skanpage/skanpage-25.08.0/src/Skanpage.cpp:388
#8  Skanpage::finishOpeningDevice (this=this@entry=0x7ffe473df3b0,
deviceName=..., deviceVendor=..., deviceModel=...) at
/usr/src/debug/skanpage/skanpage-25.08.0/src/Skanpage.cpp:468
#9  0x000055ceb2f25600 in Skanpage::openDevice (this=0x7ffe473df3b0,
deviceName=..., deviceVendor=..., deviceModel=...) at
/usr/src/debug/skanpage/skanpage-25.08.0/src/Skanpage.cpp:416
#10 0x000055ceb2efdef1 in Skanpage::Skanpage (parent=0x0, this=0x7ffe473df3b0,
deviceName=..., dumpOptionUrl=..., importUrl=...) at
/usr/src/debug/skanpage/skanpage-25.08.0/src/Skanpage.cpp:126
#11 main (argc=<optimized out>, argv=<optimized out>) at
/usr/src/debug/skanpage/skanpage-25.08.0/src/main.cpp:102
(gdb) 

KSaneCore::Option::name() is called with a null pointer ...

In case it helps, I'm using a network scanner.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to