Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30712 - [blueman] cannot receive files without notification daemon, results in a kernel oops

Attached to Project: Community Packages
Opened by Wilco (Wilco) - Monday, 16 July 2012, 20:23 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 17 July 2012, 09:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Blueman cannot receive files via bluetooth without a notification daemon. blueman-applet tries to inform the user via notify-send and if notify-send is missing (or crashed) the bluez stack fails to properly free the orphaned l2cap object resulting in a kernel oops and hard system freeze. This bug can take a few minutes and retries to manifest. Although this is technically a bluez bug (because the kernel shouldn't crash because of some userspace app) blueman cannot receive any files via bluetooth without a proper libnotify implementation.

Additional info:
System fully up-to-date
3.4.4-3-ARCH #1 SMP PREEMPT Tue Jul 3 14:36:44 UTC 2012 x86_64 GNU/Linux
Broadcom module BCM20702A0 0a5c:21e3

Steps to reproduce:
Details: https://bbs.archlinux.org/viewtopic.php?pid=1130935#p1130935

Easiest fix would be to make notification-daemon (or notify-osd) mandatory although both blueman upstream and bluez upstream should be notified.
   blueman crash missing notific... (730.8 KiB)
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 17 July 2012, 09:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  notification-daemon added to deps

Loading...