esd does not works as expected in 2.10

Vladimir Grebenschikov vova at sw.ru
Fri Apr 15 03:05:47 PDT 2005


В пт, 15/04/2005 в 18:00 +0900, Alexander Nedotsukov пишет:
> Vladimir Grebenschikov wrote:
> 
> >В пт, 15/04/2005 в 17:35 +0900, Alexander Nedotsukov пишет:
> >  
> >
> >>Vladimir, Do you run recent -CURRENT kernel?
> >>    
> >>
> >
> >6-CURRENT with gnome 2.10, cvsuped yesterday.
> >  
> >
> Okay. I got same situation here and it looks like problem is more than 
> just esd malfunction. For example system may reboot w/o panic. Or at the 
> end of background fsck process system fall into state where any process 
> trying to make disk i/o get blocked. No way to kill such processes or to 
> reboot system at all (it complains that it in wrong state ATM). 
> Definetly doesn't looks like GNOME problem to me.

Hm, I did not notice any other side-effects for half-day intensive
portupgrade.

> Cheers,
> Alexander.
> 
> >  
> >
> >>Thanks,
> >>Alexander.
> >>
> >>Vladimir Grebenschikov wrote:
> >>
> >>    
> >>
> >>>I have found that no sounds works via esd, also I notice waiting esdplay
> >>>in process list, try to find what happens:
> >>>
> >>>
> >>>% killall esd
> >>>No matching processes belonging to you were found
> >>>% esd &
> >>>[1] 1375  // it play some sound on start
> >>>% esdplay /usr/local/share/apps/sim/sounds/alert.wav
> >>>^T load: 0.26  cmd: esdplay 1376 [connec] 0.00u 0.00s 0% 920k
> >>>^C // no any sound, and it waits forever
> >>>% truss esdplay /usr/local/share/apps/sim/sounds/alert.wav
> >>>...
> >>>open("/usr/local/share/apps/sim/sounds/alert.wav",0x0,0666) = 3 (0x3)
> >>>readlink("/etc/malloc.conf","aj",63)             = 2 (0x2)
> >>>issetugid()                                      = 0 (0x0)
> >>>mmap(0x0,4096,(0x3)PROT_READ|PROT_WRITE,(0x1002)MAP_ANON|
> >>>MAP_PRIVATE,-1,0x0) = 672751616 (0x28196000)
> >>>break(0x804b000)                                 = 0 (0x0)
> >>>lseek(3,0x0,SEEK_CUR)                            = 0 (0x0)
> >>>fstat(3,0xbfbfe0c0)                              = 0 (0x0)
> >>>break(0x804c000)                                 = 0 (0x0)
> >>>lseek(3,0x0,SEEK_CUR)                            = 0 (0x0)
> >>>lseek(3,0x0,SEEK_SET)                            = 0 (0x0)
> >>>read(0x3,0x804b000,0x1000)                       = 4096 (0x1000)
> >>>break(0x804d000)                                 = 0 (0x0)
> >>>break(0x804e000)                                 = 0 (0x0)
> >>>break(0x804f000)                                 = 0 (0x0)
> >>>lseek(3,0x1000,SEEK_SET)                         = 4096 (0x1000)
> >>>read(0x3,0x804b000,0x1000)                       = 729 (0x2d9)
> >>>lseek(3,0x12da,SEEK_SET)                         = 4826 (0x12da)
> >>>lseek(3,0x0,SEEK_SET)                            = 0 (0x0)
> >>>read(0x3,0x804b000,0x1000)                       = 4096 (0x1000)
> >>>break(0x8050000)                                 = 0 (0x0)
> >>>break(0x8051000)                                 = 0 (0x0)
> >>>break(0x8052000)                                 = 0 (0x0)
> >>>access("/tmp/.esd/socket",6)                     = 0 (0x0)
> >>>socket(0x1,0x1,0x0)                              = 4 (0x4)
> >>>fcntl(4,F_SETFD,0x1)                             = 0 (0x0)
> >>>setsockopt(0x4,0xffff,0x4,0xbfbfe06c,0x4)        = 0 (0x0)
> >>>// it waits here forever
> >>>
> >>>Any ideas ?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>_______________________________________________
> >>freebsd-gnome at freebsd.org mailing list
> >>http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> >>To unsubscribe, send any mail to "freebsd-gnome-unsubscribe at freebsd.org"
> >>    
> >>
> 
-- 
Vladimir B. Grebenschikov
SWsoft Inc. vova at sw-soft.com


More information about the freebsd-gnome mailing list