Hi Rutger,

thank you for reporting the issue!

Ok, so the core of the issue seems the same - the iterator 'size' is again 257 as in #1761530, and the number of elements in the vector 'rgamma' is lesser, so the access outside of the vector causes the abort.

The question is how many elements are in the 'rgamma' vector - the vector itself can be a vector 'dev->gamma_override_tables[0]' if it is not empty, or be created from default template by 'sanei_genesys_create_default_gamma_table()'.

Let's say it is generated from template for now, because it was the case with previous crashes - then I will need to know asic type of the scanner.

--------------------------------------------------------------

So it would be great if you ran xsane in gdb, set breakpoints on sanei_genesys_create_default_gamma_table, run the program, print 'dev->model->asic_type' once it stops and tell me the output.

$ gdb /usr/bin/xsane
(gdb) b sanei_genesys_create_default_gamma_table
(gdb) r
(gdb) p dev->model->asic_type

Result of gdb xsane (after first hit of the breakpoint)

(gdb) print dev->model->asic_type
Attempt to extract a component of a value that is not a structure pointer.
(gdb) print dev->model
$1 = (SANE_String_Const) 0x7fffe34a594d "ScanJet 5S"
(gdb) c
Continuing.

Thread 1 "xsane" hit Breakpoint 1, genesys::sanei_genesys_create_default_gamma_table (dev=0x55555577ad80, gamma_table=std::vector of length 0, capacity 0, gamma=1) at genesys/genesys.cpp:359
359	{
(gdb) print dev->model->asic_type
$2 = genesys::AsicType::GL845
(gdb) print dev->model
$3 = (const genesys::Genesys_Model *) 0x55555577ede0

Thank you for the data!

So from sanei_genesys_create_default_gamma_table():

    } else if (dev->model->asic_type == AsicType::GL124 ||
               dev->model->asic_type == AsicType::GL846 ||
               dev->model->asic_type == AsicType::GL847) {
        size = 257; 
        max = 65535;
    } else {
        size = 256; 
        max = 65535;
    }

GL845 is missing, so the size is assigned to 256, which is lesser than the size from sanei_genesys_send_gamma_table().

Would you mind trying the testing rpms if they help? 

https://koji.fedoraproject.org/koji/taskinfo?taskID=81509612

Once I have your confirmation, I'll send the patch upstream.

It works just fine now, bug fixed. Thanks a lot!

Thank you for letting me know! I've sent the patch upstream as https://gitlab.com/sane-project/backends/-/merge_requests/688 .

FEDORA-2022-274a29eeef has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-274a29eeef

FEDORA-2022-2667d76e7f has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-2667d76e7f

FEDORA-2022-2667d76e7f has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-2667d76e7f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2667d76e7f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-274a29eeef has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-274a29eeef`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-274a29eeef

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2022-2667d76e7f has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

FEDORA-2022-274a29eeef has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.