Your message dated Mon, 17 Aug 2009 07:29:08 +0200
with message-id <4a88eaa4.2010...@debian.org>
and subject line Re: Bug#536191: Info received (Bug#536191: keytouch: Amarok
plugin saved as XMMS in keyboard file)
has caused the Debian Bug report #536191,
regarding keytouch: Amarok plugin saved as XMMS in keyboard file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
536191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: keytouch
Version: 2.4.1-1
Severity: grave
Justification: causes non-serious data loss
I build this from sid source packages, as suggested by you, the maintainer, and
was instructed to file it as a sid bug. Hopefully this works out. (I had the
same behaviour on stable
Lenny's version of keytouch)
1) When configuring a new keyboard, selecting Amarok plugin, action
play/stop/next/prev, upon saving the file the actual keyboard xml file contains
XMMS instead of Amarok plugin.
2) Search button is configured to launch WWW -Browser plugin ACTION search, yet
KDE 3.5.10 find file dialog box opens up.
3) Eject/BurnCD/HELP buttons are set to launch the programs /usr/bin/eject,
/usr/bin/k3b, /usr/bin/khelpcenter yet they do nothing.
4) Media Stop button is set to Amarok - STOP, yet it actually starts to
decrease the volume. This volume OSD is a small yellow volume bar in the
middle of screen.
5) Volme up/down/mute buttons are using Amixer Plugin - Actions: Increase
Volume, Decrease Volume, Mute and they work as expected.
Not sure how you want me to add different bug reports for the different issues.
Please advise.
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-bpo.1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages keytouch depends on:
ii keytouch-data 2.4.1-1 keyboard definition files and docu
ii libasound2 1.0.16-2 ALSA library
ii libatk1.0-0 1.22.0-1 The ATK accessibility toolkit
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libglib2.0-0 2.16.6-2 The GLib library of C routines
ii libgnome-menu2 2.22.2-4 an implementation of the freedeskt
ii libgtk2.0-0 2.12.12-1~lenny1 The GTK+ graphical user interface
ii libx11-6 2:1.2.1-1 X11 client-side library
ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension
keytouch recommends no packages.
Versions of packages keytouch suggests:
ii keytouch-editor 1:3.1.3-3 create keyboard files for keytouch
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:3.2.0~beta-1
Luke Cycon wrote:
> I am not sure as to why this bug has been reopened claiming that it is
> still present in version 1:3.1.3-3. As of now that version has been
> superseded by 1:3.2.0~beta-1 in both testing and unstable in which the
> bug is fixed. To my knowledge 1:3.1.3-3 is not the current version in
> any release at this moment.
>
> I wont be closing this bug at the moment, I would like to first hear
> from Luk.
The problem was that the bug was opened against keytouch and fixed in
keytouch-editor which meant that it was still seen as an open bug. So I
reassigned the bug to keytouch-editor, though I did not expect it to be
reopened... so closing again.
Cheers
Luk
--- End Message ---
