https://issues.qgis.org/https://issues.qgis.org/favicon.ico2014-06-21T06:04:55ZQGIS Issue TrackingQGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=527432014-06-21T06:04:55ZJürgen Fischerjef@norbit.de
<ul><li><strong>Category</strong> set to <i>Data Provider/PostGIS</i></li><li><strong>Resolution</strong> set to <i>up/downstream</i></li></ul> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=529492014-06-22T01:08:16ZGiovanni Manghigiovanni.manghi@gmail.com
<ul></ul><p>should this be closed?</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=530992014-06-23T05:59:47ZBrett Zbzuehlke@chartwell-consultants.com
<ul></ul><p>The issue is certainly frustrating, as anyone using pgadmin would likely have more than one entry in pgpass (we'll likely move back to 32-bit). However, if there's nothing that can be done about it on the QGIS end, it may be closed. Thank you for investigating it.</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=531182014-06-23T06:23:27ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>Brett Z wrote:</p>
<blockquote>
<p>The issue is certainly frustrating, as anyone using pgadmin would likely have more than one entry in pgpass (we'll likely move back to 32-bit). However, if there's nothing that can be done about it on the QGIS end, it may be closed. Thank you for investigating it.</p>
</blockquote>
<p>so as far as I understand does not affect only qgis, but also pgadmin (for example), right?</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=531482014-06-23T07:33:31ZBrett Zbzuehlke@chartwell-consultants.com
<ul></ul><p>I've only experienced this problem in QGIS, not pgAdmin; however, that's likely because pgAdmin is 32 bit. The issue does not occur in 32-bit QGIS, only 64 bit.</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=637802015-09-22T03:55:08ZMartin HOFFMANN
<ul><li><strong>Target version</strong> changed from <i>Version 2.4</i> to <i>Version 2.10</i></li><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li></ul><p>I propose to reopen since I've found the culprit. I also provide an updated workaround for those who encounter the same problem.<br />I confirm this occur also under Windows 10.</p>
<p>The problem is solely caused by the EOL (End Of Line) encoding of this file:</p>
<blockquote>
<p>C:\\Users\\username\\AppData\\Roaming\\postgresql\\pgpass.conf</p>
</blockquote>
<p>This file is "shared" between PgAdmin and QGis but the two programs don't use the same EOL when accessing this file.<br />PgAdmin still write Windows Style (CR/LF) but Qgis 64-bit seem to be lost with (CR) and recognize only Unix style (LF). However PgAdmin can handle Unix style (LF)-only and keep the file untouched while reading.</p>
<p><strong>So if you need to use both PgAdmin and Qgis on a Windows7+ just convert EOL to (LF)-only in "pgpass.conf" using a suitable Text Editor (Notepad++ for instance). Unlike previous workaround this will work fine with multiple lines hence multiple entries in pgpass.conf.</strong></p>
<p>Unfortunately you will need to convert this file again every time PgAdmin happen to update the file.</p>
<p>I reopen the issue as it think it would be a pretty minor work to ask Qgis 64-bit to also handle the (CR/LF) EOL when running under windows. This should have zero side effect as no-one in his right mind will use a (CR) EOL inside a password...</p>
<p>I might be wrong however, feel free to close again, at least a better workaround is now provided ;)</p>
<p>PS: On a side note i don't get why this file is actually parsed because it seems that Qgis also store connection somewhere else.Password saved through the PostgisConnection manager are not wrote in the same file. So is that some sort of legacy mode?</p>
<p>Thanks a lot for reading this boring follow-up ;)</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=637842015-09-22T05:55:23ZJürgen Fischerjef@norbit.de
<ul></ul><p>Martin HOFFMANN wrote:</p>
<blockquote>
<p>I reopen the issue as it think it would be a pretty minor work to ask Qgis 64-bit to also handle the (CR/LF) EOL when running under windows. This should have zero side effect as no-one in his right mind will use a (CR) EOL inside a password...</p>
</blockquote>
<blockquote>
<p>PS: On a side note i don't get why this file is actually parsed because it seems that Qgis also store connection somewhere else.Password saved through the PostgisConnection manager are not wrote in the same file. So is that some sort of legacy mode?</p>
</blockquote>
<p>QGIS doesn't read or write that file at all. libpq does.</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=638832015-09-28T06:48:55ZMartin HOFFMANN
<ul></ul><p>So when you install both PgAdmin and QGis (via OSGeow4w) you end up with 2 different version of libpq.<br />This seems unavoidable and none of the project are "at fault". This issue might resolve by itself when PgAdmin will switch to a more recent libpq version.</p>
<p>I guess we can close again and the next person that will stumble here can use this as the best workaround</p>
<blockquote>
<p><strong>So if you need to use both PgAdmin and Qgis on a Windows7+ just convert EOL to (LF)-only in "pgpass.conf" using a suitable Text Editor (Notepad++ for instance). Unlike previous workaround this will work fine with multiple lines hence multiple entries in pgpass.conf</strong></p>
<p>Unfortunately you will need to convert this file again every time PgAdmin happen to update the file.</p>
</blockquote>
<p>I feel like I reopened too quickly, sorry about that. So are you ok to close?</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=641442015-10-05T03:07:44ZMartin HOFFMANN
<ul><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li></ul><p>No responses, so I guess it's safe to close again.</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=751752017-03-09T05:48:23ZJérôme Guélat
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Reopened</i></li><li><strong>Target version</strong> changed from <i>Version 2.10</i> to <i>Version 2.18</i></li></ul><p>I tested this issue with 2.18.4 and 2.14.12 and I'm also having problems, even when using only LF EOL... QGIS is extracting the login/password information only for one connection (it doesn't have to be the first one in the pgpass file), but it doesn't work for the other ones. Interestingly the connection that is working is a 9.6 server, and all the other are servers with version 9.5 or lower.</p>
<p>The same pgpass file works perfectly when connecting with pgAdmin or with the RPostgreSQL package in R.</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=751762017-03-09T06:00:23ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Affected QGIS version</strong> changed from <i>2.0.1</i> to <i>2.18.4</i></li><li><strong>Resolution</strong> deleted (<del><i>up/downstream</i></del>)</li></ul> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=783082017-04-30T23:08:17ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Easy fix?</strong> set to <i>No</i></li><li><strong>Regression?</strong> set to <i>No</i></li></ul> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=890462018-03-31T08:24:51Zolivier olivierqgis@noetika.com
<ul></ul><p>Hi, I found that converting 0d 0a to 0a 0d (with software such as hex editor neo) works for pgadmin and qgis.</p>
<p>Olivier</p> QGIS Application - Bug report #10517: Reading PGPASS fails on 64-Bit Versionhttps://issues.qgis.org/issues/10517?journal_id=1018102019-03-09T14:09:30ZGiovanni Manghigiovanni.manghi@gmail.com
<ul><li><strong>Status</strong> changed from <i>Reopened</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>end of life</i></li></ul><p><strong>End of life notice: QGIS 2.18 LTR</strong></p>
<p><strong>Source:</strong><br /><a class="external" href="http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/">http://blog.qgis.org/2019/03/09/end-of-life-notice-qgis-2-18-ltr/</a></p>
<p>QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.</p>
<p>We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4</p>
<p>Most plugins have been either migrated or incorporated into the core QGIS code base.</p>
<p>We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.</p>
<p>You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, <strong>in which case they should reopen the ticket</strong>.</p>
<p>If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.</p>
<p>The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.</p>