Bug 467419 - Okular crashed when connecting usb-c docking with 4k screen
Summary: Okular crashed when connecting usb-c docking with 4k screen
Status: RESOLVED DUPLICATE of bug 473602
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 22.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-03-15 20:09 UTC by Ondrej Malek
Modified: 2023-10-27 15:27 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 Ondrej Malek 2023-03-15 20:09:20 UTC
Application: okular (22.12.2)

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.8-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
Not sure if crashed happend while disconneted or connected to dock.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fe366d6954d in __memmove_avx_unaligned_erms () from /lib64/libc.so.6
#5  0x00007fe362b0e3ba in ?? () from /lib64/libQt5XcbQpa.so.5
#6  0x00007fe362b0e9b9 in ?? () from /lib64/libQt5XcbQpa.so.5
#7  0x00007fe362b0f2f9 in ?? () from /lib64/libQt5XcbQpa.so.5
#8  0x00007fe367b4d462 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib64/libQt5Gui.so.5
#9  0x00007fe3681b2a7f in QWidgetRepaintManager::flush (this=this@entry=0x563114e12900, widget=0x563114440040, region=..., widgetTextures=<optimized out>) at kernel/qwidgetrepaintmanager.cpp:1198
#10 0x00007fe3681b4609 in QWidgetRepaintManager::flush (this=0x563114e12900) at kernel/qwidgetrepaintmanager.cpp:1096
#11 0x00007fe3681b6688 in QWidgetRepaintManager::paintAndFlush (this=0x563114e12900) at kernel/qwidgetrepaintmanager.cpp:1028
#12 0x00007fe3681ff3e1 in QWidgetWindow::handleResizeEvent (this=0x563114e00450, event=0x7fff9fd4d220) at kernel/qwidgetwindow.cpp:841
#13 0x00007fe36820334b in QWidgetWindow::event (this=0x563114e00450, event=0x7fff9fd4d220) at kernel/qwidgetwindow.cpp:322
#14 0x00007fe3681a544e in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x563114e00450, e=0x7fff9fd4d220) at kernel/qapplication.cpp:3640
#15 0x00007fe3674dc1e8 in QCoreApplication::notifyInternal2 (receiver=0x563114e00450, event=0x7fff9fd4d220) at kernel/qcoreapplication.cpp:1064
#16 0x00007fe367977ccc in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib64/libQt5Gui.so.5
#17 0x00007fe36794f26c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Gui.so.5
#18 0x00007fe362b1914a in ?? () from /lib64/libQt5XcbQpa.so.5
#19 0x00007fe365d1ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#20 0x00007fe365d1be48 in ?? () from /lib64/libglib-2.0.so.0
#21 0x00007fe365d1bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#22 0x00007fe367533c16 in QEventDispatcherGlib::processEvents (this=0x5631143d60f0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x00007fe3674dac5b in QEventLoop::exec (this=this@entry=0x7fff9fd4d4a0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x00007fe3674e2dc6 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x000056311405d1f6 in ?? ()
#26 0x00007fe366c2c5b0 in __libc_start_call_main () from /lib64/libc.so.6
#27 0x00007fe366c2c679 in __libc_start_main_impl () from /lib64/libc.so.6
#28 0x000056311405dd05 in ?? ()
[Inferior 1 (process 18739) detached]

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

Reported using DrKonqi
Comment 1 Nate Graham 2023-05-02 18:03:49 UTC

*** This bug has been marked as a duplicate of bug 465077 ***
Comment 2 Nate Graham 2023-10-27 15:27:36 UTC

*** This bug has been marked as a duplicate of bug 473602 ***