abrt 1.0.7 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/nm-connection-editor --type vpn component: NetworkManager executable: /usr/bin/nm-connection-editor kernel: 2.6.32.9-67.fc12.x86_64 package: NetworkManager-gnome-1:0.7.998-2.git20100106.fc12 rating: 4 reason: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. 1 added 2 vpn connections (my first ones) via network-applet 2. i connected to one vpn - it works, then disconnected after a minute 3. i changed the name for my ethernet-connection and the crash happens. i was connected wia wlan all the time
Created attachment 398350 [details] File: backtrace
How to reproduce ----- 1. Open NM 2. Set connecting to Eth0 automatically at startup (it might be not set before the operation) 3. Badaboum !
Created attachment 405253 [details] gdb backtrace of a crash I've managed to reproduce the bug. Unfortunately only once. When I tried again (several times) no crash occured. What I did: 1. Have a wired connection activated ("Connect automatically" and "Available to all users" checked). 2. Open nm-connection-editor 3. Find my active connection in "Wired" tab 4. Click on it, click "Edit" button 5. Change the connection name 6. Click "Apply" 7. *Crash* Components: NetworkManager-gnome-0.7.998-2.git20100106.fc12.x86_64 NetworkManager-0.7.998-2.git20100106.fc12.x86_64 gtk2-2.18.9-2.fc12.x86_64 libX11-1.3-1.fc12.x86_64 libxcb-1.5-1.fc12.x86_64
It is probably gtk/X11 issue connected with a tooltip. #0 0x000000387004d4f8 in insert_pending_request (dpy=0x968200, rep=0x7fff282fa330, extra=0, discard=1) at xcb_io.c:417 #1 _XReply (dpy=0x968200, rep=0x7fff282fa330, extra=0, discard=1) at xcb_io.c:451 #2 0x000000387003acf0 in XQueryPointer (dpy=0x968200, w=29488517, root=0x7fff282fa4c8, child=0x7fff282fa4c0, root_x=0x7fff282fa4ec, root_y=0x7fff282fa4e8, win_x=<value optimized out>, win_y=<value optimized out>, mask=<value optimized out>) at QuPntr.c:50 #3 0x0000003633a7344d in _gdk_windowing_window_at_pointer (display=<value optimized out>, win_x=<value optimized out>, win_y=<value optimized out>, mask=<value optimized out>, get_toplevel=0) at gdkwindow-x11.c:3257 #4 0x0000003633a1f6ad in gdk_display_real_get_window_at_pointer (display=<value optimized out>, win_x=0x7fff282fa59c, win_y=0x7fff282fa598) at gdkdisplay.c:513 #5 0x0000003633a1fe2c in IA__gdk_display_get_window_at_pointer (display=0x975000 [GdkDisplayX11], win_x=0x7fff282fa5cc, win_y=0x7fff282fa5c8) at gdkdisplay.c:594 #6 0x00000036340318cb in IA__gtk_tooltip_trigger_tooltip_query (display=<value optimized out>) at gtktooltip.c:489 #7 0x0000003a7d257a9c in IA__g_slist_foreach (list=<value optimized out>, func=0x36340318a0 <IA__gtk_tooltip_trigger_tooltip_query>, user_data=0x0) at gslist.c:743 #8 0x0000003634075d99 in tooltip_query_idle (data=<value optimized out>) at gtkwidget.c:10686 #9 0x0000003633a1d2a6 in gdk_threads_dispatch (data=0xcf6ae0) at gdk.c:506 #10 0x0000003a7d23923e in g_main_dispatch (context=0x984040) at gmain.c:1960 #11 IA__g_main_context_dispatch (context=0x984040) at gmain.c:2513 #12 0x0000003a7d23cc28 in g_main_context_iterate (context=0x984040, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 #13 0x0000003a7d23d075 in IA__g_main_loop_run (loop=0x988fd0) at gmain.c:2799 #14 0x000000000041aa88 in main (argc=1, argv=0x7fff282faaf8) at main.c:291 This bug looks very similar to bug 549043.
*** Bug 571255 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.