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 535665 - crash in CD/DVD Creator: Open a samba share on re...
crash in CD/DVD Creator: Open a samba share on re...
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-30 06:21 UTC by korjavin
Modified: 2008-05-30 09:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description korjavin 2008-05-30 06:21:46 UTC 
What were you doing when the application crashed?
Open a samba share on remote winxp.

Like smb://computerip/share


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: Aurora
Icon Theme: SphereCrystal

Memory status: size: 445812736 vsize: 445812736 resident: 34332672 share: 18186240 rss: 34332672 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212128260 rtime: 260 utime: 229 stime: 31 cutime:0 cstime: 1 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 0x2b8e0f4c7240 (LWP 19450)]
[New Thread 0x41802950 (LWP 19568)]
(no debugging symbols found)
0x00002b8e08cbdedf in waitpid () from /lib/libpthread.so.0

+ Trace 199103

Thread 1 (Thread 0x2b8e0f4c7240 (LWP 19450))

  • #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 (715119 sec old) ---------------------
![1211412009,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] 	ATTENTION! Currently cached group 0 is not equal to the current gAutoselected keyboard map ru
WARNING: No translation for (keysym 0x0, NoSymbol)
WARNING: No translation for (keysym 0x0, NoSymbol)
WARNING: No translation for (keysym 0x0, NoSymbol)
WARNING: No translation for (keysym 0x0, NoSymbol)
Autoselected keyboard map ru
WARNING: No translation for (keysym 0x0, NoSymbol)
WARNING: No translation for (keysym 0x0, NoSymbol)
(soffice:26991): Gtk-WARNING **: Загружаемый модуль тем не найден в module_path: "aurora",
Предупреждение менеджера окон: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp
Предупреждение менеджера окон: last_focus_time (151436386) is greater than comparison timestamp (151436377).  This most likely represents a buggy client sending inaccurate t
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e000ae (OpenOffice)
Предупреждение менеджера окон: 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-30 09:48:41 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 ***