abrt creates empty folders named with non-printable characters

asked 2019-01-13 07:07:24 -0500

dave997 gravatar image

Hi there,

I've just spent two hours trying to figure out a very strange and worrying behavior on my Fedora 29 machine.

A random, empty folder is created every time I start the system and after some researches it appears to be abrt causing the problem. I've had to use audit to track changes since it was impossible for me to get information otherwise (system logs etc). This is what I got with the last one which - fortunately enough - was named with a strange yet printable character. (The previous ones used non-printable ones and ausearch refused to show their entries).

dave997@localhost ~]$ sudo ausearch -k testingChangesOnHomeDavid | aureport -f -i | grep Д
8887. 13/01/2019 13:42:40 Д mkdir yes /usr/bin/abrt-applet dave997 6761
8889. 13/01/2019 13:42:40 /home/dave997/Д openat yes /usr/bin/baloo_file dave997 6763
8890. 13/01/2019 13:42:40 /home/dave997/Д getxattr no /usr/bin/baloo_file dave997 6764
8891. 13/01/2019 13:42:40 /home/dave997/Д getxattr no /usr/bin/baloo_file dave997 6765
8892. 13/01/2019 13:42:40 /home/dave997/Д getxattr no /usr/bin/baloo_file dave997 6766
18805. 13/01/2019 13:43:05 Д getxattr no /usr/bin/kdeinit5 dave997 16690
18806. 13/01/2019 13:43:05 Д getxattr no /usr/bin/kdeinit5 dave997 16691
18807. 13/01/2019 13:43:05 Д getxattr no /usr/bin/kdeinit5 dave997 16692
19178. 13/01/2019 13:43:05 /home/dave997/Д getxattr no /usr/bin/kdeinit5 dave997 17063
19179. 13/01/2019 13:43:05 /home/dave997/Д getxattr no /usr/bin/kdeinit5 dave997 17064
19180. 13/01/2019 13:43:05 /home/dave997/Д openat yes /usr/bin/kdeinit5 dave997 17065
19181. 13/01/2019 13:43:05 /home/dave997/Д openat yes /usr/bin/kdeinit5 dave997 17066
19420. 13/01/2019 13:43:07 /home/dave997/Д getxattr no /usr/bin/kdeinit5 dave997 17305
19421. 13/01/2019 13:43:07 /home/dave997/Д getxattr no /usr/bin/kdeinit5 dave997 17306
19422. 13/01/2019 13:43:07 /home/dave997/Д openat yes /usr/bin/kdeinit5 dave997 17307
19423. 13/01/2019 13:43:07 /home/dave997/Д openat yes /usr/bin/kdeinit5 dave997 17308
19445. 13/01/2019 13:43:10 /home/dave997/Д getxattr no /usr/bin/dolphin dave997 17330
19450. 13/01/2019 13:43:10 /home/dave997/Д getxattr no /usr/bin/dolphin dave997 17335
19451. 13/01/2019 13:43:10 /home/dave997/Д getxattr no /usr/bin/dolphin dave997 17336
19452. 13/01/2019 13:43:10 /home/dave997/Д getxattr no /usr/bin/dolphin dave997 17337
19453. 13/01/2019 13:43:10 /home/dave997/Д getxattr no /usr/bin/dolphin dave997 17338
19454. 13/01/2019 13:43:10 /home/dave997/Д openat yes /usr/bin/dolphin dave997 17339
19463. 13/01/2019 13:43:10 /home/dave997/Д getxattr no /usr/bin/kdeinit5 dave997 17348
19464. 13/01/2019 ...
(more)
edit retag flag offensive close merge delete

Comments

1

Please read my (@clnetbox) related answer here : Files and folders with name "� (invalid encoding)"; what does it mean and how to fix it? - the workaround solves the problem ... :)

clnetbox gravatar imageclnetbox ( 2019-01-13 09:53:50 -0500 )edit
1

Yep, that workaround seems to fix the problem indeed. All we have to do is to wait for abrt to be patched then. Thank you for your help!

dave997 gravatar imagedave997 ( 2019-01-13 09:59:48 -0500 )edit
1

You're welcome @dave997 ! I'm glad that it could help ... you may want to consider voting up the answer to "push it a little bit up to the top" so that other affected users can find it faster. Thanks. :)

clnetbox gravatar imageclnetbox ( 2019-01-13 10:15:52 -0500 )edit

Done. I was looking for a way to mark it as solution here but couldn't find any, sorry XD

dave997 gravatar imagedave997 ( 2019-01-13 17:45:20 -0500 )edit