RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Automount do not mount usb stick in case to other is occupied by multiseat device (Plugable UD-160-M in my case)

Version-Release number of selected component (if applicable):
systemd-207-2.el7.x86_64
kernel-3.10.0-26.el7.x86_64
gnome-shell-3.8.4-5.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. have session #1 running on PC
2. attache multiseat device and login in to a session #2
3. attache usb disk to PC (session #1)

Actual results:
lsusb can list the attached device but nothing mounted

Expected results:
disk should mount to #1

Additional info:
attaching dist to session #2 works as expected

any progress?

(In reply to Harald Hoyer from comment #5)
> any progress?

I was not able to reproduce on freshly installed Client and Server. So most probably there was some miss configuration in my Workstation.

So we might close as not a bug.