Ubuntu
openoffice.org package

open office crashed on upgrade mailmerge

Bug #527437 reported by rlyle on 2010-02-24

This bug report is a duplicate of: Bug #450569: [Master] package openoffice.org-emailmerge 1:3.2.0-7ubuntu4.1 failed to install/upgrade:. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	openoffice.org (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: ubuntuone-client

open office update

ProblemType: Bug
.home.plyle..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.plyle..config.ubuntuone.syncdaemon.conf:
[bandwidth_throttling]
on = False
read_limit = 0
write_limit = 0
.home.plyle..config.ubuntuone.ubuntuone.client.conf:
[ubuntuone]
connected = False
connect = 0
show_applet = 1
bookmarked = True
Architecture: i386
Date: Wed Feb 24 16:42:06 2010
DistroRelease: Ubuntu 9.10
Package: ubuntuone-client 1.0.3-0ubuntu1
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: ubuntuone-client
Uname: Linux 2.6.31-19-generic i686
XsessionErrors:
(gnome-settings-daemon:1978): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
(polkit-gnome-authentication-agent-1:2075): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:2063): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

Tags:

Revision history for this message

rlyle (rlyle) wrote on 2010-02-24:

.home.plyle..cache.ubuntuone.log.oauth.login.log.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
UbuntuoneClientPackages.txt Edit (207 bytes, text/plain; charset="utf-8")

Revision history for this message

Mitch Towner (kermiac) wrote on 2010-02-24:

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 450569, so it is being marked as such. 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. Please continue to report any other bugs you may find.