SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If you get errors about *.gir files missing then that respective dependency was built without building its introspection files enabled. There's a number of slackbuilds on slackbuilds.org that have building introspection files (*.gir files) disabled by the maintainer, hence the need for those environment variables to re-enable them.
Can you give some more informations plz?
this problem was before you
Code:
export INTROSPECTION=yes
right?
or you still cant build gnome-maps?
thank you.
So I think this was probably due to previous packages being built without INTROSPECTION. I only enabled it when I got to cogl. I'll rebuild all the packages again later today.
If you want to be sure then build it again. But if you builded properly after "cogl" then you can only re-build packages before "cogl" to save time...
But its better to rebuild all list to be sure 100%
If you want to be sure then build it again. But if you builded properly after "cogl" then you can only re-build packages before "cogl" to save time...
But its better to rebuild all list to be sure 100%
Going through a full rebuild now. Will report back when completed.
Build completed and happy to report that it built this time around!
I tried building it for -current, but the new meson is not jiving with some of the packages.
For current there 2 other repos ready with vanilla Gnome42 and this time almost all Gnome suite included, 95%. One is the a updaded fork of gfs and developer of this project will announce it in few days here on forum. And the other is this https://github.com/0xBOBF/gnome-42-slackbuilds, but we need 2-3 days to update the build list... If you like to have a fast experience in
-current with Gnome42 on a VBox you can just download binaries from here https://github.com/rizitis/Gnome-42 to test it. But if you want to build it , just wait 2-3 days... Both repos are tested and are ok.
For current there 2 other repos ready with vanilla Gnome42 and this time almost all Gnome suite included, 95%. One is the a updaded fork of gfs and developer of this project will announce it in few days here on forum. And the other is this https://github.com/0xBOBF/gnome-42-slackbuilds, but we need 2-3 days to update the build list... If you like to have a fast experience in
-current with Gnome42 on a VBox you can just download binaries from here https://github.com/rizitis/Gnome-42 to test it. But if you want to build it , just wait 2-3 days... Both repos are tested and are ok.
So gnome-terminal doesn't start on Wayland. I get the following error:
Code:
# Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0:
Error calling StartServiceByName for org.gnome.Terminal: Process org.gnome.Terminal exited with status 8
you are very welcome I am requesting Bob right now to make sure that it is included in his build script we found this problem back in May on Gnome 42.x and Bob found the solution that was required for it.
Please make sure this command is in the rc.local file
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
