I got into a problem making a cloned sdcard and running it on another raspi: essentially cloning went smoothly. But after booting the cloned system and logging into my xfce user, the display came out excessively big (the resolution on the original system had been 1600x1200, the display for the cloned user appeared as if the resolution had been configured to 1024x768
Background:
- origin (source for the clone: fully upgraded Buster-lite image (as off 06.06.20)
- target machines (origin and cloned systen) Rapsi 4B
- cloning method: dd to a gzip file (as documented in this forum
It became rapidly evident that the faulty data in the cloned system was xfce data: the incorrect display only happened for a specific user, the one for whom on the original system some minor edits to the panel settings had been made and some panel items had been removed resp.added - (1) logging into other users (e.g. pi) that had not been modified provide the correct resolution on the cloned system, and (2) destroying the .config directory for the user with the problem and having it re-created (new login on the cloned system) resulted in a correct resolution. And, please note, I certainly did nothing between booting the cloned system a first time and logging into the user environment.
Since destroying/remaking .config can be used as a work-around, this problem is not a serious handicap for me. But I am preoccupied with the reliability of the cloning process: how can this be explained? is this a very local incident with xfce, or is there a hidden problem with cloning? what can I do to clarify (note that both creating the image and writing it to a new sdcard is a very lengthy process)?
More details
- I used a display with a resolution of 1600x1200, the original system was correctly configured to that resolution (both in raspi-confg->Advance Options and in Settings->Display
- Settings->Display on the cloned system appeared as 1024x768; changing this setting to 1600x1200 was accepted (and shown as the selected setting when I went back to Settings->Display), but had no effect whatever