ALHP/ALHP.GO
6
42
Fork 9
Code Issues 25 Pull Requests Projects Releases Wiki Activity

Telegram Desktop fails to start with ALHP wayland #80

New Issue
Closed
opened 2021-12-14 22:21:08 +01:00 by alissonlauffer · 7 comments
alissonlauffer commented 2021-12-14 22:21:08 +01:00
Copy Link

This time I did some testing before submitting an issue and it's unrelated to testing repos being enabled xD

Apparently, Telegram Desktop is broken in my environment (GNOME over Wayland) when using wayland from ALHP repo (installing it from official repos makes the issue disappear, and installing back makes it happen again).

telegram-desktop: symbol lookup error: telegram-desktop: undefined symbol: wl_proxy_marshal_flags
_This time I did some testing before submitting an issue and it's unrelated to testing repos being enabled xD_ Apparently, Telegram Desktop is broken in my environment (GNOME over Wayland) when using wayland from ALHP repo (installing it from official repos makes the issue disappear, and installing back makes it happen again). ``` telegram-desktop: symbol lookup error: telegram-desktop: undefined symbol: wl_proxy_marshal_flags ```
alissonlauffer commented 2021-12-14 22:35:11 +01:00
Author
Copy Link

Digging a bit on this:
Apparently telegram-desktop on ALHP has been built over wayland 1.20.0, while latest wayland version on ALHP is 1.19.0, then leaving the dependencies in a broken state until wayland completes its build (which is taking some time, since there are lots of queued packages).

Digging a bit on this: Apparently `telegram-desktop` on ALHP has been built over wayland 1.20.0, while latest wayland version on ALHP is 1.19.0, then leaving the dependencies in a broken state until wayland completes its build (which is taking some time, since there are lots of queued packages).
Gontier-Julien commented 2021-12-14 22:39:38 +01:00
Copy Link

Seems related to my issue

Seems related to my [issue](https://git.harting.dev/ALHP/ALHP.GO/issues/79)
alissonlauffer commented 2021-12-14 22:42:54 +01:00
Author
Copy Link

Seems related to my issue

Yeah, indeed. ALHP should delay package publishing until package dependences are built too, avoiding broken packages.

> Seems related to my [issue](https://git.harting.dev/ALHP/ALHP.GO/issues/79) Yeah, indeed. ALHP should delay package publishing until package dependences are built too, avoiding broken packages.
alissonlauffer commented 2021-12-14 22:48:17 +01:00
Author
Copy Link

Related to #78.

Related to #78.
anonfunc commented 2021-12-15 10:34:35 +01:00
Owner
Copy Link

Seems related to my issue

Yeah, indeed. ALHP should delay package publishing until package dependencies are built too, avoiding broken packages.

ALHP does not build with its own packages as dependencies. It always builds with official packages, and it does make sure these are up-to-date. This can only be an LTO problem. Most likely we have some new candidates for the LTO blacklist.

I would like to try a rebuild, but I would expect the same problem appearing again.

Same goes for #79.

> > Seems related to my [issue](https://git.harting.dev/ALHP/ALHP.GO/issues/79) > > Yeah, indeed. ALHP should delay package publishing until package dependencies are built too, avoiding broken packages. ALHP does **not** build with its own packages as dependencies. It always builds with official packages, and it does make sure these are up-to-date. This can only be an LTO problem. Most likely we have some new candidates for the LTO blacklist. I would like to try a rebuild, but I would expect the same problem appearing again. Same goes for #79.
anonfunc added the
bug
 label 2021-12-15 10:34:54 +01:00
alissonlauffer commented 2021-12-15 10:36:20 +01:00
Author
Copy Link

This can only be an LTO problem. Most likely we have some new candidates for the LTO blacklist.

In this case, it was because of the Wayland version, now it is working properly after wayland 1.20 arrived ALHP.

> This can only be an LTO problem. Most likely we have some new candidates for the LTO blacklist. In this case, it was because of the Wayland version, now it is working properly after wayland 1.20 arrived ALHP.
anonfunc commented 2021-12-15 10:40:14 +01:00
Owner
Copy Link

Ah, I did not check wayland. Well, good that it works now.

Ah, I did not check `wayland`. Well, good that it works now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked upstream
bug
Something is not working
build-failure
package build fails
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
informational
Provides information about something
invalid
Something is wrong
invalid/corrupt package
Package needs to be rebuild
packaging issue
priority: high
High priority
question
More information is needed
support
wontfix
This won't be fixed
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
anonfunc
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ALHP/ALHP.GO#80
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?