Bug 216659
Summary: | gnome-bluetooth-manager doesn't return scan info & properties | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Erik Bussink <erik> |
Component: | gnome-bluetooth | Assignee: | Bastien Nocera <bnocera> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | dag, roguexz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | RC | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-02-08 00:42:33 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
Erik Bussink
2006-11-21 13:32:47 UTC
I experienced the same result in Fedora Core 6 on i686, having the same version of gnome-bluetooth-manager. Starting the gnome-bluetooth-manager from a terminal gives some warning messages that might be relevant. <Startup of the manager> /usr/lib/python2.4/site-packages/gnomebt/manager.py:142: DeprecationWarning: gnome.ui.AppBar constructor takes exactly 3 arguments, but calling old gtk.HBox constructor for compatibility reasons. self.statusbar = gnome.ui.AppBar (True, True) <After selectin Devices->scan> /usr/lib/python2.4/site-packages/gnomebt/manager.py:220: GtkWarning: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed self.statusbar.pop () /usr/lib/python2.4/site-packages/gnomebt/manager.py:222: GtkWarning: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed self.statusbar.push (_("Scanning for devices...")) (Bluetooth Device Manager:4146): GnomeUI-CRITICAL **: gnome_appbar_set_progress_percentage: assertion `appbar->_priv->progress != NULL' failed This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. *** Bug 216660 has been marked as a duplicate of this bug. *** I am no python expert, but from looking at the code here is what i have deciphered: AppBar extends from HBox, and HBox has a two argument constructor which is over-shadowing the 3 argument constructor of AppBar, when it is invoked using just two arguments. The third argument in AppBar is an enum on PreferencesType. Now, i am not sure how we would specify a preferences type in the UI, but here is what I did: /usr/lib/python2.4/site-packages/gnomebt/manager.py changed #142 from: self.statusbar = gnome.ui.AppBar (True, True) to: self.statusbar = gnome.ui.AppBar (True, True, 0) This got rid of the null pointer assertions and the UI comes up fine. Now, when I do a scan for devices, it hangs at retrieving device names! And there are no messages on the console either. Details: Bluetooth Device Manager: 0.7.0 Fedora Core 6 fixed with gnome-bluetooth-0.7.0-10.2.el5 Harald, I've downloaded the gnome-bluetooth-0.7.0-10.2.el5 for my x86_64 install using the path you gave me, but I cannot tell if this bug is now fixed or not. The gnome-bluetooth-manager application isn't in the RPM gnome-bluetooth-0.7.0-10.2.el5.x86_64.rpm anymore. Is the removal of the gnome-bluetooth-manager done on purpose or a mistake ? Removed on purpose, you should be using "Send To" from the nautilus context menu on files. Btw, it's removed in newer upstream versions as well. A package has been built which should help the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |