[kontact] [Bug 170621] Pending to-do summary ignores summary configuration

2015-03-24 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=170621

gjditchfi...@acm.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from gjditchfi...@acm.org ---
To-do view configuration no longer provides these configuration options.

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


[kmail2] [Bug 326072] Scam detector misidentifies FQDN as numerical IP

2013-10-16 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=326072

--- Comment #2 from gjditchfi...@acm.org ---
Created attachment 82893
  -- https://bugs.kde.org/attachment.cgi?id=82893action=edit
mail message that triggers the scam detector

I deleted the original message, but this extract triggers the scam detector in
the same way.

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


[kmail2] [Bug 326072] New: Scam detector misidentifies FQDN as numerical IP

2013-10-15 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=326072

Bug ID: 326072
   Summary: Scam detector misidentifies FQDN as numerical IP
Classification: Unclassified
   Product: kmail2
   Version: 4.11.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: gjditchfi...@acm.org

The scam detector wrongly identifies Bruce Schneir's CRYPTO-GRAM newsletter for
October 15, 2013 as a scam. The details dialog says

This email contains a link which points to a numerical IP address
(baseball2.2ndhalfplays.com) instead of a typical textual website address. This
is often the case in scam emails.

That is not a numerical IP.

The link _is_ part of an example of a purported NSA malware site, but I don't
think that's what KMail is trying to warn be about...

Reproducible: Always

Steps to Reproduce:
1. Subscribe to CRYPTO-GRAM at http://www.schneier.com/crypto-gram.html.
2. Get it to send you the Oct 15, 2013 issue.
3. Open the issue.
Actual Results:  
The scam warning appears on the message.

Expected Results:  
No scam warning should appear, or no warning about the above link should
appear.

-- 
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 312197] New: Increasing font size causes horizontal spacing errors

2012-12-25 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=312197

Bug ID: 312197
   Summary: Increasing font size causes horizontal spacing errors
Classification: Unclassified
   Product: akregator
   Version: 4.9.4
  Hardware: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: internal browser
  Assignee: kdepim-bugs@kde.org
  Reporter: gjditchfi...@acm.org

When I view comp.risks articles with a font size that I have increased from the
default, for instance by typing Ctrl++, horizontal spacing between some
characters is incorrect. Characters may overlap or have excessive space between
them. The spacing errors often occur at transitions between alphabetic and
non-alphabetic characters.

Reproducible: Always

Steps to Reproduce:
1. Create a feed for URL
http://rss.gmane.org/messages/excerpts/gmane.comp.security.risks.
2. Visit the article titled Risks Digest 27.12. (Similar errors occur in
other articles.)
3. Note that the spacing around the URL in the text This issue is archived at
http://www.risks.org ... near the top of the article is correct.
4. Scroll roughly half-way down to the subsection Subject: 3D-Printing Firm
Makerbot Cracks Down On Printable Guns'. Note that the spacing of the many
occurences of 3D in the section is correct.
5. Enlarge the font size one step by typing Ctrl++.
6. Scroll back to the top. The spacing around the  and  characters that
surround the URL in This issue is archived ... is now incorrect.
7. Scroll back down to the section on 3D printing. Varying amounts of
horizontal space now appear between some of the 3 and D characters.
Actual Results:  
Described above.

Expected Results:  
Horizontal spacing should not change.

I will try to attach my akregatorrc and before-and-after screenshots.

From .kde/share/apps/akregator/data/feeds.opml:
   outline title=gmane.comp.security.risks useCustomFetchInterval=false
version=RSS maxArticleAge=60 description=
htmlUrl=http://permalink.gmane.org/gmane.comp.security.risks;
xmlUrl=http://rss.gmane.org/messages/excerpts/gmane.comp.security.risks;
fetchInterval=30 loadLinkedWebsite=true type=rss id=1652503191
archiveMode=globalDefault maxArticleNumber=1000
text=gmane.comp.security.risks/

-- 
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 312197] Increasing font size causes horizontal spacing errors

2012-12-25 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=312197

--- Comment #1 from gjditchfi...@acm.org ---
Created attachment 76015
  -- https://bugs.kde.org/attachment.cgi?id=76015action=edit
akregatorrc and screenshots.

akregatorrc and screenshots.

-- 
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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]

2010-12-21 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=193514


gjditchfi...@acm.org changed:

   What|Removed |Added

 CC|gjditchfi...@acm.org|




-- 
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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]

2010-05-22 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=193514





--- Comment #98 from  gjditchfield acm org  2010-05-22 17:14:46 ---
I haven't had this Kontact crash since I switched to KDE 4.4.2 on Karmic, but
Ryan Gordon is still affected with KDE 4.4.2 on Lucid, and Jon Skanes is
affected with KDE 4.4.1 on Karmic.

Some possible reasons for my good fortune:
- I'm using KDE 4.4.2 from the Launchpad PPA,
http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu karmic main
- I switched hardware and changed from the i386 Ubuntu variant to amd64.
- I copied my data files into a new home directory, so most of my old
preferences were destroyed.

-- 
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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]

2010-04-08 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=193514





--- Comment #86 from  gjditchfield acm org  2010-04-09 01:00:50 ---
This bug only has 140 votes.  The top 5 most hated bugs all have more than a
thousand.

If you want this bug to get some love, voting for it might help.

-- 
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 226241] New: Kontact from KDE SC 4.4.0 crashes on exit

2010-02-10 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=226241

   Summary: Kontact from KDE SC 4.4.0 crashes on exit
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: gjditchfi...@acm.org


Application: kontact (4.4)
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.1
Operating System: Linux 2.6.31-19-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
KDE SC 4.4 installed from the Kubuntu backports PPA. Kontact still crashes
every time I close it.

The crash can be reproduced every time.

 -- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0xb7736760 (LWP 1974))]

Thread 3 (Thread 0xb4487b70 (LWP 1975)):
#0  0x00efb832 in ?? () from /lib/ld-linux.so.2
#1  0x00a61bd3 in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0x009f8f57 in ?? () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xb3c02b70 (LWP 1976)):
#0  0x00efb832 in ?? () from /lib/ld-linux.so.2
#1  0x00a61bd3 in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0x009f8f57 in ?? () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb7736760 (LWP 1974)):
[KCrash Handler]
#6  0x00efb832 in ?? () from /lib/ld-linux.so.2
#7  0x009b5932 in abort () from /lib/tls/i686/cmov/libc.so.6
#8  0x009e8ee5 in ?? () from /lib/tls/i686/cmov/libc.so.6
#9  0x009f2ff1 in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0x009f46f2 in ?? () from /lib/tls/i686/cmov/libc.so.6
#11 0x009f77cd in free () from /lib/tls/i686/cmov/libc.so.6
#12 0x0059b6f1 in operator delete(void*) () from /usr/lib/libstdc++.so.6
#13 0x0194e8f3 in ~Private (this=0xbfa6a6ac, __in_chrg=value optimized out)
at ../../kcal/calendar.cpp:79
#14 ~Calendar (this=0xbfa6a6ac, __in_chrg=value optimized out) at
../../kcal/calendar.cpp:121
#15 0x019bb75f in ~CalendarResources (this=0x9ebd9a8, __in_chrg=value
optimized out) at ../../kcal/calendarresources.cpp:262
#16 0x01b510f3 in ~StdCalendar (this=0x9ebd9a8, __in_chrg=value optimized
out) at ../../korganizer/stdcalendar.cpp:109
#17 0x01b52d1f in K3StaticDeleterKOrg::StdCalendar::destructObject
(this=0x1b550e4) at /usr/include/KDE/../k3staticdeleter.h:174
#18 0x00d15274 in K3StaticDeleterPrivate::deleteStaticDeleters () at
../../kde3support/kdecore/k3staticdeleter.cpp:56
#19 0x007811f0 in qt_call_post_routines () at kernel/qcoreapplication.cpp:201
#20 0x02483f88 in ~QApplication (this=0xbfa6aea4, __in_chrg=value optimized
out) at kernel/qapplication.cpp:1014
#21 0x010f8a3a in ~KApplication (this=0xbfa6aea4, __in_chrg=value optimized
out) at ../../kdeui/kernel/kapplication.cpp:896
#22 0x010fffb8 in ~KUniqueApplication (this=0xbfa6aea4, __in_chrg=value
optimized out) at ../../kdeui/kernel/kuniqueapplication.cpp:372
#23 0x0804b551 in ~KontactApp (argc=1, argv=0xbfa6b0c4) at
../../../kontact/src/main.cpp:67
#24 main (argc=1, argv=0xbfa6b0c4) at ../../../kontact/src/main.cpp:227

This bug may be a duplicate of or related to bug 224277.

Possible duplicates by query: bug 224277, bug 222083, bug 198635.

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 224277] New: Kontact crashes on exit every time.

2010-01-25 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=224277

   Summary: Kontact crashes on exit every time.
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: gjditchfi...@acm.org


Application: kontact (4.4 rc2)
KDE Platform Version: 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2))
Qt Version: 4.6.0
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
Note: this is KDE 4.4 RC2, installed from karmic-backports as an upgrade to
RC1.The possible duplicate 222083 is from the RC1 release that I upgraded.

The crash can be reproduced every time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::deref (this=0x91acab8, __in_chrg=value optimized out) at
/usr/include/qt4/QtCore/qatomic_i386.h:132
#7  ~QList (this=0x91acab8, __in_chrg=value optimized out) at
/usr/include/qt4/QtCore/qlist.h:620
#8  ~QStringList (this=0x91acab8, __in_chrg=value optimized out) at
/usr/include/qt4/QtCore/qstringlist.h:67
#9  ~Private (this=0x91acab8, __in_chrg=value optimized out) at
../../kcal/calfilter.cpp:48
#10 ~CalFilter (this=0x91acab8, __in_chrg=value optimized out) at
../../kcal/calfilter.cpp:77
#11 0x024238e8 in ~Private (this=0x902e9c0, __in_chrg=value optimized out) at
../../kcal/calendar.cpp:79
#12 ~Calendar (this=0x902e9c0, __in_chrg=value optimized out) at
../../kcal/calendar.cpp:121
#13 0x0249075f in ~CalendarResources (this=0x902e9c0, __in_chrg=value
optimized out) at ../../kcal/calendarresources.cpp:262
#14 0x02b440f3 in ~StdCalendar (this=0x902e9c0, __in_chrg=value optimized
out) at ../../korganizer/stdcalendar.cpp:109
#15 0x02b45d1f in K3StaticDeleterKOrg::StdCalendar::destructObject
(this=0x2b480e4) at /usr/include/KDE/../k3staticdeleter.h:174
#16 0x0190a274 in K3StaticDeleterPrivate::deleteStaticDeleters () at
../../kde3support/kdecore/k3staticdeleter.cpp:56
#17 0x011553a0 in qt_call_post_routines () at kernel/qcoreapplication.cpp:201
#18 0x06f72738 in ~QApplication (this=0xbfee1cc4, __in_chrg=value optimized
out) at kernel/qapplication.cpp:1011
#19 0x0049f25a in ~KApplication (this=0xbfee1cc4, __in_chrg=value optimized
out) at ../../kdeui/kernel/kapplication.cpp:896
#20 0x004a67d8 in ~KUniqueApplication (this=0xbfee1cc4, __in_chrg=value
optimized out) at ../../kdeui/kernel/kuniqueapplication.cpp:372
#21 0x0804b541 in ~KontactApp (argc=1, argv=0xbfee1ee4) at
../../../kontact/src/main.cpp:67
#22 main (argc=1, argv=0xbfee1ee4) at ../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 222083, bug 224126.

Possible duplicates by query: bug 224126, bug 222083.

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 222083] New: Kontact crashes when I close it

2010-01-10 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=222083

   Summary: Kontact crashes when I close it
   Product: kontact
   Version: 4.4 rc1
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: gjditchfi...@acm.org


Application: kontact (4.4 rc1)
KDE Platform Version: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1))
Qt Version: 4.6.0
Operating System: Linux 2.6.31-17-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
I upgraded Kubuntu 9.10 from KDE SC 4.3.4 (installed from karmic-backports) to
KDE SC 4.4 RC1 (installed from ppa:kubuntu-ppa/beta).

When I log in, I get the Nepomuk Indexing Disabled dialog telling me that
Nepomuk is not running.

I then launch Kontact.  It opens with the Summary view and fetches mail.

I then close Kontact without leaving the Summary view.  Kontact crashes (four
times out of four so far.)

The crash can be reproduced every time.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::deref (this=0xaa02660, __in_chrg=value optimized out) at
/usr/include/qt4/QtCore/qatomic_i386.h:132
#7  ~QList (this=0xaa02660, __in_chrg=value optimized out) at
/usr/include/qt4/QtCore/qlist.h:620
#8  ~QStringList (this=0xaa02660, __in_chrg=value optimized out) at
/usr/include/qt4/QtCore/qstringlist.h:67
#9  ~Private (this=0xaa02660, __in_chrg=value optimized out) at
../../kcal/calfilter.cpp:48
#10 ~CalFilter (this=0xaa02660, __in_chrg=value optimized out) at
../../kcal/calfilter.cpp:77
#11 0x081588e8 in ~Private (this=0xa870f08, __in_chrg=value optimized out) at
../../kcal/calendar.cpp:79
#12 ~Calendar (this=0xa870f08, __in_chrg=value optimized out) at
../../kcal/calendar.cpp:121
#13 0x081c575f in ~CalendarResources (this=0xa870f08, __in_chrg=value
optimized out) at ../../kcal/calendarresources.cpp:262
#14 0x0291d0f3 in ~StdCalendar (this=0xa870f08, __in_chrg=value optimized
out) at ../../korganizer/stdcalendar.cpp:109
#15 0x0291ed1f in K3StaticDeleterKOrg::StdCalendar::destructObject
(this=0x29210e4) at /usr/include/KDE/../k3staticdeleter.h:174
#16 0x074f0274 in K3StaticDeleterPrivate::deleteStaticDeleters () at
../../kde3support/kdecore/k3staticdeleter.cpp:56
#17 0x00cac3a0 in qt_call_post_routines () at kernel/qcoreapplication.cpp:201
#18 0x00ff5738 in ~QApplication (this=0xbfd81474, __in_chrg=value optimized
out) at kernel/qapplication.cpp:1011
#19 0x00569eba in ~KApplication (this=0xbfd81474, __in_chrg=value optimized
out) at ../../kdeui/kernel/kapplication.cpp:896
#20 0x00571438 in ~KUniqueApplication (this=0xbfd81474, __in_chrg=value
optimized out) at ../../kdeui/kernel/kuniqueapplication.cpp:372
#21 0x0804b541 in ~KontactApp (argc=1, argv=0xbfd81694) at
../../../kontact/src/main.cpp:67
#22 main (argc=1, argv=0xbfd81694) at ../../../kontact/src/main.cpp:224

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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]

2010-01-05 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=193514





--- Comment #68 from  gjditchfield acm org  2010-01-06 02:27:42 ---
Could one of the maintainers tell us whether there is any hope of having this
bug fixed?  Or is it one of the problems that is just supposed to go away when
the great Akonadi rewrite is finished?

-- 
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 124111] create maildir folders (cur/, new/, tmp/) if they don't exist

2009-11-10 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=124111





--- Comment #2 from  gjditchfield acm org  2009-11-10 21:13:07 ---
This bug is still present in KMail Version 1.12.2 Using KDE 4.3.2 (KDE
4.3.2), as distributed with Kubuntu 9.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 170621] Pending to-do summary ignores summary configuration

2009-11-10 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=170621





--- Comment #2 from  gjditchfield acm org  2009-11-10 21:46:56 ---
This bug is still present in Kontact 4.3.2, as distributed in Kubuntu 9.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 213012] New: kontact crashed when launched

2009-11-03 Thread gjditchfield
https://bugs.kde.org/show_bug.cgi?id=213012

   Summary: kontact crashed when launched
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: gjditchfi...@acm.org


Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I woke my computer from hibernation and launched Kontact from krunner.  As far
as I knew, Kontact had shut down normally quite some time before hibernation. 
Akgregator would have ben running at hibernation time

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  0x00f2d1fc in QString (this=0x919d2d0) at
/usr/include/qt4/QtCore/qstring.h:711
#7  Kontact::Plugin::identifier (this=0x919d2d0) at
../../kontactinterfaces/plugin.cpp:97
#8  0x0031050e in Kontact::MainWindow::activatePluginModule (this=0x8f4c818) at
../../../kontact/src/mainwindow.cpp:303
#9  0x003105c4 in Kontact::MainWindow::setActivePluginModule (this=0x8f4c818,
module=...) at ../../../kontact/src/mainwindow.cpp:281
#10 0x0804bd0f in KontactApp::newInstance (this=0xbfd3c594) at
../../../kontact/src/main.cpp:147
#11 0x00994380 in KUniqueApplicationAdaptor::newInstance (this=0x8eea190,
asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459
#12 0x00994a92 in KUniqueApplicationAdaptor::qt_metacall (this=0x8eea190,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfd3bbbc) at
./kuniqueapplication_p.moc:75
#13 0x0034a7b4 in QDBusConnectionPrivate::deliverCall (this=0x8e59c98,
object=0x8eea190, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:891
#14 0x0034b9c5 in QDBusConnectionPrivate::activateCall (this=0x8e59c98,
object=0x8eea190, flags=337, msg=...) at qdbusintegrator.cpp:803
#15 0x0034c234 in QDBusConnectionPrivate::activateObject (this=0x8e59c98,
node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1347
#16 0x0034c4da in QDBusActivateObjectEvent::placeMetaCall (this=0x97d2bc8) at
qdbusintegrator.cpp:1464
#17 0x00c9b5fe in QObject::event (this=0xbfd3c594, e=0x97d2bc8) at
kernel/qobject.cpp:
#18 0x00c8affb in QCoreApplication::event (this=0xbfd3c594, e=0x97d2bc8) at
kernel/qcoreapplication.cpp:1434
#19 0x0105b9a6 in QApplication::event (this=0xbfd3c594, e=0x97d2bc8) at
kernel/qapplication.cpp:2317
#20 0x01055f54 in QApplicationPrivate::notify_helper (this=0x8e60d88,
receiver=0xbfd3c594, e=0x97d2bc8) at kernel/qapplication.cpp:4056
#21 0x0105d67c in QApplication::notify (this=0xbfd3c594, receiver=0xbfd3c594,
e=0x97d2bc8) at kernel/qapplication.cpp:3603
#22 0x0098cbfa in KApplication::notify (this=0xbfd3c594, receiver=0xbfd3c594,
event=0x97d2bc8) at ../../kdeui/kernel/kapplication.cpp:302
#23 0x00c8b6cb in QCoreApplication::notifyInternal (this=0xbfd3c594,
receiver=0xbfd3c594, event=0x97d2bc8) at kernel/qcoreapplication.cpp:610
#24 0x00c8c2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0,
data=0x8e41820) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x8e41820) at kernel/qcoreapplication.cpp:1247
#26 0x00c8c47d in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1140
#27 0x00cb63ff in QCoreApplication::sendPostedEvents (s=0x8e69eb0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#28 postEventSourceDispatch (s=0x8e69eb0) at
kernel/qeventdispatcher_glib.cpp:210
#29 0x0194de78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x01951720 in ?? () from /lib/libglib-2.0.so.0
#31 0x01951853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x00cb602c in QEventDispatcherGlib::processEvents (this=0x8e419f8,
flags=...) at kernel/qeventdispatcher_glib.cpp:327
#33 0x010f6be5 in QGuiEventDispatcherGlib::processEvents (this=0x8e419f8,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00c89c79 in QEventLoop::processEvents (this=0xbfd3c4f4, flags=) at
kernel/qeventloop.cpp:149
#35 0x00c8a0ca in QEventLoop::exec (this=0xbfd3c4f4, flags=...) at
kernel/qeventloop.cpp:201
#36 0x00c8c53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x01055dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x0804b4e6 in main (argc=1, argv=0xbfd3c7b4) at
../../../kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 212385

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

[Bug 170621] New: Pending to-do summary ignores summary configuration

2008-09-07 Thread gjditchfield
http://bugs.kde.org/show_bug.cgi?id=170621

   Summary: Pending to-do summary ignores summary configuration
   Product: kontact
   Version: 1.1
  Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: summary
AssignedTo: kdepim-bugs@kde.org
ReportedBy: [EMAIL PROTECTED]


Version:   1.1 (using 4.1.1 (KDE 4.1.1), Kubuntu packages)
Compiler:  cc
OS:Linux (i686) release 2.6.27-2-generic

I booted a Dell D600 from a Kubuntu Intrepid alpha 5 CD and launched Kontact. 
I created three to-dos
- single, start date 2008-09-09, due 2008-09-13, no time associated,
(default) reminder 15 minutes, description single, due soon
- long, start date 2008-09-06, due 2008-09-16, no time associated, default
reminder, no description
- recurring, start date 2008-09-13, due 2008-09-13, no time associated,
default reminder, description recurring todo, recurrence enabled, recurrence
monthly, every 1 months, on the 13 day.

The panel clock showed the date as 7 Sep 2008.

Back in the summary view, Pending To-dos showed recurring and single but
not long.  That was what I expected.

I selected Settings  Configure Summary View ... and in Pending To-dos Summary
Setup  I changed Show To-dos Due to Within the next month (31 days).  In
Hide Following To-do Types I checked off Completed and Unstarted (start
date is in the future).

Back in the summary view, Pending To-dos still showed only recurring and
single.  I expected it to show long, since the start date is in the past,
it is not completed, and it is due within 31 days.

Since the Hide Following To-do Types section is below the Show To-dos Due
section in configuration window, I expected the hide settings to override the
show settings.  In that case single should not show in the pending to-dos.  

In the Pending To-dos configuration, I changed the Show To-dos Due settings
to Within the next 12 days.  In the summary view, Pending To-dos still
shows recurring and single, but not long.


-- 
Configure bugmail: http://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 170579] New: Display to-dos if and only if start date has come

2008-09-06 Thread gjditchfield
http://bugs.kde.org/show_bug.cgi?id=170579

   Summary: Display to-dos if and only if start date has come
   Product: kontact
   Version: 1.1
  Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: summary
AssignedTo: kdepim-bugs@kde.org
ReportedBy: [EMAIL PROTECTED]


Version:   1.1 (using 4.1.1 (KDE 4.1.1), Kubuntu packages)
Compiler:  cc
OS:Linux (i686) release 2.6.27-2-generic

If a pending to-do has a start date, I want the summary view to display it if,
and only if, the start date is today or in the past.  I don't think I can get
Kontact to behave that way now.

In the Pending To-dos section of the Summary View configuration dialog, under
Hide following to-do types, I can check off Unstarted, which should do half
of what I want.  However, I think that a to-do with a start date in the past
will only appear in the summary if one of the conditions in Show To-dos Due
is true.

For instance, assume today is 2008-09-07, and I have a to-do with a start date
of 2008-09-01 and an end date of 2008-09-30.  Assume that the summary is
configured to show to-dos due within the next 7 days, and to hide unstarted
to-dos.  I want the to-do to show up in the summary now, but it won't appear
until the last week of the month.

If I change the settings to show to-dos due within the next month, the to-do
should appear, but so will a lot of other to-dos that I am not yet interested
in.

I suggest the following:
- remove the Unstarted checkbox from Hide Following To-do Types
- rename Show To-dos Due to Show Following To-do Types
- add a Ready (start date is in the past) checkbox to Show Following To-do
Types.


-- 
Configure bugmail: http://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