[kontact] [Bug 373244] New: Kontact crashes on launch

2016-12-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=373244

Bug ID: 373244
   Summary: Kontact crashes on launch
   Product: kontact
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: simonlang1...@gmail.com
  Target Milestone: ---

Application: kontact (5.3.3 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.28.0
Operating System: Linux 4.8.12-1-ck-piledriver x86_64
Distribution: "Arch Linux"

-- Information about the crash:
Tried to start Kontact like everyday but it immediately crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe421d42840 (LWP 2203))]

Thread 33 (Thread 0x7fe2cf7fe700 (LWP 2320)):
#0  0x7fe41e79e48d in poll () at /usr/lib/libc.so.6
#1  0x7fe418579786 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe41857989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe41f2da72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe41f28423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe41f0a70f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fe41f0abd78 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fe41a566454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fe41e7a77df in clone () at /usr/lib/libc.so.6

Thread 32 (Thread 0x7fe2c700 (LWP 2319)):
#0  0x7fff77de1939 in  ()
#1  0x7fff77de1bbb in clock_gettime ()
#2  0x7fe41e7b46b6 in clock_gettime () at /usr/lib/libc.so.6
#3  0x7fe41f1511a1 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fe41f2d83a9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#5  0x7fe41f2d8955 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#6  0x7fe41f2d9f94 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fe418578c89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#8  0x7fe4185796ab in  () at /usr/lib/libglib-2.0.so.0
#9  0x7fe41857989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#10 0x7fe41f2da72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#11 0x7fe41f28423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#12 0x7fe41f0a70f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#13 0x7fe41f0abd78 in  () at /usr/lib/libQt5Core.so.5
#14 0x7fe41a566454 in start_thread () at /usr/lib/libpthread.so.0
#15 0x7fe41e7a77df in clone () at /usr/lib/libc.so.6

Thread 31 (Thread 0x7fe2d6fd5700 (LWP 2285)):
#0  0x7fe41e79a4ed in read () at /usr/lib/libc.so.6
#1  0x7fe4185bda10 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe418579235 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7fe418579724 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe41857989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fe41f2da72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fe41f28423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fe41f0a70f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fe41f0abd78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fe41a566454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fe41e7a77df in clone () at /usr/lib/libc.so.6

Thread 30 (Thread 0x7fe2d77d6700 (LWP 2283)):
#0  0x7fe41f0a2f3b in QMutex::lock() () at /usr/lib/libQt5Core.so.5
#1  0x7fe41f2d9e9f in  () at /usr/lib/libQt5Core.so.5
#2  0x7fe418578c89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe4185796ab in  () at /usr/lib/libglib-2.0.so.0
#4  0x7fe41857989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7fe41f2da72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7fe41f28423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7fe41f0a70f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7fe41f0abd78 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fe41a566454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fe41e7a77df in clone () at /usr/lib/libc.so.6

Thread 29 (Thread 0x7fe2e6ddd700 (LWP 2273)):
#0  0x7fe418578d72 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7fe4185796ab in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fe41857989c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fe41f2da72b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fe41f28423a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fe41f0a70f3 in QThread::exec() () at /us

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

2016-12-04 Thread darwin te
https://bugs.kde.org/show_bug.cgi?id=350731

--- Comment #34 from darwin te  ---
Is this fixed already? I am using kde neon 5.8.4. (Based on Ubuntu 16.04)

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

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

2016-12-04 Thread darwin te
https://bugs.kde.org/show_bug.cgi?id=350731

--- Comment #35 from darwin te  ---
Is this fixed already? I am using kde neon 5.8.4. (Based on Ubuntu 16.04)

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

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

2016-12-04 Thread darwin te
https://bugs.kde.org/show_bug.cgi?id=350731

--- Comment #33 from darwin te  ---
Is this fixed already? I am using kde neon 5.8.4. (Based on Ubuntu 16.04)

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

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

2016-12-04 Thread Sven Fischer
https://bugs.kde.org/show_bug.cgi?id=350731

Sven Fischer  changed:

   What|Removed |Added

 CC||s...@leiderfischer.de

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

[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately

2016-12-04 Thread Laurent Carlier
https://bugs.kde.org/show_bug.cgi?id=350731

Laurent Carlier  changed:

   What|Removed |Added

 CC|lordhea...@gmail.com|

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

[kmail2] [Bug 373256] New: "Delete duplicate messages" feature does not work

2016-12-04 Thread Gunter Ohrner
https://bugs.kde.org/show_bug.cgi?id=373256

Bug ID: 373256
   Summary: "Delete duplicate messages" feature does not work
   Product: kmail2
   Version: 5.3.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: kdeb...@customcdrom.de
  Target Milestone: ---

I tried "Folder -> Delete Duplicate Messages" on different folders and always
get the attached dialog as a result.

No messages seem to have been deleted in the process.

kMail 5.3.3, KDE Neon, German locale

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

[kmail2] [Bug 373256] "Delete duplicate messages" feature does not work

2016-12-04 Thread Gunter Ohrner
https://bugs.kde.org/show_bug.cgi?id=373256

--- Comment #1 from Gunter Ohrner  ---
Created attachment 102615
  --> https://bugs.kde.org/attachment.cgi?id=102615&action=edit
verbose information dialog after invoking "Delete duplicate messages"

I forgot to add: The account is a normal IMAP account (no DIMAP).

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

[kmail2] [Bug 368136] email only renders to a quarter of its designated space

2016-12-04 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=368136

jonathan.lucas.m...@gmail.com changed:

   What|Removed |Added

 CC||jonathan.lucas.mail@gmail.c
   ||om

--- Comment #6 from jonathan.lucas.m...@gmail.com ---
issue persists in kmail 5.3.3. 
similarly, once a specific mail is opened via double click in new window, it
keeps being non-scaled as seen in Lukas' screenshot.

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

[akregator] [Bug 141244] aKregator updates feed even if configured to never do so

2016-12-04 Thread Ricardo J . Barberis
https://bugs.kde.org/show_bug.cgi?id=141244

--- Comment #10 from Ricardo J. Barberis  ---
Unfortunately, this bug is still present on akregator 5.3.0 (applications
16.08.2) if you have Check feeds on startup enabled.

Feeds also get updated if you use Ctr+L to update all the feeds, even the feeds
configured to never update.

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

[akregator] [Bug 369382] Middle mouse click on article title behaves like left mouse button

2016-12-04 Thread Ricardo J . Barberis
https://bugs.kde.org/show_bug.cgi?id=369382

Ricardo J. Barberis  changed:

   What|Removed |Added

 CC||ricardo.barbe...@gmail.com

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

[akregator] [Bug 323462] akregator refreshes all feeds when network connection state changes

2016-12-04 Thread Ricardo J . Barberis
https://bugs.kde.org/show_bug.cgi?id=323462

--- Comment #7 from Ricardo J. Barberis  ---
I can confirm that this bug is resolved as of akregator 5.3.0 (applications
16.08.2).

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

[akregator] [Bug 235991] Images that previously failed to load are not reloaded when a feed is redisplayed

2016-12-04 Thread Ricardo J . Barberis
https://bugs.kde.org/show_bug.cgi?id=235991

--- Comment #2 from Ricardo J. Barberis  ---
I can confirm that this bug is resolved as of akregator 5.3.0 (applications
16.08.2).

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

[akregator] [Bug 323462] akregator refreshes all feeds when network connection state changes

2016-12-04 Thread Orivej Desh
https://bugs.kde.org/show_bug.cgi?id=323462

Orivej Desh  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

--- Comment #8 from Orivej Desh  ---
Thanks for the confirmation!  (I did not confirm it myself, although I reported
this bug, because my distribution Gentoo is cautious of updating KDE PIM, and
still ships the latest KDE 5 with KDE PIM 4.)

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

[akregator] [Bug 235991] Images that previously failed to load are not reloaded when a feed is redisplayed

2016-12-04 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=235991

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org
 Resolution|WAITINGFORINFO  |FIXED
   Version Fixed In||5.3.0
 Status|NEEDSINFO   |RESOLVED

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

[akregator] [Bug 202370] closing tab sets focus to search instead of content

2016-12-04 Thread Ricardo J . Barberis
https://bugs.kde.org/show_bug.cgi?id=202370

Ricardo J. Barberis  changed:

   What|Removed |Added

 CC||ricardo.barbe...@gmail.com

--- Comment #14 from Ricardo J. Barberis  ---
Still present in akregator 5.3.0

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

[akregator] [Bug 369045] read feed not fixed

2016-12-04 Thread Ricardo J . Barberis
https://bugs.kde.org/show_bug.cgi?id=369045

Ricardo J. Barberis  changed:

   What|Removed |Added

 CC||ricardo.barbe...@gmail.com

--- Comment #1 from Ricardo J. Barberis  ---
Can't reproduce on akregator 5.3.0, though new feeds usually get marked as read
on restart.

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

[kmail2] [Bug 373040] Stop line wrapping long links

2016-12-04 Thread Nilesh Sah
https://bugs.kde.org/show_bug.cgi?id=373040

Nilesh Sah  changed:

   What|Removed |Added

 CC||nilesh.sa...@gmail.com

--- Comment #1 from Nilesh Sah  ---
Can this bug be taken up by a newbie or does it require certain level of
expertise? Would really like a bit of guidance here.

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