rocksdanister / lively

Free and open-source software that allows users to set animated desktop wallpapers and screensavers powered by WinUI 3.
https://rocksdanister.com/lively
GNU General Public License v3.0
14.38k stars 1.03k forks source link

Wallpaper fails when dwm crash #2283

Closed Ishan-Sinha-5006 closed 5 days ago

Ishan-Sinha-5006 commented 3 weeks ago

Bug After applying a wallpaper the wallpaper doesn't apply. However while switching between the desktop and a different program the wallpaper applies for a second or two before disappearing.

How To Reproduce Please note these steps may not be accurate or correct as i myself aren't sure what i did to cause it, so think as this more as a timeline of events. Steps to reproduce the behavior: 1.Windows hanged after attempting closing a high memory consumption application. 2.Opened task manager using ctrl+ shift+ esc. However it didn't come up because there was lack of ram. I later confirmed this 3.Using ctrl+alt+delete to bring up security options page 4.while holding ctrl i pressed the power button to bring up the emergency restart page

  1. I closed the restart page and security options page
  2. Task manager finally loads
  3. I end the application which caused this mess.
  4. The wallpaper overlays on top of everything
  5. I exit the wallpaper thinking this is a glitch 10 I restart the wallpaper and it doesn't work

Expected behavior If you do encounter this glitch it should not apply the lively wallpaper on the desktop, will show the lively wallpaper while switching between tabs.

Video Sorry for the bad video. I had to record it with my phone and left hand without OIS

https://github.com/rocksdanister/lively/assets/172957227/2cdae68b-5ad6-4d7e-ac46-b589b2205988

Desktop (please complete the following information):

Log file (Important) 20240616_180159.txt

Ishan-Sinha-5006 commented 3 weeks ago

ps. if this either a common issue( even though i didn't find other posts about this nor was it mentioned in the common issues page) or it is specific to me please tell me how to fix this. I am thankful toward anyone who helps

rocksdanister commented 1 week ago

Do you have any other software that modify desktop or system? stardock fences etc.

Ishan-Sinha-5006 commented 1 week ago

no But i did figure out what was causing it restarting DWM causes this

rocksdanister commented 1 week ago

When does your dwm restart?

Ishan-Sinha-5006 commented 6 days ago

I restart dwm manually because of a memory leak in my graphics driver. it is an integrated driver which came pre installed

Ishan-Sinha-5006 commented 6 days ago

i cant update the driver as while a newer version of the driver from intell exists, the oem(hp) has not updated the graphics driver to the latest version.

rocksdanister commented 6 days ago

Usually generic Intel/Amd drivers should work without problem, atleast that's what I use.

Ishan-Sinha-5006 commented 5 days ago

To be fair this problem only started when I updated lively to the newset version.

Ishan-Sinha-5006 commented 5 days ago

Other factors I can think of that might cause this are: The high strain use of the device( most of the times during use it is at 7.8/8 gb ram as i use for gaming) The fact that the device is a laptop and thus less powerful which might be causing lively to get suspended after a dwm restart(probably not) The regular background itself is a scrolling background that cycles through multiple images so it might be that when I restart dwm I accidentally restart it at the exact moment it changes the background to a new image so that might break it.( This is very improbable as I have restarted dwm about 20 times for testing and I getting the timing on that is well not likely to say the least)

rocksdanister commented 5 days ago

Wallpaper program will crash if dwm crash, that is normal.. Lively only listens for explorer crash and restart wallpaper if its not too frequent.

At the moment I don't have plans to listen to dwm process crash since that means there is something critically wrong with the system like in this case faulty driver and it is better to fix the root of the issue.

Closing this as unrelated.