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 402857 - It claims to have ended unexpectedly, but I closed it normally.
It claims to have ended unexpectedly, but I closed it normally.
Status: RESOLVED DUPLICATE of bug 349051
Product: epiphany
Classification: Core
Component: General
2.14.x
Other other
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2007-01-31 15:41 UTC by Rune Schjellerup Philosof
Modified: 2007-02-06 08:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
Stacktrace of error (2.95 KB, text/plain)
2007-02-06 07:31 UTC, Rune Schjellerup Philosof 		Details

Description Rune Schjellerup Philosof 2007-01-31 15:39:19 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: epiphany
Severity: Normal
Version: GNOME2.14.3 2.14.3
Gnome-Distributor: Ubuntu
Synopsis: It claims to have ended unexpectedly, but I closed it normally.
Bugzilla-Product: epiphany
Bugzilla-Component: General
Bugzilla-Version: 2.14.3
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
A message box popped up claiming that the program had ended
unexpectedly.
This was weird since I had just pressed the close button of the
program's window.

I have not been able to reproduce it since.

Steps to reproduce the crash:
1.  close epiphany
2.
3.

Expected Results:
If the message box had not popped up, all would be fine :)

How often does this happen?
First time

Additional Information:



Debugging Information:

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

(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 -1227979072 (LWP 13905)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 106843

Thread 1 (Thread -1227979072 (LWP 13905))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 gtk_moz_embed_get_title
    from /usr/lib/firefox/libgtkembedmoz.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #8 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main_iteration
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #16 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2007-01-31 15:41 -------


Unknown version 2.14.3 in product epiphany.  Setting version to "2.14.x".
Comment 1 Reinout van Schouwen 2007-01-31 16:09:17 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. 

If you could try with a newer Epiphany version (2.16.3 or >= 2.17.90) that would be great as well.

Thanks in advance!
Comment 2 Rune Schjellerup Philosof 2007-02-01 10:42:30 UTC 
(In reply to comment #1)
> Can you get us a stack trace with debugging symbols?

I would, if I could reproduce the problem.
I will install the debug stuff, so that it's handy if the problem reoccurs.
Comment 3 Reinout van Schouwen 2007-02-01 21:32:06 UTC 
Closing this bug report per reporter's comment #2. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 4 Rune Schjellerup Philosof 2007-02-06 07:31:17 UTC 
Created attachment 81982 [details]
Stacktrace of error

It happened again.
Since last time I have installed more debug packages.

Enjoy
Comment 5 Reinout van Schouwen 2007-02-06 08:06:45 UTC 
Thanks for the follow up. It looks like the same trace as bug 348397, which is a duplicate of 349051.

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