Bug 452170 - logjam crash during Retrieve of image dimensions
logjam crash during Retrieve of image dimensions
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: logjam (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Tom "spot" Callaway
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-19 15:43 EDT by Warren Togami
Modified: 2008-07-03 23:42 EDT (History)
0 users

See Also:
Fixed In Version: 4.5.3-24.fc8.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-03 23:42:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Warren Togami 2008-06-19 15:43:20 EDT
logjam-4.5.3-23.fc9.x86_64

Insert > Image... > <paste an image URL> Retrieve Dimensions from Network

Detaching after fork from child process 18035.
The program 'logjam' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 3515 error_code 14 request_code 1 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
logjam: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

Program exited with code 01.
Comment 1 Fedora Update System 2008-07-02 18:59:01 EDT
logjam-4.5.3-24.fc8.1 has been submitted as an update for Fedora 8
Comment 2 Fedora Update System 2008-07-03 23:41:53 EDT
logjam-4.5.3-24.fc8.1 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.