Re: An example of how things should *not* be done

2008-06-01 Thread Vincenzo Ciancia
Il giorno mer, 23/04/2008 alle 11.36 +0300, Timo Aaltonen ha scritto: > >  > The dexconf approach would only work for tablets, but not pluggable > devices that aren't plugged in during install/reconfiguration. So, a > possible approach would be to use the device manager (jockey) to add > the ne

Re: Wacom config hacks (was: An example of how things should *not* be done)

2008-04-23 Thread Vincenzo Ciancia
Il giorno mer, 23/04/2008 alle 12.38 -0400, Martin Owens ha scritto: > > I'd like my wacom tablet to work, I'd also like not to have X warnings > about it not being plugged in. I'd also like my tablet to work as soon > as I plug it in and not have to restart X every time to get none > mouse funct

Re: Wacom config hacks (was: An example of how things should *not* be done)

2008-04-23 Thread Martin Owens
> The problem in this case is that there's no record of the discussion in > question. Upstream asked for more information about the issue over a > year ago, and it's clear that it's a gdm bug (I've changed the state of > #83860, since there *wasn't* a fix released in gdm). Instead of fixing >

Re: Wacom config hacks (was: An example of how things should *not* be done)

2008-04-23 Thread Matthew Garrett
On Wed, Apr 23, 2008 at 03:41:52AM -0700, Bryce Harrington wrote: > No. That bug was mostly cosmetic IMHO, aside from the .xsession-errors > file growth in Kubuntu. Note there were dozens of other similar bug > reports that derived from this issue. In fact, a lot of users confused > the wacom e

Re: Wacom config hacks (was: An example of how things should *not* be done)

2008-04-23 Thread Vincenzo Ciancia
Il giorno mer, 23/04/2008 alle 03.41 -0700, Bryce Harrington ha scritto: > > Not sure how you missed it, but I was quite explicit in the bug you > reference in stating why my patch was not viable: "However, as others > point out in this and other wacom threads, this [patch] obviously > would > br

Wacom config hacks (was: An example of how things should *not* be done)

2008-04-23 Thread Bryce Harrington
> Please anybody, don't take this e-mail personally. In general, if you need to preface emails with this statement, it's probably a clue you should do more fact checking. Also, note that there is a ubuntu-x@ mailing list specifically for X issues that would be more effective to bring up X issues

Re: An example of how things should *not* be done

2008-04-23 Thread Timo Aaltonen
On Tue, 22 Apr 2008, Dylan McCall wrote: > Ideally, couldn't the install script for xserver-input-wacom add the > necessary stuff to xorg.conf itself? The driver is installed on every system (due to x-x-input-all), so it wouldn't work. The dexconf approach would only work for tablets, but not p

Re: An example of how things should *not* be done

2008-04-22 Thread Dylan McCall
Ideally, couldn't the install script for xserver-input-wacom add the necessary stuff to xorg.conf itself? I imagine that would lead to really ugly xorg configuration files, though, as we see with the old Screens & Graphics tool. I guess what we need is a magical, open-ended and centralized tool fo

An example of how things should *not* be done

2008-04-22 Thread Vincenzo Ciancia
Please anybody, don't take this e-mail personally. I just want to point out an example where a not-so-well-tought decision has caused troubles to a niche of users who are too few to get listened to. I love you all and hardy is really pretty. I report this story here just because I think it has some