Occasionally, when I start Zorin, none of the icons appear on the screen. I have to restart Zorin to get the icons to appear.
Does anybody know what is causing the icons to not appear and what I can to to correct the problem?
Thanks.
This could be due to the system hanging and taking too long to enter into the GUI. And when this happens in the future, instead of restarting the whole computer, try just restarting the desktop, by running the following commands.
CTRL F2
Type lower case r in the box, and hit enter.
Now, in regards to figuring out the cause of the issue in the first place, we might try looking at your log files. Please do CTRL ALT T to enter a terminal window.
sudo dmesg
It will produce a huge log view, please copy and past the log in a response here, and @Aravisian will be able to help you further with this.
Additionally, in regards to keeping track of boot times, you can also run this command...
systemd-analyze
Go ahead and post those results as well, as they could be informative. I assume you have CORE installed? There is no way for me to know for sure, since your profile hasn't been updated. Well, thats all I got for now.
Also, incase machine SPECS are important. Please run this command...
sudo apt install screenfetch
Once installed, just type the word screenfetch, and it will produce your machine specs, then you just take a screenshot of that with the print screen key, and post the screenshot in a response here.
StarTreker
Your Tech Support Guru
1 Like
I have copied the log file and saved it in Libre Office. When I go to attach the file, it looks like it will only allow me to upload an image.
If I try to paste the file directly into the post, the file is to large.
It sounds like your Desktop Manager is not initializing.
2 Likes
Any way I can fix that?
1 Like
I may be wrong. Something about what I said earlier bothered me- I recall reading about how Gnome disabled Desktop Icons.
So I just looked it up:
It seems and extension is used to create that function to make up for yet another... Gnome removal...
I do not use Gnome, so perhaps @StarTreker or another Gnome User can check which extension Zorin uses.
I tried the ctrl F2 and r but that did not work.
OK, I spent time to work on this to check out the Desktop Icons extension from RasterSoft. OK, but lets begin by first demonstrated icons already on my desktop from the Zorin Appearance menu.
Now lets install the extension at Gnome-Look
I am testing this on POP OS though, but the results should be identical to Zorin OS as they are the same systems at their core, Ubuntu and Gnome.
With the extensions turned off...
With extension turned on...
As you can see, it just repeats what the system already has set in functionality. So honestly, I don't really know if this extension is a good thing or not.
Zorin OS comes with an extension already installed for this purpose.
I will log into Gnome in a bit and see what I can find.
Yeah, cause I've already lost patience with it. I don't get what the extension is supposed to do that Zorin don't already have.
I believe I found it:
Try:
sudo apt install --reinstall gnome-shell-extension-zorin-desktop-icons
It happened this morning when I booted up. So I copied part of the log files which should show the error.
[ 9171.159624] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9171.159629] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9173.378972] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9173.378991] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9173.378998] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9173.379004] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9174.402752] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9174.402770] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9174.402778] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9174.402783] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9178.379223] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9178.379242] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9178.379249] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9178.379255] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9184.386653] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9184.386671] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9184.386679] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9184.386684] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9188.378548] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9188.378566] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9188.378573] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9188.378579] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9189.159117] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9189.159135] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9189.159143] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9189.159148] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9193.378384] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9193.378397] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9193.378400] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9193.378402] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9194.402551] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9194.402569] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9194.402577] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9194.402582] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9195.157073] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9195.157091] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9195.157099] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9195.157104] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9199.394503] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9199.394521] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9199.394529] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9199.394534] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9200.418514] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9200.418532] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9200.418540] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9200.418545] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9203.378614] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9203.378632] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9203.378640] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mask=00000001/00002000
[ 9203.378645] pcieport 0000:00:1c.0: AER: [ 0] RxErr
[ 9204.386441] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[ 9204.386460] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[ 9204.386467] pcieport 0000:00:1c.0: AER: device [8086:a33d] error status/mas
1 Like
Can you open a terminal and run
sudo nano /etc/default/grub
Arrow key down to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
And adjust it to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
When finished, hit ctrl+x to exit, then the y key to say yes to save, then the enter key to save as current configuration.
The terminal will revert to normal.
Now, run:
sudo update-grub
Reboot and test.
Okay, I did that and everything came up okay. Let's see how it goes for the next few days.
Thanks.
1 Like
I sometime have this problem when I go back and forth between the virtual desktops. When it happens I solve it by simply log off / log on which is much faster than rebooting.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
Marked solution. 140