-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dunst does not update screen size when resolution changes #434
Comments
Can you run |
Ping @josswright |
Oh, sorry. I didn't see the reply. I'll upload the data later today when I'm connected to an external projector. |
Here's a dump, as requested. The steps were:
Tested, and the dunst notification appears 1024x768 pixels into my 1920x1080 internal monitor. |
I have the same issue. When disconnecting the external screen, thus reducing the overall geometry, the notification is still shown outside of the current screen boundaries [I'm on the current master branch]. I'm using notification-screen-follows-mouse, so it might be that the notification of pointer changing screen is never emitted? I manually invoke xrandr --auto when plugging/unplugging extra monitors. |
@wavexx What does |
For me:
|
@josswright Thanks for the answer. Could you also please paste the |
On Thu, Dec 21 2017, Benedikt Heine wrote:
@wavexx What does xrandr --version report? I can't reproduce it with my own system.
I'm on debian unstable.
$ xrandr --version
xrandr program version 1.5.0
Server reports RandR version 1.5
I'm not sure the output of ``systemctl status --user dunst.service``
matters here. If I kill dunst, it gets respawned correctly and the
notifications are shown correctly using the new geometry.
I tried again and narrowed the issue a bit:
- follow=mouse is set
- mouse is on external screen
- disconnect external screen
- generate notification -> not shown (likely offscreen)
- mouse the mouse
- generate notification -> correctly shown
The current screen is probably not updated until the pointer is moved.
Not sure this is the complete story, but since I'm a keyboard-heavy
user, it would explain why I would see it so often.
|
I also don't run dunst through a systemd service -- I just spawn it manually. (Arch Linux.) (Or, I should clarify, through my .xinitrc.) |
@josswright Interesting that you don't spawn dunst via dbus. But anyways, what's your setting of i3's @wavexx do you run also i3? If so, could you also tell me the value of |
@bebehei Just default: |
On Thu, Dec 21 2017, Benedikt Heine wrote:
@wavexx do you run also i3? If so, could you also tell me the value of
focus_follows_mouse?
follow=mouse is the dunst setting.
As a WM I'm using spectrwm (which does focus-follows-mouse anyway).
|
Oh, sorry, for dunst configuration I've got |
This issue is getting weirder to debug by every comment 😂 I've tested all four combinations already yesterday and nothing made me able to reproduce this. Well, I can only shoot into the dark and I'm guessing around. I'm not getting illuminated by the I've also created a PKGBUILD.gz, which builds this as a package directly from there. (You have to gunzip it first, github does not allow me to push it raw.) Thanks in advance. |
Still affected by this. When the screen configuration changes, dunst still uses the old screen. I'm pretty sure this happens due to:
I can easily "fix" dunst by moving the mouse to another window, thus triggering a focus change event. This does update the position of the notification instantly to the current screen. |
@wavexx Can you build tsipinakis@e97f226 and tell me if that fixes it? From a few tests I've tried I can't reproduce this locally. |
On Sat, Mar 23 2019, Nikos Tsipinakis wrote:
@wavexx Can you build ***@***.*** and tell me if that fixes it?
Ok, I've built it but testing is also going to take a while on my side.
This is annoying to reproduce :/
|
I am experiencing the same behavior when switching resolutions. Currently I kill and restart dunst but that doesn't seem favorable? What other steps can I take for this? |
@FatBoyXPC could you give a bit more info? Eg: your setup, desktop environment, distribution, Dunst version, your dunstrc. Does the issue go away when you move your mouse? Please provide as much info as possible to narrow down the problem. A reliable way to reproduce it would help a lot. |
I'm running arch with xmonad. Dunst 1.6.1. dunstrc:
The issue does not go away when I move the mouse. I have a usb c docking station with an external monitor that I use. When I am docked, I've got the laptop monitor turned off and the external monitor at 1920x1080. When I undock, the laptop resolution is 2560x1440. If I start dunst while docked, and I undock, dunst appears in the middle of my screen. When I re-dock, dunst goes back to the appropriate corner. If I start dunst while undocked, then dock, I never see the notification at all. If I re-dock, then the notification goes back to the appropriate corner. |
does this still happen in the latest versions of dunst? |
This isn't an issue for me since I've changed hardware and don't normally use different resolutions anymore. That said, this seems easy enough to test by forcing the resolution to change? |
Is changing resolution with xrandr enough to trigger it? You mentioned attaching an external monitor |
I use dunst on a laptop where I often present on an external screen. When I do so, I tend to reduce my internal monitor resolution to match the external. (My internal monitor goes from 1920x1080 to, for example, 1024x768).
On reducing the screen resolution, dunst seems to display notifications correctly. When, however, I retun to the larger screen size, dunst notifications now appear in the correct location for the smaller screen. (So 1024x768 pixels into my 1920x1080 screen.)
For reference, I'm running this under i3, and changing resolution using xrandr directly.
Installation info
Dunst - A customizable and lightweight notification-daemon 1.2.0 (2017-07-12)
Package
Arch Linux
The text was updated successfully, but these errors were encountered: