Re: KDE SC 4.5.1 packages available
On Fri, Sep 10, 2010 at 3:53 PM, Zsolt Rizsanyi
<rizsanyi@users.sourceforge.net> wrote:
> On Fri, Sep 10, 2010 at 2:35 PM, Dietz Pröpper <dietz@rotfl.franken.de> wrote:
>> George Kiagiadakis:
>>> On Fri, Sep 10, 2010 at 12:02 PM, Dietz Pröpper <dietz@rotfl.franken.de>
>> wrote:
>>> > - digikam from unstable crashes (the kde term for "crash" should be
>>> > "krash" imho ;-) on startup.
>>> > - marble (from 4.5.1) crashes on startup too.
>>>
>>> Marble seems to work just fine here. I'll check digikam as well... Do
>>> you have any backtraces?
>>
>> Unfortunately not. And just no time atm to go to 4.5.1 again to check.
>
> Marble crashes on startup for me too. Here is a backtrace:
> Thread 3 (Thread 0xb1362b70 (LWP 4221)):
> #0 0xb4572e16 in *__GI_clock_gettime (clock_id=-1269338124,
> tp=0xb1361fb8) at ../sysdeps/unix/clock_gettime.c:100
> #1 0xb6a631db in ?? () from /usr/lib/libQtCore.so.4
> #2 0xb6a68435 in ?? () from /usr/lib/libQtCore.so.4
> #3 0xb6a6847a in ?? () from /usr/lib/libQtCore.so.4
> #4 0xb6a662e8 in ?? () from /usr/lib/libQtCore.so.4
> #5 0xb6a66375 in ?? () from /usr/lib/libQtCore.so.4
> #6 0xb44e47ca in g_main_context_prepare () from /lib/libglib-2.0.so.0
> #7 0xb44e4be9 in ?? () from /lib/libglib-2.0.so.0
> #8 0xb44e51b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
> #9 0xb6a660df in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () from /usr/lib/libQtCore.so.4
> #10 0xb6a38b19 in
> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
> from /usr/lib/libQtCore.so.4
> #11 0xb6a38f6a in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib/libQtCore.so.4
> #12 0xb693b629 in QThread::exec() () from /usr/lib/libQtCore.so.4
> #13 0xb6a1895b in ?? () from /usr/lib/libQtCore.so.4
> #14 0xb693dfbe in ?? () from /usr/lib/libQtCore.so.4
> #15 0xb458e955 in start_thread (arg=0xb1362b70) at pthread_create.c:300
> #16 0xb5b8e10e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
>
> It is a segfault.
That's not very useful, you need to install libqt4-dbg before
generating the backtrace.
>
> Not sure how did glib get into this backtrace :) I don't have time to
> now to try to find out.
glib is used internally by Qt and provides a backend for its event
loop. This has been there for a long time. It is used to make
glib-based libraries integrate nicely in Qt applications.
> BTW which version of Qt are you using? My Qt version is 4:4.6.3-1+b1
> and libglib2.0-0 2.24.1-1. I can try some other versions if needed.
Hmm.. I'm actually using Qt 4.7.0~rc1 from experimental and glib
2.24.1, like you.
Reply to: