Bug 175540 - Adept crashes with SIGABRT with invalid sources.list.
Summary: Adept crashes with SIGABRT with invalid sources.list.
Status: RESOLVED FIXED
Alias: None
Product: adept
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Rockai
URL:
Keywords:
: 176989 177117 177289 178690 180024 180876 181500 182777 182856 185028 186085 187115 187674 188167 189162 189245 189357 191056 192244 193655 202073 210038 217355 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-19 02:38 UTC by Mika Smith
Modified: 2009-12-05 03:06 UTC (History)
32 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The KDE Crash Handling Bug Report (2.38 KB, application/octet-stream)
2009-02-02 23:22 UTC, Otis Lockhart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mika Smith 2008-11-19 02:38:00 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Application: Adept (adept), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f16f580a6f0 (LWP 6886)]
[New Thread 0x420d9950 (LWP 6894)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f16f23f7fd5 in raise () from /lib/libc.so.6
#6  0x00007f16f23f9b43 in abort () from /lib/libc.so.6
#7  0x00007f16f2c9cf84 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#8  0x00007f16f2c9b386 in ?? () from /usr/lib/libstdc++.so.6
#9  0x00007f16f2c9b3b3 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0x00007f16f2c9b435 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#11 0x00007f16f3b888fd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#12 0x00007f16f3b8acbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#13 0x000000000048f40f in ?? ()
#14 0x00007f16f23e3466 in __libc_start_main () from /lib/libc.so.6
#15 0x0000000000458059 in _start ()
#0  0x00007f16f246d621 in nanosleep () from /lib/libc.so.6
Comment 1 Peter Rockai 2008-11-19 06:42:58 UTC
Hi,

1: How to reproduce? If not possible, at least a description of what were you doing, in which mode (installer, updater, manager)...
2: Could you please include terminal output of adept? (Ie. run it from a terminal and paste the output here.)

Thanks.
Comment 2 PabloJavier 2008-12-24 18:39:44 UTC
(In reply to comment #1)
> Hi,
> 
> 1: How to reproduce? If not possible, at least a description of what were you
> doing, in which mode (installer, updater, manager)...
> 2: Could you please include terminal output of adept? (Ie. run it from a
> terminal and paste the output here.)
> 
> Thanks.
> 

I have the same problem, Im tryng to run Adep from the apliccation launcher then app than addep.

Application: Adept (adept), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5f876c0 (LWP 5645)]
[New Thread 0xb483cb90 (LWP 5653)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb805c430 in __kernel_vsyscall ()
#7  0xb6818880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb681a248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6a3c6f8 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb6a3a5d5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6a3a612 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb6a3a6cb in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb74cede5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb74cf7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb74d4db7 in ?? () from /usr/lib/libQtCore.so.4
#16 0xb74d4edc in ?? () from /usr/lib/libQtCore.so.4
#17 0xb74c953f in QObject::event () from /usr/lib/libQtCore.so.4
#18 0xb6baa8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#19 0xb6bb272e in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0xb7988b2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0xb74b9e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#22 0xb74e7d81 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb74e4520 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb63006f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb6303da3 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb6303f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb74e4478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb6c44ea5 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb74b852a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb74b86ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb74bada5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6baa767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0x080c80c6 in ?? ()
#34 0xb6803685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#35 0x08095ae1 in _start ()
#0  0xb805c430 in __kernel_vsyscall ()


Comment 3 Sybren Deuzeman 2009-01-03 19:55:08 UTC
ubuntu 8.10, kernel 2.6.27-11-generic[AutoMagic]
OS: Linux
Installed from: Unknown


I think this is the same problem

Just before I had this problem, I try to set this in my third-software-tab 
deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu intrepid main. After this I closed adept and when I try to start Adept I get the same problem. After this, I tried if I could start other package managers. These programs didn't start as well. 

Starting Adept give this:

Application: Adept (adept), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f34c387c6f0 (LWP 5679)]
[New Thread 0x42729950 (LWP 5687)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f34c046bfd5 in raise () from /lib/libc.so.6
#6  0x00007f34c046db43 in abort () from /lib/libc.so.6
#7  0x00007f34c0d10f84 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#8  0x00007f34c0d0f386 in ?? () from /usr/lib/libstdc++.so.6
#9  0x00007f34c0d0f3b3 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0x00007f34c0d0f435 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#11 0x00007f34c1bfc8fd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#12 0x00007f34c1bfecbd in QCoreApplication::exec ()
   from /usr/lib/libQtCore.so.4
#13 0x000000000048f40f in ?? ()
#14 0x00007f34c0457466 in __libc_start_main () from /lib/libc.so.6
#15 0x0000000000458059 in _start ()
#0  0x00007f34c04e1621 in nanosleep () from /lib/libc.so.6

Add / Remove give this fault:

"
Failed to check for installed and available applications

This is a major failure of your software management system. Please check for broken packages with synaptic, check the file permissions and correctness of the file '/etc/apt/sources.list' and reload the software information with: 'sudo apt-get update' and 'sudo apt-get install -f'.
"
I tried to do both, giving this

sybren@sybren-laptop:~$ sudo apt-get update
E: Type ‘http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu’ is not known on line 45 in source list /etc/apt/sources.list

sybren@sybren-laptop:~$ sudo apt-get install -f
E: Type ‘http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu’ is not known on line 45 in source list /etc/apt/sources.list
E: The list of sources could not be read.


Synaptic give this fault:

"An error occurred

the following details are provided

E: Type ‘http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu’ is not known on line 45 in source list /etc/apt/sources.list
E: The list of sources could not be read.
Go to the repository dialogue to correct the problem.
E: _cache->open() failed, please report."

after this I tried to download with the console, but when I try to search at amarok, I got this message.

"sybren@sybren-laptop:~$ aptitude search amarok
E: Type ‘http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu’ is not known on line 45 in source list /etc/apt/sources.list
E: Type ‘http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu’ is not known on line 45 in source list /etc/apt/sources.list
E: The list of sources could not be read.

I am not sure if this is the same problem, but I think so.
Comment 4 Jonathan Thomas 2009-01-18 20:39:49 UTC
The problem is that Adept crashes when non-valid entries are in /etc/apt/sources.list
Comment 5 Jonathan Thomas 2009-01-18 20:40:20 UTC
*** Bug 180024 has been marked as a duplicate of this bug. ***
Comment 6 Jonathan Thomas 2009-01-18 20:41:26 UTC
*** Bug 176989 has been marked as a duplicate of this bug. ***
Comment 7 Jonathan Thomas 2009-01-18 20:41:45 UTC
*** Bug 177117 has been marked as a duplicate of this bug. ***
Comment 8 Jonathan Thomas 2009-01-18 20:50:27 UTC
*** Bug 178690 has been marked as a duplicate of this bug. ***
Comment 9 Jonathan Thomas 2009-01-18 21:58:11 UTC
*** Bug 180876 has been marked as a duplicate of this bug. ***
Comment 10 Dario Andres 2009-01-21 16:01:28 UTC
*** Bug 181500 has been marked as a duplicate of this bug. ***
Comment 11 Jonathan Thomas 2009-01-29 15:45:17 UTC
*** Bug 177289 has been marked as a duplicate of this bug. ***
Comment 12 Jonathan Thomas 2009-02-02 17:15:02 UTC
*** Bug 182856 has been marked as a duplicate of this bug. ***
Comment 13 Otis Lockhart 2009-02-02 23:00:22 UTC
Hey Thomas,

I tried what you suggested and my gdebi installer stated, " my software index is broken.  In the Konsole it stated, "that the malformed line 55 in the /etc/apt/sources.list cannot be read.  Plus I cannot open adept at all or add/remove either. So, is this the same problem like the others.  I really damage the installer application none of them will work. Only from Konsole can I do anything.  So, what sudo command should I use to correct this issue.

Thanks
Comment 14 Otis Lockhart 2009-02-02 23:18:28 UTC
(In reply to comment #0)
> Version:            (using KDE 4.1.3)
> OS:                Linux
> Installed from:    Ubuntu Packages
> 
> Application: Adept (adept), signal SIGABRT
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread 0x7f16f580a6f0 (LWP 6886)]
> [New Thread 0x420d9950 (LWP 6894)]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [KCrash handler]
> #5  0x00007f16f23f7fd5 in raise () from /lib/libc.so.6
> #6  0x00007f16f23f9b43 in abort () from /lib/libc.so.6
> #7  0x00007f16f2c9cf84 in __gnu_cxx::__verbose_terminate_handler ()
>    from /usr/lib/libstdc++.so.6
> #8  0x00007f16f2c9b386 in ?? () from /usr/lib/libstdc++.so.6
> #9  0x00007f16f2c9b3b3 in std::terminate () from /usr/lib/libstdc++.so.6
> #10 0x00007f16f2c9b435 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
> #11 0x00007f16f3b888fd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
> #12 0x00007f16f3b8acbd in QCoreApplication::exec ()
>    from /usr/lib/libQtCore.so.4
> #13 0x000000000048f40f in ?? ()
> #14 0x00007f16f23e3466 in __libc_start_main () from /lib/libc.so.6
> #15 0x0000000000458059 in _start ()
> #0  0x00007f16f246d621 in nanosleep () from /lib/libc.so.6
> 

Comment 15 Otis Lockhart 2009-02-02 23:22:40 UTC
Created attachment 30884 [details]
The KDE Crash Handling Bug Report

This is my Adept's bug report for the crash and Software Index is broken I have a major problem that can only be solved in Konsole.  So, I need to know what sudo commands I need to do to fix this Thanks,

Otis
Comment 16 Dario Andres 2009-02-21 01:44:33 UTC
*** Bug 185028 has been marked as a duplicate of this bug. ***
Comment 17 Jonathan Thomas 2009-03-04 03:56:09 UTC
*** Bug 186085 has been marked as a duplicate of this bug. ***
Comment 18 jscardenasr 2009-03-12 05:12:59 UTC
yhis may be the same problem
Application: Adept (adept), signal SIGABRT
0x00007fb2e93656e1 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 8849)]
Thread 2 (Thread 0x421f6950 (LWP 8855)):
#0 0x00007fb2e939c4b2 in select () from /lib/libc.so.6
#1 0x00007fb2eaa62006 in ?? () from /usr/lib/libQtCore.so.4
#2 0x00007fb2ea999362 in ?? () from /usr/lib/libQtCore.so.4
#3 0x00007fb2e90a83ea in start_thread () from /lib/libpthread.so.0
#4 0x00007fb2e93a3cbd in clone () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7fb2ec7046f0 (LWP 8849)):
[KCrash Handler]
#5 0x00007fb2e92f0015 in raise () from /lib/libc.so.6
#6 0x00007fb2e92f1b83 in abort () from /lib/libc.so.6
#7 0x00007fb2e9b94f94 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6
#8 0x00007fb2e9b93396 in ?? () from /usr/lib/libstdc++.so.6
#9 0x00007fb2e9b933c3 in std::terminate () from /usr/lib/libstdc++.so.6
#10 0x00007fb2e9b93445 in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#11 0x00007fb2eaa808fd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#12 0x00007fb2eaa82cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#13 0x000000000048f40f in ?? ()
#14 0x00007fb2e92db466 in __libc_start_main () from /lib/libc.so.6
#15 0x0000000000458059 in _start ()
Comment 19 Dario Andres 2009-03-14 22:53:35 UTC
*** Bug 187115 has been marked as a duplicate of this bug. ***
Comment 20 chasemyers 2009-03-15 01:30:15 UTC
(In reply to comment #19)
> *** Bug 187115 has been marked as a duplicate of this bug. ***

thanks for letting me know that this is a known bug, i hope it's fixed in the next upgrade. but that doesn't really help me at all. how do i fix it?
Comment 21 Dario Andres 2009-03-27 17:49:46 UTC
@chasemyers@gmail.com (comment 20): you need to review your sources.list file and try to remove the invalid line. Using the command line app "apt-get" to install some package should complain about that invalid line (that probably was manually added)
Thanks
Comment 22 Jonathan Thomas 2009-03-31 04:22:56 UTC
*** Bug 188167 has been marked as a duplicate of this bug. ***
Comment 23 Jonathan Thomas 2009-03-31 04:23:21 UTC
*** Bug 187674 has been marked as a duplicate of this bug. ***
Comment 24 Jonathan Thomas 2009-03-31 04:25:04 UTC
*** Bug 182777 has been marked as a duplicate of this bug. ***
Comment 25 Dario Andres 2009-04-10 03:20:38 UTC
*** Bug 189245 has been marked as a duplicate of this bug. ***
Comment 26 Dario Andres 2009-04-11 15:44:06 UTC
*** Bug 189357 has been marked as a duplicate of this bug. ***
Comment 27 blacknails28 2009-04-12 12:58:13 UTC
hi all,

this is the crash detail in my ubuntu...

Thanks,

Application: Adept (adept), signal SIGABRT
[Current thread is 0 (LWP 11807)]

Thread 2 (Thread 0xb470eb90 (LWP 11815)):
#0  0xb7f45430 in __kernel_vsyscall ()
#1  0xb67afdf1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7381150 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb72b16ae in ?? () from /usr/lib/libQtCore.so.4
#4  0xb66c350f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb67b7a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb5e706c0 (LWP 11807)):
[KCrash Handler]
#6  0xb7f45430 in __kernel_vsyscall ()
#7  0xb67018a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6703268 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0x080ae99f in ?? ()
#10 0x08103c09 in ?? ()
#11 0x08101778 in ?? ()
#12 0x08100da7 in ?? ()
#13 0x08100c8d in ?? ()
#14 0x080cf51a in ?? ()
#15 0xb73b6a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb73b77e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0x080cf5fb in ?? ()
#18 0x080bfc65 in ?? ()
#19 0x080e08fd in ?? ()
#20 0x080b65ad in ?? ()
#21 0x080b7cf9 in ?? ()
#22 0x080d0eee in ?? ()
#23 0xb73b6a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb73b77e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb73bcdb7 in ?? () from /usr/lib/libQtCore.so.4
#26 0xb73bcedc in ?? () from /usr/lib/libQtCore.so.4
#27 0xb73b153f in QObject::event () from /usr/lib/libQtCore.so.4
#28 0xb6a928ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#29 0xb6a9a72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#30 0xb7870d1d in KApplication::notify () from /usr/lib/libkdeui.so.5
#31 0xb73a1e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#32 0xb73cfd81 in ?? () from /usr/lib/libQtCore.so.4
#33 0xb73cc520 in ?? () from /usr/lib/libQtCore.so.4
#34 0xb61e9718 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#35 0xb61ecdc3 in ?? () from /usr/lib/libglib-2.0.so.0
#36 0xb61ecf81 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#37 0xb73cc478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#38 0xb6b2cea5 in ?? () from /usr/lib/libQtGui.so.4
#39 0xb73a052a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#40 0xb73a06ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#41 0xb73a2da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#42 0xb6a92767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#43 0x080c80c6 in ?? ()
#44 0xb66ec685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#45 0x08095ae1 in _start ()
Comment 28 Fainblat 2009-04-24 18:21:48 UTC
Hey guys! Thats what I did: I used the terminal to get to sources.list - etc/apt/sources.list
Then I made a sudo kwrite sources.list, gave it a password, and finally got the file opened. Then, I removed manually the third party sources I had configured using adept. In my case, it was wicd. That made it work ok! Bye
Comment 29 Dario Andres 2009-04-30 00:39:21 UTC
*** Bug 191056 has been marked as a duplicate of this bug. ***
Comment 30 Dario Andres 2009-05-10 19:46:33 UTC
*** Bug 192244 has been marked as a duplicate of this bug. ***
Comment 31 Dario Andres 2009-05-22 17:57:44 UTC
*** Bug 193655 has been marked as a duplicate of this bug. ***
Comment 32 pebroy 2009-06-20 21:13:59 UTC
Folks,

I don't know if I missed something on this thread, has this issue been resolved?  I just came across this issue today 06/20/2009 after changing third party options.  I have tried change etc/apt/sources.list since I had a backup but it still does not work.  I keep getting error "Adept Manager The KDE Crash Handler" Is there a solution to this issue?

look forward to your comments.
Comment 33 Dario Andres 2009-06-20 21:17:18 UTC
(In reply to comment #32)
> Folks,
> 
> I don't know if I missed something on this thread, has this issue been
> resolved?  I just came across this issue today 06/20/2009 after changing third
> party options.  I have tried change etc/apt/sources.list since I had a backup
> but it still does not work.  I keep getting error "Adept Manager The KDE Crash
> Handler" Is there a solution to this issue?
> 
> look forward to your comments.

Hi. AFAIK Adept is not going to be developed anymore so I guess this bug is not going to be fixed. The workaround was to remove the invalid entries from the sources.list file (IIRC, doing a "apt-get" operation you will get which entry is invalid, so you can remove it).
May be your crash is a different one (and the root cause is different). Have you compared the backtraces?
Regards
Comment 34 pebroy 2009-06-20 21:27:36 UTC
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65f56c0 (LWP 6457)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7f92410 in __kernel_vsyscall ()
#7  0xb666d085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb666ea01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb687d480 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb687ad05 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb687ad42 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb687ae6a in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0x080fe3c6 in ?? ()
#14 0x080fe7ca in ?? ()
#15 0x080ff035 in ?? ()
#16 0x080ff115 in ?? ()
#17 0x080fcb0d in ?? ()
#18 0x0813870e in ?? ()
#19 0x080974b0 in ?? ()
#20 0x080758dd in ?? ()
#21 0x080764ff in ?? ()
#22 0xb6ed0704 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb725faba in QSignal::signal () from /usr/lib/libqt-mt.so.3
#24 0xb6eef7b2 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#25 0xb6ef7936 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6e64c36 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6e66a5f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb760d9b2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6df528d in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6e57b19 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6e0a64b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6e7ff90 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6e7fc8e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6e667df in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x080717b3 in ?? ()
#36 0xb6658450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x08071401 in ?? ()
Comment 35 Dario Andres 2009-06-20 21:29:45 UTC
It seems the same ... (anyways all backtrace are lacking some info)
Comment 36 Dario Andres 2009-07-31 14:44:43 UTC
*** Bug 202073 has been marked as a duplicate of this bug. ***
Comment 37 youssef.mokrane 2009-08-01 00:41:05 UTC
I have the same problem - I think- . I wanted to install mozilla firefox, and the research within Adept installer didn't give result, so I had copied the link of Mozilla installation file in the ressources tab of Adept and after that, Adept stopped running and i didn't be able to restart it. I tried to apply methods presented above to modifiy my sources.list but i didn't be able for the following problem:
When i tape "sudo /etc/apt/sources.list", i find an invite to tape my password but, i cannot type it at all. 
youssef@youssef-laptop:~$ sudo /etc/apt/sources.list
[sudo] password for youssef:

Is this an other problem or is a simple question of wrong setting in my terminal..

At the same time i cannot use any "apt-get" command (update, check, remove (i tried to remove "adept"),...) So actually i cannot complete the installation of software in my Kubuntu 8.10 or  upgrade to  9.4 distribution.

Thank you to help me.

Youssef
Comment 38 youssef.mokrane 2009-08-01 00:44:05 UTC
I put there the error details  from the crash report :
Application : Adept (adept), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5fb86c0 (LWP 8974)]
[New Thread 0xb47e9b90 (LWP 8986)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb8086430 in __kernel_vsyscall ()
#7  0xb6849880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb684b248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6a6d6f8 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb6a6b5d5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6a6b612 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb6a6b6cb in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb74ffde5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb75007e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb7505db7 in ?? () from /usr/lib/libQtCore.so.4
#16 0xb7505edc in ?? () from /usr/lib/libQtCore.so.4
#17 0xb74fa53f in QObject::event () from /usr/lib/libQtCore.so.4
#18 0xb6bdb8ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#19 0xb6be376e in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0xb79b972d in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0xb74eae61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#22 0xb7518d81 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb7515520 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb63316f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb6334da3 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb6334f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb7515478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb6c75ee5 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb74e952a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb74e96ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb74ebda5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6bdb767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0x080c80c6 in ?? ()
#34 0xb6834685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#35 0x08095ae1 in _start ()
#0  0xb8086430 in __kernel_vsyscall ()
Comment 39 Peter Rockai 2009-08-06 18:24:40 UTC
*** Bug 189162 has been marked as a duplicate of this bug. ***
Comment 40 Peter Rockai 2009-08-06 19:11:07 UTC
Well, fixed in beta5 (available in Debian Sid near you).
Comment 41 Jonathan Thomas 2009-10-10 14:14:59 UTC
*** Bug 210038 has been marked as a duplicate of this bug. ***
Comment 42 Dario Andres 2009-12-05 03:06:35 UTC
*** Bug 217355 has been marked as a duplicate of this bug. ***