Bug 485855 - Crash after entering value in cell of newly created column
Summary: Crash after entering value in cell of newly created column
Status: RESOLVED WORKSFORME
Alias: None
Product: calligrasheets
Classification: Applications
Component: general (show other bugs)
Version: 3.2.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Calligra Sheets (KSpread) Bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-04-20 14:19 UTC by Joe
Modified: 2024-11-04 03:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe 2024-04-20 14:19:38 UTC
Application: calligrasheets (3.2.1)

Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.0-28-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.10
DrKonqi: 5.27.8 [KCrashBackend]

-- Information about the crash:
Created new column
Enter vaue in to cell of new coulmn
Press enter
=> crash

Happened several times, each time.

The crash can be reproduced every time.

-- Backtrace:
Application: Calligra Sheets (calligrasheets), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f9a1f1510bc in Calligra::Sheets::StyleStorage::invalidateCache() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17
#5  0x00007f9a1f11f72a in Calligra::Sheets::Map::handleDamages(QList<Calligra::Sheets::Damage*> const&) () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17
#6  0x00007f9a2c90602d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f9a1f062136 in Calligra::Sheets::Map::damagesFlushed(QList<Calligra::Sheets::Damage*> const&) () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17
#8  0x00007f9a1f1199ac in Calligra::Sheets::Map::flushDamages() () from /lib/x86_64-linux-gnu/libcalligrasheetsodf.so.17
#9  0x00007f9a2c8f99a0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f9a2cd6bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007f9a2d76e8bb in KoApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libkomain.so.17
#12 0x00007f9a2c8cc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f9a2c8cfeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f9a2c9286f7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f9a2a113b2c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f9a2a16f46f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007f9a2a111d20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f9a2c927daa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f9a2c8cb15b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007f9a2c8d3904 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f9a2dad3d63 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_calligrasheets.so
#22 0x00007f9a2d828150 in __libc_start_call_main (main=main@entry=0x5839f838e060, argc=argc@entry=2, argv=argv@entry=0x7ffe45b9b388) at ../sysdeps/nptl/libc_start_call_main.h:58
#23 0x00007f9a2d828209 in __libc_start_main_impl (main=0x5839f838e060, argc=2, argv=0x7ffe45b9b388, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe45b9b378) at ../csu/libc-start.c:360
#24 0x00005839f838e095 in ?? ()
[Inferior 1 (process 11479) detached]

The reporter indicates this bug may be a duplicate of or related to bug 421067.

Reported using DrKonqi
Comment 1 Justin Zobel 2024-10-05 03:02:33 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols.
Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this.
Thanks again!
Comment 2 Bug Janitor Service 2024-10-20 03:47:33 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2024-11-04 03:46:24 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.