You are not logged in.
I installed Code::Blocks with pacman on plasma but I am unable to run it.
The loading screen freeze with the message (Not responding) and I am forced to kill the process.
in the console i get the following message :
Starting Code::Blocks Release 25.03 rev 13644 Jun 7 2025, 18:00:35 - wxWidgets 3.2.8 - gcc 15.1.1 (Linux, unicode) - 64 bit
Manager initialized
Initialize EditColourSet .....
Initialize EditColourSet: done.
Loading menubar...
CB_Koders: loaded
SmartIndentPascal: loaded
ClassWizard: loaded
MouseSap: loaded
ProjectOptionsManipulator: loaded
rndgen: loaded
CodeSnippets: loaded
Exporter: loaded
but it get stuck after that.
Can someone help me to know what's going on ??
Last edited by fatra5 (2025-10-27 21:27:26)
Offline
I have the same problem, CodeBlocks shows a splashscreen but it remains stuck at startup,
an interesting thread here :
https://forums.codeblocks.org/index.php?topic=26131.0
A possible workaround is to delete some files related to wxSmith in /usr/share/codeblocks/, or recompile CodeBlocks without the support of the wxSmith plugin :
Not sure if this helps but I got around the start up freeze by turning off (removing) all the wxsmith.zips from /usr/share/codeblocks/
...
cb works again when the zip-files of the three wxsmith plugins are deleted. Alternatively, disabling them when calling configure (not cmake) works as well as expected.
Obviously, wxSmith can not be used in that case.
Last edited by Potomac (2025-10-25 19:49:23)
Offline
Have you tried with https://aur.archlinux.org/packages/gdk-pixbuf2-noglycin ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Yyeah same. It's not responding.
Starting Code::Blocks Release 25.03 rev 13644 Jun 7 2025, 18:00:35 - wxWidgets 3.2.8 - gcc 15.1.1 (Linux, unicode) - 64 bit
Manager initialized
Initialize EditColourSet .....
Initialize EditColourSet: done.
Loading menubar...
ToolsPlus: loaded
RegExTestbed: loaded
CodeStat: loaded
CodeSnippets: loaded
NassiShneidermanPlugin: loaded
HexEditor: loaded
HelpPlugin: loaded
AStylePlugin: loaded
cbDragScroll: loaded
ToDoList: loaded
SpellChecker: loaded
ProjectsImporter: loaded
CppCheck: loaded
EnvVars: loaded
Offline
I have the same problem, CodeBlocks shows a splashscreen but it remains stuck at startup,
an interesting thread here :
https://forums.codeblocks.org/index.php?topic=26131.0A possible workaround is to delete some files related to wxSmith in /usr/share/codeblocks/, or recompile CodeBlocks without the support of the wxSmith plugin :
Not sure if this helps but I got around the start up freeze by turning off (removing) all the wxsmith.zips from /usr/share/codeblocks/
...
cb works again when the zip-files of the three wxsmith plugins are deleted. Alternatively, disabling them when calling configure (not cmake) works as well as expected.
Obviously, wxSmith can not be used in that case.
THis works. THANKS
Offline
I have the same problem, CodeBlocks shows a splashscreen but it remains stuck at startup,
an interesting thread here :
https://forums.codeblocks.org/index.php?topic=26131.0A possible workaround is to delete some files related to wxSmith in /usr/share/codeblocks/, or recompile CodeBlocks without the support of the wxSmith plugin :
This indeed works just fine THANKS.
(even though I'm not sure to understand why)
If the PlugIn don't work, why is it in the package update of Pacman...
Or maybe it works just fine for other distros...
Offline
If the PlugIn don't work, why is it in the package update of Pacman...
Maybe because no one filed a bug report to inform the arch devs that maintain it ?
Last edited by Lone_Wolf (2025-10-27 10:47:40)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The current bug tracker for arch linux site is not easy to use, I didn't manage to create an account, as arch linux administrators decided to close new souscriptions (because of too much spam), it can explain why the bug was not filed,
Due to an influx of spam, we have had to temporarily disable account registrations. Please write an email to accountsupport@archlinux.org, with your desired username, if you want to get access. Sorry for the inconvenience.
previous bug tracker didn't have this problem.
Last edited by Potomac (2025-10-27 18:13:09)
Offline
Please write an email to accountsupport@archlinux.org, with your desired username, if you want to get access.
New subscriptions haven't been closed even once since archlinux bugtracker migrated to gitlab.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks for that, been having the same issue, and didn't have time to raise a post about it, come to do it and found this one.
Your workaround does seem to work, I run my own PKGBUILD for Codeblocks and changed the configure line to this:
./configure --prefix='/usr' --with-contrib-plugins='all, -wxsmith, -wxsmithcontrib, -wxsmithaui'"-wxsmith" alone is not enough for anyone else building it.
Desktop: Ryzen 7 1800X | AMD 7800XT | KDE Plasma
Offline
Have you tried the -noglycin package for gdkpixbuf, does that hang for you as well just like the OP?
Last edited by progandy (2025-10-28 18:46:57)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
Have you tried the -noglycin package for gdkpixbuf, does that hang for you as well just like the OP?
Just tested now:
When running gdk-pixbuf2-noglycin I am able to run both the trunk version (latest revision) and extra/codeblocks.
When running extra/gdk-pixbuf2 I am not able to run codeblocks unless I compile it without the wxsmith plugins.
Desktop: Ryzen 7 1800X | AMD 7800XT | KDE Plasma
Offline
Please write an email to accountsupport@archlinux.org, with your desired username, if you want to get access.
New subscriptions haven't been closed even once since archlinux bugtracker migrated to gitlab.
I sent an email for a new subscription 2 days ago, and got an answer from a bot saying something like "Thank you for your support request! We are tracking your request and will respond as soon as we can",
I hope my request will be approved, I want to contribute for reporting bugs to Arch Linux.
Offline