"Add Layer" from Layers panel Cancel crash

Bug #977938 reported by Daniel Anken
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
High
Unassigned

Bug Description

Inkscape version : 0.48.3.1 r9886
OS : Arch Linux (kernel 3.3.1), KDE 4.8.2, Oxygen-gtk for GTK applications
Language : English

Inkscape crashes when I cancel the creation of a new layer, after having pressed the '+' button from the Layers panel.
This crash does not occur when a new layer is created from the 'Layer' menu, nor when using the Shift+Ctrl+N shortcut.

It happens everytime I test.

Steps :
1. Open Inkscape (blank document)
2. Open the Layers panel
3. Click the 'Create a new layer' [+] button
4. Click on 'Cancel' in the opened 'Add Layer' dialog box
5. Inkscape crashes

Debug output from gdb :
Starting program: /usr/bin/inkscape
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0x7fffea557700 (LWP 10030)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff1846678 in __dynamic_cast () from /usr/lib/libstdc++.so.6
(gdb) bt
#0 0x00007ffff1846678 in __dynamic_cast () from /usr/lib/libstdc++.so.6
#1 0x00007ffff7a1949f in Gtk::Container_Class::forall_vfunc_callback(_GtkContainer*, int, void (*)(_GtkWidget*, void*), void*) () from /usr/lib/libgtkmm-2.4.so.1
#2 0x00007ffff5c84ec5 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#3 0x00007ffff5c8705b in gtk_widget_queue_draw () from /usr/lib/libgtk-x11-2.0.so.0
#4 0x00007fffea966860 in Oxygen::WidgetStateData::delayedUpdate(void*) ()
   from /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so
#5 0x00007fffea960eed in Oxygen::TimeLine::update() () from /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so
#6 0x00007fffea961609 in Oxygen::TimeLineServer::update(void*) ()
   from /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so
#7 0x00007ffff425709b in ?? () from /usr/lib/libglib-2.0.so.0
#8 0x00007ffff42558bd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9 0x00007ffff42560b8 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x00007ffff42565f2 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff5b63637 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x0000000000653130 in sp_main_gui(int, char const**) ()
#13 0x00000000006385b8 in main ()
(gdb)

I don't know if this bug exists on other platforms.
I haven't tested on the latest development version either (not yet, at least).

Tags: crash layers ui
Revision history for this message
jazzynico (jazzynico) wrote :

Not reproduced on Windows XP, Inkscape 0.48.3.1 and trunk revision 11205.

tags: added: crash layers ui
Changed in inkscape:
importance: Undecided → High
Revision history for this message
su_v (suv-lp) wrote :

> I don't know if this bug exists on other platforms.

Could you test with the stock Gtk+ theme 'Raleigh', whether the crash still occurs?

(other reported crashes with oxygen-gtk theme under KDE: e.g. bug #948178, bug #952971)

Revision history for this message
su_v (suv-lp) wrote :

Not reproduced on Mac OS X 10.5.8 (32bit, glib2 2.28.8) and OS X 10.7.2 (64bit, glib 2.32.0), with Inkscape 0.48.3.1 and trunk revision 11208, testing with Raleigh, Murrine, Clearlooks, Mist, Equinox and Aurora theme engine.

Revision history for this message
Daniel Anken (daniel-anken) wrote :

Yeah right, the crash does not occur with other Gtk themes.
I tested the ones I have and it worked fine (Raleigh, Clearlook, Mist, ...).

Shall I report the bug directly to the Oxygen-Gtk (KDE) team ?

Revision history for this message
Daniel Anken (daniel-anken) wrote :

I just tested with the devel version of inkscape (from Archlinux's AUR - 0.48+devel r11233), and strangely enough, the crash occurs only after repeating the operation twice.
I mean :
1. Click add a new layer
2. Cancel
3. Click add a new layer, again
4. Cancel
=> crash.

As far as I can see, the crash output is the same, except the 2 last lines :

#0 0x00007ffff1835678 in __dynamic_cast () from /usr/lib/libstdc++.so.6
#1 0x00007ffff6d4249f in Gtk::Container_Class::forall_vfunc_callback(_GtkContainer*, int, void (*)(_GtkWidget*, void*), void*) () from /usr/lib/libgtkmm-2.4.so.1
#2 0x00007ffff5cefec5 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#3 0x00007ffff5cf205b in gtk_widget_queue_draw () from /usr/lib/libgtk-x11-2.0.so.0
#4 0x00007fffea966860 in Oxygen::WidgetStateData::delayedUpdate(void*) ()
   from /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so
#5 0x00007fffea960eed in Oxygen::TimeLine::update() () from /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so
#6 0x00007fffea961609 in Oxygen::TimeLineServer::update(void*) ()
   from /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so
#7 0x00007ffff1b2309b in ?? () from /usr/lib/libglib-2.0.so.0
#8 0x00007ffff1b218bd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9 0x00007ffff1b220b8 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x00007ffff1b225f2 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff5bce637 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x00000000006a2fdb in sp_main_gui(int, char const**) ()
#13 0x00007ffff1164455 in __libc_start_main () from /lib/libc.so.6
#14 0x00000000006a0601 in _start ()

Revision history for this message
su_v (suv-lp) wrote :

Daniel Anken wrote:
> Yeah right, the crash does not occur with other Gtk themes.
> I tested the ones I have and it worked fine (Raleigh, Clearlook, Mist, ...).
>
> Shall I report the bug directly to the Oxygen-Gtk (KDE) team ?

Sorry for the delayed response - yes, it would be much appreciated if you report it directly for Oxygen-Gtk.

Revision history for this message
Daniel Anken (daniel-anken) wrote :

Well, (sorry for my delayed response as well)
I just checked with the latest devel version (Inkscape 0.48+devel r11535, under ArchLinux) and the bug seems to be fixed.
I can't reproduce it.

Inkscape 0.48+devel r11535 (latest bazaar updates)
Oxygen-gtk2 1.2.5-1
KDE 4.8.4
ArchLinux kernel 3.4.4

Unless somebody else reproduces the bug, it can be closed.

Thank you for your time.

Revision history for this message
su_v (suv-lp) wrote :

> Inkscape 0.48+devel r11535 (latest bazaar updates)
> Oxygen-gtk2 1.2.5-1

Is this the same version you had installed at the time you reported the crash? Any chance you could test with stable Inkscape 0.48.3.1 too, so that we get a clue whether this is indeed due to (undefined) changes in Inkscape trunk, or due to changes in Oxygen-gtk2 (as has happened for other similar reports, see comment #2)?

Revision history for this message
Daniel Anken (daniel-anken) wrote :

Ok as far as I can see in my pacman.log (package manager's log), the Oxygen-gtk2 version I had installed when I reported the bug was 1.2.2-1.

I just checked with the stable Inkscape 0.48.3.1 :
the bug is still here BUT only if I open a new (blank) document, click 'create new layer' and cancel.
As soon as I add another layer, and then test again, I can't reproduce the bug, even if I delete the layer I just created afterwards.
I couldn't reproduce the bug in 'non-blank' svg files (tested with some of my realisations --> no problem).

The bug stack is also much smaller than it used to be :

Starting program: /usr/bin/inkscape
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3200.3-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff178c7f8 in __dynamic_cast () from /usr/lib/libstdc++.so.6
(gdb)

I'm currently building the latest bazaar version to do some more testing.
Will post the details soon.

Revision history for this message
Daniel Anken (daniel-anken) wrote :

Uh... Alright, now it gets tricky...

Just tested with the latest bazaar fetch - Inkscape 0.48+devel r11547 custom (Jul 13 2012) - and strangely enough, I can reproduce the bug :-/

I guess I missed it, because it only occurs after doing the "new layer - cancel" operation around 6 to 10 times, randomly.
And it does occur wether it is a blank document or a multi layer document.

The error is the same as for the 0.48.3.1 version :
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff103c7f8 in __dynamic_cast () from /usr/lib/libstdc++.so.6

I also tested with other GTK themes, and the bug still does not occur.
So I guess I'll notify the oxygen-gtk team.

Revision history for this message
su_v (suv-lp) wrote :

> So I guess I'll notify the oxygen-gtk team.

Did you receive any feedback from the oxygen-gtk team about the issue?

Changed in inkscape:
status: New → Incomplete
Revision history for this message
Daniel Anken (daniel-anken) wrote :

Oh yeah sorry !
It was indeed a oxygen-gtk linked issue.
(Apparently the problem was due to Oxygen animations)

https://bugs.kde.org/show_bug.cgi?id=303459

The bug has been solved :-)
Thanks for your help !

Kind regards

Revision history for this message
su_v (suv-lp) wrote :

> It was indeed a oxygen-gtk linked issue. (…)
> The bug has been solved :-)

Thanks for reporting it upstream in Oxygen-gtk, and providing feedback about the current status, much appreciated!

Closing report as 'Invalid' for Inkscape.

Changed in inkscape:
status: Incomplete → 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.