You are not logged in.
Hello to all. I have the problem specified in the title. The animations are too fast. For example, notifications last for 5 seconds, but disappear after 2-3 seconds. It all seems speeded up. Shortcuts to songs (back and forth) are also speeded up. For example, spotify receives a double press of the shortcut, that is, if I press once it goes forward (or backward) by two songs. How can I solve it? Thank you all
PS: Arch is on a desktop pc with ryzen 5 3600 and amd 5700. Can it be the fault of something of the gpu?
Offline
... Which environment? Is this actually Arch?
Last edited by V1del (2020-01-09 10:58:28)
Offline
... Which environment? Is this actually Arch?
I'm using kde plasma 5.17.5
Offline
What is "spotify"? The webpage? Does this all actually concern browser items?
Offline
What is "spotify"? The webpage? Does this all actually concern browser items?
sorry for my absence. With spotify I mean the application. On the spotify web player I can only put play and pause. On my laptop I don't have this problem and I have Arch installed on both
Last edited by Teddo (2020-04-12 13:38:28)
Offline
This one https://aur.archlinux.org/packages/spotify/ ?
The notification delay is not an animation, how long does this stay up:
notify-send -t 10000 test
Offline
This one https://aur.archlinux.org/packages/spotify/ ?
The notification delay is not an animation, how long does this stay up:
notify-send -t 10000 test
I timed with the smartphone and the result is 3.80 seconds
Offline
Bug in the plasma notification daemon?
sleep 10; ping
notify-send -t 20000 test # to see whether it scales
Offline
Bug in the plasma notification daemon?
sleep 10; ping notify-send -t 20000 test # to see whether it scales
What do I have to do exactly?
Offline
Run those and measure the time with your phone.
The insteresting part about the 20s notification is whether it lasts 7.6 seconds or something entirely different.
Offline
Run those and measure the time with your phone.
The insteresting part about the 20s notification is whether it lasts 7.6 seconds or something entirely different.
Sleep lasts 10 seconds while the notification is shown fot 7.33 seconds
Last edited by Teddo (2020-04-12 19:04:38)
Offline
seth wrote:Run those and measure the time with your phone.
The insteresting part about the 20s notification is whether it lasts 7.6 seconds or something entirely different.Sleep lasts 10 seconds while the notification is shown fot 7.33 seconds
Up
Offline
Don't do this.
https://wiki.archlinux.org/index.php/Co … ct#Bumping
The system doesn't run too fast, but there seems a bug in the plasma notification daemon, perhaps it indeed falsely takes some animation speed parameter (of the compositor) into account.
Did you check that?
You can also try to deactivate it in "kcmshell5 kded" and see how eg. dunst behaves.
https://www.archlinux.org/packages/comm … _64/dunst/
Offline
Don't do this.
https://wiki.archlinux.org/index.php/Co … ct#BumpingThe system doesn't run too fast, but there seems a bug in the plasma notification daemon, perhaps it indeed falsely takes some animation speed parameter (of the compositor) into account.
Did you check that?You can also try to deactivate it in "kcmshell5 kded" and see how eg. dunst behaves.
https://www.archlinux.org/packages/comm … _64/dunst/
Sorry, I don't kwon that. .
In kcmshell5 kded there isn't a notification daemon. Also I have the same configuration on my laptop and I don't have this problem. Could it be the gpu driver? I have a rx5700
Offline
If this was related to the compositor effects (you can try to disable the compositor using Alt+SHIFT+F12) you'd not see a linear scale.
The compositor animations would discard 10-3.8 = 6.2 seconds from the notification, so a 20 sec notification should stay for 15.8 seconds, not 7.33
In kcmshell5 kded there isn't a notification daemon.
Look harder.
plasma-workspace provides /usr/lib/qt/plugins/kf5/kded/desktopnotifier.so and the notification-daemon dependency.
Offline
If this was related to the compositor effects (you can try to disable the compositor using Alt+SHIFT+F12) you'd not see a linear scale.
The compositor animations would discard 10-3.8 = 6.2 seconds from the notification, so a 20 sec notification should stay for 15.8 seconds, not 7.33In kcmshell5 kded there isn't a notification daemon.
Look harder.
plasma-workspace provides /usr/lib/qt/plugins/kf5/kded/desktopnotifier.so and the notification-daemon dependency.
With the compositor disabled a notification of 20 seconds lasts 7.30 seconds.
So I reinstalled dunst. I ran dunst and kill the other notification daemon (plasma), and then I ran dunstify -t 10000 "test" and the new notification lasts 10 seconds
Last edited by Teddo (2020-04-19 15:41:45)
Offline
Yeah, so it's for pretty much sure a bug in the KDE notification daemon.
Can you impact the time w/ t he animation speed setting? (Again: there's no technical relation, but it might accidentally incorportate that value)
Offline
Yeah, so it's for pretty much sure a bug in the KDE notification daemon.
Can you impact the time w/ t he animation speed setting? (Again: there's no technical relation, but it might accidentally incorportate that value)
I tried to modify the speed's animations but there isn't changes. But if it is a bug in the daemon, why doesn't my laptop have the problem?
Last edited by Teddo (2020-04-21 10:45:12)
Offline
Because it's a bug - god knows what triggers it.
Create a new user account, does it happen for that user as well?
Offline
I can't reproduce this either. Maybe a more general clock/timer issue. Are you able to reproduce this with something completely trivial like
sleep 10
? What are your outputs for
dmesg | grep -iE 'rtc|hpet|tsc'
timedatectl
are your microcode updates properly applied/is your UEFI up to date?
Ah rats, didn't read the entire thread. but microcode is something you should check regardless
Last edited by V1del (2020-04-21 12:07:42)
Offline
Offline
so what can I do? Should I report this?
Offline
Did you test creating a new user? It would be better at least try to find an approximation to the cause first.
Offline
Did you test creating a new user? It would be better at least try to find an approximation to the cause first.
I have reinstalled arch few days ago
Offline