qdbus: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qdbus': No such file

[jlittle]

After upgrade to Saucy, running qdbus gave:

qdbus: could not exec '/usr/lib/x86_64-linux-gnu/qt5/bin/qdbus': No such file or directory

sudo apt-get install qdbus said:

qdbus is already the newest version.

Looking in muon, I saw that there's a package "qdbus-qt5" not installed, so I installed it, problem solved.

This suggests to me some kind of packaging inadequacy. Maybe the Qt versioning stuff (/usr/bin/qdbus links to qtchooser, which works out which version of Qt you want) defeats the APT mechanism.

Regards, John Little

[Rog132]

Defaults

As default the Kubuntu 13.10 / KDE 4.11 is using the Qt4. The (K)ubuntu plans (Trusty): https://lists.ubuntu.com/archives/ku...er/007541.html

At here:

$ apt-cache policy qdbus
qdbus:
  Installed: 4:4.8.4+dfsg-0ubuntu18
  Candidate: 4:4.8.4+dfsg-0ubuntu18
  Version table:
 *** 4:4.8.4+dfsg-0ubuntu18 0
        500 http://fi.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
        100 /var/lib/dpkg/status

~$ apt-cache policy qdbus-qt5
qdbus-qt5:
  Installed: (none)
  Candidate: 5.0.2-7ubuntu1
  Version table:
     5.0.2-7ubuntu1 0
        500 http://fi.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages

The Ubuntu / Unity is using the Qt5. If you install Unity / Qt development packages you could end to the mixed system.

Qt SDK:

~$ apt-get install -s qt-sdk
NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
...qt5-default qt5-qmake qtbase5-dev qtbase5-dev-tools...
The following packages will be REMOVED:
  qt4-default
...

They are:

~$ apt-cache show qt4-default
Package: qt4-default
Priority: optional
...
Description: Qt 4 development defaults package
 Qt is a cross-platform C++ application framework. Qt's primary feature
 is its rich set of widgets that provide standard GUI functionality.
 .
 This package sets Qt 4 to be the default Qt version to be used when
 using development binaries like qmake. It provides a default
 configuration for qtchooser, but does not prevent alternative Qt
 installations from being used.

:~$ apt-cache show qt5-default
Package: qt5-default
Priority: optional
...
Description: Qt 5 development defaults package
 Qt is a cross-platform C++ application framework. Qt's primary feature
 is its rich set of widgets that provide standard GUI functionality.
 .
 This package sets Qt 5 to be the default Qt version to be used when
 using development binaries like qmake. It provides a default
 configuration for qtchooser, but does not prevent alternative Qt
 installations from being used.

:~$ apt-cache show qtchooser
Package: qtchooser
Priority: extra
...
Description: Wrapper to select between Qt development binary versions
 Qt is a cross-platform C++ application framework. Qt's primary feature
 is its rich set of widgets that provide standard GUI functionality.
 .
 The Qt Chooser provides a wrapper to switch between versions of Qt
 development binaries when multiple versions like 4 and 5 are installed
 or local Qt builds are to be used.
 .
 If you wish to use Qt development binaries with the default PATH and
 without special parameters, you need to additionally install either
 qt4-default or qt5-default package to provide the default configuration.
...
Task: ubuntu-desktop, ubuntu-usb, kubuntu-desktop, kubuntu-active, kubuntu-active-desktop, kubuntu-active, ...

This suggests to me some kind of packaging inadequacy. Maybe the Qt versioning stuff (/usr/bin/qdbus links to qtchooser, which works out which version of Qt you want) defeats the APT mechanism...

If you think that this is a packaging bug you could file a bug report...