Summary: | adept can't find any updates from kde 4.3.1 | ||
---|---|---|---|
Product: | [Unmaintained] adept | Reporter: | Acidburn_Zero <acidburn0> |
Component: | general | Assignee: | Peter Rockai <me> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | annma, molkentin |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | All | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Acidburn_Zero
2009-10-10 01:55:28 UTC
Application that crashed: adept Version of the application: 3.0 Beta 4 (Sheldon) KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-server x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: <In detail, tell us what you were doing when the application crashed.> -- Backtrace: Application: Adept (adept), signal: Aborted [KCrash Handler] #5 0x00007fd21d781fb5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00007fd21d783bc3 in *__GI_abort () at abort.c:88 #7 0x00007fd21e0270b4 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #8 0x00007fd21e0254b6 in ?? () from /usr/lib/libstdc++.so.6 #9 0x00007fd21e0254e3 in std::terminate () from /usr/lib/libstdc++.so.6 #10 0x00007fd21e025565 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #11 0x00007fd21d459429 in QEventLoop::exec (this=0x7fff27e70bf0, flags={i = 669453312}) at kernel/qeventloop.cpp:214 #12 0x00007fd21d45b5e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #13 0x000000000048d1b7 in ?? () #14 0x00007fd21d76d5a6 in __libc_start_main (main=0x48c0ad, argc=2, ubp_av=0x7fff27e71068, init=0x4dd2f0 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff27e71058) at libc-start.c:220 #15 0x0000000000455ed9 in _start () Report to https://bugs.kde.org Does this happen on a new install? or after an upgrade? or did it work before and then it just stopped working? *** This bug has been marked as a duplicate of bug 175540 *** |