** Description changed: Binary package hint: telepathy-mission-control-5 1) k...@mars:~$ lsb_release -rd Description: Ubuntu lucid (development branch) Release: 10.04 2) k...@mars:~$ apt-cache policy empathy empathy: Installiert: 2.29.90-0ubuntu2 3) I can chat again within the ICQ-network. 4) I can't. Description: Empathy didnt login to ICQ so i followed these steps http://live.gnome.org/Empathy/FAQ#I_can.27t_connect_to_my_AIM.2BAC8-ICQ_account_anymore . When i typed in the last line i got a segfault. console I/O: k...@mars:~$: mc-tool update _3xxxxxxxxx0 bool:use-clientlogin=false //xxxxxxxxx=my icq nummber Segmentation fault (Speicherabzug geschrieben) + + UPDATE: + When I type in: + mc-tool update haze/icq/ _3xxxxxxxxx0 bool:use-clientlogin=false + + everything works and I can chat again. + ENDUPDATE ProblemType: Crash Architecture: amd64 CheckboxSubmission: e67518e39bad86d14b571225dc886146 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Sun Feb 21 12:24:10 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes ExecutablePath: /usr/bin/mc-tool InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100220) NonfreeKernelModules: nvidia Package: telepathy-mission-control-5 5.3.2-2 ProcCmdline: mc-tool update _3xxxxxxxxx0 bool:use-clientlogin=false ProcEnviron: SHELL=/bin/bash LANG=de_LI.utf8 LANGUAGE=de_LI.utf8 ProcVersionSignature: Ubuntu 2.6.32-14.20-generic SegvAnalysis: Segfault happened at: 0x409574: mov 0x60(%rbx),%rax PC (0x00409574) ok source "0x60(%rbx)" (0x00000060) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: telepathy-mission-control-5 StacktraceTop: ?? () ?? () __libc_start_main () from /lib/libc.so.6 ?? () ?? () Title: mc-tool crashed with SIGSEGV in __libc_start_main() Uname: Linux 2.6.32-14-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
-- mc-tool crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/525253 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
