https://bugs.kde.org/show_bug.cgi?id=469676
jvss...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469676
Nicolas Fella changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=469676
--- Comment #5 from Bug Janitor Service ---
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 b
https://bugs.kde.org/show_bug.cgi?id=469676
--- Comment #4 from jvss...@gmail.com ---
(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 w
https://bugs.kde.org/show_bug.cgi?id=469676
Nicolas Fella changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469676
--- Comment #2 from jvss...@gmail.com ---
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 li
https://bugs.kde.org/show_bug.cgi?id=469676
--- Comment #1 from jvss...@gmail.com ---
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 manag
