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 139558 - Crashes after make a new profile with space characters in the profile name.
Crashes after make a new profile with space characters in the profile name.
Status: RESOLVED DUPLICATE of bug 122349
Product: gnome-terminal
Classification: Core
Component: general
2.4.x
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-02-09 21:34 UTC by hylin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description hylin 2004-04-09 07:48:03 UTC
Distribution: Fedora Core release 1 (Yarrow)
Package: gnome-terminal
Severity: major
Version: GNOME2.4.0 2.4.x
Gnome-Distributor: GNOME.Org
Synopsis: Crashes after make a new profile with space characters in the profile name.
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.4.x
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:

The gnome-terminal crashes when I try to create a new profile with space
characters in the profile name.
If I name the profile with a shorter name, the application works fine.
That's why I guess the bug is due to
the space characters (or long file name) in the profile name.

Steps to reproduce the crash:
1. Choose "Profile..." menu item.
2. Click "New" button.
3. Name the new profile as "Nimbus Mono font".
4. Choose "Default" as the base profile.
5. Click "Create" or kit the Enter key.
6. Crash...

Expected Results:

Needly to say. No crash. :)

How often does this happen?

Always.

Additional Information:

My OS is an updated Fedora Core 1 (last update: Feb/08/2004).
CPU: Pentium III 1 GHz
RAM: 512 MB



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[Thread
debugging using libthread_db enabled]
[New Thread -1084411232 (LWP 2717)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x00606c32 in _dl_sysinfo_int80 ()
   from /lib/ld-linux.so.2

Thread 1 (Thread -1084411232 (LWP 2717))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #5 raise
    from /lib/tls/libc.so.6
  • #6 abort
    from /lib/tls/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 terminal_app_edit_encodings
  • #10 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-09 03:48 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-terminal".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was hylin@lion.ee.ntu.edu.tw.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Mariano Suárez-Alvarez 2004-04-09 08:15:18 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

*** This bug has been marked as a duplicate of 122349 ***