File a new bug or re-open an old one
I am not an Ubuntu developer; I learn a lot, however, from lurking on this list. If this is not the right forum to raise this issue, I would be grateful for a pointer in a better direction. I use Kubuntu. I have many years experience at breaking development software and of filing bug reports. Efforts to install Kubuntu Lucid Lynx beta1 on an amd64 machine have generated numerous problems, all of which I have tried to document at Launchpad. The focus of this message is one bug which the Apport retracer on Launchpad tagged as a duplicate. The original bug (of which mine was marked duplicate) was originally submitted on 2009-12-14, that is, as Karmic was approaching release. A fix was released the following day, 2009-10-15. I suspect that I may be dealing with a regression. If I do nothing to flag that concern, there would appear to be a risk that the bug would never come to the attention of a developer. I have therefore changed the status of the bug from "Fix Released" to "New." I also deleted the tag "regression-retracer," and substituted the tag "regression-potential." I personally would always hesitate to re-open a bug once it is marked "Fix Released," and would prefer to file a new bug. The designers of the Apport retracer see matters differently. Are the changes in status to the old bug the best way to signal that it once again requires attention? Is there a better way? -- Bruce Miller, Ottawa, Ontario, Canada br...@brmiller.ca; (613) 745-1151 Just when you think your software is idiot proof, somebody comes up with a better idiot Keyboard not found...Press any key to continue. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
xmodmap evdev and unusable keyboards
Hello all, Since evdev was introduced driving keybords, keyboard mapping with xmodmap has basically changed so keymaps created before end up in unusable keyboard. I've setup https://bugs.launchpad.net/ubuntu/+source/xmodmap/+bug/512622 without response up to now. Further searching showed up several bugs for xorg-server where I found the "mother" bug of that issue https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/255008?comments=all It has a long history, many duplicates, high priority, a fix which doesn't solve the problem - at least not up to lucid alph3, and is assigned to nobody. I'm confused. Can anybody explain what's up there? I think this bug is worth thinking about finding a solution, because every LTS-Upgrader with customized keybord will run in *really* big trouble. regards -- Friedrich Schöne Grüße von der Sonnenalb -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: .desktop files and translations help needed
On Sat, Mar 27, 2010 at 08:10:43AM +0200, Timo Jyrinki wrote: [...] > Any other developer facing similar problems is free to ask for help! > :) The more technical l10n people will be happy to help in the swamp > of gettext and various intltool usage methods. Also if you just want > to figure it out yourself, it's often useful to take a look at some > other well-behaving package, like update-manager (Python) or > update-notifier (C). Siegfried Gevatter and Red Hats website [1] helped me with this one. [1] http://www.redhat.com/magazine/013nov05/features/freedesktop/#intltool -- Name| Richard JOHNSON Title| Developer WWW| http://www.ubuntu.com Email| nixter...@ubuntu.com GnuPG| 3578 0981 A21D D662 2A96 7623 F4C1 838C D8C4 4738 signature.asc Description: Digital signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
