You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree to follow the Code of Conduct that this project adheres to.
I have searched the issues tracker for a bug report similar to mine, in vain
Ferdium Version
6.7.7
What Operating System are you using?
Ubuntu
Operating System Version
24.04 & 22.04
What arch are you using?
x64
Last Known Working Ferdium version
No response
Expected Behavior
WhatsApps loads after Ferdum starts, and you can use it normally.
Actual Behavior
After initial load (Starting OS, or opening Ferdium) just after Ferdium starts and load services, you can use WhatsApp just for a few seconds and then get stucked completely for about 5 minutes.
After that, you can use WhatsApp just like nothing happens
I have opened the Sys process monitor but I didn't see anything wrong. Sorry for my bad english.
Steps to reproduce
Open Ferdium with WhatsApp.
Use it about 20 seconds
Got Stucked
Wait
Magically it starts working again, no more stuckes till system restart (Or closing and starting ferdium again)
Debug link
No response
Screenshots
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Avoid duplicates
Ferdium Version
6.7.7
What Operating System are you using?
Ubuntu
Operating System Version
24.04 & 22.04
What arch are you using?
x64
Last Known Working Ferdium version
No response
Expected Behavior
WhatsApps loads after Ferdum starts, and you can use it normally.
Actual Behavior
After initial load (Starting OS, or opening Ferdium) just after Ferdium starts and load services, you can use WhatsApp just for a few seconds and then get stucked completely for about 5 minutes.
After that, you can use WhatsApp just like nothing happens
I have opened the Sys process monitor but I didn't see anything wrong. Sorry for my bad english.
Steps to reproduce
Debug link
No response
Screenshots
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: