[kmail2] [Bug 470788] Tree with folder structure scrolls on top when try to drop email on any folder

2023-09-20 Thread Stuart Morrison
https://bugs.kde.org/show_bug.cgi?id=470788

Stuart Morrison  changed:

   What|Removed |Added

 CC||stu...@hadez.org

--- Comment #1 from Stuart Morrison  ---
This bug looks related to bug 440874

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 462482] Folder list scrolls upwards when moving mails to folders

2023-09-20 Thread Stuart Morrison
https://bugs.kde.org/show_bug.cgi?id=462482

Stuart Morrison  changed:

   What|Removed |Added

 CC||stu...@hadez.org

--- Comment #1 from Stuart Morrison  ---
This bug looks related to bug 440874

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 444108] kmail dragging mail to sidebar starts scrolling fast in wayland sessions

2023-09-20 Thread Stuart Morrison
https://bugs.kde.org/show_bug.cgi?id=444108

Stuart Morrison  changed:

   What|Removed |Added

 CC||stu...@hadez.org

--- Comment #2 from Stuart Morrison  ---
This bug looks related to bug 440874

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder

2023-07-10 Thread Stuart Morrison
https://bugs.kde.org/show_bug.cgi?id=440874

Stuart Morrison  changed:

   What|Removed |Added

 CC||stu...@hadez.org

--- Comment #2 from Stuart Morrison  ---
Can replicate.

Dragging a message into the folder list tree view causes it to scroll to the
top of the list if the folder list tree view is scrollable due to size of
folder list entries making it impossible to drop a message into any folders not
at the top of the list.

This does not happen in a X11 session.

Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-24-generic (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail

2022-11-13 Thread Stuart Prescott
https://bugs.kde.org/show_bug.cgi?id=457233

Stuart Prescott  changed:

   What|Removed |Added

 CC||bugs.kde.org@nanonanonano.n
   ||et

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2

2022-07-15 Thread Stuart Morrison
https://bugs.kde.org/show_bug.cgi?id=421664

Stuart Morrison  changed:

   What|Removed |Added

 CC||stu...@hadez.org

--- Comment #11 from Stuart Morrison  ---
(In reply to Kishore Gopalakrishnan from comment #8)
> Does anyone still have this issue? STMP with XOAUTH2 on Gmail works for me
> without any problems (I earlier had the issue described here).

I still have the same problem, SMTP stops working after a while and requires an
Akonadi restart so can't realistically use KMail at work any more. 

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-41-generic (64-bit)
Graphics Platform: X11

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on starting connection to backend postgresql database

2020-12-23 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=430689

--- Comment #5 from stuart  ---
Pleas note, the crashes started before upgrading postgresql, so this is not
related to postgresql upgrade.  Further, if I revert akonadi to 20.04, it
connects ok, and is usable.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on starting connection to backend postgresql database

2020-12-21 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=430689

stuart  changed:

   What|Removed |Added

Summary|Any version of  |Any version of
   |akonadi-server after 20.04  |akonadi-server after 20.04
   |fails on staring connection |fails on starting
   |to backend postgresql   |connection to backend
   |database|postgresql database

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database

2020-12-21 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=430689

--- Comment #3 from stuart  ---
This started in August after the initial upgrade to 20.08 while I was running
postgresql 12.4.  I later upgraded to postgresql t0 13.1.  After reverting to
20.04, akonadi successfully connects to the backend.  I do see in the
akonadictl output that the database version may not be supported, but I don't
see this message in v20.04, so I don't think this is related to the database
version.

The revert has been a workaround, but I was hoping for an eventual fix. Since
this has persisted, I am opening this bug report.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database

2020-12-21 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=430689

stuart  changed:

   What|Removed |Added

 CC||sfbar...@gmail.com

--- Comment #2 from stuart  ---
Created attachment 134257
  --> https://bugs.kde.org/attachment.cgi?id=134257=edit
akonadi.error.old file

akonadi.error is blank on this test, but akonadi.error.old shows errors.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 430689] Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database

2020-12-21 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=430689

--- Comment #1 from stuart  ---
Created attachment 134256
  --> https://bugs.kde.org/attachment.cgi?id=134256=edit
postgresql log during akonadi query failure

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 430689] New: Any version of akonadi-server after 20.04 fails on staring connection to backend postgresql database

2020-12-21 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=430689

Bug ID: 430689
   Summary: Any version of akonadi-server after 20.04 fails on
staring connection to backend postgresql database
   Product: Akonadi
   Version: 5.15.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: sfbar...@gmail.com
  Target Milestone: ---

Created attachment 134255
  --> https://bugs.kde.org/attachment.cgi?id=134255=edit
console output of akonadictl start --verbose

SUMMARY

After Tumbleweed distribution upgrade, akonadi-server updated from 20.04 to
20.08. All later packages report the same error attempting to start.

Error during selection of all records from table "SchemaVersionTable" "SSL
SYSCALL error: Bad file descriptor\n() QPSQL: Unable to create query" "SELECT
version, generation FROM SchemaVersionTable"



STEPS TO REPRODUCE
1. Setup and start local postgres db server
2. Configure akonadi to user postgres as backend db
3. akonadictl start

OBSERVED RESULT

akonadi performs many queries to the db successfully, but then starts failing
with multiple errors

Error during selection of all records from table "SchemaVersionTable" "SSL
SYSCALL error: Bad file descriptor\n() QPSQL: Unable to create query" "SELECT
version, generation FROM SchemaVersionTable"


EXPECTED RESULT

Register new connection notifications:

org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f5e7c0d9cf0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f5e7c0f5630) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f5e7c0fdfb0) )
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f5e7c1073d0) )



SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSuSE Tumbleweed > 2020-08-18
(available in About System)
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
PostgreSQL: 13.1

ADDITIONAL INFORMATION

I can revert to the following packages from openSuSE Leap 15.2 which contain
akonadi v20.04 and akonadi-server starts ok.

Also, since release 20.12, I have to first remove these packages

rpm -ev libKPimAddressbookImportExport5 kaddressbook kdepim-addons
kaddressbook-lang korganizer kmail kdepim-addons-lang korganizer-lang
pim-sieve-editor kmail-lang pim-sieve-editor-lang 
Preparing packages...
kmail-20.12.0-172.1.x86_64
kaddressbook-20.12.0-153.2.x86_64
korganizer-20.12.0-149.1.x86_64
kdepim-addons-20.12.0-187.1.x86_64
pim-sieve-editor-20.12.0-141.1.x86_64
pim-sieve-editor-lang-20.12.0-141.1.noarch
libKPimAddressbookImportExport5-20.12.0-153.2.x86_64
kdepim-addons-lang-20.12.0-187.1.noarch
korganizer-lang-20.12.0-149.1.noarch
kaddressbook-lang-20.12.0-153.2.noarch
kmail-lang-20.12.0-172.1.noarch

then revert to these, with 

rpm -Uvh --oldpackage akonadi-calendar-lang-20.04.2-lp152.1.1.noarch.rpm
akonadi-calendar-tools-20.04.2-lp152.1.1.x86_64.rpm
akonadi-calendar-tools-lang-20.04.2-lp152.1.1.noarch.rpm
akonadi-contact-20.04.2-lp152.1.1.x86_64.rpm
akonadi-contact-lang-20.04.2-lp152.1.1.noarch.rpm
akonadi-import-wizard-20.04.2-lp152.1.1.x86_64.rpm
akonadi-import-wizard-lang-20.04.2-lp152.1.1.noarch.rpm
akonadi-mime-20.04.2-lp152.1.1.x86_64.rpm
akonadi-mime-lang-20.04.2-lp152.1.1.noarch.rpm
akonadi-notes-lang-20.04.2-lp152.1.1.noarch.rpm
akonadi-plugin-calendar-20.04.2-lp152.1.1.x86_64.rpm
akonadi-plugin-contacts-20.04.2-lp152.1.1.x86_64.rpm
akonadi-plugin-kalarmcal-20.04.2-lp152.1.1.x86_64.rpm
akonadi-plugin-mime-20.04.2-lp152.1.1.x86_64.rpm
akonadi-search-20.04.2-lp152.1.1.x86_64.rpm
akonadi-search-lang-20.04.2-lp152.1.1.noarch.rpm
akonadi-server-20.04.2-lp152.1.1.x86_64.rpm
akonadi-server-lang-20.04.2-lp152.1.1.noarch.rpm
akregator-20.04.2-lp152.1.1.x86_64.rpm
akregator-lang-20.04.2-lp152.1.1.noarch.rpm
calendarsupport-20.04.2-lp152.1.1.x86_64.rpm
calendarsupport-lang-20.04.2-lp152.1.1.noarch.rpm
eventviews-20.04.2-lp152.1.1.x86_64.rpm
eventviews-lang-20.04.2-lp152.1.1.noarch.rpm
incidenceeditor-20.04.2-lp152.1.1.x86_64.rpm
incidenceeditor-lang-20.04.2-lp152.1.1.noarch.rpm
kaccounts-integration-20.04.2-lp152.1.1.x86_64.rpm
kaccounts-integration-lang-20.04.2-lp152.1.1.noarch.rpm
kaccounts-providers-20.04.2-lp152.1.1.x86_64.rpm
kaccounts-providers-lang-20.04.2-lp152.1.1.noarch.rpm
kaddressbook-20.04.2-lp152.1.1.x86_64.rpm
kaddressbook-doc-20.04.2-lp152.1.1.noarch.rpm
kaddressbook-lang-20.04.2-lp152.1.1.noarch.rpm
kalarmcal-20.04.2-lp152.1.1.x86_64.rpm
kalarmcal-lang-20.04.2-lp152.1.1.noarch.rpm
kdepim-addons-20.04.2-lp152.1.1.x86_64.rpm
kdepim-addons-lang-20.04.2-lp152.1.1.noarch.rpm
kdepim-apps-libs-20.04.2-lp152.1.1.x86_64.rpm

[kmail2] [Bug 413941] Crash when opening Kmail

2019-12-01 Thread Stuart Morgan
https://bugs.kde.org/show_bug.cgi?id=413941

--- Comment #2 from Stuart Morgan  ---
Given this was 3 weeks ago, I really cannot remember. I am using the
proprietary driver. I doubt I would have filed a report if I knew that to be
the case but it's still a possibility.

Feel free to close, if the same crash occurs again I can re-open.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 413941] New: Crash when opening Kmail

2019-11-08 Thread Stuart Morgan
https://bugs.kde.org/show_bug.cgi?id=413941

Bug ID: 413941
   Summary: Crash when opening Kmail
   Product: kmail2
   Version: 5.11.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: stu...@tase.co.uk
  Target Milestone: ---

Application: kmail (5.11.3)

Qt Version: 5.12.5
Frameworks Version: 5.61.0
Operating System: Linux 5.3.8-300.fc31.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:

Kmail's message window was only showing black, so I quit kmail and started it
again, only now it crashes immediately on startup before any windows are
displayed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7f1106c680 (LWP 559274))]

Thread 20 (Thread 0x7f7ec8ff9700 (LWP 559318)):
#0  0x7f7f1d71907a in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7f171d882a in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7f7f171d91e7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7f7f171d92e1 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#4  0x7f7f17199a12 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f7f1719c525 in base::internal::SchedulerWorker::RunWorker() () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7f7f1719cae4 in base::internal::SchedulerWorker::RunPooledWorker() ()
from /lib64/libQt5WebEngineCore.so.5
#7  0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0
#9  0x7f7f1ff15643 in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7f7ec97fa700 (LWP 559304)):
#0  0x7f7f1d718d45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7f171d875a in base::ConditionVariable::Wait() () from
/lib64/libQt5WebEngineCore.so.5
#2  0x7f7f171d91f8 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7f7f171d929f in base::WaitableEvent::Wait() () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f7f17199a28 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /lib64/libQt5WebEngineCore.so.5
#5  0x7f7f1719c838 in base::internal::SchedulerWorker::RunWorker() () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7f7f1719cb64 in base::internal::SchedulerWorker::RunDedicatedWorker()
() from /lib64/libQt5WebEngineCore.so.5
#7  0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#8  0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0
#9  0x7f7f1ff15643 in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f7ec9ffb700 (LWP 559303)):
#0  0x7f7f1ff0aa1f in poll () from /lib64/libc.so.6
#1  0x7f7f1220e196 in poll_func () from /lib64/libpulse.so.0
#2  0x7f7f121ff801 in pa_mainloop_poll () from /lib64/libpulse.so.0
#3  0x7f7f121ffe83 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#4  0x7f7f121fff30 in pa_mainloop_run () from /lib64/libpulse.so.0
#5  0x7f7f1220e0dd in thread () from /lib64/libpulse.so.0
#6  0x7f7f1154eb9c in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-13.0.so
#7  0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0
#8  0x7f7f1ff15643 in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f7eca7fc700 (LWP 559302)):
#0  0x7f7f1d71907a in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7f171d882a in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /lib64/libQt5WebEngineCore.so.5
#2  0x7f7f171d91e7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /lib64/libQt5WebEngineCore.so.5
#3  0x7f7f17156188 in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from
/lib64/libQt5WebEngineCore.so.5
#4  0x7f7f1717820f in base::RunLoop::Run() () from
/lib64/libQt5WebEngineCore.so.5
#5  0x7f7f171aa86e in base::Thread::ThreadMain() () from
/lib64/libQt5WebEngineCore.so.5
#6  0x7f7f171db75f in base::(anonymous namespace)::ThreadFunc(void*) ()
from /lib64/libQt5WebEngineCore.so.5
#7  0x7f7f1d7124e2 in start_thread () from /lib64/libpthread.so.0
#8  0x7f7f1ff15643 in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f7ecaffd700 (LWP 559301)):
#0  0x7f7f1d718d45 in 

[Akonadi] [Bug 412629] Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists

2019-10-10 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=412629

--- Comment #3 from stuart  ---
Ok, I didn't suspect that since it is communicating with the database.
Just that the query fails and Akonadi shuts down.

On Thu, Oct 10, 2019 at 9:20 PM Sandro Knauß 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=412629
>
> Sandro Knauß  changed:
>
>What|Removed |Added
>
> 
>  CC||skna...@kde.org
>  Status|REPORTED|CONFIRMED
>  Ever confirmed|0   |1
>
> --- Comment #2 from Sandro Knauß  ---
> Keep in mind, that even Qt does not support Postgres 12 atm, so in first
> glance
> there needs to be a bug filed against Qt:
>
>
> https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/psql/qsql_psql.cpp#n1080
>
> also in Debian this bug is reported:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941763
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 412818] Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12

2019-10-10 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=412818

stuart  changed:

   What|Removed |Added

 CC||sfbar...@gmail.com
   Keywords||reproducible
URL||https://www.postgresql.org/
   ||docs/12/release-12.html#id-
   ||1.11.6.5.5

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 412818] New: Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12

2019-10-10 Thread stuart
https://bugs.kde.org/show_bug.cgi?id=412818

Bug ID: 412818
   Summary: Akonadi query on SchemaVersionTable is broken in
PostgreSQL Version 12
   Product: Akonadi
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: sfbar...@gmail.com
  Target Milestone: ---

SUMMARY

When backed by the postgres db, Akonadi executes the query;

"SELECT pg_attribute.attname, pg_attribute.atttypid::int,
pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod,
pg_attrdef.adsrc FROM pg_class, pg_attribute LEFT JOIN pg_attrdef ON
(pg_attrdef.adrelid = pg_attribute.attrelid AND pg_attrdef.adnum =
pg_attribute.attnum) WHERE pg_table_is_visible(pg_class.oid) AND
pg_class.relname = 'schemaversiontable' AND pg_attribute.attnum > 0 AND
pg_attribute.attrelid = pg_class.oid AND pg_attribute.attisdropped = false
ORDER BY pg_attribute.attnum ;"

In versions of PostGreSQL before 12, this query succeeds.  Due to the changes
to the informationschema, as identified in PostGreSQL PostgreSQL release notes:

E.1. Release 12
https://www.postgresql.org/docs/12/release-12.html#id-1.11.6.5.5

PostgreSQL Version 12 removes:

obsolete pg_constraint.consrc column
obsolete pg_attrdef.adsrc column


STEPS TO REPRODUCE
1. Upgrade PostGreSQL backend database to 12.x
2. Restart with Akonadictl start
3. 

OBSERVED RESULT

This causes the query to fail and Akonadi quits with the error.

org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Running DB initializer
org.kde.pim.akonadiserver: "\nSql error: ERROR:  column \"version\" of relation
\"schemaversiontable\" already exists\n(42701) QPSQL: Unable to create
query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT
NULL DEFAULT 0"
org.kde.pim.akonadiserver: Unable to initialize database.
org.kde.pim.akonadiserver: Shutting down AkonadiServer...


EXPECTED RESULT

When the query succeeds, Akonadi continues to process emails.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: ANY
(available in About System)
KDE Plasma Version: ANY
KDE Frameworks Version: ANY 
Qt Version: ANY

ADDITIONAL INFORMATION

The schema information for these dropped columns can be obtained using the
functions,

pg_constraint.consrc pg_get_constraintdef(pg_constraint.oid)
pg_attrdef.adsrc pg_get_expr(pg_attrdef.adbin, pg_class.oid)

So the Akonadi query:

SELECT pg_attribute.attname, pg_attribute.atttypid::int,
pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod,
pg_attrdef.adsrc
FROM pg_class, pg_attribute
LEFT JOIN pg_attrdef ON (pg_attrdef.adrelid = pg_attribute.attrelid AND
pg_attrdef.adnum = pg_attribute.attnum)
WHERE pg_table_is_visible(pg_class.oid)
AND pg_class.relname = 'schemaversiontable'
AND pg_attribute.attnum > 0
AND pg_attribute.attrelid = pg_class.oid
AND pg_attribute.attisdropped = false ORDER BY pg_attribute.attnum ;

should probably be changed to something like:

SELECT pg_attribute.attname, pg_attribute.atttypid::int,
pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod,
pg_get_expr(pg_attrdef.adbin, pg_class.oid) AS adsrc
FROM pg_class
LEFT JOIN pg_attribute ON ( pg_attribute.attrelid = pg_class.oid )
LEFT JOIN pg_attrdef ON  ( pg_attrdef.adrelid = pg_attribute.attrelid
 AND   pg_attrdef.adnum = pg_attribute.attnum )
WHERE pg_table_is_visible(pg_class.oid)
AND pg_class.relname = 'schemaversiontable'
AND pg_attribute.attnum > 0
AND pg_attribute.attisdropped = false
ORDER BY pg_attribute.attnum;

This will produce something like the following table:

  attname   | atttypid | attnotnull | attlen | atttypmod | adsrc
+--+++---+---
 version|   23 | t  |  4 |-1 | 0
 generation |   23 | t  |  4 |-1 | 0
(2 rows)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 372236] Akonadi will not start

2016-11-14 Thread Stuart
https://bugs.kde.org/show_bug.cgi?id=372236

--- Comment #3 from Stuart <sbe...@thevegfactor.co.uk> ---
(In reply to Christoph Feck from comment #1)
> Could you please state your distribution and/or updates that cause this
> issue?

Linux Mint 17.2 Rafaela
I have tended to do updates maybe once a week or fortnight. I'm not sure as to
which update may have caused Akonadi to stop working.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

[Akonadi] [Bug 372236] New: Akonadi will not start

2016-11-08 Thread Stuart
https://bugs.kde.org/show_bug.cgi?id=372236

Bug ID: 372236
   Summary: Akonadi will not start
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: KAlarm resource
  Assignee: djar...@kde.org
  Reporter: sbe...@thevegfactor.co.uk
CC: kdepim-bugs@kde.org
  Target Milestone: ---

Akonadi Server Self-Test Report
===

Test 1:  SUCCESS


Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server
configuration and was found on your system.

File content of '/home/stuart/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-stuart.3lRYnN/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS


Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the
recommended setup for a secure system.

Test 3:  SUCCESS


MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server
'/usr/sbin/mysqld-akonadi'.
Make sure you have the MySQL server installed, set the correct path and ensure
you have the necessary read and execution rights on the server executable. The
server executable is typically called 'mysqld'; its location varies depending
on the distribution.

Test 4:  SUCCESS


MySQL server is executable.
Details: MySQL server found: 161109  2:41:53 [Warning] Using unique option
prefix key_buffer instead of key_buffer_size is deprecated and will be removed
in a future release. Please use the full name instead.
/usr/sbin/mysqld  Ver 5.5.53-0ubuntu0.14.04.1 for debian-linux-gnu on i686
((Ubuntu))


Test 5:  SUCCESS


No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The
log can be found in '/home/stuart/.local/share/akonadi/db_data/mysql.err'.

Test 6:  SUCCESS


MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is
readable at /etc/akonadi/mysql-global.conf.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <k...@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
#
sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of
data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for
debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM
information_schema.tables WHERE table_schema not in ("mysql",
"information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show
global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other
internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables
(default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin,
8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but
more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous conn

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

2016-06-14 Thread Stuart Morrison via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354056

Stuart Morrison <stu...@hadez.org> changed:

   What|Removed |Added

 CC||stu...@hadez.org

--- Comment #43 from Stuart Morrison <stu...@hadez.org> ---
Same versions and symptoms at those above.

Have automatic compact on but it does not work.

Expiring manually through Thunderbird works.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 271167] akonadi resource entree cannot be removed from kaddressbook

2013-08-29 Thread Stuart Morrison
https://bugs.kde.org/show_bug.cgi?id=271167

Stuart Morrison stu...@hadez.org changed:

   What|Removed |Added

 CC||stu...@hadez.org

--- Comment #4 from Stuart Morrison stu...@hadez.org ---
I have the same issue with old akonadi_googlecalendar_resource entries.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 259574] conflict resolution box appears a lot

2011-07-14 Thread Stuart Morgan
https://bugs.kde.org/show_bug.cgi?id=259574


Stuart Morgan stu...@tase.co.uk changed:

   What|Removed |Added

 CC||stu...@tase.co.uk




-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Bug 67504] IMAP IDLE support for KMail (over 7 years in the making, over 3.5k votes, reporter switched to xfce years ago)

2011-03-19 Thread Stuart Morgan
https://bugs.kde.org/show_bug.cgi?id=67504





--- Comment #47 from Stuart Morgan stuart tase co uk  2011-03-19 22:54:08 ---
@ Timo - You're confusing democracy with open source. They are not the same
thing, open source means that you can write your own solution and even
contribute it back if there is interest. It does not mean that developers need
to listen to your opinions.

I voted for this feature, but I also have respect for the thousands of people
who contribute their time and effort to open source software. I have nothing
but contempt for those who think that they entitled to service when they have
paid nothing for a product and who contribute nothing but their snide comments.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs