do not open files on desktop (on my laptop all is OK)

[yuractv]

Binary package hint: totem

** (totem:21450): WARNING **: Failed to create dbus proxy for org.gnome.SettingsDaemon: Could not get owner of name 'org.gnome.SettingsDaemon': no such name
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 109 error_code 11 request_code 132 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.)

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/totem-gstreamer
Package: totem-gstreamer 2.26.1-0ubuntu5
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
Uname: Linux 2.6.28-11-generic i686

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

could you attach your ~/.xsession-errors file?

[yuractv (uchetverov)]

yuractv@yura:~$ debug totem
outputting trace to '/tmp/gdb-totem.txt'
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 76 error_code 11 request_code 132 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.)

yuractv@yura:~$ cat /tmp/gdb-totem.txt
[Thread debugging using libthread_db enabled]
[New Thread 0xb6866a60 (LWP 28794)]
[New Thread 0xb63b4b90 (LWP 28798)]
[New Thread 0xb5b30b90 (LWP 28799)]
[Thread 0xb5b30b90 (LWP 28799) exited]
[New Thread 0xb5b30b90 (LWP 28800)]
[New Thread 0xb4551b90 (LWP 28801)]
[New Thread 0xafd12b90 (LWP 28802)]
[New Thread 0xaf511b90 (LWP 28803)]
[New Thread 0xaed10b90 (LWP 28804)]
[New Thread 0xae50fb90 (LWP 28805)]

Program exited with code 01.
No stack.
The program has no registers now.
No registers.

## error arise when i open media file
## in ~/.xsession-errors is nothing

[yuractv (uchetverov)]

# ~/.xsession-errors after system boot

yuractv@yura:~$ cat ~/.xsession-errors
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping root privileges.
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
N: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges:
N: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits.
N: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user.
GNOME_KEYRING_SOCKET=/tmp/keyring-bkY4Y7/socket
SSH_AUTH_SOCK=/tmp/keyring-bkY4Y7/socket.ssh
GNOME_KEYRING_PID=3358

(gnome-settings-daemon:3323): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed

(gnome-settings-daemon:3323): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Checking for Xgl: not present.
xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log
Detected PCI ID for VGA:
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Checking screen 1Comparing resolution (1152x864) to maximum 3D texture size (2048): Passed.
Checking for Software Rasterizer: present.
Software rasterizer detected, abortingaborting and using fallback: /usr/bin/metacity
Window manager warning: Failed to read saved session file /home/yuractv/.config/metacity/sessions/104a5bac18fc083ae0124266592930910600000031040019.ms: Failed to open file '/home/yuractv/.config/metacity/sessions/104a5bac18fc083ae0124266592930910600000031040019.ms': No such file or directory
** (nm-applet:3439): DEBUG: applet_common_device_state_changed
** (gnome-panel:3423): DEBUG: Adding applet 0.
** (gnome-panel:3423): DEBUG: Initialized Panel Applet Signaler.
** (gnome-panel:3423): DEBUG: Adding applet 1.
** (gnome-panel:3423): DEBUG: Adding applet 2.
** (gnome-panel:3423): DEBUG: Adding applet 3.
** (gnome-panel:3423): DEBUG: Adding applet 4.
** (gnome-panel:3423): DEBUG: Adding applet 5.
** (gnome-panel:3423): DEBUG: Adding applet 6.
** (gnome-panel:3423): DEBUG: Adding applet 7.
** (gnome-panel:3423): DEBUG: Adding applet 8.
** (gnome-panel:3423): DEBUG: Adding applet 9.
** (gnome-panel:3423): DEBUG: Adding applet 10.

** (nautilus:3424): WARNING **: Unable to add monitor: Not supported
** (gnome-panel:3423): DEBUG: Adding applet 11.
** (gnome-panel:3423): DEBUG: Adding applet 12.
** (gnome-panel:3423): DEBUG: Adding applet 13.
** (gnome-panel:3423): DEBUG: Adding applet 14.

(gnome-panel:3423): libglade-WARNING **: Unexpected element <requires-version> inside <glade-interface>.
** (gnome-panel:3423): DEB...

[Sebastien Bacher (seb128)]

Could you try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report?

[yuractv (uchetverov)]

Thanks, i find solution more simple way
take error from command line
(Details: serial 61 error_code 11 request_code 132 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
search throw google by phrase Details: serial 61 error_code 11 request_code 132 minor_code 19

Solution
... is to not use Xv, via 'gstreamer-properties' -> 'Video' tab -> select 'X Windows System (No Xv)'
the problem fixed

I forgot
I did thomething like this in MPlayer properties before

Excuse me for dull qwestion

[Sebastien Bacher (seb128)]

what videocard and driver do you use?

[yuractv (uchetverov)]

VideoCard: Intel Corporation 82865G Integrated Graphics [Video Card]
Driver: xf86-video-intel

Problem:
System by default consider that video driver - X11/xv
But -- in fact - it's X11/OpenGL

I'll see my laptop /etc/X11/xorg.conf
After NVidea installation I have on laptop OpenGL by default
I think it's only 1 line in xorg.conf -- nothing more

[Bryce Harrington (bryce)]

Hi uchetverov,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[yuractv (uchetverov)]

Unfortunately I have no xserver-xorg-video-intel at all
But now I find the solution:
I add option
Option "XVideo" "off"
on section "Device" in /etc/X11/xorg.conf

So, all new players know now, that default=gl, not xv
Nothing more. That's it
----

And besise, I configured videocard and have now max. resolution and frec. for my monitor (1280x1024/75Hz) by default
My xorg.conf now:

Section "Monitor"
    Identifier "Default Monitor"
    VendorName "Unknown"
    ModelName "BenQ FP71G"
    HorizSync 31.0 - 83.0
    VertRefresh 56.0 - 76.0
    Option "DPMS"
    Modeline "1280x1024_75.00" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync
    Option "PreferredMode" "1280x1024_75.00"
EndSection
Section "Device"
    Identifier "Intel Corporation 82852/865G Integrated Graphics Device"
    Option "XVideo" "off" # Disable xv
EndSection
Section "Screen"
    Identifier "Default Screen"
    Device "Intel Corporation 82852/865G Integrated Graphics Device"
    Monitor "Default Monitor"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
        Modes "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

------
Maybe it'll be usefull for someone who have the same configuration
------
Comments:
Section "Monitor" is specific for your monitor
Information you can probably find on producer site
Option "PreferredMode" must be the same as one of Modeline specifications (another case an error will arise)

"Intel Corporation 82852/865G Integrated Graphics Device" must be replaced with your Graphics Device specification
(intel driver support several Graphics Devices)

Device & Monitor in section Screen must be the same as an Identifiers in sections Monitor & Device
"Default Monitor" can be replaced with any name you like

Option "XVideo" "off" # Mean xv off, default - gll; only for intel drivers

All errors can be found in log - /var/log/Xorg.0.log

---
PS. My video card driver now: ftom packet xserver-xorg-video-intel (Intel i8xx, i9xx display driver)

[Bryce Harrington (bryce)]

[This is an automatic notification.]

A new major version of the -intel driver is now available in Karmic.

This version includes a major reworking of the acceleration
architecture, which resolves a huge number of issues. We do not know
whether it resolves the issue you reported.

Would you mind testing Karmic Alpha-2 and seeing if it is still a
problem? CD ISO images are available here:

  http://cdimages.ubuntu.com/releases/karmic/

If the issue can still be reproduced on karmic, please report here with
your findings, and attach a fresh Xorg.0.log from your test, and we will
be able to forward the bug upstream.

Otherwise, if the bug no longer exists in Karmic, let us know that as
well.

In the off chance you encounter different bugs while attempting to test
Karmic, please report those as new bug reports.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

It seems likely to me this bug is gone; the -intel driver has improved immensely in Karmic and a lot of bugs are being reported as no longer present. So hopefully that's the case here too.