I just installed openSUSE 13.2 milestone 0 KDE 32-bit, DVD iso burned to a USB stick. Formatted /, reused /home from 13.1. I started the install and wandered away. On returning, the system was waiting to boot from the hard disk. When it did, it was a normal log-in, not a second phase for device configuration like I always got with previous version installations.
Kinfocenter reports the system as:
Linux 3.14.0-rc5-1-desktop
openSUSE 13.2 Milestone 0 (Harlequin) (i586)
KDE 4.12.2
YaST is very broken.
Is this the design installation now for milestone 0, only one phase? Or did something go past while I was not looking?
No, it’s not very broken at all AFAICS.
YaST has been freshly ported to Qt5, so there might be issues, yes. But it should work.
The most obvious and critical problem at the moment (and I think that’s what you’re referring to) is that libproxy-config-kde4 and libqdialogsolver1 use Qt4 and therefore make YaST crash when they are installed.
To circumvent this, just uninstall those 2 packages (libqdialogsolver1 shouldn’t be installed by default anyway).
Is this the design installation now for milestone 0, only one phase? Or did something go past while I was not looking?
No idea, could be. I don’t really remember, my last Factory installation was 2 weeks ago already…
Well, if your system is working, everything must have gone according to plan, no?
But have you tried to switch to NetworkManager?
Network Manager was used by default, with a very different interface from 13.1. It shows wireless enabled, and our network ID, but will not connect. YaST hardware information reports the wireless card as
net interface: name = wlp4s2, path = /class/net/wlp4s2
type = 1
carrier = 0
hw_addr = 00:13:ce:d4:8d:57
net device: path = /devices/pci0000:00/0000:00:1e.0/0000:04:02.0
net driver: name = ipw2200, path = /bus/pci/drivers/ipw2200
ethtool private flags: 0
When I tried to start Network Settings in YaST, both text and GUI, it popped up a window saying “Internal error. Please report a bug.”
Right, that’s the new plasma-nm, which is already included in 13.1 but not installed by default there, as it still was a pre-release version.
It shows wireless enabled, and our network ID, but will not connect. YaST hardware information reports the wireless card as
net interface: name = wlp4s2, path = /class/net/wlp4s2
type = 1
carrier = 0
hw_addr = 00:13:ce:d4:8d:57
net device: path = /devices/pci0000:00/0000:00:1e.0/0000:04:02.0
net driver: name = ipw2200, path = /bus/pci/drivers/ipw2200
ethtool private flags: 0
Hm. AFAIK intel devices need additional firmware which should be part of the package “kernel-firmware”. So please check if that’s installed.
Other than that I don’t know.
When I tried to start Network Settings in YaST, both text and GUI, it popped up a window saying “Internal error. Please report a bug.”
ipw-firmware - Firmware for Intel PRO/Wireless WLAN Cards was already installed. kernel-firmware was not installed, so it is now, but seemed to make no difference.
I installed milestone0 from the live KDE.
,
The proposed partitioning is too long to read. That’s going to be a problem with “btrfs”. I switched to “ext4” (expert partitioning mode).
It complained that I had not provided “/boot/efi”. That was correct. So I fixed that. And it still made the same complaint.
I told it to proceed anyway. It wanted to use “grub2” for booting. I expect that’s because I first booted the live USB on a non-UEFI box, and it probably saved information in the hybrid partition, and forced that on subsequent boots – I reported a bug about that for 13.1. I switched to grub2-efi, and the install proceeded.
On reboot, Yast told me that auto-configuration had failed and that I should report a bug. I have not reported as of yet, though maybe someone else has reported this by now.
Have installations from live media been done in two stages previously, with reboot in between? Did that happen this time? I’m wondering if my installation from DVD image proceeded with some default settings through a reboot, instead of waiting for user action like I have had on all other recent installations. For instance, with 13.2 ms0, I did not have an opportunity to set host name, which I always could before. Maybe I should start installation again, and stay put to watch progress.
Thanks,
Howard
AFAIR you have to deselect “Automatic configuration” for that.
By default you’re not able to set the host name during a 13.1 install either (I did one yesterday). So that hasn’t really changed.
Installed 13.2 MS0 AMD64 from DVD-media in a VirtualBox session. Works a-ok. Set up NFS-shares, Printer/Scanner (Brother MFC 7360). I haven’t bee able to crash the session testing different set up’s and reboots. Works very well after/installed rdesktop-1.7.1-5.1.1.x86_64 on my PC. ?
What make me hick-up was the suggested partitioning. Brfs may be technically superior as a file system but it doesn’t create a trust for a user when see “suggested partitioned”.
OK, sorry. I just tried a Factory install and that option does not exist any more.
It’s definitely there in 13.1 (and enabled by default, so you cannot set the host name during installation if you don’t change it).
I think it was still there on Factory 2 weeks ago, but I’m not 100% sure now.
I installed again from scratch (13.2 ms0 KDE 32-bit from DVD iso on USB stick) and stayed glued to the screen to watch progress. Installation went through to a reboot and normal log-in, rather than a hardware configuration process after the first reboot. Previous versions had a second installation phase to set up devices like network cards and printers. Have others had the same experience? If this is an on-purpose change, I think it is not for the better.
Howard
In the YaST GUI, Software Repositories section, checking and unchecking the Enabled and Automatically Refresh boxes has no effect on the configuration. The settings can be changed in text-mode YaST.
Is YaST still be actively revised, or is this the sort of bug that should be reported?
I installed M0, this time from the DVD image (via a USB).
This time it worked better than the earlier install from live KDE.
There was no option to disable automatic configuration.
It looks as if the automatic configuration step is now done before the reboot. So there is no final install stage after the reboot.
Here are some problems and/or questions:
Normally, I select “icewm-default”, and that automatically deselects “icewm-lite”. When I tried that for this install, I noticed that both were already selected. This seems to be a change. The installed system does seem to work as “icewm-default” has worked in the past.
After the reboot, I could not login, except as root. I had told it to import users from a previous system. It did that. But it appears to have made up new passwords for those users, without telling me what they were. Did it re-encrypt the encrypted passwords, or what? I was able to login at a command line as root, and fix the password for one user. I could then login to the GUI for that user. I’ll fix the others later.
There was no network. I’m not sure if this is just a first reboot problem, or whether “wicked” is wicked. I switched NetworkManager, and had network.
There was no “/etc/resolv.conf”. I could not resolve hostnames. There now was network, and the IP address came from the DHCP server on the router. So there should have been DNS support. I hastily concocted a temporary “/etc/resolv.conf”, so that I could resolve names.
Yast crashed on software management. I restarted Yast with “–gtk”, and that got it work though I do not like that gtk interface.
Software management wanted to install Plymouth (which I had carefully deselected during install). Do I have to lock that, or go through that for any software update?
Those are my complaints for today. I guess it is time to head to the bugzilla.
