[Bug 153382] Re: debug log madness after segfault

2008-01-24 Thread Pedro Villavicencio
Thanks for the report, this is fixed on Hardy, feel free to re open it
if is still an issue with latest Hardy package. thanks you.

** Changed in: nautilus (Ubuntu)
   Status: Triaged = Fix Released

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2008-01-19 Thread Jürgen Barlag
My nautilus-debug-log.txt starts with:

= BEGIN MILESTONES =
0x81778c8 2008/01/19 10:30:14.9518 (GLog): nautilus-metafile.c: metafiles 
hash table still has 2 elements at quit time (keys above)
0x81778c8 2008/01/19 10:30:14.9518 (GLog): nautilus-directory.c: directories 
hash table still has 2 elements at quit time (keys above)
0x81778c8 2008/01/19 10:30:14.9519 (USER): debug log dumped due to signal 11
0x81778c8 2008/01/19 10:30:14.9701 (USER): debug log dumped due to signal 11

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2008-01-15 Thread ThomasNovin
Just had this issue my self. I have noticed it maybe 10-20 times before.

$ wc -l nautilus-debug-log.txt
26119 nautilus-debug-log.txt

$ tail -3 nautilus-debug-log.txt
0x8177510 2008/01/15 17:03:39.9329 (USER): debug log dumped due to signal 11
0x8177510 2008/01/15 17:03:39.9446 (USER): debug log dumped due to signal 11
0x8177510 2008/01/15 17:03:39.9563 (USER): debug log dumped due to signal 11

After I killed the nautilus process that took 100% CPU with -15 it
stopped.

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2007-12-21 Thread Lars Wirzenius
** Tags added: qa-hardy-list

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2007-12-19 Thread Pedro Villavicencio
** Changed in: nautilus (Ubuntu)
   Target: None = ubuntu-8.04

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2007-11-19 Thread Pedro Villavicencio
** Tags added: desktop-next-lts

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2007-10-23 Thread Sebastien Bacher
Not marking duplicate, the other bug is likely a specific crash, the log
handler is broken and we should also fix that, confirming the issue

** This bug is no longer a duplicate of bug 150471
   [Gutsy] high processor activity after logging out and then logging in again

** Changed in: nautilus (Ubuntu)
   Importance: Undecided = High
 Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
   Status: Invalid = Triaged

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2007-10-22 Thread Pedro Villavicencio
*** This bug is a duplicate of bug 150471 ***
https://bugs.launchpad.net/bugs/150471

Thanks for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.

** Changed in: nautilus (Ubuntu)
   Status: New = Invalid

** This bug has been marked a duplicate of bug 150471
   [Gutsy] high processor activity after logging out and then logging in again

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for nautilus in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 153382] Re: debug log madness after segfault

2007-10-16 Thread Ubuntu QA Tracker
** Tags added: iso-testing

-- 
debug log madness after segfault
https://bugs.launchpad.net/bugs/153382
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for nautilus in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs