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 532502 - crash in Home Folder: Beim kopieren einer grös...
crash in Home Folder: Beim kopieren einer grös...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-10 17:30 UTC by meyfra
Modified: 2008-05-10 18:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description meyfra 2008-05-10 17:30:46 UTC 
What were you doing when the application crashed?
Beim kopieren einer grösseren Anzahl von Dateien von einem smb-Server (kopieren war noch nicht beendet) habe ich parallel dazu eine weitere Datei vom selben Server aber aus einem anderen Verzeichnis kopieren wollen. Beides Kopiervrogänge habe ich über Nautilus gestartet 


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 486088704 vsize: 486088704 resident: 58220544 share: 19668992 rss: 58220544 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210434349 rtime: 23108 utime: 19721 stime: 3387 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 0x2b2366c45240 (LWP 3728)]
[New Thread 0x41001950 (LWP 17168)]
(no debugging symbols found)
0x00002b236053cedf in waitpid () from /lib/libpthread.so.0

+ Trace 197386

Thread 1 (Thread 0x2b2366c45240 (LWP 3728))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (359 sec old) ---------------------
	->drv:///hpijs.drv/hp-deskjet_920c-hpijs.ppd (HP Deskjet 920c Foomatic/hpijs[0]) and
	->drv:///hpijs.drv/hp-deskjet_920c-hpijs.ppd (HP Deskjet 920c Foomatic/hpijs)[0]

** (gnome-cups-add:17450): WARNING **: Two ppds have driver == 'hpijs'
	->drv:///hpijs.drv/hp-laserjet_2100m-hpijs.ppd (HP LaserJet 2100M Foomatic/hpijs[0]) and
	->drv:///hpijs.drv/hp-laserjet_2100m-hpijs.ppd (HP LaserJet 2100M Foomatic/hpijs)[0]

** (gnome-cups-add:17450): WARNING **: model named 'LaserJet M1522 MFP' doesn't have a recognized structure

** (gnome-cups-add:17450): WARNING **: model named 'Officejet H470' doesn't have a recognized structure
Selected ppd file = lsb/usr/foomatic-rip/openprinting-gs-builtin/HP/HP-DeskJet_950C-cdj550.ppd.gz
Selected ppd file = gutenprint.5.0://hp-dj_959c/expert/C
** Message: init gpgme version 1.1.6
Initializing gnome-mount extension
seahorse nautilus module initialized
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-10 18:17:11 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 522534 ***