[systemsettings] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #3 from Paśnikowski Marek --- (In reply to Nate Graham from comment #2) > I doubt this is related to Kirigami. It's more likely to be an issue with > the way the distro's fontconfig interacts with the settings in the Fonts > KCM. Moving there. To test the interaction, I suggest to implement an option which clears the current KCM font configuration and keeps the options undeclared, which would let the inherited system configuration do its job. This would show in which direction the bug is hidden. If the issue persists, it would indicate a problem with Fontconfig parsing or rendering by a library or a framework. If the issue disappears, it would indicate an actual KCM interaction problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 431649] Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 --- Comment #1 from Paśnikowski Marek --- I started to doubt if this bug is actually in Kirigami. Today I installed Libreoffice-QT and it also has this problem, but only in the menus and tooltips. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 431649] New: Most KDE Applications Do Not Respect Fontconfig
https://bugs.kde.org/show_bug.cgi?id=431649 Bug ID: 431649 Summary: Most KDE Applications Do Not Respect Fontconfig Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: m...@marekpasnikowski.name Target Milestone: Not decided Created attachment 134907 --> https://bugs.kde.org/attachment.cgi?id=134907=edit Presentation of Fontconfig Resistance I have seen this problem for a couple of version now. Regardless of distribution or configuration, many of the KDE applications enforce their own fontconfig. In my previous, already discarded installation, even the system wide Fontconfig was ignored. The attached screenshot shows it all. The AA is in the disabled position, my GTK based browser, KWin and the Plasma Shell are properly aliased, but the Settings Manager is still smoothed. My desire is to have no font antialiasing, because my eyes can't focus properly on the blurry curves. The reproduction is as easy as unchecking the antialiasing button and applying the change. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 268341] Complete Konqueror crash on phoronix.com
https://bugs.kde.org/show_bug.cgi?id=268341 --- Comment #29 from Paśnikowski Marek --- It's been months since I last used KDE and even longer since I last used konqueror. I am not able to test. > 14 grudnia 2020 02:38 Justin Zobel napisał(a): > > > https://bugs.kde.org/show_bug.cgi?id=268341 > > Justin Zobel changed: > >What|Removed |Added > > CC||justin.zo...@gmail.com > Resolution|--- |WAITINGFORINFO > Status|CONFIRMED |NEEDSINFO > > --- Comment #28 from Justin Zobel --- > Thank you for the crash reports. > > 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 on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 --- Comment #8 from Paśnikowski Marek --- Yes. I forgot I had an OwnCloud server. This says something. Email z Środa, 29 stycznia 2020 od bugzilla_nore...@kde.org: > https://bugs.kde.org/show_bug.cgi?id=330472 > > --- Comment #7 from y...@jacky.wtf --- > On Wednesday, January 29, 2020 7:43:17 AM PST bugzilla_nore...@kde.org wrote: > > https://bugs.kde.org/show_bug.cgi?id=330472 > > > > kde.sebac...@simplelogin.co changed: > > > >What|Removed |Added > > > > CC||kde.sebac...@simplelogin.co > > > > --- Comment #6 from kde.sebac...@simplelogin.co --- > > any news about this? > > I think it's dead, tbh. The project and this ticket. > > > Bet, > *Jacky Alcine* > > -- > 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.
[Akonadi] [Bug 413708] New: Akonadi Crash During Deduplication
https://bugs.kde.org/show_bug.cgi?id=413708 Bug ID: 413708 Summary: Akonadi Crash During Deduplication Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: akonadiserver (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I am removing duplicates in my e-mail archives and this particular folder (one of the big ones) causes Akonadi to crash every time. It seems to do so on the "deleting" phase, according to the status bar. The crash can be reproduced every time. -- Backtrace (Reduced): #7 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #8 0x7f427255655d in __GI_abort () at abort.c:79 [...] #10 0x7f42725b78fc in malloc_printerr (str=str@entry=0x7f42726bd0f1 "free(): invalid pointer") at malloc.c:5332 #11 0x7f42725b92dc in _int_free (av=, p=, have_lock=0) at malloc.c:4173 #12 0x7f4272a4cafb in QTypedArrayData::deallocate (data=) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:236 Possible duplicates by query: bug 412300, bug 412218, bug 411993, bug 411687, bug 411347. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413706] Akonadi Crash During Removal of Duplicates in a Folder
https://bugs.kde.org/show_bug.cgi?id=413706 Paśnikowski Marek changed: What|Removed |Added CC||m...@marekpasnikowski.name -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 413706] New: Akonadi Crash During Removal of Duplicates in a Folder
https://bugs.kde.org/show_bug.cgi?id=413706 Bug ID: 413706 Summary: Akonadi Crash During Removal of Duplicates in a Folder Product: Akonadi Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: akonadiserver (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I am removing duplicates in my e-mail archives and this particular folder (one of the big ones) causes Akonadi to crash every time. It seems to do so on the "deleting" phase, according to the status bar. The crash can be reproduced every time. -- Backtrace (Reduced): #7 0x7fcab32ccabe in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x6e0061006a0024) at /usr/include/c++/9/bits/atomic_base.h:413 #8 QAtomicOps::load (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227 #9 QBasicAtomicInteger::load (this=0x6e0061006a0024) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103 [...] #11 QString::operator= (this=this@entry=0x7fca4406d828, other=...) at tools/qstring.cpp:2434 #12 0x558bfe64af01 in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x558bfee3a6c0, request=0x7fca4406d810, errorMsg=...) at /usr/src/debug/akonadi-server-19.08.2-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:224 Possible duplicates by query: bug 413301, bug 411886, bug 410782, bug 410345, bug 410267. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 413355] New: Random Crash of Kontact
https://bugs.kde.org/show_bug.cgi?id=413355 Bug ID: 413355 Summary: Random Crash of Kontact Product: kontact Version: 5.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: kontact (5.12.2) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I pressed the button to delete a journal entry. After restarting Kontact the same action resulted in no crash. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fa47cf5af80 (LWP 3162))] Thread 30 (Thread 0x7fa3e7853700 (LWP 7048)): #0 __GI___libc_read (nbytes=10, buf=0x7fa3e785295e, fd=112) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=fd@entry=112, buf=buf@entry=0x7fa3e785295e, nbytes=nbytes@entry=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fa4700f60f1 in read (__nbytes=10, __buf=0x7fa3e785295e, __fd=112) at /usr/include/bits/unistd.h:44 #3 pa_read (fd=112, buf=buf@entry=0x7fa3e785295e, count=count@entry=10, type=type@entry=0x55d721acc458) at pulsecore/core-util.c:422 #4 0x7fa471c4aa0e in clear_wakeup (m=) at pulse/mainloop.c:782 #5 pa_mainloop_prepare (m=m@entry=0x55d721acc380, timeout=-1) at pulse/mainloop.c:789 #6 0x7fa471c4b4b0 in pa_mainloop_iterate (m=0x55d721acc380, block=, retval=0x0) at pulse/mainloop.c:923 #7 0x7fa471c4b570 in pa_mainloop_run (m=0x55d721acc380, retval=retval@entry=0x0) at pulse/mainloop.c:945 #8 0x7fa471c59439 in thread (userdata=0x55d721a1f6f0) at pulse/thread-mainloop.c:101 #9 0x7fa470123c78 in internal_thread_func (userdata=0x55d720c38860) at pulsecore/thread-posix.c:81 #10 0x7fa47c79cf2a in start_thread (arg=) at pthread_create.c:479 #11 0x7fa47d8034af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7fa3454d2700 (LWP 7047)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fa3454d18e0, clockid=, expected=0, futex_word=0x7fa3454d1a08) at ../sysdeps/unix/sysv/linux/futex-internal.h:208 #1 __pthread_cond_wait_common (abstime=0x7fa3454d18e0, clockid=, mutex=0x7fa3454d19b8, cond=0x7fa3454d19e0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7fa3454d19e0, mutex=0x7fa3454d19b8, abstime=0x7fa3454d18e0) at pthread_cond_wait.c:656 #3 0x7fa475c4c486 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7fa475c4ce53 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230 #5 0x7fa475c4cfd1 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162 #6 0x7fa475c05141 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37 #7 0x7fa475c07fdd in base::internal::SchedulerWorker::RunWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303 #8 0x7fa475c086d4 in base::internal::SchedulerWorker::RunPooledWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229 #9 0x7fa475c4f2c5 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7fa47c79cf2a in start_thread (arg=) at pthread_create.c:479 #11 0x7fa47d8034af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fa344cd1700 (LWP 6715)): #0 0x7fa47d7f8bdf in __GI___poll (fds=0x7fa3f8002fe0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa47bd3e2ae in g_main_context_poll (priority=, n_fds=1, fds=0x7fa3f8002fe0, timeout=, context=0x7fa3f8000bf0) at ../glib/gmain.c:4216 #2 g_main_context_iterate (context=context@entry=0x7fa3f8000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:3912 #3 0x7fa47bd3e3cf in g_main_context_iteration (context=0x7fa3f8000bf0, may_block=may_block@entry=1) at ../glib/gmain.c:3978 #4 0x7fa47ddbf99b in QEventDispatcherGlib::processEvents (this=0x7fa3f8002000, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fa47dd680db in QEventLoop::exec (this=this@entry=0x7fa344cd0b20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fa47dba0021 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fa47dba11a2 in
[kontact] [Bug 412439] New: Kontact Crash When Moving Moving Email Folders
https://bugs.kde.org/show_bug.cgi?id=412439 Bug ID: 412439 Summary: Kontact Crash When Moving Moving Email Folders Product: kontact Version: 5.12.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@marekpasnikowski.name Target Milestone: --- Application: kontact (5.12.1) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.2.14-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Moving folders in my email structure. Kontact has a tendency to crash after some move operations. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fe486fd0a80 (LWP 2818))] Thread 32 (Thread 0x7fe41a7fc700 (LWP 3479)): #0 futex_reltimed_wait_cancelable (private=0, reltime=0x7fe41a7fb840, expected=0, futex_word=0x7fe41a7fba08) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fe41a7fb8e0, mutex=0x7fe41a7fb9b8, cond=0x7fe41a7fb9e0) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fe41a7fb9e0, mutex=0x7fe41a7fb9b8, abstime=0x7fe41a7fb8e0) at pthread_cond_wait.c:667 #3 0x7fe48002b486 in base::ConditionVariable::TimedWait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:127 #4 0x7fe48002be53 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:230 #5 0x7fe48002bfd1 in base::WaitableEvent::TimedWait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:162 #6 0x7fe47ffe4141 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:37 #7 0x7fe47ffe732b in base::internal::SchedulerWorker::RunWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:331 #8 0x7fe47ffe76d4 in base::internal::SchedulerWorker::RunPooledWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:229 #9 0x7fe48002e2c5 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7fe486a43faa in start_thread (arg=) at pthread_create.c:486 #11 0x7fe48903873f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fe34fd9a700 (LWP 3361)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x7fe34fd99a18) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fe34fd999c8, cond=0x7fe34fd999f0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fe34fd999f0, mutex=0x7fe34fd999c8) at pthread_cond_wait.c:655 #3 0x7fe48002b38c in base::ConditionVariable::Wait () at ./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75 #4 0x7fe48002be60 in base::WaitableEvent::TimedWaitUntil () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:232 #5 0x7fe48002bf8f in base::WaitableEvent::Wait () at ./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155 #6 0x7fe47ffe4116 in base::internal::SchedulerWorker::Delegate::WaitForWork () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:35 #7 0x7fe47ffe6fdd in base::internal::SchedulerWorker::RunWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:303 #8 0x7fe47ffe7714 in base::internal::SchedulerWorker::RunSharedWorker () at ./../../3rdparty/chromium/base/task/task_scheduler/scheduler_worker.cc:241 #9 0x7fe48002e2c5 in ThreadFunc () at ./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81 #10 0x7fe486a43faa in start_thread (arg=) at pthread_create.c:486 #11 0x7fe48903873f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7fe350921700 (LWP 3144)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x56457878c2c8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56457878c278, cond=0x56457878c2a0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56457878c2a0, mutex=0x56457878c278) at pthread_cond_wait.c:655 #3 0x7fe46f36bb8b in cnd_wait (mtx=0x56457878c278, cond=0x56457878c2a0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=) at ../src/util/u_queue.c:272 #5 0x7fe46f36ba37 in impl_thrd_routine.lto_priv.4.lto_priv () at ../src/util/u_cpu_detect.c:508 #6 0x7fe486a43faa in start_thread (arg=) at
