xmessage X errors

Bug #792268 reported by Emanuel Bronshtein
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
x11-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: x11-utils

xmessage unable to handle long input and crash with X error .

test case :
1 )
emanuel@emanuel-desktop:/tmp$ /usr/bin/xmessage 'text' -buttons `python -c "print 'A'*100000"`
X Error of failed request: BadAlloc (insufficient resources for operation)
  Major opcode of failed request: 53 (X_CreatePixmap)
  Serial number of failed request: 171
  Current serial number in output stream: 190

2 ) the window opened and immediately closed with error .
emanuel@emanuel-desktop:/tmp$ echo `python -c "print 'A'*1000000"` > /tmp/Z
emanuel@emanuel-desktop:/tmp$ /usr/bin/xmessage -file /tmp/Z
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
  Major opcode of failed request: 74 (X_PolyText8)
  Serial number of failed request: 198
  Current serial number in output stream: 198

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in x11-utils (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.