After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 614007 - totem change screen resoltion on full screen mode
totem change screen resoltion on full screen mode
Status: RESOLVED NOTGNOME
Product: totem
Classification: Core
Component: general
2.29.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-03-26 13:02 UTC by Diska
Modified: 2010-04-15 09:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Diska 2010-03-26 13:02:10 UTC
can you look about bug on https://bugs.launchpad.net/ubuntu/+source/totem/+bug/541471

i don't know if the problem is that i use a screen resolution manually added to xrandr

cat .xprofile

#!/bin/sh
xrandr --newmode "1280x1024_85.00" 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -HSync +Vsync
xrandr --addmode VGA1 "1280x1024_85.00"
Comment 1 Bastien Nocera 2010-03-26 14:27:41 UTC
(In reply to comment #0)
> can you look about bug on
> https://bugs.launchpad.net/ubuntu/+source/totem/+bug/541471

No. Post the relevant information here.
Comment 2 Diska 2010-03-26 14:57:22 UTC
ok sorry

When i try to open totem in full screen mode ( with a video or not ) it change monitor resolution.

i'm using it on ubuntu lucid with a non standard video resolution

that i set manually  to xrandr via .xprofile

cat .xprofile

#!/bin/sh
xrandr --newmode "1280x1024_85.00" 159.36 1280 1376 1512 1744 1024 1025 1028 1075 -HSync +Vsync
xrandr --addmode VGA1 "1280x1024_85.00"
Comment 3 Bastien Nocera 2010-04-06 18:30:30 UTC
What's the output of "xrandr -q" before and after Totem has switched the screen resolution? Could you also take a screenshot of xvidtune in the "normal" resolution?

My guess is a bug in XF86VidModeGetModeLine() which returns a value that's not up-to-date.
Comment 4 Diska 2010-04-09 06:44:29 UTC
before 

Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1360x768       59.8  
   1024x768       60.0  
   800x600        60.3     56.2  
   848x480        60.0  
   640x480        59.9     59.9  
   1280x1024_85.00   84.8* 
DVI1 disconnected (normal left inverted right x axis y axis)
TV1 disconnected (normal left inverted right x axis y axis)


after totem change

Screen 0: minimum 320 x 200, current 1360 x 768, maximum 4096 x 4096
VGA1 connected 1360x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1360x768       59.8* 
   1024x768       60.0  
   800x600        60.3     56.2  
   848x480        60.0  
   640x480        59.9     59.9  
   1280x1024_85.00   84.8  
DVI1 disconnected (normal left inverted right x axis y axis)
TV1 disconnected (normal left inverted right x axis y axis)
Comment 5 Bastien Nocera 2010-04-09 11:20:17 UTC
I'd also need a screenshot of the screen presented by xvidtune before and after the problem occurs.

My guess is that the XRandR output before the problem occurs does not match the xvidtune (XVidMode) output.
Comment 6 Diska 2010-04-09 11:55:49 UTC
the same output before and after 

xvidtune
Unable to query monitor info

xvidtune -show
"1360x768"     84.75   1360 1432 1568 1776    768  771  781  798 -hsync +vsync
Comment 7 Bastien Nocera 2010-04-09 14:47:21 UTC
Yep, it's a bug in libXxf86vm or in your display driver.

"xvidtune -show" should show the same resolution as xrandr before resizing, but it instead makes us think it has a viewport. It might be happening because you're creating the mode yourself, and libXxf86vm isn't catching up to that fact.

On my Fedora 12 machine with an intel driver:
$ xrandr -q
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm
   1680x1050      60.0*+
   1280x1024      75.0     60.0  
   1152x864       75.0  
   1024x768       75.1     60.0  
   800x600        75.0     60.3  
   640x480        75.0     60.0  
   720x400        70.1  
$ xvidtune -show
"1680x1050"   146.25   1680 1784 1960 2240   1050 1053 1059 1089 -hsync +vsync
$ xrandr -s 1280x1024
$ xvidtune -show
"1280x1024"   135.00   1280 1296 1440 1688   1024 1025 1028 1066 +hsync +vsync

File a bug against your distrubution, and have them check whether it's a display driver or libXxf86vm bug.
Comment 8 Diska 2010-04-14 19:30:43 UTC
(In reply to comment #7)
> Yep, it's a bug in libXxf86vm or in your display driver.
> 
> "xvidtune -show" should show the same resolution as xrandr before resizing, but
> it instead makes us think it has a viewport. It might be happening because
> you're creating the mode yourself, and libXxf86vm isn't catching up to that
> fact.
> 
> On my Fedora 12 machine with an intel driver:
> $ xrandr -q
> Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 4096 x 4096
> VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x
> 270mm
>    1680x1050      60.0*+
>    1280x1024      75.0     60.0  
>    1152x864       75.0  
>    1024x768       75.1     60.0  
>    800x600        75.0     60.3  
>    640x480        75.0     60.0  
>    720x400        70.1  
> $ xvidtune -show
> "1680x1050"   146.25   1680 1784 1960 2240   1050 1053 1059 1089 -hsync +vsync
> $ xrandr -s 1280x1024
> $ xvidtune -show
> "1280x1024"   135.00   1280 1296 1440 1688   1024 1025 1028 1066 +hsync +vsync
> 
> File a bug against your distrubution, and have them check whether it's a
> display driver or libXxf86vm bug.


can you tell me your libxx.. version and driver version?
Comment 9 Bastien Nocera 2010-04-15 09:00:02 UTC
I don't think my versions would help. The problem most likely is that you're creating a mode yourself, rather than relying on those detected by xrandr.