gwibber crashed with segfault

[jMehdi]

Binary package hint: gwibber

kernel: [246370.896605] gwibber[25242]: segfault at 88 ip b607501b sp bf81e2a0 error 4 in libwebkit-1.0.so.1.0.0[b5ce1000+7d8000]

[jMehdi (jmehdi-deactivatedaccount-deactivatedaccount)]

Architecture: i386
DistroRelease: Ubuntu 9.04
Package: gwibber 0.9.2~bzr263-0ubuntu1~jaunty
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

[Krzysztof Klimonda (kklimonda)]

Thanks for your report, unfortunately it doesn't contain informations that developers need to work on it.
If you can reproduce the crash can you the following:
1) Make sure that your system is up to date (by running System->Administration->Update Manager and checking for updates)
2) in terminal type:
sudo force_start=1 /etc/init.d/apport restart
2a) You can check if apport is enabled by doing
cat /proc/sys/kernel/core_pattern
in terminal. It should return
"|/usr/share/apport/apport %p %s %c"
3) Now work with gwibber until it crashes again, it should trigger a window which asks if you want to report a problem. Choose "Report Problem" and send a full report to Launchpad, then proceed as usually.
4) Mark this bug as a duplicate of a new bug.

[jMehdi (jmehdi-deactivatedaccount-deactivatedaccount)]

ok, I did that, gwibber crashed again and I chose "Report problem" but then a message box displays: "The problem cannot be reported: This is not a genuine Ubuntu package"

[Janith Sampath Bandara (janith)]

I also got this message when my firefox is crashed.!

[Alexander Sack (asac)]

please check whether this happens with the latest karmic packages of gwibber. if you are on jaunty and cannot try karmic check-out the daily PPA to get equivalent backports: https://edge.launchpad.net/~gwibber-daily/+archive/ppa.

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!