Bug 1012180 - profiling:/builddir:Cannot create directory after close
Summary: profiling:/builddir:Cannot create directory after close
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libevdev
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-25 22:34 UTC by Igor Gnatenko
Modified: 2013-11-29 06:57 UTC (History)
5 users (show)

Fixed In Version: libevdev-0.5-1.fc19
Clone Of:
Environment:
Last Closed: 2013-11-29 06:57:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Igor Gnatenko 2013-09-25 22:34:06 UTC
Description of problem:


Version-Release number of selected component (if applicable):
bijiben-3.9.91-1.fc20.x86_64

How reproducible:
always

Steps to Reproduce:
1. open bijiben
2. close bijiben

Actual results:
profiling:/builddir:Cannot create directory
profiling:/builddir/build/BUILD/libevdev-0.4/libevdev/.libs/libevdev.gcda:Skip
profiling:/builddir:Cannot create directory
profiling:/builddir/build/BUILD/libevdev-0.4/libevdev/.libs/libevdev-uinput.gcda:Skip

Expected results:
clear

Additional info:

Comment 1 Pierre-Yves Luyten 2013-09-25 23:50:30 UTC
my guess is the issue comes from the build, but i have to look for the fix (request another build?)

does not occur on rawhide

Comment 2 Pierre-Yves Luyten 2013-09-26 06:05:17 UTC
> does not occur on rawhide

my bad, it does too. And mockbuild too.

Comment 3 Michael Schwendt 2013-09-26 06:05:54 UTC
$ strings /usr/lib64/libevdev.so.1.0.0|grep builddir
/builddir/build/BUILD/libevdev-0.4/libevdev/.libs/libevdev-uinput.gcda
/builddir/build/BUILD/libevdev-0.4/libevdev/.libs/libevdev.gcda
$ rpm -qf /usr/lib64/libevdev.so.1.0.0
libevdev-0.4-1.fc20.x86_64

Comment 4 Michael Schwendt 2013-09-26 07:25:59 UTC
This is because libevdev's configure default is --enable-gcov, so it builds with profiling enabled.

Comment 5 Fedora Update System 2013-10-02 00:26:47 UTC
libevdev-0.4-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/libevdev-0.4-2.fc19

Comment 6 Fedora Update System 2013-10-02 00:27:40 UTC
libevdev-0.4-2.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/libevdev-0.4-2.fc20

Comment 7 Fedora Update System 2013-10-03 01:10:37 UTC
Package libevdev-0.4-2.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libevdev-0.4-2.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-18173/libevdev-0.4-2.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2013-10-04 01:52:57 UTC
libevdev-0.4-2.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-10-31 23:32:14 UTC
libevdev-0.4.1-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/libevdev-0.4.1-1.fc19

Comment 10 Fedora Update System 2013-11-02 04:59:26 UTC
Package libevdev-0.4.1-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libevdev-0.4.1-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-20508/libevdev-0.4.1-1.fc19
then log in and leave karma (feedback).

Comment 11 Fedora Update System 2013-11-26 21:58:13 UTC
libevdev-0.5-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/libevdev-0.5-1.fc19

Comment 12 Fedora Update System 2013-11-29 06:57:43 UTC
libevdev-0.5-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


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