Bug 415092 - Segmentation fault if the colors scheme is used
Summary: Segmentation fault if the colors scheme is used
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kalzium
Classification: Applications
Component: general (show other bugs)
Version: 19.08.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kalzium Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-12 14:36 UTC by hugleo
Modified: 2019-12-12 16:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
image of the colors scheme (251.19 KB, image/png)
2019-12-12 14:36 UTC, hugleo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hugleo 2019-12-12 14:36:57 UTC
Created attachment 124444 [details]
image of the colors scheme

SUMMARY


STEPS TO REPRODUCE
1. Menu option View/Scheme/Colors
2. 
3. 

OBSERVED RESULT

Program crash:

Reading symbols from /usr/bin/kalzium...
(No debugging symbols found in /usr/bin/kalzium)
(gdb) run
Starting program: /usr/bin/kalzium 
/usr/lib/../share/gcc-9.2.0/python/libstdcxx/v6/xmethods.py:731: SyntaxWarning: list indices must be integers or slices, not str; perhaps you missed a comma?
  refcounts = ['_M_refcount']['_M_pi']
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffeedc7700 (LWP 34833)]
[New Thread 0x7fffed3ff700 (LWP 34834)]

Thread 1 "kalzium" received signal SIGSEGV, Segmentation fault.


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION

Now Kalzium always crash on start since View/Scheme/Colors became the default option.

/usr/bin/kalzium --version
kalzium 19.08.3
Comment 1 hugleo 2019-12-12 15:27:34 UTC
I think the problem can be the kalzium-openbabel3.patch used the arch package since looks like Kalzium doesn't support openbabel3.
Comment 2 Antonio Rojas 2019-12-12 16:11:29 UTC
(In reply to hugleo from comment #1)
> I think the problem can be the kalzium-openbabel3.patch used the arch
> package since looks like Kalzium doesn't support openbabel3.

Quite likely. I'll take a look, please report downstream so I don't forget.