[tellico] [Bug 379607] tellico crashes with segfault on start

2017-09-22 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #21 from ghichtin --- (In reply to Robby Stephenson from comment #20) > (In reply to ghichtin from comment #19) > > (In reply to Robby Stephenson from comment #18) > > > (In reply to ghichtin from comment #17) > > &

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-09-22 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #19 from ghichtin --- (In reply to Robby Stephenson from comment #18) > (In reply to ghichtin from comment #17) > > But, again, I've lost bol.it support > > Tellico 3.02 fixed the ibs.it search, but I don't think

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-08-27 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #17 from ghichtin --- Installed ver. 3.0.2 from artful repo seems to work, despite Ubuntu version being different (I'm on 17.04) IDK if I should put [SOLVED] because of the fresh install. (Sorry but I couldn't follow the

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-06-06 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #11 from ghichtin --- (In reply to Christoph Feck from comment #10) > Does the backtrace really stop at #2? If there are additional lines, even > incomplete ones, please show all of them. You might need to press Return to > see m

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-05-30 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #9 from ghichtin --- After new compilation and installation this is the result with gdb: :~/tellico-3.0.2/build$ gdb tellico GNU gdb (Ubuntu 7.12.50.20170314-0ubuntu1) 7.12.50.20170314-git [...] Reading symbols from tellico...done. (gdb

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-05-30 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #8 from ghichtin --- (In reply to Robby Stephenson from comment #7) > Hmmm. There's still no pointer into a crash inside Tellico. This is a bit > weird. If we back up a bit, can you post the log file or output that you get >

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-05-11 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #6 from ghichtin --- (In reply to Christoph Feck from comment #4) > Does 'bt' really only display a single line? We need the full backtrace. > Please also install qt5 debug symbols, if possible. So I've t

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-05-11 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #5 from ghichtin --- (In reply to Christoph Feck from comment #4) > Does 'bt' really only display a single line? We need the full backtrace. > Please also install qt5 debug symbols, if possible. Yes it does. ASAP I'

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-05-08 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #3 from ghichtin --- (In reply to Robby Stephenson from comment #1) > When you run "gdb tellico" and tellico crashes, type "bt" without the > quotes, to get a backtrace. If it has debug symbols (did you compile wit

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-05-08 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 --- Comment #2 from ghichtin --- Created attachment 105385 --> https://bugs.kde.org/attachment.cgi?id=105385&action=edit valgrind output running tellico -- You are receiving this mail because: You are watching all bug changes.

[tellico] [Bug 379607] New: tellico crashes with segfault on start

2017-05-07 Thread ghichtin
https://bugs.kde.org/show_bug.cgi?id=379607 Bug ID: 379607 Summary: tellico crashes with segfault on start Product: tellico Version: 3.0.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: