ubuntuone-login crashed with SIGSEGV in dbus_watch_handle()

[Robbie Williamson]

Binary package hint: ubuntuone-client

Selected "Ubuntu One" in the Me Menu...and crash :/. I did, however, get the U1 information window presented.

ProblemType: Crash
.home.robbiew..config.ubuntuone.syncdaemon.conf:
 [bandwidth_throttling]
 read_limit = 65536
 write_limit = 0
 on = False
.home.robbiew..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 bookmarked = True
 connected = False
 connect = 0
 show_applet = 0
Architecture: amd64
Date: Wed Mar 10 10:28:09 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InterpreterPath: /usr/bin/python2.6
Package: ubuntuone-client-gnome 1.1.3-0ubuntu1
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-16.24-generic
SegvAnalysis:
 Segfault happened at: 0x7fb7b11351b0: mov 0x34(%rdi),%eax
 PC (0x7fb7b11351b0) ok
 source "0x34(%rdi)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntuone-client
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_watch_handle () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libgnome-keyring.so.0
Title: ubuntuone-login crashed with SIGSEGV in dbus_watch_handle()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

python2.6: installed version 2.6.4-6ubuntu1, latest version: 2.6.5~rc2-0ubuntu1
libgtk2.0-common: installed version 2.19.6-1ubuntu4, latest version: 2.19.7-0ubuntu1
klibc-utils: installed version 1.5.15-1ubuntu2, latest version: 1.5.15-1ubuntu4
libdbus-glib-1-2: installed version 0.82-2, latest version: 0.84-1
ubuntuone-client: installed version 1.1.3-0ubuntu1, latest version: 1.1.4-0ubuntu1
libklibc: installed version 1.5.15-1ubuntu2, latest version: 1.5.15-1ubuntu4
python-problem-report: installed version 1.12.1-0ubuntu5, latest version: 1.13-0ubuntu2
dpkg: installed version 1.15.5.6ubuntu1, latest version: 1.15.5.6ubuntu2
python-apport: installed version 1.12.1-0ubuntu5, latest version: 1.13-0ubuntu2
xdg-utils: installed version 1.0.2-6.1ubuntu2, latest version: 1.0.2-6.1ubuntu3
ubuntuone-client-gnome: installed version 1.1.3-0ubuntu1, latest version: 1.1.4-0ubuntu1
libnautilus-extension1: installed version 1:2.29.92-0ubuntu1, latest version: 1:2.29.92.1-0ubuntu1
python2.6-minimal: installed version 2.6.4-6ubuntu1, latest version: 2.6.5~rc2-0ubuntu1
python-ubuntuone-client: installed version 1.1.3-0ubuntu1, latest version: 1.1.4-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[Duane Hinnen (duanedesign)]

Robbie,
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 368626 , so it is being marked as such. The problem is some of your files have non UTF8 characters in them. I have a script you can use to locate these files. It will make it a little easier to locate the offending files. If you wish to use it please run the following commands in a Terminal (Applications > Accesories > Terminal):

1. wget http://people.ubuntu.com/~duanedesign/utf8-filename-check.py

2. python utf8-filename-check.py

Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

When your bug is marked as a duplicate, you become a subscriber of the other bug report and you will start receiving all messages that are related to the original bug report. You can unsubscribe from your bug at any time.

thank you,
duanedesign

[Duane Hinnen (duanedesign)]

Robbie,
Please disregard post #6. I posted that reply to the wrong bug. The UTF8 encoding problem definitely has nothing to do with your report. I apologize for any possible confusion this might have created.
thank you,
duanedesign

[Jason S. Wagner (jasonswagner)]

Reproduced on Lucid Beta 1. I told Launchpad that this is the same bug, so hopefully it linked my trace to this bug for further triage.

[dino99 (9d9)]

This version is outdated and no more supported