ubuntuone-login crashed with SIGSEGV

Bug #525064 reported by ec on 2010-02-20
This bug affects 263 people
Affects Status Importance Assigned to Milestone
ubuntuone-client (Ubuntu)
Ubuntu One Foundations+ team

Bug Description

Binary package hint: ubuntuone-client

This occured while trying to open ubuntuone preferences through 'System' -> 'Preferences' -> 'Ubuntu One'

Ubuntu lucid (development branch) \n \l
Linux cd-a03-5 2.6.32-13-generic #18-Ubuntu SMP Wed Feb 10 21:32:38 UTC 2010 x86_64 GNU/Linux

  Geïnstalleerd: 1.1.2-0ubuntu1
  Kandidaat: 1.1.2-0ubuntu1
 *** 1.1.2-0ubuntu1 0
        500 http://nl.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash

 on = False
 read_limit = 0
 write_limit = 0
 bookmarked = True
 connected = True
 connect = 0
 show_applet = 0
Architecture: amd64
Date: Sat Feb 20 22:38:00 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/ubuntuone-client/ubuntuone-login
InterpreterPath: /usr/bin/python2.6
Package: ubuntuone-client-gnome 1.1.2-0ubuntu1
ProcCmdline: /usr/bin/python /usr/lib/ubuntuone-client/ubuntuone-login
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
 Segfault happened at: 0x7f613ec824e0: movl $0xffffffff,0x4(%rdi)
 PC (0x7f613ec824e0) ok
 source "$0xffffffff" ok
 destination "0x4(%rdi)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: ubuntuone-client
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
Title: ubuntuone-login crashed with SIGSEGV
Uname: Linux 2.6.32-13-generic x86_64
UserGroups: admin fuse libvirtd

ec (ecroes) wrote :
visibility: private → public

 _dbus_watch_invalidate (watch=0x0) at dbus-watch.c:153
 free_watches (transport=0x2e4fc70)
 socket_disconnect (transport=0x0)
 _dbus_transport_disconnect (transport=0x2e4fc70)
 _dbus_transport_queue_messages (transport=0x2e4fc70)

Changed in ubuntuone-client (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Windle (vindellepounze) wrote :

Starting ubuntu one through task bar not 'System' -> 'Preferences' -> 'Ubuntu One'

Joshua Blount (jblount) on 2010-03-02
Changed in ubuntuone-client (Ubuntu):
status: New → Triaged
assignee: nobody → Ubuntu One Foundations+ team (ubuntuone-foundations+)
tags: added: foundations+
Blümchen Blau (bluemchen-blau) wrote :

You're lucky: I have no icon in task-bar at all! :-)
Never seen in this lucid installation.

ec (ecroes) wrote :

After upgrading the package to version 1.1.2-0ubuntu2, the crash keeps occuring

  Geïnstalleerd: 1.1.2-0ubuntu2
  Kandidaat: 1.1.2-0ubuntu2
 *** 1.1.2-0ubuntu2 0
        500 http://nl.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

Same problem here, after launching from "me-menu".

Uncle Spellbinder (spellbinder) wrote :

Same issue here. Seems OK launching from 'System' -> 'Preferences' -> 'Ubuntu One'. But the "me menu" is a no-go

Might be related to https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/530541 ?

Although I can't find out if Ubuntu One does use CouchDB (it's not listed as a dependency).

Ben Romer (bromer) wrote :

I get this problem when launching from the System preferences, and the Me menu link works just fine...

Tommaso R. Donnarumma (tawmas) wrote :

The problem can be worked around by killing the syncdaemon and then editing your ~/.config/ubuntuone/syncdaemon.conf file to comment out the following two lines in the [bandwidth_throttling] section:

read_limit = 0
write_limit = 0

The newer version of the sync daemon doesn't like those limits to be zero even when bandwidth throttling is disabled.

Andrea Caminiti (nrayever) wrote :

Same issue here. Seems OK launching from 'System' -> 'Preferences' -> 'Ubuntu One'.

CPKS (c-1) wrote :

I fixed the problem by killing the syncdaemon, deleting ~/.config/ubuntuone/syncdaemon.conf* and restarting the daemon. Running the Preferences app then rewrites a valid .conf file.

description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers