totem-xine启动后自动关闭问题(可能是硬件不支持而无法解决)
-
- 帖子: 18
- 注册时间: 2005-12-13 15:55
totem-xine启动后自动关闭问题(可能是硬件不支持而无法解决)
我想播放RMVB。
我已经sudo apt-get install beep-media-player totem-xine w32codecs gstreamer0.8-plugins了。提示如下:
正在读取软件包列表... 完成
正在分析软件包的依赖关系树... 完成
beep-media-player 已经是最新的版本了。
totem-xine 已经是最新的版本了。
w32codecs 已经是最新的版本了。
gstreamer0.8-plugins 已经是最新的版本了。
共升级了 0 个软件包,新安装了 0 个软件包,要卸载 0 个软件包,有 3 个软件未被升级。
但totem-xine启动后自动关闭!
请问如何解决?
我已经sudo apt-get install beep-media-player totem-xine w32codecs gstreamer0.8-plugins了。提示如下:
正在读取软件包列表... 完成
正在分析软件包的依赖关系树... 完成
beep-media-player 已经是最新的版本了。
totem-xine 已经是最新的版本了。
w32codecs 已经是最新的版本了。
gstreamer0.8-plugins 已经是最新的版本了。
共升级了 0 个软件包,新安装了 0 个软件包,要卸载 0 个软件包,有 3 个软件未被升级。
但totem-xine启动后自动关闭!
请问如何解决?
上次由 arky 在 2005-12-19 20:23,总共编辑 1 次。
-
- 帖子: 18
- 注册时间: 2005-12-13 15:55
终端启动提示:
~$ totem
(totem:8239): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
(totem:8239): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
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 80 error_code 11 request_code 140 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.)
然后TOTEM启动,闪了一下就不见了。
~$ totem
(totem:8239): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
(totem:8239): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
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 80 error_code 11 request_code 140 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.)
然后TOTEM启动,闪了一下就不见了。
- oneleaf
- 论坛管理员
- 帖子: 10441
- 注册时间: 2005-03-27 0:06
- 系统: Ubuntu 12.04
-
- 帖子: 18
- 注册时间: 2005-12-13 15:55
$ sudo rm -rf .gnome .nautilus .gnome2
Password:
~$ totem
(totem:8413): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
(totem:8413): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
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 80 error_code 11 request_code 140 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.)
还是一闪不见了。
Password:
~$ totem
(totem:8413): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
(totem:8413): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
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 80 error_code 11 request_code 140 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.)
还是一闪不见了。
-
- 帖子: 18
- 注册时间: 2005-12-13 15:55
~$ sudo totem
(totem:8476): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
(totem:8476): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
** (totem:8476): WARNING **: Failed to connect to the D-BUS daemon: No reply within specified time
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 80 error_code 11 request_code 140 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.)
也是一闪不见
(totem:8476): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
(totem:8476): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
** (totem:8476): WARNING **: Failed to connect to the D-BUS daemon: No reply within specified time
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 80 error_code 11 request_code 140 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.)
也是一闪不见
-
- 帖子: 18
- 注册时间: 2005-12-13 15:55
- oneleaf
- 论坛管理员
- 帖子: 10441
- 注册时间: 2005-03-27 0:06
- 系统: Ubuntu 12.04
-
- 帖子: 120
- 注册时间: 2005-11-26 19:01
- 联系:
- oneleaf
- 论坛管理员
- 帖子: 10441
- 注册时间: 2005-03-27 0:06
- 系统: Ubuntu 12.04
那就不用了,真是奇怪的问题。 去: http://www.ubuntuforums.org/ 问问?arky 写了:我的是FCITX,如果需要的话我把它删除试试看
- Beetle
- 帖子: 1637
- 注册时间: 2005-10-14 16:55
- 系统: OS X
- 来自: 江苏
- 联系: