Thank you for the bug report. As you no longer have this problem and no
more users have experienced this, I will be closing the bug report. If
you have any reservations, feel free to respond to this.
** Changed in: amarok (Ubuntu)
Status: Needs Info => Rejected
--
SIGSEGV in knotify when
No - it's fine on the one in dapper-backports.
--
SIGSEGV in knotify when configuring amoraK
https://launchpad.net/bugs/55284
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
does this still happen with the latest edgy beta cd or amarok 1.4.3 from
dapper-backports ?
--
SIGSEGV in knotify when configuring amoraK
https://launchpad.net/bugs/55284
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Is that all the info you need?
--
SIGSEGV in knotify when configuring amoraK
https://launchpad.net/bugs/55284
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1231477056 (LWP 6519)]
[KCrash handler]
#6 0xb67ed73f in KAudioManagerPlay (this=0x81ee3c8, server=0xbfbf37a0,
[EMAIL PROTECTED]) at soundserver.h:1787
#7 0xb688
I guess that you will only have to rebuild the knotify package and wait
for a crash to happen - then you will get the backtrace with debugging
symbols from the crash handler.
** Changed in: amarok (Ubuntu)
Status: Unconfirmed => Needs Info
--
SIGSEGV in knotify when configuring amoraK
htt
Thank you for your bug report. Can you please try to obtain a backtrace
following the instructions on
http://wiki.ubuntu.com/DebuggingProgramCrash ?
--
SIGSEGV in knotify when configuring amoraK
https://launchpad.net/bugs/55284
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
