[Bug 273774] New: zombied Kontact process crashed when closed via TERM signal

2011-05-20 Thread ytzemih
https://bugs.kde.org/show_bug.cgi?id=273774

   Summary: zombied Kontact process crashed when closed via TERM
signal
   Product: kontact
   Version: 4.4.10
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ytze...@yahoo.de


Application: kontact (4.4.10)
KDE Platform Version: 4.6.3 (4.6.3)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic x86_64
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:
 - I chose the krunner task manager to send TERM
 - Kontact crashed

- Reason for this:
 - very often KMail cannot be restarted (for some reason unkown to me)
 - One way is to log out, restart the machine or just to stop an existing
kontact process by TERM/KILL signal

Although the bug report doesnt give any insight to me, there are some BOOST and
GPG references. I'm using GPG with KMail. Maybe the professionals can use these
hints.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x7fdbea548aab in QDBusAdaptorConnector::relaySlot (this=0x1292080,
argv=0x7fdbc93a3130) at qdbusabstractadaptor.cpp:270
#7  0x7fdbea548de5 in QDBusAdaptorConnector::qt_metacall (this=0x1292080,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fdbc93a3130)
at qdbusabstractadaptor.cpp:366
#8  0x7fdbec4765f8 in QMetaObject::activate (sender=0x12c1770, m=, local_signal_index=, argv=0x7fdbc93a3130)
at kernel/qobject.cpp:3287
#9  0x7fdbec476b0f in QObject::destroyed (this=,
_t1=0x12c1770) at .moc/release-shared/moc_qobject.cpp:149
#10 0x7fdbec4781f7 in QObject::~QObject (this=0x12c1770, __in_chrg=) at kernel/qobject.cpp:843
#11 0x7fdbea8fab79 in KIO::Scheduler::~Scheduler (this=0x12c1770,
__in_chrg=) at ../../kio/kio/scheduler.cpp:770
#12 0x7fdbea8ffef6 in ~SchedulerPrivate () at
../../kio/kio/scheduler.cpp:668
#13 destroy () at ../../kio/kio/scheduler.cpp:734
#14 0x7fdbebca5961 in __run_exit_handlers (status=-1) at exit.c:78
#15 exit (status=-1) at exit.c:100
#16 0x7fdbd0132f3a in kmsignalHandler (sigId=15) at
../../kmail/kmstartup.cpp:59
#17 
#18 __lll_lock_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:134
#19 0x7fdbe5c3e5b4 in _L_lock_944 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#20 0x7fdbe5c3e3ca in __pthread_mutex_lock (mutex=0x7fdbcd8e7480) at
pthread_mutex_lock.c:61
#21 0x7fdbcd6d171c in ?? () from /usr/lib/libgpgme-pthread.so.11
#22 0x7fdbcd6d17de in ?? () from /usr/lib/libgpgme-pthread.so.11
#23 0x7fdbcd6cf10f in ?? () from /usr/lib/libgpgme-pthread.so.11
#24 0x7fdbcd6cf3df in ?? () from /usr/lib/libgpgme-pthread.so.11
#25 0x7fdbcd6ce0e3 in ?? () from /usr/lib/libgpgme-pthread.so.11
#26 0x7fdbcd6c7247 in ?? () from /usr/lib/libgpgme-pthread.so.11
#27 0x7fdbcd6c1abe in gpgme_op_keylist_start () from
/usr/lib/libgpgme-pthread.so.11
#28 0x7fdbce850b4e in GpgME::Context::startKeyListing (this=, pattern=, secretOnly=) at ../../gpgme++/context.cpp:458
#29 0x7fdbce850beb in GpgME::Context::startKeyListing (this=, patterns=, secretOnly=) at ../../gpgme++/context.cpp:466
#30 0x7fdbceb0cd98 in do_list_keys (ctx=0x4377d90, pats=, keys=..., secretOnly=false) at
../../libkleo/backends/qgpgme/qgpgmekeylistjob.cpp:69
#31 0x7fdbceb0d959 in list_keys (ctx=0x4377d90, pats=..., secretOnly=false)
at ../../libkleo/backends/qgpgme/qgpgmekeylistjob.cpp:87
#32 0x7fdbceb104a9 in operator(), QString, GpgME::Error>,
boost::tuples::tuple, QString,
GpgME::Error> (*)(GpgME::Context*, QStringList, bool),
boost::_bi::list1 > (function_obj_ptr=)
at /usr/include/boost/bind/bind.hpp:382
#33 operator() (function_obj_ptr=) at
/usr/include/boost/bind/bind_template.hpp:32
#34 operator(), QString, GpgME::Error>,
boost::_bi::bind_t, QString, GpgME::Error>,
boost::tuples::tuple, QString,
GpgME::Error> (*)(GpgME::Context*, QStringList, bool),
boost::_bi::list3, boost::_bi::value,
boost::_bi::value > >, boost::_bi::list0> (function_obj_ptr=) at /usr/include/boost/bind/bind.hpp:243
#35 operator() (function_obj_ptr=) at
/usr/include/boost/bind/bind_template.hpp:20
#36
boost::detail::function::function_obj_invoker0 >, QString, GpgME::Error,
boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type,
boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>,
boost::tuples::tuple >, QString, GpgME::Error, boost::tuples::null_type,
boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type,
boost::tuples::null_type, boost::tuples::null_type> (*)(GpgME::Context*,
QStringList, bool), boost::_bi::list3,
boost::_bi::value, boost::_bi::value > >,
boost::_bi::list1 > >,
boost::tuples::tuple >, QString, GpgME::Error, boost::tuples::null_type,
boo

[Bug 245288] When signing the pinentry dialog flickers for a few seconds and then signing fails

2011-05-12 Thread ytzemih
https://bugs.kde.org/show_bug.cgi?id=245288


ytze...@yahoo.de changed:

   What|Removed |Added

 CC||ytze...@yahoo.de




--- Comment #1 from2011-05-12 09:21:53 ---
Can confirm this bug for Kubuntu 11.04 amd64

-- 
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 203251] column size kmail list

2011-02-07 Thread ytzemih
https://bugs.kde.org/show_bug.cgi?id=203251


ytze...@yahoo.de changed:

   What|Removed |Added

 CC||ytze...@yahoo.de




--- Comment #12 from2011-02-07 21:34:51 ---
Can still confirm this bug with kmail --version
Qt: 4.7.0
KDE: 4.6.00 (4.6.0)
KMail: 2.0.89

For me the columns are always too narrow, seems like an internal, type-specific
default value is always taken instead of some logged settings. This behaviour
significantly reduces useability of kmail, which is functionally already quite
good.

-- 
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 244880] Regression: autocompletion does not work in 'To' field anymore

2011-02-02 Thread ytzemih
https://bugs.kde.org/show_bug.cgi?id=244880


ytze...@yahoo.de changed:

   What|Removed |Added

 CC||ytze...@yahoo.de




--- Comment #8 from2011-02-02 17:00:27 ---
Can confirm this bug, I first used KDE 4.6 RC2 and updated to the 4.6 release,
both under Kubuntu Maverik. All my contacts are located in one source of type
"single vcf files". kmail -v says:
Qt: 4.7.0
KDE: 4.6.00 (4.6.0)
KMail: 2.0.89

-- 
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 250373] kmail2 migration fails for cached imap

2010-12-28 Thread ytzemih
https://bugs.kde.org/show_bug.cgi?id=250373


ytze...@yahoo.de changed:

   What|Removed |Added

 CC||ytze...@yahoo.de




--- Comment #1 from2010-12-28 12:32:58 ---
Can confirm this bug. 

I just updated my ubuntu 10.10 to KDE 4.6 RC1 as well as to KDEPIM 4.6.
When starting Kontact, the Kmail migration wizard showed up. I've got two POP3
accounts (for whom migration was successful) and a single disconnected imap
account which causes the error message "the migration of XYZ to Akonadi
ressource has failed: resource XYZ did not create any directories". Next, the
wizard tells me, that he starts the import of the local cache of XYZ and seems
to never stop. After killing the wizard, I tried to cancel it at the next start
of Kontact/KMail, but KMail does not start either.

-- 
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 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf

2010-10-08 Thread ytzemih
https://bugs.kde.org/show_bug.cgi?id=226630





--- Comment #3 from2010-10-08 09:11:44 ---
I found out that kwatchgnupg makes changes in the files 
  gpg.conf, 
  gpgsm.conf and 
  gpg-agent.conf. 
It adds lines like 
 log-file socket:///path/to/.gnupg/log-socket
 debug-level basic
who seem not to be understood by gpg.
Really annoying, as Kleopatra and depending programs like KMail are rather
frequently used in KDE in these days.

-- 
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 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf

2010-09-24 Thread ytzemih
https://bugs.kde.org/show_bug.cgi?id=226630


ytze...@yahoo.de changed:

   What|Removed |Added

 CC||ytze...@yahoo.de




--- Comment #2 from2010-09-24 10:37:45 ---
Experienced exactly the same: These generated lines in gpg.conf make Kleopatra
disappearing several keys. They are in consequence not available to kmail
anymore.

gpg: /path/to/.gnupg/gpg.conf:247: invalid option

For Kubuntu 10.04 (gnupg 1.4.10), the option "debug-level basic" (here in line
247) seems not be known to this gnupg-version.

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