[Bug 268117] New: add address book from any groupware server eg. egroupware

2011-03-10 Thread Rainer Merz
https://bugs.kde.org/show_bug.cgi?id=268117

   Summary: add address book from any groupware server eg.
egroupware
   Product: kaddressbook
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: rainer.m...@uni.de
CC: to...@kde.org


Version:   unspecified (using KDE 4.6.0) 
OS:Linux

Kaddressbook only lists kolab, google address book or normal KDE or vcard etc..
if i want to add a new addressbook. Is it possible to add syncml resources or
webDAV. In KDE 3.4 I was able to add the addressbook of an eGroupware server to
the Kaddressbook in a similar way it is up to now possible to add calendars
from any server. Why this option in KDE 4 is removed?

Reproducible: Didn't try




OS: Linux (i686) release 2.6.35-27-generic
Compiler: cc

-- 
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 268120] New: Annoyed by Akonadi Startup Dialogs

2011-03-10 Thread Bernhard Beschow
https://bugs.kde.org/show_bug.cgi?id=268120

   Summary: Annoyed by Akonadi Startup Dialogs
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS/Version: Linux
Status: NEW
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: bbesc...@cs.tu-berlin.de


Version:   unspecified
OS:Linux

It is _very_ annoying to see various dialogs (bouncing progress bar, failed
self-test) showing up from Akonadi due to starting e.g. KMail. If the user is
not demanded, no dialog should appear whatsoever. In case of an error, a more
elegant solution should be found to tell the user (e.g. using KNotify).
Currently, users are overwhelmed with technical details if e.g. some database
error occurs. This adds bad reputation to Akonadi [1, 2], which is quiet
unfortunate given its technical brilliance.

[1] http://kubuntuforums.net/forums/index.php?topic=3115868.0
[2]
http://eyemeansit.wordpress.com/2011/03/03/migrating-from-kmail-to-evolution-or-thunderbird/

Reproducible: Didn't try

-- 
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 266031] wallet error when starting Kontact

2011-03-10 Thread Lars Scheiter
https://bugs.kde.org/show_bug.cgi?id=266031


Lars Scheiter lars.schei...@gonicus.de changed:

   What|Removed |Added

 CC||lars.schei...@gonicus.de




-- 
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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received

2011-03-10 Thread flying-sheep
https://bugs.kde.org/show_bug.cgi?id=86423





--- Comment #213 from  flying-sheep web de  2011-03-10 13:38:55 ---
(In reply to comment #212)
 +1 from me - this could likely mean knocking off 90% of the hassle with 10% of
 the effort ?
maybe it seems like that, but i am sorry for having to disappoint you:

the reply message is a html document, so you have two ways of inserting
another:
merging the latter into the further or an iframe.

while the iframe solution would indeed be a way to preserve the other message
in 100%, it is impossible or at least impractical (you have to store the
additional documents somewhere)

the merging solution, however, is what this bug is about in the first place: as
soon as you can merge in another message in a reliable way, you can edit it
anyway.

so sorry, no quick'n'dirty solution here.

-- 
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 268138] New: Crypto operations like verify and decrypt hang in the mail frontend after a few operations, cpu intensive

2011-03-10 Thread Bernhard E . Reiter
https://bugs.kde.org/show_bug.cgi?id=268138

   Summary: Crypto operations like verify and decrypt hang in the
mail frontend after a few operations, cpu intensive
   Product: KMail Mobile
   Version: unspecified
  Platform: Maemo 5
OS/Version: Linux
Status: NEW
  Keywords: komo3
  Severity: major
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: bernh...@intevation.de


I can reproduce on the N900 and the HTC Touch Pro2,
that after a few crypto operations, the crypto thread of kmail-mobile
seems to hang. 

Symptoms:
No other crypto operations completes in Kontact Touch Mail.
Can still operate and switch to other email otherwise.
Can do crypto operations on the command line. 
No dirmngr and no gpgsm running.
gpg-connect-agent gets prompt from the gpg-agent.
kontact-mobile getting all available CPU seen on top. 

How to reproduce:
E.g send yourself three emails: Signed only, signed and encrypted, encrypted
only.
Switch between all those emails back and forth.
After doing this up a few times (usually three times is enough),
the symptoms occur.

N900
Package: kdepim-mobile
Version: 4:4.6~.20110211.1251.git9d81e94-1maemo1.1219908
Package: libqt4-experimental-gui
Version: 4.7.0~git2010-0maemo1
Config-Version: 4.7.0~git2010-0maemo1

HTC Touch pro2:
Version build 20110217-1613 (I believe)

-- 
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 268138] Crypto operations like verify and decrypt hang in the mail frontend after a few operations, cpu intensive

2011-03-10 Thread Bernhard E . Reiter
https://bugs.kde.org/show_bug.cgi?id=268138





--- Comment #1 from Bernhard E. Reiter bernhard intevation de  2011-03-10 
16:30:03 ---
Oh, on the N900 it does not use dirmngr which in this version has other
defects:
cat .gnupg/gpgsm.conf
disable-crl-checks
prefer-system-dirmngr

-- 
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 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received

2011-03-10 Thread G . Gavranovic
https://bugs.kde.org/show_bug.cgi?id=86423





--- Comment #214 from G. Gavranovic gabrijel gavro nl  2011-03-10 16:53:42 ---
It's so bizarre that this problem is still not picked up; that the only
activity still is ... *discussing it*!!
Whatever happened to the pledgies? (see: http://pledgie.com/campaigns/7325 ).
I though this was finally going to be implemented?

In my opinion this is a never ending discussion. KMail was, and still is, a
beautiful mail client, but I'm getting a really strong vibe that it's
bleeding to its death. Developers can be very stubborn and on the other hand
users are getting more and more programs to choose from; I've given up and
moved on to 'greener pastures'.

It still is *very funny* to see the discussion flame up every once in a
while!

-- 
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 226527] Reply does not open composer window over NX connections

2011-03-10 Thread Tristan Miller
https://bugs.kde.org/show_bug.cgi?id=226527


Tristan Miller psychon...@nothingisreal.com changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DUPLICATE




--- Comment #5 from Tristan Miller psychonaut nothingisreal com  2011-03-10 
17:46:44 ---
Problem is recurring for me again, with both KDE 4.5 and 4.6.  But I've since
discovered this bug is a duplicate of Bug 201080.

*** This bug has been marked as a duplicate of bug 201080 ***

-- 
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 201080] The composer window does not appear when running KMail from an NX xterm session

2011-03-10 Thread Tristan Miller
https://bugs.kde.org/show_bug.cgi?id=201080


Tristan Miller psychon...@nothingisreal.com changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m




--- Comment #2 from Tristan Miller psychonaut nothingisreal com  2011-03-10 
17:46:44 ---
*** Bug 226527 has been marked as a duplicate of this bug. ***

-- 
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 201080] The composer window does not appear when running KMail from an NX xterm session

2011-03-10 Thread Tristan Miller
https://bugs.kde.org/show_bug.cgi?id=201080





--- Comment #3 from Tristan Miller psychonaut nothingisreal com  2011-03-10 
17:59:11 ---
I've been experiencing this problem off and on (mostly on) for over a year. 
I've tried everything I can think of to determine the cause, but it's a bit
difficult since it can't always be reproduced.  I suspect it may be a problem
on the local environment (i.e., the one running the NX client, not the one
running kmail).  I am able to reproduce the problem fairly consistently on my
main account running KDE 4.6.  When I log in with a different windowing
environment (for example, IceWM), the problem does not occur.  I also tried
creating a completely new user account and logging in with KDE 4.6; the problem
did not occur then.  So I went back to my normal account and deleted everything
in /tmp and almost every dot file and dot directory in my home directory
(~/.kde4, ~/.config, ~/.local, ~/.nx, etc.).  In ~/.kde4 I kept only the
application and configuration files for ktorrent, krdc, kopete, konsole,
amarok.  Even with this nearly-pristine home directory, the problem occurred. 
I also tried logging into KDE 4.6 and then replacing the running kwin window
manager with IceWM, but that didn't fix the problem.

Diederick, if there's anything you've done since filing this bug report which
has narrowed down the cause of the problem, or has solved it, please post that
information here.

-- 
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 268151] New: loading email

2011-03-10 Thread Chris
https://bugs.kde.org/show_bug.cgi?id=268151

   Summary: loading email
   Product: kontact
   Version: 4.4.10
  Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: crgla...@gmail.com


Application: kontact (4.4.10)
KDE Platform Version: 4.5.5 (KDE 4.5.5) release 1
Qt Version: 4.7.2
Operating System: Linux 2.6.34.7-0.7-desktop x86_64
Distribution: openSUSE 11.3 (x86_64)

-- Information about the crash:
- What I was doing when the application crashed:  Started Kontact and was
loading email.  Nothing else running that I am aware of.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  KMail::ActionScheduler::actionMessage (this=0x18bb290, res=value optimized
out) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:675
#7  0x7f651f9646a5 in KMail::ActionScheduler::filterMessage
(this=0x18bb290) at /usr/src/debug/kdepim-4.4.10/kmail/actionscheduler.cpp:648
#8  0x7f651f964a54 in KMail::ActionScheduler::qt_metacall (this=0x18bb290,
_c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fff7c131700)
at /usr/src/debug/kdepim-4.4.10/build/kmail/actionscheduler.moc:130
#9  0x7f65394db88f in QMetaObject::activate (sender=0x18b2080, m=value
optimized out, local_signal_index=value optimized out, argv=0x0) at
kernel/qobject.cpp:3278
#10 0x7f65394da239 in QObject::event (this=0x18b2080, e=value optimized
out) at kernel/qobject.cpp:1181
#11 0x7f6538881114 in QApplicationPrivate::notify_helper (this=0x642d40,
receiver=0x18b2080, e=0x7fff7c131ea0) at kernel/qapplication.cpp:4462
#12 0x7f65388896aa in QApplication::notify (this=value optimized out,
receiver=0x18b2080, e=0x7fff7c131ea0) at kernel/qapplication.cpp:4341
#13 0x7f6539e09876 in KApplication::notify (this=0x7fff7c132260,
receiver=0x18b2080, event=0x7fff7c131ea0) at
/usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310
#14 0x7f65394c663c in QCoreApplication::notifyInternal
(this=0x7fff7c132260, receiver=0x18b2080, event=0x7fff7c131ea0) at
kernel/qcoreapplication.cpp:731
#15 0x7f65394f3ee8 in sendEvent (this=0x640130) at
kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x640130) at
kernel/qeventdispatcher_unix.cpp:619
#17 0x7f65394f0c58 in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:231
#19 0x7f6530b95a93 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#20 0x7f6530b96270 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x7f6530b96510 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#22 0x7f65394f130f in QEventDispatcherGlib::processEvents (this=0x6132c0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:422
#23 0x7f6538926b8e in QGuiEventDispatcherGlib::processEvents (this=value
optimized out, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:204
#24 0x7f65394c5a72 in QEventLoop::processEvents (this=value optimized
out, flags=...) at kernel/qeventloop.cpp:149
#25 0x7f65394c5c85 in QEventLoop::exec (this=0x7fff7c1321b0, flags=...) at
kernel/qeventloop.cpp:201
#26 0x7f65394ca0eb in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1008
#27 0x0040417e in _start ()

Possible duplicates by query: bug 267496, bug 267387, bug 267073, bug 267057,
bug 267056.

Reported using DrKonqi

-- 
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 268153] New: IMAP Filtering

2011-03-10 Thread Chris
https://bugs.kde.org/show_bug.cgi?id=268153

   Summary: IMAP Filtering
   Product: kontact
   Version: 4.4.10
  Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: crgla...@gmail.com


Application: kontact (4.4.10)
KDE Platform Version: 4.5.5 (KDE 4.5.5) release 1
Qt Version: 4.7.2
Operating System: Linux 2.6.34.7-0.7-desktop x86_64
Distribution: openSUSE 11.3 (x86_64)

-- Information about the crash:
- What I was doing when the application crashed: This is ridiculous!  I can't
get more than two emails viewed and Kontact crashes.  I was manually filtering
IMAP mail.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fdaed0aa760 (LWP 8709))]

Thread 5 (Thread 0x7fdac72eb710 (LWP 8729)):
#0  0x7fdae53c439c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fdaeb48d73b in wait (this=value optimized out, mutex=0xb28810,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=value optimized out, mutex=0xb28810,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x7fdad16373f6 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0xf7c640,
th=0x15eeb50) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WeaverImpl.cpp:365
#4  0x7fdad1639e45 in waitForAvailableJob (this=0xd93740, th=0x15eeb50) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WeaverImpl.cpp:356
#5  ThreadWeaver::WorkingHardState::applyForWork (this=0xd93740, th=0x15eeb50)
at /usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WorkingHardState.cpp:71
#6  0x7fdad16377ef in ThreadWeaver::ThreadRunHelper::run
(this=0x7fdac72eae30, parent=0xf7c640, th=0x15eeb50) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/Thread.cpp:87
#7  0x7fdad1637878 in ThreadWeaver::Thread::run (this=0x15eeb50) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/Thread.cpp:142
#8  0x7fdaeb48d055 in QThreadPrivate::start (arg=0x15eeb50) at
thread/qthread_unix.cpp:320
#9  0x7fdae53bfa4f in start_thread () from /lib64/libpthread.so.0
#10 0x7fdaea1cf82d in clone () from /lib64/libc.so.6
#11 0x in ?? ()

Thread 4 (Thread 0x7fdac6aea710 (LWP 8732)):
#0  0x7fdae53c439c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fdaeb48d73b in wait (this=value optimized out, mutex=0xb28810,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=value optimized out, mutex=0xb28810,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x7fdad16373f6 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0xf7c640,
th=0x169be30) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WeaverImpl.cpp:365
#4  0x7fdad1639e45 in waitForAvailableJob (this=0xd93740, th=0x169be30) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WeaverImpl.cpp:356
#5  ThreadWeaver::WorkingHardState::applyForWork (this=0xd93740, th=0x169be30)
at /usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WorkingHardState.cpp:71
#6  0x7fdad1639e5e in ThreadWeaver::WorkingHardState::applyForWork
(this=0xd93740, th=0x169be30) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WorkingHardState.cpp:74
#7  0x7fdad16377ef in ThreadWeaver::ThreadRunHelper::run
(this=0x7fdac6ae9e30, parent=0xf7c640, th=0x169be30) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/Thread.cpp:87
#8  0x7fdad1637878 in ThreadWeaver::Thread::run (this=0x169be30) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/Thread.cpp:142
#9  0x7fdaeb48d055 in QThreadPrivate::start (arg=0x169be30) at
thread/qthread_unix.cpp:320
#10 0x7fdae53bfa4f in start_thread () from /lib64/libpthread.so.0
#11 0x7fdaea1cf82d in clone () from /lib64/libc.so.6
#12 0x in ?? ()

Thread 3 (Thread 0x7fdac62e9710 (LWP 8735)):
#0  0x7fdae53c439c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fdaeb48d73b in wait (this=value optimized out, mutex=0xb28810,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=value optimized out, mutex=0xb28810,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x7fdad16373f6 in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned (this=0xf7c640,
th=0x13dd590) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WeaverImpl.cpp:365
#4  0x7fdad1639e45 in waitForAvailableJob (this=0xd93740, th=0x13dd590) at
/usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WeaverImpl.cpp:356
#5  ThreadWeaver::WorkingHardState::applyForWork (this=0xd93740, th=0x13dd590)
at /usr/src/debug/kdelibs-4.5.5/threadweaver/Weaver/WorkingHardState.cpp:71
#6  0x7fdad1639e5e in 

[Bug 257097] Categories (nepomuk) dont'run

2011-03-10 Thread Marco Roeder
https://bugs.kde.org/show_bug.cgi?id=257097


Marco Roeder m...@marco-roeder.net changed:

   What|Removed |Added

 CC||m...@marco-roeder.net




--- Comment #4 from Marco Roeder mail marco-roeder net  2011-03-11 01:19:39 
---
I can confirm the issue. It has been there since quite a while. 

I'm attaching screenshots of what goes wrong. 

Screenshot 1: New User Test created. No categories (in German: Kategorien) so
far. 
Screenshot 2: Opened the edit categories window. We see that there are some
categories, but there are no  names attached to them. 
Screenshot 3: Created a new category Test
Screenshot 4: The edit category window is closed. KAddressbook shows a nepomuk
resource identifier in the categories box
Screenshot 5: Opened again the edit categories window. We see a number of
things: the number of entries increased by one, but again all names are empty.
Also, all entries are ticked now. Expected behaviour would be that we have a
Test entry that is ticked.
Screenshot 6: Closed the categories window and opened it again. Now the number
of categories increased again significantly. 

KAddressbook 4.4.9, KDE 4.6.1. from KDE Backports repository, running on
Kubuntu 10.10

-- 
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 268182] New: Kontact spanish version

2011-03-10 Thread bauchwitzgj
https://bugs.kde.org/show_bug.cgi?id=268182

   Summary: Kontact spanish version
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: bauchwit...@hotmail.com


Version:   unspecified (using KDE 4.4.5) 
OS:Linux

I need something for convert the english version in spanish one. Can you help
me?


Reproducible: Always

-- 
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 268188] New: Trying to open an attachment caused a crash

2011-03-10 Thread Con Kolivas
https://bugs.kde.org/show_bug.cgi?id=268188

   Summary: Trying to open an attachment caused a crash
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: k...@kolivas.org


Application: kmail (1.13.5)
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.0
Operating System: Linux 2.6.35.11-ck1-1 x86_64
Distribution: Ubuntu 10.10

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

There was an excel spreadsheet attachment in the email I had selected and I
tried to open it in the selected application oo.o and it crashed.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f45af293820 (LWP 16083))]

Thread 2 (Thread 0x7f458afc0700 (LWP 16086)):
#0  0x7f45abc2b203 in __poll (fds=value optimized out, nfds=value
optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f45a37c7009 in ?? () from /lib/libglib-2.0.so.0
#2  0x7f45a37c745c in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#3  0x7f45ac5851e6 in QEventDispatcherGlib::processEvents (this=0x181c420,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:417
#4  0x7f45ac557a02 in QEventLoop::processEvents (this=value optimized
out, flags=) at kernel/qeventloop.cpp:149
#5  0x7f45ac557dec in QEventLoop::exec (this=0x7f458afbfcf0, flags=) at
kernel/qeventloop.cpp:201
#6  0x7f45ac4622fd in QThread::exec (this=value optimized out) at
thread/qthread.cpp:490
#7  0x7f45ac5375f8 in QInotifyFileSystemWatcherEngine::run (this=0x1940c10)
at io/qfilesystemwatcher_inotify.cpp:248
#8  0x7f45ac46527e in QThreadPrivate::start (arg=0x1940c10) at
thread/qthread_unix.cpp:266
#9  0x7f45a9815971 in start_thread (arg=value optimized out) at
pthread_create.c:304
#10 0x7f45abc3792d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x in ?? ()

Thread 1 (Thread 0x7f45af293820 (LWP 16083)):
[KCrash Handler]
#6  0x7f45add2a4a3 in KMHandleAttachmentCommand::slotStart (this=0x1c73ab0)
at ../../kmail/kmcommands.cpp:3035
#7  0x7f45add2cc16 in KMHandleAttachmentCommand::qt_metacall
(this=0x1c73ab0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=0x1aa8350) at ./kmcommands.moc:2571
#8  0x7f45ac56abde in QObject::event (this=0x1c73ab0, e=0x1c73ab0) at
kernel/qobject.cpp:1219
#9  0x7f45aca43fdc in QApplicationPrivate::notify_helper (this=0x11eb080,
receiver=0x1c73ab0, e=0x1e0fe60) at kernel/qapplication.cpp:4396
#10 0x7f45aca49aed in QApplication::notify (this=0x7fff807de2f0,
receiver=0x1c73ab0, e=0x1e0fe60) at kernel/qapplication.cpp:4277
#11 0x7f45aeca0a36 in KApplication::notify (this=0x7fff807de2f0,
receiver=0x1c73ab0, event=0x1e0fe60) at ../../kdeui/kernel/kapplication.cpp:311
#12 0x7f45ac558cdc in QCoreApplication::notifyInternal
(this=0x7fff807de2f0, receiver=0x1c73ab0, event=0x1e0fe60) at
kernel/qcoreapplication.cpp:732
#13 0x7f45ac55bc22 in sendEvent (receiver=0x0, event_type=value optimized
out, data=0x1185250) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value
optimized out, data=0x1185250) at kernel/qcoreapplication.cpp:1373
#15 0x7f45ac585653 in sendPostedEvents (s=0x11e9110) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#16 postEventSourceDispatch (s=0x11e9110) at
kernel/qeventdispatcher_glib.cpp:277
#17 0x7f45a37c3342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x7f45a37c72a8 in ?? () from /lib/libglib-2.0.so.0
#19 0x7f45a37c745c in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#20 0x7f45ac585193 in QEventDispatcherGlib::processEvents (this=0x11849b0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:415
#21 0x7f45acaf6a4e in QGuiEventDispatcherGlib::processEvents
(this=0x1c73ab0, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:204
#22 0x7f45ac557a02 in QEventLoop::processEvents (this=value optimized
out, flags=) at kernel/qeventloop.cpp:149
#23 0x7f45ac557dec in QEventLoop::exec (this=0x7fff807de120, flags=) at
kernel/qeventloop.cpp:201
#24 0x7f45ac55bebb in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1009
#25 0x00403212 in main (argc=value optimized out, argv=value
optimized out) at ../../kmail/main.cpp:156

Reported using DrKonqi

-- 
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 268189] New: kmail crashed

2011-03-10 Thread maneeshsingh00
https://bugs.kde.org/show_bug.cgi?id=268189

   Summary: kmail crashed
   Product: kmail
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: maneeshsing...@gmail.com


Version:   unspecified
OS:Linux



Reproducible: Didn't try

-- 
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 268189] kmail crashed

2011-03-10 Thread maneeshsingh00
https://bugs.kde.org/show_bug.cgi?id=268189





--- Comment #1 from  maneeshsingh00 gmail com  2011-03-11 06:22:28 ---
Created an attachment (id=57853)
 -- (http://bugs.kde.org/attachment.cgi?id=57853)
kmail crashed

-- 
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 264861] Google calendar and contacts don't work

2011-03-10 Thread Max
https://bugs.kde.org/show_bug.cgi?id=264861


Max haz...@gmail.com changed:

   What|Removed |Added

 CC||haz...@gmail.com




--- Comment #18 from Max hazica gmail com  2011-03-11 08:58:25 ---
Can only confirm the bug with Kubuntu 10.10 and KDE 4.6. Never tried it with
4.5, but in 4.6 i can't even add the google calendar resource straight away.
Instead I create an empty resource first, then add the gcal plugin; results as
described above.

Any developer feedback?

Thanks

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- 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