http://bugzilla.novell.com/show_bug.cgi?id=602773 http://bugzilla.novell.com/show_bug.cgi?id=602773#c0 Summary: "udevadm trigger" does not seem to work, resulting in bluetooth being disabled Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: seife@novell.slipkontur.de QAContact: qa@suse.de CC: kasievers@novell.com, vbotka@novell.com Found By: Community User Blocker: --- running current factory with KOTD kernel and bluez from home:seife:testing (the same version is now in FACTORY), I noticed today, that bluetooth is not active after booting. Note that due to boot ordering constraints (bluez needs d-bus, but is started via udev), there is a "bluez-coldplug" init-script, that basically does udevadm trigger --subsystem-match=bluetooth after d-bus is started, to make sure that the bluez rule is triggered again. this is the rule: ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/lib/udev/bluetooth.sh" trying manually, i get: susi:~ # udevadm trigger --verbose --subsystem-match=bluetooth /sys/devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0 but /lib/udev/bluetooth.sh is not triggered. I strace'd udevd and found it does read all rules, but execute no action. Help! ;-) susi:~ # uname -a Linux susi 2.6.34-rc6-28-desktop #1 SMP PREEMPT 2010-05-02 19:55:56 +0200 x86_64 x86_64 x86_64 GNU/Linux susi:~ # rpm -q udev udev-153-1.2.x86_64 susi:~ # rpm -q bluez bluez-4.64-50.3.x86_64 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.