** Description changed:

  Binary package hint: pidgin
  
  It's an "old" bug that apport poped-up after last update, 20 minutes ago
  (I think it wasn't working fine and on the last 10 minutes it threw up
  more than 10 old bugs...). I don't even remember what happened to
  Pidgin.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: pidgin 1:2.6.6-1ubuntu4 [modified: usr/bin/pidgin]
  ProcVersionSignature: Ubuntu 2.6.32-20.29-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-20-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Apr  5 11:28:26 2010
  Disassembly: => 0x3413c83022: Não é possível acessar a memória no endereço 
0x3413c83022
  ExecutablePath: /usr/bin/pidgin
  ProcCmdline: /usr/bin/pidgin
  ProcEnviron:
   LANGUAGE=pt_BR:pt:pt_PT:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
- SegvAnalysis:
-  Segfault happened at: 0x3413c83022:  Não é possível acessar a memória no 
endereço 0x3413c83022
-  PC (0x3413c83022) ok
-  source "0x3413c83022" (0x3413c83022) ok
-  SP (0x7fff96264008) ok
-  Reason could not be automatically determined.
  Signal: 11
  SourcePackage: pidgin
  Stacktrace:
   #0  0x0000003413c83022 in ?? ()
   No symbol table info available.
   Não é possível acessar a memória no endereço 0x7fff96264008
  StacktraceTop: ?? ()
  ThreadStacktrace:
   .
   Thread 1 (Thread 15811):
   #0  0x0000003413c83022 in ?? ()
   No symbol table info available.
   Não é possível acessar a memória no endereço 0x7fff96264008
  Title: pidgin crashed with SIGSEGV
  UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev 
plugdev scanner vboxusers video
+ SegvAnalysis:
+  Segfault happened at: 0x3413c83022:  Não é possível acessar a memória no 
endereço 0x3413c83022
+  PC (0x3413c83022) ok
+  source "0x3413c83022" (0x3413c83022) ok
+  SP (0x7fff96264008) ok
+  Reason could not be automatically determined.
+ SegvReason: Reason could not be automatically determined.

-- 
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/561309
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to