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 493407 - crash in File Browser: próba wejścia we właściw...
crash in File Browser: próba wejścia we właściw...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-04 15:58 UTC by pabianczyk
Modified: 2007-11-05 08:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description pabianczyk 2007-11-04 15:58:37 UTC
Version: 2.18.3

What were you doing when the application crashed?
próba wejścia we właściwości pliku .png przy pomocy prawokliku


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-486 #1 Thu Aug 30 23:45:36 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 74129408 vsize: 74129408 resident: 24961024 share: 15634432 rss: 24961024 rss_rlim: 4294967295
CPU usage: start_time: 1194184758 rtime: 289 utime: 264 stime: 25 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6df66b0 (LWP 3527)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6df66b0 (LWP 3527))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
  VirtualChannelSelector: No progress for op 1: listener = class com.aelitis.azureus.core.clientmessageservice.impl.NonBlockingReadWriteService$2, count = 10, socket: open = true, connected = true
    VirtualChannelSelector::select::329,NonBlockingReadWriteService$1::runSupport::82,AEThread::run::69
DEBUG::Sun Nov 04 16:00:55 GMT+01:00 2007::com.aelitis.azureus.core.networkmanager.impl.tcp.VirtualChannelSelectorImpl::select::586:
  VirtualChannelSelector: No progress for op 1: listener = class com.aelitis.azureus.core.clientmessageservice.impl.NonBlockingReadWriteService$2, count = 100, socket: open = true, connected = true
    VirtualChannelSelector::select::329,NonBlockingReadWriteService$1::runSupport::82,AEThread::run::69
DEBUG::Sun Nov 04 16:01:06 GMT+01:00 2007::com.aelitis.azureus.core.networkmanager.impl.tcp.VirtualChannelSelectorImpl::select::586:
  VirtualChannelSelector: No progress for op 1: listener = class com.aelitis.azureus.core.clientmessageservice.impl.NonBlockingReadWriteService$2, count = 200, socket: open = true, connected = true
    VirtualChannelSelector::select::329,NonBlockingReadWriteService$1::runSupport::82,AEThread::run::69
DEBUG::Sun Nov 04 16:01:16 GMT+01:00 2007::com.aelitis.azureus.core.networkmanager.impl.tcp.VirtualChannelSelectorImpl::select::586:
  VirtualChannelSelector: No progress for op 1: listener = class com.aelitis.azureus.core.clientmessageservice.impl.NonBlockingReadWriteService$2, count = 300, socket: open = true, connected = true
    VirtualChannelSelector::select::329,NonBlockingReadWriteService$1::runSupport::82,AEThread::run::69
[GUI] SWT update aborted due to previously reported issues regarding its install location
Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
--------------------------------------------------
Comment 1 André Klapper 2007-11-05 08:17:11 UTC
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.


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