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 511758 - crash in Home Folder: as i just saw the whole ...
crash in Home Folder: as i just saw the whole ...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-24 11:06 UTC by sboberg
Modified: 2008-01-24 23:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description sboberg 2008-01-24 11:06:56 UTC
What were you doing when the application crashed?
as i just saw the whole bugzilla is in english so i rproduced the cra.sh. what did i do?
i used a usb stick. everything was fine, until i want to check it's properties via nautilus. as soon as i clicked the properties button, this bug buddy opened.
lenny's cool thanx for your effort,
stefan


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Smooth-Mech-1.1
Icon Theme: OpenWorld

Memory status: size: 73261056 vsize: 73261056 resident: 23097344 share: 15323136 rss: 23097344 rss_rlim: 4294967295
CPU usage: start_time: 1169635725 rtime: 529 utime: 485 stime: 44 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 0xb6d806b0 (LWP 4227)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6d806b0 (LWP 4227))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (74 sec old) ---------------------
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (gnome-control-center:4904): WARNING **: 
error raised: [libslab_get_gconf_value: error getting /desktop/gnome/applications/main-menu/lock-down/user_modifiable_apps]
(gnome-control-center:4904): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
** (gnome-control-center:4904): WARNING **: 
error raised: [load_xbel_store: couldn't load bookmark file [(null)]
]
** (gnome-control-center:4904): WARNING **: Schlüssel »/apps/control-center/cc_actions_list« konnte nicht gefunden werden
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-24 23:07:27 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 355018 ***