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 483812 - crash in Open Folder: 1) I was installing gimp...
crash in Open Folder: 1) I was installing gimp...
Status: RESOLVED DUPLICATE of bug 459221
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-05 17:22 UTC by farmazon
Modified: 2007-10-19 01:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description farmazon 2007-10-05 17:22:04 UTC
Version: 2.18.3

What were you doing when the application crashed?
1) I was installing gimp2.4.0-RC3 from devel repo
# yum install gimp
2) When I try run gimp or nautilus or yumex they don't run

When I try run gimp
[root@fnhi fnhi]# gimp
gimp: symbol lookup error: gimp: undefined symbol: g_once_init_enter_impl


When I try run nautilus

[root@fnhi .nautilus]# nautilus

(nautilus:2856): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
nautilus: symbol lookup error: /usr/lib/nautilus/extensions-1.0/libevince-properties-page.so: undefined symbol: g_once_init_enter_impl


When I try run Yumex
------------
Error Type: <class 'yum.update_md.UpdateNoticeException'>
Error Value: No id element found
 File : /usr/share/yumex/yumex.py , line 759, in <module>
   mainApp = YumexApplication()
 File : /usr/share/yumex/yumex.py , line 439, in __init__
   self.setupYum()
 File : /usr/share/yumex/yumex.py , line 462, in setupYum
   self.yumbase._setupBase()
 File : /usr/share/yumex/yumapi.py , line 80, in _setupBase
   self._setupUpdateMetadata()
 File : /usr/share/yumex/yumapi.py , line 137, in _setupUpdateMetadata
   self.updateMetadata.add(repo)
 File : /usr/lib/python2.5/site-packages/yum/update_md.py , line 255, in add
   un = UpdateNotice(elem)
 File : /usr/lib/python2.5/site-packages/yum/update_md.py , line 58, in __init__
   self._parse(elem)
 File : /usr/lib/python2.5/site-packages/yum/update_md.py , line 128, in _parse
   raise UpdateNoticeException("No id element found":wink: 

I was  decided update from devel repo these packages
#1379 vsx, [root@fnhi fnhi]# yum install gtk2 pango atk glib2
Loading "kernel-module" plugin
Loading "fedorakmod" plugin
Setting up Install Process
Parsing package install arguments
Package gtk2 - 2.10.14-3.fc7.i386 is already installed.
Package pango - 1.16.4-1.fc7.i386 is already installed.
Package atk - 1.18.0-1.fc7.i386 is already installed.
Package glib2 - 2.12.13-1.fc7.i386 is already installed.
Resolving Dependencies
--> Running transaction check
---> Package atk.i386 0:1.20.0-1.fc8 set to be updated
--> Processing Dependency: glib2 = 2.12.13-1.fc7 for package: glib2-devel
---> Package glib2.i386 0:2.14.1-1.fc8 set to be updated
---> Package pango.i386 0:1.18.2-1.fc8 set to be updated
---> Package gtk2.i386 0:2.12.0-4.fc8 set to be updated
--> Running transaction check
---> Package glib2-devel.i386 0:2.14.1-1.fc8 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

=============================================================================
Package                 Arch       Version          Repository        Size
=============================================================================
Updating:
atk                     i386       1.20.0-1.fc8     development       212 k
gtk2                    i386       2.12.0-4.fc8     development       6.8 M
Updating for dependencies:
glib2                   i386       2.14.1-1.fc8     development       822 k
glib2-devel             i386       2.14.1-1.fc8     development       921 k
pango                   i386       1.18.2-1.fc8     development       362 k

Transaction Summary
=============================================================================
Install      0 Package(s)        
Update       5 Package(s)        
Remove       0 Package(s)        

Total download size: 9.0 M
Is this ok [y/N]: y
Downloading Packages:
(1/5): gtk2-2.12.0-4.fc8. 100% |=========================| 6.8 MB    00:55    
(2/5): glib2-devel-2.14.1 100% |=========================| 921 kB    00:07    
(3/5): pango-1.18.2-1.fc8 100% |=========================| 362 kB    00:02    
(4/5): glib2-2.14.1-1.fc8 100% |=========================| 822 kB    00:06    
(5/5): atk-1.20.0-1.fc8.i 100% |=========================| 212 kB    00:01    
Running rpm_check_debug
Running Transaction Test
warning: atk-1.20.0-1.fc8: Header V3 DSA signature: NOKEY, key ID 30c9ecf8
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
 Updating  : glib2                        ####################### [ 1/10]
 Updating  : atk                          ####################### [ 2/10]
 Updating  : pango                        ####################### [ 3/10]
 Updating  : gtk2                         ####################### [ 4/10]
 Updating  : glib2-devel                  ####################### [ 5/10]
 Cleanup   : atk                          ####################### [ 6/10]
 Cleanup   : glib2                        ####################### [ 7/10]
 Cleanup   : pango                        ####################### [ 8/10]
/var/tmp/rpm-tmp.2911: line 24: /etc/pango/i686-redhat-linux-gnu/pango.modules: No such file or directory
 Cleanup   : glib2-devel                  ####################### [ 9/10]
 Cleanup   : gtk2                         ####################### [10/10]

Updated: atk.i386 0:1.20.0-1.fc8 gtk2.i386 0:2.12.0-4.fc8
Dependency Updated: glib2.i386 0:2.14.1-1.fc8 glib2-devel.i386 0:2.14.1-1.fc8 pango.i386 0:1.18.2-1.fc8
Complete!
[root@fnhi fnhi]# gimp
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Gimp was runing successfully but GPU usage was 100% when I was drawing in gimp. RAM only 50% usage. And in the and desktop completely was freezing. Ctr +Alt+SysRq, Ctr+Alt+Del, or Ctr+Alt+Backspace and other combinations don't work. I was switch off computer by pressing at power baton.

Then I was try run Nautilus for back up my files.
After runing was trying open Desktop folder, and was geting this bag.
These bug take place when I try open any folder




Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 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: 92078080 vsize: 92078080 resident: 30322688 share: 18051072 rss: 30322688 rss_rlim: 4294967295
CPU usage: start_time: 1191603449 rtime: 221 utime: 204 stime: 17 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 -1208391968 (LWP 2805)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208391968 (LWP 2805))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 g_cclosure_marshal_VOID__BOXED
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 gtk_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #30 ??
    from /lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
--- Hash table keys for warning below:
--> file:///home/fnhi
(nautilus:2764): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
** ERROR **: file nautilus-navigation-window.c: line 834 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
--------------------------------------------------
Comment 1 André Klapper 2007-10-19 01:46:48 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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