[amarok] [Bug 403889] Unable to start amarok

2019-03-08 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=403889

Myriam Schweingruber  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |DOWNSTREAM

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 403889] Unable to start amarok

2019-03-07 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=403889

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #7 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 403889] Unable to start amarok

2019-02-20 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=403889

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 403889] Unable to start amarok

2019-02-06 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=403889

Myriam Schweingruber  changed:

   What|Removed |Added

Version|unspecified |2.9.0

--- Comment #5 from Myriam Schweingruber  ---
(In reply to Cfossy3 from comment #4)
> version 2:2.9.0-Oubuntu2(bionic)

thank you for the feedback, did you report this to your distribution? It looks
like the fault is not in Amarok itself. Also, were you able to start this
version of Amarok in your distribution before?

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 403889] Unable to start amarok

2019-02-03 Thread Cfossy3
https://bugs.kde.org/show_bug.cgi?id=403889

--- Comment #4 from Cfossy3  ---
version 2:2.9.0-Oubuntu2(bionic)

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 403889] Unable to start amarok

2019-02-03 Thread Cfossy3
https://bugs.kde.org/show_bug.cgi?id=403889

--- Comment #3 from Cfossy3  ---
Application: Amarok (amarok), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f692d505b80 (LWP 23794))]

Thread 34 (Thread 0x7f6857ab5700 (LWP 23846)):
#0  0x7f692a10b0b4 in __GI___libc_read (fd=79, buf=0x7f6857ab4820,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f6921d11cd0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6921ccd027 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6921ccd4e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6921ccd64c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f692a93022e in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x55c83cff01d0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f692a8fe12f in
QEventLoop::processEvents(QFlags)
(this=this@entry=0x7f6857ab4a30, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f692a8fe495 in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f6857ab4a30, flags=...) at kernel/qeventloop.cpp:204
#8  0x7f692a7ed549 in QThread::exec() (this=) at
thread/qthread.cpp:538
#9  0x7f692a7efe3c in QThreadPrivate::start(void*) (arg=0x7f68b802a020) at
thread/qthread_unix.cpp:352
#10 0x7f692879c6db in start_thread (arg=0x7f6857ab5700) at
pthread_create.c:463
#11 0x7f692a11c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 33 (Thread 0x7f6898f9c700 (LWP 23845)):
#0  0x7f69287a29f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f6920ab2698) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f69287a29f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f6920ab2648, cond=0x7f6920ab2670) at pthread_cond_wait.c:502
#2  0x7f69287a29f3 in __pthread_cond_wait (cond=0x7f6920ab2670,
mutex=0x7f6920ab2648) at pthread_cond_wait.c:655
#3  0x7f69200206fd in  () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#4  0x7f6920020759 in  () at /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#5  0x7f692879c6db in start_thread (arg=0x7f6898f9c700) at
pthread_create.c:463
#6  0x7f692a11c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 32 (Thread 0x7f68999ba700 (LWP 23844)):
#0  0x7f69287a29f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55c83d797d88) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f69287a29f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55c83d797d38, cond=0x55c83d797d60) at pthread_cond_wait.c:502
#2  0x7f69287a29f3 in __pthread_cond_wait (cond=0x55c83d797d60,
mutex=0x55c83d797d38) at pthread_cond_wait.c:655
#3  0x7f68acd7223b in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4  0x7f68acd71f67 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5  0x7f692879c6db in start_thread (arg=0x7f68999ba700) at
pthread_create.c:463
#6  0x7f692a11c88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 31 (Thread 0x7f68aeffd700 (LWP 23840)):
#0  0x7f69287a29f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55c83cee4a64) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f69287a29f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55c83cee4a10, cond=0x55c83cee4a38) at pthread_cond_wait.c:502
#2  0x7f69287a29f3 in __pthread_cond_wait (cond=0x55c83cee4a38,
mutex=0x55c83cee4a10) at pthread_cond_wait.c:655
#3  0x7f692a7f03a6 in QWaitConditionPrivate::wait(unsigned long)
(time=18446744073709551615, this=0x55c83cee4a10) at
thread/qwaitcondition_unix.cpp:86
#4  0x7f692a7f03a6 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x55c83cee4918, mutex=0x55c83cee4b90,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#5  0x7f69257c8d7f in
ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*)
(this=0x55c83cee48f0, th=0x55c83c61cef0) at
./threadweaver/Weaver/WeaverImpl.cpp:370
#6  0x7f69257cb9bb in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) (this=0x55c83cee4c20, th=0x55c83c61cef0, previous=0x0) at
./threadweaver/Weaver/WorkingHardState.cpp:68
#7  0x7f69257cb9d4 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) (this=0x55c83cee4c20, th=0x55c83c61cef0, previous=0x0) at
./threadweaver/Weaver/WorkingHardState.cpp:71
#8  0x7f69257cb9d4 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*,
ThreadWeaver::Job*) (this=0x55c83cee4c20, th=0x55c83c61cef0,
previous=0x55c83da82d10) at ./threadweaver/Weaver/WorkingHardState.cpp:71
#9  0x7f69257ca497 in ThreadWeaver::Thread::run() (this=0x55c83c61cef0) at
./threadweaver/Weaver/Thread.cpp:98
#10 0x7f692a7efe3c in QThreadPrivate::start(void*) (arg=0x55c83c61cef0) at
thread/qthread_unix.cpp:352
#11 0x7f692879c6db in 

[amarok] [Bug 403889] Unable to start amarok

2019-02-03 Thread Myriam Schweingruber
https://bugs.kde.org/show_bug.cgi?id=403889

Myriam Schweingruber  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO

--- Comment #2 from Myriam Schweingruber  ---
Which exact version is this about? 

Did you report this to your distribution?

Looking at the backtrace this crash does not appear to be in Amarok itself, and
you do not have debugging symbols installed for Amarok and all its
dependencies, so not really helpful
FWIW: please do not attach backtraces, paste those in the comment directly,
also attaching PDF is not really helpful either as it can't be opened in
bugzilla.

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 403889] Unable to start amarok

2019-02-03 Thread Cfossy3
https://bugs.kde.org/show_bug.cgi?id=403889

Cfossy3  changed:

   What|Removed |Added

 CC||craigfoste...@gmail.com

--- Comment #1 from Cfossy3  ---
Created attachment 117803
  --> https://bugs.kde.org/attachment.cgi?id=117803=edit
Backtrace

-- 
You are receiving this mail because:
You are watching all bug changes.