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 443855 - crash in Home Folder: FC6 benutzt, auf FC7 akt...
crash in Home Folder: FC6 benutzt, auf FC7 akt...
Status: RESOLVED DUPLICATE of bug 442829
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-04 09:39 UTC by alfonsname
Modified: 2007-06-05 00:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description alfonsname 2007-06-04 09:39:10 UTC
What were you doing when the application crashed?
FC6 benutzt, auf FC7 aktualisiert.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 39317504 vsize: 39317504 resident: 9502720 share: 7663616 rss: 9502720 rss_rlim: 4294967295
CPU usage: start_time: 1180949906 rtime: 7 utime: 5 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 -1208617248 (LWP 6956)]
(no debugging symbols found)
0x00e9d402 in __kernel_vsyscall ()

Thread 1 (Thread -1208617248 (LWP 6956))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyModule_GetDict
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #5 nautilus_python_init_python
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #6 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #7 ??
  • #8 g_type_module_use
    from /lib/libgobject-2.0.so.0
  • #9 nautilus_module_init
  • #10 nautilus_application_startup
  • #11 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
beryl: Kein Prozess abgebrochen
SESSION_MANAGER=local/charlie.zuhause.all:/tmp/.ICE-unix/6862
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager;  Geben Sie die Option »--replace« an, um zu versuchen, den aktuellen Fenstermanager zu ersetzen.
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager;  Geben Sie die Option »--replace« an, um zu versuchen, den aktuellen Fenstermanager zu ersetzen.
(gnome-panel:6953): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x9235958
(gnome-panel:6953): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x9235958
(nautilus:6956): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
Could not find platform independent libraries <prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
'import site' failed; use -v for traceback
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Desktop-Datei file:///home/michael/Desktop/alltray.desktop konnte nicht für Panel-Starter :  geöffnet werdenDatei oder Verzeichnis nicht gefunden
--------------------------------------------------
Comment 1 AlfonsName 2007-06-04 15:39:32 UTC
"What were you doing when the application crashed?":
Original: FC6 benutzt, auf FC7 aktualisiert.
New: I used Fedora Core 6, updated to FC7 and restartet the system.
Comment 2 Pedro Villavicencio 2007-06-05 00:06:03 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 442829 ***