libreoffice draw / impress crash if user service publishing is disabled in avahi

Bug #1328908 reported by Sven Mueller
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
New
Medium
Unassigned

Bug Description

Crash report for bug #1319941

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Apr 17 05:17:06 2014
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
ExecutableTimestamp: 1397067724
InstallationDate: Installed on 2014-04-17 (0 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204)
ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --draw --splash-pipe=5
ProcCwd: /home/smu
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: libreoffice
StacktraceTop:
 __assert_fail_base (fmt=0x7f0db38b4718 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f0da8b2d919 "client", file=file@entry=0x7f0da8b2d910 "client.c", line=line@entry=626, function=function@entry=0x7f0da8b2dfe0 "avahi_client_free") at assert.c:92
 __GI___assert_fail (assertion=0x7f0da8b2d919 "client", file=0x7f0da8b2d910 "client.c", line=626, function=0x7f0da8b2dfe0 "avahi_client_free") at assert.c:101
 avahi_client_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 ?? () from /usr/lib/libreoffice/program/../program/libsdlo.so
 ?? () from /usr/lib/libreoffice/program/../program/libsdlo.so
Title: soffice.bin crashed with SIGABRT in __assert_fail_base()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Sven Mueller (smu-u) wrote :
information type: Private → Public
penalvch (penalvch)
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0x7f0db38b4718 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f0da8b2d919 "client", file=file@entry=0x7f0da8b2d910 "client.c", line=line@entry=626, function=function@entry=0x7f0da8b2dfe0 "avahi_client_free") at assert.c:92
 __GI___assert_fail (assertion=0x7f0da8b2d919 "client", file=0x7f0da8b2d910 "client.c", line=626, function=0x7f0da8b2dfe0 "avahi_client_free") at assert.c:101
 avahi_client_free () from /tmp/apport_sandbox_wk9CF1/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 sd::AvahiNetworkService::clear (this=<optimized out>) at /build/buildd/libreoffice-4.2.3~rc3/sd/source/ui/remotecontrol/AvahiNetworkService.cxx:189
 create_services (c=0x1f3d700) at /build/buildd/libreoffice-4.2.3~rc3/sd/source/ui/remotecontrol/AvahiNetworkService.cxx:90

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libreoffice (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Sven Mueller (smu-u) wrote :

Could you please at least comment why you think this is not a duplicate of the bug I linked it to?

Revision history for this message
Sven Mueller (smu-u) wrote :

For the record, I think it is a duplicate and exact reproduction of the case described in: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1319941

Philipp Kern (pkern)
description: updated
Revision history for this message
Philipp Kern (pkern) wrote :

So I pointed out on the bug this was duplicated to why I did that. I find it tiring that you still chose to fight the duplication without any comment. Can you please provide a rationale? Otherwise I'll dupe it to the other bug again. Thanks.

Revision history for this message
penalvch (penalvch) wrote :

Philipp Kern, thanks for your comment. The triage preference is when a bug is marked Invalid due to no crash report, it's not resurrected and then triaged again because someone reported the crash via apport. I'll mark it duplicate as you are the point on this (please feel free mark yourself Assigned at the top of the MASTER report).

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.