gnome-phone-manager crashed with SIGSEGV in gn_sms_send()

Bug #404277 reported by Tanguy Le Meur
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-phone-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: gnome-phone-manager

I tried to send a SMS but gnome-phone-manager crashed when I send it.
Just before crash my phone (a Samsung D900) tells me that I had to use Samsung studio.

I remember that gnome-phone-manager works many months ago with my phone (with certainly another version). Perhaps is it a regression ?

If it is not possible to have the application working with my phone, it should be telling me it is not possible and not crashing.

Thank you for help :-)

It is my first bug report, so be aware to ask me more information !

ProblemType: Crash
Architecture: amd64
Date: Fri Jul 24 21:07:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-phone-manager
NonfreeKernelModules: nvidia
Package: gnome-phone-manager 0.65-1
ProcCmdline: gnome-phone-manager
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SegvAnalysis:
 Segfault happened at: 0x7f34172f6a85 <gn_sms_send+149>: mov 0x18(%rdx),%edx
 PC (0x7f34172f6a85) ok
 source "0x18(%rdx)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-phone-manager
StacktraceTop:
 gn_sms_send () from /usr/lib/libgnokii.so.4
 phonemgr_listener_queue_message ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gnome-phone-manager crashed with SIGSEGV in gn_sms_send()
Uname: Linux 2.6.31-3-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Tanguy Le Meur (tanguy) wrote :
Revision history for this message
Tanguy Le Meur (tanguy) wrote :

Since this report, I tried to use gnome-bluetooth instead of bluez-gnome.

Well, it is better because gnome-phone-manager didn't crash.

My phone displayed the same message, so I think my message was not sent (I am not sure).

Finally is gnome-phone-manager in conflict with bluez-gnome ?
Also gnome-bluetooth should be more verbose and tell us "Your message was sent" (or not). If not the message must not be lost :-( I have to rewrite it each time it fail.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-phone-manager (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Tanguy Le Meur (tanguy) wrote :

Well, it is quite difficult to do all of this...

I'm unable to use gnome-phone-manager with gdb, it doesn't connect to my phone (but
without gdb it does)

This are the messages:

 gdb gnome-phone-manager 2>&1 | tee ~/gdb-gnome-phone-manager.txt
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
(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 0x7fffe6756950 (LWP 5747)]
[New Thread 0x7fffe5f55950 (LWP 5749)]
** Message: New connection device is 00:18:AF:0E:95:3C (changed)
** Message: New connection device is 00:18:AF:0E:95:3C (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
** Message: starting search
** Message: Using serial channel 2 for device 00:18:AF:0E:95:3C
Can't connect: Appel système interrompu
[New Thread 0x7fffe5cae950 (LWP 5752)]

** (gnome-phone-manager:5744): WARNING **: gn_gsm_initialise: Command failed
** Message: La connexion au périphérique sur 00:18:AF:0E:95:3C a échoué
** Message: Exiting connect thread

Revision history for this message
Tanguy Le Meur (tanguy) wrote :

Okay using valgrind and bluez-gnome the message was sent.

Hum, I should sleep now. I don't understand anything !

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-phone-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-phone-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.