From Fedora Project Wiki

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 229: Line 229:
| {{result|warn}}  
| {{result|warn}}  
<ref>1024x600 + 1920x1200</ref>
<ref>1024x600 + 1920x1200</ref>
<ref group="long">Gnome 3 shell: First connection to second monitor is "OK" but very slow (mutter 95% CPU). After disconnecting it is OK and resolutions are switched automatic. But second connection killed Gnome3 session.</ref>
<ref>Gnome 3 shell: First connection to second monitor is "OK" but very slow (mutter 95% CPU). After disconnecting it is OK and resolutions are switched automatic. But second connection killed Gnome3 session.</ref>
<ref>RHBZ#[https://bugzilla.redhat.com/show_bug.cgi?id=680037 680037] </ref>  
<ref>RHBZ#[https://bugzilla.redhat.com/show_bug.cgi?id=680037 680037] </ref>  
<ref>Gnome 3 fallback: is OK</ref>
<ref>Gnome 3 fallback: is OK</ref>
Line 309: Line 309:
| {{result|pass}} <ref>https://fedoraproject.org/wiki/File:Sgordon_rendercheck.txt</ref>
| {{result|pass}} <ref>https://fedoraproject.org/wiki/File:Sgordon_rendercheck.txt</ref>
| {{result|pass}}  
| {{result|pass}}  
| {{result|fail}} <ref group="long">"Unable to start new display. The name org.gnome.DisplayManager was not provided by any .service files" on attempting to switch user from gnome-shell. Suspect this is not however a driver bug?</ref>
| {{result|fail}} <ref>"Unable to start new display. The name org.gnome.DisplayManager was not provided by any .service files" on attempting to switch user from gnome-shell. Suspect this is not however a driver bug?</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|fail}} <ref>RHBZ#[https://bugzilla.redhat.com/show_bug.cgi?id=680142 680142] </ref>
| {{result|fail}} <ref>RHBZ#[https://bugzilla.redhat.com/show_bug.cgi?id=680142 680142] </ref>
Line 320: Line 320:
| {{result|warn}}<ref>only got fallback, starting gnome-shell --replace works, but is too slow to use</ref>
| {{result|warn}}<ref>only got fallback, starting gnome-shell --replace works, but is too slow to use</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|fail}}<ref group="long">In fullscreen the time slider wasn't available, only blinked a few times just to disappear again plus some [http://www.strlen.de/ukleinek/inteltestday/Screenshot.png strange effects on the Desktop] even after totem segfaulted (reported using that crash applet).  All that without compositing.</ref>
| {{result|fail}}<ref>In fullscreen the time slider wasn't available, only blinked a few times just to disappear again plus some [http://www.strlen.de/ukleinek/inteltestday/Screenshot.png strange effects on the Desktop] even after totem segfaulted (reported using that crash applet).  All that without compositing.</ref>
| {{result|pass}}
| {{result|pass}}
|  
|  
Line 328: Line 328:
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail}} <ref group="long">gnome spans both monitors, but I cannot disable one of them; it is instantly reenabled, related [https://bugs.freedesktop.org/show_bug.cgi?id=31519 bugreport]</ref>
| {{result|fail}} <ref>gnome spans both monitors, but I cannot disable one of them; it is instantly reenabled, related [https://bugs.freedesktop.org/show_bug.cgi?id=31519 bugreport]</ref>
| Hardware: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] + [8086:2792] <references/>
| Hardware: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] + [8086:2792] <references/>
|-
|-
Line 550: Line 550:
| {{result|pass}}
| {{result|pass}}
| {{result|pass}} <ref>46 tests passed of 46 total, so I'm not uploading any file</ref>
| {{result|pass}} <ref>46 tests passed of 46 total, so I'm not uploading any file</ref>
| {{result|warn}} <ref group="long">glxgears started fine at first, but I left it running for more than an hour, and eventually my LiveCD boot ran out of memory (read-only file system) and the gears quit spinning; I wonder if there is a resource leak or log file that overflows the livecd file system</ref>
| {{result|warn}} <ref>glxgears started fine at first, but I left it running for more than an hour, and eventually my LiveCD boot ran out of memory (read-only file system) and the gears quit spinning; I wonder if there is a resource leak or log file that overflows the livecd file system</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref group="long">pm-suspend took everything down, and on recovery, glxgears was still running; but I was running on LiveCD, and something about recovery made it so that all attempts to spawn new process failed with a segfault; not sure if it was an issue with livecd limitations, so I'm not opening a BZ</ref>
| {{result|warn}} <ref>pm-suspend took everything down, and on recovery, glxgears was still running; but I was running on LiveCD, and something about recovery made it so that all attempts to spawn new process failed with a segfault; not sure if it was an issue with livecd limitations, so I'm not opening a BZ</ref>
| {{result|pass}}
| {{result|pass}}
| <references/>
| <references/>
Line 566: Line 566:
| {{result|warn}}<ref>Same as BZ680325, desktop spans disabled display</ref>
| {{result|warn}}<ref>Same as BZ680325, desktop spans disabled display</ref>
| {{result|pass}}<ref>46 tests passed of 46 total</ref>
| {{result|pass}}<ref>46 tests passed of 46 total</ref>
| {{result|warn}}<ref group="long">With glxgears, terminal, and ff running, can sometimes get stray graphics when moving the mouse around on gnome shell's overview screen.  This also sometimes occurs with glxgears running and opening the shutdown dialog.</ref>
| {{result|warn}}<ref>With glxgears, terminal, and ff running, can sometimes get stray graphics when moving the mouse around on gnome shell's overview screen.  This also sometimes occurs with glxgears running and opening the shutdown dialog.</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail}}<ref group="long">Ran pm-suspend.  First time succeeded.  Second time hung the graphics.  Mouse moves, windows are not interactive, ctrl-alt-f2 kills mouse, ctrl-alt-f* doesn't do anything from that point.</ref>
| {{result|fail}}<ref>Ran pm-suspend.  First time succeeded.  Second time hung the graphics.  Mouse moves, windows are not interactive, ctrl-alt-f2 kills mouse, ctrl-alt-f* doesn't do anything from that point.</ref>
| {{result|fail}}<ref group="long">Double FAIL! [https://bugzilla.redhat.com/show_bug.cgi?id=639057 BZ639057] still present from F14, plus [https://bugzilla.redhat.com/show_bug.cgi?id=680333 BZ680333].  Along with BZ680325 and suspend issues, this makes F15 completely unusable for this laptop</ref>
| {{result|fail}}<ref>Double FAIL! [https://bugzilla.redhat.com/show_bug.cgi?id=639057 BZ639057] still present from F14, plus [https://bugzilla.redhat.com/show_bug.cgi?id=680333 BZ680333].  Along with BZ680325 and suspend issues, this makes F15 completely unusable for this laptop</ref>
|<references/>
|<references/>
|-
|-
Line 585: Line 585:
| {{result|pass}}<ref>notification-daemon died when I switched to different users</ref>
| {{result|pass}}<ref>notification-daemon died when I switched to different users</ref>
| {{result|pass}}<ref>desktop was on CTRL-ALT-F7; CTRL-ALT-F1 just led to a raw, empty xterm window</ref>
| {{result|pass}}<ref>desktop was on CTRL-ALT-F7; CTRL-ALT-F1 just led to a raw, empty xterm window</ref>
| {{result|fail}}<ref group="long">Closed laptop lid, system suspended; after about five minutes, opened lid and system resumed nicely. However, about ten minutes later the system slowly died with symptoms similar to Alex Williamson's, above. Could also be because I left glxgears running in each of the two users I had switched to, following Eric Blake's theory of a resource leak.</ref>
| {{result|fail}}<ref>Closed laptop lid, system suspended; after about five minutes, opened lid and system resumed nicely. However, about ten minutes later the system slowly died with symptoms similar to Alex Williamson's, above. Could also be because I left glxgears running in each of the two users I had switched to, following Eric Blake's theory of a resource leak.</ref>
| N/A
| N/A
| Integrated Graphics Chipset: Intel(R) GM45 <references/>
| Integrated Graphics Chipset: Intel(R) GM45 <references/>
Line 596: Line 596:
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|none}}
| {{result|
| {{result|none}}
| {{result|
|-
|-
| [[User:Rob Whalley|Rob Whalley]]  
| [[User:Rob Whalley|Rob Whalley]]  
Line 644: Line 644:
| {{result|pass}}
| {{result|pass}}
| {{result|fail|}}<ref>System suspends fine - leds are glitching properly - but it hangs on resume</ref>
| {{result|fail|}}<ref>System suspends fine - leds are glitching properly - but it hangs on resume</ref>
| {{result|fail|}}<ref group="long">It's an Nvidia Optimus laptop and the second screen connected to hdmi port is useless. xrandr outputs:
| {{result|fail|}}<ref>It's an Nvidia Optimus laptop and the second screen connected to hdmi port is useless. xrandr outputs:
LVDS1 connected ...
LVDS1 connected ...
VGA1 disconnected
VGA1 disconnected
Line 670: Line 670:
| [http://www.smolts.org/client/show/pub_b1a67576-eb6f-46d1-a7dd-5993972da97c HW]
| [http://www.smolts.org/client/show/pub_b1a67576-eb6f-46d1-a7dd-5993972da97c HW]
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref group="long">Sometimes the window-manager crashed. 2 times when it crashed the upper panel and alle windows disappears. Another time only the frameborders disappears, but the windows stay on desktop.</ref>
| {{result|warn}} <ref>Sometimes the window-manager crashed. 2 times when it crashed the upper panel and alle windows disappears. Another time only the frameborders disappears, but the windows stay on desktop.</ref>
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref group="long">The rotation is ok. But when I choose 180 degree rotation (and only with 180) and switches back to normal view, the normal view gets darker. The display light on the laptop was set to a darker value. With the brightness keys I can set it to the normal value.</ref>  
| {{result|warn}} <ref>The rotation is ok. But when I choose 180 degree rotation (and only with 180) and switches back to normal view, the normal view gets darker. The display light on the laptop was set to a darker value. With the brightness keys I can set it to the normal value.</ref>  
| {{result|pass}} <ref>Works. On terminal the following output appears:<BR>
| {{result|pass}} <ref>Works. On terminal the following output appears:<BR>
[[File:Rolle.2011-02-26.XRestart.JPG.gz]]<BR>
[[File:Rolle.2011-02-26.XRestart.JPG.gz]]<BR>
[[File:Rolle_2011-02-26_Xorg.0.log.gz]].</ref>
[[File:Rolle_2011-02-26_Xorg.0.log.gz]].</ref>
| {{result|warn}} <ref group="long">This test was really fast over, but no error occured. The time-command says:<BR>
| {{result|warn}} <ref>This test was really fast over, but no error occured. The time-command says:<BR>
real 0m57.643s<BR>
real 0m57.643s<BR>
user 0m0.705s<BR>
user 0m0.705s<BR>
Line 683: Line 683:
[[File:Rolle_2011-02-26_Renderchecklog.gz]]
[[File:Rolle_2011-02-26_Renderchecklog.gz]]
</ref>
</ref>
| {{result|pass}} <ref group="long">Running synchronized to the vertical refresh.  The framerate should be
| {{result|pass}} <ref>Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.<BR>
approximately the same as the monitor refresh rate.<BR>
...<BR>
...<BR>
Line 694: Line 694:
| {{result|pass}} <ref>Desktop was on CTRL-ALT-F7; CTRL-ALT-F1 is a terminal with bootmessages.</ref>
| {{result|pass}} <ref>Desktop was on CTRL-ALT-F7; CTRL-ALT-F1 is a terminal with bootmessages.</ref>
| {{result|fail}} <ref>After 1-2 seconds the system give up to suspend and nothing happens. The desktop remains fully visible and usable.</ref>
| {{result|fail}} <ref>After 1-2 seconds the system give up to suspend and nothing happens. The desktop remains fully visible and usable.</ref>
| {{result|warn}} <ref group="long">The second monitor is working and also the plug'n'play is working. The only thing is, when I locate the second monitor under the first one, on the second monitor on the upper side is a "gradient"-artefact, see [[File:Rolle_2011-02-26_Multihead.png.gz]]‎<BR>
| {{result|warn}} <ref>The second monitor is working and also the plug'n'play is working. The only thing is, when I locate the second monitor under the first one, on the second monitor on the upper side is a "gradient"-artefact, see [[File:Rolle_2011-02-26_Multihead.png.gz]]‎<BR>
[[File:Rolle_2011-02-26.LaptopFujitsu.xrandr.txt.gz]]</ref>
[[File:Rolle_2011-02-26.LaptopFujitsu.xrandr.txt.gz]]</ref>
| Laptop: Fujitsu Siemens Lifebook E8420<BR>
| Laptop: Fujitsu Siemens Lifebook E8420<BR>
Line 709: Line 709:
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref group="long">This test was really fast over, but no error occured. The time-command says approx. 1:50 min<BR>
| {{result|warn}} <ref>This test was really fast over, but no error occured. The time-command says approx. 1:50 min<BR>
[[File:Rolle_2011-03-01.EeePC.renderchecklog.gz]]</ref>
[[File:Rolle_2011-03-01.EeePC.renderchecklog.gz]]</ref>
| {{result|pass}}
| {{result|pass}}
Line 715: Line 715:
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}
| {{result|fail}} <ref group="long">The plug'n'play-event is functional. In 'display" both monitors appears correctly. Also the unplug is functional. But when I plugin the second monitor the desktop gets veeery slow. Every mouseclick executes after some seconds. I can't setup a new resolution. After I click 'apply' no change happens (or I must wait much longer?). When I play longer with plug'n'play it crashed randomly. One time the desktop crashed and the login screen appears. When I login now the fallback-mode is on.<BR>[[File:Rolle_2011-03-01.EeePC.xrandr.txt.gz]]</ref>
| {{result|fail}} <ref>The plug'n'play-event is functional. In 'display" both monitors appears correctly. Also the unplug is functional. But when I plugin the second monitor the desktop gets veeery slow. Every mouseclick executes after some seconds. I can't setup a new resolution. After I click 'apply' no change happens (or I must wait much longer?). When I play longer with plug'n'play it crashed randomly. One time the desktop crashed and the login screen appears. When I login now the fallback-mode is on.<BR>[[File:Rolle_2011-03-01.EeePC.xrandr.txt.gz]]</ref>
| Netbook: Asus EeePC 1001PX<BR>
| Netbook: Asus EeePC 1001PX<BR>
00:02.0 VGA compatible controller [0300]: Intel Corporation Pineview Integrated Graphics Controller [8086:a011]<BR>
00:02.0 VGA compatible controller [0300]: Intel Corporation Pineview Integrated Graphics Controller [8086:a011]<BR>
Line 777: Line 777:
|-
|-
| [[User:djasa | David Jaša]]
| [[User:djasa | David Jaša]]
| [http://www.smolts.org/client/show/pub_b371cdd8-fd23-4d59-b110-4568a6cdbff0 HW]
| [http://www.smolts.org/client/show/pub_b371cdd8-fd23-4d59-b110-4568a6cdbff0
HW]
| {{result|pass}}
| {{result|pass}}
| {{result|pass}}  
| {{result|pass}}  
Line 790: Line 791:
| {{result|fail}} <ref>pointer disappears on primary monitor (sometimes)</ref> <ref>Window manager gets killed (often)
| {{result|fail}} <ref>pointer disappears on primary monitor (sometimes)</ref> <ref>Window manager gets killed (often)
     </ref> <ref>every new process segfaults (if previous doesn't happen)</ref>  
     </ref> <ref>every new process segfaults (if previous doesn't happen)</ref>  
| {{result|warn}} <ref>X crashed once</ref> <ref group="long">"mirror" mode only recognizes only 800x600 and 1024x768, but that isn't native resolution of any connected display and both displays have 16:9 aspect ratio</ref>
| {{result|warn}} <ref>X crashed once</ref> <ref>"mirror" mode only recognizes only 800x600 and 1024x768, but that isn't native resolution of any connected display and both displays have 16:9 aspect ratio</ref>
| <references/>
| <references/>
|-
|-
Line 873: Line 874:
| [http://www.smolts.org/client/show/pub_b1a67576-eb6f-46d1-a7dd-5993972da97c HW]
| [http://www.smolts.org/client/show/pub_b1a67576-eb6f-46d1-a7dd-5993972da97c HW]
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref group="long">As Liveuser it works.<BR>
| {{result|warn}} <ref>As Liveuser it works.<BR>
As root-User it fails with the following shell-output:<BR>
As root-User it fails with the following shell-output:<BR>
root@localhost mesa]# avogadro<BR>
root@localhost mesa]# avogadro<BR>
Line 890: Line 891:
| [http://www.smolts.org/client/show/pub_7f920b64-c270-4914-9eb6-94388e06f26f HW]
| [http://www.smolts.org/client/show/pub_7f920b64-c270-4914-9eb6-94388e06f26f HW]
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref group="long">As Liveuser it works.<BR>
| {{result|warn}} <ref>As Liveuser it works.<BR>
As root-User it fails with the following shell-output:<BR>
As root-User it fails with the following shell-output:<BR>
root@localhost mesa]# avogadro<BR>
root@localhost mesa]# avogadro<BR>
Line 923: Line 924:
|}
|}


== Long comments ==
[[Category:Fedora 15 Test Days]]
<references group="long" />
 
[[Category:Fedora 15 Test Days]]
Please note that all contributions to Fedora Project Wiki are considered to be released under the Attribution-Share Alike 4.0 International (see Fedora Project Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please solve the following task below and enter the answer in the box (more info):

Cancel Editing help (opens in new window)