No drivers shown, but I know there are drivers available

Bug #1303209 reported by Ben
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kubuntu-driver-manager (Ubuntu)
Fix Released
Medium
Unassigned
kubuntu-notification-helper (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

The driver manager does not show any drivers for my graphics card but I know that there are proprietary drivers available.
This is the second time I've installed 14.04 on this computer.
The first time, I loaded the driver manager on the frist boot after installing and it worked, there were additional drivers listed. After that, I wanted to try different drivers but the driver manager wouldn't list any.

This time around, I didn't try the driver manager on the first boot, as I installed the system updates first and then rebooted. However, upon the second boot I ran the driver manager and there are no drivers to choose from no matter how many times I refresh it.

Ubuntu Release - Kubuntu 14.04 Trusty Tahr 64bit

kubuntu-driver-manager:
  Installed: 14.04ubuntu5
  Candidate: 14.04ubuntu5
  Version table:
 *** 14.04ubuntu5 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages
        100 /var/lib/dpkg/status

I expected to be able to load a proprietary driver for my AMD/ATI graphics card.

What actually happened is no drivers were listed despite the fact that I know they should be available.
Also, sometimes it says, "Something went terribly wrong. Please hit the 'Refresh Drivers List' button."

Tags: kubuntu
Ben (bshatt1987)
description: updated
Revision history for this message
Harald Sitter (apachelogger) wrote :

Please run:

ubuntu-drivers debug > ~/devices.log
qdbus --literal org.kubuntu.DriverManager /DriverManager org.kubuntu.DriverManager.devices >> ~/devices.log

this will createa file called devices.log in your home directory, please attach it to the this bug report.

Changed in kubuntu-driver-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Ben (bshatt1987) wrote :

Okay, here it is.
I hope it doesn't make a difference that I installed the driver manually.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Curious.

Please post the output of

/usr/lib/kde4/libexec/DriverManager_DBus& sleep 1; qdbus --literal org.kubuntu.DriverManager /DriverManager org.kubuntu.DriverManager.devices

Revision history for this message
Ben (bshatt1987) wrote :

Here we are:

[1] 23429
DriverManager_DBus::devices START
Error: org.freedesktop.DBus.Error.NoReply
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.

Revision history for this message
Harald Sitter (apachelogger) wrote :

:O

If you hit CTRL+Esc and search for 'driver' does it list a python3 process?

(the python helper for some reason apparently does not return)

Revision history for this message
Harald Sitter (apachelogger) wrote :

that is: shortly after you get the error when running the previous command

Revision history for this message
Ben (bshatt1987) wrote :

I do not. The only thing that I get when I search for 'driver' immediately after performing that command is the listing for Firefox because the word driver is in the title of this tab/window.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Most peculiar indeed.

What's the output of
time ubuntu-drivers list
time /usr/lib/kde4/libexec/DriverManager_DBus&; time qdbus --literal org.kubuntu.DriverManager /DriverManager org.kubuntu.DriverManager.devices

please note that you have to let it run for around 5 seconds after you get the error, your terminal should contain something like this as last line:

> /usr/lib/kde4/libexec/DriverManager_DBus 5.65s user 0.12s system 36% cpu 15.816 total

Revision history for this message
Ben (bshatt1987) wrote :

time ubuntu-drivers list -
fglrx-updates
fglrx

real 0m30.269s
user 0m29.668s
sys 0m0.491s

 time /usr/lib/kde4/libexec/DriverManager_DBus&; time qdbus --literal org.kubuntu.DriverManager /DriverManager org.kubuntu.DriverManager.devices -
Okay, well the original command you gave me give me :
bash: syntax error near unexpected token `;'

So I removed the '&', and instead ran:
time /usr/lib/kde4/libexec/DriverManager_DBus; time qdbus --literal org.kubuntu.DriverManager /DriverManager org.kubuntu.DriverManager.devices -
Exception ignored in: <bound method BusName.__del__ of <dbus.service.BusName org.kubuntu.DriverManager on <dbus._dbus.SessionBus (session) at 0x7fe1e0746d58> at 0x7fe1e06073c8>>
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 169, in __del__
  File "/usr/lib/python3/dist-packages/dbus/bus.py", line 320, in release_name
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 638, in call_blocking
TypeError: 'NoneType' object is not callable

real 0m10.715s
user 0m0.644s
sys 0m0.058s
Error: org.freedesktop.DBus.Error.NoReply
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.

real 0m25.618s
user 0m0.009s
sys 0m0.007s

Then I ran it without the ';', so this:
time /usr/lib/kde4/libexec/DriverManager_DBus& time qdbus --literal org.kubuntu.DriverManager /DriverManager org.kubuntu.DriverManager.devices -
[1] 2463
DriverManager_DBus::devices START
Error: org.freedesktop.DBus.Error.NoReply
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.

real 0m25.625s
user 0m0.010s
sys 0m0.008s
ben@ben-laptop:~$ DriverManager_DBus::devices END

real 0m39.891s
user 0m29.356s
sys 0m0.436s

And then it doesn't seem to want to end ever so I hit the enter button and it adds this -
[1]+ Done time /usr/lib/kde4/libexec/DriverManager_DBus

Changed in kubuntu-driver-manager (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Changed in kubuntu-notification-helper (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Changed in kubuntu-driver-manager (Ubuntu):
milestone: none → ubuntu-14.04
Changed in kubuntu-notification-helper (Ubuntu):
milestone: none → ubuntu-14.04
tags: added: kubuntu
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kubuntu-notification-helper - 14.04ubuntu11

---------------
kubuntu-notification-helper (14.04ubuntu11) trusty; urgency=medium

  * Set dbusinterface timeout to highest possible value to prevent timeouts
    when the dbus helper is tediously slow (LP: #1303209)
 -- Harald Sitter <email address hidden> Mon, 07 Apr 2014 14:55:41 +0200

Changed in kubuntu-notification-helper (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kubuntu-driver-manager - 14.04ubuntu6

---------------
kubuntu-driver-manager (14.04ubuntu6) trusty; urgency=medium

  [ Rohan Garg ]
  * Use a checkbox when there's only one driver

  [ Harald Sitter ]
  * Set dbusinterface timeout to highest possible value to prevent timeouts
    when the dbus helper is tediously slow (LP: #1303209)
    Looking back that was probably why we opted for an async connection earlier
 -- Harald Sitter <email address hidden> Mon, 07 Apr 2014 14:50:32 +0200

Changed in kubuntu-driver-manager (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Ben (bshatt1987) wrote :

Hey, hey. It works. Great work, thanks for helping (myself and the community)!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.