[BUG]

[smithyyang]

Describe the bug

I don't know what happened ,I just opened rare,then a window appeared, asking me to report this issue on github. Some details are as follows:

Traceback (most recent call last): File "/usr/lib/python3.14/site-packages/rare/utils/qt_requests.py", line 139, in __on_finished handler(data) ~~~~~~~^^^^^^ File "/usr/lib/python3.14/site-packages/rare/components/tabs/store/widgets/image.py", line 115, in __on_image_ready self.setPixmap(cover) ~~~~~~~~~~~~~~^^^^^^^ File "/usr/lib/python3.14/site-packages/rare/widgets/image_widget.py", line 63, in setPixmap self.update() ~~~~~~~~~~~^^ RuntimeError: Internal C++ object (StoreItemWidget) already deleted.

It is the first time I meet issue like this ,so I don't know what information should I provide.
Here is some information may help you:
OS:archlinux
kernel:Linux 6.19.8-zen1-1-zen
cpu: 13th Gen Intel(R) Core(TM) i7-13700H (20) @ 5.00 GHz
gpu:NVIDIA GeForce RTX 4060 and Intel Iris Xe Graphics
brand of pc: ASUS
compositor: hyprland

If there is any information you need ,please comment and I will provide

By the way ,what i use is the rare from yay

Steps to Reproduce

I don't know ,I just opened it

Expected behavior

Have no idea

Screenshots

No response

Operating system

Linux

Version

6.19.8-zen1-1-zen

Installation method

Package manager

Python version

No response

Error message

Traceback (most recent call last):
  File "/usr/lib/python3.14/site-packages/rare/utils/qt_requests.py", line 139, in __on_finished
    handler(data)
    ~~~~~~~^^^^^^
  File "/usr/lib/python3.14/site-packages/rare/components/tabs/store/widgets/image.py", line 115, in __on_image_ready
    self.setPixmap(cover)
    ~~~~~~~~~~~~~~^^^^^^^
  File "/usr/lib/python3.14/site-packages/rare/widgets/image_widget.py", line 63, in setPixmap
    self.update()
    ~~~~~~~~~~~^^
RuntimeError: Internal C++ object (StoreItemWidget) already deleted.

Additional context

No response

[loathingKernel]

Thank you for the report. I don't think this is just when you opened it, this is from the "Store" page which doesn't get loaded until you switch to it. That being said, I am aware of the issue and I have been trying to resolve it for some time. It is safe to ignore the issue by pressing the Ignore button.

If you don't mind, I would suggest trying again with the AppImage from the latest pre-release, I have done a few things to make it less likely to happen since the last proper release.