Revision history [back]
 | 1 | initial version | posted 2014-02-27 01:03:58 +0200 |
What creates the files named (null).* in nemo user home dir?
Why are there constantly coming files named (null).something popping up in the nemo user home directory?
e.g.
[nemo@localhost ~]$ ls -1 \(null\).*
(null).04ZSAX
(null).0W4OBX
(null).36YABX
(null).492WBX
(null).4I9YAX
(null).7AFTBX
(null).9KVHBX
(null).A0GRAX
(null).C7WRBX
(null).DQ15AX
(null).EF7GBX
(null).GBW3AX
(null).GDOUAX
(null).GEGSAX
(null).H044AX
(null).HSRYBX
(null).IAJLBX
(null).J4Z6AX
(null).KW4NBX
(null).N6CFBX
(null).NO2IBX
(null).NV6RBX
(null).P6HXBX
(null).PKDWBX
(null).QZ1IBX
(null).UO1OBX
Something is obviously not cleaning up after itself and therefore wasting storage space and inodes. Please fix? :)
| | 2 | No.2 Revision |
What creates the files named (null).* in nemo user home dir?
Why are there constantly coming files named (null).something popping up in the nemo user home directory?
e.g.
[nemo@localhost ~]$ ls -1 \(null\).*
(null).04ZSAX
(null).0W4OBX
(null).36YABX
(null).492WBX
(null).4I9YAX
(null).7AFTBX
(null).9KVHBX
(null).A0GRAX
(null).C7WRBX
(null).DQ15AX
(null).EF7GBX
(null).GBW3AX
(null).GDOUAX
(null).GEGSAX
(null).H044AX
(null).HSRYBX
(null).IAJLBX
(null).J4Z6AX
(null).KW4NBX
(null).N6CFBX
(null).NO2IBX
(null).NV6RBX
(null).P6HXBX
(null).PKDWBX
(null).QZ1IBX
(null).UO1OBX
\(null\).* | xargs file
(null).04ZSAX: JPEG image data, JFIF standard 1.02
(null).0LKDBX: JPEG image data, JFIF standard 1.02
(null).0W4OBX: JPEG image data, JFIF standard 1.02
(null).36YABX: JPEG image data, JFIF standard 1.02
(null).492WBX: JPEG image data, JFIF standard 1.02
(null).4I9YAX: JPEG image data, JFIF standard 1.01
(null).7AFTBX: JPEG image data, JFIF standard 1.02
(null).9KVHBX: JPEG image data, JFIF standard 1.01
(null).A0GRAX: JPEG image data, JFIF standard 1.02
(null).C7WRBX: JPEG image data, JFIF standard 1.02
(null).DQ15AX: JPEG image data, JFIF standard 1.02
(null).EF7GBX: JPEG image data, JFIF standard 1.02
(null).GBW3AX: JPEG image data, JFIF standard 1.01
(null).GDOUAX: JPEG image data, JFIF standard 1.02
(null).GEGSAX: JPEG image data, JFIF standard 1.02
(null).GM3SBX: JPEG image data, JFIF standard 1.02
(null).H044AX: JPEG image data, JFIF standard 1.02
(null).HFBQBX: JPEG image data, JFIF standard 1.02
(null).HSRYBX: JPEG image data, JFIF standard 1.02
(null).IAJLBX: JPEG image data, JFIF standard 1.02
(null).J4Z6AX: JPEG image data, JFIF standard 1.02
(null).JCFOBX: JPEG image data, JFIF standard 1.02
(null).KW4NBX: JPEG image data, JFIF standard 1.02
(null).N6CFBX: JPEG image data, JFIF standard 1.01
(null).NO2IBX: JPEG image data, JFIF standard 1.01
(null).NV6RBX: JPEG image data, JFIF standard 1.02
(null).P6HXBX: JPEG image data, JFIF standard 1.02
(null).PKDWBX: JPEG image data, JFIF standard 1.02
(null).QZ1IBX: JPEG image data, JFIF standard 1.02
(null).RAMMBX: JPEG image data, JFIF standard 1.01
(null).UO1OBX: JPEG image data, JFIF standard 1.02
Something is obviously not cleaning up after itself and therefore wasting storage space and inodes. Please fix? :)
[update] ran the files above through file(1) and updated the list. They're all images, and they're all podcast-related, so I'm guessing this is a bug in gPodder.
| | 3 | No.3 Revision |
What creates the files named (null).* in nemo user home dir?
Why are there constantly coming files named (null).something popping up in the nemo user home directory?
e.g.
[nemo@localhost ~]$ ls -1 \(null\).* | xargs file
(null).04ZSAX: JPEG image data, JFIF standard 1.02
(null).0LKDBX: JPEG image data, JFIF standard 1.02
(null).0W4OBX: JPEG image data, JFIF standard 1.02
(null).36YABX: JPEG image data, JFIF standard 1.02
(null).492WBX: JPEG image data, JFIF standard 1.02
(null).4I9YAX: JPEG image data, JFIF standard 1.01
(null).7AFTBX: JPEG image data, JFIF standard 1.02
(null).9KVHBX: JPEG image data, JFIF standard 1.01
(null).A0GRAX: JPEG image data, JFIF standard 1.02
(null).C7WRBX: JPEG image data, JFIF standard 1.02
(null).DQ15AX: JPEG image data, JFIF standard 1.02
(null).EF7GBX: JPEG image data, JFIF standard 1.02
(null).GBW3AX: JPEG image data, JFIF standard 1.01
(null).GDOUAX: JPEG image data, JFIF standard 1.02
(null).GEGSAX: JPEG image data, JFIF standard 1.02
(null).GM3SBX: JPEG image data, JFIF standard 1.02
(null).H044AX: JPEG image data, JFIF standard 1.02
(null).HFBQBX: JPEG image data, JFIF standard 1.02
(null).HSRYBX: JPEG image data, JFIF standard 1.02
(null).IAJLBX: JPEG image data, JFIF standard 1.02
(null).J4Z6AX: JPEG image data, JFIF standard 1.02
(null).JCFOBX: JPEG image data, JFIF standard 1.02
(null).KW4NBX: JPEG image data, JFIF standard 1.02
(null).N6CFBX: JPEG image data, JFIF standard 1.01
(null).NO2IBX: JPEG image data, JFIF standard 1.01
(null).NV6RBX: JPEG image data, JFIF standard 1.02
(null).P6HXBX: JPEG image data, JFIF standard 1.02
(null).PKDWBX: JPEG image data, JFIF standard 1.02
(null).QZ1IBX: JPEG image data, JFIF standard 1.02
(null).RAMMBX: JPEG image data, JFIF standard 1.01
(null).UO1OBX: JPEG image data, JFIF standard 1.02
Something is obviously not cleaning up after itself and therefore wasting storage space and inodes. Please fix? :)
[update] ran the files above through file(1) and updated the list. They're all images, and they're all podcast-related, so I'm guessing this is a bug in gPodder.
[update2] so there's indication that this doesn't have to do with gPodder, but rather with the media app. Can we please have more confirmations?
| | 4 | No.4 Revision |
What Bug: Media player creates the files named (null).* in nemo user home dir?dir
Why are there There constantly coming files named (null).something popping up in the nemo user home directory?
e.g.directory, and it seems the media player is the culprit. This files can look like these:
[nemo@localhost ~]$ ls -1 \(null\).* | xargs file
(null).04ZSAX: JPEG image data, JFIF standard 1.02
(null).0LKDBX: JPEG image data, JFIF standard 1.02
(null).0W4OBX: JPEG image data, JFIF standard 1.02
(null).36YABX: JPEG image data, JFIF standard 1.02
(null).492WBX: JPEG image data, JFIF standard 1.02
(null).4I9YAX: JPEG image data, JFIF standard 1.01
(null).7AFTBX: JPEG image data, JFIF standard 1.02
(null).9KVHBX: JPEG image data, JFIF standard 1.01
(null).A0GRAX: JPEG image data, JFIF standard 1.02
(null).C7WRBX: JPEG image data, JFIF standard 1.02
(null).DQ15AX: JPEG image data, JFIF standard 1.02
(null).EF7GBX: JPEG image data, JFIF standard 1.02
(null).GBW3AX: JPEG image data, JFIF standard 1.01
(null).GDOUAX: JPEG image data, JFIF standard 1.02
(null).GEGSAX: JPEG image data, JFIF standard 1.02
(null).GM3SBX: JPEG image data, JFIF standard 1.02
(null).H044AX: JPEG image data, JFIF standard 1.02
(null).HFBQBX: JPEG image data, JFIF standard 1.02
(null).HSRYBX: JPEG image data, JFIF standard 1.02
(null).IAJLBX: JPEG image data, JFIF standard 1.02
(null).J4Z6AX: JPEG image data, JFIF standard 1.02
(null).JCFOBX: JPEG image data, JFIF standard 1.02
(null).KW4NBX: JPEG image data, JFIF standard 1.02
(null).N6CFBX: JPEG image data, JFIF standard 1.01
(null).NO2IBX: JPEG image data, JFIF standard 1.01
(null).NV6RBX: JPEG image data, JFIF standard 1.02
(null).P6HXBX: JPEG image data, JFIF standard 1.02
(null).PKDWBX: JPEG image data, JFIF standard 1.02
(null).QZ1IBX: JPEG image data, JFIF standard 1.02
(null).RAMMBX: JPEG image data, JFIF standard 1.01
(null).UO1OBX: JPEG image data, JFIF standard 1.02
Something There's a bug here; something is obviously not cleaning up after itself and therefore wasting storage space and inodes. Please fix? :)
[update][update3] ran the files above through file(1) and updated the list. They're all images, and they're all podcast-related, so I'm guessing The first theory was this is a bug in gPodder.
[update2] so there's indication that this doesn't have has to do with gPodder, but rather with gPodder. This has been disconfirmed, and now it looks like the media app. app is the culprit. Can we please have more confirmations?
| | 5 | retagged |
Bug: Media player creates files named (null).* in nemo user home dir
There constantly coming files named (null).something in the nemo user home directory, and it seems the media player is the culprit. This files can look like these:
[nemo@localhost ~]$ ls -1 \(null\).* | xargs file
(null).04ZSAX: JPEG image data, JFIF standard 1.02
(null).0LKDBX: JPEG image data, JFIF standard 1.02
(null).0W4OBX: JPEG image data, JFIF standard 1.02
(null).36YABX: JPEG image data, JFIF standard 1.02
(null).492WBX: JPEG image data, JFIF standard 1.02
(null).4I9YAX: JPEG image data, JFIF standard 1.01
(null).7AFTBX: JPEG image data, JFIF standard 1.02
(null).9KVHBX: JPEG image data, JFIF standard 1.01
(null).A0GRAX: JPEG image data, JFIF standard 1.02
(null).C7WRBX: JPEG image data, JFIF standard 1.02
(null).DQ15AX: JPEG image data, JFIF standard 1.02
(null).EF7GBX: JPEG image data, JFIF standard 1.02
(null).GBW3AX: JPEG image data, JFIF standard 1.01
(null).GDOUAX: JPEG image data, JFIF standard 1.02
(null).GEGSAX: JPEG image data, JFIF standard 1.02
(null).GM3SBX: JPEG image data, JFIF standard 1.02
(null).H044AX: JPEG image data, JFIF standard 1.02
(null).HFBQBX: JPEG image data, JFIF standard 1.02
(null).HSRYBX: JPEG image data, JFIF standard 1.02
(null).IAJLBX: JPEG image data, JFIF standard 1.02
(null).J4Z6AX: JPEG image data, JFIF standard 1.02
(null).JCFOBX: JPEG image data, JFIF standard 1.02
(null).KW4NBX: JPEG image data, JFIF standard 1.02
(null).N6CFBX: JPEG image data, JFIF standard 1.01
(null).NO2IBX: JPEG image data, JFIF standard 1.01
(null).NV6RBX: JPEG image data, JFIF standard 1.02
(null).P6HXBX: JPEG image data, JFIF standard 1.02
(null).PKDWBX: JPEG image data, JFIF standard 1.02
(null).QZ1IBX: JPEG image data, JFIF standard 1.02
(null).RAMMBX: JPEG image data, JFIF standard 1.01
(null).UO1OBX: JPEG image data, JFIF standard 1.02
There's a bug here; something is not cleaning up after itself and therefore wasting storage space and inodes. Please fix? :)
[update3] The first theory was this has to do with gPodder. This has been disconfirmed, and now it looks like the media app is the culprit. Can we please have more confirmations?