LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices


Reply
  Search this Thread
Old 12-29-2011, 10:51 PM   #1
unitedfollowers
LQ Newbie
 
Registered: Aug 2011
Location: USA/CO
Distribution: FC-14
Posts: 11

Rep: Reputation: 0
Cannot use Gnome 3 with F16 and Nvidia 560ti


Error is with dbus -- Skip down to **update**

I just installed F16 off of a Live CD and I've tried following some guides for installing the Nvidia proprietary drivers. I know the Nvidia driver is being used and is working, but when I logout after telling Gnome 3 to try non fall back mode all I get is a black screen and nothing happens, causing me to have to restart every time.

Like in the title, I'm using a Nvidia 560Ti. To install the Nvidia driver, I used yum to install kmod-nvidia and the x-11-nvidia-... packages from rpmfusion. Then I updated the initrd to use the Nvidia drivers. I also put nouveau as a blacklist in the kernel line in grub and put selinux into permissive. When I do lsmod I see nvidia and not nouveau. Direct acceleration by glxinfo is also at 'yes'.

There is a Nvidia X-server config program in my applications menu and when I change things like digital vibrance the display does change accordingly. And it seems to be monitoring the temp and etc correctly of the GPU.

So why is it giving me a black screen upon attempting to use Gnome 3 functionality?

Also as a side note, it appeared that the original F16 live cd couldn't run in its normal mode when I originally tried to run it. I had to run it under simple graphics mode to get it to work. And then I noticed that after I installed F16 to my hd, lsmod had vesa instead of nouveau (which only changed to nouveau after installing the kmod-nvidia stuff I think)

**update**
I think my issue is that dbus is broken. I've seen in /etc/log/messages there are dbus errors. Also upon trying to run gnome tweak it says the dbus daemon isn't running.

**update again**
It is most likely dbus, as I can't start the dbus daemon with
dbus-daemon --system as it says

Failed to start message bus: Element <fork> is not allowed in this context

Here is my /etc/dbus-1/session.conf:
Code:
<!-- This configuration file controls the per-user-login-session message bus.
     Add a session-local.conf and edit that rather than changing this 
     file directly. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
  <!-- Our well-known bus type, don't change this -->
  <type>session</type>

  <!-- If we fork, keep the user's original umask to avoid affecting
       the behavior of child processes. -->
  <keep_umask/>

  <listen>unix:tmpdir=/tmp</listen>

  <standard_session_servicedirs />

  <policy context="default">
    <!-- Allow everything to be sent -->
    <allow send_destination="*" eavesdrop="true"/>
    <!-- Allow everything to be received -->
    <allow eavesdrop="true"/>
    <!-- Allow anyone to own anything -->
    <allow own="*"/>
  </policy>

  <!-- Config files are placed here that among other things, 
       further restrict the above policy for specific services. -->
  <includedir>session.d</includedir>

  <!-- This is included last so local configuration can override what's 
       in this standard file -->
  <include ignore_missing="yes">session-local.conf</include>

  <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>

  <!-- For the session bus, override the default relatively-low limits 
       with essentially infinite limits, since the bus is just running 
       as the user anyway, using up bus resources is not something we need 
       to worry about. In some cases, we do set the limits lower than 
       "all available memory" if exceeding the limit is almost certainly a bug, 
       having the bus enforce a limit is nicer than a huge memory leak. But the 
       intent is that these limits should never be hit. -->

  <!-- the memory limits are 1G instead of say 4G because they can't exceed 32-bit signed int max -->
  <limit name="max_incoming_bytes">1000000000</limit>
  <limit name="max_incoming_unix_fds">250000000</limit>
  <limit name="max_outgoing_bytes">1000000000</limit>
  <limit name="max_outgoing_unix_fds">250000000</limit>
  <limit name="max_message_size">1000000000</limit>
  <limit name="max_message_unix_fds">4096</limit>
  <limit name="service_start_timeout">120000</limit>  
  <limit name="auth_timeout">240000</limit>
  <limit name="max_completed_connections">100000</limit>  
  <limit name="max_incomplete_connections">10000</limit>
  <limit name="max_connections_per_user">100000</limit>
  <limit name="max_pending_service_starts">10000</limit>
  <limit name="max_names_per_connection">50000</limit>
  <limit name="max_match_rules_per_connection">50000</limit>
  <limit name="max_replies_per_connection">50000</limit>

</busconfig>
And system.conf:
Code:
<!-- This configuration file controls the systemwide message bus.
     Add a system-local.conf and edit that rather than changing this 
     file directly. -->

<!-- Note that there are any number of ways you can hose yourself
     security-wise by screwing up this file; in particular, you
     probably don't want to listen on any more addresses, add any more
     auth mechanisms, run as a different user, etc. -->

<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-Bus Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>

  <!-- Our well-known bus type, do not change this -->
  <type>system</type>

  <!-- Run as special user -->
  <user>81</user>

  <!-- Fork into daemon mode -->
  <fork/>

  <!-- We use system service launching using a helper -->
  <standard_system_servicedirs/>

  <!-- This is a setuid helper that is used to launch system services -->
  <servicehelper>/lib/dbus-1/dbus-daemon-launch-helper</servicehelper>

  <!-- Write a pid file -->
  <pidfile>/var/run/messagebus.pid</pidfile>

  <!-- Enable logging to syslog -->
  <syslog/>

  <!-- Only allow socket-credentials-based authentication -->
  <auth>EXTERNAL</auth>

  <!-- Only listen on a local socket. (abstract=/path/to/socket 
       means use abstract namespace, don't really create filesystem 
       file; only Linux supports this. Use path=/whatever on other 
       systems.) -->
  <listen>unix:path=/var/run/dbus/system_bus_socket</listen>

  <policy context="default">
    <!-- All users can connect to system bus -->
    <allow user="*"/>

    <!-- Holes must be punched in service configuration files for
         name ownership and sending method calls -->
    <deny own="*"/>
    <deny send_type="method_call"/>

    <!-- Signals and reply messages (method returns, errors) are allowed
         by default -->
    <allow send_type="signal"/>
    <allow send_requested_reply="true" send_type="method_return"/>
    <allow send_requested_reply="true" send_type="error"/>

    <!-- All messages may be received by default -->
    <allow receive_type="method_call"/>
    <allow receive_type="method_return"/>
    <allow receive_type="error"/>
    <allow receive_type="signal"/>

    <!-- Allow anyone to talk to the message bus -->
    <allow send_destination="org.freedesktop.DBus"/>
    <!-- But disallow some specific bus services -->
    <deny send_destination="org.freedesktop.DBus"
          send_interface="org.freedesktop.DBus"
          send_member="UpdateActivationEnvironment"/>
  </policy>

  <!-- Config files are placed here that among other things, punch 
       holes in the above policy for specific services. -->
  <includedir>system.d</includedir>

  <!-- This is included last so local configuration can override what's 
       in this standard file -->
  <include ignore_missing="yes">system-local.conf</include>

  <include if_selinux_enabled="yes" selinux_root_relative="yes">contexts/dbus_contexts</include>

</busconfig>
***
Got dbus-daemon --system to work with no errors, (there was an unclosed tag) but gnome-tweak-tool still throws dbus errors:
Code:
WARNING : Shell not running
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_shell.py", line 57, in __init__
    self._shell = GnomeShellFactory().get_shell()
  File "/usr/lib/python2.7/site-packages/gtweak/utils.py", line 38, in getinstance
    instances[cls] = cls()
  File "/usr/lib/python2.7/site-packages/gtweak/gshellwrapper.py", line 121, in __init__
    proxy = _ShellProxy()
  File "/usr/lib/python2.7/site-packages/gtweak/gshellwrapper.py", line 30, in __init__
    d = Gio.bus_get_sync(Gio.BusType.SESSION, None)
  File "/usr/lib/python2.7/site-packages/gi/types.py", line 43, in function
    return info.invoke(*args, **kwargs)
GError: The connection is closed
WARNING : Could not list shell extensions
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_shell.py", line 62, in __init__
    extensions = self._shell.list_extensions()
AttributeError: ShellThemeTweak instance has no attribute '_shell'

** (gnome-tweak-tool:29959): WARNING **: The connection is closed

** (gnome-tweak-tool:29959): WARNING **: The connection is closed

** (gnome-tweak-tool:29959): WARNING **: The connection is closed

(gconftool-2:29962): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/desktop/gnome/shell/windows/button_layout': No D-BUS daemon running


(gconftool-2:29963): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Failed to get value for `/desktop/gnome/shell/windows/button_layout': No D-BUS daemon running


(gnome-tweak-tool:29959): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/gnome-tweak-tool", line 76, in <module>
    MainWindow()
  File "/usr/lib/python2.7/site-packages/gtweak/mainwindow.py", line 44, in __init__
    model)
  File "/usr/lib/python2.7/site-packages/gtweak/tweakview.py", line 40, in __init__
    self._model.load_tweaks()
  File "/usr/lib/python2.7/site-packages/gtweak/tweakmodel.py", line 131, in load_tweaks
    mods = __import__("gtweak.tweaks", globals(), locals(), tweak_files, 0)
  File "/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_shell.py", line 212, in <module>
    ShowWindowButtons(size_group=sg),
  File "/usr/lib/python2.7/site-packages/gtweak/tweaks/tweak_shell.py", line 42, in __init__
    **options)
  File "/usr/lib/python2.7/site-packages/gtweak/widgets.py", line 215, in __init__
    self.gconf.get_value(),
  File "/usr/lib/python2.7/site-packages/gtweak/gconf.py", line 62, in get_value
    return self._client.get_string(self._key)
  File "/usr/lib/python2.7/site-packages/gi/types.py", line 43, in function
    return info.invoke(*args, **kwargs)
gi._glib.GError: No D-BUS daemon running

Last edited by unitedfollowers; 12-29-2011 at 11:39 PM.
 
Old 12-30-2011, 08:28 PM   #2
John VV
LQ Muse
 
Registered: Aug 2005
Location: A2 area Mi.
Posts: 17,623

Rep: Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651Reputation: 2651
Quote:
I've tried following some guides....

I used yum to install kmod-nvidia and the x-11-nvidia
Did you did fallow leigh123linux's guide ?
"F16,F15 & F14 Nvidia driver guides "
http://forums.fedoraforum.org/showthread.php?t=204752

I would use the akmod

also the very first thing BEFORE messing with the nvidia driver would be to install the 2 gig's of updates for 16

Quote:
There is a Nvidia X-server config program in my applications menu and when I change things
that needs to be ran from the terminal AS root
 
Old 12-30-2011, 10:34 PM   #3
unitedfollowers
LQ Newbie
 
Registered: Aug 2011
Location: USA/CO
Distribution: FC-14
Posts: 11

Original Poster
Rep: Reputation: 0
I will try again tomorrow with a fresh install of F16 and with akmod. And I did have a fully up to date version of F16 (used software update)
 
Old 12-31-2011, 01:24 AM   #4
unitedfollowers
LQ Newbie
 
Registered: Aug 2011
Location: USA/CO
Distribution: FC-14
Posts: 11

Original Poster
Rep: Reputation: 0
I got it to work, I followed the instructions for akmod installation but upon reboot the system hung at Started SYSV: Late init script for live image..
So I reboot into rescue mode and changed /etc/X11/xorg.conf 'driver' from vesa to nvidia (which was there as default) and then reboot again. Then it finally worked and I have full Gnome 3 functionality.
Thanks!
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
F16 - missing/hidden windows R00ts Fedora 0 12-15-2011 11:29 AM
preupgrade from F15 to F16 : "Error 15 : File not found" Moore Linux - General 10 12-05-2011 04:31 AM
grub under f16 doesn't boot to MS XP Professional SP3 landonmkelsey Linux - Software 9 11-23-2011 11:39 AM
F16, How to change DE SSDnoob Fedora 11 11-17-2011 01:58 PM
getting game-port CH F16 combat stick to work in linux nitto Linux - Hardware 0 10-07-2006 06:51 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora

All times are GMT -5. The time now is 11:47 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration