Which version of sope-gdl1-postgres are you using?

sope-gdl1-postgres 4.9-20111212_1664.el5.1

• postgresql 8.1.23-1.el5_7.3

same problem exists for CentOs 5.7 x86_64
tested with firefox 3.6.24, Safari 5.0.6
No display problem with iCal Version 3.0.8 (1287) but the entries with more then one Line are not updated any more (see screenshots)

Same problem here with lightning or web interface.

postgresql-8.1.23-1.el5_7.3
sogo-1.3.11-1.el5
sope49-gdl1-postgresql-4.9-20111212_1664.el5.1

The DESCRIPTION field only shows the first line either in lightning or in the web interface, however the DB stores rightly the filed when the appointment is created either from lightning or from web interface: "DESCRIPTION:test\nline1\nline2\nline3\r\n"

However if the appointment is edited then the field becomes (in the data base, nothing happens in the gui): DESCRIPTION:test\r\nX-LIC-ERROR;X-LIC-ERRORTYPE=COMPONENT-PARSE-ERROR:Got a data line, but co\r\n uld not find a property name or component begin tag: line3\r\nSEQUENCE:6\r\nX-MOZ-GENERATION:2

I can confirm that the problem is still present with last sope49-gdl1-postgresql

postgresql-8.1.23-1.el5_7.3
sogo-1.3.11-1.el5
sope49-gdl1-postgresql-4.9-20111226_1664.el5.1

Hi all we have the same problem. We are also running CentOS 5 with the package versions as stated above:

sogo-1.3.11-1.el5
sope49-gdl1-postgresql-4.9-20111212_1664.el5.1
postgresql-8.1.23-1.el5_7.3

We have verified that the data is actually written succesfully to the postgres database with a pg_dump command. However the gui is not showing the data when reopening the task or events. We have tried Thunderbird Lighning, Kde Organizer and the web-frontend. All show the same problem, that the data is only shown until the first new-line.

When looking at the db dump it can be seen that older entries which are displayed fine have a sequence of \n instead of \n. Could this be the problem?

Product version should be set to 1.3.11

Update today to version 1.3.12a and found that the error is still present. Has anyone found the root cause or a workaround for this?
There was also another new bug report 0001630 opened concerning this issue.

Our configuration (see bug report 0001630) is the following:

postgresql-server-8.1.23-1.el5_7.3
postgresql-libs-8.1.23-1.el5_7.3
sope49-gdl1-postgresql-4.9-20120214_1664.el5.1
postgresql-8.1.23-1.el5_7.3
sogo-1.3.12c-1.el5

I verified that this bug happens when reading from the database, as there is multiline data within the table:

psql -U sogo sogo -c "SELECT * FROM sogo<myuser><randomhash>;"

...
DESCRIPTION:test1
test2
...

I can confirm that the bug is still present in 1.3.12c

postgresql-8.1.23-1.el5_7.3
postgresql-libs-8.1.23-1.el5_7.3
sope49-gdl1-postgresql-4.9-20120214_1664.el5.1
sogo-1.3.12c-1.el5
postgresql-server-8.1.23-1.el5_7.3

Please update "Product Version" in this report to reflect the fact that this bug has been present either in 1.3.11 and 1.3.12

Can you reproduce it on sogo-demo.inverse.ca ?

Please show ALL SOPE packages you're using.

@ludovic: No, it's not reproducible on sogo-demo.inverse.ca

Sope packages:

sope49-core-4.9-20120214_1664.el5.1
sope49-appserver-4.9-20120214_1664.el5.1
sope49-cards-1.3.12c-1.el5
sope49-sbjson-2.3.1-20120214_1664.el5.1
sope49-xml-4.9-20120214_1664.el5.1
sope49-gdl1-4.9-20120214_1664.el5.1
sope49-mime-4.9-20120214_1664.el5.1
sope49-ldap-4.9-20120214_1664.el5.1
sope49-gdl1-postgresql-4.9-20120214_1664.el5.1
sope49-gdl1-contentstore-1.3.12c-1.el5

Show your complete Apache and PostgreSQL configuration.

Apache:

Alias /SOGo.woa/WebServerResources/ \
/usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ \
/usr/lib/GNUstep/SOGo/WebServerResources/
AliasMatch /SOGo/so/ControlPanel/Products/(.)/Resources/(.) \
/usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2

<Directory /usr/lib/GNUstep/SOGo/>
AllowOverride None
Order deny,allow
Allow from all
</Directory>

<LocationMatch "^/SOGo/so/ControlPanel/Products/.UI/Resources/..(jpg|png|gif|css|js)">
SetHandler default-handler
</LocationMatch>

ProxyRequests Off
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On

ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0

<Proxy http://127.0.0.1:20000/SOGo>
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "someserver.some.where"
RequestHeader set "x-webobjects-server-url" "https://someserver.some.where&quot;

RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
RequestHeader set "x-webobjects-remote-host" %{REMOTE_HOST}e env=REMOTE_HOST

AddDefaultCharset UTF-8

Order allow,deny
Allow from all
</Proxy>

RewriteEngine On
RewriteRule ^/SOGo/(.*)$ /SOGo/$1 [env=REMOTE_HOST:%{REMOTE_ADDR},PT]

PostgreSQL

grep '^[^# ]' /var/lib/pgsql/data/postgresql.conf
max_connections = 100
shared_buffers = 1000 # min 16 or max_connections*2, 8KB each
redirect_stderr = on # Enable capturing of stderr into log
log_directory = 'pg_log' # Directory where log files are written
log_filename = 'postgresql-%a.log' # Log file name pattern.
log_truncate_on_rotation = on # If on, any existing log file of the same
log_rotation_age = 1440 # Automatic rotation of logfiles will
log_rotation_size = 0 # Automatic rotation of logfiles will
lc_messages = 'es_ES.UTF-8' # locale for system error message
lc_monetary = 'es_ES.UTF-8' # locale for monetary formatting
lc_numeric = 'es_ES.UTF-8' # locale for number formatting
lc_time = 'es_ES.UTF-8' # locale for time formatting

Apache

Alias /SOGo.woa/WebServerResources/ \
/usr/lib64/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ \
/usr/lib64/GNUstep/SOGo/WebServerResources/
AliasMatch /SOGo/so/ControlPanel/Products/(.)/Resources/(.) \
/usr/lib64/GNUstep/SOGo/$1.SOGo/Resources/$2

<Directory /usr/lib64/GNUstep/SOGo/>
AllowOverride None
Order deny,allow
Allow from all
</Directory>

<LocationMatch "^/SOGo/so/ControlPanel/Products/.UI/Resources/..(jpg|png|gif|css|js)">
SetHandler default-handler
</LocationMatch>

ProxyRequests Off
SetEnv proxy-nokeepalive 1
ProxyPreserveHost On
ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0

<Proxy http://127.0.0.1:20000/SOGo>
RequestHeader set "x-webobjects-server-port" "443"
RequestHeader set "x-webobjects-server-name" "www.my.company.de"
RequestHeader set "x-webobjects-server-url" "https://www.my.company.de&quot;
RequestHeader set "x-webobjects-server-protocol" "HTTP/1.0"
RequestHeader set "x-webobjects-remote-host" %{REMOTE_HOST}e env=REMOTE_HOST
AddDefaultCharset UTF-8
Order allow,deny
Allow from all
</Proxy>

RewriteEngine On
RewriteRule ^/SOGo/(.*)$ /SOGo/$1 [env=REMOTE_HOST:%{REMOTE_ADDR},PT]

Postgres

In our postgres.log file I found a lot of the following messages:
ERROR: parameter "standard_conforming_strings" cannot be changed

logfile is default centos5 install I would say, only the following options are set the rest is default.
postgresql version is: postgresql-server-8.1.23-1.el5_7.3

listen_addresses = 'localhost' # what IP address(es) to listen on;
redirect_stderr = on # Enable capturing of stderr into log
log_directory = 'pg_log' # Directory where log files are written
log_filename = 'postgresql-%a.log' # Log file name pattern.
log_truncate_on_rotation = on # If on, any existing log file of the same
log_rotation_age = 1440 # Automatic rotation of logfiles will
log_rotation_size = 0 # Automatic rotation of logfiles will

With 8.3 on Debian, it works like a charm. With 8.1 on CentOS I can reproduce the issue.

What happens if you add standard_conforming_strings = on in your postgresql.conf ? 8.1 refuses to start but 8.2 is supposed to accept this.

Forget about everything above. This has been fixed in commit 8c2e4c4dc578c74711ed9d90287f0dfd342f4361. Please try the next nightlies for sope-gdl1-postgresql.