Created attachment 1235583 [details]
Description of problem:
By default if I am using xfce 4, the notification comes out in top right of the screen, regardless of what's behind. So if volume is in the same position, it makes hard to adjust volume control
Version-Release number of selected component (if applicable):
Fedora 25 XFCE
Steps to Reproduce:
1. Install Fedora XFCE and log in
2. Adjust volume from the volume icon
Volume adjust area are mostly covered by notification
Notify don't cover the volume control
See the attached ogv video if the steps is not clear enough for you.
I remember some newer version of Fedora 24 XFCE also have this issue.
And currently the workaround is simple, but not user-friendly enough, either
run xfce4-notifyd-config and change the Default Position to somewhere else, or
move the volume control from the default position to somewhere else.
But I hope there is a much user-friendly default settings for users.
Well, I am not sure if other locations are too much better... each has tradeoffs.
This might be a good discussion for the fedora-xfce list. Would you be willing to bring it up there? Or if not, I can do so...
Fine, I just send it to the list
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Is this still an issue or should we close this bug?
What I understood from the last message was that this was worked around.
xfce4-notifyd-0.3.5-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ec2e2a24c5
xfce4-notifyd-0.3.5-1.fc25 has been pushed to the Fedora 25 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-2017-ec2e2a24c5
xfce4-notifyd-0.3.5-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.