[yast-devel] broken GUI installer
Trying to GUI HTTP install from Factory right now everywhere I hover in a select list is nothing but black. Gfxchip is mga g550. Target is multiboot P4 system with 10.2 and 11.4 working normally. After completing expert partitioning and boot loader installation configuration, clicking the section management tab produces "UI Syntax Error. No widget with ID 'inst-proposal-progress' Check the log file!." Prior bootloader choices included Grub Legacy, propose new configuration, 15 second timeout, and deselecting all options except boot from root partition. After clearing the popups, clicking the add button produces no response. Clicking cancel wants to abort everything. Clicking install wants to proceed as if software installation had been performed, yet it hadn't been. There is not back button. Logs: http://fm.no-ip.com/Tmp/SUSE/y2l20140429-a865.tgz -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Tue, 29 Apr 2014 22:13:08 -0400 Felix Miata <mrmazda@earthlink.net> wrote:
Trying to GUI HTTP install from Factory right now everywhere I hover in a select list is nothing but black. Gfxchip is mga g550. Target is multiboot P4 system with 10.2 and 11.4 working normally.
After completing expert partitioning and boot loader installation configuration, clicking the section management tab produces "UI Syntax Error. No widget with ID 'inst-proposal-progress' Check the log file!." Prior bootloader choices included Grub Legacy, propose new configuration, 15 second timeout, and deselecting all options except boot from root partition. After clearing the popups, clicking the add button produces no response. Clicking cancel wants to abort everything. Clicking install wants to proceed as if software installation had been performed, yet it hadn't been. There is not back button.
Hi Felix, thanks for reporting. I investigate code where it happen and something is strange with mount points. Arvin: Can you check logs as it looks like Storage.GetMountPoints returns as one key Hash instead of String, so bootloader report error. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 30.4.2014 11:26, Josef Reidinger wrote:
Hi Felix, thanks for reporting. I investigate code where it happen and something is strange with mount points.
Bugzilla seems to be better place for bugs. And it's already there, isn't it? Thanks Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2014-04-30 11:57 (GMT+0200) Lukas Ocilka composed:
Josef Reidinger wrote:
thanks for reporting. I investigate code where it happen and something is strange with mount points.
Bugzilla seems to be better place for bugs. And it's already there, isn't it?
The first problem with Bugzilla is people don't always make summaries that are readily related to the problem observed, often putting some cryptic string in place of real description. I didn't find anything either about hover, or about loader + unfixed matching my observation/experience. The second problem is Factory isn't entirely about latest, and one must either remember or guess whether and what isn't current in it in order to decide whether the observed problem isn't stemming from something several versions old and thus most likely known about already, or known to be a build or other transitory problem that might be gone in a matter of hours or a day. So, reporting/asking here e.g. is a way to find out whether it may be recognized as something new, particularly with this Ruby rebuilding of YaST and its dedicated mailing list. FWIW, notwithstanding bugs, I liked the pre-Ruby installation YaST very much, far and away more than any other OS installer ever used, and am not particularly pleased with the installation simplification changes observed so far. Also, I'm particularly unhappy that 13 month old https://bugzilla.novell.com/show_bug.cgi?id=663749 has not been implemented, which wouldn't even be needed if there was a checkbox to say new bootloader is or is not to be the master bootloader (aka stanzas for any but new OS desired or necessary). -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, 30 Apr 2014 06:53:24 -0400 Felix Miata <mrmazda@earthlink.net> wrote:
On 2014-04-30 11:57 (GMT+0200) Lukas Ocilka composed:
Josef Reidinger wrote:
thanks for reporting. I investigate code where it happen and something is strange with mount points.
Bugzilla seems to be better place for bugs. And it's already there, isn't it?
The first problem with Bugzilla is people don't always make summaries that are readily related to the problem observed, often putting some cryptic string in place of real description. I didn't find anything either about hover, or about loader + unfixed matching my observation/experience.
The second problem is Factory isn't entirely about latest, and one must either remember or guess whether and what isn't current in it in order to decide whether the observed problem isn't stemming from something several versions old and thus most likely known about already, or known to be a build or other transitory problem that might be gone in a matter of hours or a day. So, reporting/asking here e.g. is a way to find out whether it may be recognized as something new, particularly with this Ruby rebuilding of YaST and its dedicated mailing list.
mailing list live for a long time and this problem is not related to YaST in ruby. Actually 13.1 installer use ruby, so if you cannot observe it in 13.1 then it is not related to ruby conversion.
FWIW, notwithstanding bugs, I liked the pre-Ruby installation YaST very much, far and away more than any other OS installer ever used, and am not particularly pleased with the installation simplification changes observed so far.
well, no one is always satisfied. But if you convince enough people that it make sense for opensuse and someone is willing to do it, it is possible to make it configurable in control file for opensuse, that there is richer configuration in installation.
Also, I'm particularly unhappy that 13 month old https://bugzilla.novell.com/show_bug.cgi?id=663749 has not been implemented, which wouldn't even be needed if there was a checkbox to say new bootloader is or is not to be the master bootloader (aka stanzas for any but new OS desired or necessary).
There is three reasons why it is not implemented: 1) it have problem with edit button, as it is tricky to edit more items at once 2) it do not have enough priority, if you convince some from opensuse release team and! we have time ( so suse sponsor work) or there is code change from someone which we can just review, then it can be implemented 3) plan is to move forward to grub2 as we have even trouble with one bootloader and for two, it multiple number of issues we have and for the most people working bootloader is more important then plenty of choices. Of course always is possible to do it manually with none bootloader and then install it yourself outside of installer. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2014-04-30 13:26 (GMT+0200) Josef Reidinger composed:
There is three reasons why it is not implemented: 1) it have problem with edit button, as it is tricky to edit more items at once
The problem would be greatly reduced by not moving selection to top of list at end of each edit or delete process. The top entry, default for new installation, seems to me like it would be the one least likely of need to add, edit or delete. Why is it jumped to on each screen refresh? You might get more test installations out of testers by considering more the annoyances attributable to testers of alphas and betas rather than focusing on those who only install once per GA. I very often shortcut to avoid installation annoyances by cloning, then using zypper to upgrade. IIRC, no more than two of my 14 current Factory installations were "installed", maybe less than two. The rest are zypper'd 13.1s, probably most of which were 12.3 before, and maybe 12.2 before that. #14 I did last night, not for to avoid YaST, but because of the brokenness that caused me to start this thread. The whole process, including removing HD from one puter, installing HD in the target, booting it, making the clone, putting the HD back where it came from, adjusting volume label, UUID, menu.lst & fstab on the clone, setting up Grub Legacy on the clone, and booting the "new" installation didn't even take 12 minutes. On new installations I spend far more time than that just in software selection (not a bad thing of itself, as other installers don't even present the opportunity for such welcome detail). -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
В Wed, 30 Apr 2014 06:53:24 -0400 Felix Miata <mrmazda@earthlink.net> пишет:
Also, I'm particularly unhappy that 13 month old https://bugzilla.novell.com/show_bug.cgi?id=663749 has not been implemented,
grub2 defaults to os-prober disabled with exact the same result as requested - only entries for current OS are present in menu.
which wouldn't even be needed if there was a checkbox to say new bootloader is or is not to be the master bootloader (aka stanzas for any but new OS desired or necessary).
This could relatively easy be implemented by allowing no "status location" in bootloader dialog. This would avoid physically installing bootloader while still generating all needed files. Actually, I believe at least for grub2 this may work already - pbl just loops over locations and installs on each one; if no location is selected, it should do nothing. I'm just not sure whether YaST/glue libraries support it. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2014-05-01 03:59 (GMT-0400) Andrey Borzenkov composed:
÷ Wed, 30 Apr 2014 06:53:24 -0400 Felix Miata composed:
Also, I'm particularly unhappy that 13 month old https://bugzilla.novell.com/show_bug.cgi?id=663749 has not been implemented,
grub2 defaults to os-prober disabled with exact the same result as requested - only entries for current OS are present in menu.
I wouldn't know what Grub2 under openSUSE does. As long as any installer offers an option to install Grub Legacy, that's what I choose. When given only the choices no bootloader at all or Grub2, I choose no bootloader at all. I'm sure I'm not the only one who prefers the simplicity of the vastly lighter weight Grub that never complains about reliability when it can't commandeer the boot track, and never declares on boot that the perfectly valid vga= cmdline option for gfxchips lacking KMS support is deprecated. As such times as I want to know about Grub2, I boot *buntu (which is almost the only use I ever have for *buntu, or any Debian for that matter). So, I am familiar enough with Grub2 to know I don't want it replacing Grub Legacy on any system that doesn't require something that Grub Legacy cannot provide. While most users apparently think that YaST is the most important openSUSE standout against competitors, I find openSUSE's Grub Legacy Gfxboot menu another feature without comparison, and a sleeping dog that for most users does not need to be awakened.
which wouldn't even be needed if there was a checkbox to say new bootloader is or is not to be the master bootloader (aka stanzas for any but new OS desired or necessary).
This could relatively easy be implemented by allowing no "status location" in bootloader dialog. This would avoid physically installing bootloader while still generating all needed files. Actually, I believe at least for grub2 this may work already - pbl just loops over locations and installs on each one; if no location is selected, it should do nothing. I'm just not sure whether YaST/glue libraries support it.
Something seems lost in translation. I don't want to have to choose between installation of either no bootloader at all, or installation of a bootloader that wants to be master of all systems installed. I want Grub Legacy on the / partition, and would much prefer for it to get there the same way it has ever since before openSUSE 10.0 was released, via YaST, and with the added simplicity of only the two stanzas that unconditionally make sense for a new installation. I'm certainly capable of managing my own systems' bootloaders without help of scripts or YaST, but to assist over the phone, via email or in web forums I much prefer coaching people through the overall simpler choice that is the senior Grub that only requires two short and simple shell commands to set up, and without even having to mount the target for them to work. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 2014-05-01 11:59 (GMT+0400) Andrey Borzenkov composed:
÷ Wed, 30 Apr 2014 06:53:24 -0400 Felix Miata composed:
Also, I'm particularly unhappy that 13 month old https://bugzilla.novell.com/show_bug.cgi?id=663749 has not been implemented,
grub2 defaults to os-prober disabled with exact the same result as requested - only entries for current OS are present in menu.
I wouldn't know what Grub2 under openSUSE does. As long as any installer offers an option to install Grub Legacy, that's what I choose. When given only the choices no bootloader at all or Grub2, I choose no bootloader at all. I'm sure I'm not the only one who prefers the simplicity of the vastly lighter weight Grub that never complains about reliability when it can't commandeer the boot track, and never declares on boot that the perfectly valid vga= cmdline option for gfxchips lacking KMS support is deprecated. As such times as I want to know about Grub2, I boot *buntu (which is almost the only use I ever have for *buntu, or any Debian for that matter). So, I am familiar enough with Grub2 to know I don't want it replacing Grub Legacy on any system that doesn't require something that Grub Legacy cannot provide. While most users apparently think that YaST is the most important openSUSE standout against competitors, I find openSUSE's Grub Legacy Gfxboot menu another feature without comparison, and a sleeping dog that for most users does not need to be awakened.
which wouldn't even be needed if there was a checkbox to say new bootloader is or is not to be the master bootloader (aka stanzas for any but new OS desired or necessary).
This could relatively easy be implemented by allowing no "status location" in bootloader dialog. This would avoid physically installing bootloader while still generating all needed files. Actually, I believe at least for grub2 this may work already - pbl just loops over locations and installs on each one; if no location is selected, it should do nothing. I'm just not sure whether YaST/glue libraries support it.
Something seems lost in translation. I don't want to have to choose between installation of either no bootloader at all, or installation of a bootloader that wants to be master of all systems installed. I want Grub Legacy on the / partition, and would much prefer for it to get there the same way it has ever since before openSUSE 10.0 was released, via YaST, and with the added simplicity of only the two stanzas that unconditionally make sense for a new installation. I'm certainly capable of managing my own systems' bootloaders without help of scripts or YaST, but to assist over the phone, via email or in web forums I much prefer coaching people through the overall simpler choice that is the senior Grub that only requires two short and simple shell commands to set up, and without even having to mount the target for them to work. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (4)
-
Andrey Borzenkov -
Felix Miata -
Josef Reidinger -
Lukas Ocilka