Bug 713109
Summary: | wicd crashes when daemon is not running | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Raphael Groner <projects.rg> |
Component: | wicd | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 14 | CC: | artix, blackmetalowiec, dcantrell, dtdraganov, duck, jnfbatista, kvinayaks, martadinata666, piyush_harsh, y_scherbak |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | abrt_hash:7cc26af9 | ||
Fixed In Version: | wicd-1.7.0-6.fc14 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 611104 | Environment: | |
Last Closed: | 2011-08-23 04:25:53 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Raphael Groner
2011-06-14 10:23:51 UTC
Sorry, but please fix the crash. It's okay to show a message box about the failed connection to DBus. But the crash will cause a report to Abrt and that's not user-friendly. - Package: wicd-gtk-1.7.0-4.fc14 Latest Crash: Di 14 Jun 2011 12:01:04 Command: /usr/bin/python -O /usr/share/wicd/gtk/wicd-client.py --no-tray Reason: gui.py:154:__init__:AttributeError: 'NoneType' object has no attribute 'ReadWindowSize' Comment: Daemon wicd wasn't running and there's a message box not being able to connect to dbus then. After started the daemon, there's no crash any more. Bug Reports: Status: CLOSED NOTABUG https://bugzilla.redhat.com/show_bug.cgi?id=611104 Package: wicd-gtk-1.7.0-4.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. installed WICD from System -> Administration -> Add/Remove Software 2. installed wicd-gtk package from System -> Administration -> Add/Remove Software 3. clicken on Application -> Internet -> Wicd Network Manager Comment ----- Launching the Wicd Network Manager causes this crash, NetworkManager was running already while this happened wicd-1.7.0-5.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/wicd-1.7.0-5.fc14 Package wicd-1.7.0-5.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wicd-1.7.0-5.fc14' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/wicd-1.7.0-5.fc14 then log in and leave karma (feedback). Package: wicd-gtk-1.7.0-4.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. wicd daemon wasn't running 2. 3. Comment ----- This is a test to reproduce the bug and verify the fix in updates-testing. Package: wicd-gtk-1.7.0-5.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. select Quit from context menu of wicd systray icon -> icon disappears 2. stop wicd daemon with system-config-services 3. try to start wicd-gtk -> message box and crash reported to abrt Comment ----- Sorry, but the -5 patch does not seem to fix this issue. You would need to add the patch also to the %prep section in the spec file as "%patch3 -p1" for instance, if you list it in the header as "Patch3: wicd-1.7.0-dbus-failure.patch". Notice that there are even more patches for fc15 and fc16 applied already[1], so you maybe should first try to build against rawhide before fiddling with fc14 only. Further, you should sync the source to the very outdated looking git[2]. A good idea would also be to disable the Search and Connection info entries in the context menu of the systray icon if the daemon is not running. Both will lead to a crash due to a null pointer dereference, too. It happens when wicd-gtk was called from within a terminal. [1] https://admin.fedoraproject.org/updates/wicd [2] http://pkgs.fedoraproject.org/gitweb/?p=wicd.git (In reply to comment #7) > You would need to add the patch also to the %prep section in the spec file as > "%patch3 -p1" for instance, if you list it in the header as "Patch3: > wicd-1.7.0-dbus-failure.patch". Yeah, that would help. Stupid mistake. > Notice that there are even more patches for fc15 and fc16 applied already[1], > so you maybe should first try to build against rawhide before fiddling with > fc14 only. No, I'm working the stack of wicd bugs backwards right now, mainly due to the major changes from F-14 to F-15 to rawhide. As the person who got wicd in to Fedora and the maintainer of the package, I'm aware of the patches on the other branches. > Further, you should sync the source to the very outdated looking git[2]. What? > A good idea would also be to disable the Search and Connection info entries in > the context menu of the systray icon if the daemon is not running. Both will > lead to a crash due to a null pointer dereference, too. It happens when > wicd-gtk was called from within a terminal. I don't want this bug to become a 100+ comment "hey, and fix this too!" bug chase. I'm just trying to fix the issue originally reported. Another test update coming up shortly. Thanks for the feedback. Package wicd-1.7.0-6.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wicd-1.7.0-6.fc14' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/wicd-1.7.0-6.fc14 then log in and leave karma (feedback). *** Bug 718401 has been marked as a duplicate of this bug. *** *** Bug 715182 has been marked as a duplicate of this bug. *** *** Bug 716691 has been marked as a duplicate of this bug. *** wicd-1.7.0-6.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |