Bug 29869 - wxHexEditor: Crash at saving preferences
Summary: wxHexEditor: Crash at saving preferences
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: validated_update
Depends on: 29848
Blocks:
  Show dependency treegraph
 
Reported: 2022-01-11 19:00 CET by Morgan Leijström
Modified: 2022-01-27 19:52 CET (History)
5 users (show)

See Also:
Source RPM: wxhexeditor-0.24-9.2.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Morgan Leijström 2022-01-11 19:00:57 CET
Description of problem:

When launching, gives after welcome window a popup:

./src/common/socketiohandler.cpp(50): assert ""socket->m_fd != -1"" failed in Install_Callback(): shouldn't be called on invalid socket

Then memory dump when exiting.

Or, click continue repeatedly, and it goes past that dialogue.
Next launch, the dialogue do not show up.


ref: https://bugs.mageia.org/show_bug.cgi?id=29848#c30


Version-Release number of selected component (if applicable):
wxhexeditor-0.24-9.1.mga8.src.rpm
But also the package before that.
Comment 1 Morgan Leijström 2022-01-11 19:07:03 CET
Assigning to registered maintainer, Barry

Note:
This problem seem to occur in both the release and core_updates version in bug 29848, as dependency of wxgtk3.1 update.

You decide if you want to fix it now or after all packages in that bug are released.  - If updating before, please tell so in that bug.

Depends on: (none) => 29848
Assignee: bugsquad => zen25000

Comment 2 Jani Välimaa 2022-01-11 20:55:23 CET
Same is also happening in cauldron and looks like the issue is caused by an upstream version check when starting the app first time. I'll add a patch to disable it.

CC: (none) => jani.valimaa

Comment 3 Jani Välimaa 2022-01-12 16:35:32 CET
This should be fixed with wxhexeditor-0.24-9.2.mga8 in core/updates_testing. wxgtk 3.1.5 libraries from core/updates_testing are also needed to test the app.

Pop up error msgs can be reproduced by removing ~/.wxHexEditor config file before starting the app.

RPMS/SRPMS:
wxhexeditor-0.24-9.2.mga8

Source RPM: wxhexeditor-0.24-9.1.mga8.src.rpm => wxhexeditor-0.24-9.mga8.src.rpm
Assignee: zen25000 => qa-bugs

Jani Välimaa 2022-01-12 16:43:05 CET

Summary: wxHexEditor => wxHexEditor: Popup error msgs when starting the app first time

Comment 4 Morgan Leijström 2022-01-12 18:03:29 CET
No message at start, but:

Menu: Options -> Preferences, then press [Save] button:

ASSERT INFO:
./src/gtk/choice.cpp(284): assert ""Assert failure"" failed in GetString(): invalid index

BACKTRACE:
[1] wxChoice::GetString(unsigned int) const
[2] std::ctype<char>::do_widen(char) const
[3] std::ctype<char>::do_widen(char) const
[4] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[5] wxEvtHandler::SearchDynamicEventTable(wxEvent&)
[6] wxEvtHandler::TryHereOnly(wxEvent&)
[7] wxEvtHandler::ProcessEventLocally(wxEvent&)
[8] wxEvtHandler::ProcessEvent(wxEvent&)
[9] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[10] g_signal_emit_valist
[11] g_signal_emit
[12] g_closure_invoke
[13] g_signal_emit_valist
[14] g_signal_emit
[15] g_signal_emit_valist
[16] g_signal_emit
[17] g_cclosure_marshal_VOID__BOXEDv
[18] g_signal_emit_valist
[19] g_signal_emit
[20] gtk_event_controller_handle_event
[21] g_closure_invoke
[22] g_signal_emit_valist
[23] g_signal_emit
[24] gtk_main_do_event
[25] g_main_context_dispatch
[26] g_main_loop_run
[27] gtk_main
[28] wxGUIEventLoop::DoRun()
[29] wxEventLoopBase::Run()
[30] wxDialog::ShowModal()
[31] std::ctype<char>::do_widen(char) const
[32] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[33] wxEvtHandler::SearchDynamicEventTable(wxEvent&)
[34] wxEvtHandler::TryHereOnly(wxEvent&)
[35] wxEvtHandler::DoTryChain(wxEvent&)
[36] wxEvtHandler::ProcessEvent(wxEvent&)
[37] wxWindowBase::TryAfter(wxEvent&)
[38] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[39] wxMenuBase::DoProcessEvent(wxMenuBase*, wxEvent&, wxWindow*)
[40] wxMenuBase::SendEvent(int, int)
[41] g_closure_invoke
[42] g_signal_emit_valist
[43] g_signal_emit
[44] gtk_widget_activate
[45] gtk_menu_shell_activate_item
[46] g_signal_emit_valist
[47] g_signal_emit
[48] gtk_main_do_event
[49] g_main_context_dispatch
[50] g_main_loop_run
[51] gtk_main
[52] wxGUIEventLoop::DoRun()
[53] wxEventLoopBase::Run()
[54] wxAppConsoleBase::MainLoop()
[55] wxEntry(int&, wchar_t**)
[56] __libc_start_main

..and memory dumps when closing the error dialogue.


At start, it in terminal from where it is started, outputs:

dbind-WARNING **: 17:43:13.895: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

The former version did that too, I don't know if it matters.


Peculiar: Opening a file, i get a message in terminal i needed to translate:
https://translate.google.com/?sl=auto&tl=en&text=Rahman%20ve%20Rahim%20olan%20Allah%27%C4%B1n%20ad%C4%B1yla&op=translate
I guess the author is wishing the user luck :)

Source RPM: wxhexeditor-0.24-9.mga8.src.rpm => wxhexeditor-0.24-9.2.mga8.src.rpm
Assignee: qa-bugs => zen25000

Morgan Leijström 2022-01-12 18:05:28 CET

Summary: wxHexEditor: Popup error msgs when starting the app first time => wxHexEditor: Crash at saving preferences

Comment 5 Morgan Leijström 2022-01-12 18:16:21 CET
And when closing hexedit with that file opened:

18:12:20: Debug: In file ./src/unix/threadpsx.cpp at line 278: 'pthread_mutex_destroy()' failed with error 0x00000010 (Enhet eller resurs upptagen).

"Enhet eller resurs upptagen" = "Device or resource busy"
Comment 6 Jani Välimaa 2022-01-12 18:27:31 CET
Issue noted in comment 4 is happening if language selection in preferences is empty.
Comment 7 Morgan Leijström 2022-01-12 19:15:31 CET
Ah yes, and the language selection is empty by default.

Could not find a bug on this issue in upstream bug tracker, and have no energy to open one.

This is a beta version anyway, and no advances for a couple years.
(Paypal blocking donations of course do not help...)

Assignee: zen25000 => qa-bugs
Whiteboard: (none) => MGA8-64-OK

Comment 8 Thomas Andrews 2022-01-12 19:20:07 CET
Validating.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

Comment 9 Jani Välimaa 2022-01-12 20:01:37 CET
(In reply to Morgan Leijström from comment #7)
> Ah yes, and the language selection is empty by default.
> 
> Could not find a bug on this issue in upstream bug tracker, and have no
> energy to open one.
> 
> This is a beta version anyway, and no advances for a couple years.
> (Paypal blocking donations of course do not help...)

It's not empty if system language happens to be one of the languages wxhexeditor provides translations for.

If one starts wxHexeditor first time e.g. with 'LC_ALL=en_GB.UTF-8 wxHexEditor' language selection is populated, but 'LC_ALL=en_US.UTF-8 wxHexEditor' is not working. The first one sets 'Language=English' in ~/.wxHexEditor and the second one 'Language=English (U.S.)' which isn't working as supposed.

Like said, it's beta version.
Comment 10 Jani Välimaa 2022-01-12 21:19:45 CET
wxhexeditor-0.24-9.3.mga8 should fix the empty language selection issue. Please test.

RPMS/SRPMS:
wxhexeditor-0.24-9.3.mga8

Whiteboard: MGA8-64-OK => (none)
Keywords: validated_update => (none)

Comment 11 Morgan Leijström 2022-01-12 23:27:38 CET
So you added the icing too ! :)

$ rm ~/.wxHexEditor
And then ran it again:
Welcome message: OK.
Menu: Options -> Preferences, I see English is filled in.
Press [Save] button: No problem.
Exiting: No problem

Keywords: (none) => validated_update
Whiteboard: (none) => MGA8-64-OK

Dave Hodgins 2022-01-14 22:57:38 CET

Keywords: (none) => advisory
CC: (none) => davidwhodgins

Comment 12 Lewis Smith 2022-01-27 19:43:47 CET
I think this bug should be closed 'validated', but *without* an advisory, closed 'fixed'; and like others in the same position, it should go out with the host bug 29848 (updated to include the new version-id).

@Dave: can you withdraw the advisory? The host bug advisory will (?) include mention of this.

Status: NEW => RESOLVED
Keywords: advisory => (none)
CC: (none) => lewyssmith
Resolution: (none) => FIXED

Comment 13 Dave Hodgins 2022-01-27 19:52:28 CET
Advisory deleted from svn

Note You need to log in before you can comment on or make changes to this bug.