Nautilus 3.8.2 Self Close

Bug #1198658 reported by sabri unal on 2013-07-07
44
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Undecided
Unassigned

Bug Description

My file manager close every 5 minute...

ı try started from terminal:

Gnome PPA is installed.

System properties: Ubuntu 13.04, Gnome PPA, amd64, İntel OnboardVGA

sabri@yakusha:~$ nautilus
(nautilus:2970): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed
(nautilus:2970): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed

(nautilus:2970): Gdk-ERROR **: The program 'nautilus' received an X Window System error.

This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 7556 error_code 9 request_code 62 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.8.2-0ubuntu1~ubuntu13.04.1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.8.0-25.17-lowlatency 3.8.13
Uname: Linux 3.8.0-25-lowlatency x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sun Jul 7 20:29:33 2013
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'679x719+453+155'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'438'
InstallationDate: Installed on 2013-04-25 (72 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince 3.8.2-0ubuntu4~raring1
 file-roller 3.8.2-0ubuntu1~raring1
 nautilus-image-converter 0.3.1~git20110416-1

sabri unal (yakushabb-g) wrote :
Rick Harris (rickfharris) wrote :

Bitten by this bug, but it appears disabling a few background gnome-settings-daemon patches fixes the issue ?

See https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1170483

I have the same problem, with the same error message as Sabri:

maziero@citronelle:~$ nautilus
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.6.0

(nautilus:27643): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed

(nautilus:27643): GLib-GObject-CRITICAL **: g_object_set: assertion `G_IS_OBJECT (object)' failed

(nautilus:27643): Gdk-ERROR **: The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 22628 error_code 9 request_code 62 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap

In addtion, I found these nautilus-related messages in dmesg:

[179959.794201] traps: nautilus[30992] trap int3 ip:7f24546c4135 sp:7fff82e82510 error:0
[216974.709210] traps: nautilus[17283] trap int3 ip:7f88a555e135 sp:7fff8b132250 error:0
[217418.090110] traps: nautilus[18842] trap int3 ip:7fa968467135 sp:7fffe8fdf820 error:0
[217816.236356] traps: nautilus[20310] trap int3 ip:7f5b1145c135 sp:7fff782ba840 error:0
[220126.979085] traps: nautilus[27643] trap int3 ip:7f5531dd7135 sp:7fffbf8d58c0 error:0

My install is a Ubuntu 13.04 64 bits, with Gnome 3.8 (PPA gnome3-team), running in a Sony Vaio SVF14A15CBB (BIOS R0210DA).

Just to add some more information to my last post:
- I'm using this PPA: ppa:gnome3-team/gnome3.
- My kernel is 3.8.0-31-generic #46-Ubuntu SMP x86_64.

Nautilus packages installed in my system are:
  gnome-sushi 3.8.0-1build1~raring1 amd64
  libnautilus-extension1a 1:3.8.2-0ubuntu1~ubuntu13.04.1 amd64
  nautilus 1:3.8.2-0ubuntu1~ubuntu13.04.1 amd64
  nautilus-data 1:3.8.2-0ubuntu1~ubuntu13.04.1 all
  nautilus-open-terminal 0.20-1 amd64
  nautilus-sendto 3.6.1-0ubuntu1 amd64
  libglib2.0-0:amd64 2.36.3-0ubuntu1~raring1
  libgdk-pixbuf2.0-0:amd64 2.28.1-1ubuntu1~raring1
  libgtk2.0-0:amd64 2.24.17-0ubuntu2

Hi, I have found something new here: I replaced the default time-cycling background image (the vertical blue strips) by another background image and Nautilus stopped to die.

Now I'm using a static image (the reddish sand labyrinth from the chooser) and all seems fine.

Maybe the problem is related to the background time-cycling mechanism (it never worked here, by the way).

Ubuntu GNOME (ug-bot) wrote :

Thank you for reporting this bug to Ubuntu. raring reached EOL on Jan 27, 2014.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please feel free to report any other bugs you may find.

Changed in ubuntu-gnome:
status: New → Expired
raydar (raydar) wrote :

What's the proper way to reopen this under 14.04?

I'm experiencing this problem with both Nautilus and Nemo under Ubuntu Gnome 64-bit.

skunk (tiobra666) wrote :

same problem after upgrading from 12.04 to 14.04.

Changed in ubuntu-gnome:
status: Expired → Confirmed
tags: added: utopic
removed: raring
Bruce Pieterse (octoquad) wrote :

Those experiencing this under 14.04, please confirm if you are using the main and staging ppa's or without them. If you are no longer experiencing this problem, please let me know. Thanks

Waqar Ahmed (waqar-17a) wrote :

I am using the official and staging ppa for 14.04.3. It's still happening, mostly when I click a network-bookmark. Sometimes it crashes, sometimes it doesn't.

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

Other bug subscribers