RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 636420 - sealert -s / -S segfaults if LANG=japanese is set
Summary: sealert -s / -S segfaults if LANG=japanese is set
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: setroubleshoot
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Walsh
QA Contact: Karel Srot
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-22 08:23 UTC by Milos Malik
Modified: 2017-12-05 10:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 09:48:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1509 0 normal SHIPPED_LIVE setroubleshoot bug fix update 2011-12-06 00:39:33 UTC

Description Milos Malik 2010-09-22 08:23:18 UTC 
Description of problem:
Not sure if the problem is in sealert or in gtk+glade.
Does not matter if you run it as root or as common user, segfault is a sure thing in both cases.
Does not matter if you run it locally or via SSH session.

Version-Release number of selected component (if applicable):
setroubleshoot-server-2.2.94-1.el6.i686
setroubleshoot-2.2.94-1.el6.i686
setroubleshoot-plugins-2.1.60-1.el6.noarch
setroubleshoot-doc-2.2.94-1.el6.i686

How reproducible:
always

Steps to Reproduce:
# LANG=japanese sealert -s
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 78 文字目でエラー:名前はUTF-8として正しくない文字列です - 'SELinux �ȥ��֥륷�塼�ȥ֥饦��' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 74 文字目でエラー:名前はUTF-8として正しくない文字列です - '���� - �������� -' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 84 文字目でエラー:名前はUTF-8として正しくない文字列です - 'ɽ���������ΤϤ����ޤ�����' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 37 文字目でエラー:名前はUTF-8として正しくない文字列です - '����' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Invalid input string
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
Segmentation fault (core dumped)
# LANG=japanese sealert -S
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 78 文字目でエラー:名前はUTF-8として正しくない文字列です - 'SELinux �ȥ��֥륷�塼�ȥ֥饦��' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 74 文字目でエラー:名前はUTF-8として正しくない文字列です - '���� - �������� -' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 84 文字目でエラー:名前はUTF-8として正しくない文字列です - 'ɽ���������ΤϤ����ޤ�����' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Failed to set text from markup due to error parsing markup: 1 行の 37 文字目でエラー:名前はUTF-8として正しくない文字列です - '����' は妥当ではありません
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
/usr/lib/python2.6/site-packages/setroubleshoot/browser.py:188: GtkWarning: Invalid input string
  self.widget_tree = gtk.glade.XML(self.gladefile, domain=domain)
Segmentation fault (core dumped)


Actual results:
2 segfaults

Expected results:
0 segfaults
Comment 1 Milos Malik 2010-09-22 08:33:11 UTC 
It did work on RHEL-5.5 where is 2.0.5-5.el5 version.
Comment 3 Milos Malik 2010-09-22 08:47:34 UTC 
It seems that glib is the culprit.

# dmesg | grep sealert
sealert[2477]: segfault at a112000 ip 00bef558 sp bff41780 error 4 in
libglib-2.0.so.0.2200.5[bb4000+e8000]
sealert[2480]: segfault at a76e000 ip 009f3558 sp bfcd3d90 error 4 in
libglib-2.0.so.0.2200.5[9b8000+e8000]
sealert[3908]: segfault at 8d85000 ip 007d0558 sp bfbbf070 error 4 in
libglib-2.0.so.0.2200.5[795000+e8000]
sealert[3914]: segfault at a000000 ip 007d0558 sp bfa520c0 error 4 in
libglib-2.0.so.0.2200.5[795000+e8000]
sealert[3921]: segfault at 9c7e000 ip 007d0558 sp bff28460 error 4 in
libglib-2.0.so.0.2200.5[795000+e8000]
sealert[3927]: segfault at 9c69000 ip 007d0558 sp bf9c9100 error 4 in
libglib-2.0.so.0.2200.5[795000+e8000]
sealert[4119]: segfault at 9567000 ip 00402558 sp bfcd3050 error 4 in
libglib-2.0.so.0.2200.5[3c7000+e8000]
sealert[4123]: segfault at 9217000 ip 002ca558 sp bfbdfa30 error 4 in
libglib-2.0.so.0.2200.5[28f000+e8000]
Comment 4 Matthias Clasen 2011-03-22 22:16:56 UTC 
The error messages actually point at invalid UTF-8 in the translated string.
Does this reproduce with any other locale ?
Comment 5 Matthias Clasen 2011-03-22 22:30:40 UTC 
Could be this string from ja.po, which looks suspicious. Note the \t in the attribute list which definitively looks like invalid markup to me.

msgid ""
"<span size='large' weight='bold' \tface='verdana'>No alerts to view.</span>"
msgstr ""
"<span size='large' weight='bold' \tface='verdana'>表示する通知はありません。"
"</span>"

I notice the same dubious \t in other .po files. It is the result of a stray tab in gui/browser.glade
Comment 6 Daniel Walsh 2011-03-23 18:32:09 UTC 
We are planning on back porting the new version of setroubleshoot from Fedora into RHEL6,  I tried this command on an F15 command, and it seemed to work.
Comment 10 Daniel Walsh 2011-05-23 18:51:22 UTC 
Fixed in setroubleshoot-3.0.31-1.el6
Comment 12 Eduard Benes 2011-06-27 09:05:14 UTC 
Clearing qa_ack, setroubleshoot has been removed from 6.2 approved list.
Comment 18 Miroslav Grepl 2011-11-01 18:24:09 UTC 
Looks like a test issue. I don't see it.
Comment 20 errata-xmlrpc 2011-12-06 09:48:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1509.html
Note You need to log in before you can comment on or make changes to this bug.