After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 408038 - crash in Open Folder: Reading mail in seamonke...
crash in Open Folder: Reading mail in seamonke...
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.17.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-02-14 22:55 UTC by Jim Cornette
Modified: 2007-02-16 22:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jim Cornette 2007-02-14 22:55:22 UTC
Version: 2.17.91

What were you doing when the application crashed?
Reading mail in seamonkey on one screen and updating evince, evolution on the other monitor. No Nautilus browsers were loaded at the time.


Distribution: Fedora release 6.90 (Rawhide)
Gnome Release: 2.17.91 2007-02-13 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.20-1.2925.fc7 #1 SMP Mon Feb 12 14:53:24 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled

Memory status: size: 189571072 vsize: 0 resident: 189571072 share: 0 rss: 8151040 rss_rlim: 0
CPU usage: start_time: 1171475945 rtime: 0 utime: 502 stime: 0 cutime:385 cstime: 0 timeout: 117 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208587504 (LWP 3098)]
0x003e7402 in __kernel_vsyscall ()

Thread 1 (Thread -1208587504 (LWP 3098))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (11057 sec old) ---------------------
** (eggcups:3104): WARNING **: IPP request failed with status 1030
** (eggcups:3104): WARNING **: IPP request failed with status 1030
** (eggcups:3104): WARNING **: IPP request failed with status 1030
** (eggcups:3104): WARNING **: IPP request failed with status 1030
** (eggcups:3104): WARNING **: IPP request failed with status 1030
** (eggcups:3104): WARNING **: IPP request failed with status 1030
** (eggcups:3104): WARNING **: IPP request failed w
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jim Cornette 2007-02-14 23:01:16 UTC
I am adding the Nautilus-debuginfo package for possible future failures.
I did have a problem with control-center as pasted below during the yum upgrade.

Running Transaction
  Updating  : evolution                    ####################### [ 1/10] 
error: %pre(control-center-2.17.91-1.fc7.i386) scriptlet failed, exit status 1
error:   install: %pre scriptlet failed (2), skipping control-center-2.17.91-1.fc7

After yum finished, I got the below. One of these elements might have triggered the problem.

Updated: control-center.i386 1:2.17.91-1.fc7 epiphany.i386 0:2.17.91-1.fc7 evince.i386 0:0.7.2-1.fc7 evolution.i386 0:2.9.91-2.fc7 evolution-connector.i386 0:2.9.91-2.fc7
Complete!
Comment 2 Christian Kirbach 2007-02-15 20:48:44 UTC
thank you, please try to reproduce the problem.

btw only one problem per report. and upgrade failures are distribution problems, not Gnome problems.
Comment 3 Jim Cornette 2007-02-16 00:31:29 UTC
I'm trying to determine what caused the crash. I had a printer problem which happened after I ran out of paper on a large print job. I restarted cups to print the job again. I mentioned this because of eggcups listing in the report output. I did not see any printer job notigfier applet in the panel.

What clues are there for an "Open Folder" operation? I don't recall opening up a folder.

Do you have any clues as how to trigger the error again?
Comment 4 Christian Kirbach 2007-02-16 20:52:56 UTC
nautilus always run on Gnome and is responsible for the Desktop.
perhaps this can only be triggered by the software upgrade path you did.

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 Jim Cornette 2007-02-16 22:13:23 UTC
No problem with closing the bug. I have the debug packages installed in case this problem resurfaces.

Thanks!