Candidate ISO build 1082

rugyada · May 31, 2017, 3:00pm

It was not a blocker either because even if browser opens 3.0 links in the page/s it’s displayed in a visible box “Link to 3.02 …”
Small issue but not a blocker.

Postedit:

The problem of Calamares running in standalone mode (outside of the live system) has returned.

At that time it happened also in VB. I can say I have installed every development ISOs from main ISO menu without any problem.
In real hw instead I have experienced this issue today when finally I made install for testing ISO candidate in hw. As reported. I attached also omv-bug-report log for more complete documentation on my hw.

TPG · May 31, 2017, 3:27pm

@rugyada Nothing bad in your logs.
@Colin how i can reproduce that "The problem of Calamares running in standalone mode (outside of the live system) has returned. " ???

ben79 · June 1, 2017, 4:34pm

What’s meant it that on the ISO “Install” doesn’t work. Calamares window briefly flashes and disappears and after a bit of time system reboots itself. I just double checked this on ISO # 1082 and it’s true “Install” is broken.

Edit: Issues · OpenMandrivaAssociation/distribution · GitHub
Would be excellent if someone could confirm this bug.

ben79 · June 1, 2017, 7:09pm

About KMail see this thread.

ben79 · June 1, 2017, 7:42pm

kdenlive is only thing in Application Launcher I have found to be not working. rugyada was kind enough to file a bug report.

ben79 · June 1, 2017, 7:57pm

This bug report indicates that nvidia kernel modules aren’t building. Seems like this may be the only blocker I’m aware of. If it is a blocker?

Anyway sure wish this could be fixed before public release of Lx 3.02.

Full disclosure: I don’t have nVidia hardware so can’t confirm or help on this one. But if nVida users find this to be an issue need to let us know before release not after…

TPG · June 1, 2017, 8:06pm

This bug report is not from running iso in live mode.
Iso does not carry nvidia proprietary drivers, so that bug is not related to Iso.

Anyways situation is the same like couple months ago. Nobody cares to make a release, good proof is that QA did not even prepared an announcement.
I’d say that lack of announcement and promotion on social medias is a REAL blocker.
@Qa Still not ready to get things together and make things professional to be able to have releases each 3 months?

ben79 · June 1, 2017, 8:22pm

Um, really. It sounds like your saying only the ISO matters and is to be tested. That how a system installed from the ISO performs isn’t a relevant part of testing and Quality Assurance? I strongly with prejudice disagree. If what you say is correct I don’t want to be a tester any more.

kdenlive crashes exactly the same in ‘Live’ as it does in an installed system. Seems like a valid bug to me.

I think our users with nVidia hardware might prefer that nvidia kernel modules actually build. But I seem to be in error on a number of things here…

I’m done testing for now.

Edit: Ever post something on the internet and wish you could take it back. Well that last sentence probably should have gone unsaid. Apologies.

rugyada · June 1, 2017, 8:27pm

Sorry, not sure to fully understand what it means.
Btw this is from live mode.

That’s not fair…

good proof is that QA did not even prepared an announcement.
I’d say that lack of announcement and promotion on social medias is a REAL blocker.

I sent to Council a link to a raw draft asking for further inputs. I’d like to make a great announcement.

ben79 · June 1, 2017, 9:01pm

Please check your e-mail for one titled “OpenMandriva Lx 3.02 announcement draft”.

Edit: And note the date sent.

ben79 · June 1, 2017, 9:41pm

I think the overall quality of ISO 1082 is very good. Our developers have done an excellent job with a specific mention of all the work done by TPG. Thanks, much appreciated in this corner.

My disappointment (above in post 28 I think) is 'cause I’ve been busting my rear end today to check some things and try to mention before public release not just things that need to be fixed but also things that could be fixed before public release. I thought this was what QA was supposed to do. You know to make the overall quality of release as high as we possibly can.

I never have been aware of a rule that testing was to be done only in ‘Live’ ISO. I’ve been laboring under the perception that we were to test both the ISO, ‘Live’, ‘Install’, and ‘Basic Graphic Mode’ and then to install the system on the ISO and test that as well. Furthermore that the bulk of testing specifically should take place on that installed system as that is where it is most important to users that everything they expect to work actually works. Which do users use the most? The installed system by far. From experience I know users judge the distro more by how the installed system works. If any of Y’all noticed I’ve always been insistent that testing needs to be done on real hardware not just in VirtualBox and have done so diligently.

Maybe I’m wrong but to me Release Manager, TPG, is arbitrarily dictating a new condition regarding how we do Quality Assurance on a release. If I am wrong please correct me. I’ll deal with the embarrassment of how much time I’ve been wasting on my own…

Colin · June 2, 2017, 12:15am

I have the funeral of my sister tomorrow and I did not really want to be engainging in a debate about what should work and what should not. All those involved in this thread have dedicated long hours of updating, building, fixing software packages then testing and bug reporting it has been a huge cooperative effort by everyone involved and yet now after all that cooperation we are bickering over the few final issues and unjustifiably harsh words are being thrown around without any thought as to the circumstances or feelings of others.

The number of issues under discussion are few. Of the issues in question there is now a patch for the nVidia drivers which allows them to build under kernel-4.11.1 this is available under bug 2169.
The issue of akonadiconsole can now be resolved by the simple expediant of creating a new package for akonadiconsole please see bug 2172 for an explanation.
As for the issue of Calamares installer not starting this has happened before and crisb fixed it by reverting some code in calamares. I have checked git and there have been some attempts by upstream to fix the issue but these changes were reverted because they did not improve matters. Finally version 3 came out and crisb’s patches were dropped and it seems that the problem is back again.
I note that TPG has just built V3.1 let’s hope that this fixes the issue. The only remaining issue that requires a little work is kdenlive. If we can’t fix it in a reasonable time then we could simply leave it off the iso. And ship it at a later date.
If you would all like to cast your minds back to the 2014 release and recall how proud we all were that we had put out a release that has proved to be so good that people are still using it!
What is the problem with fixing a few issues that will make all the difference to the quality of the reviews in the public arena.
There will always be bugs in any distro but there really shouldn’t be bugs that we know about and that we know how to fix.

Colin · June 2, 2017, 12:22am

Subscript,
I have just built kdenlive git locally and it works!! Though it does segfault on exit.

rugyada · June 2, 2017, 10:49am

The good new is that kernel 4.11.3-2 (I think it’s due to the kernel) improved display window in virtualbox. The ISO menu starts at 1024x768 and Plymouth screen as well.
The so-so is that subsequent windows resize again to 800x600

Install “standalone” in virtualbox keep on working for me as before.
But window is still small.

Then Plymouth as above in live mode.
Then calamares:

I’ve run out of real hardware available for testing. ATM I can not confirm or deny whether or not new calamares version fixed the Install on hardware issue.

The above testing have been made using LXQt ISO 1090, which is supposed to include new kernel and new calamares versions.

Hope it helps.

Sirius · June 3, 2017, 1:29pm

Good morning for all (it’s morning here in Argentina !).
Good afternoon for the Europeans !

My report, part 1.

It was done over direct hardware (no virtual machine).

As others had reported, I had tried to install directly from USB at boot without success.The machine simply reboot very soon in the installation process.

The USB can boot in Live mode. I’m writing from OMV Lx 3.02, build 1082, right now.

One single observation: if I select “Errata” at the boot screen, the errata of LX 3.01 appears (anyway, that errata is empty). But in the page of 3.01 errata there’s a link pointing to “Release 3”. Clicking on it goes to all the articles under “release 3”, as expected. The point is “3.02/Errata” EXIST.

Another point, common to all versions of OMV Lx, is that the License only appears in English, even after selecting “Spanish” in the first screen after the boot screen. Mandriva 2010.2 had the license in Spanish !! (I guess this is not that much serious, as 99,9999% of users will press “next” without reading the license !)

I have a nVidia GTX 650 graphic card. inxi says, apparently, OMV Live is not using nvidia proprietary (logically !) nor nouveau driver. Graphics are at full resolution (1920x1080 for my configuration).


$ inxi -F
System:    Host: localhost.localdomain Kernel: 4.11.2-desktop-1omv x86_64 (64 bit) Desktop: KDE Plasma 5.9.5
           Distro: OpenMandrivaLinux 3.0 Einsteinium
[...]
Graphics:  Card: NVIDIA GK107 [GeForce GTX 650]
           Display Server: OpenMandriva X.org 119.3 drivers: (unloaded: fbdev,vesa)
           Resolution: 1920 x 1080 @ 60.00hz
           GLX Renderer: Gallium 0.4 on NVE7 GLX Version: 3.0 Mesa 17.1.0
[...]

But lspci says it’s using nouveau:


$ lspci -v
[...]
01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: eVga.com. Corp. GK107 [GeForce GTX 650]
        Flags: bus master, fast devsel, latency 0, IRQ 26
        Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        Memory at f0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: 
        Kernel driver in use: nouveau
        Kernel modules: nvidiafb, nouveau

No glitches, at least no up to now (after 20 minutes of use) !!

Checklist, part 1:

Checklist OMLx 3.02 development ISO build 1082

Does iso burns on usb stick - YES -
Does the grub/boot screen appears - YES - (*)
Does the options in grub/boot screen works - YES, but not all options tested. “Direct installation” option can be selected, and installation process is launched, but installation cannot be completed.

(*) In my PC, I can select which drive must be used to boot. I have two options regarding USB: “USB drive” and “UEFI mode USB drive”. If I select first option, I get 4 options at grub menu. If I select the second, a fifth option appears: “Use UEFI image at boot”. A good proof that UEFI works at least in my PC (3 1/2 years old).

LIVE MODE in VirtualBox: NOT TESTED

LIVE MODE in Hardware
Does autologin for user works - YES -
Does default graphical desktop shows after login - YES -
Does default graphical desktop is useable (basics, like menu, file manager, web browser) - YES -
Plymouth does show up

INSTALLATION in Hardware
Install starts from ISO menu, but after some seconds, PC reboots. A known bug.

Edit:
Glitches appeared !!!

But they’re only notable after starting to see YouTube videos and Facebook pages !!!

Colin · June 4, 2017, 7:50am

New nVidia proprietry rpms available in testing repo. Please test and report.
Thank you,
Colin

ben79 · June 4, 2017, 4:22pm

Thanks Colin, I’m sure a lot of nVidia users are looking forward to testing. Unfortunately I’m not finding them here. Need help finding.

Edit: You blithering idiot. They would be in non-free-testing. Look there ben79, and drink your coffee before posting…

Edit 2: The nVidia driver packages are here. Currently for nVidia current. Do we need new packages for nVidia Legacy versions?

mandian · June 4, 2017, 11:30pm

I think it is just a legal issues: a contract in another language is a different contract. When you find software contract in languages different from English usually somewhere you may find it is translated for a favour but the valid one remains the English one.

Sirius · June 4, 2017, 11:41pm

I thought that, in Mandriva case (not sure about OpenMandriva), the “legal” license was in French.

In any case, it would be enough to state that “valid” license is the English one (or the French one), and translated licenses are given as a “guide” to what license says.

ben79 · June 4, 2017, 11:50pm

Makes sense to me. One problem currently is we don’t have anyone working with languages and translations. Last person we had doing this went bye bye. Volunteers needed…