gvfsd-trash crashed with SIGSEGV in g_idle_funcs()

[Niels Egberts]

Binary package hint: gvfs

Upon starting Ubuntu Intrepid the gvfsd-trash crashed.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Fri Jul 25 19:00:49 2008
Disassembly: 0x7ff656a343ec:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gvfs/gvfsd-trash
NonfreeKernelModules: nvidia
Package: gvfs-backends 0.99.3-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.16 /org/gtk/gvfs/exec_spaw/2
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? () from /lib/libpthread.so.0
 ?? ()
 g_idle_funcs () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch ()
Title: gvfsd-trash crashed with SIGSEGV in g_idle_funcs()
Uname: Linux 2.6.26-4-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:?? ()
?? () from /lib/libpthread.so.0
?? ()
g_idle_funcs () from /usr/lib/libglib-2.0.so.0
IA__g_main_context_dispatch (context=0xfd7390)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[sam tygier (samtygier)]

also seeing this on amd64. i tried
ubuntu@ubuntu:~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/lib/gvfs/gvfsd-trash
Added new job source 0x7093e98 (GVfsBackendTrash)
Queued new job 0x7095c80 (GVfsJobMount)
send_reply, failed: 0
register_mount_callback, mount_reply: (nil), error: 0x70c7e08
Mount failed: DBus error org.freedesktop.DBus.Error.InvalidArgs: Mountpoint Already registered

i am not sure if there is anything more i should seen as its not an app that is usually started by hand. looks to me that it did not actually start.

[ebnf (eric-zeitler)]

I get the same message when trying to run valgrind.

[Alexander Rødseth (alexanro)]

I got this bug too.

[sojourner (itsmealso2)]

I also have it here on intrepid amd64. The way I produced the crash was , after updating august 5 PM on bootup and trying to do my AM update from terminal with aptitude I found that up arrow to scroll the term actualy took a screenshot ! I could type into the window but up arrow would not scroll just take screenshots . attempting to cleanup my destop by deleting the screenshots crashed GVFSD .

[sojourner (itsmealso2)]

I cannot reproduce the crash now using the method described just above .

[KevinM (kevbert1)]

This was on an AMD64 PC, Intrepid -4 kernel.
I got this bug when trying to access another drive via Places - Removable Media.

[Marc (m-chabot)]

Same thing here

[amahfouz (eldood)]

Yep same as KevinM but i was trying to access a fixed drive

[ibizatunes (ibizatunes)]

I just got this bug after a reboot after a some updates, i wasnt accessing any drives

[Hew (hew)]

Do not attach .crash files as they may contain private information. A .crash file has already been submitted by the reporter. I have removed the attachment.

[darkenergy (darkenergy)]

can confirm this bug.
happened on plugin an esata device and at some other occasions

[locust (marineworks)]

I get this bug too.
But it seems to have no following troubles on my system.
Intrepid-64 2.6.26.3
HP pavillion dv6000
best regards and good job!
David

[Italo Canepa (italoc)]

I have this bug too.

[Olivier Cortès (olive)]

HI,
I have this bug too. Latest Intrepid to date, Sony Vaio BZ11XN (dmesg, dmidecode, lspci, uname, proc/acpi… @ http://deep-ocean.net/files/sony/ )
Happened upon session open, just after i entered my session-keychain password. I didn't do anything particular except that.

[kseise (kevin-seise)]

Same problem here with Intrepid Beta on 64 bit

[Alexander Jones (alex-weej)]

Every time I log in.

[kulight (kulight)]

i also get this in amd 64

[Jose Luis Rodilla (jlrodilla)]

Confirmed in amd64

[kseise (kevin-seise)]

Confirmed here also. Just booted into Intrepid and got the crash message after a few minutes of sitting idle.

[Sef (jo-ker)]

I got this bug right after booting up.

[Jose Luis Rodilla (jlrodilla)]

Now, I have this bug just after booting into Intrepid.

[phidia (jyon)]

same here-as described previously AMD64 just let crash reporter do it's thing.

[nullack (nullack)]

Moving status to confirmed as requested valgrind was attached by a user. Also to add that this is still occurring at what seems to be intermittent intervals on bootup of Intrepid 13/09/08.

[Arnaud Malapert (amalapert)]

did an aptitude full-upgrade and got the message right after booting up on Sept 13th 08

[Sef (jo-ker)]

I just logged in and it occured in 64-bit Intrepid Ibex with all the updates as of 18 Sep 08.

[Sam_ (and-sam)]

Hi,
after booting Live CD Intrepid Alpha4 this bug occured, adding, that on the first boot with the same CD few weeks ago this bug did not occur. However, I was asked to submit a report to developers and that is what I did now, hope it was submitted and helps. Not sure, but the difference to the first boot was that I choosed german localization and today I leave the english, beside, that is why my keyboard gives me a hard time at the moment to find the right keys.

For the record, the reason I run once in a while Live CD is some testing about xorg and at the moment I was supposed to test a bug within Totem, what I will do after this report. Actually I run Hardy LTS on amd_64.

[Sam_ (and-sam)]

Hi again,
confirming the bug doesn't occur when I boot with german localization.

[kseise (kevin-seise)]

This happened while my computer was sitting idle overnight. Running 64 bit version of Intrepid Alpha 6.

[Graham Inggs (ginggs)]

I was getting this error after upgrading from Hardy x86_64 to Intrepid Alpha 4. I've just upgraded to Intrepid Alpha 6 and am still getting the error.

[Jeff Schroeder (sejeff)]

Got this bug when cleaning up some old cruft from an intrepid upgrade:
sudo apt-get remove linux-image-2.6.27-2-generic linux-image-2.6.24-19-generic linux-image-2.6.24-16-generic -y

[Julio Lajara (ju2wheels)]

I can confirm on Intrepid Alpha 6 AMD64.

[Marcel (marcel-vd-berg)]

The bug occurred after a very long time loading my user preferences, directly after login.

[Sebastien Bacher (seb128)]

there is has been no recent duplicate, that was probably the same issue than bug #252174 which has been fixed, closing the bug now, feel free to reopen if run into the issue using the current intrepid version though