Created attachment 158894 [details] result of: strace -c dolphin . & pid=$!; sleep 3; kill $pid SUMMARY When I try to open dolphin with arguments to start on a specific directory it just hangs without actually open anything. Also, I'm not using Plasma, I use xmonad (just a windows manager). *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open dolphin normally will just open it 2. Open dolphin with argument (dolphin .) just hangs OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux: 6.3.1-arch2-1 Qt Version: 5.15.9 ADDITIONAL INFORMATION I don't know if this would be relevant but if not just ignore it. I managed to run a "strace -c" for a normal startup and one with arguments and noticed the calls were really low compared to the normal one. If I do the same just with just strace (no -c flag) the stuck one stays in "poll([{fd=4, events=POLLIN}, {fd=12, events=POLLIN}], 2, -1", while the normal one has a much larger output mainly staying with "poll([{fd=4, events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14, events=POLLPRI}, {fd=16, events=POLLIN}, {fd=27, events=POLLIN}, {fd=28, events=POLLIN}, {fd=29, events=POLLIN}, {fd=33, events=POLLIN}, {fd=34, events=POLLIN}, {fd=35, events=POLLIN}, {fd=39, events=POLLIN}, {fd=44, events=POLLIN}], 13, 27969". I'll also attach the "strace -c" results for each case.
I accidentally sent the report before attaching the strace -c results and trying to get a proper backtrace. I'll just put the "strace -c" results here and add another comment with the backtrace as soon as I manage to get it. called with: strace -c dolphin . & pid=$!; sleep 3; kill $pid % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ------------------ 26,86 0,001801 2 871 mmap 13,26 0,000889 0 1188 19 newfstatat 11,01 0,000738 1 541 104 openat 8,78 0,000589 1 382 48 access 7,04 0,000472 0 559 2 read 5,58 0,000374 1 305 244 readlink 5,32 0,000357 0 602 227 statx 4,80 0,000322 2 135 37 futex 4,61 0,000309 1 200 mprotect 4,31 0,000289 0 433 close 1,92 0,000129 0 141 getrandom 1,64 0,000110 3 29 munmap 0,95 0,000064 4 14 getdents64 0,79 0,000053 0 64 writev 0,78 0,000052 0 66 clock_gettime 0,69 0,000046 1 40 brk 0,46 0,000031 0 83 poll 0,36 0,000024 0 49 fstatfs 0,27 0,000018 0 30 write 0,18 0,000012 0 22 fadvise64 0,10 0,000007 1 6 4 prctl 0,06 0,000004 2 2 2 mkdir 0,04 0,000003 1 2 getuid 0,03 0,000002 0 3 geteuid 0,03 0,000002 2 1 inotify_init1 0,01 0,000001 0 3 getpid 0,01 0,000001 0 4 fcntl 0,01 0,000001 0 3 getcwd 0,01 0,000001 0 2 1 arch_prctl 0,01 0,000001 1 1 set_tid_address 0,01 0,000001 1 1 inotify_add_watch 0,01 0,000001 1 1 set_robust_list 0,01 0,000001 1 1 rseq 0,00 0,000000 0 1 lseek 0,00 0,000000 0 1 rt_sigaction 0,00 0,000000 0 5 rt_sigprocmask 0,00 0,000000 0 2 pread64 0,00 0,000000 0 1 shmget 0,00 0,000000 0 1 shmat 0,00 0,000000 0 1 shmctl 0,00 0,000000 0 1 socket 0,00 0,000000 0 1 connect 0,00 0,000000 0 2 recvfrom 0,00 0,000000 0 23 6 recvmsg 0,00 0,000000 0 1 getsockname 0,00 0,000000 0 1 getpeername 0,00 0,000000 0 1 execve 0,00 0,000000 0 1 uname 0,00 0,000000 0 1 shmdt 0,00 0,000000 0 1 gettid 0,00 0,000000 0 1 prlimit64 0,00 0,000000 0 2 clone3 ------ ----------- ----------- --------- --------- ------------------ 100,00 0,006705 1 5832 694 total called with: strace -c dolphin & pid=$!; sleep 3; kill $pid % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ------------------- 43,33 0,033740 1 24098 clock_gettime 7,76 0,006043 6 988 224 futex 6,55 0,005102 1 3284 write 6,46 0,005033 1 3571 695 read 4,97 0,003869 3 1159 mmap 3,91 0,003048 1 1765 159 openat 3,77 0,002938 1 2711 962 statx 3,23 0,002517 0 2905 198 newfstatat 2,98 0,002319 773 3 clone 2,66 0,002075 0 2259 2004 readlink 2,49 0,001941 1 1216 poll 2,45 0,001908 636 3 wait4 1,79 0,001393 0 1621 close 1,32 0,001027 0 2312 1550 access 0,73 0,000569 2 221 ioctl 0,56 0,000437 1 380 writev 0,48 0,000370 1 257 mprotect 0,46 0,000356 1 190 1 statfs 0,43 0,000334 0 366 ppoll 0,39 0,000304 3 100 munmap 0,37 0,000289 2 100 getdents64 0,35 0,000276 3 85 inotify_add_watch 0,34 0,000263 0 347 getrandom 0,23 0,000180 13 13 13 mkdir 0,23 0,000178 13 13 clone3 0,21 0,000160 1 132 brk 0,18 0,000144 4 35 rt_sigprocmask 0,17 0,000132 2 66 readlinkat 0,14 0,000111 1 82 fstatfs 0,11 0,000085 0 187 getuid 0,11 0,000082 7 11 2 linkat 0,08 0,000065 4 16 unlink 0,07 0,000057 5 11 socket 0,06 0,000049 2 22 fadvise64 0,06 0,000045 1 33 faccessat2 0,05 0,000042 0 50 gettimeofday 0,05 0,000041 5 8 bind 0,04 0,000033 16 2 setsockopt 0,04 0,000029 7 4 fdatasync 0,04 0,000028 0 29 6 recvmsg 0,03 0,000023 7 3 shmdt 0,03 0,000021 0 42 getpid 0,03 0,000020 6 3 shmctl 0,02 0,000019 1 17 lseek 0,02 0,000019 2 7 accept4 0,02 0,000019 3 6 pipe2 0,02 0,000015 5 3 2 connect 0,02 0,000013 0 30 fcntl 0,02 0,000012 6 2 rename 0,02 0,000012 0 14 geteuid 0,01 0,000010 1 7 listen 0,01 0,000009 3 3 shmat 0,01 0,000009 0 13 getcwd 0,01 0,000008 2 3 shmget 0,01 0,000008 0 9 getsockname 0,01 0,000007 1 6 4 prctl 0,01 0,000006 0 7 getsockopt 0,01 0,000005 0 6 uname 0,01 0,000005 2 2 sched_setscheduler 0,00 0,000003 1 2 pread64 0,00 0,000003 1 2 recvfrom 0,00 0,000002 1 2 rt_sigaction 0,00 0,000002 0 8 getpeername 0,00 0,000002 1 2 chmod 0,00 0,000002 1 2 inotify_init1 0,00 0,000001 0 2 fchmod 0,00 0,000001 0 2 1 arch_prctl 0,00 0,000001 1 1 gettid 0,00 0,000001 1 1 set_tid_address 0,00 0,000001 1 1 set_robust_list 0,00 0,000001 1 1 prlimit64 0,00 0,000001 1 1 rseq 0,00 0,000000 0 1 madvise 0,00 0,000000 0 1 execve 0,00 0,000000 0 2 flock 0,00 0,000000 0 1 sysinfo 0,00 0,000000 0 1 inotify_init ------ ----------- ----------- --------- --------- ------------------- 100,00 0,077873 1 50871 5821 total
Backtrace for successful dolphin launch and the hanging one (with GNU gdb (GDB) 13.1) (I had to Ctrl+C the process): Starting program: /usr/bin/dolphin [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffefb8d6c0 (LWP 373538)] [New Thread 0x7fffef38c6c0 (LWP 373539)] [New Thread 0x7fffee5536c0 (LWP 373540)] [New Thread 0x7fffece3a6c0 (LWP 373577)] [New Thread 0x7fffd65ff6c0 (LWP 373578)] [New Thread 0x7fffd5dfe6c0 (LWP 373579)] [New Thread 0x7fffd55fd6c0 (LWP 373580)] [New Thread 0x7fffd4dfc6c0 (LWP 373581)] [Detaching after fork from child process 373621] [Detaching after fork from child process 373623] [New Thread 0x7fffbffff6c0 (LWP 373625)] [New Thread 0x7fffbf4986c0 (LWP 373627)] [New Thread 0x7fffbec976c0 (LWP 373630)] [New Thread 0x7fffbe4966c0 (LWP 373631)] [New Thread 0x7fffbdc956c0 (LWP 373632)] [New Thread 0x7fffbd4946c0 (LWP 373633)] [Detaching after fork from child process 373645] Starting program: /usr/bin/dolphin . [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffefb8d6c0 (LWP 374519)] [New Thread 0x7fffef38c6c0 (LWP 374520)]
Is another Dolphin instance already running? Depending on your configuration opening a second instance can attach to an existing window instead of opening a new window
(In reply to Nicolas Fella from comment #3) > Is another Dolphin instance already running? Depending on your configuration > opening a second instance can attach to an existing window instead of > opening a new window No, it also happens when killing all dolphin processes (checked there were no processes left with `ps aux | grep -i dolphin`)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
For some reason it has been fixed in the last few days. I would say it was a missing optional dependency that I've installed, but it has also been fixed on a laptop with Artix in which I was able to replicate the bug and haven't booted it up since.