Bug 606561 - [abrt] crash in NetworkManager-gnome-1:0.8.1-0.1.git20100510.fc13: cell_editing_canceled: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in NetworkManager-gnome-1:0.8.1-0.1.git20100510.fc13: cell_editi...
Keywords:
Status: CLOSED DUPLICATE of bug 572466
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9e2717469ea239d6ebd904eaf93...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-22 00:01 UTC by Maksim Ali
Modified: 2010-06-28 19:37 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-28 19:37:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (28.01 KB, text/plain)
2010-06-22 00:01 UTC, Maksim Ali 		no flags Details
View All

Description Maksim Ali 2010-06-22 00:01:18 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: nm-connection-editor
component: NetworkManager
crash_function: cell_editing_canceled
executable: /usr/bin/nm-connection-editor
global_uuid: 9e2717469ea239d6ebd904eaf939cab093c2203a
kernel: 2.6.33.4-95.fc13.x86_64
package: NetworkManager-gnome-1:0.8.1-0.1.git20100510.fc13
rating: 4
reason: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Возникла так (не повторял :))  ): запустил "Сетевые соединения" ; "Изменить выделенное соединение"   (в данном случае   System eth1)
2.  переход на вкдадку  "Параметры IPv4"
3. Левый клик на введенном адресе, правый - чтобы скопировать его... и возник данный сбой в системе :(
Comment 1 Maksim Ali 2010-06-22 00:01:25 UTC 
Created attachment 425777 [details]
File: backtrace
Comment 2 Dan Williams 2010-06-28 19:37:39 UTC 
Probably same cause as bug 572466

*** This bug has been marked as a duplicate of bug 572466 ***
Note You need to log in before you can comment on or make changes to this bug.