Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#80208 - [mysql-workbench] 8.0.34-2 crashes due to missing WBAdmin module

Attached to Project: Arch Linux
Opened by Clarence Risher (sparr) - Thursday, 09 November 2023, 14:48 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 22 November 2023, 00:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Unfortunately I haven't been able to test on other configurations to narrow down the cause here. The program works when installed via snap or by unpacking the deb package manually.

Steps to reproduce:
1. Launch mysql-workbench
2. Click (+) and fill out connection details for server on localhost
3. Test connection, confirm it works
4. Click "OK"
5. Program crashes

```
% mysql-workbench
Found /usr/lib/libproj.so.25

** (mysql-workbench-bin:3335173): ERROR **: 09:36:06.423:
unhandled exception (type std::exception) in signal handler:
what: Module WbAdmin not found

/usr/bin/mysql-workbench: line 108: 3335173 Trace/breakpoint trap (core dumped) $MWB_BINARIES_DIR/mysql-workbench-bin "$@"
```
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 22 November 2023, 00:50 GMT
Reason for closing:  No response
Comment by loqs (loqs) - Thursday, 09 November 2023, 19:30 GMT
Please provide a backtrace that includes debugging information. Please read the following links [1][2][3]. It's usually as simple as (with gdb installed):

$ coredumpctl gdb (then answer y when it asks "Enable debuginfod for this session?")
(gdb) set logging enabled
(gdb) bt (or bt full)

Then post gdb.txt

[1]: https://blogs.gnome.org/mcatanzaro/2021/09/18/creating-quality-backtraces-for-crash-reports/
[2]: https://wiki.archlinux.org/title/Debugging/Getting_traces
[3]: https://wiki.archlinux.org/title/Core_dump#Analyzing_a_core_dump
Comment by Clarence Risher (sparr) - Thursday, 09 November 2023, 20:10 GMT
attaching log of `thread apply all bt full`
   gdb.txt (5.8 KiB)
Comment by Toolybird (Toolybird) - Thursday, 09 November 2023, 20:40 GMT
The "glib2" portions of your backtrace are missing debugging information from debuginfod (source code line numbers etc). Is your system up-to-date? Are you running a different "glib2" pkg?

Loading...