With a CD in the drive, Nautilus refuses to open, glib error.

[ToKico]

Yesterday I upgraded my 8.10 machine to 9.04. As soon as I put a CD in my CD drive, all icons in the desktop disappear and Nautilus refuses to open. It gives me the following error when launching Nautilus in a terminal, as a normal user or as root:

GLib-ERROR **: /build/buildd/glib2.0-2.20.1/glib/gmem.c:156: failed to allocate 1073741824 bytes
aborting...

When I removed the CD the icons in the desktop appeared again and Nautilus worked properly without any error.

I don't know if the same problem happens with a fresh install, at least in my upgraded 9.04 the problems occur.

Other users that have the same problem: http://ubuntuforums.org/showthread.php?t=1135678

[Fabio Bossi (fabio-bossi-deactivatedaccount)]

Could this be related to bug 366262?

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Arthur Sa (artie)]

I reported the same bug. But I can seem to fine it. I think many people are have this problem. It should be given a very high priority, if is not solved soon I will have to go back to 8.10.

[FactTech (launchpad-facttechnologies)]

I am experiencing the exact same symptoms on a machine that was upgraded from 8.10 to 9.04 today. Nautilus will not open when a CD is present in the drive, and the same error message (with identical byte count) is given if I try to launch nautilus from terminal.

Attached is a valgrind log as requested by Sebastian Bacher. Let me know if I can provide any further information.

[Sebastien Bacher (seb128)]

the new comment seems one of the issue fixed in the candidate updates for jaunty

[FactTech (launchpad-facttechnologies)]

Sebastian, if this is a duplicate of a known bug, will you mark it as such so that people who find this page are directed to more complete information?

[FactTech (launchpad-facttechnologies)]

FYI for anyone following this thread -- a suggested workaround has been posted on the forum, which is to execute the command:

sudo chmod a-r /usr/lib/nautilus/extensions-2.0/libnautilus-brasero-extension.so

I tried it, and it worked. Likewise, reversing the change with parameter 'a+r' caused the issue to reappear.

This doesn't seem like a great long-term solution, but this information should help narrow down the cause. Please let me know if there are any other debugging or testing steps any developers would like me to take.

[FactTech (launchpad-facttechnologies)]

This appears to be duplicate of bug #335942. (see https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/335942)

Sebastian has not marked it as such, so I will not, either, but it seems clear that this is the same issue given that the workaround mentioned above works for both. Apparently, a fix is already in the pipeline (as Sebastian mentioned). If you can't wait for that, your options are:

1) enable testing/proposed packages so you can get the current version of brasero ahead of the official release (see https://wiki.ubuntu.com/Testing/EnableProposed for more information)

2) remove the packages 'brasero' and 'libbrasero-media0' using synaptic or apt-get, then add them back later once the fixed version is officially released

Enabling the proposed packages and upgrading brasero with synaptic per option #1 seems to have fixed the issue for me. Anyone doing this will want to create the /etc/apt/preferences file as described in the wiki link to prevent Update Manager from wanting to install every proposed update for any packages they have installed. With this file in place, you can highlight the brasero package, then use menu item Package/Force Version to update only brasero from the jaunty-proposed repository.

[Sebastien Bacher (seb128)]

closing the issue seemed to be a duplicate of some other bugs, not due to nautilus and has been solved since