gnome-phone-manager crashed with SIGSEGV

[Martin-Éric Racine]

Binary package hint: gnome-phone-manager

Crashes as soon as the option to send an SMS is selected. Information collected by ubuntu-bug attached.

ProblemType: Crash
Architecture: i386
Disassembly: 0xb45a8070:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-phone-manager
Package: gnome-phone-manager 0.60-1build1
ProcCmdline: gnome-phone-manager
ProcEnviron:
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-phone-manager
Stacktrace: #0 0xb45a8070 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: gnome-phone-manager crashed with SIGSEGV
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse-rt video

[Apport retracing service (apport)]

StacktraceTop:?? ()

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Martin-Éric Racine (q-funk)]

Thank you for getting around responding to this bug.

I'm unfortunately unable to perform any test at this time, because I keep on getting Access Denied when trying to connect to my phone i.e. gnome-phone-manager shows the red circle with the white dash in it as its icon. Until someone has found the way to restore basic connectivity, it will be very hard to perform this test.

[Martin-Éric Racine (q-funk)]

Actually, here's the interesting part: gnome-phone-manager manages to connect to the phone if it runs on its own. However, when started via GDB, it fails to connect.

[Martin-Éric Racine (q-funk)]

Pedro, would you happen to know why Access is denied when running gnome-phone-manager under GDB?

[Martin-Éric Racine (q-funk)]

When running under GDB:
-----
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/gnome-phone-manager
[Thread debugging using libthread_db enabled]
[New Thread 0xb6633760 (LWP 7319)]
** Message: bdaddr 00:1A:75:B6:58:D1
** Message: New connection device is 00:1A:75:B6:58:D1 (changed)
** Message: New connection device is 00:1A:75:B6:58:D1 (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
[New Thread 0xb642ab90 (LWP 7327)]
** Message: Using serial channel -1 for device 00:1A:75:B6:58:D1
** Message: Failed connection to device on 00:1A:75:B6:58:D1
** Message: Exiting connect thread
-----

When running normally from command line:
-----
** Message: bdaddr 00:1A:75:B6:58:D1
** Message: New connection device is 00:1A:75:B6:58:D1 (changed)
** Message: New connection device is 00:1A:75:B6:58:D1 (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
conn_complete: status 0x00
** Message: starting search
** Message: Using serial channel 2 for device 00:1A:75:B6:58:D1
** Message: Model Sony Ericsson K750 using default driver
** Message: Using driver 'AT'
** Message: Status 2
** Message: Serial port connected
** Message: Connected to device on 00:1A:75:B6:58:D1
** Message: Exiting connect thread
** Message: Our own phone number is:
** Message: driver and phone support sms notifications
** Message: emitting network info
** Message: emitting battery
-----
This is what I meant by fails to connect. Access Denied when executing under GDB, but allowed when running normally from command line. Until we can get a connection to my phone under GDB, we won't be able to get a backtrace on failing to send an SMS.

[dino99 (9d9)]

This version has expired long time ago, and is no more supported