[opensuse] Upgrading to OpenSuSE15.0 problems
I am in the process of trying to upgrade one of my computers to OpenSuSE 15.0 and running into a number of problems. I first started with OpenSuSE42.3 x64 with the KDE/Plasma desktop, and I tried to do an in place straight upgrade. I will also mention that my OpenSuSE42.3 system had something broken with the network drivers so I did not have access to the internet directly from it. So I used my laptop to download the OpenSuSE 15.0 iso file and burned it to a DVD. I mention this because I am suspicious that this may be what is causing me some of the problems I am experiencing, though I do not understand why that should be the case. After my first attempt to upgrade my computer to 15.0 it failed to boot. My research lead me to discover that the installer had changed the grub configuration so that it was trying to make calls to linuxefi and initrdefi. I don't use the efi filesystem on this computer and have no desire to do so. (don't get me started on how much troubles I have had with efi. I use it on my laptop only because I am using solid state drives and it seems that I must use efi on it.) My BIOS in the computer I am trying to upgrade has EFI turned off and only uses legacy file management. So I manually edited the grub configuration file and removed the efi suffix of these calls, i.e. made calls to linux and initrd instead, and the boot up succeeded. However, that lead me to another mess, after logging in to my account, I discovered the KDE/Plasma desktop was not working properly. I had a few konsole windows that opened up (ones I had left open when I brought the system down) but the plasma part of the desktop was not there. No background, no kicker bar, no mouse activity or the ability to right click and bring up the pop up menu dialog etc. In other words almost useless, although all the services and background tasks I have configured to run started up fine. (things like Apache, Tomcat, Bind, DHCPD etc.) I don't know how to recover from this mess, I tried reinstalling all the KDE and Plasma packages but no joy, so I decided to try a different approach - My next attempt was to install OpenSuSE 15.0 into a new/separate partition but I cannot get past the partitioner. It appears it is trying to force me into using the EFI boot system. I don't allow the OpenSuSE installer's partitioner to decide for me (it's defaults) how to configure my system as it makes choices that I don't want. Instead I have it import all my mount points that I have defined in what was my OpenSuSE42.3 (now upgraded to a broken 15.0) system. That much works fine and I just move the mount point for / to a new partition so that the new OpenSuSE15.0 system will be mostly installed in a different partition and I can keep my old system for the time being. However when I tell the partitioner to accept all the new changes I get a complaint - "Missing device for /boot/efi with size equal or bigger than 256MiB and filesystem vfat." Why am I being forced into using EFI? My system/BIOS is configured to use the legacy boot loaders and explicitly turns off EFI! I cannot find any means of telling the OpenSuSE installer/partitioner to use the legacy method of boot loading either, so I am stuck. I have one other complaint about the OpenSuSE 15.0 installer/partitioner that I want to pass along as it almost destroyed my entire system, had I not caught it. After I told the partitioner to import all my mount points from my previous system, I fortunately observed that it had marked ALL of my mount point partitions to be formatted!!! That is just plain wrong, the user should NEVER have to opt out of having data destroyed, but have to opt in to having anything formatted. That modus operandi really needs to be reversed, formatting of any partition should never be done by default. I will listen to any arguments to the contrary but I feel pretty strongly that this should be reported as a bug and fixed. (I am willing to do so.) Appreciate any thoughts on how to install OpenSuSE 15.0 using the legacy boot loaders and not use EFI booting? Sorry for the long writeup and please forgive me if I didn't communicate this technically correctly, this is definitely not my area of expertise! ... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Marc Chamberlin composed on 2019-01-12 13:46 (UTC-0800): ... Output from parted -l should explain to us what the installation partitioner is seeing. UEFI vs MBR process is a function of how the DVD is booted. You can't make a choice once booted to it. It must be booted in the desired mode. You'll probably have to use your BIOS boot menu to override its predilection to use UEFI mode. When it's in UEFI mode, the function key menu options are missing from its menu. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/12/2019 02:11 PM, Felix Miata wrote:
Marc Chamberlin composed on 2019-01-12 13:46 (UTC-0800): ... Output from parted -l should explain to us what the installation partitioner is seeing.
Thanks Felix for responding, Ok I can do this! ;-) parted -l Model: ATA WDC WD5001AALS-0 (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 53.7GB 53.7GB primary linux-swap(v1) type=82 3 53.7GB 107GB 53.7GB primary ext4 type=83 2 107GB 500GB 393GB primary ext4 type=83 Model: ATA WDC WD5000AAKS-0 (scsi) Disk /dev/sdb: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 53.7GB 53.7GB primary xfs type=83 2 53.7GB 107GB 53.7GB primary xfs type=83 3 107GB 215GB 107GB primary xfs type=83 4 215GB 500GB 285GB extended lba, type=0f 5 215GB 392GB 177GB logical xfs type=83 6 392GB 446GB 53.7GB logical xfs type=83 7 446GB 500GB 54.5GB logical xfs type=83 Model: ATA WDC WD10EZEX-22M (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 1 53.9GB 54.1GB 207MB ext4 primary msftdata 2 54.1GB 161GB 107GB ext4 primary legacy_boot, msftdata 3 161GB 183GB 21.5GB ext4 primary msftdata 4 183GB 237GB 53.7GB ext4 primary msftdata 5 237GB 344GB 107GB ext4 primary msftdata 6 344GB 398GB 53.7GB ext4 primary msftdata 7 398GB 612GB 215GB ext4 primary msftdata
UEFI vs MBR process is a function of how the DVD is booted. You can't make a choice once booted to it. It must be booted in the desired mode. You'll probably have to use your BIOS boot menu to override its predilection to use UEFI mode. When it's in UEFI mode, the function key menu options are missing from its menu.
Good to know how UEFI vs MBR is chosen, but I don't understand why UEFI is being chosen. It wasn't, AFAIK when I installed the previous versions of OpenSuSE but I am not going to be adamant about that, too many computers in my past to keep track of em all... Anywise I think I had disabled UEFI mode in the BIOS, although I am not sure what you are referring to when you say function key menu options.... The BIOS is wrapped in some fancy schmancy Gigabyte GUI that is all pizzazed up to look pretty and sexy for gamers. Any setting I found that mentions UEFI I turned off but it is not a simple setting in one location. I am given the choice between "No not launch", UEFI, and Legacy for "Storage Boot Option Control" and "Other PCI devices" both of which are set to Legacy. The Gigabyte logo splash screen, shown right after power up, shows only briefly and does show a couple of function key menu options and it also tells the user to use the Del key to access the BIOS settings. Then the OpenSuSE GRUB menu opens up and just shows the two versions of OpenSuSE operating systems (plus two variants with advanced options) to choose from. Also a couple of other things like an Edit option to make changes to the Grub configuration. But no function key menu options are shown in the Grub menu. Marc... -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Marc Chamberlin composed on 2019-01-12 15:27 (UTC-0800):
I am not sure what you are referring to when you say function key menu options....
While POST is in process, press F12 key. You want to see a screen much like this: http://fm.no-ip.com/SS/Suse/YaST/150/gigabyte-F12menu.jpg Notice the highlight on the first option, which does not include the text UEFI. That's my Leap 15.0 in the Plextor DVD drive ready to proceed to boot in Legacy MBR mode. The BIOS is
wrapped in some fancy schmancy Gigabyte GUI that is all pizzazed up to look pretty and sexy for gamers.
It is a mess...
Any setting I found that mentions UEFI I turned off but it is not a simple setting in one location.
Agreed. Start by finding this screen. http://fm.no-ip.com/SS/Suse/YaST/150/gigabyte-BIOSstorageOption.jpg Note on the right side I had to scroll down to find it "Storage Boot Option Control". You can see the highlight on UEFI, but you need it on Legacy.
I am given the choice between "No not launch", UEFI, and Legacy for "Storage Boot Option Control" and "Other PCI devices" both of which are set to Legacy.
Choose Legacy there. Mine has the same three options. I didn't mess with Other PCI devices.
The Gigabyte logo splash screen, shown right after power up, shows only briefly and does show a couple of function key menu options and it also tells the user to use the Del key to access the BIOS settings.
That's when you need your finger on the F12 key. When it goes right, you get this (MBR/Legacy): http://fm.no-ip.com/SS/Suse/YaST/150/150-BIOSmenu.jpg If you can't get it following my instructions, look for a BIOS upgrade from Gigabyte. Also, how did exactly you burn the iso to DVD? I know it's possible to do wrong with Windows burning apps, but not the details. Not this (UEFI): http://fm.no-ip.com/SS/Suse/YaST/150/150-UEFImenu.jpg -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/12/2019 04:52 PM, Felix Miata wrote:
The Gigabyte logo splash screen, shown right after power up, shows only briefly and does show a couple of function key menu options and it also tells the user to use the Del key to access the BIOS settings. That's when you need your finger on the F12 key. When it goes right, you get this (MBR/Legacy): http://fm.no-ip.com/SS/Suse/YaST/150/150-BIOSmenu.jpg
Thanks Felix! That did the trick. I was able to select the right version of the DVD drive to boot from the choices (non UEFI) and was able to proceed and complete the installation of a new OpenSuSE 15.0. GIGABYTE sure does not give one much time to hit that F12 key or even display the message telling you that is an option. I have simply ignored it in the past because it just blinks on then almost immediately goes off.... There was only one additional hiccup but I have seen it before in the past and was able to solve it also. After I did the installation and the system rebooted the GRUB menu did show me all the versions of OpenSuSE that I could choose from to boot up (in different partitions) I chose of course the new version of OpenSuSE that I had just installed and it booted up just fine. I then had it get all the updates from the repositories and then I rebooted again. This time however the GRUB menu only gave me one choice for booting up, just the version of OpenSuSE15.0 that I had just installed. The other choices for the past versions of OpenSuSE were gone. So I went ahead and booted the new system up, then went into the YaST Bootloader app and had it rebuild the GRUB menus making sure it probed for all OS's. And that worked. Like I said I have seen that before so there is a bug somewhere that causes the GRUB installer to lose the entries in the menu for other OS's. Marc... -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Marc Chamberlin composed on 2019-01-12 13:46 (UTC-0800):
"Missing device for /boot/efi with size equal or bigger than 256MiB and filesystem vfat."
Two distinct points about this statement: 1-Missing: such device is only necessary when (U)EFI is or is to be the boot environment. 2-256M: Result of broken installation program. Those proceeding to use UEFI can ignore the claim unless in an as yet unreported actual circumstance described e.g. on: <https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions> If you are not using storage with both logical and physical sector size 4K (4K but not Advanced Format), there is no applicable 256M requirement in the specifications. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/01/2019 22.46, Marc Chamberlin wrote:
I am in the process of trying to upgrade one of my computers to OpenSuSE 15.0 and running into a number of problems. I first started with OpenSuSE42.3 x64 with the KDE/Plasma desktop, and I tried to do an in place straight upgrade. I will also mention that my OpenSuSE42.3 system had something broken with the network drivers so I did not have access to the internet directly from it. So I used my laptop to download the OpenSuSE 15.0 iso file and burned it to a DVD. I mention this because I am suspicious that this may be what is causing me some of the problems I am experiencing, though I do not understand why that should be the case.
Ok...
After my first attempt to upgrade my computer to 15.0 it failed to boot. My research lead me to discover that the installer had changed the grub configuration so that it was trying to make calls to linuxefi and initrdefi. I don't use the efi filesystem on this computer and have no desire to do so. (don't get me started on how much troubles I have had with efi. I use it on my laptop only because I am using solid state drives and it seems that I must use efi on it.) My BIOS in the computer I am trying to upgrade has EFI turned off and only uses legacy file management. So I manually edited the grub configuration file and removed the efi suffix of these calls, i.e. made calls to linux and initrd instead, and the boot up succeeded.
Strange, but ok, understood.
However, that lead me to another mess, after logging in to my account, I discovered the KDE/Plasma desktop was not working properly. I had a few konsole windows that opened up (ones I had left open when I brought the system down) but the plasma part of the desktop was not there. No background, no kicker bar, no mouse activity or the ability to right click and bring up the pop up menu dialog etc. In other words almost useless, although all the services and background tasks I have configured to run started up fine. (things like Apache, Tomcat, Bind, DHCPD etc.) I don't know how to recover from this mess, I tried reinstalling all the KDE and Plasma packages but no joy, so I decided to try a different approach -
At this point you should just have created a new user and login as him instead. Seeing that you have not yet formatted this partition, you can still try.
My next attempt was to install OpenSuSE 15.0 into a new/separate partition but I cannot get past the partitioner. It appears it is trying to force me into using the EFI boot system.
I don't know what is used to decided bios/uefi, but it is doing the wrong detection. And I don't know how to change it either.
I don't allow the OpenSuSE installer's partitioner to decide for me (it's defaults) how to configure my system as it makes choices that I don't want. Instead I have it import all my mount points that I have defined in what was my OpenSuSE42.3 (now upgraded to a broken 15.0) system. That much works fine and I just move the mount point for / to a new partition so that the new OpenSuSE15.0 system will be mostly installed in a different partition and I can keep my old system for the time being.
Ok...
However when I tell the partitioner to accept all the new changes I get a complaint - "Missing device for /boot/efi with size equal or bigger than 256MiB and filesystem vfat." Why am I being forced into using EFI? My system/BIOS is configured to use the legacy boot loaders and explicitly turns off EFI! I cannot find any means of telling the OpenSuSE installer/partitioner to use the legacy method of boot loading either, so I am stuck.
Maybe go ahead as it wants, then later install grub your way.
I have one other complaint about the OpenSuSE 15.0 installer/partitioner that I want to pass along as it almost destroyed my entire system, had I not caught it. After I told the partitioner to import all my mount points from my previous system, I fortunately observed that it had marked ALL of my mount point partitions to be formatted!!! That is just plain wrong, the user should NEVER have to opt out of having data destroyed, but have to opt in to having anything formatted. That modus operandi really needs to be reversed, formatting of any partition should never be done by default. I will listen to any arguments to the contrary but I feel pretty strongly that this should be reported as a bug and fixed. (I am willing to do so.)
AFAIK, it was reported and ignored. I can't find the report, but it was said to be intentional, that a new install needs a clean slate. This is wrong, IMO, the previous YaST partitioner did a better effort at what needed to be formatted and what not. /home, for instance, was not, while "/" was. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 01/12/2019 05:35 PM, Carlos E. R. wrote:
However, that lead me to another mess, after logging in to my account, I discovered the KDE/Plasma desktop was not working properly. I had a few konsole windows that opened up (ones I had left open when I brought the system down) but the plasma part of the desktop was not there. No background, no kicker bar, no mouse activity or the ability to right click and bring up the pop up menu dialog etc. In other words almost useless, although all the services and background tasks I have configured to run started up fine. (things like Apache, Tomcat, Bind, DHCPD etc.) I don't know how to recover from this mess, I tried reinstalling all the KDE and Plasma packages but no joy, so I decided to try a different approach - At this point you should just have created a new user and login as him instead. Seeing that you have not yet formatted this partition, you can still try.
Hi Carlos and thanks for your thoughts... I tried to create a new user and login is him but not joy, it results in a total black screen that is unresponsive to anything other than having an active mouse cursor. Right clicking fails to bring up the context menu either. So something is hosed at the system level and not allowing plasma things to run. The only thing that saves me in my own account is that I have been leaving some konsole windows open whenever I exit or reboot the system. Those get reopened whenever I log back in to my own account so at least I have shell access then and can run stuff from the command line. Marc.. -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/01/2019 20.15, Marc Chamberlin wrote:
On 01/12/2019 05:35 PM, Carlos E. R. wrote:
However, that lead me to another mess, after logging in to my account, I discovered the KDE/Plasma desktop was not working properly. I had a few konsole windows that opened up (ones I had left open when I brought the system down) but the plasma part of the desktop was not there. No background, no kicker bar, no mouse activity or the ability to right click and bring up the pop up menu dialog etc. In other words almost useless, although all the services and background tasks I have configured to run started up fine. (things like Apache, Tomcat, Bind, DHCPD etc.) I don't know how to recover from this mess, I tried reinstalling all the KDE and Plasma packages but no joy, so I decided to try a different approach - At this point you should just have created a new user and login as him instead. Seeing that you have not yet formatted this partition, you can still try.
Hi Carlos and thanks for your thoughts... I tried to create a new user and login is him but not joy, it results in a total black screen that is unresponsive to anything other than having an active mouse cursor. Right clicking fails to bring up the context menu either. So something is hosed at the system level and not allowing plasma things to run. The only thing that saves me in my own account is that I have been leaving some konsole windows open whenever I exit or reboot the system. Those get reopened whenever I log back in to my own account so at least I have shell access then and can run stuff from the command line.
I would suggest doing a "zypper dup" on it, but you said you have network problems :-( Run one of these: rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \ %{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \ %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}\n" \ | sort | cut --fields="2-" --delimiter=\; \ | tee rpmlist.csv | less -S (for importing on spreadsheet) or rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist | less -S (for visual inspection) It is a complete list of packages, sorted by installation date. Search from the start to find out if you have old packages, packages that were not upgraded to the new version. You have to manage upgrading those somehow. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 01/13/2019 12:32 PM, Carlos E. R. wrote:
On 13/01/2019 20.15, Marc Chamberlin wrote:
On 01/12/2019 05:35 PM, Carlos E. R. wrote:
However, that lead me to another mess, after logging in to my account, I discovered the KDE/Plasma desktop was not working properly. I had a few konsole windows that opened up (ones I had left open when I brought the system down) but the plasma part of the desktop was not there. No background, no kicker bar, no mouse activity or the ability to right click and bring up the pop up menu dialog etc. In other words almost useless, although all the services and background tasks I have configured to run started up fine. (things like Apache, Tomcat, Bind, DHCPD etc.) I don't know how to recover from this mess, I tried reinstalling all the KDE and Plasma packages but no joy, so I decided to try a different approach - At this point you should just have created a new user and login as him instead. Seeing that you have not yet formatted this partition, you can still try.
Hi Carlos and thanks for your thoughts... I tried to create a new user and login is him but not joy, it results in a total black screen that is unresponsive to anything other than having an active mouse cursor. Right clicking fails to bring up the context menu either. So something is hosed at the system level and not allowing plasma things to run. The only thing that saves me in my own account is that I have been leaving some konsole windows open whenever I exit or reboot the system. Those get reopened whenever I log back in to my own account so at least I have shell access then and can run stuff from the command line. I would suggest doing a "zypper dup" on it, but you said you have network problems :-(
Run one of these:
rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \ %{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \ %{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}\n" \ | sort | cut --fields="2-" --delimiter=\; \ | tee rpmlist.csv | less -S
(for importing on spreadsheet)
or
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist | less -S
(for visual inspection)
It is a complete list of packages, sorted by installation date. Search from the start to find out if you have old packages, packages that were not upgraded to the new version. You have to manage upgrading those somehow.
Hi Carlos and thanks again for your thoughts... I have managed to solve the network problem I was having, (bad NIC) so I have network capabilities back. I went ahead and did the zypper dup and it did install/replace a bunch of stuff but unfortunately still no joy getting the plasma part of the desktop working. This makes it seem like some sort of configuration issue and not bad or missing files, but I am not an expert on KDE/Plasma so I am only guessing... Marc.. -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/13/2019 11:15 AM, Marc Chamberlin wrote:
At this point you should just have created a new user and login as him instead. Seeing that you have not yet formatted this partition, you can still try.
Hi Carlos and thanks for your thoughts... I tried to create a new user and login is him but not joy, it results in a total black screen that is unresponsive to anything other than having an active mouse cursor. Right clicking fails to bring up the context menu either. So something is hosed at the system level and not allowing plasma things to run. The only thing that saves me in my own account is that I have been leaving some konsole windows open whenever I exit or reboot the system. Those get reopened whenever I log back in to my own account so at least I have shell access then and can run stuff from the command line.
Hi Marc, I have no idea if this is your problem, but I've regularly seen situations where two directories in a user's home directory become owned by root. These are ~/.cache ~/.dbus I've seen it happen when I create a new user, the symptoms are a black screen with the cursor that can be moved by the mouse. Nothing else works. The fix has been to login as root and do a "chown -R username.users /home/username/.dbus" and again with .cache. I have no idea why this happens, but it's been a fairly regular occurrence for me since the start of the Leap series. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/13/2019 01:56 PM, Lew Wolfgang wrote:
Hi Marc,
I have no idea if this is your problem, but I've regularly seen situations where two directories in a user's home directory become owned by root. These are
~/.cache ~/.dbus
I've seen it happen when I create a new user, the symptoms are a black screen with the cursor that can be moved by the mouse. Nothing else works. The fix has been to login as root and do a "chown -R username.users /home/username/.dbus" and again with .cache. I have no idea why this happens, but it's been a fairly regular occurrence for me since the start of the Leap series.
Regards, Lew
Hi Lew, thanks for piping in with your thoughts also! ;-) I checked those two directories and they (and their contents) are owned by me - marc:users Because I am mounting /home (it is in it's own partition) under both the old version of OpenSuSE15 that I upgraded in place, from OpenSuSE 42.3, and in the new version of OpenSuSE15 that I just installed, I don't think the issue is caused by anything in my home directories. They all work fine in the new version of OpenSuse15, but fail in the version I upgraded. Marc... -- Linux Counter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14/01/2019 00.21, Marc Chamberlin wrote:
On 01/13/2019 01:56 PM, Lew Wolfgang wrote:
Hi Lew, thanks for piping in with your thoughts also! ;-) I checked those two directories and they (and their contents) are owned by me - marc:users Because I am mounting /home (it is in it's own partition) under both the old version of OpenSuSE15 that I upgraded in place, from OpenSuSE 42.3, and in the new version of OpenSuSE15 that I just installed, I don't think the issue is caused by anything in my home directories. They all work fine in the new version of OpenSuse15, but fail in the version I upgraded.
Then some package is missing/wrong, or some configuration is wrong. I'm not familiar with Plasma nuances, though. Only that it is touchy. Can you try with another desktop type? Try XFCE. Perhaps in YaST click again to install the complete patterns pertaining to Plasma. How about your video card? I have Nvidia, and initially it would not work when I upgraded to 15.0. I reinstalled and fidled about, till I noticed that some package in the nvidia repo was not installed, probably a new one, so that it could not have been upgraded. I installed that one and I had graphics back. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (4)
-
Carlos E. R. -
Felix Miata -
Lew Wolfgang -
Marc Chamberlin