On Thu, 2007-10-11 at 10:19 +0100, Matt Davey wrote: > On Wed, 2007-10-10 at 18:35 +0100, Matt Davey wrote: > > Dear all, > > > > There have been reports that gnome-pilot can only sync once after each > > reboot. Recently a user seems to have tracked this down to HAL > > behaviour, in which the 'device_added' event only fires once, even if > > the palmos device is physically unplugged from the host. > > > > This doesn't sound right to me. I wonder if this behaviour is a known > > regression in HAL, or is it intended for some reason I'm not fathoming? > > Apologies if this is a FAQ - I didn't spot it after a quick scan through > > the list archives for the last couple of months. > > > > System info from the reporter: > > hal: 0.5.9.1 > > hal-info: 0.20070831 > > kernel: 2.6.22-ARCH > > udev: 115 > > > > The gnome-pilot-list thread is here: > > http://mail.gnome.org/archives/gnome-pilot-list/2007-October/msg00022.html > > Further update: > I have now reproduced this problem myself and have narrowed it down to a > regression between two kernel versions: I was able to sync fine using > the initial fedora-7 installation (kernel 2.6.21-1.3194.fc7). I then > updated just the kernel, to 2.6.22.9-91.fc7, and could then duplicate > Tom's symptoms (only syncs once per reboot). 'lshal' retained the info > on the 'usb_device' entry even after disconnecting my palmos device. > > Again, is this a known issue? Should I take to greg-k-h?
I'm not sure this is relevant, but most of my problems with device nodes not going away were fixed with a newer udev (at the time). That was my bug report: https://bugzilla.redhat.com/show_bug.cgi?id=203932 And it seems to work fine for me. Maybe it's time to go add Bluetooth support to gnome-pilot? :) -- Bastien Nocera <[EMAIL PROTECTED]> _______________________________________________ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list