dia seg faults on startup

Bug #597264 reported by Tom Haddon
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dia (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: dia

Here's what I get on starting up dia:

$ dia

** (dia:10668): CRITICAL **: menu_proxy_module_load: assertion `dbusproxy != NULL' failed
Segmentation fault

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: dia 0.97.1-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Tue Jun 22 14:31:25 2010
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: dia

Revision history for this message
Tom Haddon (mthaddon) wrote :
Revision history for this message
Krishna (krishnab) wrote :

This is the output on Terminal When I start dia

progname=dia; RGBA=on

(dia:25538): Gdk-WARNING **: Attempt to draw a drawable with depth 24 to a drawable with depth 32
sys:1: GtkWarning: IA__gtk_pixmap_set: assertion `gdk_colormap_get_visual (gtk_widget_get_colormap (GTK_WIDGET (pixmap)))->depth == gdk_drawable_get_depth (GDK_DRAWABLE (val))' failed
sys:1: GtkWarning: IA__gtk_drag_source_set_icon: assertion `GDK_IS_PIXMAP (pixmap)' failed
Segmentation fault

Revision history for this message
penalvch (penalvch) wrote :

Tom Haddon, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in dia (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.