KDE session didn't start after upgrading from Quantal to Raring. Fixed after installing proper qdbus package according to amd64 architecture

Bug #1155687 reported by avlas
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Undecided
Unassigned

Bug Description

Instead an error message appeared about qdbus. I then checked whether qdbus was correctly installed. I saw that only qdbus:i386 (in my amd64 system) was actually installed, so I proceeded to install regular qdbus. This replaced qdbus:i386 by the regular qdbus, which finally solved my problem. Now the KDE session starts without problems.

I hope this helps to fix the issue before the final release in April.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: qdbus 4:4.8.4+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Fri Mar 15 12:17:32 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2011-07-27 (597 days ago)
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=ca_ES
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ca_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: qt4-x11
UpgradeStatus: Upgraded to raring on 2013-03-15 (0 days ago)

Revision history for this message
avlas (avlas) wrote :
avlas (avlas)
summary: - KDE session didn't start after Raring upgrade (qdbus problem)
+ KDE session didn't start after Quantal to Raring Beta 1 upgrade (qdbus
+ problem)
avlas (avlas)
summary: - KDE session didn't start after Quantal to Raring Beta 1 upgrade (qdbus
- problem)
+ KDE session didn't start after upgrading from Quantal to Raring Beta 1.
+ Fixed after installing proper qdbus package according to amd64
+ architecture
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: KDE session didn't start after upgrading from Quantal to Raring Beta 1. Fixed after installing proper qdbus package according to amd64 architecture

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in qt4-x11 (Ubuntu):
status: New → Confirmed
Revision history for this message
Felix Geyer (debfx) wrote :

The problem seems to be that qdbus:i386 is already installed before the raring upgrade.

One example is from a precise upgrade:
  Installing ia32-libs-multiarch as Recommends of ia32-libs
    Installing libqtcore4 as Depends of ia32-libs-multiarch
      Installing libstdc++6 as Depends of libqtcore4
    Installing libqtgui4 as Depends of ia32-libs-multiarch
      Installing libaudio2 as Depends of libqtgui4
      Installing libmng1 as Depends of libqtgui4
        Installing liblcms1 as Depends of libmng1
      Installing libqt4-declarative as Depends of libqtgui4
        Installing libqt4-network as Depends of libqt4-declarative
          Installing libqt4-dbus as Depends of libqt4-network
            Installing libqt4-xml as Depends of libqt4-dbus
            Installing qdbus as Depends of libqt4-dbus

Here apt chose to install qdbus:i386 instead of the native amd64.

This worked fine until raring where qdbus is a symlink to qtchooser.
qtchooser seems to only consider native arch binaries (maybe the path is hardcoded to /usr/lib/<arch>/qt4/bin/).

Revision history for this message
Felix Geyer (debfx) wrote :

/usr/bin/qdbus is a symlink to qtchooser.
qtchooser only works when /usr/share/qtchooser/default.conf exists and points to qt4.conf,
This required both qt4-default and libqt4-dev.
Both aren't installed in a default kubuntu installation.
startkde however prepends `kde4-config --qt-binaries` (= /usr/lib/x86_64-linux-gnu/qt4/bin on amd64) to PATH so calling qdbus works even without those packages when qdbus is installed in the native arch.

amichair (amichai2)
summary: - KDE session didn't start after upgrading from Quantal to Raring Beta 1.
- Fixed after installing proper qdbus package according to amd64
- architecture
+ KDE session didn't start after upgrading from Quantal to Raring. Fixed
+ after installing proper qdbus package according to amd64 architecture
Revision history for this message
amichair (amichai2) wrote :

I just upgraded from 12.10 to 13.04 release (about a month after release, still not fixed), and got this problem - after reboot and login the desktop never showed up, and there was an xmessage process with the message "Could not start d-bus. Can you call qdbus?" (the message actually did not appear on the screen, but I saw it in the htop full process list - it must have been displayed somewhere off-screen).

The fix is to run "apt-get install qdbus" and reboot (to reach the terminal for running this command, try ctrl-alt-F1).

Seems like quite a serious bug to me, performing a successful (so it seems) upgrade and ending up with an unusable system. Newbies would probably not even know how to reach the terminal without a desktop, and may not see the message with a clue as to what might be wrong.

Revision history for this message
Adam Porter (alphapapa) wrote :

Just happened to me, too. This really needs to be fixed ASAP so people upgrading won't be stuck with unusable systems. A black eye for Kubuntu. :(

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

Other bug subscribers