FS#53613 - [exfat-utils] core dump
Attached to Project:
Community Packages
Opened by Amitav (amitavmohanty01) - Saturday, 08 April 2017, 11:14 GMT
Last edited by Ivy Foster (escondida) - Saturday, 12 October 2019, 17:56 GMT
Opened by Amitav (amitavmohanty01) - Saturday, 08 April 2017, 11:14 GMT
Last edited by Ivy Foster (escondida) - Saturday, 12 October 2019, 17:56 GMT
|
Details
Description:
when an usb drive with exfat partition is connected there is a coredump Additional info: * package version(s) exfat-utils-1.2.6-1 * config and/or log files etc. PID: 6024 (mount.exfat) UID: 0 (root) GID: 0 (root) Signal: 6 (ABRT) Timestamp: Sat 2017-04-08 01:48:54 IST (14h ago) Command Line: /sbin/mount.exfat /dev/sdb2 /run/media/dknight/New Volume -o rw,nodev,nosuid,uid=1000,gid=100,iocharset=utf8,namecase=0,errors=remount-ro,uhelper=udisks2 Executable: /usr/bin/mount.exfat-fuse Control Group: /system.slice/udisks2.service Unit: udisks2.service Slice: system.slice Boot ID: db9f6c0154fc4e19aa966e6de7869c80 Machine ID: f52d0eeb525f4cd584fe54d97e927133 Hostname: clown.man.machine Storage: /var/lib/systemd/coredump/core.mount\x2eexfat.0.db9f6c0154fc4e19aa966e6de7869c80.6024.1491596334000000000000.lz4 Message: Process 6024 (mount.exfat) of user 0 dumped core. Stack trace of thread 6024: #0 0x00007f5b50ac7a10 raise (libc.so.6) #1 0x00007f5b50ac913a abort (libc.so.6) #2 0x0000000000403b0b n/a (mount.exfat-fuse) #3 0x0000000000405613 n/a (mount.exfat-fuse) #4 0x00000000004055bd n/a (mount.exfat-fuse) #5 0x00000000004055bd n/a (mount.exfat-fuse) #6 0x0000000000404d05 n/a (mount.exfat-fuse) #7 0x00007f5b51067aa2 fuse_fs_destroy (libfuse.so.2) #8 0x00007f5b51067b0c n/a (libfuse.so.2) #9 0x00007f5b5106b083 n/a (libfuse.so.2) #10 0x00007f5b5106cf91 n/a (libfuse.so.2) #11 0x00007f5b5106933c fuse_session_loop (libfuse.so.2) #12 0x00007f5b510616e8 fuse_loop (libfuse.so.2) #13 0x0000000000401b65 n/a (mount.exfat-fuse) #14 0x00007f5b50ab4511 __libc_start_main (libc.so.6) #15 0x0000000000401c5a n/a (mount.exfat-fuse) |
This task depends upon
Closed by Ivy Foster (escondida)
Saturday, 12 October 2019, 17:56 GMT
Reason for closing: Deferred
Additional comments about closing: OP believes it may have been a one-off issue; no further reports have come in on it in two years.
Saturday, 12 October 2019, 17:56 GMT
Reason for closing: Deferred
Additional comments about closing: OP believes it may have been a one-off issue; no further reports have come in on it in two years.
Comment by Ivy Foster (escondida) -
Thursday, 10 October 2019, 22:05 GMT
Comment by
Amitav (amitavmohanty01) - Friday,
11 October 2019, 06:56 GMT
Comment by Ivy Foster (escondida) -
Saturday, 12 October 2019, 17:54 GMT
amitavmohanty01, do you still experience this issue?
The issue was more than 2 years earlier. So, I do not know whether
it is happening now. I understand that issues like these that are
one-off or not affecting many people will get neglected but in the
course of time, I have also stopped caring for this. So, if you
want to close it, go ahead. If I find the issue again some time, I
will open another ticket.
Thanks for getting back to me, amitavmohanty01. I'm I'm going to
go ahead and close this for now, then, and if the bug rears its
ugly head for you or someone else I guess we'll deal with that
then.