I can't confirm this (but I'm on PHP 7.0.9, MySQL 5.6.31): I'm presented with the usual first page and then second page (see snapshot)

But wait... I executed /index.php, not /installation/index.php to start installation: I guess this could be your mistake... <-- bull**it

Sergio check your address bar and you will see you might have only typed
/index.php but you ended up at installation/index.php

On 10 Aug 2016 8:09 p.m., "Sergio Manzi" notifications@github.com wrote:

I can't confirm this (but I'm on PHP 7.0.9, MySQL 5.6.31): I'm
presented with the usual first page and then second page (see snapshot)

But wait... I executed /index.php, not /installation/index.php to
start installation: I guess this could be your mistake...

[image: capture]
https://cloud.githubusercontent.com/assets/552475/17567093/429354f0-5f3e-11e6-89b9-9bf96e21fcad.PNG

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#11537 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8X4FsnDiwG4x0Krdq8tnWIlwbXjRks5qeiHXgaJpZM4Jg1xh
.

correct: I was about posting that even with /installation/index.php (directly entered), I'm not affected by this issue...

Have successfully created several 3.6.2 sites locally this week, on a much
similar setup.
Main difference in setup from reporter seems to be I am using MySQL while
they are using the fork MariaDB.

Databaseversion 5.6.24
Databasesammenkøring utf8_general_ci
Database forbindelse kollation utf8mb4_general_ci
PHP version 5.6.8
Webserver Apache/2.4.12 (Win32) OpenSSL/1.0.1l PHP/5.6.8 mod_wsgi/3.5
Python/2.7.9
WebServer til PHP interface apache2handler
Joomla!-version Joomla! 3.6.2 Stable [ Noether ] 4-August-2016 23:41 GMT
Joomla! platformsversion Joomla Platform 13.1.0 Stable [ Curiosity ]
24-Apr-2013 00:00 GMT

Brugeragent

Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Have you succeeded in creating any sites locally with that new root user
with a non-empty password?
Thinking you could be having more root users now where the new not having
all privileges granted.
MariaDB generally is reported to work with former releases, dunno if there
could be an issue for 3.6.2 in particular.

On Wed, Aug 10, 2016 at 9:16 PM, Sergio Manzi notifications@github.com
wrote:

correct: I was about posting that even with /installation/index.php (directly
entered), i'm not affected by this issue...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#11537 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwPrVEn2UEsR5AmYiBbS_fQKY3g-0yiks5qeiNzgaJpZM4Jg1xh
.

MariaDB generally is reported to work with former releases, dunno if there
could be an issue for 3.6.2 in particular.

It perfectly works for me on my production sites where I have MariaDB 5.5.47 under CentOS 7.2 and recently upgraded most of them from J! 3.4.8 to J! 3.6.2. No new install over there, thus.

If needed, I can try.

Tested with the same DB version and on windows 10 as the original report

Database Version: 5.5.5-10.1.13-MariaDB  (xampp distribution)

but not with PHP 5.6.19 instead i have PHP 7.0.8 and it works

When password for MySQL user 'root' is non-empty:

When password for MySQL user 'root' is empty:

Perhaps the problem is the server. I try to reinstall it.

UPD: I found that problem is Xdebug. When Xdebug is on (i.e. row of php.ini 'zend_extension=...' is uncommented) I can't install Joomla! When Xdebug is off, error disappears.

I tried to install old versions of Joomla! when the xdebug is on. 3.5.1 - the same error, 3.4.8 - no errors.

I made a quick check of the differences in installation between 3.4.8 and 3.5.1.

I only see something that jumps to my eyes (because of that "Failed to start the session..." error you get):

In 3.4.8 we had JFactory::$session = null; in the constructors of the following classes and it has been removed in 3.5.1:

• InstallationControllerSetdefaultlanguage
• InstallationControllerInstallEmail
• InstallationControllerInstallLanguages

I don't know if this has anything to do with the issue at hand, but I think it can be a "lead" for someone more experienced than I am.

The other thing that probably has changed is that maybe somewhere we make a check of the the DB connection collation. Could it be the case that this check is somehow triggered even before having provided the DB parameters??

Just two 2 [Edit: it will make 4, too much...] cents from my part without presuming I exactly know what I'm talking about...

Im surprised no one has pointed out that using the root mysql user goes against all best practice and security principles - even in a development environment!

At this time I am closing this. It can always be reopened if there is anything constructive to add