Reply
Thread Tools
Posts: 254 | Thanked: 509 times | Joined on Nov 2011 @ Canada
#11
sudo killall pulseaudio

??
 
peterleinchen's Avatar
Posts: 4,117 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#12
Yes.

Insert
Exec=sudo /usr/bin/killall pulseaudio
into the desktop file.

But to get that working you will need a sudoers entry. Add a file into /etc/sudsers.d (example in this directory) and run update-sudoers.
Or, if you do not know how to do, just install sudsers. But this is security mess as it will allow user to execute every binary to be executed with root rights!
__________________
SIM-Switcher, automated SIM switching with a Double (Dual) SIM adapter
--
Thank you all for voting me into the Community Council 2014-2016!

Please consider your membership / supporting Maemo e.V. and help to spread this by following/copying this link to your TMO signature:
[MC eV] Maemo Community eV membership application, http://talk.maemo.org/showthread.php?t=94257

editsignature, http://talk.maemo.org/profile.php?do=editsignature
 

The Following User Says Thank You to peterleinchen For This Useful Post:
Posts: 445 | Thanked: 367 times | Joined on Nov 2010 @ Italy
#13
thanks.

also i found another way with queen beecon widget:

written killall pulseaudio in a file script.sh

then given to the queen beecon widget the command:

echo sh "path to script.sh" | root

btw is not clear still why the pulseaudio stays active and use cpu after phone calls...
__________________
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman
 
Posts: 445 | Thanked: 367 times | Joined on Nov 2010 @ Italy
#14
still investigating the issue with pulseaudio using cpu after closing a call

"powertop" , before killing pulseaudio, shows:

37% interrupt : DMA
34% interrupt : i2c_omap
21% interrupt : gp timer
2% i interrupt : mmc1

and "top" shows cpu usage around 24% for /usr/bin/pulseaudio -- system --high-priorit (user=pulse)

killing tonegend is not killing pulseaudio like said in similar bugs on bugs.maemo.org

should i open a new bug?
it needs other info like strace -p pidof pulseaudio?
__________________
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman
 
Posts: 445 | Thanked: 367 times | Joined on Nov 2010 @ Italy
#15
i tried to run from term
ls -thl /proc/`pidof pulseaudio`/fd

while pulseaudio stuck after a call

and i got this

Code:
lrwx------    1 pulse    pulse         64 May 10 22:06 0 -> /dev/null
lrwx------    1 pulse    pulse         64 May 10 22:06 1 -> /dev/null
lrwx------    1 pulse    pulse         64 May 10 22:06 10 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 11 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 12 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 13 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 14 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 15 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 16 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 17 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 18 -> /dev/snd/controlC0
lrwx------    1 pulse    pulse         64 May 10 22:06 19 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 2 -> /dev/null
lrwx------    1 pulse    pulse         64 May 10 22:06 20 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 21 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 22 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 23 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 24 -> socket:[24042]
lrwx------    1 pulse    pulse         64 May 10 22:06 25 -> socket:[35672]
lrwx------    1 pulse    pulse         64 May 10 22:06 26 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 27 -> socket:[24003]
lrwx------    1 pulse    pulse         64 May 10 22:06 28 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 29 -> anon_inode:[eventfd]
lr-x------    1 pulse    pulse         64 May 10 22:06 3 -> pipe:[23963]
lrwx------    1 pulse    pulse         64 May 10 22:06 30 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 31 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 32 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 33 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 34 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 35 -> /dev/cmt_speech
lrwx------    1 pulse    pulse         64 May 10 22:06 36 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 37 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 38 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 39 -> anon_inode:[eventfd]
l-wx------    1 pulse    pulse         64 May 10 22:06 4 -> pipe:[23963]
lrwx------    1 pulse    pulse         64 May 10 22:06 40 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 41 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 42 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 43 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 44 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 45 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 46 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 47 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 48 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 49 -> anon_inode:[eventfd]
lr-x------    1 pulse    pulse         64 May 10 22:06 5 -> pipe:[23964]
lrwx------    1 pulse    pulse         64 May 10 22:06 50 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 51 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 52 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 53 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 54 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 55 -> anon_inode:[eventfd]
lrwx------    1 pulse    pulse         64 May 10 22:06 56 -> socket:[24015]
lrwx------    1 pulse    pulse         64 May 10 22:06 57 -> socket:[24021]
lrwx------    1 pulse    pulse         64 May 10 22:06 58 -> socket:[24023]
lrwx------    1 pulse    pulse         64 May 10 22:06 59 -> socket:[24025]
l-wx------    1 pulse    pulse         64 May 10 22:06 6 -> pipe:[23964]
lrwx------    1 pulse    pulse         64 May 10 22:06 60 -> socket:[24028]
lrwx------    1 pulse    pulse         64 May 10 22:06 61 -> socket:[24029]
lrwx------    1 pulse    pulse         64 May 10 22:06 62 -> socket:[25535]
lrwx------    1 pulse    pulse         64 May 10 22:06 63 -> socket:[24033]
lrwx------    1 pulse    pulse         64 May 10 22:06 64 -> socket:[24036]
lrwx------    1 pulse    pulse         64 May 10 22:06 65 -> socket:[26414]
lrwx------    1 pulse    pulse         64 May 10 22:06 68 -> /dev/snd/pcmC0D0p
lrwx------    1 pulse    pulse         64 May 10 22:06 7 -> socket:[24019]
lrwx------    1 pulse    pulse         64 May 10 22:06 8 -> socket:[23985]
lrwx------    1 pulse    pulse         64 May 10 22:06 9 -> socket:[23988]
does it give any clues?
__________________
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman
 
Posts: 445 | Thanked: 367 times | Joined on Nov 2010 @ Italy
#16
[problem solved?]

maybe not but i have strong feelings that the issue is linked to sociality running in background.

if i activate "keep running in background" in sociality, i can notice pulseaudio stuck after a call, but if i deactivate that option, no issue after several calls

when sociality is running in background, you can see /usr/bin/sociality running via top in xterm or conky

having sociality running in background also generate issue with audio volume: for example if you have audio volume at medium level, after receiving a notification from sociality running in background (with the iphone-like sound), the audio volume automatically increase to high level (even if you are using earphones, that is bad)

somebody can confirm?
__________________
Flickr photos taken with N900 https://www.flickr.com/cameras/nokia/n900/
"Closed source software tells you what you can do. With open source, you decide what software can do for you" Richard Stallman

Last edited by gianko; 2014-07-10 at 14:29.
 

The Following User Says Thank You to gianko For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 02:14.