[kmail2] [Bug 390900] Import vcf from email does not work
https://bugs.kde.org/show_bug.cgi?id=390900 --- Comment #10 from Laurent Montel --- (In reply to Helmar Gerloni from comment #9) > (In reply to Laurent Montel from comment #8) > > I can confirm the bug. > > I will work on it now. > Thanks! Interesting detail I just found out: While you are not able to > import the contact using the link "[Add this contact to the address book]" > in the mail it works perfectly using the small link "[vcard]" in the mail > header "From: sen...@example.com [vcard]". yep I know it's a problem with vcard plugin. So [vcard] will work correctly -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 408811] New: Crashes when link is clicked
https://bugs.kde.org/show_bug.cgi?id=408811 Bug ID: 408811 Summary: Crashes when link is clicked Product: akregator Version: 5.11.2 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: dougjsha...@gmail.com Target Milestone: --- Application: akregator (5.11.2) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.15.0-51-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: clicked external link in the news reader window, and Akregator crashed immediately. - Custom settings of the application: None 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 0x7fbe3c398100 (LWP 5614))] Thread 21 (Thread 0x7fbd01659700 (LWP 5724)): #0 0x7fbe2b9ea9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fbd01658908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fbd016588b8, cond=0x7fbd016588e0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fbd016588e0, mutex=0x7fbd016588b8) at pthread_cond_wait.c:655 #3 0x7fbe31ce5a49 in base::ConditionVariable::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fbe31ce6478 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fbe31ce650f in base::WaitableEvent::Wait() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fbe31ca6fc8 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fbe31ca94c7 in base::internal::SchedulerWorker::RunWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fbe31ca9af4 in base::internal::SchedulerWorker::RunSharedWorker() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fbe31ce8561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fbe2b9e46db in start_thread (arg=0x7fbd01659700) at pthread_create.c:463 #11 0x7fbe3813688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fbd01e5a700 (LWP 5721)): #0 0x7fbe380b2b4a in __GI___strerror_r (errnum=errnum@entry=9, buf=buf@entry=0x0, buflen=buflen@entry=0) at _strerror.c:72 #1 0x7fbe380b2a4f in strerror (errnum=9) at strerror.c:31 #2 0x7fbe2400fb31 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #3 0x7fbe2401146c in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7fbe24007114 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7fbe31cebc79 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fbe31c862db in base::RunLoop::Run() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fbe31cb8311 in base::Thread::ThreadMain() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fbe31ce8561 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fbe2b9e46db in start_thread (arg=0x7fbd01e5a700) at pthread_create.c:463 #10 0x7fbe3813688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fbcf1f6b700 (LWP 5664)): #0 0x7fbdf8ce7d9a in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #1 0x7fbdf8ce889f in pa_fdsem_after_poll () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7fbdf8d0035d in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7fbdf9165108 in pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7fbdf91654de in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7fbdf9165560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7fbdf91733c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7fbdf8d10318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #8 0x7fbe2b9e46db in start_thread (arg=0x7fbcf1f6b700) at pthread_create.c:463 #9 0x7fbe3813688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fbd137fe700 (LWP 5641)): #0 0x7fbe2b9ea9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fbd137fd908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mut
[kmail2] [Bug 408798] KMail Fails to Start
https://bugs.kde.org/show_bug.cgi?id=408798 --- Comment #2 from y...@jacky.wtf --- On Sunday, June 16, 2019 12:30:26 PM PDT Wolfgang Bauer wrote: > https://bugs.kde.org/show_bug.cgi?id=408798 > > Wolfgang Bauer changed: > >What|Removed |Added > > Status|REPORTED|RESOLVED > CC||wba...@tmo.at > Resolution|--- |DUPLICATE > > --- Comment #1 from Wolfgang Bauer --- > Fixed in 5.11.1, you can disable the "Share Text" plugin as a workaround. > > Removing the files in .local/share/kmail2/autosave/ should make it start > again. > > *** This bug has been marked as a duplicate of bug 403317 *** Oh thank you so much! Lost so much time trying to figure this out. Is there a newsletter / feed of the changes in KMail so things like this can be surfaced? These being bugs -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408798] KMail Fails to Start
https://bugs.kde.org/show_bug.cgi?id=408798 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED CC||wba...@tmo.at Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- Fixed in 5.11.1, you can disable the "Share Text" plugin as a workaround. Removing the files in .local/share/kmail2/autosave/ should make it start again. *** This bug has been marked as a duplicate of bug 403317 *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 403317] KMAIL2; "Share Text" plugin segfaults
https://bugs.kde.org/show_bug.cgi?id=403317 Wolfgang Bauer changed: What|Removed |Added CC||y...@jacky.wtf --- Comment #22 from Wolfgang Bauer --- *** Bug 408798 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408798] New: KMail Fails to Start
https://bugs.kde.org/show_bug.cgi?id=408798 Bug ID: 408798 Summary: KMail Fails to Start Product: kmail2 Version: 5.10.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: y...@jacky.wtf Target Milestone: --- Application: kmail (5.10.3) Qt Version: 5.12.2 Frameworks Version: 5.58.0 Operating System: Linux 5.0.0-16-generic x86_64 Distribution: Ubuntu 19.04 -- Information about the crash: - What I was doing when the application crashed: This happened a few days ago (actually inspired me to get kdesrc-build runnng though this bug happens in both the source build and my distro's provided packages). I attempt to launch the application from the command line, from KRunner and from the Plasma Application launcher. - Unusual behavior I noticed: No graphical interface was ever presented. The application indicator bounced but that's about it. 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 0x7fee96d85f00 (LWP 24314))] Thread 8 (Thread 0x7fee82532700 (LWP 24853)): #0 0x7feead8192e9 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7feeadb8e954 in QSemaphore::acquire(int) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fee82b6ef6c in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqttexttospeech_flite.so #3 0x7feeadb8c612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feeab007182 in start_thread (arg=) at pthread_create.c:486 #5 0x7feead81fb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7fee837fe700 (LWP 24598)): #0 0x7feead813729 in __GI___poll (fds=0x7fee70004e30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7feeaa6bacb6 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7feeaa6baddc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feeadd95063 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feeadd405bb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7feeadb8b2c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7feeadb8c612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feeab007182 in start_thread (arg=) at pthread_create.c:486 #8 0x7feead81fb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fee83fff700 (LWP 24593)): #0 0x7feead80efb4 in __GI___libc_read (nbytes=16, buf=0x7fee83ffe480, fd=14) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7feead80efb4 in __GI___libc_read (fd=14, buf=0x7fee83ffe480, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7feeaa7014d0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feeaa6ba78f in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7feeaa6bac60 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7feeaa6baddc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7feeadd95063 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feeadd405bb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7feeadb8b2c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7feeadb8c612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7feeab007182 in start_thread (arg=) at pthread_create.c:486 #11 0x7feead81fb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fee8ce69700 (LWP 24584)): #0 0x7feeaa7058e4 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7feeaa6bacab in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7feeaa6baddc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feeadd95063 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feeadd405bb in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7feeadb8b2c6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7feeadb8c612 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feeab007182 in start_thread (arg=) at pthread_create.c:486 #8 0x7feead81fb1f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fee8f42b700 (LWP 24522)): #0 0x7feeab00d3bb in futex_wait_cancelable (private=, expected=0, futex_word=0x55fb5e8cab28) at ../sysdeps/unix/sysv/linux/futex
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 --- Comment #16 from Martin Steigerwald --- Created attachment 120924 --> https://bugs.kde.org/attachment.cgi?id=120924&action=edit akonadiserver.error log with akonadictl --verbose start on second start reusing existing PostgreSQL processes On second start with some of the PostgreSQL processes still running, this happens: Found pg_ctl: "/usr/lib/postgresql/11/bin/pg_ctl" Found initdb: "/usr/lib/postgresql/11/bin/pg_ctl" Found a postmaster.pid pidfile, checking whether the server is still running... PostgreSQL for Akonadi is already running, trying to connect to it. Database "akonadi" opened using driver "QPSQL" DbInitializer::run() checking table "SchemaVersionTable" checking table "ResourceTable" It reuses the PostgreSQL processes that were left over from the last akonadictl stop: % ps aux | grep postgres martin 25164 0.0 0.1 214568 26444 ?S19:59 0:00 /usr/lib/postgresql/11/bin/postgres -D /home/martin/.local/share/akonadi/db_data -k/tmp/akonadi-martin.wTqoXj -h martin 25166 0.0 0.1 214696 19412 ?Ss 19:59 0:00 postgres: checkpointer martin 25167 0.0 0.0 214700 9152 ?Ss 19:59 0:00 postgres: background writer martin 25168 0.0 0.0 214568 9496 ?Ss 19:59 0:00 postgres: walwriter martin 25169 0.0 0.0 214976 6508 ?Ss 19:59 0:00 postgres: autovacuum launcher martin 25170 0.0 0.0 69616 5108 ?Ss 19:59 0:00 postgres: stats collector martin 25171 0.0 0.0 214968 6484 ?Ss 19:59 0:00 postgres: logical replication launcher martin 25507 1.4 0.9 229764 160720 ? Ss 20:04 0:02 postgres: martin akonadi [local] idle martin 25516 0.0 0.0 218628 14992 ?Ss 20:04 0:00 postgres: martin akonadi [local] idle martin 25517 0.0 0.0 218628 15052 ?Ss 20:04 0:00 postgres: martin akonadi [local] idle martin 25567 0.0 0.0 218492 12980 ?Ss 20:04 0:00 postgres: martin akonadi [local] idle [… about 20-30 more of these …] if you compare this with my last comment, you see that the PIDs are exactly the same. However there are some additional processes running now. When I stop Akonadi again the following processes remain: % ps aux | grep postgres martin 25164 0.0 0.1 214568 26444 ?S19:59 0:00 /usr/lib/postgresql/11/bin/postgres -D /home/martin/.local/share/akonadi/db_data -k/tmp/akonadi-martin.wTqoXj -h martin 25166 0.0 0.1 214696 19412 ?Ss 19:59 0:00 postgres: checkpointer martin 25167 0.0 0.0 214700 9152 ?Ss 19:59 0:00 postgres: background writer martin 25168 0.0 0.0 214568 9496 ?Ss 19:59 0:00 postgres: walwriter martin 25169 0.0 0.0 214976 6508 ?Ss 19:59 0:00 postgres: autovacuum launcher martin 25170 0.0 0.0 69616 5108 ?Ss 19:59 0:00 postgres: stats collector martin 25171 0.0 0.0 214968 6484 ?Ss 19:59 0:00 postgres: logical replication launcher martin 25781 0.0 0.0 8236 924 pts/3S+ 20:10 0:00 grep postgres So it appears to me that this could be somewhat an intended feature or option of PostgreSQL: If it does not tear down *all* of the processes it can more quickly be started again. However that is still all just guess work until I take the time to dig deeper in how PostgreSQL handles stopping the database. I'd somehow still expect that it would remove all processes. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 --- Comment #15 from Martin Steigerwald --- Created attachment 120923 --> https://bugs.kde.org/attachment.cgi?id=120923&action=edit akonadiserver.error log with akonadictl --verbose start With KDEPIM/Akonadi 18.08 (I know, still outdated, Debian in deep freeze till likely beginning of July) I can confirm Axel's results. Logfile attached. Some database processes are still running. % ps aux | grep postgres martin 25164 0.0 0.1 214568 26444 ?S19:59 0:00 /usr/lib/postgresql/11/bin/postgres -D /home/martin/.local/share/akonadi/db_data -k/tmp/akonadi-martin.wTqoXj -h martin 25166 0.0 0.0 214568 3928 ?Ss 19:59 0:00 postgres: checkpointer martin 25167 0.0 0.0 214568 5600 ?Ss 19:59 0:00 postgres: background writer martin 25168 0.0 0.0 214568 9496 ?Ss 19:59 0:00 postgres: walwriter martin 25169 0.0 0.0 214976 6508 ?Ss 19:59 0:00 postgres: autovacuum launcher martin 25170 0.0 0.0 69616 5108 ?Ss 19:59 0:00 postgres: stats collector martin 25171 0.0 0.0 214968 6484 ?Ss 19:59 0:00 postgres: logical replication launcher martin 25400 0.0 0.0 8236 928 pts/3S+ 20:01 0:00 grep postgres However if I do not stop the database processes manually it reuses the existing PostgreSQL processes as I show in my next attachment. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 --- Comment #14 from Axel Braun --- Created attachment 120920 --> https://bugs.kde.org/attachment.cgi?id=120920&action=edit error log After the akonadiserver claimed 'Database is no longer running': docb@T520:~> ps ax | grep postgres 7817 ?S 0:00 /usr/lib/postgresql11/bin/postgres -D /home/docb/.local/share/akonadi/db_data -k/tmp/akonadi-docb.N9ni6K -h 7819 ?Ss 0:00 postgres: logger 7821 ?Ss 0:00 postgres: checkpointer 7822 ?Ss 0:00 postgres: background writer 7823 ?Ss 0:00 postgres: walwriter 7824 ?Ss 0:00 postgres: autovacuum launcher 7825 ?Ss 0:00 postgres: stats collector 7826 ?Ss 0:00 postgres: logical replication launcher -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 406047] '\' character at end of displayed address
https://bugs.kde.org/show_bug.cgi?id=406047 aux...@gmail.com changed: What|Removed |Added Version|unspecified |5.11.2 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 406047] '\' character at end of displayed address
https://bugs.kde.org/show_bug.cgi?id=406047 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding for column "address" (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 aux...@gmail.com changed: What|Removed |Added Version|5.5.2 |5.11.2 -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 383934] DAV-Groupware resource for OwnCloud uses incorrect encoding for column "address" (not UTF-8)
https://bugs.kde.org/show_bug.cgi?id=383934 aux...@gmail.com changed: What|Removed |Added CC||aux...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386173] akonadictl stop does not shut down database
https://bugs.kde.org/show_bug.cgi?id=386173 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #13 from Daniel Vrátil --- Can you get full debug logs of the Akonadi Server, please? You can do so by starting Akonadi manually from the commandline: akonadictl --verbose start ... (wait for a bit) akonadictl stop You can retrieve the full logfile from ~/.local/share/akonadi/akonadiserver.error -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408789] New: Click on a "mailto" on a web page
https://bugs.kde.org/show_bug.cgi?id=408789 Bug ID: 408789 Summary: Click on a "mailto" on a web page Product: kmail2 Version: 5.11.2 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mvasquez.carm...@gmail.com Target Milestone: --- Application: kmail (5.11.2) (Compiled from sources) Qt Version: 5.12.3 Frameworks Version: 5.59.0 Operating System: Linux 4.18.0-21-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I clicked on a "mailto" link on a web page and the system informed me that KMail had to close. -- 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 0x7fe5ad74abc0 (LWP 15162))] Thread 21 (Thread 0x7fe4ef7fe700 (LWP 15214)): #0 0x7fe59ff009f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fe4ef7fd908) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fe59ff009f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7fe4ef7fd8b8, cond=0x7fe4ef7fd8e0) at pthread_cond_wait.c:502 #2 0x7fe59ff009f3 in __pthread_cond_wait (cond=0x7fe4ef7fd8e0, mutex=0x7fe4ef7fd8b8) at pthread_cond_wait.c:655 #3 0x7fe594fdba49 in base::ConditionVariable::Wait() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fe594fdc478 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fe594fdc50f in base::WaitableEvent::Wait() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fe594f9cfc8 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fe594f9f7f6 in base::internal::SchedulerWorker::RunWorker() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fe594f9fb34 in base::internal::SchedulerWorker::RunDedicatedWorker() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fe594fde561 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fe59fefa6db in start_thread (arg=0x7fe4ef7fe700) at pthread_create.c:463 #11 0x7fe5aa78588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fe4e700 (LWP 15213)): #0 0x7fe5aa7946d9 in __lll_unlock_wake_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:341 #1 0x7fe5aa79650c in _IO_acquire_lock_clear_flags2_fct (p=) at ../libio/libioP.h:807 #2 0x7fe5aa79650c in ___fprintf_chk (fp=0x7fe5aaa50680 <_IO_2_1_stderr_>, flag=1, format=) at fprintf_chk.c:30 #3 0x7fe58a6879ad in event_logv_ () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #4 0x7fe58a687b44 in event_warn () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #5 0x7fe58a68946c in () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #6 0x7fe58a67f114 in event_base_loop () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #7 0x7fe594fe1c79 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fe594f7c2db in base::RunLoop::Run() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fe594fae311 in base::Thread::ThreadMain() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fe594fde561 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fe59fefa6db in start_thread (arg=0x7fe4e700) at pthread_create.c:463 #12 0x7fe5aa78588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fe52cff9700 (LWP 15212)): #0 0x7fe59ff00ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fe52cff8710, expected=0, futex_word=0x7fe52cff88f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fe59ff00ed9 in __pthread_cond_wait_common (abstime=0x7fe52cff87b0, mutex=0x7fe52cff88a8, cond=0x7fe52cff88d0) at pthread_cond_wait.c:533 #2 0x7fe59ff00ed9 in __pthread_cond_timedwait (cond=0x7fe52cff88d0, mutex=0x7fe52cff88a8, abstime=0x7fe52cff87b0) at pthread_cond_wait.c:667 #3 0x7fe594fdbb17 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fe594fdc46a in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fe594fdc552 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fe594f9cfb1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::
[kmail2] [Bug 393421] No ability to hide the HTML Message Status Bar
https://bugs.kde.org/show_bug.cgi?id=393421 Christophe Giboudeaux changed: What|Removed |Added CC||ssliac...@gmail.com --- Comment #62 from Christophe Giboudeaux --- *** Bug 408727 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 408727] No option to remove ugly useless HTML warning bar
https://bugs.kde.org/show_bug.cgi?id=408727 Christophe Giboudeaux changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christophe Giboudeaux --- *** This bug has been marked as a duplicate of bug 393421 *** -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 341046] Emoticons not shown in HTML view
https://bugs.kde.org/show_bug.cgi?id=341046 fbampaloukas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||marinus.savorit...@tuta.io Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from fbampaloukas --- Closing as Worksforme due to inactivity for more than 15 days as per: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Policies Fanis -- You are receiving this mail because: You are the assignee for the bug.
