[neon] [Bug 464783] Do not see Add account button for adding google calendar

2023-01-25 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=464783

Kedar Apte  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|CONFIRMED   |RESOLVED

--- Comment #2 from Kedar Apte  ---
Worked. thanks

-- 
You are receiving this mail because:
You are watching all bug changes.

[kalendar] [Bug 464783] New: Do not see Add account button for adding google calendar

2023-01-24 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=464783

Bug ID: 464783
   Summary: Do not see Add account button for adding google
calendar
Classification: Applications
   Product: kalendar
   Version: 22.12.1
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: plasmagee...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
On a freshly installed Kalendar app on KDE Neon, unable to add google calendar.
The add account section has no buttions to add accounts.


STEPS TO REPRODUCE
1. Install Kalendar
2. Click on Configure Kalendar
3. Click on Accounts

OBSERVED RESULT
1. Do not see any button or any way to add an account
2. Right click has no effect 

EXPECTED RESULT
1. Add button with ability to add Google Calendar

The bug can be seen on youtube here - https://youtu.be/xSvGDL9AISI



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE NEON 5.26
(available in About System)
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0 
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Kernel Version: 5.15.0-58-generic
Graphics Platform: X11

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 449024] Unable to fetch google calendar events

2022-02-02 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=449024

--- Comment #25 from Kedar Apte  ---
(In reply to Terry Barnaby from comment #11)
> Same issue on Fedora35, recently stopped working.

correctly articulated

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 449024] Unable to fetch google calendar events

2022-02-02 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=449024

Kedar Apte  changed:

   What|Removed |Added

 CC||plasmagee...@gmail.com

--- Comment #24 from Kedar Apte  ---
I am able to add google calendar, but it is not seen in Korganizer. When I
click on Add calendar, it shows, I have the calendar, but events are not seen.
Neither can I accept events in the google calendar. 

Below is my version levels
KDE Neon 5.23 - user edition
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
QT Version: 5.15.3
Kernel Version: 5.13.0-28-generic
Graphics Platform: X11
Korganizer Version: 5.19.1 (21.12.1)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 439885] New: KMAIL crashed

2021-07-15 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=439885

Bug ID: 439885
   Summary: KMAIL crashed
   Product: kmail2
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: plasmagee...@gmail.com
  Target Milestone: ---

Application: kmail (5.17.2 (21.04.2))

Qt Version: 5.15.3
Frameworks Version: 5.83.0
Operating System: Linux 5.8.0-59-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.3
Distribution: KDE neon User Edition 5.22

-- Information about the crash:
- What I was doing when the application crashed: - I was responding to an
email, the kmail crashed when I clicked Send

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault

[New LWP 118447]
[New LWP 118448]
[New LWP 118449]
[New LWP 118450]
[New LWP 118451]
[New LWP 118452]
[New LWP 118453]
[New LWP 118454]
[New LWP 118455]
[New LWP 118460]
[New LWP 118479]
[New LWP 118481]
[New LWP 118487]
[New LWP 118488]
[New LWP 118489]
[New LWP 118490]
[New LWP 118491]
[New LWP 118492]
[New LWP 118511]
[New LWP 118520]
[New LWP 118531]
[New LWP 118630]
[New LWP 119121]
[New LWP 132748]
[New LWP 144794]
[New LWP 145797]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fb9f56e2aff in __GI___poll (fds=0x7ffcd6fc4b78, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7fb9e65a4200 (LWP 118445))]

Thread 27 (Thread 0x7fb9350a5700 (LWP 145797)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7fb9350a40b0, clockid=, expected=0,
futex_word=0x7fb9350a4288) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7fb9350a40b0, clockid=, mutex=0x7fb9350a4238, cond=0x7fb9350a4260) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x7fb9350a4260, mutex=0x7fb9350a4238,
abstime=0x7fb9350a40b0) at pthread_cond_wait.c:656
#3  0x7fb9f9f2f20a in ?? () from
/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x0001ef58 in ?? ()
#5  0x3636ba8c in ?? ()
#6  0x0001ef37 in ?? ()
#7  0x3636ba8c in ?? ()
#8  0x7fb954001568 in ?? ()
#9  0x7c6fd7a01c04d000 in ?? ()
#10 0x in ?? ()

Thread 26 (Thread 0x7fb93cd22700 (LWP 144794)):
#0  0x7fb9f56e2aff in __GI___poll (fds=0x7fb988003790, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fb9e7c0d1d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7fb9e7bfe841 in pa_mainloop_poll () from
/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fb9e7bfeec3 in pa_mainloop_iterate () from
/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fb9e7bfef70 in pa_mainloop_run () from
/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fb9e7c0d11d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7fb9e705f72c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#7  0x7fb9f2543609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb9f56ef293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7fb937fff700 (LWP 132748)):
#0  0x7fb9f56e2aff in __GI___poll (fds=0x7fb958003be0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fb9ef03d36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb9ef03d4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb9f5cb1fcb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb9f5c5625b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb9f5a6fc22 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb9f5a70dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb9f2543609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7fb9f56ef293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7fb9368a8700 (LWP 119121)):
#0  0x7fb9f5cb18ae in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fb9f5cb012d in QTimerInfoList::updateCurrentTime() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fb9f5cb0709 in QTimerInfoList::timerWait(timespec&) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fb9f5cb1d26 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb9ef03c8ef in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb9ef03d29b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7fb9ef03d4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fb9f5cb1fcb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb9f5c5625b in
QEven

[Akonadi] [Bug 439386] New: Kmail crashed

2021-07-01 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=439386

Bug ID: 439386
   Summary: Kmail crashed
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-b...@kde.org
  Reporter: plasmagee...@gmail.com
  Target Milestone: ---

Application: akonadi_imap_resource (5.17.2 (21.04.2))

Qt Version: 5.15.3
Frameworks Version: 5.83.0
Operating System: Linux 5.8.0-59-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.2
Distribution: KDE neon User Edition 5.22

-- Information about the crash:
- What I was doing when the application crashed: I was connected to SSL VPN
using openvpn to the corporate network. When I disconnected, kmail resource
crashed

The crash can be reproduced every time.

-- Backtrace:
Application: Zeta (akonadi_imap_resource), signal: Segmentation fault

[New LWP 1599]
[New LWP 1620]
[New LWP 1625]
[New LWP 1646]
[New LWP 1949]
[New LWP 2037]
[New LWP 10854]
[New LWP 10890]
[New LWP 11129]
[New LWP 12825]
[New LWP 12864]
[New LWP 13074]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7ff935343aff in __GI___poll (fds=0x7fff37767c78, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7ff930d38980 (LWP 1580))]

Thread 13 (Thread 0x7ff91cd91700 (LWP 13074)):
#0  0x7ff9346d8ae5 in g_main_context_query () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff9346d92e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff9346d94a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff93592bf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff9358d01eb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff9356e9bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff9356ead4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff9345c7609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7ff935350293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7ff8fb7fe700 (LWP 12864)):
#0  0x7ff9346d88aa in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7ff9346d929b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff9346d94a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff93592bf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff9358d01eb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff9356e9bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff9356ead4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff9345c7609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7ff935350293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7ff91d592700 (LWP 12825)):
#0  0x7ff935343aff in __GI___poll (fds=0x7ff8fc0017c0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff9346d936e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff9346d94a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff93592bf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff9358d01eb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff9356e9bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff9356ead4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff9345c7609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7ff935350293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7ff91ef6a700 (LWP 11129)):
#0  __GI___libc_read (nbytes=16, buf=0x7ff91ef69a10, fd=17) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=17, buf=0x7ff91ef69a10, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7ff934721b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff9346d8ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff9346d9312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff9346d94a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7ff93592bf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff9358d01eb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff9356e9bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7ff9356ead4c in ?? () 

[Discover] [Bug 438798] New: Discover crashed

2021-06-17 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=438798

Bug ID: 438798
   Summary: Discover crashed
   Product: Discover
   Version: 5.22.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: plasmagee...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.22.1)

Qt Version: 5.15.3
Frameworks Version: 5.83.0
Operating System: Linux 5.4.0-74-generic x86_64
Windowing System: X11
Drkonqi Version: 5.22.1
Distribution: KDE neon User Edition 5.22

-- Information about the crash:
- What I was doing when the application crashed: - I was checking for updates.
Since yesterday, I was being notified that there are updates available. Even
though all the updates were insatlled, there was a notification that updates
are available. Same updates were being installed again and again. tried
updating through the terminal as well. Right now the updates were being
re-installed through Discover and thats when Discover crashed.. Everytime, I am
starting Discover now and checking for updates, after sometime, it crashes. I
have done multiple restarts since yesterday

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault

[New LWP 30855]
[New LWP 30856]
[New LWP 30857]
[New LWP 30858]
[New LWP 30859]
[New LWP 30860]
[New LWP 30865]
[New LWP 30867]
[New LWP 30868]
[New LWP 30869]
[New LWP 30876]
[New LWP 30877]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f836d65eaff in __GI___poll (fds=0x7ffe5a8f7cf8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f836902ee40 (LWP 30853))]

Thread 13 (Thread 0x7f82d7fff700 (LWP 30877)):
#0  0x7f836c034508 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f836bfe7363 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f836bfe74a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f836dc2ab3b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f836dbcedcb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f836d9e8bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f836d9e9d4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f836ca43609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f836d66b293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7f8310ef1700 (LWP 30876)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x560994b2ec00) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x560994b2ebb0,
cond=0x560994b2ebd8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x560994b2ebd8, mutex=0x560994b2ebb0) at
pthread_cond_wait.c:638
#3  0x7f836d9efebb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f836f825b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f836f825fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f836d9e9d4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f836ca43609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f836d66b293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7f832d3e4700 (LWP 30869)):
#0  0x7f836d65eaff in __GI___poll (fds=0x7f83180b1790, nfds=1,
timeout=135055) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f836bfe736e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f836bfe74a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f836dc2ab3b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f836dbcedcb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f836d9e8bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f836d9e9d4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f836ca43609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f836d66b293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7f832dd0b700 (LWP 30868)):
#0  __GI___libc_read (nbytes=16, buf=0x7f832dd0aa10, fd=25) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=25, buf=0x7f832dd0aa10, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f836c02fb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f836bfe6ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f836bfe7312 in ?? () from 

[Akonadi] [Bug 438235] New: Akonadi server crashed

2021-06-08 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=438235

Bug ID: 438235
   Summary: Akonadi server crashed
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: SendLaterAgent
  Assignee: mon...@kde.org
  Reporter: plasmagee...@gmail.com
CC: kdepim-b...@kde.org
  Target Milestone: ---

Application: akonadi_sendlater_agent (5.17.1 (21.04.1))

Qt Version: 5.15.3
Frameworks Version: 5.82.0
Operating System: Linux 5.4.0-74-generic x86_64
Windowing System: X11
Drkonqi Version: 5.21.5
Distribution: KDE neon User Edition 5.21

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

I was trying to send out emails that were stuck in the outbox. I have two IMAP
email accounts conifgured with independent identities and independent smtp
servers. From one of the accounts, mail was getting stuck in the outboox. I was
trying to send it multiple times when this crash happened

The crash can be reproduced every time.

-- Backtrace:
Application: akonadi_sendlater_agent (akonadi_sendlater_agent), signal:
Segmentation fault

[New LWP 1696]
[New LWP 1732]
[New LWP 1733]
[New LWP 1734]
[New LWP 1735]
[New LWP 1749]
[New LWP 1750]
[New LWP 1841]
[New LWP 12578]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f579cfa6aff in __GI___poll (fds=0x7fff67f0fba8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f5786c08200 (LWP 1657))]

Thread 10 (Thread 0x7f57696b3700 (LWP 12578)):
#0  0x7f579cfa6aff in __GI___poll (fds=0x7f574c007170, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5769a6a1d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f5769a5b841 in pa_mainloop_poll () from
/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f5769a5bec3 in pa_mainloop_iterate () from
/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f5769a5bf70 in pa_mainloop_run () from
/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f5769a6a11d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f5769a0672c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#7  0x7f579b23d609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f579cfb3293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f576affd700 (LWP 1841)):
#0  __GI___libc_read (nbytes=16, buf=0x7f576affc190, fd=15) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=15, buf=0x7f576affc190, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f579a87fb2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f579a836ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f579a837312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f579a8374a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f579d58db3b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f579d531dcb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f579d34bbb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f579d34cd4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f579b23d609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7f579cfb3293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f576b7fe700 (LWP 1750)):
#0  0x7f579cfa6aff in __GI___poll (fds=0x7f576001f6c0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f579a83736e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f579a8374a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f579d58db3b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f579d531dcb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f579d34bbb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f579d34cd4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f579b23d609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f579cfb3293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f576bfff700 (LWP 1749)):
#0  0x7f579cfa6aff in __GI___poll (fds=0x7f576002fb00, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f579a83736e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f579a8374a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f579d58db3b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f579d53

[kdeconnect] [Bug 438065] kdeconnectd crashes on connection attempt from another device

2021-06-04 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=438065

Kedar Apte  changed:

   What|Removed |Added

 Status|VERIFIED|CLOSED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 438065] kdeconnectd crashes on connection attempt from another device

2021-06-04 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=438065

Kedar Apte  changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED

--- Comment #21 from Kedar Apte  ---
Works now. Thanks for the quick turn around

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 438065] kdeconnectd crashes on connection attempt from another device

2021-06-04 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=438065

--- Comment #20 from Kedar Apte  ---
beauty.. Works now. Thanks for the quick turnaround

On Fri, Jun 4, 2021 at 6:36 PM Adrien Beau  wrote:

> Adrien Beau  changed bug 438065
> <https://bugs.kde.org/show_bug.cgi?id=438065>
> What Removed Added
> CC   abe.kde.b...@zerty.xyz
>
> *Comment # 15 <https://bugs.kde.org/show_bug.cgi?id=438065#c15> on bug
> 438065 <https://bugs.kde.org/show_bug.cgi?id=438065> from Adrien Beau
>  *
>
> The newly built (and released) package works fine now.
>
> --
> You are receiving this mail because:
>
>- You are on the CC list for the bug.
>
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 438052] New: KDE Connect stopped working

2021-06-03 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=438052

Bug ID: 438052
   Summary: KDE Connect stopped working
   Product: kdeconnect
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: plasmagee...@gmail.com
  Target Milestone: ---

Application: kdeconnectd (21.04.1)

Qt Version: 5.15.3
Frameworks Version: 5.82.0
Operating System: Linux 5.4.0-74-generic x86_64
Windowing System: X11
Drkonqi Version: 5.21.5
Distribution: KDE neon User Edition 5.21

-- Information about the crash:
- What I was doing when the application crashed:
I was using KDE connect. I got a message saying there are updates. When I
installed the updates, it asked for a restart, installed the updates and since
then KD connect is crashing.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[New LWP 1319]
[New LWP 1329]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f5b11915aff in __GI___poll (fds=0x7fff06a26f28, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f5b0dde8d40 (LWP 1277))]

Thread 3 (Thread 0x7f5b06279700 (LWP 1329)):
#0  0x7f5b11915aff in __GI___poll (fds=0x7f5af8004a60, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f5b1040a36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f5b1040a4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5b11ee3b3b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f5b11e87dcb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5b11ca1bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5b11ca2d4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5b10e2b609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f5b11922293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f5b0748a700 (LWP 1319)):
#0  __GI___libc_read (nbytes=16, buf=0x7f5b07489aa0, fd=7) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=7, buf=0x7f5b07489aa0, nbytes=16) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7f5b10452b2f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f5b10409ebe in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f5b1040a312 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f5b1040a4a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f5b11ee3b3b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5b11e87dcb in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5b11ca1bb2 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f5b1280cf4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x7f5b11ca2d4c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f5b10e2b609 in start_thread (arg=) at
pthread_create.c:477
#12 0x7f5b11922293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7f5b0dde8d40 (LWP 1277)):
[KCrash Handler]
#4  Device::reloadPlugins (this=this@entry=0x560c82628ed0) at
./core/device.cpp:192
#5  0x7f5b13475990 in Device::pairStatusChanged (this=0x560c82628ed0,
status=DeviceLink::Paired) at ./core/device.cpp:249
#6  0x7f5b11ec02ee in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5b1342baa5 in DeviceLink::pairStatusChanged
(this=this@entry=0x560c82629050, _t1=,
_t1@entry=DeviceLink::Paired) at
./obj-x86_64-linux-gnu/core/kdeconnectcore_autogen/CSWKE6ESUK/moc_devicelink.cpp:211
#8  0x7f5b134555f8 in DeviceLink::setPairStatus
(this=this@entry=0x560c82629050, status=status@entry=DeviceLink::Paired) at
./core/backends/devicelink.cpp:26
#9  0x7f5b134457bf in LanDeviceLink::setPairStatus (this=0x560c82629050,
status=) at ./core/backends/lan/landevicelink.cpp:164
#10 0x7f5b1344715d in LanPairingHandler::acceptPairing
(this=0x560c8261ab80) at ./core/backends/lan/lanpairinghandler.cpp:83
#11 0x7f5b134720d2 in Device::acceptPairing (this=) at
./core/device.cpp:345
#12 0x7f5b11ec02ee in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f5b13260330 in KNotification::activate(unsigned int) () from
/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#14 0x7f5b13268507 in ?? () from
/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#15 0x7f5b11ec02ee in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f5b1325b283 in KNotificationPlugin::actionInvoked(int, int) () from
/lib/x86_64-linux-gn

[plasma-pa] [Bug 384875] Plasma Crashed

2020-12-06 Thread Kedar
https://bugs.kde.org/show_bug.cgi?id=384875

--- Comment #3 from Kedar  ---
Works. thanks for the help

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-pa] [Bug 384875] Plasma Crashed

2020-12-06 Thread Kedar
https://bugs.kde.org/show_bug.cgi?id=384875

Kedar  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Kedar  ---
(In reply to Justin Zobel from comment #1)
> Thank you for the report, Kedar.
> 
> As it has been a while since this was reported, can you please test and
> confirm if this issue is still occurring or if this bug report can be marked
> as resolved.
> 
> I have set the bug status to "needsinfo" pending your response, please
> change back to "reported" or "resolved/worksforme" when you respond, thank
> you.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 386839] High memory utilization for plasmshell

2017-11-13 Thread Kedar
https://bugs.kde.org/show_bug.cgi?id=386839

--- Comment #4 from Kedar  ---
Issue seems to have fixed. Looks like openshot was the culprit. I uninstalled
it  and gave the machine a restart and since then it is working as usual.

I also changed from the onboard display card to ATI / Radeon display card. The
performance has since improved dramatically. Can see that the displays don't
lag any more. I guess it was more of a display card issue for me.

Cheers

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 386839] High memory utilization for plasmshell

2017-11-13 Thread Kedar
https://bugs.kde.org/show_bug.cgi?id=386839

--- Comment #2 from Kedar  ---
Created attachment 108834
  --> https://bugs.kde.org/attachment.cgi?id=108834&action=edit
QT version and sys info

I have added the screenshot for the sysinfo

I have three 22inch (1080p) monitors all running picture of the day as desktop
background

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 386839] New: High memory utilization for plasmshell

2017-11-12 Thread Kedar
https://bugs.kde.org/show_bug.cgi?id=386839

Bug ID: 386839
   Summary: High memory utilization for plasmshell
   Product: plasmashell
   Version: 5.11.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kedar.a...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 108828
  --> https://bugs.kde.org/attachment.cgi?id=108828&action=edit
memory utilization by plasmashell

Hey

Today, after an update, (13th November), I found the memory utilization of the
plasmashell is about 2 GB. It was never the case before. I am running a KDE
Neon 5.11.3 and is fully updated.

I am not running any custom packages etc. Attached is the screenshot. Let me
know if you need any trace etc and the commands to run the same. Will be happy
to share the details. Right now the desktop has become un-usable as it has
become quite slow.

Cheers 
Kedar

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 385011] Plasma crashed

2017-09-25 Thread Kedar
https://bugs.kde.org/show_bug.cgi?id=385011

Kedar  changed:

   What|Removed |Added

 CC||kedar.a...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 384875] New: Plasma Crashed

2017-09-20 Thread Kedar
https://bugs.kde.org/show_bug.cgi?id=384875

Bug ID: 384875
   Summary: Plasma Crashed
   Product: plasmashell
   Version: 5.10.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kedar.a...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.10.0-35-generic x86_64
Distribution: KDE neon User Edition 5.10

-- Information about the crash:
- What I was doing when the application crashed:
I was using Skype, Google Chrome, Kmail, Firefox. My video in Skype froze while
having a conversation. So I disconnected the call and exited skype by right
clicking on the icon in the try. And I got a message Plasma crashed.

I have the updated Skype client. My KDE Neon is a fairly new fresh install on a
Dell Optiplex Desktop. All updates and patches are regularly taken as and when
they arrive.

Regards

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fef4cca88c0 (LWP 1353))]

Thread 18 (Thread 0x7fee490a9700 (LWP 7311)):
#0  0x7fef474f324d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fef3bfd2f61 in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7fef3cd6aa2e in pa_mainloop_prepare () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fef3cd6b4a0 in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fef3cd6b560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fef3cd797a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7fef3c001078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#7  0x7fef46a9c6ba in start_thread (arg=0x7fee490a9700) at
pthread_create.c:333
#8  0x7fef475033dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 17 (Thread 0x7fae337ff700 (LWP 6252)):
#0  0x7fef474f770d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fef42e9438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fef42e9449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fef47e1f94b in QEventDispatcherGlib::processEvents
(this=0x7fae280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fef47dc87ca in QEventLoop::exec (this=this@entry=0x7fae337fece0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fef47bf1cd4 in QThread::exec (this=this@entry=0x200ab60) at
thread/qthread.cpp:515
#6  0x7fef4a2c00c5 in QQmlThreadPrivate::run (this=0x200ab60) at
qml/ftw/qqmlthread.cpp:147
#7  0x7fef47bf6989 in QThreadPrivate::start (arg=0x200ab60) at
thread/qthread_unix.cpp:368
#8  0x7fef46a9c6ba in start_thread (arg=0x7fae337ff700) at
pthread_create.c:333
#9  0x7fef475033dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 16 (Thread 0x7fee49ffb700 (LWP 3947)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fef47bf78eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x8124c50) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x742d650,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7fee6e4ea6df in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fee6e4ee768 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fee6e4e98cd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fee6e4ee7c2 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fee6e4e98cd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fee6e4ec2e0 in ThreadWeaver::Thread::run() () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fef47bf6989 in QThreadPrivate::start (arg=0x7fee44002f90) at
thread/qthread_unix.cpp:368
#10 0x7fef46a9c6ba in start_thread (arg=0x7fee49ffb700) at
pthread_create.c:333
#11 0x7fef475033dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7fee4a7fc700 (LWP 3946)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fef47bf78eb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x8124c50) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x74

[kmail2] [Bug 380152] KMail segfaults consistently when replying to an attached email.

2017-06-07 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=380152

Kedar Apte  changed:

   What|Removed |Added

 CC||plasmagee...@gmail.com

--- Comment #4 from Kedar Apte  ---
I can confirm this happens to me too especially when there are more than one
recipients...either in Cc or To or Bcc. I can send a fresh email to as many,
but I cant respond.
This behaviour is only for certain emails. Not all.

I am using KDE Neon 5.10. This happened to me even when I was on KDE 5.5 and
also on Kubuntu 16.04

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 379911] No mail accounts (IMAP) can be created or configured anymore

2017-06-07 Thread Kedar Apte
https://bugs.kde.org/show_bug.cgi?id=379911

Kedar Apte  changed:

   What|Removed |Added

 CC||plasmagee...@gmail.com

--- Comment #8 from Kedar Apte  ---
Hey - I also came across the same issue. For adding any account, I guess the
users are required to use the account wizard found under Tools menu. From there
on the accounts and all settings w.r.t setting up the account works.

However, if one needs to make any change to the account, one cannot select the
account to be modified and click on 'Modify' in 'Configure Kmail' menu. Dialog
box to tweak the account settings does not appear when once clicks on 'Modify'.
At the same time if you want to add email accounts from the 'Configure Kmail'
menu item, the same cannot be done as it does not provide any option to enter
any server settings.

-- 
You are receiving this mail because:
You are watching all bug changes.