Bug 1405568

Summary: empty file /null is created by blkdeactivate anytime the system is rebooted with gnome-shell power menu
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: agk, anprice, bmarzins, bmr, extras-orphan, gmazyland, heinzm, jonathan, lvm-team, msnitzer, prajnoha, prockai, zkabelac
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-16 18:58:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris Murphy 2016-12-16 17:53:38 UTC
Description of problem:

If Gnome Software has updates pending, and I reboot from gnome-shell (upper right corner, power button icon, restart) with "Install pending software updates" not checked, an empty file "null" is created in the root directory.


Version-Release number of selected component (if applicable):
device-mapper-1.02.131-3.fc25.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Clean install Fedora 25 and reboot
2. Wait for some updates to appear in gnome-software
3. reboot without installing updates


Actual results:

empty file /null appears; delete the file and restart again from gnome-shell as described and the file reappears


Expected results:

file should not exist


Additional info:

chattr +i on /null and reboot, then use 'journalctl -b-1 | grep null' to see if this file is being touched at restart time, and it is:

Dec 16 10:19:30 localhost.localdomain blkdeactivate[1787]: /usr/sbin/blkdeactivate: line 469: /null: Operation not permitted

Comment 1 Chris Murphy 2016-12-16 18:23:44 UTC
Is not reproducible with device-mapper-1.02.136-1.fc25.x86_64... hmm.

Also changing summary because I can reproduce this even without pending updates, just a regular gnome-shell restart is all that was needed to create this null file.

Comment 2 Milan Broz 2016-12-16 18:58:21 UTC

*** This bug has been marked as a duplicate of bug 1402800 ***