Glad I could help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/313514
Title:
MASTER: evdev driver ignores keycodes > 255
To manage notifications about this bug go to:
https://bugs.launchpad.net/li
First of all I own a Logitech LX710 desktop kit, one single USB receiver
for both keyboard and mouse. You can have a look at the keyboard here
http://launchpadlibrarian.net/21698239/lx710.jpg and see what I mean for
extra/multimedia keys: on the left there is some image editing stuff, on
the left s
Got my keys working thanks to udev, I was remapping to keycodes with no
keysym associated (and avoiding xmodmap as well). WOW, after lots of
waisted hours and after 3 years since I bought this keyboard, I can
finally use all my multimedia/extra keys! Amazing! Thanks X11!
--
You received this bug
Well, I hope for every distribution and developers to move to Wayland as
soon as possible (so we can get rid of this 25 years old X crap), but in
the meantime is there a chance to have keycodes > 255 working with X
without having to poke at input.h every now and then? It there a
solution to easily
Il 08/07/2010 17:22, Sebastien Bacher ha scritto:
>> option allowing the power users to switch from the default fixed timeout to
>> client defined timeouts is easy to implement and
> doesn't disturb anybody that might not care. "why is that so much of an
> issue?". But once again you won't reply.
Il 08/07/2010 13:49, Sebastien Bacher ha scritto:
> bealer, opensource based doesn't mean you can't take design decisions or
> choices,
Right, but it's still possible to suggest a change or feature and maybe
provide a patch for it (often developers don't spend time in features
they are not direc
Il 08/07/2010 10:54, Sebastien Bacher ha scritto:
> The list where the design is discussed, see comment #95
Fine.
>> No, and I'm not the only one. You seem quite sure that the ubuntu team
> is always right and the (l)users are always wrong and, being stupid,
> can't comprehend the great design b
Il 07/07/2010 23:20, Sebastien Bacher ha scritto:
> Could you take those discussions somewhere else as requested before?
Where?
> You
> disagree on the design choices there and don't see the value in having a
> system working on a consistent way
No, and I'm not the only one. You seem quite sure
Il 07/07/2010 12:02, Holger Berndt ha scritto:
> There's a "should", a recommendation. The spec does not demand that the
> expire timeout parameter is respected. (In fact, if it did, it would be
> a fishy spec - an implementation could just as well chose (or offer
> config parameters to let the us
t he wanted or not. So, again, why should developers
spend time using something that comes with no guarantee at all to work
or to work exactly as they expected?
> @Marco Chiappero:
>> And we don't really care about you telling us what's right or wrong for us.
> I am not
Holger Berndt ha scritto:
>> Totally wrong
>
> No, it's not.
I have clear in mind what is the aim of notify-osd. But I still don't
see any reason why that goal is achived by imposing *every* user a fixed
5 seconds timeout.
> I was not talking about what you'd like, but about what notify-osd is
> Guys, you just don't seem to get that notify-osd is about unification
> and consistency amongst applications using it.
Totally wrong, we want to use it exactly for this reason: it's a common
(and nice) interface for showing messages from different applications.
But I can't see how this idea and
As I said quite a long time ago "inconsistent" has no meaning here right
now. Consistent with what? The aspect? Colours? The time you decide is
right for everybody? The time you decide is fine for every message you
don't even know about? And YES, your "inconsistency" IS what WE ALL want
here, even
I'm really really really disappointed.
Sorry Mattew, but what the hell are you saying? "We think we can set more
consistent and reliable durations for users automatically than diverse
application developers ever could manually.". You're not supposed to do that,
you should not do that, you don't
Well, I'm using both beckclear patched and unpatched systems, and I'm
afraid I have to admit that there might be memory leaks in the first
one. However it is the one I use most and often for small amount of
time, so I'm not that sure. In any case, sometimes I see 200-300M (RES),
that it's not very
Maybe I can try to apply ubuntu modifications in the next days, but
where should I find them? Should I start from lm-
sensors-3_3.0.2-2ubuntu4.diff patch?
--
Please merge lm-sensors 3.1.1-4 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/336418
You received this bug notificatio
Please provide a newer lm-sensors version, 3.0.2 is pretty old, Debian
is already shipping 3.1.1 since a while, in both testing and unstable.
--
asus_atk0110 driver not enabled in kernel configuration by default
https://bugs.launchpad.net/bugs/447837
You received this bug notification because you
** Changed in: notify-osd (Ubuntu)
Status: Won't Fix => New
--
notify-send ignores the expire timeout parameter
https://bugs.launchpad.net/bugs/390508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Hi, thinking that notify-osd is an interesting piece of software, I'm going to
write a small program to show messages from my proprietary UPS software to
notify-osd. That said, I totally agree with wirespot and other guys here, but I
prefer not to comment too much the absurd policy of not consid
I can confirm this.
Well, I haven't tried Jaunty yet but using the last vanilla I'm experiencing
the same issue (and same syslog output).
It should be notified upstream.
--
padlock-sha.ko fails to load since 2.6.28-2-generic
https://bugs.launchpad.net/bugs/305934
You received this bug notificati
Same thing here, the module is now compiling and loading fine but X
refuses to start because of the mismatch.
--
fglrx fails to compile with 2.6.27-2 kernel
https://bugs.launchpad.net/bugs/266956
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
21 matches
Mail list logo
