[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time

2018-05-09 Thread Dean Cording
https://bugs.kde.org/show_bug.cgi?id=361764

Dean Cording <d...@cording.id.au> changed:

   What|Removed |Added

 CC||d...@cording.id.au

--- Comment #18 from Dean Cording <d...@cording.id.au> ---
Can confirm that the problem with Kontact changing AM times to PM in the
Australia timezone is still an issue in Version 5.7.3.  Changing the time
format in the System Setting Module to 'United Kingdom - British English' is a
work-around.

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

[korganizer] [Bug 361764] Cannot add event to calendar with correct time: Add event window will not accept an "A.M." time

2018-05-09 Thread Dean Cording
https://bugs.kde.org/show_bug.cgi?id=361764

Dean Cording <d...@cording.id.au> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #17 from Dean Cording <d...@cording.id.au> ---
*** This bug has been confirmed by popular vote. ***

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

[Akonadi] [Bug 283334] After suspend to ram KMail does not work, akonadi says MySQL server has gone away.

2014-06-01 Thread Dean Cording
https://bugs.kde.org/show_bug.cgi?id=283334

Dean Cording d...@cording.id.au changed:

   What|Removed |Added

 CC||d...@cording.id.au

--- Comment #31 from Dean Cording d...@cording.id.au ---
I am getting this error again with Akonadi version 1.12.1 under Kubuntu 14.04
with KDE 4.13.1.  After I resume from suspend to RAM, kmail cannot access any
mail folders and the Akondai server reports:

DATABASE ERROR:
Error code: 2006
DB error:  MySQL server has gone away
Error text: MySQL server has gone away QMYSQL: Unable to execute query
Query: SELECT CollectionTable.id, CollectionTable.remoteId,
CollectionTable.remoteRevision, CollectionTable.name, CollectionTable.parentId,
CollectionTable.resourceId, CollectionTable.subscribed,
CollectionTable.cachePolicyInherit, CollectionTable.cachePolicyCheckInterval,
CollectionTable.cachePolicyCacheTimeout,
CollectionTable.cachePolicySyncOnDemand, CollectionTable.cachePolicyLocalParts,
CollectionTable.queryString, CollectionTable.queryAttributes,
CollectionTable.queryCollections, CollectionTable.isVirtual FROM
CollectionTable WHERE ( remoteId = :0 AND resourceId = :1 )
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString)
Notification source akonadi_davgroupware_resource_10_12904_hrngU9 now
serving: () 
Lost connection to resource
org.freedesktop.Akonadi.Resource.akonadi_davgroupware_resource_10 ,
discarding cached interface


Restarting the Akondai server recovers from the problem.

An interesting clue is that if I suspend to RAM and then immediately resume
(within a minute) the error does not occur and everything is OK.

In my ~/.local/share/akonadi/mysql.conf file has:

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

-- 
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


[kontact] [Bug 334730] New: Kontact crash on logout

2014-05-13 Thread Dean Cording
https://bugs.kde.org/show_bug.cgi?id=334730

Bug ID: 334730
   Summary: Kontact crash on logout
Classification: Unclassified
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: d...@cording.id.au

Application: kontact (4.13.1)
KDE Platform Version: 4.13.1
Qt Version: 4.8.6
Operating System: Linux 3.13.0-26-generic i686
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
On logging out from KDE, Kontact crashed.  I had only been logged in for a few
minutes.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xaf6a4780 (LWP 3210))]

Thread 5 (Thread 0xacac7b40 (LWP 3211)):
#0  0xb770e424 in __kernel_vsyscall ()
#1  0xb317bd4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb60868ec in __pthread_cond_wait (cond=0xb57d5cb0, mutex=0xb57d5c98) at
forward.c:149
#3  0xb4f5d9ac in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4f5d9ff in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb3177f70 in start_thread (arg=0xacac7b40) at pthread_create.c:312
#6  0xb607970e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 4 (Thread 0xac19eb40 (LWP 3212)):
#0  0xb770e424 in __kernel_vsyscall ()
#1  0xb317bd4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb60868ec in __pthread_cond_wait (cond=0xac20c7dc, mutex=0xac20c7c4) at
forward.c:149
#3  0xb4f8c9f3 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4c68574 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb4f737c6 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb4f8c369 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb3177f70 in start_thread (arg=0xac19eb40) at pthread_create.c:312
#8  0xb607970e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 3 (Thread 0xa947db40 (LWP 3217)):
#0  0xb30d7120 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb3091515 in g_main_context_release () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb3092390 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb3092528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb63ce95f in QEventDispatcherGlib::processEvents (this=0xa8b00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#5  0xb639d823 in QEventLoop::processEvents (this=this@entry=0xa947d248,
flags=...) at kernel/qeventloop.cpp:149
#6  0xb639db49 in QEventLoop::exec (this=this@entry=0xa947d248, flags=...) at
kernel/qeventloop.cpp:204
#7  0xb628a23d in QThread::exec (this=this@entry=0x9794fc0) at
thread/qthread.cpp:537
#8  0xb628a38b in QThread::run (this=0x9794fc0) at thread/qthread.cpp:604
#9  0xb628cb6f in QThreadPrivate::start (arg=0x9794fc0) at
thread/qthread_unix.cpp:349
#10 0xb3177f70 in start_thread (arg=0xa947db40) at pthread_create.c:312
#11 0xb607970e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 2 (Thread 0xa71cdb40 (LWP 3227)):
#0  0xb770e424 in __kernel_vsyscall ()
#1  0xb6087392 in __GI___clock_gettime (clock_id=1, tp=0xa71ccfb8) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb62e78cc in do_gettime (frac=0xa71ccfb0, sec=0xa71ccfa8) at
tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0xb63d02a2 in updateCurrentTime (this=0xa7802c64) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0xa7802c64, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0xb63ce82b in timerSourcePrepareHelper (src=optimized out,
timeout=0xa71cd0ac) at kernel/qeventdispatcher_glib.cpp:143
#7  0xb63ce8bd in timerSourcePrepare (source=0xa7802c30, timeout=0xa71cd0ac) at
kernel/qeventdispatcher_glib.cpp:176
#8  0xb30919b3 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb30922df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb3092528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb63ce95f in QEventDispatcherGlib::processEvents (this=0xa78028c8,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#12 0xb639d823 in QEventLoop::processEvents (this=this@entry=0xa71cd218,
flags=...) at kernel/qeventloop.cpp:149
#13 0xb639db49 in QEventLoop::exec (this=this@entry=0xa71cd218, flags=...) at
kernel/qeventloop.cpp:204
#14 0xb628a23d in QThread::exec (this=this@entry=0x9b2d5e0) at
thread/qthread.cpp:537
#15 0xb637dc44 in QInotifyFileSystemWatcherEngine::run (this=0x9b2d5e0) at
io/qfilesystemwatcher_inotify.cpp:265
#16 0xb628cb6f in QThreadPrivate::start 

[Bug 293098] KAddressbook/Akonadi stores CATEGORIES escaped the wrong way

2012-02-09 Thread Dean Cording
https://bugs.kde.org/show_bug.cgi?id=293098


Dean Cording d...@cording.id.au changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1




--- Comment #1 from Dean Cording dean cording id au  2012-02-09 13:48:58 ---
*** This bug has been confirmed by popular vote. ***

-- 
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