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 512432 - crash in Home Folder: I've watched the propert...
crash in Home Folder: I've watched the propert...
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-27 19:29 UTC by hermann.strassberger
Modified: 2008-01-27 21:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description hermann.strassberger 2008-01-27 19:29:57 UTC
What were you doing when the application crashed?
I've watched the properties of a removeable drive


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: Cybertron-leopard-1
Icon Theme: Mac4Lin_Icons_v0.4

Memory status: size: 84295680 vsize: 84295680 resident: 26689536 share: 15687680 rss: 26689536 rss_rlim: 4294967295
CPU usage: start_time: 1201462138 rtime: 330 utime: 317 stime: 13 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 0xb6d826b0 (LWP 30957)]
(no debugging symbols found)
0xb75d7321 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6d826b0 (LWP 30957))

  • #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 strcmp
    from /lib/libc.so.6
  • #6 ??
  • #7 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
        /home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/Tabs/notebook_top_flat.png,
borders don't fit within the image
** (nautilus:30957): WARNING **: Invalid borders specified for theme pixmap:
        /home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/Tabs/notebook_top_flat.png,
borders don't fit within the image
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/panel.rc:62: Background image options specified without filename
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/panel.rc:86: Background image options specified without filename
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/gtkrc:236: Bilddatei konnte nicht in pixmap_path gefunden werden: »Lines/line-v.png«
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/gtkrc:239: Background image options specified without filename
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/gtkrc:761: Bilddatei konnte nicht in pixmap_path gefunden werden: »Shadows/entry-shadow-in.png«
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/gtkrc:764: Background image options specified without filename
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/gtkrc:1457: Background image options specified without filename
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/gtkrc:1568: Bilddatei konnte nicht in pixmap_path gefunden werden: »Menu-Menubar/menubar.png«
/home/hermann/.themes/Cybertron-leopard-1/gtk-2.0/gtkrc:1571: Background image options specified without filename
--------------------------------------------------
Comment 1 Gianluca Borello 2008-01-27 21:20:18 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 ***