Bug 542812
| Summary: | [abrt] crash detected in blueman-1.21-2.fc12 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alrik <alrikb> | ||||||
| Component: | blueman | Assignee: | Juan Manuel Rodriguez <nushio> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 15 | CC: | 06707731732, aaron-kuo, a.aspden, abugreporter, aconti, admin, adrigiga, alan, andras.szilard, andrew.kavalov, ansgar.konermann, antillon.maurizio, archeootas, arkaitzmugica, artur.pierscinski, avramovski.dragan, batucador, bengt.sjogren, ben.v.root, bethebeast, bloch, bluelight37435, brucelm, b.thielman, Bugreporta, bugzilla, buyit01, chandrams, christoph.wickert, chuck.lasher, chunnayya, claudiomar.costa, contactmail, corsi_paolo, crackadict, cristian.ciupitu, cristovaozr, c_w_sutherland, dan4793, danemarks, daniel-fedoauth, davematel, dcjava, djo2, djuran, dmitry, driffer85, dr-ru, dusan, dwattttt, eblix08, einer, elnair.rnd, emanuel, erbengi, eric, eslam.husseiny, f.demiralp, fedora, francesco.pasqualetti, freetgm, ggold, giove, girivs, giu.senese, GJahchan, gpvprasad, gsieranski, gurnik, hanzhin.stas, henrique, hndrcksn, ioan.albescu, ironmiky, janhelgester, javadieh.msd, jclere, jesus, jhauva, Jim.andreu, jmlopezsn, johnmargaritopoulos, jonathanr.pritchard+bugzilla, jon.hamelin, joy.career, jtsigkos, julian.rubach, koolacc, kuijstej, kupon.bg, la_antorcha_guia, lassaad, laurentiu_lpascu, lazeroptyx, ld.daniel, lgraves, long.james410, luzemail, lynnevan, mail, marbolangos, matteopacini.informatica, matthew.hooper, mattventura, mauro_inter, mcgowen, me, meme23, metal3d, metayerclaire, mfmagar, mhroncok, mikkel, mjstefl, morten, mr.vieq, mutengine, n12367, naoki, narf, nefelim, neoh.ys, nerd__02, nicolas.macquet, nicolas, nitishproxy, nushio, ocubacub, oleg-sz, olof.tangrot, olver.ramos, orion520a, phyrefyter, pinode, pitamm, pmpcdg, poczta, pratyush.a.sahay, proser_sistemas, pstorr, qte125, raaschou1, ralphclark, redchernobil, redhat, redhatbugzilla, redhat-bugzilla, Reinhard.Scheck, rhbug, rhjm.gnu, rjabovol, robert.miciovici, Ross606, rpm, samuelyogi, sauloal, schwarcz.kaiser, skaturn, smooge, snake-duse, srozhkoff, srsnet, srushfeldt, ssabcew, stajem, stefanmurariu, steffen.mann, stephen.moehle, steven, stiven52, svante.victorsson, theophane, thub, trebla, trevor.joerges, Triv, UHQWTAEZRLVF, vesselam, vincent.passaro, vinnitrash, virum, vonbrand, vscherbo, wapembe, wjstarrsiii, wvincenti, yantrikig | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | abrt_hash:b4d53965 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-08-07 19:37:46 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
Alrik
2009-11-30 20:30:51 UTC
Created attachment 374878 [details]
File: backtrace
This dies on startup, because /tmp/blueman-applet-{pid} has a stale pid file. The |kill| call fails because this happens to be packagekitd for me, but presumably sometimes its a process run by the user where the kill call would work, even if its a different process being killed.
(In reply to comment #2) > This dies on startup, because /tmp/blueman-applet-{pid} has a stale pid file. > The |kill| call fails because this happens to be packagekitd for me, but > presumably sometimes its a process run by the user where the kill call would > work, even if its a different process being killed. In that case, it should check that the pid in the file is actually the pid of blueman-applet before it kills the process with this pid. Comment ----- restarted after update How to reproduce ----- 1. Setup blueman-applet to start when starting session 2. Boot machine with BT dongle removed 3. Login How to reproduce ----- 1. Boot 2. Login Comment ----- don't know. But there is no bluetooth device in my computer ^^ How to reproduce ----- 1. Boot system 2. 3. Comment ----- Boot system How to reproduce ----- 1.Login (graphical way) 2. 3. Comment ----- After the normal login, I saw the "red lamp" in my system tray. Comment ----- Happens on boot. How to reproduce ----- Booting up and connecting bluetooth mouse Comment ----- Booting up and connecting bluetooth mouse How to reproduce ----- 1. Blueman is started automatically at login Comment ----- The general Bluetooth state seems to be a bit bogus. The standard Gnome Bluetooth applet shows that Bluetooth is disabled, while the laptop itself indicates that bluetooth is enabled. In these cases Blueman always crashes at startup. How to reproduce ----- 1. Boot up the machine 2. Log in 3. Go away for about 10 minutes Comment ----- Nothing special for this. I just booted up my Fedora 12 machine, logged in and went away for about 10 minutes to do some things in the kitchen. When I came back, I found the ABRT icon in the panel reporting this crash. How to reproduce ----- 1.boot system 2. 3. Comment ----- boot system How to reproduce ----- 1. Immediately after starup 2. 3. Comment ----- Directly came up on boot. How to reproduce ----- 1. Gnome Login (no user action yet) 2. 3. How to reproduce ----- 1. This seemed to occur when I rebooted the computer after an update. How to reproduce ----- 1. Unknown how to reproduce - just started Fedora. Crash was reported by ABRT immediately after gnome desktop appeared. 2. 3. How to reproduce ----- 1. boot up and log in How to reproduce ----- Unknown how to reproduce How to reproduce ----- 1. Single issue (up to now) 2. 3. Comment ----- On cold start Package: blueman-1.21-2.fc12 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Unknown. This occurred as the PC was starting up. Comment ----- This error was reported as the system started up. I have no bluetooth devices installed on this PC, so this error may be related to it not being able to find any bluetooth hw/sw to use. Package: blueman-1.21-2.fc12 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- This occurs when logging in, with no Bluetooth devices on the system. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.error happens when booting up 2. 3. Package: blueman-1.21-2.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.reboot 2. 3. Comment ----- restarted after update Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Log into account and the crash occurred 2. 3. Comment ----- Just started up laptop and logged into my account. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Just login, blueman setup to start-up with login 2. 3. Comment ----- Just login, blueman setup to start-up with login Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Crash on startup the system. 2. 3. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. I don't now. 2. 3. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Login 2. 3. Comment ----- This happened when I logged in. I have no bluetooth device on this desktop. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- Unknown. This occurred on first boot-up after package update. Comment ----- Unknown. This occurred on first boot-up after package update. Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Not sure 2. 3. Comment ----- I "switched user" from another session and the error message appeared. This software is not being fixed. The standard GNOME bluetooth-manager does a better job and even integrates with NetworkManager. (In reply to comment #33) > This software is not being fixed. The standard GNOME bluetooth-manager does a > better job and even integrates with NetworkManager. I'm sorry, but what is this? People are obviously using blueman instead of GNOME bluetooth-manager because it provides them with features they want/need/like better in blueman. Both blueman and GNOME bluetooth-manager are available in the standard Fedora repositories. Let's not start a discussion that we should not use blueman - that is not a fruitful discussion in this bug report. Let's rather provide enough information for the blueman developer to fix the bugs. And then the users themselves can decide if they want to use GNOME bluetooth-manager or blueman. (In reply to comment #33) > This software is not being fixed. The standard GNOME bluetooth-manager does a > better job and even integrates with NetworkManager. 1: No, it does neither the one or the other. Fx. how do you connect to _only_ the A2DP profile on a stereo headset? How do you connect DUN? You are either talking about a different standard bluetooth manager, the documentation is woefully inadequate or you don't know what you're talking about. Blueman on the other hand does both "do a good job" and integrate with Network Manager, (when the selinux setup is fixed) 2: Have you studied the bug reports enough to notice that wuite a few of the reporters apparently don't actually have bluetooth devices and/or are starting fc12 for the first time? How then is the other bluetooth manager the "standard". Blueman seems to be installed in a fresh install. 3: On my machine at least the blueman crash is often accompanied by a kernel oops. There seems to be something worth investigating, no? 4: Would it be such a burden to forward the suggestion from comment 3 upstream? The whole bluetooth stack has become more and more unstable in fc12 during the last 6 months or so, so don't just shrug off bug reports. To be fair, for pretty much the entire lifetime of the F12 release, blueman has done none of the things you list, as it has consistently crashed on startup, both manual and automatic. (In reply to comment #36) > To be fair, for pretty much the entire lifetime of the F12 release, blueman has > done none of the things you list, as it has consistently crashed on startup, > both manual and automatic. Fair enough, but restarting it when the bluetooth device enabled it works as expected. For me, it only crashes when I have not enabled the bluetooth device. I've searched quickly in the launchpad bugtracker which blueman seems to primarily use, without finding a similar issue - but I might have overseen it. I don't know if upstream is aware of this bug - or if it is a Fedora specific problem. But, IMHO, the package maintainer could raise his voice at sometime, providing some more info on this issue. And if upstream is not aware of this problem, we as a Fedora community have failed help solving this bug. In my case blueman doesn't crash, but it can not start the service bluez. So it doesn't work. Don't know what to do with it. tried to start the service manually but that also failed. Sadly, this is not my experience. I just inserted my BT dongle, started blueman, and it promptly crashed. Thrice, according to the abrt-popups. Checking abrt, I have two entries for blueman, both marked as reported. I notice this one: https://bugzilla.redhat.com/show_bug.cgi?id=530680 is marked as closed. Can't imagine why, since it's clearly still happening. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Start computer with loadinit 3 2. startx 3. Comment ----- Happens every time I start my computer. (In reply to comment #38) > In my case blueman doesn't crash, but it can not start the service bluez. So it > doesn't work. > Don't know what to do with it. tried to start the service manually but that > also failed. I start bluez, (which crashes a lot more than blueman itself BTW, possibly because of related kernel oops'), using the old bluetooth manager. After that you should be able to enable bluetooth in blueman. You might have to kill everything bluetooth including removing the kernel module, before it works though. If this isn't caused by the comment 3 problem, it might be caused by the bluez stack dying out from under blueman. @Daniel completely off-topic I suppose but uninstalled all of bluez* and bluetooth reinstalled only bluez same problem Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) Comment ----- Occured afer reboot from recent automated kernel update. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) Comment ----- Installed the current set of updates and rebooted the system. The crash occurred during the boot up process. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Power PC on from Cold 2.Immediate Crash 3. Comment ----- DELL D630 with integrated bluetooth. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) Comment ----- non so cosa sia successo Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. 2. 3. startup :/ Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Start PC and wait. 2. 3. Comment ----- Upgraded from stable F11 recently, and seem to have a multitude of crashes occuring in ABRT Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Switching on bluetooth from Blueman menu 2. 3. Package: blueman-1.21-2.fc12 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Conectar el dispositivo bluetooth 2. 3. Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Switching on bluetooth from Blueman menu 2. Switch off Wireless radio from external switch and reboot 3. Comment ----- Switched off the wireless radio from the hardware switch and rebooted system. Upon logon, abrt reported a blueman crash. Also, blueman also crashes when trying to switch on Bluetotth radio from blueman menu (hardware switch is on ON position). Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Gnome login 2. 3. Comment ----- Just logged into gnome Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Login upon initial boot 2. 3. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. I logged into X Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.started gnome 2. 3. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- just happened when logging in. fm@thinkpad:~ # ll /tmp/blueman-applet-500 -rw-rw-r-- 1 fm fm 6 21. Jun 00:42 /tmp/blueman-applet-500 Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Let a user log in 2. Log in as another user using switch user Comment ----- Logging in while another user is logged into another session Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- Crashed upon boot-up after update. Am not using bluetooth on this system. Comment ----- Rebooted after update. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) Comment ----- i don't know what cause the crash... Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Plug in Belkin bluetooth dongle that formerly worked in Fedora 2. Up pops the Automatic Bug Reporting Tool describing the crash 3. Comment ----- I plugged in my Belkin bluetooth dongle that formerly worked in Fedora, and got the crash report. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Gnome login 2. 3. Comment ----- Just logged into gnome. No bluetooth devcies attached. Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Logged in 2. 3. Comment ----- I just logged into my gnome session. RE Comment 62 I have no bluetooth devices on my system Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. booting ... and the crash was reported just after login before any other action was taken 2. 3. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Log into Fedora Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. upon booting 2. 3. Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Crash immediately on boot up. Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.reboot . . . 2. 3. Package: blueman-1.21-2.fc12 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Startx 2. Crashes occurs 3. Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I merely turned the computer on and logged in. 2. Immediately upon logging in, I got this crash report. 3. I haven't logged out to replicate it yet, just filling out this bug report. Package: blueman-1.21-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Just logged in. 2. 3. Comment ----- All I did was log in and I immediately was shown this crash report by ABRT. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) Comment ----- On boot Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Started up system and saw in info panel 2. 3. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- Log in Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.This crash happen right after boot 2. 3. Comment ----- I only use bluetooth for one time and it works fine. Then a week after, this crash appear. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- crash on reboot after update Package: blueman-1.21-4.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)
How to reproduce
-----
1. It would crash on startup.
2. If I try to manually run blueman-manager or blueman-applet, it would also crash
3.
Comment
-----
This is the output when attempting to run blueman-manager from the command-line (I tried to get --help):
blueman-manager --help
Loading configuration plugins
Using gconf config backend
_________
on_bluez_name_owner_changed (/usr/bin/blueman-manager:104)
org.bluez owner changed to :1.75
Using gconf config backend
ERROR:dbus.proxies:Introspect error on org.blueman.Applet:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/blueman-applet exited with status 1
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 586, in msg_reply_handler
reply_handler(*message.get_args_list(**get_args_opts))
File "/usr/bin/blueman-manager", line 132, in on_bluez_name_owner_changed
if not self.Applet.GetBluetoothStatus():
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 630, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/blueman-applet exited with status 1
^CTraceback (most recent call last):
File "/usr/bin/blueman-manager", line 296, in <module>
Blueman()
File "/usr/bin/blueman-manager", line 179, in __init__
gtk.main()
KeyboardInterrupt
And this is the output when attempting to run blueman-applet:
blueman-applet
Loading configuration plugins
Using gconf config backend
there is an instance already running
Traceback (most recent call last):
File "/usr/bin/blueman-applet", line 364, in <module>
BluemanApplet()
File "/usr/bin/blueman-applet", line 297, in __init__
check_single_instance("blueman-applet")
File "/usr/lib/python2.6/site-packages/blueman/Functions.py", line 290, in check_single_instance
os.kill(pid, signal.SIGUSR1)
OSError: [Errno 1] Operation not permitted
As a follow-up to my previous bug report (the one right before, assuming no one posts one as I submit this), I plugged-in my USB bluetooth adapter and then restarted my computer, and Blueman started just fine without any errors. This appears to be consistent with other reports where blueman would crash when the bluetooth devices were not connected. Hopefully that helps in finding the source of this bug. Blueman is a really nice utility and it's easier to use than the Bluetooth Manager that comes with Gnome - perhaps they can be merged so we don't need/have to use both. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Fedora 13 Boot up 2. 3. Comment ----- This was an initial sign in. I did not even touch the keyboard before the error occurred. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Fedora 13 Boot up 2. 3. Comment ----- This was an initial sign in. I did not even touch the keyboard before the error occurred. Hmm. This is a relatively new install on a new netbook. It had been working for more than a week just fine. I did just perform a yum update on several modules but do not remember which ones it updated. Now it is failing on every boot up...... Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. boot PC Package: blueman-1.21-2.fc12
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)
How to reproduce
-----
Simply touching the lockfile will cause it to crash in the same function (check_single_instance), but not with the same error.
1. Recreate lockfile ('touch /tmp/blueman-applet-1000')
2. Attempt to run blueman-applet
Comment
-----
Blueman did not handle a stale lockfile correctly. Looking at the source mentioned in the traceback, it appeared to think that it was still running, and attempted to kill a process which it did not have permission to kill. Removing the lock file caused it to work again.
It appears that it stores the pid in the lock file, and if this lock file is storing the wrong pid, it will attempt to kill that process, which will fail unless the process is owned by the user.
Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Logged into a GNOME session 2. Blueman crashed 3. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- I just started up my computer and logged into my Gnome desktop. Comment ----- I don't think my computer even has bluetooth, and I usually disable this service (but I might have forgotten to for this install). Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Logged on as Normal user 2. crash message appeared on desktop 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Logged in to Gnome Desktop 2. 3. Did anyone ever look into this problem? (In reply to comment #87) > Did anyone ever look into this problem? Look at my comment #82. At least some of the failures are due to stale lockfiles, which could easily be remedied with a patch that could validate the lockfile, and make sure the PID contained in the lockfile is a valid blueman PID, not a PID belonging to another currently-running application. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Logged in. No bluetooth devices. 2. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- while starting the box after loggon. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Login in to desktop Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Computer hochgefahren 2. Absturz 3. Comment ----- Bei jedem Start des Computers Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booted the computer after it had been off for a couple hours. 2. Logged in to standard user account. 3. ABRT reported crash Comment ----- Kernel: 2.6.34.7-56.fc13.x86_64 Gnome: 2.30.0 On: MacBook 2.1, 2.0Ghz Core-Duo, 2.5Gb Ram Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.It crushed just after login. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Installation on Gnome of KDE version of blutooth program from packages 2. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Login to GNOME desktop 2. Applet crash reported Comment ----- Didn't do anything, just logged in, and this error appeared Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Загрузка ОС 2. 3. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping As several people have reported this bug on Fedora 13, I'm raising the version accordingly. @Juan, have you made any attempts to report this to the upstream developers? Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. On login. 2. 3. Comment ----- Logged in to the system. Happens haphazardly. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booting linux. 2. Error message occurs. 3. Here's a patch that should solve at least a part of the problems with killing an inappropriate process. http://codereview.appspot.com/2997042 Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booting fedora. 2. Error message occurs. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Started Fedora 2. Crash 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Error ocurred during gnome start 2. 3. Comment ----- I don't know how to reproduce it. It happends from time to time. May be reason is in not correct shootdown. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Crash during start-up 2. 3. Comment ----- A new start-up didn't reproduce this. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Install updates. Need logout. 2.Logout. 3.Login 4.Have message of bug reporter. Comment ----- USB Bluetooth device not connected in all time. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booting fedora. 2. Error message occurs. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.startup OS 2. 3. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booting fedora. 2. Error message occurs. 3. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booting fedora. 2. Error message occurs. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. booted system 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Boot system 2. 3. Comment ----- I actually boot my system and it crashes. It does not happen always, unfortunately i can not figure out what might cause it. Created attachment 463384 [details]
A quick patch
This is a quick hack to fix the lock file issues. If the lock file makes something throw an error, it will simply delete the lock file and go on.
This patch is a diff for /usr/lib/python2.6/site-packages/blueman/Functions.py
Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I have no idea how it happened, I do not use Bluetooth at all on my system (thought I did not even install it unless it was a dependency for something else) but it came up in ABRT when I logged in. 1. 2. 3. Comment ----- See ABRT... crash in package... no Bluetooth on system so no idea of any symptoms Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. system boot 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Try to start bluetooth settings from Xfce menu 2. Nothing happens, ABRT warning comes up As I write this, following the suggestion in #82, in F14 removing the lockfile (/tmp/blueman-applet-someNumberIDontKnowWhatMeans), in my case /tmp/blueman-applet-500 solves the problem and blueman-applet then starts normally. I haven't tried rebooting yet, but will post after-reboot status ASAP. Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booting fedora. 2. Error message occurs. 3. Okay, it's confirmed. After several reboots, i can say that problem is solved. Seriously, developer should do some work about that lockfile.. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Just autoupdate Fedora 14 2.Reboot 3.Start Alert message compare Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Login in gnome desktop 2. 3. Comment ----- Just after login in gnome desktop Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- start - boot - crash Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- start - boot - crash Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Log in 2. 3. Juan, this is my second attempt to contact you. Please respond to this bug report, it affects more than 150 users! The bug has already been reported to the blueman developers at https://bugs.launchpad.net/blueman/+bug/673759 There even is a patch available. Please apply it ASAP! Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.startup crash 2. 3. There have been a number of proposed fixes posted here, is anyone from Fedora (ever) going to take a look into patching these into the release package? I am willing to help out if needed. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Started blueman Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Start X. 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Happens every now the then after log on. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start gnome 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3.just open the aplication Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.blueman crash after boot 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Crashes on login. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just booted up, ABRT showed a crash reported for Blueman. 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I turned on the computer, then logged in, nothing else. 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. logged in... bluetooth crashed.. logged out.. logged back in... crashed again... Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.just switched on CPU with blue tooth device disconnected 2. 3. FYI, I whipped up a yum repository with a new blueman edition that includes the patch, as we've had no reaction from the blueman authors for quite some time. Since the original patch was applied to blueman head and backporting to Fedora's 1.21 was time-consuming, I simply added a (big) patch that fast-forwards blueman-1.21 to current HEAD. So, it may be that we're just trading one set of problems for another, but I'd really like to find some brave souls to check the updated package out. The repo instructions are at the URL below: http://www.hdlfactory.com/~filmil/#%5B%5BHDL%20Factory%20YUM%20repository%20for%20Fedora%5D%5D All feedback is welcome. Patches especially. Thanks Filip, I would rather prefer a backported version of the patch but I haven't yet found the time to do it. Once we have a patch, no matter if for 1.21 or for HEAD, I can build an updated package. Juan, this is my 3rd attempt to contact you. I am now officially starting the policy for nonresponsive package maintainers [1]. If you cannot cope with this bug, that's fine, we all are willing to help you. But we need to know if you are still around and willing to maintain packages in Fedora. Please respond, thanks! [1] https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers (In reply to comment #141) > the time to do it. Once we have a patch, no matter if for 1.21 or for HEAD, I > can build an updated package. Well, there is a patch against HEAD (i.e. blueman rev. 707) at http://codereview.appspot.com/2997042, does that mean that you can whip up a fix? I looked at backporting, and it was a huge pain. I advise not going for it unless you're a real diehard. Maybe I'm just confused, but can you please explain what your plan for fixing this is as I'm not sure what you want to do? Is there anything especially problematic about just bundling a diff between release 1.21 and HEAD+my patch and having that patch included? FWIW, I built a source RPM that includes exactly this patch at: continued... (In reply to comment #142) > Is there anything especially problematic about just bundling a diff between > release 1.21 and HEAD+my patch and having that patch included? FWIW, I built a > source RPM that includes exactly this patch at: http://www.hdlfactory.com/yum/13/i686/srpm/blueman-1.21-7.fc13.src.rpm Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.. 2. 3. Comment ----- I did nothing unusual. Just booted the system and a crash did wait to happen (before the gnome panel appeared) *didn't wait to happen Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Boot 2.Login to userID 3.Nothing else I don't know if it's reproducible Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. power on system 2. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Just did a yum update and restarted Desktop session (logged out and logged back in) 2. Rebooted and logged back in .... 3. Comment ----- See 1 and 2 in How did crash happen... Package: blueman-1.21-4.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. 2.i have family that is sending and trying to manage the network its personal 3. Comment ----- i really dont know how to program operate iam a beginer in computing i dont know how to block and take control of my pc i am learning i am mexican Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted up 2. Logged in. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I logged in and I suppose this program starts automatically; I don't actively use it. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.freshly started the laptop ... 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 1 2. 3. Comment ----- I'm dont know !! Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Crashes when starting X 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I logged in to GNOME Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. turned off bluetooth Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I don't remembere :( Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.no idea 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.on login, as soon as desktop appeared 2. 3. Comment ----- I ignored it. If this is something to do with Bluetooth it is not installed on this machine. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.Power On Laptop 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Crash occured as blueman startedon login 2. 3. Ok, everyone, I'm outta here. I prepared a fixed packet in a repo at Comment 140, and since I installed it, I'm seeing no errors of this sort. No reason to dwell here anymore (and all the error reports are getting spammy). I'll try to push the fix upstream, but that's going to be difficult given that there's noone on the receiving end. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Blueman aptostarted 2. Failure Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Logged on 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I don't know 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I don't know 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted computer Blueman crashed 2. 3. Package: blueman-1.21-7.fc15 Architecture: x86_64 OS Release: Fedora release 16 (Rawhide) How to reproduce ----- 1. Started a Gnome session (fallback), after X froze and I had to shut down forcefully 2. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Crashes at logon. 2. 3. Comment ----- Logged on to the system. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. i do not know 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted up 2. Logged in. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start up computer and log in Not sure how reproducible comment #126 suggests that this bug indeed has been reported upstream. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. crashed! Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.iniciar sesion en fedora 2.crash 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.iniciar sesion en fedora 2.crash 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I don't know 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- just starting computer Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I don't know 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Just finished booting my PC 2. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. happened during system boot immediately as I logged in. 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I don't know 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. During bootup 2. Reboot will reproduce 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I do not know 2. 3. Comment ----- I do not know Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.. 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Application crashed as soon as I logged in. 2. 3. Package: blueman-1.21-4.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Boot 2.Login gnome 3. Comment ----- Two days ago I upgraded from Fedora 13 to Fedora 14 Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Booted up 2. Logged in. 3. Crash message Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Crashed upon login Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.while booting up 2.application crashed 3. Comment ----- system reboot Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Updated the computer using yum 2. Blueman appeared to crash on restart - was told a restart was needed to apply new policies. Package: blueman-1.21-4.fc12 Architecture: x86_64 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.crash happened during system startup 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.startup error 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.booting up system 2. 3. Comment ----- crashed on boot up of system Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.crahsed booting up system 2. 3. Comment ----- crashed on a boot up Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.startup error 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. by starting up the laptop this mmessage appear Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.crahsed booting up system 2. 3. Comment ----- crashed on a boot up Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. start fedora 2. disable bluetooh 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Gnome start 2. 3. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Still crashes in F15, updating bug to avoid it gets closed. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.crahsed booting up system 2. 3. Comment ----- crashed on a boot up Package: blueman-1.21-8.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I Don't Know 2. 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.start X 2. crash 3. Package: blueman-1.21-6.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Log in 2. 3. Comment ----- Nothing special, just booted my PC, and logged in. The report happened either just after or as part of the log in process, before I had launched any other programs. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.system boot 2. 3. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. At system bootup 2. 3. Package: blueman-1.21-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. Just booted and logged in. Package: blueman-1.21-4.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. it's crashed at start gnome 2. 3. Package: blueman-1.21-8.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. Crash after login as usual Package: blueman-1.21-8.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. log in system 2. 3. Package: blueman-1.21-8.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. starting up the laptop... Package: blueman-1.21-8.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. It just happened without me launching Bluetooth. 2. 3. Comment ----- No idea what happened. Just told by the GUI something is wrong. I did not ask Bluetooth to do anything. Package: blueman-1.21-8.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.system startup. sometimes 2. 3. This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |