[kaddressbook] [Bug 396685] New: Edit Location not possible with dark theme
https://bugs.kde.org/show_bug.cgi?id=396685 Bug ID: 396685 Summary: Edit Location not possible with dark theme Product: kaddressbook Version: 5.8.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: robby.engelm...@igfs-ev.de CC: to...@kde.org Target Milestone: --- It is currently not possible to edit edit an existing location because text and symbols seem to white on white background. Reproduce: -switch to breeze dark theme -open a contact with an existing address -switch to the Location tab -you will recognize the issue -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 396685] Edit Location not possible with dark theme
https://bugs.kde.org/show_bug.cgi?id=396685 Robby Engelmann changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #1 from Robby Engelmann --- Created attachment 114023 --> https://bugs.kde.org/attachment.cgi?id=114023=edit the problem -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396686] New: kmail crashes on startup
https://bugs.kde.org/show_bug.cgi?id=396686 Bug ID: 396686 Summary: kmail crashes on startup Product: kmail2 Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: b...@valdyas.org Target Milestone: --- Application: kmail (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-23-generic x86_64 Distribution: KDE neon Developer Edition -- Information about the crash: Simply starting kmail will crash. This happened after updating Neon 18.04 this morning, after a reboot. The crash can be reproduced every time. -- 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 0x7f02cbee0880 (LWP 8056))] Thread 3 (Thread 0x7f0292199700 (LWP 8058)): #0 0x7f02c8f8bbf9 in __GI___poll (fds=0x7f028c004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f02bc98f439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f02bc98f54c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f02c98cba9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f02c986fdea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f02c969ab8a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f02c7ec9e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f02c96a5aab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f02be85b6db in start_thread (arg=0x7f0292199700) at pthread_create.c:463 #9 0x7f02c8f9888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f029ba7b700 (LWP 8057)): #0 0x7f02c8f8bbf9 in __GI___poll (fds=0x7f029ba7ac28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f02bbdbb747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f02bbdbd36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f029db90129 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f02c96a5aab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f02be85b6db in start_thread (arg=0x7f029ba7b700) at pthread_create.c:463 #6 0x7f02c8f9888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f02cbee0880 (LWP 8056)): [KCrash Handler] #6 0x0001 in ?? () #7 0x7f02cbb506fd in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #8 0x559e045f6695 in main (argc=, argv=) at ./src/main.cpp:128 Possible duplicates by query: bug 353876. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396694] New: Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 Bug ID: 396694 Summary: Kontact crashes right after start Product: kontact Version: 5.8.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: andrasszerencs...@gmail.com Target Milestone: --- Application: kontact (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: On KDE Neon, Plasma desktop was upgraded from 5.12 to 5.13 and I restarted the system. Simple tried to start Kontact application and it's every time 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 0x7f310b224940 (LWP 6854))] Thread 2 (Thread 0x7f30dcc4b700 (LWP 6857)): #0 0x7f3107c0474d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f310196738c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f30d8003020, timeout=, context=0x7f30d8000990) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f30d8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7f310196749c in g_main_context_iteration (context=0x7f30d8000990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7f31087320bb in QEventDispatcherGlib::processEvents (this=0x7f30d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f31086d95ba in QEventLoop::exec (this=this@entry=0x7f30dcc4ac40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f310850e5e4 in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7f3106e77f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f3108519727 in QThreadPrivate::start (arg=0x7f31070f0d60) at thread/qthread_unix.cpp:367 #9 0x7f310395e6ba in start_thread (arg=0x7f30dcc4b700) at pthread_create.c:333 #10 0x7f3107c1041d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f310b224940 (LWP 6854)): [KCrash Handler] #6 0x7f310acb2c20 in KontactInterface::PimUniqueApplication::staticMetaObject () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #7 0x7f310aaadd3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x0040437b in main (argc=1, argv=0x7ffe00e3f848) at /workspace/build/src/main.cpp:216 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 yc-153...@hs-weingarten.de changed: What|Removed |Added CC||yc-153...@hs-weingarten.de -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 --- Comment #1 from yc-153...@hs-weingarten.de --- Created attachment 114030 --> https://bugs.kde.org/attachment.cgi?id=114030=edit New crash information added by DrKonqi kontact (5.8.2) using Qt 5.11.1 - What I was doing when the application crashed: When I try to start Kontact it crashes immediatly. No startscreen or something else is seen. - Custom settings of the application: the application starts automatically when I boot KDE Neon -- Backtrace (Reduced): #6 0x7f71acb5ec20 in KontactInterface::PimUniqueApplication::staticMetaObject () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #7 0x7f71ac959d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x0040437b in main (argc=1, argv=0x7ffc6dd0dbf8) at /workspace/build/src/main.cpp:216 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 396700] New: Korganizer crashes on startup after installing over 400 updates to KDE Neon.
https://bugs.kde.org/show_bug.cgi?id=396700 Bug ID: 396700 Summary: Korganizer crashes on startup after installing over 400 updates to KDE Neon. Product: korganizer Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jv3...@comcast.net Target Milestone: --- Application: korganizer (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: Trying to start korganizer. Korganizer worked fine until I installed over 400 updates for KDE Neon on 7/20/18. Now it crashes everytime it is started. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8dc6f3d940 (LWP 2557))] Thread 2 (Thread 0x7f8d9f95a700 (LWP 2559)): #0 0x7f8dc278674d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8db872138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8db872149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8dc32b40bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8dc325b5ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8dc30905e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8dc1c4af35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f8dc309b727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8dba42d6ba in start_thread (arg=0x7f8d9f95a700) at pthread_create.c:333 #9 0x7f8dc279241d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f8dc6f3d940 (LWP 2557)): [KCrash Handler] #6 0xfff0 in ?? () #7 0x7f8dc6c0fd3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x004084ce in main (argc=1, argv=0x7ffecac75ec8) at /workspace/build/src/main.cpp:55 Possible duplicates by query: bug 396694, bug 389840, bug 389365, bug 386013, bug 385374. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 tomas nackaerts changed: What|Removed |Added CC||tomas.nackae...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 396698] New: Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Bug ID: 396698 Summary: Akregator crashes on start after plasma upgrade Product: akregator Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gianni_2...@hotmail.it Target Milestone: --- Application: akregator (5.8.2) Qt Version: 5.11.1 Frameworks Version: 5.48.0 Operating System: Linux 4.15.15-041515-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: Akregator crashes immediately after starting it. This started happening after upgrading the system: KDE Plasma: 5.13.2 to 5.13.3 KDE Frameworks: 5.47 to 5.48.0 Qt: 5.11.0 to 5.11.1 Kernel used: 4.15.15-041515-generic The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4c46f45980 (LWP 30861))] Thread 2 (Thread 0x7f4c18907700 (LWP 30863)): #0 0x7f4c3b378c78 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4c3b379330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4c3b37949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4c436ea0bb in QEventDispatcherGlib::processEvents (this=0x7f4c0c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4c436915ba in QEventLoop::exec (this=this@entry=0x7f4c18906c00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7f4c434c65e4 in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7f4c453b4f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f4c434d1727 in QThreadPrivate::start (arg=0x7f4c4562dd60) at thread/qthread_unix.cpp:367 #8 0x7f4c3d2d26ba in start_thread (arg=0x7f4c18907700) at pthread_create.c:333 #9 0x7f4c42dd441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f4c46f45980 (LWP 30861)): [KCrash Handler] #6 0x7f4c43415438 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f4c46a49d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7fff28440798) at /workspace/build/src/main.cpp:106 The reporter indicates this bug may be a duplicate of or related to bug 392544. Possible duplicates by query: bug 396694, bug 394490, bug 392544, bug 389840, bug 386013. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 --- Comment #2 from Øystein Steffensen-Alværvik --- Sorry, *here's* the backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f81089bd980 (LWP 13572))] Thread 2 (Thread 0x7f80d4f78700 (LWP 13574)): #0 0x7f810484627d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f80fce416f0 in read (__nbytes=16, __buf=0x7f80d4f779f0, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0xd1f0b0) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gwakeup.c:210 #3 0x7f80fcdfde74 in g_main_context_check (context=context@entry=0x7f80d990, max_priority=2147483647, fds=fds@entry=0x7f80d0003020, n_fds=n_fds@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3632 #4 0x7f80fcdfe330 in g_main_context_iterate (context=context@entry=0x7f80d990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837 #5 0x7f80fcdfe49c in g_main_context_iteration (context=0x7f80d990, may_block=may_block@entry=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901 #6 0x7f81051620bb in QEventDispatcherGlib::processEvents (this=0x7f80d8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f81051095ba in QEventLoop::exec (this=this@entry=0x7f80d4f77c00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #8 0x7f8104f3e5e4 in QThread::exec (this=this@entry=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #9 0x7f8106e2cf35 in QDBusConnectionManager::run (this=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #10 0x7f8104f49727 in QThreadPrivate::start (arg=0x7f81070a5d60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #11 0x7f80fed566ba in start_thread (arg=0x7f80d4f78700) at pthread_create.c:333 #12 0x7f810485641d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f81089bd980 (LWP 13572)): [KCrash Handler] #6 0x7f8104e8d558 in vtable for __cxxabiv1::__si_class_type_info () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f81084c1d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7ffd3e22a518) at /workspace/build/src/main.cpp:106 -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 396714] New: Calendar doesn't show Facebook events
https://bugs.kde.org/show_bug.cgi?id=396714 Bug ID: 396714 Summary: Calendar doesn't show Facebook events Product: korganizer Version: 5.8.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: aalexand...@gmail.com Target Milestone: --- I connected a Facebook account as calendar source in KOrganizer. It shows 5 folders like "Events I'm attending" etc, but shows no actual event in the calendar. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396686] kmail crashes on startup
https://bugs.kde.org/show_bug.cgi?id=396686 Johannes Mueller changed: What|Removed |Added CC||git...@johannes-mueller.org --- Comment #1 from Johannes Mueller --- Same problem with kmail, korganzier and organizer after `apt full-upgrade` today (2018/07/20). -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 --- Comment #1 from Øystein Steffensen-Alværvik --- Created attachment 114036 --> https://bugs.kde.org/attachment.cgi?id=114036=edit New crash information added by DrKonqi akregator (5.8.2) using Qt 5.11.1 Here's a backtrace with proper debug symbols installed. Also reproducible every time. -- Backtrace (Reduced): #7 0x7f9531368d3d in KontactInterface::PimUniqueApplication::start (arguments=..., unique=unique@entry=true) at /workspace/build/src/pimuniqueapplication.cpp:135 #8 0x00408327 in main (argc=1, argv=0x7ffe8df8d8a8) at /workspace/build/src/main.cpp:106 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Øystein Steffensen-Alværvik changed: What|Removed |Added CC||yst...@posteo.net -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Øystein Steffensen-Alværvik changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 321669] multipart mails incompletely displayed
https://bugs.kde.org/show_bug.cgi?id=321669 Denis Kurz changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from Denis Kurz --- Rawk, which version did you experience this with? Iirc, we closed all bugs only reported against version 4.14 or older a while ago. Bugs in those versions will definitely not be fixed. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 327282] Google calendar/ical event gets doubled, i.e. added twice - event visible with no calendar displayed
https://bugs.kde.org/show_bug.cgi?id=327282 Denis Kurz changed: What|Removed |Added Version|5.3.0 |5.7.3 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 Dmitry Ivanov changed: What|Removed |Added CC||dm.vl.iva...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396686] kmail crashes on startup
https://bugs.kde.org/show_bug.cgi?id=396686 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 396694 *** -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 396698] Akregator crashes on start after plasma upgrade
https://bugs.kde.org/show_bug.cgi?id=396698 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 396694 *** -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 365944] SIGSEGV in Akonadi::Tag::isValid() crashing KAddressbook on startup with configured CardDav, or KOrganizer on event edition (or creation) or access to settings
https://bugs.kde.org/show_bug.cgi?id=365944 --- Comment #29 from Filipus Klutiero --- I must say I've had several issues with KOrganizer even with the packages I rebuilt. A few crashes and an empty calendar once, as if there's still something which KOrganizer doesn't quite like. But it's not blocking me. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 arpj.reb...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 CC||arpj.reb...@gmail.com Status|UNCONFIRMED |CONFIRMED --- Comment #2 from arpj.reb...@gmail.com --- Confirmed this bug on a fresh install of KDE Neon. The bug appears after upgrade through apt-get alone, could not locate the precise package that provokes the problem. -- You are receiving this mail because: You are the assignee for the bug.
[neon] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 Christoph Feck changed: What|Removed |Added CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Assignee|kdepim-bugs@kde.org |neon-b...@kde.org Component|general |general Product|kontact |neon Version|5.8.2 |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[kleopatra] [Bug 360364] Kleopatra displays an error report received from gpg in gibberish after clicking "refresh OpenPGP certificates". .
https://bugs.kde.org/show_bug.cgi?id=360364 --- Comment #7 from lockyw...@gmail.com --- I don't have Windows at the moment to test the issue, but thanks for your work! Windows character encoding system is unbelievably messy. -- You are receiving this mail because: You are on the CC list for the bug.
[kmail2] [Bug 396327] column settings not remembered in folder pane
https://bugs.kde.org/show_bug.cgi?id=396327 Sudhir Khanger changed: What|Removed |Added CC||sud...@sudhirkhanger.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Sudhir Khanger --- I am also experiencing this issue. The columns are restored to contain name, unread, total, and size after you restart the Kmail. Irrespective of what you set it to the default column list are restored. Plasma 5.12.6 Frameworks 5.47.0 Linux 4.17.7-200.fc28.x86_64 Fedora 28 Kmail 17.12.3-1.fc28 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396716] Empty and non-removable columns are added in KMail UI
https://bugs.kde.org/show_bug.cgi?id=396716 --- Comment #1 from Sudhir Khanger --- Created attachment 114039 --> https://bugs.kde.org/attachment.cgi?id=114039=edit account setting -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 396716] New: Empty and non-removable columns are added in KMail UI
https://bugs.kde.org/show_bug.cgi?id=396716 Bug ID: 396716 Summary: Empty and non-removable columns are added in KMail UI Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: sud...@sudhirkhanger.com Target Milestone: --- Created attachment 114038 --> https://bugs.kde.org/attachment.cgi?id=114038=edit folder list KMail is adding empty columns in several places like folder list, account tab in the settings. The columns can't be removed. Please see the screenshot linked. Plasma 5.12.6 Frameworks 5.47.0 Linux 4.17.7-200.fc28.x86_64 Fedora 28 Kmail 17.12.3-1.fc28 -- You are receiving this mail because: You are the assignee for the bug.
