Created attachment 1888 [details]
Here's the error messages in the terminal

Could you please install things like:
  nautilus-debug
  glib2.0-debug
  gtk+3.0-debug


Then:
gdb nautilus
r
bt
thread apply all bt

attach what that gives here.


no crash for me.

Keywords: (none) => NEEDINFO
CC: (none) => olav
Assignee: bugsquad => olav

Created attachment 1889 [details]
Here's the gdb nautilus messages

This morning ( 30 Mar 2012 San Diego time )
I had to move my Mageia 2 test platform from
one HD ( 80GB ) to the final HD ( 1TB ) for
my LAN server. That involved a complete
reinstall of Mageia 2 using 32-bit boot.iso
for the install. So that means that all the
packages installed are the latest versions.
I also updated the install to the latest vers.
All went in, and updated, successfully including
KDE4 and Gnome 3.4. Once again when launching
Nautilus it crashes immediately.

removing NEEDINFO keyword because the requested backtrace has been provided

Keywords: NEEDINFO => (none)
CC: (none) => marja11

Did you copy your old HOME or have you created your user from scratch?

Please do try with a new, blank user.

CC: (none) => oliver.bgr

When I retest this Bug I have been doing
a complete install using boot.iso So install
from scratch and the issue still persists.
I anticipate the new Gnome Live-CD M2B3 to
see if it is in there also.

Well a little more testing on this reveals a very
interesting problem. I wiped the disk ( killdisk )
then using my local updated repo ( mirrors.kernel.org
source ) and using the latest boot.iso ( 32-bit, 7 Apr 2012 )
I installed Mageia 2 ( Cauldron ) in Gnome only mode.
This went well and Nautilus runs just fine.

So wipe the disk again and with no changes to the
repo use the same boot.iso and install KDE first. Once
that's up and running then run task-gnome. Reboot
and log into Gnome and sure enough Nautilus crashes.

So for me if I install Cauldron in Gnome only mode
then Nautilus will run fine. If I install KDE first
then do task-gnome then that will create the situation
where Nautilus crashes. If I try to run Nautilus
from a terminal in KDE it will not start. I will
post the terminal error messages when this happens
shortly.

Created attachment 2015 [details]
Nautilus crash in KDE

It has something to do with my NFS share

I have a Mageia 1 Server that has one Directory
that is shared NFS. So every other system on the
network can get to this common directory. Once
the NFS share is installed on a client then Nautilus
in Gnome & KDE4 crashes. Comment out the NFS share line
in etc/fstab, reboot, then Nautilus works just fine
in both Gnome & KDE4

Interestingly enough Dolphin will work fine, even
when the NFS share is turned on, in both KDE4 and
Gnome.

Maybe the title of this bug needs to be changed to

"Nautilus crashes if system is an NFS client"

(In reply to comment #11)
> Maybe the title of this bug needs to be changed to
> 
> "Nautilus crashes if system is an NFS client"

Yes, but as the reporter of this bug, it would have been OK if you had done that :)

Does it also never crash if KDE is installed *after* Gnome? Or only never if you don't install KDE at all?

Summary: Nautilus crashes immediately after opening => Nautilus crashes if system is an NFS client

Gimme a couple days and I'll try
a few combinations. I think what
I saw yesterday was that it had
nothing to do with KDE. A Gnome
only install, no NFS client, Nautilus
was ok. Install NFS client and
Nautilus would crash.

Lemme confirm that today ( Wed )
at latest Tomorrow ( Thur ).

Thanks for your help.

Created attachment 2025 [details]
Nautilus on Mageia 2 testing methodology

(In reply to comment #12)

> Does it also never crash if KDE is installed *after* Gnome? Or only never if
> you don't install KDE at all?

Take a look at my testing in Comment 14
I don't think installing just KDE4 then
installing Nautilus on that will make
any difference. I can do that if you
wish.

(In reply to comment #15)
> (In reply to comment #12)
> 
> > Does it also never crash if KDE is installed *after* Gnome? Or only never if
> > you don't install KDE at all?
> 
> Take a look at my testing in Comment 14
> I don't think installing just KDE4 then
> installing Nautilus on that will make
> any difference. I can do that if you
> wish.

Thanks, William.

I had misread something before ;)
So no, for me no need to try with KDE.

removing NEEDINFO keyword

Keywords: NEEDINFO => (none)

Installed RC from boot.iso today and
this bug is still a problem.

Thanks

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

This appears to still be a problem in M2.
More testing on my part is needed.

Well I've put some considerable time into trying to figure
this one out. What am I doing wrong, what's going wrong,
what don't I understand? Or a combination of all of
the above.

First and foremost, both Nautilus and Dolphin work just
fine. In fact if you install both KDE & Gnome they'll
work in either environment. Both work just fine in
their Live-CDs. Both work just fine when installed
from the install DVD disc.

Having said that if you install NFS client into your
workstation then allow the MCC to execute it's own
mount point, again, you'll be just fine. Mount point
being:

/mnt/mountpoint

Dolphin, IMO, deals with the mounted NFS share better
and presents it in an easy to understand way. Over
the years I've gotten into the habit of placing the
mount point within my user webspace. Like here:

/home/wilcal/shares/sherman

"sherman" being the mount point for the NFS shared
directory on the server "sherman". That's actually
worked just fine with both Mandriva and Mageia 1.

Along comes Mageia 2 and when you launch the Gnome
default file browser ( Nautilus ) it immediately
crashes. See details above. Launch Dolphin within
Gnome 3 and it runs just fine. Launch Nautilus
within KDE and it immediately crashes.

Now comment out the NFS share in /etc/fstab, run
"mount -a" in an su terminal, and both file browsers
run just fine. Here's the command in fstab:

192.168.1.2:/home/wilcal/databank /home/wilcal/shares/sherman nfs rsize=8192,wsize=8192,nosuid,soft 0 0

Now put a mount point in /mnt/sherman and change the
fstab command to:

192.168.1.2:/home/wilcal/databank /mnt/sherman nfs rsize=8192,wsize=8192,nosuid,soft 0 0

do the "mount -a" command in a su terminal and
both file browsers work just fine in both
Gnome and KDE.

So I don't know why but for some reason Nautilus
is not happy with the NFS mount in the user space.
If you attempt to launch it it crashes immediately.
Move the mount point to /mnt/sherman ( or whatever )
then Nautilus works just fine.

Feel free to suggest any testing. Or, is putting the
mount point in the user space not acceptable?

FWIW if I launch the Gnome Live-CD and then move NFS
mount between the user space and /mnt I get the same
results. NFS client is installed by default in the
Live-CD.

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

(In reply to comment #21)
> @ the reporter and persons in the cc of this bug:
> 
> If you have any new information that wasn't given before (like this bug being
> valid for another version of Mageia, too, or it being solved) please tell us.
> 
> @ the reporter of this bug
> 
> If you didn't reply yet to a request for more information, please do so within
> two weeks from now.
> 
> Thanks all :-D

I have no additional information.

Hi, just wanted to chime in that I'm having the same problem. Nautilus crashes if I mount a shared NFS on my netbook, which is located in the server's /home/user folder. When I removed the share completely, and changed it on the server side to samba, the problem went away on my netbook completely. Nautilus loads just fine, and has no issues whatsoever.

The only problem being, that I now have to get with our server admin to see what I have to do to get it to mount onto the netbook as a samba share (I r doink somethink wronk, and don't know what it is ;) ).

I have a gdb backtrace, and also if you can, take a look at: https://forums.mageia.org/en/viewtopic.php?f=7&t=4580

Thanks.

CC: (none) => skeeter1029

Oh, btw, this is in fully updated Mageia 2.

Created attachment 3648 [details]
Terminal output from gdp of nautilus with nautilus-dropbox

The backtrace.log on this for some reason hosed on me, so I copied everything from terminal into a .txt file. I also posted results at http://pastebin.ca/2339565.

Created attachment 3649 [details]
gdb of nautilus without nautilus-dropbox, to rule it out as being the issue.

This is the gdb, after having disabled and uninstalled nautilus-dropbox, to rule it out as being the issue. It wasn't. It was running fine.
Again, terminal output, as I don't trust the backtrace.log from this time, since the first didn't go so well.

Sorry, but this bug saw no action since over 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

Status: NEW => RESOLVED
Resolution: (none) => OLD