# Signum 11 when trying to import source in \`Source paths...\` dialog

**URL:** <https://community.hex-rays.com/t/signum-11-when-trying-to-import-source-in-source-paths-dialog/607>\
**Category:** Bugs\
**Created:** [November 24, 2025, 6:45pm UTC](https://community.hex-rays.com/t/signum-11-when-trying-to-import-source-in-source-paths-dialog/607 "2025-11-24T18:45:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yuiozank](https://sea2.discourse-cdn.com/flex002/user_avatar/community.hex-rays.com/yuiozank/32/293_2.png) [@yuiozank](https://community.hex-rays.com/u/yuiozank)\
**Post date:** [November 24, 2025, 6:45pm UTC](https://community.hex-rays.com/t/signum-11-when-trying-to-import-source-in-source-paths-dialog/607/1 "2025-11-24T18:45:44Z")

</div>

**Step to reproduce:**

1. Open `Source paths...` (`SetupSrcPath` action) dialog
2. Right click on one of the two tables (both produce the same result)
3. Select `Insert...`

No file dialog will open, just signum error.

 ![fx](https://us1.discourse-cdn.com/flex002/uploads/rays_hex/original/1X/70c50c4648a241fa53eddd42f2f1811ef0403520.jpeg)

P.S  
I’m on Intel on macOS 15.7.2.

---

<div class="post-metadata">

**Author:** ![teresa\_hexrays](https://sea2.discourse-cdn.com/flex002/user_avatar/community.hex-rays.com/teresa_hexrays/32/11_2.png) [@teresa\_hexrays](https://community.hex-rays.com/u/teresa_hexrays)\
**Post date:** [November 26, 2025, 4:55pm UTC](https://community.hex-rays.com/t/signum-11-when-trying-to-import-source-in-source-paths-dialog/607/2 "2025-11-26T16:55:33Z")

</div>

Hi, thanks for reporting! We are on it and checking the issue on our side.

---

<div class="post-metadata">

**Author:** ![teresa\_hexrays](https://sea2.discourse-cdn.com/flex002/user_avatar/community.hex-rays.com/teresa_hexrays/32/11_2.png) [@teresa\_hexrays](https://community.hex-rays.com/u/teresa_hexrays)\
**Post date:** [November 28, 2025, 11:28am UTC](https://community.hex-rays.com/t/signum-11-when-trying-to-import-source-in-source-paths-dialog/607/3 "2025-11-28T11:28:02Z")

</div>

A brief update and some good news as well - this issue is expected to be fixed in the next IDA release.
