https://bugzilla.novell.com/show_bug.cgi?id=661370 https://bugzilla.novell.com/show_bug.cgi?id=661370#c0 Summary: Inkscape 0.48 Crashes when Opening Document Properties Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: andi@opensuse-id.org QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b7) Gecko/20101105 Firefox/4.0b7 The upstream bug-tracker has the issue[0] reported already, Inkscape 0.48 crashes when opening 'Document Properties' (menu: File - Document Properties) like this: http://picasaweb.google.com/andisugandi/OpenSUSE#5554112159829885570 The error when running it (then opening 'Document Properties') on Konsole: +++++
inkscape terminate called after throwing an instance of 'Gtk::IconThemeError'
Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. ++++ Changing GTK Styles (System Settings, go to: Application Appearance, choose: GTK Styles and Fonts) to other style except Oxygen-molecule (I tried Sonar), solves the issue. It runs on openSUSE Factory:
cat /etc/SuSE-* openSUSE VERSION = 11.4 openSUSE 11.4 Milestone 5 of 6 (x86_64) VERSION = 11.4 CODENAME = Celadon
rpm -q inkscape inkscape-0.48.0-17.1.x86_64
[0] https://bugs.launchpad.net/inkscape/+bug/658055 Reproducible: Always Steps to Reproduce: 1. Run: openSUSE Factory 2. Run: Inkscape 3. Open: menu: File, Document Properties Actual Results: Inkscape crashes, and pop-up a window that tells: "Inkscape encountered an internal error and will close now." Expected Results: It should open the 'Document Properties' without problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.