Public bug reported:
Binary package hint: gnome-media
While attempting to get ANY sound to record on Ubuntu, I tried various
preferences using the Volume control.
Then went back and forth to the Gnome Sound Recorder to check my microphone.
Now I am in a state where after recording, the Recorder
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/14116121/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/14116122/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/14116123/ProcStatus.txt
--
Gnome Sound
Hi Matt,
Indeed I only have one gpilotd. I attempted to get libusb working. -
that seems fine as i got
pilot-xfer -p usb: -l
to work. But I did have a question about
~/.gnome2/gnome-pilot.d/gpilot
I could not figure out what to set /dev/pilot to?
I tried device=/dev/bus/usb/002/001 which
One more attempt by deleting the gpilotd config file caused the applet
to reconfigure the gpilot. I attempted to set it to usb; but that
complained with the visor module still running. So I selected the
dev/ttyUSB1 which sync'd correctly and repeatedly.
I have put visor in both
Hi Matt,
Now all is well - although there still seems to be a bug related to
visor and being confused as you suspected about which usb device to use.
I have deleted just the gpilotd config which causes the applet to
re-inquire and setup again.
Now USB is working and much faster as well - since
Now, with all the updates, running directly from the panel, there is
never any connection to the T3. BUT if I kill the gpilot-applet, and
then start gpliotd on the command line with no arguments, and then start
the gpilot-applet, I can sync as many times as I want.
? what arguments does the
I thought about my last post some more and thought, perhaps it would be
more helpful to load gpilod, then add the applet and then sync twice and
record the output. See the attaced file 1 below for the First Sync.
After that Sync - the only output was:
gpilotd-Message: setting PILOTRATE=115200
Public bug reported:
Binary package hint: gnome-pilot
After one sync, connections to a Tungsten T3 device fails.
If you kill the gpilotd process, one can once again press the sync button on
the Palm and everything works.
It appears that the close of the first sync does not clean up
Hi Daniel,
I did one sync which worked fine. Then as usuall, the second one
failed. So I killed gpilotd after removing the pilot applet from the
panel.
I then realized that pilot-xfer was not on my sytem and installed
pilot-link.
pilot-xfer -p /dev/pilot -l complained with
sudo pilot-xfer -p
