Totem: Warning in console: Error connecting to DBus

Bug #93663 reported by Marco
0
Affects Status Importance Assigned to Milestone
Totem
Expired
High
gtk+2.0 (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: totem

** (totem:7514): WARNING **: Error connecting to DBus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 629 error_code 8 request_code 141 minor_code 13)
  (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.)

ProblemType: Bug
Architecture: i386
Date: Mon Mar 19 12:11:11 2007
DistroRelease: Ubuntu 7.04
Uname: Linux amilo 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux

Marco (mfj)
Changed in totem:
status: Unconfirmed → Unknown
Revision history for this message
Marco (mfj) wrote :

totem --sync
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 3500 error_code 8 request_code 141 minor_code 13)
  (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.)

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. Can you get a backtrace by running these commands?

$ gdb totem
...
(gdb) break gdk_x_error
(gdb) run --sync
...
(gdb) set logging on
(gdb) thread apply all bt full

and attach the resulting gdb.txt file here?

Changed in totem:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Marco (mfj) wrote :

I report many freeze and crashes, when I take a backtrace.
I hope that this is a correct way for you.

Changed in totem:
status: Unknown → Unconfirmed
Revision history for this message
Marco (mfj) wrote :

As requested from Gnome Team, I re-take a backtrace of Totem using libgtk with debugging symbols.

Revision history for this message
Marco (mfj) wrote :

Moved to gtk+ from Gnome Team

Changed in totem:
status: Unconfirmed → Unknown
Revision history for this message
Marco (mfj) wrote :

Backtrace using libgtk and libx11 with debugging symbols.

Changed in totem:
status: Unknown → Unconfirmed
Changed in gtk+2.0:
status: Needs Info → Unconfirmed
Changed in gtk+2.0:
importance: Medium → Low
status: New → Triaged
Andrew (and471)
Changed in totem:
status: New → Confirmed
status: Confirmed → New
Changed in totem:
importance: Unknown → High
Changed in totem:
status: New → Incomplete
Changed in totem:
status: Incomplete → Expired
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.