Hi, @Ben, thanks for replying to this message.
What you propose didnât sort it out. Iâm still not able to start it.
Iâm also using the same version as you:
> ulauncher --version
ulauncher 5.15.1
Hereâs the full output I get when executing ulauncher from the terminal:
output
⯠ulauncher
2023-02-20 00:31:30,457 | ERROR | ulauncher: except_hook() | Uncaught exception
Traceback (most recent call last):
File â/usr/bin/ulauncherâ, line 28, in
main()
File â/usr/lib/python3.10/site-packages/ulauncher/main.pyâ, line 136, in main
window = UlauncherWindow.get_instance()
File â/usr/lib/python3.10/site-packages/ulauncher/utils/decorator/singleton.pyâ, line19, in wrapper
instance = fn(*args, **kwargs)
File â/usr/lib/python3.10/site-packages/ulauncher/ui/windows/UlauncherWindow.pyâ, line 56, in get_instance
return cls()
File â/usr/lib/python3.10/site-packages/ulauncher/ui/windows/UlauncherWindow.pyâ, line 66, in new
new_object.finish_initializing(builder)
File â/usr/lib/python3.10/site-packages/ulauncher/ui/windows/UlauncherWindow.pyâ, line 99, in finish_initializing
self.init_theme()
File â/usr/lib/python3.10/site-packages/ulauncher/ui/windows/UlauncherWindow.pyâ, line 242, in init_theme
self._render_prefs_icon()
File â/usr/lib/python3.10/site-packages/ulauncher/ui/windows/UlauncherWindow.pyâ, line 393, in _render_prefs_icon
surface = Gdk.cairo_surface_create_from_pixbuf(prefs_pixbuf, scale_factor, self.get_window())
TypeError: Couldnât find foreign struct converter for âcairo.Surfaceâ
Iâm now also using krunner, and maybe this is an opportunity to start using a nice native Plasma APP instead of third party softwareâŚ
An update on this issue: I posted a message to the Archlinux User Repository, reporting the problem. One user suggested that my system was broken and that I should follow the instructions in this link.
If I understand correctly, this happens because Arch breaks AUR Python modules when we upgrade Python versions, and rebuilding Ulauncher should fix the problem. As I am using paru, I have run paru -S ulauncher --rebuild,
but the problem persists.
Iâm currently stuck. Although I have been using krunner and enjoying it, I would like to solve this problem, so any help would be appreciated.
As I often do out of curiosity, I just built the thing.
With the help of yay, because that is what I most often use. yay -S ulauncher
I selected to remove build dependencies, all dependencies where installed, then ulauncher was built - and the dependencies removed again.
ulauncher started and works flawlessly when started from terminal
Iâm not familiar with it or how to use it instead of my current whiskermenu (Xfce4).
Perhaps your system needs to be updated?
Mine definitely was/is.
(Manjaro stable Xfce4 in a virtual machine)
they might have a point
not broken, perhaps - just not up to date?
ps:
a possible path to a solution - after your system is brought up to date
sudo pacman -Rns ulauncher
then remove the paru build cache - I donât know where it resides, probably in ~/.cache
then initiate the build again
point is to make sure you are not re-using old files âŚ
Thanks for your reply @Nachlese.
My system is (always) up to date.
I cleaned paruâs cache, removed all files and packages associated to Ulauncher (sudo pacman -Rns ulauncher), and rebuilt it with paru -S ulauncher. The problem persists.
From the official Ulauncher website. The PKGBUILD file you indicated is exactly the same as that one.
It compiles without any error, but I get the errors I indicated before.
Why would it be - if it works (for me) right now?
As it does.
I seriously doubt that ⌠waiting ⌠would magically fix anything,
which should already work as it is.
Iâd be very surprised if âitâ would somehow automatically fix itself.
That âmaybeâ of yours is rather a âvery likely notâ - and pointing towards some issue with your current system configuration that should be addressed.
So I also out of curiosity decided to try to install ulauncher. I did use a fully up-to-date manjaro KDE using stable repository (in Virutalbox, my host system is also Manjaro KDE but I use the unstable repository and I wanted to try using a similar setup as yours). I cannot reproduce your problem, it installed successfully and works as intended. I donât know if it makes any difference, but I did not use paru, I used yay.
The address is the same address pamac and yay uses to clone a PKGBUILD before processing it.
This is a perfectly valid oneliner
git clone https://aur.archlinux.org/ulauncher.git
cd ulauncher
makepkg -is
Prior to running makepkg -is it is important to ensure your system is fully synced.
Another possible issue could be Manjaro branch - if you are - like most - you are using Manjaro stable - verify using this command
pacman-mirrors -G
Then it is likely a python library which has not yet reached Manjaro stable. Changing branch to Manjaro unstable - just a denomination - it is not unstable is simple.
sudo pacman-mirrors -aS unstable
Then run a full sync of your system packages
sudo pacman -Syyu
Then uninstall your version of ulauncher
sudo pacman -Rns ulauncher
Then rebuild using your AUR helper - I would lean towards using pamac
I just found a solution.
While trying to run Proton VPN, I got a somehow similar error, related to Cairo: undefined symbol: cairo_tee_surface_index.
So, suspecting that the problems were related to my Cairo installation, I did the following:
I removed python-cairo using pip:
pip uninstall pycairo
Found existing installation: pycairo 1.21.0
Uninstalling pycairo-1.21.0:
Would remove:
/home/ngomes/.local/lib/python3.10/site-packages/cairo/*
/home/ngomes/.local/lib/python3.10/site-packages/pycairo-1.21.0.dist-info/*
Proceed (Y/n)?
Successfully uninstalled pycairo-1.21.0
I tried to reinstall pycairo:
pip install pycairo
And here is the interesting part: another, more recent version of pycairo was already installed on my system!
Requirement already satisfied: pycairo in /usr/lib/python3.10/site-packages (1.23.0)
Soâalthough I donât know howâI had two different versions of python-cairo installed on my system, and the oldest one (located in ~/.local/lib) was the default, causing a conflict.
By simply removing the old version of python-cairo, as described in 1. above, I solved the problems and Ulauncher and Proton VPN now both work.
Thank you all (@Nachlese, @Ben, @ydar, and @linux-aarhus) for your attention to this issue. I have been using Manjaro since 2016, and one of the main reasons for not switching distros is the great community, always willing to help. Kudos, you guys are awesome!
Thereâs also an option to get this one in Chaotic:
2 aur/ulauncher 5.15.1-1 [+67 ~1.60] [Installed]
Application launcher for Linux
1 chaotic-aur/ulauncher 5.15.1-1 [0B 5.89MiB] [Installed]
Application launcher for Linux
