"Manjaro Hello" does not start after Update

Today, my Manjaro notified me about an available update. I ran it, and now everything works well again, except for one thing: Manjaro-Hello. It doesn’t show upp after system start. When I start it by command line, I get error messages as follows:

$ manjaro-hello
Traceback (most recent call last):
  File "/usr/bin/manjaro-hello", line 456, in <module>
    hello = Hello()
  File "/usr/bin/manjaro-hello", line 120, in __init__
    Gtk.Window.__init__(self, title="Manjaro Hello", border_width=6)
  File "/usr/lib/python3.11/site-packages/gi/overrides/Gtk.py", line 519, in __init__
    raise RuntimeError(
RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you want to handle this case.

Of course, this is not a show stopper, but probably a low-priority thing to fix

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

1 Like

I am on Cinnamon Stable and “Manjaro Hello” (0.7.0-6) does not start after todays update. Rest of my system works well. I don´t need it to often, but it would be nice to have it working again.
The problem occurs identically on two of my manjaro machines after todays update.
Default browser on both machines is Firefox (Brave additionally installed).
Thanks for any suggestions.

Yep, it does not work anymore after the stable update from 11 August. Although i see different error

[teo@teo-lenovo-v15 ~]$ manjaro-hello 
DEBUG:root:_DATA_DIR is /usr/share/application-utility
DEBUG:root:_PREF_FILE is /usr/share/application-utility/preferences.json
DEBUG:root:self.file is {'desktop': '', 'main': '/usr/share/application-utility/default.json'}
INFO:root:json to merge : /usr/share/application-utility/default.json
DEBUG:root:json : /tmp/manjaro-hello-preferences.json
Error in Embled application: 'Database' object has no attribute 'enable_appstream'
Segmentation fault (core dumped)

This is most likely caused by a change in libpamac - which is utilized by Manjaro Application Utility which is a plugin to Manjaro Hello.

When i start it by command line, i get also a different message to @ueli, but it’s the same like @teo’s:

$ manjaro-hello
DEBUG:root:_DATA_DIR is /usr/share/application-utility
DEBUG:root:_PREF_FILE is /usr/share/application-utility/preferences.json
DEBUG:root:self.file is {'desktop': '', 'main': '/usr/share/application-utility/default.json'}
INFO:root:json to merge : /usr/share/application-utility/default.json
DEBUG:root:json : /tmp/manjaro-hello-preferences.json
Error in Embled application: 'Database' object has no attribute 'enable_appstream'
Speicherzugriffsfehler (Speicherabzug geschrieben)

Same message on both systems.

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

The error is rooted in changes in libpamac.

You can safely remove Manjaro Hello along with components.

Manjaro Hello is a helper application - not vital in any aspects - so reporting the issue at gitlab is the best course of action

EDIT: link to issue

Oh no. I was following a tutorial using Manjaro Hello to install extended input method support, and suddenly found Manjaro Hello failed to launch. I thought I accidentally broke my system :upside_down_face:

We’re actually using @Chrysostomus’ fork:

Issue is created:

1 Like

In the gitlab report it is stated “You just need to remove the conflicting line db.enable_appstream(), it’s no more needed.” Could somebody kindly explain how I should go about removing the conflicting line.

1 Like

Second that - from what I can see in the diff terminal output, it seems to be in 2 files? (maybe more?)
I don’t have coding knowledge, but I could find the file, open it as root, find the line, and edit/delete it. but I need to be sure what file/s to open and edit. So if someone could kindly point us nobs to the file/s to be edited, that would be great. Thanks


I have not found iso-apps-json in /usr/share/application-utility/

But not working…

You should not do anything. What’s mentioned in the issue are not instructions for users. Besides, it does not work.

In case this helps anyone, I have noticed that manjaro-hello only fails to launch (without any error message, from the KDE application menu) for the first user to login after the computer boots. If I logout and login as another user, manjaro-hello launches and works fine. This behavior is the same on multiple computers after the last stable update (8/11). Manjaro-hello will never launch for me when I’m logged in as the first user to login after the computer boots, even if I have logged out and logged back in; but it will launch for users who are not the first to login after the computer boots.

inxi --full --admin --filter --width                                                                                                ✔ 
  Kernel: 6.1.44-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=05da14d1-cb6a-4952-b124-3777857e9f62 rw quiet
  Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2 dm: SDDM
    Distro: Manjaro Linux base: Arch Linux
  Type: Desktop System: Gigabyte product: H97M-HD3 v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Gigabyte model: H97M-HD3 v: x.x serial: <superuser required>
    BIOS: American Megatrends v: F8 date: 09/18/2015
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
  Info: model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell
    gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
    family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 1867 high: 3529 min/max: 800/4000 scaling:
    driver: intel_cpufreq governor: schedutil cores: 1: 1961 2: 800 3: 3513
    4: 3529 5: 800 6: 800 7: 800 8: 2737 bogomips: 57630
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
    vendor: Gigabyte driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm
    built: 2013 ports: active: HDMI-A-2 empty: HDMI-A-1,VGA-1 bus-ID: 00:02.0
    chip-ID: 8086:0412 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-2 mapped: HDMI-2 model: Asus VE247 serial: <filter>
    built: 2014 res: 1920x1080 hz: 60 dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.5 renderer: Mesa Intel HD Graphics 4600 (HSW
    GT2) direct-render: Yes
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
    driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c
    class-ID: 0403
  Device-2: C-Media CMI8738/CMI8768 PCI Audio driver: snd_cmipci v: kernel
    bus-ID: 04:00.0 chip-ID: 13f6:0111 class-ID: 0401
  API: ALSA v: k6.1.44-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 0.3.77 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-4: PulseAudio v: 16.1 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8168 v: 8.050.03-NAPI modules: r8169 pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlp5s0 state: up mac: <filter>
  Local Storage: total: 704.24 GiB used: 409.68 GiB (58.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT256MX100SSD1
    size: 238.47 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: MU03 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT500MX500SSD1
    size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 023 scheme: MBR
  ID-1: / raw-size: 224 GiB size: 219.43 GiB (97.96%) used: 155.93 GiB (71.1%)
    fs: ext4 dev: /dev/sdb1 maj-min: 8:17
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdb2 maj-min: 8:18
  System Temperatures: cpu: 32.0 C mobo: N/A
  Fan Speeds (RPM): N/A
  Processes: 240 Uptime: 1h 0m wakeups: 2 Memory: total: 16 GiB note: est.
  available: 15.43 GiB used: 2.2 GiB (14.3%) Init: systemd v: 253
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 15.0.7
  Packages: 1768 pm: pacman pkgs: 1760 libs: 491 tools: pamac,yay pm: flatpak
  pkgs: 0 pm: snap pkgs: 8 Shell: Zsh v: 5.9 default: Bash v: 5.1.16
  running-in: konsole inxi: 3.3.28

I confirm this is the same for me with XFCE. Many thanks.

I have the same issue, Teo, and my output matched yours.

With the update to manjaro-hello 0.7.0-7, manjaro-application-utility is now optional and can be removed for now until it’s able to be fixed. Manjaro Hello will work otherwise without it.


I have been offered and applied the upgrade to 0.7.0-7 last night, but ‘manjaro-hello’ still does not work? are you suggesting that i need to uninstall ‘manjaro-application-utility’ for it to work? and re-install it later once it is fixed? will removing ‘manjaro-application-utility’ break something else?





For those who wonder, manjaro-application-utility gave the ability to install from/launch an Octopi-like interface from that Hello window.

It was a list with checkboxes … which then went and installed the checked things.
Maybe a slightly nice touch for a few people … but a bit silly to ‘need’ in just about any context.