Bug 1405568 - empty file /null is created by blkdeactivate anytime the system is rebooted with gnome-shell power menu
Summary: empty file /null is created by blkdeactivate anytime the system is rebooted w...
Keywords:
Status: CLOSED DUPLICATE of bug 1402800
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-16 17:53 UTC by Chris Murphy
Modified: 2016-12-16 18:58 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-16 18:58:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


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