Moved to a fresh install of Zorin 17 from 16 about a week ago and immediately noticed that when logging back in from a locked screen some of the desk top icons has moved. For example the Rubbish Bin was in the lower right corner but shifts up by one block (for the want of a better description), the folders and files down the left hand side have moved down by one.
Anyone else seen this behaviour? Never seen it happen of ver 16.
I have a hp Z800 with nvidia K4000 and dual monitors.
Do you have anything that starts up immediately after boot (or log-in) which changes the Desktop?
For instance, I noticed something similar when I started using Conky (set up so it remains visible even when windows are maximized)... some icons would move around (a couple of the drive icons would move down one 'block', another of the drive icons would move right one 'block').
The solution was to close down Conky, move the icons where I wanted them, start up Conky, move the icons where I wanted them again, and after that, they stayed where they should.
Thanks, I looked at what was automatically started in "Start-up Applications" and had Nvidia X server settings and SSH keys. I stopped them, positioned the Rubbish Bin and rebooted the machine. All Icons were where I had placed them so I locked the machine and then logged back in. Bingo the Rubbish Bin and other icon moved. I again locked the machine and went back in but the icons did not move.
I restarted the nvidia server.
The plot thickens ....
Having restarted nvidia server and leaving the desktop icons where they had been moved to, I shut the machine down are rebooted. Guess what, the icons were in the correct position not the moved position.
Does this sound like a bug? and if it is how do I report it? what logs would be helpful?
Just realised. It only appears to occur on display 1, which is also the primary display in my case.
Further thickening of the gravy ...
With the icons in the moved position, I dragged a file from the desktop to a directory on the desktop and all the Icons were repositioned to where they should be.
Is there a hidden desk top 'reposition icons' setting somewhere at play?
This sounds similar to this following thread. Can you please provide the answers to the same questions I asked there here in this thread:
Two monitors are used both are hp Pavilion23xi.
Graphics card: NVIDIA Corporation GK106GL [Quadro K4000]
Machine: Hewlett-Packard HP Z800 Workstation
Dual Processors: Intel® Xeon(R) CPU E5630 @ 2.53GHz × 16
Windowing System: X11
If it helps. From Logs application "Important" Tab:
14:25:18 systemd: Failed to start Save current user state periodically.
09:19:42 gdm-session-wor: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
09:19:42 gnome-session-b: GLib-CRITICAL: g_hash_table_foreach_remove_or_steal: assertion 'version == hash_table->version' failed
09:19:38 systemd: Failed to start Application launched by gnome-session-binary.
09:19:32 pulseaudio: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
09:19:27 gdm-session-wor: gkr-pam: unable to locate daemon control file
09:19:11 gnome-session-b: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'RAID_VOL0_PHYS_DISK [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptsas.c:726:23
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'IOC_3_PHYS_DISK [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptscsih.c:2149:39
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'IOC_3_PHYS_DISK [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptscsih.c:2214:41
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'IOC_3_PHYS_DISK [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptscsih.c:2213:51
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'IOC_3_PHYS_DISK [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptscsih.c:2212:46
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'IOC_3_PHYS_DISK [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptscsih.c:2135:51
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'IOC_3_PHYS_DISK [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptscsih.c:2134:46
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 2 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptsas.c:2443:46
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptsas.c:2451:7
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptsas.c:2448:22
09:18:47 kernel: ================================================================================
09:18:47 kernel: index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]'
09:18:47 kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/drivers/message/fusion/mptsas.c:2446:22
09:18:47 kernel: ================================================================================
09:18:47 kernel:
09:18:47 kernel: ACPI Error: Aborting method _SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20230331/psparse-529)
09:18:47 kernel: ioremap memtype_reserve failed -22
Which driver are you on?
nvidia-smi
and which kernel?
uname -r
This looks like a known bug in the later kernel used with Nvidia later drivers.
I recommend avoiding using the 535 driver - the 525 driver works.
I recommend if using the 545 driver, upgradinbg to the 6.6.5 kernel.
Reports: NVIDIA-SMI 470.223.02 Driver Version: 470.223.02 CUDA Version: 11.4
uname -r
Reports: 6.5.0-14-generic
Regarding your recommended driver and kernel. If Zorin publish the 6.6.5 kernel then auto update will do its magic. The 535 driver was not recommended when I ran the appropriate install process but again I expect auto update to resolve that.
I also kept having issues with the DVI signal disappearing about 30sec after not moving the mouse.
Got fed-up with the issues and switched back to the X.Org X server.
So far no issues with moving desktop icons or disappearing DVI signal.
Just noticed that the windowing system has switched from X11 using the nvidia driver to Wayland with the X.Org drivers.
Are you saying that you logged in on Zorin Desktop on X and it switched you back to Wayland during that session?
Nope. I reselected the X.Ord driver then rebooted before checking the icon jiggling, loss of DVI and making the Wayland observation.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.