search for: libqt5cor

Displaying 11 results from an estimated 11 matches for "libqt5cor".

Did you mean: libqt5core
2016 Nov 17
2
[Bug 98763] New: Lots of crashes of kontact /kmail5
...t /usr/lib64/libglib-2.0.so.0 #1 0x00007f2a3fc16230 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007f2a3fc1642c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007f2a4543232b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007f2a453dffdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007f2a4521af1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007f2a4521f9e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x00007f2a40853734 in start_threa...
2017 Jan 05
1
[Bug 99282] New: KDE kontact crashes always
...2.0.so.0 #2 0x00007f216c2491c0 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x00007f216c24926c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x00007f2179c7e73b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #5 0x00007f2179c2f73a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #6 0x00007f2179a8c5f3 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x00007f2179a909da in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x00007f217...
2018 May 15
2
[Bug 106530] New: [Wayland+Nouveau] KDE Desktop crashed after login.
...#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fdff00bc9b0, cond=0x7fdff00bc9d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fdff00bc9d8, mutex=0x7fdff00bc9b0) at pthread_cond_wait.c:655 #3 0x00007fe0c585e86b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #4 0x00007fe0c961b558 in QSGRenderThread::processEventsAndWaitForMore() () from /usr/lib64/libQt5Quick.so.5 #5 0x00007fe0c961b93a in QSGRenderThread::run() () from /usr/lib64/libQt5Quick.so.5 #6 0x00007fe0c585daf8 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x000...
2018 Jul 12
4
[Bug 107210] New: Segment Fault while opening thunderbitf windows
...rary "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fac70d2de80 (LWP 2674))] Thread 6 (Thread 0x7fac4f5ef700 (LWP 3324)): #0 0x00007fac706afdd6 in ppoll () at /usr/lib/libc.so.6 #1 0x00007fac6da4ccbb in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x00007fac6da4e1ab in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #3 0x00007fac6d9fc6fc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5 #4 0x00007fac6d845849 in QThread::e...
2017 Aug 21
20
[Bug 102349] New: nv4x crashing with plasmashell - gdb log included
...0x00007ffff5de49b7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x00007ffff5de627c in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007ffff5de63fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007ffff2e0fda8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007ffff1ce3494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x00007ffff2728aff in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7fffd10f4700 (LWP 5176)): #0 0x00007ffff1ce915f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/lib...
2020 May 07
2
libQt5Core.so ver 5.12
Hello, For the last few days, 'dnf upgrade' on my Centos 8 installation has been showing problems saying that it cannot install the best update candidates for packages (kf5-*) because nothing provides libQtCore.so.5(Qt_5.12). My system shows that it presently has libQtCore.so.5(Qt_5.11). I've been keeping the system up to date using the --nobest option in dnf. I could download
2020 May 07
1
libQt5Core.so ver 5.12
Hello, For the last few days, 'dnf upgrade' on my Centos 8 installation has been showing problems saying that it cannot install the best update candidates for packages (kf5-*) because nothing provides libQtCore.so.5(Qt_5.12). My system shows that it presently has libQtCore.so.5(Qt_5.11). I've been keeping the system up to date using the --nobest option in dnf. I could download
2016 Oct 04
28
[Bug 98039] New: KMail crash on starting (nouveau-related)
https://bugs.freedesktop.org/show_bug.cgi?id=98039 Bug ID: 98039 Summary: KMail crash on starting (nouveau-related) Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/DRI/nouveau Assignee:
2018 Jan 06
2
LLVM EH tables much larger than GCC's
...ces between Clang and GCC: 1. *ULEB128 encoding.* In the call site table, GCC encodes offsets using a ULEB128 variable-length encoding, whereas LLVM uses fixed-size 32-bit values (udata4). Switching to ULEB128 is a large size improvement. For instance, I'm currently playing with Qt5, and the libQt5Core.so binary is about 4MB with a 215KB .ARM.extab section. Switching the encoding cuts the .ARM.extab section down to 100KB for an overall file size reduction of about 2.9%. There is a complication with ULEB128: there is a ULEB128 field near the front of the EH table pointing to aligned typeinfo val...
2018 Jan 10
0
LLVM EH tables much larger than GCC's
...ev at lists.llvm.org> wrote: > 2. *Termination landing pads.* > > Clang sometimes uses a landing pad that calls __clang_call_terminate to > terminate the program. GCC instead leaves a gap in the call site table, > and the personality routine calls std::terminate. For the 4MB > libQt5Core.so sample I'm looking at, I think it'd reduce the size of .text > and .ARM.extab by maybe 7000 bytes (about 0.18%). (I see about 500 calls to > __clang_call_terminate, and I estimate 14 bytes per call, assuming the call > site table is using ULEB128 already.) > > I tried to...
2018 Jan 11
1
LLVM EH tables much larger than GCC's
...te: > >> 2. *Termination landing pads.* >> >> Clang sometimes uses a landing pad that calls __clang_call_terminate to >> terminate the program. GCC instead leaves a gap in the call site table, >> and the personality routine calls std::terminate. For the 4MB >> libQt5Core.so sample I'm looking at, I think it'd reduce the size of .text >> and .ARM.extab by maybe 7000 bytes (about 0.18%). (I see about 500 calls to >> __clang_call_terminate, and I estimate 14 bytes per call, assuming the call >> site table is using ULEB128 already.) >>...