- This topic has 5 odgovora, 3 glasa, and was last updated 18 years ranije by
.
-
Članci
-
Kopete je počeo da se šlogira iz meni neznanog razloga. Naime, pri pokretanju toliko krene da troši resurse da se sve skoro pa pokoči, hdd se vrti kao čigra, RAM memorija se skroz popuni, itd.
Na kraju, posle nekih 45 sekundi mučenja, izbaci ovo:
Evo ga i bektrejs:
Provera podešavanja sistema pri pokretanju je uključena.
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 0xb60376d0 (LWP 8938)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(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 0xffffe430 in __kernel_vsyscall ()
#7 0xb6a0f900 in raise () from /lib/libc.so.6
#8 0xb6a11238 in abort () from /lib/libc.so.6
#9 0xb6be6728 in __gnu_cxx::__verbose_terminate_handler ()
from /usr/lib/libstdc++.so.6
#10 0xb6be4055 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6be4092 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb6be41ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0xb6be4dc3 in operator new () from /usr/lib/libstdc++.so.6
#14 0xb6be4ead in operator new[] () from /usr/lib/libstdc++.so.6
#15 0xb71b4e80 in QString::setLength () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb71b504c in QString::grow () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb71b9ba2 in QString::operator+= () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb7d515a5 in KABC::Addressee::insertCustom ()
from /opt/kde3/lib/libkabc.so.1
#19 0xb7d7062e in KABC::VCardTool::parseVCards ()
from /opt/kde3/lib/libkabc.so.1
#20 0xb7d70a9b in KABC::VCardConverter::parseVCards ()
from /opt/kde3/lib/libkabc.so.1
#21 0xb7d70b80 in KABC::VCardFormatPlugin::loadAll ()
from /opt/kde3/lib/libkabc.so.1
#22 0xb5a3659c in KABC::ResourceFile::load ()
from /opt/kde3/lib/libkabc_file.so.1
#23 0xb7d3c36f in KABC::AddressBook::load () from /opt/kde3/lib/libkabc.so.1
#24 0xb7d3cc28 in KABC::StdAddressBook::init () from /opt/kde3/lib/libkabc.so.1
#25 0xb7d3cff1 in KABC::StdAddressBook::StdAddressBook ()
from /opt/kde3/lib/libkabc.so.1
#26 0xb7d3d04e in KABC::StdAddressBook::self () from /opt/kde3/lib/libkabc.so.1
#27 0xb7e097b5 in Kopete::KABCPersistence::addressBook ()
from /opt/kde3/lib/libkopete.so.1
#28 0xb7e1e71e in Kopete::MetaContact::MetaContact ()
from /opt/kde3/lib/libkopete.so.1
#29 0xb7e1e88f in Kopete::ContactList::myself ()
from /opt/kde3/lib/libkopete.so.1
#30 0x0806fd50 in ?? ()
#31 0x08077f5c in ?? ()
#32 0x080813b6 in ?? ()
#33 0x08081804 in ?? ()
#34 0x08081fa8 in ?? ()
#35 0xb69fb5f5 in __libc_start_main () from /lib/libc.so.6
#36 0x0806e991 in ?? ()Pokušao sam iz konzole da ga pokrenem, pukne na isti način, ali ispiše ovo:
superadmin@suselinux:~> kopete
terminate called after throwing an instance of ‘std::bad_alloc’
what(): std::bad_alloc
KCrash: Application ‘kopete’ crashing…
superadmin@suselinux:~>Zatim sam pokušao da ga pokrenem kao rut, što mi je glatko uspelo – pokrenu se za sekundu. Međutim, ko normalan pokreće i koristi programe kao rut, je l’? Nije to rešenje.
E onda mi je palo na pamet da obrišem sva podešavanja iz „/home/normal_user/.kde/share/apps/kopete“ ali to nije pomoglo ni za dlaku. 😡
Ah da, guglao sam za rešenjem sa onom greškom koju mi vrati iz konzole, ali ne nađoh ništa :-\
Šta sledeće mogu da probam?
E onda mi je palo na pamet da obrišem sva podešavanja iz „/home/normal_user/.kde/share/apps/kopete“ ali to nije pomoglo ni za dlaku. 😡
Jesi li pobrisao i ove datoteke:
$HOME/.kde/share/config/kopete.eventsrc
$HOME/.kde/share/config/kopetercJesi li pobrisao i ove datoteke:
$HOME/.kde/share/config/kopete.eventsrc
$HOME/.kde/share/config/kopetercUpravo, ni to nije pomoglo 🙁
Nešto je kanda zviznulo sa adresarom i v-karticama, ovo bi moglo da bude rešenje: http://ubuntuforums.org/showpost.php?p=4918353&postcount=8 Ako nije, onda probaj dalje da brišeš po ~/.kde/share/apps/kabc/ (naravno, pazi ako ti je tamo nešto važno…)
Uh, zaista je zviznulo sa adresarom! Nikad ne bih pomislio… ali, evo, čim si mi dao ispravnu direkciju, pokušah da otvorim još par programa koji se oslanjaju na adresar (kmail, kontact) i bi ista priča. Pojedu svu memoriju i prsnu.
Fajl „~/.kde/share/apps/kabc/std.vcf“ je bio sasvim u redu, šta više, prazan. Ali, pošto sam za adresar napravio poseban fajl „~/Documents/Adresar/adresar.dat“ proverio sam njega i bio je skroz loš (preko 200 MB, a samo 10 kontakata). Primenio sam rešenje sa adrese http://ubuntuforums.org/showpost.php?p=4918353&postcount=8 i sredio ga.
Hvala svima na pomoći!
Moraš biti prijavljen da bi postavio komentar u ovoj temi.