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 706062 - Fedora19/gnome3: Activities : Applications : All = no icons displayed
Fedora19/gnome3: Activities : Applications : All = no icons displayed
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: drivers
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-08-15 11:55 UTC by shotboy
Modified: 2013-09-26 19:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
journalctl output (80.60 KB, application/octet-stream)
2013-08-18 14:44 UTC, shotboy
Details

Description shotboy 2013-08-15 11:55:25 UTC
New x86-64bit install of Fedora-19 using a pre-existing /home partition.
The all-applications display is apparently working as clicking on blank areas of the display will invoke applications, but: [frequent] displays the appropriate subset of application icons and [all] displays no icons.  Blank screen.
Changing background (solid, wallpaper, picture) does not alter the symptom.
<alt><F>,<r> does not alter the symptom.
Post-F19 new-user has the same symptom.
Comment 1 drago01 2013-08-18 12:32:34 UTC
Can you run journalctl e as the affected user after opening the application view and attach the output here?
Comment 2 shotboy 2013-08-18 14:44:19 UTC
Created attachment 252127 [details]
journalctl output
Comment 3 drago01 2013-08-18 15:51:09 UTC
OK, seems like shaders fail to compile which  gpu is that? Can you attach the output of glxinfo as well?
Comment 4 shotboy 2013-08-18 16:10:13 UTC
Cannot provide.
running 'glxinfo' in a terminal window caused Fedora to crash.  The display went to a gray screen with blue hyphens in a diagonal pattern and networking died (an existing SSH session terminated and the IP was not longer pingable).
Hard-reset to boot, logged in, opened a terminal window, and tried again.  Same symptoms.
Comment 5 drago01 2013-08-18 16:24:15 UTC
Ouch ... this smells like a driver bug. Do you happen to know which GPU (graphics card) do you have? Can you attach the output of "lspci" ?
Comment 6 shotboy 2013-08-18 17:13:18 UTC
00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
Comment 7 shotboy 2013-08-18 17:14:45 UTC
Integrated graphics on a Gigabyte GA-M68MT-S2PE motherboard.
Comment 8 drago01 2013-09-15 12:22:52 UTC
This looks like a driver bug. As a workaround you can try to install the proprietary nvidia driver which should work. But please file a bug against the nouveau driver at bugzilla.freedesktop.org
Comment 9 shotboy 2013-09-15 13:16:54 UTC
I created account on bugzilla.freedesktop.org and filed the bug against XORG.
In the interim, can you provide some guidance on how to install the proprietary nvidia driver ?
Comment 10 drago01 2013-09-15 15:00:20 UTC
(In reply to comment #9)
> I created account on bugzilla.freedesktop.org and filed the bug against XORG.
> In the interim, can you provide some guidance on how to install the proprietary
> nvidia driver ?

Type this commands in a terminal (as root i.e "type su and enter your rootpassword before"):

yum http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-19.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-19.noarch.rpm

yum install akmod-nvidia-304xx xorg-x11-drv-nvidia-304xx-libs


And then reboot your system.
Comment 11 drago01 2013-09-15 15:01:00 UTC
(In reply to comment #10)
> (In reply to comment #9)
> > I created account on bugzilla.freedesktop.org and filed the bug against XORG.
> > In the interim, can you provide some guidance on how to install the proprietary
> > nvidia driver ?
> 
> Type this commands in a terminal (as root i.e "type su and enter your
> rootpassword before"):
> 

yum install http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-19.noarch.rpm  http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-19.noarch.rpm

Sorry forgot the "install"
Comment 12 shotboy 2013-09-15 22:34:23 UTC
That didn't work out so well.  My system now gets no further than
[OK] Started GNOME Display Manager
I can ssh to it, but the KVM appears to be useless.
Comment 13 drago01 2013-09-15 22:45:32 UTC
(In reply to comment #12)
> That didn't work out so well.  My system now gets no further than
> [OK] Started GNOME Display Manager
> I can ssh to it, but the KVM appears to be useless.

OK that sucks ... do "yum history undo last" from your ssh session to get back to the previous state. 

I will try to get a fixed mesa package with a fix into fedora (will talk to the mesa maintainers).
Comment 14 shotboy 2013-09-15 22:51:28 UTC
That didn't work out so well.  My system now gets no further than
[OK] Started GNOME Display Manager
I can ssh to it, but the KVM appears to be useless.
Comment 15 shotboy 2013-09-15 22:52:58 UTC
Sorry for the duplicious post.
The undo last got be back to where I was.  Thank you.
I look forward to the next installment.
Thank you for your perseverance.
Comment 16 drago01 2013-09-18 11:26:36 UTC
This should be fixed in mesa 9.2.1 which will get released soon.
Comment 17 shotboy 2013-09-26 19:00:13 UTC
Indeed, the latest round of Fedora updates corrected the display problem.
TYVM