Description of problem: While launching CodeBlocks from MageiaWelcome an assert error appeared. ./src/gtk/choice.cpp(284): ""Assert failure"" failed in GetString(): Invalid index After clicking the Backtrace button in th error dialog, I found the following: ASSERT INFO: ./src/gtk/choice.cpp(284): assert ""Assert failure"" failed in GetString(): invalid index BACKTRACE: [1] wxChoice::GetString(unsigned int) const [2] FileExplorer::WriteConfig() [3] FileExplorer::~FileExplorer() [4] FileExplorer::~FileExplorer() [5] FileManagerPlugin::OnRelease(bool) [6] cbPlugin::Release(bool) [7] PluginManager::DetachPlugin(cbPlugin*) [8] PluginManager::UnloadPlugin(cbPlugin*) [9] PluginManager::UnloadAllPlugins() [10] PluginManager::~PluginManager() [11] PluginManager::~PluginManager() [12] Manager::Shutdown() [13] wxStringTokenizer::~wxStringTokenizer() [14] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [15] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [16] wxEvtHandler::TryHereOnly(wxEvent&) [17] wxEvtHandler::DoTryChain(wxEvent&) [18] wxEvtHandler::ProcessEvent(wxEvent&) [19] wxEvtHandler::SafelyProcessEvent(wxEvent&) [20] wxWindowBase::Close(bool) [21] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) [22] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) [23] wxEvtHandler::TryHereOnly(wxEvent&) [24] wxEvtHandler::DoTryChain(wxEvent&) [25] wxEvtHandler::ProcessEvent(wxEvent&) [26] wxWindowBase::TryAfter(wxEvent&) [27] wxEvtHandler::SafelyProcessEvent(wxEvent&) [28] wxMenuBase::DoProcessEvent(wxMenuBase*, wxEvent&, wxWindow*) [29] wxMenuBase::SendEvent(int, int) [30] g_closure_invoke [31] g_signal_emit_valist [32] g_signal_emit [33] gtk_widget_activate [34] gtk_menu_shell_activate_item [35] g_signal_emit_valist [36] g_signal_emit [37] gtk_main_do_event [38] g_main_context_dispatch [39] g_main_loop_run [40] gtk_main [41] wxGUIEventLoop::DoRun() [42] wxEventLoopBase::Run() [43] wxAppConsoleBase::MainLoop() [44] wxEntry(int&, wchar_t**) [45] __libc_start_main After the error message was dismissed, CodeBlocks was open, so I proceeded to create a new console application. The data entry ended when a message that the selected directory could not be created. So I stopped. Version-Release number of selected component (if applicable): Whichever versions of MageiaWelcome and CodeBlocks shipped with the new Mageia 9 How reproducible: Steps to Reproduce: 1. start konsole 2. enter mageiawelcome, press enter 3. wait for error dialog to appear 4. click on backtrace, then copy to clipboard 5. paste into email and Bugzilla
Thank you for the report. Which is enigmatic. > While launching CodeBlocks from MageiaWelcome Not sure what you meant by this - ah, I see now: MageiaWelcome-Programs-Programming-CodeBlocks ! I cannot find CodeBlocks anywhere in our M9 repositories! But very many icons for it. Is it a carry-forward from upgrading Mageia 8 to 9? Or I have a mirror problem. Trying the Welcome 'install' button for it soon says there is no such package. This probably needs fixing (to remove). Your report implies that you not only have it installed, but tried to run it from Welcome. If you do indeed have it, - How did you install it? - Please give the rpm ID (from rpm -q codeblocks). - Does it work from the application menu? - Does it work from the command line? - Does it only fail as you describe if launched from Welcome?
CC: (none) => lewyssmith
I also cannot find it in mga9. madb say it is in mga8 and cauldron *) as .mga9 https://madb.mageia.org/package/show/name/codeblocks/release/cauldron/arch/x86_64 And no recent bug about it. So it should be available. CC registered packager. --- ...and i have already asked to add Mageia 9 release distribution to madb https://ml.mageia.org/l/arc/qa-discuss/2023-09/msg00069.html Maybe i should create a bug instead, but set to what?
CC: (none) => cvargas, fri
So in what repo to put this codeblocks (and any deps) rpm? We may not alter release repo. backport is not right - one reason being it will not be found easily and not with mageiawelcome unless user enables backport. So best put it in in updates. --- @Kenneth: Codeblocks is also not in cauldron repos, and the Mageia 8 version (latest in updates) need deps not available in suitable version on mga9. You could experiment with that, or install codeblocks using https://wiki.mageia.org/en/Flatpak
It's been removed from svn for m9, but is in present in cauldron. https://svnweb.mageia.org/packages/cauldron/codeblocks/ The last info about it in the dev ml is Le 2023-06-25 16:13, Jani Välimaa a écrit : Please move codeblocks-20.03^svn12803-4.mga9 to core/release. It's just a rebuild with parallel builds limited to 8 to fix an autobuild failure. done Did that build fail too?
CC: (none) => davidwhodginsAssignee: bugsquad => cvargas
Asking Jani
CC: (none) => jani.valimaa
Indeed I now see it in Cauldron: new version: 20.03, Mar 2020 update to latest upstream svn snapshot, Apr 2022 plus regular activity between times. So it clearly exists. I think we need answers to the questions in comment 1, notwithstanding.
Hmmmm! I don't know why and how it is possible but it seems that by mistake codeblocks was retired from repo! Once our Build System fixed I'll restore back codeblocks for mga9 and cauldron too.
CC: (none) => geiger.david68210
Summary: While launching CodeBlocks from MageiaWelcome an assert error appeared. => CodeBlocks was removed from Mageia 9 by accident, will be backKeywords: (none) => IN_ERRATA9Priority: Normal => High
Comments 2 & 4 (CC then Assign) re Cesar Vargas: I suspect that he is no longer active with us. Not for the first time, because DavidG is on board and doing something about this (previous comment; and as usual many thanks), he wins the bug assignment!
Assignee: cvargas => geiger.david68210
> Trying the Welcome 'install' button for it soon says there is no such package. > This probably needs fixing (to remove). From inside MageiaWelcome my machine shows a Launch button, not an Install button. > Your report implies that you not only have it installed, but tried to run it > from Welcome. If you do indeed have it, > - How did you install it? Some months ago with Mageia 8 operating I installed CodeBlocks without incident through the Add/Remove Programs application. I played with it for a little while, but fell back into old habits with command line vim and g++. So, it sat on the platter until the Mageia 9 distribution upgrade completed, and I began to explore what had been delivered. > - Please give the rpm ID (from rpm -q codeblocks). codeblocks-20.03-4.1.mga8 Also, in the search results of the software management application, entering codeblock returns a second file, lib64codeblocks0, with the same release, version, and architecture, with a note that it is a shared library for codeblocks. > - Does it work from the application menu? Yes, it did just a moment ago, but now I can't see the development line in the menu. This is an on-going challenge with my machine's menu system, and it's probably a different conversation than this one. Very frustrating, though. > - Does it work from the command line? Starting Code::Blocks Release 20.03 rev 11997 Jan 5 2022, 16:51:54 - wx3.1.5 - gcc 10.3.0 (Linux, unicode) - 64 bit This is the response it gave me just now, but I had just closed CodeBlocks with an X-box click before moving to Konsole. > - Does it only fail as you describe if launched from Welcome? No, it consistently fails with the error message I mentioned in the bug report, and will give list of errors from the traceback button. At this moment, though, it is telling me that it is configured to run only one instance of itself, and that I need to adjust the environment section if I want different behavior.
Thank you for answering all those questions. Because Welcome shows a 'launch' button for CodeBlocks, Welcome must recognise that CodeBlocks is installed. > it consistently fails with the error message I mentioned in the bug report Your intitial report says it fails on launching from Welcome; the previous comment indicates that it works to some extent from the application menu; what happens from the command line is unclear. Never mind, we are dealing with an unsure package. It is probably referring to things that have changed since M8. I think we should wait until DavidG has got it back into Mageia 9.
Source RPM: (none) => codeblocks-20.03-4.1.mga8.src.rpm
Assigning to QA, Packages in 9/Core/Updates_testing: ====================== codeblocks-20.03^svn12803-4.mga9 libcodeblocks-devel-20.03^svn12803-4.mga9 lib64codeblocks-devel-20.03^svn12803-4.mga9 libcodeblocks0-20.03^svn12803-4.mga9 lib64codeblocks0-20.03^svn12803-4.mga9 From SRPMS: codeblocks-20.03^svn12803-4.mga9.src.rpm
Assignee: geiger.david68210 => qa-bugs
Great job David. @QA As well as testing that it can be installed to work, it will be worth cross-checking the original complaint about it not launching from MageiaWelcome. And once validated, that once it gets into Core ? Updates, it can be seen & installed like any other package.
CC: lewyssmith => (none)
A user in the german forum reported that codeblocks needs cross-avr-gcc to compile a program. It throws an error and asks for the missing avr-gcc. TV obsoleted cross-avr-gcc and broke codeblocks in this way...
(In reply to sturmvogel from comment #13) > A user in the german forum reported that codeblocks needs cross-avr-gcc to > compile a program. It throws an error and asks for the missing avr-gcc. > > TV obsoleted cross-avr-gcc and broke codeblocks in this way... So re-adding codeblocks is useless? CC'ing tv
CC: (none) => marja11, thierry.vignaud
(In reply to sturmvogel from comment #13) > A user in the german forum reported that codeblocks needs cross-avr-gcc to > compile a program. It throws an error and asks for the missing avr-gcc. > > TV obsoleted cross-avr-gcc and broke codeblocks in this way... In fedora, I see avr-gcc & avr-gcc-c++, maybe we need to import that and replace the cross-avr-gcc requires/recommends to avr-gcc
Keywords: (none) => feedback
Summary: CodeBlocks was removed from Mageia 9 by accident, will be back => CodeBlocks was removed from Mageia 9, needs a solution for lacking avr-gcc to come back
(In reply to Marja Van Waes from comment #14) > (In reply to sturmvogel from comment #13) > > A user in the german forum reported that codeblocks needs cross-avr-gcc to > > compile a program. It throws an error and asks for the missing avr-gcc. > > > > TV obsoleted cross-avr-gcc and broke codeblocks in this way... > > So re-adding codeblocks is useless? I guess it is only broken for compiling to AVR microcontrollers? But of course it is a popular usage we like to support.
cross-avr-gcc-12.3.0-1.mga10 now again available on Cauldron. Can someone confirm if codeblocks works properly with cross-avr-gcc-12.3.0-1.mga10? So I can restore also cross-avr-gcc for mga9.
Source RPM: codeblocks-20.03-4.1.mga8.src.rpm => cross-avr-gcc, codeblocks-20.03-4.1.mga8.src.rpm
CC: (none) => mageia
Any news?
Status comment: (none) => mga9 is waiting for an update if mga10 version is OK