[dolphin] [Bug 476842] Constant crashes recently

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sun Nov 12 23:58:26 GMT 2023


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

--- Comment #9 from fanzhuyifan at gmail.com ---
(In reply to Henning from comment #8)
> I got a crash:
> 
> /v/h/user ❯❯❯ dolphin                                                       
> master ◼
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> GPL Ghostscript 10.01.2: Unrecoverable error, exit code 1
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> Not a JPEG file: starts with 0x00 0x00
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> Not a JPEG file: starts with 0x00 0x00
> libpng warning: iCCP: known incorrect sRGB profile
> QProcess: Destroyed while process ("git") is still running.
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> QProcess: Destroyed while process ("git") is still running.
> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x5617b6e13900] stream 0, timescale not set
> [mov,mp4,m4a,3gp,3g2,mj2 @ 0x5617b6e13900] stream 0, timescale not set
> QProcess: Destroyed while process ("git") is still running.
> KCrash: Application 'dolphin' crashing...
> KCrash: Attempting to start /usr/libexec/drkonqi
> kf5idletime_wayland: This plugin does not support polling idle time
> QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 20 and type 'Exception', disabling...
> QSocketNotifier: Invalid socket 22 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 37 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 43 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 44 and type 'Read', disabling...
> QSocketNotifier: Invalid socket 54 and type 'Read', disabling...
> fish: Job 1, 'dolphin' has stopped

Hi, unfortunately this is not a backtrace.. To get the backtrace you can refer
to the instructions on the wiki
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

One method is to run dolphin in gdb. For details, you could refer to this
section
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the kfm-devel mailing list