#531008 Whenever PC starts juk from autostart directory, application crashes

Package:
juk
Source:
juk
Description:
music jukebox / music player
Submitter:
Jordan Manolov
Date:
2018-11-29 17:24:25 UTC
Severity:
normal
#531008#5
Date:
2009-05-29 07:38:48 UTC
From:
To:
I have set juk to start in the kde autostart directory; when the environment
loads, all apps in the directory start as expected except juk, below is the
backtrace (debugging symbols installed):

Application: JuK (juk), signal SIGSEGV
[Current thread is 0 (LWP 5033)]

Thread 6 (Thread 0xb30a7b90 (LWP 5062)):
#0  0xb7fa0424 in __kernel_vsyscall ()
#1  0xb61852e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb63fe0b4 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb3ce6903 in ?? () from /usr/lib/libxine.so.1

Thread 5 (Thread 0xb2805b90 (LWP 5063)):
#0  0xb63225b2 in ?? () from /lib/i686/cmov/libc.so.6
#1  0xb63fe1fb in pthread_mutex_lock () from /lib/i686/cmov/libc.so.6
#2  0xb5c7a226 in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0
#3  0xb5c7b96c in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x09e24160 in ?? ()
#5  0x7fffffff in ?? ()
#6  0x09e25078 in ?? ()
#7  0x00000001 in ?? ()
#8  0xb5cf4928 in ?? () from /usr/lib/libglib-2.0.so.0
#9  0xb5cf4558 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0xb6185e65 in pthread_getspecific () from /lib/i686/cmov/libpthread.so.0
#11 0xa1650000 in ?? ()
#12 0x00000048 in ?? ()

Thread 4 (Thread 0xb2004b90 (LWP 5072)):
#0  0xb7fa0424 in __kernel_vsyscall ()
#1  0xb63e4b17 in poll () from /lib/i686/cmov/libc.so.6
#2  0xb28a1a51 in ?? () from
/usr/lib/xine/plugins/1.25/xineplug_ao_out_alsa.so
#3  0xb2004298 in ?? ()
#4  0x00000001 in ?? ()
#5  0xb2004298 in ?? ()
#6  0x00000000 in ?? ()

Thread 3 (Thread 0xb1803b90 (LWP 5073)):
#0  0xb7fa0424 in __kernel_vsyscall ()
#1  0xb6184fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb63fe05d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb3cf7962 in ?? () from /usr/lib/libxine.so.1
#4  0x0a08e5d0 in ?? ()
#5  0x0a08e5b8 in ?? ()
#6  0x00000000 in ?? ()

Thread 2 (Thread 0xb1002b90 (LWP 5075)):
#0  0xb7fa0424 in __kernel_vsyscall ()
#1  0xb6184fb5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i686/cmov/libpthread.so.0
#2  0xb63fe05d in pthread_cond_wait () from /lib/i686/cmov/libc.so.6
#3  0xb3cf7962 in ?? () from /usr/lib/libxine.so.1
#4  0x0a0acb48 in ?? ()
#5  0x0a0acb30 in ?? ()
#6  0x00000000 in ?? ()

Thread 1 (Thread 0xb562aad0 (LWP 5033)):
[KCrash Handler]
#6  0x080d67a4 in PlaylistCollection::time (this=0xa399f04) at
../../juk/playlistcollection.cpp:124
#7  0x080efffc in StatusLabel::updateData (this=0xa3bcb30) at
../../juk/statuslabel.cpp:128
#8  0x080f0ac0 in StatusLabel (this=0xa3bcb30, playlist=0xa399f04,
parent=0xa3bc538) at ../../juk/statuslabel.cpp:97
#9  0x080aac20 in JuK::setupLayout (this=0xa35fe78) at ../../juk/juk.cpp:131
#10 0x080aef3d in JuK (this=0xa35fe78, parent=0x0) at ../../juk/juk.cpp:87
#11 0x080b3f87 in JuKApplication::newInstance (this=0xbfbbe48c) at
../../juk/main.cpp:65
#12 0xb769ce46 in KUniqueApplicationAdaptor::newInstance (this=0x9e82568,
asn_id=@0x9e878a8, args=@0x9e873f8) at
../../kdeui/kernel/kuniqueapplication_p.h:77
#13 0xb769b03e in KUniqueApplicationAdaptor::qt_metacall (this=0x9e82568,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfbbd358) at
./kuniqueapplication_p.moc:74
#14 0xb7247ec5 in QDBusConnectionPrivate::deliverCall (this=0x9dd7440,
object=0x9e82568, msg=@0x9fcf770, metaTypes=@0x9ddbb44, slotIdx=4) at
qdbusintegrator.cpp:891
#15 0xb7249159 in QDBusConnectionPrivate::activateCall (this=0x9dd7440,
object=0x9e82568, flags=337, msg=@0x9fcf770) at qdbusintegrator.cpp:803
#16 0xb72495c1 in QDBusConnectionPrivate::activateObject (this=0x9dd7440,
node=@0x9fcf75c, msg=@0x9fcf770, pathStartPos=16) at qdbusintegrator.cpp:1375
#17 0xb7249aba in QDBusActivateObjectEvent::placeMetaCall (this=0x9fcf730) at
qdbusintegrator.cpp:1469
#18 0xb7140290 in QObject::event (this=0xbfbbe48c, e=0x9fcf730) at
kernel/qobject.cpp:1118
#19 0xb712f3cb in QCoreApplication::event (this=0xbfbbe48c, e=0x9fcf730) at
kernel/qcoreapplication.cpp:1434
#20 0xb66f80f9 in QApplication::event (this=0xbfbbe48c, e=0x9fcf730) at
kernel/qapplication.cpp:2318
#21 0xb66f27bc in QApplicationPrivate::notify_helper (this=0x9ddc440,
receiver=0xbfbbe48c, e=0x9fcf730) at kernel/qapplication.cpp:4057
#22 0xb66faace in QApplication::notify (this=0xbfbbe48c, receiver=0xbfbbe48c,
e=0x9fcf730) at kernel/qapplication.cpp:3604
#23 0xb7693b7d in KApplication::notify (this=0xbfbbe48c, receiver=0xbfbbe48c,
event=0x9fcf730) at ../../kdeui/kernel/kapplication.cpp:307
#24 0xb712fa2b in QCoreApplication::notifyInternal (this=0xbfbbe48c,
receiver=0xbfbbe48c, event=0x9fcf730) at kernel/qcoreapplication.cpp:610
#25 0xb7130685 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0,
event_type=0, data=0x9dbab18) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 0xb713087d in QCoreApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qcoreapplication.cpp:1140
#27 0xb715b74f in postEventSourceDispatch (s=0x9ddecb8) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#28 0xb5c78848 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb5c7bdab in ?? () from /usr/lib/libglib-2.0.so.0
#30 0x09dde490 in ?? ()
#31 0x00000000 in ?? ()

#531008#10
Date:
2009-05-29 08:55:36 UTC
From:
To:
tags 531008 upstream
thanks

Hello,

the bug you reported is a KDE bug. Please report it via
Help -> Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one on the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
control@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)
------------[ copy this ]------------ forwarded 531008 KDE-BUG-URL thanks ------------[ copy this ]------------
#531008#19
Date:
2014-07-28 11:50:03 UTC
From:
To:
Version: 4:4.8.4-2

Hi,

I could reproduce this issue in a wheezy installation, and since there is quite
a version gap between the reported version and the tested one, I'm marking this
issue as fixed in the later versions. Please reopen the issue is it's still
reproduceable for you.

Happy hacking,

#531008#22
Date:
2014-07-28 11:50:03 UTC
From:
To:
Version: 4:4.8.4-2

Hi,

I could reproduce this issue in a wheezy installation, and since there is quite
a version gap between the reported version and the tested one, I'm marking this
issue as fixed in the later versions. Please reopen the issue is it's still
reproduceable for you.

Happy hacking,