Crash to graphical login when connecting to MTP filesystem

[sync1211]

Hi there,
since a few days ago I have a bug with my Kali installation where the Desktop (I belive it's gdm3) would crash to its login screen when connecting to a MTP filesystem (Samsung Galaxy A3) via USB (2.0 and 3.0).
Is there a way to fix it?

System Information:

#cat /etc/*release*

DISTRIB_ID=Kali
DISTRIB_RELEASE=kali-rolling
DISTRIB_CODENAME=kali-rolling
DISTRIB_DESCRIPTION="Kali GNU/Linux Rolling"
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2018.1"
VERSION_ID="2018.1"
ID_LIKE=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.kali.org/"
SUPPORT_URL="http://forums.kali.org/"
BUG_REPORT_URL="http://bugs.kali.org/"

# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b374 Chicony Electronics Co., Ltd 
Bus 001 Device 004: ID 0489:e04e Foxconn / Hon Hai 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

A part of dmesg after connecting the MTP device:
new high-speed USB device number 12 using xhci_hcd
[ 1850.871833] usb 3-2: New USB device found, idVendor=04e8, idProduct=6860
[ 1850.871841] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1850.871845] usb 3-2: Product: SAMSUNG_Android
[ 1850.871848] usb 3-2: Manufacturer: SAMSUNG
[ 1850.871851] usb 3-2: SerialNumber: 3100f1c6a381330b
[ 1855.393864] rfkill: input handler enabled
[ 1856.582081] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1856.633739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1858.978857] usb 3-2: USB disconnect, device number 12
[ 1864.839232] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1867.065183] rfkill: input handler disabled

Let me know if you need any more information!


Thanks in advance!

[sync1211]

Nevermind; it started working again without me doing anything...