On Fri, 2020-01-03 at 18:03 -0800, Ernesto Alfonso wrote:
> I was able to use linphone, which is available in buster.
>
> Ernesto
Linphone is also available from a Flatpak. The newer version is much
better than the one in the Debian main repository.
I was able to use linphone, which is available in buster.
Ernesto
From: Robin Krahl , Fri, 19 Jul 2019 20:12:58 +0200
> Ekiga has been removed as the last upstream release was in 2013, see:
> https://tracker.debian.org/pkg/ekiga
> https://tracker.debian.org/news/1004860/removed-401-9-from-unstable/
> https://bugs.debian
On Wed 24 Jul 2019 at 17:12:39 (-0400), Greg Wooledge wrote:
> On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
> > On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
> >
> > [...]
> >
> > > If I read a file that has an embedded NUL into an editor, I would
> > > consid
On Tue 23 Jul 2019 at 15:31:12 (-0400), Michael Stone wrote:
> On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> > I don't see any NUL characters, but x80 as shown below. I'm reading
> > the cached message that mutt downloaded from an IMAP server. Is that
> > different from you?
>
>
On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
FWIW, I (somewhat strongly) disagree with Michael here. I'm a
strong proponent of Postel's principle (both sides!).
That's fine, it was a lovely ideal for a different and simpler time.
On Wed, Jul 24, 2019 at 05:12:39PM -0400, Greg Wooledge wrote:
> On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
> > On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
> >
> > [...]
> >
> > > If I read a file that has an embedded NUL into an editor, I would
> > > cons
On Wed, Jul 24, 2019 at 11:02:33PM +0200, to...@tuxteam.de wrote:
> On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
>
> [...]
>
> > If I read a file that has an embedded NUL into an editor, I would
> > consider it suboptimal if the editor ceased reading any more of the
> > file when
On Wed, Jul 24, 2019 at 10:57:09PM +0200, Sven Joachim wrote:
> On 2019-07-24 15:49 -0500, David Wright wrote:
>
> > Where is the definition of NUL as "ignore everything following this
> > character"? AFAICT the mutt manual says nothing about NUL at all.
>
> In the design of the C language, where
On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
[...]
> If I read a file that has an embedded NUL into an editor, I would
> consider it suboptimal if the editor ceased reading any more of the
> file when it hit a NUL.
Vim and Emacs both qualify. Are there other editors? (yes, a bit
On 2019-07-24 15:49 -0500, David Wright wrote:
> Where is the definition of NUL as "ignore everything following this
> character"? AFAICT the mutt manual says nothing about NUL at all.
In the design of the C language, where NUL is the end of the string as
we know it.
Cheers,
Sven
On Wed, Jul 24, 2019 at 03:49:38PM -0500, David Wright wrote:
> If I read a file that has an embedded NUL into an editor, I would
> consider it suboptimal if the editor ceased reading any more of the
> file when it hit a NUL.
>
> In the same way, I expect mutt and its pager to behave much the
> li
On Wed 24 Jul 2019 at 13:51:22 (-0400), Michael Stone wrote:
> On Wed, Jul 24, 2019 at 07:28:11PM +0200, to...@tuxteam.de wrote:
> > On Wed, Jul 24, 2019 at 01:10:49PM -0400, Michael Stone wrote:
> > > On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
> > > >However, I would not award +
On Wed, Jul 24, 2019 at 07:28:11PM +0200, to...@tuxteam.de wrote:
On Wed, Jul 24, 2019 at 01:10:49PM -0400, Michael Stone wrote:
On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
>However, I would not award +1 to the MUAs that, we are told,
>truncate the message, or even just the lin
On Wed, Jul 24, 2019 at 01:10:49PM -0400, Michael Stone wrote:
> On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
> >However, I would not award +1 to the MUAs that, we are told,
> >truncate the message, or even just the line, at the first
> >NUL byte. That could yield a message with a
On Wed, Jul 24, 2019 at 09:29:47AM -0500, David Wright wrote:
However, I would not award +1 to the MUAs that, we are told,
truncate the message, or even just the line, at the first
NUL byte. That could yield a message with a very different sense
from what the sender wrote.
And that is what happ
On Wed 24 Jul 2019 at 07:10:14 (-0400), rhkra...@gmail.com wrote:
> On Tuesday, July 23, 2019 11:07:37 AM Greg Wooledge wrote:
> > On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > > * From: Brad Rogers
> >
> > Oh, it's this guy again.
> >
> > /me looks at the raw mail messag
On Tuesday, July 23, 2019 11:07:37 AM Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > * From: Brad Rogers
>
> Oh, it's this guy again.
>
> /me looks at the raw mail message with less(1)
>
> * From: Brad Rogers ^@b...@fineby.me.uk^@
>
> Yup.
On Tue, Jul 23, 2019 at 09:35:59PM +0200, to...@tuxteam.de wrote:
On Tue, Jul 23, 2019 at 03:31:12PM -0400, Michael Stone wrote:
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
>I don't see any NUL characters, but x80 as shown below. I'm reading
>the cached message that mutt downlo
On Tue, Jul 23, 2019 at 03:38:33PM -0400, Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> > On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote:
> > > Yup. Two NUL bytes in the body of the message. How completely bizarre.
> > >
> > > Apparently what
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote:
> > Yup. Two NUL bytes in the body of the message. How completely bizarre.
> >
> > Apparently what mutt does is truncate that *line* at the first NUL
> > byte, but then sh
On Tue, Jul 23, 2019 at 03:31:12PM -0400, Michael Stone wrote:
> On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
> >I don't see any NUL characters, but x80 as shown below. I'm reading
> >the cached message that mutt downloaded from an IMAP server. Is that
> >different from you?
>
> I
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
I don't see any NUL characters, but x80 as shown below. I'm reading
the cached message that mutt downloaded from an IMAP server. Is that
different from you?
I see it as x80 in mutt and x00 in the raw file on the imap server. I
assum
On Tue, Jul 23, 2019 at 02:19:27PM -0500, David Wright wrote:
[...]
> I don't see any NUL characters, but x80 as shown below [...]
Oh, that's cute :-)
If I followed along correctly, the questionable mails have
neither Content-Type nor Content-Transfer-Encoding. So the
content type defaults to t
On Tue 23 Jul 2019 at 11:07:37 (-0400), Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > * From: Brad Rogers
>
> Oh, it's this guy again.
>
> /me looks at the raw mail message with less(1)
>
> * From: Brad Rogers ^@b...@fineby.me.uk^@
>
> Yu
On Tue, Jul 23, 2019 at 11:07:37AM -0400, Greg Wooledge wrote:
> On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> > * From: Brad Rogers
>
> Oh, it's this guy again.
>
> /me looks at the raw mail message with less(1)
>
> * From: Brad Rogers ^@b...@fineby.me.uk^@
>
>
On Tue, 23 Jul 2019 07:41:20 -0700
pe...@easthope.ca wrote:
Hello pe...@easthope.ca,
>* From: Brad Rogers * Date: Fri, 19 Jul 2019 19:32:46
>> It was replaced by Empathy.
...
>item are pale gray. Ideas about contacts?
All I know about Empathy is that it replaced
On Tue, Jul 23, 2019 at 07:41:20AM -0700, pe...@easthope.ca wrote:
> * From: Brad Rogers
Oh, it's this guy again.
/me looks at the raw mail message with less(1)
* From: Brad Rogers ^@b...@fineby.me.uk^@
Yup. Two NUL bytes in the body of the message. How completely bizarre.
Apparen
* From: Brad Rogers
On Fri, 19 Jul 2019 09:43:46 -0700
pe...@easthope.ca wrote:
Hello pe...@easthope.ca,
>ekiga is absent from buster.
It was replaced by Empathy.
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Every single on
On 2019-07-19 09:43:46, pe...@easthope.ca wrote:
> ekiga is absent from buster. Something involving ssl/tls?
Ekiga has been removed as the last upstream release was in 2013, see:
https://tracker.debian.org/pkg/ekiga
https://tracker.debian.org/news/1004860/removed-401-9-f
Hello again,
ekiga is absent from buster. Something involving ssl/tls?
I guess it will surface sooner or later. Any suggestions
for the interim? Add stretch to /etc/apt/sources.list
and try that?
Thanks, ... P.
--
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140
Appears that the graphical contact list in ekiga is based upon
~/.gconf/apps/ekiga/contacts/%gconf.xml .
Does the first character of the file name, %, have a significance
beyond being very unusual?
Manipulation of the graphical contact list is too inconvenient.
Does anyone keep contacts as plain
On Sat, Oct 16, 2010 at 01:55:24AM +0200, lee wrote:
> Unfortunately, ekiga is the only phone that would work. Twinkle
> remains unable to receive incoming calls; ekiga does, but it´s useless
> without a microphone. I´ve also tried linphone and qutecom, but they
> don´t work at all.
headset,
> >> Bluetooth...
> >
> > It´s a headset plugged into the soundcard which uses alsa. Ekiga is the
> > only application for which the microphone doesn´t work.
>
> What type? I guess it's a jack-ed device. I ask because Ekiga does not
> work for all
On Sat, Oct 16, 2010 at 01:04:32PM +, Camaleón wrote:
> This can sound quite simple but, have you also reviewed the microphone
> volume setting in Ekiga? How did you test your microphone? Is people
> saying that they cannot hear you? What about their volume settings? What
>
On Sat, 16 Oct 2010 14:50:50 +0200, lee wrote:
> On Sat, Oct 16, 2010 at 11:04:07AM +, Camaleón wrote:
>> (...)
>>
>> What kind of micro are we talking here? Jack audio, USB headset,
>> Bluetooth...
>
> It´s a headset plugged into the soundcard whi
On Sat, Oct 16, 2010 at 11:04:07AM +, Camaleón wrote:
> On Sat, 16 Oct 2010 01:55:24 +0200, lee wrote:
>
> > ekiga doesn´t get any input from the microphone, though it´s working
> > fine with other applications. Many users seem to have this problem, but
> > I haven´t f
On Sat, 16 Oct 2010 01:55:24 +0200, lee wrote:
> ekiga doesn´t get any input from the microphone, though it´s working
> fine with other applications. Many users seem to have this problem, but
> I haven´t found anyone who was able to fix it.
(...)
What kind of micro are we talking h
On Sat, Oct 16, 2010 at 04:20:04AM +0400, Roman Khomasuridze wrote:
> well, qutecom/wengophone always worked fine for me, never used ekiga, can't
> help with that what problems do you have with qutecom? mic? no incomming
> calls?
Qutecom was unsuccessful in making or receiving c
On Sat, Oct 16, 2010 at 08:11:27AM +0200, Csanyi Pal wrote:
> Rob Owens writes:
>
> > I use Ekiga. You need to try different settings under Preferences,
> > Audio Devices, Input Device.
>
> I'm using Ekiga too and my microphone works fine.
>
> I'
On Fri, Oct 15, 2010 at 08:59:08PM -0400, Rob Owens wrote:
> I use Ekiga. You need to try different settings under Preferences,
> Audio Devices, Input Device.
Yes, I tried all the devices there, but for others than the default
alsa device, ekiga says that only silence is being recorded o
Rob Owens writes:
> I use Ekiga. You need to try different settings under Preferences,
> Audio Devices, Input Device.
I'm using Ekiga too and my microphone works fine.
I'm using sound devices in Ekiga/menu/Edit/Settings:
for the ring: Default (PTLIB/ALSA)
for the output: H
I use Ekiga. You need to try different settings under Preferences,
Audio Devices, Input Device.
-Rob
On Sat, Oct 16, 2010 at 01:55:24AM +0200, lee wrote:
> Hi,
>
> ekiga doesn´t get any input from the microphone, though it´s working
> fine with other applications. Many users seem
well, qutecom/wengophone always worked fine for me, never used ekiga, can't
help with that what problems do you have with qutecom? mic? no incomming
calls?
as of other sip phones, Xlite is the best, though it freeware (not FOSS),
but it's best softphone available out there.. Hope
Hi,
ekiga doesn´t get any input from the microphone, though it´s working
fine with other applications. Many users seem to have this problem,
but I haven´t found anyone who was able to fix it.
Unfortunately, ekiga is the only phone that would work. Twinkle
remains unable to receive incoming calls
oth audio under Debian lenny/sid
http://quail.southernvaleslug.org/webblog/archives/85
Bluetooth handsfree with laptop in debian squeeze
http://forums.debian.net/viewtopic.php?f=16&t=49867
***
> Here is quotation from ekiga wiki [1]:
>
> Warning: btsco (bluetooth linux driver) is no
ese helps:
***
Bluetooth audio under Debian lenny/sid
http://quail.southernvaleslug.org/webblog/archives/85
Bluetooth handsfree with laptop in debian squeeze
http://forums.debian.net/viewtopic.php?f=16&t=49867
***
> Here is quotation from ekiga wiki [1]:
>
> Warning: btsco (bluetooth linu
Hi all
I switched to Squeeze and try out bluetooth Nokia headset. Blueman can
see it, so I can pair, add it, enable. This works perfect, but
unfortunately no new audio device appeared.
Here is quotation from ekiga wiki [1]:
Warning: btsco (bluetooth linux driver) is no longer maintained and
Tom Ashley wrote:
>
> On Wed, 2009-06-10 at 22:58 -0400, H.S. wrote:
>> Hello,
>>
>> After a recent upgrade we got new Ekiga in Testing (Ekiga
>> 3.2.1~git20090515.9d0263-1). Wonderful, since the last version of
>> segfaulting (due to ptlib I think). But now th
On Wed, Jun 10, 2009 at 7:58 PM, H.S. wrote:
> Hello,
>
> After a recent upgrade we got new Ekiga in Testing (Ekiga
> 3.2.1~git20090515.9d0263-1). Wonderful, since the last version of
You might try downloading the source for 3.2.4 off Ekiga's website
along with the correspondi
On Wed, 2009-06-10 at 22:58 -0400, H.S. wrote:
> Hello,
>
> After a recent upgrade we got new Ekiga in Testing (Ekiga
> 3.2.1~git20090515.9d0263-1). Wonderful, since the last version of
> segfaulting (due to ptlib I think). But now this new version is keeping
> the CPU bus
Hi,
On Thu, Jun 11, 2009 at 4:58 AM, H.S. wrote:
> Hello,
>
> After a recent upgrade we got new Ekiga in Testing (Ekiga
> 3.2.1~git20090515.9d0263-1). Wonderful, since the last version of
> segfaulting (due to ptlib I think). But now this new version is keeping
> the CPU bus
Hello,
After a recent upgrade we got new Ekiga in Testing (Ekiga
3.2.1~git20090515.9d0263-1). Wonderful, since the last version of
segfaulting (due to ptlib I think). But now this new version is keeping
the CPU busy and the audio is broken. It used to work wonderfully in the
earlier version
Michael Pobega wrote:
> On Mon, May 11, 2009 at 10:32:25AM -0400, H.S. wrote:
>> Hello,
>>
>> I did an upgdate of my Debian Testing machine earlier today and now when
>> I start Ekiga, it segfaults.
>>
>> The debugging info from Ekiga is:
>> [... $&g
On Mon, May 11, 2009 at 10:32:25AM -0400, H.S. wrote:
> Hello,
>
> I did an upgdate of my Debian Testing machine earlier today and now when
> I start Ekiga, it segfaults.
>
> The debugging info from Ekiga is:
> [... $> ekiga -d4 ...]
>
> This is on Ekiga version
Hello,
I did an upgdate of my Debian Testing machine earlier today and now when
I start Ekiga, it segfaults.
The debugging info from Ekiga is:
$> ekiga -d4
2009/05/11 10:29:30.042 0:00.842 ekiga ekiga
Version 2.0.12 by on Unix Linux (2.6.26-2-686-i686) at 2009/5/11
On Tue, 17 Mar 2009 19:27:50 -0400
"H.S." wrote:
> Hello,
>
> Perhaps I am trying to do something that is not possible, though
> certainly it is inconvenient.
>
> If I try to make a call with ekiga when a skype call is active (and
> the other way around), I
Hello,
Perhaps I am trying to do something that is not possible, though
certainly it is inconvenient.
If I try to make a call with ekiga when a skype call is active (and the
other way around), I get an error saying there is a problem with a sound
device. I was under the impression that the mixer
ok, thanks!
putting in the audio-admin section all devices to pulse solved the
problem for the cd-player...
but now i noticed that another application doesn't want to play with
pulse:
ekiga
just hitting the echo adress to test i get on the console:
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix
ice chats well.
> >
> > kopete seems to be able to use video, but not audio, for some strange
> > reason. Telepathy/Empathy does not seem to support voice chats with
> > Yahoo accounts (which are only supported through pidgin's libpurple).
>
> somewhat OT, bu
on. Telepathy/Empathy does not seem to support voice chats with
> Yahoo accounts (which are only supported through pidgin's libpurple).
somewhat OT, but Ekiga may do what you want -- it can't talk
to Yahoo, but there are builds of it for Lin/Win/OSX, so if
you're communicating on a
On 9/22/07, Manu Hack <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> After a dist-upgrade (I'm using sid), ekiga can't be installed
> anymore. Is there any way to install it in sid?
>
> Thanks!
>
> Manu
I have Ekiga installed in sid; right at the moment t
Hi all,
After a dist-upgrade (I'm using sid), ekiga can't be installed
anymore. Is there any way to install it in sid?
Thanks!
Manu
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
64 matches
Mail list logo
