Hide Forgot
Description of problem: disconnected & reconnected nexus 7 wich cyanogenmod 12.1 Seems to have apeared when I reconnected it. Version-Release number of selected component: Thunar-1.6.10-2.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: thunar_shortcuts_model_set_busy executable: /usr/bin/thunar global_pid: 27279 kernel: 4.3.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 thunar_shortcuts_model_set_busy at thunar-shortcuts-model.c:2163 #1 thunar_browser_poke_device_finish at thunar-browser.c:588 #2 thunar_device_operation_finish at thunar-device.c:275 #3 mount_foreign_callback at gproxyvolume.c:824 #4 g_simple_async_result_complete at gsimpleasyncresult.c:801 #5 mount_reply at gdaemonfile.c:2012 #6 g_task_return_now at gtask.c:1106 #7 g_task_return at gtask.c:1164 #8 reply_cb at gdbusproxy.c:2569 #9 g_task_return_now at gtask.c:1106 Potential duplicate: bug 1273581
Created attachment 1116324 [details] File: backtrace
Created attachment 1116325 [details] File: cgroup
Created attachment 1116326 [details] File: core_backtrace
Created attachment 1116327 [details] File: dso_list
Created attachment 1116328 [details] File: environ
Created attachment 1116329 [details] File: exploitable
Created attachment 1116330 [details] File: limits
Created attachment 1116331 [details] File: maps
Created attachment 1116332 [details] File: mountinfo
Created attachment 1116333 [details] File: namespaces
Created attachment 1116334 [details] File: open_fds
Created attachment 1116335 [details] File: proc_pid_status
Created attachment 1116336 [details] File: var_log_messages
Does this happen everytime? Or is it sporadic? Did you copy files to it before disconnecting?
First time this happened. As far as I remember I have copied from the device and deleted some stuff on the device, then disconnected and it crashed when I reconnected it.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.