LoL the design is better what was before or i am wrong?
What version is it? 21.10 or 20.04?
21.10...Design is better, yes but you should note that I am using Gruvbox theme and not the default.
1 Like
Something like that? Very good a colours not a strong and not lighting. Good for eyes and code designer who using a terminal mostly in jobb.
1 Like
That's why I like it...Most dark themes are too dark and light themes are good but not very appealing to me anymore.
From this guide this is possible your theme.
The gruvbox i saw have 5 stars.
1 Like
Nope that isn't mine...Though it looks cool. I have a reddit account with 0 posts..Might as well delete it.
I don't have reddit but if you can share shortly tutorial or links how to do that will be good point. I bet in Zorin also can do that the same "UBUNTU" distribution. Interesting the iso 21.10 only 2.5GB it is a 50% lower from Zorin ISO.
1 Like
Its really easy actually, but I don't know how it looks like in XFCE but since it uses gtk3 so I presume that it should work fine:
Download Gruvbox theme:
extract the compressed folder
create a ~/.themes folder if it doesn't exist already in your home directory.
put the extracted theme folder in ~/.themes folder
Here is the Gruvbox icon theme for XFCE but I use Tela brown icons
1 Like
Yeah this feature was included in the same update as the one which included kernel 5.16. I even came to know about Pop!_OS Chat.
When I installing a newer version ZORIN the place where put a Gruvbox is
/usr/share/themes/ in xfce but i wondering how to copy if i cannot?
Something not going properly.
Here is example copy
cd /usr/share/themes
sudo cp /pathtodownloadedtheme/yourtheme.tar.gz /usr/share/themes
but how unpacl that is zip
You can use the unzip command, followed by the filename.zip
For example:
unzip Gruvbox-Dark.zip
Usually a .zip instead of a .tar.gz implies that is a parent Directory that contains the theme folders. So if you cannot see your theme in Zorin Appearance, check if you need to Move the Theme Folder into /usr/share/themes instead of leaving it nested in the master folder.
2 Likes
Ok. Today I gived last chance POP OS.
Testing with 5 minutes must be a joke then i gived him more time.
One what I saw they really fixed many things with version 21.10
I am installed drivers for nvidia.
also installed a couple themes nordic,gruvbox and we will se what next. Zorin and POP OS are ubuntu then this is just some diffrents "LEGO". I want see also how people talking about kernel old is good new is wrong. I will also checked xfce is better from Gnome.
1 Like
Ok. Fast experience with newest kernel and Gnome in POP OS.
The software working stable and music not doing pause when changing or loading some software background.
The Gnome configuration desktop and themes are more complicated from xfce.
I mean you need go there and install in webbrowser some app extension to get dash to dock. Look better for eyes but for me it could be like Temple OS but not working smoothly with my experience.
In Zorin I don't have that issue with a game.
One what was very terrible and dissapoint a simple a game from 2013 warframe.
When playing after trying both drivers nouveau and nvidia drivers the game working not smoothly. Something like a car when you start engine and after some 20 meters he stop. Something like shortly freezing on nvidia. On drivers nouveau game don't loading everything freeze.
Maybe it doing a conflicts and then better uninstall nouveau drivers?
In Zorin I don't have that issue with a game but don't recognize resolution what i put somewhere and cannot change with xandr.
POP OS what i saw using only flathub packs. Good move also remove snap from Zorin.
I am really want to know where are this all youtube channels where talking about how it all is good and perfect.
So if you have some solution how to help me with "freezing" when i start digging web.
Sound is good maybe because they using a pipewire?
1 Like
In Pop! OS you don't need dash to dock there are taskbar settings in the settings app:
Yep you need to install "User Themes" extension in Pop! OS to apply third party themes. In Zorin OS that extension is installed by default.
Try using Proton-GE. Maybe it will fix the issue. You can visit protondb to see how people got it working. I am not a core gamer so I don't think I can be of much help... 
Yes flatpak is much better than snap. Snap slows down the boot as well. Flatpak doesn't do that.
They still use pulseaudio.
Prefer using proprietary driver instead of nouveau drivers.
I heard POP OS want go to Rust?
From Linus Torvalds <>
Date Wed, 14 Apr 2021 12:44:54 -0700
Subject Re: [PATCH 00/13] [RFC] Rust support
share 584
On Wed, Apr 14, 2021 at 11:46 AM ojeda@kernel.org wrote:
Some of you have noticed the past few weeks and months that
a serious attempt to bring a second language to the kernel was
being forged. We are finally here, with an RFC that adds support
for Rust to the Linux kernel.
So I replied with my reactions to a couple of the individual patches,
but on the whole I don't hate it.
HOWEVER.
I do think that the "run-time failure panic" is a fundamental issue.
I may not understand the ramifications of when it can happen, so maybe
it's less of an issue than I think it is, but very fundamentally I
think that if some Rust allocation can cause a panic, this is simply
fundamentally not acceptable.
Allocation failures in a driver or non-core code - and that is by
definition all of any new Rust code - can never EVER validly cause
panics. Same goes for "oh, some case I didn't test used 128-bit
integers or floating point".
So if the Rust compiler causes hidden allocations that cannot be
caught and returned as errors, then I seriously think that this whole
approach needs to be entirely NAK'ed, and the Rust infrastructure -
whether at the compiler level or in the kernel wrappers - needs more
work.
So if the panic was just some placeholder for things that can be
caught, then I think that catching code absolutely needs to be
written, and not left as a to-do.
And if the panic situation is some fundamental "this is what the Rust
compiler does for internal allocation failures", then I think it needs
more than just kernel wrapper work - it needs the Rust compiler to be
fixed.
Because kernel code is different from random user-space system tools.
Running out of memory simply MUST NOT cause an abort. It needs to
just result in an error return.
I don't know enough about how the out-of-memory situations would be
triggered and caught to actually know whether this is a fundamental
problem or not, so my reaction comes from ignorance, but basically the
rule has to be that there are absolutely zero run-time "panic()"
calls. Unsafe code has to either be caught at compile time, or it has
to be handled dynamically as just a regular error.
With the main point of Rust being safety, there is no way I will ever
accept "panic dynamically" (whether due to out-of-memory or due to
anything else - I also reacted to the "floating point use causes
dynamic panics") as a feature in the Rust model.
Linus
What's the difference between chat and/or joining/using a forum?
chat is like a streaming live and when you logout history your chat is dissapeard. Forum put something and this is still there. Chat also all people can taken conversation or some "rooms". Chat is chat - forum is forum where topic can be closed.
1 Like