gdmsetup crashed with SIGSEGV in g_file_load_partial_contents_finish()

Bug #283162 reported by NITSCH Zoltán
66
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GLib
Fix Released
Medium
glib2.0 (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs
Hardy
Won't Fix
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gdm

Nautilus crashed on sturtup, after trying to send bugreport this new crash happened.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/sbin/gdmsetup
NonfreeKernelModules: nvidia
Package: gdm 2.20.7-0ubuntu1.1
ProcAttrCurrent: unconfined
ProcCmdline: gdmsetup
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gdm
StacktraceTop:
 g_file_load_partial_contents_finish ()
 ?? ()
 ?? () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 g_main_context_dispatch ()
Title: gdmsetup crashed with SIGSEGV in g_file_load_partial_contents_finish()
Uname: Linux 2.6.24-21-generic x86_64
UserGroups: sambashare vboxusers

Tags: apport-crash
Revision history for this message
NITSCH Zoltán (boritek) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:on_autorun_loaded (source_object=0x1190d80, res=0xb53de0, user_data=<value optimized out>) at ghalmount.c:208
load_contents_open_callback (obj=<value optimized out>, open_res=<value optimized out>,
complete_in_idle_cb (data=0xb53de0) at /build/buildd/glib2.0-2.16.6/gio/gsimpleasyncresult.c:563
IA__g_main_context_dispatch (context=0x66d5b0) at /build/buildd/glib2.0-2.16.6/glib/gmain.c:2012
g_main_context_iterate (context=0x66d5b0, block=1, dispatch=1, self=<value optimized out>)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gdm:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gdm:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in glib:
status: Unknown → Confirmed
Revision history for this message
lesshaste (clifford-cs) wrote :

This looks similar to the bug that just got closed here http://bugzilla.gnome.org/show_bug.cgi?id=556458 (see in particular Comment #24 onwards) which was marked as a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=545203 and then fixed.

There is a patch which has already been applied for intrepid and jaunty apparently which can be found here http://bugzilla.gnome.org/attachment.cgi?id=115443&action=view. It's a very small patch, could it be applied for hardy?

Raphael

Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug is fixed in intrepid and jaunty

Changed in glib2.0 (Ubuntu):
status: Triaged → Fix Released
Changed in glib:
status: Confirmed → Unknown
Revision history for this message
Sebastien Bacher (seb128) wrote :

confirming as a low priority candidate for an hardy update

Changed in glib2.0 (Ubuntu Hardy):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Confirmed
Changed in glib:
status: Unknown → Fix Released
Changed in glib:
importance: Unknown → Medium
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix".

Changed in glib2.0 (Ubuntu Hardy):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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