Bug 873932 - Generating backtrace locally fails with complaining the permission for build_ids
Summary: Generating backtrace locally fails with complaining the permission for build_ids
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-07 02:08 UTC by Mamoru TASAKA
Modified: 2013-07-31 17:36 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-07-31 17:36:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
strace for /usr/bin/abrt-action-perform-ccpp-analysis (758.15 KB, text/plain)
2012-11-07 02:08 UTC, Mamoru TASAKA
no flags Details
strace retaken with -s 1000 (1.53 MB, text/plain)
2012-11-12 01:32 UTC, Mamoru TASAKA
no flags Details

Description Mamoru TASAKA 2012-11-07 02:08:40 UTC
Created attachment 639761 [details]
strace for  /usr/bin/abrt-action-perform-ccpp-analysis

Description of problem:
When I choose to generate backtrace locally instead of uploading coredump, it fails with complaining the permission for build_ids

Version-Release number of selected component (if applicable):
abrt-2.0.18-1.fc17.i68

How reproducible:
100%

Steps to Reproduce:
1. From terminal type $ /usr/libexec/xscreensaver/maze &
2. And from the terminal type $ killall -SIGSEGV maze
3. notify event happens (in GNOME), telling something like "A problem in xscreensaver-extras-5.20-3.fc17 has been detected" (in Japanese), then click "report" (in Japanese)
4. One dialog pops up, asking "Ok to upload core dump? ...... If your answer is 'No', a stack trace will be generated locally", then click "NO"
  
Actual results:

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'NO'
Analyzing coredump 'coredump'
Can't open build_ids: [Errno 13] Permission denied: 'build_ids'
(exited with 1)

Expected results:
backtrace should be reported locally and abrt should successfully report the problem


Additional info:
strace for  /usr/bin/abrt-action-perform-ccpp-analysis is attached.

$ pwd
/home/mtasaka/.cache/abrt/spool/ccpp-2012-11-07-10:47:47-5940

$ env LANG=C ls -al
total 584
drwxr-x---.  2 mtasaka mtasaka     4096 Nov  7 10:52 .
drwx------. 12 mtasaka mtasaka     4096 Nov  7 11:00 ..
-rw-------.  1 mtasaka mtasaka        6 Nov  7 10:47 abrt_version
-rw-------.  1 mtasaka mtasaka        4 Nov  7 10:47 analyzer
-rw-------.  1 mtasaka mtasaka        4 Nov  7 10:47 architecture
-rw-------.  1 mtasaka mtasaka      697 Nov  7 10:52 build_ids
-rw-------.  1 mtasaka mtasaka      130 Nov  7 10:47 cgroup
-rw-------.  1 mtasaka mtasaka       30 Nov  7 10:47 cmdline
-rw-------.  1 mtasaka mtasaka       12 Nov  7 10:47 component
-rw-------.  1 mtasaka mtasaka      504 Nov  7 10:47 core_backtrace
-rw-------.  1 mtasaka mtasaka 20553728 Nov  7 10:47 coredump
-rw-------.  1 mtasaka mtasaka        1 Nov  7 10:47 count
-rw-------.  1 mtasaka mtasaka     1349 Nov  7 10:47 dso_list
-rw-------.  1 mtasaka mtasaka     3192 Nov  7 10:47 environ
-rw-------.  1 mtasaka mtasaka      399 Nov  7 10:52 event_log
-rw-------.  1 mtasaka mtasaka       30 Nov  7 10:47 executable
-rw-------.  1 mtasaka mtasaka       21 Nov  7 10:47 hostname
-rw-------.  1 mtasaka mtasaka       17 Nov  7 10:47 kernel
-rw-------.  1 mtasaka mtasaka     1323 Nov  7 10:47 limits
-rw-------.  1 mtasaka mtasaka     4272 Nov  7 10:47 maps
-rw-------.  1 mtasaka mtasaka      130 Nov  7 10:47 open_fds
-rw-------.  1 mtasaka mtasaka       33 Nov  7 10:47 os_release
-rw-------.  1 mtasaka mtasaka       31 Nov  7 10:47 package
-rw-------.  1 mtasaka mtasaka        4 Nov  7 10:47 pid
-rw-------.  1 mtasaka mtasaka        4 Nov  7 10:47 pkg_arch
-rw-------.  1 mtasaka mtasaka        1 Nov  7 10:47 pkg_epoch
-rw-------.  1 mtasaka mtasaka       19 Nov  7 10:47 pkg_name
-rw-------.  1 mtasaka mtasaka        6 Nov  7 10:47 pkg_release
-rw-------.  1 mtasaka mtasaka        4 Nov  7 10:47 pkg_version
-rw-------.  1 mtasaka mtasaka      767 Nov  7 10:47 proc_pid_status
-rw-------.  1 mtasaka mtasaka       13 Nov  7 10:47 pwd
-rw-------.  1 mtasaka mtasaka       72 Nov  7 10:47 reason
-rw-------.  1 mtasaka mtasaka       57 Nov  7 10:47 reported_to
-rw-------.  1 mtasaka mtasaka       10 Nov  7 10:47 time
-rw-------.  1 mtasaka mtasaka        3 Nov  7 10:47 uid
-rw-------.  1 mtasaka mtasaka        8 Nov  7 10:47 username
-rw-------.  1 mtasaka mtasaka       40 Nov  7 10:47 uuid
-rw-------.  1 mtasaka mtasaka      330 Nov  7 10:47 var_log_messages

Comment 1 Mamoru TASAKA 2012-11-12 01:32:53 UTC
Created attachment 643149 [details]
strace retaken with -s 1000

strace log taken with -s 1000 option

This log says:
[pid  5063] execve("/bin/sh", ["/bin/sh", "-c", "abrt-action-analyze-core --core=coredump -o build_ids &&\n        /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache --size_mb=4096 &&\n        abrt-action-generate-backtrace &&\n        abrt-action-analyze-backtrace &&\n        (\n            bug_id=$(reporter-bugzilla -h `cat duphash`) &&\n            if test -n \"$bug_id\"; then\n                abrt-bodhi -r -b $bug_id\n            fi\n        )"], [/* 55 vars */]) = 0
[pid  5066] execve("/usr/libexec/abrt-action-install-debuginfo-to-abrt-cache", ["/usr/libexec/abrt-action-install-debuginfo-to-abrt-cache", "--size_mb=4096"], [/* 55 vars */]) = 0
[pid  5066] open("build_ids", O_RDONLY|O_LARGEFILE) = -1 EACCES (Permission denied)

And /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache has setuid
permission:
-rwsr-xr-x. 1 abrt abrt 9772 Nov  1 20:28 /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache

So looks like abrt-action-install-debuginfo-to-abrt-cache really does not have permission for accessing build_ids.

Comment 2 Fedora End Of Life 2013-07-03 19:17:36 UTC
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.

Comment 3 Fedora End Of Life 2013-07-31 17:36:48 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.