gnome-panel crashed with SIGSEGV in g_type_instance_get_private()

Bug #262017 reported by Matt Zimmerman on 2008-08-27
Affects Status Importance Assigned to Milestone
libsoup2.4 (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

This crash was reported shortly after I resumed from hibernation

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:
ProcAttrCurrent: unconfined
ProcCmdline: gnome-panel
Signal: 11
SourcePackage: gnome-panel
 g_type_instance_get_private ()
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 g_main_context_dispatch ()
Title: gnome-panel crashed with SIGSEGV in g_type_instance_get_private()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin cdrom dialout fuse kvm lpadmin plugdev sambashare video

Matt Zimmerman (mdz) wrote :

StacktraceTop:IA__g_type_instance_get_private (instance=0x46805a8c50000002,
update_address (addr=0x46805a8c50000002, lookup=0x1f862c0) at soup-address.c:514
lookup_resolved (lookup=0x1f862c0, status=200, user_data=<value optimized out>)
do_async_callback (user_data=<value optimized out>) at soup-dns.c:523
IA__g_main_context_dispatch (context=0x10e4b10)

Changed in gnome-panel:
importance: Undecided → Medium
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here:

Changed in gnome-panel:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in libsoup:
status: Unknown → New
Changed in libsoup:
importance: Unknown → Critical
Changed in libsoup:
status: New → Expired
Jamie Strandboge (jdstrand) wrote :

Thank you for reporting this bug to Ubuntu. 8.10 reached EOL. Please see this document for currently supported Ubuntu releases:

Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.

Changed in libsoup2.4 (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.