[kmail2] [Bug 467796] Two Kmail icons appearing in dock

2024-04-11 Thread Scott Newton
https://bugs.kde.org/show_bug.cgi?id=467796

Scott Newton  changed:

   What|Removed |Added

 CC||sco...@quantumchaos451.co.n
   ||z

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

[kmail2] [Bug 466124] kmail preview pane empty on wayland nvidia

2023-04-07 Thread Scott Newton
https://bugs.kde.org/show_bug.cgi?id=466124

Scott Newton  changed:

   What|Removed |Added

 CC||sco...@quantumchaos451.co.n
   ||z

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

[akregator] [Bug 458116] Articles spilling from one feed to another

2022-11-14 Thread Scott Newton
https://bugs.kde.org/show_bug.cgi?id=458116

--- Comment #29 from Scott Newton  ---
Tried 5.100 - it does not fix it. Given that this is basically a data
corruption 
issue I'm surprised it hasn't been given higher priority.

Thanks

On Sunday, 13 November 2022 12:15:48 AM NZDT Colin J Thomson wrote:
> https://bugs.kde.org/show_bug.cgi?id=458116

> Is the fix coming in 5.100 who knows?
> So for now I will stick with kio* 5.98

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

[akregator] [Bug 458116] Articles spilling from one feed to another

2022-08-28 Thread Scott Newton
https://bugs.kde.org/show_bug.cgi?id=458116

Scott Newton  changed:

   What|Removed |Added

 CC||sco...@quantumchaos451.co.n
   ||z

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

[kmail2] [Bug 457894] New: DKIM plugin treats ed25119 signed messages as invalid

2022-08-14 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=457894

Bug ID: 457894
   Summary: DKIM plugin treats ed25119 signed messages as invalid
   Product: kmail2
   Version: 5.15.3
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@kitterman.com
  Target Milestone: ---

SUMMARY
***
With the DKIM plugin enabled, it appears to treat signatures which use the
ed25519 as invalid.  Ed25519 was added to DKIM by RFC 8463.  Even if RFC 8463
is not supported, according to the current main DKIM RFC, RFC 6376, signatures
with unknown algorithms must be ignored (Paragraph 3.3.4).  A dual signed
RSA-SHA256/ed25519 message should show as DKIM: valid if the RSA signature
verifies.  This appears not to be the case.
***


STEPS TO REPRODUCE
1. Enable DKIM plugin
2. Receive dual DKIM signed RSA-SHA256/ed25519 message
3. Select the message

OBSERVED RESULT
DKIM: invalid

EXPECTED RESULT
DKIM: valid

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

ADDITIONAL INFORMATION
Addition of ed25519 to DKIM is relatively recent and so such signatures can be
difficult to come by.  If anyone needs a representative email to evaluate this
with, please contact me and let me know.  I'll be glad to send it.

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

[Akonadi] [Bug 402780] Akonadi doesn't work with Exchange again

2020-10-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=402780

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[Akonadi] [Bug 422410] EWS resource uses 100% CPU when its target server becomes inaccessible

2020-10-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=422410

John Scott  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||jsc...@posteo.net
 Status|REPORTED|CONFIRMED

--- Comment #1 from John Scott  ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I can reproduce this every time on Debian Bullseye if, for example, I
disconnect my computer from the Internet but don't tell KMail to 'Go Offline.'

Two processes seem to eat the CPU, and I don't know what their relation is:
akonadi_ews_res and http_so. Here's a crummy backtrace from when I stopped the
former:
#0  0x7f894330f4bf in __GI___poll (fds=0x5614f8a31510, nfds=8, timeout=40)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f893e859dce in g_main_context_poll
(priority=, n_fds=8, fds=0x5614f8a31510, timeout=, context=0x7f8930005000) at ../../../glib/gmain.c:4395
#2  g_main_context_iterate (context=context@entry=0x7f8930005000,
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at ../../../glib/gmain.c:4087
#3  0x7f893e859eef in g_main_context_iteration (context=0x7f8930005000,
may_block=may_block@entry=1) at ../../../glib/gmain.c:4157
#4  0x7f89438bf31b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5614f84d4be0, flags=...)
at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f89438684db in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffc114e3b90, flags=...,
flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#6  0x7f8943870782 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#7  0x7f894c80faae in Akonadi::ResourceBase::init(Akonadi::ResourceBase&)
() at /lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#8  0x5614f6c2d1c3 in  ()
#9  0x7f8943242cca in __libc_start_main (main=0x5614f6bdaa10, argc=3,
argv=0x7ffc114e3e78, init=, fini=,
rtld_fini=, stack_end=0x7ffc114e3e68) at ../csu/libc-start.c:308
#10 0x5614f6bdf33a in  ()

and from the latter:
#0  0x7f3da04c25b6 in __ppoll (fds=fds@entry=0x7ffec64504e8,
nfds=nfds@entry=1, timeout=, timeout@entry=0x7ffec6450480,
sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44
#1  0x7f3da08872a0 in ppoll (__ss=, __timeout=, __nfds=, __fds=)
at /usr/include/x86_64-linux-gnu/bits/poll2.h:77
#2  qt_ppoll (timeout_ts=0x7ffec6450480, nfds=1, fds=0x7ffec64504e8) at
kernel/qcore_unix.cpp:132
#3  qt_ppoll (timeout_ts=0x7ffec6450480, nfds=1, fds=0x7ffec64504e8) at
kernel/qcore_unix.cpp:129
#4  qt_safe_poll (fds=fds@entry=0x7ffec64504e8, nfds=nfds@entry=1,
timeout_ts=0x7ffec64504f0) at kernel/qcore_unix.cpp:164
#5  0x7f3d9c5d27a2 in qt_poll_msecs (nfds=1, timeout=,
fds=0x7ffec64504e8)
at
../../include/QtCore/5.14.2/QtCore/private/../../../../../src/corelib/kernel/qcore_unix_p.h:381
#6  QNativeSocketEnginePrivate::nativeSelect (this=this@entry=0x56127de01fc0,
timeout=, checkRead=checkRead@entry=true,
checkWrite=checkWrite@entry=false,
selectForRead=selectForRead@entry=0x7ffec64505c6,
selectForWrite=0x7ffec64505c7)
at socket/qnativesocketengine_unix.cpp:1435
#7  0x7f3d9c5d0271 in QNativeSocketEngine::waitForReadOrWrite
(this=0x56127de02b00, readyToRead=0x7ffec64505c6,
readyToWrite=, checkRead=,
checkWrite=, msecs=, timedOut=0x0)
at socket/qnativesocketengine.cpp:1120
#8  0x7f3d9c5c37b6 in QAbstractSocket::waitForReadyRead
(this=0x56127de038c0, msecs=6)
at
../../include/QtCore/5.14.2/QtCore/private/../../../../../src/corelib/tools/qringbuffer_p.h:218
#9  0x7f3d9c7b90e8 in KIO::ConnectionBackend::waitForIncomingTask
(this=0x56127de05d90, ms=6) at ./src/core/connectionbackend.cpp:168
#10 0x7f3d9c7b9dc5 in KIO::Connection::waitForIncomingTask (this=, ms=ms@entry=6) at ./src/core/connection.cpp:204
#11 0x7f3d9c814cdd in KIO::SlaveBase::dispatchLoop (this=0x7ffec6450730) at
./src/core/slavebase.cpp:328
#12 0x7f3d9b01fda2 in kdemain () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so
#13 0x56127d771c5d in ?? ()
#14 0x56127d772d4a in ?? ()
#15 0x56127d77373a in ?? ()
#16 0x56127d76e63f in ?? ()
#17 0x7f3da03f5cca in __libc_start_main (main=0x56127d76dc70, argc=5,
argv=0x7ffec6451128, init=, fini=,
rtld_fini=, stack_end=0x7ffec6451118) at
../csu/libc-start.c:308
#18 0x56127d76f2aa in ?? ()

I'll work on getting some better ones, but I'd appreciate tips like what
breakpoints to set. I don't remember which way it was but when debugging, if I
stopped one of the programs, a new process would spawn. That makes it tricky to
pin where the fault lies: akonadi_ews_res or http_so.
-BEGIN PGP SIGNATURE-

iQ9FBAEWCA7tFiEE9vO1rZsVIZobnDZ4crxxSMCrLacFAl98rg3ODiYAmQINBFzE
2VsBEADAj1mv5RNr31Hy597sG0eAiTJkfOigNmVhV/53DGVJ6qll7FVHxTCT9Sfz
UAZ0J9CQ9cRpOfhiD6RyF

[korganizer] [Bug 427393] Incidence editor crashes deleting template

2020-10-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=427393

John Scott  changed:

   What|Removed |Added

  Component|general |incidence editors
   Platform|Debian stable   |Debian testing
Version|unspecified |5.14.1

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

[korganizer] [Bug 427393] New: Incidence editor crashes deleting template

2020-10-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=427393

Bug ID: 427393
   Summary: Incidence editor crashes deleting template
   Product: korganizer
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsc...@posteo.net
  Target Milestone: ---

Application: korganizer (5.14.1 (20.04.0))

Qt Version: 5.14.2
Frameworks Version: 5.70.0
Operating System: Linux 5.8.0-2-amd64 x86_64
Distribution: Debian GNU/Linux bullseye/sid

-- Information about the crash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I was making an event from the 'New Event...' dialog with a title and times put
in. I made a new template from this and gave it a nameWhen I open the incidence
editor, on the command-line I see
org.kde.pim.incidenceeditor: free slot calculation: invalid range. range(  0 )
/ mSlotResolutionSeconds( 900 ) =  0

Now whenever I try to delete this template, it crashes. Just to try to see if I
could make a workaround, I created a second template with a new name and was
*apparently* able to delete the first (after restarting, it's still there).
Still when I try to delete this apparent last one it crashes again.

If I try various combinations of applying, deleting, and/or creating I can get
messages like these
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2084, resource
id: 46353165, major code: 40 (TranslateCoords), minor code: 0

or
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
QSocketNotifier: Invalid socket 20 and type 'Read', disabling...
QSocketNotifier: Invalid socket 21 and type 'Read', disabling...
QSocketNotifier: Invalid socket 22 and type 'Read', disabling...
QSocketNotifier: Invalid socket 34 and type 'Read', disabling...
QSocketNotifier: Invalid socket 31 and type 'Read', disabling...
QSocketNotifier: Invalid socket 32 and type 'Read', disabling...
QSocketNotifier: Invalid socket 38 and type 'Read', disabling...
QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...

What follows is a backtrace that seems more relevant than the Dr. Konqi one to
the incidence editor:
#0  IncidenceEditorNG::TemplateManagementDialog::slotRemoveTemplate
(this=0x7fffe80090e0) at ./src/templatemanagementdialog.cpp:186
#1  0x769188c6 in QtPrivate::QSlotObjectBase::call (a=0x7fffc310,
r=0x7fffe80090e0, this=0x568ae0c0)
at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#2  doActivate (sender=0x568a9b20, signal_index=9,
argv=argv@entry=0x7fffc310) at kernel/qobject.cpp:3870
#3  0x76912830 in QMetaObject::activate
(sender=sender@entry=0x568a9b20,
m=m@entry=0x778792a0 ,
local_signal_index=local_signal_index@entry=2,
argv=argv@entry=0x7fffc310) at kernel/qobject.cpp:3930
#4  0x7746c762 in QAbstractButton::clicked
(this=this@entry=0x568a9b20, _t1=) at
.moc/moc_qabstractbutton.cpp:313
#5  0x7746d0ca in QAbstractButtonPrivate::emitClicked
(this=this@entry=0x568a9b60) at widgets/qabstractbutton.cpp:415
#6  0x7746e91f in QAbstractButtonPrivate::click
(this=this@entry=0x568a9b60) at widgets/qabstractbutton.cpp:408
#7  0x7746eaf1 in QAbstractButton::mouseReleaseEvent
(this=0x568a9b20, e=0x7fffc8d0) at widgets/qabstractbutton.cpp:1012
#8  0x773c052e in QWidget::event (this=0x568a9b20,
event=0x7fffc8d0) at kernel/qwidget.cpp:9033
#9  0x7738003f in QApplicationPrivate::notify_helper (this=, receiver=0x568a9b20, e=0x7fffc8d0)
at kernel/qapplication.cpp:3685
#10 0x77385781 in QApplication::notify(QObject*, QEvent*) () at
kernel/qapplication.cpp:3129
#11 0x768e3b62 in QCoreApplication::notifyInternal2
(receiver=0x568a9b20, event=0x7fffc8d0)
at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#12 0x77384696 in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x568a9b20, event=event@entry=0x7fffc8d0,
alienWidget=alienWidget@entry=0x568a9b20, nativeWidget=0x7fffe80090e0,
buttonDown=, lastMouseReceiver=...,
spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2615
#13 0x773d895e in QWidgetWindow::handleMouseEvent (this=0x568ae840,
event=0x7fffcb90)
at /usr/include/c++/10/bits/atomic_base.h:420
#14 0x773db7ae in QWidgetWindow::event (this=0x568ae840,
event=0x7fffcb90) at kernel/qwidgetwindow.cpp:295
#15 0x7738003f in 

[kmail2] [Bug 338184] RFE: enable specifying custom headers

2020-07-21 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=338184

--- Comment #2 from John Scott  ---
For anyone looking for a quick fix, this can be done on the command-line:
kmail -s foo --header In-Reply-To:bar

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

[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab

2020-06-17 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=399570

--- Comment #16 from John Scott  ---
Created attachment 129456
  --> https://bugs.kde.org/attachment.cgi?id=129456=edit
New crash information added by DrKonqi

akregator (5.14.1 (20.04.0)) using Qt 5.12.5

I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1.

The crash *does* happen for me when manually right-clicking and opening in a
new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I
was able to reproduce with JavaScript disabled, and also opening in a
Background Tab.

What seems to do it for me is clicking a link beneath the title on an /r/netsec
post, which you can get the RSS feed like
https://www.reddit.com/r/netsec/.rss

-- Backtrace (Reduced):
#4  0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent()
const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f7b6ad178b5 in
QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f7b6ad1fb8e in
QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*,
std::unique_ptr
>, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f7b6c740187 in
content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int,
int, content::mojom::CreateNewWindowParams const&,
content::SessionStorageNamespace*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f7b6c44d150 in
content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr,
base::OnceCallback)>) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5

--- Comment #17 from John Scott  ---
Created attachment 129457
  --> https://bugs.kde.org/attachment.cgi?id=129457=edit
New crash information added by DrKonqi

akregator (5.14.1 (20.04.0)) using Qt 5.12.5

I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1.

The crash *does* happen for me when manually right-clicking and opening in a
new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I
was able to reproduce with JavaScript disabled, and also opening in a
Background Tab.

What seems to do it for me is clicking a link beneath the title on an /r/netsec
post, which you can get the RSS feed like
https://www.reddit.com/r/netsec/.rss

-- Backtrace (Reduced):
#4  0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent()
const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f7b6ad178b5 in
QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f7b6ad1fb8e in
QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*,
std::unique_ptr
>, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f7b6c740187 in
content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int,
int, content::mojom::CreateNewWindowParams const&,
content::SessionStorageNamespace*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f7b6c44d150 in
content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr,
base::OnceCallback)>) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5

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

[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab

2020-06-17 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=399570

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab

2020-06-17 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=399570

--- Comment #16 from John Scott  ---
Created attachment 129456
  --> https://bugs.kde.org/attachment.cgi?id=129456=edit
New crash information added by DrKonqi

akregator (5.14.1 (20.04.0)) using Qt 5.12.5

I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1.

The crash *does* happen for me when manually right-clicking and opening in a
new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I
was able to reproduce with JavaScript disabled, and also opening in a
Background Tab.

What seems to do it for me is clicking a link beneath the title on an /r/netsec
post, which you can get the RSS feed like
https://www.reddit.com/r/netsec/.rss

-- Backtrace (Reduced):
#4  0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent()
const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f7b6ad178b5 in
QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f7b6ad1fb8e in
QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*,
std::unique_ptr
>, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f7b6c740187 in
content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int,
int, content::mojom::CreateNewWindowParams const&,
content::SessionStorageNamespace*) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f7b6c44d150 in
content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr,
base::OnceCallback)>) () at
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5

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

[korganizer] [Bug 419836] Events with empty UID are present in akonadi console but not showing up in the calendar

2020-05-07 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=419836

John Scott  changed:

   What|Removed |Added

 CC||philippe.roub...@free.fr

--- Comment #6 from John Scott  ---
*** Bug 378391 has been marked as a duplicate of this bug. ***

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

[korganizer] [Bug 378391] ics merging fails

2020-05-07 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=378391

John Scott  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #3 from John Scott  ---


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

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

[kmail2] [Bug 388036] Include support for autocrypt

2020-04-24 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=388036

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[Akonadi] [Bug 408897] ItemRetrievalManager crash

2020-04-13 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=408897

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kleopatra] [Bug 363309] certificates signed through marginal trusted certificates are incorrectly displayed

2020-03-31 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=363309

John Scott  changed:

   What|Removed |Added

   See Also||http://bugs.debian.org/9490
   ||42
 CC||jsc...@posteo.net

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

[Akonadi] [Bug 393002] Akonadi-ews does not save password in kwallet

2020-01-27 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=393002

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

--- Comment #17 from John Scott  ---
Affects Akonadi 19.08.3 on Debian unstable. I worked around by making the
appropriate entry with KWalletManager, though this would surely not be useful
for anyone using OAuth2.

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

[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28

2019-12-10 Thread Scott
https://bugs.kde.org/show_bug.cgi?id=256034

Scott  changed:

   What|Removed |Added

 CC||westlake.b...@gmail.com

--- Comment #47 from Scott  ---
same thing here on Debian 10
Akregator - Version 5.9.3

I completely wiped out my Akregator settings (including ~/.cache/akregator),
imported an .opml file.

I added a duplicate for one of the feeds, and the "date" showed up as year
2106.

I looked again in the the feeds that were set and noticed a feed was a
duplicate.

I am testing the duplicate rss feed issue with this one, 
http://planet.kernel.org/rss20.xml


The datestamp for the first copy of this feed is correct, but if a copy of this
feed is used, all the datestamps for the second feed become 2106 for the year.

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

[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle

2019-12-07 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=397825

John Scott  changed:

   What|Removed |Added

Summary|[Wayland] Message viewer|[Wayland] Message viewer
   |displays only a black   |displays only a black
   |rectangle when restoring|rectangle
   |from systray|

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

[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle when restoring from systray

2019-12-07 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=397825

--- Comment #7 from John Scott  ---
*** Bug 414057 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 414057] [Wayland] Message viewer shows a black screen or is transparent under Wayland

2019-12-07 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=414057

John Scott  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||jsc...@posteo.net
 Resolution|--- |DUPLICATE

--- Comment #2 from John Scott  ---


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

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

[korganizer] [Bug 378391] ics merging fails

2019-12-07 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=378391

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[korganizer] [Bug 411777] import of vcs fails, still says success

2019-12-07 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=411777

--- Comment #2 from John Scott  ---
(In reply to Martin Koller from comment #0)
> Created attachment 122574 [details]
> test vcs
> 
> SUMMARY
> A webpage produced the attached vcs file.
> When importing it, korganizer shows a blue bar saying "1 incidence was
> successfully imported" but in konsole I see the log output:
> 
> Incidence has empty UID. id= 336260 ; summary= "Test" Please fix it.
> Ignoring this incidence.
> org.kde.pim.kcalcore: The incidence didn't have any UID! Report a bug  to
> the application that generated this file.
> 
> OBSERVED RESULT
> The incidence is not shown in korganizer
> 
> EXPECTED RESULT
> Show imported incidence.
> When an import finds a missing UID, it should simply generate one and import
> the file, instead of just ignoring this file. A user can not control what
> content a web server produces and there is zero chance that a user can
> convince any company to fix the producer.
> Please be more forgiving on broken input.
> 
> SOFTWARE/OS VERSIONS
> KDE Frameworks 5.61.0
> Qt 5.13.0 (built against 5.13.0)
> The xcb windowing system
> openSuse Leap 15.0

The mention of an issue with empty UID looks similar to
https://bugs.kde.org/show_bug.cgi?id=378391#c2 , could you take a look?

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

[korganizer] [Bug 411777] import of vcs fails, still says success

2019-12-03 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=411777

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kontact] [Bug 403359] Kontact crashes when closing email window

2019-07-23 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=403359

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[korganizer] [Bug 409972] New: korganizer sends new todo to wrong calendar

2019-07-18 Thread Scott
https://bugs.kde.org/show_bug.cgi?id=409972

Bug ID: 409972
   Summary: korganizer sends new todo to wrong calendar
   Product: korganizer
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: todoview
  Assignee: kdepim-bugs@kde.org
  Reporter: westlake.b...@gmail.com
  Target Milestone: ---

(Korganizer version: 5.9.3)
SUMMARY
korganizer sends new todo on wrong calendar
If a user has more than 1 calendar, and they create a todo (described below),
that todo goes to the wrong calendar.

Whether a feature or not (new user), the user is not able to change the applied
calendar for the new todo. 


STEPS TO REPRODUCE
1. right-click on calendar event and from context-menu choose to 'create todo' 
2. Select a specific calendar
3. check the todo list


OBSERVED RESULT
The todo does not get created on the specified calendar. Instead the first of
available calendars gets the new todo item.

Note: a new todo via the "todo view" gets stored in the correct calendar, but
not via 'create todo' using the context-menu from calendar events.

SOFTWARE/OS VERSIONS
Korganizer version: 5.9.3
Linux: Debian 10
Qt Version: 5.x

Calendars: 
Davical server -> 1 caldav server (davical -- using custom https:// connect
string)
^ Davical Calendars - 1 account, two calendars

Bug occurs using just these two calendars with 1 caldav server.
(bug was occurring previously as well with the built-in calendars: when
attempting to send a new todo to a caldav server, it was instead being sent to
the built-in Personal calendar. The built-in calendars were removed, and the
bug was still occurring among the two calendars with the davical server.)

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

[kleopatra] [Bug 407761] New: Certificates Must be imported after server reboot

2019-05-20 Thread Scott Coffey
https://bugs.kde.org/show_bug.cgi?id=407761

Bug ID: 407761
   Summary: Certificates Must be imported after server reboot
   Product: kleopatra
   Version: 2.2.0
  Platform: Other
OS: MS Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@gnupg.org
  Reporter: scof...@privatewealthsystems.com
CC: kdepim-bugs@kde.org, m...@kde.org
  Target Milestone: ---

SUMMARY
Certificates must be imported after every server reboot.

STEPS TO REPRODUCE
1. Reboot server
2. Certificates no longer in Kleopatra
3. Import certificates

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

[kaddressbook] [Bug 407666] New: Dial phone number with tel:// and sms:// via xdg

2019-05-17 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=407666

Bug ID: 407666
   Summary: Dial phone number with tel:// and sms:// via xdg
   Product: kaddressbook
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsc...@posteo.net
CC: to...@kde.org
  Target Milestone: ---

Support for dialing phone numbers from contacts is handled in the Configure
dialog, choosing a program such as Ekiga or Skype. With KDE Connect's tel://
URL handler, most programs on my system can tell my phone to dial a number this
way without extra configuration, including Firefox and Okular.

KAddressBook is an exception, because it seems to require its own configuration
for setting how to dial a number instead of using the mechanism these other
programs utilize.

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

[kmail2] [Bug 338184] RFE: enable specifying custom headers

2019-05-04 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=338184

John Scott  changed:

   What|Removed |Added

Summary|RFE: allow me specify the   |RFE: enable specifying
   |in-reply-to/references  |custom headers
   |headers explicitly  |
 CC||jsc...@posteo.net

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

[korganizer] [Bug 406546] New: korganizer crash on login

2019-04-14 Thread Scott Simpson
https://bugs.kde.org/show_bug.cgi?id=406546

Bug ID: 406546
   Summary: korganizer crash on login
   Product: korganizer
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reminder daemon (korgac)
  Assignee: kdepim-bugs@kde.org
  Reporter: ssimp...@alumni.usc.edu
  Target Milestone: ---

SUMMARY
Opensuse Tumbleweed


Don't know how to reproduce but getting on boot. Here is the stack trace

Application: KOrganizer Reminder Daemon (korgac), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f70068e8940 (LWP 2671))]

Thread 5 (Thread 0x7f6ffe01d700 (LWP 2737)):
#0  0x7f700a708ae9 in poll () from /lib64/libc.so.6
#1  0x7f7008810e36 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f7008810f5c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f700ac54e7b in QEventDispatcherGlib::processEvents
(this=0x7f6ff4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f700ac003cb in QEventLoop::exec (this=this@entry=0x7f6ffe01cc60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7f700aa4b016 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7f700aa4c362 in QThreadPrivate::start (arg=0x558c9c42c800) at
thread/qthread_unix.cpp:361
#7  0x7f700918cfab in start_thread () from /lib64/libpthread.so.0
#8  0x7f700a7136af in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f6ffe81e700 (LWP 2734)):
#0  0x7f70088102f0 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#1  0x7f7008810d6b in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f7008810f5c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f700ac54e7b in QEventDispatcherGlib::processEvents
(this=0x7f6ffb20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f700ac003cb in QEventLoop::exec (this=this@entry=0x7f6ffe81dc60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7f700aa4b016 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7f700aa4c362 in QThreadPrivate::start (arg=0x558c9c38fe90) at
thread/qthread_unix.cpp:361
#7  0x7f700918cfab in start_thread () from /lib64/libpthread.so.0
#8  0x7f700a7136af in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f6fffa3a700 (LWP 2718)):
#0  0x7f700885bc99 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f700880ffb4 in g_main_context_release () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f7008810df6 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f7008810f5c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f700ac54e7b in QEventDispatcherGlib::processEvents
(this=0x7f6ff8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7f700ac003cb in QEventLoop::exec (this=this@entry=0x7f6fffa39c30,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#6  0x7f700aa4b016 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#7  0x7f700aece565 in ?? () from /usr/lib64/libQt5DBus.so.5
#8  0x7f700aa4c362 in QThreadPrivate::start (arg=0x7f700af4ed80) at
thread/qthread_unix.cpp:361
#9  0x7f700918cfab in start_thread () from /lib64/libpthread.so.0
#10 0x7f700a7136af in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7004874700 (LWP 2705)):
#0  0x7f700a708ae9 in poll () from /lib64/libc.so.6
#1  0x7f70091b7cc7 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f70091b98fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f7004aa6788 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f700aa4c362 in QThreadPrivate::start (arg=0x558c9c2dec70) at
thread/qthread_unix.cpp:361
#5  0x7f700918cfab in start_thread () from /lib64/libpthread.so.0
#6  0x7f700a7136af in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f70068e8940 (LWP 2671)):
[KCrash Handler]
#6  0x7f700c6f78d9 in Akonadi::BlockAlarmsAttribute::isAlarmTypeBlocked
(this=this@entry=0x558c9d6a2ca0, type=KCalCore::Alarm::Display) at
/usr/src/debug/akonadi-calendar-18.12.3-1.2.x86_64/src/blockalarmsattribute.cpp:84
#7  0x7f700c70a54c in Akonadi::ETMCalendar::alarms (this=,
from=..., to=..., excludeBlockedAlarms=) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:312
#8  0x558c9a8aab39 in KOAlarmClient::checkAlarms (this=0x7ffc91326920) at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:312
#9  0x558c9a8ab915 in KOAlarmClient::deferredInit (this=0x7ffc91326920) at
/usr/src/debug/korganizer-18.12.3-1.2.x86_64/korgac/koalarmclient.cpp:169
#10 0x7f700ac2b343 in QtPrivate::QSlotObjectBase::call (a=0x7ffc91326010,
r=0x7ffc91326920, 

[akregator] [Bug 130529] support for rss on https protokol missing

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=130529

John Scott  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #5 from John Scott  ---
This bug is old, and Akregator has supported HTTPS for a long time now.

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

[akregator] [Bug 273391] Akregator should not ask to restore session if there is nothing to restore

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=273391

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=256034

John Scott  changed:

   What|Removed |Added

 CC||hast0...@gmail.com

--- Comment #40 from John Scott  ---
*** Bug 357281 has been marked as a duplicate of this bug. ***

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

[akregator] [Bug 357281] the date of a specific feed are completely wrong

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=357281

John Scott  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from John Scott  ---


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

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

[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=256034

John Scott  changed:

   What|Removed |Added

 CC||anand.chi...@gmail.com

--- Comment #39 from John Scott  ---
*** Bug 262271 has been marked as a duplicate of this bug. ***

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

[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=262271

John Scott  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|CONFIRMED   |RESOLVED

--- Comment #19 from John Scott  ---


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

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

[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=256034

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.

2019-04-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=262271

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kmail2] [Bug 406167] New: Show all messages in mbox

2019-04-02 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=406167

Bug ID: 406167
   Summary: Show all messages in mbox
   Product: kmail2
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: jsc...@posteo.net
  Target Milestone: ---

I find it handy to download mbox files with multiple messages, mostly for the
sake of working with Debian's BTS. Opening an mbox for a bug shows "The file
contains multiple messages. Only the first message is shown." It would be nice
to see the other messages inside.

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

[kaddressbook] [Bug 314087] Use marble to show addresses and coordinates

2019-03-30 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=314087

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kaddressbook] [Bug 406047] New: '\' character at end of displayed address

2019-03-30 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=406047

Bug ID: 406047
   Summary: '\' character at end of displayed address
   Product: kaddressbook
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsc...@posteo.net
CC: to...@kde.org
  Target Milestone: ---

Created attachment 119158
  --> https://bugs.kde.org/attachment.cgi?id=119158=edit
screenshot showing contact's address

I use my CalDAV/CardDAV account with Posteo across several devices. Addresses
display fine with Google's Contacts for Android (the app with which most
contacts and addresses were created) and also with Contacts on macOS. 

KAddressBook often shows a "\" at the end of the first address line, but the
other clients display the addresses fine, so I'm assuming this is a bug in
KAddressBook. Right-clicking and choosing to copy the address also includes the
backslash, but it's not visible in the editor.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.14
KDE Frameworks Version: 5.54
Qt Version: 5.11.3

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

[kmail2] [Bug 403159] Blank page on print and print preview

2019-03-20 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=403159

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kmail2] [Bug 404492] Kmail show empty printpreview and crashes after closing it, and producing empty print

2019-03-20 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404492

--- Comment #3 from John Scott  ---
(In reply to Wolfgang Bauer from comment #2)
> (In reply to John Scott from comment #1)
> And the crash looks like another duplicate of bug#398577...

I believe that might've been DrKonqi's initial suggestion too, but that bug
pertains to Kontact, which I wasn't using when I had the crash.

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

[kmail2] [Bug 404492] Kmail show empty printpreview and crashes after closing it, and producing empty print

2019-03-19 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404492

--- Comment #1 from John Scott  ---
Created attachment 118920
  --> https://bugs.kde.org/attachment.cgi?id=118920=edit
New crash information added by DrKonqi

kmail (5.9.3) using Qt 5.11.3

I've found this bug with 18.08.3 on Debian Buster.

-- Backtrace (Reduced):
#7  0x7fe9a2704d95 in content::RenderProcessHostImpl::ShutdownRequest() ()
from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fe9a1f022a5 in
content::mojom::RendererHostStubDispatch::Accept(content::mojom::RendererHost*,
mojo::Message*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7fe9a3b81959 in IPC::(anonymous
namespace)::ChannelAssociatedGroupController::AcceptOnProxyThread(mojo::Message)
() from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#11 0x7fe9a3b8143e in void
base::internal::Invoker,
base::internal::PassedWrapper >, void ()>::RunImpl,
base::internal::PassedWrapper > const&, 0ul, 1ul>(void
(IPC::(anonymous namespace)::ChannelAssociatedGroupController::*
const&)(mojo::Message), std::tuple,
base::internal::PassedWrapper > const&,
std::integer_sequence) [clone .isra.234] () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#12 0x7fe9a32bb688 in base::debug::TaskAnnotator::RunTask(char const*,
base::PendingTask*) () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5

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

[kmail2] [Bug 404492] Kmail show empty printpreview and crashes after closing it, and producing empty print

2019-03-19 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404492

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kontact] [Bug 403065] Akregator crashes when adding link

2019-03-16 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=403065

--- Comment #1 from John Scott  ---
Created attachment 118848
  --> https://bugs.kde.org/attachment.cgi?id=118848=edit
New crash information added by DrKonqi

akregator (5.9.3) using Qt 5.11.3

I experienced this on Debian, previewing feeds in Firefox which invoked
Akregator. It takes 15 seconds or so for it to crash. I hope my backtrace can
be helpful.

It could be a coincidence, but I did notice after subscribing to the feed that
it showed in 'Imported Folder,' but the feed doesn't have a name and the icon
is an 'x' in a bubble.

-- Backtrace (Reduced):
#6  0x7f78efd05dbf in Akregator::Feed::slotAddToFetchQueue
(this=0x5626423d3910, queue=0x562641cc8f70, intervalFetchOnly=)
at ./src/feed/feed.cpp:535
#7  0x7f78efd1aff1 in Akregator::Folder::slotAddToFetchQueue
(this=, queue=0x562641cc8f70, intervalFetchOnly=true) at
./src/folder.cpp:389
#8  0x7f78ee7da703 in QtPrivate::QSlotObjectBase::call (a=0x7ffdb25a93e0,
r=0x562641b1db00, this=0x562641ca83e0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376
[...]
#10 0x7f78ee7e62d7 in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:200
#11 0x7f78ee7dae0b in QObject::event (this=0x562641c14c10, e=) at kernel/qobject.cpp:1232

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

[kontact] [Bug 403065] Akregator crashes when adding link

2019-03-16 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=403065

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kontact] [Bug 404881] Kontact crashes when closing Akregator from tray icon

2019-03-15 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404881

John Scott  changed:

   What|Removed |Added

  Component|general |akregator

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

[kontact] [Bug 404881] Kontact crashes when closing Akregator from tray icon

2019-02-27 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404881

John Scott  changed:

   What|Removed |Added

 OS|NetBSD  |Linux

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

[kontact] [Bug 404881] Kontact crashes when closing Akregator from tray icon

2019-02-27 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404881

John Scott  changed:

   What|Removed |Added

 OS|Linux   |NetBSD
   Platform|Debian stable   |Debian testing

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

[kontact] [Bug 404881] New: Kontact crashes when closing Akregator from tray icon

2019-02-27 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=404881

Bug ID: 404881
   Summary: Kontact crashes when closing Akregator from tray icon
   Product: kontact
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsc...@posteo.net
  Target Milestone: ---

Application: kontact (5.9.3)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-2-amd64 x86_64
Distribution: Debian GNU/Linux buster/sid

-- Information about the crash:
On my system, I open Kontact and navigate to Feeds. When I secondary click on
the icon and choose Quit, Kontact crashes. I can reproduce on X11 and Wayland.

The crash can be reproduced every time.

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

Thread 29 (Thread 0x7fa285a7f700 (LWP 12706)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7fa285a7e400,
expected=0, futex_word=0x7fa285a7e5e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fa285a7e4a0, mutex=0x7fa285a7e598,
cond=0x7fa285a7e5c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7fa285a7e5c0, mutex=0x7fa285a7e598,
abstime=0x7fa285a7e4a0) at pthread_cond_wait.c:667
#3  0x7fa377800a37 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fa37780330a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fa3778033f2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fa377807981 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fa377808c7f in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fa377811c81 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fa37dc6bfa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fa37ee2680f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7fa280238700 (LWP 12705)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7fa280237400,
expected=0, futex_word=0x7fa2802375e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fa2802374a0, mutex=0x7fa280237598,
cond=0x7fa2802375c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7fa2802375c0, mutex=0x7fa280237598,
abstime=0x7fa2802374a0) at pthread_cond_wait.c:667
#3  0x7fa377800a37 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fa37780330a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fa3778033f2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fa377807981 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fa377808e61 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fa377811c81 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fa37dc6bfa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fa37ee2680f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7fa27a6a8700 (LWP 12703)):
#0  futex_reltimed_wait_cancelable (private=0, reltime=0x7fa27a6a7400,
expected=0, futex_word=0x7fa27a6a75e8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7fa27a6a74a0, mutex=0x7fa27a6a7598,
cond=0x7fa27a6a75c0) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x7fa27a6a75c0, mutex=0x7fa27a6a7598,
abstime=0x7fa27a6a74a0) at pthread_cond_wait.c:667
#3  0x7fa377800a37 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fa37780330a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fa3778033f2 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fa377807981 in

[kontact] [Bug 398577] closing a message subwindow crashes Kontact

2019-02-23 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=398577

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

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

[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle when restoring from systray

2019-01-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=397825

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

--- Comment #6 from John Scott  ---
I can reproduce on Debian Buster too. Maybe this is related to #402241 as the
latter is Wayland-specific and causes more widespread trouble drawing the UI.

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

[kmail2] [Bug 402241] KMail Wayland UI drawing flakiness

2019-01-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=402241

John Scott  changed:

   What|Removed |Added

   Keywords||wayland

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

[kmail2] [Bug 402241] KMail Wayland UI drawing flakiness

2019-01-06 Thread John Scott
https://bugs.kde.org/show_bug.cgi?id=402241

John Scott  changed:

   What|Removed |Added

 CC||jsc...@posteo.net

--- Comment #1 from John Scott  ---
I'm experiencing this on Intel graphics too, on Debian Testing. KMail becomes
difficult to use when opening multiple KMail windows; they fight with each
other if I don't minimize one.

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

[akregator] [Bug 394568] Next article with Key 'Left' moves addigtinally the article list to the left

2018-05-22 Thread Scott Harvey
https://bugs.kde.org/show_bug.cgi?id=394568

Scott Harvey <sc...@spharvey.me> changed:

   What|Removed |Added

 CC||sc...@spharvey.me
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #2 from Scott Harvey <sc...@spharvey.me> ---
Confirmed on openSUSE Tumbleweed.

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

[kontact] [Bug 387553] New: Kontact crash while exiting

2017-12-03 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=387553

Bug ID: 387553
   Summary: Kontact crash while exiting
   Product: kontact
   Version: 5.2.3
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@humanleg.org.uk
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 9.2 (stretch)

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

Closing Kontact through right clicking on the Akregator system tray entry. No
main Kontact window open.

- Unusual behavior I noticed:

Kontact main window had been failing to repaint itself properly (was using
kmail pane).

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5253f09dc0 (LWP 29594))]

Thread 10 (Thread 0x7f51dd797700 (LWP 29603)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d2913 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51dd797700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 9 (Thread 0x7f51ddf98700 (LWP 29602)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d2913 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51ddf98700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 8 (Thread 0x7f51de799700 (LWP 29601)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d2913 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51de799700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 7 (Thread 0x7f51def9a700 (LWP 29600)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f3d17f1 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#2  0x7f524f6fa681 in  () at /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5
#3  0x7f524b632494 in start_thread (arg=0x7f51def9a700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 6 (Thread 0x7f51d700 (LWP 29599)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f522c72475b in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f522c724487 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f524b632494 in start_thread (arg=0x7f51d700) at
pthread_create.c:333
#4  0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 5 (Thread 0x7f522d972700 (LWP 29598)):
#0  0x7f52520212a9 in QMutex::unlock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f525224d7f1 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f5249834edd in g_main_context_prepare
(context=context@entry=0x7f51e990, priority=priority@entry=0x7f522d971b40)
at ././glib/gmain.c:3501
#3  0x7f524983591b in g_main_context_iterate
(context=context@entry=0x7f51e990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#4  0x7f5249835b0c in g_main_context_iteration (context=0x7f51e990,
may_block=1) at ././glib/gmain.c:3990
#5  0x7f525224e06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f52521f79ca in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f52520250f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5252029da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f524b632494 in start_thread (arg=0x7f522d972700) at
pthread_create.c:333
#10 0x7f5251723aff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 4 (Thread 0x7f522f432700 (LWP 29597)):
#0  0x7f524b63815f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f524f6c998b in  () at 

[kmail2] [Bug 385624] New: kmail crash after resize of window after startup

2017-10-11 Thread Barry Scott
https://bugs.kde.org/show_bug.cgi?id=385624

Bug ID: 385624
   Summary: kmail crash after resize of window after startup
   Product: kmail2
   Version: 5.5.1
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ba...@barrys-emacs.org
  Target Milestone: ---

Application: kmail (5.5.1)

Qt Version: 5.7.1
Frameworks Version: 5.36.0
Operating System: Linux 4.13.4-200.fc26.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

booted fedora
login to KDE
start kmail
resize window
- kmail crash here

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
84  T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f7f55461940 (LWP 2242))]

Thread 26 (Thread 0x7f7eb783a700 (LWP 2305)):
#0  0x7f7f7384190b in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f7f5ab60478) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7f7384190b in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f7f5ab60428, cond=0x7f7f5ab60450) at pthread_cond_wait.c:502
#2  0x7f7f7384190b in __pthread_cond_wait (cond=0x7f7f5ab60450,
mutex=0x7f7f5ab60428) at pthread_cond_wait.c:655
#3  0x7f7f5aa65534 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at
/lib64/libQt5Script.so.5
#4  0x7f7f5aa65579 in  () at /lib64/libQt5Script.so.5
#5  0x7f7f7383b36d in start_thread (arg=0x7f7eb783a700) at
pthread_create.c:456
#6  0x7f7f778eabbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 25 (Thread 0x7f7ec1689700 (LWP 2292)):
#0  0x7f7f778deacd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7f63883569 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f7f6388367c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f7f786f6e6b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f7eb80008f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f7f786a760a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f7ec1688c70, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f7f784ff99a in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7f7f78503c9e in QThreadPrivate::start(void*) (arg=0x562ed8f3cf10) at
thread/qthread_unix.cpp:368
#7  0x7f7f7383b36d in start_thread (arg=0x7f7ec1689700) at
pthread_create.c:456
#8  0x7f7f778eabbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 24 (Thread 0x7f7ee27fc700 (LWP 2277)):
#0  0x7f7f778da22d in write () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7f7785822d in _IO_new_file_write (f=0x7f7f77ba6500
<_IO_2_1_stderr_>, data=0x7f7ee27f8ce0, n=39) at fileops.c:1271
#2  0x7f7f77858bcf in new_do_write (to_do=,
data=0x7f7ee27f8ce0 "[warn] epoll_wait: Bad file descriptor\n",
fp=0x7f7f77ba6500 <_IO_2_1_stderr_>) at fileops.c:526
#3  0x7f7f77858bcf in _IO_new_file_xsputn (f=0x7f7f77ba6500
<_IO_2_1_stderr_>, data=, n=39) at fileops.c:1350
#4  0x7f7f7782c747 in buffered_vfprintf (s=s@entry=0x7f7f77ba6500
<_IO_2_1_stderr_>, format=format@entry=0x7f7f5ddefb10 "[%s] %s\n",
args=args@entry=0x7f7ee27fb2a0) at vfprintf.c:2346
#5  0x7f7f77829786 in _IO_vfprintf_internal (s=s@entry=0x7f7f77ba6500
<_IO_2_1_stderr_>, format=0x7f7f5ddefb10 "[%s] %s\n",
ap=ap@entry=0x7f7ee27fb2a0) at vfprintf.c:1293
#6  0x7f7f778fb2d6 in ___fprintf_chk (fp=0x7f7f77ba6500 <_IO_2_1_stderr_>,
flag=1, format=) at fprintf_chk.c:35
#7  0x7f7f5ddd7880 in _warn_helper () at /lib64/libevent-2.0.so.5
#8  0x7f7f5ddd7a44 in event_warn () at /lib64/libevent-2.0.so.5
#9  0x7f7f5dddc1e0 in epoll_dispatch () at /lib64/libevent-2.0.so.5
#10 0x7f7f5ddc6dbe in event_base_loop () at /lib64/libevent-2.0.so.5
#11 0x7f7f6afbc559 in
base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at
/lib64/libQt5WebEngineCore.so.5
#12 0x7f7f6afb8828 in base::MessageLoop::RunHandler() () at
/lib64/libQt5WebEngineCore.so.5
#13 0x7f7f6afd526b in base::RunLoop::Run() () at
/lib64/libQt5WebEngineCore.so.5
#14 0x7f7f6afecf66 in base::Thread::ThreadMain() () at
/lib64/libQt5WebEngineCore.so.5
#15 0x7f7f6afe906b in base::(anonymous namespace)::ThreadFunc(void*) () at
/lib64/libQt5WebEngineCore.so.5
#16 0x7f7f7383b36d in start_thread (arg=0x7f7ee27fc700) at
pthread_create.c:456
#17 0x7f7f778eabbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97

Thread 23 (Thread 0x7f7ee2ffd700 (LWP 2276)):
#0  0x7f7f7384190b in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f7ee2ffc988) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7f7384190b in __pthread_cond_wait_common (abstime=0x0,

[kleopatra] [Bug 375164] New: Import error

2017-01-16 Thread Scott Slocum
https://bugs.kde.org/show_bug.cgi?id=375164

Bug ID: 375164
   Summary: Import error
   Product: kleopatra
   Version: 2.3.0
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: aheine...@intevation.de
  Reporter: swslo...@gmail.com
CC: kdepim-bugs@kde.org, m...@kde.org
  Target Milestone: ---

When I go to import, both from the clipboard or from a saved file it will say
processed:0 
Imported :0

I am not sure why it will no even notice I am attempting to import a key.

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

[kmail2] [Bug 277007] KMail2 full search of emails does not work

2015-09-28 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=277007

Robert Scott <b...@humanleg.org.uk> changed:

   What|Removed |Added

 CC||b...@humanleg.org.uk

--- Comment #38 from Robert Scott <b...@humanleg.org.uk> ---
I'm having the same problem with 4.14.1 under debian jessie. Immediately
returning no search results no matter what I type.

Part of me wants to say this is the last straw with kmail2, but I've said it
before too much already. I think the only reason I've been staying with it is
because of the convenience of kde's kioslaves. It makes me sad because kmail1
was one of my *favourite* applications.

-- 
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 350953] New: KMail2 crash when selecting/deselecting text in message panel

2015-08-04 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=350953

Bug ID: 350953
   Summary: KMail2 crash when selecting/deselecting text in
message panel
   Product: kmail2
   Version: 4.14.1
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@humanleg.org.uk

Application: kmail (4.14.1)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 8.1 (jessie)

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

Selecting/deselecting text in message panel when reading an IMAP email

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f79267f8800 (LWP 1507))]

Thread 4 (Thread 0x7f78fe734700 (LWP 1512)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7917e1306f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7917e130a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f792131f0a4 in start_thread (arg=0x7f78fe734700) at
pthread_create.c:309
#4  0x7f7923a6a04d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f78bcf10700 (LWP 1513)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7917b35973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7917e427f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f792131f0a4 in start_thread (arg=0x7f78bcf10700) at
pthread_create.c:309
#4  0x7f7923a6a04d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f78b7fff700 (LWP 1514)):
#0  0x7f7923a6150d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f791b74bee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f791b74bffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7924403d37 in QEventDispatcherGlib::processEvents
(this=0x7f78b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f79243d3271 in QEventLoop::processEvents
(this=this@entry=0x7f78b7ffedd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f79243d35d5 in QEventLoop::exec (this=this@entry=0x7f78b7ffedd0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f79242c7e99 in QThread::exec (this=optimized out) at
thread/qthread.cpp:538
#7  0x7f79242ca70f in QThreadPrivate::start (arg=0x1f03b30) at
thread/qthread_unix.cpp:349
#8  0x7f792131f0a4 in start_thread (arg=0x7f78b7fff700) at
pthread_create.c:309
#9  0x7f7923a6a04d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f79267f8800 (LWP 1507)):
[KCrash Handler]
#6  0x7f79239b9107 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x7f79239ba4e8 in __GI_abort () at abort.c:89
#8  0x7f79239b2226 in __assert_fail_base (fmt=0x7f7923ae8ce8 %s%s%s:%u:
%s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f79232d1f60
!xcb_xlib_threads_sequence_lost, file=file@entry=0x7f79232d1dab
../../src/xcb_io.c, line=line@entry=274,
function=function@entry=0x7f79232d2266 poll_for_event) at assert.c:92
#9  0x7f79239b22d2 in __GI___assert_fail (assertion=0x7f79232d1f60
!xcb_xlib_threads_sequence_lost, file=0x7f79232d1dab ../../src/xcb_io.c,
line=274, function=0x7f79232d2266 poll_for_event) at assert.c:101
#10 0x7f792325ea79 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#11 0x7f792325eb2b in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#12 0x7f792325ee3d in _XEventsQueued () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#13 0x7f79232619f0 in _XData32 () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#14 0x7f792323b923 in XChangeProperty () from
/usr/lib/x86_64-linux-gnu/libX11.so.6
#15 0x7f792499c87d in QWidgetPrivate::setWindowIcon_sys
(this=this@entry=0x367f340, forceReset=forceReset@entry=false) at
kernel/qwidget_x11.cpp:1548
#16 0x7f792494e3b8 in QWidget::create (this=this@entry=0x6479e70,
window=window@entry=0, initializeWindow=initializeWindow@entry=true,
destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1543
#17 0x7f7924956ca2 in QWidget::setVisible (this=0x6479e70,
visible=optimized out) at kernel/qwidget.cpp:7726
#18 0x7f792498fa8f in show (this=optimized out) at
../../include/QtGui/../../src/gui/kernel/qwidget.h:497
#19 QDragManager::updatePixmap (this=this@entry=0x23e0bb0) at
kernel/qdnd_x11.cpp:2079
#20 0x7f7924990d35 in QDragManager::drag (this=0x23e0bb0,
o=o@entry=0x6186c60) at kernel/qdnd_x11.cpp:2007
#21 0x7f7924915f5a in QDrag::exec (this=0x6186c60, 

[kmail2] [Bug 349665] New: Crash when choosing Tools/Find Messages...

2015-06-27 Thread Barry Scott
https://bugs.kde.org/show_bug.cgi?id=349665

Bug ID: 349665
   Summary: Crash when choosing Tools/Find Messages...
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ba...@barrys-emacs.org

Application: kmail (4.14.9)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 4.0.5-300.fc22.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I use IMAP mail and need to file mails that are in the wrong folder.

Choose Tools/Find messages...

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f6e36655900 (LWP 3577))]

Thread 4 (Thread 0x7f6e0122b700 (LWP 3603)):
#0  0x7f6e3199b530 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6e2da10f61 in JSC::BlockAllocator::blockFreeingThreadMain() () from
/lib64/libQtWebKit.so.4
#2  0x7f6e2dd0f6d6 in WTF::wtfThreadEntryPoint(void*) () from
/lib64/libQtWebKit.so.4
#3  0x7f6e31996555 in start_thread () from /lib64/libpthread.so.0
#4  0x7f6e2feebf3d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f6dbbffd700 (LWP 3611)):
#0  0x7f6e2fee066d in poll () from /lib64/libc.so.6
#1  0x7f6e2203bdbc in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f6e2203becc in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f6e31d654ee in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /lib64/libQtCore.so.4
#4  0x7f6e31d33791 in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/lib64/libQtCore.so.4
#5  0x7f6e31d33b05 in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/lib64/libQtCore.so.4
#6  0x7f6e31c23289 in QThread::exec() () from /lib64/libQtCore.so.4
#7  0x7f6e31c25aac in QThreadPrivate::start(void*) () from
/lib64/libQtCore.so.4
#8  0x7f6e31996555 in start_thread () from /lib64/libpthread.so.0
#9  0x7f6e2feebf3d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f6db3bea700 (LWP 3817)):
#0  0x7f6e3199b530 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f6e35d2db5a in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQtScript.so.4
#2  0x7f6e35d2db89 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQtScript.so.4
#3  0x7f6e31996555 in start_thread () from /lib64/libpthread.so.0
#4  0x7f6e2feebf3d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f6e36655900 (LWP 3577)):
[KCrash Handler]
#6  0x7f6e2f7e8994 in MailCommon::SearchPattern::purify(bool) () from
/lib64/libmailcommon.so.4
#7  0x7f6e361e20a6 in
KMail::SearchWindow::addRulesToSearchPattern(MailCommon::SearchPattern const)
() from /lib64/libkmailprivate.so.4
#8  0x7f6e3613faa3 in KMMainWidget::slotRequestFullSearchFromQuickSearch()
() from /lib64/libkmailprivate.so.4
#9  0x7f6e3624f42c in KMMainWidget::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libkmailprivate.so.4
#10 0x7f6e31d490c0 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /lib64/libQtCore.so.4
#11 0x7f6e30e62442 in QAction::triggered(bool) () from /lib64/libQtGui.so.4
#12 0x7f6e30e637a3 in QAction::activate(QAction::ActionEvent) () from
/lib64/libQtGui.so.4
#13 0x7f6e312be43d in
QMenuPrivate::activateCausedStack(QListQPointerQWidget  const, QAction*,
QAction::ActionEvent, bool) () from /lib64/libQtGui.so.4
#14 0x7f6e312c2839 in QMenuPrivate::activateAction(QAction*,
QAction::ActionEvent, bool) () from /lib64/libQtGui.so.4
#15 0x7f6e32b3b8a3 in KMenu::mouseReleaseEvent(QMouseEvent*) () from
/lib64/libkdeui.so.5
#16 0x7f6e30ebc340 in QWidget::event(QEvent*) () from /lib64/libQtGui.so.4
#17 0x7f6e312c6aab in QMenu::event(QEvent*) () from /lib64/libQtGui.so.4
#18 0x7f6e30e683ac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQtGui.so.4
#19 0x7f6e30e6f3c6 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQtGui.so.4
#20 0x7f6e32a7105a in KApplication::notify(QObject*, QEvent*) () from
/lib64/libkdeui.so.5
#21 0x7f6e31d34f1d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /lib64/libQtCore.so.4
#22 0x7f6e30e6e9cd in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointerQWidget, bool) () from
/lib64/libQtGui.so.4
#23 0x7f6e30ee7402 in QETWidget::translateMouseEvent(_XEvent const*) ()
from /lib64/libQtGui.so.4
#24 0x7f6e30ee53bd in QApplication::x11ProcessEvent(_XEvent*) () from
/lib64/libQtGui.so.4
#25 0x7f6e30f0e489 in 

[Akonadi] [Bug 348319] New: Akonadi IMAP crash

2015-05-27 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=348319

Bug ID: 348319
   Summary: Akonadi IMAP crash
   Product: Akonadi
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: b...@humanleg.org.uk
CC: kdepim-bugs@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 8.0 (jessie)

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

Nothing related. KMail2 was in the background, presumably checking my IMAP
(provided by gmail).

-- Backtrace:
Application: beauhurst of type IMAP E-Mail Server (akonadi_imap_resource),
signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7fc8b6577780 (LWP 1444))]

Thread 16 (Thread 0x7fc8a1b8b700 (LWP 1671)):
#0  0x7fffe51e8a32 in clock_gettime ()
#1  0x7fc8b1db2c9d in __GI___clock_gettime (clock_id=optimized out,
tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fc8b5a93a05 in do_gettime (frac=synthetic pointer, sec=synthetic
pointer) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fc8b5b76b85 in updateCurrentTime (this=0x7fc89c0030d0) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fc89c0030d0, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fc8b5b7546c in timerSourcePrepareHelper (src=optimized out,
timeout=0x7fc8a1b8ac84) at kernel/qeventdispatcher_glib.cpp:136
#7  0x7fc8b5b75535 in timerSourcePrepare (source=optimized out,
timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169
#8  0x7fc8b0d2a45d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fc8b0d2ae0b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fc8b0d2affc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fc8b5b75d37 in QEventDispatcherGlib::processEvents
(this=0x7fc89c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fc8b5b45271 in QEventLoop::processEvents
(this=this@entry=0x7fc8a1b8ae50, flags=...) at kernel/qeventloop.cpp:149
#13 0x7fc8b5b455d5 in QEventLoop::exec (this=this@entry=0x7fc8a1b8ae50,
flags=...) at kernel/qeventloop.cpp:204
#14 0x7fc8b5a39e99 in QThread::exec (this=optimized out) at
thread/qthread.cpp:538
#15 0x7fc8b5a3c70f in QThreadPrivate::start (arg=0x117ff10) at
thread/qthread_unix.cpp:349
#16 0x7fc8b14170a4 in start_thread (arg=0x7fc8a1b8b700) at
pthread_create.c:309
#17 0x7fc8b1da604d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 15 (Thread 0x7fc8a138a700 (LWP 1893)):
#0  0x7fffe51e8a32 in clock_gettime ()
#1  0x7fc8b1db2c9d in __GI___clock_gettime (clock_id=optimized out,
tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fc8b5a93a05 in do_gettime (frac=synthetic pointer, sec=synthetic
pointer) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7fc8b5b76b85 in updateCurrentTime (this=0x7fc894003600) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0x7fc894003600, tm=...) at
kernel/qeventdispatcher_unix.cpp:460
#6  0x7fc8b5b7546c in timerSourcePrepareHelper (src=optimized out,
timeout=0x7fc8a1389c84) at kernel/qeventdispatcher_glib.cpp:136
#7  0x7fc8b5b75535 in timerSourcePrepare (source=optimized out,
timeout=optimized out) at kernel/qeventdispatcher_glib.cpp:169
#8  0x7fc8b0d2a45d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fc8b0d2ae0b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fc8b0d2affc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fc8b5b75d37 in QEventDispatcherGlib::processEvents
(this=0x7fc894012510, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#12 0x7fc8b5b45271 in QEventLoop::processEvents
(this=this@entry=0x7fc8a1389e50, flags=...) at kernel/qeventloop.cpp:149
#13 0x7fc8b5b455d5 in QEventLoop::exec (this=this@entry=0x7fc8a1389e50,
flags=...) at kernel/qeventloop.cpp:204
#14 0x7fc8b5a39e99 in QThread::exec (this=optimized out) at
thread/qthread.cpp:538
#15 0x7fc8b5a3c70f in QThreadPrivate::start (arg=0x10a1a60) at
thread/qthread_unix.cpp:349
#16 0x7fc8b14170a4 in start_thread (arg=0x7fc8a138a700) at
pthread_create.c:309
#17 0x7fc8b1da604d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 14 (Thread 0x7fc89a7fc700 (LWP 3963)):
#0  0x7fffe51e8a32 in clock_gettime ()
#1  0x7fc8b1db2c9d in __GI___clock_gettime 

[kmail2] [Bug 345517] New: KMail crashes on exit

2015-03-25 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=345517

Bug ID: 345517
   Summary: KMail crashes on exit
   Product: kmail2
   Version: 4.14.1
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@humanleg.org.uk

Application: kmail (4.14.1)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 8.0 (jessie)

-- Information about the crash:
- What I was doing when the application crashed:
Closing KMail.
- Unusual behavior I noticed:
KMail had been continually complaining that the KMail folders were broken
because it couldn't write to one of the directories. I couldn't see why it
couldn't write to the directory.
- Custom settings of the application:
Had just upgraded an old kmail1 setup with disconnected imap folders.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f8952207800 (LWP 6549))]

Thread 5 (Thread 0x7f892a1b1700 (LWP 6556)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f894382006f in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f89438200a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f894cd2c0a4 in start_thread (arg=0x7f892a1b1700) at
pthread_create.c:309
#4  0x7f894f47704d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f88e8990700 (LWP 6559)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8943542973 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f894384f7f6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f894cd2c0a4 in start_thread (arg=0x7f88e8990700) at
pthread_create.c:309
#4  0x7f894f47704d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f88e7c88700 (LWP 6560)):
#0  0x7ffd937a3a32 in clock_gettime ()
#1  0x7f894f483c9d in __GI___clock_gettime (clock_id=optimized out,
tp=optimized out) at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f894fd2ea05 in do_gettime (frac=synthetic pointer, sec=synthetic
pointer) at tools/qelapsedtimer_unix.cpp:127
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:144
#4  0x7f894fe11789 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f88d80030d0) at kernel/qeventdispatcher_unix.cpp:354
#5  0x7f894fe10667 in timerSourceCheckHelper (src=0x7f88d8003070) at
kernel/qeventdispatcher_glib.cpp:150
#6  0x7f89471588c1 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f8947158e83 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f8947158ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f894fe10d37 in QEventDispatcherGlib::processEvents
(this=0x7f88d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#10 0x7f894fde0271 in QEventLoop::processEvents
(this=this@entry=0x7f88e7c87dd0, flags=...) at kernel/qeventloop.cpp:149
#11 0x7f894fde05d5 in QEventLoop::exec (this=this@entry=0x7f88e7c87dd0,
flags=...) at kernel/qeventloop.cpp:204
#12 0x7f894fcd4e99 in QThread::exec (this=optimized out) at
thread/qthread.cpp:538
#13 0x7f894fcd770f in QThreadPrivate::start (arg=0x2617290) at
thread/qthread_unix.cpp:349
#14 0x7f894cd2c0a4 in start_thread (arg=0x7f88e7c88700) at
pthread_create.c:309
#15 0x7f894f47704d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f88e6533700 (LWP 6566)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f893a3d8dea in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f893a3d8e19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f894cd2c0a4 in start_thread (arg=0x7f88e6533700) at
pthread_create.c:309
#4  0x7f894f47704d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f8952207800 (LWP 6549)):
[KCrash Handler]
#6  ref (this=0xfff8) at
../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:121
#7  QVector (v=..., this=0x3f4a990) at
../../include/QtCore/../../src/corelib/tools/qvector.h:123
#8  QVectorQVectorQPersistentModelIndexData* ::realloc
(this=this@entry=0x24fd788, asize=59957040, aalloc=optimized out) at
../../include/QtCore/../../src/corelib/tools/qvector.h:532
#9  0x7f894fdd699a in detach_helper (this=0x24fd788) at
../../include/QtCore/../../src/corelib/tools/qvector.h:337
#10 detach (this=0x24fd788) at
../../include/QtCore/../../src/corelib/tools/qvector.h:147
#11 data (this=0x24fd788) at

[Akonadi] [Bug 340740] New: IMAP resource sometimes crashes after reconnecting to Internet

2014-11-07 Thread Scott Garrett
https://bugs.kde.org/show_bug.cgi?id=340740

Bug ID: 340740
   Summary: IMAP resource sometimes crashes after reconnecting to
Internet
   Product: Akonadi
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: m...@exovenom.net
CC: kdepim-bugs@kde.org, vkra...@kde.org

Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.17.1-1.g5c4d099-desktop x86_64
Distribution: openSUSE 20141102 (Harlequin) (x86_64)

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

On log-in or when reconnecting to the Internet,  the IMAP resource sometimes
segfaults. 
This is happening on both of the computers I use KDE on.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Exovenom Mail of type IMAP E-Mail Server (akonadi_imap_resource),
signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f0350e38780 (LWP 1872))]

Thread 4 (Thread 0x7f033d213700 (LWP 4312)):
#0  0x7f034c7a24ad in poll () at /lib64/libc.so.6
#1  0x7f034b72bbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f034b72bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f03504770de in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
(this=0x7f0330003160, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f0350448e6f in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
(this=this@entry=0x7f033d212e60, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f0350449165 in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)
(this=this@entry=0x7f033d212e60, flags=...) at kernel/qeventloop.cpp:204
#6  0x7f03503460bf in QThread::exec() (this=optimized out) at
thread/qthread.cpp:538
#7  0x7f035034879f in QThreadPrivate::start(void*) (arg=0x1107c60) at
thread/qthread_unix.cpp:349
#8  0x7f034be103a4 in start_thread (arg=0x7f033d213700) at
pthread_create.c:310
#9  0x7f034c7aaa4d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f03364de700 (LWP 2908)):
#0  0x7f034c79e57d in read () at /lib64/libc.so.6
#1  0x7f034b76c750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f034b72b714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f034b72bb7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f034b72bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f03504770de in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
(this=0x7f032c009e10, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f0350448e6f in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
(this=this@entry=0x7f03364dde60, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f0350449165 in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)
(this=this@entry=0x7f03364dde60, flags=...) at kernel/qeventloop.cpp:204
#8  0x7f03503460bf in QThread::exec() (this=optimized out) at
thread/qthread.cpp:538
#9  0x7f035034879f in QThreadPrivate::start(void*) (arg=0x10fbd40) at
thread/qthread_unix.cpp:349
#10 0x7f034be103a4 in start_thread (arg=0x7f03364de700) at
pthread_create.c:310
#11 0x7f034c7aaa4d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f033da14700 (LWP 4318)):
#0  0x7fffe4f68b26 in clock_gettime ()
#1  0x7f034c7b746d in clock_gettime () at /lib64/libc.so.6
#2  0x7f035039cd47 in qt_gettime() (frac=0x7f033da13bf0,
sec=0x7f033da13be8) at tools/qelapsedtimer_unix.cpp:127
#3  0x7f035039cd47 in qt_gettime() () at tools/qelapsedtimer_unix.cpp:144
#4  0x7f0350478875 in QTimerInfoList::timerWait(timeval)
(this=0x7f0338011f80) at kernel/qeventdispatcher_unix.cpp:354
#5  0x7f0350478875 in QTimerInfoList::timerWait(timeval)
(this=0x7f0338011f80, tm=...) at kernel/qeventdispatcher_unix.cpp:460
#6  0x7f0350476f8c in timerSourcePrepareHelper(GTimerSource*, gint*)
(src=optimized out, timeout=0x7f033da13ca4) at
kernel/qeventdispatcher_glib.cpp:143
#7  0x7f0350477035 in timerSourcePrepare(GSource*, gint*)
(source=optimized out, timeout=optimized out) at
kernel/qeventdispatcher_glib.cpp:176
#8  0x7f034b72b28d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#9  0x7f034b72bb03 in  () at /usr/lib64/libglib-2.0.so.0
#10 0x7f034b72bcec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#11 0x7f03504770de in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
(this=0x7f03380144a0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#12 0x7f0350448e6f in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag)
(this=this@entry=0x7f033da13e60, flags=...) at 

[kontact] [Bug 336019] New: moving local Folders to another local folder

2014-06-09 Thread scott
https://bugs.kde.org/show_bug.cgi?id=336019

Bug ID: 336019
   Summary: moving local Folders to another local  folder
Classification: Unclassified
   Product: kontact
   Version: 4.11.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: venti...@zoho.com

Application: kontact (4.11.5)
KDE Platform Version: 4.11.5
Qt Version: 4.8.5
Operating System: Linux 3.11.10-11-desktop x86_64
Distribution: openSUSE 13.1 (Bottle) (x86_64)

-- Information about the crash:
Was moving some local Folders to another local folder, worked the first time
but, second time crashed nothing else

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f63fe728880 (LWP 18209))]

Thread 4 (Thread 0x7f63e1d4a700 (LWP 18210)):
#0  0x7f63f5d3b0af in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f63f94d1f76 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x7f63f94d1fa9 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x7f63f5d370db in start_thread () from /lib64/libpthread.so.0
#4  0x7f63fbc6690d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f63a143f700 (LWP 18211)):
#0  0x7f63f5d3b0af in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f63f92442cd in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x7f63f94f9ad6 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x7f63f5d370db in start_thread () from /lib64/libpthread.so.0
#4  0x7f63fbc6690d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f6391570700 (LWP 18224)):
#0  0x7f63fbc5db3d in poll () from /lib64/libc.so.6
#1  0x7f63f5774604 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f63f577470c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f63fc3e3d76 in QEventDispatcherGlib::processEvents
(this=0x7f63880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#4  0x7f63fc3b5d0f in QEventLoop::processEvents
(this=this@entry=0x7f639156fd60, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f63fc3b6005 in QEventLoop::exec (this=this@entry=0x7f639156fd60,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f63fc2b4fef in QThread::exec (this=optimized out) at
thread/qthread.cpp:536
#7  0x7f63fc2b768f in QThreadPrivate::start (arg=0xeda640) at
thread/qthread_unix.cpp:338
#8  0x7f63f5d370db in start_thread () from /lib64/libpthread.so.0
#9  0x7f63fbc6690d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f63fe728880 (LWP 18209)):
[KCrash Handler]
#6  QSortFilterProxyModelPrivate::proxy_to_source (this=0x1123ae0,
proxy_index=...) at itemviews/qsortfilterproxymodel.cpp:369
#7  0x7f63fd34005d in QSortFilterProxyModel::mapToSource (this=optimized
out, proxyIndex=...) at itemviews/qsortfilterproxymodel.cpp:2519
#8  0x7f63fd3385a8 in QSortFilterProxyModel::data (this=optimized out,
index=..., role=43) at itemviews/qsortfilterproxymodel.cpp:1732
#9  0x7f63facdcce6 in ?? () from /usr/lib64/libakonadi-kde.so.4
#10 0x7f63facd98a9 in ?? () from /usr/lib64/libakonadi-kde.so.4
#11 0x7f63fc3cad68 in QMetaObject::activate (sender=sender@entry=0x131b030,
m=m@entry=0x7f63fd879c80 QMenu::staticMetaObject,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff59a24280)
at kernel/qobject.cpp:3556
#12 0x7f63fd1ece72 in QMenu::triggered (this=this@entry=0x131b030,
_t1=_t1@entry=0x1442e190) at .moc/release-shared/moc_qmenu.cpp:177
#13 0x7f63fd1ed048 in QMenuPrivate::activateCausedStack
(this=this@entry=0x5751560, causedStack=..., action=action@entry=0x1442e190,
action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at
widgets/qmenu.cpp:1048
#14 0x7f63fd1f1619 in QMenuPrivate::activateAction (this=0x5751560,
action=0x1442e190, action_e=QAction::Trigger, self=optimized out) at
widgets/qmenu.cpp:1130
#15 0x7f63fce17dfe in QWidget::event (this=this@entry=0x1ffa570,
event=event@entry=0x7fff59a24890) at kernel/qwidget.cpp:8376
#16 0x7f63fd1f53eb in QMenu::event (this=0x1ffa570, e=0x7fff59a24890) at
widgets/qmenu.cpp:2481
#17 0x7f63fcdc88ac in QApplicationPrivate::notify_helper
(this=this@entry=0xc3cc70, receiver=receiver@entry=0x1ffa570,
e=e@entry=0x7fff59a24890) at kernel/qapplication.cpp:4562
#18 0x7f63fcdcefad in QApplication::notify (this=this@entry=0x7fff59a25f40,
receiver=receiver@entry=0x1ffa570, e=e@entry=0x7fff59a24890) at
kernel/qapplication.cpp:4105
#19 0x7f63fdadf18a in KApplication::notify (this=0x7fff59a25f40,
receiver=0x1ffa570, event=0x7fff59a24890) at
/usr/src/debug/kdelibs-4.11.5/kdeui/kernel/kapplication.cpp:311
#20 0x7f63fc3b70ad in QCoreApplication::notifyInternal
(this=0x7fff59a25f40, receiver=receiver@entry=0x1ffa570,

[kmail2] [Bug 334753] New: Kmail Crashes when using Reply All

2014-05-14 Thread Scott
https://bugs.kde.org/show_bug.cgi?id=334753

Bug ID: 334753
   Summary: Kmail Crashes when using Reply All
Classification: Unclassified
   Product: kmail2
   Version: 4.10.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: scot...@worldsofwar.co.uk

Application: kmail (4.10.5)
KDE Platform Version: 4.10.5 release 1
Qt Version: 4.8.4
Operating System: Linux 3.7.10-1.16-desktop x86_64
Distribution: openSUSE 12.3 (x86_64)

-- Information about the crash:
- Custom settings of the application:

Runing X11 forwaring over ssh.  This makes the crash reproduceable every time,
Kmail crashes when it tries to start

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library /lib64/libthread_db.so.1.
[KCrash Handler]
#6  0x7f79312333d5 in raise () from /lib64/libc.so.6
#7  0x7f7931234858 in abort () from /lib64/libc.so.6
#8  0x7f793127344b in __libc_message () from /lib64/libc.so.6
#9  0x7f7931278fc6 in malloc_printerr () from /lib64/libc.so.6
#10 0x7f7931279d43 in _int_free () from /lib64/libc.so.6
#11 0x7f79323dd095 in free (alignment=8, x=optimized out) at
../../src/corelib/tools/qvector.h:99
#12 free (x=optimized out, this=optimized out) at
../../src/corelib/tools/qvector.h:468
#13 operator= (v=..., this=0x1e501d0) at ../../src/corelib/tools/qvector.h:395
#14 clear (this=0x1e501d0) at ../../src/corelib/tools/qvector.h:348
#15 QTextEngine::clearLineData (this=0x1e501d0) at text/qtextengine.cpp:1483
#16 0x7f7932425c3d in QTextDocumentLayout::documentChanged (this=0x19c1d90,
from=0, oldLength=0, length=6909) at text/qtextdocumentlayout.cpp:2869
#17 0x7f79325e837c in QTextEditPrivate::relayoutDocument
(this=this@entry=0x19c2ff0) at widgets/qtextedit.cpp:1438
#18 0x7f79325e8b89 in QTextEdit::resizeEvent (this=optimized out,
e=0x7fff97e57420) at widgets/qtextedit.cpp:1397
#19 0x7f79321d3315 in QWidget::event (this=0x19c1840, event=0x7fff97e57420)
at kernel/qwidget.cpp:8540
#20 0x7f793257df26 in QFrame::event (this=0x19c1840, e=0x7fff97e57420) at
widgets/qframe.cpp:557
#21 0x7f7931c45ef6 in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) ()
from /usr/lib64/libQtCore.so.4
#22 0x7f793218383c in QApplicationPrivate::notify_helper
(this=this@entry=0x1580730, receiver=receiver@entry=0x19c1630,
e=e@entry=0x7fff97e57420) at kernel/qapplication.cpp:4558
#23 0x7f7932187ceb in QApplication::notify (this=0x7fff97e582d0,
receiver=0x19c1630, e=0x7fff97e57420) at kernel/qapplication.cpp:4423
#24 0x7f79339ad7f6 in KApplication::notify (this=0x7fff97e582d0,
receiver=0x19c1630, event=0x7fff97e57420) at
/usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#25 0x7f7931c45d8e in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQtCore.so.4
#26 0x7f79321cd8e6 in sendEvent (event=0x7fff97e57420, receiver=0x19c1630)
at ../../src/corelib/kernel/qcoreapplication.h:231
#27 QWidgetPrivate::sendPendingMoveAndResizeEvents (this=this@entry=0x19c24f0,
recursive=recursive@entry=false, disableUpdates=optimized out,
disableUpdates@entry=false) at kernel/qwidget.cpp:7445
#28 0x7f79321d5281 in QWidgetPrivate::show_helper
(this=this@entry=0x19c24f0) at kernel/qwidget.cpp:7496
#29 0x7f79321d5682 in QWidget::setVisible (this=0x19c1630,
visible=optimized out) at kernel/qwidget.cpp:
#30 0x7f79321d521e in show (this=0x19c1630) at
../../src/gui/kernel/qwidget.h:494
#31 QWidgetPrivate::showChildren (this=this@entry=0x19c2ff0,
spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:7865
#32 0x7f79321d529d in QWidgetPrivate::show_helper
(this=this@entry=0x19c2ff0) at kernel/qwidget.cpp:7502
#33 0x7f79321d5682 in QWidget::setVisible (this=0x19c1840,
visible=optimized out) at kernel/qwidget.cpp:
#34 0x7f79321d521e in show (this=0x19c1840) at
../../src/gui/kernel/qwidget.h:494
#35 QWidgetPrivate::showChildren (this=this@entry=0x19bfd60,
spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:7865
#36 0x7f79321d529d in QWidgetPrivate::show_helper
(this=this@entry=0x19bfd60) at kernel/qwidget.cpp:7502
#37 0x7f79321d5682 in QWidget::setVisible (this=0x198d310,
visible=optimized out) at kernel/qwidget.cpp:
#38 0x7f79321d521e in show (this=0x198d310) at
../../src/gui/kernel/qwidget.h:494
#39 QWidgetPrivate::showChildren (this=this@entry=0x19cb990,
spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:7865
#40 0x7f79321d529d in QWidgetPrivate::show_helper
(this=this@entry=0x19cb990) at kernel/qwidget.cpp:7502
#41 0x7f79321d5682 in QWidget::setVisible (this=0x191db80,
visible=optimized out) at kernel/qwidget.cpp:
#42 0x7f79321d521e in show (this=0x191db80) at

[kontact] [Bug 327808] New: Kontact crash - customizing settings

2013-11-19 Thread scott
https://bugs.kde.org/show_bug.cgi?id=327808

Bug ID: 327808
   Summary: Kontact crash - customizing settings
Classification: Unclassified
   Product: kontact
   Version: 4.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: grey4...@outlook.com

Application: kontact (4.10.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.4
Operating System: Linux 3.8.0-23-generic x86_64
Distribution: Netrunner 5 Enigma (13.06)

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

Attempted to integrate kontact with other components. Kmail, etc...

- Custom settings of the application:

Opened settings. Selected the components I wanted intergrated. Upon saving the
settings, Kontact crashed..

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f7db7586700 (LWP 2775)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7dd2693585 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7dd26935d9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f7dcd0e8f8e in start_thread (arg=0x7f7db7586700) at
pthread_create.c:311
#4  0x7f7dd348ca0d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7f7d76d83700 (LWP 2776)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7dd23d9a09 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f7dd26c1cee in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f7dcd0e8f8e in start_thread (arg=0x7f7d76d83700) at
pthread_create.c:311
#4  0x7f7dd348ca0d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7f7d6e933700 (LWP 2779)):
#0  0x7fff727feaf7 in ?? ()
#1  0x013908d0 in ?? ()
#2  0x0002727a61e0 in ?? ()
#3  0x7f7d68002860 in ?? ()
#4  0x7f7d6e932bb0 in ?? ()
#5  0x7f7d6e932c68 in ?? ()
#6  0x in ?? ()

Thread 2 (Thread 0x7f7d6cf60700 (LWP 2785)):
#0  0x7f7dd347ffbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f7dcca261dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7dcca26304 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7dd48b2036 in QEventDispatcherGlib::processEvents
(this=0x7f7d68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7f7dd488238f in QEventLoop::processEvents
(this=this@entry=0x7f7d6cf5fd90, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f7dd4882618 in QEventLoop::exec (this=this@entry=0x7f7d6cf5fd90,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f7dd4784410 in QThread::exec (this=this@entry=0x145d960) at
thread/qthread.cpp:542
#7  0x7f7dd4863edf in QInotifyFileSystemWatcherEngine::run (this=0x145d960)
at io/qfilesystemwatcher_inotify.cpp:256
#8  0x7f7dd4786bec in QThreadPrivate::start (arg=0x145d960) at
thread/qthread_unix.cpp:338
#9  0x7f7dcd0e8f8e in start_thread (arg=0x7f7d6cf60700) at
pthread_create.c:311
#10 0x7f7dd348ca0d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f7dd5f0b7c0 (LWP 2774)):
[KCrash Handler]
#6  0x7f7d66516159 in AppearancePageFontsTab::doLoadOther (this=0x2356ee0)
at ../../kmail/configuredialog.cpp:885
#7  0x7f7d66529d1d in load (this=0x2356ee0) at
../../kmail/configuredialog_p.cpp:97
#8  ConfigModuleWithTabs::load (this=0x2356390) at
../../kmail/configuredialog_p.cpp:67
#9  0x7f7dd53589a9 in qt_static_metacall (_a=optimized out,
_id=optimized out, _o=optimized out, _c=optimized out) at
./kcmodule.moc:66
#10 KCModule::qt_static_metacall (_o=optimized out, _c=optimized out,
_id=optimized out, _a=optimized out) at ./kcmodule.moc:57
#11 0x7f7dd489d5be in QObject::event (this=this@entry=0x2356390,
e=e@entry=0x23afff0) at kernel/qobject.cpp:1194
#12 0x7f7dd3c761ca in QWidget::event (this=0x2356390, event=0x23afff0) at
kernel/qwidget.cpp:8845
#13 0x7f7dd3c298ec in QApplicationPrivate::notify_helper
(this=this@entry=0xed0ca0, receiver=receiver@entry=0x2356390,
e=e@entry=0x23afff0) at kernel/qapplication.cpp:4567
#14 0x7f7dd3c2c25b in QApplication::notify (this=this@entry=0x7fff727a61e0,
receiver=receiver@entry=0x2356390, e=e@entry=0x23afff0) at
kernel/qapplication.cpp:4428
#15 0x7f7dd52cc1a6 in KApplication::notify (this=0x7fff727a61e0,
receiver=0x2356390, event=0x23afff0) at ../../kdeui/kernel/kapplication.cpp:311
#16 0x7f7dd488363e in QCoreApplication::notifyInternal

[kontact] [Bug 327808] Kontact crash - customizing settings

2013-11-19 Thread scott
https://bugs.kde.org/show_bug.cgi?id=327808

scott grey4...@outlook.com changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Kubuntu Packages

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


[Akonadi] [Bug 326594] New: Crash when authorizing Google account for akonadi calendar sync

2013-10-24 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=326594

Bug ID: 326594
   Summary: Crash when authorizing Google account for akonadi
calendar sync
Classification: Unclassified
   Product: Akonadi
   Version: 4.11
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@redhat.com
  Reporter: k...@kitterman.com
CC: kdepim-bugs@kde.org

Application: akonadi_googlecalendar_resource (4.11)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-12-generic i686
Distribution: Ubuntu 13.10

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

I was attempting to reauthorize akonadi to sync the calendar from the Google
account.  When I clicked the button to authorize the application, there was a
crash.

- Unusual behavior I noticed:

The sequence started with an error that my Google calendar couldn't be reached
because my daily quota had been exceeded (which seems very odd since I didn't
actually do anything with the calendar today).

-- Backtrace:
Application: Google Calendars and Tasks (scott.kitter...@gmail.com) of type
Google Calendars and Tasks (akonadi_googlecalendar_resource), signal:
Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb19a3740 (LWP 26318))]

Thread 5 (Thread 0xaecd9b40 (LWP 26440)):
#0  g_mutex_get_impl (mutex=0xae3004e0) at
/build/buildd/glib2.0-2.38.0/./glib/gthread-posix.c:123
#1  0xb4f2ebd8 in g_mutex_unlock (mutex=mutex@entry=0xae3004e0) at
/build/buildd/glib2.0-2.38.0/./glib/gthread-posix.c:232
#2  0xb4eeb572 in g_main_context_check (context=context@entry=0xae3004e0,
max_priority=2147483647, fds=fds@entry=0xae302288, n_fds=n_fds@entry=1) at
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3554
#3  0xb4eebaea in g_main_context_iterate (context=context@entry=0xae3004e0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3709
#4  0xb4eebc98 in g_main_context_iteration (context=0xae3004e0, may_block=1) at
/build/buildd/glib2.0-2.38.0/./glib/gmain.c:3773
#5  0xb71f88df in QEventDispatcherGlib::processEvents (this=0xae300468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0xb71c79f3 in QEventLoop::processEvents (this=this@entry=0xaecd9228,
flags=...) at kernel/qeventloop.cpp:149
#7  0xb71c7d19 in QEventLoop::exec (this=this@entry=0xaecd9228, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb70b6e3d in QThread::exec (this=this@entry=0x9032438) at
thread/qthread.cpp:542
#9  0xb71a7e14 in QInotifyFileSystemWatcherEngine::run (this=0x9032438) at
io/qfilesystemwatcher_inotify.cpp:265
#10 0xb70b972f in QThreadPrivate::start (arg=0x9032438) at
thread/qthread_unix.cpp:338
#11 0xb4fcfd78 in start_thread (arg=0xaecd9b40) at pthread_create.c:311
#12 0xb59b001e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 4 (Thread 0xae2ffb40 (LWP 26441)):
#0  0xb7715424 in __kernel_vsyscall ()
#1  0xb4fd384b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb59bd9bc in __pthread_cond_wait (cond=0xb4a6bd90
WTF::pageheap_memory+20720, mutex=0xb4a6bd78 WTF::pageheap_memory+20696) at
forward.c:149
#3  0xb41f1a7c in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb41f1acf in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb4fcfd78 in start_thread (arg=0xae2ffb40) at pthread_create.c:311
#6  0xb59b001e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 3 (Thread 0xad9feb40 (LWP 26442)):
#0  0xb7715424 in __kernel_vsyscall ()
#1  0xb4fd384b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb59bd9bc in __pthread_cond_wait (cond=0xada4c7dc, mutex=0xada4c7c4) at
forward.c:149
#3  0xb4220ae3 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb3efc744 in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb4207866 in WTF::threadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb4220459 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb4fcfd78 in start_thread (arg=0xad9feb40) at pthread_create.c:311
#8  0xb59b001e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 2 (Thread 0xaca64b40 (LWP 26443)):
#0  0xb7715424 in __kernel_vsyscall ()
#1  0xb59c34d2 in clock_gettime (clock_id=1, tp=0xaca64048) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb71143ec in do_gettime (frac=0xaca64040, sec=0xaca64038) at
tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at 

[kontact] [Bug 323736] New: Segfault when deleting lots of notes

2013-08-19 Thread Robert Scott
https://bugs.kde.org/show_bug.cgi?id=323736

Bug ID: 323736
   Summary: Segfault when deleting lots of notes
Classification: Unclassified
   Product: kontact
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: notes
  Assignee: kdepim-bugs@kde.org
  Reporter: b...@humanleg.org.uk

Application: kontact (4.4.11)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.2
Operating System: Linux 3.2.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 7.1 (wheezy)

-- Information about the crash:
- What I was doing when the application crashed:
Deleting a note (actually lots of notes at once)

- Custom settings of the application:
This was a set of notes from a just-upgraded kde3 installation which had had
the side effect of duplicating each of my notes about 100 times. I was trying
to clean out some of the redundant ones.

Reproducible: Always




Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[KCrash Handler]
#6  KNotesResourceManager::deleteNote (this=0x280f6e0, journal=0x2c61340) at
../../../../knotes/resourcemanager.cpp:109
#7  0x7effba64d1ac in KNotesPart::killSelectedNotes (this=0x27c3a90) at
../../../../kontact/plugins/knotes/knotes_part.cpp:354
#8  0x7effba64d52d in qt_static_metacall (_a=optimized out,
_id=optimized out, _o=optimized out, _c=optimized out) at
./knotes_part.moc:89
#9  KNotesPart::qt_static_metacall (_o=optimized out, _c=optimized out,
_id=optimized out, _a=0x7fff9e853bc0) at ./knotes_part.moc:67
#10 0x7effd60fa54f in QMetaObject::activate (sender=0x29b9e60, m=optimized
out, local_signal_index=optimized out, argv=0x7fff9e853bc0) at
kernel/qobject.cpp:3547
#11 0x7effd5487502 in QAction::triggered (this=this@entry=0x29b9e60,
_t1=false) at .moc/release-shared/moc_qaction.cpp:277
#12 0x7effd54876f0 in QAction::activate (this=0x29b9e60, event=optimized
out) at kernel/qaction.cpp:1257
#13 0x7effd58c1413 in QMenuPrivate::activateCausedStack
(this=this@entry=0x18323b0, causedStack=..., action=action@entry=0x29b9e60,
action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at
widgets/qmenu.cpp:1028
#14 0x7effd58c7729 in QMenuPrivate::activateAction (this=0x18323b0,
action=0x29b9e60, action_e=QAction::Trigger, self=true) at
widgets/qmenu.cpp:1120
#15 0x7effd6c32340 in KMenu::mouseReleaseEvent (this=0x4f9bac0,
e=0x7fff9e854760) at ../../kdeui/widgets/kmenu.cpp:464
#16 0x7effd54dce10 in QWidget::event (this=0x4f9bac0, event=0x7fff9e854760)
at kernel/qwidget.cpp:8371
#17 0x7effd58c89db in QMenu::event (this=0x4f9bac0, e=0x7fff9e854760) at
widgets/qmenu.cpp:2469
#18 0x7effd548d70c in QApplicationPrivate::notify_helper
(this=this@entry=0x16434c0, receiver=receiver@entry=0x4f9bac0,
e=e@entry=0x7fff9e854760) at kernel/qapplication.cpp:4556
#19 0x7effd54923eb in QApplication::notify (this=optimized out,
receiver=0x4f9bac0, e=0x7fff9e854760) at kernel/qapplication.cpp:4099
#20 0x7effd6b79886 in KApplication::notify (this=0x7fff9e855430,
receiver=0x4f9bac0, event=0x7fff9e854760) at
../../kdeui/kernel/kapplication.cpp:311
#21 0x7effd60e4b5e in QCoreApplication::notifyInternal
(this=0x7fff9e855430, receiver=0x4f9bac0, event=0x7fff9e854760) at
kernel/qcoreapplication.cpp:915
#22 0x7effd548e54b in sendEvent (event=optimized out, receiver=optimized
out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#23 QApplicationPrivate::sendMouseEvent (receiver=0x4f9bac0,
event=0x7fff9e854760, alienWidget=0x0, nativeWidget=0x4f9bac0,
buttonDown=0x7effd5f632a8, lastMouseReceiver=..., spontaneous=true) at
kernel/qapplication.cpp:3167
#24 0x7effd5508e8c in QETWidget::translateMouseEvent
(this=this@entry=0x4f9bac0, event=event@entry=0x7fff9e854ed0) at
kernel/qapplication_x11.cpp:4457
#25 0x7effd5507d51 in QApplication::x11ProcessEvent (this=0x7fff9e855430,
event=0x7fff9e854ed0) at kernel/qapplication_x11.cpp:3646
#26 0x7effd552ebc2 in x11EventSourceDispatch (s=0x164a670, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#27 0x7effcdd2a355 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7effcdd2a688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7effcdd2a744 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7effd6113276 in QEventDispatcherGlib::processEvents (this=0x1609b60,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#31 0x7effd552e83e in QGuiEventDispatcherGlib::processEvents
(this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x7effd60e38af in QEventLoop::processEvents
(this=this@entry=0x7fff9e8552a0, flags=...) at kernel/qeventloop.cpp:149
#33 0x7effd60e3b38 in QEventLoop::exec (this=0x7fff9e8552a0, 

[kontact] [Bug 322264] Crash on startup

2013-07-12 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=322264

--- Comment #2 from Scott Kitterman k...@kitterman.com ---
It happened a few times right after I upgraded to 4.10.5, but not since, so I
don't know if I'll be able to do that or not.

-- 
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 322264] New: Crash on startup

2013-07-11 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=322264

Bug ID: 322264
   Summary: Crash on startup
Classification: Unclassified
   Product: kontact
   Version: 4.10.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@kitterman.com

Application: kontact (4.10.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.4
Operating System: Linux 3.8.0-26-generic i686
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:  I had been trouble getting
Kontact/Akonadi to work since updating to 4.10.5 and had manually exited
Kontact and manually stopped Akonadi.  The crash was almost instantly after
launching Kontact.  Akonadi was not started before the crash.

This is a bit concerning since I have not seen a crash like this prior to
4.10.5.

-- 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 0xb1650740 (LWP 3130))]

Thread 5 (Thread 0xaf07ab40 (LWP 3131)):
#0  0xb77c0424 in __kernel_vsyscall ()
#1  0xb318d84b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb60f1d7c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb56d7ae5 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb56d7b1f in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb3189d78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb60e43de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 4 (Thread 0xae759b40 (LWP 3133)):
#0  0xb77c0424 in __kernel_vsyscall ()
#1  0xb318d84b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb60f1d7c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb5708f63 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb53e7b1b in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb56ed982 in WTF::threadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb5708b12 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb3189d78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0xb60e43de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xac24ab40 (LWP 3136)):
#0  0xb77c0424 in __kernel_vsyscall ()
#1  0xb60d2c9b in read () from /lib/i386-linux-gnu/libc.so.6
#2  0xb3101d4e in read (__nbytes=16, __buf=0xac24a03c, __fd=optimized out) at
/usr/include/i386-linux-gnu/bits/unistd.h:44
#3  g_wakeup_acknowledge (wakeup=0x9d8c860) at
/build/buildd/glib2.0-2.36.0/./glib/gwakeup.c:212
#4  0xb30bf1e3 in g_main_context_check (context=context@entry=0xab9004e0,
max_priority=2147483647, fds=fds@entry=0xab902288, n_fds=n_fds@entry=1) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3502
#5  0xb30bf662 in g_main_context_iterate (context=context@entry=0xab9004e0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3698
#6  0xb30bf831 in g_main_context_iteration (context=0xab9004e0, may_block=1) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3762
#7  0xb6f0dc3f in QEventDispatcherGlib::processEvents (this=0xab900468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#8  0xb6eda3ec in QEventLoop::processEvents (this=this@entry=0xac24a228,
flags=...) at kernel/qeventloop.cpp:149
#9  0xb6eda6e1 in QEventLoop::exec (this=this@entry=0xac24a228, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb6dc5fec in QThread::exec (this=this@entry=0xa34d620) at
thread/qthread.cpp:542
#11 0xb6eb9f2d in QInotifyFileSystemWatcherEngine::run (this=0xa34d620) at
io/qfilesystemwatcher_inotify.cpp:256
#12 0xb6dc8b18 in QThreadPrivate::start (arg=0xa34d620) at
thread/qthread_unix.cpp:338
#13 0xb3189d78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#14 0xb60e43de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xab80cb40 (LWP 3152)):
#0  0xb77c0424 in __kernel_vsyscall ()
#1  0xb60d4dcb in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb30ce2db in poll (__timeout=830, __nfds=1, __fds=0xaaf02160) at
/usr/include/i386-linux-gnu/bits/poll2.h:46
#3  g_poll (fds=0xaaf02160, nfds=1, timeout=830) at
/build/buildd/glib2.0-2.36.0/./glib/gpoll.c:132
#4  0xb30bf6d0 in g_main_context_poll (n_fds=1, fds=0xaaf02160,
timeout=optimized out, context=0xaaf004e0, priority=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3995
#5  g_main_context_iterate (context=context@entry=0xaaf004e0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3696
#6  0xb30bf831 in 

[Akonadi] [Bug 321077] New: Crash while adding Google account to akonadi_googlecalendar_resource

2013-06-12 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=321077

Bug ID: 321077
   Summary: Crash while adding Google account to
akonadi_googlecalendar_resource
Classification: Unclassified
   Product: Akonadi
   Version: 4.10
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@redhat.com
  Reporter: k...@kitterman.com
CC: kdepim-bugs@kde.org

Application: akonadi_googlecalendar_resource (4.10)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.8.0-23-generic i686
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:  I was trying to validate the
googlecalendar resource with Google and was waiting for verification when the
crash happened.  After restarting akonadi, the account was listed in the
resource, but with insufficient permissions to actually read my calendars.

-- Backtrace:
Application: Google Calendars and Tasks (akonadi_googlecalendar_resource),
signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb2307740 (LWP 27525))]

Thread 7 (Thread 0xaf70ab40 (LWP 27536)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0xb5ccedcb in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb557b2db in poll (__timeout=-1, __nfds=1, __fds=0xaee022c0) at
/usr/include/i386-linux-gnu/bits/poll2.h:46
#3  g_poll (fds=0xaee022c0, nfds=1, timeout=-1) at
/build/buildd/glib2.0-2.36.0/./glib/gpoll.c:132
#4  0xb556c6d0 in g_main_context_poll (n_fds=1, fds=0xaee022c0,
timeout=optimized out, context=0xaee004e0, priority=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3995
#5  g_main_context_iterate (context=context@entry=0xaee004e0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3696
#6  0xb556c831 in g_main_context_iteration (context=0xaee004e0, may_block=1) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3762
#7  0xb7341c3f in QEventDispatcherGlib::processEvents (this=0xaee00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#8  0xb730e3ec in QEventLoop::processEvents (this=this@entry=0xaf70a228,
flags=...) at kernel/qeventloop.cpp:149
#9  0xb730e6e1 in QEventLoop::exec (this=this@entry=0xaf70a228, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb71f9fec in QThread::exec (this=this@entry=0xa0df0b0) at
thread/qthread.cpp:542
#11 0xb72edf2d in QInotifyFileSystemWatcherEngine::run (this=0xa0df0b0) at
io/qfilesystemwatcher_inotify.cpp:256
#12 0xb71fcb18 in QThreadPrivate::start (arg=0xa0df0b0) at
thread/qthread_unix.cpp:338
#13 0xb564ad78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#14 0xb5cde3de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 6 (Thread 0xaed4fb40 (LWP 27549)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0xb564e84b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb5cebd7c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb47c3ae5 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb47c3b1f in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb564ad78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb5cde3de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 5 (Thread 0xae42eb40 (LWP 27550)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0xb564e84b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb5cebd7c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb47f4f63 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb44d3b1b in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb47d9982 in WTF::threadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb47f4b12 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb564ad78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0xb5cde3de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 4 (Thread 0xad500b40 (LWP 27551)):
#0  0xb77ac424 in __kernel_vsyscall ()
#1  0xb5ccedcb in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb557b2db in poll (__timeout=6947, __nfds=1, __fds=0xacb02160) at
/usr/include/i386-linux-gnu/bits/poll2.h:46
#3  g_poll (fds=0xacb02160, nfds=1, timeout=6947) at
/build/buildd/glib2.0-2.36.0/./glib/gpoll.c:132
#4  0xb556c6d0 in g_main_context_poll (n_fds=1, fds=0xacb02160,
timeout=optimized out, context=0xacb004e0, priority=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3995
#5  g_main_context_iterate (context=context@entry=0xacb004e0,
block=block@entry=1, dispatch=dispatch@entry=1, 

[Akonadi] [Bug 320484] New: Akonadi Google Contacts crash during setup

2013-05-30 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=320484

Bug ID: 320484
   Summary: Akonadi Google Contacts crash during setup
Classification: Unclassified
   Product: Akonadi
   Version: 4.10
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@redhat.com
  Reporter: k...@kitterman.com
CC: kdepim-bugs@kde.org

Application: akonadi_googlecontacts_resource (4.10)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.0-22-generic i686
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:  I was trying to set up a
Google contacts service for Akonadi when I got the crash.  I do have an older,
non-KDE SC version installed, not sure if that's relevant.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Google Contacts (akonadi_googlecontacts_resource), signal:
Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb22b7740 (LWP 14982))]

Thread 5 (Thread 0xafc54b40 (LWP 14985)):
#0  0xb775b424 in __kernel_vsyscall ()
#1  0xb56a484b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb590ad7c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb4876ae5 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4876b1f in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb56a0d78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb58fd3de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 4 (Thread 0xaf333b40 (LWP 14986)):
#0  0xb775b424 in __kernel_vsyscall ()
#1  0xb56a484b in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb590ad7c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb48a7f63 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb4586b1b in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb488c982 in WTF::threadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xb48a7b12 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb56a0d78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0xb58fd3de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 3 (Thread 0xae400b40 (LWP 14987)):
#0  qt_gettime () at tools/qelapsedtimer_unix.cpp:143
#1  0xb732080e in QTimerInfoList::updateCurrentTime
(this=this@entry=0xada02074) at kernel/qeventdispatcher_unix.cpp:354
#2  0xb731f695 in timerSourceCheckHelper (src=0xada02040) at
kernel/qeventdispatcher_glib.cpp:150
#3  timerSourceCheckHelper (src=0xada02040) at
kernel/qeventdispatcher_glib.cpp:144
#4  0xb55c3117 in g_main_context_check (context=context@entry=0xada004e0,
max_priority=2147483647, fds=fds@entry=0xada02160, n_fds=n_fds@entry=1) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3545
#5  0xb55c3662 in g_main_context_iterate (context=context@entry=0xada004e0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3698
#6  0xb55c3831 in g_main_context_iteration (context=0xada004e0, may_block=1) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3762
#7  0xb731fc3f in QEventDispatcherGlib::processEvents (this=0xada00468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#8  0xb72ec3ec in QEventLoop::processEvents (this=this@entry=0xae400258,
flags=...) at kernel/qeventloop.cpp:149
#9  0xb72ec6e1 in QEventLoop::exec (this=this@entry=0xae400258, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb71d7fec in QThread::exec (this=this@entry=0x96bd580) at
thread/qthread.cpp:542
#11 0xb71d814b in QThread::run (this=0x96bd580) at thread/qthread.cpp:609
#12 0xb71dab18 in QThreadPrivate::start (arg=0x96bd580) at
thread/qthread_unix.cpp:338
#13 0xb56a0d78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#14 0xb58fd3de in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xac4ffb40 (LWP 14990)):
#0  0xb56a2de3 in pthread_mutex_lock () from
/lib/i386-linux-gnu/libpthread.so.0
#1  0xb590af84 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6
#2  0xb5606d30 in g_mutex_lock (mutex=mutex@entry=0xabb004e0) at
/build/buildd/glib2.0-2.36.0/./glib/gthread-posix.c:210
#3  0xb55c2711 in g_main_context_acquire (context=0xabb004e0) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3115
#4  0xb55c3578 in g_main_context_iterate (context=context@entry=0xabb004e0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/build/buildd/glib2.0-2.36.0/./glib/gmain.c:3651
#5  0xb55c3831 in g_main_context_iteration (context=0xabb004e0, may_block=1) at

[Akonadi] [Bug 320484] Akonadi Google Contacts crash during setup

2013-05-30 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=320484

Scott Kitterman k...@kitterman.com changed:

   What|Removed |Added

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

--- Comment #2 from Scott Kitterman k...@kitterman.com ---
You misunderstand.  This was from the one shipped with 4.10, I just happen to
have the older one installed too.

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


[libkgapi] [Bug 320484] Akonadi Google Contacts crash during setup

2013-05-30 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=320484

--- Comment #4 from Scott Kitterman k...@kitterman.com ---
I got an SSL certificate pop up that I accepted.  I think that was it.

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


[kleopatra] [Bug 316306] Kleopatra segfaults when trusting a previously untrusted root certificate

2013-04-19 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=316306

Scott Kitterman k...@kitterman.com changed:

   What|Removed |Added

 CC||k...@kitterman.com

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


[kleopatra] [Bug 316306] Kleopatra segfaults when trusting a previously untrusted root certificate

2013-04-19 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=316306

--- Comment #1 from Scott Kitterman k...@kitterman.com ---
Created attachment 79032
  -- https://bugs.kde.org/attachment.cgi?id=79032action=edit
New crash information added by DrKonqi

kleopatra (2.1.1) on KDE Platform 4.9.5 using Qt 4.8.3

- What I was doing when the application crashed:

I was marking an untrusted GPG key as trusted (this is not just about root
certificates).

-- Backtrace (Reduced):
#7  QSortFilterProxyModelPrivate::updateChildrenMapping (this=0x9c02ab0,
source_parent=..., parent_mapping=0x9f110c0, orient=Qt::Vertical, start=0,
end=0, delta_item_count=1, remove=true) at
itemviews/qsortfilterproxymodel.cpp:948
#8  0xb6ab8f7c in source_items_removed (orient=Qt::Vertical, end=0, start=0,
source_parent=..., this=0x9c02ab0) at itemviews/qsortfilterproxymodel.cpp:890
#9  QSortFilterProxyModelPrivate::source_items_removed (this=0x9c02ab0,
source_parent=..., start=0, end=0, orient=Qt::Vertical) at
itemviews/qsortfilterproxymodel.cpp:848
#10 0xb6ab915b in QSortFilterProxyModelPrivate::_q_sourceRowsRemoved
(this=0x9c02ab0, source_parent=..., start=0, end=0) at
itemviews/qsortfilterproxymodel.cpp:1298
[...]
#12 0xb5f888b5 in QAbstractItemModel::rowsRemoved (this=0x9dc72d8, _t1=...,
_t2=0, _t3=0) at .moc/release-shared/moc_qabstractitemmodel.cpp:211

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


[kmail] [Bug 188222] Remote mailbox control not available

2013-02-14 Thread Scott Neville
https://bugs.kde.org/show_bug.cgi?id=188222

Scott Neville scott.nevi...@bluestar-software.co.uk changed:

   What|Removed |Added

 CC||scott.neville@bluestar-soft
   ||ware.co.uk

--- Comment #3 from Scott Neville scott.nevi...@bluestar-software.co.uk ---
Hi,

I have just upgraded to kmail2, and this feature is present in kmail1 but
appears to have been removed from kmail2.  Unless I cant find it?  We have a
shared remote mailbox called ~public which everyone has access too, but Kmail
can no longer see it.

-- 
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 293633] KMail asked for an IMAP password, entered and crashed

2012-12-01 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=293633

--- Comment #18 from Scott Kitterman k...@kitterman.com ---
I reported one of the duplicates (298326) and I don't recall seeing the
behavior I reported since I upgraded to 4.9.

-- 
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 293633] KMail asked for an IMAP password, entered and crashed

2012-12-01 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=293633

--- Comment #20 from Scott Kitterman k...@kitterman.com ---
Try removing the .dat files in ~/.config/akonadi.  I've had to do that due to a
different bug, so perhaps that's the difference.

-- 
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 298328] Crash on Kontact Startup

2012-05-09 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298328

Scott Kitterman k...@kitterman.com changed:

   What|Removed |Added

 CC||k...@kitterman.com

-- 
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 298328] Crash on Kontact Startup

2012-05-09 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298328

--- Comment #4 from Scott Kitterman k...@kitterman.com ---
Created attachment 70978
  -- https://bugs.kde.org/attachment.cgi?id=70978action=edit
New crash information added by DrKonqi

kontact (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

Kontact crashed on startup.

- Unusual behavior I noticed:

Akonadi was not running when I started Kontact (I'd stopped it manually).  I
don't believe I've seen this when Akonadi was running before Kontact.

-- Backtrace (Reduced):
#7  0xb76b0b8b in QString (other=..., this=0xbfa32054) at
/usr/include/qt4/QtCore/qstring.h:725
#8  KontactInterface::Plugin::identifier (this=0x986d2f8) at
../../kontactinterface/plugin.cpp:101
#9  0xb76e0ee0 in activateInitialPluginModule (this=0x9584fc0) at
../../../kontact/src/mainwindow.cpp:320
#10 Kontact::MainWindow::activateInitialPluginModule (this=0x9584fc0) at
../../../kontact/src/mainwindow.cpp:315
#11 0xb76e0fd5 in Kontact::MainWindow::setInitialActivePluginModule
(this=0x9584fc0, module=...) at ../../../kontact/src/mainwindow.cpp:297

-- 
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 298257] Akonadi resources start using a lot of memory and cpu when a .dat file is corrupted

2012-04-26 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298257

--- Comment #5 from Scott Kitterman k...@kitterman.com ---
akonadi_mailfilter_agent is shipped as part of kmail, so I think the product is
wrong on this bug.

-- 
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 298626] akonadi_mailftiler_agent crashes and fails to start after system freeze

2012-04-25 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298626

--- Comment #2 from Scott Kitterman k...@kitterman.com ---
 Does it crash immediately ? or does the resource start eating cpu  memory ?

It eats CPU and memory and then dies.  If I tell it to restart with Dr. Konqi, 
then it does again (and again and again).

-- 
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 298626] New: akonadi_mailftiler_agent crashes and fails to start after system freeze

2012-04-22 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298626

Bug ID: 298626
  Severity: crash
   Version: 4.8
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: akonadi_mailftiler_agent crashes and fails to start
after system freeze
Classification: Unclassified
OS: Linux
  Reporter: k...@kitterman.com
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: Mail Filter Agent
   Product: Akonadi

Application: akonadi_mailfilter_agent (4.8)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic-pae i686
Distribution: Ubuntu 12.04 LTS

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

My system was completely frozen due to a kernel panic, so I manually powered it
down and started again.  After boot, I got this crash, restarted the
mailfilter_agent, and then got it again.  

I saw something similar after upgrading from KDE 4.7 to 4.8.  I suspect some
kind of data corruption or unexpected condition causes mailfter_agent to crash.
 When this happened before, it took deleting all the local data and then
re-importing it to get mailfilter_agent to work again.

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Agent (akonadi_mailfilter_agent), signal: Aborted
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[KCrash Handler]
#7  0xb76f2424 in __kernel_vsyscall ()
#8  0xb567c1ef in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0xb567f835 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0xb58be13d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0xb58bbed3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0xb58bbf0f in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0xb58bc05e in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0xb67f3102 in qBadAlloc () at global/qglobal.cpp:1994
#15 0xb68010a5 in QByteArray::realloc (this=0xbffcf938, alloc=0) at
tools/qbytearray.cpp:1458
#16 0xb68036eb in detach (this=0xbffcf938) at
../../include/QtCore/../../src/corelib/tools/qbytearray.h:436
#17 detach (this=0xbffcf938) at tools/qbytearray.cpp:2754
#18 data (this=0xbffcf938) at
../../include/QtCore/../../src/corelib/tools/qbytearray.h:430
#19 operator (in=..., ba=...) at tools/qbytearray.cpp:2768
#20 0xb6b438b8 in loadFrom (device=optimized out, this=optimized out) at
../../akonadi/changerecorder_p.h:144
#21 Akonadi::ChangeRecorderPrivate::loadNotifications (this=0x89275b8) at
../../akonadi/changerecorder_p.h:123
#22 0xb6b40472 in Akonadi::ChangeRecorder::setConfig (this=0x6, settings=0x0)
at ../../akonadi/changerecorder.cpp:50
#23 0xb6b1c9a4 in Akonadi::AgentBasePrivate::init (this=0x8a049f8) at
../../akonadi/agentbase.cpp:216
#24 0xb6b1d7b9 in Akonadi::AgentBase::AgentBase (this=0x8a04a80, id=...) at
../../akonadi/agentbase.cpp:510
#25 0x08058db4 in MailFilterAgent::MailFilterAgent (this=0x8a04a80, id=...) at
../../mailfilteragent/mailfilteragent.cpp:52
#26 0x0805a01c in Akonadi::AgentBase::initMailFilterAgent (argc=3,
argv=0xbffcfd14) at /usr/include/akonadi/agentbase.h:335
#27 0x080505eb in main (argc=3, argv=0xbffcfd14) at
../../mailfilteragent/mailfilteragent.cpp:207

Possible duplicates by query: bug 284993, bug 283922, bug 277811, bug 272697.

Reported using DrKonqi

-- 
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 298328] Crash on Kontact Startup

2012-04-18 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298328

--- Comment #2 from Scott Kitterman k...@kitterman.com ---
It has happened a few times.  It was not reliably reproducable, but IIRC it did
happen with akonadi stopped.  At the time, Kontact was starting in Kmail.

-- 
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 298326] New: Crash after resume/failed to connect

2012-04-17 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298326

Bug ID: 298326
  Severity: crash
   Version: 4.8
  Priority: NOR
CC: kdepim-bugs@kde.org, vkra...@kde.org
  Assignee: er...@kde.org
   Summary: Crash after resume/failed to connect
Classification: Unclassified
OS: Linux
  Reporter: k...@kitterman.com
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: IMAP resource
   Product: Akonadi

Application: akonadi_imap_resource (4.8)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic-pae i686
Distribution: Ubuntu precise (development branch)

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

I had just resumed and got a dialogue that Kmail was unable to connect.  I
tried to enter the password manually after the resource in question was
restarted and it crashed again.

The crash can be reproduced some of the time.

-- Backtrace:
Application: IMAP Account 1 of type IMAP E-Mail Server (akonadi_imap_resource),
signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb49c1980 (LWP 7181))]

Thread 2 (Thread 0xb2191b40 (LWP 7196)):
#0  0xb5457770 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb5457f6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb54581c1 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb73138e7 in QEventDispatcherGlib::processEvents (this=0xb18bcd08,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0xb72df50d in QEventLoop::processEvents (this=0xb2191240, flags=...) at
kernel/qeventloop.cpp:149
#5  0xb72df7a9 in QEventLoop::exec (this=0xb2191240, flags=...) at
kernel/qeventloop.cpp:204
#6  0xb71c894c in QThread::exec (this=0x8973da0) at thread/qthread.cpp:501
#7  0xb72bcb5d in QInotifyFileSystemWatcherEngine::run (this=0x8973da0) at
io/qfilesystemwatcher_inotify.cpp:248
#8  0xb71cbde0 in QThreadPrivate::start (arg=0x8973da0) at
thread/qthread_unix.cpp:298
#9  0xb557ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#10 0xb5717ace in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb49c1980 (LWP 7181)):
[KCrash Handler]
#7  0x in ?? ()
#8  0xb72f8fb0 in QObject::connect (sender=0x893d420, signal=0x80acc64
2stateChanged(KIMAP::Session::State,KIMAP::Session::State),
receiver=0x8939418, method=0x80acc20
1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State),
type=Qt::AutoConnection) at kernel/qobject.cpp:2551
#9  0x0809b1e8 in SessionPool::onPasswordRequestDone (this=0x8939418,
resultType=0, password=...) at ../../../resources/imap/sessionpool.cpp:335
#10 0x0809ce10 in SessionPool::qt_static_metacall (_o=0x8939418,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfcd9254) at ./sessionpool.moc:94
#11 0xb72f76b1 in QMetaObject::activate (sender=0x89340e0, m=0x80aa7e0,
local_signal_index=0, argv=0xbfcd9254) at kernel/qobject.cpp:3547
#12 0x0808713f in PasswordRequesterInterface::done (this=0x89340e0, _t1=0,
_t2=...) at ./passwordrequesterinterface.moc:118
#13 0x08064b00 in SettingsPasswordRequester::onPasswordRequestCompleted
(this=0x89340e0, password=..., userRejected=false) at
../../../resources/imap/settingspasswordrequester.cpp:89
#14 0xb72f76b1 in QMetaObject::activate (sender=0x89371c0, m=0x80a3e20,
local_signal_index=0, argv=0xbfcd9374) at kernel/qobject.cpp:3547
#15 0x08063587 in Settings::passwordRequestCompleted (this=0x89371c0, _t1=...,
_t2=false) at ./settings.moc:124
#16 0x08063aa6 in Settings::onDialogFinished (this=0x89371c0, result=1) at
../../../resources/imap/settings.cpp:164
#17 0x08063cf9 in Settings::qt_static_metacall (_o=0x89371c0,
_c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfcd94b8) at ./settings.moc:74
#18 0xb72f76b1 in QMetaObject::activate (sender=0x896c548, m=0xb714e2c8,
local_signal_index=0, argv=0xbfcd94b8) at kernel/qobject.cpp:3547
#19 0xb6d1e815 in QDialog::finished (this=0x896c548, _t1=1) at
.moc/release-shared/moc_qdialog.cpp:153
#20 0xb6d1e909 in QDialog::done (this=0x896c548, r=1) at
dialogs/qdialog.cpp:597
#21 0xb6d1d0ea in QDialog::accept (this=0x896c548) at dialogs/qdialog.cpp:612
#22 0xb5cf9f3f in KPasswordDialog::KPasswordDialogPrivate::actuallyAccept
(this=0x8967630) at ../../kdeui/dialogs/kpassworddialog.cpp:404
#23 0xb5cfa053 in KPasswordDialog::qt_static_metacall (_o=0x896c548,
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x8974ed8) at
./kpassworddialog.moc:62
#24 0xb72f2c01 in QMetaCallEvent::placeMetaCall (this=0x896d1c0,
object=0x896c548) at kernel/qobject.cpp:525
#25 0xb72fbc7b in QObject::event (this=0x896c548, e=0x896d1c0) at
kernel/qobject.cpp:1195
#26 0xb6825e62 in QWidget::event (this=0x896c548, event=0x896d1c0) at
kernel/qwidget.cpp:8821
#27 0xb67cbed4 in notify_helper (e=0x896d1c0, receiver=0x896c548,
this=0x87f2058) at kernel/qapplication.cpp:4559
#28 

[Bug 290774] Kmail cannot send emails : Failed to get D-Bus interface of mailfilteragent.

2012-04-16 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=290774

Scott Kitterman k...@kitterman.com changed:

   What|Removed |Added

 CC||k...@kitterman.com

--- Comment #18 from Scott Kitterman k...@kitterman.com ---
(In reply to comment #13)
 The problem is in our KDEPIM-COMMON package, please close this bug report,
 i'm fixing this package right now.

What was the problem?  I'm having a similar problem with the Kubuntu packages,
so maybe we made the same mistake.

-- 
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 298148] New: Repeated crashes

2012-04-14 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=298148

Bug ID: 298148
  Severity: crash
   Version: 4.8
  Priority: NOR
CC: kdepim-bugs@kde.org, vkra...@kde.org
  Assignee: er...@kde.org
   Summary: Repeated crashes
Classification: Unclassified
OS: Linux
  Reporter: k...@kitterman.com
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: IMAP resource
   Product: Akonadi

Application: akonadi_imap_resource (4.8)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-23-generic-pae i686
Distribution: Ubuntu precise (development branch)

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

I wasn't actually paying attention to Kontact/Kmail when the crashes happen. 
This has been happening all day.  I tried stopping akonadi and restarting it,
but still got the crash.

-- Backtrace:
Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[KCrash Handler]
#7  0xb77ad424 in __kernel_vsyscall ()
#8  0xb56d81ef in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0xb56db835 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0xb591a13d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0xb5917ed3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0xb5917f0f in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0xb591805e in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0xb591867f in operator new(unsigned int) () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#15 0xb5659ae6 in Akonadi::NotificationMessage::NotificationMessage() () from
/usr/lib/libakonadiprotocolinternals.so.1
#16 0xb75c78ac in loadFrom (device=optimized out, this=optimized out) at
../../akonadi/changerecorder_p.h:142
#17 Akonadi::ChangeRecorderPrivate::loadNotifications (this=0x8e36a88) at
../../akonadi/changerecorder_p.h:123
#18 0xb75c4472 in Akonadi::ChangeRecorder::setConfig (this=0x6, settings=0x0)
at ../../akonadi/changerecorder.cpp:50
#19 0xb75a09a4 in Akonadi::AgentBasePrivate::init (this=0x8e1b618) at
../../akonadi/agentbase.cpp:216
#20 0xb75a16f3 in Akonadi::AgentBase::AgentBase (this=0x8e1d5f8, d=0x8e1b618,
id=...) at ../../akonadi/agentbase.cpp:518
#21 0xb768a699 in Akonadi::ResourceBase::ResourceBase (this=0x8e1d5f8, id=...)
at ../../akonadi/resourcebase.cpp:297
#22 0x0805a964 in ImapResource::ImapResource (this=0x8e1d5f8, id=...) at
../../../resources/imap/imapresource.cpp:95
#23 0x0805e3cc in Akonadi::ResourceBase::initImapResource (argc=3,
argv=0xbf96e5d4) at /usr/include/akonadi/resourcebase.h:180
#24 0x080586ab in main (argc=3, argv=0xbf96e5d4) at
../../../resources/imap/imapresource.cpp:607

Possible duplicates by query: bug 285381.

Reported using DrKonqi

-- 
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 294956] New: Kontact Crash While Focused Elsewhere

2012-02-27 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=294956

   Summary: Kontact Crash While Focused Elsewhere
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: k...@kitterman.com


Application: kontact (4.7.3)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic-pae i686
Distribution: Ubuntu 11.10

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

At the time of the crash, Kontact was not the window on top, so I don't know
exactly what happened, but I closed Chromium and then almost immediately
Kontact died as well.  I've no idea how they could be connected.

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

Thread 5 (Thread 0xb171bb70 (LWP 2480)):
#0  0xb7898424 in __kernel_vsyscall ()
#1  0xb3dd3a5c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0xb6237cfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb59df883 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb60fb340) at
wtf/FastMalloc.cpp:2495
#4  0xb59df99f in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0xb60fb340) at wtf/FastMalloc.cpp:1618
#5  0xb3dcfd31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb622a0ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 4 (Thread 0xb0df2b70 (LWP 2482)):
[KCrash Handler]
#7  0xb7898424 in __kernel_vsyscall ()
#8  0xb6185c8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0xb61892b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0xb61bbdfc in ?? () from /lib/i386-linux-gnu/libc.so.6
#11 0xb61c6bc2 in ?? () from /lib/i386-linux-gnu/libc.so.6
#12 0xb61c7862 in ?? () from /lib/i386-linux-gnu/libc.so.6
#13 0xb61ca94d in free () from /lib/i386-linux-gnu/libc.so.6
#14 0xb6eeae2b in qFree (ptr=0xb0401628) at global/qmalloc.cpp:60
#15 0xb6f1fbd7 in QMapData::continueFreeData (this=0xb0470ba0, offset=16) at
tools/qmap.cpp:93
#16 0xb700b8bc in QMapQString, QVariant::freeData (x=0xb0470ba0,
this=optimized out) at
../../include/QtCore/../../src/corelib/tools/qmap.h:654
#17 0xb700ebad in ~QMap (this=0xa59aeea0, __in_chrg=optimized out) at
../../include/QtCore/../../src/corelib/tools/qmap.h:187
#18 v_clearQMapQString, QVariant  (d=0xa59aeea0) at
../../include/QtCore/private/../../../src/corelib/kernel/qvariant_p.h:144
#19 clear (d=0xa59aeea0) at kernel/qvariant.cpp:208
#20 0xb6556779 in clear (d=0xa59aeea0) at kernel/qguivariant.cpp:280
#21 0xb700b83a in ~QVariant (this=0xa59aeea0, __in_chrg=optimized out) at
kernel/qvariant.cpp:1408
#22 QVariant::~QVariant (this=0xa59aeea0, __in_chrg=optimized out) at
kernel/qvariant.cpp:1405
#23 0xb459d9db in node_destruct (to=0xb043a6f4, from=0xb043a6f4,
this=optimized out) at
../../include/QtCore/../../src/corelib/tools/qlist.h:418
#24 free (data=0xb043a6e0, this=optimized out) at
../../include/QtCore/../../src/corelib/tools/qlist.h:744
#25 ~QList (this=0xb0df1c38, __in_chrg=optimized out) at
../../include/QtCore/../../src/corelib/tools/qlist.h:719
#26 QListQVariant::~QList (this=0xb0df1c38, __in_chrg=optimized out) at
../../include/QtCore/../../src/corelib/tools/qlist.h:716
#27 0xb45a6df0 in QDBusConnectionPrivate::deliverCall (this=0xb0400c88,
object=0xb0412ac8, msg=..., metaTypes=..., slotIdx=0) at
qdbusintegrator.cpp:869
#28 0xb45b0c26 in QDBusCallDeliveryEvent::placeMetaCall (this=0x2548e338,
object=0xb0412ac8) at qdbusintegrator_p.h:103
#29 0xb7004b52 in QObject::event (this=0xb0412ac8, e=0x2548e338) at
kernel/qobject.cpp:1217
#30 0xb6517d84 in notify_helper (e=0x2548e338, receiver=0xb0412ac8,
this=0x842b460) at kernel/qapplication.cpp:4486
#31 QApplicationPrivate::notify_helper (this=0x842b460, receiver=0xb0412ac8,
e=0x2548e338) at kernel/qapplication.cpp:4458
#32 0xb651d133 in QApplication::notify (this=0x2548e338, receiver=0xb0412ac8,
e=0x2548e338) at kernel/qapplication.cpp:3886
#33 0xb75d7971 in KApplication::notify (this=0xbfa4a404, receiver=0xb0412ac8,
event=0x2548e338) at ../../kdeui/kernel/kapplication.cpp:311
#34 0xb6fec19e in QCoreApplication::notifyInternal (this=0xbfa4a404,
receiver=0xb0412ac8, event=0x2548e338) at kernel/qcoreapplication.cpp:787
#35 0xb6feff93 in sendEvent (event=optimized out, receiver=optimized out)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x8523398) at kernel/qcoreapplication.cpp:1428
#37 0xb6ff00ec in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1321
#38 0xb701a6a4 in sendPostedEvents () at

[Bug 289506] Errors when scanning nested IMAP folders

2011-12-21 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=289506


Scott Kitterman k...@kitterman.com changed:

   What|Removed |Added

 CC||k...@kitterman.com




--- Comment #1 from Scott Kitterman kde kitterman com  2011-12-21 16:10:29 ---
I can confirm this problem.

-- 
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 221332] Unable to open TNEF files (winmail.dat)

2011-12-14 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=221332





--- Comment #4 from Scott Kitterman kde kitterman com  2011-12-13 23:22:22 ---
Excellent news.  Thank you.

-- 
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 284993] New: Akonadi imap resource crash Signal 6 aborted

2011-10-26 Thread Paul Scott
https://bugs.kde.org/show_bug.cgi?id=284993

   Summary: Akonadi imap resource crash Signal 6 aborted
   Product: Akonadi
   Version: 4.7
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Nepomuk Feeder Agents
AssignedTo: to...@kde.org
ReportedBy: paulssc...@gmail.com
CC: vkra...@kde.org, kdepim-bugs@kde.org


Application: akonadi_nepomuk_email_feeder (4.7)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic-pae i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
Trying to read email via IMAP using kontact. Can see list of emails in the
folder but when I click on an email I cannot see the content in the preview
pane or double click to bring up a window. Can read email that is stored in
local folders ok. Kubuntu 11.10

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Agent (akonadi_nepomuk_email_feeder), signal: Aborted
[KCrash Handler]
#7  0xb77f3424 in __kernel_vsyscall ()
#8  0xb595ec8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0xb59622b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0xb5b7c4ed in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0xb5b7a283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0xb5b7a2bf in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0xb5b7a40e in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0xb69e4f92 in qBadAlloc () at global/qglobal.cpp:2031
#15 0xb69f1a15 in QByteArray::realloc (this=0xbff446cc, alloc=0) at
tools/qbytearray.cpp:1429
#16 0xb69f407b in detach (this=0xbff446cc) at
../../include/QtCore/../../src/corelib/tools/qbytearray.h:418
#17 detach (this=0xbff446cc) at tools/qbytearray.cpp:2725
#18 data (this=0xbff446cc) at
../../include/QtCore/../../src/corelib/tools/qbytearray.h:412
#19 operator (in=..., ba=...) at tools/qbytearray.cpp:2739
#20 0xb6cec5dd in loadFrom (device=optimized out, this=optimized out) at
../../akonadi/changerecorder_p.h:144
#21 Akonadi::ChangeRecorderPrivate::loadNotifications (this=0x9153540) at
../../akonadi/changerecorder_p.h:118
#22 0xb6ce9092 in Akonadi::ChangeRecorder::setConfig (this=0x6, settings=0x0)
at ../../akonadi/changerecorder.cpp:50
#23 0xb6cc8464 in Akonadi::AgentBasePrivate::init (this=0x923ce00) at
../../akonadi/agentbase.cpp:214
#24 0xb6cc9249 in Akonadi::AgentBase::AgentBase (this=0x923d6e8, id=...) at
../../akonadi/agentbase.cpp:500
#25 0x0806089b in NepomukFeederAgentBase::NepomukFeederAgentBase
(this=0x923d6e8, id=...) at
../../nepomuk_email_feeder/shared/nepomukfeederagentbase.cpp:98
#26 0x080535bd in NepomukFeederAgent (id=optimized out, this=optimized out)
at ../../nepomuk_email_feeder/shared/nepomukfeederagent.h:37
#27 Akonadi::NepomukEMailFeeder::NepomukEMailFeeder (this=0x923d6e8, id=...) at
../../nepomuk_email_feeder/nepomukemailfeeder.cpp:43
#28 0x080553cc in Akonadi::AgentBase::initAkonadi::NepomukEMailFeeder
(argc=3, argv=0xbff44aa4) at /usr/include/akonadi/agentbase.h:335
#29 0x0805307b in main (argc=3, argv=0xbff44aa4) at
../../nepomuk_email_feeder/nepomukemailfeeder.cpp:133

Possible duplicates by query: bug 283922, bug 277811, bug 272697.

Reported using DrKonqi

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


[Bug 283922] New: Crash on startup

2011-10-13 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=283922

   Summary: Crash on startup
   Product: Akonadi
   Version: 4.7
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Nepomuk Feeder Agents
AssignedTo: to...@kde.org
ReportedBy: k...@kitterman.com
CC: vkra...@kde.org, kdepim-bugs@kde.org


Application: akonadi_nepomuk_email_feeder (4.7)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic-pae i686
Distribution: Ubuntu 11.10

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

I had just restarted akonadi.  There was high CPU usage for awhile and then
crash.

-- Backtrace:
Application: Akonadi Agent (akonadi_nepomuk_email_feeder), signal: Aborted
[KCrash Handler]
#7  0xb7833424 in __kernel_vsyscall ()
#8  0xb599bc8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0xb599f2b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0xb5bb94ed in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0xb5bb7283 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0xb5bb72bf in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0xb5bb740e in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0xb6a21f92 in qBadAlloc () at global/qglobal.cpp:2031
#15 0xb6a2ea15 in QByteArray::realloc (this=0xbfd6b45c, alloc=0) at
tools/qbytearray.cpp:1429
#16 0xb6a3107b in detach (this=0xbfd6b45c) at
../../include/QtCore/../../src/corelib/tools/qbytearray.h:418
#17 detach (this=0xbfd6b45c) at tools/qbytearray.cpp:2725
#18 data (this=0xbfd6b45c) at
../../include/QtCore/../../src/corelib/tools/qbytearray.h:412
#19 operator (in=..., ba=...) at tools/qbytearray.cpp:2739
#20 0xb6d295dd in loadFrom (device=optimized out, this=optimized out) at
../../akonadi/changerecorder_p.h:144
#21 Akonadi::ChangeRecorderPrivate::loadNotifications (this=0x964e6a0) at
../../akonadi/changerecorder_p.h:118
#22 0xb6d26092 in Akonadi::ChangeRecorder::setConfig (this=0x6, settings=0x0)
at ../../akonadi/changerecorder.cpp:50
#23 0xb6d05464 in Akonadi::AgentBasePrivate::init (this=0x964b108) at
../../akonadi/agentbase.cpp:214
#24 0xb6d06249 in Akonadi::AgentBase::AgentBase (this=0x9644ee8, id=...) at
../../akonadi/agentbase.cpp:500
#25 0x0806089b in NepomukFeederAgentBase::NepomukFeederAgentBase
(this=0x9644ee8, id=...) at
../../nepomuk_email_feeder/shared/nepomukfeederagentbase.cpp:98
#26 0x080535bd in NepomukFeederAgent (id=optimized out, this=optimized out)
at ../../nepomuk_email_feeder/shared/nepomukfeederagent.h:37
#27 Akonadi::NepomukEMailFeeder::NepomukEMailFeeder (this=0x9644ee8, id=...) at
../../nepomuk_email_feeder/nepomukemailfeeder.cpp:43
#28 0x080553cc in Akonadi::AgentBase::initAkonadi::NepomukEMailFeeder
(argc=3, argv=0xbfd6b834) at /usr/include/akonadi/agentbase.h:335
#29 0x0805307b in main (argc=3, argv=0xbfd6b834) at
../../nepomuk_email_feeder/nepomukemailfeeder.cpp:133

Possible duplicates by query: bug 277811, bug 272697.

Reported using DrKonqi

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


[Bug 283196] Kontact crash using 4.7.x git head

2011-10-12 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=283196





--- Comment #2 from Scott Kitterman kde kitterman com  2011-10-12 15:51:02 ---
No.  It hasn't happened again.

-- 
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 282337] akonadi agent crashed on trying to get mail from unreachable IMAP server

2011-10-05 Thread Scott Kitterman
https://bugs.kde.org/show_bug.cgi?id=282337





--- Comment #2 from Scott Kitterman kde kitterman com  2011-10-05 14:05:15 ---
Created an attachment (id=64246)
 -- (http://bugs.kde.org/attachment.cgi?id=64246)
New crash information added by DrKonqi

akonadi_imap_resource (4.7) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4

- What I was doing when the application crashed:

Lost network connectivity and then automatic imap email check ran.  Akonadi
1.6.2 and kdepim* 4.7.2.

-- Backtrace (Reduced):
#7  0x08099f26 in takeFirst (this=0x9dead94) at
/usr/include/qt4/QtCore/qlist.h:477
#8  SessionPool::declareSessionReady (this=0x9dead70, session=0x9fc38c0) at
../../../resources/imap/sessionpool.cpp:207
#9  0x0809ba29 in SessionPool::onLoginDone (this=0x9dead70, job=0xa089f50) at
../../../resources/imap/sessionpool.cpp:348
#10 0x0809bd89 in SessionPool::qt_metacall (this=0x9dead70,
_c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfe24358) at
./sessionpool.moc:118
#11 0xb73c7b7d in metacall (argv=0xbfe24358, idx=14,
cl=QMetaObject::InvokeMetaMethod, object=0x9dead70) at
kernel/qmetaobject.cpp:237

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


  1   2   >