Hello, I recently switched from 13.1 to Tumbleweed and would like to make some remarks - Booting takes a very long time, very much longer than with 13.1 and former versions. The hard disk is running like there is no end to it, longer than a minute, and when the graph working screen comes up, the HD still does not stop; it takes another 20 seconds or so before I can do anything. 13.1 did all that in no more than 20 seconds. - As I do not care for looking at an inert graph screen, in 13.1 I booted showing the text screen (splash=no quiet showopts silent), giving a nice sequence of the files that are loaded. In Tumbleweed I have the same GRUB setting, but I get just a few lines initially and then a black screen for the rest of the booting. However, I seem to belong to a minority, as apparently most prefer the graph booting. - I understand that at booting a lot of services are loaded, apparently many more so than in 13.1, and I suppose that many of them are not necessary ones. However, I miss the possibility to have a look and switch off what I do not need; it would be nice to have something non-command line identical to services.msc under Windows (am I ignorant and is there?) for the non-essential and non-for-this-specific-hardware related ones. Which ones are specifically essential for each individual machine and can not be eliminated can be determined in the installation. That my idea is not so trivial is shown by the advice in https://lizards.opensuse.org/2012/07/26/optimizing-a-boot-time-aka-2-second-... from 2012, although that is quite extreme. - The system user configuration is limited compared to 13.1 - I use the KDE desktop. As there is a lot of vertical separation space between the lines of the menu items, the menu windows got very big (laptop screen!) and have to be rolled up and down. Form before function, but why? - It is funny to have menues and other text items in English and German mixed (e.g. in the main menue: Utilities, Lost and Found, Energieverwaltung/Sitzung). I do speak both, so for me it is no issue. The machine where I installed the Tumbleweed on is a HP Pavilion laptop with dual Opensuse/Windows7 installation. One general remark: When a program goes wrong, e.g. when writing and no access, it hangs and there is no possibility to close it. Cancel only works during normal execution, not when it hangs, and right-clicking in the toolbar and selecting close (hehe, now schließen) neither. There is no sure-working emergency brake for such cases, at least not that I have found. I have experienced this since I first installed Suse, quite some years ago. Great work! Ed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org