Version-Release number of selected component: udisks2-2.0.1-3.fc18 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/lib/udisks2/udisksd --no-debug crash_function: g_thread_abort executable: /usr/lib/udisks2/udisksd kernel: 3.10.12-100.fc18.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #2 g_thread_abort at gthread-posix.c:76 #3 g_mutex_lock at gthread-posix.c:211 #4 dispatch_in_thread_func at gdbusinterfaceskeleton.c:507 #5 io_job_thread at gioscheduler.c:162 #7 g_thread_proxy at gthread.c:797 #9 clone at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114
Created attachment 840261 [details] File: backtrace
Created attachment 840262 [details] File: cgroup
Created attachment 840263 [details] File: core_backtrace
Created attachment 840264 [details] File: dso_list
Created attachment 840265 [details] File: environ
Created attachment 840266 [details] File: limits
Created attachment 840267 [details] File: maps
Created attachment 840268 [details] File: open_fds
Created attachment 840269 [details] File: proc_pid_status
Created attachment 840270 [details] File: var_log_messages
Can you please provide a bit more details about the crash? It seems like a crash during mount operation, would be great to know what kind of device did you try to mount, details on how the mount operation has been spawned and if it's reproducible.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
(In reply to Tomáš Bžatek from comment #11) > Can you please provide a bit more details about the crash? It seems like a > crash during mount operation, would be great to know what kind of device did > you try to mount, details on how the mount operation has been spawned and if > it's reproducible. Sorry, this was a while ago. It was a Sansa C240 portable music player with a microSD card in it. It was an intermittent problem. I haven't run into it since, but don't often use that device at the moment, and that was with a different laptop to the one I'm using now, so who knows. I'll just raise a new bug if it happens again, with more detail.