After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 363628 - crash in Ekiga Softphone: Nothing actually. Ekiga ...
crash in Ekiga Softphone: Nothing actually. Ekiga ...
Status: RESOLVED DUPLICATE of bug 364480
Product: ekiga
Classification: Applications
Component: PTLIB
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-20 10:33 UTC by Duncan Lithgow
Modified: 2006-11-21 12:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Duncan Lithgow 2006-10-20 10:33:58 UTC
Version: 2.0.3

What were you doing when the application crashed?
Nothing actually. Ekiga was open and started, it had registered my accounts - but was not in use - and had not been used since system boot up. I just got a bunch of updates (20th October) but they didn't include an ekiga update. These problems started immediately after the notification popup appeared.

My only other clue is that I was running Internet Explorer at the same time. Several things crashed at once, here's the list:
* The panel's notification icon - so the popup when my update was finished had to pop up over the ubuntu logo on the Applications menu
* Internet explorer in WINE using ie4linux package
* Something running the gnome panels crashed - after CTRL+ALT+BACKSPACE I have no panels. Gnome said it has detected panels running and will exit. So I guess the panels crashed too and are still running somewhere.
I think these were also open:
* The default PDF viewer (sorry can't remember the name)
* Evolution
* Nautilus

I will install ekiga-dbg for next time...


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 136679424 vsize: 0 resident: 136679424 share: 0 rss: 28901376 rss_rlim: 0
CPU usage: start_time: 1161339510 rtime: 0 utime: 379 stime: 0 cutime:317 cstime: 0 timeout: 62 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/ekiga'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1247304016 (LWP 5427)]
[New Thread -1319814240 (LWP 6110)]
[New Thread -1319548000 (LWP 6109)]
[New Thread -1319281760 (LWP 6108)]
[New Thread -1310229600 (LWP 6107)]
[New Thread -1309201504 (LWP 6094)]
[New Thread -1308935264 (LWP 6093)]
[New Thread -1298891872 (LWP 5834)]
[New Thread -1298625632 (LWP 5832)]
[New Thread -1300235360 (LWP 5830)]
[New Thread -1249227872 (LWP 5695)]
[New Thread -1248961632 (LWP 5694)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 11 (Thread -1249227872 (LWP 5695))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PTime::operator-
    from /usr/lib/libpt.so.1.10.2
  • #5 PIPCacheData::HasAged
    from /usr/lib/libpt.so.1.10.2
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 PString::PString
    from /usr/lib/libpt.so.1.10.2
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
    from /usr/lib/libpt.so.1.10.2
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 PCaselessString::PCaselessString
    from /usr/lib/libpt.so.1.10.2
  • #18 vtable for PTime
  • #19 ??
  • #20 ??
  • #21 ??
    from /usr/lib/libpt.so.1.10.2
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 PHostByName::GetHost
    from /usr/lib/libpt.so.1.10.2
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 PIPSocket::Address::operator=
    from /usr/lib/libpt.so.1.10.2
  • #30 ??
  • #31 ??
  • #32 PWLibFactoryLoader::PluginLoaderStartup_PString
    from /usr/lib/libpt.so.1.10.2
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??

Comment 1 Snark 2006-10-20 10:39:49 UTC
Can't you have run out of memory and the kernel begun to kill processes ?
Comment 2 Snark 2006-10-20 10:41:36 UTC
Let me be more specific in my question : why do you report this as an ekiga bug if ekiga was just one of the programs dying?

After all, the fact that parts of your whole desktop died makes it very unlikely to be a bug in ekiga!
Comment 3 Duncan Lithgow 2006-10-20 11:09:53 UTC
I reported this against ekiga because bug-buddy started after picking up the ekiga crash. In other words I don't know what else to do.

My system is documented here: https://wiki.ubuntu.com/LaptopTestingTeam/HP_Pavilion_DV8220EA

I've got 1Gb ram and 1Gb swap - that shouldn't run out of memory should it?

I can't find ekiga-dbg - what's the best way to debug for ekiga?
Comment 4 Snark 2006-10-20 11:28:49 UTC
Uh... it shouldn't run out of memory unless you run something very leaky indeed.

The fact that several things crashed at once makes me think it's very highly probably *not* an ekiga bug.
Comment 5 Duncan Lithgow 2006-10-22 08:28:46 UTC
And now after a reboot I've got bugbuddy reporting another ekiga crash. Bug 364113
Comment 6 Snark 2006-10-22 09:06:51 UTC
This is very different : in one case several applications stopped to work simultaneously, and the other is a single application crashing.

In the first case (this bug report), I think ekiga isn't culprit. In the second case, it certainly is.
Comment 7 Damien Sandras 2006-10-23 09:22:25 UTC
I also think Ekiga is not the culprit on this one. If everything crashed, I don't think Ekiga can be held as culprit.

Closing.
Comment 8 Duncan Lithgow 2006-10-23 19:19:37 UTC
Okay, maybe it isn't ekiga - but something is buggy. So I've reopened the bug.

I can't see a way of marking it as caused by an unknown package - so sorry bug-buddy team - I've put it in your lap hoping that you guys can make sense of the output at the start of the bug report.
Comment 9 Damien Sandras 2006-10-23 19:39:26 UTC
Reassigning to Ekiga if it can make you happy, but that bug is unlikely to be fixed without more information.

Please provide a way to reproduce it, so that we can confirm it is an Ekiga bug. At best, try to provide a sane backtrace.
Comment 10 Damien Sandras 2006-11-21 12:09:01 UTC

*** This bug has been marked as a duplicate of 364480 ***