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 487503 - crash in XChat-GNOME IRC Chat: stavo aprendo l'applicaz...
crash in XChat-GNOME IRC Chat: stavo aprendo l'applicaz...
Status: RESOLVED FIXED
Product: l10n
Classification: Infrastructure
Component: Italian [it]
GNOME 2.18
Other All
: High critical
: ---
Assigned To: algol
algol
: 488246 491377 495715 497051 499064 506706 510386 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-17 13:48 UTC by clabopax
Modified: 2008-07-22 20:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
Update for the Italian po (801 bytes, patch)
2007-10-29 17:44 UTC, Milo Casagrande
none Details | Review

Description clabopax 2007-10-17 13:48:27 UTC
What were you doing when the application crashed?
stavo aprendo l'applicazione xchat gnome e basta


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Bluecurve

Memory status: size: 116830208 vsize: 116830208 resident: 46530560 share: 43065344 rss: 46530560 rss_rlim: 4294967295
CPU usage: start_time: 1192628756 rtime: 82 utime: 68 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208318240 (LWP 4221)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208318240 (LWP 4221))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 pevent_make_pntevts
  • #8 load_text_events
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (10 sec old) ---------------------
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  18
  Minor opcode:  0
  Resource id:  0x380001c
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x380029f non valido per 0x38007af (Search res).
Launched ok, pid = 3619
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x380029f non valido per 0x38008e4 (Search res).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x65 non valido per 0x380029f (Konfigurat).
ICE default IO error handler doing an exit(), pid = 3173, errno = 0
ICE default IO error handler doing an exit(), pid = 3609, errno = 0
(xchat-gnome:4221): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
(xchat-gnome:4221): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed
XChat CRITICAL *** default event text failed to build!
--------------------------------------------------
Comment 1 Milo Casagrande 2007-10-29 14:09:05 UTC
If it's the Italian version of the program, as I suppose, it's a translation problem: there's a malformed string in the Italian translation (it was also reported in Launchpad: 89964).

As I back home from office I'll send new updated translation.
Comment 2 Milo Casagrande 2007-10-29 17:44:53 UTC
Created attachment 98123 [details] [review]
Update for the Italian po

This patch should resolve this issue for the 0.18 version.
Comment 3 Diego Escalante Urrelo (not reading bugmail) 2007-12-08 04:26:49 UTC
-> l10n
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2007-12-08 04:27:32 UTC
*** Bug 488246 has been marked as a duplicate of this bug. ***
Comment 5 Diego Escalante Urrelo (not reading bugmail) 2007-12-08 04:28:27 UTC
*** Bug 491377 has been marked as a duplicate of this bug. ***
Comment 6 Diego Escalante Urrelo (not reading bugmail) 2007-12-08 04:30:26 UTC
*** Bug 495715 has been marked as a duplicate of this bug. ***
Comment 7 Diego Escalante Urrelo (not reading bugmail) 2007-12-08 04:30:37 UTC
*** Bug 497051 has been marked as a duplicate of this bug. ***
Comment 8 Diego Escalante Urrelo (not reading bugmail) 2007-12-08 04:30:50 UTC
*** Bug 499064 has been marked as a duplicate of this bug. ***
Comment 9 Marc-Andre Lureau 2008-03-23 23:55:50 UTC
*** Bug 506706 has been marked as a duplicate of this bug. ***
Comment 10 Marc-Andre Lureau 2008-03-23 23:56:01 UTC
*** Bug 510386 has been marked as a duplicate of this bug. ***
Comment 11 Claude Paroz 2008-03-24 08:41:08 UTC
Milo's patch has already been committed to trunk. Shouldn't we consider this as closed? 
Comment 12 Milo Casagrande 2008-07-22 15:17:11 UTC
(In reply to comment #11)
> Milo's patch has already been committed to trunk. Shouldn't we consider this as
> closed? 

Yes, this bug could be closed...