touch-packages team mailing list archive

[Rolf Leggewie <1176686@xxxxxxxxxxxxxxxxxx>]

raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".

** Changed in: qtchooser (Ubuntu Raring)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1176686

Title:
  qtchooser does not properly work with multiarch

Status in qt4-x11 package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtchooser package in Ubuntu:
  Fix Released
Status in qt4-x11 source package in Raring:
  Confirmed
Status in qtbase-opensource-src source package in Raring:
  Confirmed
Status in qtchooser source package in Raring:
  Won't Fix
Status in qt4-x11 source package in Saucy:
  Confirmed
Status in qtbase-opensource-src source package in Saucy:
  Fix Released
Status in qtchooser source package in Saucy:
  Fix Released

Bug description:
  qtchooser reads the path to resolve a binary from default.conf which
  always points to the architecture qtchooser was built for. e.g.
  /x86_64-linuxwhateverblahblah/ on amd64

  this in particular means that if one is on amd64 and installs
  qdbus:i386 it will replace (i.e. remove) qdbus:amd64 and from that
  point on /usr/bin/qdbus (which is backed by qtchooser) will no longer
  work because it will look in the x86_64 path but not the x86_32 one.

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

  this has a rather grave impact on users that get their qdbus replaced
  with qdbus:i386 as large parts of kde software expect qdbus to simply
  work (such as startkde - bug 827815) and even platform stuff does
  (such as the power button handler - bug 1124149).

  and judging from those bugs this can happen rather easily, and has
  already happened to a lot of users.

  to resolve this qtchooser either needs to also look in the 32bit path
  OR the package deps need to be adjusted such that one cannot have a
  mixture of arch packages (which I doubt will be feasible because
  switching the tooling to i386 will likely cause all of kde/qt to be
  switched to i386 too...).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1176686/+subscriptions