gdb crashed with ImportError in /usr/lib/debug/usr/lib/libreoffice/program/libsvllo.so-gdb.py: No module named libreoffice.svl

Bug #1026941 reported by Daniel Winzen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I started libreoffice writer, but it didn't start, instead I got an message from apport, that gdb crashed. Maybe it is because libreoffice is not fully upgraded, because of dependency-problems.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gdb 7.4-2012.06-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-5.5-generic 3.5.0-rc7
Uname: Linux 3.5.0-5-generic x86_64
ApportVersion: 2.4-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Fri Jul 20 09:20:40 2012
ExecutablePath: /usr/bin/gdb
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
ProcCmdline: gdb --batch --ex file\ "/usr/lib/libreoffice/program/soffice.bin" --ex core-file\ /tmp/tmpuj9c2g --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ __abort_msg->msg
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gdb
Title: gdb crashed with ImportError in /usr/lib/debug/usr/lib/libreoffice/program/libsvllo.so-gdb.py: No module named libreoffice.svl
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/debug/usr/lib/libreoffice/program/libsvllo.so-gdb.py", line 39, in <module>
     from libreoffice.svl import register_pretty_printers
 ImportError: No module named libreoffice.svl
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Daniel Winzen (q-d-deactivatedaccount) wrote :
visibility: private → public
tags: removed: need-duplicate-check
Changed in gdb (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Matthias Klose (doko) wrote :

closing this rather old issue. sorry for not addressing this earlier. Please could you recheck with the recent 14.04 LTS or 14.10 releases and reopen the issue if the problem persists?

Changed in gdb (Ubuntu):
status: New → Invalid
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.