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 347954 - Crash if temp_iso_dir is not available
Crash if temp_iso_dir is not available
Status: RESOLVED FIXED
Product: nautilus-cd-burner
Classification: Deprecated
Component: cd-burner
unspecified
Other other
: High critical
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
: 348003 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-18 19:52 UTC by guettli
Modified: 2006-07-21 11:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description guettli 2006-07-18 19:52:52 UTC
Distribution: Ubuntu 6.06 (dapper)
Package: nautilus-cd-burner
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash if temp_iso_dir is not available
Bugzilla-Product: nautilus-cd-burner
Bugzilla-Component: cd-burner
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
I set with the Config Editor the variable "temp_iso_dir" of
apps/nautilus-cd-burner to /data/tmp, 
since /tmp has not enough space. If /data is not mounted, nautilus
crashes.

Steps to reproduce the crash:
1.  set variable with config editor (Don't know the exact english term)
2.  insert CD
3. right-click on CD-Icon choose, copy, click "Burn"

Expected Results:
I would like to see a message, that the temp-dir is not
available.

How often does this happen?
Always

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/nautilus-cd-burner'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224563008 (LWP 12454)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224563008 (LWP 12454))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall




------- Bug created by bug-buddy at 2006-07-18 19:52 -------

Comment 1 Fabio Bonelli 2006-07-18 20:11:01 UTC
Thanks for the bug report!

Can you get us a stacktrace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Can you reproduce this with CVS HEAD? See also bug 344437.
Comment 2 Bastien Nocera 2006-07-19 10:10:30 UTC
*** Bug 348003 has been marked as a duplicate of this bug. ***
Comment 3 Bastien Nocera 2006-07-19 10:11:13 UTC
According to 348003, this should be straight forward to reproduce.
Comment 4 Fabio Bonelli 2006-07-19 10:37:08 UTC
Yes Bastien, I've set this one as NEEDINFO because, like bug 344437, I can't reproduce it.
Comment 5 Bastien Nocera 2006-07-19 10:50:41 UTC
Fair enough :)
Comment 6 Thomas Güttler 2006-07-21 10:58:02 UTC
(In reply to comment #2)
> *** Bug 348003 has been marked as a duplicate of this bug. ***
> 

Yes, both are surely the same bug. If you can not reproduce this bug with a new version, I think it is save to close this bug.
Comment 7 Fabio Bonelli 2006-07-21 11:13:30 UTC
Thanks Thomas, closing.

Feel free to reopen this bug if you can reproduce it again.