Bug 456259 - k3b crash
Summary: k3b crash
Status: REPORTED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 22.04.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2022-07-02 20:21 UTC by Eat greens
Modified: 2022-07-03 21:23 UTC (History)
3 users (show)

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


Attachments
k3b (409 bytes, text/plain)
2022-07-03 18:21 UTC, Eat greens
Details
k3b burner (18.46 KB, text/plain)
2022-07-03 20:03 UTC, Eat greens
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eat greens 2022-07-02 20:21:50 UTC
Application: k3b (22.04.2)
 (Compiled from sources)
Qt Version: 5.15.5
Frameworks Version: 5.95.0
Operating System: Linux 5.17.15-1 x86_64
Windowing System: X11
Distribution: KaOS (2022)
DrKonqi: 5.25.2 [KCrashBackend]

-- Information about the crash:
Just a quick flash of k3b appliction starting, then it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: K3b (k3b), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fdf2cb2bc56 in K3b::PluginManager::loadAll() () from /usr/lib/libk3blib.so.7
#5  0x00007fdf2cae17f7 in K3b::Core::init() () from /usr/lib/libk3blib.so.7
#6  0x00000000004809bc in ?? ()
#7  0x00007fdf2ab807be in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#8  0x00007fdf2b6e2abf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#9  0x00007fdf2ab55d8a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#10 0x00007fdf2ab58b17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#11 0x00007fdf2abaa1d3 in ?? () from /usr/lib/libQt5Core.so.5
#12 0x00007fdf2615b6eb in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#13 0x00007fdf2615b958 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007fdf2615b9ff in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#15 0x00007fdf2aba98a4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#16 0x00007fdf2ab5490b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#17 0x00007fdf2ab5c55c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#18 0x000000000046759a in ?? ()
#19 0x00007fdf2a4dc1f7 in __libc_start_call_main () from /lib/libc.so.6
#20 0x00007fdf2a4dc2ac in __libc_start_main_impl () from /lib/libc.so.6
#21 0x0000000000467791 in _start ()
[Inferior 1 (process 2851) detached]

Reported using DrKonqi
Comment 1 Albert Astals Cid 2022-07-03 10:17:44 UTC
Can you attach what you get if you run 

valgrind k3b

from a terminal?
Comment 2 Eat greens 2022-07-03 18:21:45 UTC
Created attachment 150369 [details]
k3b

On 3.7.2022 13.17, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=456259
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |aacid@kde.org
>
> --- Comment #1 from Albert Astals Cid <aacid@kde.org> ---
> Can you attach what you get if you run
>
> valgrind k3b
>
> from a terminal?
>
Comment 3 Eat greens 2022-07-03 20:03:16 UTC
Created attachment 150373 [details]
k3b burner

On 3.7.2022 13.17, Albert Astals Cid wrote:
> https://bugs.kde.org/show_bug.cgi?id=456259
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |aacid@kde.org
>
> --- Comment #1 from Albert Astals Cid <aacid@kde.org> ---
> Can you attach what you get if you run
>
> valgrind k3b
>
> from a terminal?
>
Comment 4 Albert Astals Cid 2022-07-03 21:23:38 UTC
You compiled k3b manually? Can you compile it in debug mode so the backtrace crash is more useful?