Cannot login into KDE after upgrade from 12.04 to 14.04

[HugoHirsch]

After having run an upgrade to 14.04 I'm not able to login into a KDE session anymore.
I do get the stuff described in
https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1304805

My /usr/bin/startkde contains the problematic quotes although my package version is greater than the one proposed as a fix in case 1304805.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: kde-workspace 4:4.11.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 25 21:38:51 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-12-04 (1237 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
SourcePackage: kde-workspace
UpgradeStatus: Upgraded to trusty on 2014-04-24 (1 days ago)

[HugoHirsch (ubuntubugs-aiki-it)]

Manually removing the quotes makes the KDE session start again. I am not sure whether this really solves the bug mentioned in case https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1304805 but I would like to make clear that a newer version does not seem to contain the proposed fix and might break KDE systems after upgrading to 14.04.

[HugoHirsch (ubuntubugs-aiki-it)]

Problem remains after upgrading to
   kde-workspace-bin:amd64 4:4.11.8-0ubuntu6 => 4:4.11.9-0ubuntu0.2
    kde-workspace-data:all 4:4.11.9-0ubuntu0.1 => 4:4.11.9-0ubuntu0.2

The /usr/bin/startkde still contains the lines that should have been patched a while ago; not sure why this remains to be problematic.

[Harald Sitter (apachelogger)]

If you look again you'll notice that the line is in fact not the same but starts with an alias whereas the line in the other bug report did not.

Now, first off, please make sure that you actually get a very ugly error window that say s "Could not start d-bus. Can you call qdbus?" at login with the canonical startkde (you can restore it by running `sudo apt-get install --reinstall kde-workspace-bin`). If not, then you are having an entirely different issue and qdbus only happens to tie into it.

Once you confirmed that qdbus is in fact the culprit please copy ~/.cache/upstart/startkde.log (after a login attempt with error) to safety before fixing startkde and logging in again. Attach the file to this bug report once you fixed startkde again.

After that please fix your startkde again, login and post the output of the following commands as they might give us a hint as to what exactly is wrong.:

ls -lah /bin/sh
dpkg -l qdbus*
which qdbus
QT_SELECT=qt4 qdbus --help
QT_SELECT=qt5 qdbus --help
qdbus --help
dash -c 'alias qdbus="QT_SELECT=qt4 qdbus"; alias; qdbus --help'

After that please run the the following commands. The latter one might take quite a while, nothing to worry about:

sudo apt install debsums
sudo debsums -sc | tee debsums.log

once the last command has finished you will find a file called debsums.log in your home directory, also upload this file to the bug report.

[HugoHirsch (ubuntubugs-aiki-it)]

Thanks for the input provided - I've attached all outputs ... something seems to be wrong with my dbus installation if I get the messages right; but I'm not sure what exactly is wrong.

I do see plenty of
...
debsums: no md5sums for libobasis4.2-math
debsums: no md5sums for libobasis4.2-ogltrans
debsums: no md5sums for libobasis4.2-onlineupdate
debsums: no md5sums for libobasis4.2-ooofonts
debsums: no md5sums for libobasis4.2-ooolinguistic
debsums: no md5sums for libobasis4.2-postgresql-sdbc
debsums: no md5sums for libobasis4.2-python-script-provider
debsums: no md5sums for libobasis4.2-pyuno
debsums: no md5sums for libobasis4.2-writer
debsums: no md5sums for libobasis4.2-xsltfilter
debsums: no md5sums for libreoffice4.0-ure
debsums: no md5sums for libreoffice4.1-debian-menus
debsums: no md5sums for libreoffice4.2
debsums: no md5sums for libreoffice4.2-base
debsums: no md5sums for libreoffice4.2-calc
debsums: no md5sums for libreoffice4.2-de
debsums: no md5sums for libreoffice4.2-debian-menus
debsums: no md5sums for libreoffice4.2-dict-de
debsums: no md5sums for libreoffice4.2-dict-en
debsums: no md5sums for libreoffice4.2-dict-es
debsums: no md5sums for libreoffice4.2-dict-fr
debsums: no md5sums for libreoffice4.2-draw
debsums: no md5sums for libreoffice4.2-en-us
debsums: no md5sums for libreoffice4.2-impress
debsums: no md5sums for libreoffice4.2-math
debsums: no md5sums for libreoffice4.2-ure
debsums: no md5sums for libreoffice4.2-writer
...
but can neither tee nor pipe them into the debsums.log.

[HugoHirsch (ubuntubugs-aiki-it)]

These are the changes applied to /usr/bin/startkde that make a login possible.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "changes_2_startkde.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Harald Sitter (apachelogger)]

To fix this run

sudo apt-get install qdbus:amd64

for general information on what is going wrong see the other bug report.
Short version: qdbus:i386 is installed but the tool orchestrating binary selection wants to look for qdbus:amd64 and fails.