Building fsearch and Kazam: package confusion

Hello,
I’ve been trying to install fsearch and Kazam, and apparently they are not supported by pacman. For fsearch, the build instructions page says that it needs the following packages to build it:

git 
build-essential (*)
automake  
autopoint  
autoconf  
libtool  
pkg-config (or pkgconfig )
intltool  
autoconf-archive 
 
libpcre3-dev  (*)
libglib2.0-dev  (*)
libgtk-3-dev  (*)
libxml2-utils (*)
 
glib2-devel  (*)
gtk3-devel (*)

In Manjaro, I have problems with the ones having “(*)” in front of them. I’m a beginner and it’s unclear and confusing to me where those packages are and how to install them.

Also, when trying to build Kazam, I’d get the following errors:

/usr/bin/kazam:32: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
WARNING Kazam - Running from local directory, AppIndicator icons could be missing.
WARNING Kazam - Failed to correctly detect operating system.
Traceback (most recent call last):
  File "/usr/bin/kazam", line 146, in <module>
    from kazam.app import KazamApp
  File "../kazam/app.py", line 35, in <module>
    from kazam.backend.prefs import *
  File "../kazam/backend/prefs.py", line 478, in <module>
    prefs = Prefs()
  File "../kazam/backend/prefs.py", line 119, in __init__
    self.config = KazamConfig()
  File "../kazam/backend/config.py", line 76, in __init__
    ConfigParser.__init__(self, self.DEFAULTS[0]['keys'])
  File "/usr/lib/python3.8/configparser.py", line 639, in __init__
    self._read_defaults(defaults)
  File "/usr/lib/python3.8/configparser.py", line 1219, in _read_defaults
    self.read_dict({self.default_section: defaults})
  File "/usr/lib/python3.8/configparser.py", line 754, in read_dict
    self.set(section, key, value)
  File "../kazam/backend/config.py", line 126, in set
    self.add_section(section)
  File "/usr/lib/python3.8/configparser.py", line 1208, in add_section
    super().add_section(section)
  File "/usr/lib/python3.8/configparser.py", line 656, in add_section
    raise ValueError('Invalid section name: %r' % section)
ValueError: Invalid section name: 'DEFAULT'

Looks like there’s a problem with Gtk?
I’d appreciate your help.

Info about my system:

System:
  Kernel: 5.8.16-2-MANJARO x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=e7163391-d960-41ec-b9b2-63ffdbfd518d rw quiet 
  cryptdevice=UUID=d9153841-42fb-46e0-9b03-2ede24fa9ae9:luks-d9153841-42fb-46e0-9b03-2ede24fa9ae9 
  root=/dev/mapper/luks-d9153841-42fb-46e0-9b03-2ede24fa9ae9 apparmor=1 
  security=apparmor 
  resume=/dev/mapper/luks-14281edd-92f6-482c-b728-97bfe1826474 
  udev.log_priority=3 
  Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4 
  dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: ASUSTeK product: X556UQK v: 1.0 serial: <filter> 
  Mobo: ASUSTeK model: X556UQK v: 1.0 serial: <filter> 
  UEFI: American Megatrends v: X556UQK.315 date: 01/24/2019 
Battery:
  ID-1: BAT0 charge: 17.4 Wh condition: 17.4/38.0 Wh (46%) volts: 7.6/7.6 
  model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Not charging 
  cycles: 439 
CPU:
  Topology: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP 
  arch: Amber Lake family: 6 model-id: 8E (142) stepping: 9 microcode: D6 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 21607 
  Speed: 500 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 500 2: 500 3: 500 
  4: 500 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel HD Graphics 620 vendor: ASUSTeK driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:5916 
  Device-2: NVIDIA GM108M [GeForce 940MX] vendor: ASUSTeK driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:134d 
  Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo 
  bus ID: 1-6:3 chip ID: 13d3:5a01 serial: <filter> 
  Display: x11 server: X.Org 1.20.9 driver: intel,nouveau 
  unloaded: modesetting alternate: fbdev,nv,vesa display ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
  s-diag: 582mm (22.9") 
  Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 143 size: 340x190mm (13.4x7.5") 
  diag: 389mm (15.3") 
  OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.1.8 
  direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus ID: 00:1f.3 
  chip ID: 8086:9d71 
  Sound Server: ALSA v: k5.8.16-2-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: d000 bus ID: 02:00.0 
  chip ID: 10ec:8168 
  IF: enp2s0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter 
  vendor: AzureWave driver: ath10k_pci v: kernel port: d000 bus ID: 03:00.0 
  chip ID: 168c:0042 
  IF: wlp3s0 state: up mac: <filter> 
  IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter> 
  IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter> 
Drives:
  Local Storage: total: 931.51 GiB used: 62.31 GiB (6.7%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB 
  block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: SDM1 scheme: GPT 
Partition:
  ID-1: / raw size: 918.47 GiB size: 903.06 GiB (98.32%) 
  used: 62.31 GiB (6.9%) fs: ext4 dev: /dev/dm-0 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 12.74 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/dm-1 
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 2600 
Info:
  Processes: 215 Uptime: 1h 54m Memory: 11.58 GiB used: 2.01 GiB (17.3%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1130 lib: 340 
  flatpak: 0 Shell: Bash v: 5.0.18 running in: xfce4-terminal inxi: 3.1.05

Hello welcome to Manjaro

Those build instructions are for Debian based systems. (eg build-essential is specific to those OSes)

Both these packages are available from AUR. Enable AUR Support in Pamac Preferences.

https://wiki.manjaro.org/index.php/Pamac#Installing_Software

2 Likes

Thank you, @usul_of_arakis.
I knew about AUR support in Manjaro, but there was a warning message somewhere that said enabling support for AUR has some security risks and should be dealt with by Linux pros, so I didn’t enable it.

1 Like

You’re welcome @Sepp.

Yes there are risks using the AUR and there is a link to the Manjaro Wiki page explaining this in the article I linked to above. if you didn’t read it, it is here.

One of the main issues to remember is that

" No support will be provided by the Manjaro team for any issues that may arise relating to software installations from the AUR. When Manjaro is updated, AUR packages might stop working. This is not a Manjaro issue

[EDIT] I should add that this does not mean you will not get help in the Manjaro Forum, there are many people here who are willing to to do so. It just means that the Manjaro Devs are not responsible if an update to Manjaro stops an AUR package from working.

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.