Gnome 42.0: Dark Mode Style does not work #8
Comments
|
When you have new binaries plz upload here. Also give us a feed back, what was missing. :)) |
|
New binaries for Gnome 42 / Slackware -current are online libportal and xdg-desktop-portal-gtk were missing. Just for a change, I also added a script to install the new Fedora 36 wallpapers. |
|
Arch have first beta unstable release , there is a new arch patch for GDM https://gitlab.com/fabiscafe/gnome-unstable/-/blob/main/gdm/0001-Xsession-Don-t-start-ssh-agent-by-default.patch |
Thank you for pointing that out! I think to get run gdm on Slackware would be my next challenge. Fingers crossed ;-) |
|
good luck !!!! ps If you decide to fight with the devil... keep this on your /tmp you may need it... |
|
@slackernetuk, I haven't tried your packages but on Porteus (the distro I work on that is based on Slackware) dark mode works just nice. Gonna try on Slackware 15 live later on.
|
|
No problems :)
Have you tried in Slackware 15.0? Maybe the issue you're seeing is related to Slackware current, which I haven't tried. |
Honestly, I don't like 'gnome-console', too simple for my needs. By the way, 'gnome-console' isn't a 'Gnome-Terminal' replacement. But, I can see your point...to modify the build script with a parameter would be Possibly 'libportal' isn't necessary,but without 'xdg-desktop-portal-gtk' the What shall I say, the German perfectionism is a bit strange...sometimes. 😆 |
|
GNOME is such a mess, hahaha! In the official release note they say:
It's so odd that Slackware current requires
LOL |
|
Indeed, in Slackware current I end up in that lovely GNOME shell error screen. But that was using my GNOME 42 binaries. Let's see with yours. EDIT: using your binaries: |
|
So, yes, for some reason Slackware current requires |
|
I had successfully hack google-online-account so goa-daemon is runing if I want, only if its needed as dependency from other apps-service during compiling , whithout really working as informer... but dependency is satisfied lol |
|
Nice work, @slackernetuk! :) BTW, have you managed to solve this? |
|
Maybe you guys want to read my GNOME 42 review :) https://medium.com/@fulalas/gnome-42-the-nonsense-continues-7d96c3287f7 |
Good news are that probably I found a solution to pass systemd dependency, but I am not sure because I have this meson bug ... edit: the error on the slackbuild name(mailn) is ok, I dont want tgz package to be created now... if script run ok untill that stage... |
|
https://github.com/rizitis/Gnome42-Slackware-15.0-STABLE/tree/main/power-profiles-daemon thats the best I can do... :) |
Not yet....but rizitis solution seems alright....sadly, I just can test stuff by QEMU/KVM at the moment. |
I have modified your scripts, have a look and tell me what you think.
|
|
I builded it with If you want command |
I don't know, maybe you misunderstood, what I have written earler. The point is, to build 'power-profiles-daemon' on Just have a look into By the way, to delete the BTW, it wasn't a technical question, I just wanted to know your opinion. 😄 |
|
I am sorry , I m using google translate... I try hard with my (non) English... :( btw: I have a problem with if you have any suggestion plz... ps It very important to find a solution to be working "record desktop" because its the only app for record desktop properly on Wayland... we must found what is missing... |
|
also from terminal if command
but since its part of gnome desktop the app why we all have the same problem? Something is missing... |
If you want build Gnome 42 on Slackware 15.0 following this steps. If you prefer the gnome-terminal instead of gnome-console Oh, 'xdg-desktop-portal-gtk' is just necessary on Slackware -current.....is this bloody GNOME mess. 😆 I have some Greek friends but I don't speak Greek at all, but German is welcome as well. 🤣 Screencasting on Wayland is 'obs' or 'obs-gnome-screencast' probably the best choice |
|
@slackernetuk it would be nice if you submit the packages to Sbo. |
|
Ι have localy upgrade all slackport/gfs scripts to the latest release of every version. Untill Monday I hope I finsh. GDM included :p |
|
well it woud be nice if someone submit the slackbuilds to slackbuilds.org although i dont use Gnome some user will like to have gnome, i submitted slackbuilds but nothing related to gnome. |
|
You are right, but the problem is that sbo scripts have very special writing typo, and they will not approved my typo of script... 13 packages only canot be build to latest version from gfs because of bugs ... I will try again Monday and then I will upoload everything... I will try to pull request first slackport/gfs , thats the first thing... |
|
https://slackbuilds.org/templates/ just adapt the slackbuilds to the suggested new templates, i did that for my slackbuilds its very easy but it takes time. |
|
Also now i can install extensions from the site. Everything works fine except gdm and screen record. But to be honest, gnome is a big dependency confusio... To build it we need to upgrade, downgrade lots of libs... Every app need other version of the same lib 🤒 |
|
now that all is working as it should including gdm ( i saw the slackware post) if you want to submit the packages you have to create README, slack-desc, slackbuilds and the package.info files for every package, maintain the Rafael Tavares name in the slackbuilds. if you want you can email me so i can help you to speed up because now its a tedious thing of typing a lot. |
|
Ok @adcdam I will sent you all scripts that was not modified but work as it was or the only change was the number of version. Yew I m a farmer, a poor farmer. I have olives trees and I product olive oil. |
|
@adcdam @slackernetuk these scripts I dont have to send them via email because you can take them directly from slackports/gfs ps sorry for the path... just read the last words before "okold", the name of file as it is on slackports/gfs
|
|
@rizitis Let's be honest, Rafael has done a really good job, but I think I will rewrite all scripts to the SBo standard. |
Yes thats exactly what I m doing now. Rafael has done GREAT job, but I m writing all scripts I kept (not those "okold" thats for @adcdam ) to the sbo way. If you want guys we can organize our job so we dont do double work.. I really dont care if my name is as modifier on scripts. I know very well how to write a script on the sbo way, its the only thing I know well... If you guys want to separate the job , it will be fine for me, if you want to work alone, thats ok for me also... |
|
I want to say one more, from the files I kept to work the sbo way , 99 files are already to sbopkg, even if are not up to date, we CANT send them to SlackBuilds, because they dont accept packages who someone else maintain , even if those packages are not updated. We have to email the maintainer fist and if he accept we must send the email we received from him to SlackBuilds and after that we can send the scripts updated to SlackBuilds. I will not do that. I will write only scripts that are not in SBo and I will send them. If they approve them ok, if not no problem for me...
|
|
rizitis about slackbuilds.org they do accept updates from someone else but you ll have to ask the mantainer first. |
@adcdam yes thats what I wrote^^ |
|
someone post in the slackware forum posted this wow fantastic that user recommend to use another distro for gnome. what a nice community.... |
|
We can write that we have gnome running on our slackware64 and we are very happy... |
|
@adcdam I m to old to play games... so I ask on irc #slackbuilds
if they dont answer yes, I will not lose my time... I m online now and waiting... |
The answer is yes! |
|
Just my opinion, if everyone is cooking their own soup...it's a waste of time. I think the project needs a bit more structure and I think Gitlab isn't the best platform to talk about the details. Maybe a small management tool for software projects would be better to talk about the details. By the way, are you guys on Facebook? |
No i dont have facebook or any other socials... this is the dialog I had we the slackbuild team
but i agree that this is not the right place for talking... if you think a solution that we can speak as a team it would be nice.. this issue here should be close... |
|
i think that slackernetuk is right i agree on "if everyone is cooking their own soup...it's a waste of time". if im mistaken please correct me specially the part about gtk4 version. |
|
Ok then we all agree, so i think that slackernetuk should take the risk to be the "leader" and organise the job. First of all we have to find a place to talk. This issue must close... |
|
first please check if im mistaken or not about the gtk4 version. |
Firstly, I'll make a rough plan and then let you guys know which direction we could take. I prefer to talk about the details by mail....if you guys have better ideas let me know. By the way, Linux from Scratch has updated to GNOME42 as well.....very helpful for dependencies, patches etc. |
|
The best free solution for talking is to use Discord as mail list , we have it on SBo easy installtion, you can just login with email verification, and its safe. If you agree follow the link https://discord.gg/sMzwUS8GxB name of small friends community is "Gnome for Slack". I think is the best solution, because in future there will be more people interesting to help... |
Hiya guys,
the work is done, all scripts to build Gnome 42 are online. I had to modify some scripts and I added gnome-background & gnome-terminal as well. The most things working nicely but there a little complication....to turn on the dark mode does not work.
Maybe someone can help to fix it.
Scripts:
https://gitlab.com/slackernetuk/gnome-light/-/tree/Current-42.0
Binaries -current
https://slackernet.ddns.net/slackware/slackware64-current/slackware64/gnome-light/42.0/
The text was updated successfully, but these errors were encountered: