I am no longer able to reproduce this issue on a fresh install using the
Lucid release candidate image. I have tested this issue on 2 machines
that were experiencing this behaviour with earlier versions of quassel-
client-qt4. This issue has now been resolved.
$uname -a
Linux lucid-hdx 2.6.32-21-generic-pae #32-Ubuntu SMP Fri Apr 16 09:39:35 UTC
2010 i686 GNU/Linux
$ apt-cache policy indicator-application
indicator-application:
Installed: 0.0.19-0ubuntu4
Candidate: 0.0.19-0ubuntu4
Version table:
*** 0.0.19-0ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
$ apt-cache policy quassel-client-qt4
quassel-client-qt4:
Installed: 0.6.1-0ubuntu1
Candidate: 0.6.1-0ubuntu1
Version table:
*** 0.6.1-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ lucid/universe Packages
100 /var/lib/dpkg/status
$ apt-cache policy indicator-applet
indicator-applet:
Installed: 0.3.6-0ubuntu2
Candidate: 0.3.6-0ubuntu2
Version table:
*** 0.3.6-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
100 /var/lib/dpkg/status
$ apt-cache policy quassel-client
quassel-client:
Installed: 0.6.1-0ubuntu1
Candidate: 0.6.1-0ubuntu1
Version table:
0.6.1-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ lucid/universe Packages
100 /var/lib/dpkg/status
** Changed in: indicator-application (Ubuntu)
Status: New => Fix Released
--
indicator-application-service crashed with SIGSEGV in
g_type_instance_get_private()
https://bugs.launchpad.net/bugs/551355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
