Bug 4899 - Gedit crashes in gtk+3.0 on drag & drop
Summary: Gedit crashes in gtk+3.0 on drag & drop
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-03-12 13:38 CET by Herbert Poetzl
Modified: 2012-08-03 20:20 CEST (History)
4 users (show)

See Also:
Source RPM: gtk+3.0
CVE:
Status comment:


Attachments
GDB stack trace of crashing gedit (1.62 KB, text/plain)
2012-03-29 17:35 CEST, Herbert Poetzl
Details
GDB stack trace of crashing gedit 3.4.0-1 (1.65 KB, text/plain)
2012-04-15 06:41 CEST, Herbert Poetzl
Details

Description Herbert Poetzl 2012-03-12 13:38:03 CET
Description of problem:
under certain circumstances, a drag & drop crashes gedit

Version-Release number of selected component (if applicable):
gedit-3.3.7-1.mga2.x86_64
lib64gtk+-x11-2.0_0-2.24.10-3.mga2.x86_64
lib64x11_6-1.4.99.1-2.mga2.x86_64

How reproducible:
always

Steps to Reproduce:
1. use epiphany to 'load' http://vserver.13thfloor.at/test.php
   (this will open the test.txt in gedit on gnome3 by default)
2. drag the tab to a terminal or filemanager
3.
Comment 1 Manuel Hiebel 2012-03-12 18:17:07 CET
Can you attach a gdb strace please ?

Keywords: (none) => NEEDINFO

Comment 2 Herbert Poetzl 2012-03-12 20:23:32 CET
Program received signal SIGSEGV, Segmentation fault.
0x00007f0097c4bbf0 in XVisualIDFromVisual () from /usr/lib64/libX11.so.6
(gdb) where
#0  0x00007f0097c4bbf0 in XVisualIDFromVisual () from /usr/lib64/libX11.so.6
#1  0x00007f00988f2ecb in gdk_x11_window_foreign_new_for_display (display=
    0x1889010 [GdkX11Display], window=29360133) at gdkwindow-x11.c:933
#2  0x00007f00988df642 in gdk_x11_drag_context_find_window (context=
    0x1c461f0 [GdkX11DragContext], drag_window=0x1889010 [GdkX11Display], 
    screen=<optimized out>, x_root=936, y_root=609, protocol=0x7fffbd5f3644)
    at gdkdnd-x11.c:3325
#3  0x00007f00988b5434 in gdk_drag_find_window_for_screen (context=
    0x1c461f0 [GdkX11DragContext], drag_window=0x203ba20 [GdkX11Window], 
    screen=0x18900c0 [GdkX11Screen], x_root=936, y_root=609, dest_window=
    0x7fffbd5f3638, protocol=0x7fffbd5f3644) at gdkdnd.c:277
#4  0x00007f009902c36f in gtk_drag_update_idle (data=0x20ad240)
    at gtkdnd.c:4098
#5  0x00007f00988acd0f in gdk_threads_dispatch (data=<optimized out>)
    at gdk.c:763
#6  0x00007f0096d6eb0a in g_main_dispatch (context=0x1898f70) at gmain.c:2510
#7  g_main_context_dispatch (context=0x1898f70) at gmain.c:3047
#8  0x00007f0096d6eed0 in g_main_context_iterate (dispatch=1, 
    block=<optimized out>, context=0x1898f70, self=<optimized out>)
    at gmain.c:3118
#9  g_main_context_iterate (context=0x1898f70, block=<optimized out>, dispatch=
    1, self=<optimized out>) at gmain.c:3055
#10 0x00007f0096d6f2ca in g_main_loop_run (loop=0x1efba00) at gmain.c:3312
#11 0x00007f0098ec0f4d in gtk_main () at gtkmain.c:1161
#12 0x00000000004281bc in gedit_main (service=<optimized out>) at gedit.c:205
#13 main (argc=1, argv=0x7fffbd5f38f8) at gedit.c:331

CC: (none) => herbert

Comment 3 Marja Van Waes 2012-03-29 08:33:56 CEST
(In reply to comment #2)
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007f0097c4bbf0 in XVisualIDFromVisual () from /usr/lib64/libX11.so.6
> (gdb) where
> #0  0x00007f0097c4bbf0 in XVisualIDFromVisual () from /usr/lib64/libX11.so.6

cc'ing Thierry, who committed libX11 most often.

Keywords: NEEDINFO => (none)
CC: (none) => marja11, olav, thierry.vignaud
Source RPM: gedit-3.3.7-1.mga2.src.rpm => libx11-1.4.99.1-2.mga2.src.rpm gedit-3.3.7-1.mga2.src.rpm

Comment 4 Thierry Vignaud 2012-03-29 09:39:52 CEST
Please attach (not paste) GDB trace after having installed missing debug packages (at least libx11-debug)

Keywords: (none) => NEEDINFO

Comment 5 Herbert Poetzl 2012-03-29 17:35:08 CEST
Created attachment 1887 [details]
GDB stack trace of crashing gedit
Comment 6 Thierry Vignaud 2012-03-29 21:31:56 CEST
It's gedit bug that pass a NULL pointer...

Source RPM: libx11-1.4.99.1-2.mga2.src.rpm gedit-3.3.7-1.mga2.src.rpm => gedit-3.3.7-1.mga2.src.rpm

Comment 7 Olav Vitters 2012-03-29 21:35:01 CEST
$ rpm -q gedit
gedit-3.4.0-1.mga2

Please install *all* updates. Especially gedit + gtk+3.0.
Comment 8 Herbert Poetzl 2012-03-29 23:00:07 CEST
# urpmi.update -a
# urpmi --auto-select

$ rpm -qa | egrep 'gedit|gtk\+3.0'
gtk+3.0-3.4.0-1.mga2.x86_64
gedit-3.4.0-1.mga2.x86_64
lib64gtk+3_0-3.4.0-1.mga2.x86_64
gtk+3.0-debug-3.4.0-1.mga2.x86_64
lib64gedit0-3.4.0-1.mga2.x86_64
gedit-debug-3.4.0-1.mga2.x86_64
Comment 9 Marja Van Waes 2012-04-14 22:40:48 CEST
@ Herbert

gedit-3.4.0-1.mga2 hit the mirrors on ± March 27th, had you already updated to it when you got that gdb trace in comment 5 ?

Or, in other words: do you still have those crashes?
Comment 10 Herbert Poetzl 2012-04-15 06:36:49 CEST
yes, I still have those crashes, they are trivial to trigger with a single click and drag.

capturing the gdb trace is a little trickier, thus I'll attach a recent one.
Comment 11 Herbert Poetzl 2012-04-15 06:41:46 CEST
Created attachment 1996 [details]
GDB stack trace of crashing gedit 3.4.0-1
Comment 12 Marja Van Waes 2012-04-15 09:33:37 CEST
Thanks, asigning to maintainer

BTW, Herbert, does it crash too when you log in as a different user? I noticed I have some gedit stuff in my /home/marja/.gconf/apps/ directory (in Mga 1, but I suppose it won't be much different in cauldron)

Assignee: bugsquad => olav
Source RPM: gedit-3.3.7-1.mga2.src.rpm => gedit-3.4.0-1.mga2.src.rpm

Comment 13 Olav Vitters 2012-04-15 15:04:06 CEST
it crashes in gtk+, not gedit.
Marja Van Waes 2012-05-02 09:08:02 CEST

Keywords: NEEDINFO => (none)
Summary: Gedit crashes on drag & drop => Gedit crashes in gtk+3.0 on drag & drop
Source RPM: gedit-3.4.0-1.mga2.src.rpm => gtk+3.0

Comment 14 Marja Van Waes 2012-05-26 13:09:12 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 15 Marja Van Waes 2012-07-06 15:05:35 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 16 Marja Van Waes 2012-08-03 20:20:01 CEST
2x no reply, closing as old

Feel free to reopen if needed and tell in which fully updated Mageia version(s) you still have this issue

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.