[Bug 113538] Re: Playback very distorted

2007-05-16 Thread Adrian Harvey
Installed xine-ui and tested with xine wavfile.wav - no distortion present. Retested with totem wavfile.wav (same file) and still got distorted output. Thanks for looking at this one! -- Playback very distorted https://bugs.launchpad.net/bugs/113538 You received this bug notification because

[Bug 113538] Playback very distorted

2007-05-09 Thread Adrian Harvey
Public bug reported: Binary package hint: totem Playing back wav files is distorted to the point of incomprehensability. Audio in other applications is fine. Files play back in, for example, play(1) with no problem. Other media types play back correctly. WAV files played back correctly before

[Bug 113538] Re: Playback very distorted

2007-05-09 Thread Adrian Harvey
** Attachment added: Dependencies.txt http://librarian.launchpad.net/7587969/Dependencies.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/7587970/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/7587971/ProcStatus.txt -- Playback

[Bug 63895] time-admin, menu items as installed in edgy does not gksu, and so fails

2006-10-04 Thread Adrian Harvey
Public bug reported: Binary package hint: gnome-system-tools time-admin requires root rights, but the menu item does not have a gksu first on the command line. This results in the menu item failing. This is on Edgy beta after upgrade from Dapper. Right clicking on clock in panel and selecting

[Bug 63895] Re: time-admin, menu items as installed in edgy does not gksu, and so fails

2006-10-04 Thread Adrian Harvey
I didn't have an admin group at all. I had an adm group, of which my account is a member. Tried creating a group called admin - just in case -, but that makes no difference... users-admin, which shows certain core groups as privlege checkboxes, has all the boxes ticked for my account (including

[Bug 63895] Re: time-admin, menu items as installed in edgy does not gksu, and so fails

2006-10-04 Thread Adrian Harvey
*** This bug is a duplicate of bug 59946 *** Though not an exact duplicate, 59946 did give me the answer to the problem - the configuration daemon needed restarting after creating the admin group (which happened when I shut down for the night...) I hadn't realised there was a daemon for these