Install does not finish on Windows 7 Home Premium



  • I cannot install Vivaldi latest build 105 (previous built either) on Windows 7 Home Premium. I can see in Systernals Process Monitor that the installer stops at the attempt to access some registry entry related with timezone - as per the screenshot below. The installer falls into an infnite loop trying to access this missing entry every 30s. [img]https://vivaldi.net/media/kunena/attachments/15783/Cannotfindregistryentry.png[/img] I checked with Registry Editor that this entry is indeed non-existent. Any workaround to get Vivaldi installed? Should I submit a bug report? Attachments: [img]https://forum.vivaldi.net/uploads/attachments/15783/Cannotfindregistryentry.png[/img]



  • It says something about Central European Standard Time - I take it that is your timezone? Here in the US Eastern timezone it installed fine. Not that I know why the installer should care about the time zone …

    The picture is too small for me to make out anything else.



  • Yes, this is my timezone, CET. Only the last part of the registry key does not exist - "Dynamic DST".
    Vivaldi installed on my other computer with Windows 7 (but probably Proffessional) so I don't have an idea what is special about setup of this one. And like you, I do not understand why installer bothers so much about timezone that cannot skip this step.
    The screenshot seems readable enough for me. There is nothing more to show than you have read.



  • I have installed Vivaldi also under W7x64 Home without problems. But I used the "Advanced " button and installed it as standalone version. Maybe you want to try out this.



  • @Ralf-Brinkmann:

    I have installed Vivaldi also under W7x64 Home without problems. But I used the "Advanced " button and installed it as standalone version. Maybe you want to try out this.

    I also used advanced option - good point - so just to add, I used the Standalone option. Other options also do not finish installing properly, though I would need to check if they got stuck in the same place.

    @RRR13:

    @wojcieche:

    Should I submit a bug report?

    Absolutely!
    You seem to have gathered some useful info about the issue too, so that would be useful for the developers.

    Yup, that I know, thank you. ;) I was actually expecting either the opposite reply or none. :P This was a rather common question on Opera forum, before submitting a bug report, to avoid duplicate reports if the issue was already known. Sometimes Opera developers replied on the forum whether they need it submitted or they are already working on it. So that was actually the intention. If I do not get any further responses soon, I will submit the bug report.

    Also any idea for workaround of this issue would be helpful. Thank you.



  • @wojcieche:

    Also any idea for workaround of this issue would be helpful. Thank you.

    Unpack the installer it with 7zip or winrar , then copy the folder vivaldi-bin

    to C:\Users{your-username}\AppData\Local and rename it as vivaldi

    Then create a link from vivaldi.exe to your desktop / start menu /quick launch / whatever you prefer, to launch the program w/o dig in to the long path.



  • Generally true, but Vivaldi is a small company and QA people to go through all the bug reports do cost money (pay and benefits) … if you actually want them to succeed then you should do what you can to make their work easier.



  • @sgunhouse:

    … Vivaldi is a small company and QA people to go through all the bug reports do cost money (pay and benefits) ... if you actually want them to succeed then you should do what you can to make their work easier.

    That seems to raise the question: how can we as users best help Vivaldi with observed bugs? I've seen a fair number of "problem" discussions on one topic embedded within other unrelated thread topics since Vivaldi was released. Whether any of those resulted in bug reports is hard to say… and there's little way that anyone outside the thread would realize they were even there. (Just look at the subject of this thread vs. the last few posts on bug/problem reporting!) Likewise, I've seen multiple forum threads and posts on the same problem. Then there are the comments sections over in the developer blogs, which may duplicate much said in this forum. And of course, there stands the bug reporting tool itself...

    So, while users certainly ought to carefully scan this forum for topic titles that relate to their own issues and post within those where possible, brief titles all too often don't capture the essence of a topic sufficiently to match up with a user's own problem. Likewise, topics may start out relating to problems in one version that are patched in a follow-up version, yet a user runs into something similar in a still later version.

    What is the "officially" recommended path to follow for users to report or discuss "problems" they have, which may or may not rise to "bug" level, and which may conceivably have also have been described elsewhere in one or a variety of ways? Should the users assume that just because they happened to see something like their problem discussed in an existing thread, it has been bug-reported or otherwise come to the attention of the devs? I think this is the dilemma and source of confusion many of us experienced over in the Opera forums and which we see recurring here... and perhaps it's just the nature of things. But it would be good to hear some specific, recommended direction for how users should deal with all this in order to best help Vivaldi to keep efficient responsiveness to user-observed problems.



  • Not being "official" I really couldn't say.. Though I do have the benefit of being able to search for bugs, and being on the mailing list.

    Personally, I don't file bug reports if the issue is related to a specific site or page. They need to be able to duplicate the issue, so I try to find more than one example or what about that example causes the issue. Likewise when trying to duplicate issues posted in the forums, I'll try to figure out what it is about the example that causes the issue. If it is only that page/site I may just chalk it up to bad web design. Once I know how to duplicate the issue, then I'll file a report.



  • I do post example pages (if the bug only happens on certain pages), even though by the time I post it I'll know more than one.

    And keep in mind, pages they can't access do them no good. A bug you only see after you log in to your bank's website is one they can't identify, since they can't get there.

    I'm not a web designer, barring something obvious I don't really know if a bug that shows up on a specific page is bad design or a browser issue. That's why I don't report bugs seen in a page until I can find them somewhere else. But yes, that's me.



  • @The_Solutor:

    @wojcieche:

    Also any idea for workaround of this issue would be helpful. Thank you.

    Unpack the installer it with 7zip or winrar , then copy the folder vivaldi-bin

    to C:\Users{your-username}\AppData\Local and rename it as vivaldi

    Although the idea is good, it does not work from another reason. After a second thought and look on the screenshot in the original post, installer does finish its work, but Vivaldi browser does not start. Therefore even if I unpack the browser this way, it stil does not start from the same reason as described - no registry entry.
    More interestingly, some timezone's registry keys have the "Dynamic DST" subkey. But even when I changed timezone in my Windows to that one, Vivaldi found the registry entry of the timezone, but still Vivaldi launch was stuck, did not progress.

    Nevertheless thank you for the tip that may become useful some other time.



  • Bug report submitted.



  • @Blackbird:

    What is the "officially" recommended path to follow for users to report or discuss "problems" they have, which may or may not rise to "bug" level (…)?
    Should the users assume that just because they happened to see something like their problem discussed in an existing thread, it has been bug-reported or otherwise come to the attention of the devs?

    Starting from your second question above - the good practice on Opera's forums was that when the discussed problem was reported, the reporting person (usually the original poster / thread founder) informed in a thread that he reported the bug - for all readers to know. He also provided the bug number for reference but I can see Vivaldi bug tracker does not provide this information. Still I find it reasonable to continue with this practice, like I did above.

    Regarding your first question and all the doubts, it is rather impossible to define one procedure to follow, which would be best for everyone. Different people are willing to spend different amounts of effort on reporting problems/bugs they encountered.
    If the procedure would be set to maximize user effort and minimize developer's effort, then only you and a small group of dedicated people, willing to spend a considerable amount of time on proper bug analysis and reporting would follow it, most would still report them in variety of ways all over the place. But while streamlining the process is helpful, this is not bad either - if some problem is popular and reported all over the place by many users, it will be surely easily noticed by developers and fixed.

    If you are looking for tips and best practices how to help Vivaldi developers in the most effective way for them, the first step is surely to search the problem on a forum - if the problem is already discussed and has it been reported already.
    In case you do not find it, create a new thread to put the problem for public review. It is a sanity check, which will either help you resolve the problem without need to submit a bug report or else it will allow reporting the bug in more precise way, with more details which will come up during forum discussion. Such bug report will surely be much more mature and valueable than if it was reported immediately after you noticed the problem. You just need to allow some time to come up with some ideas and figure out the specifics of the problem, workarounds. Reporting more precise details will be beneficial for Vivaldi developers.

    This thread is a good confirmation of correctness of the above advice - it seemed to me that it was a problem with the installer, but after the discussion and some time for analysis, I figured out that installer is fine and that is a problem with a browser itself. This way I avoided submitting a bug report with a misleading title.

    Of course when you create a forum thread, its subject is critical, so do spend a moment to make it describe the problem adequately.

    Lastly, you can also highlight some problem in the comment to the blog post of the Vivaldi team blog about release of the new snapshot. But I would appeal to not abuse it - it would be most suitable to highlight to developers in this way primarily the problems which are regressions from previous version or major bugs.



  • @wojcieche:

    @The_Solutor:

    @wojcieche:

    Also any idea for workaround of this issue would be helpful. Thank you.

    Unpack the installer it with 7zip or winrar , then copy the folder vivaldi-bin

    to C:\Users{your-username}\AppData\Local and rename it as vivaldi

    Although the idea is good, it does not work from another reason. (…)
    Nevertheless thank you for the tip that may become useful some other time.

    And this is the time the tip occured to be very helpful.
    While the instaler fails both for the 32-bit and newly introduced 64-bit version in build 111, when I unpacked the 64-bit version, it launched! The 32-bit version still does not run on my system. I forgot to mention before it is 64-bit version of Windows 7.

    I guess I will need to provide another brand new bug report, considering I have no Bug No. of the one already submitted or the way to add any information to it…



  • What would you do if you did know the bug number? The one you created on the 21st is VB-3757 …


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.