Version-Release number of selected component: btrfs-progs-0.20.rc1.20121017git91d9eec-3.fc18 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /sbin/btrfs-debug-tree /dev/sdb1 crash_function: btrfs_print_tree executable: /usr/sbin/btrfs-debug-tree kernel: 3.9.10-200.fc18.x86_64 runlevel: N 5 uid: 0 var_log_messages: Jul 21 09:50:05 isuldur abrt[18613]: Saved core dump of pid 18611 (/usr/sbin/btrfs-debug-tree) to /var/tmp/abrt/ccpp-2013-07-21-09:50:05-18611 (47099904 bytes) Truncated backtrace: Thread no. 1 (1 frames) #2 btrfs_print_tree at print-tree.c:837
Created attachment 776494 [details] File: backtrace
Created attachment 776495 [details] File: cgroup
Created attachment 776496 [details] File: core_backtrace
Created attachment 776497 [details] File: dso_list
Created attachment 776498 [details] File: environ
Created attachment 776499 [details] File: limits
Created attachment 776501 [details] File: maps
Created attachment 776504 [details] File: open_fds
Created attachment 776506 [details] File: proc_pid_status
Would you mind testing the version in rawhide to see if the problem persists, if you can reproduce it?
I will give it a try in the next day or two. It's worth noting that I was simply logging in to KDE. I wasn't doing anything specific. Further, I have not seen the error since.
Weird. I have no idea why logging in to KDE would have caused /sbin/btrfs-debug-tree to execute...?
It's clear that nobody's going to look at abrt bugs on these old btrfs-progs releases; let's just be honest about it and close them.