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 530927 - crash in Home Folder: i sent a request to wind...
crash in Home Folder: i sent a request to wind...
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-01 19:09 UTC by Tobias_Letschka
Modified: 2008-05-02 23:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Tobias_Letschka 2008-05-01 19:09:47 UTC 
What were you doing when the application crashed?
i sent a request to windows-XP desktop computer. I tried to connect on his prim. partiton.



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

System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nuvola
Icon Theme: Flat-Blue

Memory status: size: 140271616 vsize: 140271616 resident: 84774912 share: 18034688 rss: 84774912 rss_rlim: 4294967295
CPU usage: start_time: 1209658274 rtime: 3919 utime: 3755 stime: 164 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6c12720 (LWP 4660)]
[New Thread 0xb5e04b90 (LWP 11540)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 196616

Thread 1 (Thread 0xb6c12720 (LWP 4660))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 istr_hash
    at nautilus-directory-async.c line 170
  • #7 g_hash_table_insert_internal
    at /build/buildd/glib2.0-2.16.3/glib/ghash.c line 118
  • #8 istr_set_insert
    at nautilus-directory-async.c line 189
  • #9 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 848
  • #10 directory_load_callback
    at nautilus-directory-async.c line 1035
  • #11 dispatch_job_callback
    at gnome-vfs-job.c line 237
  • #12 g_idle_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 4087
  • #13 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #14 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #15 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #16 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
  • #17 main
    at nautilus-main.c line 556
  • #0 __kernel_vsyscall 


----------- .xsession-errors (223 sec old) ---------------------
** (gnome-cups-add:12320): 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:12320): WARNING **: model named 'LaserJet M1522 MFP' doesn't have a recognized structure

** (gnome-cups-add:12320): WARNING **: model named 'Officejet H470' doesn't have a recognized structure

** (gnome-cups-add:12320): WARNING **: Could not list smb:// : Datei oder Verzeichnis nicht gefunden

Selected ppd file = lsb/usr/foomatic-rip/openprinting-gs-builtin/Canon/Canon-BJ-10v-bj10vh.ppd.gz
Selected ppd file = gutenprint.5.0://bjc-PIXMA-iP2000/expert/C
Selected ppd file = gutenprint.5.0://bjc-PIXMA-iP3000/expert/C
Kennwort für iron auf localhost? 
** (gnome-cups-manager:12300): WARNING **: IPP request failed with status 1280
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-02 23:26:47 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 ***