nautilus crash

Bug #508936 reported by Emanuel Steen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

stack trace to come

ProblemType: Bug
Architecture: amd64
Date: Mon Jan 18 00:16:45 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3)
NonfreeKernelModules: nvidia
Package: nautilus 1:2.29.1-0ubuntu2
ProcEnviron:
 LC_TIME=sv_SE.utf8
 LANGUAGE=en_US.utf8
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.32-10.14-generic
SourcePackage: nautilus
Tags: lucid
Uname: Linux 2.6.32-10-generic x86_64

Revision history for this message
Emanuel Steen (kozz) wrote :
Revision history for this message
Emanuel Steen (kozz) wrote :

Stack trace for nautilus. You want me to install libglib symbols too?

Revision history for this message
Emanuel Steen (kozz) wrote :

This started to happen after updating to nvidia-current, i.e. Nvidia 190.53, well at least I think to. I held back Xorg 7.5 a long time since I knew the Nvidia drivers wasn't updated in Lucid yet. So when I saw that Alberto Milone started to work on updating Nvidia for Lucid I updated Xorg. So most likely because of new Xorg and Nvidia driver.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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 nautilus (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you install nautilus-dbg libglib2.0-0-dbg libgtk2.0-0-dbg and get a stracktrace running nautilus using --sync and breaking in gdb on gdk_x_error?

Revision history for this message
Emanuel Steen (kozz) wrote :

Stack trace with more debug symbols installed and break on gdk_x_error.

Revision history for this message
Emanuel Steen (kozz) wrote :

I had a theory yesterday when I posted this bug and I just verified it.

This crash only occurs when running multiple desktops. I have an NVIDIA card and have my computer attached to the TV. I run two separate X screens configured with nvidia-settings. With this setup nautilus crashes all the time.

If just use one screen and disable the TV (hence I only use the monitor) nautilus starts just fine.

I haven't tested with TwinView, I can do that too.

Revision history for this message
Emanuel Steen (kozz) wrote :

Ok, tested with TwinView and it works. So same two screens and same resolution (1680x1050, 1920x1080) on both configurations - separate X screens crashes nautilus while TwinView doesn't.

Please let me know if I can provide any more informations.

And btw, I'm a programmer so I don't have any problems applying a patch and rebuilding nautilus. It's just the combination of lack of knowledge/experience about the Gnome/GDK/GTK/X11 stack and lack of time that prevents myself from digging into the code.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your details there, the bug has probably enough informations to be useful but there is not nautilus hacker in the current ubuntu team and the issue is rather a corner case one, would be maybe worth talking to upstream about it though

Changed in nautilus (Ubuntu):
status: Incomplete → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash seems similar to bug #508890

Revision history for this message
Sebastien Bacher (seb128) wrote :

I'm closing the bug as duplicate of bug #508890 which is the same issue and opened slightly before yours and using apport, could you check if both screen use the same visual using xwininfo and comment on the other bug?

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.