date:20170903

[korganizer] [Bug 384328] New: Sidebar Calender manager

2017-09-03 Thread KS

https://bugs.kde.org/show_bug.cgi?id=384328

Bug ID: 384328
   Summary: Sidebar Calender manager
   Product: korganizer
   Version: 5.1.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: cyberbr...@hotmail.com
  Target Milestone: ---

What ever check box list (or other information) that might be in the sidebar
for the Calender Manager is squished too close together vertically to be seen.

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

[kontact] [Bug 384324] New: View Calendars Side by Side

2017-09-03 Thread Richard Lee

https://bugs.kde.org/show_bug.cgi?id=384324

Bug ID: 384324
   Summary: View Calendars Side by Side
   Product: kontact
   Version: 5.6.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rlee17.incepto...@gmail.com
  Target Milestone: ---

Application: kontact (5.6.0)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.4.0-93-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed: Attempting to view two
calendars side by side. Each time I try, Kontact crashes. I am using
akonadi-ews if that matters.

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 0x7ff546250900 (LWP 15924))]

Thread 23 (Thread 0x7ff43d223700 (LWP 15970)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7ff55687336f in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#2  0x7ff556873b07 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#3  0x7ff5568748d0 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7ff556870f3d in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7ff5612d46ba in start_thread (arg=0x7ff43d223700) at
pthread_create.c:333
#6  0x7ff5647de3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 22 (Thread 0x7ff43e97d700 (LWP 15961)):
#0  0x7ff55f2af3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff55f2af49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff56531094b in QEventDispatcherGlib::processEvents
(this=0x7ff4340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7ff5652b97ca in QEventLoop::exec (this=this@entry=0x7ff43e97ccc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#4  0x7ff5650e2cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#5  0x7ff5650e7989 in QThreadPrivate::start (arg=0x25a81f0) at
thread/qthread_unix.cpp:368
#6  0x7ff5612d46ba in start_thread (arg=0x7ff43e97d700) at
pthread_create.c:333
#7  0x7ff5647de3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 21 (Thread 0x7ff4477fe700 (LWP 15958)):
#0  0x7ff55f2f3a79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff55f2af290 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff55f2af49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff56531094b in QEventDispatcherGlib::processEvents
(this=0x7ff4380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff5652b97ca in QEventLoop::exec (this=this@entry=0x7ff4477fdcc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7ff5650e2cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7ff5650e7989 in QThreadPrivate::start (arg=0x22946a0) at
thread/qthread_unix.cpp:368
#7  0x7ff5612d46ba in start_thread (arg=0x7ff4477fe700) at
pthread_create.c:333
#8  0x7ff5647de3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 20 (Thread 0x7ff447fff700 (LWP 15957)):
#0  0x7ff5647d270d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff55f2af38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff55f2af49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff56531094b in QEventDispatcherGlib::processEvents
(this=0x7ff448c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff5652b97ca in QEventLoop::exec (this=this@entry=0x7ff447ffecc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7ff5650e2cd4 in QThread::exec (this=) at
thread/qthread.cpp:515
#6  0x7ff5650e7989 in QThreadPrivate::start (arg=0x2265c70) at
thread/qthread_unix.cpp:368
#7  0x7ff5612d46ba in start_thread (arg=0x7ff447fff700) at
pthread_create.c:333
#8  0x7ff5647de3dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7ff44cc1c700 (LWP 15956)):
#0  0x7ff5647d270d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7ff55f2af38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff55f2af49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff56531094b in QEventDispatcherGlib::processEvents
(this=0x7ff4480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7ff5652b97ca in QEventLoop::exec (this=this@entry=0x7ff44cc1bcc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7ff5650e2cd4

[kmail2] [Bug 384254] window title not updated when switching tab

2017-09-03 Thread Thomas Monjalon

https://bugs.kde.org/show_bug.cgi?id=384254

--- Comment #4 from Thomas Monjalon  ---
Thanks a lot

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

[kdepim] [Bug 358116] messageviewer leaks temporary files with mail parts in it

2017-09-03 Thread Thomas Monjalon

https://bugs.kde.org/show_bug.cgi?id=358116

--- Comment #16 from Thomas Monjalon  ---
> > Or could they be created in a subfolder of /tmp?
> 
> messageviewer_XXX is not enough ?

No it's not enough because these files are never removed.
So my /tmp is filling and it prevents me from seeing my new files in /tmp.

> What is the advantage to create a subfolder ?

The advantage is to keep /tmp clean.
I use /tmp a lot and I need to keep it clean.

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

[kmail2] [Bug 378315] KMail crash on logout

2017-09-03 Thread NSLW

https://bugs.kde.org/show_bug.cgi?id=378315

NSLW  changed:

   What|Removed |Added

 CC||lukasz.wojnilow...@gmail.co
   ||m
 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

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

[korgac] [Bug 382151] Reminder daemon dialog: wrong date format in 'Date time' column (Trigger Time is correct)

2017-09-03 Thread Allen Winter

https://bugs.kde.org/show_bug.cgi?id=382151

Allen Winter  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Allen Winter  ---
should be fixed in 92a5ef10b6cd16272b61d8a21db35f3b6cd43846

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

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

2017-09-03 Thread Arthur Țițeică

https://bugs.kde.org/show_bug.cgi?id=381929

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[kontact] [Bug 384310] New: Kontact crashes every time when started

2017-09-03 Thread Kai Holthaus

https://bugs.kde.org/show_bug.cgi?id=384310

Bug ID: 384310
   Summary: Kontact crashes every time when started
   Product: kontact
   Version: 5.2.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kai_holth...@hotmail.com
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-33-generic x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
- What I was doing when the application crashed:
Starting Kontact. Kontact windows is displayed, and then immediately Kontact
crashes.

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 0x7f9f8f1df000 (LWP 4400))]

Thread 18 (Thread 0x7f9ed9687700 (LWP 4430)):
#0  0x7f9f850c98b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f9f8c7d0a26 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9f8c7cc252 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9f850c36da in start_thread (arg=0x7f9ed9687700) at
pthread_create.c:456
#5  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 17 (Thread 0x7f9ed9e88700 (LWP 4429)):
#0  0x7f9f8333aef0 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4b70 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9f8c99cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9f8c7caf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9f850c36da in start_thread (arg=0x7f9ed9e88700) at
pthread_create.c:456
#9  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f9ef910f700 (LWP 4422)):
#0  0x7f9f8333aef4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4f81 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f5514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9f8c99cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9f8c7caf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9f850c36da in start_thread (arg=0x7f9ef910f700) at
pthread_create.c:456
#9  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7f9ef9910700 (LWP 4420)):
#0  0x7f9f8333aef4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4a60 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9f8c99cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9f8c7caf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9f850c36da in start_thread (arg=0x7f9ef9910700) at
pthread_create.c:456
#9  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 14 (Thread 0x7f9efa111700 (LWP 4418)):
#0  0x7f9f832f2557 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4ec4 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f5514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at

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

2017-09-03 Thread Christoph Feck

https://bugs.kde.org/show_bug.cgi?id=350731

Christoph Feck  changed:

   What|Removed |Added

 CC||thopp...@web.de

--- Comment #47 from Christoph Feck  ---
*** Bug 384256 has been marked as a duplicate of this bug. ***

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

[akregator] [Bug 384256] Akregator mark 'new' messages to 'read' if using the fIlter

2017-09-03 Thread Christoph Feck

https://bugs.kde.org/show_bug.cgi?id=384256

Christoph Feck  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Christoph Feck  ---


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

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

[Akonadi] [Bug 384309] New: Adding a certain iCal resource makes Akonadi creates high CPU load

2017-09-03 Thread bugzilla_noreply

https://bugs.kde.org/show_bug.cgi?id=384309

Bug ID: 384309
   Summary: Adding a certain iCal resource makes Akonadi creates
high CPU load
   Product: Akonadi
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ICal file resource
  Assignee: kdepim-bugs@kde.org
  Reporter: spiolli...@googlemail.com
  Target Milestone: ---

Adding a certain Google Calendar iCal file to KOrganizer/ Akonadi makes Akonadi
use 80-100% CPU for a very long time. I removed the iCal resource after ca.
15-20min and restarted Akonadi + KOrganizer to end this behaviour.

How to reproduce:
1. Open KOrganizer
2. Add a new calendar
3. Choose "ICal calendar file"
4. Enter the following URI as filename:
https://calendar.google.com/calendar/ical/24l1i4pt8aosa0t34js2k7m...@group.calendar.google.com/public/basic.ics
I also enabled the "read-only" option.
5. Add the calendar and observe CPU load.

This behaviour doesn't only happen directly after adding the calendar. After
some tries I managed to add the calendar successfully without messing up my
system, but after a reboot the 100% CPU load issue appeared again.

If I shall provide additional information or logfiles, just tell me how.

I'm using Akonadi 17.08.0 on 64bit Gentoo system with mariadb as a backend

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

[korganizer] [Bug 384328] New: Sidebar Calender manager

[kontact] [Bug 384324] New: View Calendars Side by Side

[kmail2] [Bug 384254] window title not updated when switching tab

[kdepim] [Bug 358116] messageviewer leaks temporary files with mail parts in it

[kmail2] [Bug 378315] KMail crash on logout

[korgac] [Bug 382151] Reminder daemon dialog: wrong date format in 'Date time' column (Trigger Time is correct)

[akregator] [Bug 381929] Feeds list gets corrupted when akregator is restored on log in

[kontact] [Bug 384310] New: Kontact crashes every time when started

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

[akregator] [Bug 384256] Akregator mark 'new' messages to 'read' if using the fIlter

[Akonadi] [Bug 384309] New: Adding a certain iCal resource makes Akonadi creates high CPU load

11 matches

Site Navigation

Mail list logo

Footer information