Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1665740 - abrt-applet creates "weird" directories in my home directory
Summary: abrt-applet creates "weird" directories in my home directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1666337 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-13 14:32 UTC by Kostya Vasilyev
Modified: 2019-01-16 14:39 UTC (History)
10 users (show)

Fixed In Version: abrt-2.11.1-3.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-16 02:19:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
The weird directory in Thunar (142.52 KB, image/png)
2019-01-13 14:32 UTC, Kostya Vasilyev 		no flags Details
View All

Description Kostya Vasilyev 2019-01-13 14:32:17 UTC 
Created attachment 1520275 [details]
The weird directory in Thunar

Description of problem:

abrt-applet creates "weird" directories in my home directory after (almost) each login.

Version-Release number of selected component (if applicable):

abrt-gui-2.11.1-2.fc29.x86_64

How reproducible:

Almost always - i.e. 75% on each login into XFCE

Steps to Reproduce:

1. abrt-gui recently updated to 2.11.1-2

    Upgrade  abrt-gui-2.11.1-2.fc29.x86_64                   @updates-testing
    Upgraded abrt-gui-2.11.0-1.fc29.x86_64                   @@System

2. After almost each login (XFCE), I see some new "weird" looking directories in my home directory.

In Thunar, they show as "0� (invalid encoding)"

In ls -l, they show as

drwxrwxr-x.  2 kman kman   4096 Jan 13 17:15 '0'$'\330'

The directory names do vary, but they're always weird names like this made of "invalid characters"

3. I used audit to track it down:

time->Sun Jan 13 17:15:22 2019
type=PROCTITLE msg=audit(1547388922.809:644): proctitle=616272742D6170706C6574002D2D676170706C69636174696F6E2D
73657276696365
type=PATH msg=audit(1547388922.809:644): item=1 name=30D8 inode=14041143 dev=103:01 mode=040775 ouid=1000 ogid
=1000 rdev=00:00 obj=unconfined_u:object_r:user_home_t:s0 nametype=CREATE cap_fp=0000000000000000 cap_fi=00000
00000000000 cap_fe=0 cap_fver=0
type=PATH msg=audit(1547388922.809:644): item=0 name="/home/kman" inode=13926401 dev=103:01 mode=040700 ouid=1
000 ogid=1000 rdev=00:00 obj=unconfined_u:object_r:user_home_dir_t:s0 nametype=PARENT cap_fp=0000000000000000 
cap_fi=0000000000000000 cap_fe=0 cap_fver=0
type=CWD msg=audit(1547388922.809:644): cwd="/home/kman"
type=SYSCALL msg=audit(1547388922.809:644): arch=c000003e syscall=83 success=yes exit=0 a0=55dd7eb29cf0 a1=1ff a2=ffffffffffffff80 a3=0 items=2 ppid=1693 pid=1823 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=4 comm="abrt-applet" exe="/usr/bin/abrt-applet" subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key="kman5"

Note the "name" in the audit - 30D8, believe this is binary

syscall=83 is mkdir

ausearch with "-i" - which is "show info as human readable" - gives:

type=PROCTITLE msg=audit(01/13/2019 17:15:22.809:644) : proctitle=abrt-applet --gapplication-service 
type=PATH msg=audit(01/13/2019 17:15:22.809:644) : item=1 name=0� inode=14041143 dev=103:01 mode=dir,775 ouid=kman ogid=kman rdev=00:00 obj=unconfined_u:object_r:user_home_t:s0 nametype=CREATE cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 
type=PATH msg=audit(01/13/2019 17:15:22.809:644) : item=0 name=/home/kman inode=13926401 dev=103:01 mode=dir,700 ouid=kman ogid=kman rdev=00:00 obj=unconfined_u:object_r:user_home_dir_t:s0 nametype=PARENT cap_fp=none cap_fi=none cap_fe=0 cap_fver=0 
type=CWD msg=audit(01/13/2019 17:15:22.809:644) : cwd=/home/kman 
type=SYSCALL msg=audit(01/13/2019 17:15:22.809:644) : arch=x86_64 syscall=mkdir success=yes exit=0 a0=0x55dd7eb29cf0 a1=0777 a2=0xffffffffffffff80 a3=0x0 items=2 ppid=1693 pid=1823 auid=kman uid=kman gid=kman euid=kman suid=kman fsuid=kman egid=kman sgid=kman fsgid=kman tty=(none) ses=4 comm=abrt-applet exe=/usr/bin/abrt-applet subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 key=kman5 

Note the "name=0�" above (same as it shows in Thunar)
Comment 1 Kostya Vasilyev 2019-01-13 14:34:23 UTC 
PS - filed as "high priority" because until I knew what it was, it totally looked like a file system corruption or similar...
Comment 2 Kostya Vasilyev 2019-01-13 15:02:13 UTC 
Looks like a duplicate of

https://bugzilla.redhat.com/show_bug.cgi?id=1665521

And already fixed:

https://github.com/abrt/abrt/commit/cf78b299371995cbd7607a536f4b1469c09b40cf

New packages with the fix please?

And maybe remove the "bad" version from @updates-testing for now?
Comment 3 Fedora Update System 2019-01-14 08:26:01 UTC 
abrt-2.11.1-3.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b5c308118f
Comment 4 Fedora Update System 2019-01-15 02:23:23 UTC 
abrt-2.11.1-3.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b5c308118f
Comment 5 Fedora Update System 2019-01-16 02:19:36 UTC 
abrt-2.11.1-3.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
Comment 6 Rex Dieter 2019-01-16 14:38:45 UTC 
*** Bug 1666337 has been marked as a duplicate of this bug. ***
Comment 7 Rex Dieter 2019-01-16 14:39:39 UTC 
*** Bug 1666734 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.