| Summary: | computer freezes at SDDM when upgrade from Mga8 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | w unruh <unruh> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | fri, marja11 |
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | sddm? xorg? | CVE: | |
| Status comment: | |||
|
Description
w unruh
2024-05-23 19:49:39 CEST
This seems not like a bug. You can't simply switch between home partitions from different OS releases. When you do an upgrade from MGA8->MGA9 parts of your home directory get updated/adapted to be compatible with the new version. But you can't simply use an hold MGA8 home partition (not adapted/upgraded) AFTER you have installed a fresh MGA9. Downgrading is not supported. This includes using Mageia 8 with desktop configuration where Mageia 9 have been running. Status:
NEW =>
RESOLVED Im sorry but these make no sense. It has been recommended in many places that instead of upgrading one should carry out a fresh install instead. A fresh install cannot look into users directories to change users data. If you mean that items in /etc/ or /var/ , then those were all part of the fresh install, with changes made so that the system decisions I made were reimplimented. (eg /etc/passwd, /etc/shadow, /etc/hosts, /etc/sysconfig,... were changed from the fresh install. Resolution:
INVALID =>
(none) Please reread the documentation. Fresh install means fresh install including a new /home. You seem to mix some stuff up. https://wiki.mageia.org/en/How_to_choose_the_right_Mageia_upgrade_method It is possible to upgrade from MGA8->MGA9 by formatting / but keeping /home. It is not possible to install MGA9 completely fresh (all formatted) and than later try to bind an old MGA8 /home to the fresh MGA9. You try to use a MGA8 /home and a MGA9 /home on a base MGA9 system. This is not supported (on no linux distribution). Or your description is unclear… Resolution:
(none) =>
INVALID I guess I did not make it clear. I have a separate home partition which contains the home directory. I installed Mga9 on a separate partition from the home partition. sddm froze at the login screen after I entered my password. while alt-ctrl-F2 worked. My stating that lightdm worked, I am not sure now (I do not have immediate access to the machine at present) that I properly tested it. sddm does work if I have a brand new home created by Mga9.but of course that loses all my previous work- which is NOT acceptable. So, the home directory is on a separate partition to the mga9 / partition. The mga8 is also on a separate partition from both the mga9 / and the home partitions. The mga8 and mga9 / partitions contain their own /etc, /var, /usr (except /usr/local) which is on a separate partition from all of the above) Ie, the mga9 and mga8 are on separate partition. sddm on mga9 freezes when I log onto my own account. whether mga9 freezes if I use lightdm I have to recheck in I did the test on a mga9 generated home/unruh directory or an mga8 generated one. I transferred the /etc/passwd entries > than uid >1000 from mga8 to mga9. I transferred /etc/hosts from mga8 to mga9. Note that instead of being so quick to declare a bug report invalid, ask for clarification. I have reopened it Resolution:
INVALID =>
(none) You can't simply switch /home directorys from different OS releases as you like! - Different UUIDs in fstab. - Breaking of settings/databases and so on as downgrade is unsupported. Do a proper upgrade from your MGA8->MGA9 by preserving the seperate home partition and you will be able to login. Read the release notes how to perform an upgrade. Bugzilla is not the right place for user education. Of Course /etc/fstab needs to be changed. I_ have been running mageia since it was Mandrake. I have upgraded numerous times. I have had home and /usr/local on separate partition for at least 30 years, and before mga9 have never had this kind of problem. The computer I am trying to upgrade is a server which serves about 5 other Mageia machines. I cannot afford to have it go down -- eg by upgrading mga8 to 9, and then discovering 9 is broken. I have to upgrade with a separate new partition for the new mga9, so I have a route back to an operating system. You seem to say that the upgrade path alters stuff in th /home partition. That would make all backups useless, since suddenly they would not have those changes needed for the system to run. Thus I do not believe that the upgrade touches stuff in the home directories (never mind that they might have to change things in 1000 home directories on some servers). My home directories are all on separate partitions from the system. My mga9 were installed on fresh partitions. sddm did not work for me.(I do not have everyone elses' passwords to test them all). Is it something in my home directory? I do not know. It is not in .config. It is not in Desktop. (In both cases I moves them out of the way, and leet the system recreate them when I tried to log in). I have also had this problem with sddm on three machines, and on most lightdm "fixed" the problem. Yes on all of them the home directories were on separate partitions from the system. (In reply to w unruh from comment #0) > > I installed a new version of Mga9 on a machine that used to run Mga8 on a > sparate partition. If I use the home directory installed during the > installation of Mga9 it domes up. If I use the home directory from Mga8, I > get a black screen, or the system never leaves the sddm login screen. I have > no idea how to chase down the bug. I wouldn't call this a bug, because doing a fresh install with a new /home partition and then later switching to the /home partition of a previous installation, is not supported nor does it ever get tested by QA-team. However, doing a fresh install while keeping the old home partition (so giving it the mount point /home when you are in the partitioning step and NOT selecting to format it), that is tested. (In reply to w unruh from comment #7) > > I have also had this problem with sddm on three machines, and on most > lightdm "fixed" the problem. Yes on all of them the home directories were on > separate partitions from the system. And, who knows, maybe it had been the other way around if you used lightdm in the past and tried sddm now... You might want to ask in the Forum for help. Or you could run urpmq -l sddm | grep conf and check the config files of sddm. Maybe, if you have settings like RememberLastUser=true RememberLastSession=true that it can cause problems when using a different /home partition. Anyway, closing. CC:
(none) =>
marja11 (In reply to Marja Van Waes from comment #8) > > You might want to ask in the Forum for help. https://forums.mageia.org/en/ |