Bug 813562
Summary: | [abrt] control-center-3.4.0-1.fc17: dbus_g_proxy_set_interface: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lukas Bezdicka <social> | ||||||||||
Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 17 | CC: | bnocera, bugs, control-center-maint, danw, dcbw, igor, jan, jklimes, mkasik, rstrode, scampa.giovanni | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | abrt_hash:464d98be48c45bd4ad42aa1c221f2be3113104b8 | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2013-08-01 18:40:59 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: | |||||||||||||
Attachments: |
|
Description
Lukas Bezdicka
2012-04-17 21:34:56 UTC
Created attachment 578160 [details]
File: backtrace
Created attachment 578161 [details]
File: maps
Created attachment 578162 [details]
File: dso_list
Created attachment 578163 [details]
File: build_ids
Happens if you try to setup bluetooth DUN, probably because the gnome-bluetooth plugin in NetworkManager was not ported from dbus-glib to GDBus backtrace_rating: 4 Package: control-center-3.4.1-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Is there any other way to go online via bluetooth? I'm offline at the moment because of this bug. Trying to activate DUN from a mobile phone via bluetooth from gnome-control-center after an unsuccessful pairing. You can find additional problems that leaded me to this in bug #754469 comment #5. All this stuff used to work with this same phone in F16. backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Tried to configure Bluetooth device for DUN. Clicked the related checkbox in the BT control panel, after which I expected the connection wizard to pop up. Got a segfault instead. backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) (In reply to comment #5) > Happens if you try to setup bluetooth DUN, probably because the > gnome-bluetooth plugin in NetworkManager was not ported from dbus-glib to > GDBus > > backtrace_rating: 4 > Package: control-center-3.4.1-1.fc17 > OS Release: Fedora release 17 (Beefy Miracle) It should certainly be possible to use dbus-glib and GDBus in the same process. I"d expect this to work smoothly until we do get around to porting it to GDBus. (In reply to comment #9) > (In reply to comment #5) > > Happens if you try to setup bluetooth DUN, probably because the > > gnome-bluetooth plugin in NetworkManager was not ported from dbus-glib to > > GDBus > > > > backtrace_rating: 4 > > Package: control-center-3.4.1-1.fc17 > > OS Release: Fedora release 17 (Beefy Miracle) > > It should certainly be possible to use dbus-glib and GDBus in the same > process. I"d expect this to work smoothly until we do get around to porting > it to GDBus. That's not the problem, gnome-bluetooth has been ported to use GDBus, NM didn't follow suite (eg. it's asking gnome-bluetooth for the DBus proxy, and gets something of the wrong type). Pretty sure this is upstream too. This happened when when trying to use the Internet via a bluetooth connection between this computer (running Fedora 17) and a Nokia N8 cellphone, running Symbian^3. The bluetooth connection had already been established, but there were a few quirks along the way. I think I can reliably reproduce this, if you'd like me to capture more data or try something different in order to gather more information. backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) I conform this bug with two phones from Samsung, one is GT-BT2710 and another one is Nexus. In both cases in Fedora 16 I could connect without ani problems. Are there any workarounds to enable DUNor should I just revert to Fedora 16? Happens also with N9 and N900. Trying to stablish DUN connection with mobile phone via bluetooth. This worked in F16. backtrace_rating: 4 Package: control-center-3.4.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Any news on this one? This is pretty much a blocker for certain users. As a workaround install all the latest updates, install KDE desktop and try to setup DUN connection using KDE. It worked for me, see bug 754469. After that I could switch to gnome desktop and activate the already established connection from there. Upstream fixes in gnome-bluetooth plugin: http://git.gnome.org/browse/network-manager-applet/commit/?id=dac307f98ff7c6ac9eb1f934b6b362066df9368d http://git.gnome.org/browse/network-manager-applet/commit/?id=56d0e9334990adb174c9b669f26676b99bdd682b (In reply to comment #18) > Upstream fixes in gnome-bluetooth plugin: > http://git.gnome.org/browse/network-manager-applet/commit/ > ?id=dac307f98ff7c6ac9eb1f934b6b362066df9368d > http://git.gnome.org/browse/network-manager-applet/commit/ > ?id=56d0e9334990adb174c9b669f26676b99bdd682b so is this working now with the latest f18 packages? This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. |