June 2026 - Koha-bugs - lists.koha-community.org

[Bug 34602] New: Failing tests during package build
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34602 Bug ID: 34602 Summary: Failing tests during package build Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: koha(a)skrivy.net QA Contact: testopia(a)bugs.koha-community.org Trying to build current 22.11.x branch without success due to failing tests. I know about option to skip tests, but we don't want to use it at the moment. Test Summary Report ------------------- t/Auth.t (Wstat: 512 Tests: 1 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 12 tests but ran 1. t/AuthoritiesMarc_MARC21.t (Wstat: 65280 Tests: 5 Failed: 1) Failed test: 5 Non-zero exit status: 255 t/Labels.t (Wstat: 512 Tests: 10 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 11 tests but ran 10. t/Labels_split_lccn.t (Wstat: 512 Tests: 3 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 69 tests but ran 3. t/Output.t (Wstat: 65280 Tests: 7 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 8 tests but ran 7. t/Search.t (Wstat: 65280 Tests: 4 Failed: 1) Failed test: 4 Non-zero exit status: 255 Files=88, Tests=2032, 157 wallclock secs ( 0.55 usr 0.12 sys + 108.08 cusr 14.39 csys = 123.14 CPU) Result: FAIL Full scenarion (including docker installation) in the attachment. Tested on Debian Buster, which should be current build version. Tested also without docker, we receive the same errors. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 34578] New: Check-in table should have a column to display hold status
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34578 Bug ID: 34578 Summary: Check-in table should have a column to display hold status Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice if the checked in table on the check-in screen would include a column displaying holds status. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 34150] New: Personal name (100a) field missing tag editor on acquisition framework
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34150 Bug ID: 34150 Summary: Personal name (100a) field missing tag editor on acquisition framework Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 152833 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=152833&action=e… Missing tag editor button With the RequireChoosingExistingAuthority set to required for cataloging, this requirement is now enforced on the acquisitions framework. However, the authority field is missing the tag editor to allow a look up. To recreate: 1. Set the RequireChoosingExistingAuthority system setting to required. 2. Make sure the acquisitions framework has the 100 Personal name field 2. In Acquisitions, find a vendor and add to a basket from a new empty record. See that the 100 Personal name field is missing the tag editor button. This is new behavior with 22.11. Previously the required look up was not present with this system setting enabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35035] New: Koha hide field values in reference fields based on $w
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35035 Bug ID: 35035 Summary: Koha hide field values in reference fields based on $w Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The Marc 21 Format for Authority Data includes the possibility to not display data in reference fields (4XX and 5XX) based on the third value of subfield w. "/3 - Reference display One-character alphabetic code that enables the generation or suppression of a cross reference from a 4XX or 5XX field. a - Reference not displayed b - Reference not displayed, field 664 used c - Reference not displayed, field 663 used d - Reference not displayed, field 665 used n - Not applicable" The possibility to hide data is important for example for authority records of trans people. The Metadata Best Practices for Trans and Gender Diverse Resources of the Trans Metadata Collective (2022) includes this recommendation in 3.2.4.2 Technical details (MARC & RDA). Catalogers should be able to record former names to assure findability of resources, but it should be also possible to hide them for the public in compliance with cataloging ethics guidelines. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 36564] New: Koha staff interface logs out on homepage refresh with 2FA enforced
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36564 Bug ID: 36564 Summary: Koha staff interface logs out on homepage refresh with 2FA enforced Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: chris.rowlands6(a)nhs.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Koha will log the staff user out if they refresh the homepage and confirm form resubmission after logging in with 2FA enforced. To reproduce: 1) ensure TwoFactorAuthentication is set to "Enforce" 2) log into staff interface including two factor code 3) refresh the homepage and confirm dialogue box for confirm form resubmission This logs you out. However if you navigate to another page and back a refresh functions normally; also if you don't have 2FA enabled a refresh functions normally. I've not submitted a bug before so please let me know if I've submitted this poorly/incorrectly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 34506] New: After deleting record from a search result the link 'Go back to the results' has disappeared
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34506 Bug ID: 34506 Summary: After deleting record from a search result the link 'Go back to the results' has disappeared Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com As was implemented in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5428 the link 'Go back to the results' seems to have disappeared to test: 1. make a search in the staff interface eg "perl" 2. chose a record 3. delete it (maybe including items) 4. in 21.05 there was a link 'Go back to the results', which is no present in 21.11.06 thx mark -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 34664] New: Notes added to fund not visible unless editing that fund
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34664 Bug ID: 34664 Summary: Notes added to fund not visible unless editing that fund Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Notes added to a fund in acquisitions are not currently visible unless the edit option is selected again for that particular fund. Budget_notes don't seem to appear anywhere in the codebase, except on aqbudgets.tt when editing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 39676] New: koha-reset-passwd fails
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39676 Bug ID: 39676 Summary: koha-reset-passwd fails Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.liddle(a)wycliff.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Hello! I discovered today that using the command koha-reset-passwd fails on Koha 22.11.25 with the following error: env: ‘/bin/admin/set_password.pl’: No such file or directory The command was run as indicated in --help: sudo koha-reset-passwd instancename userid Directly running the underlying script succeeds: sudo koha-shell -c '/usr/share/koha/bin/admin/set_password.pl --userid userid' instancename In this particular case, the userid takes the form of an email address, and I thought perhaps the '@' symbol may have been problematic, but the command also fails for a userid that follows the default pattern of firstname.surname. Am I doing something wrong, or is there a bug in the command? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 34483] New: [Omnibus] Standardize fund pull downs
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34483 Bug ID: 34483 Summary: [Omnibus] Standardize fund pull downs Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org We have a very nice fund pull down on the order receive page. * shows the budget * makes hierarchies visible * shows inactive on demand * always shows currently selected to prevent data loss * ordered alphabetically within budgets/hierarchies * select2 for easy selecting We should really have a nice fund list like this everywhere in Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 33775] New: Different/no results between Check Out and Search Patron when searching for names with spaces
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33775 Bug ID: 33775 Summary: Different/no results between Check Out and Search Patron when searching for names with spaces Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For the patron first name Jane surname Van Allen - in Check out, entering Van Allen will bring up the patron record, entering Van Allen in the Search Patron brings no results. The search needs to be the same in both. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3