Bug 5532 - Package Totem crash at the opening
Summary: Package Totem crash at the opening
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-21 14:55 CEST by David GEIGER
Modified: 2012-04-22 12:13 CEST (History)
0 users

See Also:
Source RPM: totem
CVE:
Status comment:

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

Description David GEIGER 2012-04-21 14:55:56 CEST 
I test Mageia 2_beta 3 for x86_64 ,and when I open the package totem it
crash .

Here the result :


$ totem

(totem:25374): Gdk-WARNING **: The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 3306 error_code 3 request_code 3 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 GDK_SYNCHRONIZE environment
   variable 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 Manuel Hiebel 2012-04-21 23:51:49 CEST 
You try to open totem under gnome ?

Assignee: bugsquad => olav

Comment 2 David GEIGER 2012-04-22 01:45:18 CEST 
No , I try to open totem on kde4 ,which is installed by default.
Comment 3 David GEIGER 2012-04-22 08:17:23 CEST 
Well I'm sorry for the inconvenience but today the package totem works well and opens without error message.
This is probably a result has an update.

$ totem

---------------------------------------------------------------

I think you can close this bug.
Comment 4 Manuel Hiebel 2012-04-22 12:13:41 CEST 
ok, feel free to reopen

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.