I see what you are saying, but it was one of those automatic crash
notifications and I was using Karmic Koala as far as I recollect. I
certainly got the notification - I don't believe I was using jaunty at
the time. I only have jaunty or karmic on the computer - so if that
doesn't exist in karmic,
This just happened in karmic alpha 6. I assume the automatic crash
report will have uploaded the various files associated.
--
gvfs-hal-volume-monitor crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/255511
You received this bug notification because you are a member of
Hello Yannick,
I cannot answer your question as I have not tried ekiga again, mainly
because I [eventually] tracked down the likely cause of ekiga not
working to a hardware issue with the modem/router from my isp, which I
have been unable to port forward ??? locked by isp ??? Sorry I can't
help.
Public bug reported:
Binary package hint: ekiga
I have gone to considerable difficulty getting ekiga to a point where it
connects to the ekiga '500' address and I can successfully do the audio test
where I can hear what I have said return through the earphones during the druid
setup phase. My
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23675135/Dependencies.txt
--
ekiga gets stuck on standby
https://bugs.launchpad.net/bugs/340165
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ekiga in ubuntu.
--
