Kmess do not keep Friendly name after restart.

[SystemArpi]

Binary package hint: kmess

Impact:
Each time I restart my machine I have to set up again my “Friendly name” since the configuration for some reason is not saved.

Patch: http://trac.kmess.org/changeset/5693?format=diff&new=5693

How it's addressed: Patch saves friendly name on exit and restores it on startup.

TEST CASE:
Set a friendly name
Exit
Start kmess again
Note that current friendly name does not match the one set before

Kmess 2.0 for AMD64 (Package installed from repositories)
System: Kubuntu 9.10

ProblemType: Bug
Architecture: amd64
Date: Thu Nov 19 19:50:33 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kmess
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: kmess 2.0-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: kmess
Uname: Linux 2.6.31-15-generic x86_64
XsessionErrors:
 (npviewer.bin:2080): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
 (npviewer.bin:2383): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
 (npviewer.bin:2704): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
 (npviewer.bin:2998): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64
 (npviewer.bin:4784): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64

[Guinnevere (marijke)]

I have the same problem, ever since I updated to 9.10

[Riccardo Iaconelli (riccardo-kde)]

Upstream project has been patched. Can you please send a package update through usual apt means? It's a rather annoying bug...

http://trac.kmess.org/changeset/5693

[Connel Hooley (connelhooley)]

i would like to second Riccardo and request the patch to be implemented through apt or something

[Rivo Laks (rivol)]

KMess 2.0.2 has been released now and includes fix for this bug. Could the Ubuntu packages be updated to that?

[Harald Sitter (apachelogger)]

Lucid fix: sync debian's 2.0.2-1 (Jonathan Thomas is working on that)

[Harald Sitter (apachelogger)]

Karmic fix: patch existing package to include referenced upstream fix per SRU (https://wiki.kubuntu.org/StableReleaseUpdates#Procedure)

[Launchpad Janitor (janitor)]

This bug was fixed in the package kmess - 2.0.2-1

---------------
kmess (2.0.2-1) unstable; urgency=low

  * New upstream release
    - Fixes friendly names (LP: #485640)
  * Update Homepage: http://kmess.org
  * Add Build-Depends: libphonon-dev | libqt4-phonon-dev (ubuntu friendly)
  * kmess.1 fix lintian:hyphen-used-as-minus-sign

kmess (2.0-3) unstable; urgency=low

  +++ Changes by José Manuel Santamaría Lema:

  * Fix FTBFS with binutils-gold. (Closes: #555020)
  * Added 12_rev5667_fixed_likeback_icons_install_condition.diff - without this
    patch the package will not install some icons, specifically those clearly
    visible in the right upper corner of the main window.
  * Bump to Standars-Version 3.8.3, no changes needed.
  * Don't refer to symlinks for text licenses in debian/copyright

kmess (2.0-2) unstable; urgency=low

  * Update debian/watch to handle rc/beta & alpha upstream
  * Include upstream rev5532 - Work around KDE bug #209960 that caused a
    crash when closing the account settings dialog. (Closes: #551061)
 -- Jonathan Thomas <email address hidden> Mon, 21 Dec 2009 18:02:19 +0000

[Harald Sitter (apachelogger)]

Heads up for Karmic:
Currently it does not seem like we will be able to provide a stable release update (which would become automagically available via the regular updates) for karmic, since it appears more difficult to obtain a non-invasive patch for the issue at hand than we originally thought. So at least until we can provide an update (if at all), we backported 2.0.2 to the karmic-backports repository.

The backports are not activated by default. For information on what exactly backports are and what support looks like for them and what quality you can expect at the very least, please refer to [1]. This Ubuntu Help page also explains how to obtain one single package (which in this case would be kmess) and how to activate all of karmic-backports if desired.

[1] https://help.ubuntu.com/community/UbuntuBackports

[Rolf Leggewie (r0lf)]

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