Bug 810137 - re-login to Fedora 17 Beta Live image causes fail whale
Summary: re-login to Fedora 17 Beta Live image causes fail whale
Keywords:
Status: CLOSED DUPLICATE of bug 810451
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-05 09:02 UTC by Daiki Ueno
Modified: 2012-04-18 04:53 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-04-12 15:55:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
~/.xsession-errors (17.10 KB, text/plain)
2012-04-05 09:02 UTC, Daiki Ueno
no flags Details

Description Daiki Ueno 2012-04-05 09:02:40 UTC
Created attachment 575328 [details]
~/.xsession-errors

Description of problem:
With Beta RC3 Live Desktop image, I got fail whale when I clicked "Log Out..." from the status menu (that should trigger re-login).

Version-Release number of selected component (if applicable):
gnome-shell-3.4.0-1.fc17.x86_64
xorg-x11-server-Xorg-1.12.0-2.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1. qemu-kvm -m 2G -net nic -net user -vnc :5 -cdrom Fedora-17-Beta-x86_64-Live-Desktop.iso -boot d
2. Click "Live System User" on the right top corner
3. Click "Log Out..." button on the menu
  
Actual results:
log out, and then automatically re-log in.

Expected results:
log out, and got fail whale

Additional info:

Comment 1 Owen Taylor 2012-04-12 15:55:16 UTC

*** This bug has been marked as a duplicate of bug 810451 ***

Comment 2 Daiki Ueno 2012-04-18 04:53:33 UTC
Hmm, still I can reliably reproduce the problem with the final Beta live image.

I tried it with several different settings:

* run on kvm or baremetal
* host video drivers: intel or nvidia
* i686 or x86_64 image
* (on kvm) different display options (vnc, -vga std, and -vga cirrus)

and only with the baremetal cases, re-login works.

So I suspect this is an issue of gnome-shell software rendering (mesa or X11?).


Note You need to log in before you can comment on or make changes to this bug.