Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8228 - Nautilus generates debug log in home directory

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Saturday, 06 October 2007, 02:59 GMT
Last edited by Jan de Groot (JGC) - Monday, 19 May 2008, 17:10 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Very Low
Priority Normal
Reported Version 2007.08.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

On Gnome startup, Nautilus generates a debug log in the user's home dir, even if nothing significant happens (in which case the log is completely empty). Looks to me like some kind of debugging option was enabled at compile time.

(Could be that I'm being thick and this was deliberate though. It is in Testing.)

Additional info:
* nautilus 2.20.0-1
* nautilus-debug-log.txt, found in ~/
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 19 May 2008, 17:10 GMT
Reason for closing:  Fixed
Additional comments about closing:  Assuming fixed for 2.22.
Comment by Henrique C. Alves (freakcode) - Wednesday, 21 November 2007, 17:03 GMT
Happens here too. Can reproduce it by logging off or user switching on GDM.

Its totally ANNOYING, Nautilus segfaults and then start dumping thousand lines on this log file, which makes HD and CPU go crazy. You need to kill it manually via a sane terminal (killall nautilus) to stop it.

I hope its a know upstream bug.

Raise the severity of this bug, please.
Comment by Paolo Loberto (mrloba) - Thursday, 22 November 2007, 20:09 GMT
Same problem to me!
I noticed also nautilus slowdown when opening a dir and CPU utilization up to 90% !
I see no segfaults...
Comment by Paolo Loberto (mrloba) - Thursday, 22 November 2007, 20:25 GMT
I was wrong in previous comment! Sorry :)
I have the log in my home because of signal 11 (SIGSEGV)
So raise the severity ;)
Comment by Roman Kyrylych (Romashka) - Friday, 23 November 2007, 08:58 GMT
I've reported same bug here:  FS#8375 . But it appeared that log was created only after nautilus crash. I don't have it anymore.
Comment by Paolo Loberto (mrloba) - Sunday, 25 November 2007, 21:01 GMT
Error logging seems to be stopped...i don't know how and why!
But i have that strange slow down with high CPU utilization while opening a directory!
Seems that nautilus has some problems browsing the content of directories taking too much time to do it.
Comment by Jan de Groot (JGC) - Sunday, 25 November 2007, 22:08 GMT
Nautilus wants to identify mime types for every file in a directory and does this everytime you open it. Try to open /usr/bin in nautilus, you'll get scared...
Comment by Paolo Loberto (mrloba) - Monday, 26 November 2007, 08:50 GMT
I know this!
But it appens only in archlinux for me, in other distros nautilus-2.20 works well!
Comment by 甘露(Lu Gan) (ganlu) - Sunday, 02 December 2007, 10:50 GMT
It often freenzed when I open a directory with thousands of pictures too, which seems only occur only in Archlinux. I have to kill nautilus, but sometimes it freezes all my system.
Comment by Gavin Bisesi (Daenyth) - Friday, 25 April 2008, 20:08 GMT
I've also seen this issue on ArchPPC
Comment by Jan de Groot (JGC) - Monday, 19 May 2008, 15:06 GMT
Is this still an issue with nautilus 2.22?
Comment by 甘露(Lu Gan) (ganlu) - Monday, 19 May 2008, 15:30 GMT
It's hard to tell, since I don't remember I have ever met a nautilus crash after I upgrade to gnome 2.22.

Loading...