Package Details: tangram 3.0-3

Git Clone URL: https://aur.archlinux.org/tangram.git (read-only, click to copy)
Package Base: tangram
Description: Browser for your pinned tabs
Upstream URL: https://apps.gnome.org/Tangram
Licenses: GPL-3.0-or-later
Submitter: sonny
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 7
Popularity: 0.000081
First Submitted: 2019-09-16 16:37 (UTC)
Last Updated: 2024-01-21 22:19 (UTC)

Latest Comments

1 2 3 Next › Last »

yochananmarqos commented on 2023-05-02 13:59 (UTC)

@iavalos @spsf64: @greut is right. Sorry, I've been testing GNOME 44 and forgot to check this package on my other machine running 43.

greut commented on 2023-05-02 06:36 (UTC)

runAsync is coming with GNOME 44... so we'll have to wait a little bit.

cf. https://release.gnome.org/44/developers/index.html#gnome-javascript (and https://gitlab.gnome.org/GNOME/gjs/-/tags/1.75.2)

spsf64 commented on 2023-05-02 00:16 (UTC)

@iavalos, I think we have similar errors, probably some missing dependency. If you find anything let us known...

yochananmarqos commented on 2023-05-01 22:38 (UTC)

@iavalos: Well, since the developer believes it's not an upstream issue and I already mentioned it's not a packaging issue, then the only logical conclusion is it's something on your end.

Just to be sure: Using the AUR expects a user to be fully up to date with Arch stable. If you're using another distro, then seek their support channels for help.

iavalos commented on 2023-05-01 22:34 (UTC)

@yochananmarqos: I created an upstream issue, but Sonny closed it and told me to report it to the AUR maintainers. https://github.com/sonnyp/Tangram/issues/266

yochananmarqos commented on 2023-05-01 21:27 (UTC)

@spsf64: Maybe try removing the local data directories as listed. Might want to back them up first except for the cache. Other than that, please create an upstream issue.

AUR package comment sections are for package related issues, not technical support.

spsf64 commented on 2023-05-01 21:17 (UTC)

@yochananmarqos, sorry, here is the output from terminal. Maybe the directories are not being created?


re.sonny.Tangram
Gjs-Message: 18:09:24.546: JS LOG: env: host
Gjs-Message: 18:09:24.546: JS LOG: data_dir: /home/user/.local/share/Tangram
Gjs-Message: 18:09:24.547: JS LOG: cache_dir: /home/user/.cache/Tangram
Gjs-Message: 18:09:24.547: JS LOG: config_dir: /home/user/.config/Tangram
Gjs-Message: 18:09:24.547: JS LOG: applications_dir: /home/user/.local/share/applications
Gjs-Message: 18:09:24.547: JS LOG: keyfile_settings_path: 

(re.sonny.Tangram:26336): Gjs-CRITICAL **: 18:09:24.608: JS ERROR: TypeError: application.runAsync is not a function
main@resource:///re/sonny/Tangram/main.js:33:22
@file:///usr/bin/re.sonny.Tangram:20:25


(re.sonny.Tangram:26336): Gjs-CRITICAL **: 18:09:24.608: Module file:///usr/bin/re.sonny.Tangram threw an exception

yochananmarqos commented on 2023-05-01 21:06 (UTC)

@spsf64: The failing appstream test is not related. "Does not work" doesn't tell me anything. It works for me.

spsf64 commented on 2023-05-01 20:55 (UTC) (edited on 2023-05-01 20:55 (UTC) by spsf64)

It compiles but does not work... I get these errors:

3/3 Validate appstream file FAIL 4.27s exit status 1

MALLOC_PERTURB_=146 /usr/bin/appstream-util validate data/appdata/re.sonny.Tangram.metainfo.xml

Summary of Failures:

3/3 Validate appstream file FAIL 4.27s exit status 1

yochananmarqos commented on 2023-05-01 20:07 (UTC)

@iavalos: Can't reproduce that. Make sure you're fully up to date.

1 2 3 Next › Last »