The last window does not disappear

[iCrwx]

I used the automatic installer on a newly installed Arch Linux operating system, when I start qtile (wayland) it doesn't start so I start qtile but things don't disappear, the display manager It is still visible, but very bugged with the bar and when I open anything like a terminal and close it, it closes but does not disappear, I will show a couple of photos so you can see how it looks

[Darkkal44]

Great to hear that the installer works, Actually this is not supposed to work in qtile Wayland, Wayland doesn't support a ton of stuff like rofi, so never expect it to work with a Wayland environment. Now the issue you are facing is most probably because of picom, and in order to fix this, try restarting the system, and wait for atleast 5mins after you put in your passwd and enters the Qtile wm.. this should most probably fix the issue on its own. Now if you wonder why this is happening, it's because, some parts of the rice is being themed bt pywal, and for the first launch pywal takes some time to read colors from the wallpaper and you just have to give it some time. From the next time you launch/restart your system/qtile you will get it done within 20 seconds or so. Lemme know if a re-start and a bit of patience does the job.

[iCrwx]

Great to hear that the installer works, Actually this is not supposed to work in qtile Wayland, Wayland doesn't support a ton of stuff like rofi, so never expect it to work with a Wayland environment. Now the issue you are facing is most probably because of picom, and in order to fix this, try restarting the system, and wait for atleast 5mins after you put in your passwd and enters the Qtile wm.. this should most probably fix the issue on its own. Now if you wonder why this is happening, it's because, some parts of the rice is being themed bt pywal, and for the first launch pywal takes some time to read colors from the wallpaper and you just have to give it some time. From the next time you launch/restart your system/qtile you will get it done within 20 seconds or so. Lemme know if a re-start and a bit of patience does the job.

I tried what you told me and it didn't work for me, it keeps coming out as before

[chadcat7]

1. picom is not for wayland @Darkkal44!
2. Most probably your system is not compatible with wayland @iCrwx

[Darkkal44]

1. picom is not for wayland @Darkkal44!

   2. Most probably your system is not compatible with wayland @iCrwx

Indeed it's not, and I have said it to him that Wayland is not compatible with this rice..

[Darkkal44]

@iCrwx oh, that's unfortunate, try this tho. Do the same thing again, wait for a bit and when the mouse cursor appears, click windows (command) + T, this will bring up the theme menu, select Sakura and then patiently wait for 2mins so that the script configures everything as it's for the first time, and now restart the system and wait sometime to see if it works.

[Darkkal44]

I FEEL LIKE YOU JUST HAVE TO WAIT A BIT MORE IN THIS SCREEN. that's how it's supposed to work, anyways, If this is not working then try the method I have suggested just before this.

[iCrwx]

@Darkkal44 @chadcat7 Sorry for being such a problem but none of the things you told me worked for me

[chadcat7]

@Darkkal44 @chadcat7 Sorry for being such a problem but none of the things you told me worked for me

Try x11, does it work there? Then we'll see what the issue is on Wayland

[Darkkal44]

@Darkkal44 @chadcat7 Sorry for being such a problem but none of the things you told me worked for me

It's fine, you told me that you're able to launch terminal right? Can you share the qtile log (last few lines) located at ~/.local/share/qtile/qtile.log

[Darkkal44]

And if you can, then contact me through discord @darkkal44

[iCrwx]

@Darkkal44 @chadcat7 Sorry for being such a problem but none of the things you told me worked for me

It's fine, you told me that you're able to launch terminal right? Can you share the qtile log (last few lines) located at ~/.local/share/qtile/qtile.log

FileNotFoundError: [Errno 2] No such file or directory: '~/.config/qtile/autostart_once.sh'2023-86-30 17:35:07,093 WARNING Libqtile Lifecycle.py:_atexit():L37 Qtile will now terminate2023-06-30 17:36:54,501 WARNING Libqtile lifecycle.py:_atexit():L37 Qtile will now terminate2823-86-30 17:50:02,731 ERROR Libqtile core.py:init_():L103 not starting; existing window manager L630

[ky3ow]

changing

@hook.subscribe.startup_once
def autostart_once():
    subprocess.run('~/.config/qtile/autostart_once.sh')# path to my script, under my user directory
    subprocess.call([home])

to

@hook.subscribe.startup_once
def autostart_once():
    home = os.path.expanduser('~/.config/qtile/autostart_once.sh')# path to my script, under my user directory
    subprocess.call([home])

worked for me "windows not disappearing" was caused by wallpaper absence as it seems

[Darkkal44]

changing

@hook.subscribe.startup_once
def autostart_once():
    subprocess.run('~/.config/qtile/autostart_once.sh')# path to my script, under my user directory
    subprocess.call([home])

to

@hook.subscribe.startup_once
def autostart_once():
    home = os.path.expanduser('~/.config/qtile/autostart_once.sh')# path to my script, under my user directory
    subprocess.call([home])

worked for me "windows not disappearing" was caused by wallpaper absence as it seems

Thanks a lot to you for coming up with a fix, so much appreciated tbh. I have been busy lately and havnt been able to troubleshoot this..

[Darkkal44]

And if I'm not mistaken, every wallpaper seems to be in there and it's provided in the script correctly. And I think this is more likely to be an issue with qtile figuring out where exactly the autostart file is located.. the logs shared by @iCrwx shows the same error...

[ky3ow]

And if I'm not mistaken, every wallpaper seems to be in there and it's provided in the script correctly. And I think this is more likely to be an issue with qtile figuring out where exactly the autostart file is located.. the logs shared by @iCrwx shows the same error...

I don't really know python but from what i've read, it treats ~ as literal tilde, and to make tilde into home you need to expand it with os.path.expanduser However in qtile widgets like Image you don't need to do it because its done under the hood

# From source code
class Image(base._Widget, base.MarginMixin):
    #bunch of stuff
    def _update_image(self):
        self.img = None

        if not self.filename:
            logger.warning("Image filename not set!")
            return

        self.filename = os.path.expanduser(self.filename)
    #bunch of stuff

[Darkkal44]

And if I'm not mistaken, every wallpaper seems to be in there and it's provided in the script correctly. And I think this is more likely to be an issue with qtile figuring out where exactly the autostart file is located.. the logs shared by @iCrwx shows the same error...

I don't really know python but from what i've read, it treats ~ as literal tilde, and to make tilde into home you need to expand it with os.path.expanduser However in qtile widgets like Image you don't need to do it because its done under the hood

# From source code
class Image(base._Widget, base.MarginMixin):
    #bunch of stuff
    def _update_image(self):
        self.img = None

        if not self.filename:
            logger.warning("Image filename not set!")
            return

        self.filename = os.path.expanduser(self.filename)
    #bunch of stuff

Oh okay, thanks for this information, I too am new to python and ricing in general tbh, and it's wierd how some part of the config works.. now it makes sense why it's showing errors for some people, thanks a lot for your guidance mate.