[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-22 Thread Sebastien Bacher
*** This bug is a duplicate of bug 560588 ***
https://bugs.launchpad.net/bugs/560588

Thanks for the bug report. This particular bug has already been
reported, but feel free to report any other bugs you find.

** Package changed: gdm (Ubuntu) = libgnome-keyring (Ubuntu)

** Changed in: libgnome-keyring (Ubuntu)
   Status: Incomplete = Invalid

** This bug has been marked a duplicate of bug 560588
   Nautilus in Lucid Lynx Samba could not display network location dbus error 
gvfsd-smb-browse

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-10 Thread Charlie Kravetz
The stacktrace above is not useable to find what caused this issue.
Please try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash  and upload the backtrace
(as an attachment) to the bug report. This will greatly help us in
tracking down your problem.

** Changed in: gdm (Ubuntu)
   Status: New = Incomplete

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-06 Thread Pedro Villavicencio
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: gdm (Ubuntu)
   Importance: Undecided = Medium

** Changed in: gdm (Ubuntu)
   Status: New = Invalid

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-06 Thread Sebastien Bacher
You can also retrace the crash file locally and add the stracktrace to
the bug, you can unpack the crash file using apport-unpack to get it.

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-06 Thread Henk Bekkering
/etc/default/apport is already enabled, and there is a crash report
file.

double click on the crash report says:

The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be 
retrieved.
Apport does not support reporting these crashes.

What should I do (is it save to attach the crash file?)

** Changed in: gdm (Ubuntu)
   Status: Invalid = New

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-06 Thread Henk Bekkering
I changed the status back to new to make sure this issue is looked at again.
If it was not correct to do so, please tell me (and I am sorry)

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-06 Thread Henk Bekkering
With apport-unpack I extracted the Stacktrace:

# cat Stacktrace
#0  0x00d11422 in __kernel_vsyscall ()
No symbol table info available.
#1  0x0085b641 in raise () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2  0x0085ea72 in abort () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#3  0x00255dd3 in g_assertion_message () from /lib/libglib-2.0.so.0
No symbol table info available.
#4  0x0025642d in g_assertion_message_expr () from /lib/libglib-2.0.so.0
No symbol table info available.
#5  0x00c7c802 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#6  0x00c7bb55 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#7  0x00c7c8fc in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#8  0x00c7d5b1 in ?? () from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#9  0x00c86938 in gnome_keyring_find_network_password_sync ()
   from /usr/lib/libgnome-keyring.so.0
No symbol table info available.
#10 0x08064864 in ?? ()
No symbol table info available.
#11 0x08050667 in ?? ()
No symbol table info available.
#12 0x003b7107 in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#13 0x003b7318 in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#14 0x003b7b06 in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#15 0x003b955b in ?? () from /usr/lib/libsmbclient.so.0
No symbol table info available.
#16 0x0805249f in ?? ()
No symbol table info available.
#17 0x08059b68 in ?? ()
No symbol table info available.
#18 0x080589fd in ?? ()
No symbol table info available.
#19 0x0805476e in ?? ()
No symbol table info available.
#20 0x0025acec in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#21 0x00258dcf in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#22 0x00dee96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#23 0x008fe9de in clone () from /lib/tls/i686/cmov/libc.so.6

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556809] Re: Crash report gvfs-mount during logon

2010-04-06 Thread Henk Bekkering
Some more info from the crashfile:

# cat Package
gvfs-backends 1.6.0-0ubuntu1

# cat ProcCmdline 
/usr/lib/gvfs/gvfsd-smb --spawner :1.6 /org/gtk/gvfs/exec_spaw/0

# cat UnreportableReason 
The program crashed on an assertion failure, but the message could not be 
retrieved. Apport does not support reporting these crashes.cat

# cat UserGroups 
adm admin cdrom dialout lpadmin plugdev sambashare

-- 
Crash report gvfs-mount during logon
https://bugs.launchpad.net/bugs/556809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs