You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, crreating a new address results in a crash.
This is from the flatpak release.
Version: 2.8.0
OS: Linux 6.9.3-76060903-generic
0# signal_handler(int) in /app/feather
1# 0x000078FF75047560 in /gnu/store/zvlp3n8iwa1svxmwv4q22pv1pb1c9pjq-glibc-2.39/lib/libc.so.6
2# 0x000078FF750913FC in /gnu/store/zvlp3n8iwa1svxmwv4q22pv1pb1c9pjq-glibc-2.39/lib/libc.so.6
3# gsignal in /gnu/store/zvlp3n8iwa1svxmwv4q22pv1pb1c9pjq-glibc-2.39/lib/libc.so.6
4# signal_handler(int) in /app/feather
5# 0x000078FF75047560 in /gnu/store/zvlp3n8iwa1svxmwv4q22pv1pb1c9pjq-glibc-2.39/lib/libc.so.6
6# 0x00005A0A5E9832D7 in /app/feather
7# 0x00005A0A5EC584E0 in /app/feather
8# 0x00005A0A5EC5BE8F in /app/feather
9# 0x00005A0A5EC5D411 in /app/feather
10# 0x00005A0A5EC5D6F8 in /app/feather
11# 0x00005A0A5EA2E810 in /app/feather
12# 0x00005A0A5EA8E166 in /app/feather
13# 0x00005A0A5E783F5E in /app/feather
14# 0x00005A0A5E9D42D5 in /app/feather
15# 0x00005A0A5E784218 in /app/feather
16# 0x00005A0A5EA26C09 in /app/feather
17# 0x00005A0A5EA27108 in /app/feather
18# 0x00005A0A5EA288C6 in /app/feather
19# 0x00005A0A5EA28729 in /app/feather
20# 0x00005A0A5EA27216 in /app/feather
21# 0x00005A0A5EA288C6 in /app/feather
22# 0x00005A0A5EA28729 in /app/feather
23# 0x00005A0A5EA28729 in /app/feather
24# 0x00005A0A5EA27216 in /app/feather
25# 0x00005A0A5EA288C6 in /app/feather
26# 0x00005A0A5EA27216 in /app/feather
27# 0x00005A0A5EA288C6 in /app/feather
28# 0x00005A0A5EA27216 in /app/feather
29# 0x00005A0A5EA288C6 in /app/feather
30# 0x00005A0A5EA28729 in /app/feather
31# 0x00005A0A5EA27216 in /app/feather
32# 0x00005A0A5EA288C6 in /app/feather
33# 0x00005A0A5EA27216 in /app/feather
34# 0x00005A0A5EA288C6 in /app/feather
35# 0x00005A0A5EA27216 in /app/feather
36# 0x00005A0A5EA288C6 in /app/feather
37# 0x00005A0A5EA27216 in /app/feather
38# 0x00005A0A5EA288C6 in /app/feather
39# 0x00005A0A5EA27216 in /app/feather
40# 0x00005A0A5EA38434 in /app/feather
41# 0x00005A0A5EA2EDAC in /app/feather
42# 0x00005A0A5E9D42E5 in /app/feather
43# 0x00005A0A5E784218 in /app/feather
44# 0x00005A0A5E78823A in /app/feather
45# 0x00005A0A5E8B883E in /app/feather
46# 0x00005A0A5FEAF9E2 in /app/feather
47# 0x00005A0A5E78DD1B in /app/feather
48# 0x00005A0A5E78C0CF in /app/feather
49# main in /app/feather
50# 0x000078FF75032BF7 in /gnu/store/zvlp3n8iwa1svxmwv4q22pv1pb1c9pjq-glibc-2.39/lib/libc.so.6
51# __libc_start_main in /gnu/store/zvlp3n8iwa1svxmwv4q22pv1pb1c9pjq-glibc-2.39/lib/libc.so.6
52# _start in /app/feather
More info: It seems to correct after the first crash. I tried with two different wallets after updating to 2.8.0 and they both crashed on first open (while trying to generate new address), second try was fine. The generated adresses appear to have been created prior to the crash because they are present on the second load.
The lack of symbols in the stack trace lead me to believe the crash occurs somewhere in Qt code. I will update Qt in the upcoming point release, so perhaps this issue will resolve itself.
Please let me know if you encounter the crash in 2.8.1 or later.
This crash is still occurring on Linux when attempting to generate a sub-address after restoring a wallet with one or more inputs to a non-default sub-address, i.e., address #11 or higher. Something to note that isn't provided by OP is the warning printed just before the error output:
[2025-07-29 03:33:31 W] (:0) QSortFilterProxyModel: invalid inserted rows reported by source model
Feather is failing to correctly populate the address list on restore which leads to a crash due to invalid address order in the UI.
Conditions
The wallet was restored, e.g., via seed
Wallet has more than 11 addresses, including the primary #0
Inputs have been made to address #11 or higher before restoring
The Receive tab contains only addresses #0 to #10
Used addresses above #10 do not appear
Steps to Reproduce (Debian)
Launch Feather (AppImage or Binary) and create new wallet bug_test
Generate new sub-address #11: Receive -> Create new address
Activity
tobtoht commentedon Apr 3, 2025
Are you using a hardware device like Ledger or Trezor?
monero-love commentedon Apr 3, 2025
Nope.
monero-love commentedon Apr 3, 2025
More info: It seems to correct after the first crash. I tried with two different wallets after updating to 2.8.0 and they both crashed on first open (while trying to generate new address), second try was fine. The generated adresses appear to have been created prior to the crash because they are present on the second load.
Edit:
Same issue on a second machine.
tobtoht commentedon Apr 11, 2025
I have not been able to reproduce this issue.
tobtoht commentedon Apr 13, 2025
The lack of symbols in the stack trace lead me to believe the crash occurs somewhere in Qt code. I will update Qt in the upcoming point release, so perhaps this issue will resolve itself.
Please let me know if you encounter the crash in 2.8.1 or later.
WorldShredder commentedon Jul 29, 2025
This crash is still occurring on Linux when attempting to generate a sub-address after restoring a wallet with one or more inputs to a non-default sub-address, i.e., address
#11or higher. Something to note that isn't provided by OP is the warning printed just before the error output:Feather is failing to correctly populate the address list on restore which leads to a crash due to invalid address order in the UI.
Conditions
#0#11or higher before restoringReceivetab contains only addresses#0to#10#10do not appearSteps to Reproduce (Debian)
bug_test#11:Receive->Create new address#11rm ~/Monero/wallets/bug_test*bug_testfrom seedWorkarounds