_usr_bin_gnome-sound-properties. 1000.crash

[Paul Bélair]

Binary package hint: nautilus

/var/crash/_usr_bin_gnome-sound-properties.1000.crash
/var/crash/_usr_bin_rhythmbox.1000.crash
/var/crash/_usr_lib_totem_totem-plugin-viewer.1000.crash

ProblemType: Bug
Architecture: i386
Date: Sat May 19 21:19:43 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.18.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcCwd: /home/ezx62jw
ProcEnviron:
 LANGUAGE=fr_CA:fr
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
Uname: Linux ezx62jw-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

[Sebastien Bacher (seb128)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>. We'd be grateful if you would then provide a more complete description of the problem.

 We have instructions on debugging some types of problems. <http://wiki.ubuntu.com/DebuggingProcedures> Thanks!

[Paul Bélair (pbelair)]

Le mardi 29 mai 2007 à 20:23 -0400, Paul a écrit :
> > Hi,
> >
> > After an update of the kernel on May 28th, gnome-sound-properties was
> > restablished. Rhythmbox and Totem-plugin-viewer was not.
> >
> > I'd like to know if something was being done about the bug. I did not
> > receive any comments or update on the manner.
> >
> > Thank you for taking the time to read me and answer my questions.

Thank you for your bug. Could you reply on launchpad rather than by
direct mail? As commented on the website it would be nice to have extra
details on the bug

If more info is required I would like to help if possible.

[Pedro Villavicencio (pedro)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.