Some apps is not closed or killed 100% #27
Comments
|
Hi there! I know what you mean, since I've experienced a similar bug before. The problem is that some programs will unmap their window(s) but not destroying them immediately, leaving empty window(s) in the workspace (as seen in the screenshot you provided). Are you running the latest build of this wm? I'm asking because I've fixed this issue ~2 days ago. If you're already running the latest build but still having this problem, please let me know and I'll test it with Just tested it on my machine with |
|
Umm.. it seems to be affected on another programs. I mean, if you opened some link from terminal (in this case, i'm using urxvt) you'll get two browsers run like mirror display. Check it out my video below. |
|
I've successfully reproduced this bug with firefox. I'll see if I could fix it! |
This commit fixes issue #27 We should check if the window is already in Client::mapper_, not in the workspace.
|
The patch 78aac74 is now in master. Tested it with firefox and the problem no longer exists. |
|
Confirmed, it's fixed! |
|
Yay! If you've found any other bug, please let me know! 😄 |
|
Sure! Thanks, pal! I really love you window manager 😂 |
Hi, again.
I hope you're not bored with me.
In this case, some applications is not
closedorkilled100%. I mean, when i usingtelegram-desktopthen i kill the app it's looks like the app is not closed (running in background). I don't know how to describe this issue, but see the screenshot below.Thanks, Marco.
The text was updated successfully, but these errors were encountered: