gvsfd-metadata segfault in live 10.04

Bug #588550 reported by Peter Brewster
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gvfs

1) 10.04 current to June 1. Bug also present in 9.10.
2) Package gvfs via upgrade from 9.10 to 10.04. The 9.10 was a fresh install and current to the time of upgrade. Problem application is /usr/lib/gvfs/gvfsd-metadata.
3) Live system created using remastersys and unetbootin-linux to USB flash drive. The system works perfectly, before and after the segfault. However the segfault causes an "Application problem" window saying "Sorry, the program gvsfd-metadata closed unexpededly" which remains on-display until closed. This is impossible to explain away for the intended users of system.
4) From message log:
Jun 1 16:07:26 ppeterb kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jun 1 16:07:26 ppeterb rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="831" x-info="http://www.rsyslog.com"] (re)start
.
.
Jun 1 16:07:28 ppeterb kernel: [ 21.591269] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jun 1 16:07:29 ppeterb kernel: [ 21.924094] intel8x0_measure_ac97_clock: measured 53661 usecs (2586 samples)
Jun 1 16:07:29 ppeterb kernel: [ 21.924100] intel8x0: clocking to 48000
Jun 1 16:07:52 ppeterb pulseaudio[2023]: ratelimit.c: 1 events suppressed
Jun 1 16:08:48 ppeterb kernel: [ 100.375155] gvfsd-metadata[2179]: segfault at 7 ip 08052aa6 sp bfa52b90 error 6 in gvfsd-metadata[8048000+c000]

Nothing further logged

Revision history for this message
Peter Brewster (peter-brewster) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in gvfs (Ubuntu):
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Peter Brewster (peter-brewster) wrote : Re: [Bug 588550] Re: gvsfd-metadata segfault in live 10.04
Download full text (3.2 KiB)

Your request notwithstanding, aaport refuses to make a report - it claims gvfs is "not a genuine Ubuntu package." The crash report is attached.

Peter

----- Original Message -----
From: Pedro Villavicencio
To: <email address hidden>
Sent: Wednesday, June 02, 2010 4:46 PM
Subject: [Bug 588550] Re: gvsfd-metadata segfault in live 10.04

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.

** Changed in: gvfs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gvfs (Ubuntu)
       Status: New => Invalid

--
gvsfd-metadata segfault in live 10.04
https://bugs.launchpad.net/bugs/588550
You received this bug notification because you are a direct subscriber
of the bug.

Status in “gvfs” package in Ubuntu: Invalid

Bug description:
Binary package hint: gvfs

1) 10.04 current to June 1. Bug also present in 9.10.
2) Package gvfs via upgrade from 9.10 to 10.04. The 9.10 was a fresh install and current to the time of upgrade. Problem application is /usr/lib/gvfs/gvfsd-metadata.
3) Live system created using remastersys and unetbootin-linux to USB flash drive. The system works perfectly, before and after the segfault. However the segfault causes an "Application problem" window saying "Sorry, the program gvsfd-metadata closed unexpededly" which remains on-display until closed. This is impossible to explain away for the intended users of system.
4) From message log:
Jun 1 16:07:26 ppeterb kernel: imklog 4.2.0, log source = /proc/kmsg started.
Jun 1 16:07:26 ppeterb rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="831" x-info="http://www.rsyslog.com"] (re)start
.
.
Jun 1 16:07:28 ppeterb kernel: [ 21.591269] Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jun 1 16:07:29 ppeterb kernel: [ 21.924094] intel8x0_measure_ac97_clock: measured 53661 usecs (2586 samples)
Jun 1 16:07:29 ppeterb kernel: [ 21.924100] intel8x0: clocking to 48000
Jun 1 16:07:52 ppeterb pulseaudio[2023]: ratelimit.c: 1 events suppressed
Jun 1 16:08:48 ppeterb kernel: [ 100.375155] gvfsd-metadata[2179]: segfault at 7 ip 08052aa6 sp bfa52b90 error 6 in gvfsd-metadata[8048000+c000]

Nothing further logged

To unsubscribe from this bug, go to:
https://bugs.lau...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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