nautilus crashed when attempting to share publicly a picture via right-click and UbuntuOne

Bug #643431 reported by Gerwin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu One Client
In Progress
High
Rodrigo Moya
ubuntuone-client (Ubuntu)
In Progress
Medium
Rodrigo Moya

Bug Description

Binary package hint: ubuntuone-client

Description: Ubuntu maverick (development branch)
Release: 10.10

gerwin@s7110:~$ apt-cache policy nautilus
nautilus:
  Installiert: 1:2.31.92-0ubuntu1
  Kandidat: 1:2.31.92-0ubuntu1
  Versionstabelle:
 *** 1:2.31.92-0ubuntu1 0
        500 http://de.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
        100 /var/lib/dpkg/status

Expected: Right-clicked on a picture file in the UbuntuOne Shared directory, chose UbuntuOne->Veröffentlichen (publish) in the context menu. Expected some sort of link being displayed from where to download the picture.

Instead, nautilus crashed, all graphically visible instances of the file manager disappeared, the bug reporting feature came up instead.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: ubuntuone-client-gnome 1.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CheckboxSubmission: 60f08cd5c2980300d1baece2421e5c60
CheckboxSystem: 2d991aea396681f7e366e4b093d459e1
CrashCounter: 1
Date: Mon Sep 20 12:53:30 2010
ExecutablePath: /usr/bin/nautilus
ProcCmdline: nautilus --sm-client-id 10b26ef0fb18cc8f79126269118089906100000023470024 --sm-client-state-file /home/username/.config/session-state/nautilus-1284909916.desktop
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x49ce89 <g_hash_table_iter_init+41>: mov 0x24(%edx),%edx
 PC (0x0049ce89) ok
 source "0x24(%edx)" (0x0000011c) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntuone-client
StacktraceTop:
 g_hash_table_iter_init () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/nautilus/extensions-2.0/libnautilus-ubuntuone.so
 g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_hash_table_iter_init()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Gerwin (gerwin-klaus) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_hash_table_iter_init () from /lib/libglib-2.0.so.0
 ubuntuone_nautilus_reset_emblem (uon=<value optimized out>,
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ubuntuone-client (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: desktop+
Changed in ubuntuone-client (Ubuntu):
assignee: nobody → Rodrigo Moya (rodrigo-moya)
status: New → In Progress
Changed in ubuntuone-client:
assignee: nobody → Rodrigo Moya (rodrigo-moya)
importance: Undecided → High
Changed in ubuntuone-client:
status: New → In Progress
importance: High → Medium
importance: Medium → High
tags: added: u1-maverick
Revision history for this message
Rodrigo Moya (rodrigo-moya) wrote :

Gerwin, can you replicate this easily? If so, could you please install the ubuntuone-client-dbg package and try again to make it crash so that we get another backtrace with more debugging information? I see it's crashing in g_hash_table_iter_init, but not sure exactly in what code path, so that new backtrace after you install the -dbg package and restart nautilus (killall -9 nautilus) would be helpful

Revision history for this message
Gerwin (gerwin-klaus) wrote : Re: [Bug 643431] Re: nautilus crashed when attempting to share publicly a picture via right-click and UbuntuOne

Yes, I can replicate the behaviour. I'll follow your instructions and
report back. Not sure how to gather the debugging information and post
it to the right bug on launchpad, but hope the reporting tool will guide
the way.

Gerwin

Am 21.09.2010 14:58, schrieb Rodrigo Moya:
> Gerwin, can you replicate this easily? If so, could you please install
> the ubuntuone-client-dbg package and try again to make it crash so that
> we get another backtrace with more debugging information? I see it's
> crashing in g_hash_table_iter_init, but not sure exactly in what code
> path, so that new backtrace after you install the -dbg package and
> restart nautilus (killall -9 nautilus) would be helpful
>

Revision history for this message
Rodrigo Moya (rodrigo-moya) wrote :

when you get the reporting tool, I think you have a 'review' or 'see details' button. Just click on that and you should get the backtrace, IIRC

Revision history for this message
Gerwin (gerwin-klaus) wrote :

The problem seems to be less urgent, because, as it turns out, it is actually not that easy to replicate:

Just before posting #6 I could replicate the bug in the first attempt by moving some pictures into the UbuntuOne/shared folder, right-click->UbuntuOne->Veröffentlichen(Publish), just as before. Then, I installed ubutuone-client-dbg via Synaptic and restarted nautilus as per your instructions. Tried to replicate, but everything worked fine: nautilus did not crash and the context menu offered the option to display the download link.

Did various tests trying to replicate the bug and it only reoccurred a few times. Observations: seems only to occur, when files are freshly dropped into the folder UbuntuOne/shared and not yet transferred (little circular arrows on the file icon); even then, the bug only happened sometimes; it never occurred when the files were already transmitted (so I assume: little green tick on the file icon); I could not discover a pattern in when or when not the bug occurred besides this (tired closing/opening UbuntuOne window, restarting nautilus, restarting entire system, but with inconsistent results for the following probability of nautilus crashing as it originally did).

Unfortunately, once the bug did happen, the reporting tool did not come up. I started it manually for ubuntuone-client, got the debugging information displayed but was unable to copy it from the Apport window :( -- so I transferred it instead under the new bug #643431.

Hope it helps.

Revision history for this message
Roman Yepishev (rye) wrote :

Setting as a duplicate of LP:498019 which describes the reason of the crash.

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.