https://bugs.kde.org/show_bug.cgi?id=473781

            Bug ID: 473781
           Summary: Kate crashed after wakeup from standby
    Classification: Applications
           Product: kate
           Version: 22.12.3
          Platform: Ubuntu
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: kwrite-bugs-n...@kde.org
          Reporter: wuestenbaeckersaeltes...@gmail.com
  Target Milestone: ---

Application: kate (22.12.3)

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.0-27-generic x86_64
Windowing System: X11
Distribution: Ubuntu 23.04
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
Kate crashed to gater with the plasma shell sortly after wacking up the
notebook from standby. The files that ware open in Kate ware opened via sftp on
a server with a public DNS name. The laptop auto conected to a public hotspot
that requires klicking ok on a "login" page to get internet. I had not don that
at the time of the crash so the laptop had a wifi network but no usible
internet connection.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f47a8eef3f3 in QObject::property(char const*) const () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f47a9ba57f4 in KUiServerV2JobTracker::registerJob(KJob*) () from
/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#6  0x00007f47a9ba279c in ?? () from
/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#7  0x00007f47a8ef39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f47a8ef39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007f47aa43b8a3 in QDBusServiceWatcher::serviceOwnerChanged(QString
const&, QString const&, QString const&) () from
/lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x00007f47aa43c1e2 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x00007f47aa43c69b in QDBusServiceWatcher::qt_metacall(QMetaObject::Call,
int, void**) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x00007f47aa3ed22b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x00007f47a8ee7de0 in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f47a9d6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f47a8ebae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f47a8ebdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f47a8f157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f47a6f1549d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f47a6f70178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f47a6f141b0 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f47a8f14e7a in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f47a8eb97cb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007f47a8ec1c1a in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000055f22a27b388 in ?? ()
#25 0x00007f47a8423a90 in __libc_start_call_main
(main=main@entry=0x55f22a279ef0, argc=argc@entry=3,
argv=argv@entry=0x7ffdde56db08) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007f47a8423b49 in __libc_start_main_impl (main=0x55f22a279ef0, argc=3,
argv=0x7ffdde56db08, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffdde56daf8) at ../csu/libc-start.c:360
#27 0x000055f22a27d795 in ?? ()
[Inferior 1 (process 3284) detached]

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

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to