Bug 213896 - gnome-bleutooth manager crashes at startup
Summary: gnome-bleutooth manager crashes at startup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth
Version: 6
Hardware: x86_64
OS: Linux
medium
urgent
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-03 17:15 UTC by Louis Lagendijk
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-06-27 08:41:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
output at terminal at first startup (3.06 KB, application/octet-stream)
2006-11-03 17:15 UTC, Louis Lagendijk
no flags Details
bug reporting tool output (9.93 KB, text/plain)
2006-11-03 17:17 UTC, Louis Lagendijk
no flags Details

Description Louis Lagendijk 2006-11-03 17:15:36 UTC
Description of problem:
Gnome-bluetooth-manager crashes


Version-Release number of selected component (if applicable):
fc6 + gnome-bleutooh -0.7.0-10.1

How reproducible:
always at start of gnome-bleutooth-manager
  
Actual results:
bug-buddy is displayed. When the manager is started for the first time, it scans
for devices (see std-err output) but it crashes before it shows devices. In
later attempts it crashes right away

Expected results:
normal startup

Additional info:

Comment 1 Louis Lagendijk 2006-11-03 17:15:40 UTC
Created attachment 140283 [details]
output at terminal at first startup

Comment 2 Louis Lagendijk 2006-11-03 17:17:00 UTC
Created attachment 140284 [details]
bug reporting tool output

Comment 3 Ondrej Vasik 2007-06-27 08:41:58 UTC
Gnome-bluetooth-manager was removed from the latest upstream (and Fedora)
versions of gnome-bluetooth package. Was removed from current FC-6 version
too(first version with completely removed gnome-bluetooth-manager is
gnome-bluetooth-0.7.0-11.fc6).
Closing WONTFIX, AFAIK upstream is working on completely new bluetooth manager,
so this old won't be fixed.


Note You need to log in before you can comment on or make changes to this bug.