GNOME Bugzilla – Bug 316890
totem again.....
Last modified: 2005-10-03 08:13:25 UTC
Distribution: Debian testing/unstable Package: totem Severity: normal Version: GNOME2.10.2 1.0.4 Gnome-Distributor: Debian Synopsis: totem again..... Bugzilla-Product: totem Bugzilla-Component: general Bugzilla-Version: 1.0.4 BugBuddy-GnomeVersion: 2.0 (2.10.1) Description: Description of the crash: sala15:/home/altamir# totem (totem:10032): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. libhal.c 2282 : Error sending msg: Service "org.freedesktop.Hal" does not exist The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 87 error_code 11 request_code 141 minor_code 19) (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.) sala15:/home/altamir# totem --sync (totem:10051): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. libhal.c 2282 : Error sending msg: Service "org.freedesktop.Hal" does not exist Option '--sync' is unknown and was ignored The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 87 error_code 11 request_code 141 minor_code 19) (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.) sala15:/home/altamir# Steps to reproduce the crash: 1. just click in totem icon 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223878976 (LWP 10073)] [New Thread -1226773584 (LWP 10074)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb731e201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 63127
Thread 1 (Thread -1223878976 (LWP 10073))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-21 23:38 UTC ------- Unknown version 1.0.4 in product totem. Setting version to "1.0.x". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was altamir@emc.ufsc.br.
BadAlloc's bad, but it doesn't match the stack trace. *** This bug has been marked as a duplicate of 316880 ***
*** Bug 316880 has been marked as a duplicate of this bug. ***