Summary: | Network connections crashed when added wireless profile with wpa enterprise | ||
---|---|---|---|
Product: | Network Management | Reporter: | artur.cuvasov |
Component: | Control Module | Assignee: | Lamarque V. Souza <lamarque> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | avsco, DroidJD, leoni.massimiliano1, martin.holec, pasquale.africa, robert.munteanu, sirpingus, xhudik |
Priority: | NOR | ||
Version: | 0.9 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=839284 | ||
Latest Commit: | http://commits.kde.org/networkmanagement/1b12d01965d9d8e1e56218abfbbe7436f06442d2 | Version Fixed In: | 0.9.0.10 |
Attachments: |
crash dump as root with qdbus working
networkmanagement-0.9.0.6 crash dump Backtrace for crash on OpenSUSE 12.3 New crash information added by DrKonqi |
Description
artur.cuvasov
2012-05-12 09:03:39 UTC
According to the crashlog you were editing a connection, not creating a new one. Anyway, the crash happens in libdbus, not in Plasma NM. It does not matter if you edit an existing connection, or create a new one. Still this looks like an upstream bug. Can be. So what are the further steps? I cannot reproduce this problem here, so I cannot help you much. Which dbus version do you use? Is there any bug related to dbus in Fedora's bugzilla? The dbus is: dbus-1.4.10-3.fc16.i686 I am not sure if there are any related tickets to this problem at the moment. *** Bug 300512 has been marked as a duplicate of this bug. *** Can you reproduce this problem with Plasma NM 0.9.0.3? Version : 0.9.0.3 Release : 2.fc17 Architecture: i686 The problem persists. Do you want a crash dump? Yes, send me the crashlog, the files ~/.kde/share/config/networkmanagementrc and ~/.xsession-errors and NetworkManager's log. Can you try upgrading to libdbus-1.4.20? There are a lot of error messages regarding dbus in your .xsession-errors and no application is able to use dbus according to the log. Updated to the latest dbus available, same problem. Sent crash dump and .xsession-errors by mail. python-slip-dbus-0.2.20-2.fc17.noarch dbus-python-0.83.0-9.fc17.i686 dbus-debuginfo-1.6.0-1.fc18.i686 dbus-1.6.0-1.fc18.i686 dbus-glib-0.92-3.fc17.i686 dbus-libs-1.6.0-1.fc18.i686 abrt-dbus-2.0.10-4.fc17.i686 dbusmenu-qt-0.9.2-1.fc18.i686 dbus-x11-1.6.0-1.fc18.i686 dbus is still not working properly in you installation. What does the commands below return? qdbus qdbus --system org.freedesktop.NetworkManager qdbus org.kde.networkmanagement The installation is default. qdbus Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, th e message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. qdbus --system org.freedesktop.NetworkManager / /com /com/redhat /com/redhat/ifcfgrh1 /org /org/freedesktop /org/freedesktop/NetworkManager /org/freedesktop/NetworkManager/AccessPoint /org/freedesktop/NetworkManager/AccessPoint/5167 /org/freedesktop/NetworkManager/AccessPoint/5281 /org/freedesktop/NetworkManager/AccessPoint/5494 /org/freedesktop/NetworkManager/AccessPoint/5503 /org/freedesktop/NetworkManager/AccessPoint/5515 /org/freedesktop/NetworkManager/AccessPoint/5520 /org/freedesktop/NetworkManager/AccessPoint/5533 /org/freedesktop/NetworkManager/AccessPoint/5535 /org/freedesktop/NetworkManager/AccessPoint/5536 /org/freedesktop/NetworkManager/AccessPoint/5537 /org/freedesktop/NetworkManager/AccessPoint/5538 /org/freedesktop/NetworkManager/AccessPoint/5539 /org/freedesktop/NetworkManager/ActiveConnection /org/freedesktop/NetworkManager/ActiveConnection/21 /org/freedesktop/NetworkManager/AgentManager /org/freedesktop/NetworkManager/DHCP4Config /org/freedesktop/NetworkManager/DHCP4Config/10 /org/freedesktop/NetworkManager/Devices /org/freedesktop/NetworkManager/Devices/0 /org/freedesktop/NetworkManager/Devices/1 /org/freedesktop/NetworkManager/IP4Config /org/freedesktop/NetworkManager/IP4Config/10 /org/freedesktop/NetworkManager/Settings /org/freedesktop/NetworkManager/Settings/0 /org/freedesktop/NetworkManager/Settings/1 /org/freedesktop/NetworkManager/Settings/2 /org/freedesktop/NetworkManager/Settings/3 /org/freedesktop/NetworkManager/Settings/4 /org/freedesktop/NetworkManager/Settings/5 /org/freedesktop/NetworkManager/Settings/6 /org/freedesktop/NetworkManager/Settings/7 qdbus org.kde.networkmanagement Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. The session bus is not started. You should open a bug request in Fedora's bugzilla about this problem. It has nothing to do with KDE. This does not seem to be a (just) dbus problem, since I tried logging in as root, where all those 3 dbus related commands gave a positive result. Nevertheless, I am still getting a crash (attached, created as root) ########## qdbus :1.100 org.kde.nepomuk.services.nepomukfileindexer :1.106 org.kde.kwalletmanager :1.108 org.kde.StatusNotifierItem-20768-1 :1.109 org.kde.konsole :1.116 org.freedesktop.PackageKit org.kde.ApperSentinel :1.118 :1.119 :1.120 org.a11y.Bus :1.121 :1.122 :1.123 :1.17 org.kde.klauncher :1.18 org.freedesktop.PowerManagement org.freedesktop.PowerManagement.Inhibit org.kde.Solid.PowerManagement org.kde.Solid.PowerManagement.PolicyAgent org.kde.StatusNotifierWatcher org.kde.kded org.kde.keyboard org.kde.networkmanagement :1.21 org.kde.BlueDevil.Service org.kde.bluedevilfilereceiverhelper-20440 :1.22 :1.23 org.openobex :1.24 org.kde.bluedevilmonolithic :1.26 org.kde.StatusNotifierItem-20447-1 :1.27 org.kde.kglobalaccel :1.29 org.kde.kwalletd :1.3 com.redhat.imsettings :1.31 org.kde.kactivitymanagerd :1.34 org.kde.knotify :1.36 org.kde.ksmserver org.kde.ksmserver-20462 :1.37 org.kde.kwin org.kde.kwin-20465 org.kde.kwin.Screenshot :1.38 org.freedesktop.Notifications org.kde.DeviceNotifications org.kde.StatusNotifierHost-20474 org.kde.plasma-desktop :1.4 :1.40 org.kde.JobViewServer org.kde.kuiserver :1.43 org.kde.kaccess :1.45 org.freedesktop.ScreenSaver org.kde.krunner org.kde.screensaver :1.47 org.kde.NepomukServer :1.49 org.gnome.zeitgeist.datahub :1.5 org.gtk.vfs.Daemon :1.50 org.kde.NepomukStorage org.kde.nepomuk.DataManagement org.kde.nepomuk.services.nepomukontologyloader org.kde.nepomuk.services.nepomukstorage :1.51 org.gnome.zeitgeist.Engine :1.52 com.redhat.abrt.applet :1.53 org.kde.klipper :1.55 org.kde.kmix :1.57 :1.58 :1.59 org.freedesktop.Tracker1.Miner.Applications org.freedesktop.Tracker1.Miner.Files org.freedesktop.Tracker1.Miner.Files.Index :1.6 :1.61 org.kde.nepomukcontroller :1.63 ca.desrt.dconf :1.64 :1.65 org.kde.Polkit1AuthAgent :1.67 org.kde.StatusNotifierItem-20595-1 :1.68 org.kde.StatusNotifierItem-20580-1 :1.69 org.PulseAudio1 org.pulseaudio.Server :1.7 :1.70 :1.71 :1.72 org.kde.printer-applet-20543 :1.73 :1.74 org.gtk.Private.UDisks2VolumeMonitor :1.75 :1.76 org.gtk.Private.GPhoto2VolumeMonitor :1.77 org.gtk.Private.AfcVolumeMonitor :1.78 :1.79 org.gnome.GConf :1.81 :1.82 org.kde.StatusNotifierItem-20582-1 :1.83 org.kde.StatusNotifierItem-20543-1 :1.84 org.gnome.zeitgeist.SimpleIndexer :1.86 :1.88 :1.89 org.freedesktop.Tracker1 :1.90 :1.96 org.kde.nepomuk.services.nepomukqueryservice :1.97 org.kde.nepomuk.services.nepomukbackupsync :1.98 org.kde.nepomuk.services.nepomukfilewatch :1.99 org.kde.nepomuk.services.digikamnepomukservice org.freedesktop.DBus ################# qdbus org.kde.networkmanagement / /KBookmarkManager /KBookmarkManager/kfilePlaces /KIO /KIO/Scheduler /Layouts /MainApplication /Mixers /Mixers/0 /Mixers/0/Bass_Speaker_0 /Mixers/0/Beep_0 /Mixers/0/Capture_0 /Mixers/0/Digital_0 /Mixers/0/Headphone_0 /Mixers/0/IEC958_0 /Mixers/0/IEC958_1 /Mixers/0/IEC958_2 /Mixers/0/Line_Jack_Mode_0_penum /Mixers/0/Master_0 /Mixers/0/Mic_Jack_Mode_0_penum /Mixers/0/Mute_LED_Mode_0_penum /Mixers/0/Mux_0 /Mixers/0/PCM_0 /Mixers/0/Speaker_0 /StatusNotifierWatcher /kbuildsycoca /kded /modules /modules/StatusNotifierWatcher /modules/apperd /modules/bluedevil /modules/desktopnotifier /modules/device_automounter /modules/dnssdwatcher /modules/favicons /modules/freespacenotifier /modules/keyboard /modules/khotkeys /modules/kmixd /modules/kremotecontroldaemon /modules/ktimezoned /modules/kwrited /modules/nepomuksearchmodule /modules/networkmanagement /modules/networkstatus /modules/obexftpdaemon /modules/phononserver /modules/powerdevil /modules/randrmonitor /modules/remotedirnotify /modules/solidautoeject /modules/statusnotifierwatcher /org /org/freedesktop /org/freedesktop/PowerManagement /org/freedesktop/PowerManagement/Inhibit /org/kde /org/kde/Solid /org/kde/Solid/PowerManagement /org/kde/Solid/PowerManagement/PolicyAgent /org/kde/networkmanagement /org/kde/networkmanagement/Activatable /org/kde/networkmanagement/Activatable/1 /org/kde/networkmanagement/Activatable/2 /org/kde/networkmanagement/Activatable/3 /org/kde/networkmanagement/Activatable/4 /org/kde/networkmanagement/Activatable/5 /org/kde/networkmanagement/Activatable/6 /org/kde/networkmanagement/Activatable/7 /org/kde/networkmanagement/Activatable/8 Created attachment 72452 [details]
crash dump as root with qdbus working
Your new crash is still related to a problem in dbus library. You setup is probably messed up or NetworkManager is crashing at some point. Opened a ticket in Fedora bugtrack: https://bugzilla.redhat.com/show_bug.cgi?id=839284 *** Bug 307496 has been marked as a duplicate of this bug. *** (In reply to comment #0) > Open network connections window, create a new wireless profile with WPA/WPA2 Enterprise and save it. Crashes every time. Artur, did you try to fill-in the "Identity" field, setting it to certificate's Common Name (the body to which the certificate was issued to)? I have a similar problem with NetworkManager 0.9.0.2 and found such a workaround. (In reply to comment #18) > Your new crash is still related to a problem in dbus library. You setup is probably messed up or NetworkManager is crashing at some point. Lamarque, in both our crash dumps (Artur's in comment 17 and mine from bug 307496) there are a couple of lines near the top of the call stack: > 0x... in _dbus_abort () at dbus-sysdeps.c:94 > 0x... in _dbus_warn_check_failed (format=0x... "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:290 I am not a skilled crash dump parser, but this message looks more like a deliberate argument checking and early halting on encountered error, rather than passing obviously incorrect parameters further to lower-level functions. Although the presence of "%s" and "%d" placeholders introduces some doubts about dbus' own sanity, I still suppose that dbus is not the one to blame, since it really receives bad arguments. Isn't it the caller's responsibility to provide a valid "Identity" parameter, whether explicitly defined by user or implicitly looked up in the certificate? Git commit cca7c1e9d50afeba8fb5bc880b652056c9c5b9ae by Lamarque V. Souza. Committed on 02/12/2012 at 03:12. Pushed by lvsouza into branch 'master'. Add mechanism to validate EAP methods' settings. The first one implemented is for TLS, which requires the identify field to be filled or it will crash the edit dialog. Now the Ok button in edit dialog will be disabled if the identify field is empty. M +2 -0 libs/ui/security/eapmethod.h M +2 -1 libs/ui/security/securityeap.cpp M +10 -1 libs/ui/security/tlswidget.cpp M +1 -0 libs/ui/security/tlswidget.h M +1 -0 libs/ui/security/wirelesssecuritysettingwidget.cpp http://commits.kde.org/networkmanagement/cca7c1e9d50afeba8fb5bc880b652056c9c5b9ae Git commit 9adc021082dfe43afa3d5a68a40d3807e867b46c by Lamarque V. Souza. Committed on 02/12/2012 at 03:12. Pushed by lvsouza into branch 'nm09'. Add mechanism to validate EAP methods' settings. The first one implemented is for TLS, which requires the identify field to be filled or it will crash the edit dialog. Now the Ok button in edit dialog will be disabled if the identify field is empty. (cherry picked from commit cca7c1e9d50afeba8fb5bc880b652056c9c5b9ae) M +2 -0 libs/ui/security/eapmethod.h M +2 -1 libs/ui/security/securityeap.cpp M +10 -1 libs/ui/security/tlswidget.cpp M +1 -0 libs/ui/security/tlswidget.h M +1 -0 libs/ui/security/wirelesssecuritysettingwidget.cpp http://commits.kde.org/networkmanagement/9adc021082dfe43afa3d5a68a40d3807e867b46c Is this problem still happening? Yes, NM crashes when I add Enterprise WPA2. networkmanagement-0.9.0.6 dump attached. Created attachment 76903 [details]
networkmanagement-0.9.0.6 crash dump
(In reply to comment #24) > Is this problem still happening? As for openSUSE 12.2 (bug 307496), it still claims Network Manager's version to be 0.9.0.2 (nm09 20120507), although package versions have changed since that report of mine; anyway the binary is dated 2012-11-23, which definitely precedes your commit of 2012-12-02. Perhaps they won't update it till 12.3 comes out in March. (In reply to comment #23) > TLS requires the identify field to be filled. Now the Ok button in edit dialog will be disabled if the identify field is empty. Isn't there any option to just use the Common Name field from certificate, unless the user overrides it with custom value? *** Bug 315857 has been marked as a duplicate of this bug. *** *** Bug 325553 has been marked as a duplicate of this bug. *** Created attachment 82844 [details]
Backtrace for crash on OpenSUSE 12.3
I still have this issue on OpenSUSE 12.3 - NM 0.9.6.4 and OpenSUSE 13.1 RC1 - NM 0.9.8.6.
I've attached the backtrace with debug symbols. Please note I can't save without filling in the identity field, so the fixes referenced in this bug report are in my local installations.
*** Bug 323106 has been marked as a duplicate of this bug. *** Git commit 1b12d01965d9d8e1e56218abfbbe7436f06442d2 by Lamarque V. Souza. Committed on 28/11/2013 at 11:03. Pushed by lvsouza into branch 'nm09'. Those operator overloads are not necessary and cause crash when adding WPA2 Enterprise connections. Thanks Jan Grulich for spotting this solution. FIXED-IN: 0.9.0.10 M +0 -33 libs/marshalarguments.h M +1 -1 plasma_nm_version.h http://commits.kde.org/networkmanagement/1b12d01965d9d8e1e56218abfbbe7436f06442d2 *** Bug 326129 has been marked as a duplicate of this bug. *** *** Bug 322861 has been marked as a duplicate of this bug. *** *** Bug 322203 has been marked as a duplicate of this bug. *** Created attachment 86593 [details]
New crash information added by DrKonqi
kcmshell4 (4.11.5) on KDE Platform 4.11.5 using Qt 4.8.5
- What I was doing when the application crashed:
I was trying to create a new wpa2 network profile in network manager, but it crashed when I tried to save the profile.
-- Backtrace (Reduced):
#8 0x00007f9020aa6735 in _dbus_abort () at dbus-sysdeps.c:92
#9 0x00007f9020a9d3c1 in _dbus_warn_check_failed (format=0x7f9020aacb60 "arguments to %s() were incorrect, assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some application using the D-Bus library.\n") at dbus-internals.c:290
#10 0x00007f9020a8ffe6 in dbus_message_iter_append_basic (iter=0x7fff0e90a888, type=98, value=0x7fff0e90a700) at dbus-message.c:2586
#11 0x00007f9023d900a1 in append (arg=<optimized out>, this=0x7f9023fb9d84 <QDBusMetaTypeId::argument>) at qdbusmarshaller.cpp:79
#12 QDBusMarshaller::appendVariantInternal (this=this@entry=0x7fff0e90a870, arg=...) at qdbusmarshaller.cpp:415
|