Version-Release number of selected component: udisks-1.0.4-6.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: /usr/libexec/udisks-daemon --no-debug crash_function: g_logv kernel: 3.5.3-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (6 frames) : #0 g_logv at gmessages.h : #2 register_disks_device at device.c : #3 device_new at device.c : #4 block_device_add at daemon.c : #5 device_add at daemon.c : #10 monitor_event at src/gudev/gudevclient.c
Created attachment 612515 [details] File: core_backtrace
Created attachment 612516 [details] File: environ
Created attachment 612517 [details] File: smart_data
Created attachment 612518 [details] File: backtrace
Created attachment 612519 [details] File: limits
Created attachment 612520 [details] File: cgroup
Created attachment 612521 [details] File: maps
Created attachment 612522 [details] File: dso_list
Created attachment 612523 [details] File: var_log_messages
Created attachment 612524 [details] File: open_fds
I found that udisks2.service crash often and service udisks2.service goes down , since mid-August.
This happened after unmounted an Android Phone. Also SELINUX triggered an alert: SELinux is preventing /usr/sbin/skdump from read access on the blk_file sdb. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that skdump should be allowed read access on the sdb blk_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep skdump /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Context system_u:object_r:fixed_disk_device_t:s0 Target Objects sdb [ blk_file ] Source skdump Source Path /usr/sbin/skdump Port <Unknown> Host toxibas Source RPM Packages libatasmart-0.18-2.fc17.x86_64 Target RPM Packages Policy RPM selinux-policy-3.10.0-156.fc17.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name toxibas Platform Linux toxibas 3.6.2-4.fc17.x86_64 #1 SMP Wed Oct 17 02:43:21 UTC 2012 x86_64 x86_64 Alert Count 2 First Seen 2012-10-26 11:12:11 WEST Last Seen 2012-10-26 11:12:11 WEST Local ID 006e3cce-834d-4156-9d11-d8b3e7ce15a4 Raw Audit Messages type=AVC msg=audit(1351246331.908:97): avc: denied { read } for pid=4476 comm="skdump" name="sdb" dev="devtmpfs" ino=1918899 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:fixed_disk_device_t:s0 tclass=blk_file type=SYSCALL msg=audit(1351246331.908:97): arch=x86_64 syscall=open success=no exit=EACCES a0=22496c0 a1=80900 a2=0 a3=9 items=0 ppid=4473 pid=4476 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=skdump exe=/usr/sbin/skdump subj=system_u:system_r:abrt_t:s0-s0:c0.c1023 key=(null) Hash: skdump,abrt_t,fixed_disk_device_t,blk_file,read audit2allow #============= abrt_t ============== allow abrt_t fixed_disk_device_t:blk_file read; audit2allow -R #============= abrt_t ============== allow abrt_t fixed_disk_device_t:blk_file read; backtrace_rating: 4 Package: udisks-1.0.4-6.fc17 OS Release: Fedora release 17 (Beefy Miracle)
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 877641 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
I haven't seen this bug for a long time in FC18, so it's safe assume that's resolved?
I also, don't see this bug for a long time in FC18
(In reply to Paulo Fidalgo from comment #16) > I haven't seen this bug for a long time in FC18, so it's safe assume that's > resolved? Unlikely as udisks codebase has not been updated since the reported release. More likely the applications you're using have been ported to udisks2.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.