Bug 116727 - Blam reports X-Windows Errors
Summary: Blam reports X-Windows Errors
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: RC 2
Hardware: x86-64 All
: P5 - None : Major
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-13 09:53 UTC by Holger Hetterich
Modified: 2006-01-27 06:52 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Hetterich 2005-09-13 09:53:10 UTC 
How to reproduce: Start Blam on 10.0-RC2-x86_64

hhetter@g180:~> blam
ALSA lib pcm_direct.c:202:(make_local_socket) chmod failed:
/tmp/alsa-dmix-16103-1126605004-61562: Operation not permitted
ALSA lib pcm_dmix.c:840:(snd_pcm_dmix_open) unable to create server
The program 'Blam' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 140 error_code 2 request_code 25 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.)
Comment 1 JP Rosevear 2005-09-13 12:28:33 UTC 
Starts fine under beta 4 on x86_64 and no recent changes have been made, the
alsa problems were recently fixed, could you try this newer alsa package?
Comment 2 Holger Hetterich 2005-09-13 12:38:33 UTC 
I can try Alsa from stable but I don't think that's the problem as I use RC2.

blam starts fine when I use --sync as command line parameter.
Comment 3 Takashi Iwai 2005-09-13 12:44:45 UTC 
Note taht RC2 alsa package had another bug (#115817).  This is already fixed on
STABLE.
Comment 4 Holger Hetterich 2005-09-13 13:09:27 UTC 
I now installed alsa from STABLE, and I don't get the socket error messages, but
the problem stays the same,  blam crashes with:


hhetter@g180:~> blam
The program 'Blam' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 140 error_code 2 request_code 25 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.)
hhetter@g180:~>
Comment 5 JP Rosevear 2005-09-15 14:19:56 UTC 
Possible idea - can you update to gtk2 2.8.3-4?
Comment 6 JP Rosevear 2006-01-26 19:06:29 UTC 
Did you ever try the update holger?
Comment 7 Holger Hetterich 2006-01-27 06:52:13 UTC 
It works fine on x86_64 with 10.0-final.