Re: [SOGo] Misquoted apostrophe - anyone seen it? - and bug tracker accounts

2012-04-12 Thread Wolfgang Sourdeau

Le 12-04-12 13:01, Wolfgang Sourdeau a écrit :

Hi,


Provided you install the sogo-dbg package, can you launch gdb against 
one of your running instances (gdb -p [pid of instance]) and, at the
Please note that "pid of instance" must not be the pid referenced in 
/var/run/sogo/sogo.pid but the one of one of its children.
To make sure you have go a right one, you can just perform a "pstree -p 
[pid of parent]" using the number found in that file.



Wolfgang

--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Misquoted apostrophe - anyone seen it? - and bug tracker accounts

2012-04-12 Thread Wolfgang Sourdeau

Hi,


Provided you install the sogo-dbg package, can you launch gdb against 
one of your running instances (gdb -p [pid of instance]) and, at the 
prompt, perform the following commands:


> b GCSFolderManager.m:250
> continue

Once the breakpoint is reached, execute the following:

> bt
[output]
> q

and return me the result.
The "q" command will cause gdb to leave but it will let the sogo process 
running.

What interests me is the output of the "bt" command.


Thanks!


Wolfgang

--
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Misquoted apostrophe - anyone seen it? - and bug tracker accounts

2012-04-12 Thread Christian Mack
On 2012-04-12 17:18, Christian Mack wrote:
> Hello MJ Ray
> 
> 
> On 2012-04-12 16:09, MJ Ray wrote:
>> Running sogo 1.3.14 with current stable packages on current stable
>> debian, we're seeing log lines like this
>>
>> Apr 12 06:56:42 sogod [17806]: <0x0xf5fa60[GCSFolderManager]> 
>> ERROR(-[GCSFolderManager performSQL:]): cannot execute
>> SQL 'SELECT c_folder_id, c_path, c_location, c_quick_location, 
>> c_acl_location, c_folder_type FROM sogo_folder_info WHERE c_path1 = 'Users' 
>> AND c_path2 = 'austen' AND c_path3 = 'Calendar\' AND c_path4 = 'personal'':
>>  NAME:PostgreSQL72FatalError REASON:fatal 
>> pgsql error (channel=<0x0x15fa420[PostgreSQL72Channel]: 
>> connection=<0x0x15faaf0[PGConnection]:  connection=0x0x15faca0>>): ERROR:  
>> syntax error at or near "personal"
>>
>> with a few different c_path2 values but always the misquoting in
>> c_path3.  I've vague fault reports from other users that I'm now
>> trying to pin down, but has anyone else encountered this?
>>
>> I found a few similar things by searching http://www.sogo.nu/bugs/
>> for PostgreSQL72FatalError but they are all resolved.
>>
>> Finally, could I have an account on http://www.sogo.nu/bugs/ without
>> taking an eyetest, please?  Then I can report this once I narrow it
>> down enough to report.
>>
> 
> See Bug #1767
> http://www.sogo.nu/bugs/view.php?id=1767
> 

Sorry, forgot to answer the second part :-)

Just go to
http://www.sogo.nu/bugs/signup_page.php

Fill in your desired username and a valid email.
Answer the captcha and press the button.
That's it.


Kind regards,
Christian Mack

-- 
Christian Mack
Gruppe Informationsdienste
Rechenzentrum Universität Konstanz
-- 
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Misquoted apostrophe - anyone seen it? - and bug tracker accounts

2012-04-12 Thread Christian Mack
Hello MJ Ray


On 2012-04-12 16:09, MJ Ray wrote:
> Running sogo 1.3.14 with current stable packages on current stable
> debian, we're seeing log lines like this
> 
> Apr 12 06:56:42 sogod [17806]: <0x0xf5fa60[GCSFolderManager]> 
> ERROR(-[GCSFolderManager performSQL:]): cannot execute
> SQL 'SELECT c_folder_id, c_path, c_location, c_quick_location, 
> c_acl_location, c_folder_type FROM sogo_folder_info WHERE c_path1 = 'Users' 
> AND c_path2 = 'austen' AND c_path3 = 'Calendar\' AND c_path4 = 'personal'':
>  NAME:PostgreSQL72FatalError REASON:fatal 
> pgsql error (channel=<0x0x15fa420[PostgreSQL72Channel]: 
> connection=<0x0x15faaf0[PGConnection]:  connection=0x0x15faca0>>): ERROR:  
> syntax error at or near "personal"
> 
> with a few different c_path2 values but always the misquoting in
> c_path3.  I've vague fault reports from other users that I'm now
> trying to pin down, but has anyone else encountered this?
> 
> I found a few similar things by searching http://www.sogo.nu/bugs/
> for PostgreSQL72FatalError but they are all resolved.
> 
> Finally, could I have an account on http://www.sogo.nu/bugs/ without
> taking an eyetest, please?  Then I can report this once I narrow it
> down enough to report.
> 

See Bug #1767
http://www.sogo.nu/bugs/view.php?id=1767


Kind regards,
Christian Mack

-- 
Christian Mack
Gruppe Informationsdienste
Rechenzentrum Universität Konstanz
-- 
users@sogo.nu
https://inverse.ca/sogo/lists