Description of problem:
I was configuring my desktop on a freshly installed system, when this crash happened.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (4 frames)
#0 gtk_drag_finish at gtkdnd.c:961
#1 gtk_drag_drop_finished at gtkdnd.c:2593
#2 gtk_drag_abort_timeout at gtkdnd.c:3265
#9 gtk_main at gtkmain.c:1323
Created attachment 1497304 [details]
Created attachment 1497305 [details]
Created attachment 1497306 [details]
Created attachment 1497307 [details]
Created attachment 1497308 [details]
Created attachment 1497309 [details]
Created attachment 1497310 [details]
Created attachment 1497311 [details]
Created attachment 1497312 [details]
Created attachment 1497313 [details]
Created attachment 1497314 [details]
Created attachment 1497315 [details]
(In reply to Suvayu from comment #0)
> Description of problem:
> I was configuring my desktop on a freshly installed system, when this crash
Is this crash happening every time you are using the desktop?
No, just this once. I had just installed the system, and was configuring my desktop. I have since rebooted and used the system for another day, and it hasn't recurred.
One thought, I think I might have also been updating the system in the background (I installed from Live media), don't recall exactly. Do you think the update process could have caused the crash?
Hope this helps.
xfce4-settings-4.13.6-1.fc30 xfce4-appfinder-4.13.3-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-cfc156acd7
xfce4-appfinder-4.13.3-1.fc30, xfce4-settings-4.13.6-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-cfc156acd7
xfce4-appfinder-4.13.3-1.fc30, xfce4-settings-4.13.6-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.