Description of problem: I had just installed the Fritzing package (fritzing.i686 0.7.5b-2.fc18 as displayed) using yum, on a fresh install of Fedora 18, from the Fedora repo. When I try to add any component, or sometimes just click anywhere in the Fritzing window, it crashes. I had the same problem with Fritzing in Fedora 17. To reproduce: 1. Fresh install Fedora 18 2. Update system 3. Install Fritzing 4. Run Fritzing and try to add any component P.S. Fritzing 0.7.10b downloaded from the project's web page works ok. Version-Release number of selected component: fritzing-0.7.5b-2.fc18 Additional info: backtrace_rating: 4 cmdline: Fritzing crash_function: QMetaObject::activate executable: /usr/bin/Fritzing kernel: 3.7.2-201.fc18.i686.PAE remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QMetaObject::activate at kernel/qobject.cpp:3441 #1 QStatusBar::messageChanged at .moc/release-shared/moc_qstatusbar.cpp:145 #2 QStatusBar::hideOrShow at widgets/qstatusbar.cpp:696 #3 QStatusBar::showMessage at widgets/qstatusbar.cpp:616 #4 message at widgets/qstatusbar.h:88 #5 qt_static_metacall at .moc/release-shared/moc_qstatusbar.cpp:67 #6 QStatusBar::qt_static_metacall at .moc/release-shared/moc_qstatusbar.cpp:57 #7 QMetaObject::activate at kernel/qobject.cpp:3539 #8 QStatusBar::messageChanged at .moc/release-shared/moc_qstatusbar.cpp:145 #9 QStatusBar::hideOrShow at widgets/qstatusbar.cpp:696
Created attachment 682791 [details] File: backtrace
Created attachment 682792 [details] File: cgroup
Created attachment 682793 [details] File: core_backtrace
Created attachment 682794 [details] File: dso_list
Created attachment 682795 [details] File: environ
Created attachment 682796 [details] File: limits
Created attachment 682797 [details] File: maps
Created attachment 682798 [details] File: open_fds
Created attachment 682799 [details] File: proc_pid_status
Created attachment 682800 [details] File: var_log_messages
This is a known bug, and version 0.7.11b is slated to go out as a stable release in F18 shortly. You can pull it in by enabling the updates-testing repo if you'd like to work with it sooner than that. Thanks for the report! *** This bug has been marked as a duplicate of bug 852568 ***